F3404AddDataFromF3002

F3404 Add Data From F3002

Minor Business Rule

Object Name: B3401100

Parent DLL: CMFG

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
This business function will add records to F3404 when a record is retrieved from F3002.

1.2Setup Notes and Prerequisites

1.3Special Logic

2.Technical Specifications
1. Read a F3404 record using DS input fields as key values
         F3404 pmkit           <           DS KIT
         F3404 pmcmcu          <           DS CMCU
         F3404 pmefft          <           DS EFFT
         F3404 pmmmcu          <           DS MMCU
         F3404 pmitm           <           DS ITM

2. if a F3404 record exists    UPDATE CONDITION
    2a. update the F3404 fields with DS input fields

3. if a F3404 record does not exist    INSERT CONDITION
    3a. build new F3404 record with DS input fields

4. Call B9800100, GetAuditInfo to retrieve audit information
    4a. assign audit information to F3404 fields
    4b. assign DS PID to F3404 PID field

5. Update or Insert F3404 record depending on CONDITION in 2 or 3

^

Data Structure

D3401100 - F3404 Add Data From F3002

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnItemNumberKit	KIT	MATH_NUMERIC	NONE	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.
szBranchComponent	CMCU	char	NONE	NONE
A secondary or lower-level business unit. The system uses the value that you enter to indicate that a branch or plant contains several subordinate departments or jobs. For example, assume that the component branch is named MMCU. The structure of MMCU might be as follows: Branch/Plant - (MMCU) Dept A - (MCU) Dept B - (MCU) Job 123 - (MCU)
szCostCenterAlt	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 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.
cCoProductsByProducts	COBY	char	NONE	NONE
A code that distinguishes standard components or ingredients from co-products,by-products, and intermediates. Co-products are (concurrent) end items as the result of a process. By-products are items that can be produced at any step of a process, but were not planned. Intermediate products are items defined as a result of a step but are automatically consumed in the following step. Generally, intermediates are nonstock items and are only defined steps with a pay-point for reporting purposes. Standard components (Discrete Manufacturing) or ingredients (Process Manufacturing) are consumed during the production process. Valid values are: C Co-products B By-products I Intermediate products Blank Standard components or ingredients
mnIdentifierShortItem	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 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
szDescription	DSC1	char	NONE	NONE
Brief information about an item; a remark or an explanation.
mnFeaturePlannedPercent	FTRP	MATH_NUMERIC	NONE	NONE
The percentage of demand for a specified feature based on projected production. For example, a company might produce 65% of their lubricant with high viscosity, and 35% with low viscosity, based on customer demand. The Material Planning system uses this percentage to accurately plan for a process's co-products and by-products. Enter percentages as whole numbers, for example, enter 5% as 5.0. The default value is 0%.
mnFeatureCostPercent	FTRP	MATH_NUMERIC	NONE	NONE
The percentage of demand for a specified feature based on projected production. For example, a company might produce 65% of their lubricant with high viscosity, and 35% with low viscosity, based on customer demand. The Material Planning system uses this percentage to accurately plan for a process's co-products and by-products. Enter percentages as whole numbers, for example, enter 5% as 5.0. The default value is 0%.
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 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.
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 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.
szProgramID	PID	char	NONE	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.

Related Functions

B9800100 Get Audit Information

F3404AddDataFromF3002