Orders Not Submitted To AIA Due To Account Blocking In Resequencer
(Doc ID 1284354.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Communications Integration Pack for Order to Billing - Version 2.5 to 2.5 [Release 2.5]
Information in this document applies to any platform.
In the order submissing process from Siebel to AIA, some orders sent from Siebel get an account (the account associated to the order) lock in oraesb aia schema in table esb_group_status in two columns: error and lockconid. This lock makes impossible to send orders to those accounts. If we change the value of column error to 0 and value of column lockconid to NONE the order is re-processed.
1- Why is the acount locked?
2- In what situations is the account lock?
3- Sometimes the lock happens in column error (with value = 1) and other time in column lockconid (changing value from NONE to another one). Why is this? What is the meaning of these columns?
We would like to know why an error happens if, without any correction (only by unlocking the account), the order is sucessfully submitted.
Is the error visible in any other place (like bpel console) besides the esb_group_status table (using sql directly)?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!