cancel
Showing results for 
Search instead for 
Did you mean: 

Need to Store a Reference Number in PO.

Former Member
0 Kudos

The purchase Orders in SAP are created through interface from a legacy system.

To have the cross reference between the two systems, the PO number of the legacy system must be stored in the SAP PO.

What field in ME21N can be used for this requirement?

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Take a Requisitioner field it will be better.

Venkatesh

Answers (4)

Answers (4)

Former Member
0 Kudos

Thanks Everyone

Former Member
0 Kudos

Hi Bala,

you can use the field "our reference" under communication tab at the PO header...

This usually identifies the person responsible for the purchasing document in your company. The reference number/code often consists of the relevant person's initials.

but you can use this for your purpse...

Regards,

Archit

Former Member
0 Kudos

at item level, you may use Requirement Tracking Number. At header level, you may use Your Reference (EKKO-IHREZ)

Former Member
0 Kudos

hi Balakumaran

use requirment number for tracking the PO ..

regards

ravikant

Former Member
0 Kudos

If i use the requirement Tracking number i will have conflicts with the Purchase Requisitions.

i dont want to use the requistioner field either, as both these fields are at the item level, I prefer to have it at the header level.

Would it be wise to have this reference number mapped into the COmmunication TAB at the header level into the fields YOUR REFERENCE or OUR REFERENCE?

It should ideally be at the header level, coz its a PO to PO reference.

Cheers

Former Member
0 Kudos

Yes, you can use any of those fields. But if you may have more than one item in PO, I will suggest to identify also the PO item. Even if you think that you will have the same item number, you may have to delete an item, and create a new one for any reason. In that case, you won't have the exact 1 to 1 relation at item level.

One way will be having the purchase order number at header level using "Your Reference", and using Req tracking number to keep the relationship at item level. If you cannot use none of those fields at item level, you can create a confirmation control schema, with a custom confirmation category, and keep item relationship in the external document field.

This will be very useful in case you work with IDOCs for Confirmations/IR/GR/Inbound deliveries. Believe me, I've been there.

Hope this helps.