Control Append FAQS

1. What is the Control Append strategy?
• The Control Append strategy is an enhanced version of the Append strategy. It inserts data into the target table but includes additional steps like error handling and flow control to ensure only valid data is inserted.
2. How is data handled in the Control Append strategy?
• Data is first loaded into a temporary integration table, where it is checked for errors using the Check Knowledge Module (CKM). Invalid data is removed, and the valid data is then inserted into the target table.
3. What is the role of the Check Knowledge Module (CKM) in the Control Append strategy?
• The CKM evaluates the data in the integration table against the constraints defined for the target table. It identifies erroneous records, moves them to an error table, and ensures only valid records remain in the integration table for insertion into the target.
4. Is the target table cleared before the data is inserted in the Control Append strategy?
• Yes, the target table can be cleared of all records before the new data is inserted. This step can be controlled by an option set by the designer of the mapping.
5. What happens to the invalid data in the Control Append strategy?
• Invalid data is removed from the integration table, and it is inserted into an error table ("E$") for further investigation or correction.
6. What is an integration table in the Control Append strategy?
• An integration table ("I$") is a temporary staging table used to hold the data before it is inserted into the target table. It allows for flow control, error checking, and transformation before the final insert.
7. How are errors recycled in the Control Append strategy?
• Error recycling allows previously rejected records (e.g., due to missing data) to be re-inserted into the flow. These records, once the issue is resolved (e.g., missing product IDs), can be processed in the next execution of the mapping.
8. How are previously rejected records reprocessed?
• Rejected records are retrieved from the error table and inserted into the integration table for reprocessing. The integration table is then passed through the CKM again to ensure data quality before inserting into the target.
9. What is the RECYCLE_ERRORS KM option?
• The RECYCLE_ERRORS KM option is used to control whether previously rejected records should be reprocessed in a subsequent mapping execution. It allows the recycling of errors for re-evaluation and integration.
10. Why would I use the Control Append strategy instead of the Append strategy?
• The Control Append strategy is useful when you need more control over the data flow, such as ensuring data integrity through error handling, validating the data against target table constraints, and recycling previously rejected records. If you simply need to insert data without validation or error handling, the basic Append strategy might suffice.
11. Can the Control Append strategy be used with remote data sources?
• Yes, the Control Append strategy can handle data from remote sources. The Loading Knowledge Module (LKM) will prepare loading tables for remote sources, and the integration process will work similarly to data from local sources.