+

1. What is the difference between standard PO vs Planned PO vs Blanket PO vs Contract PO

2. What is the difference between purchase requisition vs internal requisition
3. What is the difference between Standard RFQ vs Catalog RFQ vs Bid RFQ
4. difference between position hierarchy and supervisor hierarchy
5. Catalog Items vs Non-Catalog Items
6. difference between internal and external Organization in oracle apps
7. difference between Business Group vs Legal Entity vs Operating Unit vs Inventory Organization vs HR Organization in
oracle apps
8. What is MOAC architecture in oracle apps
9. difference between MO: Operating Unit vs MO: Security Profile vs HR Security Profile in oracle apps with example
10. What is difference between open vs hold vs cancel vs freeze vs unfreeze vs close for receive and close for invoice and
open for receive and open for invoice PO status .
11. difference between requisition and Purchase order
12. difference between available to reserve and available to transact
13. difference between MTL_ONHAND_QUANTITIES vs MTL_RESERVATIONS vs MTL_DEMAND vs MTL_SUPPLY
14. What is difference between Cost Manager vs Material Transaction vs Move Transaction vs Lot Move Transaction
15. what is allow express transaction
16. what is allow cascade transaction
17. what is functionality of WMS in oracle apps
18. comparison between Oracle Inventory with WMS vs. without WMS
19. what is functionality of ASCP
20. what is functionality of MRP in oracle apps
21. what is lead time
22. Difference between ASCP and MRP in oracle apps
23. what is ATP
24. Would you like a demo scenario or setup steps for ATP rules in Oracle Inventory or Order Management?
25. what is Global purchase agreement with example GPA and Blanket Purchase Agreement

1.
 1. What is the difference between standard PO vs Planned PO vs Blanket PO vs Contract PO
The key differences between Standard PO, Planned PO, Blanket PO, and Contract PO lie in their purpose, timing, and level of
detail in terms of quantity, delivery schedules, and pricing. Here's a breakdown of each:

1. Standard Purchase Order (Standard PO)

 Purpose: For one-time purchases with well-defined details.
 Used When: You know exactly what you need, when you need it, how much, and at what price.
 Key Characteristics:
o Specifies item, quantity, price, delivery date, and location.
o Commitment is made upfront.
 Example: Ordering 100 laptops to be delivered in one shipment next week.

2. Planned Purchase Order (Planned PO)

 Purpose: Used when you know the items and quantities you’ll need in the future, but not the exact delivery schedule.
 Used When: You can forecast demand but deliveries will be scheduled later.
 Key Characteristics:
o Contains expected items, quantities, and pricing.
o Delivery is scheduled through Releases against the PO (called Release Orders).
 Example: Planning to buy 1,000 units over 6 months, but you’ll issue releases monthly as needed.

3. Blanket Purchase Order (Blanket PO)

 Purpose: Used for repetitive purchases of services or items over a period, usually from the same supplier.
 Used When: You know you'll be purchasing a specific category of goods/services, but not exact quantities or delivery
dates.
 Key Characteristics:
o Specifies terms and conditions, pricing (sometimes), and time period.
o Individual purchases are made through Releases (similar to Planned PO).
o Often used for utilities, maintenance, or recurring services.
 Example: A blanket PO with a cleaning service vendor for office cleaning for one year.

4. Contract Purchase Order (Contract PO)

 Purpose: Used to establish terms and conditions for future POs; no actual items or quantities are specified.
 Used When: You want to negotiate and lock in commercial terms but will create Standard POs later based on the
contract.
 Key Characteristics:
o Contains terms like pricing agreements, discounts, and payment terms.
o No commitment to purchase until actual POs are issued.
 Example: Entering into a contract with a supplier for office supplies over a year, with actual orders to be placed as
needed.

Summary Table:
Feature Standard PO Planned PO Blanket PO Contract PO
Item Details Known Yes Yes Possibly (broad) No
Delivery Schedule Known Forecasted, by release Unknown, by release Not specified
Quantity Specified Yes Yes (planned) Usually not No
Pricing Specified Yes Yes Often Yes
Used For One-time purchases Future known purchases Recurring services/items Strategic agreements
2. What is the difference between standard PO vs Planned PO vs Blanket PO vs Contract PO with example

📝 1. Standard Purchase Order (Standard PO)

🔹 Definition:
A Standard PO is used for one-time, specific purchases where all the details are known upfront: item, quantity, price, delivery
location, and date.
✅ Best When:
You need to buy something once and all the information is available.
📦 Example:
Your IT department needs 20 monitors urgently. You raise a Standard PO like:
 Item: Dell 24" Monitor
  Quantity: 20
 Unit Price: $150
 Delivery Date: May 25
 Location: Main Office

📝 2. Planned Purchase Order (Planned PO)

🔹 Definition:
A Planned PO is used for forecasted future purchases. You know the items, pricing, and estimated delivery schedule but will
confirm delivery through releases.
✅ Best When:
You plan to buy in bulk over time, but want to issue smaller orders as needed.
📦 Example:
You expect to buy 1,000 printer cartridges over the year. You create a Planned PO like:
 Item: HP 410X Cartridge
 Total Quantity: 1,000
 Unit Price: $80
 Expected Delivery: Monthly for 12 months
Each month, you issue a Release Order for the quantity needed (e.g., 80 cartridges in June).

📝 3. Blanket Purchase Order (Blanket PO)

🔹 Definition:
A Blanket PO is for recurring purchases of services or items over a time period, but you don’t know exact quantities or timing.
Usually set for a spending limit.
✅ Best When:
You regularly buy the same goods or services, but not on a fixed schedule.
📦 Example:
You hire a vendor to provide office cleaning services as needed. You issue a Blanket PO like:
 Vendor: XYZ Cleaning Services
 Service: Office cleaning
 Period: Jan–Dec
 Rate: $500 per visit
 Total Limit: $10,000
You release individual service orders as the service is performed.

📝 4. Contract Purchase Order (Contract PO)

🔹 Definition:
A Contract PO sets up legal terms and conditions for future purchasing, but no goods or services are ordered yet. You’ll later
issue Standard POs referencing this contract.
✅ Best When:
You want to lock in pricing or terms before making purchases.
📦 Example:
You sign an annual agreement with a hardware supplier for discounted laptops:
 Vendor: ABC Technologies
 Contract Period: Jan–Dec
 Laptop Price: $1,200 each
 Discount: 15% off retail
 Minimum Commitment: 100 units
You then issue Standard POs as needed during the year, referring to this Contract PO.

📊 Summary Comparison Table

Feature Standard PO Planned PO Blanket PO Contract PO
Frequency One-time Repeated (with forecast) Repeated (unscheduled) Not for direct purchasing
Release Required? ❌ No ✅ Yes (scheduled) ✅ Yes (as needed) ✅ Yes (via Standard PO)
Pricing Known ✅ Yes ✅ Yes ✅ Often ✅ Yes
Quantity Known ✅ Yes ✅ Estimated ❌ No ❌ No
Delivery Schedule ✅ Yes ✅ Forecasted ❌ No ❌ No
Example Use Buy 20 monitors Buy 1,000 cartridges over time Office cleaning services Laptop supply agreement

3. What is the difference between purchase requisition vs internal requisition

The difference between a Purchase Requisition and an Internal Requisition lies in what is being requested and from where it is
being sourced.
Here's a clear breakdown:
📊 Purchase Requisition vs Internal Requisition
Feature Purchase Requisition Internal Requisition
Request to buy goods/services from external Request to obtain goods/services from internal departments
Purpose
vendors or stores
Source of Goods External suppliers (outside the organization) Internal inventory or departments
Item is not available in stock or needs to be
Used When Item is already available internally
bought
Resulting
Leads to a Purchase Order (PO) Leads to an Internal Transfer/Movement Request
Document
Often more complex due to procurement
Approval Flow Usually simpler within internal departments
policies
Example Requesting laptops from an IT supplier Requesting stationery from internal office supplies stock
🔍 Simple Definitions:
 Purchase Requisition:
A formal request to procure items from external suppliers.
✅ Example: "We need to buy 10 printers from HP."
 Internal Requisition:
A formal request to transfer items from within the organization.
✅ Example: "We need 5 chairs from the company warehouse."

4. What is the difference between purchase requisition vs internal requisition

📌 1. Purchase Requisition
🔹 Definition:
A Purchase Requisition is a request to buy goods or services from an external supplier.
✅ Used When:
The item or service is not available internally, and must be purchased from outside the organization.
📦 Example:
The marketing team needs a new projector that is not in stock internally.
They raise a Purchase Requisition to buy the projector from an external vendor like Amazon or Dell.
"Request to purchase 1 projector from Dell at $800."

📌 2. Internal Requisition
🔹 Definition:
An Internal Requisition is a request to transfer goods/services from one internal department or store to another within the
organization.
✅ Used When:aaa
The item is already available within the company, such as in a warehouse or another department.
📦 Example:
The HR team needs 10 chairs. These are available in the company warehouse.
They raise an Internal Requisition to transfer the chairs from the warehouse.
"Request to transfer 10 chairs from central warehouse to HR department."

🧾 Summary Table:
Feature Purchase Requisition Internal Requisition
Source External Supplier Internal Store/Warehouse
Used For Buying items not available internally Requesting existing stock internally
Resulting Action Purchase Order to external vendor Internal Stock Transfer or Issue
Example Buying a laptop from HP Requesting a laptop from internal IT stock

🧠 Tip:
 Think of Purchase Requisition as "Buy from outside"
 And Internal Requisition as "Get from inside"
5. What is the difference between Standard RFQ vs Catalog RFQ vs Bid RFQ

📦 What is an RFQ?
RFQ (Request for Quotation) is a formal request sent to suppliers asking for price quotes for specific goods or
services.
📊 Difference Between Standard RFQ, Catalog RFQ, and Bid RFQ

Type of RFQ Standard RFQ Catalog RFQ Bid RFQ

Request for quote for specific items or Request quote for items listed in an Competitive request to multiple
Definition
services not in a catalog internal/external catalog suppliers to get best quote
 One-time or specific purchase Predefined/catalog items needed in When price competition is the key
Use Case
requests bulk or regularly factor for selection
Supplier Typically sent to suppliers already Sent to multiple vendors to get
Sent to selected/specific vendors
Count associated with the catalog competitive pricing
Control Buyer-defined items, specs, and Buyer selects items from a predefined Suppliers submit bids to win the
Level quantity catalog order
Limited or no negotiation (fixed Often involves competitive
Negotiation May or may not involve negotiation
catalog pricing) bidding and negotiation

📌 Examples
✅ Standard RFQ Example:
Your company needs 50 custom-made steel racks. These are not in any existing catalog.
You issue a Standard RFQ to 3 steel fabrication vendors, asking for quotes based on your design specs.

✅ Catalog RFQ Example:

Your procurement system includes an approved vendor catalog for office supplies.
You raise a Catalog RFQ to request a quote for 200 pens and 100 notebooks from the approved catalog items.

✅ Bid RFQ Example:

You need 1,000 laptops for a government project, and price is the primary selection criteria.
You issue a Bid RFQ to 10 laptop suppliers and award the contract to the lowest qualified bidder.

🧠 Summary in One Line:

 Standard RFQ = Custom, specific purchase from selected vendors
 Catalog RFQ = Pre-approved items from catalog
 Bid RFQ = Competitive bidding to get the best price

6. What is the difference between Standard RFQ vs Catalog RFQ vs Bid RFQ

📌 1. Standard RFQ (Request for Quotation)

🔹 Definition:
A Standard RFQ is issued when you want to procure specific goods or services that are not listed in a predefined catalog.
✅ Use Case:
For custom or one-time purchases, where specifications must be shared with suppliers.
📦 Example:
A company needs custom-built furniture for a new office. It sends a Standard RFQ to 3 vendors with detailed dimensions and
materials.
"Requesting a quote for 10 custom-made wooden desks based on attached design."

📌 2. Catalog RFQ
🔹 Definition:
A Catalog RFQ is used to request prices for items already listed in an internal or vendor-maintained product catalog.
✅ Use Case:
For routine or standard purchases, using pre-approved catalog items.
📦 Example:
The procurement team needs office supplies like pens and paper, available in a vendor catalog. They create a Catalog RFQ
from the system.
"Requesting quote for 500 gel pens and 200 A4 notebooks from Supplier Catalog."

📌 3. Bid RFQ
🔹 Definition:
A Bid RFQ is used when you want to invite multiple suppliers to compete by offering their best price or terms — usually for
large-scale or strategic procurements.
✅ Use Case:
When cost, quality, or delivery competitiveness is crucial — often in public sector or high-value projects.
📦 Example:
A government agency needs to buy 1,000 laptops and wants competitive pricing. They issue a Bid RFQ to 5 vendors and award
to the best offer.
"Inviting bids from qualified vendors for supply of 1,000 laptops — best price and warranty terms will win."

📊 Comparison Table
Feature Standard RFQ Catalog RFQ Bid RFQ
Item Source Custom items, not in catalog Items listed in catalog Open competition among vendors
Purpose Specific, ad-hoc purchases Routine, catalog-based purchases Competitive bidding for best deal
Supplier Selection Sent to selected known vendors Sent to catalog-approved vendors Sent to multiple vendors for bidding
Negotiation May involve negotiation Limited (fixed catalog pricing) High — based on best offer
Example Custom desks for office Stationery from catalog Laptops for government tender

🧠 Summary:
 Standard RFQ = For unique or non-catalog items
 Catalog RFQ = For known items from catalog
 Bid RFQ = For competitive bidding among vendors

7. difference between position hierarchy and supervisor hierarchy

📌 1. Position Hierarchy
🔹 Definition:
Position Hierarchy is based on job positions, not people. It defines the organizational structure using roles or titles, regardless
of who holds them.
✅ Key Features:
 Focuses on positions (roles) like “Manager,” “Team Lead,” etc.
 Used for approvals, reporting, and budget control.
 Static – does not change often.
📦 Example:
 CEO → VP → Manager → Analyst
 Even if a position is vacant, the structure remains.
"Marketing Manager" reports to "Marketing Director" — regardless of who is currently in those roles.

📌 2. Supervisor Hierarchy
🔹 Definition:
Supervisor Hierarchy is based on person-to-person reporting. It shows who actually reports to whom.
✅ Key Features:
 Based on employee reporting relationships
 Commonly used for leave approvals, workflow routing
 Dynamic – changes when people move, resign, or are reassigned.
📦 Example:
 Alice (Analyst) reports to Bob (Team Lead)
 Bob reports to Sarah (Manager)
Even if Bob becomes a Manager, the hierarchy updates based on real-time reporting.

📊 Comparison Table
Feature Position Hierarchy Supervisor Hierarchy
Based On Job positions (roles) Actual employee reporting
Structure Type Organizational structure Person-to-person relationship
Used For Budgeting, approval limits, structural planning Workflow routing, leave approvals
Changes With Re-orgs or structural updates Employee movement or reassignment
Vacant Position Handling Stays in the hierarchy Irrelevant – based on actual people
Example "HR Manager" → "HR Director" Raj reports to Neha (regardless of title)

🧠 Summary:
 Position Hierarchy = Role-based (Who should report to whom)
 Supervisor Hierarchy = People-based (Who actually reports to whom)

difference between position hierarchy and supervisor hierarchy

Here is a simple and clear explanation of the difference between Position Hierarchy and Supervisor Hierarchy:

📊 Position Hierarchy vs Supervisor Hierarchy

Feature Position Hierarchy Supervisor Hierarchy
Based On Job positions (titles/roles) Actual employees and reporting lines
Structure Type Role-to-role (organizational structure) Person-to-person (reporting relationships)
Used For Approvals, budgeting, organizational planning Workflow routing, leave approvals, daily reporting
Dynamic or Dynamic – changes when reporting relationships
Static – remains same even if position is vacant
Static change
Vacancy Impact Position still exists in structure No impact unless a person is assigned to the role
"Finance Manager" reports to "Finance Director" (by
Example Riya reports to Suresh (by person, regardless of title)
role)

🧠 Quick Summary
 Position Hierarchy = Based on roles/positions → “Manager” reports to “Director”
 Supervisor Hierarchy = Based on people → “John” reports to “Sarah”

✅ Real-world Example:
 If a "Sales Manager" position is vacant, it still appears in the Position Hierarchy.
 In Supervisor Hierarchy, only filled positions matter. If John is the new Sales Manager, his name appears under his
supervisor.

8. difference between catalog items and non-catalog items

Here’s a clear explanation of the difference between Catalog Items and Non-Catalog Items in procurement or ERP systems
(like Oracle, SAP, etc.), along with examples:

📊 Catalog Items vs Non-Catalog Items

Feature Catalog Items Non-Catalog Items

Items that are pre-approved and listed in a
Definition Items that are not listed in any standard catalog
catalog
Source From vendor catalogs or internal item lists Defined manually by the requester
Quick and easy – pre-filled details (price,
Ease of Ordering Slower – details must be manually entered
vendor)
Approval
Usually faster approval (standardized items) May need extra approval due to custom nature
Requirements
Custom-made furniture, unique tools, special
Examples Office stationery, laptops, software subscriptions
services
Use Case Frequent, repeat purchases One-time or special purchases

✅ Examples
📦 Catalog Item Example:
You need to buy 100 pens. These pens are already listed in the supplier catalog with price and details.
You select the item directly from the catalog – fast and simple.
Non-Catalog Item Example:
You need a custom-made wooden signboard for your office.
You manually enter the description, quantity, price, and supplier into the requisition form.

🧠 Quick Summary
 Catalog Items = Pre-listed, standardized, faster to order
 Non-Catalog Items = Custom or ad-hoc items, require manual entry

difference between internal and external Organization in oracle apps

In Oracle Apps (E-Business Suite), the terms Internal Organization and External Organization refer to how an
organization is classified in relation to your own enterprise or business group. These classifications are key in modules like
Inventory, Purchasing, Order Management, and HRMS.
🔹 Internal Organization:
 Definition: An organization that is part of your enterprise.
 Purpose: Used for managing internal operations like inventory, manufacturing, distribution, and HR.
 Examples:
o Inventory organizations (e.g., warehouses)
o Operating units (for transaction processing)
o HR organizations (departments, divisions)
 Used in:
o Inventory: For storing and shipping goods.
o Order Management: As shipping warehouses.
o Purchasing: As the buyer or receiver of goods.
o HRMS: For workforce management.
 Key Setup: Must be assigned to a Business Group, Legal Entity, and Operating Unit, depending on context.
🔹 External Organization:
 Definition: An entity outside your enterprise.
 Purpose: Used to represent customers, suppliers, or other business partners.
 Examples:
o Supplier organizations
o Customer accounts
o Third-party logistics providers (3PL)
 Used in:
o Purchasing: As suppliers/vendors.
o Order Management: As customers.
o TCA (Trading Community Architecture): To manage third-party data.
 Key Setup: Managed primarily through the Trading Community Architecture (TCA) as parties.

🔁 Quick Comparison:
Feature Internal Organization External Organization
Part of Enterprise? Yes No
Examples Warehouses, departments Customers, vendors
Key Use Areas Inventory, HRMS, Financials Purchasing, Order Management
Defined In HR, Inventory, Financials Trading Community Architecture
Involved in Transactions? Yes (shipping, receiving) Yes (buying, selling)
Would you like to see how to set them up in Oracle Apps or how they impact transactions like Purchase Orders or Sales
Orders?

difference between Business Group vs Legal Entity vs Operating Unit vs Inventory Organization vs HR Organization in oracle
apps

In Oracle E-Business Suite (Oracle Apps), understanding the differences between Business Group, Legal Entity, Operating
Unit, Inventory Organization, and HR Organization is essential for setting up the Multi-Org (Multi-Organization
Architecture). These entities define the enterprise structure and how transactions, data access, and processes are managed.

🔹 1. Business Group
 Definition: The highest-level HR organization that represents the enterprise from a human resources perspective.
 Purpose: Manages employee data, jobs, positions, and payroll across the enterprise.
 Scope: HR and Payroll only.
 Independent From: Legal and accounting structure.
 Example: A multinational company may have one business group per country.
🧠 Think of this as the HR boundary.

🔹 2. Legal Entity
 Definition: An entity that is recognized by the government as a company that can enter into contracts, pay taxes, and
be legally liable.
 Purpose: Used for statutory and tax reporting; owns financial transactions.
 Scope: Financial and legal.
 Associated With: Ledgers and Operating Units.
 Example: "ABC Inc. USA" and "ABC Ltd. UK" are separate legal entities.
🧠 Think of this as the tax and regulatory boundary.

🔹 3. Operating Unit (OU)

 Definition: A subdivision of a Legal Entity where business transactions like Sales Orders, Purchase Orders, Invoices,
etc., are processed.
 Purpose: Manages day-to-day business operations.
 Scope: Purchasing, Order Management, Payables, Receivables.
 Tied To: A specific Legal Entity.
 Access Controlled By: MOAC (Multi-Org Access Control).
🧠 Think of this as the transaction-processing unit.

🔹 4. Inventory Organization
 Definition: A facility where inventory is stored and managed; represents a warehouse or distribution center.
 Purpose: Controls inventory, costing, manufacturing, and material transactions.
 Scope: Inventory and Supply Chain.
 Child Of: Operating Unit.
  Can Be: Shipping or Receiving organizations.
🧠 Think of this as the physical location for inventory.

🔹 5. HR Organization
 Definition: Any organization used within the HR module (like departments, business groups, legal employers).
 Purpose: Structures the organization for HR processes (reporting, payroll, recruitment).
 Types: Departments, Divisions, Legal Employers.
 Used In: HRMS, Payroll, OTL (Time and Labor).
🧠 Think of this as the organizational chart within HR.

🔁 Summary Table
Component Scope Used In Purpose
Business Group Enterprise-wide HR HRMS, Payroll Manages employee data across enterprise
Legal Entity Legal/Statutory Financials, Legal Reporting Owns assets, incurs liabilities, pays taxes
Operating Unit Transactional OM, PO, AR, AP Handles business transactions
Inventory Org Physical/Warehouse Inventory, MFG, WIP Manages inventory and supply chain processes
HR Organization Organizational HR Structure HRMS, OTL Represents departments, divisions, employers

🧱 Hierarchy (Conceptual)
Business Group
│
├── Legal Entity
│ └── Operating Unit
│ └── Inventory Organizations
│
└── HR Organizations (Departments, Divisions)

difference between Business Group vs Legal Entity vs Operating Unit vs Inventory Organization vs HR Organization in oracle
apps with example

Here's a clear comparison chart explaining the difference between Business Group, Legal Entity, Operating Unit,
Inventory Organization, and HR Organization in Oracle E-Business Suite (Oracle Apps) with examples:

🧾 Oracle Apps Organization Structure – Comparison Chart

Hindi
Term Meaning Usage Example
Meaning
व्यापार
The highest-level HR organization HRMS module – manages
Business समूह / Global Business Group (e.g.,
structure; represents a business in people, jobs, grades,
Group मुख्य Infosys Global HR)
its entirety positions
संगठन
Financials – used for Infosys Technologies Ltd
A company registered under the कानूनी
Legal Entity statutory compliance, tax, (India legal entity), Infosys
law; can own assets and liabilities इकाई
audits USA Inc (US LE)
Represents a division/sub-division संचालन
Operating Purchasing, Order Infosys India – Bangalore OU,
performing daily operations, tied to इकाई /
Unit Management, AR, AP Infosys USA – New York OU
a LE कार्य इकाई
इन्वेंट्री
Physical/Logical warehouse for संगठन / Bangalore Warehouse,
Inventory Org Inventory, MRP, WIP
storing goods गोदाम Chennai Distribution Center
संगठन
मानव HRMS – to define IT Department in Infosys India
HR Organization used to manage
संसाधन departments, locations, OU, Finance Dept in Infosys
Organization employees within an OU or BG
संगठन reporting USA OU

🔁 Hierarchy (Typical Oracle Apps Structure)

Business Group
└── Legal Entity (can be multiple under BG)
└── Operating Unit (linked to LE)
└── Inventory Organization (linked to OU)
└── HR Organization (can be defined at any level)

🧠 Quick Recap in Simple Terms

Component Purpose Real-Life Example
Business Group Full enterprise HR setup Infosys Global HR
Legal Entity Registered company Infosys India Pvt. Ltd
Operating Unit Division handling transactions Infosys Bangalore Sales Division
Inventory Org Warehouse Bangalore Warehouse
HR Organization Team/Dept in HR setup HR Dept or Finance Dept

What is MOAC architecture in oracle apps

MOAC Architecture in Oracle Apps (E-Business Suite)

MOAC stands for Multi-Org Access Control — a feature introduced in Oracle E-Business Suite R12 that allows users to
access multiple Operating Units (OUs) from a single responsibility without switching responsibilities.

🔍 What is MOAC (Multi-Org Access Control)?

Aspect Details
Full Form Multi-Org Access Control
Introduced In Oracle EBS R12
Purpose To allow access to multiple Operating Units (OUs) from a single login
Benefit No need to switch responsibilities for each OU; streamlines multi-OU work
Modules Affected Payables, Receivables, Purchasing, Order Management, etc.

⚙️How MOAC Works – Technical Architecture

1. Security Profile is created using HRMS Responsibility (e.g., "Global HRMS Manager").
2. Security Profile includes multiple OUs.
3. Security Profile is assigned to the MO: Security Profile profile option at the responsibility/user level.
4. Oracle uses the MO_GLOBAL application context to restrict data per OU.

🧭 MOAC Key Components

Component Description
MO: Operating Unit Used in pre-R12 to assign a single OU to a responsibility
MO: Security Profile New in R12; assigns multiple OUs to one responsibility
HR Security Profile Created in HRMS to define accessible organizations/OUs
MO_GLOBAL package Used internally by Oracle to filter data based on selected OU

✅ Advantages of MOAC
Feature Benefit
Access multiple OUs from one login Increases productivity
Centralized control Simplifies user and data management
Reduces customizations Less need for personalization to handle multiple OUs
Streamlined reporting Cross-OU reporting in one place

💡 Example Use Case

A user in Infosys handles payments for Infosys India OU and Infosys USA OU.
With MOAC, the user can access both OUs from a single responsibility like "Payables Manager" and process invoices
without switching.

MOAC in Action
 Responsibility: Payables Manager
 Security Profile: Includes Infosys India OU, Infosys USA OU
 User Action: Enters invoices for both OUs by selecting the desired OU on the invoice screen (via LOV - List of
Values)

difference between MO: Operating Unit vs MO: Security Profile vs HR Security Profile in oracle apps with example

Here's a clear comparison chart explaining the difference between MO: Operating Unit, MO: Security Profile, and HR
Security Profile in Oracle Apps (E-Business Suite R12) with real-world examples:

📘 Oracle Apps – MOAC Profile Options Comparison

Profile Full Name Purpose / Use Level Applies To Introduced Example
Option /
In
Term
MO: Multi-Org: Assigns a single R11 / R12 "Payables Manager"
Responsibility /
Operating Operating Operating Unit to a (backward R11i responsibility is tied to
User
Unit Unit responsibility compatibility) Infosys India OU only
Allows access to
MO: Multi-Org: Security profile includes
multiple Operating Responsibility / R12 (MOAC
Security Security R12 Infosys India OU +
Units through a User feature)
Profile Profile Infosys USA OU
security profile
Human HR user can view
Defines org access for
HR Security Resources Business Group / Always employees from
HR data (employees, HRMS Module
Profile Security Responsibility existed multiple departments
orgs, positions, etc.)
Profile across business units

🔁 Key Differences
Feature MO: Operating Unit MO: Security Profile HR Security Profile
HR Organizations (employees, jobs,
Scope One Operating Unit Multiple Operating Units
locations, etc.)
Financials, Procurement, Financials, Procurement, OM (with HRMS Module (Core HR, SSHR,
Used In
OM MOAC) Payroll)
Low – Only 1 OU per High – Access multiple OUs in one Controls employee/org access within
Flexibility
responsibility responsibility HR
Required For No (used only if not using
✅ Yes – Required to enable MOAC No – Used only in HR modules
MOAC? MOAC)

💡 Real-World Scenario Example

Let's say you're working at Infosys, which has 2 Operating Units:
 Infosys India OU
 Infosys USA OU
Scenario Without MOAC With MOAC
Payables clerk enters Needs separate responsibilities: one for each One responsibility (e.g., "AP Manager") with MO:
invoices OU Security Profile assigned
HR Manager accesses Uses HR Security Profile to access all Uses HR Security Profile to access multiple orgs,
employee data departments in Infosys India jobs, and locations if allowed

🔐 MOAC Profile Setup Flow

1. Create a Security Profile in HRMS (includes multiple Operating Units)
2. Assign it to the MO: Security Profile
3. If not using MOAC, use MO: Operating Unit (assigns a single OU)
4. HR-related access is controlled separately via HR Security Profile

What is difference between open vs hold vs cancel vs freeze vs unfreeze vs close for receive and close for invoice and open for
receive and open for invoice PO status .
Great question! Understanding Purchase Order (PO) statuses is crucial in systems like Oracle Purchasing or Oracle Apps.
The terms you're asking about — Open, Hold, Cancel, Freeze, Unfreeze, Close for Receiving, Close for Invoicing — refer to
different life cycle states of a Purchase Order and its availability for further processing.
Below is a clear comparison of each status, specifically in the context of a PO (Purchase Order):

🔁 General PO Statuses
Status Meaning Effect
Open The PO is active and open for receiving and invoicing. Items can be received and invoiced.
Hold Puts a temporary stop on PO processing. Prevents receiving and invoicing until released.
Cannot be received or invoiced. Budget is
Cancel Terminates the PO or a PO line completely.
released.
PO is read-only but can still be received or
Freeze Prevents any updates or changes to the PO.
invoiced.
Unfreeze Lifts the freeze. PO can be modified again.
Close for
Receiving is complete. No more receipts allowed. Cannot receive further quantities.
Receiving
Close for Invoicing Invoicing is complete. No more invoices allowed. Cannot match further invoices.
Both receiving and invoicing are completed or forced
Finally Closed No further action allowed. Budget is released.
closed.
📦 Receiving-Related Status
Status Receive Allowed? Notes
Open for Receiving ✅ Yes Normal state for receiving items.
Closed for Receiving ❌ No Receiving is completed or force-closed.
Hold ❌ No Receiving blocked until hold is removed.
Canceled ❌ No Cannot receive; PO is canceled.

💵 Invoice-Related Status
Status Invoice Allowed? Notes
Open for Invoicing ✅ Yes Open to match invoices.
Closed for Invoicing ❌ No No further invoices can be matched.
Hold ❌ No Invoicing is blocked.
Canceled ❌ No Cannot invoice.

🔒 Freeze vs Hold — Key Difference

Freeze Hold
Used to prevent edits to PO. Used to temporarily block PO from processing (receiving/invoicing).
PO can still be received and invoiced. PO cannot be received or invoiced.
Administrative action, often to pause changes. Operational control, often used for budget or approval issues.

✅ Summary Table
Status Can Edit? Can Receive? Can Invoice?
Open ✅ Yes ✅ Yes ✅ Yes
Hold ❌ No ❌ No ❌ No
Freeze ❌ No ✅ Yes ✅ Yes
Unfreeze ✅ Yes ✅ Yes ✅ Yes
Cancel ❌ No ❌ No ❌ No
Close for Receiving ✅ Yes ❌ No ✅ Yes
Close for Invoicing ✅ Yes ✅ Yes ❌ No
Finally Closed ❌ No ❌ No ❌ No
difference between requisition and Purchase order

The difference between a Requisition and a Purchase Order (PO) lies in their purpose, timing, and authority in the
procurement process.
Here’s a clear, structured comparison:

📝 1. Requisition
Aspect Details
Definition An internal request to purchase goods or services.
Purpose To initiate the procurement process and seek approval.
Created By Employees, departments, or requesters inside the organization.
Used For Requesting a purchase, specifying items, quantities, and reasons.
Approval Required? Yes, before it can become a PO.
Legal Document? ❌ No, it's an internal document only.
Can Be Sent to Supplier? ❌ No
Example “We need 10 laptops for the IT team.”

📄 2. Purchase Order (PO)

Aspect Details
Definition A formal, external document sent to a supplier to order goods/services.
Purpose To authorize a vendor to deliver goods/services and initiate the buying contract.
Created From Approved requisitions or manually by purchasing department.
Used For Placing official orders with vendors.
Approval Required? Yes, but typically after the requisition stage.
Legal Document? ✅ Yes, it is a binding contract once accepted by the vendor.
Can Be Sent to Supplier? ✅ Yes
Example “Order placed for 10 laptops with XYZ Supplier for $12,000.”
🔁 Requisition-to-PO Flow in Oracle (Simplified)
Employee Creates Requisition → Approval Workflow → Buyer Converts to PO → PO Approved → PO Sent to Vendor

🧠 Key Differences Summary

Feature Requisition Purchase Order
Initiates procurement? ✅ Yes ❌ No
Sent to supplier? ❌ No ✅ Yes
Legally binding? ❌ No ✅ Yes
Created by Requester/Employee Purchasing Department
Used for Internal approval External procurement
Becomes a PO? ✅ After approval N/A

difference between available to reserve and available to transact

Great question! In Oracle Inventory or Order Management, "Available to Reserve" and "Available to Transact" are key
terms related to inventory availability, but they serve different purposes.
Here’s a clear and concise comparison:

📦 1. Available to Transact (ATT)

Aspect Details
The quantity of an item that is physically available in inventory for any transaction (issue,
Definition
transfer, sales order, etc.).
Includes On-hand quantity minus reservations.
Used In Inventory transactions like move orders, subinventory transfers, etc.
Example You have 100 items in stock, 20 are reserved. Then:
👉 Available to Transact =
80

🔒 2. Available to Reserve (ATR)

Aspect Details
Definition The quantity that can be reserved for demand (like a sales order or work order).
Includes On-hand stock that is available for reservation only, not already reserved or on hold.
Used In Order Management, WIP (Work in Process), and similar modules that require demand reservation.
✅ Yes — not everything available to transact is necessarily reservable (e.g., if held or in restricted
More Restrictive?
subinventories).

✅ Key Differences Summary

Feature Available to Transact Available to Reserve
Purpose For any transaction (issue, transfer, etc.) For reserving items for demand
Used in Inventory module Order Management, WIP
Scope Broader — includes more Narrower — only eligible items
Subinventory Restrictions Less strict More strict (must be reservable)
Can be greater than ATR? ✅ Yes ❌ No

📌 Simple Example:
You have 100 units in stock:
 20 are reserved.
 10 are in a subinventory not reservable.
Metric Value
On-Hand 100
Reserved 20
Unreservable 10
Available to Transact 80 (100 - 20 reserved)
Available to Reserve 70 (80 - 10 unreservable)

Great! Here's how "Available to Transact" and "Available to Reserve" are handled in Oracle Inventory — including
relevant tables, queries, and a diagram explanation.

🧾 Oracle Tables Involved

Table Description
MTL_ONHAND_QUANTITIES Stores on-hand quantity at inventory and subinventory levels.
MTL_RESERVATIONS Stores reservation details (how much is reserved, for whom).
MTL_DEMAND Stores demand information (sales orders, work orders, etc.).
MTL_SUPPLY Tracks supply sources like purchase orders, jobs.

🔍 SQL Queries
🔹 1. Available to Transact (ATT)
SELECT SUM(transaction_quantity)
FROM mtl_onhand_quantities
WHERE inventory_item_id = :item_id
AND organization_id = :org_id;
This gives total on-hand quantity (without checking reservations).

🔹 2. Available to Reserve (ATR)

SELECT SUM(moq.transaction_quantity) -
NVL((SELECT SUM(reservation_quantity)
FROM mtl_reservations
WHERE inventory_item_id = moq.inventory_item_id
AND organization_id = moq.organization_id), 0) AS available_to_reserve
FROM mtl_onhand_quantities moq
WHERE moq.inventory_item_id = :item_id
AND moq.organization_id = :org_id;
This subtracts reserved quantities to show what's actually reservable.
You might also need to join with MTL_SECONDARY_INVENTORIES to exclude non-reservable subinventories (like
"staging" or "damaged").

🔁 Diagram: Flow of Quantities

+----------------------+
| Total On-Hand (100) |
+----------------------+
|
+---------------------+----------------------+
| |
+------------------+ +-----------------------+
| Reserved (20) | | Not Reserved (80) |
+------------------+ +------------------------+
| |
| +----------------+------------------+
| | |
Used in: | Reservable (70)
Sales Orders, etc. | (excluding 10 not in
| reservable subinventory)
Unreservable (10)
(e.g., QA hold, staging)

✅ Summary
Metric Description Example (of 100 on-hand)
On-Hand Quantity Total physically present 100
Reserved Already committed 20
Available to Transact Can be issued or moved 80
Available to Reserve Can be reserved for demand 70
difference between MTL_ONHAND_QUANTITIES vs MTL_RESERVATIONS vs MTL_DEMAND vs MTL_SUPPLY

Excellent question! These four tables — MTL_ONHAND_QUANTITIES, MTL_RESERVATIONS, MTL_DEMAND, and

MTL_SUPPLY — are core inventory tables in Oracle E-Business Suite (Oracle Apps). Each plays a different role in
managing inventory, demand, supply, and reservations.

🔍 Quick Comparison Table

Table Name Purpose Stores Info About Used By
Tracks physical on-hand Current stock in subinventories &
MTL_ONHAND_QUANTITIES Inventory, WIP, OM
inventory locators
MTL_RESERVATIONS Links supply to demand Reserved quantities for specific OM, WIP, Inventory
 (reserves stock) demand
What is needed (sales/work OM, MRP (Material
MTL_DEMAND Records demand requirements
orders) Planning)
Records expected incoming What is incoming (POs, Jobs,
MTL_SUPPLY MRP, Inventory, WIP
supply etc.)

🧾 Detailed Breakdown
📦 1. MTL_ONHAND_QUANTITIES
 What it tracks: Real-time physical inventory.
 Grain: Item, subinventory, locator, lot, serial.
 Key Columns:
o inventory_item_id
o organization_id
o subinventory_code
o transaction_quantity
 Example: 100 units of Item A in Subinventory FG1.

🔒 2. MTL_RESERVATIONS
 What it tracks: Reserved quantity of on-hand or future supply against a demand (like a sales order).
 Used to "link" supply to demand.
 Key Columns:
o inventory_item_id, reservation_quantity
o demand_source_type_id → links to demand (e.g., sales order)
o supply_source_type_id → links to supply (e.g., on-hand, PO)
 Example: 20 units reserved from FG1 for SO#123.

📥 3. MTL_DEMAND
 What it tracks: Demand in the system — sales orders, work orders, WIP requirements, etc.
 Used by MRP and ATP (Available to Promise).
 Key Columns:
o inventory_item_id
o demand_source_type_id (e.g., Order Management)
o demand_quantity
 Example: Sales Order needs 50 units of Item A by next week.

📤 4. MTL_SUPPLY
 What it tracks: Supply coming into inventory — from POs, WIP jobs, etc.
 Used by MRP and ATP to calculate available quantity.
 Key Columns:
o inventory_item_id
o supply_source_type_id (e.g., PO, WIP)
o supply_quantity
o supply_required_date
 Example: 30 units coming via PO#456 next Friday.

🔄 Flow Example
+-------------------+ +-------------------+
| MTL_DEMAND | -----> | MTL_RESERVATIONS |
| (Need 50 units) | | (Reserve 20 units)|
+-------------------+ +-------------------+
| |
↓ ↓
+-------------------+ +-------------------+
| MTL_SUPPLY | | MTL_ONHAND_QUANT. |
| (PO Incoming 30) | | (Current: 100) |
+-------------------+ +-------------------+

✅ Use Case Summary

Use Case Table Used
How much stock do we have? MTL_ONHAND_QUANTITIES
How much is reserved? MTL_RESERVATIONS
How much do customers want? MTL_DEMAND
How much is coming in? MTL_SUPPLY
Would you like example queries across these tables for a specific item or organization?

What is difference between Cost Manager vs Material Transaction vs Move Transaction vs Lot Move Transaction

Great question! In Oracle Inventory and Cost Management modules, Cost Manager, Material Transactions, Move
Transactions, and Lot Move Transactions each play distinct roles in handling inventory, costing, and movement of goods.
Here's a detailed comparison:

🔹 1. Cost Manager
Aspect Details
Module Oracle Cost Management
Purpose Calculates and updates costs of inventory transactions
Program/Process Cost Manager (Concurrent Manager process)
Processes cost-related data such as material, resource, overhead, and outside processing costs; updates cost
Functionality
layers in perpetual costing
When an inventory transaction occurs (e.g., PO receipt), Cost Manager calculates and posts the accounting
Example
distributions.
Important Table CST_COST_HISTORY, CST_INV_TRANSACTIONS

🔹 2. Material Transaction
Aspect Details
Module Oracle Inventory
Purpose Records physical movement of items in inventory
Program/Process Automatically triggered or submitted via Inventory Transaction Worker
Functionality Handles inventory transactions like issues, receipts, transfers, subinventory moves
Example Transfer item from Subinventory A to B, or issue to Work Order
Important Table MTL_MATERIAL_TRANSACTIONS, MTL_TRANSACTION_ACCOUNTS

🔹 3. Move Transaction
Aspect Details
Module Oracle Work in Process (WIP)
Purpose Tracks movement of discrete jobs or assemblies between operations
Program/Process Move Transaction Manager
Functionality Records step-by-step progress of WIP jobs on the shop floor (from one operation to next)
Example Move a job from Operation 10 (Cutting) to Operation 20 (Welding)
Important Table WIP_MOVE_TXNS, WIP_ENTITIES

🔹 4. Lot Move Transaction

Aspect Details
Module Oracle WIP with Lot-controlled Items
Purpose Tracks movement of lot-controlled WIP items between operations
Program/Process Lot-based version of move transaction
Functionality Similar to Move Transactions, but includes tracking lot numbers in WIP flow
Example Moving Lot# L001 from Op 10 to Op 20 in a discrete job
Important Table WIP_LOT_TRANSACTIONS, WIP_MOVE_TXNS (related)

✅ Summary Table
Feature Cost Manager Material Transaction Move Transaction Lot Move Transaction
Module Costing Inventory WIP WIP
Track operation
Purpose Calculate & post cost Record physical item movement Track lot movement in WIP
progress
Key Move Transaction
Cost Manager Process Inventory Transaction Manager Lot Move Transaction Process
Program Manager
CST_COST_HISTOR MTL_MATERIAL_TRANSACTION WIP_MOVE_TXN WIP_LOT_TRANSACTION
Table
Y S S S
Lot
Not required Optional Optional Required
Controlled

Great! Here's a detailed breakdown including process flow diagrams and sample SQL queries for:
1. Cost Manager
 2. Material Transactions
3. Move Transactions
4. Lot Move Transactions

🔹 1. Cost Manager
🔄 Process Flow:
Inventory Transaction → Transaction Interface Table → Cost Manager → Cost Calculation → Accounting Distributions
✅ Key Tables:
 CST_INV_TRANSACTIONS
 CST_TRANSACTION_COSTS
 MTL_MATERIAL_TRANSACTIONS
🧾 Sample SQL:
SELECT transaction_id, costed_flag, error_code, error_explanation
FROM CST_INV_TRANSACTIONS
WHERE costed_flag <> 'Y';

🔹 2. Material Transaction
🔄 Process Flow:
User/API Inputs → MTL_TRANSACTION_INTERFACE → Inventory Transaction Manager →
MTL_MATERIAL_TRANSACTIONS
✅ Key Tables:
 MTL_MATERIAL_TRANSACTIONS
 MTL_TRANSACTION_ACCOUNTS
 MTL_TRANSACTION_INTERFACE
🧾 Sample SQL:
SELECT transaction_id, inventory_item_id, transaction_type_id, transaction_date, organization_id
FROM MTL_MATERIAL_TRANSACTIONS
WHERE transaction_date > SYSDATE - 7;

🔹 3. Move Transaction
🔄 Process Flow:
Operator Records Job Movement → WIP_MOVE_TXN_INTERFACE → Move Transaction Manager → WIP_MOVE_TXNS
✅ Key Tables:
 WIP_MOVE_TXNS
 WIP_MOVE_TXN_INTERFACE
 WIP_ENTITIES
🧾 Sample SQL:
SELECT move_transaction_id, wip_entity_id, from_operation_seq_num, to_operation_seq_num, transaction_date
FROM WIP_MOVE_TXNS
WHERE transaction_date >= TRUNC(SYSDATE) - 3;

🔹 4. Lot Move Transaction

🔄 Process Flow:
WIP Lot Movement Recorded → WIP_LOT_TXN_INTERFACE → Lot Move Transaction Process →
WIP_LOT_TRANSACTIONS
✅ Key Tables:
 WIP_LOT_TRANSACTIONS
 WIP_LOT_TXN_INTERFACE
🧾 Sample SQL:
SELECT lot_transaction_id, lot_number, wip_entity_id, from_op_seq_num, to_op_seq_num
FROM WIP_LOT_TRANSACTIONS
WHERE transaction_date > SYSDATE - 5;

Let me know if you want:

 A diagram visualizing these processes
 Example errors and troubleshooting
 Concurrent program names to monitor or troubleshoot processing
Would you like a visual diagram of these flows?

what is allow express transaction

In Oracle E-Business Suite, the "Allow Express Transactions" checkbox is a feature that enables users to perform quick,
bulk receiving and delivery actions — especially useful in high-volume or warehouse environments.
🔹 What Is Allow Express Transactions?
"Allow Express Transactions" is an option available at the:
 Receiving Parameters
 Supplier or Supplier Site
 Organization Setup
When enabled, it allows users to:
 Receive all items on a purchase order or shipment in one action
 Deliver all received lines at once without needing to handle each line individually

🔹 Where You See This Setting

You can enable this option in:
 Inventory > Setup > Organizations > Receiving Parameters
 Purchasing > Suppliers > Supplier Sites > Receiving Region
Look for: ✅ Allow Express Transactions

🔹 Use Case Example

Example Scenario:
You receive a shipment with 10 PO lines (items) from a supplier.
Without Express Receiving:
 You must click and receive each line manually.
 Then, for each line, click "Deliver".
With Express Receiving:
 You select the Express Receive option.
 Oracle automatically receives all lines and delivers them in a single step.

🔹 How to Use Express Receiving (Steps)

1. Navigation: Inventory > Transactions > Receiving > Receipts
2. Enter PO or ASN Number
3. Select "Express" checkbox
4. Click “Receive”
5. All lines are received and delivered instantly

🔹 Benefits
Feature Benefit
Speed Reduces receiving effort and time
Accuracy Minimizes user input errors
Efficiency Ideal for high-volume warehouses
Automation Simplifies full shipment receipt

✅ Notes
 If some lines are not available or partially shipped, Express Receiving might not work — you’ll need manual
receiving.
 You can still perform partial receipts or inspect items if required, but Express is usually for complete, standard
receipts.

what is allow cascade transaction

In Oracle E-Business Suite (EBS), particularly in Inventory and Warehouse Management, the "Allow Cascade
Transactions" option is designed to improve efficiency when transferring or delivering multiple quantities of an item
across multiple subinventories or locators.

🔹 What Is Allow Cascade Transactions?

"Allow Cascade Transactions" is a setup option that allows automatic cascading of unallocated quantity across multiple
locators or subinventories until the entire quantity is transacted.
💡 It's particularly useful in inventory transfers, picking, and WMS operations, where users don’t want to manually split
quantities between locators.

🔹 Where You See This Setting

You’ll typically find it in:
 Inventory > Setup > Organizations > Parameters > Transaction Parameters tab
 For specific subinventories or WMS-enabled organizations
Look for: ✅ Allow Cascade Transactions

🔹 Real-World Example
Scenario:
You are transferring 100 units of Item A from Subinventory Stores to Production, but no single locator in the destination has
room for 100 units.
Without Cascade:
 You manually split the quantity:
o 50 units to Locator A
o 30 units to Locator B
o 20 units to Locator C
With Cascade Enabled:
 You enter 100 units and select "Cascade".
 Oracle automatically allocates across available locators based on capacity, picking rules, or locator order:
o 50 to A, 30 to B, 20 to C (automatically)

🔄 Use Case Flow

Perform Transfer/Transaction
↓
Select Item + Quantity (e.g., 100 units)
↓
System checks available locators
↓
With Cascade = ON → Auto splits quantity
Without Cascade = Manual split required

🔹 Key Benefits
Feature Benefit
Saves Time Reduces need for manual splitting
Reduces Errors Avoids incorrect locator entry
Efficient Picking Ideal for warehouse or WMS use
Streamlines Transfers Especially with constrained locator capacity

🧾 Optional SQL Example: Check if Cascade is Enabled

SELECT organization_id, allow_cascade_transactions
FROM org_parameters
WHERE organization_id = :your_org_id;

✅ Summary
Setting Allow Cascade Transactions
Purpose Auto-split unallocated qty across locators/subinventories
Use Case Transfers, picking, delivery
Benefit Automation and efficiency in warehouse operations
what is functionality of WMS in oracle apps

In Oracle Applications, WMS (Warehouse Management System) is an advanced module within Oracle Inventory and
Oracle Logistics that enhances warehouse operations by providing automated, optimized, and real-time control over
inventory movement. It is typically used in high-volume and complex warehouse environments.

🔍 Key Functionality of Oracle WMS

1. Task Management
 Automatically creates and assigns tasks for picking, putaway, replenishment, and cycle counting.
 Prioritizes tasks based on rules (e.g., FIFO, LIFO, expiration dates).
2. Directed Picking and Putaway
 Guides warehouse operators to the optimal locations for picking and storing items.
 Reduces travel time and increases efficiency.
3. License Plate Numbers (LPNs)
 Tracks inventory using LPNs, which are containers that can hold one or multiple items.
 LPNs simplify movement and tracking of goods within the warehouse.
4. Mobile RF Devices Support
 Operators use handheld devices for scanning and updating transactions in real-time.
 Enables faster and more accurate inventory operations.
5. Cost Group and Rules-Based Management
 Allows segregation of inventory by cost groups.
 Supports complex costing structures and accounting needs.
6. Wave Planning
 Batches picking tasks based on criteria such as order priority, ship-to location, or carrier.
  Helps manage workload and improve shipping efficiency.
7. Warehouse Rules Engine
 Configurable engine for defining custom rules for putaway, picking, and task prioritization.
 Enhances flexibility and automation.
8. Cycle Counting and Physical Inventory
 Enables real-time, task-driven cycle counts.
 Supports dynamic count scheduling based on activity or frequency.
9. Material Status Control
 Controls the usability of items through material statuses (e.g., "Hold", "Restricted").
 Enforces quality or regulatory rules.
10. Label Printing and Integration
 Integrates with barcode and label printers for real-time label generation.
 Supports UCC128, serial numbers, LPNs, etc.

📦 Integration with Other Modules

Oracle WMS works closely with:
 Oracle Inventory – for stock tracking and control.
 Oracle Order Management – for fulfilling customer orders.
 Oracle Shipping Execution – for packing, staging, and shipping.
 Oracle Purchasing & Receiving – for inbound logistics.
 Oracle Cost Management – for tracking cost implications of warehouse activities.

✅ Benefits
 Improved warehouse accuracy and throughput.
 Real-time visibility of inventory and warehouse operations.
 Reduced labor costs and manual errors.
 Better customer satisfaction due to timely and accurate shipments.

comparison between Oracle Inventory with WMS vs. without WMS

Great! Here's a comparison between Oracle Inventory with WMS vs. without WMS, followed by an example of a WMS
picking and shipping workflow.

📊 Oracle Inventory: With WMS vs Without WMS

Without WMS (Standard
Feature / Process With WMS
Inventory)
Putaway / Picking Manual or rule-limited Directed by rules engine (optimized routes/locations)
Task Management Not available Automated task creation, assignment, and monitoring
License Plate Numbers
Not supported Fully supported (container-based tracking)
(LPNs)
Mobile RF Devices Limited or custom implementations Native support for mobile scanners and barcode readers
Wave planning based on order criteria and warehouse
Wave Planning Manual or batch picking
zones
Material Status Limited (status on item level) Granular control by subinventory, locator, or LPN
Cycle Counting Manual or scheduled Dynamic, task-driven, based on activity or exceptions
Supports multiple cost groups within the same inventory
Cost Group Segregation Basic
org
Labor Management Not available Task assignment and tracking by user/device
Label Printing Basic Integrated with Zebra printers, real-time label generation

🔄 Example: WMS Picking and Shipping Workflow

Let’s walk through a typical sales order picking and shipping process in Oracle WMS:
🧾 Step 1: Sales Order is Booked
 Order is entered in Order Management and booked.
 It flows to Shipping Execution and creates a delivery.
📦 Step 2: Pick Release
 Pick release is initiated (manually or scheduled).
 WMS creates picking tasks and assigns them to warehouse operators.
🔍 Step 3: Task Execution via RF Device
 Warehouse operator receives the task on a mobile RF device.
 System guides the operator to the exact location using directed picking.
 Operator scans the item and confirms the pick.
 Items are placed into an LPN (License Plate Number).
🚚 Step 4: Staging and Packing
  Picked items are moved to a staging locator.
 At the staging area, items are scanned and packed.
 Shipping labels (UCC128) and packing slips are printed.
✅ Step 5: Ship Confirm
 The delivery is ship confirmed in Oracle.
 Inventory is decremented, and financial accounting happens.
 Interface to Accounts Receivable for invoicing.

🧠 Real-World Benefit:
 Without WMS, you'd rely on printed pick slips and manual updates.
 With WMS, it's real-time, efficient, and reduces errors.
what is functionality of ASCP

Here’s a short summary of the functionality of ASCP (Advanced Supply Chain Planning) in Oracle Apps:

✅ ASCP Functionality in Short:

 Global Planning: Plans across multiple organizations, suppliers, and distribution centers.
 Constraint-Based Planning: Considers capacity, supplier limits, and material availability.
 Material & Resource Planning: Simultaneously plans what to make, buy, and how to schedule it.
 Real-Time & Fast: Uses in-memory processing for faster and more frequent planning runs.
 Optimized Decisions: Supports cost and service level optimization (optional).
 What-If Simulations: Allows planners to simulate changes without affecting the live plan.
 Integrated Planning: Works with Inventory, Purchasing, BOM, WIP, and Order Management.
 Planner Workbench: Interactive UI for analyzing and acting on plan recommendations.

what is functionality of MRP in oracle apps

✅ MRP Functionality in Short:

 Material Planning: Calculates material requirements based on demand (sales orders, forecasts).
 Netting Logic: Considers on-hand, open orders, and lead times to generate net requirements.
 Planned Orders: Suggests work orders and purchase requisitions to meet shortages.
 Rescheduling & Cancellation: Recommends rescheduling or canceling existing supply if needed.
 Single-Org Focus: Plans within a single inventory organization.
 No Capacity Constraints: Ignores resource limits—assumes infinite capacity.
 Batch-Based Planning: Runs periodically (not real-time).
what is lead time

In Oracle Apps (Oracle E-Business Suite), particularly within the Inventory and Purchasing modules, lead time refers to the
amount of time it takes for a product or component to be available for use after initiating a procurement or manufacturing
action.
There are different types of lead times used in Oracle depending on the context (buying, manufacturing, transferring, etc.).
Here's a breakdown:

🔹 Types of Lead Time in Oracle Apps

1. Preprocessing Lead Time
 Time required before actual processing begins.
 Example: Time to review and approve a purchase requisition.
2. Processing Lead Time
 Time required to actually manufacture the item or process the purchase order.
 For manufactured items, it's the time to build the item.
 For purchased items, it's the time the supplier takes to deliver after receiving the PO.
3. Postprocessing Lead Time
 Time after the item has been received but before it becomes available for use.
 Example: Time needed for quality inspection, testing, or stocking.
4. Cumulative Lead Time
 Total time required to make an item from scratch, including all components and subassemblies.
 Calculated as:
Cumulative Manufacturing Lead Time + Preprocessing + Postprocessing
5. Cumulative Total Lead Time
 Includes procurement and manufacturing lead times for all levels in a BOM (Bill of Materials).
 Important for MRP (Material Requirements Planning).
6. Lead Time Lot Size
 Specifies the lot size used to calculate the manufacturing or purchasing lead time.
7. Supplier Lead Time
 In Oracle Purchasing, this is defined on the Approved Supplier List (ASL) or Sourcing Rules and indicates how long a
 supplier takes to deliver an item.

🔹 Where Lead Time Is Used

 MRP and MPS planning
 Reorder calculations
 Production scheduling
 ATP (Available to Promise) calculations
 Purchase order scheduling

🔹 How to Set Lead Time in Oracle

Lead time values can be entered in:
 Inventory > Items > Master Items / Organization Items
 Purchasing > Approved Supplier List
 Bills of Material > Routings

Difference between ASCP and MRP in oracle apps

In Oracle E-Business Suite, ASCP (Advanced Supply Chain Planning) and MRP (Material Requirements Planning) are both
planning tools used to manage supply and demand, but they differ significantly in functionality, scope, and technology.

🔍 Key Differences Between ASCP and MRP

MRP (Material Requirements
Feature ASCP (Advanced Supply Chain Planning)
Planning)
Runs in Oracle EBS instance (same Runs in a separate planning server (uses APS - Advanced
Architecture
database) Planning Server)
Planning Scope Single organization Multiple organizations / Global planning
Performance Slower for large data sets Optimized for high performance, large data
Uses in-memory planning engine with more advanced
Data Model Based on discrete MRP logic
algorithms
Supports Material, Capacity, Constraint-based, and Order-
Plan Types Only Material Plans
based plans
Assumes infinite capacity and Supports constraint-based planning (resource, supplier,
Constraints
unconstrained resources transportation)
Text-based output (standard Oracle
User Interface Modern, web-based UI with interactive planning workbench
forms)
No simulation, must run a plan again to
Simulation Supports what-if analysis and simulations
see changes
Supply Chain Supports complex supply chains, hubs, distribution centers,
Not supported
Modeling sourcing rules
Planning Frequency Typically run nightly or periodically Can be run frequently, even in real-time (near)
Basic integration with Inventory, BOM, Deep integration with Order Management, Manufacturing,
Integration
WIP, PO Transportation, Distribution

✅ When to Use What?

Use MRP if:
 You are planning for one organization.
 Your planning is simple, with few constraints.
 You don’t need advanced simulations or multi-org visibility.
Use ASCP if:
 You need global supply chain planning.
 You want to consider constraints like capacity, supplier limits.
 You want to do what-if simulations and work in real-time.
 You're dealing with complex sourcing, multi-org, or drop shipments.

🚀 Bonus: Key Components of ASCP

 Planning Workbench: Central UI for analyzing plans.
 Sourcing Rules & Assignment Sets: Define how demand is sourced (buy/make/transfer).
 Collections: Extract and load data from Oracle EBS or other systems.
 Plans: Can be unconstrained, constrained, or optimized.
what is ATP

In Oracle Apps (E-Business Suite), ATP stands for Available to Promise. It is a key order promising functionality used in
Order Management and Supply Chain Management to determine whether a product can be promised to a customer on
a requested date based on current and future availability.
✅ Definition of ATP
Available to Promise (ATP) is the quantity of an item that is available and can be promised to fulfill customer orders,
considering current on-hand inventory, open supply (like purchase orders or work orders), and existing demand (customer
orders, reservations, etc.).

🔍 Where ATP Is Used

 Sales Order Entry in Order Management
 Inventory inquiries
 Advanced Supply Chain Planning (ASCP)
 Global Order Promising (GOP)

📘 ATP Calculation Logic

Basic ATP Calculation Formula:
ATP = On-hand quantity + Incoming supply - Existing demand
ATP Rule Options:
ATP rules define how ATP is calculated and can include:
 On-hand inventory
 Purchase orders
 Work orders
 Reservations
 Safety stock
 Forecasted demand

🔧 ATP in Order Management Flow

When you enter a sales order and request a ship date:
1. Oracle checks the ATP rules defined for the item.
2. It evaluates available stock, planned receipts, and existing commitments.
3. The system suggests the earliest possible date the item can be shipped — this is the ATP date.

📦 ATP Methods in Oracle

There are two major ATP types in Oracle Inventory:
1. Without Reservations (Unconstrained ATP)
 Considers all supply and demand without holding or allocating specific quantities.
2. With Reservations (Constrained ATP)
 Takes into account existing reservations or allocations.

🌐 Global Order Promising (GOP) — for Advanced Users

 GOP is an extension of ATP in Oracle Advanced Supply Chain Planning.
 It provides real-time ATP/CTP (Capable to Promise) across multiple organizations and supply chains.
 Supports complex promise logic like drop shipments, back-to-back, and configure-to-order.

🔍 Example Scenario:
 On-hand: 100 units
 Sales Order A: 30 units
 Purchase Order incoming: 50 units
 ATP = 100 (on-hand) + 50 (incoming) – 30 (existing SO) = 120 units available to promise

Would you like a demo scenario or setup steps for ATP rules in Oracle Inventory or Order Management?

Great! Let's walk through a simple demo scenario and setup steps for configuring and using ATP (Available to Promise) in
Oracle Inventory and Order Management.

✅ Demo Scenario:
Let’s assume the following:
 Item: AS100 (Assembly Item)
 Organization: M1
 On-hand Quantity: 100 units
 Sales Order A: 30 units
 Open Purchase Order (supply): 50 units
 ATP Rule: Includes on-hand + purchase orders – sales orders
Expected ATP:
ATP = 100 (on-hand) + 50 (supply) – 30 (demand) = 120 units
 ATP Setup Steps in Oracle Inventory
Step 1: Define ATP Rule
Navigation:
Inventory > Setup > Rules > ATP
 Rule Name: ATP_BASIC
 Include in ATP:
o On-hand: ✅
o Purchase Orders: ✅
o Work Orders: ❌ (optional)
o Reservations: ✅
o Safety Stock: ❌ (optional)
 Save the rule.

Step 2: Assign ATP Rule to Item

Navigation:
Inventory > Items > Master Items
Find Item: AS100
 Go to the Order Management tab.
 Set ATP Rule: ATP_BASIC
 Set ATP Components: ATP = Yes
 Save.

Step 3: Check ATP in Inventory

Navigation:
Inventory > On-hand, Availability > Available to Promise
 Query Item: AS100
 Organization: M1
 Click ATP Details
 You will see ATP calculated by date bucket (per supply and demand)

📦 ATP Check During Sales Order Entry

Navigation:
Order Management > Orders, Returns > Sales Orders
 Enter a new order for item AS100
 Quantity: 50
 Enter Requested Date
 Click on Availability Button
You will see:
 ATP Date
 Available Quantity
 Promised Date
If enough ATP exists (>= 50), it will confirm the requested date.
Otherwise, it will propose the earliest possible date based on incoming supply.

🧠 Notes:
 If ATP is not calculating correctly, check:
o ATP rule setup
o Assignment of the rule to item
o Data in supply and demand (on-hand, open orders, reservations)
 You can define multiple ATP rules for different strategies (e.g., include work orders or forecast demand).

what is Global purchase agreement with example

What is a Global Purchase Agreement (GPA)?

A Global Purchase Agreement (GPA) is a long-term agreement between a buying organization and a supplier that defines
pre-negotiated terms (such as pricing, payment terms, and delivery conditions), which can be used across multiple operating
units or business units globally.
It is typically used in Oracle Purchasing to streamline global procurement by enabling multiple branches or subsidiaries of a
company to buy from the same supplier under one unified contract.

🔑 Key Characteristics:
 Pre-defined terms and conditions.
 No specific delivery schedules.
 Used globally across multiple regions or operating units.
 Enables local purchases (via releases) using the central agreement.
  Promotes cost savings, standardization, and efficiency.

✅ Example of Global Purchase Agreement:

Scenario:
A multinational company, TechGlobal Inc., has offices in:
 India
 USA
 Germany
They purchase laptops and IT equipment from Dell.

Step-by-Step Use of GPA:

1. Create Global Purchase Agreement (GPA):
o Buyer at the headquarters creates a Global Purchase Agreement with Dell.
o Agreement includes:
 Item categories (e.g., Laptops, Monitors)
 Standard price list (e.g., Laptop: $900 each)
 Terms: 30 days payment, 2-week delivery window
 Validity: 1 year
o GPA is made available to all operating units.
2. Releases by Local Units:
o India Office raises a release for 50 laptops.
o Germany Office raises a release for 20 monitors.
o Both use the same GPA, ensuring consistent pricing and terms.

📌 Benefits:
 Unified Procurement: One agreement covers multiple geographies.
 Efficiency: No need to negotiate separately for each location.
 Cost Control: Leverages bulk pricing.
 Consistency: Ensures uniform contract terms globally.

Would you like a comparison between GPA and Blanket Purchase Agreement or a sample format of a GPA in Oracle?
Great! Here's a detailed breakdown of:

✅ Comparison: Global Purchase Agreement vs Blanket Purchase Agreement

Feature Global Purchase Agreement (GPA) Blanket Purchase Agreement (BPA)
Scope Used across multiple operating units (global or multi-org) Used within a single operating unit
Localized, recurring purchases from a
Purpose Centralized, standardized global procurement
supplier
Access Shared across multiple legal entities or business units Limited to one legal entity or OU
For multi-national companies with centralized vendor For local purchases with repetitive
Use Case
agreements demand
System Setup Requires Global Agreements flag enabled and document
Created directly in the purchasing module
(Oracle) style setup
Releases Local business units issue Blanket Releases Blanket Releases are also used
Local vendor supplying office supplies
Example Dell supplying laptops globally
monthly

📄 Sample Format: Global Purchase Agreement in Oracle

When you create a GPA in Oracle, you typically fill in the following:
1. Header Level
 Agreement Type: Global Blanket Purchase Agreement
 Supplier: Dell Technologies
 Agreement Number: GPA12345
 Effective Dates: 01-JAN-2025 to 31-DEC-2025
 Global Agreement Checkbox: ✔️Enabled
 Terms: 30 Days Net, FOB - Destination
 Currency: USD
2. Line Level
Line Item Category Description Unit Price UOM Supplier Item Quantity
1 Laptops Dell Latitude 7440 $900 Each DL-7440 1000
2 Monitors 24” LED Monitor $150 Each DL-24LED 500
3. Terms and Conditions
 Delivery Time: Within 14 days from release
  Payment Terms: 30 Days
 Penalty Clause: Included
 Tax and Freight: As per region/local OU

🧾 What Happens After GPA Creation?

✅ Local OU (India, Germany, US) can:
 Reference the GPA to create Blanket Releases in their own local currency or PO module.
 Make purchases without renegotiating terms.

🔁 Example of Blanket Release against GPA:

 Operating Unit: India OU
 Blanket Agreement: GPA12345
 Release Number: BR-IND-001
 Items Ordered: 50 Laptops
 Delivery Address: Bangalore Office
 Currency: INR (converted using exchange rate)

Would you like a visual workflow (diagram), setup steps in Oracle, or SQL query to track GPAs and their releases?