BRM12 PS6 Docgen Script not Update Invoice Status Correctly. (Doc ID 2936306.1)

Last updated on MARCH 22, 2023

Applies to:

Symptoms

While testing an upgraded Billing and Revenue Management 12.0 with Patch Set6(BRM12 PS6) environment and in one of the unit test case, customer has to run docgen on bulk pending invoices (status 0) around 90 invoices at once. observing that if customer run docgen for say 5 pending invoices (ran this for 3 times in two primary and secondary BRM servers) post docgen, the status update is not correct in each run.

Expected Behavior:
All invoices status in invoice_t should be updated with status = 4 (failed due to Simple Mail Transfer Protocol(SMTP) email delivery fail)

Actual Behavior: First invoice status is updated as 1, all invoices after the first invoice in the list is updated as status 4.

Why the first invoice processing by docgen is updating as 1 instead of 4.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Perform Billing on any 5 accounts using pin_bill_accts
2. Post billing, run invoicing using pin_inv_accts on pending invoices.
3. From $BRM_HOME/apps/pin_inv_doc_gen
run ./docgen.sh

First pending invoice is picked for processing and status is updated to 1 (instead of status 4, this is because email delivery is an issue), then all 4 subsequent invoices are updated correctly as status 4( since delivery failure)

For every invoice poid, docgen utility will do both File Transfer Protocol(FTP) and email.
For some invoice poids, if the docgen tries to email first and then FTP, in these cases status will update as 1. In such cases as an email is failing (due to different issue) the overall status should be 4 but it is considering FTP success and overall success.
For some invoice poids, if the docgen tried to FTP first and then email. In these cases, as the last delivery method email is failure, it will be update status as 4.

Issue here is that, it is only considering the latest delivery method's as overall status but not considering the failed delivery status.

Customer expectation is, If pin_inv_doc_gen fails for one method (Eg: email or FTP) status should be updated as fail (4) , in the current behavior status is updated based on last method of delivery, not considering the previous status of delivery.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.