SAP ISM_CONVERT_DATE_CATGRY_SINGLE Function Module for IS-M/SD: Convert Date Category-Controlled Event

Search SAP Function Modules

ISM_CONVERT_DATE_CATGRY_SINGLE is a standard ism convert date catgry single 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/SD: Convert Date Category-Controlled Event 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 convert date catgry single FM, simply by entering the name ISM_CONVERT_DATE_CATGRY_SINGLE into the relevant SAP transaction such as SE37 or SE38.

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

Function ISM_CONVERT_DATE_CATGRY_SINGLE 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_CONVERT_DATE_CATGRY_SINGLE'"IS-M/SD: Convert Date Category-Controlled Event
  EXPORTING
   I_DRERZ =  "Publication
   I_TERMINTYP =  "
   I_TERMVON =  "
*  I_TERMVONC =  "

 IMPORTING
   E_GUELTIGVON =  "Valid-from Date of Sales Order Item
   E_HEFTNUMVON =  "Copy Number of First Issue to be Delivered

EXCEPTIONS
   DATE_IS_INVALID = 1    COPY_IS_INVALID = 2    INVALID_DRERZ = 3 

.

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_SAPLJK11_001 IS-M/SD: Convert Copy Number to Internal Format

IMPORTING Parameters details for ISM_CONVERT_DATE_CATGRY_SINGLE

I_DRERZ - Publication

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

I_TERMINTYP -

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

I_TERMVON -

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

I_TERMVONC -

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

EXPORTING Parameters details for ISM_CONVERT_DATE_CATGRY_SINGLE

E_GUELTIGVON - Valid-from Date of Sales Order Item

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

E_HEFTNUMVON - Copy Number of First Issue to be Delivered

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

EXCEPTIONS details

DATE_IS_INVALID -

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

COPY_IS_INVALID -

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

INVALID_DRERZ -

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

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

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