Ansicht
Dokumentation

J-J20001 - IS-M/MDIS: OBSOLETE - MDIS Correction Order Update

The statistics update for correction requests only uses data from the documents themselves, with the addition of some data derived in the standard system.
If you want to use other data in the statistics update that is not made available as standard, this data can be read by means of user exits.

User exit '001' - Derive data at document header level
User exit '002' - Derive data at item level
User exit '003' - Derive data at schedule line level

Procedure:

1. Define new data as fields in ABAP/4 Data Dictionary
The fields must be added to the user structures provided for this purpose: MCJKAKUSR (document header level), MCJKAPUSR (item level) or MCJKEPUSR (schedule line level).

2. Determine new fields in user exits
Data from the documents is used to determine the field contents:

User exit '001':
I_XMCJKAK (all fields from document header - structure MCJKAKB)
I_CONTROL (general update control, for example whether the update
is a normal update or regenerative planning)

User exit '002':
I_XMCJKAK (all fields from document header - structure MCJKAKB)
I_XMCJKAP (all fields from document item - structure MCJKAPB)
I_CONTROL (general update control, for example whether the update
is a normal update or regenerative planning)
This means data from the document header is also used for item processing. If the document contains several items, the user exit is processed several times (for each individual item). No data from other items is used when processing an item.

User exit '003':
I_XMCJKAK (all fields from document header - structure MCJKAKB)
I_XMCJKAP (all fields from document item - structure MCJKAPB)
I_XMCJKEP (all fields from schedule line - structure MCJKEPB)
I_CONTROL (general update control, for example whether the update
is a normal update or regenerative planning)
This means data from the document header and the document item are used in schedule line processing. If a document item contains several schedule lines, the user exit is processed several times (for each individual schedule line). No data from other schedule lines is used when processing a schedule line.

Once the new field contents have been determined, they are transferred to the update program via the structures E_XMCJKAKUSR (user exit '001'), E_XMCJKAPUSR (user exit '002') or E_XMCJKEPUSR (user exit '003').

3. Field catalogs
The new fields must be included in field catalogs so that they can be used when defining info structures.

CAUTION
Please note the following when using these user exits:

1. Updating changes to documents

The application always uses two types of data in changes to documents: data that corresponds to the status before the change and data after the change.
The statistics update uses the data before the change to reverse the statistics data originally updated (negative posting). The new data is then used to perform the normal statistics update.
If additional data is determined using user exits, you must ensure that the data was not changed since the last change to the document or that the old statuses of the data can also be determined. The field SUPKZ in the structures provides information on processing for these old statuses. If the entry in the field is 1, the system is processing the old data, and if the entry is 2, the new billing status is available.

2. Reading data twice

If additional data is determined from the customer or material master record, you must check whether the document data could also be derived. The master data is already read in document processing. If the additional fields required for the statistics update are added to the document data, they can be read along with the master data in document processing. User exits are also available for document processing. This means that the data need not be read for a second time in the statistics update. Doing this also eliminates the problem of determining 'old' datasets (see above) since the old field contents are recorded in the document.