Once new BDoc types are created there might be certain changes that may be done to these BDoc types. While making these changes, if the table fields are deleted, the BDoc types have to be regenerated. After this, the entire generation process (transactions asci, smap and asc2) must be redone.

In standard BDoc instances, checks must be done to see whether there are any relevant segment fields correspondingly available in OLTP ERP. If found, the corresponding ERP keys must be checked in the temporary tables since primary keys for a segment are generated based on the ERP keys; the combination of ERP field values must be unique.

In customer BDocs, if the segments are not relevant to OLTP ERP, then the primary and foreign key values must be taken from the flat files. Alternatively, key values can be generated using the customer exits of the Structure Mapper.

KeyGen service is invoked automatically and fills the segments that has ERP keys.

In order to avoid the process of replication and realignment, certain changes must be done in the flow control so that data written in the consolidated database is not extracted and used by the replication and realignment engine.

During data download from the DBMS file to the ASCII file, the user can provide a condition (Select clause input field on the Table information screen) in order to get selective data into the ASCII files. This Select Clause is not parsed or validated (a limitation from the application end) and the user needs to ensure that the condition provided is valid. The user must provide the following format: WHERE <condition>. The application only ensures that the user has provided WHERE at the beginning of the Select Clause.