1z0-1077-23 Questions and Answers

Rule conditions are the Oracle Business Rule component that determines the specific rule that will be used to transform the imported orders. Oracle Business Rules are a set of logic statements that define the behavior of an application or a process, such as order transformation, order orchestration, or order approval1. A rule consists of two parts: a condition and an action. A rule condition is a statement that evaluates to true or false based on the input data, such as order attributes, order lines, or order status. A rule action is a statement that performs a specific task or operation when the rule condition is true, such as updating order attributes, creating order lines, or changing order status2. You can use the Manage Order Transformation Rules task to define the rule conditions and actions for transforming the imported orders from a legacy system into Oracle Order Management Cloud3.

References:

• Overview of Using Business Rules with Order Management
• Oracle Business Rules
• Manage Order Transformation Rules

Only customer shipments from warehouses are supported.

Shipping tolerances are not limited to customer shipments from warehouses. They also support drop ship orders, where ordered items are sourced from a supplier1. Shipping tolerances are the acceptable variations in the quantity shipped for an order line, expressed as a percentage of the ordered quantity2. You can set up shipping tolerances in Order Management to handle over-shipments and under-shipments of order lines3.

References:

• How Drop Ship Works in Order Management
• Guidelines for Setting Up Shipment Tolerances
• Set Up Shipping Tolerances in Order Management

A pricing segment is a pricing entity that defines a set of conditions that must be met for a pricing strategy to apply. A pricing segment can include attributes such as customer, customer category, item, item category, order type, and so on. By creating a pricing segment for the specific customer, the client can set conditional logic around the customer without changing the pricing strategy for all other customers1.

References:

• How Profiles, Segments, and Strategies Work Together

By building two separate user interfaces and for each UI and selecting the corresponding application under Applicability Parameters in the user interface setup.

This answer is correct because it allows you to create different user interfaces for different hosting applications, and control the visibility and behavior of each UI based on the applicability parameters. You can use the User Interface Setup task in the Setup and Maintenance work area to create and manage user interfaces for Oracle Order Management Cloud Order to Cash1.

The other answers are incorrect for the following reasons:

• By building this using different languages; for example, you can have the first hosting application to provide access by using American English and the second hosting application to provide access by using British English: This answer is incorrect because using different languages does not change the user interface design or functionality. It only changes the language of the labels and messages that are displayed to the user.
• By doing nothing. You cannot have more than one UI based on different applications that are accessing it. All users will have to use the more simplified method: This answer is incorrect because you can have more than one UI based on different applications that are accessing it. You can use the applicability parameters to specify the hosting application for each UI, and the order of precedence to determine which UI to display when there are multiple matches1.
• By using Dynamic Tree Navigation and making the first question that users are prompted with to be related to the interface that they want to use: This answer is incorrect because Dynamic Tree Navigation is a feature that enables you to create a guided selling experience for configurable products. It does not allow you to create different user interfaces for different hosting applications2.
• By building a Configurator rule that shows different options based on the application that is accessing: This answer is incorrect because Configurator rules are used to define the logic and constraints for configurable products. They do not allow you to create different user interfaces for different hosting applications3.

References:

• Overview of User Interface Setup
• Overview of Dynamic Tree Navigation
• Overview of Configurator Rules

A rule that you can set on an orchestration process step that specifies the adjustments to make when an order changes.Undo, Redo, Update, Cancel, and None are each an example of a compensation pattern. For example, assume thecompensation pattern for a Create Shipment step is Redo, and that this step calls the Cancel service and the Create service.If Order Management receives a change order that includes a new warehouse for this step, then it runs the Cancel serviceand the Create service again.

Add a supplemental structure to the root node of the item-based model in the workspace area of the Configurator.

A supplemental structure is a set of predefined questions that you can use to guide customers through the configuration process. You can add a supplemental structure to the root node of the item-based model in the workspace area of the Configurator, and then associate it with a dynamic user interface. This way, the Configurator will display the questions to the customers before showing them the list of accessories and parts that match their needs1.

References:

• How Supplemental Structures Work in Configurator
• How Item-Based Models Work in Configurator

Profitable-to-promise (PTP) is a Global Order Promising mode that allows you to override the normally used source by considering the item cost in your organization, transfer-cost between internal organization, and inbound transit cost from a supplier. PTP selects the most profitable fulfillment location that meets the customer’s needs, by comparing the total cost and revenue of each potential source. PTP can also factor in the impact of discounts, taxes, and currency conversions on the profitability of each source.

References:

• Global Order Promising Data Sheet
• Oracle Fusion Cloud Order Management Global Order Promising Solution Brief
• 4 Stages of Oracle Global Order Promising (GOP) in Make-to-Order Production Systems

A processing constraint is a rule that controls the changes that can be made to an order or a fulfillment line at various stages of the order-to-cash process. A processing constraint can be based on various attributes, such as the order type, the fulfillment line status, the ship-from warehouse, and the extensible flexfield1. An extensible flexfield is a custom attribute that you can use to capture additional information that is not provided by the predefined attributes2. To set up a processing constraint based on an extensible flexfield, you need to run the “Publish extensible flexfield” process after you create or modify the extensible flexfield. This process enables the extensible flexfield to be visible and usable in the “Manage Processing Constraints” page3. If you do not run this process, the processing constraint will not be enforced when a user updates a fulfillment line that meets the conditions.

References:

• Overview of Processing Constraints
• Overview of Extensible Flexfields
• Create Processing Constraints Based on Extensible Flexfields

The Quick Availability Check REST API is a feature of Global Order Promising that allows you to provide supply information for e-commerce and order capture applications. This feature uses the method of providing quantity available today or future date to check availability. This means that it returns the quantity of supply that is currently available in your supply chain for a given item, organization, and date. It also considers the allocation rules and the supply sources that you have defined in Global Order Promising.

References:

• Quick Availability Check
• Global Order Promises REST Endpoints
• About the REST APIs

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

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

The back-to-back fulfillment process is one in which specific sales order demand triggers supply creation, and a link is established between the sales order and the supply.

Order extensions are custom actions that you can define to manipulate data on sales orders, such as adding, updating, copying, or returning lines1. You can use order extensions to handle order revisions from customers, such as adding additional products or services to support items they have already ordered2. The four types of line actions that can be executed by this extension feature are:

• Copy: This action creates a new line by copying an existing line on the same order. You can specify the attributes to copy and the attributes to change on the new line1.
• Update: This action updates one or more attributes of an existing line on the order. You can specify the attributes to update and the new values for them1.
• Create: This action creates a new line on the order. You can specify the attributes and values for the new line1.
• Return: This action creates a return order line for an existing line on the order. You can specify the attributes and values for the return line1.

References:

• Examples of Order Management Extensions for Order Lines
• Overview of Order Management

To enforce the requirement that the front camera option is not available when the customer chooses the widescreen display, the client needs to use two configurator model components: configurator rules and model structure. Configurator rules are the logic and constraints that define the valid and feasible configurations for a product or service. Model structure is the hierarchical representation of the features and options that the customer can select1. By using configurator rules and model structure, the client can create a conditional expression that hides or disables the front camera option when the widescreen display feature is selected.

References:

• Overview of Configurator Models

These are the two reasons why the Extensible Flexfield (EFF) is not visible in the order capture additional information section. An EFF is a user-defined flexfield that you can use to capture additional information on sales orders, such as trade compliance, call center details, or source order status1. To make an EFF visible in the order capture additional information section, you need to perform the following steps2:

• Associate the EFF context with the page: You need to specify which page in the Order Management work area will display the EFF, such as the order header or the order line. You can use the Pages tab in the Manage Order Extensible Flexfields task to associate the EFF context with the page.
• Publish the custom extensible flexfields: You need to deploy the EFF to the database and make it available for use. You can use the Deploy Flexfield task to publish the custom extensible flexfields.

References:

• Overview of Setting Up Extensible Flexfields in Order Management
• Set Up Extensible Flexfields in Order Management
• [Manage Order Extensible Flexfields]
• [Deploy Flexfield]

Service mappings are used to integrate Order Management with other Oracle applications by mapping attributes from a sales order to a purchase order. Service mappings enable you to pass order information from a sales order to a purchase order document, such as supplier, item, quantity, price, and so on. To use service mappings, you need three supply chain modules: Supply Chain Orchestration Cloud, Procurement Cloud, and Order Management Cloud. Supply Chain Orchestration Cloud is the module that creates and manages the purchase order document based on the sales order information. Procurement Cloud is the module that provides the functionality to manage suppliers, purchase agreements, and requisitions. Order Management Cloud is the module that captures and fulfills the sales order.

References:

• Use a Service Mapping to Integrate Order Management with Other Oracle Applications
• Overview of Order Management
• [Overview of Supply Chain Orchestration]
• [Overview of Procurement]

A shipment comprises a set of shipment lines, grouped by certain common shipping attributes, that are scheduled to be shipped to a customer's ship-to location on a specific date and time. You can include items from different sales orders in a shipment. You can either manually or automatically group shipment lines to create a shipment. The shipment lines are grouped by the mandatory default criteria: ship-from location and ship-to location. However, you may also include additional grouping criteria, such as customer, freight terms, FOB (Free on board), and shipping method.

The Manage Supply executing document creation rule is the configuration that is required to enable the warehouse user to have visibility of both the Transfer Orders and the Sales Orders. This rule determines the type of supply order that is created for each demand line, such as a transfer order, a purchase order, or a work order. You can update this rule to specify the conditions and actions for creating transfer orders for internal material transfers between warehouses1. You can also use this rule to combine visibility of internal and external orders by sending transfer orders to Oracle Order Management Cloud2.

References:

• Manage Supply Executing Document Creation Rule
• Oracle Supply Chain Management Cloud: Order to Cash Release 11 RCD

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

Constraint Definition Language (CDL) is a language that you use to create configurator rules in Oracle Configurator. Configurator rules are statements that define the logic and behavior of a configurable product model. CDL classes are categories of configurator rules that have different purposes and syntax. The valid CDL classes are:

• Default: A rule that assigns a default value to an item attribute or a component quantity when the configuration session starts.
• Constraints: A rule that restricts the values that can be assigned to an item attribute or a component quantity based on conditions.
• Compatibilities: A rule that specifies the compatibility or incompatibility between two or more items, attributes, or quantities.

References:

• Overview of Configurator Rules
• Constraint Definition Language Reference Guide

The Analysis Editor is a tool within Oracle Transaction BI Answers that allows you to create and modify analyses. An analysis is a query that you build to retrieve and present data from a subject area. You can use the Analysis Editor to perform various tasks, such as setting criteria, creating prompts and filters, adding views, and formatting results. Setting criteria is the process of selecting columns and applying filters to specify the data you want to retrieve. Creating prompts and filters is the process of adding user input controls and conditions to limit the data displayed in an analysis.

References:

• Overview of Oracle Transaction BI Answers
• Editing an Analysis in BI Answers

Needs to be run manually for Inventory MINMAX