The CIS template files define the linkage information between the IAConnect data associated with each invoice and the data fields in your Costpoint system. Header field information such as Vendor ID and Invoice Number as well as line detail information such as Quantity, Project, and Account are all pre-mapped to the correct data fields in Costpoint so that when a voucher transaction is posted, the systems know where to store the data.
The template files for the CP6 or CP7 PO are provided in the installation package. The template files are located in the folder [Costpoint Import Service Root]\bin\content. The CP6 PO Template files are located in a sub folder named Backward Compatibility CP 6. The CP7 PO Template files are located in a sub folder named Create PO Voucher.
The data is pulled from invoice keywords stored with the document and also from the GL Coding table named GLCodingData_CP. These data fields are then formatted into an XML file using the mapping in the template file using the defined placeholders. An example of a placeholder is defined as %%QUANTITY%%. It then gets placed into the XML file into a field such as <QTY>%%QUANTITY%%</QTY>.
The placeholder is replaced by the actual field from the OnBase keywords or table columns of the same name. For example, if there is a database column in the GLCodingData_CP table with the name QUANTITY, then the value from this column in the line record in this table is used to replace the placeholder in the template file resulting in the above template segment to be changed into <QTY>200</QTY>.
Similarly all the placeholders in the template files are replaced with actual values in the database or OnBase keywords to create the appropriate PO or AP Voucher XML file.
The following sample template file illustrates the basic construction of a template file by illustrating a part of the Costpoint PO structure, where the definition for the PO lines is defined. Actual files structures are much larger.
The following example includes sections from a sample CIS template file. These samples are provided as illustrations only. Because various configuration settings in these samples will vary from your actual solution, do not copy this information for use in a production environment.
<!--Result set '' Supported Operations(INSERT UPDATE DELETE SELECT )-->