May i seek your advise on a best feasible solution for tracking changes and maintaining the change history for Reservations for transactions MB21/MB22 and MB23.
Finally we had withdraws the solution to activate the table RESB and designed a custom solution to avoid conflicts to the existing reservations which are in millions.
you can activate the chang log at table level in SE11.
SE11,
enter table RESB
click change
goto the technical settings tab.
at lower part you will see the field for change log.
for activation you need a key from SAP.
(I would not do that, as too much logs slow down performance. and RESB is a pretty central table that gets often changed from production and process orders, as well as maintenance orders, so the log file can become huge.)
AUT10 is a nice transaction, but it costs as well performance and space.
you will never see the changes in MB2x transactions, as it is a different way of logging changes.
changes that you can access from within a transaction like ME53N are stored in table CDHDR and CDPOS, for this you need to have coding in the maintenance program to write and display changes. This is not present for the reservations.
Hence you can only log changes at table level. this can then be reviewed with extra reports like RSSCD110
Thanks for your valuable feedback, does it mean that even with custom solution by using User Exits (Menu Exit) we cannot track the changes to display with the transactions MB2X ?
My thaught was to create a custom table where we will track all the changes from the table level RESB and associate them with the MB2x transaction, will this approach not work ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.