Prior to release 12.1 there was no supported way to import contracts into the EBS Service Contracts application - there were no public APIs nor contract load programs provided. From release 12.1 onwards the 'Service Contracts Import Program' is provided to load service contracts into the application. The Service Contracts Import functionality is explained in How to Use the Service Contracts Import Program - Scope and Limitations (Doc ID 1057242.1). This note includes an attached document which explains the program architecture, shows the Entity Relationship Diagram and details the interface table definitions.
The Import program takes data from the interface tables listed below and populates the contracts schema tables:
OKS_USAGE_COUNTERS_INTERFACE
OKS_SALES_CREDITS_INTERFACE
OKS_NOTES_INTERFACE
OKS_LINES_INTERFACE
OKS_HEADERS_INTERFACE
OKS_COVERED_LEVELS_INTERFACE
These interface tables must be loaded via a custom load program.
The Service Contracts Import concurrent request is then submitted to create contracts from this legacy data. The parameters to run the Import program are:
| Parameter | Description |
| Mode | Validate only, Import |
| Batch Number | Batch_Id (unique id populated into the OKS_HEADERS_INTERFACE table) |
| Number of Workers | Number of workers required (these are spawned as separate sub-requests) |
| Commit size | Represents number of successfully processed contracts commited to database |
The program spawns sub-requests for the import worker(s) and the 'Service Contracts Import Report'. The data is validated prior to import and into the Contracts tables and will report errors in the Service Contracts Import Report program output file (Import Execution Report). Troubleshooting tips are provided in R12.1 - Common Service Contract Import Errors (Doc ID 762545.1); this document lists some, but not all, import errors. The document will be updated over time. Additional help is given in Debugging Tip for Service Contracts Import Errors (Doc ID 971426.1).
After you successfully import contracts, you can purge the records from the interface tables by running the Service Contracts Import Purge concurrent program. Note that there is no supported way to mass delete data from the Contracts schema tables once they are populated, so data loaded by the Import program must be fully tested and verified before the program is run to load data into a Production system.
A Service Contracts Import Test program has been provided which will take an existing contract in the application and load the interface tables using the data from that contract. This can be used as an example for guidance on how to load the interface tables. The Test program functionality is explained in How to Use the Service Contracts Test Import Program Provided in Release 12.1 (Doc ID 761209.1). Note that the Test program has some limitations which do not apply to the full Import program and is not a supported program, it is simply a testing tool.