COP Stock Order Calendar

The following document describes the steps, which have to be performed in order to implement stock order calendar processing.

1. DBOXes needed

V75SPICxxV75146: This is the DBOX, which collects all stock orders selected for processing with J119. This DBOX can either be filled manually by selecting stock orders via function S138, or automatically by using Job 120 (stock order calendar processing).

V75SPICxx01002: This DBOX is filled when a stock order for a dealer is overdue, meaning the batch job identifies a customer, for whom the order day for the next stock order has arrived, but there is no stock order for this customer in the system. In this case a message is displayed, which allows the user to contact the customer so that he can send his stock order the next day.

2. Batch Programs Required

V75100: This program calculates the stock order calendar for each customer for the next 12 months. Weekends and national holidays must be put into a parameter card, so that the calculation is based on working days only. - This calculation is done once a month, but it is no problem to run the program every night within J120 or just on demand depending on the countries needs.

The program produces a list, which should be handed out to the customers. An excerpt of this list looks as follows: Download (Word 21 KB)

V75167: This program checks all customers and stock orders in the system and writes the DBOX records into V75SPICxxV75146 if the processing dates are reached. If the order date for a customer is reached, and the customer did NOT send his stock order, a DBOX message is written into V75SPICxx01002 so that the customer can be contacted.

If the stock order is there, no DBOX message will be written into V75SPICxx01002 and the program will continue with the next customer. If the process date for a customer is reached, the stock order will be put into DBOX V75SPICxxV75146 for further processing by Job 119. The protocol of V75167 shows several counters where the important ones are explained below:
DBOX-Lat: Counter of the number of records written in DBOX V75SPICxx01002.
DBOX-Pro: Number of records processed, which are in DBOX V75spicxxv75146.
DBOX-no-: Shows the number of dealers where no stock order was received but these dealers are "due" on the stock order calendar.

J120: This job may contain both above-mentioned programs but for the daily run only program V7516700 is needed.

3. Set-up CUMAI (S 62x1)

Fields Entry/Process date and order interval have to be set for those customers, whose stock orders should be treated using the stock order calendar. When a customer first starts with stock order calendar processing, these entries have to be done manually in the above-mentioned function. Later on program V7516700 recalculates the order dates for the next stock orders for this customer.

Calculation of Order Interval:
Order Entry Date + Order Interval = Next Order Entry Date

The following entries are possible in the customer master file:

Entry/Process date: 00.00.00, Interval: 0
This customer will be disregarded in the stock order calendar processing.

Entry/Process date: 00.00.00, Interval: 99
The stock orders in S 138 for this customer will be put in the DBOX V75SPIC30V75146 for processing. Meaning whenever there is a stock order in the system for this customer, it will be processed.

Entry date: 23.08.99/Process Date: 24.08.99, Interval: (Example!)
Attention:
The stock order calculation is done based on the predated date. If a customer is supposed to send in his stock orders every Friday then the ENTRY date should

Be set to the following Monday and the PROCESSING date should be set to the following thuesday. This needs to be done as the program V7516700 internally calculates it's actual run date plus 1 working day (which is assumed to be used for internal warehouse processing and reaction time in case a stock order is late) and this is the cut-off date for the stock order. So if the program runs on Friday the 20.08.99 and it finds a stock order in the system for a Customer whose date is set to 23.08.99 the program will select this order for processing. It will also change the ENTRY date to the next possible date. The processing date will remain with the date 24.08.99 until program V7516700 is run on Monday. On Monday night the process date will then be recalculated to the next possible date. To predate the entry and process date is a bid confusing but this is the way it was designed at the time. Which date has been used internally by program V7516700 can checked in DBOX V75SPIC30V75146 the date that is shown there is the date that has been used as cut-off date by program V7516700

Our recommendation is, to start with just a couple of customers until the process with the customers has been stabilised

In the above mentioned example, on the 20.08.99 the following happened:

Scenario A: Customer did not yet send his stock order

In this case, a message is written to DBOX V75SPICxx01002, so that the customer can be contacted.

Scenario B: Customer sent his stock order already (can be found in S 138)

In this case, the system identified that the order is available, . And the order was selected for further processing by job J119 and it is written into DBOX V75SPICxxV75146 for further processing.
For both scenarios the Order Date in the customer master file is rolled over to the next date in the customer's calendar. This may lead to date displays in S 62x1 such as Order Date: 30.08.99 , Process Date: 24.08.99 which is absolutely correct, as just the first date has been rolled over.

Here's what will happen on 24.08.99
All the stock orders with process date 24.08.99 and 25.08.99 will be put into DBOX V75SPICxxV75146 for further processing with job J119 (stock order processing).

Also, the process date in S 62x1 is rolled over to the next process date in the customer's stock order calendar even though there was no stock order for this customer that day.