Integration user and DAGs

An Integration user is defined in Security so that when data is received from an incoming BOD, an operator code can be associated to the data written in SunSystems.

Integration User in Security

The same logic can be applied for outgoing data.

Recommended Setup for Integration User

The recommended setup for the Integration user is to have full access to all objects and data in the system. If the user does not, integration data could be filtered for both incoming and outgoing BODs based on the access setup for the user.

Inbound Data

If the system is DAG enabled, the Integration user selected should have suitable permission to write and access data in the target business unit. Each of these BODs uses a standard SSC component for import. If DAG checking is in place for the component, it is applied when importing data. If incoming data cannot be accepted due to DAG restrictions, BODs are rejected, a Confirm BOD is produced, and an error is available in the Integration Error Log (INL).

Business unit level DAG checking is in place for all components. That is, if DAGs are defined on a business unit in Business Unit Administration (BUA), a check is run to see if the Integration user has the correct DAG associated to them before importing the data.

Note: DAG checking can be different for adding and amending data at the component level, so this should be fully understood for each component.

Outbound Data

If the system is DAG enabled, the Integration user should be set up to have access to all the data required to meet the integration needs.

Standard BODs

Publication of standard Infor OAGIS BODs does not implement DAG checking against the Integration user defined in Security.

Custom BODs

If the component associated to a BOD supports DAG checking, a DAG check is performed on data publication.

Note: This is only applicable if the SSC component associated to each BOD supports DAG checking.


OAGIS BODs consumed	Incoming data rejected without sufficient DAG privileges?
ChartOfAccounts	No
CodeDefinition	Yes
SourceSystemJournalEntry	No
ExpenseReport	No


Custom BODs published	Outbound data filtered on DAGs?
SunSystemsDaybookSetup	No
SunSystemsLedgerRevaluationProfiles	No
SunSystemsLedgerSetup	No
SunSystemsPaymentProfiles	No
SunSystemsPurchaseBusinessSetup	No
SunSystemsPurchaseTypes	Yes. Error log is produced where the system cannot publish due to conflict on the DAGs set on data, and the DAGs assigned to the integration user.
SunSystemsSalesTypes	Yes. Error log is produced where the system cannot publish due to conflict on the DAGs set on data, and the DAGs assigned to the Integration user.


OAGIS BODs published	Outbound data filtered on DAGs?
All outbound OAGIS BODs	No