You are creating integrations in Oracle Integration Cloud (OIC) using B2B trading partner agreements. Which identifier is implicitly used for all outbound agreements?

In Oracle Integration B2B, the host trading partner represents your company. A primary identifier must be configured for this host partner. This primary identifier, which corresponds to the EDI Interchange ID, is implicitly and automatically used to populate the sender ID field in the interchange control header (e.g., ISA06 for X12, UNB02.1 for EDIFACT) for all outbound B2B messages. This ensures that any receiving trading partner can uniquely identify your organization as the sender of the electronic interchange.

A. EDI Interchange Internal Sub ID is a secondary identifier used for specific internal routing or departmental identification, not the primary identifier for all outbound agreements.
C. Application Partner ID is used to identify a specific backend application or system, not the overall trading entity at the B2B interchange level.
D. EDI Group ID Qualifier is a code that specifies the format or type of the Group ID; it is not the identifier itself.

1. Oracle Cloud Infrastructure Documentation, Using B2B for Oracle Integration, "Configure the Host Trading Partner": This section explicitly states, "The primary identifier you define is used in the sender ID of the outbound EDI document's interchange header." This confirms that the primary identifier, which is the EDI Interchange ID, is used for all outbound messages.

2. Oracle Cloud Infrastructure Documentation, Using B2B for Oracle Integration, "Create Trading Partners": This page details the process of adding identifiers to a trading partner. It distinguishes between the primary identifier (required for the host) and other secondary identifiers, reinforcing that the primary EDI Interchange ID is the key identifier for the host in outbound transactions.