SAP SD_SALES_DOCU_MAINTAIN_DIALOG Function Module for NOTRANSL: Anlegen Verkaufsbeleg im Dialog mit Datenvorschlag









SD_SALES_DOCU_MAINTAIN_DIALOG is a standard sd sales docu maintain dialog 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: Anlegen Verkaufsbeleg im Dialog mit Datenvorschlag 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 sales docu maintain dialog FM, simply by entering the name SD_SALES_DOCU_MAINTAIN_DIALOG into the relevant SAP transaction such as SE37 or SE38.

Function Group: V45J
Program Name: SAPLV45J
Main Program: SAPLV45J
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SD_SALES_DOCU_MAINTAIN_DIALOG 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_SALES_DOCU_MAINTAIN_DIALOG'"NOTRANSL: Anlegen Verkaufsbeleg im Dialog mit Datenvorschlag
  EXPORTING
   I_VBAKKOM =  "
*  I_VBAKKOMX =  "
*  I_VBAKKOM_REF =  "
*  SYNCHRONOUS = ' ' "Synchronous update
*  I_POSNR = ' ' "Internal Item Number Assignment
*  MESSAGE_TYPE = 'S' "

 IMPORTING
   E_DOCUMENT_NUMBER =  "

TABLES
*  IX_VBAPKOM =  "Item Data
*  SALES_CFGS_INST =  "Configuration: Instances
*  SALES_CFGS_PART_OF =  "Configuration: Part-of Specifications
*  SALES_CFGS_VALUE =  "Configuration: Characteristic Values
*  SALES_CFGS_BLOB =  "
*  PARTNERADDRESSES =  "BAPI Reference Structure for Addresses (Org./Company)
*  IX_VBPAKOM =  "Partner Data
*  IX_KOMFKZM =  "Credit Card Data
*  IX_VBAPKOMX =  "Change List Item Data
*  IX_VBEPKOM =  "Schedule Line Data
*  IX_VBEPKOMX =  "
*  IX_KONVKOM =  "Conditions
*  IX_KONVKOMX =  "
*  SALES_CFGS_REF =  "Configuration: Reference Data
.



IMPORTING Parameters details for SD_SALES_DOCU_MAINTAIN_DIALOG

I_VBAKKOM -

Data type: VBAKKOM
Optional: No
Call by Reference: No ( called with pass by value option)

I_VBAKKOMX -

Data type: VBAKKOMX
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VBAKKOM_REF -

Data type: VBAKKOM_REF
Optional: Yes
Call by Reference: No ( called with pass by value option)

SYNCHRONOUS - Synchronous update

Data type: BAPIFLAG-BAPIFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_POSNR - Internal Item Number Assignment

Data type: BAPIFLAG-BAPIFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MESSAGE_TYPE -

Data type: BAPIFLAG-BAPIFLAG
Default: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SD_SALES_DOCU_MAINTAIN_DIALOG

E_DOCUMENT_NUMBER -

Data type: VBAK-VBELN
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SD_SALES_DOCU_MAINTAIN_DIALOG

IX_VBAPKOM - Item Data

Data type: VBAPKOM
Optional: Yes
Call by Reference: No ( called with pass by value option)

SALES_CFGS_INST - Configuration: Instances

Data type: CUXE1CUINS
Optional: Yes
Call by Reference: No ( called with pass by value option)

SALES_CFGS_PART_OF - Configuration: Part-of Specifications

Data type: CUXE1CUPRT
Optional: Yes
Call by Reference: No ( called with pass by value option)

SALES_CFGS_VALUE - Configuration: Characteristic Values

Data type: CUXE1CUVAL
Optional: Yes
Call by Reference: No ( called with pass by value option)

SALES_CFGS_BLOB -

Data type: CUXE1CUBLB
Optional: Yes
Call by Reference: No ( called with pass by value option)

PARTNERADDRESSES - BAPI Reference Structure for Addresses (Org./Company)

Data type: BAPIADDR1
Optional: Yes
Call by Reference: Yes

IX_VBPAKOM - Partner Data

Data type: VBPAKOM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_KOMFKZM - Credit Card Data

Data type: KOMFKZM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_VBAPKOMX - Change List Item Data

Data type: VBAPKOMX
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_VBEPKOM - Schedule Line Data

Data type: VBEPKOM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_VBEPKOMX -

Data type: VBEPKOMX
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_KONVKOM - Conditions

Data type: KONVKOM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_KONVKOMX -

Data type: KONVKOMX
Optional: Yes
Call by Reference: No ( called with pass by value option)

SALES_CFGS_REF - Configuration: Reference Data

Data type: CUXE1CUCFG
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for SD_SALES_DOCU_MAINTAIN_DIALOG 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_vbakkom  TYPE VBAKKOM, "   
lt_ix_vbapkom  TYPE STANDARD TABLE OF VBAPKOM, "   
lv_e_document_number  TYPE VBAK-VBELN, "   
lt_sales_cfgs_inst  TYPE STANDARD TABLE OF CUXE1CUINS, "   
lt_sales_cfgs_part_of  TYPE STANDARD TABLE OF CUXE1CUPRT, "   
lt_sales_cfgs_value  TYPE STANDARD TABLE OF CUXE1CUVAL, "   
lt_sales_cfgs_blob  TYPE STANDARD TABLE OF CUXE1CUBLB, "   
lt_partneraddresses  TYPE STANDARD TABLE OF BAPIADDR1, "   
lt_ix_vbpakom  TYPE STANDARD TABLE OF VBPAKOM, "   
lv_i_vbakkomx  TYPE VBAKKOMX, "   
lt_ix_komfkzm  TYPE STANDARD TABLE OF KOMFKZM, "   
lv_i_vbakkom_ref  TYPE VBAKKOM_REF, "   
lt_ix_vbapkomx  TYPE STANDARD TABLE OF VBAPKOMX, "   
lv_synchronous  TYPE BAPIFLAG-BAPIFLAG, "   SPACE
lv_i_posnr  TYPE BAPIFLAG-BAPIFLAG, "   SPACE
lt_ix_vbepkom  TYPE STANDARD TABLE OF VBEPKOM, "   
lt_ix_vbepkomx  TYPE STANDARD TABLE OF VBEPKOMX, "   
lv_message_type  TYPE BAPIFLAG-BAPIFLAG, "   'S'
lt_ix_konvkom  TYPE STANDARD TABLE OF KONVKOM, "   
lt_ix_konvkomx  TYPE STANDARD TABLE OF KONVKOMX, "   
lt_sales_cfgs_ref  TYPE STANDARD TABLE OF CUXE1CUCFG. "   

  CALL FUNCTION 'SD_SALES_DOCU_MAINTAIN_DIALOG'  "NOTRANSL: Anlegen Verkaufsbeleg im Dialog mit Datenvorschlag
    EXPORTING
         I_VBAKKOM = lv_i_vbakkom
         I_VBAKKOMX = lv_i_vbakkomx
         I_VBAKKOM_REF = lv_i_vbakkom_ref
         SYNCHRONOUS = lv_synchronous
         I_POSNR = lv_i_posnr
         MESSAGE_TYPE = lv_message_type
    IMPORTING
         E_DOCUMENT_NUMBER = lv_e_document_number
    TABLES
         IX_VBAPKOM = lt_ix_vbapkom
         SALES_CFGS_INST = lt_sales_cfgs_inst
         SALES_CFGS_PART_OF = lt_sales_cfgs_part_of
         SALES_CFGS_VALUE = lt_sales_cfgs_value
         SALES_CFGS_BLOB = lt_sales_cfgs_blob
         PARTNERADDRESSES = lt_partneraddresses
         IX_VBPAKOM = lt_ix_vbpakom
         IX_KOMFKZM = lt_ix_komfkzm
         IX_VBAPKOMX = lt_ix_vbapkomx
         IX_VBEPKOM = lt_ix_vbepkom
         IX_VBEPKOMX = lt_ix_vbepkomx
         IX_KONVKOM = lt_ix_konvkom
         IX_KONVKOMX = lt_ix_konvkomx
         SALES_CFGS_REF = lt_sales_cfgs_ref
. " SD_SALES_DOCU_MAINTAIN_DIALOG




ABAP code using 7.40 inline data declarations to call FM SD_SALES_DOCU_MAINTAIN_DIALOG

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 VBELN FROM VBAK INTO @DATA(ld_e_document_number).
 
 
 
 
 
 
 
 
 
 
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_synchronous).
DATA(ld_synchronous) = ' '.
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_i_posnr).
DATA(ld_i_posnr) = ' '.
 
 
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_message_type).
DATA(ld_message_type) = 'S'.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!