(Simplification Name)
15th January,2018
• Conversion pre-check • The multi-system landscape need to be considered where not all related
• Activation of the Extended Material Number Functionality systems are able to deal with a 40 character material number
• Settings need to be adapted to allow a field length of more than 18 • Code in the system must guarantee that all relevant bits of code can handle
characters - Transaction OMSL 40 characters. It's especially important to ensure that the material number is
not truncated to its former length of 18 characters, because this would result
in data loss
• MRP Storage location replaced by MRP areas • Simplification of MRP Functionality is done for Material
• Material Master: Impact on Foreign Trade Functional Fields in Master
Transactions- MM01/MM02/MM03
• A new material type SERV(Service Materials) is introduced • Leaner and simplified look
DIEN SERV
DIEN SERV
• All existing IM transactions starting with MB** has been made • MIGO, a single-screen generalized transaction
obsolete (supports only for MIGO*) • New enhanced and improved lock concept for MIGO . Lock
• MB** - MB1B , MB1C , MB1A , MBST …etc concept is for
• The transaction MMBE_OLD has been replaced by transaction - Prevent parallel change of master data attributes
MMBE. Alternatively there is also the Fiori App Stock - Defined sequence of material documents (e.g. for moving
Overview average price).
• The double-maintenance of the transaction families MIGO - Consistency with stock quantity (check availability if
and MB* delays the processing of problems with MIGO and negative stock is not allowed )
other transactions, and reduces the development capacity
provided for continuous further development. Therefore, the
discontinuation of the double-maintenance is also in the
interest of all SAP customers
Required and Recommended Action(s) Business Impacts
• Use transaction MIGO and MMBE in dialog. • Replace customer coding using
• MB** transaction codes shall not be used in customer coding especially MB** by make use of BAPI_GOODSMVT_CREATE
with S/4HANA OP1610 and higher
MB03 by make use of MIGO_DIALOG
MBST by make use of BAPI_GOODSMVT_CANCEL
• Study the current foreign trade systems and decide the future plan of action • Additional functions for import and export management are available with
(Go or no Go for GTS ) SAP GTS
• For Legal Control and Preference Management, you can use functions based
on SAP GTS
• Letter of Credit is planned to be covered by Treasury and Risk Management.
• Customers using 3rd Party software for foreign trade processing will need to
realign their software with the new S/4 HANA design
• New Header authorization object that enables the system to • New authority concept for supplier invoice enables a
perform simplified handling especially for invoice items w/o PO
- Check header data against the header authorization object – reference
Company Code (M_RECH_BUK) • Simplify and standardize the authority concept for supplier
- Check item data against the item authorization object ex- invoices
Plant (M_RECH_WRK).
• Users working with supplier invoices, additionally need the authorizations • The previous concept was based on checking header data against the item
based on M_RECH_BUK authorization object for all items.
• Mandatory to use the Material Ledger (ML) in all SAP • Flexible valuation methods in multiple currencies
S/4HANA plants . • Parallel accounting standards
• Actual Costing features like -value of inventories , cost of
goods sold , ..etc possible due to ML
• Cleaner and more consistent valuation
• Inventory account balances are calculated separately in multiple
currency
• After S4 HANA conversion need to do Customizing migration and Data • If customers are not already using the material ledger, it will be activated
migration for material ledger . during the conversion process. In MM02 and MR21 material prices can now
• Migrate the Material Ledger even if already using the Material Ledger in be maintained in multiple currencies
source system