1/27/2016 4:12:12 PM

Below the detailed step will give connectivity between SAP to BizTalk.

Step 1) Define Logical System

IDoc Interface / Application Link Enabling (ALE)->Basic Settings->Logical Systems->Define Logical System

Think carefully about the effect of your changes. Due to logical dependencies between client-specific Customizing and applications data on the one hand and cross-client Customizing data on the other hand, changing or deleting cross-client data could result in inconsistencies.

Therefore such changes should be carefully planned and coordinated, taking all the clients in the system into consideration.

Click New Entries(F5)

Click Save

Now system will ask Transport Request(Workbench request) to save the logical system

Step 2) Create RFC Destinations

Goto Transaction SM59

Fill the necessary details which is marked in yellow

Program ID

With an SAP gateway, an RFC server program can be registered under this ID and then wait for RFC calls from different SAP systems. The registered server program thus no longer has to be started locally by an SAP instance (applications server, gateway or SAPgui) or via remote shell. You must maintain the specifications made via the SAP Gateway (host name and service) if registration is not being made via the gateway of the current applications server.

The program ID or host name and service of the SAP gateway in this entry must match the registration parameters (through RfcAccept).

Select Unicode tab

When you perform the Unicode test, the external RFC server program may terminate if it is a non-Unicode RFC server program, and the Unicode setting is used in transaction SM59. If the program terminates, register it again with the setting Non-Unicode.

If you perform the Unicode test with the setting Non-Unicode, an exception is raised on the page of the external RFC server program (JCo, .Net, and JRFC). In transaction SM59, change this setting from Non-Unicode to Unicode and perform the Unicode test again.

Once you have performed the Unicode test and the target system is Unicode-compliant, you can activate the Unicode setting.

Click on save(SM59)

Note : Connection test can be done when the program ID is configured in BizTalk system.

Step 3) Maintenance of Distribution Model

Goto transaction BD64

View of distribution model: The distribution model defines how logical systems exchange messages:

Which messages flow between which systems?
Which data contents are exchanged between the systems?Sender

Due to security reason only step by step is given below

Click edit button

Model views->Click Create model view button and save

Expand the Model view and add respective message types

Sender(Created for SAP): In Application Link Enabling, the name of the logical source system for exchanging messages. For distributing via message types and asynchronous object names this system sends IDocs. In the case of synchronous method calls this logical system is the client that requests the execution of a method.

Receiver(Created in Step 2): In Application Link Enabling, the name of the logical target system for exchanging messages. When data is distributed using message types and asynchronous object methods, this is the system that receives IDocs. When synchronous method calls are used, this logical system is the server where the method is executed.

Message type: An IDoc type can be implemented for various "logical" messages; one message can also be assigned to different IDoc types (m:n relationship).     

The message is defined by the values for message type (required), message code (optional) and message function (optional). These three fields belong to the key fields in the partner profiles, which are used, for example, to determine inbound processing. If the 'Message type' field is not maintained (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface uses the value from STDMES (EDI message type).

If possible, the descriptions of the message type should be linked to the corresponding EDI message type.

Click Save button

Step 4) Generate Partner profile

Fill the Model view and partner system then execute(F8)

Now Port and Outbound parameter will be created automatically.

Step 5) BizTalk configuration

a) Login to BizTalk admin console

b) Open the project which you have compiled

c) Click Properties->General:Give the program ID which is created in SAP Step 2(PI_SAP05)

d) Enable the receive location

Step 6) Connection test in SAP

Goto transaction SM59 and do the Connection test.

Again can perform the Unicode test

Step 7) Create filter in BizTalk

Click Filter property and add send port(file type)

Enable the send port

Step 8) Final step

Trigger IDoc from SAP

Then click the BizTalk file folder for the IDoc xml file generated

You can check the active connection in SAP using transaction SMGW.

I hope now you can configure end to end connectivity between SAP and BizTalk. Please post your doubts if you have.

If you like this blog, please share (Facebook/LinkedIn/Google+) to click below links so it will reach to others.


  • AleksandrSa -4/22/2016 11:18:43 AM