SAP TPM_TRG_VAL_AREA_INITIALIZED Function Module for Read Executed and Canceled Initialization Steps









TPM_TRG_VAL_AREA_INITIALIZED is a standard tpm trg val area initialized SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Executed and Canceled Initialization Steps 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 tpm trg val area initialized FM, simply by entering the name TPM_TRG_VAL_AREA_INITIALIZED into the relevant SAP transaction such as SE37 or SE38.

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



Function TPM_TRG_VAL_AREA_INITIALIZED 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 'TPM_TRG_VAL_AREA_INITIALIZED'"Read Executed and Canceled Initialization Steps
EXPORTING
IM_PRODUCT_GROUP = "Product Group
* IM_COMPANY_CODE = "Company Code
* IM_ACCOUNTING_CODE = "Accounting Code
IM_VALUATION_AREA = "Valuation Area
* IM_USE_BUFFER = "lesen über den buffer

IMPORTING
EX_VAL_AREA_INITIALIZED = "Flag zeigt an , ob AccCode, ProdGr, BewBer initialisiert ist
EX_INITIALIZATION_IN_PROGRESS = "Flag zeigt an , ob Initialisierung für AccCode, ProdGr, BewBer z. Zt. läuft

EXCEPTIONS
WRONG_IMPORT_PARAMETER = 1 TR_ACC_CODE_INVALID = 2 TR_ACC_CODE_NOT_FOUND = 3 COMPANY_CODE_NOT_FOUND = 4
.



IMPORTING Parameters details for TPM_TRG_VAL_AREA_INITIALIZED

IM_PRODUCT_GROUP - Product Group

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

IM_COMPANY_CODE - Company Code

Data type: BUKRS
Optional: Yes
Call by Reference: Yes

IM_ACCOUNTING_CODE - Accounting Code

Data type: TPM_ACC_CODE
Optional: Yes
Call by Reference: Yes

IM_VALUATION_AREA - Valuation Area

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

IM_USE_BUFFER - lesen über den buffer

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for TPM_TRG_VAL_AREA_INITIALIZED

EX_VAL_AREA_INITIALIZED - Flag zeigt an , ob AccCode, ProdGr, BewBer initialisiert ist

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

EX_INITIALIZATION_IN_PROGRESS - Flag zeigt an , ob Initialisierung für AccCode, ProdGr, BewBer z. Zt. läuft

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

EXCEPTIONS details

WRONG_IMPORT_PARAMETER - falsche Import Parameter

Data type:
Optional: No
Call by Reference: Yes

TR_ACC_CODE_INVALID - No TR Accounting Code Transferred

Data type:
Optional: No
Call by Reference: Yes

TR_ACC_CODE_NOT_FOUND - TR Accounting Code

Data type:
Optional: No
Call by Reference: Yes

COMPANY_CODE_NOT_FOUND - Company Code not Found for Treasury Accounting Code

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TPM_TRG_VAL_AREA_INITIALIZED 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_im_product_group  TYPE TPM_PRODUCT_GROUP, "   
lv_wrong_import_parameter  TYPE TPM_PRODUCT_GROUP, "   
lv_ex_val_area_initialized  TYPE CHAR1, "   
lv_im_company_code  TYPE BUKRS, "   
lv_tr_acc_code_invalid  TYPE BUKRS, "   
lv_ex_initialization_in_progress  TYPE CHAR1, "   
lv_im_accounting_code  TYPE TPM_ACC_CODE, "   
lv_tr_acc_code_not_found  TYPE TPM_ACC_CODE, "   
lv_im_valuation_area  TYPE TPM_VAL_AREA, "   
lv_company_code_not_found  TYPE TPM_VAL_AREA, "   
lv_im_use_buffer  TYPE CHAR1. "   

  CALL FUNCTION 'TPM_TRG_VAL_AREA_INITIALIZED'  "Read Executed and Canceled Initialization Steps
    EXPORTING
         IM_PRODUCT_GROUP = lv_im_product_group
         IM_COMPANY_CODE = lv_im_company_code
         IM_ACCOUNTING_CODE = lv_im_accounting_code
         IM_VALUATION_AREA = lv_im_valuation_area
         IM_USE_BUFFER = lv_im_use_buffer
    IMPORTING
         EX_VAL_AREA_INITIALIZED = lv_ex_val_area_initialized
         EX_INITIALIZATION_IN_PROGRESS = lv_ex_initialization_in_progress
    EXCEPTIONS
        WRONG_IMPORT_PARAMETER = 1
        TR_ACC_CODE_INVALID = 2
        TR_ACC_CODE_NOT_FOUND = 3
        COMPANY_CODE_NOT_FOUND = 4
. " TPM_TRG_VAL_AREA_INITIALIZED




ABAP code using 7.40 inline data declarations to call FM TPM_TRG_VAL_AREA_INITIALIZED

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



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!