Skip navigation

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:

  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.

Do you want to determine if a program will accommodate a specific process or procedure? If yes, be sure and review all the Option exits and/or Function keys for the program. You might be pleasantly surprised to find functionality you didn't know existed.

 

After supporting the JDE World Distribution applications for 20+ years, I am often delighted to stumble upon inconspicuous functionality. For example, a customer recently posed a question regarding how to issue quantity for all components that comprise a kit using the Inventory Issues program (P4112). My initial thought was that there was no such functionality, aside from manually entering each component on the video. After reviewing the function keys and option exits, I was thrilled to find function key F10, which allows you to inquire on the Bill of Material (BOM) and pull all kit components back to V4112.

 

Here are some of my favorite function keys and option exits in the World Distribution applications that I have discovered over the years:

 

  • Voucher Match (P4314) - If you press F9 immediately after matching an order, the program will re-display the order/voucher information. I was elated to come across this functionality after years of re-inquiring on the order number after performing a match.
  • Enter Receipts (P4312) - If you press F13 immediately after performing a receipt, you can see the journal entries created for the transaction. Keep in mind that you can only view the journal entries immediately after the receipt transaction takes place.
  • Sales Order Entry (P4211) - If you enter option 8 on an order line just before you create an order, the program disregards any information entered on the line and refrains from adding it to the order. This comes in handy when you add a line to a sales order only to have the program generate an error indicating the item number doesn't exist.
  • Shipment Confirmation (P4205) - As of the World A9.2 Release, you can enter option 10 to reverse a shipment. Option 10 won't display in the Available Options window unless you have the processing option set to Display the Shipped Mode field AND you are inquiring on a previously shipped order. For more information, see DOC ID 633457.1: How to Reverse Ship Confirmation of a Sales Order.

 

If there is a program you utilize frequently, it might behoove you to look at all the available function keys and option exits. You can press F24 from any program to see all the available function keys. You can press F1 in the Option field (assuming there are individual records that display on the video) to see all available option exits. You might be tickled to find functionality you didn't know was there.

As hard as we all try, no matter what we do, our days can become hectic. Your day can begin with wondering where you set your coffee cup down at or, if you ran the dream writer that prints purchase orders for example. Then, as you ponder these questions, someone else asks if manufacturing accounting was run or not.

 

We cannot help you locate your coffee cup but we can help you to determine if your manufacturing accounting job was run or not.

 

The one thing that these jobs have in common is that they all have an associated dream writer. In order to determine if the dream writer was run or not, there is a handy way to find out if it ran without having to hunt down the report or the output.

 

Just follow these simple steps:

  1. From a command line, simply type in VL (versions list) and enter the Form ID (program number). Or, if you don't have a command line, go to the menu and menu item that displays the list of dream writers for your job.
  2. Once the screen displays all of the dream writers, look in the far right hand side of the screen for the field Last Chg (Change) Date. Press F5 (function key 5)
    and voilá! the column now displays the Last Exc (executed) Date.

 

The Last Exc Date will tell you the last date that the dream writer was launched. Not only does it display the dream writer you are looking for, but also displays the date that all of the dream writers were last run. If the date doesn't match today's date then the job did not run today.

 

Try it now!

You are in the middle of migrating and converting data from World to E1 and despite watching your checklist some files and programs get past you!

 

An example for data migration that might come up missing? World EDI file F4780 -Trading Partner Master to E1 table F4780 Trading Partner Master - Aren't these tables the same? Isn't there a conversion program?

 

Look no further!

 

What are Customer Master EDI Fields (EDCI, EDII, EDAD and EDQD) Used For? (Doc ID 2007249.1)

 

What is Address Cross-Reference (P4780) used for and can it be accessed from a menu?

 

Note: The program in EnterpriseOne is similar to the World Trading Partner Master P4780 (F4780 file) but does not have all of the functionality. See EDI Enhancement for Trading Partner Master P4780 (Doc ID 2151577.1) for release A9.2. There is no World to E1 Migration Conversion program for the P4780. The F4780 will need to be manually migrated.

 

Always search in MOS using key search terms such as program number and table for both World and EnterpriseOne searches. And... most importantly, whether it's Supply Chain, Financials or other systems contact the World Technical and EnterpriseOne Migrations teams to help determine those errant files and programs.

 

Best of luck on the conversion!

AdvisorWebcast.pngWhat are some gotchas when Upgrading in the Supply Chain systems?

 

On November 7, 2017 at 10 a.m., a web advisor is being presented, Upgrading World Supply Chain to A9.4 - Things to Think About.

Common Issues are being discussed and how they may affect your upgrade.

 

This should be posted to JD Edwards World Advisor Webcast Schedule and Archived Recordings (Doc ID 1455377.1) shortly.

 

Look forward to seeing you there!

Is your system performance slow? When launching a program, is your data returned quickly or, do you sit and wait for an inquiry screen to return information? Does it take hours to run a batch job such as Order Processing (P31410) to attach a work

order routing and parts list?

 

Should the above be true for your system, it is time to purge data.

 

Purging data from your files is the process of freeing up space in your system. When data is not purged, your database can grow so large that performance begins to deteriorate. Oracle/JDE customers have been using Manufacturing and Distribution

(M&D) software since the early 1990's. Can you believe that 27 years have already past and that in many cases, your data still contains records from the beginning of time.

 

Purging data does not necessarily mean that you are deleting data. Oracle/JDE provides programs to archive your data. Once the data is archived, it can be merged back to your existing data files if warranted. Or, better yet, a separate environment can

be created to view the archived data if needed.

 

There are several areas to take into account when purging your data. For example, what is your companies data retention policy? Are you to keep 10 years worth or data or 20+ years of data? Many companies are also SOX [Sarbanes-Oxley Act] compliant.

You will need to determine how many years worth of data SOX specifies.

 

The purge process can be based on the age of the data or the type of data which is discussed in several documents explaining how to archive your data.

 

When Should You Purge/Archive Manufacturing & Distribution files?

 

Customers are encouraged to review the information included in P00PURGE-Generic Purge Program (Doc ID 626668.1) before purging data. Running POOPURGE creates a special purge library name where your purged data is written to.

 

Launching POOPURGE over Distribution data should include the detail file along with the associated header file. An example of this is purchase orders. Purging both the Purchase Order Detail File (F4301) and the Purchase Order Header File (F4301) keeps your purchasing files in sync with one another.

 

Manufacturing has its own purge program called Purge Work Orders (P4801P) which is discussed in Purge Work Orders (P4801P) (Doc ID 1945189.1).

 

Another document that may be of interest is  World Purge and Database FAQs (Doc ID 1169966.1). Many documents exist in Knowledge Management. Using the search word of Purge, will return the documents available for each module.

summ det.bmpThis is a business decision which could be based on terms of data storage space, printing equipment,  supplies consumption, ongoing processes for control and auditing of account balances, level of detail required for the entries, human resources and labor allocated in the responsible area, as well as other direct or indirect considerations that you may identify.

 

The good news is that Manufacturing accounting programs, Work In Progress-Completions (P31802) & Work Order Variances (Standard Costing) (P31804), Work Order Closing - Actual Costing (P31806) and MFG Accounting for Orderless Completion (P31862) offer to users the options to summarize or not  journal entries and/or report printouts. 

If your shop floor activity performs many partial completions and issues  during the lifetime of each work order and you decide to create batches only once the final completion is performed, and prefer as few entries as possible, then you may choose the summarization mode.

 

Combining Summary and detailed?


Yes, you can combine summarized journal entries and print a detailed report for better understanding of what each summarized batch includes. It is important  that users distinguish the outcome of each mode in the Account Ledger (F0911) and the printing of the batches.

Remember that when summarization is set for Material Issues WITHIN Work Orders, the effect is that the program will summarize journal entries in F0911 G/L per each work order, and if desired to view printout in this mode, you will setup the report as well. While when setting up Summarize by Account ACROSS Work Orders, the summarization is done for all work orders processed, where selecting '1' will reduce the number of journal entries. If desired, users may still print out in detailed mode, using the Report processing option by leaving it blank.

 

Best Practice is to run your versions in proof mode first to view any errors that would prevent processing in final mode. 


For more information see Creating Manufacturing (WIP) Journal Entries (Doc ID 1579651.1) .

Have you gone to a program, performed an inquiry only to be presented with the P00IO - I/O Limit Exceeded window?

 

The P00IO is related to the number of records that can be read at one time during an inquiry and this can be user defined …with limits.

 

UDC Table 00/IO holds program numbers and a value for the number of records that can be “read” during the inquiry.  So you may think that making this number as big a value as the field will hold would be a good, one time solution to prevent the P00IO from disrupting your future inquiries.  Well, it is not that simple.  Each program has coding to set the maximum usable digits that can be set in the UDC and if exceeded, the value you enter could be seen by the system as zero.

 

Here is an example. If you update UDC 00/IO with a value of 100,000 for a program that has a maximum usable digits value of 5, 100,000 will actually be seen as zero.  This is due to truncating 100,000 from the LEFT to reduce the number of digits to the number defined in the program.  In this example, the 6 digit ‘100,000’ value will be reduced by dropping the 1, resulting in ‘00,000’ so the P00IO will be presented for any inquiry in that program. In contrast, if you used 999,999 for the same program, this 6 digit value would drop the left most “9” resulting in a value of 99,999 so the inquiry should produce better results.

 

So prior to adding new programs to or adjusting existing values in UDC 00/IO, you need to know the maximum usable digits for that program. IO Limit Exceeded Due to Excessive Amount of Records F5 F6 (Doc ID 827483.1) provides details related to how you can search the program code to find the maximum usable digits for the program you are using. Having this information so the program can be properly defined will help you to avoid the P00IO window from popping up in your future inquiries.

Did you know you can automate the processing of transfer orders from beginning to end? Over the years, the World applications have been enhanced to accommodate the transfer order process to flow seamlessly, with little or no manual intervention required.

 

A transfer order is typically created to accommodate the transfer of stock items from one branch to another. The process begins at creation of the transfer order, which results in two separate orders, as follows:

  • A sales order, on which the customer reflects the demand branch (typically defined with an ‘ST’ order type)
  • A related purchase order, on which the supplier reflects the supply branch (typically defined with an ‘OT’ order type)

 

The ST and OT orders are processed individually, using the same applications you would typically use to process a standard sales or purchase order.

 

Listed below are the programs that have been enhanced to accommodate an automated process:

  • Batch Sales Order Creation (P40211Z). This program was enhanced as of the A9.3 release to allow for the batch creation of the sales transfer order (ST) AND the related purchase order (OT). Prior to this enhancement, you were required to create transfer orders using the interactive Transfer Order Entry program (P4242).
  • Shipment Confirmation (P4205). This program was enhanced in the A8.1 release to invoke the receipt routing process for the OT when you ship confirm the ST.
  • Batch Shipment Confirmation (P42051). This program was created in the A9.2 release to ship confirm quantities on existing sales order lines, in their entirety. You can use the program to ship confirm transfer orders in batch mode, and simultaneously initiate the receipt routing process for the related OTs.
  • The interactive and batch Voucher Match programs (P4314 and P470412). These programs were enhanced in the A9.3 release to recognize the AP Interface flag (P4314) designated for each line type in the Order Line Type Set Up program (P40205). The primary intent of the enhancement is to accommodate the transfer order process by closing out the OT without creating a voucher, as a voucher is typically unwarranted for the transfer order process.

 

You can fully automate the OT process, as follows

  1. Set up a one-step receipt route that serves to put items on the OT directly into stock when the ST ships.
  2. Set up a version of the interactive or batch ship confirm program (P4205 or P42051) to invoke the receipt route defined in step 1 for transfer orders.
  3. Set up and use a line type specifically for transfer orders, such that vouchers will not be created for the order line type.
  4. Utilize the Evaluated Receipts program (P43800, which calls P470412) to automatically close out OTs after they are received, with no resulting voucher.

 

For more information about the processes noted above, please see the following documents:

 

Transfer Orders (P4242/P42011z) - Document 626657.1     

FAQ: Transfer Orders - Document 1538476.1

Troubleshooting Transfer Orders and Direct Ship Orders - Document 1539701.1

EDI Inbound 850 Inbound Purchase Orders - Document 626765.1

 

Otherwise, if you need further assistance, please log a service request.

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 https://community.oracle.com/docs/DOC-1022508 for instructions.