SAP SD_VBPA2KOM_FROM_VBPA Function Module for NOTRANSL: Fuellen Kommunikationstruktur VBPA2KOM aus Partnerstruktur VBPA
SD_VBPA2KOM_FROM_VBPA is a standard sd vbpa2kom from vbpa 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: Fuellen Kommunikationstruktur VBPA2KOM aus Partnerstruktur VBPA 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 sd vbpa2kom from vbpa FM, simply by entering the name SD_VBPA2KOM_FROM_VBPA into the relevant SAP transaction such as SE37 or SE38.
Function Group: V09A
Program Name: SAPLV09A
Main Program: SAPLV09A
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_VBPA2KOM_FROM_VBPA 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 'SD_VBPA2KOM_FROM_VBPA'"NOTRANSL: Fuellen Kommunikationstruktur VBPA2KOM aus Partnerstruktur VBPA.
EXPORTING
FIS_VBPA = "Sales Document: Partner
IMPORTING
FES_VBPA2KOM = "Communication Fields for Maintaining Partners in Doc.Header
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_SAPLV09A_001 Duplicate/Use as a Referene: Decision Making Manual Address
EXIT_SAPLV09A_002 EXIT in NO_KNVV for Partner Type
EXIT_SAPLV09A_003 User Exit Partner Determination (Entry Mode XYZ)
EXIT_SAPLV09A_004 U.Exit for Part. Determ.(before entering determined partner)
IMPORTING Parameters details for SD_VBPA2KOM_FROM_VBPA
FIS_VBPA - Sales Document: Partner
Data type: VBPAOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SD_VBPA2KOM_FROM_VBPA
FES_VBPA2KOM - Communication Fields for Maintaining Partners in Doc.Header
Data type: VBPA2KOMOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_VBPA2KOM_FROM_VBPA 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_fis_vbpa | TYPE VBPA, " | |||
| lv_fes_vbpa2kom | TYPE VBPA2KOM. " |
|   CALL FUNCTION 'SD_VBPA2KOM_FROM_VBPA' "NOTRANSL: Fuellen Kommunikationstruktur VBPA2KOM aus Partnerstruktur VBPA |
| EXPORTING | ||
| FIS_VBPA | = lv_fis_vbpa | |
| IMPORTING | ||
| FES_VBPA2KOM | = lv_fes_vbpa2kom | |
| . " SD_VBPA2KOM_FROM_VBPA | ||
ABAP code using 7.40 inline data declarations to call FM SD_VBPA2KOM_FROM_VBPA
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