Recently when I was trying to create a sample material using the IDoc MATMAS_MASS_BAPI we encountered a situation where the IDoc Message processed successfully (Status 53) but a material was not created.
In such cases it is best to check the ALE interfaces for the BAPI.
In the SAP GUI run the transaction code BDBG.
This means that the basic type MATMAS_MASS_BAPI04 should be used instead of the idoc type MATMAS_MASS_BAPI03.
IDoc created using the new IDoc type MATMAS_MASS_BAPI04.
When checked in the MARA table, the material is created.
The ALE interface for BAPI is one to check whether there is a mismatch in the IDOC Type associated with the BAPI and the Basic Type used for generating the IDoc.
Development using SAP Data Services
The MATMAS_MASS_BAPI message type is used in SAP Data Services for loading Material Master data as part of data migration. I’ve used this IDoc for data migration in my previous projects. In my recent data migration implementation when using the same MATMAS_MASS_BAPI I chose to use the MATMAS_MASS_BAPI03 idoc basic type. However this was not mapped as the IDOC Type against the BAPI in the ALE
RDMS4HOP01P_3-80001221 best practise Data Migration Template has batch Job “Job_DM_MaterialMaster_IDOC” uses the MATMAS_MASS_BAPI Idoc Message type to load material master data. The IDOC Basic Type used in this template is MATMAS_MASS_BAPI03. If however the situation occurs where the IDOC type is not the one in the ALE Interface definition for the BAPI, then the IDOC message needs to be changed in order to ensure that the IDocs generated create the materials in the target SAP system.
In order to Change the target import the IDoc Type required from the datastore.
Once imported drag and drop the IDOC Basic Type in the dataflow as shown below. The target to choose is message