SAP RFC Integration through BizTalk

It has been a long while since I published some technical write-ups into my blog. Today, I will try to elaborate on Integration mechanism with SAP though BizTalk middleware. As you are aware, SAP is a self-contained and modular system. So, communicating with SAP is a complex process. You have to have basic understanding of SAP Modules and Data Query/Retrieval process. But, communicating to SAP through RFC function calls has made it even easier. You can communicate with SAP RFCs in three different ways:

1.    Access SAP RFCs using WCF-SAP Adapter and SAP system credentials

2.    Access SAF RFCs through exposed RFCs as ABAP web services

3.    Access SAF RFCs through SAP Process Orchestrator, which is basically the SAP integration middleware

Today, I will concentrate on No. 2, which is to communicate with SAP through RFC Web Services via ABAP web services. To do that, you need to expose SAP RFCs as consumable web services. Please follow THIS to expose RFCs as ABAP web services and follow THIS link to expose RFCs as SOAP web services through SAP Process Orchestrator. But, in either ways you should be able to communicate with SAP with system credentials.

I will be using Visual Studio to demonstrate the BizTalk Orchestration development.

Step 1: Create a BizTalk Project

Step 2: Add Generated Items to the Project

Step 3: Consume WCF Service

Step 4: Consume Meta Data from a set of (*.WSDL) files

Step 5: Add the WSD Path and File Name

Step 6. Click Import and it will import the Service Description to the BizTalk Project and it will automatically create necessary Schema Definition for SAP Web Service, SAP Request Response Port Type and a Blank Orchestration file.

Step 7: Open up the Orchestration file and add the Receive, Transform, Send, Receive, Transform and Send shapes in to the blank orchestration in the following order

Step 8: Add a Schema (i.e. InputSchema.xsd) to the Solution for the Parameter Input file and add a Child Record (i.e. InputParameters) and add necessary Child elements to it.

Step 9: Add another Schema (i.e. OutputSchema.xsd) to the Solution for the Query output file and add a Child Record (i.e. Locations) followed by another child record (i.e. Location) for Looping through multiple item. Then add necessary Child elements to it.

Step 10: Open the Solution Window in Orchestration View and add the necessary Messages items and select appropriate Message Types (i.e. InputSchema /OutPutSchema /SAPRequest /SAPResponse)

-      InputMessage:

-      OutputMessage:

-      RequestMessage:

-ResponseMessage:

Step 11: Add necessary Ports/Port Types as follows:

-      Input parameter port (One Way Receive Port Type/Receiving Messages) - ParamReceivePort

-      SAP Request/Response Port (Request Response Port Type/Sending a Request and Receiving a Response) – SAPRequestResponse, N.B. Sap Request response port type will be created while importing the WSDL. So, you need to select existing port type in this case.

-      Output file port (One Way Send Port Type/Sending Messages) – WriteToFilePort

Step 12: Assign corresponding Message Types/Operations to ReceiveInput, SendRequest, ReceiveRequest and SendOutput. You will see that the Ports and Message Shapes are now connected.

Step 13: Update Message Constructed for 2 Transform Shapes:

Step 14: Click on first Transform Shape (i.e InputToRequest) of Construct Message shape (TransformFromXMLInputToSAPRequest) and select Imput and Output Messages as follows. It is being used to transform Input Message to a SAP Request Message. It will create a Map (i.e BizTalk.SAIF.InputToSAP) and open it in design mode.

Step 15: Define the first Mapping from Input Parameter to SAP Request. To do that Add Input File Schema (i.e. InputSchema) in the Source Schema pan and add SAP Request Schema (i.e. Z_I_MIA_LOC_LIST) in the destination schema pan and link associated elements on both sides

Step 16: Click on first Transform Shape (i.e ResponseToOutput) of Construct Message shape (TransformFromSAPResponseToOuput) and select Imput and Output Messages as follows. It is being used to transform SAP Response Message to Output Message. It will create a Map (i.e BizTalk.SAIF.SAPToFileMap) and open it in design mode.

Step 17: Define the second mapping (i.e BizTalk.SAIF.SAPToFileMap) from SAP Response to Output. To do that add SAP Response Schema (i.e. Z_I_MIA_LOC_LISTResponse) in the source schema pan and add Output File Schema (i.e. OutputSchema) in the Destination Schema pan and link associated elements on both sides:

Step 18: Now, the orchestration is complete and ready to deploy. Now, we need to add application name/BizTalk Server name in the Deployment tab.

Step 19: Add a key file to make the assembly strongly typed.

Step 20: Now deploy the solution to BizTalk server. We need to open up BizTalk administration console and configure the BizTalk application that we have just deployed.

Step 21: Create a Receive port to receive input parameter file.

-      Right click on Receive ports and select New->One-Way Receive Port

-      Give it a name (ParamReceivePort)

-      Click on Receive Locations->New

-      Enter Receive Location Name (i.e. ParamReceivePortLocation), Type as FILE and Receive Pipeline as XML Receive.

-      Click on Configure and select Receive Folder location and click "OK" and "OK" again to go back to Receive Port configuration

-      Click on Inbound Maps and select the Input Schema

 

Step 22: Create a Send port to send request to SAP and get response back from SAP as well. Select "Static Solicit-Response Send Port" in this case.

-      Give it a name (i.e. SAPRequestResponsePort)

-      Select Type as WCF-Custom, Send Pipeline as XML Transmit and Receive Pipeline as XML Receive

-      Click "Configure" button to configure WCF-Custom

-      Enter URI and SOAP action header from the imported WSDL file for the SAP RFC. You will get it almost towards the end of the file

-      Click on Binding tab and select "Basic" as Client Credential type

-      Increase incoming message size (if needed) by clicking on BasicHttpBindingElemtent->maxReceiveMessageSize

-      Enter SAP User ID and Password in the Credentials tab and click "OK"

-      Then click on Filters to subscribe to Receive Port. This is necessary to read the input parameter file from Receive Port. Enter BTS.ReceivePortName == ParamReceivePort (i.e. the Receive Port Name)

-      Click "OK" to save the SAP Request/Response port configuration

Step 23: Create a Send port to receive input parameter file.

-      Right click on Send ports and select New-> Static One-Way Send Port

-      Give it a name (WriteToFilePort), Type as FILE and Send Pipeline as XML Transmit.

 

-      Click on Configure and select Send Folder location and click "OK" and "OK" again to go back to Send Port configuration

-      Click on Inbound Maps and select the Input Schema

-      Click on Filters and add BTS.SPName == SAPRequestResponsePort. This step is necessary to add a subscription to SAPRequestResponsePort to get the SAP Response into the Output port

Step 24: Now we are all set. We just have to configure the BizTalk application and select Host Instances and assign the Physical ports to Orchestration ports. So, right click on the application and select "Configure" and select corresponding items from dropdowns.

Step 25: You can generate the "Input Schema" file from Visual Studio by selecting "Generate Instance".

Step 26. Update the InputSchema file with required parameters and drop it into the Receive Location and you will see a new file with GUID has been created in to the Send Location.

 

VOILA !!!