C_S4CPR_2408 Implementation and Configuration for Sourcing and Procurement

Implementation and Configuration for Sourcing and Procurement Detailed Explanation

Core Overview

SAP S/4HANA Cloud Public Edition provides a simplified and standardized solution for managing procurement and sourcing processes. As a beginner, your focus will be on understanding how each component of procurement works, how to configure it step by step, and how the procurement process interacts with other modules (like finance and inventory).

1.1 Procurement Processes

Procurement processes cover the key steps in acquiring goods and services from external vendors.

1.1.1 Purchase Requisition (PR)

A Purchase Requisition (PR) is an internal document created to request goods or services. It is the first step in the procurement process. PRs can be created manually by users or automatically by the system.

1. Manual Creation of PR:

   • Open the SAP Fiori App: "Create Purchase Requisition."
   • Enter required details such as:
     • Material/Service: What you are procuring (e.g., office supplies, raw materials).
     • Quantity: Amount needed.
     • Delivery Date: When you need it delivered.
     • Plant: The location where goods will be delivered.
   • Save the PR. It will now appear in the system as "Open" for further processing.

2. Automatic Creation of PR:

   • From MRP (Material Requirements Planning):
     • The system automatically generates PRs based on stock shortages or demand from production orders.
     • This ensures materials are always available without manual effort.
   • From Maintenance Orders:
     • Maintenance activities can trigger PRs for spare parts or services needed to repair equipment.

3. Approval Workflows for PRs:

   • Approval ensures that only valid requests move forward.
   • Workflow steps include:
     • PR is submitted → System assigns to an approver → Approver reviews and approves/rejects.
   • SAP Fiori App: Approvers use the "My Inbox" app to view pending PRs and approve them with a single click.

1.1.2 Purchase Order (PO)

A Purchase Order (PO) is a formal document sent to a vendor to confirm the purchase of goods or services. The PO is legally binding.

1. Steps in the Purchase Order Lifecycle:

   • Creation:

     • Convert an approved PR into a PO using the "Create Purchase Order" app.
     • Alternatively, create a PO manually from scratch.

   • Approval:

     • Multi-level approval workflows can be set up to ensure large POs are reviewed by senior management.

   • Confirmation:

     • Vendors send a confirmation of the order (acknowledgment).

   • Goods Receipt (GR):

     • When goods are delivered, the "Post Goods Receipt" app is used to record delivery.
     • The stock quantity is updated automatically in the system.

   • Invoice Verification:

     • Vendors submit invoices. The system matches the invoice with the PO and Goods Receipt (a process called 3-way matching).

2. Integration of POs with Supplier Systems:

   • Integration can be done using EDI (Electronic Data Interchange) or APIs.
   • Benefits: Faster communication, reduced errors, and automated updates.

3. PO Release Strategies:

   • Multi-level approval processes can be configured to manage approvals based on:
     • PO value (e.g., higher-value POs need senior approval).
     • Material types (e.g., critical materials).
   • SAP Fiori apps make approval workflows simple and accessible.

1.1.3 Supplier Management

Managing suppliers effectively is crucial for ensuring the quality and efficiency of procurement processes.

1. Supplier Master Data:

   • The Supplier Master Record stores all key information about vendors, such as:

     • Vendor Code: A unique identifier for each supplier.
     • Account Group: Groups suppliers by type (e.g., domestic, international).
     • Purchasing Organization Assignment: Links the vendor to relevant purchasing teams.

   • Integration with Business Partner (BP):

     • SAP S/4HANA Cloud uses the Business Partner concept to unify customer, vendor, and employee data into a single structure.

2. Supplier Evaluation:

   • Evaluates suppliers based on:

     • Delivery Reliability: Timely delivery of goods.
     • Price Competitiveness: Reasonable and consistent pricing.
     • Quality: Meeting quality standards consistently.

   • SAP automates evaluations using performance data, generating supplier scores to help purchasing teams make decisions.

1.1.4 Sourcing and Contract Management

1. Outline Agreements:

   • Long-term agreements with suppliers, such as:
     • Value-Based Contracts: Total value of goods or services.
     • Quantity-Based Contracts: Total quantity of materials procured over time.

2. Source Determination:

   • Info Records: Maintain supplier-specific data for materials (e.g., price, lead time).
   • Quota Arrangements: Split procurement volumes among multiple suppliers.

3. Request for Quotation (RFQ):

   • RFQ is sent to multiple suppliers to obtain pricing and terms.
   • Steps:
     • Create an RFQ → Send to suppliers → Receive and compare quotations → Award the contract.
   • SAP allows comparison of supplier responses to select the most competitive offer.

1.2 Configuration Tasks for Sourcing and Procurement

These configurations are necessary to enable procurement processes such as purchase requisitions (PR), purchase orders (PO), and supplier management.

1.2.1 Organizational Setup

To start with any configuration, you must first define the procurement-related organizational structure in SAP S/4HANA Cloud.

1. Key Organizational Elements:

1. Company Code:

   • A legal accounting entity where all financial transactions are recorded.
   • Every purchase is recorded against a company code.

2. Purchasing Organization:

   • The unit responsible for procurement activities.
   • Types of purchasing organizations:
     • Plant-Specific: Linked to a single plant.
     • Cross-Plant: Serves multiple plants within a company code.
     • Company-Specific: Serves all plants in a company code.

3. Purchasing Group:

   • A team or individual responsible for procurement tasks (e.g., buyers).
   • Assigned during PR or PO creation.

4. Plant and Storage Location:

   • Plant: The location where goods are received or consumed.
   • Storage Location: Subdivision within a plant to store materials.

2. Configuration Steps for Organizational Setup

1. Access Configuration Environment:

   • Open the SAP Central Business Configuration (CBC) tool.
   • This is where you configure the structure for procurement.

2. Define Company Code:

   • Go to Manage Your Solution in CBC.
   • Define the company code with:
     • Name, address, and currency.
     • Fiscal year variant (e.g., calendar year).

3. Set Up Purchasing Organization:

   • Create and assign a purchasing organization to:
     • A company code.
     • One or more plants.

4. Define Plant and Storage Locations:

   • Plants are tied to company codes.
   • Storage locations are created under each plant to enable stock management.

5. Assign Purchasing Group:

   • Define purchasing groups in CBC.
   • Examples: "Group A – Raw Materials," "Group B – Office Supplies."

Key Tip: All organizational elements are interconnected, so ensure correct assignments to avoid errors during procurement transactions.

1.2.2 Material Master Configuration

The Material Master contains all the data required to manage materials (products) in procurement. Each material has a master record that contains information relevant to purchasing, inventory, and accounting.

1. Key Procurement-Relevant Material Views:

1. Basic Data: General material attributes (material description, unit of measure).

2. Purchasing View:

   • Procurement type: Stock procurement or consumption-based procurement.
   • Purchasing group.
   • Source of supply data.

3. MRP View:

   • Defines how materials are planned for replenishment (e.g., MRP type, lot size).

4. Accounting View:

   • Valuation class (links materials to GL accounts).
   • Price control: Moving average price or standard price.

2. Configuration Steps for Material Master:

1. Material Types:

   • Define procurement-relevant material types, such as:
     • ROH (Raw Materials): For production.
     • HAWA (Trading Goods): For resale.
     • SERV (Services): Non-physical services.

2. Create Material Master Data:

   • Use the Create Material app in SAP Fiori.
   • Enter details:
     • Material Number: System-generated or manually assigned.
     • Material Type: Select from the defined types (e.g., ROH).
     • Views: Fill out relevant views like purchasing, MRP, and accounting.

3. Valuation Class Assignment:

   • Link materials to GL accounts for automatic account determination during procurement.

4. Maintaining Purchasing-Specific Data:

   • Define default purchasing group, purchasing organization, and tax indicators.

1.2.3 Source Determination

Source determination ensures that procurement processes automatically select the most appropriate supplier when creating purchase requisitions or purchase orders.

1. Key Components for Source Determination:

1. Source List:

   • Controls which suppliers can provide specific materials.
   • Enables automatic source assignment in POs.

2. Info Records:

   • Maintains supplier-specific information for a material, including:
     • Price and discounts.
     • Lead time (delivery period).
     • Validity dates for pricing.

3. Quota Arrangements:

   • Allows procurement quantities to be split among multiple suppliers.
   • Example: 60% from Supplier A, 40% from Supplier B.

2. Configuration Steps for Source Determination:

1. Create Info Records:

   • Use the Manage Info Records app to maintain data.
   • Key fields: Material, Supplier, Price, Validity Period.

2. Set Up Source List:

   • Define permitted suppliers for materials using the Manage Source List app.
   • Mark entries as fixed sources to prioritize suppliers.

3. Configure Quota Arrangements:

   • Define quotas for splitting procurement volume.
   • Example:
     • Supplier A: 70%
     • Supplier B: 30%

4. Automatic Source Determination:

   • Ensure source lists and info records are in place.
   • During PR/PO creation, the system will automatically determine the supplier.

1.2.4 Release Strategies and Approval Workflows

Approval workflows control the release (approval) of purchase requisitions (PR) and purchase orders (PO). Multi-level workflows ensure that high-value or critical documents are reviewed and approved before proceeding.

1. Key Elements of Release Strategies:

1. Release Codes:

   • Represent individual approval steps (e.g., Manager, Senior Manager).

2. Release Indicators:

   • Define the status of the PR/PO:
     • Blocked → Pending approval.
     • Released → Approved and ready for processing.

3. Release Conditions:

   • Specify when approvals are needed (e.g., based on PO value).

2. Configuration Steps for Approval Workflows:

1. Define Release Codes:

   • Set up approval steps for different roles (e.g., Buyer, Manager, Director).

2. Set Up Release Conditions:

   • Example conditions:
     • PR value > $10,000 requires approval by the Finance Manager.

3. Activate Workflows in SAP Fiori:

   • Use the Manage Workflows for Purchase Requisitions/Purchase Orders apps.

4. Testing Workflows:

   • Test approval steps using sample PRs and POs to ensure correctness.

1.2.5 Pricing and Condition Types

In SAP S/4HANA Cloud, Pricing determines how the final purchase price is calculated for a material or service. Pricing relies on Condition Types and Pricing Procedures to define the logic behind prices, discounts, taxes, and other cost components.

1. Understanding Key Pricing Concepts

1. Condition Types:

   • Condition types represent individual price components such as base price, discounts, surcharges, and taxes.
   • Example Condition Types:
     • PB00 (Gross Price): The base price of a material.
     • RA00 (Discount): Any discount applied to the base price.
     • FRB1 (Freight): Transportation costs included in the total price.
     • MWST (Tax): Sales tax percentage applied to the order.

2. Access Sequence:

   • The system searches for condition records using a sequence of tables.
   • Example: First, the system checks for a specific vendor and material; if not found, it checks for a general material group.

3. Condition Tables:

   • Store condition records, such as specific prices for a material and vendor combination.

4. Pricing Procedure:

   • The pricing procedure determines the sequence in which condition types are applied to calculate the final price.
   • It includes:
     • Condition Types.
     • Calculation Rules (e.g., percentage, fixed amount).
     • Steps (sequence of condition types).

2. Configuration Steps for Pricing

1. Define Condition Types:

   • Condition types are predefined in SAP S/4HANA Cloud. You can review and activate them using the Manage Your Solution app.
   • Examples:
     • PB00 for base price.
     • RA01 for a fixed discount.

2. Maintain Pricing Conditions:

   • Use the "Manage Prices – Procurement" app to maintain prices, discounts, and freight charges.
   • Example:
     • Material: M123
     • Vendor: V001
     • Gross Price: $100
     • Discount: 5%

3. Access Sequence Assignment:

   • SAP searches condition records using the access sequence:
     • Vendor + Material → Material Group → General Discount.

4. Define Pricing Procedure:

   • The system assigns a pricing procedure based on:

     • Document type (e.g., purchase order).
     • Vendor.
     • Purchasing Organization.

   • Example of Steps in a Pricing Procedure:

     Step	Condition Type	Description	Calculation	Result
     10	PB00	Base Price	Fixed Value	$100
     20	RA00	Discount (5%)	Percentage	-$5
     30	FRB1	Freight Charge	Fixed Value	$10
     40	MWST	Tax (10%)	Percentage	$10.50
     Total				$115.50

5. Assign Pricing Procedure to Purchasing Documents:

   • The system automatically determines the pricing procedure during PR/PO creation based on defined rules.

1.3 Key Applications in SAP Fiori

SAP S/4HANA Cloud uses the SAP Fiori Launchpad as the central hub for procurement-related activities. Here are the key applications that support procurement processes:

1. Manage Purchase Requisitions

• Purpose: Create, review, and approve purchase requisitions.
• Key Features:
  • Create PRs manually or from templates.
  • Monitor approval status using workflows.
  • Assign sources of supply (suppliers).

2. Manage Purchase Orders

• Purpose: Create, change, and monitor purchase orders.
• Key Features:
  • Create POs with reference to PRs, contracts, or RFQs.
  • Monitor PO status (e.g., pending, approved, or completed).
  • Display purchase order history (e.g., GR, invoices).

3. Monitor Supplier Evaluation Scores

• Purpose: Track supplier performance based on delivery, price, and quality.
• Key Features:
  • View supplier scores using real-time analytics.
  • Filter results by supplier, material, or evaluation period.

4. Procurement Analytics

• Purpose: Analyze procurement KPIs and monitor performance.
• Key Features:
  • View dashboards showing open purchase orders, procurement spend, and supplier performance.
  • Embedded KPI tiles for quick insights into procurement efficiency.

1.4 Integration and Automation

Procurement processes in SAP S/4HANA Cloud integrate seamlessly with other modules like Finance and Inventory Management. Automation further enhances efficiency.

1. Integration with Finance

• Account Assignment:

  • Procurement processes integrate with the General Ledger (GL) for expense or asset procurement.
  • Example: Office supplies → Expense Account.

• Automatic Financial Postings:

  • Goods receipt (GR) triggers automatic postings to:
    • Debit: Inventory/Expense Account.
    • Credit: Goods Receipt/Invoice Receipt (GR/IR) Account.
  • Invoice verification clears GR/IR accounts and records tax postings.

2. Integration with Inventory Management

• Procurement processes update stock levels automatically:

  • Stock Procurement: Goods receipt increases stock levels in the warehouse.
  • Non-Stock Procurement: Goods receipt posts directly to an expense account.

• Goods Receipt Postings:

  • Record material movements using the Post Goods Receipt app.
  • Integration updates inventory quantities and values.

3. Automation of Processes

• Automatic PO Creation:

  • Approved PRs can trigger automatic PO creation.

• Scheduling Agreements:

  • Set up long-term procurement schedules with suppliers to reduce manual effort.
  • Example: Monthly delivery of 1,000 units over 12 months.

1.5 Reporting and Analytics

SAP S/4HANA Cloud offers powerful reporting and analytics tools to monitor and analyze procurement performance.

1. Key Reports in SAP Fiori:

1. Open Purchase Orders: Track POs that are not yet completed.
2. Supplier On-Time Delivery Report: Monitor suppliers’ delivery performance.
3. Procurement Spend Analysis: Analyze procurement expenses across suppliers and materials.

2. Embedded Analytics:

• Use SAP Fiori Overview Pages to view procurement KPIs.
• Example KPI tiles include:
  • Average PO Value.
  • Supplier Performance Score.
  • Number of Open PRs.

Implementation and Configuration for Sourcing and Procurement (Additional Content)

In this section, we will delve into additional important topics related to sourcing and procurement in SAP S/4HANA Cloud. These areas provide a deeper understanding of procurement types, purchase requisition (PR) to purchase order (PO) automation, contract vs. scheduling agreements, material master procurement fields, and supplier management.

1. Procurement Types in SAP S/4HANA Cloud

Procurement types define how an organization acquires goods and services. Different procurement types influence the configuration of material master data, approval workflows, financial postings, and supplier relationships.

1.1 Common Procurement Types

Procurement Type	Description	Impact on Inventory & Finance
Stock Procurement	Standard procurement where goods are received into inventory.	Increases stock levels and updates inventory valuation.
Consumable Procurement	Procurement of items for immediate consumption (e.g., office supplies).	The cost is directly booked to an expense account instead of inventory.
Subcontracting Procurement	The supplier provides a service while the buyer provides raw materials.	Requires sending raw materials to the supplier and tracking subcontracted components.
Third-Party Procurement	Goods are delivered directly from the supplier to the customer (drop shipment).	No stock update in the buying organization; revenue recognition is based on sales order fulfillment.
Service Procurement	Procurement of non-physical goods, such as consulting or maintenance services.	Uses service entry sheets instead of goods receipt postings.

1.2 How Procurement Type Affects Configuration

• Material Master Impact:
  • Stock Procurement requires MRP settings and inventory valuation.
  • Consumable Procurement links items to cost centers or asset accounts instead of stock.
• Approval Process Differences:
  • Third-party procurement and subcontracting often require additional approval steps.
• Financial Posting Differences:
  • Stock Procurement: Debit inventory, credit supplier account.
  • Consumable Procurement: Debit cost center instead of inventory.

2. Automated PR to PO Conversion in SAP S/4HANA Cloud

SAP S/4HANA Cloud allows automatic conversion of a purchase requisition (PR) to a purchase order (PO) under certain conditions.

2.1 Automatic PO Creation Configuration

PRs can be converted to POs automatically if the following conditions are met:

1. Automatic PO Indicator is set in Material Master or Vendor Master.
2. The MRP Run identifies purchase requirements and triggers PRs.
3. The PR contains a valid source of supply (vendor or purchasing contract).
4. The vendor is flagged as "Automatic PO Allowed" in Supplier Master Data.

Configuration Steps:

1. Go to SAP Fiori app: Manage Your Solution.
2. Configure "Automatic PO Creation" under Materials Management (MM).
3. Assign valid purchase info records (PIR) to enable auto-source determination.

2.2 Conditions for PR to PO Automation

Factor	Impact on PR to PO Automation
MRP Settings	PRs created via MRP can be automatically converted to POs.
Source List	If a fixed supplier is maintained, SAP can auto-create the PO.
Contracts or Scheduling Agreements	If a PR references a contract, the PO follows automatically.
Approval Workflow	PR must be fully approved before conversion.

3. Contract vs. Scheduling Agreement in Procurement

3.1 Understanding the Difference

SAP S/4HANA Cloud supports two types of long-term agreements with suppliers: Contracts and Scheduling Agreements.

Type	Definition	Key Characteristics
Contract	A long-term agreement to procure materials/services at predefined conditions, but without specific delivery schedules.	No fixed delivery dates; PRs/POs reference the contract.
Scheduling Agreement	A procurement agreement where the supplier delivers goods based on a predefined schedule.	Delivery dates are predefined; releases (delivery schedules) trigger automatic POs.

3.2 When to Use Each Agreement

• Use a contract when:
  • The procurement schedule is uncertain.
  • The buyer wants flexibility to place orders when needed.
• Use a scheduling agreement when:
  • The supplier delivers regularly (e.g., weekly or monthly).
  • The business wants to reduce manual PO creation.

Example:

• A contract might be used to buy office furniture over a year without committing to exact delivery dates.
• A scheduling agreement is used for raw materials supply, where the vendor delivers 1,000 units per month.

4. Key Procurement Fields in Material Master

The Material Master stores essential procurement-related information, ensuring correct sourcing, valuation, and approvals.

Key Fields in the Purchasing View

Field	Description	Impact on Procurement
Procurement Type	Specifies if the material is procured externally or produced internally.	Affects MRP and source determination.
Valuation Class	Defines which GL account the material is linked to.	Determines financial postings.
Purchasing Group	Assigned buyers responsible for procurement.	Used in PR and PO approvals.
Quota Arrangement	Divides procurement quantity among multiple suppliers.	Ensures supplier distribution balance.
Price Control	Defines how the material price is calculated.	Determines whether the moving average price or standard price applies.

Example:

• A procurement type of "External Procurement" enables automatic PR creation via MRP.
• A valuation class of "3100" ensures material postings go to inventory GL accounts.

5. Advanced Supplier Management in SAP S/4HANA Cloud

Effective supplier management ensures better procurement decisions and risk mitigation. SAP integrates supplier management within SAP Ariba and SAP S/4HANA Cloud.

5.1 Key Aspects of Supplier Management

Supplier Management Component	Description
Supplier Qualification	Ensures new vendors meet business requirements.
Supplier Performance Management	Evaluates delivery reliability, quality, and cost compliance.
Supplier Risk Analysis	Identifies financial, compliance, and operational risks.

5.2 Integration with SAP Ariba

SAP Ariba enhances supplier management by providing cloud-based collaboration and risk assessment tools.

SAP Ariba Supplier Management Feature	How It Benefits SAP S/4HANA Cloud Procurement
Supplier Lifecycle Management (SLM)	Enables qualification, onboarding, and certification of suppliers.
Supplier Risk Management	Uses third-party data to assess supplier financial and operational risks.
Spend Analysis	Helps procurement teams identify cost-saving opportunities.

Example:

• A company sources a new IT hardware supplier and uses SAP Ariba Supplier Qualification to assess reliability.
• Based on historical performance, the system automatically flags high-risk suppliers before PO creation.

Conclusion

The additional topics covered here provide a deeper understanding of SAP S/4HANA Cloud procurement processes. These enhancements ensure that procurement professionals and SAP consultants:

• Understand different procurement types and their system impact.
• Know how PRs convert to POs automatically based on configuration rules.
• Differentiate between contracts and scheduling agreements for supplier management.
• Effectively configure material master procurement fields to streamline purchasing.
• Leverage supplier evaluation and risk management tools for better decision-making.