My Oracle Support Banner

Reason Code Not Populated In Front End When Credit Memos Are Imported (Doc ID 2405874.1)

Last updated on DECEMBER 16, 2019

Applies to:

Oracle Fusion Receivables Cloud Service - Version 11.13.18.02.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.13.18.02.0 version, Billing - Auto Invoice

ACTUAL BEHAVIOR
----------------------------
Reason Code is not populated in Front end when Credit Memos are imported

User is trying to create Credit Memos by inserting data into Interface table and calling the AutoInvoice Import. Reason Code is passed to the interface table as a part of the design. However, when invoice is created the Reason Code is NULL. Tried importing manually through FBDI load and ERPIntegrationService WS Load to Interface and SubmitESSJobRequest. In both the cases, imported invoices do not have Reason Code populated..

EXPECTED BEHAVIOR
-----------------------
Be able to see in the front end the Reason Code.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Populate Autoinvoice Template
2. Review transaction at the line level Reason Code is NULL


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot import transaction with Reason Code populated

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


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