Purchasing Information Record

• What if we need to separate it for the special processes? What are the categories available?
• Do we really need a material number to create a Purchasing Information Record?
• What is the T-code to create and change PIR?
• Mass update
• Additional information 
• Conversion factors 
• How can purchasing info records be transferred via ALE?
• The 'Minimum Qty' 
• 1900107 - MRP : Planned delivery time is taken from material master rather than info record
• 2892806 - The net prices/effective price are not updated in the info record after run the report RM06INP0
• EINA-MATKL
• 2342644 - Updating tax code in info record according to InfoUpdate flag in PO
• 2657807 - Purchasing info record price history shows PO effective price rather than net price
• 2559559 - Info record not filled in STO
• Order unit
• 430543 - FAQ: Purchasing info record

What is Purchasing Information Record?

• The relationships between vendors and their materials. A vendor might have specific terms and conditions of purchase for a material.

When Purchasing Information Record is used?

• Information from an information record is defaulted (copied) during the purchase order creation process.

Which data can be copied? 

• Current and future prices and conditions
• Conditions Allowed with and without Plant/Only Plant-Related Conditions Allowed
• Delivery data (planned delivery time and tolerances)
• Vendor data (vendor material number, vendor material group, etc.)
• Regular vendor is used by the system during source determination.
• Texts: Info Memo and Purchase Order Text.
• Statistical Data

At which level can we maintain these data?

1. Plant/Purchase organization
2. Purchase organization

What if we need to separate it for the special processes? What are the categories available?

• Standard purchasing information record
• Consignment purchasing information record
• Pipeline purchasing information record
• Subcontracting purchasing information record

Do we really need a material number to create a Purchasing Information Record?

• No, we can use the text for material, but we have to specify a material group and other data.

What is the T-code to create and change PIR?

• ME1*

Mass update

Use MEMASSRQ t-code to update the purch req

Additional information 

In the info record, a net price of 0 is displayed. Nevertheless, a new purchase order receives a price automatically. Where does the price come from?

• The price comes from the "last document" (field EINE-EBELN), menu Environment -> Last Document in the "Purchasing Data 1" screen in ME13 (Display Purchasing Info Record), for example.

Conversion factors 

In the purchasing info record, it is possible to maintain conversion factors that differ from those in the material master and they can be maintained differently per plant. SAP recommends not changing the relationships dynamically. If a relationship needs to be changed, it is also possible to implement a new unit of quantity

How can purchasing info records be transferred via ALE?

• All data apart from the conditions is transferred with IDocs of message type INFREC. The conditions are transferred with IDocs of message type COND_A. See also SAP Notes 392988 and 77252 for specific information on sending COND_A IDocs.

The 'Minimum Qty' 

The 'Minimum Qty' in the info record is used for purchase order rather than purchase requisition. Please use the 'Minimum Lot Size' in the material master(MRP View 1) instead of 'Minimum Qty' in the info record.

The data in the info record that is marked for deletion is still considered valid. If you do not wish that this data is adopted into purchasing documents, you have 3 options. You need to archive the info record.

1900107 - MRP : Planned delivery time is taken from material master rather than info record

System does not check the planned delivery time in info record according to the customizing of plant.

T-code OPPQ -> Maintain -> External Procurement. Set "Scheduling according to purchasing info record or agreement" indicator for relevant plant in customizing.

EINA-MATKL

You can create info records with material and vendor pair: in this case the material group (EINA-MATKL) in the EINA table is empty.

If you display the info record with ME13, the material group is just displayed from the material master (MARA-MATKL). Same happens at info record creation and edit. This logic is due to the possibility of changing the material group in the material master.

You can have info records with material group and vendor pair: in this case the EINA-MATKL field stores the material group (as in this case there is no material master to read from).

You can create info records in transaction ME11 without material number. After entering the relevant data on the start screen, enter the material group on the next screen. This is mainly useful if you create free text purchase requisition and source is needed.

2892806 - The net prices/effective price are not updated in the info record after run the report RM06INP0

When you update the conditions, for example, PB00, in MEK1 the conditions are getting updated but the net prices/effective price of the purchase info record is not getting updated or are updated to zero.

You also run the program RM06INP0 but it did not update the values in the info record.
The material is defined with an UoM different of the one defined for the price condition.

2342644 - Updating tax code in info record according to InfoUpdate flag in PO

The InfoUpdate flag is designated to update time-dependend conditions, mainly pricing. The tax code from the purchase order item

is taken over only for the first time, when there is no inforecord existing. In this case all data will be taken from PO item and will be

transferred to inforecord. But when inforecord exists already, you cannot change the tax code from PO to the info record.

2657807 - Purchasing info record price history shows PO effective price rather than net price

Configure T024E-BPEFF in the following customizing path:

Transaction OLME -> Purchasing Info Record -> Define Price History

If the "effective price in order price history" is set to X for a purchasing organization, PO effective price (EKPO-EFFWR) will be updated in the price history. If you want to update price history with PO net price, untick the "effective price in order price history".

2559559 - Info record not filled in TO

The indicator "Stock transfer vendor" (T161-UMLIF) is not activated for the STO document type in customizing under SPRO>Materials Management>Purchasing>Purchase Order>Define Document Types.

Order unit

The Purchase Order can adopt order unit, order price, the order price unit, and the conversion factor from a Info Record, overwriting information from Material Master Record.

If the Info Record contains outdated information, you need to:

- In trx ME15, mark Purchasing Info Record for deletion

- In trx MM02, update Material Master data

- In trx MM11, create a new Purchasing Info Record

430543 - FAQ: Purchasing info record

1st question: Why do the prices displayed in the info record (net or effective price) not always match the prices arising from the info record conditions or all existing conditions for the vendor-material combination?

Answer: Refer to SAP Note 392988.

2nd question: In the info record, a net price of 0 is displayed. Nevertheless, a new purchase order receives a price automatically. Where does the price come from?

Answer: The price comes from the "last document" (field EINE-EBELN), menu Environment -> Last Document in the "Purchasing Data 1" screen in ME13 (Display Purchasing Info Record), for example.

3rd question: You change conversion factors in the material master (units of measure). Why are the relationships in the purchasing info record not adapted automatically?

Answer: In the purchasing info record, it is possible to maintain conversion factors that differ from those in the material master and they can be maintained differently per plant. SAP recommends not changing the relationships dynamically. If a relationship needs to be changed, it is also possible to implement a new unit of quantity (e.g. for 1 crate = 100 KG -> 1 Kiste_01 = 120 KG).

4th question: How can purchasing info records be transferred via ALE?

Answer: All data apart from the conditions is transferred with IDocs of message type INFREC. The conditions are transferred with IDocs of message type COND_A. See also SAP Notes 392988 and 77252 for specific information on sending COND_A IDocs.

5th question: Why is it not possible to create several condition periods within a transaction call (ME11, ME12)?

Answer: The cause is technical and is based on the design of the SAP condition technique. Unfortunately, this design cannot be retroactively adjusted for reasons of compatibility.

The consequences of this are that in order to create an info record with two condition periods, for example, you must first create an info record with one period (ME11) and then create another condition period in change mode (ME12). (For three periods, you would have to use ME11 once and ME12 twice).

In the same way this also applies for batch input of info records, as transactions ME11 and ME12 are needed for this.

Note that the new function module ME_INFORECORD_MAINTAIN_MULTI supports multiple condition periods at the same time within one transaction call. See SAP Note 2492873.

6th question: Why is data from the last purchase order not always updated in the info record although the Info Update indicator is set in the order item?

Answer: This happens when the info record is blocked for processing at the time of purchase order creation. The purchase order is saved anyway. In transaction ME21/ME22, after creation of the purchase order, the system issues message 06 311 informing you that the info record was blocked. In the SAP single-screen transactions, this is not possible for technical reasons.