[OIC Error Fix] Fixed length File Translation Failure While Writing File: 'Element CreationDate Not Expected'

Fixing Fixed-Length File Translation Error in OIC: "Element 'CreationDate' Not Expected"

Use Case:

You’re building an integration in Oracle Integration Cloud (OIC) that writes data to a fixed-length flat file using the Stage File action. The NXSD schema includes a field called CreationDate. However, during runtime, OIC throws this error:

Translation Failure: Element 'CreationDate' not expected. The data does not conform to the NXSD schema.

Root Cause (Simple Explanation):

In fixed-length files, every field must appear in the exact order and position as defined in the NXSD schema.

If any field before CreationDate is:

• Not mapped
• Mapped incorrectly
• Mapped with the wrong length

… then the data will shift in the output file. As a result, CreationDate shows up at the wrong spot — making OIC think it’s unexpected.

Solution Steps:

Step 1: Review NXSD Schema

• Open the NXSD file used in the Stage File activity.
• Check the order of the fields and their lengths.
• Confirm that CreationDate is present and has the right definition.

Step 2: Check Field Mappings

• Go to the mapping just before the Stage File action.
• Make sure all fields before CreationDate are mapped.
• If a field is optional and not present in the source:
  • Map it to a blank value with the correct length (e.g., ' ' for a 5-character field).

Step 3: Test the Output

• Use the Test button or enable tracing to check the actual output string.
• Verify if the data aligns with the fixed-length format.

Step 4: Regenerate NXSD (if needed)

• If you recently changed the schema, re-import or reconfigure the Stage File activity to ensure it uses the latest NXSD version.