Skip navigation

Do you have preset trade-in values for certain products but the customer doesn't always have a trade-in when they order the product? 


You can maintain two adjustment schedules where one excludes the trade-in allowance and the other includes the trade-in allowance. When an order is entered for an item that is eligible for a trade-in allowance, the schedule that excludes the trade-in allowance will default in, but if the sales person entering the order determines the client has a trade-in, they can change the adjustment schedule that defaults on the line to pull in the trade-in allowance.


Review the our knowledge document How to Retrieve a Trade-in Allowance Using a Second Adjustment Schedule (Doc ID 2061768.1) for the setup and processing of the two allowances.

JD Edwards EnterpriseOne announces the availability of JD Edwards EnterpriseOne Outbound Inventory Management in EnterpriseOne 9.1 and 9.2.


JD Edwards EnterpriseOne Outbound Inventory Management system, system 42I, for suppliers is an integral part of the supply chain management and order management processes. Suppliers can use it with the JD Edwards EnterpriseOne Inventory Management and Sales Order Management systems to manage inventory that they produce and ship.


Some of the most important features of the JD Edwards EnterpriseOne Outbound Inventory Management system include:


    Establishing agreement between supplier and buyer for moving inventory between their locations.

    Ship consigned and vendor managed inventory to customer’s location.

    Acknowledge receipt of outbound inventory at the customer’s location.

    Report consumption of outbound inventory from customer’s location.

    Manual or automatic replenishment of stock.

    Manual or automatic billing for outbound inventory.

    Timely information and reports to review inventory status and ownership.

    Return unused or damaged inventory.


You use the JD Edwards EnterpriseOne Outbound Inventory Management system to manage consigned inventory and vendor managed inventory (VMI).


For additional information, see Outbound Inventory Management Enhancement Available in EnterpriseOne 9.1 and 9.2 (Doc ID 2056248.1).

workflow.jpgLook no further.


Example of a Custom Workflow using the Action Message Task with a Distribution List (Doc ID 2041057.1) illustrates, step-by-step, an example of a custom workflow using the new Action Message Task which is the Send Message Extended system function rather than the obsolete Message Task which is using the deprecated Send Message system function. The custom workflow example also shows how a single level distribution list can be used.

Rounding2.jpgWhen using Match Voucher to Open Receipt (P4314) to voucher match a multi-currency order with retainage, a mismatch between the F43121, F43121T, F0911, and F0411 can occur resulting in R09801 post failing and producing an R09801E Out of Balance Post Error Report.


A new processing option has been added to Match Voucher to Open Receipts (P4314) to address the small variance calculated during voucher match.



Before the enhancement, rounding issues existed when a logged voucher was matched with purchase order lines that included. Additionally, before the enhancement, rounding issues existed when a non logged voucher was matched with retainage entered at voucher match. Taxes were calculated for one single amount of the logged voucher while the purchase order may contain many lines. A small difference may result between the logged voucher total amount and the amount posted to the general ledger. For non logged vouchers, the small difference may results when retainage is calculated for the amount during voucher match.


A difference caused by the prior logged voucher issue is calculated by checking the amount of the voucher and comparing it with the total of the general ledger amount. This entry is recorded in the purchaser order detail account (DMAAI 4332) depending on "Voucher Match Variance Account" flag (ON/OFF) in Line Type Constants. The difference is recorded only when the Last Chance Variance is ON in the P4314 processing option.


For non logged voucher, the difference is written to the purchase order detail account (DMAAI 4330) when the processing option Account For Rounding Differences in Process tab of P4314 is populated with a value and the difference is within the value in the processing option.


Note: Only the above mentioned rounding scenarios are handled in this bug. Scenarios such as large amount variances caused by changing an amount during voucher, variances caused by changing the exchange rate during voucher, and/or variances caused by changing tax amounts during voucher are not handled under this bug.


To obtain the enhanced functionality, install the ESU for the following Bug:

Percent.jpgThe Percent To Fill field provides you with the flexibility to fill an order line from one or more branch/plants. The Inventory Commitment preferences work with the system's normal checking that is done for quantity available, and adds a check on all branches that are defined in the preference.


What you should know when using Inventory Commitment Preference

  • You must activate the Inventory Commitment preference through a separate processing option in the Sales Order Entry program (P4210).
  • The Inventory Commitment preference does not function with kits or configured items.


If the value in the Percent To Fill field is zero percent (0%), the system performs normal processing. The system performs no checking for the quantity on hand.  Regardless of the quantity on hand, it is shipped to fill the order.


If the value in the Percent to Fill field is between 1 and 99 percent (1-99%), the system requires that any branch must be able to fill the percentage that is specified. If the branch can fulfill the percentage, the quantity available is shipped and the remainder is transferred to the next branch. The system checks each branch to determine if the quantity can be shipped.


If you specify a percent-to-fill value of 100 percent (100%) for each of several branch/plants, an order can only be filled from a single branch/plant that has sufficient quantity to fill the order. If no branch/plant has sufficient quantity to fill 100 percent of the order, the order is put on backorder or partially shipped from the first preference branch/plant that it can satisfy.


If the percent to fill value is 100 percent (100%), the system requires that the branch must be able to ship the entire quantity. This prevents shipping from multiple branches, but enables the system to check all branches to determine if the entire quantity can be shipped. If you specify a percent-to-fill value of 100 percent for each of several branch/plants, an order can only be filled from a single branch/plant that has sufficient quantity to fill the order. If no branch/plant has sufficient quantity to fill 100 percent of the order, the order is backordered or partially shipped from the first preference.


For additional information, see Inventory Commitment Preference Basic and Advanced Profiles (Doc ID 1641298.1).

video.jpgCheck out our these great sales and procurement documents that include videos                                                                      



  • Line Types in Sales [Video] (Doc ID 985506.1)
  • Sales Order Templates [Video] (Doc ID 1479659.1)
  • Backorders in Sales FAQ [Video] (Doc ID 763476.1)



ic-Cloud-red.pngWe are pleased to announce the availability of JD Edwards EnterpriseOne enhancements to ensure JD Edwards EnterpriseOne standard business interfaces, such as business services and embedded UI can be leveraged by Oracle Sales Cloud customers to coexist. Two new One View Reports are also now available.


The enhancements include:

  • Business Services - a new method on Customer Manager – getCustomerV3 that provides the ability to search by customer address.
  • Business Services - new methods on SalesOrder Manager – getSalesOrderV4 and processSalesOrderV5 that support query and updates of opportunity ID info through BSSV.
  • Sales Order Entry (P42101)  – added the Opportunity ID field (OPPID) to the grid for queries by Opportunity ID.
  • One View Sales to Date Inquiry (P42272)  – added two new OVR reports, Sales by Opportunity and Opportunity Trends.
  • Item Batch Outbound (R4101ZO) – provide new XML export capability of the Item Master Information.


For more information on the integration and affected objects, refer to the following documents:

  • JD Edwards EnterpriseOne Announces Enhancements to Support Oracle Sales Cloud (Doc ID 1906361.1)
  • Integrating Oracle Sales Cloud with JD Edwards EnterpriseOne (Doc ID 1645923.1)

budget.jpgBudget Checking is fairly simple to understand if budgets are not being accumulated. If budgets are not set to accumulate in the Purchase Order Entry (P4310) processing options, then the only budget considered will be the one attached to the expense account on the purchase order detail line.


The majority of questions and issues are with regard to budget accumulation. One thing that many users are not aware of when upgrading is that E1 fundamentally changed how accumulation works in release 8.9 and above.


In releases XE and 8.0, budget accumulation was done by object account. This method allows users to set budgets based upon object account hierarchies.


The functionality changed beginning with EnterpriseOne release 8.9.  Beginning with release 8.9, budget accumulation occurs at the business unit level. This means that every account within the business unit can lend its budget to any other account within the business unit, regardless of object account set up.


There are two ways that budgets are accumulated in E1:

    1. Accumulation is done based upon object account. This is the functionality in releases XE, 8.9, and 9.1*.

    2. Accumulation is done based upon business unit. This is the functionality in releases 8.9, 8.10, 8.11, 8.11SP1, 8.12, 9.0, and 9.1*.


*Note that release 9.1 is in both examples above. In 9.1 Bug 18235598 changes the accumulation logic to accumulate by Object Account rather than Business Unit. If the ESU for Bug 18235598 is applied in your 9.1 environment, it is critical to understand the difference before testing Budget Accumulation.


For additional information on budget accumulation and budget checking, review the following documents:

balance.jpgIn JD Edwards EnterpriseOne,  transactions impacting inventory must create balanced entries in the Item Ledger (F4111) and the General Ledger (F0911) in order to maintain the integrity between these two tables. Examples of inventory transactions can be: Inventory Adjustments, Inventory Transfers, Sales Update for a Sales Order, the receipt of a Purchase order, the completion of a Work Order, etc.


Sometimes, discrepancies occur. It is important to identify and correct these discrepancies to ensure that the Item Ledger and the General Ledger are kept in balance.


The existing Item Ledger/Account Integrity (R41543) report is based on DMAAI setup, which limits its functionality, as the link between the inventory transactions and the previous G/L accounts is lost if users change the DMAAI setup.


New functionality has been introduced in JD Edwards EnterpriseOne Release 9.1 Update 2 that simplifies the reconciliation process between Inventory and G/L by means of the following key features:

  • There is a new flag (GPF1) introduced in the Account Ledger (F0911) table that identifies the records corresponding to inventory transactions. This flag is automatically updated to ‘1’ for the F0911 records created by new inventory transactions.
  • There is a new batch process (Inventory to G/L Reconciliation Update/R41501) that can be used to flag the F0911 records created by inventory transactions that occurred prior to the implementation of this functionality.
  • A new batch process (Automatic Inventory to G/L Reconciliation UBE/R41500) allows to automatically reconcile transactions without a variance.
  • A new Interactive application (Manual Inventory to G/L Reconciliation/P41500) allows users to review, reconcile and un-reconcile the Item Ledger and Account Ledger transactions. Users can select adjusting journal entries to reconcile transactions with variances.
  • Both the Item Ledger (F4111) and the Account Ledger (F0911) will be updated with reconciliation information when transactions are reconciled. In the Item Ledger, the Reconciliation Date will be updated. In the Account Ledger, the Reconciliation Code, Reconciliation ID and Reconciliation Date will be updated.


9.1 Enhancement - Inventory to G/L Reconciliation Process (Doc ID 1678098.1)

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.