Hierarchy
⤷ IS-U-IDX (Application Component) Enhanced Intercompany Data Exchange
⤷ /ISIDEX/EE_DEREG (Package) IDEX Deregulation Functions (PoD Identification)
Basic Data
Data Element | /ISIDEX/E_IDENT_COMPARE_NR |
Short Description | Consecutive Number of Field Comparison Rules |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | NUMC | Character string with only digits |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Con.No.FCR |
Medium | 15 | Con.No.FldCmRul |
Long | 20 | Con.No.Fld.Comp.Rule |
Heading | 10 | Con.No.FCR |
Documentation
Definition
All identification matrix fields, which must match the search data that was transferred, are grouped according to a field comparison rule. Each field comparison rule has a unique number.
Use
When identifying the point of delivery, identification matrix fields are checked to ensure that they match the search data entered. A data record is classed as identified, when all fields from the field comparison rule are matching.
Dependencies
For each process variant, you can define several field comparison rules.The field comparison rules are considered in ascending order when identifying points of delivery. As soon as a data record can be identified according to the first field comparison rule, further field comparison rules are no longer considered.
Example
A point of delivery is classed as identified when the external point of delivery ID matches the technical address. If, according to this rule, no data record can be identified, then the technical address and the meter number must be the same. In this case, you define two field comparison rules for the process variant:
History
Last changed by/on | SAP | 20050409 |
SAP Release Created in | 464 |