SAP BAPI_SALESORDER_PROXY_CREATE Function Module for Proxy BAPI for Request Upload in SFA Context: Create









BAPI_SALESORDER_PROXY_CREATE is a standard bapi salesorder proxy create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Proxy BAPI for Request Upload in SFA Context: Create 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 bapi salesorder proxy create FM, simply by entering the name BAPI_SALESORDER_PROXY_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRMA
Program Name: SAPLCRMA
Main Program: SAPLCRMA
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_SALESORDER_PROXY_CREATE 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 'BAPI_SALESORDER_PROXY_CREATE'"Proxy BAPI for Request Upload in SFA Context: Create
  EXPORTING
   I_UPLOAD_ID =  "Upload Flag
*  I_INT_NUMBER_ASSIGNMENT = 'X' "Internal Item Number Assignment
*  I_BEHAVE_WHEN_ERROR = 'R' "Error Handling
*  I_LOGIC_SWITCH =  "Internal Control Parameter
*  I_TESTRUN =  "Test Run
   I_DESTIN =  "RFC Destination of SFA Server
   I_SFA_REL =  "R/3 Release of SFA Server
*  I_KEYWORD_IN =  "
*  I_SALESDOCUMENT =  "Sales Document Number
   I_ORDER_HEADER_IN =  "Order Header
*  I_ORDER_HEADER_INX =  "Sales Order Check List
*  I_SENDER =  "Logical System - Sender
*  I_BINARY_RELATIONSHIPTYPE =  "Binary Relationship type (private)

 IMPORTING
   E_STATUS =  "Return Status of BAPI
   E_SALESDOCUMENT_EX =  "Number of Generated Document

TABLES
   TI_SFA_KEYS =  "Assignment of BAPI Structure to Tables
*  TI_ORDER_CFGS_INST =  "Configuration: Instances
*  TI_ORDER_CFGS_PART_OF =  "Configuration: Part-of Specifications
*  TI_ORDER_CFGS_VALUE =  "Configuration: Characteristic Values
*  TI_ORDER_CFGS_BLOB =  "Configuration: BLOB Internal Data (SCE)
*  TI_ORDER_CFGS_VK =  "
*  TI_ORDER_CFGS_REFINST =  "
*  TI_ORDER_CCARD =  "Credit Card Data
*  TI_ORDER_TEXT =  "Texts
*  TO_ORDER_KEYS =  "Output Table of Reference Keys
*  TI_EXTENSIONIN =  "Customer Enhancment Import
*  RETURN =  "Return Messages
*  TI_ORDER_ITEMS_IN =  "Item Data
*  TI_ORDER_ITEMS_INX =  "Checkbox Item Data
*  TI_ORDER_PARTNERS =  "Document Partner
*  TI_ORDER_SCHEDULES_IN =  "Schedule Line Data
*  TI_ORDER_SCHEDULES_INX =  "Checkbox Schedule Line Data
*  TI_ORDER_CONDITIONS_IN =  "Conditions
*  TI_ORDER_CFGS_REF =  "Configuration: Reference Data
.



IMPORTING Parameters details for BAPI_SALESORDER_PROXY_CREATE

I_UPLOAD_ID - Upload Flag

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

I_INT_NUMBER_ASSIGNMENT - Internal Item Number Assignment

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

I_BEHAVE_WHEN_ERROR - Error Handling

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

I_LOGIC_SWITCH - Internal Control Parameter

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

I_TESTRUN - Test Run

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

I_DESTIN - RFC Destination of SFA Server

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

I_SFA_REL - R/3 Release of SFA Server

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

I_KEYWORD_IN -

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

I_SALESDOCUMENT - Sales Document Number

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

I_ORDER_HEADER_IN - Order Header

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

I_ORDER_HEADER_INX - Sales Order Check List

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

I_SENDER - Logical System - Sender

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

I_BINARY_RELATIONSHIPTYPE - Binary Relationship type (private)

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

EXPORTING Parameters details for BAPI_SALESORDER_PROXY_CREATE

E_STATUS - Return Status of BAPI

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

E_SALESDOCUMENT_EX - Number of Generated Document

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

TABLES Parameters details for BAPI_SALESORDER_PROXY_CREATE

TI_SFA_KEYS - Assignment of BAPI Structure to Tables

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

TI_ORDER_CFGS_INST - Configuration: Instances

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

TI_ORDER_CFGS_PART_OF - Configuration: Part-of Specifications

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

TI_ORDER_CFGS_VALUE - Configuration: Characteristic Values

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

TI_ORDER_CFGS_BLOB - Configuration: BLOB Internal Data (SCE)

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

TI_ORDER_CFGS_VK -

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

TI_ORDER_CFGS_REFINST -

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

TI_ORDER_CCARD - Credit Card Data

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

TI_ORDER_TEXT - Texts

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

TO_ORDER_KEYS - Output Table of Reference Keys

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

TI_EXTENSIONIN - Customer Enhancment Import

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

RETURN - Return Messages

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

TI_ORDER_ITEMS_IN - Item Data

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

TI_ORDER_ITEMS_INX - Checkbox Item Data

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

TI_ORDER_PARTNERS - Document Partner

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

TI_ORDER_SCHEDULES_IN - Schedule Line Data

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

TI_ORDER_SCHEDULES_INX - Checkbox Schedule Line Data

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

TI_ORDER_CONDITIONS_IN - Conditions

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

TI_ORDER_CFGS_REF - Configuration: Reference Data

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

Copy and paste ABAP code example for BAPI_SALESORDER_PROXY_CREATE 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_e_status  TYPE CRM_PARA-UPLOADSTAT, "   
lv_i_upload_id  TYPE BAPICRMDH2-REF_ID, "   
lt_ti_sfa_keys  TYPE STANDARD TABLE OF BAPICRMSFK, "   
lt_ti_order_cfgs_inst  TYPE STANDARD TABLE OF BAPICUINS, "   
lv_i_int_number_assignment  TYPE BAPIFLAG-BAPIFLAG, "   'X'
lv_i_behave_when_error  TYPE BAPIFLAG-BAPIFLAG, "   'R'
lt_ti_order_cfgs_part_of  TYPE STANDARD TABLE OF BAPICUPRT, "   
lv_i_logic_switch  TYPE BAPISDLS, "   
lt_ti_order_cfgs_value  TYPE STANDARD TABLE OF BAPICUVAL, "   
lv_i_testrun  TYPE BAPIFLAG-BAPIFLAG, "   
lt_ti_order_cfgs_blob  TYPE STANDARD TABLE OF BAPICUBLB, "   
lt_ti_order_cfgs_vk  TYPE STANDARD TABLE OF BAPICUVK, "   
lt_ti_order_cfgs_refinst  TYPE STANDARD TABLE OF BAPICUREF, "   
lt_ti_order_ccard  TYPE STANDARD TABLE OF BAPICCARD, "   
lt_ti_order_text  TYPE STANDARD TABLE OF BAPISDTEXT, "   
lt_to_order_keys  TYPE STANDARD TABLE OF BAPISDKEY, "   
lt_ti_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_i_destin  TYPE CRM_PARA-RFCSERVER, "   
lv_e_salesdocument_ex  TYPE BAPIVBELN-VBELN, "   
lv_i_sfa_rel  TYPE CRM_PARA-SERVER_REL, "   
lt_ti_order_items_in  TYPE STANDARD TABLE OF BAPISDITM, "   
lv_i_keyword_in  TYPE BAPICRMDH1-KEYWORD_IN, "   
lt_ti_order_items_inx  TYPE STANDARD TABLE OF BAPISDITMX, "   
lv_i_salesdocument  TYPE BAPIVBELN-VBELN, "   
lt_ti_order_partners  TYPE STANDARD TABLE OF BAPIPARNR, "   
lv_i_order_header_in  TYPE BAPISDHD1, "   
lt_ti_order_schedules_in  TYPE STANDARD TABLE OF BAPISCHDL, "   
lv_i_order_header_inx  TYPE BAPISDHD1X, "   
lt_ti_order_schedules_inx  TYPE STANDARD TABLE OF BAPISCHDLX, "   
lv_i_sender  TYPE BDI_LOGSYS, "   
lt_ti_order_conditions_in  TYPE STANDARD TABLE OF BAPICOND, "   
lt_ti_order_cfgs_ref  TYPE STANDARD TABLE OF BAPICUCFG, "   
lv_i_binary_relationshiptype  TYPE BRELTYP-RELTYPE. "   

  CALL FUNCTION 'BAPI_SALESORDER_PROXY_CREATE'  "Proxy BAPI for Request Upload in SFA Context: Create
    EXPORTING
         I_UPLOAD_ID = lv_i_upload_id
         I_INT_NUMBER_ASSIGNMENT = lv_i_int_number_assignment
         I_BEHAVE_WHEN_ERROR = lv_i_behave_when_error
         I_LOGIC_SWITCH = lv_i_logic_switch
         I_TESTRUN = lv_i_testrun
         I_DESTIN = lv_i_destin
         I_SFA_REL = lv_i_sfa_rel
         I_KEYWORD_IN = lv_i_keyword_in
         I_SALESDOCUMENT = lv_i_salesdocument
         I_ORDER_HEADER_IN = lv_i_order_header_in
         I_ORDER_HEADER_INX = lv_i_order_header_inx
         I_SENDER = lv_i_sender
         I_BINARY_RELATIONSHIPTYPE = lv_i_binary_relationshiptype
    IMPORTING
         E_STATUS = lv_e_status
         E_SALESDOCUMENT_EX = lv_e_salesdocument_ex
    TABLES
         TI_SFA_KEYS = lt_ti_sfa_keys
         TI_ORDER_CFGS_INST = lt_ti_order_cfgs_inst
         TI_ORDER_CFGS_PART_OF = lt_ti_order_cfgs_part_of
         TI_ORDER_CFGS_VALUE = lt_ti_order_cfgs_value
         TI_ORDER_CFGS_BLOB = lt_ti_order_cfgs_blob
         TI_ORDER_CFGS_VK = lt_ti_order_cfgs_vk
         TI_ORDER_CFGS_REFINST = lt_ti_order_cfgs_refinst
         TI_ORDER_CCARD = lt_ti_order_ccard
         TI_ORDER_TEXT = lt_ti_order_text
         TO_ORDER_KEYS = lt_to_order_keys
         TI_EXTENSIONIN = lt_ti_extensionin
         RETURN = lt_return
         TI_ORDER_ITEMS_IN = lt_ti_order_items_in
         TI_ORDER_ITEMS_INX = lt_ti_order_items_inx
         TI_ORDER_PARTNERS = lt_ti_order_partners
         TI_ORDER_SCHEDULES_IN = lt_ti_order_schedules_in
         TI_ORDER_SCHEDULES_INX = lt_ti_order_schedules_inx
         TI_ORDER_CONDITIONS_IN = lt_ti_order_conditions_in
         TI_ORDER_CFGS_REF = lt_ti_order_cfgs_ref
. " BAPI_SALESORDER_PROXY_CREATE




ABAP code using 7.40 inline data declarations to call FM BAPI_SALESORDER_PROXY_CREATE

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 UPLOADSTAT FROM CRM_PARA INTO @DATA(ld_e_status).
 
"SELECT single REF_ID FROM BAPICRMDH2 INTO @DATA(ld_i_upload_id).
 
 
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_i_int_number_assignment).
DATA(ld_i_int_number_assignment) = 'X'.
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_i_behave_when_error).
DATA(ld_i_behave_when_error) = 'R'.
 
 
 
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_i_testrun).
 
 
 
 
 
 
 
 
 
"SELECT single RFCSERVER FROM CRM_PARA INTO @DATA(ld_i_destin).
 
"SELECT single VBELN FROM BAPIVBELN INTO @DATA(ld_e_salesdocument_ex).
 
"SELECT single SERVER_REL FROM CRM_PARA INTO @DATA(ld_i_sfa_rel).
 
 
"SELECT single KEYWORD_IN FROM BAPICRMDH1 INTO @DATA(ld_i_keyword_in).
 
 
"SELECT single VBELN FROM BAPIVBELN INTO @DATA(ld_i_salesdocument).
 
 
 
 
 
 
 
 
 
"SELECT single RELTYPE FROM BRELTYP INTO @DATA(ld_i_binary_relationshiptype).
 


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!