Oracle Cloud SKU Decision Guide
Healthcare · Higher education · Manufacturing

Oracle Cloud SCM SKU Decision Guide

Answer a series of questions to hone in on your SKU requirements.

Based on Oracle Fusion Service Descriptions effective September 29, 2026. SKU estimates indicate service scope, not prices or license quantities. Always consult your system implementer and Oracle sales team for final decisions.

The industry may provide clues, but is not a licensing trigger. The same service may support all three industries. Select what Oracle will actually do and who will do it.
1

One consolidated SKU chart

Named-user SKUs are the default below. Employee metrics and Suite bundles are alternative purchasing options. The matrix estimates individual services.

Service / SKU Include when Exclude or review when SD page
Included in B91082: Purchasing, Procurement Contracts, Sourcing, Supplier Portal, Supplier Qualification Management and transactional BI. Supplier Portal for procurement is distinct from advanced product-data supplier collaboration in Product Management.
What are Suite and employee alternatives?

Suite is a broad subscription bundle. B108674 (Suite Professional) combines professional ERP/SCM capabilities, including Product Management and Advanced Inventory, for its licensed users. B108675 (Suite Employee) covers employee self-service capabilities. These are alternatives to purchasing the covered services individually; compare user populations, scope and Oracle’s commercial terms. They are not extra functionality added by changing an assessment mode.

Compare these with the corresponding named-user services using Oracle's metric definitions and the order: ERP B91084; Procurement B91086; Supply Chain Execution B91064; Product Management B91063; Advanced Inventory B111757; WMS Enterprise B91088; SCM Analytics B95478. Do not treat an employee metric as a count of only people who log in. Self Service Procurement is separately listed as B91083; Suite Employee B108675 is another route to that capability.

2

Question-based SKU decision matrix

Answer the questions for the capabilities being implemented in Oracle. Answer business requirements, regardless of the system used today. Estimates assume the selected capabilities are in scope for the Oracle implementation. Selecting an industry fills in editable starting assumptions. Changing context replaces your answers; industry itself does not determine licensing. Uncertain requirements remain visible as reviews.

“Include” is a functional scope estimate. “Review” identifies an unresolved requirement, product choice or entitlement boundary. “Covered” applies only to the licensed user population. No quantity, price or legal compliance conclusion is calculated.

3

Sources

4

About the Author

Michael Gibby headshot

Michael Gibby is a Director at Huron Consulting Group specializing in Oracle Fusion Supply Chain and Procure-to-Pay transformation across healthcare, higher education, and commercial industries. He helps organizations move beyond implementation and quarterly regression testing to build practical operating models for continuous adoption, process improvement, and measurable business value.

With experience spanning Oracle E-Business Suite, Oracle Fusion Cloud, international manufacturing, healthcare supply chain, and P2P operations, Michael brings a rare blend of functional depth, technical fluency, and business process design. His work focuses on Redwood readiness, supply chain modernization, AI-enabled support models, testing strategy, reporting, integrations, and adoption frameworks that help organizations turn Oracle’s quarterly innovation cycle into a repeatable business discipline.

Outside of work, Michael is a technologist and technical cave diver who has developed mobile applications for rebreather equipment validation, task management, and Oracle Cloud inventory counting. He is also raising two future Oracle Cloud consultants and occasionally finds time to explore underwater caves in North Florida.

Areas of focus

  • Oracle Fusion Supply Chain and Procure-to-Pay advisor
  • Redwood readiness and continuous adoption
  • Healthcare, procurement, inventory, and operations
  • Speaker and author on Oracle Cloud modernization

The item-data decision

Manufacturing is included in Supply Chain Execution (B91057). The bundle includes Inventory, Manufacturing and Maintenance. A basic bill of material/item structure alone does not establish a production-execution requirement; tracked assembly work orders and component consumption point to the included Manufacturing capability.

Inventory needs an item master. That does not automatically mean a separate Product Management subscription. Oracle grants basic item-management capabilities with other ERP/SCM services, subject to explicit restrictions.

Requirement Basic item management Product Management decision
Standard item attributes; item DFFs; organization assignments, revisions and attachments Included, within basic-object restrictions. These alone do not trigger B91056.
Cross-references, related items and trading-partner item relationships Listed as basic item-master objects. A basic trading-partner relationship alone is not the advanced-product trigger.
GTIN relationships and spoke-system item references Explicitly excluded from basic Manage Item Relationships. Include Product Management when using these native relationships.
Item EFFs and delivered healthcare attribute groups Item EFFs are excluded, including predefined healthcare EFFs. Include Product Management. A delivered attribute group remains an EFF.
Item class hierarchy, item rules, new item requests and change workflows Only the root item class and basic management are available. Include Product Management for the advanced requirement.
Functional catalogs/categories and basic FBDI, REST/SOAP, OTBI Supported for basic objects. Additional financial/tax localization catalogs are allowed under Oracle's stated exception. Advanced catalog security, sharing, rule assignments or product publication changes the decision.

Healthcare attributes are EFFs

Oracle's predefined healthcare product-data attributes use extensible flexfields and are associated with item classes. They support GUDID/device data and healthcare integrations. The licensing conclusion follows from the general restriction on item EFFs; the healthcare attribute documentation does not itself provide a separate license grant. The 25D update adds fields such as Device Class and No. Of Usages and uses healthcare EFF privileges. Its Oracle Health synchronization/publication capabilities introduce additional product-data requirements; “no setup required” is not a license exemption.

Healthcare attribute documentation · 25D healthcare additions

Trading partner ≠ GTIN ≠ supplier association

Oracle explicitly lists trading-partner item relationships in basic item management, while separately excluding GTIN relationships, spoke references and item supplier associations. Select the exact native object the design uses.

A scanned barcode or a value stored as a permitted cross-reference is not, by itself, proof of entitlement to Oracle's native GTIN relationships, packaging hierarchy or publication features.

Basic item structures are listed as supported; pack structures are excluded. Basic item creation is different from governed New Item Request workflows. Engineering PLM requirements may also trigger Product Management, independently of Inventory.

Research conclusion: Oracle explicitly identifies the delivered healthcare attributes as predefined item EFFs, and explicitly excludes item EFFs from basic item management. Applying those two statements supports Product Management coverage for this feature. This is an inference from the published rules, rather than a separate healthcare-specific licensing sentence; no healthcare exemption was located. Existing Product Management, applicable Suite or legacy Product Hub/Product Development entitlement may avoid an incremental B91056 purchase. Operational attributes and permitted DFFs alone do not trigger this requirement.

Oracle Licensed Features — restrictions and equivalent legacy rights

What base Inventory can replenish

Supply Chain Execution includes Inventory Management. Min-max and PAR are Inventory replenishment methods. They do not inherently require Supply Planning, Demand Management, Advanced Inventory or WMS.

Min-max: replenish toward a maximum

Set item minimum and maximum levels at an inventory organization or subinventory. The process evaluates availability, relevant supply/demand and order modifiers; when availability falls below the minimum it calculates replenishment toward the maximum.

Example: minimum 20, maximum 80, calculated available quantity 15 → suggested replenishment 65 before order modifiers.

PAR: replenish a location from counts

Define a PAR location, items, target levels and replenishment count types. Enter counts or requested quantities; Inventory evaluates the count, existing requests and configured source to generate replenishment.

Sources can include a supplier or internal stock. PAR can support quantity-tracked or expense-style locations according to the design. Ordinary mobile counts do not equal advanced assigned PAR tasks.

Configured source Typical min-max output Business example
Supplier Purchase requisition Order clinical supplies, campus laboratory materials or manufacturing components.
Another subinventory Movement request Replenish a local stockroom or production supply location.
Same inventory organization, organization sourcing Intraorganization transfer order Move supplies between locations using a transfer-order flow.
Different inventory organization Interorganization transfer order Replenish another hospital, campus store or plant from central inventory.
Calculation is not the entire procure-to-pay process. Inventory can calculate replenishment and initiate requests; purchasing, requisition approval, production and accounting still rely on the applicable downstream services. The configured source determines the route—this is not an automatic supplier-versus-warehouse optimizer.

Advanced planning becomes relevant for forecast-driven, time-phased or constrained supply/demand planning. Advanced Inventory and WMS address execution requirements. The replenishment method alone does not settle those separate decisions.

Contract authoring and redlining

Do users author, redline or negotiate contracts, or only search contracts and manage deliverables? These are different user populations and entitlements.

Limited contract access

B91083 includes Enterprise Contracts Essential User access: contract viewing and deliverables management for all contract types. Standalone B86733 provides contract search, viewing details/documents and deliverables management. Neither is full authoring.

Contract authors and legal teams

B91082 explicitly includes Procurement Contracts. Oracle's functional documentation describes procurement-contract authoring, so it should not be labeled deliverables-only. However, the service description alone does not fully resolve the boundary for standalone legal contracting and every redlining workflow.

B86732 is the separate full Enterprise Contracts service. B93429 Order Management also includes Enterprise Contracts, and Suite Professional provides broad contract coverage. Grant agreement authoring and sell-side agreements belong in this broader scope assessment; grant accounting alone does not imply contract authoring. Review the contract types, user population and existing entitlement before adding another SKU.

Answer for your business process. The estimate assumes you are evaluating this capability for the Oracle implementation; if it remains in an external legal or CLM system, that requirement does not establish an Oracle contract-authoring license need.

Matrix treatment: authoring plus broader legal/non-procurement contract types includes Enterprise Contracts (B86732), unless equivalent coverage applies. Authoring with unresolved or procurement-only scope remains an entitlement review. Procurement (B91082) is not treated as covering every enterprise legal workflow.

Healthcare item attributes: what do you need to track?

These are product-master characteristics, not patient records or ordinary stock balances. Typical needs include finding latex-free or sterile supplies, identifying implants, recording MRI safety, linking medical devices to UDI/GUDID data, and maintaining charge and procedure codes.

Licensing decision: Oracle implements the following delivered healthcare attribute groups as item extensible flexfields (EFFs). Item EFFs are excluded from basic item management, so the estimate includes Product Management or equivalent coverage when this native model is required. Needing a clinical data value alone is not a license trigger: if standard attributes or permitted DFFs meet the design, reassess this answer and the separate GTIN, publication and governance requirements. A DFF substitute should be validated against integration, reporting and governance needs.

Full delivered healthcare field list

All 64 attributes listed in Oracle’s 26B Item Healthcare Attributes reference, grouped below. Fields include Device Class and No. Of Usages introduced in the 25D update.

Attribute group Fields
Device Status Combination Product; HCT/P Product; Kit
FDA Product Code; Product Code Name; Product Physical State; Device Class; Submission Type
GUDID Miscellaneous Attributes Contains Natural Rubber Latex; Not Made With Natural Rubber Latex; Prescription Use; Over-the-Counter; What MRI Safety Information Does Labeling Contain?; Requires Sterilization?; Public Device Record Key; Public Version Number; Public Version Date; Public Version Status
GUDID Package Device Identifiers Package DI Number; Package Discontinue Date; Package Status; Package Type; Quantity Per Package; Contains DI Package
Healthcare Pricing Attributes Chargeable; Charge Code; Charge Per Unit; Base Price; Markup; Revenue Code
Healthcare GUDID Primary UDI Enabled; Issuing Agency; Primary DI Number; Device Count; Unit of Use DI Number; Labeler D-U-N-S Number; Company Name; Company Address; Brand Name; Device Version; Catalog Number; Device Description; Device Exempt From Premarket Submission; FDA Listing Number; For Single-use
Healthcare Standardized Codes UNSPSC; UNSPSC Segment; UNSPSC Family; UNSPSC Class; UNSPSC Commodity; HCPCS; HCPCS Description; HCPCS Status
Healthcare Additional Attributes Implantable; Implant Type; Color; Latex Product; Sterility; Breakable Pack?; Clinical; Surgical Instrument; Reprocessed; No. Of Usages
GUDID Sterilization Method Sterilization Methods

Oracle: complete field reference · Healthcare attributes are predefined EFFs · Item licensing rules

Extra fields, attribute groups and item classes

Concept Meaning / example Licensing decision for items
DFF — descriptive flexfield Additional configurable fields using the object’s available descriptive-flexfield segments. For example, add a local supply category or campus reference code. Contexts can show different fields for different uses; DFF does not mean every item must have identical fields. Item DFFs are listed within basic item management. A few extra fields alone do not require Product Management.
EFF — extensible flexfield Expandable attribute groups and contexts stored in extension tables; they can support rich item-family specifications and, where configured, multiple rows of attributes. For example, clinical device properties or engineering specifications grouped by product family. Delivered healthcare fields are EFFs too. Item EFFs are excluded from basic item management. Include Product Management or equivalent entitlement when this model is needed.
Custom item classes A hierarchy beyond the predefined root/default class, such as Supplies → Clinical → Implants or Components → Motors. Classes can inherit attribute groups and support class-specific rules, lifecycle/governance and security. This is different from an inventory organization or a procurement category/catalog assignment. Only the root class is available under basic item management. A custom item-class hierarchy requires Product Management or equivalent entitlement.
Answer Yes when the design needs EFF attribute groups or a class hierarchy. Answer No if standard attributes, permitted DFFs and basic catalogs/categories satisfy the requirement. More descriptive data does not automatically establish an EFF requirement.

Oracle: flexfield overview · Oracle: item licensing rules

LPNs, work assignment and pick waves

What is an LPN?

A license plate number (LPN) identifies a particular container of inventory, such as a pallet, tote, carton or bin. Oracle records its contents against that identifier. An item barcode identifies a product; an LPN identifies this specific packed group of goods.

Why it helps: scan a container to transact its contents together rather than entering each item or serial separately, where the transaction supports this. For example, move a pallet of serialized equipment between locators by scanning the pallet LPN. Container visibility supports finding packed stock and controlling transfers, receiving, picking, packing, shipping and counts. LPNs complement item, lot and serial records.

Native LPN-enabled Inventory transactions point to Advanced Inventory (B111756) with base Supply Chain Execution (B91057). Merely scanning an item barcode is not the same requirement.

Select work versus manage assigned tasks

Base Inventory Advanced Inventory
Authorized users select and complete available transaction work through the relevant picking, counting, PAR or delivery pages. For example, select a pick slip to confirm or count records to enter. Completing this work does not by itself require managed task assignment. A dedicated task framework groups work and assigns or reassigns it to specific workers. Managers track workload, priorities and progress; operators see their assigned work. It covers picks, cycle/physical counts, PAR counts and receipt deliveries.

Important distinction: Advanced Inventory also lets operators self-assign unassigned tasks. The additional capability is the managed task framework, not a rule that all work must be manager-assigned. Base transaction work should not be confused with that advanced Inventory Tasks queue.

Basic Inventory already generates pick waves

A pick wave releases a selected set of demand for picking. Base Inventory can use release rules, demand/fulfillment/processing criteria, immediate release or a release schedule, and basic pick-slip grouping. Creating a wave alone does not require Advanced Inventory or WMS.

Advanced Inventory adds execution capabilities such as LPNs, managed tasks, put-away suggestions and cross-docking. WMS should be assessed when more sophisticated warehouse orchestration is needed beyond the base release/grouping process; it is not triggered merely by the word “wave.”

Oracle: LPN transactions · Oracle: assignment and self-assignment · Oracle: basic pick-wave creation · Advanced Inventory capabilities