SAP ISM_ISSUES_TO_DATE_CONVERT_2 Function Module for IS-M: Convert Copy Number for Booking Units in a Period

Search SAP Function Modules

ISM_ISSUES_TO_DATE_CONVERT_2 is a standard ism issues to date convert 2 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: Convert Copy Number for Booking Units in a Period 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 ism issues to date convert 2 FM, simply by entering the name ISM_ISSUES_TO_DATE_CONVERT_2 into the relevant SAP transaction such as SE37 or SE38.

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

Function ISM_ISSUES_TO_DATE_CONVERT_2 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 'ISM_ISSUES_TO_DATE_CONVERT_2'"IS-M: Convert Copy Number for Booking Units in a Period
  EXPORTING
*  PT_BELEINH_RANGE =  "
*  PT_JJTBE =  "
   PT_HEFT2NR_RANGE =  "

 IMPORTING
   PV_SELDAT_VON =  "Start of selection period
   PV_SELDAT_BIS =  "End of selection period
   PT_ERSCHDAT =  "
   PT_HEFT_NR_RANGE =  "

EXCEPTIONS
   NO_BELEINH_FOUND = 1    NO_PE_FOUND = 2    COPY_NO_DOESNT_EXIST = 3    WILDCARDS_NOT_ALLOWED = 4 

.

IMPORTING Parameters details for ISM_ISSUES_TO_DATE_CONVERT_2

PT_BELEINH_RANGE -

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

PT_JJTBE -

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

PT_HEFT2NR_RANGE -

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

EXPORTING Parameters details for ISM_ISSUES_TO_DATE_CONVERT_2

PV_SELDAT_VON - Start of selection period

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

PV_SELDAT_BIS - End of selection period

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

PT_ERSCHDAT -

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

PT_HEFT_NR_RANGE -

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

EXCEPTIONS details

NO_BELEINH_FOUND -

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

NO_PE_FOUND -

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

COPY_NO_DOESNT_EXIST -

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

WILDCARDS_NOT_ALLOWED -

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

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

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