Incorrect Dates Are Coming To BRM After Flist Is Passed From MW Via JCA Adapter
(Doc ID 1470968.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.4.0]
Information in this document applies to any platform.
In this implementation, CRM sends customer order request which BRM received via MW. Oracle JCA adapter is deployed between Oracle AIA and Oracle BRM.
An issue is observed in UAT instance where in BRM it is getting absolute date (actual date) in one of the field in input flist but this date is coming with -4 hours (i.e. 14400 sec). This has blocked several test cases for UAT.
Recently MPS1 and PS12 are installed and have shared latest Oracle JCA Adapter rar file to middleware (Oracle AIA) for deployment.
This issue is observed during Customer Order Synchronization process where BRM received product purchase request from CRM and MW calls BRM custom opcode. Name of Custom opcode is PCM_OP_LN_POL_CUSTOM_MODIFY_CUSTOMER. This custom opcode is used instead of OOB BRM opcode (PCM_OP_CUST_MODIFY_CUSTOMER) because BRM was getting some additional attributes from CRM during order creation which were required to be stored in BRM. This custom opcode internally calls PCM_OP_CUST_MODIFY_CUSTOMER for creation of service and attach products under it. The log shows for example,
Here, PIN_FLD_START_T is coming with -4 hours. Instead of Apr 30 00:00:00 2012, it became Apr 29 20:00:00.
Installed MPS1 and PS12.
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