Migration from SAP BC To SAP P.I

[Former Member]

HI Experts ,

I am required to do migration from SAP BC to SAP P.I. I would require the following Info/Help from you as i have not worked on such scenario before this!

1) What kind of challenges can be faced during migration from BC to XI?

2) What is the best practise for doing the same?

3) Can you share some scenario from where i can have some idea how to do migration?

4) Generally how much time it takes in migration activity if ther are not much interfaces involved in it?

Would appreciate your valuable inputs on the same!

I have read How to guide docs on how to do migration from BC to XI but not convinced with the content

Regards

Saras Jain

[prateek]

I had done one such migration for one of our clients.

<i>1) What kind of challenges can be faced during migration from BC to XI?</i>

The standard functions of BC are not supported by XI.

The Java mapping code cant be directly transferred to XI.

Handling of flow service dependency is a huge task to handle

<i>2) What is the best practise for doing the same?</i>

Either go for how to guide provided by SAP for BC to XI Migration or directly go for using tool available in market.

<i>3) Can you share some scenario from where i can have some idea how to do migration?</i>

I dont think that would be possible for any1. But example can be provided.

<i>4) Generally how much time it takes in migration activity if ther are not much interfaces involved in it?</i>

That depends which functionality of BC u r using. For a single scenaio with flow service and without java mapping, the time taken would be 1 week

Regards,

Prateek

[Former Member]

hey Prateek ,

Thanx for your reply !

Even an example would do !

I would really appreciate if you can explain with an example!

[aashish_sinha]

Hi Prateek,

>>>>Can you share some scenario from where i can have some idea how to do migration?

I dont think that would be possible for any1. But example can be provided

I have already provided a scenario here and i have my PPT for this purpose. I was not able to paste pictures. I worked extensively on BC and webMethods and this was my first project when i joined XI , to migrate BC flow services to XI/PI. and then i created the workflow. In other expects i am agreec with you rather in every way :)...

regards

Aashish Sinha

[former_member184619]

Hi Saras,

however i haven't done it practically...

1. the challanges can be ... Complex mapping and all other mapping other than graphical mapping, Presence of large, complex data types, custom Java components, IDOC interfaces

3. check the case studies in following link:

http://sisusoftware.com/website/

4. It depends upon complexity of scenario.... also mentioned in case studies above..

check this also:

http://sisusoftware.com/website/index.php?option=com_content&task=view&id=18&Itemid=41

Sachin

[aashish_sinha]

Hi Saras,

I am giving you an example senario and a how to do all the steps and why it needed. if you need more information just mail me i'll give you the concerned PDF.

Scenario

SAP Business Connector enables data exchange between an SAP system and

external systems using HTTP and e-mail. SAP Exchange Infrastructure (SAP XI)

replaces SAP Business Connector (SAP BC).

We distinguish between standard scenarios (that do not contain customer-specific

development) and individual scenarios (that do contain services or mappings created

by the customer). The following sections describe how to migrate both types of

scenarios to SAP XI.

Scenario 1 (IDoc – HTTP, HTTP – IDoc)

An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to

XML. It is sent to an external business partner by using HTTP.

An external business partner sends an XML document by using HTTP to SAP BC or

to SAP XI. The document is converted to an IDoc and sent to a connected SAP

system in the internal system landscape.

Scenario 2 (IDoc – Mail, Mail – IDoc)

An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to

XML. It is sent to an external business partner as an e-mail.

An external business partner sends an e-mail to SAP BC or to SAP XI. The

document is converted to an IDoc and sent to a connected SAP system in the

internal system landscape.

Flow Services

Flow services are services that are written in the proprietary graphical-based flow

language of SAP BC.

Java Services

Java services are services that are written in the Java language.

There are several platforms that support Java, including SAP XI. However, the data

model used in the Java services in SAP BC is proprietary.

Stylesheet Transformations

Stylesheet transformations are often used for mapping purposes. They take an XML

document as input, convert it according to rules defined in the stylesheet, which is

also an XML document, and produce an XML document as output.

The XML Stylesheet Transformation Language (XSLT) was defined by W3C (World

Wide Web Consortium), the consortium that defines most of the common standards in modern internet communication, such as HTML and SOAP.

SAP NetWeaver is the open integration and application platform from SAP. With

NetWeaver ’04, there is a significant overlap between the functions of SAP

NetWeaver and SAP BC. Many functions provided by SAP BC are offered by SAP XI

as part of SAP NetWeaver, for example, conversion of an IDoc to an XML message,

mapping, routing, and adapters to connect to a large number of third-party back-end

systems. SAP BC is therefore no longer needed. New or updated SAP solutions are

based on SAP NetWeaver. Customers looking for a strategic integration solution for

the complete application landscape should therefore now favor SAP NetWeaver.

The last version of SAP BC was SAP BC 4.7, which was released in June 2003. SAP

BC has not been developed further since this release. SAP BC is not released for

any further platforms (such as Windows 2003) and does not support any further JDK

versions, including the current version (Version 1.4).

For information about the supported SAP BC versions, JDKs, and operating systems,

see SAP Note 309834. For information about the support and maintenance strategy

for SAP BC, see SAP Note 571530. Customers who still use SAP BC need to be

aware of the following:

• A solution based on SAP BC cannot be a strategic, long-term solution.

• A solution based on SAP BC is based on technology that was implemented in

2003 and that is no longer further developed.

• SAP BC is supported on limited platforms and for limited JDKs only. Vendor

support for some of these platforms and JDK versions will soon be

discontinued.

SAP BC and SAP NetWeaver are based on different technologies: SAP BC is based

on webMethods’ proprietary Integration Server, whereas SAP NetWeaver is based

on open standards, such as BPEL4WS (business process execution language for

web services). Therefore, only parts of an SAP BC implementation, such as XSLT

mappings, can be migrated to a solution based on SAP NetWeaver. Any custom

programming based on SAP BC, such as SAP BC flow language, is unlikely to be

reusable in the SAP NetWeaver context.

Purpose of this Migration Guide

The purpose of this migration guide is to provide scenario-based descriptions of the

migration from a company’s system landscape that uses SAP BC to exchange

documents with business partners, to a system landscape that uses SAP XI instead.

This migration guide outlines, for certain scenarios, the individual steps a company

has to take to replace an existing SAP BC implementation with SAP XI.

The basic steps in the back-end systems are:

• Defining the logical systems

• Maintaining the ALE distribution model

• Maintaining partner profiles and EDI ports

• Maintaining RFC destinations

The basic steps in the SAP XI system are:

• Maintaining the System Landscape Directory

• Configuring the IDoc adapter

• Maintaining the receiver determinations, interface determinations, and

interface agreements

• Maintaining the communication channels

The type of scenario to migrate typically has an impact on the communication channels only.

Scenario 1 IDoc/HTTP

IDoc – HTTP Using SAP BC

Within the system landscape of a company, an SAP system sends an IDoc

asynchronously to SAP BC. SAP BC converts the IDoc into a standard IDoc XML

document. The fields of the IDoc are not modified, that is, the conversion does not

involve any mapping of source fields to target fields. After conversion, SAP BC uses

HTTP to send the XML document synchronously to an external URL of a business

partner.

System Landscape

• An SAP system and SAP BC are installed within the same system landscape

of a company.

• The following information is defined in the SAP system to allow data

exchange between the SAP system and SAP BC:

o An RFC destination and a logical system for SAP BC

o The distribution model is maintained, if necessary

• The following information is defined in SAP BC:

o An SAP server with an alias is defined. For this SAP server, the

information that the SAP BC requires to connect to the SAP system is

specified.

o A listener is configured to listen to requests from the SAP system.

o A routing rule with the transport type “XML” is configured for the

specific sender, receiver, and message type. The routing rule

determines how a message is to be routed and where it is to be routed

to. The scenario described does not use an ACL, (Access Control List

to restrict execution permissions for this routing rule) or pre-processing

or post-processing SAP BC services.

4.2 IDoc – HTTP Using SAP XI

Check the prerequisites described above under Prerequisites for Standard

Scenarios.

The IDoc adapter is used to receive an IDoc from an SAP back-end system and

convert it to XML.

The adapter used to post this XML to an external destination is the plain HTTP

adapter.

To set up the communication channel, perform the following steps:

1. Locate the routing rule in SAP

Business Connector.

In the Administration View, choose

Adapters – Routing to navigate to

Routing Rules.

2. Select the details of the relevant routing rule.

To display the details, choose the green triangle (Edit).

Transport is typically set to XML and a URL is specified. You can use this

URL in your SAP XI settings.In some cases, Transport is set to

B2B Service and the parameters Server Alias, Folder and Service

exist. This is the same as when Transport is set to XML and has the

URL http://<serverhost>:<port>/invoke/<folder>/<service>.

You can find <serverhost> and<port> in the definition of the

remote server under Settings –>Remote Server in the Administration

View.

3. Set up the communication channel in the Integration Directory using the parameters from the SAP BC routing rule.

Use the following settings:

• Adapter Type: HTTP Receiver

• Transport Protocol: HTTP 1.0

• Message Protocol: XI Payload in HTTP Body

• Adapter Engine: Integration Server

• Addressing Type: URL Address

• Target Host, Service Number,and Path need to be set in accordance with the SAP BC routing rule. HTTP Proxy Host and HTTP Proxy

Port can be set if required.All other parameters have no corresponding values in SAP BC and should be set to their default values.

regards

Aashish Sinha

P : Reward points if helpful