|
BC2XI™ will generate, as output from the service, a number of components and related documentation. Each of the generated components will then need to be individually imported into the target XI. Currently SAP does not provide a programmable interface for uploading full XI projects (apart from the ones generated within XI). This feature will be added if and when SAP releases such an interface.
OverviewBelow is a list of items that are delivered by the BC2XI tool. These components are guaranteed to be delivered. The headers for each section reflect the relationship between the source and destination objects. BC Record --> XI DatatypeFull conversion from BC records to XI datatypes. Standard RFC and IDOC based datatypes will only be converted for referential purposes, and should always be imported from the target SAP system. The record reference model will be reflected in the datatype model. Some extra intermediate datatypes may be generated, depending on the complexity of the project flow and mappings. BC MAP --> XI Mappings- Support for 1:1 mappings
- Support for M:1 mappings
- Support for built-in BC java mappings
- Support for BC graphical mappings
- Support for BC DCP template mappings
For each BC Map there is an option during the migration process to select whether the corresponding XI mapping should be generated as a Java, XSL, or Graphical mapping. This may however limited by the content of the mapping, which in some cases will limit the choice to one or two of the options. BC Custom Java Service --> XI (Java, XSL or Graphical) MappingAll Java Mappings are supported as long as: - They contain transferrable functionality
- Any third party libraries that have been used are compatible with XI
- All code is allowed to be used in a non-BC environment (licensing etc.)
Any custom BC Java services which contain unexpected structures will be flagged by the first stages in the service and need to be resolved manually before being able to continue with the process. BC Flow --> XI BPMBC Flow elements will be converted to corresponding XI BPM elements. If a BC Flow has references to another flow then these two flows will be combined and implemented as a single flow in XI. DocumentationBC2XI™ will generate supporting documentation along with the XI components. The documentation will contain information regarding installation of the generated components, as well as other manual steps required in XI for the project migration. The documentation will also contain information regarding the relationship between the generated components and the corresponding BC components with some short descriptions regarding the conversion process. Note that this documention is not aimed to cover all XI areas that are required for a full migration to take place, but is mainly focused on getting the generated components installed and running.
ExclusionsThe information above is for indicative purposes only. An exact list of what is guaranteed by the service will be provided individually for each project after it has been run through the analysis phase in the BC2XI™ service. This statement overrides any other statement made in this document. No 3rd party BC services will be automatically translated unless specifically mentioned in this document. There are a number of BC features which should not be introduced into XI. For example, XI has it's own built-in logging model; hence, any logging related functionality in BC would need to be rebuilt for XI. |