Type of activity change from ECC6.

0 to S4/HANA

1) Master Data Changes

The customer/vendor master will cease to exist in its current form and will be replaced by
Business Partner functionality (Bupa). SAP is also remove many of the standard transactions like
XD01, XD02, XD03, VD01 etc.…This raises a lot of questions:

Business Partner will be used for centrally managing Master data for business partners,
customers, and vendors. With current development, BP is the single point of entry to create, edit,
and display Master data for business partners, customers, and vendors.

During the system conversion existing SAP customers have to migrate Supplier and Customer
data into the Business Partner using the Customer Vendor Integration.

There are certain limitations with the current Customer Vendor Master data, not all necessarily
apply to all industries/ businesses: Only one single address, No relation between a vendor and a
customer for the same real world entity (no role concept), No persons (B2C), No time-
dependency.

With Business partner: general data shared across different roles in BP. Roles 1: N (Customer,
Vendor, HR personnel etc.), one BP can have multiple addresses, time-dependent object
attributes & relationships. CVI Integration component ensures the sync between BP object and
customer/vendor objects.

The existing data structures, T codes will be phased out and all of the Business Partner data can
be found in tables: BUT000, BUT020, BUT* etc. DEBMAS/CREMAS etc. Idocs are still
supported.

Activity – Customer master creation/change/display T code is ‘BP ‘instead of XD01/XD02/XD03.

2) Functionality Changes

1. Credit management replaced by Financial Supply Chain Management. The traditional FI/SD
Credit Management will be phased out in S/4HANA, and we will need to use FSCM.You need to
carry out a migration from FI-AR-CR to FIN-FSCM-CR.

Activity – For assigning the credit limit of a customer we are using T code – UKM_BP or BP
instead of FD32. In BP we should select role UKM000 – Click on credit segment data.
Transaction VKM1 is replaced by transaction UKM_MY_DCDS because of additional
authorization. For details follow note – 2227014, 2217124

2. Rebate Management is replaced by Settlement management in S4H. Exception: CRM TPM.

CRM TPM customers can still use SD Rebate Processing for their business process, but have to
adapt to a SAP S/4HANA optimized solution. SAP note 2535889

Activity – Settlement management we can process according to following path:

Logistics – General -> Settlement Management -> Condition Contract Management -> Condition
Contract Conditions -> Purchasing -> Define Condition Type Groups
3. Revenue Recognition SD-Revenue recognition is not available within S/4HANA. The new
functionality SAP Revenue accounting and reporting functionality has to be used instead.

4. Advanced ATP replaces ATP new Back Order Processing functionality and much interactive
delivery scheduling.

5. Output Management Traditional approach is NACE and table: NAST, which is going to be
replaced by BRF+ (Business Rules Framework Plus). In SAP S/4HANA, the target architecture is
based on Adobe Document Server and Adobe Forms only. Old billing documents that will be
migrated and have been processed on NAST can use this technique. For all new billing
documents, new output management has to be used. The BRF+ supports only: PRINT, EMAIL,
XML and IDOC, others not available by default.

3) Data Model changes/Simplification

1. Status tables VBUK/UP moved to respective documents: VBAK/VBAP for sales order,
LIKP/LIPS for deliveries, VBRK/VBRP for billing documents. OSS Note 2198647
2. Document flow table VBFA simplified- new user interface combining doc flow and status
3. Document index tables: VAKPA, VAPMA, VLKPA, VLPMA, VRKPA, VRPMA eliminated and
replaced by equivalent compatibility CDS views with same performance
4. Rebate index table VBOX eliminated
5. VBTYP field length extended to 4 character
6. NAST table phased out and a new Business Rules Framework based output control. The old
documents created in SAP ERP will continue to have entries in NAST
7. Change of Pricing result persistency enhancements: Some fields are being extended-
DZAEHK, KOLNR. KONV replaced by new table: PRCD_ELEMENTS