Docs / Inbound Messaging / IDoc Direct Commit

Immediate Posting of Inbound IDocs: ACI_IDOC_DIRECT_COMMIT

Configuration parameter for controlling commit behavior during inbound IDoc processing in ASANWEE / ASAAEMEE.

Overview

By default, the function module /ASADEV/ACI_NEW_CREATE_IDOC passes PI_DO_COMMIT = ABAP_FALSE to IDOC_INBOUND_SINGLE. This means inbound IDocs are not committed during creation and remain in status 64 (IDoc ready for transfer to application). In some cases, this can also lead to the error message "Error while custom function call!".

The configuration parameter ACI_IDOC_DIRECT_COMMIT changes this behavior. When activated, PI_DO_COMMIT is no longer explicitly passed, which lets IDOC_INBOUND_SINGLE use its default (PI_DO_COMMIT = ABAP_TRUE). This triggers a COMMIT WORK during processing and allows the IDoc to reach status 53 (Application document posted) within the same step.

Configuration

You can enable this parameter at two levels. An object-level setting takes precedence over the global default.

Option A: Object-Level (Inbound Objects)

Set the following header attribute on the relevant integration object:

Field	Value
Attribute	`ACI_IDOC_DIRECT_COMMIT`
Value	`X`

Option B: Global Default (All Objects in the Instance)

Set the default value at instance level:

Field	Value
Attribute	`ACI_IDOC_DIRECT_COMMIT`
Value	`X`

Scope and Recommendations

Note: This setting only affects inbound IDoc processing. Outbound processing is not impacted.

Recommendation: As a general recommendation, asynchronous IDoc processing should be preferred.

Related terms: ASANWEE, ASAAEMEE, IDoc, Inbound IDoc, IDOC_INBOUND_SINGLE, /ASADEV/ACI_NEW_CREATE_IDOC.