1Z0-1073-25 Practice Questions

In a back-to-back fulfillment process, the item is not fulfilled from existing on-hand inventory. Instead, a sales order triggers the creation of a specific supply order (like a purchase order or work order). Global Order Promising (GOP) schedules the fulfillment to occur from an internal warehouse. Supply Chain Orchestration then creates the necessary supply document to bring the goods into that designated internal warehouse, where they are reserved for and subsequently shipped against the original sales order. Therefore, the item must be enabled for back-to-back, and the scheduling source must be an internal warehouse.

A. Scheduling Result = Supplier, Back-to-Back Enabled = Yes: This is incorrect. When the scheduling result is a supplier, it signifies a drop ship process where the supplier ships directly to the customer, bypassing the internal warehouse.

C. Scheduling Result = Supplier: This describes a drop ship fulfillment model, not a back-to-back one. It is also an incomplete setup description.

D. Scheduling Result = Internal Warehouse, Back-to-Back Enabled = No: This describes a standard fulfillment process where an order is fulfilled from existing on-hand inventory in a warehouse, not a back-to-back flow.

1. Oracle Fusion Cloud SCM

Using Order Management (Release 24B)

Document ID F85339-02

Chapter: Fulfill Orders

Section: Overview of Back-to-Back Fulfillment. This section states

"Order Promising schedules supply for the sales order from your warehouse

then sends a supply recommendation to Oracle Supply Chain Orchestration. Supply Chain Orchestration creates the supply document

such as a purchase order

transfer order

or work order." This confirms the scheduling result is an internal warehouse.

2. Oracle Fusion Cloud SCM

Implementing Order Management (Release 24B)

Document ID F85338-02

Chapter: Manage Order Promising

Section: How Back-to-Back Fulfillment Works. This document details the process: "Global Order Promising promises the sales order and determines that the item is available in a warehouse... It sends a recommendation to Supply Chain Orchestration to create a supply order." This reinforces that the scheduling points to a warehouse.

3. Oracle Fusion Cloud SCM

Using Global Order Promising (Release 24B)

Document ID F85342-02

Chapter: Order Promising Options

Section: How Order Promising Fulfills Drop Shipments. This document clarifies the alternative: "Order Promising schedules the sales order and determines that your supplier can ship the item directly to your customer." This explicitly differentiates the "Scheduling Result = Supplier" scenario as drop shipment.

For transfers of high-value goods between two inventory organizations that require formal tracking and approval, Oracle SCM Cloud provides two primary recommended methods.

1. Internal Requisition to Transfer Order Flow (A): This process begins with an internal requisition, which goes through a formal approval workflow. Once approved, it creates a transfer order, providing robust end-to-end tracking from shipment to receipt. This method is ideal for controlled transfers, especially between different business units.

2. Movement Requests (D): A movement request is a formal document used to request the movement of materials. It can be configured to require approvals before the physical transaction is performed. This provides an essential control point for initiating transfers, ensuring they are properly authorized before execution.

B. Interorganization transfer: This refers to the direct transaction type. While it moves goods between organizations and can be tracked in-transit, the direct method lacks the built-in, formal pre-approval workflow specified as a requirement.

C. Subinventory transfer: This transaction is used for moving items within a single inventory organization (from one subinventory to another), not between two separate organizations.

1. Oracle Fusion Cloud SCM

Using Inventory Management

Chapter: Manage Internal Material Transfers

Section: Overview of Internal Material Transfers.

This section outlines the different ways to manage internal transfers. It describes Transfer Orders as being "formal requests for internal transfer of goods" that are "orchestrated business processes" often starting from an internal requisition with approvals. It also describes Movement Requests as a way to "manually request movement of material

" which can be subject to an approval process.

2. Oracle Fusion Cloud SCM

Using Inventory Management

Chapter: Manage Inventory Transactions

Section: Movement Requests.

The documentation states

"A movement request is a request for the movement of material within an inventory organization or between organizations... You can require approval for movement requests." This confirms that movement requests are a primary tool for approved transfers between organizations.

3. Oracle Fusion Cloud SCM

Using Inventory Management

Chapter: Manage Internal Material Transfers

Section: Create Transfer Orders from Requisitions.

This document details the process where an approved internal requisition is the source for a transfer order

highlighting the requisition and its approval as the key control step for initiating the interorganization transfer. This supports option A.

Project-Driven Supply Chain (PDSC) in Oracle Fusion Cloud SCM provides flexibility in managing project-specific transactions. For referenced returns (RMAs), users with appropriate privileges can remove the defaulted project and task details. This allows the returned material to be received into common inventory rather than being tied to the original project. Additionally, administrators can configure cost collection exclusions. Using the "Manage Project-Type Costing Exclusions" setup task, specific project types can be prevented from having their associated supply chain transactions transferred to Oracle Project Costing. This provides granular control over which projects accumulate supply chain costs.

A. Common inventory cannot be used for project-specific picks.

This is incorrect. A key feature of PDSC is the ability to fulfill project demand by picking from either project-specific or common inventory stock.

D. Project and task details are not available on the Manage Item Quantities page.

This is incorrect. The Manage Item Quantities page is enhanced in a PDSC environment to display project and task columns, allowing inventory visibility for both project-specific and common stock.

1. Oracle Fusion Cloud SCM

Using Project-Driven Supply Chain

Release 24B

Chapter 4: Returns. This chapter details the process for referenced returns

stating

"For a referenced return

the project and task from the original sales order are defaulted. You can clear these details to return the material to common inventory."

2. Oracle Fusion Cloud SCM

Implementing Project-Driven Supply Chain

Release 24B

Chapter 2: Set Up Project-Driven Supply Chain. This guide describes the setup tasks

including "Manage Project-Type Costing Exclusions

" which is used to "specify the project types for which you want to exclude transactions from project costing."

3. Oracle Fusion Cloud SCM

Using Inventory Management

Release 24B

Chapter: Manage Inventory Balances

Section: Manage Item Quantities. This section explains that with PDSC enabled

the Manage Item Quantities page includes Project and Task fields to view project-specific on-hand balances.

4. Oracle Fusion Cloud SCM

Using Project-Driven Supply Chain

Release 24B

Chapter 1: Overview of Project-Driven Supply Chain. The overview confirms that you can "Fulfill demand for a project from common inventory or from project-specific inventory."

In Oracle Inventory Management Cloud, when items are discovered during a physical count that do not have a pre-generated tag, the standard and recommended procedure is to create a dynamic tag. This feature is specifically designed to handle such exceptions, allowing personnel to record counts for items found in unexpected locations or for items that were missed during the initial snapshot. This ensures all physically present items are accounted for without disrupting the existing count structure or requiring a complete restart of the tag generation process.

A. Record these items on existing tags: This would corrupt the count data for the item originally assigned to that tag, leading to inaccurate inventory records for at least two items.

B. Rerun the Generate Physical Inventory Tag process for these items: This process is run before the count begins. The correct in-process action for missed items is creating dynamic tags, not rerunning an initial setup process.

1. Oracle Fusion Cloud SCM

Using Inventory Management

Release 24B

Chapter: Count Inventory

Section: Record Physical Inventory Tag Counts.

Reference: The documentation states

"You can also create dynamic tags. You can use dynamic tags to count items that you find in a location that weren't expected to be there." This directly supports the use of dynamic tags for items found without a pre-generated tag.

2. Oracle Fusion Cloud SCM

Implementing Manufacturing and Supply Chain Materials Management

Release 24B

Chapter: Inventory Management

Section: Physical Inventory.

Reference: In the "Define and Manage Inventory" chapter

under the "Physical Inventory" section

the guide explains the setup options: "Dynamic tag entry is permitted if you select the Allow Dynamic Tags option for the physical inventory. This lets you count items that are found during a physical count that weren't included in the snapshot." This confirms that allowing dynamic tags is the intended mechanism for this scenario.

In Oracle Fusion Cloud Inventory Management, you can define default stocking units of measure (UOM) at multiple levels to manage how items are stored. While an item has a primary UOM defined at the organization level, you can set specific default stocking UOMs at more granular levels. These are established at the Subinventory level for an item, and can be further specified at the Locator level. This hierarchy allows an organization to store the same item in different UOMs (e.g., boxes vs. eaches) in different parts of a warehouse, overriding the more general settings.

B. Organization level only: This is incorrect. The organization level defines the primary UOM, but specific default stocking UOMs can be set at lower, more granular levels like subinventory and locator.

D. Organization level, Subinventory level, or both levels: This option is incomplete as it omits the Locator level, which is the most granular level at which a default stocking UOM can be defined for an item.

1. Oracle Fusion Cloud SCM: Using Inventory Management (Release 24B)

Chapter: Manage Inventory Organization and Subinventory

Section: Item-Subinventory Relationship

Content: The documentation states

"You can define item-subinventory relationships that are specific to a particular subinventory... You can optionally specify a default stocking unit of measure

picking rule

and default locator for each item." This confirms the Subinventory level. The same section also details that within the item-subinventory setup

you can specify attributes at the locator level

which includes the UOM.

2. Oracle Fusion Cloud SCM: Implementing Manufacturing and Supply Chain Materials Management (Release 24B)

Chapter: Define Inventory Management

Section: Item-Subinventory and Item-Locator Defaults: Explained

Content: This guide explains that item-specific attributes

including the unit of measure

can be assigned at both the subinventory and locator levels. It describes the hierarchy where locator-specific attributes override subinventory-level attributes

which in turn override the item's primary attributes defined at the organization level. This confirms that both Subinventory and Locator are valid levels for setting these defaults.

An item organization is a fundamental structure in Oracle SCM Cloud used for defining and managing items. One of its key purposes is to serve as the Master organization definition (D). This item master organization acts as the central source of truth for all item definitions and attributes. These centrally defined items, including their sales-specific attributes, are then used as the basis for Sales catalog definition (C) within Oracle Product Information Management (PIM). Items are created in the master organization and then assigned to various sales and operational catalogs.

A. Inventory tracking: This is a function of an inventory organization, which is a specific type of item organization. An item master organization does not track inventory, making this purpose not universally applicable.

B. Financial tracking: This is a primary function of Oracle Financials modules (e.g., Cost Management, General Ledger) and is associated with a business unit, not directly a purpose of the item organization itself.

1. Oracle Fusion Cloud SCM

Implementing Product Management

Release 24B

F93562-02

Chapter 4: Set Up Item Organizations

"Item Organizations: Explained" section. This section states

"An item master organization is a logical entity in which you define items... You must designate one item organization as the item master." This directly supports option D.

2. Oracle Fusion Cloud SCM

Using Product Master Data Management

Release 24B

F93560-02

Chapter 6: Catalogs

"Create Catalogs: Procedure" section. This documentation details how catalogs are created by adding items to categories. The items available for selection are those defined within the item master organization

thus linking item organization to the purpose of sales catalog definition. This supports option C.

3. Oracle Fusion Cloud SCM

Implementing Manufacturing and Supply Chain Materials Management

Release 24B

F93559-02

Chapter 10: Manage Inventory Organizations

"Inventory Organizations: Explained" section. This source clarifies

"An inventory organization is a facility where you store and transact items." It distinguishes this role from the item master

showing that inventory tracking (A) is specific to this subtype of item organization

not a general purpose for all.

In Oracle Supply Chain Orchestration (SCO), when a discrepancy occurs that the system cannot automatically resolve, the affected supply line is categorized as an "Exception." In this scenario, the supplier reduced the quantity, and SCO was unable to find an alternative source for the deficit. This creates a mismatch between demand and supply that requires manual intervention. The "Exception" status flags the supply line for a planner or user to review and take corrective action, such as accepting the change or manually finding another source.

B. Jeopardy: This status typically indicates that a supply order is at risk of not meeting its need-by date, which is a time-based issue, not a confirmed quantity shortage.

C. Error: An error signifies a system processing failure or invalid data. The system is functioning correctly here by identifying a valid business scenario (a supply constraint).

D. Mark for Review: This is a manual action a user can take on a supply line, not an automatic status assigned by the system when it encounters an unresolvable issue.

1. Oracle SCM Cloud

Using Supply Chain Orchestration (Release 24B)

Chapter 4: Monitor and Manage Supply.

Section: Supply Lines with Exceptions: Explained: This section details the conditions that cause an exception. It states

"Supply Chain Orchestration raises an exception when it receives a change request from a supplier or a contract manufacturer for a purchase order or a transfer order... For example

a supplier might not be able to fulfill the entire quantity on a purchase order." This directly matches the scenario in the question.

2. Oracle SCM Cloud

Using Supply Chain Orchestration (Release 24B)

Chapter 4: Monitor and Manage Supply.

Section: Overview of Monitoring Supply Lines: This page describes the infolets on the Supply Orchestration work area

including "Exceptions" and "Jeopardy." It clarifies that Exceptions are for "supply lines that require your attention

" while Jeopardy is for lines "at risk of not meeting the need-by date." This differentiates option A from B.

When the Promising Mode is set to "Supply Chain Availability Search," Global Order Promising (GOP) performs a comprehensive check across the defined supply chain network. Its primary behavior is to first identify and consume existing sources of supply—such as on-hand inventory, scheduled purchase orders, transfer orders, and work orders—before it considers creating new supply. This ensures that current inventory and in-transit materials are prioritized for fulfillment, optimizing the use of existing assets to meet demand.

A. Promises on the requested date: This is a general goal of order promising, not the specific mechanism of the "Supply Chain Availability Search" mode. The ability to promise on the requested date depends on whether supply is found.

B. Assumes supply of item is infinitely available: This describes the "Infinite Availability-Based" promising mode, which ignores on-hand balances and supply schedules, relying solely on lead times.

1. Oracle Fusion Cloud SCM

Using Global Order Promising (Release 24B)

Chapter: Set Up Promising and Sourcing Rules

Section: ATP Rules.

This section details the different promising modes. For "Supply Chain Availability Search

" it states

"Order promising searches for supply across the supply chain and promises against collected supply data. It considers on-hand inventory

purchase orders

transfer orders

and work orders." This confirms the mode's function is to find and use existing supplies first.

2. Oracle Fusion Cloud SCM

Implementing Order Management (Release 24B)

Chapter: Global Order Promising

Section: Overview of Global Order Promising.

This document explains that GOP can promise orders by checking for availability of supplies in the supply chain. The "Supply Chain Availability Search" is the mode that explicitly performs this check against existing and scheduled supplies before considering other options.

for the

complete solution.

Explanation:

Back-to-Back Supply Creation Flows: Make & Transfer in Oracle Cloud

1. Overview of Back-to-Back Supply Creation Flows

Back-to-back (B2B) supply creation flows in Oracle Fusion Cloud allow businesses to generate supply

only when a sales order is placed. The system creates supply documents dynamically based on

sourcing rules and executes supply fulfillment through Manufacturing (Make Flow) or Inventory

Transfer (Transfer Flow).

Each flow follows these key steps:

Sales Order Entry & Scheduling – A customer places an order that requires supply creation.

Supply Order Generation – The system determines whether to manufacture or transfer stock.

Supply Execution – The supply is produced (Make Flow) or transferred from another warehouse

(Transfer Flow).

Receiving & Reservation – The supply is received and linked to the sales order.

Order Fulfillment – The sales order is shipped to the customer.

2. Back-to-Back Supply Creation: Make Flow (Manufacturing-Based Fulfillment)

The Make Flow is used when the item must be manufactured in-house because it is not available in

stock or through procurement. The system creates a Work Order (WO) in Oracle Manufacturing Cloud

and ties it to the sales order.

Step-by-Step Make Flow Process

Below is the step-by-step breakdown of the Back-to-Back Make Flow using Oracle Fusion Cloud

applications.

Step 1: Enter & Schedule Sales Order

The customer places an order in Oracle Order Management.

The system checks stock availability in Oracle Inventory Cloud.

Since no stock is available, Oracle Supply Chain Orchestration (SCO) triggers a supply request.

Oracle Global Order Promising (GOP) determines that the item must be manufactured.

The sales order is scheduled for back-to-back fulfillment.

✅ System Action: The system marks the sales order for manufacturing and creates a supply order.

Step 2: Create & Request Work Order

Oracle Supply Chain Orchestration (SCO) generates a Supply Order.

The system determines that a Work Order (WO) is needed.

A Work Order (WO) is created in Oracle Manufacturing Cloud.

The Work Order is tied to the sales order to ensure the finished goods are allocated for this order

only.

✅ System Action: The system creates a Work Order (WO) in Oracle Manufacturing.

Step 3: Execute Manufacturing Process

The Work Order goes through the standard production process.

Raw materials are issued from inventory.

Production activities are completed.

The final product is reported as complete in Oracle Manufacturing Cloud.

The Work Order is completed, and the finished goods are transferred to Oracle Inventory Cloud.

✅ System Action: The system marks the Work Order as complete and updates inventory.

Step 4: Reserve & Ship the Sales Order

The system reserves the manufactured stock against the sales order.

The order is picked, packed, and shipped from the warehouse.

Oracle Shipping Execution updates the order status.

An invoice is generated in Oracle Receivables.

The sales order is closed.

✅ Final Action: The system completes the order and ships it to the customer.

Oracle Fusion Cloud Modules Involved in Make Flow

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/1Z0-1073-25/page_62_img_1.jpg

for the

complete solution.

Explanation:

Back-to-Back Fulfillment in Oracle Inventory Cloud

Back-to-back fulfillment in Oracle Inventory Cloud is a supply chain process where supply is created

only after a sales order is placed. This process links the demand (customer sales order) directly to the

supply (procurement, manufacturing, transfer, or existing stock), ensuring efficient inventory

management while meeting customer demands. Below is a detailed step-by-step explanation of the

back-to-back fulfillment process.

1. Overview of Back-to-Back Fulfillment Process

The back-to-back (B2B) fulfillment process ensures that supply is created only when a customer order

is received.

Supply is specifically reserved for the sales order until shipping.

This process helps reduce excess inventory while maintaining responsiveness to customer needs.

It supports four fulfillment strategies: Buy, Make, Transfer, and On Hand Reservation.

Back-to-back fulfillment is mainly used in discrete manufacturing environments.

2. Step-by-Step Back-to-Back Fulfillment Process in Oracle Inventory Cloud

The back-to-back fulfillment process consists of the following key steps:

Step 1: Process Sales Order

The sales order is created in Oracle Order Management.

The order is validated for correctness (items, quantities, prices, etc.).

The order is scheduled, and the system checks if on-hand inventory is available.

If no inventory is available, Oracle Supply Chain Orchestration initiates a back-to-back fulfillment

request.

Step 2: Determine Supply Sources

Oracle Supply Chain Orchestration (SCO) determines the best supply source based on predefined

rules and sourcing strategies.

The system evaluates the following supply options:

Buy: Procurement from an external supplier.

Make: Internal manufacturing or contract manufacturing.

Transfer: Movement of inventory from another warehouse or distribution center.

On Hand: Direct reservation of existing inventory.

Step 3: Create and Manage the Supply Order

A supply order is generated in Oracle Supply Chain Orchestration.

The order is assigned to the appropriate fulfillment method:

Buy Order: A purchase requisition is created in Oracle Procurement Cloud, and the supplier provides

the required goods.

Make Order: A work order is created in Oracle Manufacturing Cloud, and production begins.

Transfer Order: A transfer request is initiated in Oracle Inventory Management, moving stock from

another warehouse.

On-Hand Reservation: If stock is available, it is reserved against the sales order.

Oracle monitors the progress of the supply order until completion.

Step 4: Receive and Consolidate Supply in Warehouse

Once supply is procured, manufactured, or transferred, it is received in the fulfillment warehouse.

If it is a purchased item, a receipt is created in Oracle Receiving.

If it is a manufactured item, the work order is completed, and inventory is updated.

The system ensures that the received inventory is linked to the original sales order.

Step 5: Ship to Customer

The sales order is released for fulfillment.

A Pick Release process is initiated in Oracle Inventory Cloud to allocate stock.

The order is picked, packed, and shipped using Oracle Shipping Execution.

A shipping confirmation is generated, and an invoice is created in Oracle Receivables.

The sales order is marked as complete, and the supply order is closed.

3. Detailed Explanation of Back-to-Back Fulfillment Flows

1. Buy Flow (Procurement)

If the supply is sourced externally, the system generates a purchase order in Oracle Procurement

Cloud.

The supplier delivers the goods, which are received in Oracle Receiving.

The inventory is updated, and the order is prepared for shipment.

The sales order is fulfilled once the goods arrive.

2. Make Flow (Manufacturing)

If the item is manufactured internally, a work order is created in Oracle Manufacturing Cloud.

Production is executed, and the finished product is stored in inventory.

The system reserves the item against the sales order.

The order is fulfilled when the product is available.

3. Transfer Flow (Warehouse Transfer)

If the item is available in another warehouse, a transfer order is generated in Oracle Inventory Cloud.

The inventory is moved to the fulfillment warehouse.

Once received, the inventory is reserved and prepared for shipment.

The sales order is completed upon shipment.

4. On Hand Flow (Inventory Reservation)

If the item is available in stock, the system directly reserves it.

The order moves to the shipping phase without additional procurement or manufacturing steps.

The pick, pack, and ship process is executed, and the order is fulfilled.

4. Key Benefits of Back-to-Back Fulfillment in Oracle Inventory Cloud

✔ Reduced Inventory Holding Costs – Stock is only procured, manufactured, or transferred when

needed.

✔ Improved Order Fulfillment Efficiency – Orders are linked directly to supply, reducing delays.

✔ Better Customer Satisfaction – Customers receive products faster with reduced stockouts.

✔ Automated Supply Chain Coordination – Oracle Cloud applications ensure seamless integration

between order management, procurement, manufacturing, and inventory.

✔ Flexibility in Sourcing – Users can choose between procurement, manufacturing, transfer, or

existing stock to fulfill demand efficiently.

5. Oracle Cloud Modules Involved in Back-to-Back Fulfillment

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/1Z0-1073-25/page_48_img_1.jpg

6. Example Use Case: Back-to-Back Fulfillment in Action

Scenario:

A customer places an order for 100 units of Item XYZ, but there is no stock available in the

warehouse.

Solution:

The system checks stock availability and identifies that back-to-back fulfillment is required.

The sourcing rules determine that procurement from an external supplier is the best option.

A purchase requisition is created in Oracle Procurement Cloud.

The supplier delivers the items, and they are received into inventory.

The inventory is reserved against the sales order.

The shipping process is initiated, and the order is delivered to the customer.

The sales order and supply order are closed.