Stop FU creation from Purchase order based on incoterm?

[Arjun_Mukherjee]

Hello All,

I have a question can we stop creation of FU for the document type which we have activated for TM integration based on incoterm

Suppose if the PO is created with incoterm DDP ,than FU should not be created otherwise it should create FU

I tried to implement the logic of FUBR condition by inserting incoterm field in the FUBR condition /SCMTMS/FUBR but it's still creating FU with default FUBR rule. Which is correct as the FUBR as the condition which if incoterm is fob pick FUBR xxxx .or not.

So suggest me a way to stop FU creation for thr document type with any changes in activation combination i.e sales org/distribution channel/ document type.

Thanks ,

Arjun

[sarah_moes]

If the PO is not relevant for any transportation planning because of the incoterm, you might want to avoid sending it to TM. To do this, you can implement a BADI in ECC to customize when a TM Control Key is assigned to a purchase order. The standard code checks purchase doc type, purchase org, and purchase group against the relevant configuration, but you can expand this check to include incoterm with the BADI. By preventing the TM Control Key from being assigned to the PO, there will not be an XML sent to TM.

BAdI: Purchasing Document Integration with TM (BADI_LO_TM_PUR)

[hernan_suarez]

Hi Sarah,

Thank you very much for your insight.

Do you know if it is possible to use this BADI in the case of TM embedded where the integration is internal?

For Purchase Orders I only have Puchase Organization, Group Organization and Document Type but I need at least one more field from the source document, maybe the incoterm as you said.

Thanks you very much in advance.

Best regards

Hernan

[former_member194808]

Dear Arjun,

You can't do something with condition Type /SCMTMS/DTR_TYPE (or the OTR equivalent), and customize a separate OTR/DTR Type for purchase orders which doesn't have the checkbox "Automatic Freight Unit Building" on?

An other option might be to create a seperate stage profile which will create a FU, but all stages are never relevant for Planning, you might use condition type /SCMTMS/TRQ_STG_PRF to make sure that OTR/DTR's based on a sales order get another stage profile than OTR/DTR's that are based on a purchase order.

Please share which solution you have implemented.

Kind regards,

Benno Mateman