# New IDoc trigger

Trigger New IDoc

This trigger allows you to listen to and receive IDocs from an on-premise SAP system, or from a SAP system on a server behind a corporate firewall.

IDOC DEDUPLICATION

When you resend the IDoc, recipes that previously received the IDoc do not process it again due to Workato's deduplication logic.

BEFORE YOU BEGIN

You must configure IDocs in your SAP system before using this trigger.

# Input fields

Field name	Description
IDoc name	The IDoc to listen to. You can select an IDoc name from the picklist. Note that the picklist only displays IDocs that are configured in the partner profile in your SAP system.

MESSAGE TYPE, BASIC TYPE, AND CUSTOM EXTENSIONS

We subscribe to one message type, basic type, and custom extension (if applicable) at a time. You must maintain the recipe logic to ensure that the workflow processes appropriately for different partners. For example, you can apply the condition on the RCVPRN datapill from the trigger or add the RCVPRT datapill in addition to the RCVPRN datapill.

Starting in OPA v27.1, SAP partner details are included automatically in the IDoc description. The description shows the partner number/partner profile and partner type. These values come from the message type, IDoc type, and custom extensions included in the ALE configuration for SAP transaction codes WE20 and BD64. Trigger New IDoc Description New IDoc description

In earlier OPA versions, the description only shows the total number of partners if there is more than one. The description doesn't include partner details. Trigger New IDoc Description Old OPA IDoc description with earlier OPA version

BATCH IDOC TRIGGER

Enhanced descriptions also applies to the Batch IDoc trigger.

# Output fields

The trigger outputs all segments and data fields of the IDoc received from SAP. In this sample IDoc, EDI_DC40 and E1MARAM segments.

Trigger New IDoc output