My Oracle Support Banner

BS_STATUS_CODE_GID No Longer a Predefined Variable for Order Release Status Events (Doc ID 2466953.1)

Last updated on NOVEMBER 06, 2018

Applies to:

Oracle Transportation Management - Version 6.4.3 and later
Information in this document applies to any platform.

Symptoms

When adding an order release event, the agent variable $bs_status_code_gid is no longer a predefined variable for Order Release status events. 

ACTUAL BEHAVIOR
---------------
When adding an order release event, the agent variable $bs_status_code_gid is no longer a predefined variable for Order Release status events.

 

EXPECTED BEHAVIOR
-----------------------
It is expected that bs_status_code_gid still be a predefined variable for order release status events.

 

STEPS
-----------------------
The issue can be reproduced with the following steps:

1. For any order release add an event through Actions -> Order Management -> Events -> Add Order Release Events
2. Add an event (i.e. Responsible Party of Buyer, Status of Filing Response and 'Filing Response - Information' for the status code) and click save.
3. A previously configured automation agent is triggered based on the OrsStatusReceived event being raised
4. From the resulting agent logging, it is visible that bs_status_code_gid is not an OR status agent variables and bs_status_code_gid is null

Changes

 

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
Changes
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.