Use Descriptive Flexfields in Your Integration

Apply these guidelines when you use a descriptive flexfield to integrate Order Management with another Oracle application.

Understand How You Use a Descriptive Flexfield

Note

1. To integrate Purchasing, Shipping, or Receiving, select a predefined source, such as PurchaseRequestSource. Order Management provides predefined descriptive flexfields that you can use. You don't need to create one.

2. Select a predefined entity, such as PurchaseRequestLine.

3. Add the attributes that you must integrate with your fulfillment system.

4. Add the AttributeCategory attribute. This attribute contains the value of the context code, such as ItemPriceForSupplier, of the descriptive flexfield.

5. If your descriptive flexfield uses a context sensitive segment.

   • Provide a value.

   • Reference an attribute in a view object or add an expression.

   • You typically add an expression.

   • If you add a string in your expression, then enclose it with double quotation marks ( " " ).

Reference the Attribute in the View Object

Note

• A view object, such as FulfillLineVO, contains attributes, such as FulfillLineId.

• VO is an abbreviation for view object.

• The value you chose for the View Object attribute determines the values you can select for the attribute View Object Attribute.

Use a Descriptive Flexfield When You Integrate With Accounts Receivable

Note

1. Use a predefined entity for accounts receivable, such as TransactionInterfaceHeaderDff, which is a descriptive flexfield that stores details about the receivables transaction header. Examine the entities that are available on the Entities tab to identify the one you need.

2. Add these attributes. They're all required.

   • FulfillLineId

   • NameSpace

   • XsiType

   • _FLEX_Context

   You must add these attributes for each context entity that you define for a descriptive flexfield.

3. Add the descriptive flexfield attributes that you must send to accounts receivable, such as GlobalSegment1_Custom.

Note

• You can map an interface line of type Line.

• You can't map an interface line of type Discount, Charge, or Freight.

• You can use only one context for each descriptive flexfield.

• To avoid an SQL exception, make sure the web service you use to send fulfillment lines from Receivables to Order Management includes no more than 10,000 fulfillment lines in each invoice response.

If you must map an attribute from the order header, extensible flexfield, or fulfillment line detail, then you must use an integration algorithm. Order Management uses this hierarchy.

Order header
  Fulfillment line
    Fulfillment line details

Other Oracle applications might not organize these objects into a hierarchy. Instead, they might represent them in a single object named ARLine. ARLine also includes descriptive flexfields, so it can represent the same data that the fulfillment line represents. If you must copy attributes from the fulfillment line to ARLine, then you require an integration algorithm only if you must implement conditional logic.

Specify the Source

Note

1. Click the Sources tab.

2. Query the Source for InvoiceSources.

3. Query the Entity for your entity, such as TransactionInterfaceHeaderDff.

4. Add your custom attributes. Create an expression for each of them.

5. Enter a value for NameSpace and _FLEX_Context from the XML file.

6. Enter a value for XSiType from the XSD file.

For example:

Attribute	Expression
GlobalSegment1_Custom	As an option, add an expression. For example: "Gl1"+ProductNumber.substring(0,Math.min(11,ProductNumber.length)) Note that this example is a concatenation. Here's the pseudocode. Send the product number. If the product number is a number, then convert it to a string. Add the length of the string.
NameSpace	Enter the value from the XML file you downloaded for your flexfield archive. For example: "http://xmlns.oracle.com/apps/financials/receivables/transactions/shared/model/flex/TransactionHeaderDff/"
XsiType	Enter the value from your XSD file. For example: "TransactionHeaderFLEX"
_FLEX_Context	Enter the value of the context code from the XML file you downloaded for your flexfield archive. This example uses GlobalSegment1, so you can leave _FLEX_Context empty. If you didn't include a global segment in this example, you would enter "ItemPriceForSupplier".

Specify the Service

Note

1. Click the Services tab.

2. Query the Service for InvoiceService.

3. Query the Entity for your entity, such as TransactionInterfaceHeaderDff.

4. Add your custom attributes. Create an alias for each one. The alias is the name of the service. Get it from your XML file.

   Attribute	Alias
   GlobalSegment1_Custom	_AR_5FRRRF_5FDFF_5FRCT_5FGlobal_2D1 Order Management uses this value when it creates the payload to create the task. If you prefer to send this value in your integration algorithm, then you add it to the algorithm instead.

5. Add the predefined attributes. It isn't necessary to define the alias for predefined attributes.