GT3002BCopyorDeleteGenericText

GT3002B Copy, Update, Delete Generic Text

Minor Business Rule

Object Name: B3003650

Parent DLL: CALLBSFN

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
This function will
A)Delete generic text that is associated to the F3002 record based on Parent Item, Batch Qty, and Parent Branch,  Type of Bill, Component Line
Number, and Component Item.
B)Copy the original F3002 generic text to the new F3002 record based on Parent Item, Parent Branch, Batch Qty, Type of Bill, Component Line
Number, and Component Item.

1.2Setup Notes and Prerequisites

1.3Special Logic
Set Process Edits = 'D' to delete the F3003 record's generic text.

Process Modes
D = Delete (Deletes Key in From variables)
U = Update (Updates by copying From to To, then deleting From)
C = Copy   (Copies From to To)

2.2Related Tables
F00165

2.3Related Business Functions
none

2.4Processing
If input Process Edits = Copy Mode

Copy input "From" parameters to the GT3002BF(To)  Key structure:

From Parent Item Number
From Branch Plant
From Bill Type
From Batch Qty
From Component Number
From Component Item

Copy input "To" parameters to the GT3002BT(To)  Key structure:
To Parent Item Number
To Parent Branch
To Bill Type
To Batch Qty
To Component Number
To Component Item

Call Copy Generic Text API
End If

If Successful
Error Code = 0

Else
Error Code = 1
End If

If input Process Edits = Delete Mode

Copy input "From" parameters to the GT3002BF(To)  Key structure:
From Parent Item Number
From Parent Branch
From Bill Type
From Batch Qty
From Component Number
From Component Item

Call Delete Generic Text API

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cProcessEdits	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cErrorCode	ERRC	char	OPT	NONE
This error code indicates if any errors occurred during the creation of the Trip Document Detail (F4914) records by the Delivery Document Set Server program (XT4914).
cSuppressErrorMessage	SUPPS	char	OPT	NONE
A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function. 0 = allow runtime error message handling. 1 = suppress runtime error message handling.
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.
mnFromParentItemShort	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.
szFromParentBranch	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.
szFromTypeBill	TBM	char	OPT	NONE
A user defined code (40/TB) that designates the type of bill of material. You can define different types of bills of material for different uses. For example: M Standard manufacturing bill RWK Rework bill SPR Spare parts bill The system enters bill type M in the work order header when you create a work order, unless you specify another bill type. The system reads the bill type code on the work order header to know which bill of material to use to create the work order parts list. MRP uses the bill type code to identify the bill of material to use when it attaches MRP messages. Batch bills of material must be type M for shop floor management, product costing, and MRP processing.
mnFromUnitsBatchQuantity	BQTY	MATH_NUMERIC	OPT	NONE
The quantity of finished units that you expect this bill of material or routing to produce. You can specify varying quantities of components based on the amount of finished goods produced. For example, 1 ounce of solvent is required per unit up to 100 units of finished product. However, if 200 units of finished product is produced, 2 ounces of solvent are required per finished unit. In this example, you would set up batch quantities for 100 and 200 units of finished product, specifying the proper amount of solvent per unit.
mnFromItemNumberShort	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
mnToParentItemShort	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.
szToParentBranch	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.
szToTypeBill	TBM	char	OPT	NONE
A user defined code (40/TB) that designates the type of bill of material. You can define different types of bills of material for different uses. For example: M Standard manufacturing bill RWK Rework bill SPR Spare parts bill The system enters bill type M in the work order header when you create a work order, unless you specify another bill type. The system reads the bill type code on the work order header to know which bill of material to use to create the work order parts list. MRP uses the bill type code to identify the bill of material to use when it attaches MRP messages. Batch bills of material must be type M for shop floor management, product costing, and MRP processing.
mnToUnitsBatchQuantity	BQTY	MATH_NUMERIC	OPT	NONE
The quantity of finished units that you expect this bill of material or routing to produce. You can specify varying quantities of components based on the amount of finished goods produced. For example, 1 ounce of solvent is required per unit up to 100 units of finished product. However, if 200 units of finished product is produced, 2 ounces of solvent are required per finished unit. In this example, you would set up batch quantities for 100 and 200 units of finished product, specifying the proper amount of solvent per unit.
mnToItemNumberShort	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
mnFromComponentLineNumber	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.
mnToComponentLineNumber	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.