SAP ISH_PLR_DB_UPDATE Function Module for IS-H: DB UPDATE for Legal Representative Relationship
ISH_PLR_DB_UPDATE is a standard ish plr db update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-H: DB UPDATE for Legal Representative Relationship 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 ish plr db update FM, simply by entering the name ISH_PLR_DB_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: NPLR_DB
Program Name: SAPLNPLR_DB
Main Program: SAPLNPLR_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function ISH_PLR_DB_UPDATE 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 'ISH_PLR_DB_UPDATE'"IS-H: DB UPDATE for Legal Representative Relationship.
EXPORTING
I_TAB_DEL = "BDT Buffer for Relationship Legal Representative
I_TAB_INS = "BDT Buffer for Relationship Legal Representative
I_TAB_UPD = "BDT Buffer for Relationship Legal Representative
I_TAB_UPD_OLD = "BDT Buffer for Relationship Legal Representative
I_MODUS_PLR = "Change type (U, I, E, D)
* I_TCODE = SY-TCODE "Current Transaction Code
I_UP_DATE = "Current Date of Application Server
I_UP_TIME = "Current Time of Application Server
* I_UPD_ICDTXT = ' ' "Change type (U, I, E, D)
TABLES
* ICDTXT = "Change documents: Text changes
IMPORTING Parameters details for ISH_PLR_DB_UPDATE
I_TAB_DEL - BDT Buffer for Relationship Legal Representative
Data type: ISH_T_PLROptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_INS - BDT Buffer for Relationship Legal Representative
Data type: ISH_T_PLROptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_UPD - BDT Buffer for Relationship Legal Representative
Data type: ISH_T_PLROptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_UPD_OLD - BDT Buffer for Relationship Legal Representative
Data type: ISH_T_PLROptional: No
Call by Reference: No ( called with pass by value option)
I_MODUS_PLR - Change type (U, I, E, D)
Data type: CDPOS-CHNGINDOptional: No
Call by Reference: No ( called with pass by value option)
I_TCODE - Current Transaction Code
Data type: SY-TCODEDefault: SY-TCODE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_UP_DATE - Current Date of Application Server
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_UP_TIME - Current Time of Application Server
Data type: SY-UZEITOptional: No
Call by Reference: No ( called with pass by value option)
I_UPD_ICDTXT - Change type (U, I, E, D)
Data type: CDPOS-CHNGINDDefault: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISH_PLR_DB_UPDATE
ICDTXT - Change documents: Text changes
Data type: CDTXTOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISH_PLR_DB_UPDATE 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_icdtxt | TYPE STANDARD TABLE OF CDTXT, " | |||
| lv_i_tab_del | TYPE ISH_T_PLR, " | |||
| lv_i_tab_ins | TYPE ISH_T_PLR, " | |||
| lv_i_tab_upd | TYPE ISH_T_PLR, " | |||
| lv_i_tab_upd_old | TYPE ISH_T_PLR, " | |||
| lv_i_modus_plr | TYPE CDPOS-CHNGIND, " | |||
| lv_i_tcode | TYPE SY-TCODE, " SY-TCODE | |||
| lv_i_up_date | TYPE SY-DATUM, " | |||
| lv_i_up_time | TYPE SY-UZEIT, " | |||
| lv_i_upd_icdtxt | TYPE CDPOS-CHNGIND. " SPACE |
|   CALL FUNCTION 'ISH_PLR_DB_UPDATE' "IS-H: DB UPDATE for Legal Representative Relationship |
| EXPORTING | ||
| I_TAB_DEL | = lv_i_tab_del | |
| I_TAB_INS | = lv_i_tab_ins | |
| I_TAB_UPD | = lv_i_tab_upd | |
| I_TAB_UPD_OLD | = lv_i_tab_upd_old | |
| I_MODUS_PLR | = lv_i_modus_plr | |
| I_TCODE | = lv_i_tcode | |
| I_UP_DATE | = lv_i_up_date | |
| I_UP_TIME | = lv_i_up_time | |
| I_UPD_ICDTXT | = lv_i_upd_icdtxt | |
| TABLES | ||
| ICDTXT | = lt_icdtxt | |
| . " ISH_PLR_DB_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM ISH_PLR_DB_UPDATE
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 CHNGIND FROM CDPOS INTO @DATA(ld_i_modus_plr). | ||||
| "SELECT single TCODE FROM SY INTO @DATA(ld_i_tcode). | ||||
| DATA(ld_i_tcode) | = SY-TCODE. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_up_date). | ||||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_i_up_time). | ||||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_i_upd_icdtxt). | ||||
| DATA(ld_i_upd_icdtxt) | = ' '. | |||
Search for further information about these or an SAP related objects