SAP S/4 HANA is the new offering from SAP built on the high performance In-memory platform HANA with an enriching user experience using FIORI apps.This new system includes major changes and massive simplifications ranging form changes in underlying data models to new user interface through FIORI apps.
The objective of this blog is to understand the data model simplifications in SD area through a comparative study with a non S/4 system.
Below are the major simplification points:
Let us understand the differences by looking at the table structures:
Table Name | Description | Append Name |
---|---|---|
VBAK | Sales Order Header | VBAK_STATUS |
VBAP | Sales Order Item | VBAP_STATUS |
LIKP | Delivery Header | LIKP_STATUS |
LIPS | Delivery Item | LIPS_STATUS |
VBRK | Billing Document Header | VBRK_STATUS |
VBAK:
VBAP:
When a sales order is created in a non S/4 HANA system:
Sales Order: 7137:
VBAK table holds the order header details
Order status information is present in VBUK table
Sales Order in S/4 HANA system:
VBAK table contains both the header details as well as the header status
Header status fields are now added to VBAK table
Table VBUK is present but is not filled.
Since the status tables are not being filled it can be questioned why the tables are still present and not removed from system altogether. The reason for this is to enable smooth transition for those opting for migration to S/4 HANA system.
New function modules have been written which read the document status fields from VBAK , LIKP aur VBRK tables and populate in output whose structure is similar to that of VBUK.
For example FM SD_VBUK_READ_FROM_DOC is a new FM that fills VBUK structure for one SD document out of document header tables. The data is fetched depending upon the document type.
Acknowledgment:
Suggestions and Comments Welcomed !!
~Tanmay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |