My Oracle Support Banner

Inbound Message Failure for Same Membership When Created with a Few Minute Time Gap (Doc ID 3067513.1)

Last updated on JANUARY 15, 2025

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 5.1.0.0.0 to 5.1.0.0.0 [Release 5.0]
Information in this document applies to any platform.

Symptoms

On RMB v5.1.0.0.0, Inbound Message failure for same Membership when created with less time gap.

If there are two inbound Messages with a few minutes gap in Creation Date Time, first inbound message has a valid error, second inbound message should process but it is Failing with below error message.

ERROR MESSAGE
-------------
An inbound message from the external source system already exists in the Pending, Validation, or Processing status.

STEPS
----------
1. Prepare a inbound inb1 which has some unique external source id, let's say "23450719". Provide the incorrect health plan name to the inbound.
2. Just create a inbound in pending state but do not submit it for processing.
3. Provide the correct health plan name to the same inbound inb2 and keep it in the pending state, do not submit it for processing.
4. Creation time gap should be of 1 min in between the inbounds.
5. Run C1-HCEXS batch.
6. Verify the maximum retry count on the algo "C1-TODORETRY".
7. Before reaching the maximum count, both the inbounds should be in pending state.
8. If the maximum retry count on algo C1-TODORETRY is configured as 2, then run the batch C1-HCEXS for 3 times. On the first 2 runs of C1-HCEXS, both the inbounds will be in pending state, after the completion of 3rd run of        C1-HCEXS batch, inb1 status should be updated to "Voided" and inb2 status should be "Processed" successfully.

Note: External source id should be same for both the inbounds. Also run the batch on multithread.

ACTUAL BEHAVIOR
-----------------------
If inb1 & inb2 has same external source id & inb1 has some valid error & inb2 is correct inbound, then after the run of C1-HCEXS batch, both the inbounds are failing with mentioned error.

EXPECTED BEHAVIOR
-------------------------
Incorrect inbound should be voided & correct inbound should be processed next.

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