IRL NF XML Ref NF Tag Stays In 302 Status In PO Triangulation Scenario
Last updated on JANUARY 12, 2018
Applies to:Oracle Retail Fiscal Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
Under the PO triangulation scenario, if one of the NF in the worksheet status has been manually entered using ORFM fiscal header screen and later the other NF is included in IRL INPUT folder as a NF XML, for which the NF-e XML NF Ref group, RefNFe or RefNF group is informed and references the former NF (the one already in RFM), then when IRL processes the file, it should validate the existence of the other NF in RFM and if it exists, it should proceed automatically till the NF is created and have both NFs validated in RFM, if no issues are found during the processing.
However, IRL uploads the NF XML, but the IRL processing of the NF gets terminated with status 302 (Waiting Associated Document) even though the referenced NF has been informed in NF Ref group (RefNFe or RefNF group) and that referenced NF was previously manually entered and is in the worksheet status.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms