PO doesn't get created, backend returns PO number with "S" message

[Former Member]

Hi experts,

I need your kind assisstance with the following problem: when SC is sent to the backend, the backend system returns the PO number with a message that the PO has been created. When we check at the backend the PO is not created.... It happens only when customer fields are transfered in the table EXTENSIONIN.

SRM Server 500.

Thanks a lot for your help.

Tomas Kraus

[Former Member]

Hi

<b>Lot of places, you need to check : -> </b>

!) Which R/3 version are you using ?

2) Please paste the detailed code you are using in the BADIs before calling the BAPI_PO_CREATE1 / BAPI_PO_CREATE in R/3 system.

3) Have you created Z function -BAPIs here ?

4) In SRM, Any errors noticed in RZ20 or ST22 transactions ? Please elaborate with details.

Do let me know.

Regards

- Atul

[Former Member]

Hi Atul,

we found out that the error occurs when data are tranfered to the target structure BAPI_TE_PO_ITEMS to the backend, the problem is probably caused by the structure definition as it contains also non character fields (see note 509898). Do you have any ideas how to solve the problem?

Tomas

[yann_bouillut]

Hi,

What is your backend release and patch level ?

Kind regards,

Yann

[Former Member]

Hi

<u>What error are you getting in this case ?</u>

<b>Question:</b>

<u>You are using BAPI_PO_CREATE1 and BAPI_PO_CHANGE to supply user-defined fields for tables EKKO, EKPO and EKKN. During the update, a termination occurs with DBIF_RSQL_INVALID_REQUEST.</u>

Answer: 
Check in the CI structures of the corresponding database table as to whether there are type P (packed) fields. Refer to the online documentation for user-defined fields and the ExtensionIn parameter:
In BAPI table extensions, only CHAR data type fields and similar data types can be used by the customer. This restriction arises as a result of the BAPIPAREX reference structure of the extension parameters. In addition, the customer must not use standard table fields in the APPEND of the BAPI table extension because a 'move-corresponding' would also overwrite the SAP field.
See Note 509898 for a solution approach.

<b>Please go through the SAP OSS note -</b>Note 582221 - FAQ: BAPIs for purchase orders

<b>for more details.</b>

<u>Also go through the related SAP OSS Notes -></u>

Note 390742 - Customer enhancements not transferred

Note 336589 - BAPI_PO_CREATE: Customer enhancements

Note 867018 - Customer fields transfer to the back end

Note 445169 - BAPI_PO_GET_DETAIL: Integrated customer enhancements

Note 395311 - BAPI_PO_CREATE: Customer enhancements not copied

Note 631758 BAPI_PO_GETDETAIL: Incorrect ExtensionOut struc. name

Hope this will definitely help.Do let me know.

Regards

- Atul

[Former Member]

Thanks a lot. We'll follow the instructions as described in the note 509898.

Points rewarded.