Skip navigation
1 2 3 Previous Next

JD Edwards World Support Blog

92 posts

You may run into this periodically when running the P470412 and wonder why are you getting error 2475 - PO Line already Matched when the line you are attempting to voucher has not been matched?  You can inquire on the order/receipt in P4314 (with Match Type = 1) and it pulls in the sub-file data verifying the detail lines are available for / ready for voucher creation.  So why do you get this error?


There are a few reasons why you may be getting this error.  One of the most common and most missed reasons for this error is you are attempting to create a voucher for a partial receipt and the F47042 field 'No of Lines' (SZNLIN) does not have the correct value.


Details on this answer along with the other possible causes are detailed in WS: 47: Troubleshooting Inbound EDI Transaction Sets (Doc ID 1559493.1).


If you would like even more information on this and other errors as well as general information on the P470412, use the link below to view the recent Advisor Webcast on World program P470412.


Advisor Webcast Recording: JD Edwards World (JDE World) - JD Edwards World SCM Tips for Troubleshooting of P470412 Inbound 810: Invoice with Receipt Match held on April 16, 2019 [Video] (Doc ID 2502711.1).

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).

How many times during your work day do you think of a quick question that you would like to ask World Manufacturing or World Distribution and do not want to stop to open a new service request? Are you aware that there is a way to us a question without opening a new service request?


The tool that is available for you to ask a question is called My Oracle Support Community (MOSC). Document 2266333.1 - FAQ: My Oracle Support Community (MOSC) Information and User Reference is available explaining the steps of how to open a community thread. In addition, when opening a community thread, you can remain anonymous.


The space to use to reach Supply Chain Management - JDEW (MOSC). Also, when asking your question, we ask that you please include the World release that you are operating as this information will assist us with answering you in a timely manner.


So next time that you have a question, no matter how trival you think it is, open a thread in our Community and we will answer you. Should your question be complicated, we will guide you and make suggestions.


Go ahead, ask us a question!

What makes these two versions different is the purpose of its running within the business established process in manufacturing accounting. For example, if you are processing  work orders  before reaching the status of full completion or your work order, this action is commonly called ‘Work In Process’ or WIP, denoting that the order it is not yet fully completed on the shop floor but that journal entries are been generated progressively before reaching the completed status.


Then, when the work order reaches the final status reflecting that all inventory and routing activity has been fully completed, therefore, ready to run P31802  in final mode for the last time (right before generating variances) this step is known as P31802 Completions or manufacturing accounting completion.

This is a user defined process, as it is not mandatory to run one version or the other or both. The definition of the business process can accommodate both runs, or only one.  One of the most important keys for WIP and Completions versions is the work order status defined by user and that will be data selected and/or updated for the work orders that are been processed.  User can define if there will be or not a status for WIP and a different status for final completion in UDC 00/SS, or use the same for both.  The other key is the Variance Flag (PPFG) that resides in the Work Order Header.


For more details on P31802 program setup and information on (PPFG), review Knowledge Document Creating Manufacturing (WIP) Journal Entries (Document ID 1579651.1) and Purpose of the Variance Flag (PPFG) In Manufacturing (Document ID 661187.1).

Pricing, Pricing Pricing in JD Edwards World. It's on always on the to do list as must always evolve and maintenance your pricing to keep up with the business.

It is not always easy to search on all the related pricing topics to learn set up, FAQ's and Troubleshooting.
To help with searching and to jump start your research, see the list below of the main documents related to pricing.


  • Overview of Base Pricing in Sales (Doc ID 626798.1)
  • Base Pricing and Units of Measure in Sales Orders (Doc ID 1125196.1)
  • Comparison of Base, Standard, and Advanced Pricing (Doc ID 626661.1)
  • Advanced Pricing for Markups and Discounts (Doc ID 626729.1)
  • FAQ Advanced Pricing (Doc ID 1573202.1)
  • Troubleshooting Advanced Pricing (Doc ID 1573469.1)
  • World A9.3 Enhancements to Advanced Pricing (Doc ID 1451682.1)
  • Basket and Order Repricing in Advanced Pricing (Doc ID 636432.1)
  • Preference Profiles in Sales (Doc ID 626656.1) - Review for Pricing Information (Pricing UOM, Price Codes 1,2,3, Adjustment Schedule)
  • Credit Orders and Advanced Pricing (Doc ID 626770.1)
  • Free Goods In Advanced Pricing (Doc ID 626677.1)
  • Rebate Adjustments in Advanced Pricing (Doc ID 626768.1)
  • Accruals in Advanced Pricing (Doc ID 626740.1)
  • Automatic Accounting Instructions for Distribution (AAI DMAAI) (Doc ID 626758.1)
  • Advisor Webcast: JD Edwards World -Troubleshooting Advanced Pricing [Video] (Doc ID 2172903.1)
  • Advisor Webcast: Advanced Pricing Free Good & Reprice Adjustment Enhancements in Release A9.3 (Doc ID 1477352.1)
  • Information Center: JD Edwards World Advanced Pricing (Doc ID 1590104.2)
  • Troubleshooting Pricing Problems (Doc ID 626705.1)

Documentation Guide


If you find more is needed, we are here to help. Call Global Customer Support for assistance.

Does JD Edwards E1 / Electronic Commerce (EDI) function the same as World EDI? Are the programs and files the same? Does E1 have Flex Accounting and how does it differ from JDE World? Does the World A/R post program differ from E1?

What about all those files and fields? Do they all migrate from World to E1? Can you tell me if something will not migrate?


It is hard to know all the differences and pertinent information between World and E1. Just when you think you have got it, oops, there is one you have missed inadvertently. If you have gone searching in My Oracle Support (MOS) and come up dry, try these options for more assistance.

  • World Upgrade Resources / Oracle Technical Catalog 
    • Be sure to accept the disclaimer and navigate between World and E1 in the catalog to review what may be different by objects and system codes and create reports of the information.
  • Call Oracle Global Customer Support - 1.800.223.1711 or create a SR online.
    • Remember: You may be questioning functionality in any system from Supply Chain, Tech to Financials. State the exact program, files, and fields in the SR. Support can assist you as more efficiently with the specific information.
    • Each Support area can discuss what exists or does not exist in each software. If you need more technical assistance on how data is migrated from any World JDE system to E1, contact World Tech. They can always ask their counterparts in Applications for assistance on specific system information.


The best part... Contact us anytime; we are here to help!

Lease Accounting Prior to 9.1 and all Releases of World (Doc ID 2420929.1) is intended to outline our general product direction for Lessee Accounting for customers using World Software.  The document contains suggested workarounds which may or may not be a solution for every customer. The document outlines how JD Edwards’ customers might leverage JD Edwards Fixed Assets, General Accounting and Accounts Payable modules to meet the change in Lease Accounting Standards (for Finance and Operating Leases).


It is recommended that you seek professional advice to follow accounting entries through from a local certification, compliance and verification perspective before implementing.

Approval of purchase orders is a common, highly used process in World Procurement with many companies using multiple differing Approval Routes to establish and direct the approval requests to the appropriate levels / persons for approval.


Occasionally, due to attrition, change of responsibilities or changes in the level of approval needed, you may find you need to make changes to the 'approvers' on an approval route or may even need to delete an existing approval route as it is no longer needed.

When these changes/deletions are attempted, you may run into error 2788 - Delete Not Allowed, blocking you from making this change.


The Data Dictionary defines the 2788 error as follows:

Cause. . . . The person that you have attempted to remove from the approval table has pending orders which require his/her approval or rejection.
Resolution . . Either change the person responsible for the pending orders, or wait until the orders have been approved or rejected.


Note :  The "Orders Awaiting Approval" screen (P43081) is a helpful tool in determining which orders are awaiting approval by a specific approver.


So how do you resolve this error and continue on with you updates/changes/deletions to these approval routes?


As stated in the error text, this error is generated because the person or route you are attempting to change/delete has orders pending approval.  An Approval Route cannot be deleted, nor can an approver be removed from an Approval Route when the approver has orders pending their approval.


Troubleshooting Approval Processing Issues (Doc ID 1547635.1) addresses the 2788 error and provides options for making the desired changes or deleting the approval route.


The first step is to identify the approver who has a pending approval request and as the Data Dictionary error information states, the Orders Awaiting Approval screen (P43081) is a helpful tool in determining which orders are awaiting approval by a specific approver.  Another option for identifying these approvers is to review the data in the F4209 – Held Orders file.  A record in this file designating approval is pending from a specific approver is identified by a value of 2N in HOASTS - Approval Status field.


Once you have identified which approvers have orders awaiting their approval (App Sts = 2N), you have the following options:

  1. Have this approver actually approve or reject any pending approvals for the related route.
  2. Use the Approval Delegation process/program P43280 so that all orders pending this person’s approval can be delegated to a different approver.  The new approver can then approve or reject any orders that are pending their approval.
  3. If your intent is to delete the entire approval route, you will need to use one of the first two methods to approve / reject all orders that are pending approval for this route.  The existing approver must approve or reject all pending orders before you can remove him or her from the route or delete the entire route.   An Approval Route cannot be deleted, nor can an approver be removed from an Approval Route when the approver has orders pending their approval.


Once all pending approvals have been acted upon so that there are no pending approval records (F4209 HOASTS = 2N for this route), you can go to the P43008 - Approval Level Revisions, Inquire on the Order Type & Approval Route Code to pull the Approval Route record into the video and then delete it using the D Action Code. 

Full details on the set up and use of Approval Processing can be found in Approval Processing (Doc ID 626779.1) with additional topics discussed in FAQ: Approval Processing (Doc ID 1535323.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.

Hopefully this information is reviewed before you ever encounter the situation when all your closed work orders are magically reopened. In case you do not know, launching Order Processing (P31410) and changing the Dream Writer Data Selection for the parameter 'Order Number' to *ALL, can reopen all closed work orders. This can occur when your data selection is not defined to look at a specific Work Order Status (data dictionary item SRST)  equal to 10, in the following files:


Work Order Header    (F4801)

Work Order Parts List (F3111)

Work Order Routing    (F3112)

Item Location              (F41021)

Production Cost          (F3102)


(Additional files are also updated however, the five largest files are listed above.)


Should this ever happen to you, there are only two options for correcting your manufacturing data. The two options are:

  1. Shut down all activity in Manufacturing & Distribution and restore from your production data backup.
  2. Reset all work orders to the correct status manually or via SQL and running Repost Open Orders program (P3190) to reset your commitments.


The largest cause for closed work orders reopening is running Order Processing wide open data selecting on Order Number = *ALL. Therefore, changing one setting in the data selection will prevent *ALL from ever being used for the Order Number.


To update your P31410's Data Selection, follow these steps:

  1. Select option 2 to the left of your Dream Writer.
  2. Select option 1 to the left of Data Selection Value(s) in the window DREAM Writer Menu (P98300W).
  3. Locate the Order Number parameter.
  4. Press F4 to open the fold of the Data Selection.
  5. Located on the far right hand side in the fold is the field: Allow *ALL:
  6. If this field contains a Y, change it to an N to prevent *ALL from ever being used.


Once the field 'Allow *ALL:' has been changed to an N and a user tries to select Order Number = *ALL, error 0113 - Invalid Selection (*ALL), generates forever more.


Additionally, any Dream Writer can be updated in any parameter within a Data Selection to not use *ALL. This feature is not just limited to Order Processing (P31410).

For many businesses this functionality is very effective as the outside operation is manufacturing’s vehicle to send your item(s) out for service via a purchase order generated from a specific routing step. The purchase order specifies a type of labor service to be rendered to your item(s) so that the manufacturing work order may be completed. When the goods are sent to the vendor with a labor purchase order, the system can track and trace the purchase order receipt back to the manufacturing floor and the vendor can send its invoice for the service rendered to be voucher matched and proceed with the payment. A labor purchase order interfaces with inventory, procurement, accounts payable and accounting.


From a manufacturing stand point, it is important to remember that an outside operation is nothing more than the payment for services rendered and not an inventoried item. When the receipt into shop Floor is recorded in the Cardex, it can give the impression that you are receiving an item, but the IM record is for memo purposes, so workers can confirm that the outside service has been completed by the vendor and delivered, so manufacturing can continue. The unique stock and line type X is what drives this type of operation and labor.


The setup of an outside operation is not complicated but you must follow each step exactly or you will not produce the desired results.  Other considerations to take into account are:

  • Purchase Orders can be generated interactively or by batch using Order Processing (P31410).
  • Purchase Orders can be submitted to Approvals.
  • Purchase Orders can be consolidated by Branch and Supplier.
  • Purchase Orders can be processed with Receipt Routing.
  • Work Order routing can include more than one outside operation step for different suppliers.
  • Outside operations can be backscheduled.
  • Standard or Actual costing methodology can be used in manufacturing for cost extras or add-ons when costing an outside operation item.
  • As of A9.3 release, the *OP purchasing information linked to the related manufacturing work order and inventory ledger (Cardex) transactions can be displayed using PO/ Receipt/ Voucher Summary (P43260).
  • Open receipt information linked to WO details and receipt transaction recorded in Cardex can be printed  with (P43560) - PO/Receipt/Voucher Summary).


For more and detailed information, you can review Knowledge Documentation available in My Oracle Support.

  • Outside Operations Overview, Setup, Execution and Accounting   (Doc ID 647965.1)
  • Outside Operations FAQ  (Doc ID 1533827.1)
  • Troubleshooting Outside Operations (Doc ID 1533782.1)

Blog time again and thinking a history lesson might be different!


ECS - Energy Chemical Systems


If you need a bit of background history on ECS for World Software, there is a new MOS Document out.


Have a look at ECS History From A7.3 to Current Release - ECS Programs, and Files (Doc ID 2411328.1)

Many customers are not aware of the differences between Subcontract Management in World when compared to EnterpriseOne. There are of course many similarities, but it is these differences that require Subcontract data in World to first be converted prior to migrating the data over to EnterpriseOne.


Let’s take a look at some of these differences and similarities.

  • In World, Subcontract Management is System 44 and is separate from the Purchasing system whereas in EnterpriseOne, Subcontract Management is part of Purchasing, system 43.
  • In World, Subcontract orders are created using the P44001 - Subcontract Entry and P4402 - Commitment Revisions programs.  This is not the case in EnterpriseOne where Subcontracts are created using the P4311 - Enter Purchase Orders program.
  • One similarity is that both systems create records for Subcontract orders in the F4301 & F4311 files/tables, however the records are not populated the same for a handful of fields.
    • For example, World Subcontract orders do not have Last/Next Status Codes whereas EnterpriseOne Subcontracts will have a value in the PDLTTR & PDNXTR fields.
    • The conversion process will use information entered in the processing options to add the appropriate Last and Next Status Code values to the World files so that once migrated to EnterpriseOne, they can be further processed to create receipts and/or vouchers.


These are some of the differences dealt with by P44980 - Subcontract Conversion - World to EnterpriseOne.


Previously, document Subcontract Conversion from JD Edwards World to EnterpriseOne (Doc ID 625616.1) has provided the majority of the information and instruction available to assist you in this data conversion. This document has been updated over time to contain new, expanded information, however the process can still be confusing. In addition, this document was originally written for the A7.3 release so a good portion of the information in document would not pertain to you if you are on World A9.4 for example.


To hopefully clear up any confusion related to these differences, similarities and to offer more in depth instruction for the migration process, document Preparing World A9.4 Subcontracts for Conversion to EnterpriseOne (Case Study) (Doc ID 2397295.1) is now available.


This document offers explanation as to:

  • Why this conversion process is required
  • What prerequisites need to be validated
  • Which file ‘Triggers’ are needed and offers the commands to check for, add or delete these triggers
  • Provides step by step instructions for determining processing option settings


So if you are currently in the process of a migration, planning a migration or just considering a move from World to EnterpriseOne and you use World Subcontract Management, please review and become familiar with Preparing World A9.4 Subcontracts for Conversion to EnterpriseOne (Case Study) (Doc ID 2397295.1).  Use this as your guide through the process of setting the P44980 Subcontract Conversion - World to EnterpriseOne program correctly for successful conversion of your World A9.4 Subcontract data so that it can be then be migrated to your EnterpriseOne environment.

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.

Recently, we have had an influx of service requests regarding ending dates in World Manufacturing & Distribution. Therefore, let's review the information together so everyone knows.


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 M&D. The ending date can include but is not limited to, Contract Completion Dates, Lot Expiration Dates, Effective Thru Dates and Temperature Expiration Dates. 


This program works with two UDC tables and contains two processing options which is explained on Effective-Thru Dates and #CYR (Doc ID 656831.1).


Ending dates can be manually populated or leaving an ending blank in many M&D programs automatically defaults to December 31st with the year based on the data dictionary item #CYR. If you are unable to access the data dictionary to see how #CYR is set, go to your test environment and add a new component to a bill of material leaving the Effective Thru Date blank or add a new Item Cross-Reference (10/G41112) for example. Inquire back on your entry and press F4 to open the fold. You will see the date of December 31, 20XX. Whatever XX is populated with is how your #CYR is defined.


You can also convert your own data files if required. Simply amend the corresponding UDC tables and add your information.

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.