We’ve been implementing the BPDM package for AIO SAP for the last month, and have had good success implementing Customer, Vendor, and a number of other areas. However, in the Material Master section, we’re having difficulty adding new materials to SAP. The IDoc that is used by BPDM is MATMAS_MASS_BAPI03.
When passing IDocs to the system, most are received with Status 51 - Idoc not posted to application. The application log shows that it was ‘Trying to change xxx’, where xxx is the material number we are trying to insert.
The ones that do succeed in Status 53 are materials we already have in the system (via manual entry).
It seems that we are unable to create new materials via this IDoc, but we are able to successfully update existing materials. Is there a configuration setting in MM, or in the IDoc that would allow for the insert of new materials? I’ve looked at numbering ranges, and that was set to EXT, so that seems to be not a problem.
It looks like material numbers preceded by a letter are making it into the system. Numeric material numbers such as 1000000 to 1999999 are not.
The numbering ranges are set up though such that there is a range of numeric values that are defined as external. However, it appears that when DS or the IDoc that tries to insert these values ignores this fact and always tries to do a change operation vs a create operation.
I am also working on BOBJ Best Practices Data Migration. We have a question about Mock Loads.
a. One consultant says we can simulate the effect of BOBJ to SAP ECC table writes with “Mock Load”, without actually writing data to ECC table.
b. Other consultant says, impossible - when iDoc is sent from BOBJ DS / DM to ECC and processed, it will write the data to the table. There is no ‘Mock Load’.
Although there is no simple switch for ‘mock load’, you can disable the automatic processing of IDocs, so that it goes through the syntax and consistency check, but doesn’t actually post the document to the system. Maybe that is what consultant A was referring to.
we are implementing SAP BPDM for Data Migration and are having one issue where the Child functional location IDOC is trying to execute before the Superior Location and gets failed. Any idea how we can overcome that. Please help…
(BOB member since 2009-10-23)
(BOB member since 2005-01-12)