on 10-11-2006 11:28 AM
Hi
We are using Extended Classic Scenario. After the shopping cart is approved, the PO is generated in the backend R/3. The PO is generated in the backend and the idoc is triggered which is sent to supplier.
The problem we are facing is as below:
There are some fields in the idocs which are not getting populated. We are using badi implementation BBP_PO_INBOUND_BADI in the backend. We have used both the methods BBP_MAP_BEFORE_BAPI
BBP_MAP_AFTER_BAPI
The table EKPO is getting updated but the idoc does not have the fields.
Also when we are second time retriggering the output the idoc is having the required fields.
Kindly advice.
Thanks and Regards
Manoj
Hi Manoj,
Which fields are not populated ?
Kind regards,
Yann
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi First time when the PO is generated in the backend, idoc is trigerred and sent to vendors through EDI.
Next time I am manually retrigerring the out message which is trigerring the idoc.
Our doubt is table EKPO is getting updated after the idoc is trigerred during first time. Since next time when retrigerring the idoc, values are already there in EKPO table hence they are getting populating in the idoc too.
Thanks and Regards
Manoj
Hello,
It looks the first generation occurs to early in the process.
Can you should check the processing time you defined in condition records ?
3 is too early, 4 should work because a commit work is done before. And at worst set it to 1 (selection report) and schedule a job to process the message.
Rgds,
Pierre
Hi,
We have not defined any processing time for our output time.
One more thing we have bot Classic Scenario and Extended Classic Scenario. It works correctly for the companies with Classic Scenario but with the companies with Extended Classic Scenario it does not work correctly.
Thanks and Regards
Manoj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.