Search Results

[5 Matches Found]
 
Article icon
SAP Professional Journal – 
Interface programming, especially writing programs that send or receive SAP Intermediate Documents (IDocs) for data exchange, can be a time-consuming and labor-intensive task. The new SAP Java IDoc Class Library reduces the complexity, time, and expense associated with writing such programs in Java. This second installment picks up where the first leaves off and shows you how to use this library to write Java programs that receive and process IDocs coming from an SAP system (i.e., IDoc server programs), and how to implement robust transactional RFC (tRFC) management for the IDoc server programs.

Article icon
SAP Professional Journal – 
Writing programs that exchange Intermediate Documents (IDocs) with an SAP system has traditionally been difficult, requiring you to either spend considerable time and effort writing complex custom code or license expensive third-party middleware. But it doesn’t have to be that way anymore. This article, the first in a two-part series, introduces the new SAP Java IDoc Class Library, a free add-on to the SAP Java Connector. Through many working examples, you will learn how to use this library to write efficient and reliable Java programs that compose and send IDocs to an SAP system (i.e., IDoc client programs), and how to implement robust transactional RFC (tRFC) management for the IDoc client programs.

Quick tips icon
by Robert Chu, Integration and Certification Center, SAP Labs March 15, 2003
SAP Professional Journal – 
- Download Business Connector services along with Java code to implement data mapping.

Article icon
SAP Professional Journal – 
As most of us know all too well, a smooth flow of information between your business partners' systems and your own can have a large impact on the success of your business processes. The SAP Business Connector (BC) enables you to easily and reliably exchange IDocs with your partners via XML messaging over the Internet. This article, the second of a two-part discussion, details two data-mapping options for sending IDoc data to your partners in non-SAP XML formats: XSLT transformation and Java services. It also shows you how to enable your system to receive non-SAP XML documents and outlines the special considerations involved.

Article icon
SAP Professional Journal – 

XML messaging between your SAP system and your business partner's system typically involves exchanging IDocs between your system and your SAP Business Connector (BC), mapping data between the IDocs and the desired external XML format, and then exchanging the XML documents between the BC and the external system. This article, the first of a two-part discussion, shows you how to use the IDoc-XML format to exchange XML documents with your partners directly, and for scenarios where this is not an option, shows you how to send documents to your partners in other XML formats using a widely adopted technique called flow services.