topic Re: Error in BAPI_PO_CREATE1 imputing WBS Element in Application Development and Automation Discussions

Error in BAPI_PO_CREATE1 imputing WBS Element

rafael_cermeno — Fri, 19 Sep 2014 22:12:24 GMT

hi,

I'm trying to create a service purchase order (ME21N) tied to a purchase requisition using BAPI_PO_CREATE1. The purchase requisition is imputed to Project (WBS Element). I have not been able to create, the BAPI generates an error KI235 "Account & requires an assignment to a CO object" The account 123456 is not set in OKB9 table. However, when I create a service purchase order using the same bapi with this account but charged to cost center, works perfectly. However, I need to create it imputing WBS element.

I filled the following relevant fields to the BAPI:

POITEM-PO_ITEM : 00010

POITEM-SHORT_TEXT : Texto

POITEM-PLANT : 'CENTRO'

POITEM-MATL_GROUP : 'GRUP'

POITEM-QUANTITY : 1

POITEM-PO_UNIT : 'ACT'

POITEM-NET_PRICE : 10

POITEM-ITEM_CAT : '9'

POITEM-ACCTASSCAT : 'P'

POITEM-PREQ_NO : 2000001500

POITEM-PREQ_ITEM : 00010

POITEM-PREQ_NAME : 0000012000

POITEM-PCKG_NO : 0000000100

POACCOUNT-PO_ITEM : 00010

POACCOUNT-SERIAL_NO : '01'

POACCOUNT-GL_ACCOUNT : '123456'

POACCOUNT-WBS_ELEMENT: 'PEP_ELEMET'

POACCOUNT-CO_AREA : 'SCOS'

POACCOUNT-PROFIT_CTR : 'CTRBENEF'

POACCOUNT-FUND : 'FUND'

POACCOUNT-CMMT_ITEM : '0000123456'

Best Regards,

Re: Error in BAPI_PO_CREATE1 imputing WBS Element

rafael_cermeno — Sat, 20 Sep 2014 00:21:27 GMT

After a long investigating process, implementing the following note solved the problem: 1977169.

Best regards.

Re: Error in BAPI_PO_CREATE1 imputing WBS Element

Former Member — Mon, 15 Dec 2014 13:46:02 GMT

Hello Rafael,

we are also facing same issue. we implemented the above note ,but it is not working.Could you please suggest the solution which will solve this.the above describes the CHNAGE Bapi.we are facing the issue when PO Creating.

Re: Error in BAPI_PO_CREATE1 imputing WBS Element

former_member820816 — Thu, 25 Aug 2022 07:51:02 GMT

Hello,

we had the same problem recently.

The task was to migrate project account service orders via Idoc. Then we always got the error message KI235 and noticed that the given PSP element was not read correctly from the IDoc.

The solution is to take the POSID field from the PRPS table! Not POSNR.

Best regards

Caroline