×

[PR]この広告は3ヶ月以上更新がないため表示されています。
ホームページを更新後24時間以内に表示されなくなります。




Sapass

 Simplify SAP R/3 development with Excel VBA/VB RFC  
Home> UserExit>MCST0001



Index

MCST0001

User Exits from SIS
Normally, only data from the documents is used for the statistical
update from transport documents.
If you want to use additional data for the statistical update, you
can select the data using a user exit.

User exit '001' - data enhancement at document header level
User exit '002' - data enhancement at item level

Procedure:

1. Defining the new data as fields in the ABAP/4 data dictionary
The fields must be included in the user structures MCVTTKUSR
(document header level) and MCVTTSUSR (item level).

2. Determining new fields in the user exits
To determine the field contents, data from the documents is provided:

User exit '001':
I_XMCVTTK (all fields from the document header - structure MCVTTKB)
I_CONTROL (general updating control, for example, if it is a normal
update or a statistical update)

User exit '002':
I_XMCVTTK (all fields from the document header - structure MCVTTKB)
I_XMCVTTS (all fields from the document item - structure MCVTTSB)
I_CONTROL (general updating control, for example, if it is normal
update or a statistical update)
This means that data from the document header is also provided when
processing items. If the document contains a number of items, the user
exit runs several times. When processing an item, the data of the
other items is not available.

After determining the new field content, the system transfers it
to the updating program via the structures E_XMCVTTKUSR (user exit '001') and E_XMCVTTSUSR (user exit '002').


3. Field catalog
The new fields should be included in the field catalog so that they
can be used to define info structures.

CAUTION !!!
Note the following problem areas when using this user exit:

1. Update document changes

The application always provides two types of data when changing documents: the document data that corresponds to the document status before the change and the document data after the change. Using the data before the document change, the statistical update revokes the statistical data originally updated (negative update). The normal statistical update is carried out using the new data.
If additional data is now determined using the user exit, you must ensure that when changing documents this data was not altered since the last change, or that the old statuses of the data could also be determined. You can recognize the processing of the old statuses of the data in the SUPKZ field in the structures provided. SUPKZ = '1' means that the old document data can now be processed. SUPKZ = '2' means that the new document status is offered.

2. Double reading of data

If additional data from the customer or material master record is determined, you should check if the document data should be enhanced instead. The master data is read when processing the document. If the document data is extended for the additional fields required for the statistical update, it can already be made available when reading the master data during document processing. User exits are also available for processing the document. Determining the document data a second time in the statistical update is then no longer necessary. The problem with determining the 'old' data statuses (see above) is also no longer
Function/Program:
  • EXIT_SAPLMCST_001: TIS: User Exit for Transports - Header Data
  • EXIT_SAPLMCST_002: TIS: User Exit for Transports - Segment Data

02-Oct-2005