My Oracle Support Banner

E1: 49: F0411 Record Incorrectly Created if Error Received Running Freight Update (R4981) (Doc ID 2764891.1)

Last updated on MARCH 30, 2021

Applies to:

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

Symptoms

When running Freight Update (R4981) over a shipment with two payable charges that have two different charge codes, if an error occurs during processing, the F0411 record is still created for the 2nd payable charge associated with the shipment. This causes two issues. First, there is a payable charge that should not exist since the batch was in error. No F0911 record is created, so the batch is out of balance if a user attempts to post the batch. In addition, an invoice number is assigned to the voucher created. If the shipment is processed through freight update again, a duplicate invoice number error will be received. The F0411 record must be deleted before freight update is ran again after correcting the error received.

STEPS TO DUPLICATE

Note: The following example shows a PBCO error, but the issue is related to any error received in Freight Update

1. Setup two rate definitions with different payable charge codes on each rate.
2. Setup rates for each rate defintion.
3. In the P4978, setup different GL Class Codes for each charge code.
4. In the carrier master, make sure a carrier is setup with auto pay.
5. Create a rate schedule that includes both rate definitions setup.
6. Add a new route that contains the rate schedule and carrier setup for auto pay.
7. Setup the DMAAIs (ex: 4920) to point the journal entries to different accounts based on the gl class code setup on the charge codes.
8. Enter a TMS sales order.
9. Route the shipment to the route created above and ensure there are two payable charges in the shipment charges.
10. Approve the shipment.
11. Confirm the shipment using today's date as the actual shipment date.
12. In the P0000 (General Accounting Constants), set the flag Allow PBCO Postings to blank (do not allow).
13. Set the P0010 period to a future period for the company used on the transaction.
14. Set the processing options in the R4981 to use the actual ship date as the Invoice and GL date.
15. Run the R4981 over the shipment.
16. A PBCO error will be received due to the current period being in the future. Note the batch number assigned.
17. Go into the P0411 and perform a find by the batch number. Note that a F0411 record has been created for the 2nd payable charge on the shipment. No associated F0911 has been created.

Changes

 

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
Changes
Cause
Solution
References


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