3.2.1.3 Creating the Data File

After the Data File Specification is defined, follow the below mentioned guidelines to prepare the Data Files:

  • Columns to be included in the Data File must be as per the Data File Specification.
  • Name of the Data File can be user defined. The following example gives an idea of what the Data File Name can be:
    • Data File Specification Name is “Asset.dat”
    • The As of Date is 06-July-2022
    • Name of file uploaded to object store can be like “input_20220706_loanasset.dat” or “input_20220706_asset.dat”

    The prefix (input_yyyymmdd) is mandatory in actual file name when uploaded to Object Store but is not required while you enter the name in the Task Parameters UI against the Data File Name.

  • Unique Data Validations:
    • Instrument Data Files: Account Numbers must be unique across the data files for a single As of Date.
    • Management Ledger Data Files: The combination of AS_OF_DATE, CONSOLIDATION_CODE, ISO_CURRENCY_CD, all seeded and placeholder Key Processing Dimensions (KPDs), and DATA_SOURCE_CODE must be unique across the data files for a single As of Date. This allows loading logically identical Management Ledger data more than once for the same As of Date, provided a unique DATA_SOURCE_CODE value is used for each load. Beginning with release 26C Release, DATA_SOURCE_CODE is a mandatory (NOT NULL) column in all six Stage Management Ledger tables.
    • Transaction Summary Data Files: The combination of Account Numbers and KPDs must be unique across the data files for a single As of Date.
  • Permitted Delimiters are comma (,) and pipeline (|).
  • File Format: Due to inherent differences in plain text file line endings between UNIX (LF) and Windows/DOS (CRLF), all plain-text Data Files must be converted to UNIX format before uploading into PBSM, regardless of the file extension (.txt/.csv/.dat, etc.). If the manifest option is enabled in the Data File Specification, it is recommended that the manifest file also be converted to UNIX format.

    Note:

    • If the .csv and manifest files are packaged into a .zip, convert both files to UNIX format before creating the .zip archive.
    • While generating the MD5 checksum of the datafile for inclusion in the manifest, first perform the UNIX format conversion, then generate the MD5 checksum.
  • Data Validations:
    • Number fields: only numbers and dot (.) are allowed.
    • Description fields: comma (,) pipeline (|), single quotes (‘’), and double quotes (“ “) are not supported.
    • Any nullable fields which are mapped in the Data File Specification definitions should not skipped in the Data File.
    • The Data Source column in all Stage Management Ledger and Processing Management Ledger tables defaults to -1. You can therefore choose not to include the Data Source column in the input Data File / Data File Specification.
    • The column order in the Data File should be in sync with the order defined in the Data File Specification definition.
    • Field Enclosures: Only double quotes (“”) are considered as Field Enclosures.

See the following sample files for your reference:

For more information about the data required by the Profitability and Balance Sheet Management Cloud Services, see the Data Requirements available at the Doc ID: 2869409.1.

Parent topic: Data File Specification