Picking and PGI
SD / O2Cintermediate

SD Picking and PGI Part 2: Picking Relevance, Storage Location Determination and PGI Posting Logic

Key takeaway

Configure what makes picking and PGI work: picking relevance in delivery item categories, storage location (picking location) determination rules MALA, RETA and MARE, the movement type from schedule line categories, and the accounting logic (valuation class, OBYC transaction keys GBB/VAX and BSX) behind the PGI posting.

Explanation

📌 KEY POINTS
✅ Picking relevance is set in the delivery item category (0VLP); non-relevant items (e.g. services) are not picked.

✅ Storage location rule in the delivery type: MALA (shipping point + plant + storage condition), RETA (plant + situation + storage condition), MARE (MALA, then RETA).

✅ Movement type (601) comes from the schedule line category and is copied into the delivery item.

✅ PGI accounting: inventory (BSX) credited, COGS (GBB with account modifier VAX) debited, determined by valuation class and valuation area.

⚠️ Missing picking location assignment (OVL3) leaves storage location empty and blocks picking and PGI.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 1 described the flow. Now the configuration behind it.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PICKING RELEVANCE

  • 0VLP: relevant for picking.
  • Storage location required / determine storage location / don't check.

━━━━━━━━━━━━━━━━━━━━
▶ 2. STORAGE LOCATION DETERMINATION

  • Delivery type rule: MALA, RETA, MARE.
  • MALA: picking location by shipping point + plant + storage condition (material).
  • RETA: by plant + situation + storage condition (used e.g. with warehouse numbers).
  • Assignment in OVL3 (picking locations).

━━━━━━━━━━━━━━━━━━━━
▶ 3. MOVEMENT TYPE

  • From schedule line category (VOV6): 601 standard, 651 returns.
  • Special stock scenarios use other movement types.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ACCOUNTING LOGIC

  • OBYC: BSX inventory account, GBB with modifier VAX (COGS for sales without account assignment).
  • Valuation class from material accounting view.
  • Profit center/segment derivation from material/plant.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CHECKS AT PGI

  • Picking complete, batches assigned, serial numbers, stock available in storage location.
  • Posting period open (MMRV).

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Check the delivery type storage location rule.
  2. Maintain OVL3 picking locations.
  3. Verify movement type in VOV6.
  4. Check OBYC GBB/VAX and BSX for the valuation class.
  5. Create delivery, pick, PGI; review documents.

✅ CHECKPOINT: storage location is proposed automatically and PGI posts to the expected G/L accounts.

Code example

ABAP Code
===== STEP 1: storage location rule (delivery type 0VLK) =====MALA : shipping point + plant + storage condition → storage locationRETA : plant + situation + storage condition → storage locationMARE : MALA first, then RETA ===== STEP 2: picking locations (SPRO > Logistics Execution > Shipping > Picking >             Determine Picking Location > Assign Picking Locations)  (OVL3)Shipping point 1000 | Plant 1000 | Storage condition 01 (ambient) → Sloc 0001Shipping point 1001 | Plant 1000 | Storage condition 02 (cold)    → Sloc 0002 ===== STEP 3: PGI accounting (OBYC) =====BSX           valuation class 7920 → inventory finished goodsGBB + VAX     valuation class 7920 → COGSMovement 601 (from schedule line category CP)

Real project scenario

After adding a cold-storage location, cold-chain materials still picked from the ambient location. The delivery type used MALA, but OVL3 had no entry for storage condition "cold" at the new shipping point, so the system fell back to manual entry, and clerks chose the wrong location. Adding the OVL3 entries and making storage location mandatory for the item category fixed it; the storage condition was also validated in material master governance.

Common mistakes

  • Missing OVL3 entries for new shipping points or storage conditions.
  • Choosing RETA without warehouse number setup.
  • Wrong movement type in copied schedule line categories.
  • Missing OBYC entries for new valuation classes.
  • PGI failing due to closed posting periods.

Best practices

  • Align storage location rules with warehouse layout.
  • Maintain storage conditions in material master.
  • Test PGI accounting for each valuation class.
  • Keep posting periods managed in cutover calendars.
  • Document picking location logic.

Interview angle

Questions: "How is the picking storage location determined?", "Where does the PGI movement type come from?", "Which accounts are posted at PGI?"
Strong answer: 0VLP picking relevance; delivery type rule MALA/RETA/MARE with OVL3 assignment; movement type from schedule line category; OBYC BSX and GBB-VAX by valuation class; checks like picking completeness and open period.

Practice this lesson

Quick check

1. Which G/L postings are made at PGI for a standard delivery?

2. Where does the movement type posted at PGI come from?

3. With storage location rule MALA, which inputs determine the picking storage location?

Interview questions

1. Cold-chain materials are picked from the ambient storage location. How do you analyse storage location determination?

Answer it in your own words first, then compare.

2. Which configuration elements determine how Post Goods Issue (PGI) updates inventory and financial accounts, and what must be checked if PGI fails with a stock or account error?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics