Optiva tables used for ION integrations

Infor BOD types must be mapped to the appropriate Optiva objects. These tables are created during the Optiva installation to support the ION integration.

Optiva Table Description
FSBODACTIONSETCONFIG This table maps the appropriate workflow (Action Set) to each BOD type.

This mapping is used by the Optiva Listener to launch the appropriate workflow and process the BOD XML. No user intervention is necessary.

COR_INBOX_ENTRY

COR_INBOX_HEADER

These tables store the BOD XML data and header information that is coming from the participating application.

The Listener monitors these tables and uses workflows to import the data to Optiva.

COR_OUTBOX_ENTRY

COR_OUTBOX_HEADER

These tables are where the Optiva generated BODs are delivered to. They are then read by ION and processed.
COR_PROPERTY This table is not used. It is intended to store the version of ION.