1.Functional Description
1.1Purpose
This function will load the component locator work file (F30UI001) used in the Component Locator
Revisions application (P3015) to store component locators for a given Branch, Parent Item, Component Item,
Component Line Number, and Effective From/Effective Thru dates. An input parameter determines how
many locators are loaded into one row of the work file; a maximum of 10 locators can be stored in one
work file record. This function uses the Get Component Locators (B3000870) business function to
retrieve locator values from the Component Locator table (F3015).
1.2Setup Notes and Prerequisites
No special setup for this function.
1.3Special Logic
There is no special logic within this function.
2.Technical Specifications
2.4Processing
A.Using the input parameters Branch, Parent Item, Component Item, Component Line Number,
Effective From and Effective Thru dates, call the Get Component Locators (B3000870) business function to
retrieve locator values from F3015 for one row of the Component Locator Work File. Save the "Last Key"
value passed backed from B3000870 to use in the next call made to retrieve more locators from F3015.
B. If locators matching the input parameters are retrieved:
1.Write a row in the Component Locator Work File using the Job Number and Computer Id
passed as input.
a) Load each row with the number of locators defined in the "Locators Per Row" input
parameter.
b) The work file line number should be incremented for each row written in this session;
i.e. the
first row for the Job Number/Computer Id combination will be 1, the next 2, etc.
c) If the Mode = 2 (Change/Inquiry):
- Put the locator value in the "Current" column and "Previous" column, e.g. Locator_1
passed from the business function will be populated on the work file in the
Locator01 field
and PreviousLocator01 fields.
- The Unique Key Id passed from the business function should also be populated on the
work file for each locator.
d) If the Mode = 1 (Copy):
- Put the locator value in the "Current" column only; initialize the previous column to
blanks (this logic will "force" an add to F3015 instead of an update in the the
Process Component Locator Work File business function)
- Initialize the Unique Key Id field to zeros.
2.Initialize any unused Locator or Previous Locator columns in the row to spaces. Initialize any
"unused" Unique Key Id field in the row to zeros.
3.Update the Total Number of Locators parameter which will be passed back to the calling program.
Only non-blank columns on the work file record should be counted.
Note: Locators should be placed in the work file in ascending sequence by locator value.
C. After a row has been written to the work file, test the MoreRecords flag passed back from Get
Component Locators business function. If there are more records, repeat steps A and B. When there are
no more records retrieved by the business function, return to the calling program.
D3001230 - Load Component Locator Work File
| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|---|---|---|---|
| cMode | EV02 | char | NONE | NONE |
An option that specifies the type of processing for an event. | ||||
| szComputerID | CTID | char | NONE | NONE |
| szBranch | MMCU | char | NONE | NONE |
A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which
| ||||
| mnParentItemNumber | KIT | MATH_NUMERIC | NONE | NONE |
The system provides for three separate item numbers.
1. Item Number (short) - An eight-digit, computer assigned, completely
| ||||
| mnComponentItemNumber | ITM | MATH_NUMERIC | NONE | NONE |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
| ||||
| jdEffectiveFromDate | EFFF | JDEDATE | NONE | NONE |
A date that indicates one of the following:
o When a component part goes into effect on a bill of material
o When a routing step goes into
| ||||
| jdEffectiveThruDate | EFFT | JDEDATE | NONE | NONE |
A date that indicates one of the following:
o When a component part is no longer in effect on a bill of material
o When a routing step is no
| ||||
| mnLocatorsPerRow | MATH01 | MATH_NUMERIC | NONE | NONE |
- - - Good Performance Low Value. | ||||
| mnTotalNumberOfLocators | MATH01 | MATH_NUMERIC | NONE | NONE |
- - - Good Performance Low Value. | ||||
| cSuppressErrorMessages | EV01 | char | NONE | NONE |
An option that specifies the type of processing for an event. | ||||
| szErrorMessageID | DTAI | char | NONE | NONE |
A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or
| ||||
| mnJobNumber | JOBS | MATH_NUMERIC | NONE | NONE |
The job number (work station ID) which executed the particular job. | ||||
| mnComponentLineNumber | CPNB | MATH_NUMERIC | OPT | NONE |
A number that specifies how the system displays the sequence of components on a single-level bill of material. This number initially
| ||||
| B3000870 Get Component Locators |
| F3015 Component Locator File | ||||
| F30UI001 Component Locators Work File |