PO Creation with external PO number

[Former Member]

Hi All,

We have SRM and some other legacy system. We will receive the PO information from the legacy system with the Legacy PO number. Now we have to create a PO with external number only.

So for PO creation we are using the BAPI BAPI_POEC_CREATE. this is working fine if you dont pass any external PO number.

But If you pass external PO number I am facing some problem. BAPI_POEC_CREATE is giving the informaiton that PO with XXXXXXX number is created, but when we call BAPI_TRANSACTION_COMMIT it is throing some error like.

-

---

Buffer table not up to date

Message no. BBP_PD001

Diagnosis

In LOOP OBJ_RELATIONS_UPDATE (function group SAPLBBP_PDH_OR) an inconsistent status was discovered.

Procedure

Start the transaction again. If the error occurs again, create an OSS message.

To analyze the error, you can set a breakpoint in the function module 'BBP_PD_ABORT' and look at the call-up hierarchy in debugging mode.

-

---

Is this the number range problem? please tell me what is missing.

Thanks & Regards,

Raghu

[yann_bouillut]

Hi,

To be honest, i never tried with PO external number range.

At least, you could store the external PO in a header customer field...

Kind regards,

Yann

[Former Member]

Hi,

Thanks for the reply. PO should be creaated with external PO number only. That is the customer reqirement.

Thanks & Regards,

Raghu,

[yann_bouillut]

Hi,

Did you already create an external number range in SRM SPRO ?

If yes, did you already linked this external number range to transaction type configuration point ?

Kind regards,

Yann

[Former Member]

Even I have this doubt, but the thing is I dont have access to the SRPO.

Thanks & Regards,

Raghu

[yann_bouillut]

Hi,

Once you get confirmation of the points i asked, please update the thread.

Kind regards,

Yann

[Former Member]

Yes external number range is created and assigned to the transaction type

[Former Member]

Raghavender,

I think that maybe the external number is not the problem.

Sometimes the explicit <b>COMMIT</b> causes this error cuz some processes or BADI's are accessing the table at memory level, so if you use this explicit bapi_transaction_commit maybe it will raise that error...

Have your tried to remove that function call?

Please acknowledge if it worked...

Regards,

Gerardo.