Skip to main content

Automation component to create Preload and Postload reports in SKP ADMM



1 comment

  • Best answer
    Chris Dooyema

    For the automated preload reports, there are z-fields for stage ready, data ready, target ready, and business ready flags.  These are bit fields that are defaulted as '1' initially.  Then when one of the validation reports run, each key in the report will toggle the readiness flag to '0' depending on the report type that is executing (i.e. stage ready, data ready, target ready, business ready).  The zLegacy fields should be automatically included in the preload report.

    See the link below for more details on the different report types.

    For the automated postload reports, the target ZLOADED flag should be updated as a postload update step.  For the generated postload report, the preload value and the loaded value are presented together along with a technical comparison check (i.e. "match" vs "mismatch").  For the postload report automation to work, the passthrough views for each target must exist in the working database.  

    With the automated preload and postload reports generated, they can be enhanced to pull in additional data elements as needed.  For example, if there is a business requirement to present the text descriptions that go with a configured value, this will be a manual extension of the automated preload and/or postload report.  Passthrough views can be generated for the corresponding config description tables (ie. T134T, T005T, etc..) and incorporated into the preload and postload reports to bring in these description values.


Please sign in to leave a comment.