Report RCCLORD generating multiple IDocs for same Process order

[Former Member]

A Z report has been created which submits RCCLORD report to generate process orders IDocs (LOIPRO).

This program is scheduled as a background job every 5 minutes. Each time this JOB executes, IDocs should be created to send “Process Orders” that were created or changed only once. This JOB Interface should send “Process Order” data at any time that a “Process Order” is Changed or Created only.

For Example: If I create a new “Process Order” now only, and not change it, this “Process Order” should be sent in an IDOC on the next JOB Execution, only. But, what is happening is that this Order is being sent all the time the JOB Executes.

If we search it on WE09 for a particular Process Order on IDOC Segment [E1AFKOL-AUFNR] we will be able to see that this Process Order was sent 113 times or more that is multiple times, Even if this Process Order was not created and was not changed today.

We need to know why the Process Orders are having several IDOCs even if they were not Changed or Created today ??

Please let us know if there are any pre-requisites before using the standard report RCCLORD ??

Any help in this regard is highly appreciated. Thanks in advance.

[Former Member]

plz help.........

[Former Member]

Hi, RCCLORD is not based on change pointers. There is no inbuilt logic to check if the order has been changed after the previous run. What you can do is, create a logic in your Z program to check the CDHDR table to get the list of orders that have been changed, then pass only those order numbers to the RCCLORD. This way, you wont have IDocs for orders which are not changed. Hope it helps.

[Former Member]

hello Sumanth,

Thanks a lot for your reply.

To continue the discussion, in the program RCCLORD as per the Note implementation 599845, we have IMPORT and EXPORT statements to keep track of the orders which have already been sent. But I am not able to understand how the ABAP memory will hold these values even after the session expires in a particular day.

Secondly this scenario is working perfectly in the Production system, but not in Quality. So I just wanted to know if there are any pre-requisite settings that need to be done before using RCCLORD.

And this program will be scheduled in background after every 5 minutes.

Can you please help by providing some more insights into this.

Thanks in advance.

-------------------------------------------------------------------------------------------------------------------------------

* -> import table with already sent orders

  IMPORT gt_aufnrdone FROM MEMORY ID 'LOIAUFNRTAB'.  "N599845

  SORT gt_aufnrdone BY low.                          "N599845

* -> append collected order numbers to global table

  APPEND LINES OF lt_aufnrdone TO gt_aufnrdone.

  EXPORT gt_aufnrdone TO MEMORY ID 'LOIAUFNRTAB'.

[Former Member]

Hi, I thought the IMPORT/EXPORT to memory id work only within a session. What I assume is that this check is present to avoid triggering same IDocs from one session

I am not sure how you are not facing this issue in production, but you can try the solution if no other way.

[Former Member]

Is there any scenario possible that when we have background jobs scheduled every 5 mins, the ABAP memory retains its contents ?

anyways it is strange, it is working in Production but not in Quality.

there are basically 2 requirements.

the changed Process orders IDocs should only trigger and it should not trigger multiple times.

any ideas ? plz help.

[Former Member]

hi ,

i have aquestion.i am a beginner so dont mind.

where is the segments getting populated when rcclord is executed.

is there any particular perform for this in the report?