Projected Demand Update Detail

Future Three demand is stored on MAC-PAC's Projected Demand File (MS150M).  When users select the Create Forecast Information option on the Future Three Interface menu, demand is sent from Future Three into the Projected Demand File in MAC-PAC.  Passing Future Three demand into MAC-PAC is a batch process.  The process should be run immediately prior to tentative schedule generations and Master Scheduling rollovers in MAC-PAC so that the MAC-PAC programs can adequately plan production for the Future Three demand.

The Company and Warehouse fields on the file are formatted (left-justified) from the Company and Warehouse fields on Future Three's Part X-REF File.  Future Three does not validate that the company and warehouse fields are filled in.  If the fields are blank on Future Three's Part X-REF File, or if a record is not found on the file, Future Three uses a default company/warehouse from category D26 on MAC-PAC's Reference File.

The part number on the Projected Demand File comes from the field PARTNO on Future Three's database.  Both Future Three's and MAC-PAC's Part Number field are fifteen bytes alphanumeric.

The Demand Type field is formatted from MAC-PAC Reference File category D26.  Future Three retrieves the default demand type codes for each of the four types of demand passed to MAC-PAC (Ship, AB, Material, and Plan).  Future Three passes demand for each of the four demand types as long as this information is available in Future Three's database.

Future Three formats the Customer Reference Number field on MAC-PAC's Projected Demand File depending on the value of a flag on MAC-PAC Reference File category D26, Future Three Interface Defaults.  The flag is called the summary/detail flag.  If this flag has a value of Y, then processing is performed in summary mode.  This means that Future Three does not format the Customer Reference Number field when adding records to or deleting records from the Projected Demand File in MAC-PAC.  All Future Three demand is placed on the Projected Demand File at the part level.  If the flag has a value of N, Future Three always formats the Customer Reference Number field when adding or deleting records from the Projected Demand File.  In this case, all Future Three demand is formatted on the Projected Demand File at the part/customer level.

When Future Three formats the Customer Reference Number field, Future Three left-justifies Future Three's Sold-to Customer Number in the field.  The first nine bytes are formatted with the Customer Number, and bytes ten and eleven are formatted with blanks.

The Start Date field contains the begin date of the demand period.  It is always stored in YYMMDD format.  Future Three always formats MAC-PAC's Projected Demand File with weekly demand quantities for each demand type.  Future Three determines the week start dates by using MAC-PAC's Shop Calendar Date Master File (CT140M) and a calendar code specified on Reference File category D26, Future Three Interface Defaults.

Three other fields exist on the Projected Demand File:  demand quantity, shipped quantity, and demand indicator.

·     Future Three formats all demand quantities in stockkeeping unit of measure (per piece units).  If a demand quantity equals zero for a week for an item, no projected demand record is written.

·     Future Three always formats the shipped quantity with zeroes for each projected demand record written.

·     Future Three always formats the demand indicator field with an F for each demand record written.  This signifies that Future Three has created the record and that the record will be deleted when a new demand update occurs.

Future Three updates the Projected Demand Audit Trail (MS150BP) and Transaction Register (MS150CP) files with the changes made to the Projected Demand File (MS150M).