Running the PPAIMPORT cron task
After the PPAIMPORT cron task instance is enabled, the cron task will execute at the scheduled times, convert the spreadsheet or CSV files that were created by the PPA and ESMT tools into XML files, and then pass those XML files on to the Integration Framework which handles the import into the License application.
The cron task will perform some processing steps on each record
in the CSV file while converting the file to an XML file.
- Checks if the CSV file has the required columns defined and that
each row has a value specified.
Column Name Required/Optional Default Value PARTNUMBER REQUIRED STARTDATE REQUIRED CAPACITY REQUIRED DESCRIPTION OPTIONAL COMPPERIOD OPTIONAL LICENSENAME OPTIONAL TERMINATEDATE OPTIONAL SERIALNUMBER OPTIONAL LICENSENUM OPTIONAL PLUSPCUSTOMER OPTIONAL GLACCOUNT OPTIONAL RESPARTY OPTIONAL LICTYPE OPTIONAL GENERIC PLATFORMBASE OPTIONAL DISTRIBUTED SOURCE OPTIONAL PPA LICSCOPE OPTIONAL ENTERPRISE LICTERM OPTIONAL INSTALLED CREATEDBY OPTIONAL Run as User CHANGEBY OPTIONAL Run as User STATUS - Performs a lookup on the part number provided to get the software product, charge type and sub capacity setting.
- Checks if a value for LICENSENUM is provided. If there is, it will be used. If not, then it checks to see if there are any licenses that exist which have the same values for ORGID, PARTNUMBER, STARTDATE, TERMINATEDATE, CAPACITY and SOURCE. If so, then the LICENSENUM retrieved will be used. If not, then a value for LICENSENUM will be generated.
- If a value for GLACCOUNT is provided, it will look up the associated GLORDER value. If the GLACCOUNT doesn't match an existing glaccount on the system, then the row is skipped.
- If a record starts with either a single # or //, it is considered a comment and is ignored.
- If an optional column does not have a value specified in the file, the default value is specified.
- If there is no default value and no value specified, the column will be ignored for that particular record.
When each record in the CSV file has been processed, an XML file is created in the same directory as the CSV file, as long as there are any valid rows to process. Rows can be skipped if the GLACCOUNT specified is incorrect, or the partnumber does not match an existing software product in the system. This XML file is passed on to the Integration Framework to perform the actual import into the License application.