Hi there,
We are running SRM 5.0 and are running ECC 6.0 in the backend. We are NOT using the extended classic scenario, only the classic scenario.
We are creating shopping carts in SRM with reference to a contract and then the system tries to create the PO in the backend system but fails because the contract reference does not exist in R/3 (message 06 019 in transaction RZ20.....).
What I am wanting to know is I need to debug this scenario much better. I have debugged the shopping cart save function module and realise alot of the work is done in UPDATE TASKS etc. I have turned on "update debugging" but it is still a very lengthy process to get to the route cause of this......
I have implemented BOTH the BADI's BBP_CREATE_BE_PO_NEW and BBP_CREATE_PO_BACK and they are definetly ACTIVE. I then set an ENDLESS LOOP in ALL the method calls so that I may be able to debug the process from SM50 but it never breaks in the code. I have also implemented an enhancement spot in BAPI_PO_CREATE1 that also hase an endless loop in it so that I might be able to also debug in SM50 on the ECC side of things.....but it still doesn't break!!
As I mentioned earlier I can see shopping cart monitor details in transaction RZ20 that say "Document XXXYYZZ does not exist" (I think message 06 019). But I would assume also that that error message would come back from the BAPI_PO_CREATE1 function module......but obvioulsy there must be some "pre checks" in ECC before the function module is called.
While I was debugging I found a MAPPING TABLE called BBP_FUNCTION_MAP that seemed pretty promising....
So my question is: why do those IMPLEMENTED and ACTIVE BADI's not break at all? And why does the endless loop never run in BAPI_PO_CREATE1 ? Do they only work in the EXTENDED classic scenario? Are other function modules called in the classic scenario?
PLEASE help me, I am really battling on this......;-)
Thanks in advance
Lynton