|
Contents:
1.0 Introduction
2.0 Integrating Business Connectors with XML
3.0 Benefits of XML Integration
End-to-End Web Business Processes
Open Business Document Exchange over the Internet
XML Solutions for SAP services
4.0 Structuring Interfaces of XML Documents in
Interface Repository
Architecture for Web Transactions for SAP
Business Connectors
Web Transaction services for SAP Business Connector
Adapting XML Schema Approach to integrate with SAP Business Connectors
Designing XML templates for Business Connectors
5.0 Designing XML format in the Interface
Repository
Using XML formats for BAPI
Integrating XML for RFC’s
Establishing XML formats to the IDOC
Setting Routing Table for the XML Transportation
RFC based XML messages using IFR format
Checking the Dynamic routing Process using IFR Format
6.0 Services for the SAP BC and Class
Functioning
Creating, searching and invoking RFC
Function
Understanding of wtcSAP class structure
Designing Constructor for Defining Connection
Creating SAP XML documents for RFCs/BAPI
Defining Proxy methods to the Integration Process
Converting SAP XML Object to WTScript Object
7.0 Conclusion
Extracts:
Extract 1 -
SAP BC integrates
RFC server and the client and provides an XML layer over R/3 functionality.
That is, it comes with an XML automation that converts SAP’s RFC format into
XML and supports both synchronous RFC and asynchronous RFC protocols such
that there is no requirement of SAP R/3 automation at the receiving end.
Also, SAP BC has a built in integration support for SAP’s specification of
IDOC-XML and RFC-XML standards. Hence, whenever dealing with the messages
conforming to the same standards it supports the integration.
Extract 2 -
The wtcSAP class
contains a definition of the connection to the business connector and the
SAP R/3 system data recall method for RFC and generic methods for invoking
RFCs. However, individual RFCs and BAPIs can be defined and added as an
option to the wtcSAP class by using proxy methods. In order to create a
proxy first step is launching a Web Transactions application in the base
directory using the start template wtcSAP_select.
Extract 3 - Using
XML formats for BAPI: There
are three different types of business documents for each BAPI. A request
Business Document for BAPI: The general structure of the request business
document for BAPI is:
<doc:BusinessObjectName.MethodName
xmlns:doc="urn:sap-com:document:sap:business"
[Key1=”…”, Key2=”…”, …]>
<BOR_Parameter1>...</BOR_Parameter1>
</doc:BusinessObjectName.MethodName>
In Request Business Document the root element that identifies the Request
business document carries the concatenation of the business object name and the
BOR method name as its name.
|
