SAP SPECIAL_ARRANGEMENTS Function Module for Special Arrangements









SPECIAL_ARRANGEMENTS is a standard special arrangements SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Special Arrangements 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 special arrangements FM, simply by entering the name SPECIAL_ARRANGEMENTS into the relevant SAP transaction such as SE37 or SE38.

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



Function SPECIAL_ARRANGEMENTS 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 'SPECIAL_ARRANGEMENTS'"Special Arrangements
EXPORTING
* RSICHER = ' ' "Sicherheiten-Nr. vom aufrufenden Pgm.
* FLG_MODUS = ' ' "Modus: S (Anzeigen), I (Anlegen), U (Ändern)

IMPORTING
E_PARTNER_NEW = "Kennzeichen: Partner neu angelegt
E_PARTNER_CHANGE = "Änderung am Partner erfolgt / sichern nötig

TABLES
TVDSONSI_ALT = "Alter Stand VDSONSI, ggf. für mehrere RSICHER
TVDSONSI_NEU = "Neuer Stand VDSONSI f. d. DB-Update d. Aufrufers
TVZGPO_ALT = "Alter Stand VZPARO, ggf. für mehrere RSICHER
TVZGPO_NEU = "Neuer Stand VZPARO f. Rollen-Aktualisierung

EXCEPTIONS
CANCELLED = 1 NOT_FOUND = 2
.



IMPORTING Parameters details for SPECIAL_ARRANGEMENTS

RSICHER - Sicherheiten-Nr. vom aufrufenden Pgm.

Data type: VDARLSIC-RSICHER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FLG_MODUS - Modus: S (Anzeigen), I (Anlegen), U (Ändern)

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SPECIAL_ARRANGEMENTS

E_PARTNER_NEW - Kennzeichen: Partner neu angelegt

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

E_PARTNER_CHANGE - Änderung am Partner erfolgt / sichern nötig

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

TABLES Parameters details for SPECIAL_ARRANGEMENTS

TVDSONSI_ALT - Alter Stand VDSONSI, ggf. für mehrere RSICHER

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

TVDSONSI_NEU - Neuer Stand VDSONSI f. d. DB-Update d. Aufrufers

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

TVZGPO_ALT - Alter Stand VZPARO, ggf. für mehrere RSICHER

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

TVZGPO_NEU - Neuer Stand VZPARO f. Rollen-Aktualisierung

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

EXCEPTIONS details

CANCELLED - Abbruch-Taste betätigt

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

NOT_FOUND - RSICHER = Null übergeben

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

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

DATA:
lv_rsicher  TYPE VDARLSIC-RSICHER, "   SPACE
lv_cancelled  TYPE VDARLSIC, "   
lt_tvdsonsi_alt  TYPE STANDARD TABLE OF VDSONSI, "   
lv_e_partner_new  TYPE BUS000FLDS-XCHNG, "   
lv_flg_modus  TYPE BUS000FLDS, "   SPACE
lv_not_found  TYPE BUS000FLDS, "   
lt_tvdsonsi_neu  TYPE STANDARD TABLE OF VDSONSI, "   
lv_e_partner_change  TYPE XFELD, "   
lt_tvzgpo_alt  TYPE STANDARD TABLE OF VDGPO, "   
lt_tvzgpo_neu  TYPE STANDARD TABLE OF VDGPO. "   

  CALL FUNCTION 'SPECIAL_ARRANGEMENTS'  "Special Arrangements
    EXPORTING
         RSICHER = lv_rsicher
         FLG_MODUS = lv_flg_modus
    IMPORTING
         E_PARTNER_NEW = lv_e_partner_new
         E_PARTNER_CHANGE = lv_e_partner_change
    TABLES
         TVDSONSI_ALT = lt_tvdsonsi_alt
         TVDSONSI_NEU = lt_tvdsonsi_neu
         TVZGPO_ALT = lt_tvzgpo_alt
         TVZGPO_NEU = lt_tvzgpo_neu
    EXCEPTIONS
        CANCELLED = 1
        NOT_FOUND = 2
. " SPECIAL_ARRANGEMENTS




ABAP code using 7.40 inline data declarations to call FM SPECIAL_ARRANGEMENTS

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.

"SELECT single RSICHER FROM VDARLSIC INTO @DATA(ld_rsicher).
DATA(ld_rsicher) = ' '.
 
 
 
"SELECT single XCHNG FROM BUS000FLDS INTO @DATA(ld_e_partner_new).
 
DATA(ld_flg_modus) = ' '.
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!