Replication of master inspection characteristics
This function module is identified as a BAPI, and is used to savemaster inspection characteristics to the database in the target system.
The ALE level contains data for the master inspection characteristic inthe form of IDOCs, prepares the data, and calls this BAPI with thecorresponding parameters and tables.
BAPI_QPMK_SAVEREPLICA performs various checks regarding the masterinspection characteristic to be saved. If no error is found, the masterinspection characteristic is saved with all its versions, short andlong texts and assigned catalogs and inspection methods to the databasein the target system.
The table RETURN contains messages in the case of an error, asexceptions are not allowed for BAPIs.
This function module can be used in connection with the DX workbench(transaction: SXDA) for initial data transfer.Description
This parameter is a general enhancement parameter. If required, itallows you to make enhancements (for example, additional data) in thisBAPI interface, without changing the structure of the interface.
The parameter is also available in BAPI 'BAPI_QPMK_REPLICATE'.
In both modules, the parameter 'EXTENSION1' can be managed with thehelp of the customer exit 'QPMK0020'. Description
This parameter is defined as a table.
A data record from 'MSTCHA' contains the complete data for a version ofa master inspection characteristic. Since a master inspectioncharacteristic can have several versions, this table can containseveral entries. One entry corresponds to one master inspectioncharacteristic version.
The structure of this parameter corresponds almost exactly to thestructure of the database table 'QPMK', the meaning of individualfields can, if required, be removed from the description for thedatabase table 'QPMK'.
In addition to the fields from the QPMK, 'MSTCHA' contains a field thatdefines whether the relevant master inspection characteristic should beposted as new, changed or deleted in the target system.
The fields CREATED_BY_USER, CREATED_ON_DATE, CHANGED_BY_USER andCHANGED_ON_DATE are entered in the interface, but are overwritten withnew values or initialized, when a master inspection characteristicversion is posted. Description
This parameter contains the inspection methods and catalogs that can beassigned to a master inspection characteristic version.
This table can be empty. Description
This parameter is defined as a table, and contains all long texts for amaster inspection characteristic/plant combination. The long texts forall versions of a master inspection characteristic can be found in thistable. A table entry corresponds to a long text line. As opposed to theshort text table 'MSTCHA_TEXT', 'MSTCHA_LONGTEXT' can contain severalentries for a master inspection characteristic version in the samelanguage.
This table can also be empty. Description
This parameter is defined as a table and contains all the physical-sample drawing long texts for a master inspection characteristic/plantcombination.
The physical-sample drawing long texts for all master inspectioncharacteristic versions are found in this table. A table entrycorresponds to physical-sample drawing long text line.
As opposed to the short text table 'MSTCHA_TEXT', 'MSTCHA_SMPL_LTXT'can contain several entries for a master inspection characteristicversion with the same language.
This table can also be empty. Description
This parameter 'MSTCHA_TEXT' is defined as a table. A data record forthis parameter contains the complete data for a short text for a masterinspection characteristic version. Several short texts can bemaintained in different languages for a master inspectioncharacteristic version.
There can or may only be one entry per language and master inspectioncharacteristic version in this table. 'MSTCHA_TEXT' must contain atleast one entry (that is, a short text) for each master inspectioncharacteristic version for the parameter 'MSTCHA'.
'MSTCHA_TEXT' contains all the short texts for all master inspectioncharacteristic versions that are listed in the parameter 'MSTCHA'.
This table must not be empty. Description
This parameter is a standard parameter for returning messages. If amessage (of whatever type) is written in this function module, themessage is stored in this return table.
Since exceptions are not allowed in BAPIs, this is the only option forreturning messages. If this table is empty, no error has occured.
This parameter is mandatory for a BAPI. You can find more informationin the description of the data type for this parameter (data type:BAPIRET2). |