SAP PSC_MOVE_COST Function Module for PSC group cost movement
PSC_MOVE_COST is a standard psc move cost SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PSC group cost movement 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 move cost FM, simply by entering the name PSC_MOVE_COST 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_MOVE_COST 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_MOVE_COST'"PSC group cost movement.
EXPORTING
IG_RESULT = "
IMPORTING
EG_RESULT = "
IMPORTING Parameters details for PSC_MOVE_COST
IG_RESULT -
Data type: PSCTP_IFTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PSC_MOVE_COST
EG_RESULT -
Data type: PSCTP_IFTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PSC_MOVE_COST 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_eg_result | TYPE PSCTP_IFT, " | |||
| lv_ig_result | TYPE PSCTP_IFT. " |
|   CALL FUNCTION 'PSC_MOVE_COST' "PSC group cost movement |
| EXPORTING | ||
| IG_RESULT | = lv_ig_result | |
| IMPORTING | ||
| EG_RESULT | = lv_eg_result | |
| . " PSC_MOVE_COST | ||
ABAP code using 7.40 inline data declarations to call FM PSC_MOVE_COST
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