Sender interfaces triggered during PO creation

[Bimal_S]

Whenever we create a Purchase Order in ECC, following interfaces are triggered and getting failed.

• PurchaseOrderCreatedInformation_Out

• PurchaseOrderChangedInformation_Out

• PurchaseOrderERPReplenishmentOrderCollaborationNotification_Ou
• PurchaseOrderERPRequest_Out_V1

Even though the ECC TM integration is in place, we want to be sure about these 4 interfaces.

If this is not relevant for ECC TM integration, then how can we stop this from getting triggered? Please help

[former_member910257 · Accepted solution]

The following sap notes helped me to solve this problem:

SAP Notes: 1999701

                   1317798

                   1642555

STEP-BY-STEP

- Transaction SE19

- Click the button Create Impl .

- Fills with the name of the implementation , description and creates a new Composite Enhancement Implementation with same name .

- Saves the corresponding Packege .

- Save in Request .

- Fills the next screen BAdI Implementation , Implementation Class ( automatically created ) and select the PUR_SE_PO_INTERFACE_OUT_SELECT BAdI Definition field.

- Click on Implementing Class and click  on method IF_PUR_SE_PO_IF_OUT_SELECT~IF_PUR_SE_PO_IF_OUT_SELECT

- Code that must be entered in the Method :

FIELD- SYMBOLS TYPE <lv_service_name> seoclname .

LOOP AT ct_service_name assigning <lv_service_name> .

    IF <lv_service_name> EQ ' CL_SE_PUR_POERPCONFIRMATION '

      OR <lv_service_name> EQ ' CL_SE_PUR_POCTREDINFO '

      OR <lv_service_name> EQ ' CL_SE_PUR_POCHGEDINFO '

      OR <lv_service_name> EQ ' CL_SE_PUR_POERPROCOLLABNOTIF '

      OR <lv_service_name> EQ ' CL_SE_PUR_POERPREQ_OUT '

      OR <lv_service_name> EQ ' CL_SE_PUR_POCRTEDINFO ' .

        DELETE ct_service_name .

    ENDIF .

  ENDLOOP .

- Transaction SE18

- Enhancemente Spot: PUR_SPOT_SE_PURCHASE_ORDER

- Select BAdI Definition PUR_SE_PO_INTERFACE_OUT_SELECT - > Implementation.

- After the deployment is activated with the code will appear in the right list .

- Active

- After this procedure should not the error messages of Purchase Order in the IP appears .

PurchaseOrderCreatedInformation_Out

PurchaseOrderChangedInformation_Out

PurchaseOrderERPReplenishmentOrderCollaborationNotification_Out

PurchaseOrderERPRequest_Out_V1

PurchaseOrderERPReplenishmentOrderCollaborationNotification_Out

PurchaseOrderERPReplenishmentOrderCollaborationNotification_Out

I hope I have helped.

regard

[Bimal_S · Accepted solution]

Thanks for the reply. I will get back on this.

This is not a priority issue considering other issues in peoject.

Once implemented, I can get back and update the results.

[Bimal_S · Accepted solution]

We implemented the BADI and it works fine.

[Former Member]

Hello Bimal,

Check table V_T175SOA in ERP side, entries for CL_SE_PUR_POERPREQ_OUT.

Regards, Marcelo Lauria

[Bimal_S]

Hi,

Yes this table has CL_SE_PUR_POERPREQ_OUT entries.

[Former Member]

So....cut it off!

Rgs, Marcelo Lauria

[Bimal_S]

PurchaseOrderCreatedInformation_Out

PurchaseOrderChangedInformation_Out

PurchaseOrderERPReplenishmentOrderCollaborationNotification_Out

Still the above 3 interfaces are getting triggered.

Do you know whether these interfaces are required for ECC TM integration?

Also, what is the use of these 4 interfaces?

[Former Member]

Hello Bimal,

Keep only the entries you need for your TM integration.

The other services are part of scenarios, like SRM, and so.

Let me know the results, we faced the same issue here some time ago...

Rgs, Marcelo Lauria

[Bimal_S]

We are in the process of removing these interfaces. Can update, once this is completed.

[Former Member]

Please close this thread if it is answered.

tks

Eduardo Chagas

[Bimal_S]

I would like to close once everything is implemented and tested.

Till then only comment is that this is a possible solution. There also another solution. KBA aticle/Note: 1999701.

Can update about the solution that we implemented and results once everything is over.