Use this page to enter historical transactions that you want to become historical data (historical demand) in demand planning. Note that you must alter the flow setup in Demand Planning to get these transactions read into Demand Planning. There are two main ways of using this component. The first one is that only the transactions entered to this list will become historical data in Demand Planning. For this purpose, you only need to enter the Site, Part No, Issue Date, Issue Qty and Customer No. This is all you need to create forecasts with multiple base flows. This is an easy way of getting customer data imported into Demand Planning. You can only enter transactions on sales parts in this form.
The second one is a join between transactions written in this list
and ordinary transactions in IFS Cloud.
The HIST_EXT_INVENT_PART_ISSUE view has only the manually entered historical data from this view.
The EXTERNAL_INVENT_PART_ISSUE_PUB view is based on IFS Cloud customer ordres, this will include data based on all customer orders avalible in your IFS Cloud implementation.
The COMB_EXT_INV_PART_ISSUE_PUB view is the view here IFS cusomer orders and the manualy entered historical data (HIST_EXT_INVENT_PART_ISSUE) in this view are joined togheter, so basing the flows on this view Demand Planning will read historical data both from the manualy entered hisotrical data in this form and IFS customer orders.
Note: You do not need to enter values into all the
fields in the list; which ones to use varies with the task in hand. If you
are planning to combine the entered historical transactions with actual
ordinary transactions, you must use the same fields as the fields that you
plan to use in the base flow SQL from the original transactions. If you are
using this tool to enter customer transactions, you can choose which field
you want to use freely. However, you need to enter at least the Site, Part
No, Issue date, Issue Qty, and Customer No. If you need more than Customer
No to create the base flows, you will need to specify more direction fields.
As quantity fields it is normal to use one of these: Issue
Qty, Desired Qty, Planned Qty, Net Price, Weight, Volume, Expected Average
Price, Base Price.
As date fields it is normal to use one of
these: Issue Date, Desired Date, Planned Date, Promised Date.
As where clause fields it is normal to use one of these: Sales Part
Group, Sales Price Group, Customer No, Customer Group, Customer, Category,
Market, Region, District, Country, Salesman.
None.
Depends on the Demand Plan flow setup historical data will get changed.