It is noticed that job for report BUPTDTRANSMIT processing was not completed but occupies the process.
The reason of this symptom:
Number of entries in table BUT_TDTRANS were high. The time taken to execute is directly proportional to the number of entries in the table BUT_TDTRANS.
How to solve this symptom:
1.Reduce the number of entries in BUT_TDTRANS table.
To reduce the number of entries in BUT_TDTRANS table. You need to schedule a background job (daily) for report BUPTDTRANSMIT giving a package size such as (500/1000). While it is running keep a check on the BUT_TDTRANS table if the count is decreasing or not.
To reduce the number of entries in BUT_TDTRANS table, you need to create report ZBUPTDTRANSMIT according to note 2151842 - BUPTDTRANSMIT performance problem from but000_swap and outbound and run it instead of BUPTDTRANSMIT. The report ZBUPTDTRANSMIT is used just once to get the data aligned. You need to execute this report only once. After this the entries in BUT_TDTRANS will get reduced, that is, all the data for till the current date will be distributed to the applications. Afterwards the "normal" report BUPTDTRANSMIT can be used again.
2.Note needs to be implemented in your system
SAP note 3200572 - To correct the standard report BUPTDTRANSMIT. This Note will make the data run in parallel processing which will enhance the performance.
Other questions:
How does this report BUPTDTRANSMIT work?
All the records that have become valid in the meantime are determined from table BUT_TDTRANS and are read subsequently together with the table key of the respective business partner tables. The records that are marked as containing errors by at least one application, are recorded application-specifically in the table BUT_TDMISS. Only when a record has been distributed successfully to all applications is it deleted from the table BUT_TDTRANS (and if necessary, also from BUT_TDMISS). The date of the last erroneous and the last successful BUPTDTRANSMIT run is recorded subsequently in table BUT_TDAPPLI for each application. This date should be updated daily as the report is meant to run on a daily basis.
When can run report BUPTDTRANSMIT
This report is meant to run on a daily basis. You can run this report in any hour where there are no other jobs running such that it doesn't affect the CPU memory.
Why the number of entries in table BUT_TDTRANS were high?
The number of entries were high because the data was not distributed in timely manner. It is always recommended to run the background job for the report BUPTDTRANSMIT on a daily basis. So that the number of entries will no increase and the data is distributed consistently.
Is it normal that the data continue to increase? It may happen again in the future, is it necessary to do this every time it happens?
You need to schedule a background job for BUPTDTRANSMIT report. Then, as this will be running daily, this issue will not occur.
Is it correct that the number of entries of the table BUT_TDTRANS becomes 0?
Not really. After you execute the report, the entries in BUT_TDTRANS table will get reduced, that is, all the data for till the current date will be distributed to the applications. The data for the future dates will still be there.
Further question about report ZBUPTDTRANSMIT:
- How to create report ZBUPTDTRANSMIT
See How to create report ZBUPTDTRANSMIT
- Would running report ZBUPTDTRANSMIT have any impact on the system?
It will have no negative impact. The report ZBUPTDTRANSMIT is used just once to get the data aligned. Afterwards the "normal" report can be used again. How do I check the behavior/result of report ZBUPTDTRANSMIT after execution?
You can check the entries in table BUT_TDTRANS.
Will it cause any problem to run report ZBUPTDTRANSMIT in a development/verification environment that is currently working properly?
No. But, there is no need to run the report if its working properly.
Best regards
Sherry
