A Data Processor transformation uses Scripts and Library objects to transform industry message type inputs into other formats, and vice-versa.

A Library transformation contains a large number of objects and components, such as Parsers, Serializers, and XML schemas, that transform the industry standard input and specific application messages into XML output. A Library transformation might contain objects for message validation, acknowledgments, and diagnostic displays. A Library transformation uses objects to transform the messaging type from industry standard input to XML and from XML to the library standard format.

You can create Library objects for ACORD, BAI, CREST, DTCC-NSCC, EDIFACT, EDI-UCS & WINS, EDI-VICS, EDI-X12, FIX, FpML, HIPAA, HIX, HL7, IATA, IDS, MDM Mapping, NACHA, NCPDP, SEPA, SWIFT, and Telekurs libraries.

You can use a dedicated Library editor to edit the Library specifications for the DTCC-NSCC, EDIFACT, EDI-X12, HIPAA, HL7, and SWIFT libraries. A Library object contains a root element, container elements, and data elements. The types of container and data elements vary according to message type. You can add and delete elements and configure the properties of elements to change validation settings.

When you create transformations for the Bloomberg, COBOL, and Thomson Reuters libraries, they do not contain Library objects.