Skip navigation

Always run the Integrity Analysis program immediately after a data conversion, or often when BOMs are entered, changed or deleted.  It is also strongly suggested to run the Integrity Analysis program before running the Simulate Rollup (P30820) or MRP/MPS Requirements Planning (P3482/P3483) programs.  If low level codes (LLX) are out of sequence, adding new items to BOM will not produce correct costs, and MRP will not properly plan all component items.


For additional information Understanding Integrity Analysis (P30601), Low Level Code (IBLLX) & BOM (P3002) (Doc ID 636318.1).

Information for the import/export functionality is stored in the following User Defined Code (UDC) tables:


  • 00/BE - Batch Export Enabled Program
  • 00/BI - Batch Import Enabled Program
  • 00/IE - Interactive Export Enabled Program
  • 00/II - Interactive Import Enabled Program


For information related to implementing Import/Export in JD Edwards World programs in the JD Edwards World Technical Tools Guide Release A9.4.

Beginning with A93.1 and above (A94 and A94.1) when performing a Work Order Material Issue using Inventory Issues (P31113) and changing the Lot and/or Location for an item in the fold of the Issues (V31113) screen, the change is no longer saved. This is reported in BUG 29154442 - INVENTORY ISSUES (P31113) DOES NOT SAVE MANUAL CHANGE TO LOT/LOCATION.


Potential work around would involve using option 4 from the Issues screen to call the Multi-location window (P42053) to transact an Issue.


For additional information see Inventory Issues (P31113) Not Saving Manual Change to Location or Lot (Doc ID 2489511.1).

The PM History & Completion program (P12071) is used to change the status to 99 for preventative maintenance (PM) actions. It can also update the status on assigned work orders to completed based on a processing option setting. The program is on the Equipment/Plant Maintenance menu (G1315). To set up the order activity rules navigate to the Work Order / Service Billing Setup menu (G4841) and select the Work Order Activity Rules program (P4826). Inquire on the Order Type and verify the closed status is listed in the Other Allowed Statuses for:

  • The status the WO is at before closing.
  • The work order status (far left column).


Then check the PM History & Completion program (P12071), processing option 6, to confirm that this processing option is active to update the status of the assigned work order.


Enter a '1' to update the status on the assigned work order.


The other option is to have the Work Order Activity Rules set to update the PM Schedule by having the maintenance status 99 in the fold of the work order closed status.  When the user closes the work order in Work Order Entry (P48011), the PM Schedule is automatically closed with a 99 and a new PM Schedule is created at status 01.

There are various types of routings used in manufacturing. Manufacturing can use a standard routing, work order routing, alternate routing and a master routing.  Let's evaluate each type of routing and what its purpose is.


Standard Routing - This is normally setup from menu 14/G3011 Enter/Change Routing (P3003). This routing is used in Product Costing to roll your associated Standard Costs. This is the suggested machine, labor, setup and queue hours to manufacture an end item. The Standard Routing is created with the routing type 'M'.


Work Order Routing - The Standard Routing is used to create the Work Order Routing (P3112). Calculations are performed using the work order header such as quantity ordered etc. when attaching the Work Order Routing to your Work Order header. This is the routing that is used to produce journal entries along with Capacity Planning (CRP).


Alternate Routing -  Users can define different types of routing instructions with different purposes.  M is the Standard Manufacturing routing type and any other value different than M is considered an alternate routing type. Alternate routings can be defined in Enter/Change Routing (P3003) field Type of Routing (TRT). Then the routing type to be used  on the work order header field is entered and the system then uses the indicated type of routing  to attach it to the Work Order routing (F3112).


Master Routing - When there is a need to produce manufactured items that require the exact same process (work centers, setup hours, machine and/or labor), a master routing helps to reduce the number of routings that need to be maintained. Master routings are not branch plant specific like Standard Routings are. This means that you can have multiple items from the same branch plant use the same master routing.


For additional information on any of the above Routings in Manufacturing (Doc ID 627276.1), is a good document to review.

Setting up Multi-Plant MRP (P3483) can seem at times a bit cumbersome at times. However, identifying your branch plants is the main criteria for building a supply and demand relationship. Branch Plant Relationships incorporates more of a specific relationship by utilizing the planning family a.k.a. Master Planning Family (IBPRP4).


The Master Planning Family is set up for each item using the Item Branch/Plant Information (P41026). Pressing F5 to display the category codes is where the Master Planning Family is identified. When relationships are established based on a planning family, the planning family needs to be consistent across all branch plants in the supply chain.


A common misconception is that just the planning family from the demand plant is used and that the planning family does not have to be consistent. With this set up (planning family not the same across the supply chain), MRP will not generate, what we refer to as, a good run.


A good start to planning families not being set up correctly or producing a bad run, is when MRP begins planning illogically. For example:


1. Inquiring on Supply/Demand Inquiry reveals negative availability as the last record  on the screen.


  1. Transfer Order messages will only be received for the highest level branch plants.  Then in order to generate transfer messages for the rest of the supply chain,  the P3483 has to be run again and again (without clearing files) until you get to the end (lowest level) of the supply  chain.


There are reports of other strange occurrences when MRP is not set up correctly. However, our main goal is to advise you that MRP will flow and produce what you need with the correct setup.


To find more information on Branch/Plant Relationships, review Branch Plant Relationships P3403 (Doc ID 782525.1).


Should you have any questions, remember that we are here.

The Meter Readings (P12120Z) is located on 9/G1331. You can use the Meter Readings - Z File (P12120Z) processing program to call Meter Readings (P12120) as a batch process and use that data instead of data you enter manually; to create or update the Asset Balance file (F1202) and Account Ledger file (F0911).


This program runs Meter Readings (P12120) in the background and uses file Meter Readings Z File (F12120Z).


Three processing options as associated with the P12120Z. These are:


     1. Enter the version to be used to call Meter Readings (P12120).


         If left blank, ZJDE0001 will be used.



     2. Enter '1' to skip printing the error report.


         If left blanks, the report will print.


     3. Enter the version to be used to call the error report program (P41ZERR).


         If left blank, XJDE0013 will be used.


F12120Z is meant to replace the video so the user needs to ensure data integrity before running this program. The field ZZACCM in the Z file is designed to allow user to choose which AAI account to use for the record to be processed. P12120 employs the same edit logic over the data read from the Z files.                      


Errors encountered will be written into a log file. A report program is available to print these errors. Account Ledger file (F0911) and Asset Balance file (F1202) records will be generated or updated if no errors are encountered.

The majority of MRP service requests received for 2016, pertain to issues within the Branch Plant Relationship (P3403) table. While troubleshooting the Branch Plant Relationship Table, we have come across a startling revelation. The Effective Thru Dates for each branch record contains the Effective Thru Date of 12/31/20.


We all know that 2016 is in full swing but can you believe that in just four short years, 2020 will be here? Who remembers back in the 1980's when the manufacturing data dictionary item #CYR (Century Change Year) was implemented to be used as the default for the Effective Thru Date fields? When data dictionary field #CYR contains the value of 20, Effective Thru Dates default to 12/31/20 when this field is left blank. Back in the 1980's when 2020 was the default, we had 30+ years to update the #CYR field. Or, so we thought. The majority of service requests entered still display Branch Relationship Revisions with the Effective Thru Date of 12/31/20.


Multi-Plant MRP (P3483) contains processing option 3 in each dream writer version where planning horizon periods are defined. The periods are defined in days, weeks and months. The maximum number of periods in any combination cannot exceed 52 periods. So, let's say that 52 months are added with no days or weeks. This takes MRP out to June 2020. Should the Effective Thru date in Branch Plant Constants contain 12/31/20 as the Effective Thru Date, the branch plant relationship line is only good for another 8 months which is too close for comfort.


Back in 2010, JDE introduced a program Effective Thru Date Update (P4028) that runs over 70+ data files where Effective Thru Dates and Expiration Dates are changed for Manufacturing and Distribution programs. The data dictionary field #CYR can be changed to the year of your choice as long as you follow the 100 year rule principal. When running the P4028, the files listed in UDC 40/EF are updated to include a new Effective Thru Date so that your data does not expire.


Even though this program has been available for many years, we still see customers that have not run the Effective Thru Date Update. The sooner that this program is run, the less likely issues will exist with invalid Effective Thru Dates and Expiration Dates in Distribution.


As a reminder Effective-Thru Dates and #CYR (P4028) (Doc ID 656831.1) explains what this program does for both Manufacturing & Distribution files.


Branch Plant Relationships contain default values when adding new relationships, the following information will default if left blank:

  • The Effective From date defaults to today's date     
  • The Effective Thru date defaults to December 31 and reads #CYR for the default year.     
  • The level for the component branch defaults to one  more than the level from the header for the source branch.                                              


Keeping your setup tables/files current avoids any future problems where data is no longer valid.

For more information see Branch Plant Relationships P3403 (Doc ID 782525.1).

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see for instructions.