Axway IMAGINE SUMMIT 2019. Accelerating the future. Together. Americas March 4-6 | Europe March 21-22    
Exit Preview Mode
Limit search to current manual
Product
Content Type
    Environment
    Close
      Home  \ 
    1. AccountingIntegrator 2.3.0 User Guide
    2. Terminology
    Filter
    Product
    Content Type
      Environment

      AccountingIntegrator 2.3.0 User Guide

      Show/Hide Menu

      Contents

      • Expand
      • Collapse
      • AccountingIntegrator 2.3 User Guide
      • About this guide
      • Accessibility
      • AccountingIntegrator overview
      • Get started with AccountingIntegrator
      • Rule Engine model
      • Manage the Rule Engine dynamically
      • Manage the Rule Engine configurations
      • Define the configuration
      • Configure interactions
      • Manage transformation anomalies
      • Implement functions in the Rule Engine
      • Manage reports with AccountingIntegrator
      • Administer the project
      • Implement the Rule Engine using permanent files
      • Manage exits and external calls
      • Rule Engine Error messages
      • UTF-16 implementation details
      • Required files for the Rule Engine
      • Terminology
      • Functional context generated by the sender parameter settings

      Terminology

      The requirement for structure compatibility is mentioned in several chapters in this documentation.
      Two or more structures are said to be compatible when the major fields in these structures share a common definition. That is, when the internal position, length and data types of the structures are identical.

      Related Links

        Join the discussion in Axway Community! Analytics | API Mgmt | EDI/B2B | MFT