SAP CNM2_PBDNR Function Module for NOTRANSL: Lieferant bearbeiten
CNM2_PBDNR is a standard cnm2 pbdnr 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: Lieferant bearbeiten 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 cnm2 pbdnr FM, simply by entering the name CNM2_PBDNR into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNM2
Program Name: SAPLCNM2
Main Program: SAPLCNM2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNM2_PBDNR 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 'CNM2_PBDNR'"NOTRANSL: Lieferant bearbeiten.
EXPORTING
I_PBDNR = "Requirements Plan Number
* I_DISPLAY = 'X' "Generic Type
I_WERKS = "Plant
IMPORTING Parameters details for CNM2_PBDNR
I_PBDNR - Requirements Plan Number
Data type: RESB-PBDNROptional: No
Call by Reference: Yes
I_DISPLAY - Generic Type
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
I_WERKS - Plant
Data type: RESB-WERKSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNM2_PBDNR 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_i_pbdnr | TYPE RESB-PBDNR, " | |||
| lv_i_display | TYPE C, " 'X' | |||
| lv_i_werks | TYPE RESB-WERKS. " |
|   CALL FUNCTION 'CNM2_PBDNR' "NOTRANSL: Lieferant bearbeiten |
| EXPORTING | ||
| I_PBDNR | = lv_i_pbdnr | |
| I_DISPLAY | = lv_i_display | |
| I_WERKS | = lv_i_werks | |
| . " CNM2_PBDNR | ||
ABAP code using 7.40 inline data declarations to call FM CNM2_PBDNR
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 PBDNR FROM RESB INTO @DATA(ld_i_pbdnr). | ||||
| DATA(ld_i_display) | = 'X'. | |||
| "SELECT single WERKS FROM RESB INTO @DATA(ld_i_werks). | ||||
Search for further information about these or an SAP related objects