Overview of Using Extensible Flexfields in Order Management
Set up an extensible flexfield so you can add your own attribute to Oracle Order Management.
An extensible flexfield is a field you can use to capture details in a sales order that are unique to your business requirements. Each sales order in Order Management comes predefined with a lot of attributes, but you might need one that's specific to your needs.
You can use the details in an extensible flexfield to help automate your processes, send and receive details when communicating with systems outside of Order Management, or provide the criteria to use in a complex business rule. For example:
-
Capture consumer details in an extensible flexfield, then use them to add free samples to a shipment.
-
Capture customer loyalty details in an extensible flexfield, then determine whether to call the customer or upgrade shipping priority.
-
Receive a sales order request that includes unique build specifications from your customer, store them in an extensible flexfield, and then route the sales order to different manufacturing facilities according to the specifications.
-
Select and ship a bottle of wine according to your customer's dining preferences. Store these preferences in an extensible flexfield.
-
Store an order entry clerk's user ID when they submit a source order from a source system.
-
Track source orders that include warning messages from a source system.
-
Store the original schedule date and the new schedule date on the order line so you can track and report scheduling throughout the fulfillment lifecycle.
Examples
|
Example |
Description |
|---|---|
|
Get details from a source system. |
Get source order details from one or more source systems. A source order is an order that you import into Order Management from a source system, such as from an upstream channel. A source order contains a set of attributes. If you need details or attributes that the source order doesn't contain, then you can use an extensible flexfield to get them, and use these details during order fulfillment. You can use the same extensible flexfield attributes to receive details from each source system, or use different extensible flexfield attributes according to each source system's unique requirements. |
|
Send details to a fulfillment system. |
Order Management sends a fulfillment request that includes a predefined set of attributes to a fulfillment system. You can use an extensible flexfield to send details that these attributes don't include, but that the fulfillment system needs to finish the fulfillment request. |
|
Integrate with systems outside of Order Management. |
See Overview of Using Flexfields to Integrate Order Management with Other Oracle Applications. |
|
Receive details from a fulfillment system. |
A fulfillment system might send attributes that provide a business value, and that you must view in the Order Management work area and in the source system. In some situations, Order Management might also use these details in the next set of fulfillment tasks that it runs. You can use an extensible flexfield to receive these attributes. |
|
Write a business rule. |
|
|
Manage change. |
Use an extensible flexfield to store details about a change that happened. For example, use it as input to calculate the cost of change and to select a compensation pattern when Order Management receives a change order. |
|
Display attributes in the Order Management work area. |
Search for sales orders in the Order Management work area according to the value of an extensible flexfield. |
Examples with Orchestration Processes
|
Example |
Use an Extensible Flexfield To |
|---|---|
|
Assign an orchestration process. |
Automatically assign an orchestration process. |
|
Set up an orchestration process. |
Determine branching and identify the fulfillment tasks to run. |
|
Select the fulfillment lines to process. |
Determine whether a fulfillment task will process the fulfillment line or ignore it. |
|
Calculate the lead time that an orchestration process step requires. |
Calculate lead time according to your data. For example, create an extensible flexfield named Engraving that includes a Yes or No value, then set up conditions. If the item is a silver cup, and if Engraving contains:
|