SAP MM Consignment: How It Works, Why It Matters, and How to Run It Well

Featured

Tags

, , , ,

Consignment is one of those quiet superpowers in SAP Materials Management (MM): the vendor places stock at your site, you keep it on-hand, but you only pay when you actually use it. Done right, it improves cash flow, boosts supply flexibility, and simplifies replenishment—without adding accounting noise at goods receipt.

Below is a practical, end-to-end guide you can hand to analysts, buyers, and warehouse leads. It covers the process flow, the master data you need, movement types, settlement, reports, and real-world tips.


TL;DR (What makes consignment different?)

  • Ownership stays with the vendor until you consume the material.
  • No liability or inventory value at goods receipt; it’s tracked as vendor special stock (type K).
  • You pay on consumption (or when you transfer to own stock), typically via MRKO settlement.
  • Cash-flow friendly: you carry stock physically without tying up working capital.
  • Great for fast-movers and uncertain demand where you want availability without over-buying.

The Business Idea in Plain English

With consignment, vendors place materials in your warehouse or at point-of-use locations. You scan/receive them into SAP, but the goods are tagged as consignment stock visible and usable, yet not owned or valued by you. When production or maintenance actually uses the material (or when you explicitly transfer it to your own stock), SAP records consumption and later settles those quantities and prices back to the vendor. Think of it as “stock on your floor, vendor on the hook until you consume.”


Core Process Flow (with common T-Codes)

  1. Create Consignment Info RecordME11
    Create a purchasing info record of type Consignment for material/vendor/plant. Maintain the price and relevant conditions here; this is the reference used for settlement later.
    Tip: Treat this price like a contract price keep it current; it drives what you’ll pay at settlement.
  2. Create Purchase OrderME21N
    Use item category K (Consignment). The PO often has a zero net price line, because the actual payable amount is determined during settlement from the info record conditions. No account assignment is needed.
  3. Goods Receipt to ConsignmentMIGO
    Post GR against the PO. The stock appears in your warehouse as consignment special stock (K).
    • No accounting document is created at GR.
    • Stock is visible in MMBE as “Consignment.”
    • You can store it anywhere (bin, storage location) just like regular stock.
  4. Consumption (Goods Issue)MIGO (or other GI transactions)
    When production, maintenance, or a cost center uses the material, post a goods issue from consignment. This reduces consignment stock and marks those quantities as billable to you.
    • Typical movement types include 201 K (to cost center), 261 K (to production order), 221 K (to project), etc.
    • You may also transfer consignment to own stock using 411 K if you want ownership before actual consumption (e.g., for resale or internal staging policies).
  5. Settle with the VendorMRKO
    Settlement aggregates all posted consumptions/transfers (e.g., 201 K / 261 K / 221 K / 411 K) over a date range, uses the consignment info record price, and generates the vendor credit memo. This is when the liability is recognized and the vendor gets paid.
    Good practice: Run MRKO on a cadence (weekly or monthly) with a variant by purchasing organization/plant.

Why Businesses Use Consignment (Benefits)

  • Better cash flow: You avoid tying up cash at receipt; you only pay when materials truly leave consignment.
  • Inventory flexibility: You can hold a wider buffer for critical or variable-demand items without financial penalty.
  • Supplier partnership: Vendors gain share-of-shelf at your site; you gain service level. It’s a mutual trust play.
  • Operational simplicity: Day-to-day handling is familiar to warehouse teams; the key difference is stock category and later settlement.

Master Data & Configuration Touchpoints

1) Material Master

  • Standard MRP, storage, and unit settings apply. No special material type is required.
  • Ensure correct valuation class and price control for when stock is transferred to your ownership (411 K) or consumed and settled.

2) Vendor Master

  • Standard purchasing data; consignment doesn’t require a special account group.
  • Make sure the vendor is flagged correctly for your purchasing org and plant.

3) Purchasing Info Record (Consignment)ME11

  • Create an Info Record of category “Consignment.”
  • Maintain conditions/prices; these are crucial for MRKO settlement.
  • Maintain tax and inco terms as needed. MRKO will use pricing/tax data.

4) PO SetupME21N

  • Item Category K is the differentiator. Schedules can be used for planned deliveries.
  • Often price in the PO is informational; settlement price comes from the info record.

5) SettlementMRKO

  • Configure variants for plants/purchasing orgs.
  • Coordinate with AP on posting period and tax behavior.
  • If you use output or interfaces for vendor docs, align with finance on the posting and credit memo flow.

Movement Types Cheat Sheet (Common Ones)

  • 101 (GR) to consignment via PO item category K: puts stock into consignment special stock, no accounting.
  • 201 K / 261 K / 221 K (GI from consignment): consumption to cost center, order, or project; drives settlement.
  • 411 K (transfer consignment → own stock): you take ownership; drives settlement.
  • Returns/Corrections mirror the above with appropriate reversal movement types (e.g., 262 K etc.).

Note: In S/4HANA, most historical MB1A/MB1B transactions are consolidated in MIGO; power users can still post these movement types there.


Reporting & Controls You’ll Actually Use

  • MMBE / Stock Overview: See consignment quantities alongside own stock; look for the Consignment bucket.
  • MB54 – Consignment Stocks: List consignment stock and related liability preview.
  • MRKO – Settlement: Display and settle consumptions by vendor/material/plant and date range.
  • ME2 purchasing lists:* Track open POs and delivery status for consignment items.
  • Physical Inventory: You can count consignment stock by vendor (special stock K) using the standard MI* transactions with the vendor specified.

How Consignment Interacts with MRP & Operations

  • Availability: Consignment stock is physically present and available for use. From a planning perspective, most businesses treat it much like unrestricted stock because it is on the floor.
  • Netting in MRP: In standard practice, consignment quantities can be considered in net requirements. Verify your local settings and planning procedures; your planners should understand that it’s usable inventory, just not yet owned.
  • Replenishment: Vendors typically replenish based on VMI, min/max agreements, forecasts, or your scheduled consignment POs. The PO (K) is still the logistics object to receive against.

What Actually Hits Finance (and When)

  • At GR to consignment: No accounting entry. Inventory isn’t valued, since it’s not owned.
  • At Consumption/Transfer (e.g., 201 K / 261 K / 221 K / 411 K): Quantities become eligible for settlement.
  • At Settlement (MRKO): The vendor credit memo is posted:
    • Debit: consumption/cost (or inventory if you did 411 K to take ownership first)
    • Credit: vendor payable
      Taxes and freight/conditions are applied per the consignment info record and MRKO logic.

When Consignment Shines (Use Cases)

  • High-usage, cost-sensitive consumables (fasteners, chemicals, MRO items).
  • Demand variability: items with unpredictable draw where you still need availability.
  • Supplier-managed replenishment: when vendors are willing to monitor and refill on your behalf.
  • Ramp-ups or NPI: keep materials on-hand during uncertain early demand without capitalizing everything.

Common Pitfalls (and How to Avoid Them)

  1. No Consignment Info Record Price
    • Symptom: MRKO can’t settle or settles at the wrong rate.
    • Fix: Maintain accurate prices and validity periods in ME11 (Consignment).
  2. Wrong Stock Type at GR
    • Symptom: GR posted to own stock instead of consignment, creating unwanted inventory value/liability.
    • Fix: Ensure item category K on PO and verify the MIGO line shows consignment special stock.
  3. Goods Issues Without ‘K’
    • Symptom: Consumption posted from own stock (no ‘K’) when it should have reduced consignment, leaving consignment balances stuck.
    • Fix: Train warehouse teams: when consuming from consignment, use movement types with K (e.g., 201 K, 261 K).
  4. Infrequent Settlement
    • Symptom: Large swings in vendor payables at month-end, unhappy suppliers, or audit surprises.
    • Fix: Schedule MRKO routinely (weekly/monthly) with a shared calendar between Purchasing and AP.
  5. Physical Inventory Gaps
    • Symptom: Book vs. floor differences linger.
    • Fix: Include consignment special stock K counts in cycle counting and year-end procedures; involve the vendor if required by contract.

A Quick Walk-Through Example

  • Set up a consignment info record (ME11) for Material M-100, Vendor V-200 at Plant P-300 with a valid price.
  • Place an order via ME21N with item category K for 1,000 units.
  • Receive 1,000 units in MIGO. Stock is visible as consignment in MMBE; no accounting document is created.
  • Use 400 units for a production order (261 K). Later, transfer 100 units to your own stock (411 K) for resale staging.
  • Settle week-end via MRKO: the 400 consumed + 100 transferred are priced per the info record. A vendor credit memo posts; AP pays per standard terms.

Implementation Tips & Governance

  • Define your cadence for MRKO and who owns it (Purchasing? AP?). Publish a short SOP with screenshots.
  • Train on movement types—especially the “K” variants—using a one-pager for warehouse and production.
  • Align tax and conditions with Finance early. MRKO isn’t MIRO; ensure downstream reporting matches expectations.
  • Monitor MB54 & MRKO regularly to spot anomalies (stagnant consignment stock, missing prices, unusual consumption patterns).
  • Start with a pilot (one plant, few materials, one vendor) before scaling.

Key Transactions (Quick Reference)

  • ME11 – Create Consignment Info Record
  • ME21N – Create PO (Item Category K)
  • MIGO – GR to consignment / GI from consignment (e.g., 201 K, 261 K, 411 K)
  • MMBE – Stock Overview (see Consignment bucket)
  • MB54 – Consignment Stocks
  • MRKO – Consignment Settlement (and display)

Final Word

Consignment in SAP MM is a win-win when processes and master data are clean. You get the service level of local stock without the capital burden of immediate ownership. Vendors get sticky, predictable demand and closer collaboration. Set up your info records correctly, train on the “K” movement types, and run MRKO like clockwork and consignment will quietly do what it does best: keep materials flowing and cash free for what matters.


The author, Ray Hornbrook, has many years of SAP functional and technical experience.  Ray started his career in SAP as a MM/PP Subject Matter Expert (SME) for a SAP implementation and is now a Senior Level SAP Consultant.  Since Ray has worked both sides of SAP, business end user and IT professional, he is able to communicate effectively with both IT and Business team members. Having a background as an SAP business end user has helped Ray greatly in his consulting career.  The business background helps him better communicate with the business members of the team.  As well as helping bridge gaps in communication between the IT and Business team members.

To find out more about Ray Hornbrook please check out his LinkedIn profile by clicking HERE.

End of document – www.portsap.com

SAP MM/P2P: Decision Playbook: Contracts vs. Scheduling Agreements with the Config Touchpoints

Featured

Tags

, , , , , , , ,

The Decision Playbook exists to give buyers, planners, and MM config teams a fast, shared way to choose between Contracts and Scheduling Agreements—and run each the right way. It turns policy into simple rules, key config touchpoints, and step-by-step flows so teams standardize decisions, cut PO noise, calm “nervous” schedules, and improve KPIs like contract consumption, OTIF, and MD04 exception closure.

Pick the right instrument (decision rules)

Choose a Contract when:

  • Demand is sporadic/variable, project-based, or service-heavy.
  • You want commercial terms locked but timing via POs.
  • Multi-plant consumption or flexible delivery patterns.

Choose a Scheduling Agreement (SA) when:

  • Demand is repetitive/stable (components, packaging, C-parts).
  • You want time-phased schedule lines and fewer POs.
  • You’ll use MRP and often EDI to send forecast/JIT releases.

Master data checklist (both paths)

  • Material master: Purchasing + MRP views complete (lot-sizing, lead times, rounding, planned delivery).
  • Vendor master / BP: Purchasing org + plant data set; partner functions; EDI eligibility if applicable.
  • Purchasing Info Record: Price/conditions; delivery tolerances; GR-based IV preference.
  • Source List (if used): Validity maintained; Fixed source tick for the chosen outline agreement.
  • Quota (optional): If multiple sources.

Configuration touchpoints (SPRO paths)

A. Outline agreements — general

  • Doc types & number ranges
    • SPRO → MM → Purchasing → Purchasing Documents → Contracts / Scheduling Agreements → Define Document Types & Number Ranges
  • Field selection & allowed item categories
    • SPRO → MM → Purchasing → Purchasing Documents → Define Document Types → … (field sel., item cat. allow-list)
  • Release strategy (approvals)
    • SPRO → MM → Purchasing → Purchase Requisition / Purchase Order → Release Procedure with Classification
      (Use CEKKO fields for OA approvals if required.)

B. Contracts (ME31K/ME32K/ME33K)

  • Standard types: MK (Quantity Contract), WK (Value Contract).
  • Pricing: Allow item-level conditions; align with your pricing procedure (SPRO → MM → Purchasing → Conditions).
  • Consumption reporting: Ensure doc type updates target value/qty for reporting (ME3*).
  • Services: Enable item category D (service) if you’ll use service contracts.

C. Scheduling Agreements (ME31L/ME32L/ME33L, ME38, ME84/ME9E)

  • Standard types: LP (without release documentation) and LPA (with release documentation).
  • Release Creation Profile (required for LPA)
    • SPRO → MM → Purchasing → Scheduling Agreement → Define Release Creation Profile
      Configure:
    • Horizons: Forecast horizon (e.g., 13 weeks); firm zone (e.g., 2 weeks).
    • Aggregation: Daily for short horizon (e.g., 2 weeks), weekly thereafter.
    • Change tolerances: % thresholds to limit “nervousness.”
    • Backward/forward consumption and cumulative quantities behavior.
  • Output/EDI for Releases
    • SPRO → Sales & Distribution → Basic Functions → Output Control (or NACE: Application EF)
      Define output types for Forecast and JIT releases; assign access sequences/condition tables and forms/IDocs.
    • Partner profiles (WE20): Map vendor to outbound DELFOR (forecast) and DELJIT (JIT) IDocs (EDIFACT), or appropriate ANSI/X12 equivalents.
  • Plant specificity: Enforce plant at header/item; SA is plant-specific by design.
  • Delivery tolerances & confirmations
    • SPRO → MM → Purchasing → Confirmations → Set Tolerances / Confirmation Control Keys
      (e.g., allow +5% overdelivery; set ASN requirement if used.)
  • GR-based IV default
    • SPRO → MM → Logistics Invoice Verification → GR-Based IV (and field defaults via field selection).

D. Source Determination (for MRP integration)

  • Source list requirement
    • SPRO → MM → Purchasing → Source List → Set Up Source List Requirement (per plant/material type).
  • Automatic source assignment
    • Ensure Info Record exists; Source List entry references the Contract or SA with validity; Fixed tick for primary source.
  • Quota arrangement (optional)
    • SPRO → MM → Purchasing → Quota Arrangement (if splitting demand across sources).

Process flows & roles

Contract flow (Buyer-led, flexible dates)

  1. Create Contract (ME31K: MK/WK) with conditions & validity.
  2. Master data link: Info Record; Source List → reference Contract.
  3. MRP/Planner raises PRs (MD01/MD04) → Auto-PO (ME59N) or manual PO (ME21N) referencing contract.
  4. GR (MIGO) → LIV (MIRO/MIR7).
  5. Monitor: ME3L/ME3M for consumption vs. target; price compliance.

Scheduling Agreement flow (Planner-led, time-phased)

  1. Create SA (ME31L: LPA if using releases) with price, validity, Release Creation Profile.
  2. Source List: Reference SA; mark Fixed.
  3. Schedules:
    • ME84 to generate Forecast/JIT releases (per profile).
    • ME9E to output/send releases (print/EDI).
    • ME38 to review/adjust schedule lines (near-term buckets).
  4. Vendor ships to schedule; GR (MIGO) per delivery.
  5. Monitor: MD04 (firm/open lines), SA release history, cumulative qty reconciliation, vendor OTIF.

RACI (quick):

  • Buyer: Outline agreement terms, pricing, approvals.
  • Planner/MRP: Schedule horizons, ME84/ME38 cadence, MD04 exceptions.
  • EDI/Tech: Output/IDoc config, partner profiles, error handling (WE02/WE05).
  • Warehouse/AP: GR accuracy; GR-based IV; invoice match rate.

Recommended defaults (sane starting points)

Contracts

  • Types: MK for predictable quantities; WK when $ cap is the control.
  • Pricing: Keep gross price in Info Record; use contract item conditions only when you must override.
  • Reporting: Enforce realistic target to make consumption meaningful.

Scheduling Agreements (LPA)

  • Release Creation Profile:
    • Forecast horizon 13 weeks.
    • Firm zone: 2 weeks (no changes transmitted).
    • Aggregation: Daily (weeks 1–2), weekly (weeks 3–8), monthly (>8).
    • Change tolerance: ±10% within firm zone; ±20% outside.
  • Delivery tolerances: +5% / −0% (typical for C-parts).
  • GR-based IV: Active.
  • EDI: DELFOR (forecast) weekly; DELJIT (JIT) daily for high runners.

Controls & KPIs

Contracts

  • Contract consumption % vs. time used.
  • POs referencing contract % (leakage).
  • Price compliance and lead time to first delivery.

SAs

  • Schedule adherence (vendor OTIF vs. firm zone).
  • Cumulative qty reconciliation (SAP vs. supplier).
  • Change noise (lines changed inside firm zone).
  • Exception messages in MD04 cleared within SLA.

Common pitfalls & remedies

  • MRP not picking SA/Contract → Check Source List validity & Fixed flag; Info Record existence; quota precedence.
  • Vendors ignore schedule changes → Tighten firm zone; align communication on release cadence; ensure EDI success (monitor WE02).
  • Nervous schedules → Increase aggregation, widen change tolerances, review MRP lot-sizing & safety stock.
  • Wrong plant on SA → Remember SAs are plant-specific; split by plant.
  • Services in SA → Avoid; use Contracts (item cat. D) for services.

Quick-reference (t-codes)

  • Contracts: ME31K / ME32K / ME33K; Reports ME3L/ME3M/ME3C
  • Scheduling Agreements: ME31L / ME32L / ME33L; ME38 (schedule lines); ME84 (create releases); ME9E (output releases)
  • MRP/Monitoring: MD04 (stock/reqs), MD07 (MRP lists)
  • GR/IV: MIGO; MIRO/MIR7
  • EDI monitor: WE02/WE05

Check out: SAP MM: Difference between SAP Scheduling Agreements vs. Contracts


The author, Ray Hornbrook, has many years of SAP functional and technical experience.  Ray started his career in SAP as a MM/PP Subject Matter Expert (SME) for a SAP implementation and is now a Senior Level SAP Consultant.  Since Ray has worked both sides of SAP, business end user and IT professional, he is able to communicate effectively with both IT and Business team members. Having a background as an SAP business end user has helped Ray greatly in his consulting career.  The business background helps him better communicate with the business members of the team.  As well as helping bridge gaps in communication between the IT and Business team members.

To find out more about Ray Hornbrook please check out his LinkedIn profile by clicking HERE.

End of document – www.portsap.com

SAP MM: Difference between SAP Scheduling Agreements vs. Contracts

Featured

Tags

, , , , , ,

The purpose of this blog is to demystify SAP MM Scheduling Agreements vs. Contracts so buyers, planners, and MM config teams know exactly when to use which, how each flows (PO call-offs vs. schedule releases), and which config touchpoints matter (doc types, source list, release profiles, EDI, GR-based IV). It gives clear decision rules and quick process snapshots to reduce PO noise, align with MRP, and improve supplier performance and compliance so teams make consistent, faster sourcing decisions.

Both are Outline Agreements in SAP MM (long-term supplier agreements).

Contracts commit to an overall value or quantity; you place POs (call-offs) against them when you actually need goods/services.

Scheduling Agreements (SAs) commit to time-phased deliveries; the agreement itself carries schedule lines (dates/qty) that the supplier ships against—no separate PO per delivery.

Quick comparison

TopicContractScheduling Agreement
Primary useIrregular or varied call-offs; materials and servicesRepetitive materials with steady consumption (e.g., components)
Commitment typeTarget value (WK) or quantity (MK) over a validity periodTime-phased quantities via delivery schedule lines
How you “order”Create POs referencing the contractMaintain schedule lines and send releases (forecast/JIT)
Dates/DeliveriesDates decided on each PODates live inside the SA (weekly/daily buckets)
Typical granularityCoarse: “up to $X or Y units”Fine: “Deliver 200 this Fri, 300 next Tue…”
Plant specificityCan be cross-plant at header; plant usually at item/POPlant-specific (needs plant for schedule lines)
Price conditionsIn the contract (or via info record)In the SA (or via info record); stable pricing
MRP integrationPRs can source from a contract; POs createdMRP can build schedule lines; strong source determination
Documents & TcodesME31K/ME32K/ME33K → POs (ME21N) → GR/IVME31L/ME32L/ME33L → Sched. lines (ME38) → Releases (ME84/ME9E) → GR/IV
TrackingContract consumption vs. targetOpen/firm schedule lines and release history
EDI commonalityLess commonVery common (Forecast/JIT releases)

When to use which

Use a Contract when…

  • Demand is sporadic or project-based.
  • You need commercial terms locked, but want flexible timing via POs.
  • You’re buying services or mixed items with variable specs.

Use a Scheduling Agreement when…

  • You have repetitive, stable demand and want suppliers to ship to a rolling schedule.
  • You want tight MRP integration and fewer POs.
  • You use EDI to send forecast/JIT releases.

Process at a glance

Contract flow: Create contract → (MRP creates PRs or you order) → Create PO referencing the contract → GR/IV → Contract consumption updates.

SA flow: Create SA (price/qty/validity) → Maintain or MRP-generate schedule lines → Send forecast/JIT releases → Vendor ships per schedule → GR against SA → Invoices reference deliveries.

Tips & gotchas (real-world)

  • Prices: Keep pricing in the info record for reuse; override in the contract/SA only when necessary.
  • Source determination: For SAs, maintain Source List and (optionally) Quota so MRP selects the SA and builds schedules.
  • Release creation profile (SAs): Set horizons/aggregation (weekly/daily) to avoid “nervous” schedule churn.
  • Validity & targets: Contracts need realistic target value/qty for meaningful consumption reporting.
  • Services: Prefer contracts; SAs are material-centric.
  • Reporting: Use ME3* reports for outline-agreement monitoring; MD04 for SA demand/schedule visibility.

Check out: “SAP MM/P2P: Decision Playbook: Contracts vs. Scheduling Agreements with the Config Touchpoints


If you have question on this or any other PortSAP Consulting blog please feel free to contact us at Blog@PortSAP.com. Or if you are looking for Top Quality SAP Consultants please feel free to contact us.

The author, Ray Hornbrook, has many years of SAP functional and technical experience.  Ray started his career in SAP as a MM/PP Subject Matter Expert (SME) for a SAP implementation and is now a Senior Level SAP Consultant.  Since Ray has worked both sides of SAP, business end user and IT professional, he is able to communicate effectively with both IT and Business team members. Having a background as an SAP business end user has helped Ray greatly in his consulting career.  The business background helps him better communicate with the business members of the team.  As well as helping bridge gaps in communication between the IT and Business team members.

To find out more about Ray Hornbrook please check out his LinkedIn profile by clicking HERE.

End of document – www.portsap.com

EDI 852 & 867 with SAP (via IDocs): A Practical Guide for SAP Super Users

Tags

, , , , , , ,

If you work with customers or distributors who share sell-through and inventory data, you’ve probably heard “Send us your 852,” or “We’ll send you 867 resale.” This guide explains what those X12 messages mean in SAP terms, how they move through IDocs, and what you, as a super user, actually do day to day. You’ll also see realistic scenarios you can use to sanity-check your design.


Quick primer: what each message does

  • EDI 852 — Product Activity Data (usually inbound)
    Retailers or distributors send you store/DC-level activity by SKU and date: sales (units out), on-hand inventory, receipts, sometimes returns and forecasts. Your team uses it for demand visibility, VMI, and replenishment tuning.
  • EDI 867 — Product Transfer & Resale (usually inbound)
    Distributors send resale to end customers/locations and sometimes transfer movements. You use it to trace channel sales and to settle rebates/chargebacks (ECC: SD rebates; S/4: Settlement Management/Condition Contracts).

How the flow works (high level)

  1. Trading partner → EDI gateway
    Your partner sends X12 852 or 867. Your EDI/B2B platform validates, translates, and maps to an SAP IDoc format.
  2. EDI gateway → SAP (inbound IDoc)
    The mapped file is posted to SAP over tRFC/HTTPS. Your partner profile (WE20) points the message to the right message type/process code and basic type.
  3. SAP application processing
    • 852 typically becomes a PROACT (product activity) IDoc—or Retail POS IDocs in SAP for Retail—and updates activity repositories used for VMI/replenishment and analytics.
    • 867 typically lands as SLSRPT (sales reporting) or a custom Z-IDoc and feeds resale history, often downstream to rebates/chargebacks or Settlement Management.
  4. Acknowledgements & monitoring
    997s (functional acks) go back to partners; you monitor IDoc statuses in WE02/WE05 and reprocess errors in BD87. Application logs and custom error queues catch unknown SKUs or sites.

The SAP objects and IDocs you’ll most likely see

  • 852 (Product Activity Data)
    • PROACT (e.g., PROACT01/02): generic product activity—sales, on-hand, receipts by site/SKU/date.
    • Retail POS IDocs like WPUUMS (sales), WPUWBW (stock), WPUUMR (receipts) if you’re on SAP for Retail.
    • Some teams stage 852 into Z-tables first to cleanse, then post into planning/analytics.
  • 867 (Product Transfer & Resale)
    • SLSRPT (e.g., SLSRPT01): sales reporting by end-customer/ship-to/location.
    • Custom Z-IDoc or extended PROACT if you need extra fields for rebate/chargeback references.
    • In S/4HANA Settlement Management, 867 is often staged then posted via APIs/BAdIs into Condition Contract determination and calculation.

What a super user actually does

  • Day-to-day checks
    • Review last inbound 852/867 batches in WE02/WE05.
    • Triage and reprocess in BD87.
    • Work exceptions: unknown SKU, unit mismatch, invalid location, missing contract reference.
  • Master data guardrails
    • Keep material cross-references current (partner UPC/EAN ↔ your material).
    • Validate location/site codes (plants, storage locations, sites).
    • Normalize UOMs (EA vs CS) and dates (daily vs weekly buckets).
  • Downstream sanity
    • For 852: verify that activity updates are visible in replenishment/VMI dashboards or demand planning.
    • For 867: verify resale lines are visible for rebate/chargeback or Condition Contract settlement and that accruals/settlements behave as expected.

Scenario 1: Retail VMI using EDI 852 (PROACT)

Business story
You supply camping stoves to a national retailer that wants vendor-managed inventory. Every night they send 852 with yesterday’s sales and current on-hand by store.

What arrives
For SKU CAMP-STOVE-100, you receive:

  • Store 311, Date 2025-09-25: Sales 8, On-hand 24, Receipts 0
  • Store 528, Date 2025-09-25: Sales 3, On-hand 7, Receipts 12

SAP flow

  • Your EDI tool maps 852 → PROACT02.
  • IDoc posts and updates your product activity repository.
  • Your VMI logic (in SAP or IBP) sees Store 311’s on-hand is trending below target and proposes a replenishment to the DC.

Super user checklist

  • Confirm material cross-reference: Retailer sends UPC 123456789012 → your CAMP-STOVE-100.
  • Check UOM: Retailer sends CS of 4 but sales are in EA—mapping converts correctly.
  • Verify planning result: You see a replenishment proposal for Store 311 or DC allocations reflecting the drop in on-hand.
  • If the IDoc errors with “Unknown site 311,” add/maintain the site mapping and reprocess (BD87).

Value
Fewer stockouts, smarter allocations pre-promotion, better forecast accuracy because you see sell-through and on-hand, not just your shipments.


Scenario 2: Distributor resale & chargebacks using EDI 867 (S/4 Settlement Management)

Business story
You sell water filters to a distributor at a list price, but offer a ship-and-debit (rebate) when they sell to approved end customers in municipal accounts. The distributor sends 867 weekly: who they sold to, when, and how many.

What arrives
For SKU WTR-FILT-MUNI, week ending 2025-09-26:

  • End Customer: City of Springfield Water Dept (ship-to 009876)
  • Qty: 120 EA, Net resale price: $45.00
  • Distributor transfer: from DC-01 to DC-03, 60 EA

SAP flow

  • 867 → SLSRPT01 (or custom) lands in a staging area.
  • Condition Contract (Settlement Management) finds a match for the end-customer group and SKU.
  • System accrues the rebate or directly settles a chargeback/credit based on contract terms (e.g., $5/unit).
  • Finance sees traceability from inbound resale to accrual/settlement lines.

Super user checklist

  • Confirm end-customer mapping (distributor’s ship-to ↔ your customer master/partner function).
  • Verify the Condition Contract includes this SKU and customer group and is valid for the resale date.
  • Review calculated quantity base (did transfers get excluded if your rules say so?).
  • If lines fail with “No contract found,” check condition contract determination and resale attributes (customer group, material, sales org).

Value
Fast, auditable channel programs. Lower dispute rates because your settlement math matches the distributor’s resale data.


Key master data and configuration (what trips teams up)

  • Partner profiles & ports: WE20/WE21 must point to the right message type and process code (and the correct basic type, e.g., PROACT02).
  • Material cross-references: Central table or custom mapping for UPC/EAN/customer material number ↔ MATNR.
  • Location/site mapping: Retail store/DC codes to your plant/site IDs.
  • UOM & pack: Align EA/CS and pack sizes; ensure conversions exist in MARM.
  • Calendars & buckets: Decide daily vs weekly; capture “week ending Friday” logic consistently.
  • Rebate/Settlement setup: ECC SD rebates or S/4 Condition Contracts with correct key fields; design how transfers and returns affect eligibility.

Monitoring, controls, and KPIs

  • Operational controls
    • 997 acknowledgements exchanged and monitored.
    • IDoc status dashboards: counts by partner, by day; top error reasons.
    • Exception queues: unknown SKU/site, negative on-hand, duplicate days.
  • Health KPIs
    • Timeliness of 852/867 receipts (e.g., >95% received by 10:00 local).
    • Match rate of SKU/site (target >99%).
    • Impact on forecast accuracy or OOS rate (852).
    • Rebate/chargeback settlement cycle time and dispute rate (867).

Practical tips for a smooth rollout

  • Start with a minimal viable mapping: SKU, site, date, quantity. Add price/PO/transfer flags later.
  • Decide the IDoc by downstream use: If you need VMI and planning, PROACT fits. If you need resale for settlements, SLSRPT or a purpose-built Z-IDoc is safer.
  • Backfill history: Ask partners for a catch-up of 6–13 weeks to seed planning and settlement baselines.
  • Document your “truth rules”: Net vs gross sales, how to treat returns, how to handle inter-DC transfers, late corrections.
  • Own the mapping tables: Give super users simple tools (ALV, Fiori list) to maintain UPC↔MATNR and site codes without waiting on IT.

Common issues you’ll recognize—and how to handle them

  • “Everything posted, but planning didn’t change.”
    Check the activity repository or planning interface job; confirm the bucket granularity (daily vs weekly) matches your planning run and that the posting date aligns with your horizon.
  • “Rebates missed a week of resale.”
    Look for date misalignment (partner’s “week ending Sunday” vs your calendar). Validate Condition Contract validity windows and the precise customer/material keys used for determination.
  • “Tons of errors: unknown items.”
    Refresh the UPC/EAN mappings or load new alternative UOMs. Often it’s one new product line missing from your cross-reference.

Quick start checklist (print this)

  • Partner profile in WE20 with correct message/process codes
  • Basic type chosen (PROACT02 or SLSRPT01—or your Z-type)
  • Material and location cross-reference tables loaded
  • UOM and pack conversions in MARM verified
  • Staging/cleansing job scheduled; BD87 access for reprocessing
  • For 867: Condition Contracts or SD rebates configured and testable
  • Monitoring: WE02/WE05 views, error dashboards, and 997 tracking
  • Agreed business rules (returns, transfers, late corrections, bucket logic) documented

Mini FAQ

  • Do I have to use PROACT for 852 and SLSRPT for 867?
    No, but they’re natural fits. Choose the structure that best aligns with your downstream processes. Many teams extend via Z-segments when they need extra fields.
  • Can 852 drive automatic replenishment?
    Yes—commonly for VMI. You still need guardrails: target stocks, min/max logic, and exception alerts.
  • What changes in S/4 vs ECC for 867?
    The big difference is using Settlement Management (Condition Contracts) instead of classic SD rebates. It’s more flexible, but you must align 867 keys (customer/material attributes) with contract determination early.

The bottom line

Think of 852 as your window into the shelf. It feeds replenishment and planning. Think of 867 as proof of who bought what. It feeds channel programs and settlements. As a super user, your superpower is keeping the mappings clean, the buckets aligned, and the exceptions moving so planners and finance see trustworthy results without wrestling with raw EDI.


If you have question on this or any other PortSAP Consulting blog please feel free to contact us at Blog@PortSAP.com. Or if you are looking for Top Quality SAP Consultants please feel free to contact us.

The author, Ray Hornbrook, has over 19 years of SAP functional and technical experience.  Ray started his career in SAP as a MM/PP Subject Matter Expert (SME) for a SAP implementation in 1998 and is now a Senior Level SAP Consultant.  Since Ray has worked both sides of SAP, business end user and IT professional, he is able to communicate effectively with both IT and Business team members. Having a background as an SAP business end user has helped Ray greatly in his consulting career.  The business background helps him better communicate with the business members of the team.  As well as helping bridge gaps in communication between the IT and Business team members.

To find out more about Ray Hornbrook please check out his LinkedIn profile by clicking HERE.

End of document – www.portsap.com