(SM) support tip: Revision handling during Custom Application Upgrade
What's going to happen if we have a revision of a dbdict and a new revision should be created during Custom Application Upgrade?"
Let's assume that we have the following revision records for the "Example" dbdict: Examplerevision1, Examplerevision2, Examplerevision3.
We've also set the "Max # of revisions" for our dbdict to "3". (Go to "System Navigator" > "Tailoring" > "Database Manager", for "Table" choose "Object" and click "Search", for "File name:" type the name of the table that you're willing to configure, under the "Revision" tab you can find the "Max # of revisions" field)
In our case "Examplerevision1" is the oldest from all existing "Example" revisions.
When a new revision ("Examplerevision4") for our "Example" dbdict is added the oldest existing "Examplerevision1" record will be removed and we'll have the following revision records: Examplerevision2, Examplerevision3, Examplerevision4.
Please note that OOB if the "Max # of revisions" for a given dbdict is not set then the maximum number if revisions is unlimited.
If you find that this or any post resolved your issue, please be sure
to mark it as an accepted solution.
Please also give kudo if you find it interesting 🙂