SAP ISPAM_CONTRACT_GET_CONDVALUE Function Module for IS-M/AM: Determine Amounts for Condition Reference

Search SAP Function Modules

ISPAM_CONTRACT_GET_CONDVALUE is a standard ispam contract get condvalue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/AM: Determine Amounts for Condition Reference 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 ispam contract get condvalue FM, simply by entering the name ISPAM_CONTRACT_GET_CONDVALUE into the relevant SAP transaction such as SE37 or SE38.

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

Function ISPAM_CONTRACT_GET_CONDVALUE 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 'ISPAM_CONTRACT_GET_CONDVALUE'"IS-M/AM: Determine Amounts for Condition Reference
  EXPORTING
   CONTRACT =  "
   XABRUF =  "

 IMPORTING
   BETRAG =  "

TABLES
   SCHEMATABELLE =  "

.

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_SAPLJHAR_001 IS-M/AM: Fill Billing Interfaces Contract-Related
EXIT_SAPLJHAR_002 IS-M: Selection of Assignments for Settlement
EXIT_SAPLJHAR_003 IS-M: Determine Additional Twinned Billing Datasets
EXIT_SAPLJHAR_004 IS-M: Fill Price Fields for Target Document During Contract Settlement
EXIT_SAPLJHAR_005 IS-M: Enter a Split Criterion for P/A Records
EXIT_SAPLJHAR_006 Fill Price fields for the Difference Document During Contract Settlement
EXIT_SAPLJHAR_007 IS-M: Sort Billing Interface for Contract Settlement

IMPORTING Parameters details for ISPAM_CONTRACT_GET_CONDVALUE

CONTRACT -

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

XABRUF -

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

EXPORTING Parameters details for ISPAM_CONTRACT_GET_CONDVALUE

BETRAG -

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

TABLES Parameters details for ISPAM_CONTRACT_GET_CONDVALUE

SCHEMATABELLE -

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

Copy and paste ABAP code example for ISPAM_CONTRACT_GET_CONDVALUE 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.

ABAP code using 7.40 inline data declarations to call FM ISPAM_CONTRACT_GET_CONDVALUE

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