After running, the CDP process returns a set of attributes called the Parser Repository (PREPOS). It also generates return codes and status codes that identify the conditions that were found for each parsed row.
- Parser Repository. After parsing, the Parser passes a comprehensive data block called the Parser Repository (PREPOS). The PREPOS contains parsed data including status codes, identification indicators and name information. The output schema determines which of these attributes are returned to the output.
- Return Codes and Status Codes. The Parser generates Return Codes and Status Codes to identify specific problems and conditions which occurred for each parsed row.
- PNP/BNP Confidence. PNP/BNP Confidence values provide you with detailed information about the personal and business input data.
- Mask Logic. Mask Logic Separation Statuses are produced from the token separation by logic.
- Process Report Files. You can also review the Debug file, exceptions file and statistics for information about the Parser process. See Viewing Process Report Files.
Note: The Parsing exceptions file includes the final masks for all records (pr_mask_final). A
Parsing Exception file is generated in the entity folder in the repository directory (for
example, C:/Program Files/Trillium Software/MBSW/17/.../metabase/repository_name/entity_id/
entity_id_parse_exceptions.txt).