SAP OIA_EXGAGRMNT_CONTRACT_INIT Function Module for Initialize exchange data during contract creation via rfc

Search SAP Function Modules

OIA_EXGAGRMNT_CONTRACT_INIT is a standard oia exgagrmnt contract init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initialize exchange data during contract creation via rfc processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for oia exgagrmnt contract init FM, simply by entering the name OIA_EXGAGRMNT_CONTRACT_INIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: OIA_IF_EXGAGRMNT
Program Name: SAPLOIA_IF_EXGAGRMNT
Main Program: SAPLOIA_IF_EXGAGRMNT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIA_EXGAGRMNT_CONTRACT_INIT pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'OIA_EXGAGRMNT_CONTRACT_INIT'"Initialize exchange data during contract creation via rfc
  EXPORTING
   APPLICATION =  "Application
   ACTIVITY =  "Activity category in SAP transaction
   EXCHANGE_NUMBER =  "Exchange agreement number
*  TEXT =  "Text (80 characters)

 IMPORTING
   EXCHANGE_PARTNER =  "Exchange partner (vendor number)

EXCEPTIONS
   EXCHANGE_NOT_FOUND = 1    LOCKING_ERROR = 2    NO_AUTHORIZATION = 3 

.

IMPORTING Parameters details for OIA_EXGAGRMNT_CONTRACT_INIT

APPLICATION - Application

Data type: T681A-KAPPL
Optional: No
Call by Reference: No ( called with pass by value option)

ACTIVITY - Activity category in SAP transaction

Data type: T180-AKTYP
Optional: No
Call by Reference: No ( called with pass by value option)

EXCHANGE_NUMBER - Exchange agreement number

Data type: OIA_EXGNUM
Optional: No
Call by Reference: No ( called with pass by value option)

TEXT - Text (80 characters)

Data type: OIA02-TEXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for OIA_EXGAGRMNT_CONTRACT_INIT

EXCHANGE_PARTNER - Exchange partner (vendor number)

Data type: OIA01-EXGPTR
Optional: No
Call by Reference: Yes

EXCEPTIONS details

EXCHANGE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

LOCKING_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORIZATION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIA_EXGAGRMNT_CONTRACT_INIT Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM OIA_EXGAGRMNT_CONTRACT_INIT

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects