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

SAP BAPI/RFC Interfaces

BAPI/RFC interfaces may also change from one SAP version to another. In particular, BAPI or RFC functions that are marked as "Not released" are the most subject to changes by SAP from version to version. Functions that are "Not released" may not function properly when moving from one version of R/3 to another. Therefore, any functions in use that are marked "Not released" should receive special scrutiny when performing an SAP upgrade. These functions may be untested in the newer SAP version and should be used only if absolutely necessary.

To determine the status of a BAPI or RFC

  1. Navigate to SAP transaction SE37.
  2. Enter the name of the RFC or BAPI call in use.
  3. Select the Display button.
  4. Select the Attributes tab.

    The status appears at the bottom of the General Data area. If Released, a release date also appears.

BAPIs and RFCs that have been released may also change slightly during an SAP upgrade. However, because of their release status, they are tested and supported by SAP and should remain functional from one version to another, unless SAP indicates otherwise.

To check for more information on the status of released BAPIs

  1. Navigate to the SAP transaction bapi.
  2. Select the BAPI you are interested in from the left panel.
  3. Check the release information in the Status area of the Detail tab.

    This may supply more specific information on release status. For example, BAPI_SALESORDER_CREATEFROMDAT1 shows a released status, but also shows the warning, "Caution: Method is obsolete as of Release 46C!"

Check the following for all BAPIs and RFCs during an SAP upgrade:

  • Check for any OSS notes that might indicate a change in functionality or defects.
  • Recheck the release status as mentioned in the preceding procedure.
  • Check any existing function documentation, accessed through the Function Module Documentation button in SAP transaction SE37.
  • Extract the new version of the BAPI into new integration objects (input and output) in Siebel Tools and use the Compare Objects function to detect any differences in structure between the new and old integration objects.

    If the structure is different, the new structure should always be used. If the structure is significantly different, it may be necessary to review and modify eScript maps that reference fields in the structures.

  • Always retest, even when there are no structure changes, as the function itself may have a slightly different behavior than in the previous R/3 system.

Be aware that patch installations in SAP may also affect the functionality of BAPIs and RFCs. Patches should be reviewed for content and some testing may be required after the application of a patch.

Siebel Connector for SAP R/3