retek advanced inventory planning 11.4 batch ...€¦ · global domains and simple domains ... •...

Retek® Advanced Inventory Planning ™

11.4

Batch Administration Guide Warehouse Inbound Planning

Corporate Headquarters:

Retek Inc. Retek on the Mall 950 Nicollet Mall Minneapolis, MN 55403 USA 888.61.RETEK (toll free US) Switchboard: +1 612 587 5000 Fax: +1 612 587 5100

European Headquarters:

Retek 110 Wigmore Street London W1U 3RW United Kingdom Switchboard: +44 (0)20 7563 4600 Sales Enquiries: +44 (0)20 7563 46 46 Fax: +44 (0)20 7563 46 10

The software described in this documentation is furnished under a license agreement, is the confidential information of Retek Inc., and may be used only in accordance with the terms of the agreement. No part of this documentation may be reproduced or transmitted in any form or by any means without the express written permission of Retek Inc., Retek on the Mall, 950 Nicollet Mall, Minneapolis, MN 55403, and the copyright notice may not be removed without the consent of Retek Inc. Information in this documentation is subject to change without notice. Retek provides product documentation in a read-only-format to ensure content integrity. Retek Customer Support cannot support documentation that has been changed without Retek authorization. The functionality described herein applies to this version, as reflected on the title page of this document, and to no other versions of software, including without limitation subsequent releases of the same software component. The functionality described herein will change from time to time with the release of new versions of software and Retek reserves the right to make such modifications at its absolute discretion. Retek® Warehouse Inbound PlanningTM is a trademark of Retek Inc. Retek and the Retek logo are registered trademarks of Retek Inc. This unpublished work is protected by confidentiality agreement, and by trade secret, copyright, and other laws. In the event of publication, the following notice shall apply: ©2005 Retek Inc. All rights reserved. All other product names mentioned are trademarks or registered trademarks of their respective owners and should be treated as such. Printed in the United States of America.

Customer Support Customer Support hours

Customer Support is available 7x24x365 via email, phone, and Web access.

Depending on the Support option chosen by a particular client (Standard, Plus, or Premium), the times that certain services are delivered may be restricted. Severity 1 (Critical) issues are addressed on a 7x24 basis and receive continuous attention until resolved, for all clients on active maintenance. Retek customers on active maintenance agreements may contact a global Customer Support representative in accordance with contract terms in one of the following ways.

Contact Method Contact Information

E-mail [email protected]

Internet (ROCS) rocs.retek.com Retek’s secure client Web site to update and view issues

Phone +1 612 587 5800

Toll free alternatives are also available in various regions of the world:

Australia +1 800 555 923 (AU-Telstra) or +1 800 000 562 (AU-Optus) France 0800 90 91 66 Hong Kong 800 96 4262 Korea 00 308 13 1342 United Kingdom 0800 917 2863 United States +1 800 61 RETEK or 800 617 3835

Mail Retek Customer Support Retek on the Mall 950 Nicollet Mall Minneapolis, MN 55403

When contacting Customer Support, please provide:

• Product version and program/module name.

• Functional and technical description of the problem (include business impact).

• Detailed step-by-step instructions to recreate.

• Exact error message received.

• Screen shots of each step you take.

http://rocs.retek.com/

Contents

i

Contents Chapter 1 – Introduction .................................................................. 1

Document overview...................................................................................................... 1

Intended audience ......................................................................................................... 1

Terminology and architectural notes ............................................................................ 1

Related documentation.................................................................................................. 1

Chapter 2 – Application overview................................................... 3

Description.................................................................................................................... 3

Data flow....................................................................................................................... 3

Warehouse inbound planning business process............................................................ 5

Warehouse Inbound Planning process flow.................................................................. 6

Chapter 3 – Workbooks/windows ................................................... 7

Chapter 4 – Measures and data structures .................................... 9

About measures/fields................................................................................................... 9

Data access permissions................................................................................................ 9

Global domains and simple domains ............................................................................ 9

Measures/fields used in WIP batch............................................................................... 9

Data model .................................................................................................................. 15

Chapter 5 – Implementation scripts and procedures.................. 17

UNIX shell scripts....................................................................................................... 17 Logging ............................................................................................................................ 17

Binaries ....................................................................................................................... 18 aliwip................................................................................................................................ 18

Chapter 6 – Interfaces.................................................................... 23

Input files .................................................................................................................... 23 Scripts............................................................................................................................... 23 Data files .......................................................................................................................... 24

Export files.................................................................................................................. 28 Scripts............................................................................................................................... 28 Data files .......................................................................................................................... 28

Retek Warehouse Inbound Planning

ii

Chapter 7 – Implementation process............................................ 29

Installation................................................................................................................... 29

Available hooks for customization ............................................................................. 29

Glossary .......................................................................................... 31

Chapter 1 – Introduction

1

Chapter 1 – Introduction Document overview This document describes the design and implementation of the Retek Warehouse Inbound Planning (WIP). Some sections of this document describe the actual code that is used to implement the requirements of WIP. Where appropriate, coding details are separated from the functional descriptions and can be ignored by those who do not want to modify or extend WIP. An understanding of these sections requires a basic knowledge of the design and architecture of the Retek Predictive Application Server (RPAS). If you would like a greater understanding of the RPAS general coding and architecture concepts, such as creating and registering measures and creating workbooks, refer to the RPAS technical documentation.

Intended audience This document is intended for an MIS administrator who will install the software.

Terminology and architectural notes This section describes some basic terminology used in this document. There are two components to the WIP solution. The first, known as WIP “batch,” is built on RPAS.

The second component of the WIP solution is built on Oracle and Java. This solution works in conjunction with WIP batch and is known as Order Management (OM). Refer to the Retek Advanced Inventory Planning Online Administration Guide for technical details of Order Management.

A brief overview of the RPAS concepts is provided to use as a guide in understanding this document. The basic element in RPAS is a measure. A measure is defined by several attributes, which include the following:

• Dimensionality

• The database in which it is stored

• An expression used to calculate or instantiate it

• Its type (for example, string, Boolean, integer).

Measures in WIP are registered globally and have a stored representation.

Related documentation Refer to the Order Management User Guide, Advanced Inventory Planning Installation Guide, RPAS Administration Guide, and RPAS User Guide.

Chapter 2 – Application overview

3

Chapter 2 – Application overview Description Warehouse Inbound Planning (WIP) is a module within the Advanced Inventory Planning solution. It uses a set of parameters and calculations on loaded static and dynamic data sent from Warehouse Replenishment Planning (WRP) to produce a vehicle loading plan and scheduling plan. The functionality included in the WIP module includes:

• Truckload building

• Inbound Distribution Center capacity smoothing

• Inbound Distribution Center scheduling

• Outbound Delivery Group smoothing

• Confirming orders and vehicles based on lead time criteria

After the inbound plan is generated, the system confirms the appropriate orders and vehicles on their release date and raises exceptions for user review. WIP batch sends the confirmed and forecasted orders to Order Management. Order Management creates the purchase orders, including a purchase order number. Order Management sends the confirmed orders and other relevant information to an execution system, such as Retek Merchandising System. Because of the volume of the orders, a minimum amount of user involvement is preferred. It is still possible for users to manage the exceptions, manually adjust the planning results, and change the parameters. These parameters are managed through Data Management Online and Order Management.

Most of the information in this chapter comes from the Data Management and Order Management User Guides.

Data flow Data inputs to WIP are maintained in Data Management Online. These include:

• Supplier, SKU, and warehouse relationships

• Warehouse receiving schedule (shifts and slots)

• Vehicle size and weight limits

• Commodity attributes such as stackability, supplier keep together groups, stockless product flag, order multiple, and pallet multiple

• Order lead-time for each SKU

• Supplier delivery scheduling preferences

• Supplier outbound vehicle capacity

• Vehicle minimum fill for each supplier


4

The replenishment plan generated in WRP is passed to WIP. Data from WRP includes:

• Warehouse orders generated from WRP

• Percentage of each order that is demanded and protected safety stock (used to assign a priority value to each pallet and vehicle).

WIP batch builds and schedules vehicles, as well as producing orders and sends them to Order Management. However, in Order Management, only the orders (and not the vehicles) are visible and can be amended. WIP batch outputs include:

• Confirmed and forecasted vehicles for all orders

• A list of orders and vehicles to be released to the supplier

See the following diagram for an overview of data flow in and out of WIP batch.

Data flow for Warehouse Inbound Planning

Batch Warehouse Inbound Planning

(WIPb)

Order Management (OM)

Online Data Management (DMo)

Warehouse Replenishment Planning (WRP)

Parameters (Vehicle & Warehouse

capacities, Smoothing & Scheduling Data)

Time-phased Replenishment Plan

Confirmed & Forecasted Delivery Units, Vehicles &

Orders

Chapter 2 – Application overview

5

Warehouse inbound planning business process WIP takes constrained warehouse orders from Warehouse Replenishment Planning (WRP) and makes a final plan based on each warehouse’s capacity. The WIP shipment planning process consists of five steps that run in the batch process. The orders are viewed and manually adjusted by users throughout the day.

WIP business process

1. Build Pallets

3. Smooth Inbound Deliveries

5. Confirm Orders

On -

Build Delivery

Units

Smooth Vehicles Schedule Deliveries

Confirm Orders

Online User Interface

Build Vehicles


6

1. Build delivery units – WIP receives recommended orders from WRP. The orders are converted into delivery units based on pallet multiple and supplier order multiple.

2. Build vehicles – WIP builds vehicles from the delivery units. The build process loads the optimal number of delivery units based on vehicle and supplier constraints.

3. Smooth vehicles – When one or more days are over-loaded, WIP performs smoothing, which pulls vehicles forward to days where there is available capacity. WIP performs two types of smoothing, inbound and outbound.

4. Schedule vehicles – Once the smoothing process has determined the vehicle delivery day, WIP schedules vehicles into the warehouse based on delivery preferences.

5. Confirm orders – WIP confirms orders based on order and transportation lead times.

6. Online user interface – Users have the ability to review purchase orders by day or aggregated across a selected time period.

Warehouse Inbound Planning process flow WIP batch consists of a single binary. Planning is executed via “aliwip_tn.sh”. WIP and WRP exchange data and must be processed in the following order:

• Warehouse Replenishment Planning (WRP)

• Warehouse Inbound Planning (WIP)

WIP and WRP Technical Flow

Warehouse Replenishment

Planning (WRP)

Warehouse Inbound Planning

(WIP)

Chapter 3 – Workbooks/windows

7

Chapter 3 – Workbooks/windows Note: The RPAS-based batch side of Warehouse Inbound Planning does not include any

workbooks, windows, or alerts. For information regarding the Java/Oracle online component and interfaces, see the AIP Online Administration Guide.

Chapter 4 – Measures and data structures

9

Chapter 4 – Measures and data structures This section describes the measures and calculations within the application.

About measures/fields A measure is any item of data that can be represented on a grid in worksheets used by modules that use the RPAS client graphical user interface. Examples of measures are Store Demand Forecast and Store Expected Receipts, used by Store Replenishment Planning (SRP). As WIP batch has no user interface outside the execution of the shell scripts, which run the aliwip binary, the concept of a measure is loosely applied to an array that stores data related to a concept pertaining to WIP and other AIP modules.

Data access permissions Refer to the Online Administration Guide for details on assigning data access permissions to WIP users.

Global domains and simple domains Note: The current release of WIP uses simple RPAS domains. The domains are not

configured for an RPAS global domain setup. Refer to the RPAS documentation for details on global domain functionality.

Measures/fields used in WIP batch The tables below contain a list of measures used in the calculations.

• The Label column matches the corresponding column in the AIP Online Users guides, which have a detailed description of these measures.

• The Database column contains the gem file on disk. The Measure column has measure names that are in the database.

• The Type and Intersection columns display attributes of the measure.

Note: All measures have the INFO dimension, which is not shown in the table.

• The Source column displays the owning process responsible for filling in the data values.

• The Sample column provides an example of a typical value for the measures that are inputs to aliwip.

Measures populated by the WIP Online application (for instance, Source = WIP Online) – which has not been implemented in this Release – will always be empty.

Note: The date measures contain a value in milliseconds (for instance, 210867000000000) that is converted internally to a MM/DD/YYYY date.


10

List of Measures

Label Database Measure Type Intersection Source Sample

Delivery Group Assignments

dmn_dgrasg DMN_DGRASG int DAY,SSTK,WHCH,DMGP

DM 1

Warehouse From Supplier Schedule By Pack Size

dmn_frsschpll DMN_FRSSCHPLL int DAY,SSTK,DSTK,SKPS DM 1

Warehouse-Chamber Pallet Multiple

dmn_palmltrll_i DMN_PALMLTRLL_I int DAY,SSTK,DSTK,SKPS DM 10

Warehouse Supplier Order Multiple

dmn_splordmlt_i DMN_SPLORDMLT_I int DAY,SSTK,DSTK,SKPS DM 12

Warehouse Stockless Indicator

dmn_stlind DMN_STLIND bool DAY,DSTK,SKUG DM True

Warehouse Committed Order Quantity

wi1_cmtordqty WI1_CMTORDQTY int DAY,SSTK,WHCH,SKPS WIP/output 10

Warehouse Capacity Type

wip_ins WI1_CPCTYP int WHCH DM 0

Case Weight dm1_csewgt DM1_CSEWGT real DAY,SPLR,WHCH,SKPS DM 10

Case Weight Ntier dmn_csewgt DMN_CSEWGT real DAY,SSTK,WHCH,SKPS DM 10

Delivery Group Capacity

wip_ins WI1_DGRCPC int DAY,DGR DM 10

Delivery Group Smoothing Flag

wip_ins WI1_DGRSMTFLG bool DGR DM true


11


Delivery Group Type

wip_ins WI1_DGRTYP bool DGR DM false

Direct Order Delivery Group

wi1_dirorddgr WI1_DIRORDDGR string DAY,SSTK,WHCH,SKPS WIP online DGR_01AAA1

Direct Order Quantity

wi1_dirordqty WI1_DIRORDQTY int DAY,SSTK,WHCH,SKPS WIP online 10

Warehouse DU Aggregate Order Quantity

wi1_dugordqty WI1_DUGORDQTY int DAY,SSTK,WHCH,SKPS output 10.00

Keep Together Group

wi1_ktg WI1_KTG int DAY,SSTK,WHCH,DGR DM 0

Keep Together Sku dm1_kts DM1_KTS bool DAY,SPLR,WHCH,SKPS DM False

Order Exceptions Wi1_ordexc WI1_ORDEXC int DAY,SSTK,WHCH,SKPS output 0

Warehouse Pallet FPE

dm1_palfpe DM1_PALFPE bool DAY,SPLR,WHCH,SKPS DM False

Warehouse Pallet Weight

dm1_palwgt DM1_PALWGT bool DAY,SPLR,WHCH,SKPS DM True

Warehouse Inbound Planning Horizon

wip_ins WI1_PLNHZN int Scalar WIP scalar 35

PO Confirmation Date

wi1_po_cfmdt_ WI1_PO_CFMDT_ date DAY,SSTK,WHCH,SKPS output 210867000000000

Process Orders Indicator

wip_ins WI1_PROORDIND bool WHCH,DGR DM true

Shift Capacity wi1_shfcpc WI1_SHFCPC int DAY,WHCH,SHFT DM 100


12


Slot Pallet Capacity wi1_sltpalcpc WI1_SLTPALCPC int DAY,WHCH,SLT DM 999

Slot to Shift Relationships

wi1_sltshfasc WI1_SLTSHFASC int DAY,WHCH,SLT DM 1

Slot Vehicle Capacity

wi1_sltvhccpc WI1_SLTVHCCPC int DAY,WHCH,SLT DM 20

Stackability Indicator

dm1_stbind DM1_STBIND int DAY,SPLR,WHCH,SKPS DM 0

Warehouse Transportation Lead Time

wi1_tnslt_ WI1_TNSLT_ int DAY,WHCH,DGR DM 0

Vehicle footprint wip_ins WI1_VHCFPT int WHCH,DGR DM 10

Vehicle Height wip_ins WI1_VHCHGT real WHCH,DGR DM 2

Vehicle Max Weight wip_ins WI1_VHCMAXWGT real WHCH,DGR DM 2000

Vehicle Minimum Drop

wip_ins WI1_VHCMINDRP int WHCH,DGR DM 10

Vehicle Preferences wi1_vhcpfc WI1_VHCPFC int DAY,WHCH,DGR,SLT,NVP

DM 0

Demand Priority wip_ins WIX_DMDPRY real Scalar WIP scalar 10

FPE Adjustment wip_ins WIX_FPEADJ real Scalar WIP scalar 1

Rounding Priority wip_ins WIX_RNDPRY real Scalar WIP scalar 1

Safety Stock Priority wip_ins WIX_SS_PRY real Scalar WIP scalar 5

Weight Adjustment wip_ins WIX_WGTADJ real Scalar WIP scalar 1

Commodity EDR wr1_edr WR1_EDR int SSTK,WHCH,SKPS WRP 2


13


Insufficient Inventory

wr1_insinv WR1_INSINV date SSTK,DSTK,SKPS WRP 210867000000000

Warehouse Priority Demand Percentage

wr1_prydmdpct WR1_PRYDMDPCT real DAY,DSTK,SKPS WRP 5

Warehouse Priority Safety Stock Percentage

wr1_pryss_pct WR1_PRYSS_PCT real DAY,DSTK,SKPS WRP 4

Warehouse Receipt Plan

wr1_rp_rll WR1_RP_RLL int DAY,SSTK,DSTK,SKPS WRP/output 60


14

Order Management sends committed delivery units (if any) using the format shown in the table below in a file called wi1_dus.dat, which is in the data directory.

Delivery Unit information in files wi1_dus.dat

Label Column # Type Width Sample

Oracle ID 1 int 12 83749

Confirmation Date 2 date 8 20041225

Ideal Date 3 date 8 20041225

Supplier 4 string 24 SPRL1239849

Sku and Pack size 5 string 24 SKPS40930_98

FPE 6 real 8 1.0

Quantity 7 int 8 10

Weight 8 real 8 10.0

Stackability 9 int 8 0

Priority 10 real 8 10.0

ADR 11 int 8 0

Vehicle ID 12 int 8 4

Order Management sends committed vehicles (if any) using the format shown in table below in a file called wi1_vhc.dat, which is in the data directory.

Vehicle information in files wi1_vhc.dat

Label Column# Type Width Sample

ID 1 int 8 26

Scheduling Location 2 string 24 WHCH1212

Delivery Group 3 string 24 DGR_B0001001

Confirmation Date 4 date 8 20041225

Scheduled Date 5 date 8 20041225

Slot 6 string 16 SLT_983

Priority 7 real 8 20.0

Exceptions 8 int 8 96

Full Vehicle 9 bool 1 1


15

Data model The WIP batch (RPAS) solution does not utilize any Oracle tables, so a Data model is not

applicable.

Chapter 5 – Implementation scripts and procedures

17

Chapter 5 – Implementation scripts and procedures UNIX shell scripts

Name Location Description

aliwip_tn.sh $RPAS_HOME/bin Wrapper for running aliwip binary .

Logging The output of each run of aliwip_t1.sh or aliwip_t2.sh is captured in a file. If the file contains an error, the file will be placed in the domain’s scripts/err directory with a name that contains the binary name “aliwip” and the date of execution.

Example 1:

<WIP domain directory>/scripts/logs/aliwip.20040825.135338.log

The aliwip.20040825.135338.log file contains the output from the execution of the aliwip binary from August 25, 2004, at 1:53:38 PM.

Example 2:

<WIP domain directory>/scripts/err/aliwip.20040825.135404.err

The aliwip.20040825.135404.err file contains the output from the execution of the aliwip binary from August 25, 2004, at 1:54:04 PM.


18

Binaries Name Location Description

aliwip $RPAS_APP_BIN This is the only binary for Warehouse Inbound Planning

aliwip

Inputs The wrapper aliwip_tn.sh passes the input measures to aliwip.

Note: This information comes from the tables.

Inputs into aliwip

INPUT Measure Label Intersection

DMN_DGRASG Delivery Group Assignments

DAY,SSTK,WHCH,DMGP

DMN_FRSSCHPLL Warehouse From Supplier Schedule By Pack Size

DAY,SSTK,DSTK,SKPS

DMN_PALMLTRLL_I Warehouse-Chamber Pallet Multiple

DAY,SSTK,DSTK,SKPS

DMN_SPLORDMLT_I Warehouse Supplier Order Multiple

DAY,SSTK,DSTK,SKPS

DMN_STLIND Warehouse Stockless Indicator

DAY,DSTK,SKUG

WI1_CMTORDQTY Warehouse Committed Order Quantity

DAY,SSTK,WHCH,SKPS

WI1_CPCTYP Warehouse Capacity Type

WHCH

DM1_CSEWGT Case Weight DAY,SSTK,WHCH,SKPS

WI1_DGRCPC Delivery Group Capacity

DAY,DGR

WI1_DGRSMTFLG Delivery Group Smoothing Flag

DGR

WI1_DGRTYP Delivery Group Type

DGR

WI1_DIRORDDGR Direct Order Delivery Group

DAY,SSTK,WHCH,SKPS


19


WI1_DIRORDQTY Direct Order Quantity

DAY,SSTK,WHCH,SKPS

WI1_KTG Keep Together Group

DAY,SSTK,WHCH,DGR

DM1_KTS Keep Together Sku DAY,SPLR,WHCH,SKPS

DM1_PALFPE Warehouse Pallet FPE

DAY,SPLR,WHCH,SKPS

DM1_PALWGT Warehouse Pallet Weight

DAY,SPLR,WHCH,SKPS

WI1_PLNHZN Warehouse Inbound Planning Horizon

scalar

WI1_PROORDIND Process Orders Indicator

WHCH,DGR

WI1_SHFCPC Shift Capacity DAY,WHCH,SHFT

WI1_SLTPALCPC Slot Pallet Capacity DAY,WHCH,SLT

WI1_SLTSHFASC Slot to Shift Relationships

DAY,WHCH,SLT

WI1_SLTVHCCPC Slot Vehicle Capacity

DAY,WHCH,SLT

DM1_STBIND Stackability Indicator

DAY,SPLR,WHCH,SKPS

WI1_TNSLT_ Warehouse Transportation Lead Time

DAY,WHCH,DGR

WI1_VHCFPT Vehicle footprint WHCH,DGR

WI1_VHCHGT Vehicle Height WHCH,DGR

WI1_VHCMAXWGT Vehicle Max Weight WHCH,DGR

WI1_VHCMINDRP Vehicle Minimum Drop

WHCH,DGR

WI1_VHCPFC Vehicle Preferences DAY,WHCH,DGR,SLT,NVP

WIX_DMDPRY Demand Priority scalar

WIX_FPEADJ FPE Adjustment scalar

WIX_RNDPRY Rounding Priority scalar

WIX_SS_PRY Safety Stock Priority scalar

WIX_WGTADJ Weight Adjustment scalar

WR1_EDR Commodity EDR SSTK,DSTK,SKPS


20


WR1_INSINV Insufficient Inventory

SSTK,DSTK,SKPS

WR1_PRYDMDPCT Warehouse Priority Demand Percentage

DAY,DSTK,SKPS

WR1_PRYSS_PCT Warehouse Priority Safety Stock Percentage

DAY,DSTK,SKPS

WR1_RP_RLL Warehouse Receipt Plan

DAY,SSTK,DSTK,SKPS

Outputs

Note: There are two measures, which are both input and output measures (Commited Order Quantity and Warehouse Receipt Plan), so they appear in both the preceding input measures lists as well as the following output measures lists.

Outputs from aliwip

OUTPUT Measure Label Intersection

WI1_CMTORDQTY Warehouse Committed Order Quantity

DAY,SSTK,WHCH,SKPS

WI1_DUGORDQTY Warehouse DU Aggregate Order Quantity

DAY,SSTK,WHCH,SKPS

WI1_ORDEXC Order Exceptions DAY,SSTK,WHCH,SKPS

WI1_PO_CFMDT_ PO Confirmation Date DAY,SSTK,WHCH,SKPS

WR1_RP_RLL Warehouse Receipt Plan DAY,SSTK,DSTK,SKPS


21

Two files, one of delivery units and the other for vehicles, are also written out. They are: wi1_dus.dat and wi1_vhc.dat.

Output file from aliwip (wi1_dus.dat)

Label Column# Width

Oracle ID 1 12

Confirmation Date 2 8

Ideal Date 3 8

Supplier 4 24

Sku and Pack size 5 24

FPE 6 8

Quantity 7 8

Weight 8 8

Stackability 9 8

Priority 10 8

ADR 11 8

Vehicle ID 12 8

Output file from aliwip (wi1_vhc.dat)

Label Column# Width

ID 1 8

Scheduling Location 2 24

Delivery Group 3 24

Confirmation Date 4 8

Scheduled Date 5 8

Slot 6 16

Priority 7 8

Exceptions 8 8

Full Vehicle 9 1

Chapter 6 – Interfaces

23

Chapter 6 – Interfaces WIP batch must interface with other AIP modules, both online and batch. Data flows into WIP batch and out of WIP batch using a series of UNIX shell scripts and binary executables. This section describes the data that pass between WIP batch and other modules and the programs that move the data.

Note: Indirectly, WIP can receive hierarchy data from RMS via DM Batch. For more information about the integration between RMS and AIP, refer to the AIP/RMS Integration Technical Guide (aip-rms-113-itg.pdf).

Input files Scripts As noted in the measure input and output lists in Chapter 4, WIP batch receives several files from the following AIP modules: Order Management, DM batch, and WRP. The following scripts are used to import and load the data from these various sources before the WIP batch solution (aliwip) is executed.

Order Management to WIP Batch

SCRIPT Name Location Description

load_all_hierarchies.sh $RPAS_HOME/bin Refreshes the WIP domain’s hierarchy data using the Order Management new values.

Example call: load_all_hierarchies.sh -d <WIP_DOMAIN> -s hierDir -a convert load_all_hierarchies.sh -d <WIP_DOMAIN> -s hierDir -a load

load_online_measures.sh $RPAS_HOME/bin Refreshes WIP batch measures based on new values from the Order Management.

Note: This is a full refresh, not a delta refresh. An online-to-batch script.

Example call: load_online_measures.sh <WIP_DOMAIN> WIP


24

WRP and DM Batch to WIP Batch


wip_pull_aip.ksh $RPAS_HOME/bin Refreshes DM measures required by aliwip execution. An intra-batch module script.

Example call: wip_pull_aip.ksh [<WIP_DOMAIN_PATH>]

Data files The various scripts that pull data into WIP batch do so either internally or via flat files stored on disk.

Order Management to WIP Batch The following measure data are imported into the WIP RPAS domain from Order Management.

Measure data imported to WIP

Import Script Name Data Format

Hierarchy data from Order Management. These files were transferred via ftp to the RPAS domains’ UNIX box by a different script (rms_aip_integration.sh).

load_all_hierarchies.sh Hierarchy data are in *.dat files contained in an “import” directory specified by the script.

Measure data from Order Management. These files are transferred via ftp to the RPAS domains’ UNIX box by this script. See following table for list of individual files.

load_online_measures.sh Measure data are in *.dat files, one for each *.config file in the WIP domain’s interface/config/meas subdirectory.


25

The following individual measure files make up the import of measure data from Order Management to WIP batch via the load_online_measures.sh script.

Measure Name Measure Label File Name

wi1_cpctyp Warehouse Capacity Type wi1_cpctyp.dat

wi1_csewgt Case Weight wi1_csewgt.dat

wi1_dgrcpc Delivery Group Capacity wi1_dgrcpc.dat

wi1_dgrsmtflg Delivery Group Smoothing Flag wi1_dgrsmtflg.dat

wi1_dgrtyp Delivery Group Type wi1_dgrtyp.dat

wi1_dirorddgr Direct Order Delivery Group wi1_dirorddgr.dat

wi1_dirordqty Direct Order Quantity wi1_dirordqty.dat

wi1_ktg Keep Together Groups wi1_ktg.dat

wi1_kts Keep Together Sku wi1_kts.dat

wi1_palfpe Warehouse Pallet FPE wi1_palfpe.dat

wi1_palwgt Warehouse Pallet Weight wi1_palwgt.dat

wi1_proordind Process Orders Indicator wi1_proordind.dat

wi1_shfcpc Shift Capacity wi1_shfcpc.dat

wi1_sltpalcpc Slot Pallet Capacity wi1_sltpalcpc.dat

wi1_sltshfasc Slot to Shift Relationships wi1_sltshfasc.dat

wi1_sltvhccpc Slot Vehicle Capacity wi1_sltvhccpc.dat

wi1_stbind Stackability Indicator wi1_stbind.dat

wi1_tnslt_ Warehouse Transportation Lead Time wi1_tnslt_.dat

wi1_vhcfpt Vehicle footprint wi1_vhcfpt.dat

wi1_vhchgt Vehicle Height wi1_vhchgt.dat

wi1_vhcmaxwgt Vehicle Max Weight wi1_vhcmaxwgt.dat

wi1_vhcmindrp Vehicle Minimum Drop wi1_vhcmindrp.dat

wi1_vhcpfc Vehicle Preferences wi1_vhcpfc.dat

wi1_du_adr DU ADR wi1_du_adr.dat

wi1_du_cfmdt_ DU Confirmation Date wi1_du_cfmdt_.dat

wi1_du_fpe DU FPE wi1_du_fpe.dat

wi1_du_idldt_ DU Ideal Date wi1_du_idldt_.dat

wi1_du_pry DU Priority wi1_du_pry.dat

wi1_du_psz DU SKU and Pack wi1_du_psz.dat

wi1_du_qty DU Quantity wi1_du_qty.dat


26


wi1_du_spl DU Supplier wi1_du_spl.dat

wi1_du_vhcid_ DU Vehicle ID wi1_du_vhcid_.dat

wi1_du_wgt DU Weight wi1_du_wgt.dat

wi1_fixpfcvhc Fixed Pref Vehicle wi1_fixpfcvhc.dat

wi1_fulvhc Full Vehicle wi1_fulvhc.dat

wi1_vhccfmdt_ Vehicle Confirmation Date wi1_vhccfmdt_.dat

wi1_vhcpry Vehicle Priority wi1_vhcpry.dat

wi1_vhcschdt_ Vehicle Schedule Date wi1_vhcschdt_.dat

wi1_vhcscl Vehicle Scheduling Location wi1_vhcscl.dat


27

WRP and DM Batch to WIP Batch The following measure data are imported into the WIP domain from the DM and WRP domains through the execution of the various batch-to-batch “pull” interface scripts.

IMPORT SCRIPT NAME MEASURE DATA IMPORTED INTO WIP BATCH

wip_pull_aip.ksh dmn_dgrasg

dmn_frsschpll

dmn_palmltrll_i

dmn_splordmlt_i

dm1_kts

dm1_palfpe

dm1_palwgt

dm1_stbind

dmn_stlind wr1_edr

wr1_rp_rll

wr1_insinv

wr1_prydmdpct

wr1_pryss_pct


28

Export files Scripts WIP batch exports several files that are picked up by the online components of AIP. The following script is used to export the data from WIP batch after the WIP batch solution (aliwip) is executed.

WIP batch export


send_wip_measures_to_online.sh Calls: export_wip_inter_meas.sh

$RPAS_HOME/bin Exports the WIP domain’s measure data needed by other batch modules into the domain’s interface/export directory, where it will be transferred to other modules

Example call: send_wip_measures_to_online.sh <WIP_DOMAIN> export_wip_inter_meas.sh <WIP_DOMAIN> <MEASURENAME> <FILE_FORMAT>

Data files The various scripts that pull data into WIP batch do so either internally or via flat files stored on disk.

WIP batch export The following measure data are exported from the WIP domain via send_wip_measures_to_online.sh


wi1_po_cfmdt_ PO Confirmation Date wi1_po_cfmdt_.dat

wi1_cmtordqty PO Committed Order wi1_cmtordqty.dat

Chapter 7 – Implementation process

29

Chapter 7 – Implementation process Installation The 11.4 GA release of WIP contains a script named set_implementation_parms.sh. This script is located in $RPAS_HOME/bin directory. See AIP Installation Guide for information on creating a WIP domain.

This script contains mace expressions that set the following scalar (constant) measures, which are customized for each client.

Note: Refer to the RPAS documentation for additional information on mace expression.

• wi1_plnhzn – Warehouse Inbound Planning Horizon

• wix_allsmt – Smoothing All Vehicles

• wix_dmdpry – Demand Priority

• wix_nc_smt – Non-contents Smoothing

• wix_ss_pry – Safety Stock Priority

• wix_rndpry – Rounding Priority

• wix_stlpfd – Stockless Pull Forward

After editing this script, run it by executing the following commands (where “$” is the UNIX command prompt).

$ cd <WIP domain root directory>

$ set_implementation_parms.sh

Available hooks for customization The current release of WIP has no hooks for customization of the aliwip binary.

Glossary

31

Glossary Refer to the glossary in the Data Management or Order Management User Guide for a complete list of terms and definitions.

retek advanced inventory planning 11.4 batch ...€¦ · global domains and simple domains ... •...

Documents