F3295DeleteSegmentValueHistRow

F3295 Delete Segment Value History Row

Minor Business Rule

Object Name: N3200755

Parent DLL: CMFG

Location: Client/Server

Language: NER

1.Functional Description

1.1Purpose
This business function will delete a row of the Segment Value History table (F3295) by key.

1.2Setup Notes and Prerequisites
No special setup required.

1.3Special Logic
None.

2.Technical Specifications



1.Retrieve Segment Value History row by key.


2.Delete row from table.

Data Structure

D3200755 - F3295 Segment Value History by Key

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
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.
mnConfigurationIDNumber	CFGID	MATH_NUMERIC	OPT	NONE
An identifier that represents a unique configuration. It is generated by a next number value and is the key to the configuration tables.
mnComponentIDNumber	CFGCID	MATH_NUMERIC	OPT	NONE
A number that represents a component in a configuration. This number, which is generated by next numbers, always restarts at 1 and increments, based on the number of components in the configuration.
mnParentSegmentNumber	PEL	MATH_NUMERIC	OPT	NONE
A number that establishes the sequence in which the segments were defined in the system. Segment numbers are user defined. Cross-segment editing rules reference the segment numbers to ensure that the set of values defines a valid configuration. Assembly inclusion rules reference segment numbers and their associated values to define prices, component parts, routing, and calculated values for configured items.
szSegmentValue	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

None