SAP UHC_CALL_CHARGE_POST Function Module for Post Collection Charges









UHC_CALL_CHARGE_POST is a standard uhc call charge post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Post Collection Charges 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 uhc call charge post FM, simply by entering the name UHC_CALL_CHARGE_POST into the relevant SAP transaction such as SE37 or SE38.

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



Function UHC_CALL_CHARGE_POST 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 'UHC_CALL_CHARGE_POST'"Post Collection Charges
EXPORTING
* IM_CASE = "Case: Front End (SAP GUI)
* I_CASE_GUID = "FSCM-DM: GUID (Internal Key of Dispute Case)
IM_MODE = "Processing Mode: C(reate), M(odify), D(isplay)

IMPORTING
E_RETURN = "Return Parameter(s)
E_NEED_REFRESH = "Checkbox
.



IMPORTING Parameters details for UHC_CALL_CHARGE_POST

IM_CASE - Case: Front End (SAP GUI)

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

I_CASE_GUID - FSCM-DM: GUID (Internal Key of Dispute Case)

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

IM_MODE - Processing Mode: C(reate), M(odify), D(isplay)

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

EXPORTING Parameters details for UHC_CALL_CHARGE_POST

E_RETURN - Return Parameter(s)

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

E_NEED_REFRESH - Checkbox

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

Copy and paste ABAP code example for UHC_CALL_CHARGE_POST 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_case  TYPE CL_SCMG_CASE_VISUALIZATION_WIN, "   
lv_e_return  TYPE BAPIRET2, "   
lv_i_case_guid  TYPE BDM_CASE_GUID, "   
lv_e_need_refresh  TYPE XFELD, "   
lv_im_mode  TYPE SCMG_PROCESSING_MODE. "   

  CALL FUNCTION 'UHC_CALL_CHARGE_POST'  "Post Collection Charges
    EXPORTING
         IM_CASE = lv_im_case
         I_CASE_GUID = lv_i_case_guid
         IM_MODE = lv_im_mode
    IMPORTING
         E_RETURN = lv_e_return
         E_NEED_REFRESH = lv_e_need_refresh
. " UHC_CALL_CHARGE_POST




ABAP code using 7.40 inline data declarations to call FM UHC_CALL_CHARGE_POST

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!