Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Dump Error while creating External number PO via bapi_po_create1

Former Member
0 Kudos
1,248

Hi,

     We have a requirement as, while cut over client want to migrate all the PO available in legacy system into SAP. For this, we have created PO document type ZMGR with internal as well as external number range.

     We tried posting PO manually by T-CODE- ME21N.

     As we want to migrate vast no of PO's, We were posting PO using BAPI_PO_CREATE1.

     But while posting BAPI we were getting Exception "NO DATA". If i remove the PO number from bapi it is posting PO (And also generating PO number from internal number range).

     While debugging, we came across one global variable inside bapi as "STATE". this state have value as 0. While debugging, if i go ahed and manually change the value of variable STATE to 1 (i think 1 stands for available, but not sure). PO is posting with external number range also.

     Please ;et us know if we were missing any field to be passed in bapi.

Regards,

Chandan

1 ACCEPTED SOLUTION
Read only

Former Member
0 Kudos
986

Hi,

     I finally used BAPI_PO_CREATE instead of BAPI_PO_CREATE1 and it is working fine. i used this for mass po upload with external PO number from legacy to SAP

6 REPLIES 6
Read only

Former Member
0 Kudos
986

Hi,

Please check your external number range once in SNRO transaction or in NRIV table for purchase order object EINKBELEG

Read only

0 Kudos
986

Hi,

Number range is maintained in NRIV table.

I am using number range 45

Regards,

Chandan

Read only

0 Kudos
986

For 45 external flag is not set in your screenshot. For external it should be set.

Read only

0 Kudos
986

Sorry,

it is 44. by mistake i wrote 45.

     PFB for details.

Read only

Former Member
0 Kudos
987

Hi,

     I finally used BAPI_PO_CREATE instead of BAPI_PO_CREATE1 and it is working fine. i used this for mass po upload with external PO number from legacy to SAP

Read only

RaymondGiuseppi
Active Contributor
0 Kudos
986

What is your version (this bug was corrected in 2005?) and you are loading legacy data, so your system should be recent and up to date, you could (should) consider raising an incident message?

NB: BAPI_PO_CREATE is somewhat obsolete (Check with BAPI transaction and not with SE37, the FM is not obsolete but is no longer a valid BAPI...) but for a one-shot program....

Regards,

Raymond