Brief on S4HANA Data model Changes Part1
With advent of S4HANA Product in the market, there comes a lots of buzz around the market.
How comfortable it will be migrating to S4HANA from ECC. And believe me it is not if you are not in the right direction.
Both Technical and functional expertise has to face new challenges as lots of odds coming in their way.
As technical perspective, I have started this blog to share my experience that came in my way.
Also I will be adding more, in my forthcoming post.
The idea of this blog is to keep the message brief and shorts. And share my expertise and odds.
Part1:Data model changes VBUK and VBUP
VBUK is used for SD documents in general, which includes deliveries and billing documents.
VBUP contains the status details of particular items. For every Item there is STATUS details.
In short we can say that, VBUK contains header related status along with other details
and VBUP contains items related status along with other details.
Impact on these table due to to the arrival of S4HANA:
In S4HANA, the usage of VBUK and VBUP has been obsolete. But the business requirement
to use VBUK and VBUP is still there and we cannot afford to loose it.
Alternative of VBUK and VBUP.
a) In S4HANA, lots of new field been added in tables VBAK, LIKP and VBRK to suffice the requirement. so we can make use of that.
b) FM SD_VBUK_READ_FROM_DOC can be use as an alternative of VBUK to read the header related document status fields from VBAK , LIKP and VBRK tables.
FM SD_VBUP_READ_FROM_DOC can be use as an alternative of VBUP to read the item related document status fields from VBAK , LIKP and VBRK tables.
OSS Note 2198647 can be referred for further information.
Reference taken from Simplification List for S/4 HANA 1511 0302.
Any comments and suggestions will be appreciated.