SAP ABAP Data Element MCFIELDN (Matchcode field name)

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
     ⤷ SMAC (Package) R/3 Matchcode Development

Basic Data

Data Element	MCFIELDN
Short Description	Matchcode field name

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	FDNAME
Data Type	CHAR	Character String
Length	30
Decimal Places	0
Output Length	30
Value Table	DD03L

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	MC field
Medium	15	MC field name
Long	20	MC field name
Heading	10	MC field

Documentation

Definition

All the fields which could meaningfully be used at a later time in the individual matchcode IDs are defined in a matchcode object. A separate name is assigned to each of these matchcode fields for reference in the definition of the matchcode ID. Generally the matchcode field can be named immediately, like the original table field (the system automatically uses this name in the matchcode field maintenance). However, this is not always possible if two fields are to be included in a matchcode object which were defined the same name in different original tables. In this case a new name must be defined for at least one of these fields.

Only the matchcode field name, i.e. the name assigned for a field in the matchcode object, need be specified in the definition of a matchcode ID. In contrast to the matchcode object definition, where only the fields relevant for the matchcode are defined and the sequence of the fields is of no importance, the sequence of the fields in the matchcode ID definition is of great importance in determining later access behavior. This is because the matchcode records are saved in sorted order exactly according to the order of the fields (this sorting is implemented technically using a corresponding database index to the matchcode table). Later accesses to the matchcode records are then particularly efficient if the first field(s) can be restricted with values in the search condition. The first field in the matchcode ID should therefore be the field which is most frequently accessed.

Supplementary Documentation - MCFIELDN 0001

Use

Specification of the matchcode fields that belong to a matchcode ID.

Procedure

Enter the matchcode field names relevant for this matchcode ID.

Place the cursor on a table name and choose Edit -> Select fields. A list of all the fields of the associated matchcode object is displayed, which belong to this table of the matchcode ID. Choose the fields that you want to take over.

The selection sequence corresponds to the sequence in which the fields are listed in the matchcode ID. When you return to the maintenance screen, these fields are taken over.

Examples

Dependencies

Please note that the sequence in which the fields are specified in the matchcode ID definition have a decisive influence on the access process.

Therefore the sequence of the fields should correspond to the frequency with which they are accessed (specify the field accessed most frequently as the first field, etc.

Supplementary Documentation - MCFIELDN 0002

Use

Names of the fields in the matchcode object that are involved in the selection conditions for the matchcode ID.

The field conditions not necessarily refer only to the fields that belong to the matchcode ID but can also be specified for any fields from the associated matchcode object.

Procedure

To get a list of possible table fields, place the cursor on a table name and choose Select fields or Edit -> Select fields. You can mark the required fields in this list. When you return to the maintenance screen, the selected fields are taken over.

Examples

Dependencies

History

Last changed by/on	SAP	19950209
SAP Release Created in	50A