Contract Management interfaces
- The name, description, and method for testing for each interface.
- The name of the CSV file, if applicable.
If there is only a CSV input file and no database input (business class), then there is no maintenance form for the input file. Maintenance must be done on the CSV file and the interface reprocessed.
- The business class (ISD File), which is the error/interface file where data is stored if you have errors. In some cases, the business class (ISD file) is also the file into which the data is initially interfaced.
- Where you go to perform maintenance after the interface is run.
- The Results menu item.
Interface | CSV | Business class (ISD file) | Maintenance | Results |
---|---|---|---|---|
Contract Interface No batch interface, this delivers Contract Import files to Contract. |
n/a | ContractImport ContractLineImport ContractImportTier ContractImportTierQualCode ContractImportTierQualifier ContractLineImportTierCost |
Contract Interface | n/a |
GPO Interface Contracts | n/a | ContractGPOHeader ContractGPOCategory ContractGPOTerm ContractGPOMembership ContractGPOParticipant ContractGPODistributor ContractGPOItem ContractGPOTier ContractGPOProductCategory ContractGPOProductSubcategory ContractGPOSupplier |
Supplier Mapping and Processing Member Mapping and Processing |
n/a |
The input file for Contract Interface is typically received from a manufacturer or distributor in the form of an Excel spreadsheet. You upload this using ISD, and that upload populates the various Import business classes that are listed. Any corrections to the data can be done in the maintenance form that is listed.
The input file for GPO Interface Contracts is typically received from a GPO in the form of an Excel spreadsheet. You upload this using database import tools, and that upload populates the various import business classes that are listed.