SAP SD_ORDER_CREATE_WWW Function Module for NOTRANSL: SD Auftrag anlegen









SD_ORDER_CREATE_WWW is a standard sd order create www 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: SD Auftrag anlegen 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 order create www FM, simply by entering the name SD_ORDER_CREATE_WWW into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_ORDER_CREATE_WWW 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_ORDER_CREATE_WWW'"NOTRANSL: SD Auftrag anlegen
  EXPORTING
   ORDER_HEADER_IN =  "Communication Fields for Maintaining the SD Doc.Header
*  SIMULATION = ' ' "ABAP System Field: Internal Use
*  WITHOUT_COMMIT = ' ' "Without Commit?
*  I_CALL_BAPI = ' ' "Checkbox

 IMPORTING
   RETURN =  "Return Parameter
   ORDER_NUMBER =  "Sales Document
   SOLD_TO_PARTY =  "Sold-to Party View of the Customer Master Record
   SHIP_TO_PARTY =  "Ship-to Party's View of the Customer Master Record
   BILLING_PARTY =  "Payer's View on Customer Master Record

TABLES
*  ORDER_ITEMS_IN =  "Communication Fields: Create SD Document Item: WWW
*  ORDER_CFGS_BLOB =  "BLOB of Configuration (SCE)
*  ORDER_CCARD =  "Communication Table: Means of Payment Order/Billing Doc-ww
*  EXKOMFKZM =  "Communication Table: Means of Payment Order/Billing Document
*  EX_VBEP =  "Sales Document: Schedule Line Data
*  EX_VBUVKOM =  "Communication Structure: Incompletion Log
*  EX_KONVKOM =  "Communication Fields for Maintaining Conditions in the Order
*  ORDER_SCHDL_IN =  "Communication Fields for Maintaining SD Doc. Schedule Lines
*  ORDER_PARTNERS =  "Communications Fields: SD Document Partner: WWW
*  PARTNERADDRESSES =  "BAPI Reference Structure for Addresses (Org./Company)
*  ORDER_ITEMS_OUT =  "Communication Fields: Issue SD Document Item: WWW
*  ORDER_CFGS_REF =  "Instances of Several Configurations
*  ORDER_CFGS_INST =  "Instances of several configurations
*  ORDER_CFGS_PART_OF =  "Part_of entries of several configurations
*  ORDER_CFGS_VALUE =  "Characteristic values of several configurations
.



IMPORTING Parameters details for SD_ORDER_CREATE_WWW

ORDER_HEADER_IN - Communication Fields for Maintaining the SD Doc.Header

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

SIMULATION - ABAP System Field: Internal Use

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

WITHOUT_COMMIT - Without Commit?

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

I_CALL_BAPI - Checkbox

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

EXPORTING Parameters details for SD_ORDER_CREATE_WWW

RETURN - Return Parameter

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

ORDER_NUMBER - Sales Document

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

SOLD_TO_PARTY - Sold-to Party View of the Customer Master Record

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

SHIP_TO_PARTY - Ship-to Party's View of the Customer Master Record

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

BILLING_PARTY - Payer's View on Customer Master Record

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

TABLES Parameters details for SD_ORDER_CREATE_WWW

ORDER_ITEMS_IN - Communication Fields: Create SD Document Item: WWW

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

ORDER_CFGS_BLOB - BLOB of Configuration (SCE)

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

ORDER_CCARD - Communication Table: Means of Payment Order/Billing Doc-ww

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

EXKOMFKZM - Communication Table: Means of Payment Order/Billing Document

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

EX_VBEP - Sales Document: Schedule Line Data

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

EX_VBUVKOM - Communication Structure: Incompletion Log

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

EX_KONVKOM - Communication Fields for Maintaining Conditions in the Order

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

ORDER_SCHDL_IN - Communication Fields for Maintaining SD Doc. Schedule Lines

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

ORDER_PARTNERS - Communications Fields: SD Document Partner: WWW

Data type: VBPAKOM_WW
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

ORDER_ITEMS_OUT - Communication Fields: Issue SD Document Item: WWW

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

ORDER_CFGS_REF - Instances of Several Configurations

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

ORDER_CFGS_INST - Instances of several configurations

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

ORDER_CFGS_PART_OF - Part_of entries of several configurations

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

ORDER_CFGS_VALUE - Characteristic values of several configurations

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

Copy and paste ABAP code example for SD_ORDER_CREATE_WWW 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_return  TYPE BAPIRETURN1, "   
lt_order_items_in  TYPE STANDARD TABLE OF VBAPKOM_WW, "   
lv_order_header_in  TYPE VBAKKOM, "   
lt_order_cfgs_blob  TYPE STANDARD TABLE OF CUXE1CUBLB, "   
lt_order_ccard  TYPE STANDARD TABLE OF KOMFKZM_WW, "   
lt_exkomfkzm  TYPE STANDARD TABLE OF KOMFKZM, "   
lt_ex_vbep  TYPE STANDARD TABLE OF VBEP, "   
lt_ex_vbuvkom  TYPE STANDARD TABLE OF VBUVKOM, "   
lt_ex_konvkom  TYPE STANDARD TABLE OF KONVKOM, "   
lv_simulation  TYPE SY-INPUT, "   SPACE
lv_order_number  TYPE VBAK-VBELN, "   
lt_order_schdl_in  TYPE STANDARD TABLE OF VBEPKOM, "   
lv_sold_to_party  TYPE KUAGV, "   
lt_order_partners  TYPE STANDARD TABLE OF VBPAKOM_WW, "   
lv_without_commit  TYPE BAPI_STAND-NO_COMMIT, "   SPACE
lv_i_call_bapi  TYPE XFELD, "   SPACE
lv_ship_to_party  TYPE KUWEV, "   
lt_partneraddresses  TYPE STANDARD TABLE OF BAPIADDR1, "   
lv_billing_party  TYPE KURGV, "   
lt_order_items_out  TYPE STANDARD TABLE OF VBAPKOM_WE, "   
lt_order_cfgs_ref  TYPE STANDARD TABLE OF CUXE1CUCFG, "   
lt_order_cfgs_inst  TYPE STANDARD TABLE OF CUXE1CUINS, "   
lt_order_cfgs_part_of  TYPE STANDARD TABLE OF CUXE1CUPRT, "   
lt_order_cfgs_value  TYPE STANDARD TABLE OF CUXE1CUVAL. "   

  CALL FUNCTION 'SD_ORDER_CREATE_WWW'  "NOTRANSL: SD Auftrag anlegen
    EXPORTING
         ORDER_HEADER_IN = lv_order_header_in
         SIMULATION = lv_simulation
         WITHOUT_COMMIT = lv_without_commit
         I_CALL_BAPI = lv_i_call_bapi
    IMPORTING
         RETURN = lv_return
         ORDER_NUMBER = lv_order_number
         SOLD_TO_PARTY = lv_sold_to_party
         SHIP_TO_PARTY = lv_ship_to_party
         BILLING_PARTY = lv_billing_party
    TABLES
         ORDER_ITEMS_IN = lt_order_items_in
         ORDER_CFGS_BLOB = lt_order_cfgs_blob
         ORDER_CCARD = lt_order_ccard
         EXKOMFKZM = lt_exkomfkzm
         EX_VBEP = lt_ex_vbep
         EX_VBUVKOM = lt_ex_vbuvkom
         EX_KONVKOM = lt_ex_konvkom
         ORDER_SCHDL_IN = lt_order_schdl_in
         ORDER_PARTNERS = lt_order_partners
         PARTNERADDRESSES = lt_partneraddresses
         ORDER_ITEMS_OUT = lt_order_items_out
         ORDER_CFGS_REF = lt_order_cfgs_ref
         ORDER_CFGS_INST = lt_order_cfgs_inst
         ORDER_CFGS_PART_OF = lt_order_cfgs_part_of
         ORDER_CFGS_VALUE = lt_order_cfgs_value
. " SD_ORDER_CREATE_WWW




ABAP code using 7.40 inline data declarations to call FM SD_ORDER_CREATE_WWW

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 INPUT FROM SY INTO @DATA(ld_simulation).
DATA(ld_simulation) = ' '.
 
"SELECT single VBELN FROM VBAK INTO @DATA(ld_order_number).
 
 
 
 
"SELECT single NO_COMMIT FROM BAPI_STAND INTO @DATA(ld_without_commit).
DATA(ld_without_commit) = ' '.
 
DATA(ld_i_call_bapi) = ' '.
 
 
 
 
 
 
 
 
 


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!