SAP SRET_DOCS_LS_SYN_INSERT Function Module for

Search SAP Function Modules

SRET_DOCS_LS_SYN_INSERT is a standard sret docs ls syn insert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sret docs ls syn insert FM, simply by entering the name SRET_DOCS_LS_SYN_INSERT into the relevant SAP transaction such as SE37 or SE38.

Function Group: SRIN
Program Name: SAPLSRIN
Main Program: SAPLSRIN
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SRET_DOCS_LS_SYN_INSERT 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 'SRET_DOCS_LS_SYN_INSERT'"
  EXPORTING
   CATID =  "
*  LANGU =  "
*  LAISO =  "
*  CLIENT =  " Client
*  SAPCODEPAGE =  "

 IMPORTING
   RCODE =  "Error Code

TABLES
   DOCIDTAB =  "
   DOCATTRTAB =  "
   DOCCONTTAB =  "
   BINCONTTAB =  "

EXCEPTIONS
   CATID_UNKNOWN = 1    INDEX_COULD_NOT_BE_CHANGED = 10    XERROR = 11    NO_SSR_FOUND = 2    IDXCAT_IS_INACTIVE = 3    NO_DOCS_GIVEN = 4    LANGU_NOT_VALID = 5    CAT_HAS_NO_INDEX = 6    RFC_SYS_FAILURE = 7    RFC_COM_FAILURE = 8    NO_RFC_DEST = 9 

.

IMPORTING Parameters details for SRET_DOCS_LS_SYN_INSERT

CATID -

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

LANGU -

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

LAISO -

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

CLIENT - Client

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

SAPCODEPAGE -

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

EXPORTING Parameters details for SRET_DOCS_LS_SYN_INSERT

RCODE - Error Code

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

TABLES Parameters details for SRET_DOCS_LS_SYN_INSERT

DOCIDTAB -

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

DOCATTRTAB -

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

DOCCONTTAB -

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

BINCONTTAB -

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

EXCEPTIONS details

CATID_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

INDEX_COULD_NOT_BE_CHANGED -

Data type:
Optional: No
Call by Reference: Yes

XERROR - Other Error

Data type:
Optional: No
Call by Reference: Yes

NO_SSR_FOUND -

Data type:
Optional: No
Call by Reference: Yes

IDXCAT_IS_INACTIVE -

Data type:
Optional: No
Call by Reference: Yes

NO_DOCS_GIVEN -

Data type:
Optional: No
Call by Reference: Yes

LANGU_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

CAT_HAS_NO_INDEX -

Data type:
Optional: No
Call by Reference: Yes

RFC_SYS_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

RFC_COM_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

NO_RFC_DEST -

Data type:
Optional: No
Call by Reference: Yes

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

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