This function module is marked as a BAPI and is used to save inspectionmethods in the target system.
The ALE layer contains inspection method data in the form of IDocs,formats the data, and calls up this BAPI with the correspondingparameters and tables.
BABI_QMTB_SAVEREPLICA performs various checks on the inspection methodthat is to be saved. If no errors occur, the inspection method is savedto the database in the target system with all its versions and shortand long texts.
The table RETURN contains messages if there are errors, sinceexceptions are not allowed for BAPIs.
This function module can also be used with the DX Workbench(transaction: SXDA) for initial data transfer.Description
This parameter is a general enhancement parameter that can be used tomake enhancements in this BAPI interface (for example, additional data)without changing the structure of the interface.
The parameter is also available in the BAPI "BAPI_QMTB_REPLICATE".
The parameter "EXTENSION1" can be managed in both modules usingcustomer enhancement"QSMT0020". Description
This parameter is displayed as a table. A data record of"INSPECTION_METHOD" contains the complete data for a version of aninspection method. Since an inspection method can have severalversions, this table can contain several entries. An entry correspondsto an inspection method version.
The structure of this parameter corresponds almost exactly to thestructure of the database table "QMTB". The meaning of the singlefields can be taken from the description for the database table "QMTB"if necessary.
In addition to the fields from QMTB, "INSPECTION_METHOD" contains afield with the description FUNCTION, which specifies whether therespective inspection method should be reposted, changed, or deleted inthe target system.
Note that the fields "CREATED_BY_USER", "CREATED_ON_DATE","CHANGED_BY_USER", and "CHANGED_ON_DATE" are contained in the interfacebut are generally overwritten when you save the IDoc data in the targetsystem. Value range
The parameter "INSPECTION_METHOD" should contain at least one datarecord, otherwise it is not possible to reaccess this BAPI. Description
This parameter is displayed as a table and contains all long texts foran inspection method/plant combination. The long texts for all versionsof an inspection method are in this table.
A table entry represents a long text line. In comparison to the shorttext table "INSP_METH_TEXT", "INSP_METH_LONGTEXT" can contain severalentries for an inspection method version in the same language.
This table can also be empty. Description
This parameter "INSP_METH_TEXT" is displayed as a table.
A data record for this parameter contains the complete data for a shorttext of an inspection method version. Several short texts can bemaintained in different languages for an inspection method version.There can only be one entry in this table for each language andinspection method version.
However, there must be at least one entry (this means, one short text)for each inspection method version of the parameter "INSPECTION_METHOD"in "INSP_METH_TEXT".
"INSP_METH_TEXT" contains all short texts for all inspection methodversions that are listed in the parameter "INSPECTION_METHOD".
This table cannot be empty. Description
This parameter is the standard parameter for the return of messages. Ifa message (any message type) is written within this function module,the message is stored in this return table.
Since exceptions are not allowed in BAPIs, this is the only way toreturn messages. If this table is empty, no errors have occured.
This parameter is required for a BAPI. For more information, see thedescription for the data type of this parameter (Data type: BAPIRET2). |