Subject: ERROR: File not in correct format for engine (X_CUSTOMISED_CODE.ECL_DATA_PART.DATA) in IFRS

[Musheer1]

Hello everyone,

I am encountering an error in our SAS Testing Environment while running a Credit Risk process, specifically within the IFRS 9 Solution framework.

The error points to an engine mismatch when accessing a partitioned data table.

1. Error Message & Log Context

The process fails at line 282 within a customized file include, with the following error:

ERROR: File X_CUSTOMISED_CODE.ECL_DATA_PART.DATA is not in the correct format for the given engine.

Relevant Log Snippets (Around the Error):

SAS

282        %include "E:\SASConfig\Lev1\AppData\SASIRM\fa.ifrs9.2020.10\irm\source\sas\X_Customised_Code\Load_Latest_Part_Table_ECL_Data_V1.sas";
... (Error occurs within the included file)
297        %irmc_refresh_lasr_schema_view(lasr_lib = &lasr_libref. ...

(The subsequent call to %irmc_refresh_lasr_schema_view suggests this process is heavily reliant on the LASR/CAS environment.)

2. Process Flow Context (PD Input Table Selection)

The failure is governed by a flow chart that executes the problematic include file when partitioned data is required:

• Condition: Macro variable &ECL_DATA_PART_REQUIRED = 'Y'.

• Action: Execute %include "Load_Latest_Part\_Table\_ECL\_Data\_V1.sas".

• Goal: This file is intended to access the partitioned dataset X_CUSTOMISED_CODE.ECL_DATA_PART to define the PD Input Table.

3. Current Hypothesis

The issue is an engine mismatch on the X_CUSTOMISED_CODE libref.

• The data table ECL_DATA_PART is likely stored in a format meant for the LASR or CAS engine.

• The LIBNAME X_CUSTOMISED_CODE definition is likely using a standard V9 (Base SAS) engine, which cannot read the specialized file format.

4. Need Help With

1. Confirming the correct LIBNAME definition for X_CUSTOMISED_CODE in a typical SAS IFRS 9 (IRM) installation that uses LASR/CAS data partitioning.

2. If the issue is not the libref, advice on how to inspect the contents and saving format of the ECL_DATA_PART file.

   

Thank you in advance for any assistance!

[Patrick · Accepted solution]

Suggest you move your question under Solutions/Risk and Fraud/SAS Risk Management

From what I understand and based on the error message, I believe you are on the right track. My first question would be: Has it ever worked before? What changed since?

If you can amend the code and add %include ...../source2; and also try to run in debug mode and with options mprint

I the Viya version is now called ACL and that IRM has been replaced so you must be running a solution version under SAS 9.4. CAS is Viya only.

It's too long ago that I actually did hands-on IFRS9 work and it's certainly a specialty skill. Eventually ask SAS Tech Support directly because I don't expect too many people here in the forums to know the solution in the depth needed to support you.