How can a Java application pass data to an SAP table using JCo?

How can a Java application pass data to an SAP table using JCo?

How can a Java application pass data to an SAP table using JCo?

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Updating a table directly in SAP is not recommended practice. If the table you need to update is part of a standard business object, use the function builder to find the appropriate RFC or BAPI to call to update the business object. This ensures that you are not at risk of only updating part of a business object thus creating a rift in your transactional or master data.

If the table is a custom table that you have built in SAP, you will need to create a new RFC in the function builder that updates your custom table appropriately. In any case, JCo makes it easy to interface with SAP, through Java, using an RFC/BAPI, whether standard or custom. Once you have the interface identified, JCo allows you to retrieve a Java representation of that interface, input the appropriate parameters, structures, and tables, then commit these changes directly to the business object or custom table, as required.

This was first published in June 2005