SAP PLM_AUDIT_OBJECT_CHECK_VALUE Function Module for









PLM_AUDIT_OBJECT_CHECK_VALUE is a standard plm audit object check value 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 plm audit object check value FM, simply by entering the name PLM_AUDIT_OBJECT_CHECK_VALUE into the relevant SAP transaction such as SE37 or SE38.

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



Function PLM_AUDIT_OBJECT_CHECK_VALUE 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 'PLM_AUDIT_OBJECT_CHECK_VALUE'"
EXPORTING
IV_AUDIT_TYPE = "
IV_OBJECT_TYPE = "
IV_OBJECT_VALUE = "

EXCEPTIONS
VALUE_NOT_ALLOWED = 1
.



IMPORTING Parameters details for PLM_AUDIT_OBJECT_CHECK_VALUE

IV_AUDIT_TYPE -

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

IV_OBJECT_TYPE -

Data type: PLMC_AUDIT_OBJ-OBJECT_TYPE
Optional: No
Call by Reference: Yes

IV_OBJECT_VALUE -

Data type: PLMM_AUDIT_OBJ-OBJECT_VALUE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

VALUE_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PLM_AUDIT_OBJECT_CHECK_VALUE 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_iv_audit_type  TYPE PLMT_AUDIT_TYPE, "   
lv_value_not_allowed  TYPE PLMT_AUDIT_TYPE, "   
lv_iv_object_type  TYPE PLMC_AUDIT_OBJ-OBJECT_TYPE, "   
lv_iv_object_value  TYPE PLMM_AUDIT_OBJ-OBJECT_VALUE. "   

  CALL FUNCTION 'PLM_AUDIT_OBJECT_CHECK_VALUE'  "
    EXPORTING
         IV_AUDIT_TYPE = lv_iv_audit_type
         IV_OBJECT_TYPE = lv_iv_object_type
         IV_OBJECT_VALUE = lv_iv_object_value
    EXCEPTIONS
        VALUE_NOT_ALLOWED = 1
. " PLM_AUDIT_OBJECT_CHECK_VALUE




ABAP code using 7.40 inline data declarations to call FM PLM_AUDIT_OBJECT_CHECK_VALUE

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 OBJECT_TYPE FROM PLMC_AUDIT_OBJ INTO @DATA(ld_iv_object_type).
 
"SELECT single OBJECT_VALUE FROM PLMM_AUDIT_OBJ INTO @DATA(ld_iv_object_value).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!