SAP MS_CD_FOR_PACKNO Function Module for Read changes to package
MS_CD_FOR_PACKNO is a standard ms cd for packno SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read changes to package 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 ms cd for packno FM, simply by entering the name MS_CD_FOR_PACKNO into the relevant SAP transaction such as SE37 or SE38.
Function Group: MLPR
Program Name: SAPLMLPR
Main Program: SAPLMLPR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MS_CD_FOR_PACKNO 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 'MS_CD_FOR_PACKNO'"Read changes to package.
EXPORTING
PACKNO = "
EBELN = "
BSTYP = "
EXCEPTIONS
NO_CD_FOUND = 1
IMPORTING Parameters details for MS_CD_FOR_PACKNO
PACKNO -
Data type: ESLL-PACKNOOptional: No
Call by Reference: No ( called with pass by value option)
EBELN -
Data type: EKKO-EBELNOptional: No
Call by Reference: No ( called with pass by value option)
BSTYP -
Data type: EKKO-BSTYPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_CD_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MS_CD_FOR_PACKNO 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_packno | TYPE ESLL-PACKNO, " | |||
| lv_no_cd_found | TYPE ESLL, " | |||
| lv_ebeln | TYPE EKKO-EBELN, " | |||
| lv_bstyp | TYPE EKKO-BSTYP. " |
|   CALL FUNCTION 'MS_CD_FOR_PACKNO' "Read changes to package |
| EXPORTING | ||
| PACKNO | = lv_packno | |
| EBELN | = lv_ebeln | |
| BSTYP | = lv_bstyp | |
| EXCEPTIONS | ||
| NO_CD_FOUND = 1 | ||
| . " MS_CD_FOR_PACKNO | ||
ABAP code using 7.40 inline data declarations to call FM MS_CD_FOR_PACKNO
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 PACKNO FROM ESLL INTO @DATA(ld_packno). | ||||
| "SELECT single EBELN FROM EKKO INTO @DATA(ld_ebeln). | ||||
| "SELECT single BSTYP FROM EKKO INTO @DATA(ld_bstyp). | ||||
Search for further information about these or an SAP related objects