Skip navigation

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!

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

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.

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.

Did you know that there are two methods to attach the work order parts list and routing? It seems that Order Processing (P31410) is the preferred method for attaching the part list and routing to the work order header. This is probably due to Order Processing being a batch program where more than one work order can be processed at a time. But what if you only have one work order that requires processing. Should you run Order Processing (P31410) and wait?

 

There is a second method to attach the work order parts list and routing. This is called Interactive attachment (P48013). Interactive attachment works for one work order header at a time and there is no delay. The parts list and routing are attached immediately.

 

In A73, Interactive attachment could not be run if the standard routing (F3003) contained an Outside Operation where a purchase order is created. However, this was corrected in A9.1 and above. Now, a purchase order is created when attaching Interactively. The only caveat is that the work order routing (P3112) must be attached first.

 

Interactive attachments works from the Work Order Header (P48013). Inquire on the work order using Enter/Change Order (P48013) and press F8. The standard routing file (F3003) is read and when pressing F10 twice, turns the action code of the P3112 to an 'A' for add. Press enter and the routing is created. To create the parts list at the same time, ensure that the second processing option in the P48013 for INTERACTIVE BILL/ROUTING ATTACHMENT, is activated.

 

     INTERACTIVE BILL/ROUTING ATTACHMENT

Enter a '1' to automatically create

the WO Parts List when creating the

WO Routing Instructions on-line. 

 

We highly advise to always attach the routing first and not the parts list. The only time the parts list should be attached first is when no routing exists for the item.

 

No reports are generated when attaching Interactively. If a parts list and routing are required, Order Processing can be run with the first processing option (1a.) of Order Processing (P31410) GENERATION INFORMATION set to a blank. This way, the existing routing and parts list will not be reattached. However, a parts list and a routing will be printed as long as the Parts List Print and Routing Print processing options are selected.

Once again, a new year is upon us. It is already 2016. We know that a new year is here and now, human intervention is required to inform the manufacturing programs of this as well. Several manufacturing functions require up to date calendars in manufacturing. An example of this is:

 

     Backscheduling: Work Orders perform back scheduling in order to calculate the correct start date to begin production.

     Lead-times:         Lead-time calculations are performed which depends on Shop Floor Calendars existing and being up to date.

 

Manufacturing requires calendars to be set up five years in the future along with two years back. Since it is already 2016, adding five years takes your calendars out to 2021.

 

To check if your calendars are up to date the menu, Shop Floor Control Setup (15/G3141) can assist you. Simply inquire on your branch plant along with the calendar month of 01 and year 2016 and begin paging down. Confirm that every month in 2016 displays a calendar through 2021. Should the calendar not exist, a message displays at the bottom of the Shop Floor Calendar screen (P0071) stating: Enter key must be pressed to add record.

 

For customers operating A92 and above, you have access of pressing the F5 function key to call the Calendar Generation (P0007G) program. The days of adding calendars one at a time is gone. The Calendar Generation program can add as many calendar years as you want. Enter the From month/year and update the Thru month/year to any year of you liking. For example, select to run the Calendar Generation program for 01/2016 through 12/2021.

 

Remember to add your work days as code W, Holiday's as code H and shut down as an S in your calendars. This way, backscheduling will not include a holiday when calculating work order start dates. If using Calendar Generation, add a normal calendar and then access the calendars that need some tweaking for holidays or shut down days.

 

Adding the calendar information ensures that your work order start dates calculate with a valid start date. Also, when running any MRP program such as Single Plant (P3482) or Multi-plant (P3483)following the rules of calendars five years out and two years back eliminates error JDE3401 - Errors occurred calculating the dates required for MPS/MRP/DRP processing, which seems to hide in an MRP job log.

 

More information can be located on P00071 Shop Floor Calendar Setup and Use (Doc ID 631273.1) and Work Day or Shop Floor Calendar and Branch Plant 'ALL' (Doc ID 813265.1).

Why wait for your phone to ring with someone asking you what happened to a specific work order. The resources exist to track the activities of a work order in addition to controlling the steps that a work order can take.

 

As of A9.2, the capability to track your work order was added. The Work Order Ledger can now be setup to track the work order header changes. Any field that resides in the work order header file (F4801) can be setup and tracked so you will always know all of the activities of a work order. For more information, refer to Work Order Ledger (P48019) (Doc ID 1279122.1).

 

As of A93.1, Work Order Activity Rules now work with discrete or standard work orders. Setting up the statuses that your work orders can take assist with the proverbial mistake of trying to reopen a closed work order. It simply won't be allowed to occur using Order Activity Rules.

 

Work Order status can be affected by running certain programs based on processing option settings behind each program.

 

    Enter/Change Order (P48013) - Interactive Program

    Order Processing (P31410) - Batch Program

    Inventory Issues (P31113) - Interactive Program

    Completion (P31114) - Interactive Program

    Super Backflush (P31123) - Interactive Program

    Work In Process or Completions (P31802) - Batch Program. Both modes, Proof and Final can be setup to update WO Status

    Work Order Variances (P31804) - Batch Program. Both modes, Proof and Final can be setup to update WO Status

 

Another phone call that occurs is when the material handler calls to ask what is this item doing on the parts list. You can determine if the bill of material was changed to include the item or, if an unplanned item was manually added to the parts list. The feature to display updates to the bill of material is available using BOM Change File Inquiry (P3011).

 

When the Log Bill of Material (BOM) Changes field in the Manufacturing Constants for a Branch/Plant is set to 'Y', history records are created in the Bill of Material Changes File (F3011). The Bill of Materials Change File includes all of the same fields as the Bill of Materials Master file (F3002) plus a field to record the Action Code. When a new  bill of material is added (Action Code A), a copy is created in the change file. When a bill is changed or deleted (Action Code C or D), the pre-change condition is recorded in the change file. The BOM Change File Inquire program displays a selection of the fields from these records.                                                             

 

Help your manufacturing operations by using the tools that exist now. These tools allow you to stay on top of your work orders so no surprises or puzzles are brought to your attention.

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.