F32921DeleteRuleValues

F32921 Delete Rule Values

Major Business Rule

Object Name: B3200180

Parent DLL: CMFG

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
This function will delete one or more rows from the Rule Values table (F32921) . Rows can be deleted
by one of the following options:

       a)File Code (FCOD), Configured Item (KIT), Branch/Plant (MCU), Rule             Number (ATO#),
Rule Sequence Number (ATOS), Segment Value (SVL)
       b)File Code (FCOD), Configured Item (KIT), Branch/Plant (MCU), Rule Number    (ATO#), Rule
Sequence Number (ATOS)
       c)File Code (FCOD), Configured Item (KIT), Branch/Plant (MCU), Rule Number   (ATO#)
       d)File Code (FCOD), Configured Item (KIT), Branch/Plant (MCU)

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 number of keys specified in the input parameters, delete all rows matching the key
values specified in the input parameters.

This function will delete one or more rows from the Rule Values table (F32921) .  Rows can be deleted
by Partial Key (Number of Key included in Input).
^

Data Structure

D3200180 - F32921 Delete Rule Values

Parameter Name Data Item Data Type Req/Opt I/O/Both

cFileCode FCOD char NONE NONE

The file code is used in the *RANGE and *VALUE file for configurations to determine if the *RANGE or *VALUE goes with a "IF" statement, a
"THEN"statement or with an assembly inclusion rule statement.

mnParentItemNumber 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.

szBranchPlant MCU char NONE NONE

An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units
for which you have no authority.

mnRuleNumber ATO# MATH_NUMERIC NONE NONE

The number associated with a set of cross-segment editing rules or assembly inclusion rules.

mnRuleSequenceNumber ATOS MATH_NUMERIC NONE NONE

The Sequence number is the rule number within an edit group of cross-segment editing rules or assembly inclusion rules. You can insert a
line within a rule to assign a new sequence number.

nNumberOfKeys INT01 integer NONE NONE

Number of Days in Future to Query for Responses Due.

cSuppressErrorMessage 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
special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.

szRuleSegmentValue SGVL char OPT NONE

An answer to the configurator feature and option questions that appear during order entry. When you define cross-segment editing rules,
you compare the segment answers to values to determine invalid configurations. When you define assembly inclusion rules, you create unique
configurations by comparing the segment answers to values to assign parts, prices, calculated values, or routing steps.

Related Functions

None

Related Tables

F32921 Cross Segment Editing Rules - Values

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cFileCode	FCOD	char	NONE	NONE
The file code is used in the RANGE and VALUE file for configurations to determine if the RANGE or VALUE goes with a "IF" statement, a "THEN"statement or with an assembly inclusion rule statement.
mnParentItemNumber	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.
szBranchPlant	MCU	char	NONE	NONE
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units for which you have no authority.
mnRuleNumber	ATO#	MATH_NUMERIC	NONE	NONE
The number associated with a set of cross-segment editing rules or assembly inclusion rules.
mnRuleSequenceNumber	ATOS	MATH_NUMERIC	NONE	NONE
The Sequence number is the rule number within an edit group of cross-segment editing rules or assembly inclusion rules. You can insert a line within a rule to assign a new sequence number.
nNumberOfKeys	INT01	integer	NONE	NONE
Number of Days in Future to Query for Responses Due.
cSuppressErrorMessage	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 special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.
szRuleSegmentValue	SGVL	char	OPT	NONE
An answer to the configurator feature and option questions that appear during order entry. When you define cross-segment editing rules, you compare the segment answers to values to determine invalid configurations. When you define assembly inclusion rules, you create unique configurations by comparing the segment answers to values to assign parts, prices, calculated values, or routing steps.