Upskilling from SAP ERP to SAP S/4HANA
ABAP Programming
S4D430 ABAP CDSGW100 Building Odata Services
S4D435 Transactional Apps with CDS based BOPF objects
S4D425 Extensibility for S4
Sales
S4 Migration Logistics
Production
2268088 - S4TWL - Planning File
MRP calculations are complex and therefore an MRP run can be lengthy. An important means to improve MRP performance is net change planning. An MRP running in net change planning mode only plans materials that have experienced a relevant change since the previous MRP run. A material has to be planned by the next MRP if the material was received or issued, if a material requirement like, for example, a sales order was changed, or if master data like the BOM or the product master was changed. The planning file stores the materials that have to be planned by the next MRP.In the classic Business Suite, reports RMMDVM10 and RMMDVM20 made a first setup of planning file entries and checked planning file consistency for operative planning. In SAP S/4HANA, run report PPH_SETUP_MRPRECORDS instead. For long-term planning, the reports RMMDVL10 and RMMDVL20 are replaced by the report PPH_SETUP_MRPRECORDS_SIMU.
Besides the setup reports, which trigger a new planning (NETCH = X) for all objects and also do a consistency check automatically, there are conversion reports PPH_CONVERT_MRPRECORDS and PPH_CONVERT_MRPRECORDS_SIMU, which take over the change flags (NETCH, RESAL, etc.) from the old database table DBVM. In this context it should be checked with the consistency check report RMMDVM10 first, whether the old entries in DBVM are consistent and then conversion can be done.
SAP S/4HANA, on-premise editions no longer supports net change planning in the planning horizon (processing key NETPL). MRP always determines material shortages for all known material requirements. MRP can no longer cover only the material shortages inside a limited planning horizon. This is valid both for the classic MRP and MRP Live.
2268069 - S4TWL - Simplified Sourcing
Simplified sourcing in SAP S/4HANA is simpler than sourcing in the classic SAP ERP for the following reasons:- The different sources of supply are pretty symmetrical. Sources of supply have a temporal validity, a quantitative validity, a deletion indicator, and a "relevant for automatic sourcing" indicator. The sourcing logic can treat the different sources of supply in a uniform way
- Quota arrangements can be used to prioritize any of the possible sources of supply
- Purchasing info records are proper sources of supply. The SAP S/4HANA MRP can select purchasing info records without source list entries. It is sufficient to define the supplier information of a material in the purchasing info record.
- Production versions make sure BOM and routing fit together
- Production versions have always been the only in-house production source of supply integrated with APO PP/DS. With production versions as the only in-house production source of supply, ERP sourcing and PP/DS sourcing become more similar.
- Purchasing info records, contracts, and delivery schedules have always been the external procurement sources of supply integrated with APO. With purchasing info records being proper sources of supply, ERP sourcing and PP/DS sourcing become more similar
- A unified source of supply model is the basis for future innovations in sourcing
Business Process related information
- If you want a BOM or routing to be considered by MRP, you have to create a production version.
- If you want MRP to source a purchase requisition from a certain supplier, you no longer have to define a source list entry. It is sufficient to set the indicator "relevant for automatic sourcing" in the purchasing info record.
Actions required for manufactured materials
- Check if production versions exist for those BOMs and routings that should be considered by MRP. Report CS_BOM_PRODVER_MIGRATION02 can be used to analyze the situation as well as to create proposals for production versions based on BOM validities. Run the report and accept or reject the proposed production versions. Note 2655077 contains report CS_BOM_PRODVER_MIGRATION02.
- Analyze your source list entries: No action is required if source list entries refer to contracts and delivery schedules. S/4HANA sourcing finds contracts and delivery schedules without source list entries.
- Activate the automatic sourcing indicator in the corresponding purchasing info record if the source list entry only refers to a supplier and if the supplier shall be selectable by MRP
2268045 - S4TWL - Storage Location MRP
- The MRP logic is simplified. There is only one solution for planning on storage location level
- The MRP area logic is more advanced than the logic for planning on storage location level. All MRP types and lot-sizing procedures are possible on MRP area level
- The system creates planning file entries on plant and MRP area level. If planning is required on MRP area level, then the system only plans the affected MRP area. The system does not create planning file entries on storage location level and it did not do so in SAP ERP. The SAP ERP MRP had to plan all separately planned storage locations and the plant level every time inventory or an expected receipt was changed in a single separately planned storage location. Planning on MRP area level is more efficient
Sales
SAP Customer Connection for SD Sales and Billing 2019: Delivered Improvements
With the features delivered in the context of the SAP Customer Connection project for SD Sales and Billing 2019, you can benefit from improvements in functionality and usability in the area of ERP Sales&Distribution.2897649 - Description of condition type changeable on price condition record level (part 1)
A language-dependent description field is provided on the detail screen of price condition record maintenance. This is also available for supplementary conditions. This description is then displayed in the pricing result of documents on item level and also provided for output management of these documents. Furthermore the COND_A Idoc for the data exchange of price condition records is extended and taking the description into account (delivered with part 2).
Limitations:
- Change documents for price condition record maintenance do not consider changes of the description.
- The new functionality is only provided for applications V (Sales) and M (Purchasing) and for the usage A (pricing).
- To maintain descriptions in a different language it is required to logon to the system with this language.
- For the ALV on the pricing Ui in a sales order it might be required to define individual layout settings again.
Procurement
2468294 - S4TWL - Determination of default values in Intrastat reporting
With release 1709, the determination of default values for business transaction type, procedure and movement code is as follows:
The determination of the default values for sales is based on the customizing activity “Define Default Values for Sales”. In this customizing activity the default values can be defined depending on country of declaration, sales document item category and material group for export and import. Sales document item category is taken from the billing document and material group is determined from the material and delivering plant. Note that if the material group is not initial and no default values are defined for this material group, the second access with initial value for material group is done for determination of default values in this customizing activity.
The determination of the default values for receipts from supplier in purchasing is based on the customizing activity “Define Default Values for Purchasing”.
The determination of the default values for returns to supplier in purchasing is done in two steps: in the first step, the defaults values for receipts from supplier based on the customizing activity “Define Default Values for Purchasing” are determined and, in the second step, the conversion of these default values based on the customizing activities “Define Business Transaction Type for Returns to Supplier” and “Define Procedure for Returns to Supplier” is done.
The following customizing activities should be used instead:
- Define Default Values for Sales (SM30-view /ECRS/V_TDVS)
- Define Default Value for Purchasing (SM30-view /ECRS/V_T161B)
- Define Business Transaction Type for Returns to Supplier (SM30-view /ECRS/V_TBTR)
- Define Procedure for Returns to Supplier (SM30-view /ECRS/V_TPRR)
2267225 - S4TWL - Foreign Trade fields in Material Master
The below mentioned fields for Letter of Credit/ Legal control/ Export control/ Preference management in Foreign Trade is not available through Material Master:- CAP product list no. (MARC-MOWNR)
- CAP prod. group (MARC-MOGRU)
- Preference status (MARC-PREFE)
- Vendor decl. status (MARC-PRENE)
- Validity date of vendor declaration (MARC-PRENG)
- Exemption Certificate (MARC-PRENC)
- Exemption Cert. No. 9 (MARC-PRENO)
- Iss.date of ex.cert. (MARC-PREND)
- Military goods (MARC-ITARK)
Supply Chain
2210569 - Obsolete Material inventory management transactions
The following transactions for entering and displaying goods movements (material documents) - called "MB transactions" - below, have been replaced by the single-screen generalized transaction MIGO or the BAPI's BAPI_GOODSMVT_CREATE and BAPI_GOODSMVT_CANCEL:MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31, MBNL, MBRL, MBSF, MBSL, MBST, MBSU and MBBM
2542099 - S4TWL - Document Flow Consistency for Goods Receipt to Inbound Deliver
When using transaction MIGO to post goods receipt with reference to an inbound delivery, to cancel a goods receipt with reference to an inbound delivery or post a return delivery by referring to a material document posted with reference to an inbound delivery, the inbound delivery is not updated unless the indicator "Document flow update for stock postings and return delivery" is set in the Global Shipping Data.This indicator in SAP ERP was so far optional and not set by default except for installations where the industry solutions for Discrete Industries and Mill Products have been activated. The implication of having that indicator not set are inconsistent and never completed inbound delivery documents which could not be archived.
In S/4HANA, the update of the inbound delivery is enforced to ensure the data consistency across different applications.
Check the current business process for goods receipt processing whether affected or not by the stricter consistency checks applied. Change the business process by ensuring the inbound delivery contains the correct data prior to posting goods receipt, if applicable.
When the check item is relevant, there are two alternative options to proceed with the conversion to SAP S/4HANA:
- Apply for an exemption for this check item
- Set in all clients of the system the indicator "Document Flow Update for stock postings and return delivery" in the IMG activity “Configure Global Shipping Data” under “Logistics Execution > Shipping > Basic Shipping Functions”.
2267834 - S4TWL - Material Ledger Obligatory for Material Valuation
This simplification makes it mandatory to use the Material Ledger (ML) in all SAP S/4HANA systems. After the technical SUM migration, the Material Ledger needs to be migrated.It is very important to distinguish between Material Ledger, in its role as an inventory subledger in Accounting, and the business feature Actual Costing. Material Ledger, as the inventory subledger, values material inventories in multiple currencies and GAAPs in parallel. In addition Material Ledger is a basic prerequisite for the use of Actual Costing. With Actual Costing you can value your material inventories, work in process, and cost of goods sold with weighted average unit costs that are being calculated after the fact by evaluating business transactions of one or more posting periods. Actual Costing also provides additional features, such as actual cost component splits.
Even though activation of Material Ledger is now mandatory, activation of Actual Costing is still optional.
2270199 - S4TWL - Transportation (LE-TRA)
The alternative functionality is the Basic Shipping solution within SAP S/4HANA, which is already available.The main functions of LE-TRA have already been replaced with selected functions of SAP S/4HANA Supply Chain for Transportation Management.
Comments
Post a Comment