Matchcode records are not displayed even though the corresponding Data Dictionary objects (MC object, MC ID, Matchcode pool) have been maintained correctly.
Notice that the functions of matchcodes in the F4 help to Release 4.0
changes itself. Matchcodes are automatically replaced during the release
change by search help. With that, each matchcode object is converted in a collective search help and each matchcode ID is converted in an elementary search help.
The created elementary search helps, which consist from physically realized matchcode IDs (update type A,S or P), continue to select their data from the matchcode ID assigned pool table.
For physical matchcodes (update type A, S or P), the matchcode data is stored redundantly in the System as separate tables. These tables must be constructed after you have stored and activated the matchcode object and the matchcode IDs, and stored the matchcode pool in the database. This table is constructed or deleted using the matchcode utilities (Report SAPMACO). The table is structured in the same way for all physical update types (A, S or P).
The matchcode utility works for all clients. A parameter controls whether matchcodes are to be constructed or deleted for a specific client or for all clients. In addition, the utility also offers the option of constructing matchcodes for all matchcode objects in one run.
The matchcode records must be constructed using the matchcode utility.
Working with the matchcode utility
In the screen Maintain Matchcode Object (Attributes), choose the
function Utilities -> Matchcode data -> Construct. This calls the matchcode utility.
function
Alternatively, you can call the matchcode utility by starting the report SAPMACO. In the screen
You can maintain one or more matchcode objects. If a matchcode object is to be dealt with, you must enter its name. Otherwise enter a normal ABAP/4 Open SQL Like pattern. If "*" is entered, all matchcode objects are maintained.
Client-dependent matchcode objects can be maintained for a particular client or for all clients. The logon client is taken as a default value.
If this parameter is not changed, then matchcodes are constructed only in the clients in question, all other clients remain unchanged.
If a matchcode is to be constructed in a client other than the logon client, you must enter the client ID in question. If you enter "*" a matchcode is constructed in all clients.
You can choose a function to be carried out by the matchcode utility. This function is then carried out for all matchcode IDs or for selected matchcode IDs. A corresponding query is made in the following process of the program.
o,,
o,,
o,,
o,,
o,,
A default function is entered when calling the matchcode utility from the screen Maintain Matchcode Object (Attributes). If necessary, you can overwrite this default entry. When calling
o,,
o,,
o,,
The matchcode utility functions can be executed either in the background or online. If you enter an 'X', the function is executed in the background, otherwise it is executed in online mode.
The name of the batch job is: ASYN_MC_function_mconame (for example, construction of the matchcode object VMVA: ASYN_MC_CRE_VMVA). A job repetition period can be specified in days for background processing.
If the chosen function is processed in the background, the batch job can be executed immediately or at a certain time. If execution is to be carried out immediately, enter an 'X'. If you do not make an entry, you must specify a start time in the following line.
If a job repetition period is entered in days, then the specified time also applies to the job repetition.
Here you specify the planned date and time of execution of a batch job Please note that under certain circumstances the construction of matchcode records can load the system quite heavily. In such cases it is sensible to plan the batch job for a time when the system has a smaller load, for example, at night.
Period length (days) for a batch job. This means that the batch job is repeated at the same time of day after the specified number of days.
If just one matchcode object is to be processed, you must specify the matchcode IDs in the further progression of the program. If you are maintaining several matchcode objects, the program assumes that
Status of the matchcode IDs
You can display the status of the individual matchcode IDs in the table TMCIR via the general table maintenance. To do this, proceed as follows:: Choose
- 1. Enter TMCIR as the table name. Choose
The data contained in table TMCIR is displayed. Among other things, you can enter the following status specifications in field
,,
,,
,,
,,
,,
,,
Furthermore you can take the number of constructed/deleted tuples (Tup number), the start and the end of such an activity (start function, end function) from the table. The table entry for the number of tuples is not changed for necessary adjustments for matchcode IDs that are maintained synchronously or controlled by a program.
You also receive information on records with deletion indicators for matchcode IDs (LKZ), the time stamp for the last deletion of records with a deletion indicator (time LKZ-Del.), via the message number if an error occurs (Msgno) and via the generation time of the function module (Gen.-zeitpunkt) (generation time).
Display of the constructed matchcode data
You can display the constructed matchcode data for a matchcode ID using the general table display. To do this, branch into the general table display by calling transaction SE16, and enter the name of the pool table belonging to the matchcode ID (name. In the following screen, choose the function
the menu
No comments:
Post a Comment