File Content
Conversion

File content conversion is the process of transforming data from one file format into another — for example, converting a flat file (CSV, fixed-length text) into XML, or converting XML back into a flat file — so that systems with different data format requirements can exchange information without errors. In the SAP ecosystem, this process is handled natively by the File Content Conversion (FCC) module inside the File Adapter of SAP Process Integration (PI) and Process Orchestration (PO), without requiring custom message mappings for basic transformations.

The 3 main benefits of file content conversion are reduced development effort, faster data exchange between disparate systems, and consistent payload structure across enterprise integration layers. Its 3 primary use cases are inbound flat file processing (CSV to XML), outbound XML-to-flat-file transformation, and secure data exchange using Pretty Good Privacy (PGP) encryption and decryption.

File content conversion has 4 key components: the File Adapter, FCC parameters (such as fieldSeparator and recordsetStructure), adapter modules (such as Localejbs/PGPDecryption and AF_Modules/MessageTransformBean), and the Message Mapping layer used for complex transformations when FCC alone is insufficient.

File Content Conversion in SAP Process Integration (PI) / Process Orchestration (PO) is a built-in feature of the File Adapter that converts flat files into XML — or XML into flat files — at runtime, without requiring message mapping for the conversion step itself.

SAP PI/PO serves as middleware technology connecting SAP ERP, CRM, SCM, and third-party systems within SAP-centric enterprises. When these systems exchange data, they often use different file formats. File content conversion solves the format compatibility problem at the adapter layer.

SAP PI/PO provides this functionality out of the box for unencrypted files. When the file is encrypted using PGP, additional adapter modules handle decryption before the FCC module processes the content.

The configuration takes place in two locations:

• Enterprise Services Repository (ESR): where data types, message types, service interfaces, and message mappings are created
• Integration Directory (ID): where communication channels, sender/receiver agreements, and Integrated Configuration (ICO) objects are configured

File content conversion in SAP PI is used for integrations where an external system sends a CSV file and SAP needs to parse it as XML, or where SAP sends XML data that a legacy system expects in flat file format.

For encrypted files, PGP decryption runs before Step 3, using the Localejbs/PGPDecryption adapter module.

Correctly configuring these 7 parameters ensures clean XML output and prevents runtime errors during payload conversion in SAP PI/PO.

The sender file adapter uses FCC to read a flat file and produce XML. The FCC module processes the file line by line, applies the configured parsing rules, and outputs a structured XML document that the integration flow can map and route.

File Structure

The system expects a file with one or more logical structures called recordsets. Each recordset can contain one or multiple substructure types, identified by logical names. A substructure always maps to exactly one line in the source file.

The generated XML follows this structure:

<documentName>
  <recordset>
    <NameA>
      <field-nameA1>value</field-nameA1>
      <field-nameA2>value</field-nameA2>
    </NameA>
    <NameB>
      <field-nameB1>value</field-nameB1>
    </NameB>
  </recordset>
</documentName>

Handling Structure Deviations

Structure deviations occur when the actual file contains fewer or more fields than the configured structure specifies. FCC handles these cases using 2 parameters:

NameA.missingLastFields — controls behavior when the inbound structure has fewer fields than configured. Set to ignore to output only the present fields, add to output empty tags for missing fields, or error to terminate conversion.

NameA.additionalLastFields — controls behavior when the inbound structure has more fields than configured. Set to ignore to discard extra fields or error to terminate conversion. The default is ignore.

Document Specifications

4 document-level parameters must be set for correct Message Mapping:

• Document Name: the root XML tag name, matching the ESR message type
• Document Namespace: the namespace added to the document root element
• Document Offset: the number of header lines to skip before reading data; default is 0
• Recordset Name: the name of the recordset structure element in the XML

Parameters for Recordset Structures

Each substructure in the recordset requires its own set of parameters prefixed with the substructure name. The 5 core per-substructure parameters are:

• NameA.fieldSeparator — delimiter between fields in this substructure
• NameA.fieldNames — comma-separated list of field names, in file order
• NameA.fieldFixedLengths — field widths in characters (for fixed-length files only)
• NameA.keyFieldValue — the constant value of the key field that identifies this substructure type
• NameA.endSeparator — optional character string after the last field in a row

For fixed-length files, fieldFixedLengths replaces fieldSeparator. Both can coexist, but the separator's length is not added to the fixed-length count.

Use SAP PI/PO message monitoring to identify which step the error occurs in. Runtime errors in FCC show up as failed messages in the monitoring dashboard with detailed error descriptions.

Background

SAP PI/PO file channels with File Content Conversion are common in long-running SAP-centric enterprise landscapes. During migration projects — including moves to SAP S/4HANA, SAP Integration Suite, or other middleware platforms — these channels must be re-created or migrated with their FCC parameter configurations intact.

Migration Challenges

File channel migration presents 3 specific challenges:

• FCC parameter sets can be large and complex, with 20–40 parameters per channel in multi-structure scenarios
• Manual re-entry of parameters into a new system introduces transcription errors
• Testing migrated channels requires source files that match the original format, which may no longer be readily available

Solution

Automated migration tooling — such as the Figaf Integration Suite toolset — reads existing SAP PI/PO communication channel configurations, extracts FCC parameters, and generates equivalent channel configurations in the target system. This approach eliminates manual parameter re-entry and reduces migration time for file-heavy integration landscapes.

How it Works

The migration tool connects to the source SAP PI/PO system, reads all file adapter communication channels, identifies channels with File Content Conversion enabled, and exports the full parameter set for each channel. The export includes document name, namespace, recordset structure, field separators, field names, and all substructure-level parameters.

The tool then generates the equivalent configuration in the target environment, adapting parameter formats where the target system's API differs from the source.

Automated Migration

Automated migration handles bulk file transformation workflow scenarios where hundreds of FCC channels exist in a single SAP PI/PO system. The process runs without manual intervention for standard FCC configurations. Edge cases — such as channels using custom adapter modules for PGP decryption — are flagged for manual review.

Testing

After migration, each FCC channel requires functional testing using sample flat files. The test verifies that the XML output of the migrated channel matches the XML output of the original channel for the same input file. Discrepancies in field ordering, namespace, or encoding indicate parameter migration errors.

Modules

Channels that use adapter modules — such as those in PGP scenarios using Localejbs/PGPDecryption, AF_Modules/MessageTransformBean, and Localejbs/PGPEncryption — require the same modules to be available in the target system. Module availability in the target adapter engine must be confirmed before migration begins.

Demonstration

A typical FCC migration demonstration covers 3 scenarios:

1. Simple CSV sender channel with a single recordset structure
2. Multi-structure file with keyFieldName-based substructure differentiation
3. PGP-encrypted file channel requiring adapter module migration

Each scenario validates that the migrated channel produces identical XML output to the source channel when processing the same test file.

File Content Conversion (FCC) in SAP PI/PO converts flat files into XML and XML into flat files at the adapter level, reducing development effort and removing the need for manual message mappings in basic format transformation scenarios.

FCC covers 3 core use cases: inbound CSV processing via Sender FCC, outbound XML-to-flat-file transformation via Receiver FCC, and encrypted file exchange using PGP decryption and encryption through adapter modules. Each use case requires specific parameter configurations — including fieldSeparator, recordsetStructure, keyFieldName, and documentName — to produce correct XML output.

Reliable FCC implementations follow 5 practices: validating flat files before processing, using consistent recordset structures, testing with small datasets, enabling runtime monitoring, and maintaining documentation of all parameter values. Migrating FCC channels to SAP S/4HANA or SAP Integration Suite benefits from automated tooling that extracts and re-creates parameter configurations without manual transcription.

For SAP-centric enterprises running file-based integrations across SAP ERP, CRM, SCM, and third-party systems, FCC remains one of the most efficient tools for file content migration and structured data conversion at the middleware layer.