Skip navigation
1 2 3 Previous Next

JDE EnterpriseOne Support Blog

1,501 posts

QuestIcon2.pngCapex, an Argentina based energy company upgraded to #JDEdwards EnterpriseOne 9.2 to leverage our latest features. Read their upgrade story at Quest Oracle Community http://bit.ly/2xEt4rj

Collab20.pngSave the date. We’ll deliver a series of live #JDEdwards Keynote and Roadmap sessions digitally on April 20. Join Lyle Ekdahl, Bob Monahan, Gary Grieshaber and Jeff Erickson for updates on your JDE solutions.

Reader.pngThis new KM document talks about the impact of changing the mailing address on open and closed Sales Orders. Doc ID 2639193.1. http://ora.cl/oc32B

Reader.pngThis new KM document provides an example to calculate the total (sum) of column values in a table using orchestration. Doc ID 2638066.1. http://ora.cl/bN1pX

attention.jpgPremier Support for applications release 9.1 ended on March 31, 2020. While you can remain on JD Edwards EnterpriseOne 9.1 and continue to acquire Sustaining Support for access to our Global Services team, as well as access to existing fixes for known 9.1 issues, we highly recommend you consider upgrading to JD Edwards EnterpriseOne 9.2. JD Edwards EnterpriseOne 9.2 is part of the Applications Unlimited commitment to continuous innovation. Oracle JD Edwards provides a commitment to offer Oracle Premier Support through at least 2030. For more information, see Doc ID 2627276.1http://ora.cl/i4bQ7

YouTube.pngHave you seen the #JDEdwards video showcasing the latest features of EnterpriseOne 9.2 that can help you transform your business? Watch on YouTube here - http://bit.ly/2Tt3YTD

Oracle_updated.png#Simplify and #Automate your #JDEdwards EnterpriseOne 9.2 experience by leveraging the latest capabilities. Learn more in this whitepaper – http://bit.ly/2wO2T0Z

LearnJDE_new.pngNow is the time to migrate from #JDEdwards World to EnterpriseOne 9.2. Visit this LearnJDE page to know everything about EnterpriseOne 9.2 - https://bit.ly/2QX0c4i

Reader.pngThis new KM document talks about purging data in Sales Order workfile tables:  Price Adjustment History Work File (F40UI74), SO Header Cache File (F42UI01), SO Detail Cache File MBF (F42UI11) and Sales Order Detail Cache 2 MBF (F42UI12). Doc ID 2637738.1. http://ora.cl/AP3wE

Reader.pngAfter updating Approval Routing codes, users are unable to edit open Purchase Orders, receiving "Invalid Approval Route Code Warning". This new KM document explains the functionality and workarounds. Doc ID 2637702.1. http://ora.cl/nV18Z 

Reader.pngThis new KM document explains where tax information (tax rate/area and tax explanation code) default from when performing a Voucher Match in P4314. Doc ID 2636625.1. http://ora.cl/Zs4eK

Reader.pngThis new KM document explains the process to create a service request for Sales Order Entry in AIS and override the Address to map the variable for the override address. Doc ID 2636567.1. http://ora.cl/km43u

As of JD Edwards EnterpriseOne Release 9.2, Oracle delivers a new functionality to determine how discounts are applied to partial payments.

 

A new processing option has been added to Known Invoice Match With Amount (R03B50D) and Known Invoice Match Without Amount (R03B50E) to determine how discounts are applied to partial payments.

 

Processing Option “Discount on Partial Payments”: Use this processing option to specify whether to apply discounts when the payment amount is less than the open amount of the invoice:

    Blank: Apply discounts for partially paid invoices. This works in conjunction with the processing option Discounts Recognition Method.

    1: Ignore discounts for partially paid invoices.

 

The new functionality is available as of JD Edwards EnterpriseOne release 9.2 and delivered via ESU. Install the latest ESU for Bug 30514617: DISCOUNTS ARE TAKEN WHEN INVOICE IS NOT PAID WHEN RUN R03B551/R03B50/R03B50D to obtain the new enhancement.

 

Please see the following Knowledge Documents for more information see New Enhancement – New Processing Option Discount on Partial Payments when Running Auto Cash (R03B50D/R03B50E) (Doc ID 2638014.1).

Forecast Consumption by Customer enhances the ability of a supplier to meet the requirements from large customers.

 

When working with large customers, you might want to consider the demand for each customer separately and plan production quantities accordingly.

 

You can set up the system to net forecasts and sales orders for a particular customer separately, so that you can plan more accurately for the specific demand coming from individual customers.

 

If you do not use the forecast consumption by customer functionality, you compare total sales with total forecast for a particular time period without considering individual customers.

 

Calculating the difference between total forecast and sales yields a different result than calculating the difference between forecast and sales for an individual customer.

 

To use forecast consumption by customer, you have to enter a forecast for a specific customer.

 

In this case, the forecast record has a customer number in the Customer Number field.

 

Based on the customer number, the system can search for sales orders with matching customer numbers in the ship-to or sold-to field to calculate the remaining demand for the customer.

 

You specify whether the system uses to the ship-to or sold-to field from the sales order by setting a processing option or by defining a customer address relationship.

 

When you run the MRP/MPS Requirements Planning program, you can set up the program to use forecast consumption by customer.

 

You can use this functionality for items that are defined with planning fence rule C, G or H. You cannot use forecast consumption logic for process items.

 

When you run the MRP/MPS Requirements Planning program and have activated the Forecast Consumption by Customer functionality, the program calculates the net difference between forecast and sales orders for a period for individual customers.

 

The process consists of these steps:

  • Check the Item Branch record for the item to see that the time fence rule is set to C, G or H.
  • Read the Forecast File table (F3460) and the Sales Order Header File table (F4201) record for each customer.
  • Compare sales orders and forecast for each customer to determine which is greater.
  • The greater value of the two is written to the F3460 as a new forecast record with a forecast type that indicates that it is the result of a Forecast Consumption by Customer calculation

 

You can use the MPS Time Series program (P3413) to review the results of the calculation. The net forecast that results from the Forecast Consumption by Customer calculation is displayed as the adjusted forecast quantity (-FCST).

 

Forecast Consumption by Customer Calculation these tables illustrate the different results that are reached, depending on whether you differentiate by customer. The first table demonstrates the results of a calculation that does not differentiate by customer:

 

CustomerSales OrderForecastGreater of Forecast and Sales Order
A10080
B400375
C700750
Total120012051205

In this calculation, you aggregate all of the sales orders and all of the forecasts for an item and compare the totals with each other. In this case, the total forecast is greater than the total sales order quantity. Therefore, the forecast becomes the total demand.

 

This table demonstrates the results of a calculation that nets each individual sales order against a forecast with matching customer number:

CustomerSales OrderForecastGreater of Forecast and Sales Order
A10080100
B400375400
C700750750
Total1250

In this calculation, the sales order and forecast quantities are not totaled. Instead, each sales order is compared to a matching forecast. The greater quantity in each comparison is added to the total demand. In this case, the total demand is greater than if the first method had been used.

 

Forecast Consumption by Customer Considerations

In order to use Forecast Consumption by Customer, you need to consider:

  • Set up a forecast type for forecast consumption by customer in the UDC table 34/DF (Forecast Type).
  • Set up a version of the MRP/MPS Requirements Planning program by using these processing options:
    • Set the Forecast Consumption Logic processing option for using forecast consumption by customer.
    • Specify the forecast type to be used for forecast consumption by customer.
    • Specify whether the system uses the sold-to or the ship-to number on the sales order when searching for sales orders to net against a forecast.

 

    If you use multi facility planning, set up a version of the Master Planning Schedule - Multiple Plant by using these processing options:

  •         Set the Forecast Consumption Logic processing option for using forecast consumption by customer.
  •         Specify the forecast type to be used for forecast consumption by customer.
  •         Specify whether the system uses the sold-to or the ship-to number on the sales order when searching for sales orders to net against a forecast.
  •         Specify whether the system treats inter plant demand as customer demand consumes the forecast.
  •         Ensure that the items for which you are creating a requirements plan are defined with planning fence rule C, G or H.

 

For more information on Forecast Consumption Logic by Customer please see Forecast Consumption for EnterpriseOne (Doc ID 625964.1).

LearnJDE_new.pngNow you can easily meet all user interface related business requirements with #JDEdwards EnterpriseOne Personalization framework. Check our LearnJDE page for more information - http://bit.ly/2WbE2ie

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