SAP MAP2E_PKPSHD_TO_BAPI1075_DEV Function Module for NOTRANSL: pkpshd -> bapi1075_dev_data
MAP2E_PKPSHD_TO_BAPI1075_DEV is a standard map2e pkpshd to bapi1075 dev SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: pkpshd -> bapi1075_dev_data 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 map2e pkpshd to bapi1075 dev FM, simply by entering the name MAP2E_PKPSHD_TO_BAPI1075_DEV into the relevant SAP transaction such as SE37 or SE38.
Function Group: MPKW
Program Name: SAPLMPKW
Main Program: SAPLMPKW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP2E_PKPSHD_TO_BAPI1075_DEV 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 'MAP2E_PKPSHD_TO_BAPI1075_DEV'"NOTRANSL: pkpshd -> bapi1075_dev_data.
EXPORTING
PKPSHD = "Deviating Control Cycle Data for Kanban
CHANGING
BAPI1075_DEV_DATA = "
IMPORTING Parameters details for MAP2E_PKPSHD_TO_BAPI1075_DEV
PKPSHD - Deviating Control Cycle Data for Kanban
Data type: PKPSHDOptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP2E_PKPSHD_TO_BAPI1075_DEV
BAPI1075_DEV_DATA -
Data type: BAPI1075_DEV_DATAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAP2E_PKPSHD_TO_BAPI1075_DEV 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_pkpshd | TYPE PKPSHD, " | |||
| lv_bapi1075_dev_data | TYPE BAPI1075_DEV_DATA. " |
|   CALL FUNCTION 'MAP2E_PKPSHD_TO_BAPI1075_DEV' "NOTRANSL: pkpshd -> bapi1075_dev_data |
| EXPORTING | ||
| PKPSHD | = lv_pkpshd | |
| CHANGING | ||
| BAPI1075_DEV_DATA | = lv_bapi1075_dev_data | |
| . " MAP2E_PKPSHD_TO_BAPI1075_DEV | ||
ABAP code using 7.40 inline data declarations to call FM MAP2E_PKPSHD_TO_BAPI1075_DEV
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