Prerequisite Files

The following custom files and stored procedures files must be accessible to run the Import Subcontract PO Status Updates:

  • CSTPOINT.EXE: Costpoint executable
  • CPPMGRSV.EXE: Costpoint Process Server executable
  • AOPSCST.EXE: Subcontract PO Status Update Preprocessor application executable
  • AOPSCST.ORA: Oracle stored procedures for the Subcontract PO Status Update Preprocessor
  • AOPSCST.MSS: SQL Server stored procedures for the Subcontract PO Status Update Preprocessor

The program deletes the input file after processing.

Each Update Header input file record must have at least one Update Line input file record. Similarly, an Update Line input file record must have an associated Update Header input file record. Update Line records do not need to physically follow their corresponding Update Header input file record. A single header row is sufficient for multiple PO line rows associated with the same PO. This application uses the Status Update ID, PO, and Warehouse to determine which line records belong to which header record. Every row must end with a carriage return and a line feed.

If you are using a fixed-length Input file, you must fill every position in the file with the appropriate number of either characters or spaces for a given column before entering data in the next column. It is not necessary to zero fill numbers; you can use spaces to maintain the proper format. Numeric fields should be right justified; character fields should be left justified. Once you have entered the last character of meaningful data for the input file, you do not have to fill the remaining column lines with spaces.

For example, if the Subcontract PO Status Update Header Record Format's maximum line length (i.e., the entire input file) is a total of 51 characters and the last character of meaningful data is in position 38, you do not need to add the remaining 13 spaces. If the PO ID (beginning at position 33 on the input file) is only seven characters long, you must include the PO ID plus three additional spaces before entering the Progress Payment Request in position number 43.

Error File

The Error file is a suspense file that contains records that were not processed from the Input File due to errors. It has the same name as the Input File but with an .ERR extension. The error file should be in the same directory path as the input file. The error file is named "SCMMDDYY.ERR", where "MMDDYY" is the date on which the process was run. If that file already exists, the new errors will be appended to the file.

If you select the Do Not Produce an ASCII Error File check box before processing, the program will not create an error file.

The layout of the Error File is the same as the layout of the Input File. After you select the Process Input File or Process and print the report under the on toolbar, the application generates an error report if there is at least one set of header/line records with an error or warning message. If you select the Process Valid Records in the Error Handling group box before executing the upload process, the program will process input file sets without errors and will not process sets with errors. If you select the Process No Records, the program will process no rows if there is any error. In any case, records with warnings (not errors) will be processed. Even if you run the process without a trial run (and you select the Process Valid Records), the application processes all input file header/line sets that have no errors.