S/4 HANA Major changes in PTP Area

 

 S/4 HANA Major changes in MM Area 

Material Master :

• The first change is material master field length earlier it was 18 character in ECC now it has changed to 40 characters in S/4HANA.
• However, it is switched off by default. The length of the material is 40 character meaning technically material length take on to 40 characters but by default, it is not set to 40 characters.
• But when we use interface to communicate like sales order, purchase order using IDOC or any other mechanism. SAP is still using old 18-character material length. That is because BAPI and all the system that is built and place are basically with 18 characters. For a functional consultant, the definition of material is 40 character but when it comes to interface, the external system does not know what is the definition of material.

Vendor Master

• Vendor Master Transactions : In S/4 HANA we maintain Business Partner through the  SAP Fiori app. Transactions related to Vendor Master transactions like XK01, XK03, MK01, FK01 are made obsolete in S/4 HANA
• Customer vs. vendor to Business Partner. SAP ECC maintains separate customer and vendor files, even in those cases where an organization partners with a company for both functions. S/4HANA combines common data structure elements into a Business Partner record.
• whereas before in SAP ERP a user might access a supplier using Transaction XK03, this transaction- along with the others listed in the following table-no longer exist in SAP S/4HANA.

Tables:

Inventory management is reduced from 26+ tables to a single table, MATDOC (Material Document line item).

In S/4HANA pricing table “KONV” is replaced by a new table “PRCD_ELEMENTS”.

MATDOC table now contains both header and item data for material documents. Hybrid tables (e.g. MARC, MARD, etc.) still exist, but they only hold master data information. All stock information displayed during a select on those tables is calculated on the fly. The MATDOC_EXTRACT table is used to speed up the summarization of MATDOC table during the on-the-fly calculation of stock figures:

Major Changes in Transactions:

• Restructuring of transactions - Few transactions are made obsolete such as MB01, MB02...MB05, MB0A, MB11, 1A....MBSU. They have been replaced by Fiori apps for the better user experience and improved performance and less load on data bases.
• We Can use MIGO for Goods Movements.
  

MRP:

MRP in ECC is run through batch jobs and during off peak hours. However, there is no need of batch job in S4H and MRP can now be run in real time with HANA.

MRP can be run on plant and MRP area level, but not on storage location level.

In ECC , Storage location can either be excluded from MRP or planned separately . SAP recommends to use MRP area  with MRP type (ND in case of exclusion or VB for re-order point planning) for those scenarios at storage location level. MRP with subcontracting has also been simplified.

Output management:

ECC message determination through table NAST is replaced by Business rule framework plus (BRF +) and target architecture is based on Adobe document server and Adobe forms only.

 

LSMW / LTMC:

LTMC is a newer version/ enhanced version of LSMW

· LSMW – Legacy System Migration workbench

· LTMC – Landscape Transformation Migration Cockpit

 

For the Master/Transactional data transformation, we used to use LSMW from legacy systems like ECC, any other ERP or tally, whatever data like a cost center, profit center, bank, G/L account, BP.

 

When we have more data, we cannot do this one by one manually– so we use a tool like LSMW in past.

And now we have an enhanced version called LTMC.

 

LSMW Vs LTMC: