F3015UpdateLocatorsBOMMBF
F3015 Update Locators for BOM MBF
Minor Business Rule
Object Name: N3003740
Parent DLL: CMFGBASE
Location: Client/Server
Language: NER
1.Functional Description
1.1Purpose
This function will change the component line number and effective from & thru dates for all component
locators for a specific component in a bill of material.
1.2Setup Notes and Prerequisites
None.
1.3Special Logic
None.
2.Technical Specifications
2.4Processing
If the From and To values are NOT equal:
1.0Open table F3015.
2.0Select from F3015 equaling the SzParentBranch, MnParentItemShort, MnComponentItemShort,
MnFromComponentLineNo, JdFromEffectiveFromDate, JdFromEffectiveThruDate .
3.0Call B9800100 - Get Audit Information
4.0For each selected record,
4.1Retrieve the Unique Key ID (UKID) and Locator (BLOC)
4.2Update for that BLOC the new values for MnToComponentLineNo, JdToEffectiveFromDate,
JdToEffectiveThruDate.
5.0Close table F3015.
Data Structure
D3003740 - F3015 Update Locators for BOM MBF
| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szParentBranch | MMCU | char | OPT | 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
represent lower-level business units, subordinate to it. For example:
o Branch/Plant (MMCU)
o Dept A (MCU)
o Dept B (MCU)
o Job 123
(MCU)
Business unit security is based on the higher-level business unit. |
| mnParentIItemShort | KIT | MATH_NUMERIC | OPT | NONE |
The system provides for three separate item numbers.
1. Item Number (short) - An eight-digit, computer assigned, completely
non-significant item number.
2. 2nd Item Number - The 25-digit, free form, user defined alphanumeric item number.
3. 3rd Item Number - Another
25-digit, free form, user defined alphanumeric item number. |
| mnComponentItemShort | ITM | MATH_NUMERIC | OPT | NONE |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:
o Item Number (short) - An eight-digit, computer-assigned item number
o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number
o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number |
| jdFromEffectiveFromDate | EFFF | JDEDATE | OPT | 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
effect as a sequence on the routing for an item
o When a rate schedule is in effect The default is the current system date. You can enter
future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and
recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system
determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity
dates you enter. |
| jdFromEffectiveThruDate | EFFT | JDEDATE | OPT | 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
longer in effect as a sequence on the routing for an item
o When a rate schedule is no longer active The default is December 31 of the
default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming
changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management,
and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by
the bill of material revision level. Some forms display data based on the effectivity dates you enter. |
| jdToEffectiveFromDate | EFFF | JDEDATE | OPT | 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
effect as a sequence on the routing for an item
o When a rate schedule is in effect The default is the current system date. You can enter
future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and
recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system
determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity
dates you enter. |
| jdToEffectiveThruDate | EFFT | JDEDATE | OPT | 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
longer in effect as a sequence on the routing for an item
o When a rate schedule is no longer active The default is December 31 of the
default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming
changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management,
and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by
the bill of material revision level. Some forms display data based on the effectivity dates you enter. |
| cSuppressErrorMessage | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| szErrorMessageID | DTAI | char | OPT | 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
special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.
|
| szProgramId | PID | char | OPT | NONE |
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry
interactive program is P4210, and the number of the Print Invoices batch process report is R42565.
The program ID is a variable length value.
It is assigned according to a structured syntax in the form TSSXXX, where:
T
The first character of the number is alphabetic and identifies the
type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a
program.
SS
The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210
indicates that this program belongs to system 42, which is the Sales Order Processing system.
XXX
The remaining characters of the numer are
numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry
program.
|
| cSearchKey | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| mnUniqueKeyIDInternal | UKID | MATH_NUMERIC | OPT | NONE |
This field is a unique number used to identify a record in a file. |
| mnFromComponentLineNo | 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
indicates the sequence in which a component was added to the bill of material. You can modify this number to change the sequence in which the
components appear.
|
| mnToComponentLineNo | 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
indicates the sequence in which a component was added to the bill of material. You can modify this number to change the sequence in which the
components appear.
|