BAPI_PO_CREATE1 : missing del indicator on a service line

Question

Hello gurus,
I'm facing a problem in the first distribution of a Purchase order (created from a Purchase Requisition) from SRM. The problem occours only if the PO has been created from a PR taken from the sourcing cockpit in SRM and happens only on a specific system/backend.
The problem is that a service line marked as deleted in SRM is transferred WITHOUT the deletion flag; in other systems I can test on, the outline is correctly transferred with the deletion indicator (ESSL-del = 'X').
Seemed a problem that could be easily investigated in debug; however, I tried a bit without success by tracing a parallel debug on a "correct" system; I can advice a difference only after a "perform get_current_data", that is to say, last step of the BAPI, when the creation process of the PO has already been done (and just await a commit).
In order to realize at which point and why the deletion flag on the service line is removed, I tried to investigate the class CL_PO_ITEM_HANDLE_MM; it contains an interface, IF_SERVICES_MM, which offers just three methods: GET_DATA, SET_DATA and GET_SRV_DATA. I expected to find a setter method for service data, but I was wrong.
The SET_DATA method is used once during BAPI_PO_CREATE1 execution and passes parameters concerning the ITEM position (im_comsrv) and acconting-related data (lt_acc_tab), so I didn't understand where the PO object in the BAPI is updated with service items data. That should be an useful starting point in order to backtrack and solve the problem; I guess that something goes wrong when the PO position is related to the corresponding PR position, but no idea about how to identify that point on the code.
Any clue or suggestion will be highly appreciated
ps: obviously, data passed at BAPI_PO_CREATE1 are identical for both the "OK" system and the "KO" one. Tried also to analize the stack trace by using SE30, but the call sequences are really complex and not easy to compare. A nice-to-have feature could be to track the entire code executed, row by row, on each system, but I guess it's a task impossible to manage.
Edited by: Matteo Montalto on Jun 17, 2010 4:31 PM

Answer 1

you can either share your code and your source file to have the people check if the error is on your part or you can directly contact SAP if you are the opinion that it is an error in their BAPI code.
But without looking at code and source file it is not possible to do any evaluation except you are looking for clairvoyants