While performing transports, we have experienced delay in transporting especially when we had about 1000s of transports. In order to improve the ru
While performing transports, we have experienced delay in transporting especially when we had about 1000s of transports. In order to improve the runtime, we followed the below steps to skip the generation step and perform the generation at a later time.
STMS - > Overview -> System -> Choose the System - > Transport Tool
Add an additional parameter generation with value either "false" or "later".
In case of generation = false, the transport system will ignore the generation of the programs, you may have to generate the programs again with SGEN.
With generation = later, the transport tool will ignore the generation of the programs, but the transport request will still remain the import queue. You can use command tp gen all to generate the programs for the transports in queue.
We have a real time interface in one of our ECC system and it is used to receive the IDOCs from the third party application through SAP PI. B
We have a real time interface in one of our ECC system and it is used to receive the IDOCs from the third party application through SAP PI. Basically it is an inbound processing in ECC system, on a fine Monday, all the IDOCs received at the ECC end started queuing up with the Status 75 without any further processing.
Upon our analysis we found that one of the IDOCs got failed and the status was changed to 52 (Incorrect program logic by Developer) which made the IDOCs to get stuck in the queues. Queue is basically defined from PI with message processing order, the same in our case was EOIO (Exactly once in order/ Synchronous), so basically this means only if the Predecessor IDOC is successfully processed in ECC system the successive IDOCs will get processed else this will stay in the ECC (in the queue) . In our case we had a IDOC with status 52, we have requested our support team to clear off the failed IDOC which has the status 52. After clearing the problematic IDOC we ran the report RSINBQUEUE which has processed all the IDOCs those were in queue. We have also suggested our support team to schedule this report in the background to run for every 5 minutes which will take care of processing the IDOCs in the inbound queue. You can also reprocess it using WEINBQUEUE transaction in dialog mode.
Based on the analysis, we could see that someone has played around with the export/import buffer object, they increased it to a value which cannot be accommodated by an Instance. So, we tried to reduce the buffer value to 30k which then resolved the issue.
Parameter Adjusted in Instance Profile : rsdb/obj/max_objects
DpShMCreate: ShmCreate For Key SHM_DP_ADM_KEY Failed