Multiple billing documents generated with Idoc WPUUMS

[former_member1265754]

Hello

SAP Module: IS Retail

Question about processing of IDoc WPUUMS (Consolidated Sales Data)

I have identified that when an error is found in the processing of the Idoc WPUUMS segment E1WPU02, it generates multiple billing documents, which makes it difficult to obtain all the information required for the financial reports.

Example, the following iDOC simulates an error in the second segment E1WPU02

In this scenario, the Idoc generates 1 billing document with the first segment , cuts the billing document when it finds the error, and generates another document containing the information of segment 3 and 4 .

The question is if there is a way to control the behavior of WPUUMS idoc processing in such a way that it does not generate any document until no error occurs, in order that an Accumulated sale idoc only corresponds to one invoice.

[andras_strobl]

Hello Ruben,

You cannot influence the behavior to achieve this. The idoc segments of splittable idoc (like WPUUMS) are processed in ranges. When a range must be split due to an error, the follow-on documents of the processed range are posted, then erroneous segment(s) are handled and stored, and the program proceeds with the rest of the segments like above, and building new range for processing.

So, despite of your request makes sense, the logic of the program does not allow such option.
I also remark, using non-splittable Idocs (e.g. WPUBON) will not post partial follow-on documents, any document will be posted, if everything was error-free during the IDoc's processing.

Best regards,
Andras

[mardi-cts]

Hello Andras, Ruben

Yes, the splitable idoc in WPUUMS is standard SAP behavior the same happen to my current set-up.

But the problem we face now, due to one of article having error in certain condition the splitting idoc is not working properly. Instead skip the error article and repost, it will again repost all correct articles causing duplicate sales. We suspect because we schedule RBDMANI2 program to reprocess fail WPUUMS idoc in background. And this idoc error (status 51) could repost the same billing document 2 or 3 times.

Any idea to stop this duplicate posting? Or should we stop running RBDMANI2?

Thanks,

mardi

[andras_strobl]

Hi Mardi,

The behavior described by you is not expected at all, and I cannot give you general hint on how to overcome this.

I've seen many similar cases with various reasons; majority was caused by COMMIT WORK command implemented in user exits/BAdIs somewhere within the inbound process (can be either MM, SD, FI related...). So, if you are good at debugging, you can put a breakpoint on COMMIT WORK commands and make sure that no custom codes stop with it during processing of WPUUMS IDoc(s). Otherwise the issue needs different approach of analysis.

BR,
Andras