Professional Documents
Culture Documents
If you have questions during the session please use the Q&A panel
(click on the button
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
in the lower part of the screen). 1
March 2021
Objective Initial Kickoff call Preparation phase Preparation phase Preparation phase Realization phase
Technical Logistics Finance Technical Conversion
Content & • Overview of • Readiness Check • Review STEP02 • Review STEP03 • Review STEP04
bootcamp • Maintenance Planner • Business Partner • Finance preparation • Overview about SUM
Activities • Mutual Expectations • Simplification Items concept • Consistency checks for System
• System conversion Check (tool) • Customer Vendor • Reconciliation Conversion
overview • Custom Code analysis Integration (CVI) • Period-end closing • Execute technical
• System environment • Q&A • MRP activities and conversion including
used • MATNR Extension documentation uptime and downtime
• Q&A • Simplification Items • Simplification Items phases with SUM
Check (Logistics) Check (FI-CO) (DMO)
• Q&A • Q&A • Q&A
Rollout call 1 hour 2 hours 2 hours 1,5 hours 2 hours
Objective Realization phase Realization phase Realization phase Realization phase Review and Feedback
Finance migration SAP Fiori activation Post follow-up activities Custom Code adaptation
Content & • Review STEP05 • Review STEP06 • Review STEP07 • Review STEP08 • Review STEP09
• Post technical • Overview of Fiori • Post activities for CVI • Overview of S/4HANA • Project Experience
Activities conversion tasks deployment options and MRP extensibility options • Feedback
• FI Customizing/Data • SAP Fiori apps • Configuration and • Side-by-side and in- • Certificates
Model impact selection activation of S/4HANA app extensibility • System access
changes • Rapid Activation for Output Management • Custom Code • JAM Group and
• Q&A SAP Fiori in SAP • Activation of PP/DS adaptation material access
S/4HANA • Q&A • Q&A • Q&A
• Q&A
Rollout call 1.5 hours 2 hours 2 hours 2 hours 1.5 hours
ABAP 2 hours
Finance 4 hours
Logistics 2 hours
• Transportation Management
• Q&A
SAP S/4HANA 2020 SAP HANA SAP S/4HANA 2020 SAP HANA
BP APIs
Customer / Vendor Leading Background Leading Background
Data Buffer Object Object Object Object
Get
SAVE CVI
Outbound Customer Customer
Business Business
Partner Partner
Customer APIs Vendor APIs
Vendor Vendor
CVI implementation is a prerequisite for converting an SAP ERP system to an SAP S/4HANA system.
All the customers, vendors, and contact persons must be converted to business partners in ERP before starting system conversion.
Objects in Objects in
SAP ERP SAP S/4HANA
The CVI interface ensures the synchronization between the
Customer business partner object and the customer/vendor objects in both Leading Object
ERP and SAP S/4HANA Business Partner
Vendor Roles
Customer
Vendor
© 2021 SAP SE or an SAP affiliate company. All rights reserved. 13
CVI – Business Process Impact
Purchase Order
PO 4500000004
Partial GR and Invoice
posted
Review POs
4500000005
4500000006
Required actions
» After the system conversion, you should run report PPH_SETUP_MRPRECORDS to populate the new planning file
table with operative MRP records (PP-MRP) and the report PPH_SETUP_MRPRECORDS_SIMU for simulative MRP
records (PP-MP-LTP). Alternatively, you can also use the conversion reports PPH_CONVERT_MRPRECORDS and
PPH_CONVERT_MRPRECORDS_SIMU.
For existing customers who are using the old output management
▪ Data from old Output Management is kept during the conversion
▪ Customizing for old Output Management is kept (Customizing tables are copied 1:1 when converting to S/4 HANA)
▪ Customers need to customize the new Output Management if they decide to use it
▪ Documents started in the old Output Management will still be processed with the old NAST
▪ New Documents will be using the new Output Management only (if corresponding application is adopted already)
▪ New Output Management for SAP S/4HANA only supports the "pure" output channels, while the NAST-based
output is also used for several kinds of post-processing, output management for SAP S/4HANA cannot be used
if one of the following NAST transmission mediums is required:
▪ 8 Special function
▪ 9 Events (SAP Business Workflow)
▪ A Distribution (ALE)
▪ T Tasks (SAP Business Workflow)
▪ Currently, IDocs are not fully supported by the new output management. Their use is restriced to business
applications that previously used NAST. Furthermore, the following limitations apply:
▪ Only output types which can be mapped 1:1 to the NAST-KSCHL can use IDoc.
▪ Only business partner-based communication is supported, but no communication to logical systems (no ALE support).
▪ Manually created output items cannot be used for IDoc, as the partner role cannot be set for such items.
▪ Multi tray output is not yet supported in the new Output Management
Therefore, the recommendation is not to carry out a full conversion, but to establish a coexistence of old
and new output management.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. 22
Using old and new Output Management in S/4HANA
▪ The new BRF+ based output management does not support the dunning functionality for purchase orders
(transaction ME91F). In case if this functionality is needed, the NAST based output management should be
used.
▪ With the NAST based OM all output determination scenarios of the purchase order are supported. You can
switch between BRF+ and NAST based OM at any time - always the actual configured way is used. Already
posted POs are still processed with the OM which was active during the creation of the PO. Default OM in
S/4HANA will be BRF+ based.
▪ As mentioned in note 2292571 you need ADS - requiring a JAVA installation - in case you want to use PDF-
based print forms. The BRF+ method also supports Smartform and SAPscript outputs.
▪ Note that output medium EDI (Idoc) is not fully supported in the new output method, please see note 2228611
for further details.
See note 2344602 - Is it possible to use the old logic of output determination in S/4 HANA instead of
BRF+? For more details
© 2021 SAP SE or an SAP affiliate company. All rights reserved. 23
Additional Information
Common
SAP Advanced Planning and
Master
Planning
Data
Optimization – planning and detailed Live cache
SAP S/4HANA and detailed
scheduling
scheduling
CIF
ERP Database
Roadmap* :
» DD-Scheduling (DDOM)
» Tank Planning, etc…
© 2021 SAP SE or an SAP affiliate company. All rights reserved. 28
Manufacturing & Supply Chain Integration in SAP S/4HANA
Supporting all levels of Manufacturing complexity Digital Manufacturing
Digital Supply Chain
MANUFACTURING & SUPPLY CHAIN • Integrated Business Planning (IBP)
Suite** • Responsive manufacturing (ME, MII, QIM, VE)
• Production operations (MII, QIM)
• SAP Global Track & Trace
OP or STE
4. Basic EWM
5. S/4HANA Cloud
6. Advanced EWM
Stock Basic Advanced
IM WM Room Mgmt EWM EWM 7. Decentral LE-WM
8. Classic EWM
Netweaver
WM S/4HANA 9. S/4HANA EWM
EWM
(LES) EWM 10. Non-SAP WMS
S/4HANA
MTE
Cloud
WMS
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
non-sap 38
Option 1: MM-IM managed warehouses
Main Characteristics
• No storage bin management
• Pure “total” quantity management (e.g. which product, which batch, which stock type)
• Basic pallet (i.e. handling nit) processes only
SLOC#1 • No system guided, controlled warehouse operations
IM
Main Characteristics
• Relevant for small warehouses with manual operations
• Storage bin management, basic operations
• No enhancements nor development plans
SLOC#2 • LE-WM is part of the compatibility scope in S/4HANA, hence usage rights will expire end of 2025
WM
Main Characteristics
• SAP introduces stock room functionality as an offering for existing LE-WM customers
• Compared to the LE-WM in compatibility scope, functionality is reduced (e.g. no Task & Resource Management, no
Value-Added Services, no Cross Docking, no picking waves, no WM-LSR)
• Relevant for small warehouses with manual operations
SLOC#3
• Storage bin management, basic operations
• No enhancements nor development plans
Stock room mgmt.
Main Characteristics
• Basic warehouse management provides support with and real-time transparency into managing and processing material
movements flexibly based on embedded EWM
• SAP‘s strategic warehouse product
SLOC#4
• Continuous innovations (e.g. FIORI, Analytics, …)
• Limit scope to business necessary by project and template definition (e.g. limited nodes in warehouse monitor, FIORI
apps only, limited strategies …)
Basic
EWM
Main Characteristics
• Full functionality of SAP EWM can be enabled
• SAP‘s strategic warehouse product
• Continuous innovations (e.g. FIORI, Analytics, …)
SLOC#6 • Limit scope to business necessary by project and template definition (e.g. limited nodes in warehouse monitor, FIORI
apps only, limited strategies …)
EWM
Activities:
• Logistic post-conversion
• Output Management
• PP / DS
• Situation Handling (optional)
or
Mail: sap10steps2s4@sap.com