My Oracle Support Banner

WS: 31: Troubleshooting Manufacturing Accounting & WIP Journal Entries (P31802) (Doc ID 1543487.1)

Last updated on SEPTEMBER 11, 2024

Applies to:

JD Edwards World Shop Floor Management - Version A7.3 cume 4 and later
Information in this document applies to any platform.
To assist users with troubleshooting Work Order Manufacturing Accounting related to the Standard Costing methodology.


Purpose

 This document describes the symptom, cause and resolution and/or workaround for issues encountered during the accounting of Standard Costing Work Orders.

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 WO Completions (IC) Journal Entries
 Issue 1: WIP (P31802) was run in final mode, however the IC transaction is missing in the G/L (F0911) and there is no G/L date and batch number in the corresponding Cardex record.
 Issue 2: P31802 is run in Final Mode but IC journal entries are not created.  Discovered that Work Order was created when Parent's frozen cost was missing. How to prevent this in the future?
 WO Issues (IM) Journal Entries
 Issue 1: Credit side of IM Journal Entry has no company number populated in A7.3 or A8.1.
 Issue 2: P31802 is run in Final Mode but IM journal entries are not showing up on the G/L Post report. The IM is showing up on the Item Ledger (F4111).
 Issue 3:  Identified that for one Work Order the IM entries Total in the General Ledger is different than those in the Cardex after the component cost was changed in between partial Issues and is causing an unexpected material variance.
 WO Routing and Overhead Journal Entries (IH)
 Issue 1:  How can routing related reported hours be tracked and journal entries (IH) confirmed?
 Manufacturing J/E & Batch Related
 Issue 1: P31802 displays status In Use and disappears upon exiting batch header. A7.3, A8.1.
 Issue 2: How to correct the date of an Unposted batch and Journal Entry generated by P31802 created when user entered the wrong G/L date in the processing option.
 Issue 3: Need to identify program that created orphan batch header type 0 (zero) then delete the header
References

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