Oracle 1z0-1077-23 Oracle Order Management Cloud Order to Cash 2023 Implementation Professional Exam Practice Test

• A is correct because cost method is the way of valuing inventory and cost of goods sold. Cost method can be defined at different levels of granularity, such as item category, item, or lot. This allows for more flexibility and accuracy in cost accounting1
• B is incorrect because a cost organization must have a primary cost book associated with the primary ledger. A cost book is a set of cost accounting policies and valuation structures that determine how inventory transactions are accounted for. A cost organization can have multiple cost books, but one of them must be primary2
• C is correct because Supply Chain Orchestration is the application that coordinates and executes the fulfillment of sales orders across multiple sources and systems. Supply Chain Orchestration automatically selects the appropriate orchestration process based on user-defined subledger accounting rules when a supply creation is initiated. Subledger accounting rules define how transactions are accounted for in the general ledger3
• D is correct because Landed Cost Management is the application that enables organizations to capture, track, and allocate the actual costs associated with acquiring items from suppliers. Landed cost includes not only the purchase price, but also other charges such as freight, insurance, taxes, and duties. Landed Cost Management gives organizations financial visibility into their extended supply chain costs and helps them optimize their sourcing and pricing decisions.
• E is incorrect because Receipt Accounting is not the application that performs the accrual accounting for all types of receipts. Receipt Accounting is the application that performs the accrual accounting for purchase order receipts, return to supplier transactions, and inventory adjustments. Other types of receipts, such as sales order receipts, are accounted for by other applications, such as Receivables.

References:

1: Cost Methods 2: Cost Organizations and Cost Books 3: Supply Chain Orchestration : Landed Cost Management : Receipt Accounting

A negotiation is a business flow that enables you to create and manage requests for quotations (RFQs) and auctions with your suppliers. A negotiation supports the use of supplier items, which are the items that the suppliers offer to sell to you. You can use supplier items to compare different offers from different suppliers, and select the best one based on your criteria1.

References:

• Overview of Negotiations

Oracle Contract Manufacturing is a feature of Oracle Order Management Cloud Order to Cash that enables you to outsource your manufacturing operations to a third-party supplier. Oracle Contract Manufacturing supports two types of flows: Plan-to-Produce and Back-to-Back fulfillment1. In the Back-to-Back fulfillment flow, the supplier creates the supply based on the customer’s demand, without any prior planning. The Back-to-Back fulfillment flow involves three documents: Work Order, Purchase Order, and Sales Order2. These documents are kept in sync as a parameter setting for the Back-to-Back flow. This means that any changes or updates to one document are automatically reflected in the other documents, ensuring data consistency and accuracy3.

References:

• Overview of Contract Manufacturing
• Overview of Back-to-Back Fulfillment
• Back-to-Back Supply Creation Flows

Extension rules are not part of a Configurator Model Item Snapshot. Extension rules are custom actions that you can define in the Configurator Modeling Environment to manipulate data on sales orders, such as adding, updating, copying, or returning lines1. A Configurator Model Item Snapshot is a copy of the item-based model structure that you import from the Product Information Management work area into the Configurator Models work area2. A Configurator Model Item Snapshot consists of the following components3:

• Item Structure: The hierarchy of the model and its components, including the optional components that can be configured by the user.
• Operational Attributes: The attributes that control the behavior of the model and its components, such as the minimum and maximum quantity, the default quantity, and the pricing attributes.
• User-Defined Attributes: The additional attributes that you can add to the model and its components to capture more information or to control the configuration process, such as the color, size, or style of an item.
• Structure Component Attributes: The attributes that define the relationship between the model and its components, such as the inclusion rule, the exclusion rule, and the compatibility rule.

References:

• Examples of Order Management Extensions for Order Lines
• Import Item-Based Models into Configurator
• Configurator Model Item Snapshot

“Configurator models are imported from items maintained in Oracle Fusion Product Hub (which is accessed by the Product Information Management work area) that have a Structure Type of Model. Only the optional structure and attributes of the product item are imported, because the required elements of the product item cannot be configured by an end user. The option classes and optional standard items for each model item are also imported.”“Configurator models are versioned objects. A model can go through multiple drafts before being released in a series of versions.There can be multiple drafts of the same model being modified at the same time, but they must be in different workspaces. A message notifies you if you add a model to a workspace when another draft exists in another workspace. There can only be a single released version of a model with the same effective start date.”

Make the changes in the Configurator Modeling Environment on the Item Attributes tab of the model’s details.

You can make the changes in the Configurator Modeling Environment on the Item Attributes tab of the model’s details, prior to releasing, to resolve the issue of incorrect minimum for one of your component attributes. Item attributes are user-defined attributes that you can add to an item-based model or its components to capture additional information or to control the configuration process1. You can modify the item attributes in the Configurator Modeling Environment after importing the item-based model structure from the Product Hub2. You can change the minimum value of the component attribute on the Item Attributes tab of the model’s details3.

References:

• Item Attributes
• Import Item-Based Models into Configurator
• Modify Item Attributes

http://docs.oracle.com/cloud/latest/scmcs_gs/FAIMS/FAIMS1796462.htm#FAIMS2605728

A pricing strategy is a pricing entity that defines the overall pricing approach for a market segment. A pricing strategy consists of a header and one or more pricing segments. The header contains the general information and settings for the pricing strategy, such as the name, description, objective, business unit, default currency, start date, and end date1. When creating a pricing strategy header, the following fields are required2:

• Name: The name of the pricing strategy. It must be unique within the pricing business unit.
• Business Unit: The business unit that owns the pricing strategy. It determines the scope and visibility of the pricing strategy.
• Default Currency: The currency that is used for the pricing strategy. It is used to convert the prices of the items that are priced in different currencies.
• Start Date: The date when the pricing strategy becomes effective. It cannot be earlier than the current date.

References:

• Overview of Pricing Entities
• Create Pricing Strategy Headers

Future supply can include the supply that results from planned orders of three types: make, buy, or transfer.

To change the status of a pricing strategy from “In progress” to “Approved”, you must click the Approve button on the Edit Pricing Strategy page. The Approve button is only enabled when the pricing strategy is complete and valid. A pricing strategy is complete when it has at least one pricing segment and one pricing rule. A pricing strategy is valid when it has no errors or conflicts1. By clicking the Approve button, you submit the pricing strategy for approval. The approval process depends on the approval life cycle that you have defined for the pricing strategy. The approval life cycle can include one or more approvers, who can approve or reject the pricing strategy. Once the pricing strategy is approved by all the approvers, the status changes to “Approved” and the pricing strategy becomes effective2.

References:

• How You Modify Pricing Strategies
• How You Approve Pricing Strategies

The Edit Configurator Model page is where you can modify the structure, rules, user interfaces, and connectors of a configurator model in Configurator Cloud. The Structure tab is where you can view and edit the features and options that make up the model structure. The Structure tab has two subtabs: Item attributes and Supplemental Structures1.

• Item attributes are the characteristics or properties of the features and options that participate in the model structure. You can use item attributes to define the behavior and appearance of the features and options, such as the default value, the display name, the data type, and the validation rules2.
• Supplemental Structures are the additional structures that you can create and associate with the model structure. You can use supplemental structures to add more features and options to the model, such as accessories, services, or documentation. You can also use supplemental structures to create different views of the model, such as a technical view or a marketing view3.

References:

• How You Modify Configurator Models
• Overview of Item Attributes
• Overview of Supplemental Structures

Supplier Rebates and Supplier Annual Rebates are both part of Oracle’s Supplier Channel Management. While both types of rebates are incentives offered by suppliers to encourage purchases, they differ in how they are accumulated. Supplier Rebates are typically tied to specific purchases or transactions1. On the other hand, Supplier Annual Rebates are accumulated across multiple orders over a specified time period, often a year21. This allows organizations to track and manage cumulative purchasing volumes over the effectivity of a program2.

References:

• Oracle Documentation: Supplier Rebates
• Oracle Documentation: How Supplier Rebate Works

• Change mode is the way that Order Management handles changes to sales orders during the orchestration process. Change mode determines when Order Management takes a snapshot of the orchestration process and how it applies changes to the fulfillment lines1
• Simple change mode takes a snapshot only when the orchestration process starts. It applies changes to all fulfillment lines regardless of their status1
• Incremental change mode takes a snapshot only when the orchestration process starts. It applies changes only to the fulfillment lines that are not yet completed1
• Advanced change mode takes a snapshot when the orchestration process starts and when a change order is received at an orchestration process step. It applies changes to the fulfillment lines based on the snapshot and the current status of the lines1
• None change mode does not take any snapshot and does not apply any changes to the fulfillment lines1
• Therefore, the correct answer is C. Advanced, because it is the only change mode that takes a snapshot of the following stages: when the orchestration process starts and when a change order is received at an orchestration process step.

References:

1: Change Mode

A workspace is a container that holds one or more models and their associated user interfaces, rules, and data. A workspace enables you to create and manage multiple versions of your configurator frameworks in Configurator Cloud1. The following statements are true about workspaces:

• An effective date must be specified when you create a workspace. The effective date determines when the workspace becomes active and available for use. You can specify a past, present, or future date for the effective date2.
• You can edit both the workspace name and description. You can change the name and description of a workspace at any time, as long as the workspace is not locked by another user. The name must be unique within the Configurator Cloud instance2.
• While creating a workspace, the name must be unique. You cannot create a workspace with a name that already exists in the Configurator Cloud instance. The name must be alphanumeric and can include spaces and special characters2.

References:

• Overview of Workspaces
• Create Workspaces

An orchestration process is a predefined business process that coordinates the orchestration of physical goods and activities within a single order and automates order orchestration across fulfillment systems.

Orders in jeopardy – Details – The Fulfillment Lines in Jeopardy Analysis shows the number of fulfillment lines that are in jeopardy, using a bar for each jeopardy priority that you have defined. For example, a range can indicate high, medium, or low jeopardy priorities. You can click a range bar to drill down to the Manage Fulfillment Lines page, which displays a list of fulfillment lines restricted to the exception type that corresponds to that range, as indicated by an icon in the Exception Type column.

Orders on Past Due – Details and allows filtering based upon :◦Year◦Inventory Organization Name◦Item Name◦Business Unit Name◦Bill-to Customer Name◦Ship-to Customer Name

So Past due seems to give root cause details while Jeopardy gives ranges

https://docs.oracle.com/en/clou d/saas/supply-chain-management/r13-update17d/fascp/manage-order-promising-rules.html#FASCP1127104

ATP Rule Promising Modes: ExplainedThe promising mode of an available-to-promise (ATP) rule determines which set of attributes the order promising logic evaluates when determining ATP results. When creating an ATP rule on the Manage ATP Rules page, the first thing that you must specify is which of the three promising modes is applicable to the ATP rule.

These are the three promising modes:

Supply chain availability search

Lead time based

Infinite availability based

Extensible Flexfield attributes are custom attributes that you can add to Order Management entities to capture additional information that is specific to your business needs. You can use these attributes in approval rules for sales orders to define conditions and actions based on the values of the attributes. The order entities that support the use of Extensible Flexfield attributes in approval rules for sales orders are Header, Line, and Fulfillment Line. These entities have predefined Extensible Flexfield categories that you can configure and deploy in the Setup and Maintenance work area. You can also access and update these attributes in the Order Management work area.

References:

• Overview of Using Extensible Flexfields in Order Management
• Set Up Extensible Flexfields in Order Management
• Oracle Order Management Cloud — Extensions

The values for the attributes that begin with requested, such as the Requested Item attribute and the Requested Ship-from Warehouse attribute, are initially determined by what the values are when you select the line in the Order Orchestration work area. You cannot change the values for many of the requested attributes, such as the Requested Item attribute, the Requested Quantity attribute, and the Requested Ship Date attribute. You can change or clear the values for the Requested Ship-from Warehouse attribute and the Requested Shipping Method attribute. There are also some additional attributes you can change, such as whether substitutions are allowed, to influence the results when you explore other promising option.

Create social conversations only for conversations that the Order Entry Specialist manually initiates for each sales order. It is strongly recommended that you choose Manual.

Fulfillment line and E. Task layer service

Fulfillment line and task layer service are two attributes that are available for selecting a fulfillment system connector. A fulfillment line is a line on a sales order that represents a request for a product or service. A task layer service is a predefined web service that performs a specific task in the fulfillment process, such as shipment, invoice, or payment1. You can use these attributes to create external interface routing rules that route fulfillment requests to your fulfillment system based on the sales order, fulfillment line, or orchestration process attribute2.

References:

• Fulfillment Line
• Task Layer Service
• Route Requests from Order Management to Fulfillment Systems

Supplier part numbers are created and maintained in the Product Information Management functional area. This is where you can define and manage items, such as products, services, and components, that you sell, buy, or use in your business processes. You can also associate supplier information with items, such as supplier part numbers, lead times, and prices. Supplier part numbers are used to identify items that you purchase from suppliers or sell to customers using the supplier’s terminology.

References:

• Overview of Product Information Management
• Manage Supplier Part Numbers

https://docs.oracle.com/en/cloud/saas/supply-chain-management/r13-update17d/faivc/implementing-planning-source-systems-and-profile-options.html#FAIVC134911

Use value set values to determine pricing algorithm.

Pricing Cloud does not support using value set values to determine pricing algorithm. Pricing algorithm is a predefined formula that calculates the price of an item or service. You can use value set values to determine pricing segment, which is a group of customers who share common characteristics and pricing preferences. You can also use new value set domain type as part of a condition, which is a rule that evaluates whether a pricing strategy, segment, or matrix applies to a transaction. You can also use values from a value set in a matrix, which is a table that defines the price of an item or service based on one or more attributes.

References:

• Oracle Supply Chain Management Cloud: Order to Cash Release 12 New Features
• Oracle Supply Chain Management Cloud: Order to Cash Release 12 What’s New
• Oracle Pricing Cloud User’s Guide

The drop ship flow is a variation of the order-to-cash flow, where ordered items are sourced from a supplier1. A revision on a drop ship sales order line to increase the quantity will be accepted only if the requisition is created from the drop ship sales order but the purchase order is yet to be created. This is because once the purchase order is created, the quantity on the sales order line cannot be changed2. If the purchase order is partially or fully shipped by the supplier, the sales order line is also partially or fully fulfilled and cannot be revised.

References:

• How Drop Ship Works in Order Management
• How Order-to-Cash Works in Order Management