Not Able To Restrict Through Access Group From Inbound Message
(Doc ID 2878980.1)
Last updated on JULY 14, 2022
Applies to:
Oracle Financial Services Revenue Management and Billing Cloud Service - Version NA and laterInformation in this document applies to any platform.
Goal
On : 3.1.0.0.0
Not able to restrict person/account through Access Group from inbound message. Access group not is not present either in account/person clob of inbound message bo:C1-HCInboundMessage.
Not able to provide any other access group other than default one(Default is '***').
Steps to Reproduce
----------------------
• Submit HCInbound message by providing accessGroup(New field under personData & accountData tag ) for customer registration or membership creation.
• After successful process of inbound message, verify the accessGroup for customer and account.
Expected Result
----------------------
• Customer and account should be registered in RMB without any error; access group should be the one, which is provided on inbound message
Actual Result
----------------------
• Not able to provide any other access group other than default one (Default is '***').User wants to restrict the person and account through access group.
Root Cause:
----------------------
Access group input field was not available in inbound request and it was set to default value .
Solution
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
| Goal |
| Solution |
| References |