F3404GetRecordFromF3002

F3404 Get Record From F3002

Minor Business Rule

Object Name: B3401070

Parent DLL: CMFG

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
This business function will load records on grid for P3404 when data will be retrieved from F3002.

1.2Setup Notes and Prerequisites
DS CobyIndex will be used to access members of the COBY string, used as the key to the F3002 table,
and on first call (Mode = 1) an application makes,  CobyIndex should be initialized to zero by the
calling application.

1.3Special Logic

2.Technical Specifications
KIT = User Input on Form P3404
MMCU = User Input on Form P3404
Define an array of COBY types
       CobyString[0] = B
       CobyString[1] = C
       CobyString[2] = ' '
       CobyString[3] = NULL

Note: DS CobyIndex will be used to access members of the string, and on first call (Mode = 1)
CobyIndex should be initialized to zero by the calling application.

Check CobyString[CobyIndex]  != NULL. If NULL,  ( no more COBY types in CobyString), assign '1' to DS
DoneFlag and return.
if Mode = 1
              Open Table and Read Record with ( KIT + MMCU + COBY[DS CobyIndex] ) from
F3002
              Save hRequest, hUser pointers in the corresponding DS fields

      if Mode = 2
          a. Retrieve hRequest Pointer and read Next Record with ( KIT + MMCU +
BY[DSCobyIndex] ) from F3002.
            a.1 - if record is not found, set DS FoundFlag = '9', close table and turn.
            Note - application should then add 1 to the CobyIndex so as to fetch the xt
COBY group application should then call this BF in Mode 1 again.

      if Mode = 3
           Close Table and remove hUser and hRequest Pointers

      in any Mode (except Mode 3) AND Fetch Passes
          a. If   ITM = KIT  then
                 EV01 = "  "
           Else
                 EV01 = "Y"
          b. Get description ( DSC1) from F4101 using ITM - ( X4101 Business Function )
          c. Load F3002 fields and DSC1 from X4101 into DS output fields

^

Data Structure

D3401070 - F3404 Get Record From F3002

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnShortItemNumber	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.
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.
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
szDescriptionLine1	DSC1	char	NONE	NONE
Brief information about an item; a remark or an explanation.
cFoundFlag	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
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.
idF3002_HRequestPointer	GENLNG	ID	NONE	NONE
General purpose ID variable.
cMode	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
idF3002_HUserPointer	GENLNG	ID	NONE	NONE
General purpose ID variable.
nCobyIndex	INT01	integer	NONE	NONE
Number of Days in Future to Query for Responses Due.
cDone	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
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)

Related Functions

X4101 Validate and Retrieve Item Master

Related Tables

F3002 Bill of Material Master File
F4101 Item Master