SAP GRC01_CONF_DATA_FOR_COSTING Function Module for NOTRANSL: Prüft, ob die Kalkulation Rückmeldedaten der Logistik benötigt









GRC01_CONF_DATA_FOR_COSTING is a standard grc01 conf data for costing 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: Prüft, ob die Kalkulation Rückmeldedaten der Logistik benötigt 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 grc01 conf data for costing FM, simply by entering the name GRC01_CONF_DATA_FOR_COSTING into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRC01
Program Name: SAPLGRC01
Main Program: SAPLGRC01
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function GRC01_CONF_DATA_FOR_COSTING 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 'GRC01_CONF_DATA_FOR_COSTING'"NOTRANSL: Prüft, ob die Kalkulation Rückmeldedaten der Logistik benötigt
  EXPORTING
   IM_KZBWS =  "Valuation of Special Stock
   IM_MATNR =  "Material Number
   IM_WERK =  "Plant
   IM_SOBKZ =  "Special Stock Indicator
   IM_BWTAR =  "Material Master View on Valuation Records
   IM_VBELN =  "Sales and Distribution Document Number
   IM_POSNR =  "Item number of the SD document

 IMPORTING
   EX_NO_NEED =  "New Input Values

EXCEPTIONS
   INVALID = 1    INTERNAL_ERROR = 2
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLGRC01_001

IMPORTING Parameters details for GRC01_CONF_DATA_FOR_COSTING

IM_KZBWS - Valuation of Special Stock

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

IM_MATNR - Material Number

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

IM_WERK - Plant

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

IM_SOBKZ - Special Stock Indicator

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

IM_BWTAR - Material Master View on Valuation Records

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

IM_VBELN - Sales and Distribution Document Number

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

IM_POSNR - Item number of the SD document

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

EXPORTING Parameters details for GRC01_CONF_DATA_FOR_COSTING

EX_NO_NEED - New Input Values

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

EXCEPTIONS details

INVALID - Invalid Input Parameters

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

INTERNAL_ERROR - Internal error

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

Copy and paste ABAP code example for GRC01_CONF_DATA_FOR_COSTING 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_invalid  TYPE STRING, "   
lv_im_kzbws  TYPE KZBWS, "   
lv_ex_no_need  TYPE XFLAG, "   
lv_im_matnr  TYPE MATNR, "   
lv_internal_error  TYPE MATNR, "   
lv_im_werk  TYPE WERKS_D, "   
lv_im_sobkz  TYPE SOBKZ, "   
lv_im_bwtar  TYPE BWTAR, "   
lv_im_vbeln  TYPE VBELN, "   
lv_im_posnr  TYPE POSNR. "   

  CALL FUNCTION 'GRC01_CONF_DATA_FOR_COSTING'  "NOTRANSL: Prüft, ob die Kalkulation Rückmeldedaten der Logistik benötigt
    EXPORTING
         IM_KZBWS = lv_im_kzbws
         IM_MATNR = lv_im_matnr
         IM_WERK = lv_im_werk
         IM_SOBKZ = lv_im_sobkz
         IM_BWTAR = lv_im_bwtar
         IM_VBELN = lv_im_vbeln
         IM_POSNR = lv_im_posnr
    IMPORTING
         EX_NO_NEED = lv_ex_no_need
    EXCEPTIONS
        INVALID = 1
        INTERNAL_ERROR = 2
. " GRC01_CONF_DATA_FOR_COSTING




ABAP code using 7.40 inline data declarations to call FM GRC01_CONF_DATA_FOR_COSTING

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!