SAP RP_INSERT_DOCU Function Module for Adds documentation to T512U/T513U
RP_INSERT_DOCU is a standard rp insert docu SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Adds documentation to T512U/T513U 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 rp insert docu FM, simply by entering the name RP_INSERT_DOCU into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPDO
Program Name: SAPLRPDO
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RP_INSERT_DOCU 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 'RP_INSERT_DOCU'"Adds documentation to T512U/T513U.
EXPORTING
* APPLI = 'P' "Application
* ASPCT = ' ' "Aspect
* EDFLG = 'X' "Activate editor
ONAME = "Object name
OTYPE = "Object type
* SPRSL = SY-LANGU "Language
TABLES
ITAB = "Documentation to be inserted
EXCEPTIONS
FOUND = 1 LEAVE_EDITOR = 2
IMPORTING Parameters details for RP_INSERT_DOCU
APPLI - Application
Data type: T512U-APPLIDefault: 'P'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ASPCT - Aspect
Data type: T512U-ASPCTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EDFLG - Activate editor
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ONAME - Object name
Data type: T512U-ONAMEOptional: No
Call by Reference: No ( called with pass by value option)
OTYPE - Object type
Data type: T512U-OTYPEOptional: No
Call by Reference: No ( called with pass by value option)
SPRSL - Language
Data type: T512U-SPRSLDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RP_INSERT_DOCU
ITAB - Documentation to be inserted
Data type: PDSY1Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FOUND - Documentation is already available
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LEAVE_EDITOR - Leave editor with PF3
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RP_INSERT_DOCU 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: | ||||
lt_itab | TYPE STANDARD TABLE OF PDSY1, " | |||
lv_appli | TYPE T512U-APPLI, " 'P' | |||
lv_found | TYPE T512U, " | |||
lv_aspct | TYPE T512U-ASPCT, " SPACE | |||
lv_leave_editor | TYPE T512U, " | |||
lv_edflg | TYPE T512U, " 'X' | |||
lv_oname | TYPE T512U-ONAME, " | |||
lv_otype | TYPE T512U-OTYPE, " | |||
lv_sprsl | TYPE T512U-SPRSL. " SY-LANGU |
  CALL FUNCTION 'RP_INSERT_DOCU' "Adds documentation to T512U/T513U |
EXPORTING | ||
APPLI | = lv_appli | |
ASPCT | = lv_aspct | |
EDFLG | = lv_edflg | |
ONAME | = lv_oname | |
OTYPE | = lv_otype | |
SPRSL | = lv_sprsl | |
TABLES | ||
ITAB | = lt_itab | |
EXCEPTIONS | ||
FOUND = 1 | ||
LEAVE_EDITOR = 2 | ||
. " RP_INSERT_DOCU |
ABAP code using 7.40 inline data declarations to call FM RP_INSERT_DOCU
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 APPLI FROM T512U INTO @DATA(ld_appli). | ||||
DATA(ld_appli) | = 'P'. | |||
"SELECT single ASPCT FROM T512U INTO @DATA(ld_aspct). | ||||
DATA(ld_aspct) | = ' '. | |||
DATA(ld_edflg) | = 'X'. | |||
"SELECT single ONAME FROM T512U INTO @DATA(ld_oname). | ||||
"SELECT single OTYPE FROM T512U INTO @DATA(ld_otype). | ||||
"SELECT single SPRSL FROM T512U INTO @DATA(ld_sprsl). | ||||
DATA(ld_sprsl) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects