10 Open To Buy

Open to Buy (OTB) budgets can either be maintained through the RMS UI or imported from a planning application.

The programs in this chapter receive OTB data from planning processes and send order information to planning processes and maintain OTB data.

For more information about integration with RPAS and other planning systems, see the section Integration with Oracle Retail Planning.

Figure 10-1 Open To Buy

Batch Design Summary

The following batch designs are included in this functional area:

otbdnld.pc (Download Current & Future OTB by Subclass)
otbdlord.pc (Download Summary of Outstanding Orders on OTB by Subclass)
otbupld.pc (Upload OTB Budget from Planning Systems)
otbprg.pc (Purge Aged Open To Buy Data)

otbdnld (Download Current & Future OTB by Subclass)

Module Name	otbdnld.pc
Description	Download Current & Future OTB by Subclass
Functional Area	Open To Buy
Module Type	Integration
Module Technology	ProC
Catalog ID	RMS130

Design Overview

This batch program will extract current and future Open to Buy data from the OTB table in RMS and export it to a flat file for use by an external planning system. All records with an end of week date greater than or equal to today will be sent.

Scheduling Constraints

Table 10-1 Scheduling Constraints

Schedule Information	Description
Frequency	Weekly
Scheduling Considerations	saldly and salweek should be run before this job
Pre-Processing	NA
Post-Processing	NA
Threading Scheme	NA

Restart/Recovery

The logical unit of work for the OTBDNLD module is department, class, subclass, and end-of-week date, with a recommended commit counter setting of 10,000. Each time the record counter equals the maximum recommended commit number, an application image array record will be written to the restart_start_array for restart/recovery if a fatal error occurs.

Key Tables Affected

Table 10-2 Key Tables Affected

Table	Select	Insert	Update	Delete
OTB	Yes	No	No	No
Period	Yes	No	No	No

Integration Contract

Integration Type	Download from RMS
File Name	Determined by runtime parameter
Integration Contract	IntCon000031

Output File

Table 10-3 otbdnld.pc - Output File

Record Name	Field Name	Field Type	Default Value	Description
FHEAD	File Type Record Descriptor	Char (5)	FHEAD	Identifies file record type
	File Line Sequence Number	Number (10)	NA	Keeps track of the record's position in the file by line number
	File Type Definition	Char (4)	NA	Identifies file as &rsquor;OTB Export'
	File Create Date	Char(14)	NA	Date the file was created in YYYYMMDD format. Remaining 6 characters are blank
FDETL	File record descriptor	Char(5)	FDETL	Identifies file record type
	File Line Sequence Number	Number (10)		Keeps track of the record's position in the file by line number
	Transaction Set Control Number	Number(14)		Used to force unique file check
	Department	Number(4)		The ID number of a department
	Class	Number(4)		The ID number of a class within the department given
	Subclass	Number(4)		The ID number of a subclass within the class given
	EOW Date	Date		The end of week date for the budgeted period. Format is 'YYYYMMDDHHMMSS'
	Week number	Number(2)		The week number in the month for the budgeted period
	Month number	Number(2)		The month number in the half for the budgeted period
	Half number	Number(5)		The half number for the budgeted period
	Cancel Amount	Number(20)		The total amount cancelled from orders of all order type for the budgeted period; value includes 4 implied decimal places
	N Approved Amount	Number(20)		The amount of approved non-basic (order type N/B) orders for the budgeted period; value includes 4 implied decimal places
	N Receipts Amount	Number(20)		The amount of non-basic (order type N/B) orders due in the budgeted period that have been received; value includes 4 implied decimal places
	B Approved Amount	Number(20)		The amount of approved buyer-replenished basic (order type BRB) orders for the budgeted period; value includes 4 implied decimal places
	B Receipts Amount	Number(20)		The amount of buyer-replenished basic (order type BRB) orders due in the budgeted period that have been received; value includes 4 implied decimal places
	A Approved Amount	Number(20)		The amount of approved auto-replenished basic (order type ARB) orders for the budgeted period; value includes 4 implied decimal places
	A Receipts Amount	Number(20)		The amount of auto-replenihed basic (order type ARB) orders due in the budgeted period that have been received; value includes 4 implied decimal places
FTAIL	File record descriptor	Char (5)	FTAIL	Identifies file record type
	File Line Sequence Number	Number (10)		Keeps track of the record's position in the file by line number
	Number of lines	Number (10)		Total number of all transaction lines, not including file header and trailer

Design Assumptions

otbdlord (Download Summary of Outstanding Orders on OTB by Subclass)

Module Name	otbdlord.pc
Description	Download Summary of Outstanding Orders on OTB by Subclass
Functional Area	Open To Buy
Module Type	Integration
Module Technology	ProC
Catalog ID	RMS13

Design Overview

This batch program runs at the end of the half to delete rows from the OTB table that are at least one half old. The current and previous half's OTB data is retained. The number of days that OTB records are retained by RMS is not configurable via a system parameter.

Scheduling Constraints

Table 10-4 Scheduling Constraints

Schedule Information	Description
Frequency	Daily
Scheduling Considerations	Run saldly and salweek before this job
Pre-Processing	NA
Post-Processing	NA
Threading Scheme	NA

Restart/Recovery

The logical unit of work for the otbdlord module is department/class/subclass. The commit_max_ctr field should be set to prevent excessive rollback space usage, and to reduce the overhead of the file I/O. The recommended commit counter setting is 10000 records. Each time the record counter equals the maximum recommended commit number, an application image array record will be written to the restart_start_array for restart/recovery if a fatal error occurs.

Key Tables Affected

Table 10-5 Key Tables Affected

Table	Select	Insert	Update	Delete
OTB	Yes	No	No	No
Period	Yes	No	No	No

Integration Contract

Integration Type	Download from RMS
File Name	Determined by runtime parameter
Integration Contract	IntCon000029

Output File

Table 10-6 otbdlord.pc - Output File

Record Name	Field Name	Field Type	Default Value	Description
File Header	File Type Record Descriptor	Char(5)	FHEAD	Identifies file record type
	File Line Sequence Number	Number(10)	NA	Keeps track of the record's position in the file by line number
	File Type Definition	Char(4)	OOEX	Identifies file as &rsquor;OTB Out-standing Order Export'
	File Create Date	Char(14)	NA	Date the file was created in YYYYMMDD format. Remaining six characters are blank.
File Detail	File Type Record Descriptor	Char(5)	FDETL	Identifies file record type
	File Line Sequence Number	Number(10)	NA	Keeps track of the record's position in the file by line number
	Transaction Set Control Number	Number(14)	NA	Sequence number used to force unique detail record check
	Department	Number(4)	NA	The number of the department which contains the outstanding order quantity value
	Class	Number(4)	NA	The number of the class which contains the outstanding order quantity value.
	Subclass	Number(4)	NA	The number of the subclass which contains the outstanding order quantity value
	N Outstanding Amt	Number(20)	NA	The amount of outstanding non-basic orders (order type N/B) for past periods; value includes 4 implied decimal places
	B Outstanding Amt	Number(20)	NA	The amount of outstanding buyer-replenished basic (order type BRB) orders for past periods; value includes 4 implied decimal places
	A Outstanding Amt	Number(20)	NA	The amount of outstanding auto-replenished basic (order type ARB) orders for past periods; value includes 4 implied decimal places
File Trailer	File Type Record Descriptor	Char(5)	FTAIL	Identifies file record type
	File Line Sequence Number	Number(10)	NA	Keeps track of the record's position in the file by line number
	Control Num-ber File Line Count	Control Num-ber File Line Count Number(10)	NA	Total number of all transaction lines, not including file header and trailer

Design Assumptions

otbupld (Upload OTB Budget from Planning Systems)

Module Name	otbupld.pc
Description	Upload OTB Budget from Planning Systems
Functional Area	Open To Buy
Module Type	Integration
Module Technology	ProC
Catalog ID	RMS132
Runtime Parameters	NA

Design Overview

The purpose of this batch module is to accept new and updated open to buy (OTB) budget data from an external planning system. RMS supports three types of OTB budgets – those associated with Non-Basic (N/B), Buyer Replenished Basic (BRB) and Auto-Replenished Basic (ARB) orders, as defined by the Order type on RMS purchase orders. OTB budgets are created by subclass/end of week date in RMS.

Scheduling Constraints

Table 10-7 Scheduling Constraints

Schedule Information	Description
Frequency	Daily
Scheduling Considerations	Optional - this interface only needs to be scheduled if OTB is interfaced into RMS from RPAS or another 3rd party planning system
Pre-Processing	NA
Post-Processing	NA
Threading Scheme	NA

Restart/Recovery

Processing of each row is independent and thus if an erroneous record is found during processing; only that record needs to be corrected and reprocessed.

If a record fails validation, it will be written to a rejected record file. This file will facilitate easy reprocessing once the error is fixed by writing the record exactly as it was in the source file.

Key Tables Affected

Table 10-8 Key Tables Affected

Table	Select	Insert	Update	Delete
OTB	No	Yes	Yes	No

Integration Contract

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

Table 10-9 otbupld - Input File

Record Name	Field Name	Field Type	Default Value	Description
FHEAD	File head descriptor	Char(5)	FHEAD	Describes file line type
	Line id	Number(10)	0000000001	Sequential file line number
	File Type Definition	Char(4)	&rsquor;OTBI'	Identifies file as &rsquor;OTB Import'
	File Create Date	Char(14)	NA	The date on which the file was written by external system. The Date is in YYYYMMDDHH24MISS format
	Subclass	Number(4)		The ID number of a subclass within the class given
	Eow Date	Char(14)		The end of week date for the budgeted week in YYYYMMDDHH24MISS format
FDETL	File record descriptor	Char(5)	FDETL	Describes file line type
	Line ID	Number(10)	NA	Sequential file line number
	Transaction Set Control Number	Number(14)	NA	Sequence number used to force unique transaction check
	Order Type	Char(1)	NA	Order type budgeted for: specified as A for ARB, B for BRB, and N for N/B
	Department	Number(4)	NA	The ID number of a department
	Class	Number(4)	NA	The ID number of a class within the department given
	Subclass	Number(4)	NA	The ID number of a subclass within the class given
	Eow Date	Char(14)	NA	The end of week date for the budgeted week in YYYYMMDDHH24MISS forma
	Budget Amount	Number(20)	NA	Budgeted amount for the specified order type/week; value includes 4 implied decimal places
FTAIL	File record descriptor	Char(5)	NA	Marks end of file
	Line ID	Number(10)	Line number in file	Sequential file line number
	Number of lines	Number(10)	Total detail lines	Number of lines in file not counting FHEAD and FTAIL

Design Assumptions

POs with an Order Type of DSD and Customer Order do not impact open to buy.

otbprg (Purge Aged Open To Buy Data)

Module Name	otbprg.pc
Description	Purge Aged Open To Buy Data
Functional Area	Open To Buy
Module Type	Admin
Module Technology	ProC
Catalog ID	RMS291
Runtime Parameters	NA

Design Overview

Scheduling Constraints

Table 10-10 Scheduling Constraints

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

Restart/Recovery

There is no restart/recovery in this module. Up to 10,000 records are deleted and committed at a time to avoid excessive rollback space in usage.

Key Tables Affected

Table 10-11 Key Tables Affected

Table	Select	Insert	Update	Delete
OTB	No	No	No	Yes