General 

1. How is BC2XI™ priced?

2. What does a project mean in "priced per BC project"?

3. What is the scope of a project?

4. What areas of the migration are always performed manually? 

5. Which BC components are not covered by BC2XI™? 

General  

1. How is BC2XI™ priced?

BC2XI™ is priced per Business Connector (BC) project.  Each project will be individually priced based on the complexity of the project.  Contact SISU for assistance with project-specific pricing.

2. What does a project mean in "priced per BC project"?

A SAP Business Connector (BC) flow equals a BC2XI™ conversion project.  The BC flow includes the main process logic, mappings between message structures and conversions between message fields.  If one BC project export file contains more than one flow, then the main BC process flow can be chosen during the conversion process inside the BC2XI™ flow. A main flow can refer to sub-flows, but only one flow can be defined as the main flow per project.

3. What is the scope of a project?  

The scope of a BC2XI™ conversion project is to convert SAP BC components to corresponding SAP XI components.  For example- BC records (message structures) to XI data types, BC mappings to corresponding SAP XI mappings, and BC process flow to a corresponding XI integration process. The ultimate goal is to save time and avoid human error during the conversion from BC to XI.  Time savings can be up to 80% depending on the structure of the BC project.  It is important to notice that deliverables of the BC2XI™ conversion can also be utilized for modified migrations if needed.  For example, sometimes part of the business logic may need to be changed between BC and XI, meaning that only part of the output from the migration is directly relevant.  This is supported by providing access to individual components at the end of the migration process, as well as limited capability to modify the process during the migration steps. 

4. What areas of the migration are always performed manually?

All components which the BC2XI™ conversion delivers need to be imported into XI manually using the XI import feature.  These include data types, mappings and integration processes.  A conversion document is generated to describe the manual steps that need to be followed in the XI Repository.  All communication configurations must be separately done in the XI Directory.  (Whereas in SAP BC the message processing and interaction with backend systems are implemented in the BC flow, in contrast in XI the integration processes and communication configurations are separated between the XI Repository and XI Directory).

5. Which BC components are not covered by BC2XI™?

Some BC specific features such as logging and error handling, which are replaced by new, enhanced functionality in XI, are not covered by the migration. Also, some individual features might not be supported, but these will be listed at the beginning of the migration process during the project analysis stage.  SISU has adopted an aggressive approach to building new functionality into BC2XI as features which cannot currently be converted, are found.