Siebel Connector for SAP R/3 > Modifying Siebel Interfaces After an SAP Upgrade >

SAP IDOC Interfaces

SAP IDOCs are version dependent. For instance, a single IDOC type will change structure from one R/3 version to another: New segments may be added, fields may be added to the segments, and application processing of the IDOC within SAP may change.

Generally, you can use an older IDOC type structure within a new SAP R/3 version. The R/3 version of an IDOC to be sent from SAP to the Siebel application is configurable within the partner profile for the logical system being used.

To set the version of the IDOC to be sent from SAP

  1. Navigate within SAP to transaction we20.
  2. Select the logical system/partner profile in use.
  3. Select the outbound parameters display for this logical system.
  4. Set the Seg.Release in IDOC type field to your previous R/3 IDOC version.

For example, if you are using the DEBMAS02 IDOC type, running SAP R/3 version 4.5B, and upgrading to R/3 version 4.6B; set the Seg.Release in IDOC type field to 45B. SAP then sends the IDOC type structure of version 4.5B as opposed to 4.6B. If the field is not filled in, the IDOC type structure corresponding to the current version is sent.

NOTE:  This version is only applicable to SAP developed IDOC type structures. It is not applicable to custom IDOCs if no version change has been made.

When sending IDOCs from the Siebel application to SAP, no version setting is necessary. SAP determines the version of the IDOC when it is sent.

IDOC type structures that change from version to version are changed in minimal ways. Fields and segments may be added to the structure; no fields are deleted nor does the order of preexisting fields change. However, SAP also provides application software that populates the IDOC fields on output from SAP and extracts field values on input to SAP. This application software may change during an upgrade of SAP. For this reason, test all IDOC interfaces during the upgrade process.

Siebel Connector for SAP R/3