SAP ISU_TRANSFER_SECURITY_DOC Function Module for EXTERNAL: Transfer Posting of Securities to Other Contract

Search SAP Function Modules

ISU_TRANSFER_SECURITY_DOC is a standard isu transfer security doc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EXTERNAL: Transfer Posting of Securities to Other Contract 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 transfer security doc FM, simply by entering the name ISU_TRANSFER_SECURITY_DOC into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_TRANSFER_SECURITY_DOC 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_TRANSFER_SECURITY_DOC'"EXTERNAL: Transfer Posting of Securities to Other Contract
  EXPORTING
   X_GPART =  "Business Partner
   X_VKONT =  "
   X_VERTRAG =  "
*  X_COMMIT =  "
*  X_ONE_DOC = ' ' "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  X_NO_DIALOG =  "

 IMPORTING
   Y_OPBEL =  "Document Number

TABLES
   XT_EVER =  "
*  YT_OPBEL =  "Range Structure for FI-CA Documents

EXCEPTIONS
   IU_ERROR = 1    NO_ITEMS_FOUND = 2 

.

IMPORTING Parameters details for ISU_TRANSFER_SECURITY_DOC

X_GPART - Business Partner

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

X_VKONT -

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

X_VERTRAG -

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

X_COMMIT -

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

X_ONE_DOC - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

X_NO_DIALOG -

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

EXPORTING Parameters details for ISU_TRANSFER_SECURITY_DOC

Y_OPBEL - Document Number

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

TABLES Parameters details for ISU_TRANSFER_SECURITY_DOC

XT_EVER -

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

YT_OPBEL - Range Structure for FI-CA Documents

Data type: IROPBEL
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

IU_ERROR - Program error

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

NO_ITEMS_FOUND - No documents found

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

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

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