← Back to list

IBM Maximo Receiving Application: In-Depth Explanation

Core Purpose & Business Context

Sayed Saeed · 2026-05-28 16:06 · 0 claps · 3.5 min read
#maximo #supply-chain
Open on Medium ↗
Wiki topics: MAC · Macroeconomics 💭 · Philosophy of Spirit

IBM Maximo Receiving Application: In-Depth Explanation

Core Purpose & Business Context

The Receiving application serves as the operational bridge between procurement and inventory/asset management. Its primary functions:

Function Business Impact Record delivery of materials/services against POs Ensures accurate inventory valuation and financial reconciliation Manage inspection & serialization workflows Maintains quality control and asset traceability Handle returns, voids, and partial receipts Provides flexibility for real-world supply chain exceptions Track costs for non-inventory items Enables complete spend visibility even for direct-issue items

💡 Enterprise Scenario: In a multi-site organization, a centralized purchasing team can create POs, while each site uses Receiving to manage their local deliveries — supporting decentralized operations with centralized control.

End-to-End Purchasing Process Flow

graph LR
    A[Purchase Requisition] --> B[Purchase Order]
    B --> C[Receiving Application]
    C --> D[Inspection/Serialization]
    D --> E[Inventory/Asset Update]
    E --> F[Invoice Matching]

Step-by-Step with Your Example (PR 98074):

  1. Requisition Creation: Request for programmers, PCs, software, furniture
  2. PO Splitting: One PO per vendor (98105–98108) using Copy PR Line Items to PO
  3. Receiving:
  • Services → Service Receipts tab → Select Ordered Services
  • Materials → Material Receipts tab → Select Ordered Items

4. Invoice Recording: Use Copy PO Lines in Invoices application to match receipts to bills

Critical Concepts Explained

1. Holding Locations & Inspection Workflow

Every site has one holding location — a temporary staging area for items requiring validation.

Status Meaning Next Action WINSP (Waiting for Inspection) Item received but not yet inspected Perform inspection → change to WASSET or COMP WASSET (Waiting for Serialization) Rotating item passed inspection, awaiting asset number Assign asset # → status becomes COMP COMP (Complete) Item fully processed Auto-transfer to storeroom/direct issue location

⚠️ Key Rule: Items cannot enter inventory or be issued to work orders until status = COMP.

2. Receipt Types & Use Cases

Receipt Type Tracked in Inventory? Example PO Required? Inventory Items ✅ Yes Bearings, cables, spare parts ✅ Yes Non-Inventory Materials ❌ No Catered lunch, office furniture ✅ Yes (for cost tracking) Services ❌ No Contractor hours, equipment repair ✅ Yes Rotating Assets ✅ Yes (as assets) Pumps, motors, tools ✅ Yes

3. Receipt Tolerance & Over/Under Delivery

  • PO line items can define tolerance thresholds (quantity or amount)
  • If delivery exceeds tolerance:
  • Option 1: Receive only up to tolerance limit
  • Option 2: Receive full amount (requires PO modification first)
  • Prevents unintended over-receipts that could impact budgeting or inventory accuracy

Detailed Workflows

Receiving Materials Requiring Inspection

1. Select PO → Material Receipts tab → Select Ordered Items
2. Items appear with WINSP status
3. Save Receipt (creates holding location transaction)
4. Perform physical inspection
5. Update status:
   • Rotating item? → WASSET → assign asset # → COMP
   • Non-rotating? → COMP directly
6. System auto-creates transfer to final location
7. Optional: Enter Quantity Rejected + Reject Code for returns

Receiving Rotating Assets (with Serialization)

1. Receive item → status becomes WASSET (if no inspection) or WINSP→WASSET
2. Click "Receive Rotating Items" action
3. For each line:
   • Manually enter Asset # OR click "Autonumber"
   • Optionally add Serial # (appears in Assets application)
   • Optionally apply Item Assembly Structure (IAS) for complex assets
4. Save → Asset record created in Assets application
5. Status changes to COMP → transfer transaction generated

🔧 Item Assembly Structures (IAS): Allow hierarchical asset creation (e.g., a pump assembly with motor, seal, controller). You can autonumber entire hierarchies or assign numbers level-by-level.

Handling Partial Shipments & Damaged Goods

  • Partial receipt: Modify Quantity field before saving receipt
  • Damaged items received:
  1. Receive full quantity
  2. Immediately use Select Items for Return to create negative receipt for damaged portion
  3. Add Reject Code for reporting/analysis

Rules & Restrictions: Voiding vs. Returning

Action When to Use Key Limitations Void Receipt Transaction entered in error (e.g., wrong PO line) • Cannot void if already invoiced<br>• Cannot void serialized assets (COMP status)<br>• Cannot void partially/fully returned items<br>• Voided receipts excluded from credit invoice matching Return Item Valid receipt, but item defective/unused • Asset must be in original receiving storeroom<br>• Inventory cost must match original receipt cost<br>• Direct-issue items cannot be returned if already moved/used

🔄 Critical Difference: Voids reverse the transaction entirely; returns create a new negative transaction that can be matched to vendor credit memos.

Related Records & Traceability

The View Related Records icon provides end-to-end visibility:

Receipt Line → Click Icon → View:
├─ Purchase Order (source)
├─ Contract (if applicable)
├─ Request for Quotation (procurement history)
├─ Invoice (financial reconciliation)
└─ Inventory/Asset Transactions (downstream impact)

This supports audit trails, dispute resolution, and root-cause analysis.

Common Pitfalls to Highlight:

  1. Forgetting to change inspection status → items stuck in holding location
  2. Attempting to void invoiced receipts → system error; must use return + credit invoice instead
  3. Not assigning asset numbers to rotating items → assets won’t appear in Assets application
  4. Over-receiving beyond tolerance without PO modification → receipt blocked

Reporting & Analytics Opportunities

The Receiving application feeds critical business metrics:

  • On-time delivery performance (PO receipt date vs. promised date)
  • Quality metrics (reject rates by vendor/item via Reject Codes)
  • Inspection cycle time (WINSP → COMP duration)
  • Receipt-to-invoice matching accuracy

These can be extracted via Maximo’s reporting tools or integrated with BI platforms.

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

Contact me on LinkedIn:

https://www.linkedin.com/in/sayed-saeed-ab3286214/

#maximo #Inventory#ItemSet

Full course exists here on Udemy: https://www.udemy.com/course/mastering-ibm-maximo-comprehensive-guide-for-professional/?referralCode=C768555C4F3E0DBB7664


메타데이터
post_id
c2260b396cfb
slug
ibm-maximo-receiving-application-in-depth-explanation-c2260b396cfb
url
https://medium.com/@e.sayedsaeed5/ibm-maximo-receiving-application-in-depth-explanation-c2260b396cfb
canonical_url
https://medium.com/@e.sayedsaeed5/ibm-maximo-receiving-application-in-depth-explanation-c2260b396cfb
author_url
https://medium.com/@e.sayedsaeed5
status
ok
fetched_at
2026-07-11 16:53:25