ICPLANORD – Inventory Planned Order File
- System
- Inventory Control (IC)
- Prefix
IPL- Primary key
COMPANY,LOCATION,ITEM,PERIOD-DT- Fields
- 17
- Updated by
- 2 programs
- Referenced by
- 2 programs
ICPLANORD is the Inventory Planned Order File table in Lawson Inventory Control (prefix IPL). It is indexed by COMPANY, LOCATION, ITEM, PERIOD-DT (IPLSET1); alternate indexes: IPLSET2, IPLSET3 and IPLSET4. It is related 1:1 to APCOMPANY, ICCOMPANY, ICLOCATION, ITEMLOC, ITEMMAST, APVENMAST and APVENGROUP. It is updated by DR100 and DR25.1 and referenced by DR40.1 and DR42.1. The table has 17 fields, 4 indexes and 7 documented relations.
About ICPLANORD
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.
Fields (17)
Column = COBOL field name without the IPL- prefix, hyphens → underscores. Derived fields are computed by the application and are not stored. PK = primary key (present in every index); SETn = leading/alternate key of that index.
| Field / column | Type | Description & values | Updated by |
|---|---|---|---|
#IPL-COMPANY PKCOMPANY | Numeric 4 | Identifies the AP company if the resource type = V. Identifies the HR company if the resource type = E. It is blank for type A, P or Q resources. | DR100 |
#IPL-LOCATION PKLOCATION | Alpha 5 | This field contains a valid stock location within the company inventory. This location represents the location doing the planning. | DR100 |
#IPL-ITEM PKITEM | Alpha 32 | This field contains the item identifier. | DR100 |
#IPL-PERIOD-DT PKPERIOD_DT | Numeric 8 (yyyymmdd) | 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. | DR100 |
#IPL-PLAN-RECV-DT SET3PLAN_RECV_DT | Numeric 8 (yyyymmdd) | This field contains the date the planned order is to be received at the planning location. | DR100, DR25.1 |
#IPL-PLAN-SHIP-DT SET2PLAN_SHIP_DT | Numeric 8 (yyyymmdd) | This field contains the date that the planned order is to be shipped from the source. | DR100, DR25.1 |
#IPL-VENDORVENDOR | Alpha 9 (Right Justified) | This field contains the vendor's identification code. | DR100 |
#IPL-FR-LOCATION SET2FR_LOCATION | Alpha 5 | This field contains the location from which the item is ordered or supplied. | DR100, DR25.1 |
#IPL-CREATED-DTCREATED_DT | Numeric 8 (yyyymmdd) | This field contains the date the planned order was created. This field is updated by the system. | DR100 |
#IPL-CREATED-TIMECREATED_TIME | Numeric 6 (hhmmss) | This field contains the time the planned order was created. This field is updated by the system. | — |
#IPL-BUYER-CODE SET4BUYER_CODE | Alpha 3 | This field contains the user-defined buyer identifier. This is used by the buyer for planning. | DR100 |
#IPL-FIRM-DEMANDFIRM_DEMAND | Signed 13.4 | This 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. | DR100 |
#IPL-REMAIN-FORCSTREMAIN_FORCST | Signed 13.4 | This 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. | DR100 |
#IPL-SCHED-RECEIPTSCHED_RECEIPT | Signed 13.4 | This 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. | DR100 |
#IPL-PROJ-AVAILPROJ_AVAIL | Signed 13.4 | For 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. | DR100 |
#IPL-PLAN-ORDERPLAN_ORDER | Signed 13.4 | This 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. | DR100, DR25.1 |
#IPL-FIRM-PLAN-ORDFIRM_PLAN_ORD | Signed 13.4 | This field contains the quantity of planned orders that fall within the planned order period cutoff parameter. These planned orders turn into unreleased purchase orders. | DR100 |
Indexes (4)
Keys are listed in index order; ↓ marks a descending key. Every documented Lawson index is unique unless flagged Duplicates; Subset indexes carry a Where condition.
| Index | Keys | Flags | Condition | Used in |
|---|---|---|---|---|
IPLSET1 |
| Primary | DR100, DR25.1, DR40.1 | |
IPLSET2 |
| KeyChange, Subset | Where FR-LOCATION != Spaces And PLAN-SHIP-DT > Zeroes | DR100, DR25.1 |
IPLSET3 |
| KeyChange, Subset | Where PLAN-RECV-DT > Zeroes | DR25.1 |
IPLSET4 |
| DR42.1 |
Relations
One to one (7) — lookups and parents
| Relation | Table | Rules | Condition | Field map | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Apcompany | APCOMPANY | Required |
| ||||||||||
| Company | ICCOMPANY | Required |
| ||||||||||
| Iclocation | ICLOCATION | Required |
| ||||||||||
| Itemloc | ITEMLOC | Required |
| ||||||||||
| Itemmast | ITEMMAST | Required |
| ||||||||||
| Vendor | APVENMAST | Required |
| ||||||||||
| Vendorgroup | APVENGROUP | Required |
|