Message Detail using CSV file (SQL Based Loading) as Example

This provides an example of enabling MessageDetail for an InboundInterface with a Sql Loader processor.

  1. Create an inbound interface for format type CSV. Configure the Processor as "Sql Loader". Specify the configuration details for this processor.

    images/download/attachments/144836170/message_detail_sql_loader-version-1-modificationdate-1645137965000-api-v2.png
  2. Provide SQL statements that will process the data and load the data. Make sure you include a SELECT query to return the validation errors, as these will be used by the MessageDetail framework to generate error records:

    images/download/attachments/144836170/message_detail_sql_error_format-version-1-modificationdate-1645137996000-api-v2.png
  3. Add entries to ExternalReference with the following content:

    #* Ref Type,* External Value, Local Value, Description
    PLT.MessageDetail:Enable,100~inbox/CSV~ZBKS.EnterpriseLoad_Sql~1.0,ErrorRecordsOnly,Message Detail enabled for error records only
  4. Similar to the Default Model CSV Processor, this will capture ErrorRecordsOnly/AllRecords as specified in ExternalReference.
    images/download/attachments/144836170/message_detail_sql_based_interface_menu-version-1-modificationdate-1645137975000-api-v2.png
    images/download/attachments/144836170/message_detail_sql_based_interface_search_report-version-1-modificationdate-1645137982000-api-v2.png

    Message Detail will not capture details for “Primary Ref Type” and “Primary Ref Number” if inbound interface processor is sql loader not model-based processor.