Skip to Content

Dear,

Here I would like to share some experience when I analyze such kind of issue:
“Very huge records with “Transaction Recorded’ status stucked in SM58 in ERP system.”

Please check all the below points. Points#3 and #4 are usually the ones that need more attention.

1 – Review 527481 -> there should be at least as many dialog as non-dialog work processes. Please ensure there are enough dialogs.

2 – Review 74141 -> ensure that your RFC resources are correctly configured.

3 – Review 1333417 -> Performance problems when processing IDocs immediately

Configure program RBDAPP01 (inbound) \ RSEOUT00 (outbound) to run very specifically for the high volume message types on your system. Schedule regular runs of report RBDAPP01 \ RESOUT00.

You can configure these reports to run every 10 minutes or as often as required. Then change the processing mode for the IDocs in question:

For inbound:
-> go to transaction WE20 -> Select Partner ->
Select Inbound Message Type and change the processing method from “Trigger Immediately” to “Trigger by background program”.

For outbound:
-> go to transaction WE20 -> Select Partner ->
Select Outbound Message Type and change the processing method from “Transfer IDoc Immedi.” to “Collect IDocs”

4 – Check the setting in aRFC monitor

-> Go to transaction SMQS -> Find the target system -> If Max. Conn is lower than 10, or Max. Runtime is lower than 60, please increase them to at least Max. conn = 10 & Max. Runtime = 60

You can refer to Note 1597364 – FAQ: BW-BCT: Extraction performance in source system.

5 – Please also ensure that the RFC tables are consistent, and do not contain too many invalid entries. You can review notes 375566 and 779664 to help you with that. In the later note, report RSTRFCEG can find an remove the inconsistencies, before using it, please make sure all suitable notes who have the code correction for RSTRFCEG have been applied in your ERP system.

Best regards,
Maggie

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply