12-04-2014 2:28 PM
Hi Experts,
we have an issue in which Purchase Orders are created in SRM system. They are then passed to ECC system via PI system.
I would like to know is there any way we can block/check these Purchase orders as these POs have some incorrect data. I dont know where should i check/debug the issue as there are 3 systems involved.
As per my understanding, I have to block/stop these POs in a queue when they are coming from PI to ECC. and then debug from the queue.
i am not sure if i am correct or if there is any other way of doing it. Can anyone throw more light on the solution.
Thanks
Meenakshi
12-04-2014 8:25 PM
Hi Meenakshi,
If you like to stop and debug the POs reaching ECC you can just deregister all the Queues in ECC or the specific queue where the POs are send using the T code SMQR.
Once the Queues are deregistered none of the messages reaching ECC will processed automatically and all will be put on ready status. Open the inbound Queue using the T code SMQ2 and find the Message which you can to debug, single click on that message --> Edit-->debug LUW.
You can try the below approach as well based on classic or extended classic scenario.
To debug PO transfer ,
1, Set Breakpoint in FM Meta_bapi_dispatch
2, retransfer the PO or create a new one,
3, When BP is reach, F7.
4, Find a sentence "call function call function " , double click the function , it is the driver determined from table BBP_FUNCTION_MAP.
5. F5 , go in to the determined driver , find BBP_PO_INBOUND F5 to dialog in to the backend system and find form PO_CREATE where is BAPI_PO_CREATE1 is called , which will issue the backend error .
Regards,
Suresh
12-04-2014 8:25 PM
Hi Meenakshi,
If you like to stop and debug the POs reaching ECC you can just deregister all the Queues in ECC or the specific queue where the POs are send using the T code SMQR.
Once the Queues are deregistered none of the messages reaching ECC will processed automatically and all will be put on ready status. Open the inbound Queue using the T code SMQ2 and find the Message which you can to debug, single click on that message --> Edit-->debug LUW.
You can try the below approach as well based on classic or extended classic scenario.
To debug PO transfer ,
1, Set Breakpoint in FM Meta_bapi_dispatch
2, retransfer the PO or create a new one,
3, When BP is reach, F7.
4, Find a sentence "call function call function " , double click the function , it is the driver determined from table BBP_FUNCTION_MAP.
5. F5 , go in to the determined driver , find BBP_PO_INBOUND F5 to dialog in to the backend system and find form PO_CREATE where is BAPI_PO_CREATE1 is called , which will issue the backend error .
Regards,
Suresh