1. Implementing Order Management
  2. Overview of Setting Up Extensible Flexfields in Order Management

Overview of Setting Up Extensible Flexfields in Order Management

Use a hierarchy to specify how you want to display an extensible flexfield in the Order Management work area.

Here's the hierarchy:

hierarchy of an extensible flexfield

Note

  1. Order Management Entity. The top-level object in the hierarchy. You can specify one of these entities:

    • Header Information. Store details about the order header.

    • Order Line Information. Store details about the order line while Order Management processes the order line.

  2. Extensible Flexfield. Each flexfield includes categories, contexts, and segments.

  3. Extensible Flexfield Category. Organize your data into a category according to attributes that contain similar business data. Specify where to display the flexfield in the Order Management work area, such as on the order header. You can use only one category for each entity.

  4. Extensible Flexfield Context. Specify how to display the attribute. For example:

    • Specify criteria that determines the attribute to display.

    • Type of interface element that will display the attribute, such as text box or list of values.

    • Whether the Order Entry Specialist can view or edit the attribute.

    • Validation to do on the attribute.

    • Help text to display for the attribute.

    • Data type of the attribute.

    • Table column that stores the attribute.

    You can specify one or more contexts in each category.

  5. Extensible Flexfield Segment. Specify the attributes. The segment is equivalent to a sales order's attribute. Each context includes one or more segments that you can use to specify the order's attributes that store your data. You can specify one or more segments in each context.

Consider an example:

An extensible flexfield segment

Note

  • Context1 stores details about trade compliance.

  • SegmentA references an attribute that stores the compliance description.

  • SegmentB references an attribute that stores the compliance date.

  • Context2 stores details about the call center representative who manages details about trade compliance.

  • SegmentF references an attribute that stores the representative name.

  • SegmentG references an attribute that stores the name of the person who manages the representative.

This example displays an extensible flexfield in the Order Management work area:

example that displays an extensible flexfield in the Order Management work area.

Note

  1. Additional Order Information. Part of a dialog that displays when you click Additional Order Details on the order header in the Order Management work area.

  2. Manage Order Extensible Flexfields. The page that you use in the Setup and Maintenance work area to set up your flexfield.

  3. Additional Header Information. Specify the data to display and how to display it.

  4. Pages tab. Specify each area where you want to display your flexfield. In this example, the Pages tab specifies one area named Compliance Info and another area named HeaderEFFDetails. The example displays HeaderEFFDetails in the dialog. You can specify one or more areas, and you can specify one more contexts in each area.

    In this example, the Pages tab specifies HeaderContext1 and HeaderContext2. However, for brevity, the screen capture displays only HeaderContext1. The Sequence specifies the sequence to use when displaying these contexts, with 1 at the top, 2 below 1, 3 below 2, and so on.

  5. Sequence and Display Name for page. Specify the name of each category to display in the dialog. Sequence specifies the sequence to display the pages in the dialog. In the example, the Sequence is 10 for Compliance Info and 20 for HeaderEFFDetails, so the dialog displays Compliance Info first, then HeaderEFFDetails.

  6. Sequence and Display Name for context. Specify the name of each context to display in the dialog. For example, HeaderContext1 organizes similar business data into a concise section of the dialog.

  7. Context Sensitive Segment. Specify one or more segments to display details for each attribute. The Sequence specifies the sequence to use when displaying segments in the section. You can specify these segments in each context:

    • 20 character segments. You can use up to 150 characters for each character segment.

    • 10 number segments.

    • Five date segments.

    • Five date and time segments.

Use Categories to Specify Where to Display Flexfields

You can display an extensible flexfield in different sections of the Order Management work area according to the flexfield's category:

Flexfield Category

Section in the Order Management Work Area

DOO_HEADERS_ADD_INFO

Order header

DOO_FULFILL_LINES_ADD_INFO

order line

Overview of Your Setup

flow to set up and deploy an extensible flexfield in Order Management

You do some or all of this set up, depending on your needs. It might be necessary to also do some of this flow when you update your flexfield's set up:

  1. Manage Extensible Flexfields. Use the Manage Extensible Flexfields page in the Setup and Maintenance work area to set up your flexfield. Make sure you deploy and publish your flexfield. See Set Up Extensible Flexfields in Order Management.

  2. Order Management Work Area. Test. For example, click Additional Order Details on the order head then make sure Order Management displays your flexfield as expected.

  3. Manage Order Management Extensions. Use the Manage Order Management Extensions page in the Setup and Maintenance work area to add your flexfield to an order management extension.

  4. Schedule New Process. Use the Publish Extensible Flexfield Attributes scheduled process to make your flexfield is available to various parts of Order Management, other set ups in Oracle Applications, and integrations. This scheduled process updates the dictionaries in business rules, constraints, business events, Integration Cloud Service, and the service mappings that you use for an integration.

  5. Various Set Ups:

    Do This Set Up

    So You Can Use Your Flexfield

    Business Rule

    In a business rule.

    • Routing

    • Assignment

    • Line Selection Criteria

    • Branching Expression

    • Lead Time Expression

    • Compensation Pattern

    • Cost of Change

    You can't use an extensible flexfield in an approval rule.

    Business Event

    To help determine when to use a business event, and the actions to take when you use it.

    Constraint

    To constrain the flexfield.

    Integration Cloud Service

    With Integration Cloud Service to help achieve and manage an integration between Order Management and some other technology or application:

    • Order Import

    • Order Information Service

    • Transportation Management

    • Global Trade Management

    Integration with an Oracle Application

    With a service mapping to integrate with an Oracle application:

    • Oracle Shipping

    • Oracle Receivables

    • Oracle Purchasing

    • Oracle Receiving

  6. Web Service. If you use one of these web services, then manually update your flexfield's set up in the web service payload:

    • CreateOrder

    • FulfillOrderService

    • FulfillmentResponseService

  7. Schedule New Process. Use the Import Oracle Fusion Data Extensions for Transactional Business Intelligence scheduled process to make sure your flexfield is available in the Subject Areas of Oracle Transactional Business Intelligence area. See Overview of Flexfield Change Import.

Related Topics