My Oracle Support Banner

R12: Tax Code re-defaulting after manual adjustment and then changing the Request Date. (Doc ID 987363.1)

Last updated on APRIL 04, 2025

Applies to:

Oracle Order Management - Version 12.0.6 to 12.1.1 [Release 12.0 to 12.1]
Information in this document applies to any platform.

Symptoms


On : 11.5.10.2 version, Transaction Entry
Find when changing the Tax Code on non-associated standard order lines, and then changing an attribute (eg. Request Date) on an additional ATO Model line, the Tax Code is re-defaults to the Tax Code assigned on the Model line when the attribute change is made and saved.

EXPECTED BEHAVIOR
-----------------------
Expect the standard line Tax Code to remain the same.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an order and create order lines using configurator. Create this order with one model line and other normal lines.
2. Save the order and book it.
3. Update one of the lines ( non-model lines ) to different tax code ( other than what model line has )
4. Update the field 'Estimated Project Completion Date' ( EPCD ) field in Model line in sales order lines form. Save the record.
5. Check that the tax code value which was updated ( in step-3 ) is overwritten by the tax code value of the model line

Cause

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
Symptoms
Cause
Solution
References


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