|
|
|
|
|
|
|
|
|
|
SIM (Software Integration Module)
|
|
|
|
Where it is needed to go beyond the boundaries of Dynamics Ax, it is suggested that partners and customers use Axnosis SIM. SIM attempts to standardise on interfaces to or from Ax.
|
| |
|
The principles of SIM:

|
| |
|
Firstly, integration points are identified and configured in a base enum. Mapping is done against these integration points, i.e. external table fields are mapped to the corresponding table inside Ax.
|
| |
|
Secondly, a T-SQL statement is linked to each integration point. These SQL statements are used when the actual integration job is executed. The heart of SIM is that normal SQL statements are entered into the Dynamics Ax SIM form. SIM translates SQL into native X++ without any user involvement.
|
| |
|
Thirdly, an integration class is used when the integration is executed, either manually or scheduled.
|
| |
|
Fourthly, the relevant data in Ax, populated from an external source can be used. An example is the Symplexity interface, where information in the “AxnSymGLIT” table is used to automatically create GL journal entries for the payroll.
|
| |
|
Finally, when interfacing with a 3rd party, and depending on the 3rd party application, it is possible to write data from Ax into the tables of the 3rd party application.
|
| |
|
The current application of SIM includes the following interfaces:
- A2L – Ax to Labware LIMS
- A2S – Ax to Symplexity
- A2P – Ax to Pragma
- A2M – Ax to PIMS
- A2V – Ax to VIP
|
|
|
 |
|
|
|
|
|
|
|