Ansicht
Dokumentation

J-J10001 - IS-M/MDIS: OBSOLETE - MDIS Sales Order Update

The statistics update from sales orders uses data from the documents themselves, together with some data derived in the standard system.
In the LIS, the sales order data is structured in a 3-level order hierarchy consisting of header, item and schedule line. Since the partner and delivery viability set assignments can split the time slice for an item, a fourth hierarchy level was added below the schedule line, containing the partner and delivery viability set assignment data.
If you want to use other data for the statistics update that is not made available as standard, you can determine this data using user exits that are available on each of these four hierarchy levels.

User exit '004' - Derive data at document header level
User exit '005' - Derive data at item level
User exit '006' - Derive data at schedule line level
User exit '007' - Derive data at partner/DV assignment 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 available for use in determining the new fields:

User exit '004':
I_XMCJKAK (all fields from current document header - structure MCJKAKB)
I_CONTROL (general update control, determines for example whether this
is a normal update or reorganization)
T_XMCJKAK (all document headers in table - structure MCJKAKB)

User exit '005':
I_XMCJKAK (all fields from current document header - structure MCJKAKB)
I_XMCJKAP (all fields from current document item - structure MCJKAPB)
I_CONTROL (general update control, determines for example whether this
is a normal update or reorganization)
T_XMCJKAK (all document headers in table - structure MCJKAKB)
T_XMCJKAP (all document items in table - structure MCJKAPB)
This means data from the document header is also made available in item processing. If the document contains several items, the user exit is processed several times (for each individual item). When processing an item, data from other items is also made available by means of the interface tables.

User exit '006':
I_XMCJKAK (all fields from current document header - structure MCJKAKB)
I_XMCJKAP (all fields from current document item - structure MCJKAPB)
I_XMCJKEP (all fields from current schedule line - structure MCJKEPB)
I_CONTROL (general update control, determines for example whether this
is a normal update or reorganization)
T_XMCJKAK (all document headers in table - structure MCJKAKB)
T_XMCJKAP (all document items in table - structure MCJKAPB)
T_XMCJKEP (all document schedule lines in table - structure MCJKEPB)
This means data from the document header and item data is also made available in schedule line processing. If a document item contains several schedule lines, the user exit is processed several times (for each individual schedule line). When processing a schedule line, data from other schedule lines is also made available via the interface tables.

User exit '007':
I_XMCJKAK (all fields from current document header - structure MCJKAKB)
I_XMCJKAP (all fields from current document item - structure MCJKAPB)
I_XMCJKEP (all fields from current schedule line - structure MCJKEPB)
I_XMCJKPAZ (all fields from current partner/DV assgmt - struc.MCJKPAZB)
I_CONTROL (general update control, determines for example whether this
is a normal update or reorganization)
T_XMCJKAK (all document headers in table - structure MCJKAKB)
T_XMCJKAP (all document items in table - structure MCJKAPB)
T_XMCJKEP (all document schedule lines in table - structure MCJKEPB)
T_XMCJKPAZ (all partner/deliv.via.assignments - structure MCJKPAZB)
This means data from the document header, item and schedule line are made available for processing. If several assignments exist, the user exit is processed several times (once for each assignment). When processing an assignment, data from other assignments is also made available via the interface tables.

Once the new field contents have been determined, they are passed on to the update program via the structures E_XMCJKAKUSR (user exit '004'), E_XMCJKAPUSR (user exit '005'), E_XMCJKEPUSR (user exit '006') or E_XMCJKPAZUSR (user exit '007').

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

CAUTION
Please note the following when using these user exits:

1. Updates when changes are made to documents

When changes are made to documents, the application always reads two types of data: the document data that corresponds to the status of the document before the change and the document data after the change.
The statistics update uses the data before the document change to cancel the statistics data originally updated (negative posting). The new data is then used to perform the normal statistics update.
If user exits are now used to determine additional data, you must ensure that no further changes have been made to this data since the last document change, or that the old statuses of the data can be determined. Field SUPKZ in the structures indicates the processing status of the old dataset. If the entry in this field is 1, the old document data is currently being processed, and if it is 2, the new document dataset is available.