SAP ISP_PAYMENT_MODE_CHECK Function Module for

Search SAP Function Modules

ISP_PAYMENT_MODE_CHECK is a standard isp payment mode check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 isp payment mode check FM, simply by entering the name ISP_PAYMENT_MODE_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_PAYMENT_MODE_CHECK 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 'ISP_PAYMENT_MODE_CHECK'"
  EXPORTING
   ZLSCH =  "
*  XSALES_TAX_ID_NUMBER = ' ' "
   T001_IN =  "
   WAERS =  "
*  AUART =  "
*  AUART_XCCARD = 'X' "
   XRENEWAL =  "
*  I_XTRANSFERHR =  "

 IMPORTING
   T042Z_OUT =  "
   TJK42_OUT =  "

CHANGING
   UEBART =  "
   XKINKASSO =  "
   XCCARD =  "

EXCEPTIONS
   PAYMENT_METHOD_WRONG = 1    PAYMENT_METHOD_MISSING = 2    NO_FOREIGN_CURRENCY = 3    CCARD_NOT_ALLOWED = 4 

.

IMPORTING Parameters details for ISP_PAYMENT_MODE_CHECK

ZLSCH -

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

XSALES_TAX_ID_NUMBER -

Data type: SY-DATAR
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

T001_IN -

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

WAERS -

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

AUART -

Data type: TJAK-AUART
Optional: Yes
Call by Reference: No ( called with pass by value option)

AUART_XCCARD -

Data type: TJAK-XCCARD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

XRENEWAL -

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

I_XTRANSFERHR -

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

EXPORTING Parameters details for ISP_PAYMENT_MODE_CHECK

T042Z_OUT -

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

TJK42_OUT -

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

CHANGING Parameters details for ISP_PAYMENT_MODE_CHECK

UEBART -

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

XKINKASSO -

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

XCCARD -

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

EXCEPTIONS details

PAYMENT_METHOD_WRONG -

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

PAYMENT_METHOD_MISSING -

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

NO_FOREIGN_CURRENCY -

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

CCARD_NOT_ALLOWED -

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

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

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