interface failed when calling the order confirmation BAPI_ALM_CONF_CREATE without error message?

[sallyxu-cn]

Hi PM Guru,

When calling the BAPI_ALM_CONF_CREATE and BAPI_TRANSACTION_COMMIT for order confirmation, even though the response says the order confirmation is saved, it is not reflected in SAP. Order has still not CNF status.

Here is the interface message.

Pls kindly share your experience,

Sally

[sallyxu-cn]

Hi PM Guru,

When calling the BAPI_ALM_CONF_CREATE and BAPI_TRANSACTION_COMMIT for order confirmation, even though the response says the order confirmation is saved, it is not reflected in SAP. Order has still not CNF status.

Here is the interface message.

Pls kindly share your experience,

Sally

[SimoneMilesi]

Are you calling them in the same LUW? it's the testing sequence of SE37?

[sallyxu-cn]

Hi Simone Milesi.

1. Test sequence is CNF and Commit. the same I used to test in SE37.

2. They use JCO in JAVO to call BAPI in middleware.

Please kindly help,

Sally

[peter_atkin]

Useful info:

https://answers.sap.com/questions/208483/bapialmconfcreate-with-zero-actual-work.html

https://answers.sap.com/questions/12361509/bapialmconfcreate-not-working.html

https://answers.sap.com/questions/11858902/bapialmconfcreate-issue.html

[sallyxu-cn]

Hi Pete,

Does it mean applying No.3 approach is a must in order to get the confirmation saved in DB?

So we need to add customized FM?

The standard BAPI does not work without it?

Pls kindly confirm,

Sally

[sallyxu-cn]

Hi Pete and simone.milesi,

Below is what the response is from the JCO.

Does it mean we have to apply SET UPDATE TASK LOCAL by ABABPer in SAP then call the BAPI and commit work?

Pls advise.

Sally

[Sandra_Rossi]

Better post the text rather than a very large image with lot of blank:

|-|--------------------|---|--------------------------------------------------
|O|12345678901234567890|123|45678901234567890123456789012345678901234567890123
|-|--------------------|---|--------------------------------------------------
|I|RU                  |100|Confirmation of order 4111546 saved
|-|--------------------|---|--------------------------------------------------

0007296579
Confirmation of order 4111546 saved

[sallyxu-cn]

This issue is solved on the supplier side.

They should not have added tcode when calling the BAPI even though it was not enabled. It just ruined the interface.

I was trying to check if it was caused by SAP side.

Thank you so much for your input and sharing,

Sally