1. Implementing Order Management
  2. Create Your Service Mapping

Create Your Service Mapping

Learn how to use a service mapping when you integrate Order Management with another Oracle application.

Understand Service Mapping

mapping of Service Mapping.

Note

Object

Description

Context

You specify the context for each service mapping. The context is the overall container for all objects that you create in your set up.

Entity

Specify the structure of each object. Examples of an entity include the order header, fulfillment line, purchase order request, and so on.

Source

Create what your mapping uses as the source for attribute values.

Service

Specify the attributes to send to your fulfillment system. You use it in the output that communicates with the fulfillment system. For example, in the structure of the SDO.

Algorithm

Optional. Instructions that implement complex logic.

Use the Pricing Administration Work Area

the Pricing Administration Work Area.

Note

  • You use the Pricing Administration work area to leverage the service mapping functionality that Pricing Administration provides, but you aren't setting up pricing.

  • Make sure you have the privileges that you need to administer Order Management. Don't sign in pricing privileges.

  • Go to the Pricing Administration work area.

  • Click Tasks, then, under Order Management Configuration, click a link.

  • Don't click links under Pricing Configuration.

Use Predefined Mapping

a Predefined Mapping.

Note

  • Click Manage Service Mappings.

  • Click FulfillmentIntegration. Use this predefined mapping for your deployment.

  • Reduce maintenance and troubleshooting. Use predefined entities instead of creating new ones.

  • If the entity name doesn't include suffix _Custom, then its predefined.

  • If you create a new entity, then use suffix _Custom. Enter a complete description of what it does.

  • To modify a service mapping, you must first create a sand box. For details, see Create a Sandbox So You Can Edit Service Mappings.

Specify Source

tab Sources on service mapping.

Note

  • Click the Sources tab on service mapping.

  • Use a predefined source, when possible.

  • Use predefined entities on each source, when possible.

  • View object specifies the view object to use as the source for the value.

  • Don't modify the view object of a predefined entity.

  • View object attribute specifies the attribute in the view object to use as the source for the value. Do specify the view object attribute.

If you select a new source from a predefined entity, then you must add a suffix to entity name.

Flexfield

Suffix

Descriptive flexfield

DFF_Custom

Extensible flexfield

EFF_Custom

Global descriptive flexfield

GDF_Custom

To improve readability, include an underscore ( _ ) immediately before the suffix.

myDescriptiveFlexfield_Dff_Custom

Specify Service

tab Services on service mapping.

Note

  1. Click the Services tab on service mapping.

  2. Select a predefined service, such as InvoiceService.

  3. Set the Implementation Type attribute to Algorithm.

  4. If you plan to use an integration algorithm, then enter the name of your integration algorithm in attribute Implementation. If you don't set this value, then the service won't call your algorithm.

  5. Select a predefined entity, such as ARInterfaceLine, when possible. Specify whether your fulfillment system can read or write the entity.

  6. Add the attributes that you must integrate with your fulfillment system. Specify whether your fulfillment system can read or write the attribute.

    It typically isn't necessary to specify an alias for a predefined entity or attribute.

Related Topics