CLOUD COMPUTING
CLOUD MANAGEMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
Which three statements are true about the Extensible Flexfields setup for order capture integration? (Choose three.)
|
|
The Extensible Flexfield implementation requires customers to manually map incoming Extensible Flexfield data to all Order Management entities
|
|
|
If the extensible attributes need to be passed to or received from downstream applications, the values must be passed in the payload structure
|
|
|
If the attribute information will be provided during the import process, the values should be provided in the import web service payload structure
|
|
|
The XLST “Copy-of” feature dynamically maps the input Extensible Flexfield to the Order Management entities and the Extensible Flexfield Order Management entity to the SDO/custom node for all Task Layers
|
|
|
The XLST “Copy-of” feature dynamically maps the input Extensible Flexfield to the Order Management entities and the Extensible Flexfield Order Management entity to the SDO/custom node only for the Decomposition (Sales Order Integration), Template Task Layer, and Fulfillment Task Layer
|
Explanation:
Detailed explanation-1: -An extensible flexfield is similar to a descriptive flexfield in that it provides a customizable expansion space that implementers, such as Oracle Fusion Applications customers, can use to configure additional attributes (segments) without additional programming.
Detailed explanation-2: -An extensible flexfield is similar to a descriptive flexfield, but with the added ability for customers to add as many context-sensitive segments to a flexfield as they need. In addition, customers can associate more than one context with any particular row of data.
There is 1 question to complete.