My Oracle Support Banner

Is it Possible to Disable Customer Cross Reference Validation when invoking an Activity or Fulfillment Task (Doc ID 1674497.1)

Last updated on JANUARY 25, 2017

Applies to:

Oracle Fusion Distributed Order Orchestration - Version to [Release 1.0]
Oracle Fusion Order Management Cloud Service - Version and later
Information in this document applies to any platform.
***KM Review - Dec 2016 - Checked for Relevance***


Is it possible to Disable Customer Cross Reference Validation when invoking the Activity or Fulfillment Task Layer ?

We have defined a Source System where there is no requirement to provide Customer Information and therefore no Customer Cross Reference Data has been loaded. The Order Orchestration Process is failing:

There is no requirement for Customer Cross Reference data to be loaded for the Source System XXXXXX.

This note was written to describe a Requirement where the customer is invoking a call to an activity or fulfillment Service where the Source System does not require customer information to be passed to it. The activity is not dependent on any customer information and does not require this in any payload. Xreferencing is by default enabled when invoking Activity or Fulfillment Task Layer to ensure that the correct xreferenced details are passed. In instances where the customer has no requirement for the xreferenced data to be resolved and included in the payload a parameter (RESOLVE_XREF_FOR_CUSTOMERINFO) has been provided which will prevent the xreference process from being invoked.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.