My Oracle Support Banner

E1: 76B: (R76B561) Fetch Issue For NF Print With Decimals Split Line Gives Error 0425 (Doc ID 2500501.1)

Last updated on JULY 21, 2020

Applies to:

JD Edwards EnterpriseOne Sales Order Processing - Version 9.2 and later
Information in this document applies to any platform.



When running R76B561-NFe Generation system fails to fetch a record when order line number is split  and Nota Fiscal  is printed. The symptom occurs when a sales order with more than one line, and only one of these lines is processed, (for example order has 6 lines but only line 1.00 is processed), and the non processed line number has decimals added by Shipment Confirmation-P4205 on select location option, (example 1.001), and there is not order activity rules from the status of the first line with the status of the second line, the system generates error 0425 in the Work Center.

The issue can be reproduced at will with the following steps:

Activate Brazilian Localization
1.  Setup Activity Rules for VO/S Sales Order, and NS/S Nota Fiscal where (598) status represents when the XML is generated and send to the government. Other possible status are allowed but not to re-print (598) in this process.
2.  Item exist in different locations/lots
3.  Create Sales Order with only one line / location
4.  P4205-Shipment confirmation select partial units for the original location and the rest for another location, originating the line to split . Now the order has two lines, 1.000 ad 1.001.
5.  Run R42520 - Print pick slip
6.  Run R76558B Generate Nota Fiscal for line 1,000.  Before running R76558B for line 1,000 statuses shown are: (F4211) 1.000 560/595, 1.001 914/560 and (F7611B) N/A N/A
7.  Go to Nota Fiscal Inquiry -P7610B and adjust dates
8.  Before running Nota Fiscal Electronic Info Generation UBE for line 1,000 the statuses in lines are: (F4211) 1.000 595/597 1.001 (F7611) N/A
9.  Run R76B561 for NF number and series for line 1.000 (version 39)
10. Make sure first line was successfully processed looking at the statuses. (F4211) 1.000 597/598, (F7611B) 1.000 597/598
11. Now run R76558B Generate NF for line 1,001. Verify that before the run statuses are:( F4211) 1.000 597/598 and line 1.001 914/560 . In (F7611B) 1.000 597/598
12. Check line statuses before running R76B561 for lines (F4211) 1.000 597/598, 1.001 914/595 and in (F7611B) 1.000 597/598 and 1.001 595/597
13. Run R76B561 for NF number and series, for line 1.001 
14. XML report shows error : Errors were found during the NF-3 and or DANFE generation for this NF. Please review WC for errors.
15. WC error message states: STATUS FLOW NOT SETUP. CAUSE: The status flow for the entered order type and line type has not been setup in the OAR F40203.
16. R76B561 is ignoring the decimal and trying to fetch LNID 1,000, without considering the decimal positions that are created when the original order line was split during location selection for shipment confirmation.
17. Its presumed that this R76B561 error is encountered when NEXT STATUS of the original sales order line 1.000 (598) does not exist as Other or next status allowed equal to next status (598) for line 1.001 In this example, OAR for VO/BS, status 598 does not exist as Other and/or next status in activity Print Nota Fiscal



STATUS FLOW NOT SETUP. CAUSE: The status flow for the entered order type and line type has not been setup in the OAR F40203.


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

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