Skip navigation
1 2 Previous Next

JDE EnterpriseOne Support Blog

27 Posts authored by: Peggyhr-Oracle

A new processing option has been added to Returned Materials Authorization (P400511) in 9.2 to provide the flexibility when creating purchase orders. The new processing option allows user to specify if the Branch Plant and location defined in the RMA defaults will be populated to the purchase order fields or if the values from the original sales order are used for the purchase order.


See KM document E1: 42: RMA Receipt Location as Defined in Return Materials Authorization Defaults (P40052) Able to be Used When Performing the Credit Order from History Function in Returned Material Authorization (P40051) (Doc ID 2619716.1) for a review of the objects updated and a sneak peek at the new processing option.

Purchasing Clipart - Clip Art LibraryA recent enhancement in 9.2 updated the PO wrapper functions to include the managerial cost codes and types from the Purchase Order Detail Tag File (F4311T) in the generated XMLs for RTPOOUT and RTPOOUT2. ESU for Bug 30446174 delivers the updated objects.


For a complete list of the updated objects, see KM document E1: 43: Cost Object and Cost Object Type Fields in Purchase Order Detail Tag File (F4311T) Added to Generated XMLs for RTPOOUT/RTPOOUT2 (Doc ID 2538769.1).

Many customers have requested the functionality to use the Batch Transportation Shipment Confirmation UBE (R49500) to confirm Standard and Standard Intransit loads. With the 9.2 enhancement available in the ESU for Bug 13012700, Batch Transportation Shipment Confirmation (R49500) has been modified to allow confirmation of Standard and Standard Intransit loads. Compartmentalized and Compartmentalized Intransit loads cannot be confirmed in batch and still must be confirmed interactively using Work with Loads / Load Confirmation (P4960/P49640).


Two new processing options have been added to R49500. The first processing option allows users to choose to retain the current functionality to disable load confirmation or to activate the functionality to enable load confirmation. The second new processing option  allows users to specify a version of Transportation Load Confirmation (P49640) during the load confirmation process. The P49640 version indicates the load, shipment, and sales order status values used for confirming standard Intransit and standard Non-Intransite loads.


For complete information, see our knowledge document Transportation Batch Ship Confirm (R49500) Allows Confirmation of Standard and Standard Intransit Loads (Doc ID 2161470.1)

Record reservation functionality is available in a number of programs in EnterpriseOne.  With a recent 9.2 update, record reservation has been added to the Print Delivery Notes UBE (R42535) in the 9.2 release. With the ESU installed, if a record is reserved by another program Print Delivery Notes (R42535) will not process the record.


See Record Reservation Functionality in Print Delivery Notes (R42535) (Doc ID 2601784.1) for the Bug / ESU information along with post install instructions.

Address Book Data Security / Data Privacy allows you to restrict users from viewing sensitive Address Book information. After performing the required setup for this feature, secured users will be able to see the secured fields, but these fields are populated with asterisks.  These fields are also disabled so no changes can be made.


A recent update in the 9.2 release ensures your Address Book Data Privacy carries over to the Purchase Order Entry application (P4310).  See  Data Privacy Setting Functionality Available in Purchase Order Entry (Purchase Order Entry) (Doc ID 2565600.1) for the 9.2 Bug / ESU information.


For more information about Address Book Data Privacy, see How To Set Up Address Book Data Privacy In JD Edwards EnterpriseOne (P01138) (Doc ID 1517572.1).

Historically, there has been a difference in the Soft Rounding calculation between Sales Orders and Purchase Orders when using an Item Group (Purchasing Taxable) for Multiple Tax Rate configuration. In the Sales Order module, when Sales Update (R42800) creates Accounts Receivable records (F03B11/F0911), a Soft Rounding for Tax Calculation is done grouped by Tax Area and Item Group. In the Purchase Order module, when Match Voucher to Open Receipts (P4314) creates Accounts Payable records (F0411/F0911) a Soft Rounding for Tax Calculation is done grouped by Tax Area only. The Item Group (Purchasing Taxable) was ignored.


An enhancement is now available in releases 9.1 and 9.2 that allows users to choose to enable Voucher Match Tax Rounding by company for Accounts Payable.


For more information see Enhancement Available in Match Voucher Match to Open Receipts (P4314) to Allow Soft Rounding for Tax Calculation Grouped by Tax Area and Item Group (Doc ID 2475356.1).

You asked. We delivered.


Historically in sales order entry, in order to use existing Available to Promise (ATP) or Cumulative Available to Promise (CATP) calculations to determine a Delivery Date during current sales order entry, the user must exit to the Supply/Demand Inquiry form where the date is displayed and then return the date.


An Enhancement is now available in the 9.2 release that streamlines the sales order entry process by allowing for automatic population of sales order dates without having to access the Supply/Demand Inquiry form.


The new functionality automatically populates the pick date without having to access the Supply/Demand Inquiry form when the user enters a sales order line for a quantity of an item and tabs to the next line without entering any dates.


For more information see Enhancement Available in Sales Order Entry (P4210/P42101) to Automatically Return Pick Date from Available to Promise (ATP) or Cumulative Available to Promise (CATP) (Doc ID 2555461.1)

Have you ever identified a batch that posted completely but not correctly?


Maybe, during your review of integrity reports you identified a batch where the AE entry was not created but the remainder of the entries in the batch are posted. Or, you may have identified a batch where the debits do not equal the credits but all the entries in the batch are posted.


After researching the batch, you identify the amounts and accounts that are missing entries.  Now what?


How do you create a journal entry, or multiple journal entries, to bring the batch back into balance? How do you create a one-sided journal entry and then successfully post the journal entry to update the Account Ledger (F0911) and the Account Balance (F0902) tables?


Our knowledge document How To Create and Post a One-Sided Journal Entry (Doc ID 2513031.1) walks you through successfully creating and posting a one-sided journal entry.


Are you using the customer credit limits and credit hold codes to effectively manage accounts receivable?


Credits granted to your customers are similar to financial loans.  Effective use of the credit limit ensures that the amount of credit granted a customer aligns with the financial abilities of each customer.


Setting up a credit limit on a customer account does not mean that new sales orders cannot be created for the customer. In EnterpriseOne, credit holds can be setup based on the customer's credit limit or based on the age of open accounts receivable.  A credit hold on a customer's sales order(s) will prevent further processing of the order, to reduce your risk.  You don't always want to ship items to customers who are poor payers, customers with a history of late payments or missed payments.


Did you know that you can record information for credit insurance policies (insured credit limit) in EnterpriseOne?


Don't get caught with large noncollectable accounts receivable balances. Review the functionality available in EnterpriseOne in Credit Checking (Doc ID 2319760.2).



8iE6jn6bT.gifMany suppliers have a business process where they cannot invoice customers until the customer confirms delivery of the product, which completes the supplier’s performance obligation. The elapsed time between shipping and delivery can be as great as 60 days. With this business process, suppliers cannot recognize revenue until the invoice has been posted, which must occur after the performance obligation. Also during the in-transit period the shipping company continues to have legal ownership of the product until it has been accepted by the receiving customer.


During this period, the value of in-transit inventory must remain on the balance sheet of the shipping company until the material is received and accepted by the customer. Invoicing and Sales Update processing must be delayed until the material is received and accepted at which time the legal ownership is transferred from the Supplier to the Customer.


An enhancement is available in the 9.2 release of JD Edwards EnterpriseOne to provide the functionality to create journal entries for In-Transit Inventory at the time of Ship Confirm (P4205).  For additional information see 9.2 Enhancement - Retaining Ownership of Inventory While In Transit (Doc ID 2246772.1).

An enhancement is available for JD Edwards EnterpriseOne 9.2 customers using the distribution modules.  Refresh Inventory Commitments (R42990) refreshes any inventory commitments in F41021 (Item Location File) where the item does not have any active sales orders associated with it. The existing program, Repost Active Sales Orders (R42995) refreshes the commitments for only those items that have an active sales order. There may be a case where the sales orders are all completed for an item but for some reason there is still an outstanding commitment recorded in F41021 that needs to be cleared out. R42995 will not update this item in F41021.


Prior to the enhancement, if no active sales orders exist prior to running the Repost Active Sales Orders (R42995), when R42995 was run for locations that have hard/soft committed buckets filled but no open orders in the Sales Order Detail (F4211) exist, commitments would not be cleared for those Item Locations in the F41021 file. One workaround involved creating a 'dummy' order for the specific item so that R42995 would correctly repost the order. The 'dummy' order would then need to be cancelled after running the Repost Active Sales Orders (R42995) program. Another workaround involved using a database utility program such as SQL to clear the commitment buckets in the Item Location (F41021) prior to running the Repost Active Sales Orders (R42995). This process was more efficient if numerous items need to have the quantities and amounts reposted but do not have an open order in the Sales Order Detail (F4211). This process eliminated the need to create and delete what could be many individual "dummy" orders.


For complete information on the enhancement, see Refresh Inventory Commitments (R42990) (Doc ID 2230896.1).

Companies can use Receipt Routing to track the movement of items as they leave the Supplier's warehouse until they arrive in stock through a series of operations that make up a Receipt Route. Depending on the operations, several steps may exist, such as dock, staging area, inspection, and so forth.


Any company that has a multi-step receiving process can benefit by using a Receipt Route. Receipt Routing allows companies to locate goods at any point within the routing process, which can be setup to track from the "in transit" operation to stock. A Receipt Route can be setup to require testing or inspection where samples are tested to determine the quality of the goods. Unacceptable goods, regardless of how they are found, can be dispositioned during any step prior to being placed into stock. Quantities that are dispositioned will not continue in the receipt route and will not be included in stock. Dispositioned items can be eligible for payment if the system is setup that way.


For an all inclusive document on receipt routing, review Receipt Routing (Doc ID 2101173.2).  You will find all the information on route setup, disposition, reviewing each movement of an item through a receipt route, the AAIs used in receipt routing , examples of transactions and much, much more.

Do Unit of Measure Conversions puzzle you?  How does unit of measure conversion work in JD Edwards EntepriseOne?


In order to perform daily operations and process business transactions successfully, all businesses  that distribute products (inventory) require two types of unit of measure conversions: Item Unit of Measure Conversions and Standard Unit of Measure Conversions.


What is the difference between item unit of measure conversion and standard unit of conversion? What setup is required for unit of measure conversion? How is unit of measure conversion used in Procurement? In Sales?


Review our knowledge document Unit of Measure Conversion (Doc ID 2102783.2) for the answers to these questions. Additionally, you will find information for troubleshooting common errors and specific errors.  And, much more!


Do you need to track inventory in one unit of measure and transact and calculate price in a different unit of measure?  If so, dual unit of measure functionality may be the solution for your business.  Check out our knowledge document  Dual Unit of Measure (Doc ID 625673.1).

The difference between a lot controlled item and a serialized item is that  quantities for receipt or shipment from a lot number are only limited by availability. It is not possible to receive or ship a quantity greater than 1 of a specific serial number.


EnterpriseOne provides two methods for managing serial numbered items. One method, the older method. stores a serial number in the Serial Number (F4220) table, which has a one-to-many relationship with the Item Location (F41021) table. The second method, the newer method, stores the Serial Number in the Lot/Serial field (LOTN) in the Item Location (F41021) table. Using the newer method, it is possible to track a both a lot number and serial number by linking to the Memo Lot 1/2/3 (LOT1/LOT2/LOT3) fields in the Lot Master (F4108).


The differences in setup and functionality of the two methods of serial number control are significant and are explored  in greater detail in our new knowledge document Lot Processing and Serial Number Control (Doc ID 2094021.2).

A Transfer Order is an internal sales order used to transfer inventory from one warehouse (branch) to another. The Transfer Order program (P4210) creates both a sales order in the "From Branch", the shipping branch, and a purchase order in the "To Branch", the receiving branch.


Transfer Orders (ST/OT) are designed to be used to move quantities from one Branch/Plant to another. Non-stock items, direct ship items and other items that do not have quantities in the Item Balance (F41021) table are not appropriate for transfer orders and are  not supported. Also, kits containing a parent item with K stocking type and a bill of material with component items are not supported for Transfer Orders. The individual component items can be used for transfer orders provided the line types meet the line type requirements for Transfer Orders.


The default document types created for transfer orders are ST (sales order) and OT (purchase order), and are often referred to as an ST/OT order. When a sales transfer order (ST) order is created, the purchase transfer order (OT) is also created, regardless of whether the "Generate Purchase Order" flag is activated or not in the line type constants (P40205). Additionally, the Transfer/Direct Ship/Intercompany field (SDS011) in the Sales Order Detail file (F4211) is marked with a '1', indicating a transfer order.


Transfer Orders have unique setup considerations compared with regular customer sales orders which will be discussed in detail in document Transfer Order (ST/OT) (Doc ID 2094796.2).

Filter Blog

By date: By tag:

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.