Implement Customized Mappings for Distributed Order Orchestration (DOO) Extensible Flexfields (EFF) (Doc ID 1512900.1)

Last updated on JANUARY 12, 2017

Applies to:

Oracle Fusion Distributed Order Orchestration - Version 11.1.4.0.0 to 11.1.7.0.0 [Release 1.0]
Information in this document applies to any platform.
***KM Review - Dec 2016 - Checked for Relevance - Release 7 Specific***

Goal

NOTE: for Release 8 or later please reveiw Fusion DOO: Implementing and Populating Extensible Flex Fields (EFF) in DOO (Doc ID 2005737.1)

This Note describes how to customize xsl mapping to implement User defined Flex Contexts. After customization and redeployment of the composite, users can pass the flex attributes to be stored with the order and also interface the flex attributes to Fulfillment Systems
Following pre requisite steps are mandatory:

Define Flex Contexts
Deploy Flex
Synch SOA MDS Artifacts
Establish Jdev environment so that it can access  with MDS
Obtain Composite SAR that needs to be enabled for Flex

Pre-requisite steps are described in:

<Document:1512827.1> - Configuring Jdev for Distributed Order Orchestration (DOO) customizations
<Document:1512534.1> - Create an Extensible FlexField (EFF) on a DOO Entity
<Document:1525866.1> - Assign DOO Orchestration Process based on an EFF value - OBR Rules

There are 9 categories available for defining Contexts and the steps outlined in the document are applicable for any of the categories. Use case will take Decomposition Composite - DooDecompTransformSalesOrderComposite as an example.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms