External file template to fill custom fields

Hi Julien.  I found the following information - 

Yes, it is possible to populate custom fields in IFS Applications 10 (APP10) using external file templates, provided they are set up with the appropriate Logical Unit (LU) views or data migration mappings.

How Custom Fields Work in APP10 File Loading

When you create and publish a Persistent Custom Field in APP10 (Solution Manager > User Interface > Custom Objects > Custom Fields), IFS automatically generates or updates database views and APIs:

• Custom persistent field columns carry the CF$_ prefix (e.g., CF$_MY_CUSTOM_FIELD).

• A Custom Field View (<LU_NAME>_CFV) is available, exposing both standard fields and the custom CF$_ fields.

Mappings & Setup Options

1. Data Migration Jobs with External File Templates (Recommended)

The most common approach to load external files (CSV, Excel, fixed-width, or XML) into custom fields is through Data Migration:

1. Create a Data Migration Job:

   • Navigate to Solution Manager > Data Management > Data Migration > Migration Job.

   • Set the procedure to CREATE_TABLE_FROM_FILE or MIGRATE_SOURCE_DATA.

2. Set the Target View:

   • Specify the Custom Field View (<LU_NAME>_CFV) or standard LU view as the target view.

3. Map the File Columns:

   • In the Source Information / Column Mapping tab, map your file’s columns to the standard fields as well as your custom field column names (e.g., CF$_<FIELD_NAME>).

4. Execute via External File Template:

   • Define or attach an External File Template to the migration job to handle column delimiters, file formatting, and parsing.

2. External File Interface with Custom Procedures

If you are using the native External File Interface (Solution Manager > Data Management > External Files):

1. Configure an External File Type and External File Template.

2. Map file columns to the target staging table or view.

3. If using custom processing methods/APIs, ensure the attribute string (attr_) constructed during record processing includes the custom field key-value pairs formatted with the CF$_ prefix:

    

    

    

   Client_SYS.Add_To_Attr('CF$_YOUR_FIELD_NAME', p_value_, attr_);

Key Requirements & Checklist

• Published State: The custom field must be Approved and Published before attempting to load data into it.

• Updatable / Insertable Flags: Ensure the custom field properties have the Insertable and/or Updatable checkboxes selected.

• View Exposure: Verify that your file load process interacts with the _CFV view or standard LU APIs that process custom field attribute strings.

Please advise if this helps and/or if you have any questions.  Thanks!  Jane

Thank you Jane.

In my case, I have to use your second point.