TLB with ECC Created STR instead of APO STR or Deployment order- Issue

[former_member528852]

Hello All,

This question might sound you odd, but this is what is needed.

Requirement - TLB in APO with ECC created STR's.

Issue - After successful conversion of STR to TLB orders, the STR in ECC are not deleted Causing double demand (Original STR and APO published STO)

Detail - We have STR's created in ECC by Third Party Planing tool and same are CIFed to APO for TLB planning. We able to use the STR in TLB planning view and complete the TLB planning without issue. However when TLB order is published back to ECC the original STR is not deleted (firmed or unfirmed) causing double demand at source which is wrong.

Analysis - Standard SAP does not support this, Hence thought of using customization where in when TLB order is created it will pick the STR number and link to TLB order created in APO. When this order with STR is send to ECC user Exit will be called to delete the STR reference.

Issue with development - Once STR's are used for TLB conversion STR number is deleted/converted to TLB order and we loose reference of STR number, In case we want to customize we cant get the reference for STR hence no deletion in ECC.

Question - Does anybody have similar planning situation before ? If yes how do you managed ? Is it possible to link additional field with CIF FM to perform deletion in ECC ? or any other suggestions for making this scenario successful

Please do let me know in case additional details are needed.

Thank you,

ARC

[former_member528852 · Accepted solution]

ECC STR's are made available in TLB view with std SAP report where in you need to define the TLB Data view where SNP STR's will be available in Deployment section, and same can be used for TLB purpose. Normal IM with STR and PR CIF activation will do the trick of deletion of consumed STR in ECC.