From the JD Edwards World design perspective, whatever you call it on the shop floor, is not necessarily the way it has been named in the software. When reporting a symptom in your Service Request, the product you choose will always be Shop Floor Management, but the program name will depend on the release that you are using. You will see that, for example in A7.3, it is called Rate Base Manufacturing but with release A8.1 and above, it is called Repetitive Manufacturing. The menus across releases are the same, i.e. G3115, G3116, G3141, but the options for the programs are not always named alike. These differences are due to changes in the A8.1 release, when changes were made in the manufacturing accounting program along with some enhancements , added program, and removed programs .

Here's a review of differences in menus, per release:

G3115 Menu

Menu name: A7.3 - Rate Based Scheduling

Rate Based Schedule

Enter Change Rate Schedule (P3104). This program populates file F3104, which is used to store rate schedules. As of 8.1, this file has been removed as part of the consolidation of work orders and repetitive functionality.

Oracle recently announced the general availability of group software updates for #JDEdwards World release A9.4. Read this KM document (Doc ID 2574918.1) to know more about the updates - http://bit.ly/33oSgxh

Many of you contact JDE and ask questions about E1 functionality and this opportunity is for you.

Any World customers interested may attend an E1 presentation at INFOCUS. If you are wanting to learn and understand more about vouchering or compare functionality for upgrades pertaining to JDE E1 Vouchering AP & Procurement, we invite you to...

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.

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.

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.

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.

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.

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.

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.

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.

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:

Have this approver actually approve or reject any pending approvals for the related route.

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.

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.

UPDATE OPTIONS:

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:

Shut down all activity in Manufacturing & Distribution and restore from your production data backup.

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:

Select option 2 to the left of your Dream Writer.

Select option 1 to the left of Data Selection Value(s) in the window DREAM Writer Menu (P98300W).

Locate the Order Number parameter.

Press F4 to open the fold of the Data Selection.

Located on the far right hand side in the fold is the field: Allow *ALL:

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.