Q
Problem solve Get help with specific problems with your technologies, process and projects.

Using Mass Data BAPI to move materials between clients

I have a fairly new business process with a problem in PRD that I cannot duplicate in QAS. I would like to transport all of the newly created materials and business documents (sales orders, purchase orders, etc.) from PRD to QAS to help troubleshoot. Will the Mass Data BAPI get the job done?

Have you ever used the Mass Data BAPI to move materials and specifically business reference documents between SAP clients? Example: I have a fairly new business process with a problem in PRD that I cannot duplicate in QAS. I would like to transport all of the newly created materials and business documents (sales orders, purchase orders, etc.) from PRD to QAS to help troubleshoot.

In the old 3.1 world I used IDocs to do some of this. At my new company, the Basis staff has no experience doing...

this and are resisting. Is it possible to use the replicate BAPI to achieve what I would like to do?

Any information you can provide will be greatly appreciated.
Regards,
Tim Wise

The only recommended version for doing this is using the ALE-IDoc replication. Due to the nature and complexity of the material master, you should abide by this path.

The steps to do this are easy and having your Basis staff say they have no experience is a foul excuse. Being able to set up an IDoc path between systems is a mandatory skill for any basis admin. Given the fact that creating the necessary partner profiles and RFC connection between the logical systems is a fairly easy and quick task to do, you may expect that they read the appropriate documentation or visit the two IDoc/ALE courses if nothing helps.

Here the steps:

1. Create an RFC connection from sender system to receiver system with SM59

2. Go to transaction SALE

2a. Maintain the logical systems in table TBDLS (you can use SM31 or select maintain LS in transaction SALE)

2b. Create an arbitrary new model and attach the message type MATMAS for the path DEV->>QAS (if not done, transport the logical systems changes to the receiver system)

2c. Distribute the new model to QAS

2d. Generate the partner profile in both systems (there is a menu entry) or maintain them with WE20 manually (not recommended unless you know what you are doing).

3. Send the data with transaction BD10

This was last published in October 2004

Dig Deeper on SAP interface technologies

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close