Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Idoc management

Former Member
0 Likes
882

When i upload some idocs with a report z in a job some of them can get in error status, and when i change them in we05 and reprocess them with we19 or bd87 the system creates me new idocs and this can be make many times, so i get many idocs, is there any possibility to avoid this functionality or to follow the idocs process for control the "real" nedded idocs?.

Thanks in advance

regards

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
849

Hi Carlos,

It should not create new IDoc number when you edited and saved the segment data of existing IDoc via transaction WE02/WE05.

It should ONLY change the IDoc status either 32 (for outbound) or 69 (for inbound). Then you can use standard either program RBDOUTPU (for outbound) or RBDINPUT (for inbound) to reprocess the edited IDoc.

If you are using WE19, then system will generate new IDoc.

Hope this will help.

Regards,

Ferry Lianto

When i upload some idocs with a report z in a job some of them can get in error status, and when i change them in we05 and reprocess them with we19 or bd87 the system creates me new idocs and this can be make many times, so i get many idocs, is there any possibility to avoid this functionality or to follow the idocs process for control the "real" nedded idocs?.

Thanks in advance

regards

5 REPLIES 5
Read only

Former Member
0 Likes
849

The only thing i want is reprocess the idoc without creating new idoc.

Thanks in advance

Regards

Read only

0 Likes
849

The real problem is not the we19 or bd87, the real problem is that when i go to we05 and change data, when saving it generates a new idoc.

Thnaks in advance

regards

Read only

0 Likes
849

Hi Carlos, This is how the standard SAP works. Actually when ever you try to edit an existing IDoc either in we02 or we05... A new IDoc will be created which is a copy of Original IDoc before the change. The reason can be like you would not loose the track of the changes that were made. In other terms maintaining a sort of versions.

I dont think you can avoid creating new IDoc's when ever you try to edit the existing one.

Regards,

Swaroop Patri.

Read only

Former Member
0 Likes
849

BD73 is the transaction to re-process an existing IDoc. You can re-process it as many times as you like until it is posted complete. It won't create a new IDoc like WE19.

Read only

Former Member
0 Likes
850

Hi Carlos,

It should not create new IDoc number when you edited and saved the segment data of existing IDoc via transaction WE02/WE05.

It should ONLY change the IDoc status either 32 (for outbound) or 69 (for inbound). Then you can use standard either program RBDOUTPU (for outbound) or RBDINPUT (for inbound) to reprocess the edited IDoc.

If you are using WE19, then system will generate new IDoc.

Hope this will help.

Regards,

Ferry Lianto