In this document I will outline the concept behind SPDD and SPAU and how modification adjustment transport requests should be created for automatic handling of adjustments during Support pack activity. This document can be used when handling adjustments using SPAM/SAINT tool.
During the SPDD_SPAU_CHECK phase of the support pack activity, SPAM tool scans for modified objects in the system. It compares the modified objects identified in the system to the NEW objects coming via the new support pack which are being applied in the current support pack queue. The modified objects consist of the repository and the dictionary objects. Modified objects mean SAP standard objects which are modified by the customer to suit their need. The tool makes a list of these objects and sorts then into type SPDD and SPAU. Objects classified under SPDD are dictionary objects( tables , structures, views etc. ). Objects classified into SPAU are repository objects ( Screen elements , reports, programs etc. ) .
Consider we have a 3 system landscape with SID’s DEV, QAS and PRD all in same transport landscape and domain controller. Initially the support packs are applied on DEV system. During the SPDD/SPAU phase we perform the adjustments on DEV system. The adjustments are locked in adjust modification requests. So we will create one request for SPDD and one request for SPAU. The objective now is that adjustments have to be handled automatically in QAS and PRD system.
Now the correct way to perform this as below. Consider we have one request for SPDD and one for SPAU. Please be aware that you need to release only the tasks. Not the request. The transport request will be released later by the system when we are tagging this as the adjustment transport request as shown below. If you have already released the transport request, you may have to create new transport request by including the objects or a transport of copies.
We have to assign the newly created transport for SPDD or SPAU or as below. Go to SPDD or SPAU screens after the requests are created.
- Click on the Assign transport button
- Furnish the Request/Task
- Sometimes you may have created several transport requests for SPDD or for SPAU. Now you can merge all these transport requests into a transport of copies. In that case make sure you Change the “Request Type” to transport of copies by “Transport of copies “ and below
- Click on the Check button once done. The following screens are as below
- You will get the below message at the bottom of the screen once you press “YES”
Now when the request will be appended with request attributes which you can see via SE01. Basically the SPAM tool will compare the support pack level in the request attributes and only if the support packs level matches, the transport request will be accepted as an modification request. During the SP activity you have to provide these transports when modification adjustment pops up comes. This is the same procedure to be followed for both SPAM and SAINT.
In case you are using SUM tool, then you have to use 2 separate requests for SPDD and SPAU and furnish them during the configuration roadmap step when the tool asks you.
- 1) SPDD has to be handled when SPAM/SAINT pops up for SPDD adjustment. If you skip SPDD when it is prompted all you dictionary modifications will be lost
- 2) You are not supposed to import any transport requests during support pack activity as these transport requests may corrupt the transport programs responsible for support pack activity. Always include the modification adjustment transports for automatic SPDD/SPAU handling.