Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why do the transactions SE95 and SPAU display so many objects after an upgrade from a Release prior to 4.5A to Release 4.5A or higher?

April 26, 2017display objects prior release se95 spau transactions upgrade

0

Posted

Why do the transactions SE95 and SPAU display so many objects after an upgrade from a Release prior to 4.5A to Release 4.5A or higher?

1 Answer

0

Posted

When you upgrade from a Release < 4.5A to a Release >= 4.5A, the modification adjustment (SPAU) is converted. During this upgrade, the system adds all objects to the Modification Browser (SE95) display that were edited in customer requests. Complete objects with a separate object catalog entry (R3TR) are broken down into all existing subobjects (LIMU). When you upgrade your system or import a Support Package, the system offers a subset of the objects modified for the modification adjustment in the transaction SPAU. This subset includes those objects that were reimported with the upgrade or Support Package.