Last updated on MARCH 08, 2017
Applies to:Oracle Order Management - Version 12.1 to 12.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.
Q1: Is there any restriction that 855 will only get triggered for orders with source = XML?
Q2: Do we need to make SOLD_TO site as Primary? Is it mandatory? Even though 850 works for SOLD_TO which is not defined as Primary, 855 will not work unless it is primary?
Q3: We have multiple SOLD_TO sites of customer enabled for EDI under one account. In this case it is not possible to make all SOLD_TO's as primary.
Q4: Processed 2 850 for customer 99999 with 2 SOLD TO, both are not primary. But site used for Bill To is Primary. I see 855 for 1 order with BILL TO site TP Code but not for another Order.
Q5: Created 3 sites for specific customer 99999.
cust#99999~Site#999991~OU#888 .. SOLD_TO with primary as N, SHIP_TO with Primary as Y, XML 850/855 enabled
99999~999992~888 .. SOLD_TO with primary as N, SHIP_TO with Primary as N, XML 850/855 enabled
99999~999990~888 .. BILL_TO with Primary flag as N, SOLD_TO with Primary flag as Y, XML 850 not enabled, xml 855 and 810 enabled.
Now i created 2 orders --
1) for customer and site 99999~999991~888 as SOLD_TO, 99999~999990~888 as BILL TO
2) for customer and site 99999~999992~888 as SOLD TO, 99999~999990~888 as BILL TO
Note: Both SOLD_TO sites are not PRIMARY = Y, only BILL_TO site is PRIMARY.
I can see 855 ACK for both these orders even though SOLD_TO is not primary.
Does it mean that it is not mandatory to have order SOLD_TO address as PRIMARY for 855?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms