cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SOURCE OF SUPPLY DISABLE NOT WORKING FROM ECC TO APO

former_member203215
Participant
0 Likes
407

When i do CIF from ECC to APO with deletion flag that is not reflecting in APO through

/SAPAPO/CIF_TPSRC_INBOUND

even i checked SPRKZ = 'X' IN IT_CIF_TRPROD the value is not getting reflected in

/N/sapapo/tl3 transaction.

Thanks

Ravichand

Accepted Solutions (0)

Answers (1)

Answers (1)

I310607
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Ravichand,

It depends on what object are you transferring. You can follow the way of your object through the below call stack: (such call stack can be found in the SCM APO MD Call Stack Library). More on T-lanes in general can be found here.

The TRPROD is formulated from TPSRC entries, so setting the flag for IT_CIF_TRPROD may not take an effect. Again it is rather best to see how the standard path would create (and why it does not create) the flag (SPKRZ) on the below stack:

Best Regards

Gergely

  10  WRITE_CD_TLANE_OBJECTS(/SAPAPO/LOO_TR_WRITEF53) 
 9 /SAPAPO/TR_TLANE_POST
 8  PREPARE_TRANSFER_TO_DATABASE(/SAPAPO/LOO_TR_TRANSFERF02)
 7 /SAPAPO/TR_TL_TRANSFER
 6  UPDATE_TRPROD(/SAPAPO/LMAINTAIN_TPSRCDB1)
 5   UPDATE_TPSRC_SYNC(/SAPAPO/LMAINTAIN_TPSRCDB1)
    > Call BADI (User-Exit) for TPSRC data  SE18  /SAPAPO/PWB_TPSRC_IN  interface /SAPAPO/IF_EX_PUR_TPSRC_IN
 4 /SAPAPO/DM_TPSRC_UPDATE_POST  > (or *insert_post) 
 3  /SAPAPO/DM_TPSRC_MAINTAIN
 2 /SAPAPO/CIF_TPSRC_MAINTAIN 
    > CALL BADI lr_ref_cif_enhance->change  SE18   /SAPAPO/CIF_ENHANCE_TPSRC  interface /SAPAPO/IF_CIF_ENHANCE_TPSRC
    > CALL BADI lr_ref_cif_enhance->delete
 1 /SAPAPO/CIF_TPSRC_INBOUND 
    >  CALL CUSTOMER-FUNCTION '001'  EXIT_/SAPAPO/SAPLCIF_TPSRC_001  SE18  /SAPAPO/CIF_TPSRC_IN  interface /SAPAPO/CL_EX_CIF_TPSRC_IN