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

Problem migrating PO using BAPI PO_CREATE1.

Former Member
0 Likes
3,415

Hi ,

I am trying since two days to perform this task. I am trying to create PO using an LSMW , generating an idoc , which is then calling

BAPI PO_CREATE1.

It is always generating the following errors and warnings , ( Error 51 )

Purchase order still contains faulty items

Purchase order date is in the past

Enter a quantity

Error transferring ExtensionIn data for enhancement CI_EKPODB

No instance of object type PurchaseOrder has been created. External refe

Please enter a delivery date

On debugging , I found that the values of Quantity enters the BAPI , but then it resets it to 0.00 again in the output it gives.

I have double triple checked the structures and their mappings , but the problem still persists.

I am just a fresher and new to SAP , So I may miss a lot of important details in the question , If you could please support me and ask me the relevant questions in this as this is top priority.

Regards ,

Thankyou.

2 REPLIES 2
Read only

Former Member
0 Likes
2,967

Hello,

I did this before, using BAPI_PO_CREATE. I guess it's same for BAPI_PO_CREATE1.

In LSMW transaction:

1. Maintain Object Attributes

2. Maintain Source Structures

3. Maintain Source Fields

For Header:

For Item:

You should have this by now:

4. Maintain Structure Relations

Add relationship as required.

5. Maintain Field Mapping and Conversion Rules

Pay attention to the date format here (maybe u'll need to try a bit to get it right, because it depends on the format of date you used)

6. Specify Files

Here is a format of file used:

(Used NB - standard PO, instead of ZFGM)

7. Assign Files

8. Read Data

9. Display Read Data (make sure every data is correct here)

10. Convert Data

11. Display Converted Data (make sure every data is correct here)

12. Start IDoc Generation

13. Start IDoc Processing

14. Error

Go back to Field Mapping and Conversion Rules

We can see that Vendor has been missed when doing automatic mapping. So we'll add it manually.

Click on Vendor > Click Source Field (on top)

Choose LIFNR

Save

Do these steps again:

Specify Files

Assign Files

Read Data

Display Read Data

Convert Data

Display Converted Data

Start IDoc Generation

Start IDoc Processing

Now you'll see it's no longer an error.

The purchase order has been created:

I hope it helps.

Kind Regards

Read only

0 Likes
2,967

Screenshot of the error at No. 14