SAP C142_USAGE_VALUATION_CHECK Function Module for NOTRANSL: EHS: Prüfung auf Vollständigkeit der Bewert.arten z. Status u. d

Search SAP Function Modules

C142_USAGE_VALUATION_CHECK is a standard c142 usage valuation check 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: EHS: Prüfung auf Vollständigkeit der Bewert.arten z. Status u. d 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 c142 usage valuation check FM, simply by entering the name C142_USAGE_VALUATION_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function C142_USAGE_VALUATION_CHECK 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 'C142_USAGE_VALUATION_CHECK'"NOTRANSL: EHS: Prüfung auf Vollständigkeit der Bewert.arten z. Status u. d
  EXPORTING
*  I_ACTYPE =  "Activity Type
   I_ADDINF =  "Change Number and Key Date
   I_KEYPATH =  "Current Object
*  I_TRTYPE =  "Transaction Type
*  I_FLG_DIALOG =  "
*  I_OKCODE = ' ' "

CHANGING
*  X_ADD_PARAMS =  "(Further Parameters)

TABLES
*  I_IOTAB_SAV =  "
   I_IOTAB =  "
*  I_IOTAB_DEL =  "
   E_STATUS_CHANGES_REFUSED_TAB =  "

EXCEPTIONS
   ILLEGAL_INPUT = 1    INTERNAL_ERROR = 2 

.

IMPORTING Parameters details for C142_USAGE_VALUATION_CHECK

I_ACTYPE - Activity Type

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

I_ADDINF - Change Number and Key Date

Data type: RCGADDINF
Optional: No
Call by Reference: No ( called with pass by value option)

I_KEYPATH - Current Object

Data type: RCGKPATH
Optional: No
Call by Reference: No ( called with pass by value option)

I_TRTYPE - Transaction Type

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

I_FLG_DIALOG -

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

I_OKCODE -

Data type: ESP1_OKCODE_TYPE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for C142_USAGE_VALUATION_CHECK

X_ADD_PARAMS - (Further Parameters)

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

TABLES Parameters details for C142_USAGE_VALUATION_CHECK

I_IOTAB_SAV -

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

I_IOTAB -

Data type: RCGSTIOT
Optional: No
Call by Reference: No ( called with pass by value option)

I_IOTAB_DEL -

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

E_STATUS_CHANGES_REFUSED_TAB -

Data type: ESP7_STATUS_REFUSED_TAB_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ILLEGAL_INPUT -

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

INTERNAL_ERROR -

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

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

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