SAP ISP_HELP_JDTBEZTYP Function Module for Input Help for Mix Type According to Mix Offer (Mix Type for Each Edition)









ISP_HELP_JDTBEZTYP is a standard isp help jdtbeztyp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Input Help for Mix Type According to Mix Offer (Mix Type for Each Edition) 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 isp help jdtbeztyp FM, simply by entering the name ISP_HELP_JDTBEZTYP into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_HELP_JDTBEZTYP 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_HELP_JDTBEZTYP'"Input Help for Mix Type According to Mix Offer (Mix Type for Each Edition)
  EXPORTING
*  BEZPER = ' ' "
*  DESCRIPTION_IN = ' ' "Label
*  DRERZ = ' ' "Publication
*  FIELD_IN = ' ' "
*  LIEFERART = ' ' "Delivery Type
*  PVA = ' ' "Edition
*  TRTYP = 'V' "Transaction Type

 IMPORTING
   DESCRIPTION =  "Label
   FIELD =  "

EXCEPTIONS
   NO_DATA_FOUND = 1
.



IMPORTING Parameters details for ISP_HELP_JDTBEZTYP

BEZPER -

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

DESCRIPTION_IN - Label

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

DRERZ - Publication

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

FIELD_IN -

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

LIEFERART - Delivery Type

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

PVA - Edition

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

TRTYP - Transaction Type

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

EXPORTING Parameters details for ISP_HELP_JDTBEZTYP

DESCRIPTION - Label

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

FIELD -

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

EXCEPTIONS details

NO_DATA_FOUND - No data available

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

Copy and paste ABAP code example for ISP_HELP_JDTBEZTYP 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_bezper  TYPE JDTBZANG-BZPER, "   ' '
lv_description  TYPE JDTBZANG, "   
lv_no_data_found  TYPE JDTBZANG, "   
lv_field  TYPE JDTBZANG, "   
lv_description_in  TYPE JDTBZANG, "   ' '
lv_drerz  TYPE JDTBZANG-DRERZ, "   ' '
lv_field_in  TYPE JDTBZANG, "   ' '
lv_lieferart  TYPE JDTBZANG-LFART, "   ' '
lv_pva  TYPE JDTBZANG-PVA, "   ' '
lv_trtyp  TYPE JDTBZANG. "   'V'

  CALL FUNCTION 'ISP_HELP_JDTBEZTYP'  "Input Help for Mix Type According to Mix Offer (Mix Type for Each Edition)
    EXPORTING
         BEZPER = lv_bezper
         DESCRIPTION_IN = lv_description_in
         DRERZ = lv_drerz
         FIELD_IN = lv_field_in
         LIEFERART = lv_lieferart
         PVA = lv_pva
         TRTYP = lv_trtyp
    IMPORTING
         DESCRIPTION = lv_description
         FIELD = lv_field
    EXCEPTIONS
        NO_DATA_FOUND = 1
. " ISP_HELP_JDTBEZTYP




ABAP code using 7.40 inline data declarations to call FM ISP_HELP_JDTBEZTYP

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 BZPER FROM JDTBZANG INTO @DATA(ld_bezper).
DATA(ld_bezper) = ' '.
 
 
 
 
DATA(ld_description_in) = ' '.
 
"SELECT single DRERZ FROM JDTBZANG INTO @DATA(ld_drerz).
DATA(ld_drerz) = ' '.
 
DATA(ld_field_in) = ' '.
 
"SELECT single LFART FROM JDTBZANG INTO @DATA(ld_lieferart).
DATA(ld_lieferart) = ' '.
 
"SELECT single PVA FROM JDTBZANG INTO @DATA(ld_pva).
DATA(ld_pva) = ' '.
 
DATA(ld_trtyp) = 'V'.
 


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!