SAP PVSU2_OBJ_ID_ADD Function Module for NOTRANSL: legt oid an (und evtl. zugehörige inst)
PVSU2_OBJ_ID_ADD is a standard pvsu2 obj id add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: legt oid an (und evtl. zugehörige inst) 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 pvsu2 obj id add FM, simply by entering the name PVSU2_OBJ_ID_ADD into the relevant SAP transaction such as SE37 or SE38.
Function Group: PVSU2
Program Name: SAPLPVSU2
Main Program: SAPLPVSU2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function PVSU2_OBJ_ID_ADD 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 'PVSU2_OBJ_ID_ADD'"NOTRANSL: legt oid an (und evtl. zugehörige inst).
EXPORTING
* IM_MSG_HANDLING = 'A' "
IM_OBJ_ID_INT = "
* IM_PAR_OBJ_ID = "ALV Tree Control: Node Key
* IM_EXOBJ_ID = "Identification for External Objects
* IM_QUANT = "Quantity (in Component Variant)
* IM_INSCNT = "Count parameters
* IM_DMUCNT = "Count parameters
* IM_TREE_ID = "Identification of the ALV Tree on the iPPE User Interface
* IM_EXISTENT_OBJ_ID = "ALV Tree Control: Node Key
IMPORTING
EX_OBJ_ID = "ALV Tree Control: Node Key
EX_INST_ID = "ALV Tree Control: Node Key
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for PVSU2_OBJ_ID_ADD
IM_MSG_HANDLING -
Data type: PPET_MSG_OPTDefault: 'A'
Optional: Yes
Call by Reference: Yes
IM_OBJ_ID_INT -
Data type: PPET0_OID_INT_TYPEOptional: No
Call by Reference: Yes
IM_PAR_OBJ_ID - ALV Tree Control: Node Key
Data type: LVC_NKEYOptional: Yes
Call by Reference: Yes
IM_EXOBJ_ID - Identification for External Objects
Data type: PVS_EX_OBJ_IDOptional: Yes
Call by Reference: Yes
IM_QUANT - Quantity (in Component Variant)
Data type: PVS_QUANTOptional: Yes
Call by Reference: Yes
IM_INSCNT - Count parameters
Data type: NUMC4Optional: Yes
Call by Reference: Yes
IM_DMUCNT - Count parameters
Data type: NUMC4Optional: Yes
Call by Reference: Yes
IM_TREE_ID - Identification of the ALV Tree on the iPPE User Interface
Data type: PPET0_TREE_IDOptional: Yes
Call by Reference: Yes
IM_EXISTENT_OBJ_ID - ALV Tree Control: Node Key
Data type: LVC_NKEYOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PVSU2_OBJ_ID_ADD
EX_OBJ_ID - ALV Tree Control: Node Key
Data type: LVC_NKEYOptional: No
Call by Reference: Yes
EX_INST_ID - ALV Tree Control: Node Key
Data type: LVC_NKEYOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PVSU2_OBJ_ID_ADD 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_error | TYPE STRING, " | |||
lv_ex_obj_id | TYPE LVC_NKEY, " | |||
lv_im_msg_handling | TYPE PPET_MSG_OPT, " 'A' | |||
lv_ex_inst_id | TYPE LVC_NKEY, " | |||
lv_im_obj_id_int | TYPE PPET0_OID_INT_TYPE, " | |||
lv_im_par_obj_id | TYPE LVC_NKEY, " | |||
lv_im_exobj_id | TYPE PVS_EX_OBJ_ID, " | |||
lv_im_quant | TYPE PVS_QUANT, " | |||
lv_im_inscnt | TYPE NUMC4, " | |||
lv_im_dmucnt | TYPE NUMC4, " | |||
lv_im_tree_id | TYPE PPET0_TREE_ID, " | |||
lv_im_existent_obj_id | TYPE LVC_NKEY. " |
  CALL FUNCTION 'PVSU2_OBJ_ID_ADD' "NOTRANSL: legt oid an (und evtl. zugehörige inst) |
EXPORTING | ||
IM_MSG_HANDLING | = lv_im_msg_handling | |
IM_OBJ_ID_INT | = lv_im_obj_id_int | |
IM_PAR_OBJ_ID | = lv_im_par_obj_id | |
IM_EXOBJ_ID | = lv_im_exobj_id | |
IM_QUANT | = lv_im_quant | |
IM_INSCNT | = lv_im_inscnt | |
IM_DMUCNT | = lv_im_dmucnt | |
IM_TREE_ID | = lv_im_tree_id | |
IM_EXISTENT_OBJ_ID | = lv_im_existent_obj_id | |
IMPORTING | ||
EX_OBJ_ID | = lv_ex_obj_id | |
EX_INST_ID | = lv_ex_inst_id | |
EXCEPTIONS | ||
ERROR = 1 | ||
. " PVSU2_OBJ_ID_ADD |
ABAP code using 7.40 inline data declarations to call FM PVSU2_OBJ_ID_ADD
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.DATA(ld_im_msg_handling) | = 'A'. | |||
Search for further information about these or an SAP related objects