Skip navigation

Finding Information in Oracle… can be hard at times but there are many easy ways to help alleviate the work in searching for answers. You can also ensure better searches in My Oracle Support (MOS) and help with understanding and accuracy for service requests.

  • When logging service requests provide a clear, concise description of the issue including all detailed steps to duplicate.
  • Add attachments with screen shots of the program name and number as well as related files in excel format / joblogs and dump in .txt format to help in understanding and clarification of an issue.
  • Has the issue also been tested in the TEST environment against the JDFOBJ (pristine) object and is the issue still able to be replicated?
  • Search My Oracle Support to find answers – Use Key Words to find several types of documents
    • Include a program name/number and related error numbers when searching
  • Also include in your search criteria...
    • Type ‘FAQ’ – Frequently Asked Questions document for topic/program
    • Type ‘Troubleshooting’ – Troubleshooting document for topic/program
    • Type ‘Bulletin’ – Detailed information document on topic/program
    • Type ‘Information Center’ – Shows groups of documents for JDE systems (Ex. Sales, Procurement Information Center)
  • If trying to further understand how to use My Oracle Support and getting it to work well for you, use Oracle Premier Support: Get Proactive! (Doc ID 432.1).
  • Use website when looking for more on JDE including documentation guides  and click a variety of helpful links if you are a JDE User / Admin / business user or Executive.
  • Use Communities to find answers and conversations regarding topics

How To Get Started In My Oracle Support Communities and Follow JD Edwards EnterpriseOne and World Communities(Doc ID 1561246.1)


We look forward to assisting you!

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.



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.

A Direct ship order is used to record the sale of items that you purchase from a supplier who then sends the items directly to your customer. Your inventory quantities and availability are not updated. Both a sales order and a purchase order are created.


Direct Ship orders are entered with program P4243 (18/G4211).  The Related Order fields in F4211 and F4311 associate the sales order and purchase order to each other. In the sales order, these fields are found on the detail behind the details (option 1 from a detail line of the sales order), and in the purchase order, these fields are found in the fold of the detail.

By default, the order type for the sales order is SD while the order type for the purchase order is OD.

The order line type typically used for direct ship orders is D. By default, line type D has a D inventory interface, indicating  the system will check the inventory for a valid item number, but it will not update quantities or check availability.

An order line type with a Y inventory interface can be used, allowing use of receipt routing and the writing of Item Ledger records for both the receipt and the ship confirmation. In the case of a lot controlled item, this provides Trace/Track functionality, even though the product was never physically in your warehouse. Functionality described in this paragraph became available in releases prior to A9.3.

It is important to note that changes made to the direct ship sales and purchase orders should be made through P4243. Changes you make to a direct ship order in Sales Order Entry (P4211) will not carry over to the corresponding purchase order. Likewise, changes you make in Purchase Order Entry (P4311) will not carry over to the corresponding sales order.

You can have the receipts program (P4312) update the status of the sales order upon full receipt of a direct ship purchase order line. The sales order line status will not be updated if the purchase order line is partially received.

As of Release A9.3 new processing options were added to P4243 to indicate the next status at which changes can no longer be made to either the sales or purchase order. Associated text has to be entered separately to the sales order or purchase order.  Direct Ship Orders have other unique setup and processing considerations compared to regular sales or purchase orders which are noted in detail in the document Direct Ship Orders (Doc ID 626663.1)

Did you know that keying SHIFT+F9 after entering a Work Order header will display the last entered record?


Did you know that most releases are shipped with a fast path word COST that when typing it at the command line, it will take you straight to the daily product manufacturing costing menu G3014?


Did you know that pressing function key 11 or 12 in the Cardex will display the Document Number Document Type line above the item number field in the header, allowing user to inquire on all related transactions to an specific work order?


Did you know that when a component’s Item Description is highlighted in a Bill Of Materials it is indicating that a substitute item exists? For more information please see How to Use Parts List Substitutions (Doc ID 627299.1)


Did you know that when a component’s number in the Bill of Materials is highlighted to indicate that there is an ECO message tied to that item in the Item Master?


Did you know that the item number is highlighted in the BOM Inquiry (P30200) program indicating that the component has a related flash message and if the descriptions of items are highlighted that substitutes have been defined at every level of a multi-BOM?


Did you know that function key F2 in the Journal Entries (P09101) program with the detail area visible (F4), will switch format display in sequence setup via processing options? This allows user to gather more details for the journal entry without having to exit the J/E.


Did you know that as of A9.4, Work Center Costing enhancement generates costs in work center levels where cost is broken down by component cost types? The Work Order Variances (P31804) program will create Journal Entries for variances by operation sequences on the Work Order. Variance by work center compares the consumption at the work center or the material issued and hours reported to the standard material and hours established at the work center level.


Did you know that in Parts Availability (P30205) the system highlights the Quantity on Hand field if item location has a Lot Hold Status Code, and when the Quantity Available is highlighted there is shortage for the item?


Did you know that the Calendar Window (P00CAL) shows highlighted dates based on user’s preference set up in the Calendar Holidays (UDC table 98/HL)? For more information on setting these dates up see How to Highlight Dates in Calendar Window (Doc ID 628811.1).

If you buy anything at a grocery store then you have seen Advanced Lot Management at work. Shelf Life of a product translates into the expiration date of the item.  In addition there are other dates that can be utilized to manage your lot inventory.  Think about products such as pharmaceuticals, dairy, fresh meat or produce. These items not only have a shelf life and expiration date but may also have Best By Dates and Sell By Dates which are part of lot management.


Consider also, these items have manufacturing effective and purchasing effective dates. These dates, for example, can establish a time frame for the purchased goods to be inspected prior to the lot becoming “effective”.  In a similar manner, a manufacturing effective date may be used to delay release of a lot for sale to allow the product to fully mature so the product is not available for sale until the manufacturing process, (including aging, curing, etc.) has been completed.  You do not want to sell something that is immature or not ready to be sold. Therefore, not only are the above dates considered but also immature lots are considered by programs to ensure product does not go out the door prematurely.


When selling your inventory, what inventory commitment options are available?


Standard commitment methods include:

  1. Committing from locations with greatest quantity first
  2. Committing by lot where the lowest lot number is committed first
  3. Committing by expiration date where locations with the earliest expiration date are committed first.


But what if these standard methods do not provide the flexibility you need?  Maybe you would like the ability to establish rules defining how inventory is committed for a Customer, Item or Both.  Or even by Customer or Item Groups.  Your processes may require committing inventory by Lot Expiration, Sell By, Best Before, or other specific dates.  If you could just override the standard commitment method set in Item Branch/Plant Information….


As of JD Edwards World Release A9.1, all this is possible using Advanced Lot Management! 


Advanced Lot Management combines the new lot fields on the Lot Master, Item Master and Item Branch Plant with Preference Profiles to ship product by Ascending Ship Date Rules.  This functionality is incorporated into the sales order entry, pick slip, inventory commitment and shipment confirmation programs and utilizes the new Last Customer Shipment Inquiry and file, P4239/F4239. 


For more on this topic review:

Preference Profiles in Sales(Doc ID 626656.1)

Immature Lot Functionality in Sales Order Management(Doc ID 2049519.1)

Lot Effective Dates - Manufacturing and Purchasing Days(Doc ID 804166.1)


Or join us on May 11th for the Advanced Lot Management Preference/ Ship Ascending Dates Advisor Webcast were we will be discussing these topics. You can register for this webcast at JD Edwards World Advisor Webcast Schedule and Archived Recordings (Doc ID 1455377.1).

Do you need to create purchase orders to accommodate sales order demand in one fell swoop? There is new functionality in the World A9.3 release to do just that. Prior to the A9.3 release, the Direct Ship program (P4243) was only geared to accommodate transactions for which goods are supplied directly from your supplier to your customer. As of the A9.3 release, P4243 is equipped to handle stock transactions, that is, to create a purchase order for goods received to inventory prior to being shipped to the customer on a related sales order.


In addition to creating back-to-back sales and purchase orders via P4243, the Batch Sales Order Creation program (P40211Z) will also accommodate the creation of back to back orders.


Prior to the A9.3 release, if you attempt to create back-to-back orders using a stock line type via P4243, the resulting sales and purchase orders may not be processed properly by the system. The system has been enhanced to orchestrate the back-to-back order functionality, as well as to enhance the drop ship process, as follows:


Direct Ship Orders (P4243)

  • Prevent order changes at certain statuses
  • Display requested date for purchase orders in video header
  • Display pick and ship dates for sales orders
  • Invoke the Inventory Commitment Preference (for stock transactions)
  • Accommodate order templates
  • Accommodate order duplication process
  • Default Ship-To address for supply branch on PO (for stock transactions)


Enter Receipts (P4312)

  • Accommodate partial receipts by updating order lines on PO and related SO
  • Update inventory receipt location to related sales order
  • Automatic shipment confirmation of related sales order


Shipment Confirmation (P4205)

  • Prevent shipment of sales order prior to receipt of related purchase order


An extended benefit of the new functionality is the ability to track the location of drop ship items from the time they leave your supplier’s warehouse to their final destination (via receipts routing).


For more information about the Direct Ship Order Entry program, please see Direct Ship Orders (Doc ID 626663.1).

COLLABORATE 16 offers the perfect opportunity for JD Edwards customers to explore new product releases and trends including Cloud, Big Data, security IoT, and mobility. JD Edwards customers should attend to hear more on these topics and discover solutions through knowledge sharing and networking with customers facing the same challenges in their organizations.

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

The Preferred Cost Center Preference allows the default of a detail Branch Plant (BP) on the sales order detail line based on preference profile set up.


Isn’t this Inventory Commitment Preference Profiles? It is, but it is specifically meant only to do the following:

  1. Default a Preferred BP for any given product at the sales order detail level regardless of the availability of an item.
  2. Default a Preferred BP in the detail even if the item does not exist on the header BP.


This preference:

  1. Does not exist on Preference Profiles P4007 set up. It uses the set up for Inventory Commitment Preferences.
  2. Must be flagged on the Preference Selection P40400 batch program.
  3. The version of the P40400 must be attached to sales order entry P4211 to preference the BP.


For more on using a slimmed down version of preferred cost center for sourcing inventory read document Preference Profiles in Sales(Doc ID 626656.1) / section Preferred Cost Center.

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

Did you know that as of Worldsoftware Release A9.3, you can now incorporate costs from the Cost Revisions file (F4105) into a formula based adjustment?

  • When you set up a formula based adjustment in Price Adjustment Detail (P4072) you are now required to input a Cost Method.
  • You use field COUNCS to reference an F4105 cost in a formula.
  • The system knows to retrieve a cost from the F4105 based on the Inventory Cost Level assigned to the item in Item Master Information (P4101).

In addition, there are opportunities for you to incorporate sales order unit price (SDUPRC) into a formula, the value now retrieved is the most recent net price for the sales order line. Clients on A9.3 who want SDUPRC to represent base price can change the field to SDLPRC (list price).

  • Increased Security for Cost and Price Information
  • New Advanced Pricing Report
  • Improved Calculations and Formulas
  • New Functionality for Free Goods
  • Added Flexibility for Reprice Adjustments
  • Better Visibility for Rebates
  • Improved Usability


Given the new Increased Security for Cost and Price Information you’ll need to find another way to spend your time, instead of worrying.  Many the concerns can now be alleviated with the ability to do the following.

  • Suppress cost related fields in Customer Service Inquiry
  • Suppress price related fields in Customer Service Inquiry
  • Suppress cost related fields in Check Price & Availability
  • Set “No Base Price in Effect” Notification at Order Entry

To further put your mind on easy street, and eliminate the guesswork, you can now generate a report displaying the end price for each of your items after price adjustments are applied. The report also displays the individual adjustments used to derive the end price for each item. While you’re taking it easy make sure you rest your fingers and allow the system to print prices by customer, customer group, or by item for you.  Lastly don’t doubt for a moment that all this convenience can be yours even in conjunction with the Electronic Document Delivery system and BI Publisher.


Check out the added flexibility of our versatile World A9.3 Advanced Pricing functionality!  See World A9.3 Enhancements to Advanced Pricing(Doc ID 1451682.1).

calendar.jpgFiscal year end is approaching and your business objective is to process all reported activity for Work Orders during the current fiscal year to result in a 'balanced' cutover in Manufacturing Accounting, and, start the new fiscal year with new costs for new WO activity reporting.


When and the frequency to change frozen manufacturing and inventory costs is a business decision.  However, bad timing in the execution of the final cost change could create unwanted WIP variances and imbalances between inventory values and the corresponding accounts in the General Ledger.

Unwanted and unexpected Work Order Variances, (Planned, Actual and Other) can be produced due to frozen cost changes done to items in ‘open’ Work Orders. So, it is clear now that before a cost update first you need to process open and partially completed work orders that have pending accounting activity not yet reported in the books (unaccounted units).
By generating and posting these transactions, before a final cost change, you’ll process the manufacturing journal entries at the same cost that was used to report the work order hours and your inventory activity in the Cardex.  Manufacturing Accounting will clear the unaccounted fields and the Work Order Production file will be ready to be used by the Work Order Variances program to generate the calculated IV transactions.


It never hurts to review, re-evaluate or change the steps of your yearly process. It is a good opportunity for brainstorming and sharing some best practices and considerations with your team.  Many of the steps delimited you may already be familiar with when you upgraded. The main objective was and is to ensure a ‘clean’ cutover in Manufacturing Accounting.  Review our previous blog Upgrade Best Practices for Discrete Work Orders  – JD Edwards World  as well as section "Planning a Mass Cost Update" in Standard Cost Simulation (P30820), Cost Update (P30835) and WIP Revaluation (P30837) in A8.1, A9.1 Onward (Doc ID 1541652.1).


Remember, a ‘closed work order’ term and status in manufacturing is driven by the value updated in field Variance Flag (PPFG) stored in the Work Order Header file.  Yes, the Work Order status plays a role too as it informs users what stage has been completed during the work order activity reporting.  However, the manufacturing accounting programs and some reports will validate the PPFG value to confirm if a WO has been fully completed, processed and ‘closed’ in the General Ledger.  While the WO status field in the header can be easily changed by a user aside programs setup to do so, if the variance flag is not set to a closed status, for the system this order is still considered open and active, even if the status in the header is 99.  For a better understanding of this concept, review Purpose of the Variance Flag (PPFG) In Manufacturing (Doc ID 661187.1).

Reporting for the Affordable Care Act (ACA) is just around the corner.  Here are a few things you should know:


Centralized Information Repository
JD Edwards World and EnterpriseOne have created a centralized knowledge document to assist in providing you information pertaining to ACA. Refer to JD Edwards EnterpriseOne and World – Affordable Care Act Overview (Doc ID 2038044.2) before logging a service request as this document just might answer your questions!

Service Request Create
In the event you need to enter an SR, please ensure that the Product and Component (Problem Type) are correct.  You should enter:

Product = Human Resources Management

Component (Problem Type) = Affordable Care Act

Advisor Webcasts
Register for the next Advisor Webcast:  Affordable Care Act - Preparing for Reporting for EnterpriseOne (December 15th)  and World (December 9th).

Relax, Kick Up Your Feet, Network

Join us for a fun and relaxing happy hour at the annual My Oracle Support Monday Mix. This year's gathering is Monday, October 26 from 6:00 to 8:00 p.m. at a new location—Fang Restaurant—a half-block from Moscone Center on Howard Street.

After a busy day at Oracle OpenWorld, take a break and unwind with your peers. Stop by and get to know the Oracle Support Engineers you depend on, as well as key Oracle Support executives and developers over drinks and hors d'oeuvres at Fang—a family owned restaurant known for its exciting and seasonal fare.

Admission is free for Premier Support customers with your Oracle OpenWorld badge.

Visit the Monday Mix event web site for more details. We'll see you there!

Monday, October 26, 2015
6:00 - 8:00 p.m. PT

Fang Restaurant
660 Howard St. @ 3rd St.
San Francisco, CA

Fang logo

Fang logo used with permission.

Have you struggled for a solution to error message 0027 - User Defined Code Error?  If so, you're not alone. Customers often log service requests and perform searches to understand and troubleshoot this error.


The challenge with the 0027 - User Defined Code Error which states: “The entered code was not found in the User Defined Codes” is that the Item/Account Number (UITM) or Description (DSC1) field is highlighted and neither field is associated to a user defined code (UDC).  Due to this you do not know which UDC is in need of correction.


Troubleshooting Voucher Match (P4314) (Doc ID 1531063.1) provides help with this issue. Section D. Error 0027: User Defined Code Error explains that this issue is new to the A9.2C1 release, and occurs when one of the address book category codes assigned to the supplier is not valid. Document 1531063.1 provides step by step instructions on how to identify and update the UDC table in error so the error is no longer given. The document also contains information about a list of UDC tables that do not contain blank as a valid value.  Adding the “blank” value to these tables may also help correct the 0027 error issue from occurring in the future.

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.