Overview of the Migration Concept and the Involved Components :
Conversion process without the SCA Studio
The process to perform the conversion process without the SCA Studio
consists of the following steps:
The process to perform the conversion process without the SCA Studio consists of the following steps:
1 Install and configure the conversion software on the SSA Baan IV and SSA ERPLN 6.1 environment.
2 Perform all the pre-conversion activities and steps, as described in the Data Conversion Guide.
3 Start the conversion process, as described in the Data Conversion Guide. The SSA Baan IV database tables are now extracted, transformed, and
dumped into plain ASCII files on the SSA Baan IV environment. Upon completion of the dumping process, the ASCII files are uploaded with
RDBMS high performance loaders into the SSA ERP LN 6.1 database.
4 Perform all the post-conversion activities and steps as described in the Data Conversion Guide
Conversion process with SCA Studio:
The process to perform the conversion process with the SCA Studio consists of the following steps:
1 Install and configure the conversion software on the SSA Baan IV and SSA ERPLN 6.1 environment.
2 Install and configure the SCA Studio and load the standard Logic Pack (rules) for the logic SSA Baan IVc4 SP15 to SSA ERPLN6.1a into the Studio.
- If the German Baan IVc4 extension CNT is in use, be sure that the corresponding Logic Pack (rules) will be uploaded into the SCA Studio, as well. Deliver the CNT rules from the standard 4c4-61a rules in the SCA Studio and perform a conversion build by means of the SCA Studio.
- If the German Baan IVc4 extension FBU is in use, be sure that the corresponding Logic Pack (rules) will be uploaded into the SCA Studio, as well. Deliver the FBU rules from the standard 4c4-61a rules in the SCA Studio and perform a conversion build by means of the SCA Studio.
3. Install and configure a Baan IV fat client, which is required to validate conversion logic and compile conversion objects by means of the SCA Studio.
4 Perform a conversion build in the SCA Studio. XML rules are now created locally, followed by a 3GL script generation on the Baan IVc4 environment,
and finally compile all the 3GL scripts into (obcdll) objects. This step is a single-process step if the Baan IV fat client is present.
5 Perform all the preconversion activities and steps, as described in the Data Conversion Guide.
6 Start the conversion process as described in the Data Conversion Guide. On the Baan IV environment, the Baan IV database tables are now extracted,
transformed, and dumped into plain ASCII files. Upon completion of the dumping process, the ASCII files are uploaded with RDBMS high-performance loaders into the ERP LN 6.1 database.
7 Perform all the post-conversion activities and steps, as described in the Data Conversion Guide.
Installation Sequence
Directory structure on the media
- Additional Files
- Documents
- Engine
- Logic Packs*
- Post Migration Logic
- Pre Migration Logic
- SCA2.1_Studio
SSA Baan IVc4 environment
1 Prerequisite:
PMC for SSA Baan IVc4 and Be sure that, for each package, the SSA ERP6.1a must be PMC update VRC is available in the completely configured before derived-from structure for the VRC you continue the installation derived-from structure for the VRC connected to your package combination.
2 SCA 2.0 Baan IV Engine Refer to the Installation Guide (U8350A US). VRC is bcB40_c4_cn24.
3 Import Engine Update Import the Engine Update software with the Import Data Dictionary (ttiex1285m000) session. Vrc (bcB40M_c4_cn24) and derivation(bcB40_c4_cn24) is handled automatically
4 Import Logic Base Import the Logic Base software with the Import Data Dictionary (ttiex1285m000) session. Vrc (bcB40_c4_ca20) and derivation (bcB40M_c4_cn24) is handled automatically
5 Import Logic Update
1. Create a new VRC bcB40M_c4_ca20.
2. Define directories for new vrc.
3. Derive this new VRC from bcB40_c4_ca20, the Logic Base.
4. Import the Logic Update software from the CD or the latest version on the support site into bcB40M_c4_ca20.
5.opy mcripts file from the CD or the latest version on the support site into the $BSE/application/ bcB40M_c4_ca20/obcdll directory.
C* Create Customization layer
1.eate a new VRC bcB40C_c4_ca20. Ca20 can also be replaced by any other custom code.
2 Define directories for new vrc.
3. Derive this new VRC from cB40M_c4_ca20, the Logic Update.
4. Create manually the obcdll directory $BSE/application/ bcB40C_c4_ca20/obcdll
6 Language Depend If no English language is installed on BaanIV, do the following:
1. Copy language dependant components (ttadv6200m000)
2. Copy language dependant components for help texts (ttadv6220m000)
7 Build the package combination. Make the customization migration VRC, bcB40C_c4_ca20, part of your production package combination and rebuild DD
3