How to Prevent from Re-defaulting the Tax Code When Using Order Import with Operation = UPDATE? (Doc ID 2062384.1)

Last updated on JULY 26, 2017

Applies to:

Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

How to prevent from re-defaulting the Tax code when using Order Import with Operation = UPDATE?

If we're trying to update Order Line information by Order Import(operation = UPDATE) then Tax classification is changed to Default Tax.
If we update the Order Line information via core Order Line form(OEXOEORD) then Tax classification is not changed.
This behavior is occurring only when using Order Import(operation = UPDATE) program.

Reproduce Steps
The issue can be reproduced at will with the following steps:

1. Create a new Order with Tax Code = VAT10%, Entered status (not booking).
2. Need to modify some order line information like Quantity so enter some required information into the order interface tables with 'operation = UPDATE'.
3. At this time Order status is still 'Entered' and Tax Code is VAT10%.
4. Run the Order Import concurrent.
5. After running the Order Import, the Quantity is changed as expected but Tax Code is also changed to 'VAT0%'.
Then Tax amount is re-calculated.

To overcome re-defaulting issue we added following statement to disable the dependency between Tax Date and Schedule Ship Date/Promise Date so on
but this behavior is still occurring.

x_extn_dep_tbl(l_index).source_attribute := OE_LINE_UTIL.G_SCHEDULE_SHIP_DATE;
x_extn_dep_tbl(l_index).dependent_attribute := OE_LINE_UTIL.G_TAX_DATE;
x_extn_dep_tbl(l_index).enabled_flag := 'N';
l_index := l_index + 1;

x_extn_dep_tbl(l_index).source_attribute := OE_LINE_UTIL.G_REQUEST_DATE;
x_extn_dep_tbl(l_index).dependent_attribute := OE_LINE_UTIL.G_TAX_DATE;
x_extn_dep_tbl(l_index).enabled_flag := 'N';
l_index := l_index + 1; --

x_extn_dep_tbl(l_index).source_attribute := OE_LINE_UTIL.G_PROMISE_DATE;
x_extn_dep_tbl(l_index).dependent_attribute := OE_LINE_UTIL.G_TAX_DATE;
x_extn_dep_tbl(l_index).enabled_flag := 'N';
l_index := l_index + 1;
  

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms