Correcting Failures

When a request is successfully imported, information stored in the interface tables is not deleted, and no additional action is required. It is possible to view and process the request using Demand Management.

Note: During the initial implementation of the open interface, the mapping between the third-party source and PPM should be thoroughly reviewed and the load programs thoroughly tested in a testing instance.

It is good practice to monitor executions of the open interface and periodically monitor the import of desired data into Demand Management.

For users that fail to import, you should:

Examine the audit report from the open interface report.
Identify the failed records and the specific reasons for each failure.
(Optional) Depending on the reasons, correct the problem as necessary.

Failures may be due to:

A mapping problem between the source data and existing Demand Management data.

You may need to add the specific project in Demand Management, or map the source project to a project name that already exists in Demand Management.
Missing information that cannot be defaulted.

For example, requests require a request type. If the request type columns are left blank for records in the requests 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.
A large volume of data being imported.

If you suspect that this is the problem, confirm this hypothesis by importing a smaller number of records, then checking to see if the error message persists.
Other configuration and mapping problems in either the source or in Demand Management, or could be the result of errors in the custom loading program.