Chart of Account object

The MXCOA object structure allows for bidirectional synchronization of chart of accounts data.

Prerequisite

You must load general ledger components before loading the chart of accounts. There is no predefined publish channel for this object structure.

Outbound Integration Processing

The following table shows the predefined values used in outbound integration processing.

Predefined integration components Value and description
Object Structure definition class functionality None
Publish Channel None
Processing Rules None
Integration Controls None

Inbound Integration Processing

The following table shows the preconfigured values used in inbound integration processing.

Predefined integration components Value and description
Object Structure processing class functionality MaxCOAProcess - Can process as a combination of delimited segments or as individual components that are part of the GLACCOUNT datatype definition.
Enterprise Service MXCOAInterface
Processing Rules None
Integration Controls None

Examples of inbound processing

Processing as a combination of delimited segment is available for XML and interface tables. Processing as a combination of delimited segment is available for XML files. You can specify the general ledger account this way in all object structures.

<GLACCOUNT>
  <VALUE>6400-2-10</VALUE>
</GLACCOUNT>

The object structure validates each segment, then creates the chart of account record in database with the following values:

  • GLACCOUNT=6400-2-10
  • GLCOMP01-6400
  • GLCOMP02=2
  • GLCOMP03=10

You can also process the object as individual components that are part of the GLACCOUNT datatype definition.

<GLACCOUNT>
<GLCOMP glorder="0">6400</GLCOMP>
<GLCOMP glorder="1">2</GLCOMP>
<GLCOMP glorder="2">10</GLCOMP>
</GLACCOUNT>

The object structure validates the components and creates the account, using the delimiter defined in the GLCONFIGURE table for each segment. This option is available for XML only.