SAP ISU_MIG_SPAGREE_PARA Function Module for Migration of Service Provider Agreements and Parameter Configuration

Search SAP Function Modules

ISU_MIG_SPAGREE_PARA is a standard isu mig spagree para SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Migration of Service Provider Agreements and Parameter Configuration 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 isu mig spagree para FM, simply by entering the name ISU_MIG_SPAGREE_PARA into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_MIG_SPAGREE_PARA 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 'ISU_MIG_SPAGREE_PARA'"Migration of Service Provider Agreements and Parameter Configuration
  EXPORTING
   X_DEREGSPINIT =  "Service Provider (Market Partner)
   X_DEREGSPPART =  "Processing Service Provider
   X_RAISE_EXC =  "Indicator

TABLES
   XYT_DEREGSPAGREE_AUTO =  "Automation Data for Service Provider Agreement
   XT_DEREGPARA_AUTO =  "Automation Data for Parameter Configuration
   RETURN =  "Return Parameter(s)

EXCEPTIONS
   AUTO_ERROR = 1    INVALID_WORK_MODE = 2    FOREIGN_LOCK = 3    SP_NOT_FOUND = 4    SPA_DATA_INVALID = 5    PARA_DATA_INVALID = 6    ERROR_OCCURED = 7 

.

IMPORTING Parameters details for ISU_MIG_SPAGREE_PARA

X_DEREGSPINIT - Service Provider (Market Partner)

Data type: E_DEREGSPINITIATOR
Optional: No
Call by Reference: Yes

X_DEREGSPPART - Processing Service Provider

Data type: E_DEREGSPPARTNER
Optional: No
Call by Reference: Yes

X_RAISE_EXC - Indicator

Data type: KENNZX
Optional: No
Call by Reference: Yes

TABLES Parameters details for ISU_MIG_SPAGREE_PARA

XYT_DEREGSPAGREE_AUTO - Automation Data for Service Provider Agreement

Data type: EDEREGSPAGREE_AUTO
Optional: No
Call by Reference: Yes

XT_DEREGPARA_AUTO - Automation Data for Parameter Configuration

Data type: EDEREGPARA_AUTO
Optional: No
Call by Reference: Yes

RETURN - Return Parameter(s)

Data type: BAPIRET2
Optional: No
Call by Reference: Yes

EXCEPTIONS details

AUTO_ERROR -

Data type:
Optional: No
Call by Reference: Yes

INVALID_WORK_MODE -

Data type:
Optional: No
Call by Reference: Yes

FOREIGN_LOCK -

Data type:
Optional: No
Call by Reference: Yes

SP_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

SPA_DATA_INVALID -

Data type:
Optional: No
Call by Reference: Yes

PARA_DATA_INVALID -

Data type:
Optional: No
Call by Reference: Yes

ERROR_OCCURED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_MIG_SPAGREE_PARA 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 ISU_MIG_SPAGREE_PARA

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