BN Rule Defined in Child Domain is not Applied when Object is Created with an Integration User from Parent Domain
(Doc ID 2610160.1)
Last updated on NOVEMBER 15, 2019
Applies to:Oracle Transportation Management Cloud Service - Version 19 and later
Oracle Transportation Management - Version 6.4.3 and later
Information in this document applies to any platform.
An order base is created through integration in a child domain. A BN rule has been setup for ORDER_BASE_XID.DEFAULT in the child domain that differs from the parent domain. If the order base is created through integration with an integration user that exists in the parent domain, the BN rule from the parent domain applies to the XID of the order base, although said OB is created in the child domain. If the order base is created through integration with an integration user that exists in the child domain, the BN rule from the child domain applies to the XID of the order base, which is the desired behavior.
It is expected that the BN rule configured for the respective child domain to be used at all times, regardless if the integration user is created in the parent domain.
The issue can be reproduced with the following steps:
1. Create a varying BN rule for ORDER_BASE_XID.DEFAULT in a child domain that differs from the parent domain.
2. Send an inbound order base transmission containing an order base to be created in the child domain with the credentials of the integration user of the parent domain.
3. The BN rule of the parent domain for the order base XID will apply, when the BN rule from the child domain is expected
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