C_TS452_2022 Configuration of Purchasing

Configuration of Purchasing Detailed Explanation

The Configuration of Purchasing module in SAP S/4HANA focuses on setting up essential parameters that tailor the purchasing system to an organization’s specific needs. This configuration ensures that procurement processes run smoothly, documents are generated accurately, and financial records are updated automatically. This module’s settings cover everything from document management to automated financial assignments, and they help SAP users streamline procurement activities to meet organizational standards.

Overview: Why Purchasing Configuration Matters

Configuring the purchasing module allows businesses to adapt SAP’s procurement capabilities to their specific needs. The SAP system allows you to define document types for different purchasing processes, manage account assignments that automatically allocate procurement costs to the right financial accounts, set up output processing to control how documents are shared, and design release procedures to implement approval workflows for purchasing documents. These customizations improve efficiency, reduce errors, and align the purchasing process with corporate policies.

1. Document Types

• Definition: Document types categorize the various purchasing documents generated within SAP, such as purchase orders (POs), contracts, and delivery notes. Each document type can be configured to reflect specific business needs and conditions.
• Key Components:
  • Purchase Orders (POs): POs are fundamental documents in procurement, specifying order details like quantity, delivery schedule, and price. SAP allows the configuration of different PO types based on scenarios such as standard procurement, subcontracting, or consignment.
  • Contracts: Contracts are long-term agreements with suppliers, often specifying terms over a set period or for a set quantity.
  • Delivery Notes: These documents accompany received goods, providing details for matching the receipt with the corresponding PO.
• Purpose: Configuring document types allows the SAP system to standardize documentation, ensuring that each document complies with company policies and reflects the correct terms. It also enables businesses to apply specific rules and workflows to different purchasing scenarios.

2. Account Assignment & Output Processing

• Account Assignment: This feature allows SAP users to define how procurement costs are automatically allocated to specific accounts or cost centers. Different types of purchases may be linked to different accounts, depending on whether the items are for resale, internal use, or specific projects.
  • Example: Raw material purchases might be assigned to an inventory account, while office supplies are assigned to an expense account. SAP uses account assignment categories to automate this linkage, reducing manual data entry and ensuring financial accuracy.
• Output Processing: Output processing manages how purchasing documents are shared with suppliers or other departments within the company. For example, it controls whether a purchase order is printed, emailed, or sent via EDI (Electronic Data Interchange). SAP allows users to set up output types and formats based on the document type and recipient requirements.
  • Example: A company may configure SAP to automatically send POs to suppliers via email and retain a copy in the system, ensuring seamless communication with vendors and quick access to documentation when needed.
• Purpose: Together, account assignment and output processing automate financial tracking and document distribution, making procurement workflows more efficient and compliant with reporting requirements.

3. Release Procedures

• Definition: Release procedures in SAP allow companies to establish approval workflows for purchasing documents, ensuring that purchases are reviewed and authorized based on specific criteria, such as value or department.
• How It Works: SAP administrators define release strategies that specify conditions for document approval. For example, a PO exceeding a certain amount might require approval from a manager. If the PO meets the release criteria, SAP routes it through the configured workflow until final approval is granted.
• Purpose: Release procedures ensure that high-value or critical purchases undergo necessary checks before being executed, helping organizations control spending and maintain compliance.

Exam Objectives

For the SAP C_TS452_2022 exam, candidates should be able to:

• Configure document types, account assignment categories, and output processing to align with organizational purchasing needs.
• Set up release procedures to implement approval workflows for various purchasing documents, ensuring that all purchasing activities follow company policies.

Configuration of Purchasing (Additional Content)

The Configuration of Purchasing module in SAP S/4HANA allows companies to customize purchasing documents, automate account determination, set up approval workflows, configure pricing procedures, and manage message control. Proper configuration ensures compliance, efficiency, and financial accuracy in procurement processes.

1. Customization of Document Types

SAP S/4HANA allows organizations to customize purchasing document types through SPRO (SAP Configuration Path) to define rules and behaviors for different procurement scenarios.

1.1 Key Configuration Aspects

Configuration Parameter	Description
Number Range	Defines a unique numbering pattern for different purchasing document types (e.g., PO, PR, contracts).
Field Selection	Controls which fields are mandatory, optional, hidden, or display-only in purchasing documents.
Allowed Item Categories	Specifies which procurement categories (e.g., standard, subcontracting, consignment) can be used with a document type.

1.2 Example Use Case

• Scenario: A company wants different numbering series for domestic and international purchase orders.
• Solution:
  • Domestic POs: Number range 4500000000 – 4599999999
  • International POs: Number range 4600000000 – 4699999999

1.3 SAP Configuration Path

• SPRO → Materials Management → Purchasing → Purchase Order → Define Document Types
• Transaction Code: OMEC

2. Automatic Account Determination

Automatic account determination ensures that financial postings for purchasing transactions are assigned to the correct General Ledger (G/L) accounts.

2.1 Key Configuration Components

Parameter	Purpose
Valuation Class	Determines which G/L account is used for material valuation.
Transaction Key	Controls how accounting entries are generated for purchasing transactions.
Account Modifier	Provides additional differentiation for account determination.

2.2 Common Transaction Keys in OBYC

Transaction Key	Description
BSX	Stock Posting (Inventory Account).
WRX	Goods Receipt/Invoice Receipt (GR/IR Clearing Account).
GBB	Offsetting entry for inventory changes (e.g., non-stock purchases).
PRD	Price difference between standard and actual cost.

2.3 Example Use Case

• Scenario: A company wants to separate inventory postings for raw materials (ROH) and finished goods (FERT).
• Solution:
  • ROH (Raw Materials) → G/L Account 300000
  • FERT (Finished Goods) → G/L Account 400000

2.4 SAP Configuration Path

• SPRO → Materials Management → Valuation and Account Assignment → Account Determination → Configure Automatic Postings
• Transaction Code: OBYC

3. Advanced Release Strategy Configuration

A Release Strategy defines approval workflows for procurement documents such as Purchase Requisitions (PRs) and Purchase Orders (POs).

3.1 Key Components

Component	Purpose
Release Levels	Defines approval levels based on criteria such as value, material type, and plant.
Release Code	Assigns approval rights to specific users (e.g., managers, finance team).
Release Status	Indicates whether a document is blocked, partially released, or fully approved.

3.2 Release Status

Status	Description
Blocked	Document requires approval before processing.
Partially Released	Some approval levels are completed, but additional approval is required.
Released	Document is fully approved and ready for execution.

3.3 Example Use Case

• Scenario: A company wants different approval limits for POs:
  • Procurement Manager can approve orders up to $10,000.
  • Finance Director must approve orders above $50,000.

3.4 SAP Configuration Path

• SPRO → Materials Management → Purchasing → Purchase Order → Release Procedure
• Transaction Codes: OMGS (Release Strategy), ME28 (Approve PO)

4. Condition Records and Pricing Procedure

SAP's Pricing Procedure determines how purchase order prices are calculated, ensuring correct pricing structures for materials, discounts, and additional costs.

4.1 Key Components of Pricing Procedure

Component	Description
Condition Types	Defines how different price components (base price, discounts, freight, taxes) are handled.
Calculation Sequence	Determines the order in which price conditions are applied.
Condition Records	Stores supplier-specific pricing details for different materials.

4.2 Common Condition Types in Purchasing

Condition Type	Description
PB00	Gross price (Supplier base price).
RA01	Discount applied by supplier.
FRA1	Freight cost.
MWST	Tax amount.

4.3 Example Use Case

• Scenario: A company orders 100 units of Material A:
  • Base price: $50 per unit (PB00).
  • Supplier discount: 10% (RA01).
  • Freight cost: $500 (FRA1).
• Final price calculation in PO:
  • (100 × $50) – 10% + $500 = $4,500.

4.4 SAP Configuration Path

• SPRO → Materials Management → Purchasing → Conditions → Define Pricing Procedure
• Transaction Codes: MEK1 (Maintain Condition Records), M/08 (Define Pricing Procedure)

5. Message Control (Output Determination)

SAP allows businesses to configure automatic message control for procurement documents to ensure efficient communication with suppliers.

5.1 Definition

• Message control determines how procurement documents (POs, contracts, RFQs) are shared.
• Supported output formats:
  • Print (Paper copy).
  • Email (Electronic notification to supplier).
  • EDI (Electronic Data Interchange for automated processing).

5.2 Key Configuration Aspects

Component	Purpose
Output Types	Defines message format (e.g., PO confirmation, invoice reminder).
Medium	Specifies communication method (print, email, EDI).
Time	Determines when messages are sent (immediate or scheduled).

5.3 Example Use Case

• Scenario: When a PO is created, SAP automatically sends an email to the supplier with the order details.
• Solution:
  • Configure Output Type: NEU (Purchase Order Output).
  • Set Medium: 5 (External Email).

5.4 SAP Configuration Path

• SPRO → Materials Management → Purchasing → Messages → Define Message Types
• Transaction Codes: NACE (Maintain Output Types), ME9F (View PO Messages)

Conclusion

Proper configuration of purchasing in SAP S/4HANA enhances procurement efficiency by:

1. Customizing Purchasing Document Types – Controls number ranges, field selections, and allowed item categories.
2. Automating Account Determination – Ensures correct G/L postings for purchasing transactions.
3. Setting up Release Strategies – Defines approval workflows based on PO value, material type, or location.
4. Configuring Pricing Procedures – Ensures accurate price calculations, including discounts and freight costs.
5. Managing Message Control – Automates PO communication via email, print, or EDI.