E2: 42: Enhancement Request to Optimize the Code of Print invoice(R42565 )

(Doc ID 2261340.1)

Last updated on MAY 02, 2017

Applies to:

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


The issue is related to the implementation of the Outbound Inventory Management Enhancement. When an Internally Owned Shipment has been excluded by R42565 Print Invoices it may cause the report to process the next order line with incorrect line type constants. To explain this problem we have to examine the code that is excluding the Internally Owned Shipment.


Figure : Except of R42565 Event Rules

In the code listing above you will notice that R42565 Print Invoices will stop processing an order line (1) ones it has detected that it is an Internally Owned Shipment and the related processing option hasn’t been activated. This prevents the report of keeping track (2) for which line type it retrieved the line type constants.
In the situation where orders with different line types are processed in one run, this leads to incorrect behavior as shown in the table below.

Table: Line Type Processing

Because the Stored Line Type is not updated for an Internally Owned Shipment, R42565 Print Invoices thinks it retrieved the line type constants for line type ‘S’ but in fact it retrieved the line type constants for line type ‘D1’. This causes order number 3 to be processed with the incorrect line type constants.
As a result of this logic, the following piece of coding will be executed by R42565 Print Invoices, clearing the invoice number and invoice date.

Figure: R42565 Event Rules

Note that the next and last status are not updated, causing the order to advance its status without invoice number and invoice date.
To resolve the issue that the incorrect line type constants are being used, the logic to skip the Internally Owned Shipment needs to be moved outside of the If statement.

Figure : Code correction

To solve the issue that the next and last status are being updated, the assignment statements need to be uncommented.

Figure : Code correction


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