Correcting Failures

When a package is successfully imported, information stored in the interface tables is not deleted, and no additional action is required. The package can be viewed and processed using Deployment Management.

For packages and package lines that fail to import, corrective actions are required. The first step is examining the audit report from the open interface program to identify the failed records and the specific reasons for each failure.

Depending on the reasons, it may be necessary to correct the problem through a variety of means. Some failure might occur due to a mapping problem between the source data and existing data.

Note: The source data might use a project name that does not exist in Deployment Management. Corrective measures for this specific problem would include adding the specific project in Deployment Management, or mapping the source project to a project name that already exists in Deployment Management.

Other failures might be due to missing required information that cannot be defaulted.

Note: Package lines require an object type. If the object type columns were left blank for records in the package lines interface table, the records will fail validation. To correct this, the custom program or procedure that inserts records into the interface table needs to be modified to include this required data.

Failures could occur due to other configuration and mapping problems in either the source or in Deployment Management, or could be the result of errors in the custom loading program.

Note: During initial implementation of the open interface, the mapping between the third-party source and Deployment Management should be thoroughly reviewed and the load programs thoroughly tested.

Additionally, it is good practice to monitor executions of the open interface and periodically monitor that the desired data is being imported into Deployment Management.