How to Create a Purchasing Info Record in SAP IS-Retail – ME11 and ME12 Explained
Over 70% of procurement tasks in SAP IS-Retail rely on accurate purchasing info records to automate sourcing and pricing workflows. You use transaction codes ME11 and ME12 to manually create and update these records when automatic generation isn’t triggered. Incorrect entries can lead to pricing mismatches and purchase order errors, especially for new vendor-material combinations. This guide is designed for new IS-Retail consultants and buyers who need a clear, step-by-step approach to mastering these transactions within live retail procurement cycles.
Key Takeaways:
- A purchasing info record in SAP IS-Retail links a vendor with a specific material, storing key procurement details such as pricing, delivery times, and order units, forming the foundation for purchase order creation.
- Transaction ME11 is used to manually create these records when automatic generation does not occur, typically required when a new supplier relationship is established outside of initial article master data entry.
- ME12 allows authorized users to verify and adjust pricing and other conditions in an existing info record, ensuring accuracy before procurement cycles begin, which is especially useful during promotional periods or cost adjustments.
Understanding the Purchasing Info Record in SAP IS-Retail
Definition and core purpose
A purchasing info record establishes the connection between a specific article and its supplier, serving as a centralized repository for key procurement details. You maintain data such as pricing, delivery times, and order units within this record, enabling consistent transaction handling. The link between article and supplier is foundational for accurate sourcing in SAP IS-Retail.
Importance in procurement workflows
Procurement efficiency improves when you use purchasing info records to standardize supplier-article agreements. They support automated purchase order creation and ensure pricing accuracy during order entry. Without an active info record, manual entry errors increase and audit trails weaken. Retailers rely on these records to maintain consistency across high-volume transactions.
When processing thousands of store-level orders weekly, a mid-sized SaaS firm in the retail sector reduced order discrepancies by aligning all supplier pricing through ME11-generated info records. These records feed directly into purchase orders, contracts, and scheduling agreements, minimizing deviations. Each record acts as a single source of truth for supplier-specific article terms.
Factors for Automatic Info Record Generation
- Automatic generation occurs when a supplier is entered in the Areas of Validity during article creation
- The system creates the purchasing info record without manual input via ME11
- This process links supplier data directly to the article master at setup
After defining supplier details in the correct validity section, the system initiates record creation as part of master data integration.
Integration with article master data
You establish the foundation for automated info records when creating the article master. Supplier assignments made at this stage feed directly into purchasing structures. The system uses the Areas of Validity entries to determine which vendors supply specific items. After saving the article, the info record appears if all required fields are populated.
Role of Areas of Validity in automation
Supplier entries in the Areas of Validity trigger automatic info record creation during article setup. This field defines where a material is procured and from which vendor. Missing or incorrect entries here prevent system-generated records. After the article is saved with a valid supplier in this section, the system generates the record immediately.
Each entry in the Areas of Validity specifies procurement details such as plant, distribution channel, and supplier account group. When you input a vendor in this section during article creation, the system recognizes it as a signal to generate a purchasing info record. The process eliminates redundant data entry and reduces errors. After the article master is released with complete validity data, the associated info record becomes available for use in purchase orders.
How to Manually Create Records Using Transaction ME11
Transaction code ME11 is specifically used for the manual creation of a purchasing info record when automatic generation is not applicable. You initiate the process by entering ME11 in the command field, allowing direct input of supplier and material details that bypass system-generated entries, ensuring accuracy when predefined conditions are not met.
Step-by-step manual entry process
Begin by entering ME11 in the SAP command bar and pressing Enter to open the initial screen. You then input the material number, supplier account number, and plant code to initiate the record creation, followed by pricing and delivery details in the subsequent screens.
| Field | Description |
| Material Number | Unique identifier for the product being procured |
| Supplier Number | Vendor master record key linked to the purchasing organization |
| Plant | Operational unit where the material is received and managed |
| Purchasing Organization | Entity responsible for procurement activities |
| Net Price | Agreed cost per unit, excluding taxes and freight |
Required data fields for ME11
You must enter the material number, supplier, plant, and purchasing organization to create a valid record. Missing any of these fields prevents the system from saving the info record, enforcing data integrity at the point of entry.
Each field ties directly to master data in SAP, ensuring consistency across procurement processes. The material number references the material master, while the supplier links to the vendor master, preventing mismatched or unauthorized pairings. Pricing and delivery tolerances can also be defined during this step, supporting compliance with purchasing agreements.
How to Confirm and Update Pricing via ME12
Transaction code ME12 is utilized by users to confirm existing data or update specific pricing conditions within the info record. You can adjust price agreements, validate vendor terms, and ensure alignment with current procurement contracts. For detailed guidance, refer to this community discussion: Explaination about Purchasing INFO RECORD..?
Navigating the ME12 interface
After entering ME12 in the command field, input the material number, vendor, and plant to access the info record. The initial screen displays tabs for General Data, Purchasing Organization Data, and Conditions. Correct selection of these tabs ensures access to pricing fields that can be modified based on procurement needs.
Maintaining accurate pricing conditions
Pricing conditions in ME12 include base price, discounts, and surcharges tied to specific validity periods. You must verify these values against current purchase orders to prevent discrepancies during invoice verification. Incorrect entries may lead to overpayment or blocked invoices.
When updating pricing in ME12, always review the validity dates of existing conditions before making changes. A mid-sized SaaS firm discovered a 15% pricing variance after failing to check overlapping validity periods. Each condition type must reflect actual supplier agreements and be saved with proper authorization to maintain audit compliance.
Tips for Managing Purchasing Data Effectively
Consistent data entry practices prevent pricing discrepancies and supply chain delays. Maintain accurate vendor master data, validate material groups regularly, and ensure correct plant assignments are reflected in each record. Assume that outdated info records contribute to procurement errors in a mid-sized SaaS firm. For detailed guidance on setting up and monitoring these records, refer to SAP’s official documentation on Purchasing Info Record.
Best practices for new consultants
Focus on mastering transaction codes ME11 and ME12 before advancing to automated setups. Always verify info record type and validity periods during creation to avoid incorrect pricing application. Assume that incomplete field entries lead to downstream procurement issues in live systems.
Buyer-specific data maintenance tips
Assign buying info records only to authorized personnel to maintain data integrity. Use release strategies to control purchasing thresholds and track vendor performance metrics per buyer group. Assume that unrestricted access increases maverick spending risks.
Buyer-specific records require regular audits to reflect current supplier agreements and pricing contracts. Monitor info record changes through audit logs, restrict price overrides to approved users, and align planned delivery times with seasonal demand cycles. Assume that unapproved price adjustments bypass compliance checks in high-volume retail environments.
Summing up
You use ME11 to manually create purchasing info records, entering vendor, material, and plant details to establish sourcing data. When pricing updates or contract changes occur, ME12 allows you to confirm and adjust conditions directly. A mid-sized SaaS firm managing retail procurement relies on these transactions to maintain consistency across purchase orders. Understanding the manual and automatic creation of info records via ME11 and ME12 ensures accurate procurement data for IS-Retail environments.
FAQ
Q: What exactly is a purchasing info record in SAP IS-Retail and why is it used?
A: A purchasing info record in SAP IS-Retail stores key procurement data for a specific combination of material, vendor, and plant. It contains details such as pricing, delivery times, order units, and tolerance limits, serving as a reference during purchase order creation. Retailers rely on these records to maintain consistency across orders, streamline sourcing decisions, and support automated purchasing processes. For example, when a buyer creates a purchase order for a seasonal apparel item from a long-term supplier, the system pulls the latest negotiated price and delivery terms directly from the info record, reducing manual input and minimizing errors.
Q: When should I use transaction ME11 instead of waiting for automatic info record creation?
A: Transaction ME11 is used to manually create a purchasing info record when no automatic entry has been generated, typically because the vendor was not assigned during article maintenance in the Areas of Validity. A mid-sized SaaS firm managing private-label electronics might find that new suppliers for accessories are not captured at article creation, requiring manual intervention. In such cases, entering ME11 in the command field allows the user to input the material number, vendor ID, and plant to build the record from scratch. This method ensures procurement can proceed without delay, especially during product launches or when onboarding temporary vendors for promotional items.
Q: How does transaction ME12 differ from ME11 and what role does it play in price management?
A: While ME11 creates a new purchasing info record, ME12 is designed to display and modify existing records, making it necessary for maintaining up-to-date pricing and conditions. Buyers use ME12 to confirm price changes communicated by suppliers, such as a 5% increase on imported home goods due to shipping cost fluctuations. By opening the relevant info record in ME12, the user can navigate to the Conditions tab, adjust the price, and save the update with a new validity period. The system logs the change, ensuring auditability and enabling accurate cost calculations in subsequent purchase orders.