Retek Advanced Inventory Planning 11.3 Batch ...€¦ · Build vehicles – WIP builds vehicles from the delivery units. The build process loads the optimal number of delivery units

Retek® Advanced Inventory Planning ™

11.3

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.

Retek Warehouse Inbound Planning

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.................................................................. 7

Chapter 3 – Workbooks/Screens .................................................... 9

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

About measures/fields................................................................................................. 11

Data access permissions.............................................................................................. 11

Global domains and simple domains .......................................................................... 11

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

Data model .................................................................................................................. 20

Chapter 5 – Implementation Scripts and Procedures ................. 21

UNIX shell scripts....................................................................................................... 21 Logging ............................................................................................................................ 21

Binaries ....................................................................................................................... 22 aliwip................................................................................................................................ 22

Chapter 6 – Interfaces.................................................................... 29

Input files .................................................................................................................... 29 Scripts............................................................................................................................... 29 Data Files.......................................................................................................................... 30

Export files.................................................................................................................. 33 Scripts............................................................................................................................... 33 Data Files.......................................................................................................................... 34


ii

Chapter 7 – Implementation process............................................ 35

Installation................................................................................................................... 35

Available hooks for customization ............................................................................. 35

Glossary .......................................................................................... 37

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. Please 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, including dimensionality, the database in which it is stored, an expression used to calculate or instantiate it, and 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 (contents vehicles only), inbound Distribution Center scheduling, outbound Delivery Group smoothing (contents vehicles only), and 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

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).


4

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

Confirmed & Forecasted Delivery Units, Vehicles & Orders


5

Warehouse Inbound Planning business process WIP takes unconstrained 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.


7

Warehouse Inbound Planning process flow WIP batch consists of a single binary, which is run once for tier 1 and once for tier 2. A different shell script is called for each tier. Tier 1 planning is executed via “aliwip_t1.sh” and tier 2 planning is executed via “aliwip_t2.sh”. WIP and WRP exchange data and must be processed in the following order:

• Warehouse Replenishment Planning (WRP) Tier 1

• Warehouse Inbound Planning (WIP) Tier 1

• Warehouse Replenishment Planning (WRP) Tier 2

• Warehouse Inbound Planning (WIP) Tier 2

WIP and WRP Technical Flow


Planning Tier 1 (WRP)

Warehouse Inbound Planning

Tier 1 (WIP)


Planning Tier2

(WRP)

Warehouse Inbound Planning

Tier 2 (WIP)

Chapter 3 – Workbooks/Screens

9

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

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

Chapter 4 – Measures and data structures

11

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 Please refer to the Online Administration Guide for detail 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 Tables 1 and 2 contain list of measures used in the Tier 1 and 2 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 which 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.

Some measures are not valid at the second tier. These measures are still required to exist so that the aliwip binary can maintain the same command-line arguments regardless of tier. In the case where the measure is not valid, a placeholder database and containing array are still used, but will remain empty. Furthermore, measures populated by the WIP Online application (i.e., Source = WIP Online) – which has not been implemented in this Release – will always be empty.

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

Ret

ek W

areh

ouse

Inbo

und

Plan

ning

12

Tab

le 1

: Lis

t of M

easu

res i

n T

ier

1

Labe

l D

atab

ase

Mea

sure

Ty

pe

Inte

rsec

tion

Sour

ce

Sam

ple

Del

iver

y G

roup

A

ssig

nmen

ts

dm1_

dgra

sg

DM

1_D

GR

ASG

st

ring

DA

Y,S

PLR

,WH

CH

,DM

GP

DM

D

GR

_01A

AA

1

War

ehou

se F

rom

Su

pplie

r Sch

edul

e B

y Pa

ck S

ize

dm1_

frss

chrll

D

M1_

FRSS

CH

RLL

in

t D

AY

,SPL

R,W

HC

H,S

KPS

D

M

5

War

ehou

se-C

ham

ber

Palle

t Mul

tiple

dm

1_pa

lmltr

ll_i

DM

1_PA

LMLT

RLL

_I

int

DA

Y,S

PLR

,WH

CH

,SK

PS

DM

10

War

ehou

se S

uppl

ier

Ord

er M

ultip

le

dm1_

splo

rdm

lt_i

DM

1_SP

LOR

DM

LT_I

in

t D

AY

,SPL

R,W

H,S

KPS

D

M

12

War

ehou

se

Stoc

kles

s Ind

icat

or

dm1_

stlin

d D

M1_

STLI

ND

bo

ol

DA

Y,W

H,D

MG

P D

M

True

War

ehou

se

Com

mitt

ed O

rder

Q

uant

ity

wi1

_cm

tord

qty

WI1

_CM

TOR

DQ

TY

int

DA

Y,S

PLR

,WH

CH

,SK

PS

WIP

/out

put

10

War

ehou

se C

apac

ity

Type

w

ip_i

ns

WI1

_CPC

TYP

int

WH

CH

D

M

0

Cas

e W

eigh

t w

i1_c

sew

gt

WI1

_CSE

WG

T re

al

DA

Y,S

PLR

,WH

CH

,SK

PS

WIP

10

Del

iver

y G

roup

C

apac

ity

wip

_ins

W

I1_D

GR

CPC

in

t D

AY

,DG

R

DM

10

Del

iver

y G

roup

Sm

ooth

ing

Flag

w

ip_i

ns

WI1

_DG

RSM

TFLG

bo

ol

DG

R

DM

tru

e

Del

iver

y G

roup

Ty

pe

wip

_ins

W

I1_D

GR

TYP

bool

D

GR

D

M

fals

e

Cha

pter

4 –

Mea

sure

s an

d da

ta s

truc

ture

s

13

Labe

l D

atab

ase

Mea

sure

Ty

pe

Inte

rsec

tion

Sour

ce

Sam

ple

Dire

ct O

rder

D

eliv

ery

Gro

up

wi1

_diro

rddg

r W

I1_D

IRO

RD

DG

R

strin

g D

AY

,SPL

R,W

HC

H,S

KPS

W

IP o

nlin

e D

GR

_01A

AA

1

Dire

ct O

rder

Q

uant

ity

wi1

_diro

rdqt

y W

I1_D

IRO

RD

QTY

in

t D

AY

,SPL

R,W

HC

H,S

KPS

W

IP o

nlin

e 10

War

ehou

se D

U

Agg

rega

te O

rder

Q

uant

ity

wi1

_dug

ordq

ty

WI1

_DU

GO

RD

QTY

in

t D

AY

,SPL

R,W

HC

H,S

KPS

ou

tput

10

.00

Kee

p To

geth

er

Gro

up

wi1

_ktg

W

I1_K

TG

int

DA

Y,S

PLR

,WH

CH

,DG

R

DM

0

Kee

p To

geth

er S

ku

wi1

_kts

W

I1_K

TS

bool

D

AY

,SPL

R,W

HC

H,S

KPS

D

M

Fals

e

Ord

er E

xcep

tions

w

i1_o

rdex

c W

I1_O

RD

EXC

in

t D

AY

,SPL

R,W

HC

H,S

KPS

ou

tput

0

War

ehou

se P

alle

t FP

E w

i1_p

alfp

e W

I1_P

ALF

PE

bool

D

AY

,SPL

R,W

HC

H,S

KPS

D

M

true

War

ehou

se P

alle

t W

eigh

t w

i1_p

alw

gt

WI1

_PA

LWG

T bo

ol

DA

Y,S

PLR

,WH

CH

,SK

PS

DM

Tr

ue

War

ehou

se In

boun

d Pl

anni

ng H

oriz

on

wip

_ins

W

I1_P

LNH

ZN

int

Scal

ar

WIP

scal

ar

35

PO C

onfir

mat

ion

Dat

e w

i1_p

o_cf

mdt

_ W

I1_P

O_C

FMD

T_

date

D

AY

,SPL

R,W

HC

H,S

KPS

ou

tput

21

0867

0000

000

00

Proc

ess O

rder

s In

dica

tor

wip

_ins

W

I1_P

RO

OR

DIN

D

bool

W

HC

H,D

GR

D

M

true

Shift

Cap

acity

w

i1_s

hfcp

c W

I1_S

HFC

PC

int

DA

Y,W

HC

H,S

HFT

D

M

100

Slot

Pal

let C

apac

ity

wi1

_sltp

alcp

c W

I1_S

LTPA

LCPC

in

t D

AY

,WH

CH

,SLT

D

M

999

Ret

ek W

areh

ouse

Inbo

und

Plan

ning

14

Labe

l D

atab

ase

Mea

sure

Ty

pe

Inte

rsec

tion

Sour

ce

Sam

ple

Slot

to S

hift

Rel

atio

nshi

ps

wi1

_slts

hfas

c W

I1_S

LTSH

FASC

in

t D

AY

,WH

CH

,SLT

D

M

1

Slot

Veh

icle

C

apac

ity

wi1

_sltv

hccp

c W

I1_S

LTV

HC

CPC

in

t D

AY

,WH

CH

,SLT

D

M

20

Stac

kabi

lity

Indi

cato

r w

i1_s

tbin

d W

I1_S

TBIN

D

int

DA

Y,S

PLR

,WH

CH

,SK

PS

DM

0

War

ehou

se

Tran

spor

tatio

n Le

ad

Tim

e

wi1

_tns

lt_

WI1

_TN

SLT_

in

t D

AY

,WH

CH

,DG

R

DM

0

Veh

icle

foot

prin

t w

ip_i

ns

WI1

_VH

CFP

T in

t W

HC

H,D

GR

D

M

10

Veh

icle

Hei

ght

wip

_ins

W

I1_V

HC

HG

T re

al

WH

CH

,DG

R

DM

2

Veh

icle

Max

Wei

ght

wip

_ins

W

I1_V

HC

MA

XW

GT

real

W

HC

H,D

GR

D

M

2000

Veh

icle

Min

imum

D

rop

wip

_ins

W

I1_V

HC

MIN

DR

P in

t W

HC

H,D

GR

D

M

10

Veh

icle

Pre

fere

nces

w

i1_v

hcpf

c W

I1_V

HC

PFC

in

t D

AY

,WH

CH

,DG

R,S

LT,N

VP

DM

0

Dem

and

Prio

rity

wip

_ins

W

IX_D

MD

PRY

re

al

Scal

ar

WIP

scal

ar

10

FPE

Adj

ustm

ent

wip

_ins

W

IX_F

PEA

DJ

real

Sc

alar

W

IP sc

alar

1

Rou

ndin

g Pr

iorit

y w

ip_i

ns

WIX

_RN

DPR

Y

real

Sc

alar

W

IP sc

alar

1

Safe

ty S

tock

Prio

rity

wip

_ins

W

IX_S

S_PR

Y

real

Sc

alar

W

IP sc

alar

5

Wei

ght A

djus

tmen

t w

ip_i

ns

WIX

_WG

TAD

J re

al

Scal

ar

WIP

scal

ar

1

Com

mod

ity E

DR

w

r1_e

dr

WR

1_ED

R

int

SPLR

,WH

CH

,SK

PS

WR

P 2

Cha

pter

4 –

Mea

sure

s an

d da

ta s

truc

ture

s

15

Labe

l D

atab

ase

Mea

sure

Ty

pe

Inte

rsec

tion

Sour

ce

Sam

ple

Insu

ffic

ient

In

vent

ory

wr1

_ins

inv

WR

1_IN

SIN

V

date

SP

LR,W

H,S

KPS

W

RP

2108

6700

0000

000

War

ehou

se P

riorit

y D

eman

d Pe

rcen

tage

w

r1_p

rydm

dpct

W

R1_

PRY

DM

DPC

T re

al

DA

Y,W

H,D

MG

P W

RP

5

War

ehou

se P

riorit

y Sa

fety

Sto

ck

Perc

enta

ge

wr1

_pry

ss_p

ct

WR

1_PR

YSS

_PC

T re

al

DA

Y,W

H,D

MG

P W

RP

4

War

ehou

se R

ecei

pt

Plan

w

r1_r

p_rll

W

R1_

RP_

RLL

in

t D

AY

,SPL

R,W

HC

H,S

KPS

W

RP/

outp

ut

60

Ret

ek W

areh

ouse

Inbo

und

Plan

ning

16

Tab

le 2

: Lis

t of m

easu

res i

n T

ier

2

Labe

l D

atab

ase

Mea

sure

Ty

pe

Inte

rsec

tion

Sour

ce

Sam

ple

Del

iver

y G

roup

A

ssig

nmen

ts

dm2_

dgra

sg

DM

2_D

GR

ASG

st

ring

DA

Y,S

PLR

,PC

C,D

MG

P D

M

PCD

G01

AA

A1

War

ehou

se F

rom

Sup

plie

r Sc

hedu

le B

y Pa

ck S

ize

dm2_

frss

chrll

D

M2_

FRSS

CH

RLL

in

t D

AY

,SPL

R,P

CC

,SK

PS

DM

5

PCC

Pal

let M

ultip

le

dm2_

palm

ltrll_

i D

M2_

PALM

LTR

LL_I

in

t D

AY

,SPL

R,P

CC

,SK

PS

DM

10

PCC

Site

Sup

plie

r Ord

er

Mul

tiple

dm

2_sp

lord

mlt_

i D

M2_

SPLO

RD

MLT

_I

int

DA

Y,S

PLR

,PC

CS,

SKPS

D

M

12

Plac

ehol

der f

or S

tock

less

In

dica

tor

dm2_

stlin

d D

M2_

STLI

ND

bo

ol

DA

Y,P

CC

S,D

MG

P D

M

(alw

ays b

lank

)

PCC

Com

mitt

ed O

rder

Q

uant

ity

wi2

_cm

tord

qty

WI2

_CM

TOR

DQ

TY

int

DA

Y,S

PLR

,PC

C,S

KPS

W

IP/o

utpu

t 10

War

ehou

se C

apac

ity T

ype

wip

_ins

W

I2_C

PCTY

P in

t PC

C

DM

0

Cas

e W

eigh

t w

i2_c

sew

gt

WI2

_CSE

WG

T re

al

DA

Y,S

PLR

,PC

C,S

KPS

W

IP

10

Del

iver

y G

roup

Cap

acity

w

ip_i

ns

WI2

_DG

RC

PC

int

DA

Y,P

CD

G

DM

10

Del

iver

y G

roup

Sm

ooth

ing

Flag

w

ip_i

ns

WI2

_DG

RSM

TFLG

bo

ol

PCD

G

DM

tru

e

Del

iver

y G

roup

Typ

e w

ip_i

ns

WI2

_DG

RTY

P bo

ol

PCD

G

DM

fa

lse

Dire

ct O

rder

Del

iver

y G

roup

w

i2_d

irord

dgr

WI2

_DIR

OR

DD

GR

st

ring

DA

Y,S

PLR

,PC

C,S

KPS

W

IP o

nlin

e PC

DG

01A

AA

1

Dire

ct O

rder

Qua

ntity

w

i2_d

irord

qty

WI2

_DIR

OR

DQ

TY

int

DA

Y,S

PLR

,PC

C,S

KPS

W

IP o

nlin

e 10

PCC

Agg

rega

te O

rder

Q

uant

ity

wi2

_dug

ordq

ty

WI2

_DU

GO

RD

QTY

in

t D

AY

,SPL

R,P

CC

,SK

PS

outp

ut

10.0

0

Cha

pter

4 –

Mea

sure

s an

d da

ta s

truc

ture

s

17

Labe

l D

atab

ase

Mea

sure

Ty

pe

Inte

rsec

tion

Sour

ce

Sam

ple

Kee

p To

geth

er G

roup

s w

i2_k

tg

WI2

_KTG

in

t D

AY

,SPL

R,P

CC

,PC

DG

D

M

0

Kee

p To

geth

er S

ku

wi2

_kts

W

I2_K

TS

bool

D

AY

,SPL

R,P

CC

,SK

PS

DM

Fa

lse

Ord

er E

xcep

tions

w

i2_o

rdex

c W

I2_O

RD

EXC

in

t D

AY

,SPL

R,P

CC

,SK

PS

outp

ut

0

PCC

Pal

let F

PE

wi2

_pal

fpe

WI2

_PA

LFPE

bo

ol

DA

Y,S

PLR

,PC

C,S

KPS

D

M

True

PCC

Pal

let W

eigh

t w

i2_p

alw

gt

WI2

_PA

LWG

T bo

ol

DA

Y,S

PLR

,PC

C,S

KPS

D

M

True

War

ehou

se In

boun

d Pl

anni

ng H

oriz

on

wip

_ins

W

I2_P

LNH

ZN

int

Scal

ar

WIP

scal

ar

35

PO C

onfir

mat

ion

Dat

e w

i2_p

o_cf

mdt

_ W

I2_P

O_C

FMD

T_

date

D

AY

,SPL

R,P

CC

,SK

PS

outp

ut

2108

6700

0000

000

Proc

ess O

rder

s Ind

icat

or

wip

_ins

W

I2_P

RO

OR

DIN

D

bool

PC

C,P

CD

G

DM

tru

e

Shift

Cap

acity

w

i2_s

hfcp

c W

I2_S

HFC

PC

int

DA

Y,P

CC

,SH

FT,

DM

10

0

Slot

Pal

let C

apac

ity

wi2

_sltp

alcp

c W

I2_S

LTPA

LCPC

in

t D

AY

,PC

C,S

LT

DM

99

9

Slot

to S

hift

Rel

atio

nshi

ps

wi2

_slts

hfas

c W

I2_S

LTSH

FASC

in

t D

AY

,PC

C,S

LT

DM

1

Slot

Veh

icle

Cap

acity

w

i2_s

ltvhc

cpc

WI2

_SLT

VH

CC

PC

int

DA

Y,P

CC

,SLT

D

M

20

Stac

kabi

lity

Indi

cato

r w

i2_s

tbin

d W

I2_S

TBIN

D

int

DA

Y,S

PLR

,PC

C,S

KPS

D

M

0

War

ehou

se T

rans

porta

tion

Lead

Tim

e w

i2_t

nslt_

W

I2_T

NSL

T_

int

DA

Y,P

CC

,PC

DG

D

M

0

Veh

icle

foot

prin

t w

ip_i

ns

WI2

_VH

CFP

T in

t PC

C,P

CD

G

DM

10

Veh

icle

Hei

ght

wip

_ins

W

I2_V

HC

HG

T re

al

PCC

,PC

DG

D

M

2

Veh

icle

Max

Wei

ght

wip

_ins

W

I2_V

HC

MA

XW

GT

real

PC

C,P

CD

G

DM

20

00

Veh

icle

Min

imum

Dro

p w

ip_i

ns

WI2

_VH

CM

IND

RP

int

PCC

,PC

DG

D

M

10

Veh

icle

Pre

fere

nces

w

i2_v

hcpf

c W

I2_V

HC

PFC

in

t D

AY

,PC

C,P

CD

G,S

LT,N

VP

DM

0

Ret

ek W

areh

ouse

Inbo

und

Plan

ning

18

Labe

l D

atab

ase

Mea

sure

Ty

pe

Inte

rsec

tion

Sour

ce

Sam

ple

Dem

and

Prio

rity

wip

_ins

W

IX_D

MD

PRY

re

al

Scal

ar

WIP

scal

ar

10

FPE

Adj

ustm

ent

wip

_ins

W

IX_F

PEA

DJ

real

Sc

alar

W

IP sc

alar

1

Rou

ndin

g Pr

iorit

y w

ip_i

ns

WIX

_RN

DPR

Y

real

Sc

alar

W

IP sc

alar

1

Safe

ty S

tock

Prio

rity

wip

_ins

W

IX_S

S_PR

Y

real

Sc

alar

W

IP sc

alar

5

Wei

ght A

djus

tmen

t w

ip_i

ns

WIX

_WG

TAD

J re

al

Scal

ar

WIP

scal

ar

1

Com

mod

ity E

DR

w

r2_e

dr

WR

2_ED

R

int

SPLR

,PC

C,S

KPS

W

RP

2

Plac

ehol

der f

or In

suff

icie

nt

Inve

ntor

y w

r2_i

nsin

v W

R2_

INSI

NV

da

te

SPLR

,PC

CS,

SKPS

W

RP

(alw

ays b

lank

)

PCC

Prio

rity

Dem

and

Perc

enta

ge

wr2

_pry

dmdp

ct

WR

2_PR

YD

MD

PCT

real

D

AY

,SPL

R,P

CC

,DM

GP

WR

P 5

PCC

Prio

rity

Safe

ty S

tock

Pe

rcen

tage

w

r2_p

ryss

_pct

W

R2_

PRY

SS_P

CT

real

D

AY

,SPL

R,P

CC

,DM

GP

WR

P 4

War

ehou

se R

ecei

pt P

lan

wr2

_rp_

rll

WR

2_R

P_R

LL

int

DA

Y,S

PLR

,PC

C,S

KPS

W

RP/

outp

ut60

Chapter 4 – Measures and data structures

19

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

Table 3: Delivery Unit information in files wi1_dus.dat and wi2_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 4 in a file called wi1_vhc.dat which is in the data directory.

Table 4: Vehicle information in files wi1_vhc.dat and wi2_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


20

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

21

Chapter 5 – Implementation Scripts and Procedures UNIX shell scripts

Name Location Description

aliwip_t1.sh $RPAS_APP_BIN Wrapper for running aliwip binary on tier 1 data.

aliwip_t2.sh $RPAS_APP_BIN Wrapper for running aliwip binary on tier 2 data.

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.


22

Binaries Name Location Description

aliwip $RPAS_APP_BIN This is the only binary for Warehouse Inbound Planning, and is called once per tier.

aliwip

Inputs The aliwip binary requires the same input measures for tier 1 as it does for tier 2. The data are different between tier 1 and tier 2. The wrapper aliwip_t1.sh passes the tier 1 versions of the measures to aliwip. The wrapper aliwip_t2.sh passes the tier 2 versions of the measures to aliwip. There are a few input measures which are not valid at the second tier, but which are passed (as empty measures) to the binary as input placeholders. The following two tables list the tier 1 and tier 2 input measures. Note this information comes from Tables 1 and 2.

Table 5: Inputs into aliwip, tier 1

INPUT Measure Label Intersection

DM1_DGRASG Delivery Group Assignments

DAY,SPLR,WHCH,DMGP

DM1_FRSSCHRLL Warehouse From Supplier Schedule By Pack Size

DAY,SPLR,WHCH,SKPS

DM1_PALMLTRLL_I Warehouse-Chamber Pallet Multiple

DAY,SPLR,WHCH,SKPS

DM1_SPLORDMLT_I Warehouse Supplier Order Multiple

DAY,SPLR,WH,SKPS

DM1_STLIND Warehouse Stockless Indicator

DAY,WH,DMGP

WI1_CMTORDQTY Warehouse Committed Order Quantity

DAY,SPLR,WHCH,SKPS

WI1_CPCTYP Warehouse Capacity Type

WHCH

WI1_CSEWGT Case Weight DAY,SPLR,WHCH,SKPS

WI1_DGRCPC Delivery Group Capacity

DAY,DGR

WI1_DGRSMTFLG Delivery Group Smoothing Flag

DGR

WI1_DGRTYP Delivery Group Type DGR


23


WI1_DIRORDDGR Direct Order Delivery Group

DAY,SPLR,WHCH,SKPS

WI1_DIRORDQTY Direct Order Quantity

DAY,SPLR,WHCH,SKPS

WI1_KTG Keep Together Group

DAY,SPLR,WHCH,DGR

WI1_KTS Keep Together Sku DAY,SPLR,WHCH,SKPS

WI1_PALFPE Warehouse Pallet FPE

DAY,SPLR,WHCH,SKPS

WI1_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

WI1_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


24


WR1_EDR Commodity EDR SPLR,WHCH,SKPS

WR1_INSINV Insufficient Inventory SPLR,WH,SKPS

WR1_PRYDMDPCT Warehouse Priority Demand Percentage

DAY,WH,DMGP

WR1_PRYSS_PCT Warehouse Priority Safety Stock Percentage

DAY,WH,DMGP

WR1_RP_RLL Warehouse Receipt Plan

DAY,SPLR,WHCH,SKPS

Table 6: Inputs into aliwip, tier 2


DM2_DGRASG Delivery Group Assignments DAY,SPLR,PCC,DMGP

DM2_FRSSCHRLL Warehouse From Supplier Schedule By Pack Size

DAY,SPLR,PCC,SKPS

DM2_PALMLTRLL_I PCC Pallet Multiple DAY,SPLR,PCC,SKPS

DM2_SPLORDMLT_I PCC Site Supplier Order Multiple DAY,SPLR,PCCS,SKPS

WI2_CMTORDQTY PCC Committed Order Quantity DAY,SPLR,PCC,SKPS

WI2_CPCTYP Warehouse Capacity Type PCC

WI2_CSEWGT Case Weight DAY,SPLR,PCC,SKPS

WI2_DGRCPC Delivery Group Capacity DAY,PCDG

WI2_DGRSMTFLG Delivery Group Smoothing Flag PCDG

WI2_DGRTYP Delivery Group Type PCDG

WI2_DIRORDDGR Direct Order Delivery Group DAY,SPLR,PCC,SKPS

WI2_DIRORDQTY Direct Order Quantity DAY,SPLR,PCC,SKPS

WI2_KTG Keep Together Groups DAY,SPLR,PCC,PCDG

WI2_KTS Keep Together Sku DAY,SPLR,PCC,SKPS

WI2_PALFPE PCC Pallet FPE DAY,SPLR,PCC,SKPS

WI2_PALWGT PCC Pallet Weight DAY,SPLR,PCC,SKPS

WI2_PLNHZN Warehouse Inbound Planning Horizon

scalar

WI2_PROORDIND Process Orders Indicator PCC,PCDG

WI2_SHFCPC Shift Capacity DAY,PCC,SHFT,

WI2_SLTPALCPC Slot Pallet Capacity DAY,PCC,SLT


25


WI2_SLTSHFASC Slot to Shift Relationships DAY,PCC,SLT

WI2_SLTVHCCPC Slot Vehicle Capacity DAY,PCC,SLT

WI2_STBIND Stackability Indicator DAY,SPLR,PCC,SKPS

WI2_TNSLT_ Warehouse Transportation Lead Time

DAY,PCC,PCDG

WI2_VHCFPT Vehicle footprint PCC,PCDG

WI2_VHCHGT Vehicle Height PCC,PCDG

WI2_VHCMAXWGT Vehicle Max Weight PCC,PCDG

WI2_VHCMINDRP Vehicle Minimum Drop PCC,PCDG

WI2_VHCPFC Vehicle Preferences DAY,PCC,PCDG,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

WR2_EDR Commodity EDR SPLR,PCC,SKPS

WR2_PRYDMDPCT PCC Priority Demand Percentage DAY,SPLR,PCC,DMGP

WR2_PRYSS_PCT PCC Priority Safety Stock Percentage

DAY,SPLR,PCC,DMGP

WR2_RP_RLL Warehouse Receipt Plan DAY,SPLR,PCC,SKPS


26

Outputs The aliwip binary generates similar output for tier 1 as it does for tier 2. It writes tier 1 output to different files than tier 2 output.

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.

Table 7: Outputs from aliwip, tier 1

OUTPUT Measure Label Intersection

WI1_CMTORDQTY Warehouse Committed Order Quantity

DAY,SPLR,WHCH,SKPS

WI1_DUGORDQTY Warehouse DU Aggregate Order Quantity

DAY,SPLR,WHCH,SKPS

WI1_ORDEXC Order Exceptions DAY,SPLR,WHCH,SKPS

WI1_PO_CFMDT_ PO Confirmation Date DAY,SPLR,WHCH,SKPS

WR1_RP_RLL Warehouse Receipt Plan DAY,SPLR,WHCH,SKPS

Table 8: Outputs from aliwip, tier 2

OUTPUT Measure Label Intersection

WI2_CMTORDQTY PCC Committed Order Quantity DAY,SPLR,PCC,SKPS

WI2_DUGORDQTY PCC Aggregate Order Quantity DAY,SPLR,PCC,SKPS

WI2_ORDEXC Order Exceptions DAY,SPLR,PCC,SKPS

WI2_PO_CFMDT_ PO Confirmation Date DAY,SPLR,PCC,SKPS

WR2_RP_RLL Warehouse Receipt Plan DAY,SPLR,PCC,SKPS

Two files, one of delivery units and the other for vehicles, are also written out for each tier. They are: wi1_dus.dat and wi2_vhc.dat (for tier 1) and wi2_dus.dat and wi2_vhc.dat (for tier 2).


27

Table 9: Output file from aliwip tier 1 (wi1_dus.dat) and tier 2 (wi2_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 Table 10: Output file from aliwip tier 1 (wi1_vhc.dat) and tier 2 (wi2_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

29

Chapter 6 – Interfaces WIP batch must interface with other AIP modules, both online and batch. Data flow 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_APP_BIN Refreshes the WIP domain’s hierarchy data using the Order Management new values.

Example call: load_all_hierarchies.sh <WIPDOMAIN> <DMDOMAIN>/interface

load_wiponline_measures.sh $RPAS_APP_BIN Refreshes WIP batch tier 1 and tier 2 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_wiponline_measures.sh <DOMAIN_ABSOLUTE_PATH> <WIPFTPSERVER> \ <LOCATION> user <USERNAME PASSWORD>

load_wip_inter_meas.sh $RPAS_APP_BIN Loads the measure data refreshed from Order Management into the WIP batch domain. (This script is called by load_wiponline_measures.sh.)

Example call: load_wip_inter_meas.sh <DOMAIN_PATH>


30

WRP and DM Batch to WIP Batch


wip_pull_dm.ksh <wipDomain>/scripts Refreshes DM tier 1 and tier 2 measures required by aliwip tier 1 and tier 2 executions. An intra-batch module script.

Example call: wip_pull_dm.ksh [<WIP_DOMAIN_PATH>] wip_pull_wrp_t1.ksh <wipDomain>/scripts Refreshes WRP tier 1

measures required by aliwip run on tier 1. An intra-batch module script.

Example call: wip_pull_wrp_t1.ksh [<WIP_DOMAIN_PATH>] wip_pull_wrp_t2.ksh <wipDomain>/scripts Refreshes WRP tier 2

measures required by aliwip run on tier 2. An intra-batch module script.

Example call: wip_pull_wrp_t2.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_wiponline_measures.sh load_wip_inter_meas.sh

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


31

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

IMPORT File Name

File Summary File Content

vehicle1.dat Vehicle Plan Tier 1 All committed vehicles within the current plan

vehicle2.dat Vehicle Plan Tier 2 All committed vehicles within the current plan

du1.dat Delivery Unit Plan Tier 1 All committed delivery units within the current plan

du2.dat Delivery Unit Plan Tier 2 All committed delivery units within the current plan

po1.dat Purchase Order Plan Tier 1

All committed purchase orders in the current plan

po2.dat Purchase Order Plan Tier 2

All committed purchase orders in the current plan

shift1.dat Shift Data Tier 1 All shifts for future receiving days

shift2.dat Shift Data Tier 2 All shifts for future receiving days

slot1.dat Slot Data Tier 1 All slots for future receiving days

slot2.dat Slot Data Tier 2 All slots for future receiving days

captype1.dat Receiving Capacity Type Data Tier 1

Capacity type for all scheduling locations for all future scheduling days

captype2.dat Receiving Capacity Type Data Tier 2

Capacity type for all scheduling locations for all future scheduling days

dgtype1.dat Delivery Group Type Data Tier 1

Specified type for all Delivery Groups

dgtype2.dat Delivery Group Type Data Tier 2

Specified type for all Delivery Groups

ktsupsku1.dat Keep Together Supplier/Sku Data Tier 1

All supplier/skus that must have their orders kept together

ktsupsku2.dat Keep Together Supplier/Sku Data Tier 2

All supplier/skus that must have their orders kept together

dgpref1.dat Delivery Group Preference Data Tier 1

All delivery group preferences for future scheduling days

dgpref2.dat Delivery Group Preference Data Tier 2

All delivery group preferences for future scheduling days

dirord1.dat Direct Orders Data Tier 1 All Direct Orders

dirord2.dat Direct Orders Data Tier 2 All Direct Orders


32

IMPORT File Name


vhcdgr1.dat Vehicle Delivery Group Data Tier 1

Vehicle Delivery Group data for Warehouse Chamber

vhcdgr2.dat Vehicle Delivery Group Data Tier 2

Vehicle Delivery Group Data for PCC

skupack1.dat Sku Pack Data Tier 1 Sku Pack Size Tier 1 Data

skupack2.dat Sku Pack Data Tier 2 Sku Pack Size Tier 2 Data

dgrcpc1.dat Delivery Group Capacity Tier 1

Outbound delivery group capacity for the day in number of vehicles

dgrcpc2.dat Delivery Group Capacity Tier 2

Outbound delivery group capacity for the day represented by number of vehicles

ktg1.dat Keep Together Groups Tier 1

The supplier keep together group the supplier is in

ktg2.dat Keep Together Groups Tier 2

The supplier keep together group the supplier is in

pal1.dat Warehouse Pallet Tier 1 Indicators whether to add the pallet FPE to the DU FPE and whether to add the pallet weight to the DU weight

pal2.dat Warehouse Pallet Tier 2 Indicators whether to add the pallet FPE to the DU FPE and whether to add the pallet weight to the DU weight

tnslt1.dat Warehouse Transportation Lead Time Tier 1

Transportation lead time Number of days that the vehicle must be confirmed

tnslt2.dat Warehouse Transportation Lead Time Tier 2

Transportation lead time Number of days that the vehicle must be confirmed

cmtord1.dat Warehouse Committed Order Quantity Tier 1

Committed order quantity for non-contents

cmtord2.dat PCC Committed Order Quantity Tier 2



33

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_dm.ksh dm1_dgrasg dm1_frsschrll dm1_palmltrll_i dm1_splordmlt_i dm1_stlind

dm2_dgrasg dm2_frsschrll dm2_palmltrll_i dm2_splordmlt_i

wip_pull_wrp_t1.ksh wr1_edr wr1_rp_rll wr1_insinv

wr1_prydmdpct wr1_pryss_pct

wip_pull_wrp_t2.ksh wr2_edr wr2_rp_rll

wr2_prydmdpct wr2_pryss_pct

Export files Scripts WIP batch exports several files which 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


export_wip_inter_meas.sh $RPAS_APP_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: export_wip_inter_meas.sh <WIP_DOMAIN_PATH>


34

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 export_wip_inter_meas.sh.

EXPORT File name


vehicle1.dat Vehicle Plan Tier 1 All vehicles (both committed & forecast) within the current plan.

vehicle2.dat Vehicle Plan Tier 2 All vehicles (both committed & forecast) within the current plan.

du1.dat Delivery Unit Plan Tier 1 All delivery units (both committed & forecast) within the current plan.

du2.dat Delivery Unit Plan Tier 2 All delivery units (both committed & forecast) within the current plan.

po1.dat Purchase Order Plan Tier 1 All committed purchase orders (both committed & forecast) within the current plan.

po2.dat Purchase Order Plan Tier 2 All committed purchase orders (both committed & forecast) within the current plan.

cmtord1.dat Warehouse Committed Order Quantity Tier 1


cmtord2.dat PCC Committed Order Quantity Tier 2


Chapter 7 – Implementation process

35

Chapter 7 – Implementation process Installation The 11.3 GA release of WIP contains a script named set_implementation_parms.sh. This script is located in the WIP domain’s scripts directory. (See AIP Installation Guide for information on creating a WIP domain.)

This script contains mace expressions which 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 (tier 1)

• wi2_plnhzn – Warehouse Inbound Planning Horizon (tier 2)

• wix_dmdpry – Demand Priority

• wix_ss_pry – Safety Stock Priority

• wix_rndpry – Rounding Priority

• wix_fpeadj – FPE Adjustment

• wix_wgtadj – Weight Adjustment

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

$ cd <WIP domain root directory>

$ scripts/set_implementation_parms.sh

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

Glossary

37

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

Documents

Retek Advanced Inventory Planning 11.3 Batch ...€¦ · Build vehicles – WIP builds vehicles from the delivery units. The build process loads the optimal number of delivery units