|
|
ICPLANORD FILE
Inventory Planned Order File
The Inventory Planned Order File is a repository of planned orders. Orders
are created by the Distribution Requirements Report (DR100), which takes the
supply and demand data for an item at a location over time. Based on the time
phased order point algorithm, a planned replenishment order is determined.
This file is updated with the planned order information used for inquiry and
possibly as a demand against another location.
REFERENCED BY
DR40.1 DR42.1
UPDATED BY
DR100 DR25.1
FIELD NAME DESCRIPTION/VALID VALUES UPDATED BY
IPL-COMPANY Numeric 4 DR100
Element: Company The company number represents an
established company and is entered on
all function codes.
IPL-LOCATION Alpha 5 DR100
Element: Location Code This field contains a valid stock
location within the company inventory.
This location represents the location
doing the planning.
IPL-ITEM Alpha 32 DR100
Element: Item Number This field contains the item identifier.
IPL-PERIOD-DT Numeric 8 (yyyymmdd) DR100
Element: Date This field contains the date
representing the first day of the
planned week. All planning is done by
week. The first period date defaults to
the computer date. Each successive
beginning period is calculated by adding
seven.
IPL-PLAN-RECV-DT Numeric 8 (yyyymmdd) DR100 DR25.1
Element: Date This field contains the date the
planned order is to be received at the
planning location.
IPL-PLAN-SHIP-DT Numeric 8 (yyyymmdd) DR100 DR25.1
Element: Date This field contains the date that the
planned order is to be shipped from the
source.
IPL-VENDOR Alpha 9 (Right Justified) DR100
Element: Vendor ID This field contains the vendor's
identification code.
IPL-FR-LOCATION Alpha 5 DR100 DR25.1
Element: Location Code This field contains the location from
which the item is ordered or supplied.
IPL-CREATED-DT Numeric 8 (yyyymmdd) DR100
Element: Date This field contains the date the
planned order was created. This field is
updated by the system.
IPL-CREATED-TIME Numeric 6 (hhmmss)
Element: Sys Time This field contains the time the
planned order was created. This field is
updated by the system.
IPL-BUYER-CODE Alpha 3 DR100
Element: Buyer This field contains the user-defined
buyer identifier. This is used by the
buyer for planning.
IPL-FIRM-DEMAND Signed 13.4 DR100
Element: Document TotalThis field contains the total demand of
logged customer orders from the Order
Entry and Requisitions systems. Also
included are any planned orders from
other locations that are replenished
from this location. The estimated
shipping date is used to determine which
week the customer order creates demand.
All demand due for shipping before the
current week that was not shipped is
included in the current week total.
IPL-REMAIN-FORCST Signed 13.4 DR100
Element: Document TotalThis field contains the period forecast
quantity minus the firm demand, but is
not less than zero. If the forecast is
setup as weekly, the weekly period
forecast quantity is used. If the
forecast is set up as monthly, the
quantity is divided by 4.33.
IPL-SCHED-RECEIPT Signed 13.4 DR100
Element: Document TotalThis field contains scheduled receipts,
which are the sum of open supply coming
into this location for this period. The
sum includes open purchase orders, open
intransits, and open incoming
requisitions.
IPL-PROJ-AVAIL Signed 13.4 DR100
Element: Document TotalFor the first week, this field contains
the total of the stock-on-hand minus
firm demand minus remaining forecast
plus scheduled receipts by week. If any
planned orders are calculated to arrive
this week, they are added to this
quantity. For each subsequent week, the
on-hand balance is the previous week's
on-hand balance minus the gross demand
and remaining forecast quantities plus
the scheduled receipts and planned
orders quantities.
IPL-PLAN-ORDER Signed 13.4 DR100 DR25.1
Element: Document TotalThis field contains the reorder
quantities, backed off by the leadtime,
that should be ordered to prevent the on
hand balance from becoming negative or
from going below the safety stock
quantity. Reorder quantities are printed
in the week they should be released
based on leadtime, not the week that
they are to be delivered. These planned
orders are stored here for this
location. Each one is also a demand
against another location, if the
replenishment location field is filled
in. This demand is stored on this file
as demand against the replenishment
location.
IPL-FIRM-PLAN-ORD Signed 13.4 DR100
Element: Document TotalThis field contains the quantity of
planned orders that fall within the
planned order period cutoff parameter.
These planned orders turn into
unreleased purchase orders.
ICPLANORD FILE INDEX
NAME KEY FIELDS DESCRIPTION / SUBSET CONDITION USED IN
IPLSET1 COMPANY DR100 DR25.1
LOCATION DR40.1
ITEM
PERIOD-DT
IPLSET2 COMPANY KeyChange, Subset DR100 DR25.1
FR-LOCATION Where FR-LOCATION != Spaces
ITEM And PLAN-SHIP-DT > Zeroes
PLAN-SHIP-DT
LOCATION
IPLSET3 COMPANY KeyChange, Subset DR25.1
LOCATION Where PLAN-RECV-DT > Zeroes
ITEM
PLAN-RECV-DT
IPLSET4 COMPANY DR42.1
LOCATION
BUYER-CODE
ITEM
PERIOD-DT
ICPLANORD FILE RELATIONS
ONE TO ONE RELATIONS
RELATION RELATED
NAME FILE INTEGRITY RULES / FIELD MATCH
Apcompany APCOMPANY Required
IPL-COMPANY -> CPY-COMPANY
Company ICCOMPANY Required
IPL-COMPANY -> ICC-COMPANY
Iclocation ICLOCATION Required
IPL-COMPANY -> ICL-COMPANY
IPL-LOCATION -> ICL-LOCATION
Itemloc ITEMLOC Required
IPL-COMPANY -> ITL-COMPANY
IPL-LOCATION -> ITL-LOCATION
IPL-ITEM -> ITL-ITEM
Itemmast ITEMMAST Required
ICC-ITEM-GROUP -> ITE-ITEM-GROUP
IPL-ITEM -> ITE-ITEM
Vendor APVENMAST Required
CPY-VENDOR-GROUP -> VEN-VENDOR-GROUP
IPL-VENDOR -> VEN-VENDOR
Vendorgroup APVENGROUP Required
CPY-VENDOR-GROUP -> VGP-VENDOR-GROUP
|
