SAP EXIT_SAPMJ45A_010 Function Module for IS-M/SD: Determine/Change Rate Code
EXIT_SAPMJ45A_010 is a standard exit sapmj45a 010 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: Determine/Change Rate Code 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 exit sapmj45a 010 FM, simply by entering the name EXIT_SAPMJ45A_010 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XJK1
Program Name: SAPLXJK1
Main Program: SAPLXJK1
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPMJ45A_010 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 'EXIT_SAPMJ45A_010'"IS-M/SD: Determine/Change Rate Code.
EXPORTING
CJKAK = "Order Header
CJKAP = "Order Item
CJKEP = "Schedule Line
CJKKD = "Business Data on Item
CJKPROM = "Introduction Data
* CJKAP_VG = "Preceding Item
* CJKKD_VG = "Business Data on Previous Item
* CJKEP_VG = "Schedule Line for Previous Item
CZLSCH = "IS-M: Payment Method
CHANGING
RCODE = "Rate Code
TABLES
XJKAP = "Reference Structure for XJKAP
XJKKD = "Reference Structure for XJKKD / YJKKD
XJKEP = "IS-M/SD: Reference Structure for XJKEP
XJKPA = "Reference Structure for XJKPA
XJKREMIND = "Reference Structure for XJKREMIND/YJKREMIND
IMPORTING Parameters details for EXIT_SAPMJ45A_010
CJKAK - Order Header
Data type: JKAKOptional: No
Call by Reference: No ( called with pass by value option)
CJKAP - Order Item
Data type: JKAPOptional: No
Call by Reference: No ( called with pass by value option)
CJKEP - Schedule Line
Data type: JKEPOptional: No
Call by Reference: No ( called with pass by value option)
CJKKD - Business Data on Item
Data type: JKKDOptional: No
Call by Reference: No ( called with pass by value option)
CJKPROM - Introduction Data
Data type: JKPROMOptional: No
Call by Reference: No ( called with pass by value option)
CJKAP_VG - Preceding Item
Data type: JKAPOptional: Yes
Call by Reference: No ( called with pass by value option)
CJKKD_VG - Business Data on Previous Item
Data type: JKKDOptional: Yes
Call by Reference: No ( called with pass by value option)
CJKEP_VG - Schedule Line for Previous Item
Data type: JKEPOptional: Yes
Call by Reference: No ( called with pass by value option)
CZLSCH - IS-M: Payment Method
Data type: RJKRG-ZLSCHOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EXIT_SAPMJ45A_010
RCODE - Rate Code
Data type: JKKD-RCODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPMJ45A_010
XJKAP - Reference Structure for XJKAP
Data type: JKAPVBOptional: No
Call by Reference: Yes
XJKKD - Reference Structure for XJKKD / YJKKD
Data type: JKKDVBOptional: No
Call by Reference: Yes
XJKEP - IS-M/SD: Reference Structure for XJKEP
Data type: JKEPVBOptional: No
Call by Reference: Yes
XJKPA - Reference Structure for XJKPA
Data type: JKPAVBOptional: No
Call by Reference: Yes
XJKREMIND - Reference Structure for XJKREMIND/YJKREMIND
Data type: JKREMINDVBOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPMJ45A_010 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_cjkak | TYPE JKAK, " | |||
| lv_rcode | TYPE JKKD-RCODE, " | |||
| lt_xjkap | TYPE STANDARD TABLE OF JKAPVB, " | |||
| lv_cjkap | TYPE JKAP, " | |||
| lt_xjkkd | TYPE STANDARD TABLE OF JKKDVB, " | |||
| lv_cjkep | TYPE JKEP, " | |||
| lt_xjkep | TYPE STANDARD TABLE OF JKEPVB, " | |||
| lv_cjkkd | TYPE JKKD, " | |||
| lt_xjkpa | TYPE STANDARD TABLE OF JKPAVB, " | |||
| lv_cjkprom | TYPE JKPROM, " | |||
| lt_xjkremind | TYPE STANDARD TABLE OF JKREMINDVB, " | |||
| lv_cjkap_vg | TYPE JKAP, " | |||
| lv_cjkkd_vg | TYPE JKKD, " | |||
| lv_cjkep_vg | TYPE JKEP, " | |||
| lv_czlsch | TYPE RJKRG-ZLSCH. " |
|   CALL FUNCTION 'EXIT_SAPMJ45A_010' "IS-M/SD: Determine/Change Rate Code |
| EXPORTING | ||
| CJKAK | = lv_cjkak | |
| CJKAP | = lv_cjkap | |
| CJKEP | = lv_cjkep | |
| CJKKD | = lv_cjkkd | |
| CJKPROM | = lv_cjkprom | |
| CJKAP_VG | = lv_cjkap_vg | |
| CJKKD_VG | = lv_cjkkd_vg | |
| CJKEP_VG | = lv_cjkep_vg | |
| CZLSCH | = lv_czlsch | |
| CHANGING | ||
| RCODE | = lv_rcode | |
| TABLES | ||
| XJKAP | = lt_xjkap | |
| XJKKD | = lt_xjkkd | |
| XJKEP | = lt_xjkep | |
| XJKPA | = lt_xjkpa | |
| XJKREMIND | = lt_xjkremind | |
| . " EXIT_SAPMJ45A_010 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMJ45A_010
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 RCODE FROM JKKD INTO @DATA(ld_rcode). | ||||
| "SELECT single ZLSCH FROM RJKRG INTO @DATA(ld_czlsch). | ||||
Search for further information about these or an SAP related objects