Retek Replenishment Optimization 10 - Oracle Cloud › cd › B28123_01 › ro › pdf › 102 › ro-102-ug.pdf · Printed in the United States of America. ... E-mail [email protected]

Retek® Replenishment Optimization

10.2

User Guide

Retek Replenishment Optimization

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. Corporate Headquarters:

Retek Inc.

Retek on the Mall

950 Nicollet Mall

Minneapolis, MN 55403

888.61.RETEK (toll free US)

+1 612 587 5000 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

Retek® Replenishment Optimization™ 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:

©2002 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® Confidential

Customer Support

Customer Support hours:

Customer Support is available 7x24x365 via e-mail, 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.

Contact Method Contact Information

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

E-mail [email protected]

Phone US & Canada: 1-800-61-RETEK (1-800-617-3835) World: +1 612-587-5800 EMEA: 011 44 1223 703 444 Asia Pacific: 61 425 792 927

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://www.retek.com/support

Contents i

Contents Chapter 1 – Replenishment Optimization (RO) .................... 1

What is RO? ........................................................................................................ 1

Business process.................................................................................................. 2

Chapter 2 – Base variables..................................................... 3

What is a base variable? ...................................................................................... 3

Chapter 3 – Getting started .................................................... 5

Procedures ........................................................................................................... 5

Chapter 4 – Explicit variables ................................................ 9

What is an explicit variable? ............................................................................... 9

Define an explicit variable ................................................................................ 10

Chapter 5 – Rule assessments ............................................ 15

Chapter 6 – Department control........................................... 31

Set up departments to run on RO ...................................................................... 31

Set up rules for a particular department ............................................................ 34

Chapter 7 – Review replenishment optimization................ 39

Appendix A – Description of base variables ...................... 43

Chapter 1 – Replenishment Optimization (RO) 1

Chapter 1 – Replenishment Optimization (RO)

What is RO? Replenishment Optimization uses actual client data to model and simulate your replenishment environment. Using this modeling, first, “Quick Wins” and later, optimal replenishment strategies are identified, taking into account your specific business drivers.

These optimal replenishment strategies recommended by Replenishment Optimization may include reconfiguration of RMS replenishment parameters or amendments to your replenishment processes.

The Replenishment Optimization module is then configured to apply and monitor the client-specific optimal replenishment strategies at the item/location level. The Replenishment Optimization module updates the RMS replenishment parameters as required to reflect behavior changes at the item/location level.

The Replenishment Optimization module is deployed at the client site as part of the Replenishment Optimization services offering. The module is not available without the completion of the Optimization and Simulation analysis completed by the SRI Consulting Team at Retek’s offices. The module itself does not provide optimization and simulation modeling functionality.

This micro-management of the client’s replenishment environment ensures accurate replenishment and allows the user to concentrate on maximizing profit, rather than the timely business of managing all replenishment.

Replenishment Optimization can help you:

• Reduce inventory

• Increase turns

• Maximize stock profitability

The opportunities for improvement vary for each client.

2 Retek Replenishment Optimization

Business process Business Process

Explicit Variables

Define an explicit variable

Access explicit variable Create new explicit variable

Rule Assessments Access rule assessment

Add a new rule Add rule assessment Add conditions to the assessment Add assignments

Department Control Search for the department to add Set up the department Delete department(s) from running Set up rules and rule orders for departments Delete rules from a department

Replenishment Optimization Status Approve or reject recommendation(s) Review current and recommended parameters at the item/location level Review item/location calculations and static parameters Save approved or rejected changes Cancel changes

Chapter 2 – Base variables 3

Chapter 2 – Base variables

What is a base variable? A base variable in RO 10.2 is a variable whose value is calculated for each item/location combination, based on the records in the RO tables (e.g. REPL_ITEM_LOC, ITEM_LOC_HIST, ITEM_LOC and ITEM_MASTER tables). These base variables are used to define an explicit variable and an assessment rule. Refer to Chapter 4 for more information about explicit variables and Chapter 5 for defining a rule assessment.

The value of these variables were previously calculated in the rodlopt.pc batch program, whether they were required or not by the client rules. In this release, these variables are calculated only if they are required by the client rules. Additional new base variables have also been added in this release.

Chapter 3 – Getting started 5

Chapter 3 – Getting started This chapter shows you how to log onto and exit the system. An introduction to the navigating around the system is also included.

Procedures How you access the system depends on how the system is set up at your location. Contact your system administrator for instructions. After you have started the system, you are prompted to log on.

Log on to the system

RMS Logon window

1 On the RMS Logon window, enter your user name in the Username field.

2 In the Password field, enter your password.

3 In the Connect String field, enter the name of the database that you want to access.

4 Click Logon. The Retek Enterprise Start window is displayed.


Exit system

Navigate: From the Action menu, select Close.

• Repeat this action until all the windows are closed and the program closes.

Navigate a window

Generally, you press the tab key in order to move from field to field within a window. You can also click on a field in order to place the cursor there.

You can use the mouse or the keyboard to activate a button on a window. The label on most buttons contains one underlined letter. You can press the Alt key plus the underlined letter on the keyboard in order to activate the button. If you prefer to use the mouse, you can click the button.

There are several tools within a window that you should become familiar with.

These tools simplify the data entry process.

List of Values button

The List of Values (LOV) button queries the database for a list of values. Click the LOV button to display the popup window. You choose the appropriate value from the popup window that displays the results of the query. The LOV

button is found to the right of a field. If the field is a two-part field where the first field requires an ID or code and the second field requires a description, the LOV

button is found between the two fields.

Chapter 3 – Getting started 7

Navigate: Click the LOV button to begin the query. A List of Values window displays the results of the query.

1 Select a value from the list.

2 Click OK. The selected value is entered in the text field or fields.

For some fields, usually item fields, you are prompted to enter a partial description before the query can begin. This reduces the results to a more manageable number.


Drop-down list

Some fields can only accept values from a predefined list of values. Such fields have a down arrow button to the right of the text field.

1 Click the down arrow button.

2 Select a value from the drop-down list. The value is entered in the data entry field.

Chapter 4 – Explicit variables 9

Chapter 4 – Explicit variables This chapter shows you how to create, edit, and view an explicit variable. Also it shows how to create department-level explicit variables.

What is an explicit variable? An explicit variable in RO 10.2 is a variable that can be used to define optimization rules. This variable is also used to define either the assessment rules or replenishment calculation rules.

In RO 10.2, the explicit variable is defined using this following syntax:

f(variable1 operator variable2)

where:

• f() is a mathematical function such as COS, SIN, SQRT, ABS, MOD etc.

• operator is a mathematical operator such as +, -, *, /

• variable1 and variable2 can be a base variable, a constant or a previously defined explicit variable.

Only variable1 is mandatory. But if operator is used to define an explicit variable, then variable2 becomes mandatory as well.

The list of mathematical functions that can be used in an explicit variable is:

ABS (n) - Calculates the absolute value of n.

CEIL (n) - Calculates the smallest integer greater than or equal to n.

COS (n) - Calculates the cosine of n (an angle expressed in radians).

EXP (n) - Calculates e raised to the nth power, where e = 2.71828183 ...

FLOOR (n) - Calculates the largest integer equal to or less than n.

GFCAST (n) - This is actually not a real mathematical function. This function calculates the forecast sales of an item/location in week n.

GFSDEV (n) - This is actually not a real mathematical function. This function calculates the standard deviation of forecast sales of an item/location in week n.

LN (n) - Calculates the natural log of n, where n is greater than 0.

LOG (n) - Calculates the logarithm, base 10, of n, , where n is greater than 0.


POWER (m, n) - Calculates m raised to the n th power. If n is not an integer, it will be rounded.

ROUND (n) - Calculates n rounded to 0 decimal places.

SIN (n) - Calculates the sine of n (an angle expressed in radians).

SQRT (n) - Calculates the square root of n.

TAN (n) - Calculates the tangent of n (an angle expressed in radians).

Define an explicit variable Example 1:

Let’s define an explicit variable for an optimization rule defined as:

If the following conditions are true

• median_sales_half_yr >= 14

• median_sales_half_yr < 66

• stdev_weekly_sales_half_yr / avg_weekly_sales_half_yr >= 8.9.

Then recommend these replenishment parameters

• Method = Min/Max

• Min = median_sales_hlf_yr * (total_lead_time + max_days_btwn_review) / 7

• Max = Min + 2(mean_dev_hlf_yr )*(total_lead_time + max_days_btwn_review) / 7

By reviewing Appendix A, you can see that all of the variables used in the calculations above; median_sales_half_yr, stdev_weekly_sales_half_yr, avg_weekly_sales_half_yr, total_lead_time, and max_days_btwn_review are base variables.

Since the explicit variable can only be defined based on two variables, we may have to go through a few iterations of defining explicit variables to accomplish the building of this rule.


We will define our explicit variables as follows:

To build our conditions, we need to define an explicit variable for third condition:

stdev_weekly_sales_half_yr / avg_weekly_sales_half_yr >= 8.9

We will do so as follows

Condition1 = stdev_weekly_sales_half_yr / avg_weekly_sales_half_yr

To define Min, we will define:

Min1 = (total_lead_time + max_days_btwn_review) Min2 = median_sales_hlf_yr * Min1 Min = Min2 / 7

To define Max, we will define:

Max1 = (total_lead_time + max_days_btwn_review) Max2 = mean_dev_hlf_yr * Max1 Max3 = Max2 * 2 Max4 = Max3 /7 Max = Min + Max4

Access explicit variable window

Next we will actually build the variables as outlined above.

1 From the Folder tree, select the Replenishment Optimization folder.

2 Select Rules Definition folder.

3 Select Explicit Variables.


4 Click Open. The Explicit Variable find window is displayed.


Create new explicit variable

1 In the Action field, select New.

2 Click OK. A new Explicit Variable window is displayed.

3 In the Variable Name field, enter a valid name.

4 In the Variable Type field, enter formula or constant.

If you have Variable Type as Constant then only one field Variable 1 will be enabled.

5 Enter the Numeric value if the Type is Numeric; enter the date if the Type is date, and alphanumeric if the Type is alphanumeric by clicking the LOV button.

6 For Variable Type Formula all the fields will be enabled. Enter Operator 1, variable1, Operator 2, variable 2 and then check the Dept Level check box For Variable 1 and Variable 2 use LOV button and select values.

7 Make sure that Variable 1 and Variable2 will be Numeric if Type is Numeric and Date if Type is Date and Alphanumeric for Type Alphanumeric.


8 The Dept Level button will be enabled to let you enter department level over-rides as appropriate.

The window below displays where you can establish over-rides department by department. This approach is similar to that used at the global level.

Chapter 5 – Rule Assessments 15

Chapter 5 – Rule assessments This chapter shows you how to use the explicit variables defined in Chapter 4 to create assessment and assignment rules. To clearly explain the process of creating rule assessments and assignments, two examples have been illustrated in this chapter.

Example 1: Create a simple rule with a single assessment

For this example you will build from the example used in Chapter 4 – Define an Explicit Variable. In Chapter 4 we outlined a straightforward rule as follows;




• stdev_weekly_sales_half_yr / avg_weekly_sales_half_yr >= 8.9.


• Method = Min/Max

• Min = median_sales_hlf_yr * (total_lead_time + max_days_btwn_review)/7

• Max = Min +2(mean_dev_hlf_yr )*(total_lead_time+max_days_btwn_review)/ 7

The conditions are what we use to define and build the rule’s criteria. In other words, if these conditions are met, then apply the recommendations of this rule. The recommendations are built in the form of assignments.

A particular rule may have multiple assessments, each with its own set of assignments. We will show a more complex example demonstrating this in Example 2.


Access rule assessment

1 From the Folder tree, select the Control folder.

2 Select Rules Definition.

3 Select Rule Assessment.

4 Click Open.

5 The Replenishment Rules window is displayed which lists all of the existing rules.


Add a new rule

1 Click Add to add the new rule.

2 In the Rule field, enter the rule ID. In the name field, enter the rule name (38 and Test Rule #1respectively as shown in the window below).

3 Click Assessment.

Add rule assessment

1 In the Assessment block, click Add Assess to add the assessment to the selected rule.

2 In the ID field, enter the ID name. In the Name field, enter the name (01 and Assessment 01 respectively as shown in the window below).


Add conditions to the assessment

1 In the Conditions block, click Add Cond to add a new record with the following entries.

Open braces = (

Variable1 = MEDIAN OF WEEKLY SALES 26

Comparison Operator = >=

Variable2 = 14

Close Braces = )

Join Operator = AND

2 To add a second record, click Add Cond again and add the following entries:

Open braces = (


Comparison Operator = <

Variable2 = 66

Close Braces = )

Join Operator = AND

3 To add a third record, click Add Cond again and add the following entries:

Open braces = (

Variable1 = CONDITION1


Variable2 = 8.9

Close Braces = )

Join Operator = AND

4 Click Validate. This validates that there are no syntax errors in your formulas. If an error does exist, a message appears to help you correct the error.


Add assignments

This is where you define what recommendations should be made if the conditions of this particular rule and assessment are met. You need to do two things. First, you need to establish the recommended replenishment method. Second, you need to define all of the replenishment parameters to support the recommended method.

Set the replenishment method

1 In the Assignment block, click Add.

2 You need to define the replenishment method as Min/Max. To do this, add a new record with the following entries:

Replenishment Parameter = REPLENISHMENT METHOD

Type = Constant

Value = M

3 Click Apply.

Set the replenishment parameters


2 Add a new record with the following entries:

Replenishment Parameter = MINIMUM STOCK

Type = Explicit Variable

Value = MIN

3 Click Apply.

4 Click Add.

5 In the Assignment block add another new record with the following entries:

Replenishment Parameter = MAXIMUM STOCK

Type = Explicit Variable

Value = MAX

6 Click Apply.


The window should now look like what is displayed below.

Example 2: Create a rule with multiple assessments



• stdev_weekly_sales / avg_weekly_sales < 1.5.


• Method = Dynamic

• Service Level = 90%

• Inventory Selling Days = 19

Whereas the second assessment is defined as:



• stdev_weekly_sales / avg_weekly_sales >= 1.5.



• Method = Dynamic

• Service Level = 95%

• Inventory Selling Days = 29

Notice that we can reuse the explicit variable named “Condition 1” from the previous example when defining the second condition. Re-usability is an important consideration when creating explicit variables.

Access rule assessment


2 Select Rules Definition.

3 Select Rule Assessment.

4 Click Open.

5 The Replenishment Rules window is displayed which lists all of the existing rules.


Add a new rule

1 Click Add to add the new rule.

2 In the Rule field, enter the rule ID. In the Name field, enter the rule name (39 and Test Rule #2respectively as shown in the screenshot below).

3 Click Assessment.


Add first rule assessment

1 In the Assessment block click Add Assess to add the first assessment to the selected rule.

2 To create a new record enter the ID name in the ID field. In the Name field, enter the name (01 and Assessment 01 respectively as shown in the window below).


Add conditions to the assessment


Open braces = (



Variable2 = 14

Close Braces = )

Join Operator = AND

2 To add a second record, click Add Cond again and enter with the following:

Open braces = (



Variable2 = 1.5

Close Braces = )

3 Click Validate. This validates that there are no syntax errors in your formulas. If an error does exist a message appears helping you to correct the error.

Add assignments

This is where you define what recommendations should be made if the conditions of this particular rule and assessment are met. You need to perform two steps. First, you need to establish the recommended replenishment method. Secondly, you need to define all of the replenishment parameters to support the recommended method.




2 You need to define the replenishment method as Min/Max. To define this method, add a new record with the following entries:


Type = Constant

Value = D (Dynamic)

3 Click Apply.




Replenishment Parameter = SERVICE LEVEL

Type = Constant

Value = 90

3 Click Apply.

4 Click Add.


Replenishment Parameter = INVENTORY SELLING DAYS

Type = Constant

Value = 19

6 Click Apply.


The window should look like the following:


Add second rule assessment

1 In the Assessment block click Add Assess to add the second assessment to the selected rule.

2 To create a new record enter the ID name in the ID field. In the Name field, enter the name. (02 and Assessment 02 respectively as shown in the window below).

Add conditions to the second assessment


Open braces = (



Variable2 = 14

Close Braces = )

Join Operator = AND


2 To add a second record, click Add Cond again and enter with the following:

Open braces = (



Variable2 = 1.5

Close Braces = )

3 Click Validate. This validate that there are no syntax errors in your formulas. If an error does exist a message appears helping you to correct the error.

Add assignments

This is where you define what recommendations should be made if the conditions of this particular rule and assessment are met. We need to do two things. First, you need to establish the recommended replenishment method. Second, you need to define all of the replenishment parameters to support the recommended method.



2 You need to define the replenishment method as Dynamic. To do this add a new record with the following entries:


Type = Constant

Value = D (Dynamic)

3 Click Apply.




Replenishment Parameter = SERVICE LEVEL

Type = Constant

Value = 95

3 Click Apply.


4 Click Add.


Replenishment Parameter = INVENTORY SELLING DAYS

Type = Constant

Value = 29

6 Click Apply.


The window should look like the following:

Chapter 6 – Department control 31

Chapter 6 – Department control This chapter shows you how to set up two important parameters.

• What and when departments run on RO

• What rules are applicable for each department

Set up departments to run on RO

Access department rule control


2 Select Department Rule.

3 Select Department Rule control.

4 Click Open.

5 The RO Department Process Control screen is displayed.


Search for the department to add

1 Click Add to add a department.

2 In the Department field, click the LOV button to display the list of all departments.

3 From the dropdown list, highlight the appropriate department.

4 Click OK to add the selected department.


Set up the department

1 Check the Status field checkbox to indicate that the department is set to run on RO.

2 Enter the Next Extraction Date, or click the calendar button and select the date. Once this date is reached it will trigger RO to run for this department.

3 Enter the Recurrence Frequency field to specify the recurrence frequency of the department.

4 A frequency of 1 indicates the department will run weekly; a frequency of 2 indicates RO will run once every other week; a frequency of 3 indicates RO will run once every three weeks, and so on.

5 Click OK to save your changes and close the form.

To add one more department on replenishment, click OK+Repeat before clicking OK. Enter the department, status, next extraction date and recurrence frequency as described above, and click OK to save your changes and close the form.

Delete department(s) from running

1 Click the LOV button in the Department field to display the list of departments.

2 Select the department you want to delete and click OK.

3 Click Search to populate the record that matches your search criteria.


4 Select the department to be deleted. Click Delete to delete the selected department and click Yes on the pop-up menu.

5 Click OK to close the window and save your changes.

Set up rules for a particular department

Access department rule order


2 Select Department Rule.

3 Select Department Rule Order.

4 Click Open.

5 The RO Dept Rule screen is displayed.


Set up rules and rule orders for departments

1 In the Department field, click the LOV button. The list of departments is displayed.

2 Click OK to select the department you want to set up.

3 Click Search to populate the records (if any) that match your search criteria.

4 Click Add to add rules to the selected department.

5 In the Rule ID field, click the LOV button. The list of rules is displayed.


6 Select a particular rule and click OK to assign the rule to the selected department.

7 Enter the Rule Order for the rule. Rule Order defines the priority of the rule. The rule with a Rule Order of 1 will be the first rule checked for this department; a rule with Rule Order of 2 will be checked next, and so on.

8 Check the Status checkbox to indicate that this rule designation is active. This gives you the capability to turn rules on and off on the fly.

9 Click OK to save your changes to the database. If you want to add some more rules to the same selected department, before clicking OK, click Add and enter the rule, rule order and status fields as described above. Click OK.


Delete rules from a department

1 In the Department field, click the LOV button. The list of departments is displayed.

2 Click OK to select the department where you want to delete the rules.

3 Click Search to populate the records (if any) that match your search criteria.

4 Select the rule you want to delete and click Delete. On the pop-up menu, click Yes.

5 Click OK to save the changes to the database.

Chapter 7 – Review replenishment optimization 39

Chapter 7 – Review replenishment optimization This chapter shows you how to review, approve, and reject the RO recommendations.

Access Replenishment Optimization

1 From the Folder tree, select the Replenishment Optimization folder.

2 Select Replenishment Optimization.

3 Click Open and select Edit. The Replenishment Optimization window is displayed.


Approve or reject recommendation(s)

1 In the Department field, click the LOV button A list of all pending replenishment parameters is displayed.

2 Click OK to select the department you want to review.

3 In the Status field, select a Status to filter your search or leave blank. For example, select New to display the records that have not yet been reviewed.

4 Click Search to populate the records that match your search criteria.

If you want to review supporting details about the changes before you approve a record, select the Detail Tab to review the details.

5 Click Approve All to approve all records; or click Reject All to reject all records. To approve or reject individual records, open the drop down list next to the record.

Chapter 7 – Review replenishment optimization 41

Review the current and recommended parameters at the item/location level.

1 Highlight any record and select the Parameters tab.

The left side displays current RMS replenishment parameters. The right side displays the recommended replenishment parameters.


Review the item/location calculations and static parameters

1 In the Replenishment Optimization Review window, select the Item/Location Tab select. Then select Item and Location that you want to review from the list.

2 Click the Detail tab. The Calculations and Static Replenishment Parameters are displayed.

Save approved or rejected changes

To apply status changes, click either OK to save your changes and exit out of the RO Review form, or OK + Repeat to save your changes and keep the current form open.

Cancel changes

To apply status changes, click either Cancel to exit the RO Review window without saving, or Refresh to refresh the window to allow another search to be performed.

Appendix A – Description of base variables 43

Appendix A – Description of base variables ACTIVATE DATE

Type: Date

The date on which the item/location starts to be reviewed for replenishment. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

AVG WEEKLY ISSUE 26

Type: Numeric

The average weekly issue of an Item/Location for the last 26 weeks. Even if the number of week of issues for the last 26 weeks is < 26, the average will be calculated over 26 week. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “AVG WEEKLY SALES 26” variable.

AVG WEEKLY ISSUE 52

Type: Numeric

The average weekly issue of an Item/Location for the last 52 weeks. Even if the number of week of issues for the last 52 weeks is < 52, the average will be calculated over 52 week. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “AVG WEEKLY SALES 52” variable.

AVG WEEKLY SALES 26

Type: Numeric

The average weekly sales of an Item/Location for the last 26 weeks. Even if the number of week of sales for the last 26 weeks is < 26, the average will be calculated over 26 week. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “AVG WEEKLY ISSUE 26” variable.


AVG WEEKLY SALES 52

Type: Numeric

The average weekly sales of an Item/Location for the last 52 weeks. Even if the number of week of sales for the last 52 weeks is < 52, the average will be calculated over 52 week. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “AVG WEEKLY ISSUE 52” variable.

CLASS

Type: Numeric

The class of an Item. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

COND AVG WEEKLY ISSUE 26

Type: Numeric

The average weekly issue of an Item/Location for the last 26 weeks. If the number of week of issues for the last 26 weeks is < 26, the average will be calculated over the number of weeks of issue (not over 26 weeks). The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “COND AVG WEEKLY SALES 26” variable.

COND AVG WEEKLY ISSUE 52

Type: Numeric

The average weekly issue of an Item/Location for the last 52 weeks. If the number of week of issues for the last 52 weeks is < 52, the average will be calculated over the number of weeks of issue (not over 52 weeks). The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “COND AVG WEEKLY SALES 52” variable.

COND AVG WEEKLY SALES 26

Type: Numeric

The average weekly sales of an Item/Location for the last 26 weeks. If the number of week of sales for the last 26 weeks is < 26, the average will be calculated over the number of weeks of sales (not over 26 weeks). The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “COND AVG WEEKLY ISSUE 26” variable.


COND AVG WEEKLY SALES 52

Type: Numeric

The average weekly sales of an Item/Location for the last 52 weeks. If the number of week of sales for the last 52 weeks is < 52, the average will be calculated over the number of weeks of sales (not over 52 weeks). The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “COND AVG WEEKLY ISSUE 52” variable.

CONDITIONAL STD DEV ISSUE 26

Type: Numeric

The standard deviation of weeks of issue of an Item/Location for the last 26 weeks. If the number of week of issues for the last 26 weeks is < 26, the standard deviation will be calculated over the number of weeks of issue (not over 26 weeks). The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “CONDITIONAL STD DEV ISSUE 26” variable.

CONDITIONAL STD DEV ISSUE 52

Type: Numeric

The standard deviation of weeks of issue of an Item/Location for the last 52 weeks. If the number of week of issues for the last 52 weeks is < 52, the standard deviation will be calculated over the number of weeks of issue (not over 52 weeks). The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “CONDITIONAL STD DEV ISSUE 52” variable.

CONDITIONAL STD DEV SALES 26

Type: Numeric

The standard deviation of weeks of sales of an Item/Location for the last 26 weeks. If the number of week of sales for the last 26 weeks is < 26, the standard deviation will be calculated over the number of weeks of sales (not over 26 weeks). The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “CONDITIONAL STD DEV SALES 26” variable.


CONDITIONAL STD DEV SALES 52

Type: Numeric

The standard deviation of weeks of sales of an Item/Location for the last 52 weeks. If the number of week of sales for the last 52 weeks is < 52, the standard deviation will be calculated over the number of weeks of sales (not over 52 weeks). The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “CONDITIONAL STD DEV SALES 52” variable.

CURRENT WEEK FORECAST

Type: Numeric

The forecasted sales units for the given SKU/store combination for one week after last end of week set in the system variables. This field will only contain a value for sales_type = 'R'. Available only if an item has the forecast indicator set to Y. The value for this variable will be calculated from the ITEM_FORECAST table.

DEACTIVATE DATE

Type: Date

The date on which the item/location is no longer to be reviewed for replenishment. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

DEMO STOCK

Type: Numeric

The amount of stock that cannot be sold as new and is not counted as part of inventory in the replenishment calculations. The value in this field is the amount of stock used strictly for demonstration purposes. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

DEPARTMENT

Type: Numeric

The department of an Item. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

FORECAST IND

Type: Alphanumeric

This variable indicates whether or not Retek will be interfaced to an external forecasting system. Valid values are Y and N. The value of this variable will be retrieved from the ITEM_MASTER table.


INCREMENT PERCENT

Type: Numeric

Contains the percentage by which the min and max stock levels of an item/location will be multiplied when calculating the recommended order quantity. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

INNER PACK SIZE

Type: Numeric

The break pack size for the item for the supplier. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

INVENTORY SELLING DAYS

Type: Numeric

The number of required days of on hand inventory to satisfy demand. This variable is used in the Dynamic replenishment method algorithm. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

ITEM

Type: Alphanumeric

Item number. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

LAST REVIEW DATE

Type: Date

The date on which the item/location was last reviewed. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

LOCATION

Type: Numeric

The location id. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

LOCATION TYPE

Type: Alphanumeric

The type (S = Store, W = Warehouse) of the location. The value of this variable will be retrieved from the REPL_ITEM_LOC table.


LOST SALES FACTOR

Type: Numeric

The percentage of sales that could have occurred if inventory had been available through the order lead time. This variable is used in the Dynamic replenishment method algorithm. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

MAXIMUM DAYS BETWEEN REVIEW

Type: Numeric

The maximum number of days between two reviews for an item/location The value of this variable will be calculated from the REPL_ITEM_LOC table.

MAXIMUM ISSUE 26

Type: Numeric

The maximum weekly issue quantity of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “MAXIMUM SALES 26” variable.

MAXIMUM ISSUE 52

Type: Numeric

The maximum weekly issue quantity of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “MAXIMUM SALES 52” variable.

MAXIMUM SALES 26

Type: Numeric

The maximum weekly sales quantity of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “MAXIMUM ISSUE 26” variable.

MAXIMUM SALES 52

Type: Numeric

The maximum weekly issue quantity of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “MAXIMUM ISSUE 52” variable.


MAXIMUM ISSUE DIFFERENCE 26

Type: Numeric

The maximum weekly issue quantity difference of two consecutive weeks of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “MAXIMUM SALES DIFFERENCE 26” variable.

MAXIMUM ISSUE DIFFERENCE 52

Type: Numeric

The maximum weekly issue quantity difference of two consecutive weeks of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “MAXIMUM SALES DIFFERENCE 52” variable.

MAXIMUM SALES DIFFERENCE 26

Type: Numeric

The maximum weekly sales quantity difference of two consecutive weeks of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “MAXIMUM ISSUE DIFFERENCE 26” variable.

MAXIMUM SALES DIFFERENCE 52

Type: Numeric

The maximum weekly sales quantity difference of two consecutive weeks of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “MAXIMUM ISSUE DIFFERENCE 52” variable.

MAXIMUM STOCK

Type: Numeric

The required maximum number of units available for sale. This variable is used in the Constant, Min/Max and Floating Point replenishment method algorithms. The value of this variable will be retrieved from the REPL_ITEM_LOC table.


MAXIMUM SUPPLY DAYS

Type: Numeric

The maximum number of days of supply of stock to maintain. This variable is used in the Time Supply replenishment method algorithm. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

MEAN DEVIATION OF ISSUE 26

Type: Numeric

The mean deviation of weekly issue quantity difference of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “MEAN DEVIATION OF ISSUE 26” variable.

MEAN DEVIATION OF ISSUE 52

Type: Numeric

The mean deviation of weekly issue quantity difference of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “MEAN DEVIATION OF ISSUE 52” variable.

MEAN DEVIATION OF SALES 26

Type: Numeric

The mean deviation of weekly sales quantity of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “MEAN DEVIATION OF SALES 26” variable.

MEAN DEVIATION OF SALES 52

Type: Numeric

The mean deviation of weekly sales quantity of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “MEAN DEVIATION OF SALES 52” variable.


MEDIAN OF WEEKLY ISSUE 26

Type: Numeric

The median of weekly issue quantity difference of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “MEDIAN OF WEEKLY ISSUE 26” variable.

MEDIAN OF WEEKLY ISSUE 52

Type: Numeric

The median of weekly issue quantity difference of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “MEDIAN OF WEEKLY ISSUE 52” variable.

MEDIAN OF WEEKLY SALES 26

Type: Numeric

The median of weekly sales quantity of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “MEDIAN OF WEEKLY SALES 26” variable.

MEDIAN OF WEEKLY SALES 52

Type: Numeric

The median of weekly sales quantity of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “MEDIAN OF WEEKLY SALES 52” variable.

MINIMUM ORDER REQUIRED

Type: Numeric

The minimum order quantity required by a supplier for an item. The value of this variable will be calculated from the ITEM_MASTER and ITEM_SUPPLIER_COUNTRY tables.

MINIMUM STOCK

Type: Numeric

The required minimum number of units available for sale. This variable is used in the Constant, Min/Max and Floating Point replenishment method algorithms. The value of this variable will be retrieved from the REPL_ITEM_LOC table.


MINIMUM SUPPLY DAYS

Type: Numeric

The minimum number of days of supply of stock to maintain. This variable is used in the Time Supply replenishment method algorithm. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

NO OF WEEK ISSUE 26

Type: Numeric

The number of weeks of issue of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “NO OF WEEK ISSUE 26” variable.

NO OF WEEK ISSUE 52

Type: Numeric

The number of weeks of issue of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “NO OF WEEK ISSUE 52” variable.

NO OF WEEK SALES 26

Type: Numeric

The number of weeks of sales of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “NO OF WEEK SALES 26” variable.

NO OF WEEK SALES 52

Type: Numeric

The number of weeks of sales of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “NO OF WEEK SALES 52” variable.

ORDER POINT

Type: Numeric

The order point of an item/location. The value of this variable will be retrieved from the REPL_RESULT table.


ORDER UP TO POINT

Type: Numeric

The order up to point of an item/location. The value of this variable will be retrieved from the REPL_RESULT table.

PICKUP LEAD TIME

Type: Numeric

The expected number of days required to ship the item from the supplier to the initial receiving location, which may be a store or warehouse defined on this record or the cross-dock warehouse through which the item will flow to get to the store defined on this record. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

PRESENTATION STOCK

Type: Numeric

The minimum amount of stock that needs to be on store shelves. The presentation stock is nor expected to satisfy consumer demand but is expected to remain in the fixture. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

REPLENISHMENT METHOD

Type: Alphanumeric

The character code for the algorithm that will be used to calculate the recommended order quantity for the item location. Valid values include 'C'onstant, 'M'in/Max, 'F'loating point, 'T'ime Supply, 'D'ynamic, 'SO' Store Orders. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

REPLENISHMENT ORDER CONTROL

Type: Alphanumeric

Determines if the replenishment process will create an actual order/transfer line item for the item location if there is a need for the item location or if only a record is written to the Replenishment Results table.

Valid values are 'M'anual (a record is written to the Replenishment Results table – no order/transfer line item is created), 'S'emi-Automatic (an order/transfer line item is created - the order line item will be added to an order in Worksheet status, the transfer line item will be added to a transfer in Approved status with a freight type of Hold), 'A'utomatic (an order/transfer line item is created - the order line item will be added to an order in Approved status, the transfer line item will be added to a transfer in Approved status), 'B'uyer Worksheet (a record is written to the Replenishment Results table and can be added to a purchase order on the Buyer Worksheet form/a transfer line item is added to a transfer in Approved status with a freight type of Hold). The value of this variable will be retrieved from the REPL_ITEM_LOC table.


REVIEW CYCLE

Type: Alphanumeric

The number representing when the specified item location will be reviewed for replenishment. Valid values are 0-14. A '0' represents a weekly review cycle, a '1' represents a daily review cycle, a '2' represents a review cycle of every 2 weeks, a '3' represents a review cycle of every 3 weeks, etc. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

SERVICE LEVEL

Type: Numeric

The required measure of probability that demand is satisfied from on hand inventory. This variable is used in the Dynamic replenishment method algorithm. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

SOURCE WAREHOUSE

Type: Numeric

The numeric identifier of the warehouse through which the specified item will cross dock to the specified store for a stock category of Cross docked; or the numeric identifier of the warehouse from which the specified item will be sourced for the specified store for a stock category of Warehouse Stocked. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

STD DEV FORECAST SALES

Type: Numeric

The standard deviation value for the given SKU/store combination for one week after last end of week set in the system variables. This value represents the confidence level in the sales forecast. This field is used in the safety stock calculations for the Dynamic replenishment method. Available only if an item has the forecast indicator set to Y. The value for this variable will be calculated from the ITEM_FORECAST table.

STD DEV ISSUE 26

Type: Numeric

The standard deviation of weeks of issue of an Item/Location for the last 26 weeks. Even if the number of week of issues for the last 26 weeks is < 26, the standard deviation will be calculated over 26 week. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “STD DEV ISSUE 26” variable.


STD DEV ISSUE 52

Type: Numeric

The standard deviation of weeks of issue of an Item/Location for the last 52 weeks. Even if the number of week of issues for the last 52 weeks is < 52, the standard deviation will be calculated over 52 week. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “STD DEV ISSUE 52” variable.

STD DEV SALES 26

Type: Numeric

The standard deviation of weeks of sales of an Item/Location for the last 26 weeks. Even if the number of week of sales for the last 26 weeks is < 26, the standard deviation will be calculated over 26 week. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “STD DEV SALES 26” variable.

STD DEV SALES 52

Type: Numeric

The standard deviation of weeks of sales of an Item/Location for the last 52 weeks. Even if the number of week of sales for the last 52 weeks is < 52, the standard deviation will be calculated over 52 week. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “STD DEV SALES 52” variable.

STOCK CATEGORY

Type: Alphanumeric

The sourcing strategy for the item/location relationship. Valid values are 'D'irect to store (supplier to store), 'C'ross-docked (supplier to store flowing through the warehouse), 'W'arehouse stocked (warehouse to store), 'L' for WH/Cross Link (warehouse to store and supplier to warehouse if insufficient warehouse stock). The value of this variable will be retrieved from the REPL_ITEM_LOC table.


STORE ORDER MULTIPLE

Type: Alphanumeric

The pack size level at which the item (or primary replenishment pack) is shipped between warehouses and stores. Valid values are 'C'ase, 'I'nner, 'E'ach. If the item is being replenished using a primary replenishment pack (i.e. primary_pack_no is not NULL), the store order multiple will represent the pack's store order multiple. Otherwise, the field will contain the item's store order multiple. This field is used for performance purposes during the batch replenishment process. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

SUBCLASS

Type: Numeric

The subclass of an Item. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

SUM OF ISSUE 26

Type: Numeric

The sum of issue of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “SUM OF ISSUE 26” variable.

SUM OF ISSUE 52

Type: Numeric

The sum of issue of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the issue will be all records for this item/location with sales_type = ‘I’. If the location is Store, then the value of this variable will be the same as the value of “SUM OF ISSUE 52” variable.

SUM OF SALES 26

Type: Numeric

The sum of sales of an Item/Location for the last 26 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “SUM OF SALES 26” variable.


SUM OF SALES 52

Type: Numeric

The sum of sales of an Item/Location for the last 52 weeks. The value of this variable will be calculated from the ITEM_LOC_HIST table. If the location is WH, then the sales will be calculated from the sum of sales of all stores supplied by the WH. If the location is Store, then the value of this variable will be the same as the value of “SUM OF SALES 52” variable.

SUPPLIER LEAD TIME

Type: Numeric

The number of days that will elapse between the date an order is written and the delivery to the store or warehouse from the supplier. The value of this variable will be calculated from the ITEM_MASTER and ITEM_SUPPLIER_COUNTRY tables.

SUPPLIER PACK SIZE

Type: Numeric

The quantity that orders must be placed in multiples of for the supplier for the item. The value of this variable will be calculated from the ITEM_MASTER and ITEM_SUPPLIER_COUNTRY tables.

SYSDATE

Type: Date

This variable will hold the sysdate of the database.

TERMINAL STOCK QUANTITY

Type: Numeric

The desired stock on hand for the item location when the end of season is reached. This variable is used in the Seasonal Dynamic and Seasonal Time Supply replenishment methods. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

TIME SUPPLY HORIZON

Type: Numeric

The forecasted amount over the time supply horizon. This variable is used for the time supply replenishment methods. The value of this variable will be retrieved from the REPL_ITEM_LOC table.


TOTAL LEAD TIME

Type: Numeric

This is the sum of Supplier lead time, Warehouse lead time and Pickup lead time.

VDATE

Type: Date

This variable will hold the vdate of the database.

WH LEAD TIME

Type: Numeric

The expected number of days required to move the item from the warehouse to the store defined on this record. The value of this variable will be retrieved from the REPL_ITEM_LOC table.

Documents

Retek Replenishment Optimization 10 - Oracle Cloud › cd › B28123_01 › ro › pdf › 102 › ro-102-ug.pdf · Printed in the United States of America. ... E-mail [email protected]