8 Contracts

Contract batch modules create purchase orders from contracts and purge obsolete contracts. A purchase order created from a contract has two primary differences from all other purchase orders in RMS, they are:

The only impact upon the order is a contract. Bracket costing and deals are not involved in a contract purchase order.
The cost of an item on the order is predefined in the contract and is held at the item-supplier level.

There are four types of supplier contracts in RMS: A, B, C, and D.

Type A (Plan/Availability): The contract contains a plan of manufacturing quantity by ready date. Supplier availability is matched to the ready date. Orders are raised against the plan as suggested by replenishment requirements, provided there is sufficient supplier availability. The user can also raise manual orders.
Type B (Plan/No Availability): The contract contains a plan of manufacturing quantity by ready date and dispatch-to location or locations. There are one or more ready dates, which is the date that the items are due at the dispatch-to location. Supplier availability is not required. Orders are raised automatically from the contract based on ready dates.
Type C (No Plan/No Availability): The contract is an open contract with no production schedule and no supplier availability declared. The contract lists the items that are used to satisfy a total commitment cost. Orders are raised against the contract based on replenishment requirements. The retailer can also raise manual orders.
Type D (No Plan/Availability): The contract is an open contract with no production schedule. The supplier declares availability as stock is ready. The contract lists the items that are used to satisfy a total commitment cost. Orders are raised against the contract, based on replenishment requirements and supplier availability. The retailer can raise manual orders.

Batch Design Summary

The following batch designs are included in this functional area:

edidlcon.pc (Download Contracts to Suppliers)
ediupavl.pc (Upload Item Availability for Type A & D Contracts from Suppliers)
cntrordb.pc (Create Replenishment Orders for Item/Locations on Type B Contracts)
cntrprss (Apply Type A, C & D Contracts to Orders Created by Replenishment)
cntrmain.pc (Contract Maintenance and Purging)

edidlcon (Download Contracts to Suppliers)

Module Name	edidlcon.pc
Description	Download Contracts to Suppliers
Functional Area	Contracts
Module Type	Integration
Module Technology	ProC
Catalog ID	RMS45
Runtime Parameters	N/A

Design Overview

Contacts are defined in an RMS UI that writes to series of contracts database tables. This program is used to send this contract information to vendors. Only approved contracts that are flagged as EDI contracts are processed by this batch program. The output file of this program contains all records for the supplier contract data which are in approved status.

Scheduling Constraints

Table 8-1 Scheduling Constraints

Schedule Information	Description
Frequency	Daily
Scheduling Considerations	NA
Pre-Processing	NA
Post-Processing	NA
Threading Scheme	NA

Restart/Recovery

The logical unit of work for this program is set at the contract number. This program processes one contract number at a time.

Key Tables Affected

Table 8-2 Key Tables Affected

Table	Select	Insert	Update	Delete
CONTRACT_HEADER	Yes	No	Yes	No
CONTRACT_COST	Yes	No	No	No
ITEM_MASTER	Yes	No	No	No
CONTRACT_DETAIL	Yes	No	No	No
WH	Yes	No	No	No
ITEM_SUPPLIER	Yes	No	No	No
DIFF_IDS	Yes	No	No	No

Integration Contract

Integration Type	Upload to RMS
File Name	Determined by runtime parameter
Integration Contract	IntCon000011

Table 8-3 edidlcon.pc- File Layout

Record Name	Field Name	Field Type	Default Value	Description
FHEAD	File head descriptor	Char(5)	FHEAD	Describes file line type
	Line Number	Number(10)	0000000001	Sequential file line number
	Gentran ID	Char(4)	'DNCN'	Identifies which translation Gentran uses
	Current date	Char(14)	NA	Indicates the date that the file was created in YYYYMMDDHH24MISS format
THEAD	File head de-scriptor	Char(5)	THEAD	Describes file line type
	Line Number	Number(10)	NA	Sequential file line number
	Transaction Number	Number(10)	NA	Sequential transaction number
	Supplier	Number(10)	NA	Indicates the supplier associated with the contract
	Contract Number	Number(6)	NA	Indicates the RMS contract number
	Contract type	Char(1)	NA	Type of contract. Valid types are A, B, C or D
	Department	Number(4)	NA	Indicates the RMS department ID for which the contract applies
	Currency code	Char(3)	NA	Indicates the currency code for the contract
	Total contract cost	Number(20)	NA	Contains the total cost of the contract; includes 4 implied decimal places
TDETL	File record descriptor	Char(5)	TDETL	Describes file line type
	Line Number	Number(10)	NA	Sequential file line number
	Transaction number	Number(10)	NA	Sequential transaction number
	Item Number Type	Char(6)	NA	Indicates the type of item number is represented in the file. This corresponds to the item number type defined for items on ITEM_MASTER
	Item Number	Char(25)	NA	Contains the unique ID for the item on the contract
	Ref Item Number Type	Char(6)	NA	Indicates the item number type for the reference number corresponding to the item number
	Ref Item Number	Char(25)	NA	Contains the unique ID for the reference number for the item
	Diff1	Char(120)	NA	Contains the description of Diff1 for the item
	Diff2	Char(120)	NA	Contains the description of Diff2 for the item
	Diff3	Char(120)	NA	Contains the description of Diff3 for the item
	Diff4	Char(120)	NA	Contains the description of Diff4 for the item
	VPN	Char(30)	NA	Vendor Product Number for the item
	Unit cost	Number(20)		Contains the cost of the item on the contract with 4 implied decimal places
	Ready Date	Char(14)		Date on which the items are to be provided by supplier. This field contains only values for contract types of 'A' or 'B'
	Ready Quantity	Number(20)		Quantity contracted with supplier with 4 implied decimal points. This field contains only values for contract types of 'A' or 'B'
	Location Type	Char(2)		Indicates the type of location on the contract - either 'ST' (store) or 'WH' (warehouse). This field contains only values for contract types of 'A' or 'B'
	Location number	Number(10)		Contains a location on the contract. This field contains only values for contract types of 'A' or 'B'
TTAIL	File Record descriptor	Char(5)	TTAIL	Describes file line type
	Line Number	Number(10)	NA	Sequential file line number
	Transaction number	Number(10)	NA	Sequential transaction number
FTAIL	File record descriptor	Char(5)	FTAIL	Marks the end of file
	Line number	Number(10)	NA	Sequential file line number
	Number of lines	Number(10)	NA	Number of lines in file not counting FHEAD and FTAIL

ediupavl (Upload Item Availability for Type A & D Contracts from Suppliers)

Module Name	ediupavl.pc
Description	Upload Item Availability for Type A & D Contracts from Suppliers
Functional Area	EDI - Contracts
Module Type	Integration
Module Technology	ProC
Catalog ID	RMS50
Runtime Parameters	N/A

Design Overview

This module runs to upload supplier availability information, which is a list of the items that a supplier has available. This information is used by RMS for type A and D contracts which require supplier availability information. The data uploaded is written to the SUP_AVAIL table.

Scheduling Constraints

Table 8-4 Scheduling Constraints

Schedule Information	Description
Frequency	Daily
Scheduling Considerations	N/A
Pre-Processing	N/A
Post-Processing	N/A
Threading Scheme	N/A - file-based processing

Restart/Recovery

N/A

Key Tables Affected

Table 8-5 Key Tables Affected

Table	Select	Insert	Update	Delete
SUP_AVAIL	No	Yes	Yes	No

Integration Contract

Integration Type	Upload to RMS
File Name	Determined by runtime parameter
Integration Contract	IntCon000016

Table 8-6 ediupavl.pc - File Layout

Record Name	Field Name	Field Type	Default Value	Description
FHEAD	Record descriptor	Char(5)	FHEAD	Describes file line type
	Line number	Number(10)	0000000001	Sequential file line number
	File type	Char(4)	SPAV	NA
	Create date	Char(14)	NA	File create date in YYYYMMDDHH24 MISS format
FDETL	Record descriptor	Char(5)	FDETL	Describes file line type
	Line number	Number(10)	NA	Sequential file line number
	Transaction number	Number(14)	NA	Sequential transaction number
	Supplier	Number(10)	NA	Indicates the supplier for whom the data applies
	Item type	Char(3)	NA	Indicates the type of item contained in the file. Valid types are &rsquor;ITM', &rsquor;UPC', or &rsquor;VPN'
	Item id	Char(25)	NA	Unique ID for the item
	Item supplement	Char(5)	NA	UPC supplement
	Available quantity	Number(12)	NA	Available quantity including 4 implied decimal places
FTAIL	Record descriptor	Char(5)	FTAIL	Number(10)
	Line number	Number(10)	NA	Sequential file line number (total # lines in file)
	Number of detail records	Number(10)	NA	Number of FDETL lines in file

Design Assumptions

This module will only be run if contracting is turned on in the system.

cntrordb (Create Replenishment Orders for Item/Locations on Type B Contracts)

Module Name	cntrordb.pc
Description	Create Replenishment Orders for Item/Locations on Type B Contracts
Functional Area	Contracts
Module Type	Business Processing
Module Technology	ProC
Catalog ID	RMS232
Runtime Parameters	N/A

Design Overview

This module automatically creates replenishment orders for items on an approved, orderable type &rsquor;B' contract based on production dates.

Type B (Plan/No Availability) contracts contain a plan of manufacturing quantity by ready date and dispatch-to location or locations. There are one or more ready dates, which is the date that the items are due at the dispatch-to location. Supplier availability is not required. This program automatically writes POs from the contract based on ready dates.

Prepost cntrordb post – updates the system level variable last_cont_order_date to the current vdate

Scheduling Constraints

Table 8-7 Scheduling Constraints

Schedule Information	Description
Frequency	Daily
Scheduling Considerations	This module only needs to be scheduled if the client uses contracting Must be run after repladj
Pre-Processing	repladj
Post-Processing	Prepost cntrordb post
Threading Scheme	This module is threaded by contract

Restart/Recovery

The logical unit of work is contract no. Records are committed to the database when no of records processed reaches commit_max_counter maintained in RESTART_CONTROL table.

Key Tables Affected

Table 8-8 Key Tables Affected

Table	Select	Insert	Update	Delete
SYSTEM_VARIABLES	Yes	No	No	No
SYSTEM_OPTIONS	Yes	No	No	No
PERIOD	Yes	No	No	No
CONTRACT_HEADER	Yes	No	No	No
CONTRACT_DETAIL	Yes	No	Yes	No
ORDHEAD	Yes	Yes	Yes	No
ORDSKU	Yes	Yes	Yes	No
ORDLOC	Yes	Yes	Yes	No
ORDLOC_EXP	Yes	Yes	Yes	No

Design Assumptions

This module should only be run if contracting is turned on in the system.

cntrprss (Apply Type A, C and D Contracts to Orders Created by Replenishment)

Module Name	cntrprss.pc
Description	Apply Type A, C & D Contracts to Orders Created by Replenishment
Functional Area	Contracts
Module Type	Business Processing
Module Technology	ProC
Catalog ID	RMS202
Runtime Parameters	N/A

Design Overview

This module evaluates contracts of type A, C, and D to determine whether an order should be created from the contract. Contracts are ranked so that orders are created off the best contracts first, based on lead-time, cost, contract status (such as,. closed preferred over open), and contract type (such as,. type C are preferred over D). This updates the temporary orders created by the item replenishment extract (rplext) module with the contract and supplier information of the best available contract for each item and populates the repl_results table.

Scheduling Constraints

Table 8-9 Scheduling Constraints

Schedule Information	Description
Frequency	Daily
Scheduling Considerations	Must be run after rplext and before rplbld
Pre-Processing	rplext
Post-Processing	rplbld
Threading Scheme	This module is threaded by department

Restart/Recovery

As the item requirements can span across different locations, the logical unit of work varies for each item requirement. For each item requirement, records are committed to the database.

Key Tables Affected

Table 8-10 Key Tables Affected

Table	Select	Insert	Update	Delete
ORD_TEMP	Yes	Yes	Yes	Yes
REPL_RESULTS	Yes	No	Yes	No
PERIOD	Yes	No	No	No
SYSTEM_OPTIONS	Yes	No	No	No
CONTRACT_DETAIL	Yes	No	Yes	No
CONTRACT_HEADER	Yes	No	Yes	No
CONTRACT_COST	Yes	No	No	No
ITEM_SUPP_COUNTRY	Yes	No	No	No
ITEM_MASTER	Yes	No	No	No
SUPS	Yes	No	No	No
ORD_MISSED	No	Yes	No	No
SUP_AVAIL	Yes	No	Yes	No

Design Assumptions

This module should only be run if contracting is turned on in the system.

cntrmain (Contract Maintenance and Purging)

Module Name	cntrmain.pc
Description	Contract Maintenance and Purging
Functional Area	Contracts
Module Type	Admin
Module Technology	ProC
Catalog ID	RMS231
Runtime Parameters	NA

Design Overview

This program is used to mark contracts that have reached their end date to completed (for types A and B) or review status (for types C and D). This module also purges contracts that have remained in cancelled, worksheet, submitted, or complete status for a user-defined number of months without any orders and contacts marked for deletion. The number of months is determined by the system parameter for order history months.

Scheduling Constraints

Table 8-11 Scheduling Constraints

Schedule Information	Description
Frequency	Daily
Scheduling Considerations	This module only needs to be scheduled if the client uses contracting
Pre-Processing	NA
Post-Processing	NA
Threading Scheme	NA

Restart/Recovery

This batch program has two processing functions, one for purging and another for updating contracts. The purge function (delete_contracts) deletes and commits records via arrays whose size is defined in commit max counter while the update function (reset_inactive) updates records in bulk based on the update criteria. The program as a whole is inherently restartable.

Key Tables Affected

Table 8-12 Key Tables Affected

Table	Select	Insert	Update	Delete
PURGE_CONFIG_OPTIONS	Yes	No	No	No
CONTRACT_HEADER	Yes	No	Yes	Yes
CONTRACT_DETAIL	No	No	No	Yes
CONTRACT_COST	No	No	No	Yes
ORDHEAD	Yes	No	No	No

Design Assumptions

This module should only be run if contracting is turned on in the system.