SAP PSC_GET_COST_INPUT Function Module for Read costs from PSC ledger









PSC_GET_COST_INPUT is a standard psc get cost input 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 costs from PSC ledger 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 psc get cost input FM, simply by entering the name PSC_GET_COST_INPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function PSC_GET_COST_INPUT 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 'PSC_GET_COST_INPUT'"Read costs from PSC ledger
  EXPORTING
   I_PERIOD =  "
   I_RESULT =  "
   I_YEAR =  "
   I_BUKRS =  "
   I_PSC =  "
   I_PSC_PROD =  "
   I_VNAME =  "Joint Venture
   I_EQGRP =  "Equity group
   I_PER_FROM =  "
   I_YEAR_FROM =  "

 IMPORTING
   E_RESULT =  "

TABLES
   T_CURR =  "
.



IMPORTING Parameters details for PSC_GET_COST_INPUT

I_PERIOD -

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

I_RESULT -

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

I_YEAR -

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

I_BUKRS -

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

I_PSC -

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

I_PSC_PROD -

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

I_VNAME - Joint Venture

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

I_EQGRP - Equity group

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

I_PER_FROM -

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

I_YEAR_FROM -

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

EXPORTING Parameters details for PSC_GET_COST_INPUT

E_RESULT -

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

TABLES Parameters details for PSC_GET_COST_INPUT

T_CURR -

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

Copy and paste ABAP code example for PSC_GET_COST_INPUT 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:
lt_t_curr  TYPE STANDARD TABLE OF PSC_CURR, "   
lv_e_result  TYPE PSCTP_INTERFACE, "   
lv_i_period  TYPE GLU1-POPER, "   
lv_i_result  TYPE PSCTP_INTERFACE, "   
lv_i_year  TYPE GLU1-RYEAR, "   
lv_i_bukrs  TYPE GLU1-BUKRS, "   
lv_i_psc  TYPE T8PSCMSTR-PSC_NAME, "   
lv_i_psc_prod  TYPE T8PSCPROD-PSC_PRODUCT, "   
lv_i_vname  TYPE PSCHD-VNAME, "   
lv_i_eqgrp  TYPE PSCHD-EQGRP, "   
lv_i_per_from  TYPE GLU1-POPER, "   
lv_i_year_from  TYPE GLU1-RYEAR. "   

  CALL FUNCTION 'PSC_GET_COST_INPUT'  "Read costs from PSC ledger
    EXPORTING
         I_PERIOD = lv_i_period
         I_RESULT = lv_i_result
         I_YEAR = lv_i_year
         I_BUKRS = lv_i_bukrs
         I_PSC = lv_i_psc
         I_PSC_PROD = lv_i_psc_prod
         I_VNAME = lv_i_vname
         I_EQGRP = lv_i_eqgrp
         I_PER_FROM = lv_i_per_from
         I_YEAR_FROM = lv_i_year_from
    IMPORTING
         E_RESULT = lv_e_result
    TABLES
         T_CURR = lt_t_curr
. " PSC_GET_COST_INPUT




ABAP code using 7.40 inline data declarations to call FM PSC_GET_COST_INPUT

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 POPER FROM GLU1 INTO @DATA(ld_i_period).
 
 
"SELECT single RYEAR FROM GLU1 INTO @DATA(ld_i_year).
 
"SELECT single BUKRS FROM GLU1 INTO @DATA(ld_i_bukrs).
 
"SELECT single PSC_NAME FROM T8PSCMSTR INTO @DATA(ld_i_psc).
 
"SELECT single PSC_PRODUCT FROM T8PSCPROD INTO @DATA(ld_i_psc_prod).
 
"SELECT single VNAME FROM PSCHD INTO @DATA(ld_i_vname).
 
"SELECT single EQGRP FROM PSCHD INTO @DATA(ld_i_eqgrp).
 
"SELECT single POPER FROM GLU1 INTO @DATA(ld_i_per_from).
 
"SELECT single RYEAR FROM GLU1 INTO @DATA(ld_i_year_from).
 


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!