Copying multiple contract's data to sales orders via BAPI.

Hello Experts,
We have a requirement to copy contract data into the sales order, reference multiple contracts and copy all data from referenced contract to the SO.The scenario is that a seperate contract is being refrenced at the header level and different contract is referenced to the line items.All the data needs to be copied to the header or item from the doucment being referenced.
The standard BAPI available for creating the SO (CREATEDAT2) references the contract doucment, but doesnt copy all the data from the referencing doucment to the SO, as the copy control are not called.We also tried using the BAPI 'BAPI_SALESDOCUMENT_COPY', which copies all the data but only does this for a single contract reference at a time.The BAPi doesnt allow the specific items to be copied or doesnt allow the reference of multiple contracts at the line item level.
Any BAPI which can be used or pointers to resolve this issue, will be very helpful.
Thank you.
Best Regards,
Gaurav Bhardwaj.

Better try to follow this
[Read This Before Closing your Threads |Read This Before Closing your Threads;
thanks
G. Lakshmipathi

Similar Messages

Copying multiple contract's data to sales order

Hello Experts,
We have a requirement to copy contract data into the sales order, reference multiple contracts and copy all data from referenced contract to the SO.The scenario is that a seperate contract is being refrenced at the header level and different contract is referenced to the line items.All the data needs to be copied to the header or item from the doucment being referenced.
The standard BAPI available for creating the SO (CREATEDAT2) references the contract doucment, but doesnt copy all the data from the referencing doucment to the SO, as the copy control are not called.We also tried using the BAPI 'BAPI_SALESDOCUMENT_COPY', which copies all the data but only does this for a single contract reference at a time.The BAPi doesnt allow the specific items to be copied or doesnt allow the reference of multiple contracts at the line item level.
Any BAPI which can be used or pointers to resolve this issue, will be very helpful.
Thank you.
Best Regards,
Gaurav Bhardwaj.

Hi PeteA,
I dont get any message, the problem is I dont see the contract no field on the screen.
I copied the SM01 order type to ZM01 and did the required configuration, now when I use the ZM01 order type I cannot see the contract field but when I use SM01 the same is appearing.
I saw some screen config for order types in Basic Order view but SM01 does not have any entries there.
Thanks,
Sarath.c

Upload the data for sales order using BAPI

hi experts,
how to upload the data for sales order using BAPI.
what is the FM?
it would be much helpful if i have the sample code as i am very new to BAPI.
thanks and Regards
Shyam

Hi Shyam
Its very useful for u
BAPISDORDER_GETDETAILEDLIST
BAPI_ACC_SALES_ORDER_CHECK
BAPI_ACC_SALES_ORDER_POST
BAPI_ACC_SALES_QUOTA_CHECK
BAPI_ACC_SALES_QUOTA_POST
Reward all the helpful answers..
With Regards
Navin Khedikar

Creating Billing Plan data for sales order using BAPI

Hello,
Someone ones if there is any way to create a sales order (BAPI) and then create a billing plan (by means of another BAPI)?
Or is there any way to create both at the same time?
Kind Regards.

Hi David and Nisha here is the code for creating sales order with bapi
*& Report YOBJ_BAPI_SALESORDER
*& REPORT : CREATING SALES ORDER USING STANDARD BAPI
*& AUTHOR : S.PAVAN KUMAR INUMARTHY
REPORT YOBJ_BAPI_SALESORDER.
DATA : ORDER_HEADER_IN LIKE STANDARD TABLE OF BAPISDHD1 WITH HEADER LINE.
DATA : ORDER_ITEMS_IN LIKE STANDARD TABLE OF BAPISDITM WITH HEADER LINE.
DATA : ORDER_PARTNERS LIKE STANDARD TABLE OF BAPIPARNR WITH HEADER LINE.
DATA : RETURN TYPE STANDARD TABLE OF BAPIRET2 WITH HEADER LINE.
DATA : SALESDOCUMENT LIKE BAPIVBELN-VBELN.
*APPENDING VALUES FOR HEADER.
ORDER_HEADER_IN-DOC_TYPE = 'TA'.
ORDER_HEADER_IN-SALES_ORG = '1000'.
ORDER_HEADER_IN-DISTR_CHAN = '10'.
ORDER_HEADER_IN-DIVISION = '00'.
ORDER_HEADER_IN-SALES_GRP = '130'.
ORDER_HEADER_IN-SALES_OFF = '1030'.
APPEND ORDER_HEADER_IN.
*APPENDING VALUES FOR ITEM
ORDER_ITEMS_IN-MATERIAL = 'M-13'.
ORDER_ITEMS_IN-PLANT = '1000'.
ORDER_ITEMS_IN-SALES_UNIT = 'ST'.
ORDER_ITEMS_IN-DIVISION = '07'.
ORDER_ITEMS_IN-GROSS_WGHT = '28000'.
ORDER_ITEMS_IN-NET_WEIGHT = '28000'.
ORDER_ITEMS_IN-UNTOF_WGHT = 'KG'.
ORDER_ITEMS_IN-VOLUME = '0.780'.
ORDER_ITEMS_IN-VOLUNIT = 'M3'.
APPEND ORDER_ITEMS_IN.
*APPENDING VALUES FOR PARTNER
ORDER_PARTNERS-PARTN_ROLE = 'AG'.
ORDER_PARTNERS-PARTN_NUMB = '0000001000'.
ORDER_PARTNERS-COUNTRY = 'DE'.
ORDER_PARTNERS-TRANSPZONE = 'D000080000'.
APPEND ORDER_PARTNERS.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
*   SALESDOCUMENTIN               =
    ORDER_HEADER_IN               = ORDER_HEADER_IN
*   ORDER_HEADER_INX              =
*   SENDER                        =
*   BINARY_RELATIONSHIPTYPE       =
*   INT_NUMBER_ASSIGNMENT         =
*   BEHAVE_WHEN_ERROR             =
*   LOGIC_SWITCH                  =
*   TESTRUN                       =
*   CONVERT                       = ' '
IMPORTING
   SALESDOCUMENT                  = SALESDOCUMENT
TABLES
   RETURN                         = RETURN
   ORDER_ITEMS_IN                 = ORDER_ITEMS_IN
*   ORDER_ITEMS_INX               =
    ORDER_PARTNERS                = ORDER_PARTNERS
*   ORDER_SCHEDULES_IN            =
*   ORDER_SCHEDULES_INX           =
*   ORDER_CONDITIONS_IN           =
*   ORDER_CONDITIONS_INX          =
*   ORDER_CFGS_REF                =
*   ORDER_CFGS_INST               =
*   ORDER_CFGS_PART_OF            =
*   ORDER_CFGS_VALUE              =
*   ORDER_CFGS_BLOB               =
*   ORDER_CFGS_VK                 =
*   ORDER_CFGS_REFINST            =
*   ORDER_CCARD                   =
*   ORDER_TEXT                    =
*   ORDER_KEYS                    =
*   EXTENSIONIN                   =
*   PARTNERADDRESSES              =
          IF SY-SUBRC = 0.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*           EXPORTING
*             WAIT          =
*           IMPORTING
*             RETURN        =
           ENDIF.
WRITE : 'SALES ORDER IS :', SALESDOCUMENT.
I have tested and go it.
please go through it

User exit for contract start date in sales order change mode.

24.10.2008
Hi Gurus,
I need to disable the 'contract start date' (VEDA-VBEGDAT) field in Contract data tab at header and item level. Can someone suggest a user exit for the same ???
Regards,
Udaynath

Dear Udyanath,
Please check these User exits with the help of ABAPer
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document
processing are listed below.
USEREXIT_FIELD_MODIFICATION
     This user exit can be used to modify the attributes of the screen
     fields.
     To do this, the screen fields are allocated to so-called
     modification groups 1 - 4 and can be edited together during a
     modification in ABAP. If a field has no field name, it cannot be
     allocated to a group.
     The usage of the field groups (modification group 1-4) is as
     follows:
-   Modification group 1:   Automatic modification with transaction
         MFAW
-   Modification group 2:   It contains 'LOO' for step loop fields
-   Modification group 3:   For modifications which depend on check tables or on other fixed information.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document
header level. It is described in the section "Transfer of the
customer master fields into the sales document".
The user exit is called up at the end of the FORM routine
VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document
item level. It is described in the section "Copy customer master
fields into the sales document".
The user exit is called up at the end of the FORM routine
VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of
the sales document schedule lines.
The user exit is called up at the end of the FORM routine
VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer
master fields into sales document".
The user exit is called up at the end of the FORM routine
VBKD_FUELLEN.
I hope this will help you,
Regards,
Murali.

Problem in uploading multiple line items while Creating sales order by BAPI

Hi experts , Im able to create sales order with one item while using this program, but the problem is when iam having multiple items or multiple sales order , iam not able to createthe line items , though its creating sales order header , Iam copy pasting my code , please add the additional code to my code to take more than 1 line items ,This is urgent requirement . Points will be rewarded for answers , Thanks in advance
*& Report Z_SO_CREATE_BAPI
REPORT Z_SO_CREATE_BAPI.
DATA: i_header TYPE bapisdhd1 occurs 0 with header line.
DATA: i_details TYPE bapisditm OCCURS 0 WITH HEADER LINE.
DATA: i_partner TYPE bapiparnr OCCURS 0 WITH HEADER LINE.
DATA: i_return1 TYPE bapiret2 OCCURS 0 WITH HEADER LINE.
DATA: i_return2 TYPE bapiret2.
data : ORDER_HEADER_IN like BAPISDHD1.
data : ORDER_ITEMS_IN like BAPISDITM occurs 0 with HEADER LINE .
data : ORDER_ITEMS_INX Like BAPISDITMX occurs 0 with HEADER LINE .
data : RETURN like BAPIRET2 occurs 0 with header line.
data : ORDER_PARTNERS like BAPIPARNR occurs 0 with
header line.
DATA : ORDER_KEYS LIKE BAPISDKEY OCCURS 0 WITH HEADER
LiNE.
data : ORDER_SCHEDULES_IN like BAPISCHDL occurs 0 with
header line.
data : ORDER_SCHEDULES_INX like BAPISCHDLX occurs 0 with
header line.
data : BEGIN OF TAB OCCURS 0,
       SRNO(4),
        DOC_TYPE like ORDER_HEADER_IN-dOC_TYPE,
        SALES_ORG LIKE ORDER_HEADER_IN-SALES_ORG,
        DISTR_CHAN LIKE ORDER_HEADER_IN-DISTR_CHAN,
        DIVISION like ORDER_HEADER_IN-DIVISION,
       REQ_DATE_H(10),
       PURCH_DATE(10),
       PMNTTRMS LIKE ORDER_HEADER_IN-PMNTTRMS,
       PURCH_NO_C LIKE ORDER_HEADER_IN-PURCH_NO_C,
       ITM_NUMBER like BAPISDITM-ITM_NUMBER,
        MATERIAL   LIKE ORDER_ITEMS_IN-MATERIAL ,
        PLANT LIKE ORDER_ITEMS_IN-PLANT,
       TARGET_QTY LIKE ORDER_ITEMS_IN-TARGET_QTY,
       ITM_NUMBERX like ORDER_ITEMS_INX-ITM_NUMBER ,
       MATERIALX   LIKE ORDER_ITEMS_INX-MATERIAL ,
       CUST_MAT22 LIKE ORDER_ITEMS_IN-CUST_MAT22,
       PLANTX LIKE ORDER_ITEMS_INX-PLANT,
       TARGET_QTYX LIKE ORDER_ITEMS_INX-TARGET_QTY,
       ITM_NUMBER LIKE ORDER_ITEMS_IN-ITM_NUMBER,
       MATERIAL   LIKE ORDER_ITEMS_IN-MATERIAL ,
        PARTN_ROLE LIKE ORDER_PARTNERS-PARTN_ROLE,
        PARTN_NUMB LIKE ORDER_PARTNERS-PARTN_NUMB,
      END OF TAB.
DATA: v_vbeln TYPE bapivbeln-vbeln.
selection-screen begin of block b1 with frame.
skip 3.
parameter:p_infile like rlgrap-filename obligatory.
skip 3.
selection-screen end of block b1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_infile.
PERFORM value_help.
start-of-selection.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
    filename                     = p_infile
   FILETYPE                      = 'DAT'
HAS_FIELD_SEPARATOR           = 'X'
HEADER_LENGTH                 = 0
READ_BY_LINE                  = 'X'
DAT_MODE                      = ' '
CODEPAGE                      = ' '
IGNORE_CERR                   = ABAP_TRUE
REPLACEMENT                   = '#'
CHECK_BOM                     = ' '
VIRUS_SCAN_PROFILE            =
NO_AUTH_CHECK                 = ' '
IMPORTING
FILELENGTH                    =
HEADER                        =
tables
    data_tab                      = tab.
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
NO_AUTHORITY                  = 6
UNKNOWN_ERROR                 = 7
BAD_DATA_FORMAT               = 8
HEADER_NOT_ALLOWED            = 9
SEPARATOR_NOT_ALLOWED         = 10
HEADER_TOO_LONG               = 11
UNKNOWN_DP_ERROR              = 12
ACCESS_DENIED                 = 13
DP_OUT_OF_MEMORY              = 14
DISK_FULL                     = 15
DP_TIMEOUT                    = 16
OTHERS                        = 17
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
**Validation for the Create SO screen
*AT SELECTION-SCREEN ON BLOCK na_create.
Loop at Tab.
i_header-doc_type = TAB-DOC_TYPE .
i_header-sales_org = TAB-SALES_ORG.
i_header-distr_chan = TAB-DISTR_CHAN .
i_header-division = TAB-DIVISION .
append i_header.
*endloop.
i_partner-partn_role = TAB-PARTN_ROLE .
i_partner-partn_numb = TAB-PARTN_NUMB.
APPEND i_partner.
i_details-material = TAB-MATERIAL .
APPEND i_details.
endloop.
*Bapi for Creating SO
               CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
                 EXPORTING
                 SALESDOCUMENTIN               = v_vbeln
                   order_header_in               = i_header
                 ORDER_HEADER_INX              =
                 SENDER                        =
                 BINARY_RELATIONSHIPTYPE       =
                 INT_NUMBER_ASSIGNMENT         =
                 BEHAVE_WHEN_ERROR             =
                 LOGIC_SWITCH                  =
                 TESTRUN                       =
                 CONVERT                       = ' '
                IMPORTING
                  SALESDOCUMENT                 = v_vbeln
                 tables
                  RETURN                        = i_return1
                  ORDER_ITEMS_IN                = i_details
                  ORDER_ITEMS_INX               = ORDER_ITEMS_INX
                   order_partners                = i_partner .
                 ORDER_SCHEDULES_IN            =
                 ORDER_SCHEDULES_INX           =
                 ORDER_CONDITIONS_IN           =
                 ORDER_CONDITIONS_INX          =
                 ORDER_CFGS_REF                =
                 ORDER_CFGS_INST               =
                 ORDER_CFGS_PART_OF            =
                 ORDER_CFGS_VALUE              =
                 ORDER_CFGS_BLOB               =
                 ORDER_CFGS_VK                 =
                 ORDER_CFGS_REFINST            =
                 ORDER_CCARD                   =
                 ORDER_TEXT                    =
                 ORDER_KEYS                    =
                 EXTENSIONIN                   =
                 PARTNERADDRESSES              =
IF NOT v_vbeln IS INITIAL.
*Bapi Commit Work
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT =
IMPORTING
return = i_return2
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
IMPORTING
RETURN =
ENDIF.
LOOP AT i_return1 . "INTO wa_return1.
WRITE:/ i_return1-message.
ENDLOOP.
FORM value_help .
CALL FUNCTION 'DSVAS_DOC_WS_FILENAME_GET_50'
    EXPORTING
      DEF_FILENAME     = ' '
      DEF_PATH         = ' '
      MASK             = ',.,..'
      MODE             = 'O'
      TITLE            = ' '
    IMPORTING
      FILENAME         = p_infile
    EXCEPTIONS
      INV_WINSYS       = 1
      NO_BATCH         = 2
      SELECTION_CANCEL = 3
      SELECTION_ERROR = 4
      OTHERS           = 5.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.
txt file data
order type salesorg   distch      divison       materialno                  parter role
TA     PB01     01     00     000000000000000852     WE
Partner no
8101000000

Hi Neerja,
you can reffer this sample code. It may not be complet soluation for your poblem,
but you will get some idea.
*& Report ZBAPI_SALESORDER_CREATE
*& Author : Karthik
REPORT ZBAPI_SALESORDER_CREATE.
data : ORDER_HEADER_IN like BAPISDHD1.
data : ORDER_ITEMS_IN like BAPISDITM occurs 0 with
header line.
data : RETURN like BAPIRET2 occurs 0 with header line.
data : ORDER_PARTNERS like BAPIPARNR occurs 0 with
header line.
DATA : ORDER_KEYS LIKE BAPISDKEY OCCURS 0 WITH HEADER
LINE.
data : ORDER_SCHEDULES_IN like BAPISCHDL occurs 0 with
header line.
data : BEGIN OF TAB OCCURS 0,
        SRNO(4),
        DOC_TYPE like ORDER_HEADER_IN-dOC_TYPE,
        SALES_ORG LIKE ORDER_HEADER_IN-SALES_ORG,
        DISTR_CHAN LIKE ORDER_HEADER_IN-DISTR_CHAN,
        DIVISION like ORDER_HEADER_IN-DIVISION,
       REQ_DATE_H(10),
        PURCH_DATE(10),
        PMNTTRMS LIKE ORDER_HEADER_IN-PMNTTRMS,
        PURCH_NO_C LIKE ORDER_HEADER_IN-PURCH_NO_C,
        ITM_NUMBER like BAPISDITM-ITM_NUMBER,
        CUST_MAT22 LIKE ORDER_ITEMS_IN-CUST_MAT22,
        PLANT LIKE ORDER_ITEMS_IN-PLANT,
        TARGET_QTY LIKE ORDER_ITEMS_IN-TARGET_QTY,
        PARTN_ROLE LIKE ORDER_PARTNERS-PARTN_ROLE,
        PARTN_NUMB LIKE ORDER_PARTNERS-PARTN_NUMB,
      END OF TAB.
data: itab1 like alsmex_tabline occurs 0 with header
line.
DATA: gd_currentrow type i.
data : PURCHASEORDER like ekko-ebeln.
Data: tot_rec type i,     "Total Records
     gd_update type i,   "Main Table Increement Counter
     gd_lines type i,    "Success Table increement Counter
     w_textout like t100-text. "VARIABLE TO GET ERRORLOG
data : begin of it_success occurs 0,
        SALESDOCUMENT LIKE BAPIVBELN-VBELN, "PROJECT
      end of it_success.
data : begin of it_error occurs 0,
        srno(4),
        err_msg(73) TYPE c,    "TO RETREIVE ERROR MESSAGES
     end of it_error.
data : srno(4).
DATA : SALESDOCUMENT LIKE BAPIVBELN-VBELN.
selection-screen begin of block b1 with frame.
skip 3.
parameter:p_infile like rlgrap-filename obligatory.
skip 3.
selection-screen end of block b1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_infile.
PERFORM value_help.
start-of-selection.
call function 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      filename                = p_infile
      i_begin_col             = '1'
      i_begin_row             = '2' "Do not require
headings
      i_end_col               = '22'
      i_end_row               = '10000'
    TABLES
      intern                  = itab1
    EXCEPTIONS
      inconsistent_parameters = 1
      upload_ole              = 2
      others                  = 3.
if sy-subrc <> 0.
    message e010(zz) with text-001. "Problem uploading
Excel Spreadsheet
endif.
*perform open_group.
sort itab1 by row col.
Get first row retrieved
read table itab1 index 1.
Set first row retrieved to current row
gd_currentrow = itab1-row.
loop at itab1.
Reset values for next row
    if itab1-row ne gd_currentrow.
      append tab .
      clear tab.
      gd_currentrow = itab1-row.
    endif.
    SHIFT ITAB1-VALUE LEFT DELETING LEADING SPACE.
    case itab1-col.
      when '0001'.
        TAB-SRNO = itab1-value.
      when '0002'.
        TAB-DOC_TYPE = itab1-value.
      when '0003'.
        TAB-SALES_ORG = itab1-value.
      when '0004'.
        TAB-DISTR_CHAN = itab1-value.
      when '0005'.
        TAB-DIVISION = itab1-value.
     when '0006'.
       TAB-REQ_DATE_H = itab1-value.
      when '0006'.
        TAB-PURCH_DATE = itab1-value.
      when '0007'.
        TAB-PMNTTRMS = itab1-value.
      when '0008'.
        TAB-PURCH_NO_C = itab1-value.
        when '0009'.
        TAB-ITM_NUMBER = itab1-value.
       when '0010'.
        TAB-CUST_MAT22 = itab1-value.
      when '0011'.
        TAB-PLANT = itab1-value.
      when '0012'.
        TAB-TARGET_QTY = itab1-value.
      when '0013'.
        TAB-PARTN_ROLE = itab1-value.
      when '0014'.
        TAB-PARTN_NUMB = itab1-value.
    endcase.
endloop.
append tab.
clear tab.
sort tab by SRNO.
LOOP AT TAB.
   concatenate tab-REQ_DATE_H+4(4)
tab-REQ_DATE_H2(2) tab-REQ_DATE_H0(2) into
tab-REQ_DATE_H.
    concatenate tab-PURCH_DATE+4(4)
tab-PURCH_DATE2(2) tab-PURCH_DATE0(2) into
tab-PURCH_DATE.
    SRNO = TAB-SRNO.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        INPUT = tab-PARTN_NUMB
      IMPORTING
        OUTPUT = tab-PARTN_NUMB.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        INPUT = tab-CUST_MAT22
      IMPORTING
        OUTPUT = tab-CUST_MAT22.
    IF TAB-SRNO = SRNO.
      ORDER_HEADER_IN-DOC_TYPE = TAB-DOC_TYPE.
      ORDER_HEADER_IN-SALES_ORG = TAB-SALES_ORG.
      ORDER_HEADER_IN-DISTR_CHAN = TAB-DISTR_CHAN.
     ORDER_HEADER_IN-REQ_DATE_H = TAB-REQ_DATE_H.
      ORDER_HEADER_IN-PURCH_DATE = TAB-PURCH_DATE.
      ORDER_HEADER_IN-PMNTTRMS = TAB-PMNTTRMS.
      ORDER_HEADER_IN-PURCH_NO_C = TAB-PURCH_NO_C.
      ORDER_HEADER_IN-DIVISION = tab-DIVISION.
      ORDER_ITEMS_IN-ITM_NUMBER = tab-ITM_NUMBER.
      ORDER_ITEMS_IN-material = TAB-CUST_MAT22.
      ORDER_ITEMS_IN-PLANT      = TAB-PLANT.
      APPEND ORDER_ITEMS_IN.
      ORDER_PARTNERS-PARTN_ROLE = TAB-PARTN_ROLE.
      ORDER_PARTNERS-PARTN_NUMB = TAB-PARTN_NUMB.
      APPEND ORDER_PARTNERS.
      ORDER_SCHEDULES_IN-ITM_NUMBER = tab-ITM_NUMBER.
      ORDER_SCHEDULES_IN-REQ_QTY = tab-TARGET_QTY.
      append ORDER_SCHEDULES_IN.
    ENDIF.
    AT END OF SRNO.
      CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
        EXPORTING
           SALESDOCUMENTIN               =
             ORDER_HEADER_IN               = ORDER_HEADER_IN
           ORDER_HEADER_INX              =
           SENDER                        =
           BINARY_RELATIONSHIPTYPE       =
           INT_NUMBER_ASSIGNMENT         =
           BEHAVE_WHEN_ERROR             =
           LOGIC_SWITCH                  =
           TESTRUN                       =
           CONVERT                       = ' '
       IMPORTING
         SALESDOCUMENT                 = SALESDOCUMENT
        TABLES
         RETURN                        = RETURN
             ORDER_ITEMS_IN                = ORDER_ITEMS_IN
           ORDER_ITEMS_INX               =
             ORDER_PARTNERS                = ORDER_PARTNERS
             ORDER_SCHEDULES_IN            = ORDER_SCHEDULES_IN
           ORDER_SCHEDULES_INX           =
           ORDER_CONDITIONS_IN           =
           ORDER_CONDITIONS_INX          =
           ORDER_CFGS_REF                =
           ORDER_CFGS_INST               =
           ORDER_CFGS_PART_OF            =
           ORDER_CFGS_VALUE              =
           ORDER_CFGS_BLOB               =
           ORDER_CFGS_VK                 =
           ORDER_CFGS_REFINST            =
           ORDER_CCARD                   =
           ORDER_TEXT                    =
         ORDER_KEYS                    = ORDER_KEYS
           EXTENSIONIN                   =
           PARTNERADDRESSES              =
      IF SALESDOCUMENT <> SPACE.
        commit work.
        ADD 1 TO gd_update.
        it_success-SALESDOCUMENT = SALESDOCUMENT.
        append it_success.
        CLEAR :SALESDOCUMENT,ORDER_HEADER_IN.
        REFRESH : RETURN,ORDER_ITEMS_IN,ORDER_PARTNERS.
      ELSE.
        loop at return.
          it_error-SRNO = tab-SRNO.
          it_error-err_msg = return-MESSAGE .
          Append it_error.
        ENDLOOP.
        CLEAR :SALESDOCUMENT,ORDER_HEADER_IN.
        REFRESH : RETURN,ORDER_ITEMS_IN,ORDER_PARTNERS.
      ENDIF.
    endat.
endloop.
DESCRIBE TABLE it_success LINES gd_lines.
IF gd_lines GT 0.
    Display result report column headings
    PERFORM display_column_headings.
    Display result report
    PERFORM DISPLAY_SUCESS.
ENDIF.
IF SUCESS FAILS Display Error Report
DESCRIBE TABLE it_error LINES gd_lines.
IF gd_lines GT 0.
    PERFORM errorheadings.
    PERFORM errorreport.
ENDIF.
*&      Form display_column_headings
      text
FORM display_column_headings.
WRITE:2 ' Success Report '(014) COLOR COL_POSITIVE.
SKIP.
WRITE:2 'The following records inserted
successfully:'(013).
WRITE:/ sy-uline(15).
FORMAT COLOR COL_HEADING.
WRITE:/      sy-vline,
           (10) 'Sales order'(004), sy-vline.
WRITE:/ sy-uline(15).
ENDFORM.                    "display_column_headings
*Subroutine to display SUCESS REPORT
FORM DISPLAY_SUCESS.
FORMAT COLOR COL_NORMAL.
LOOP AT it_success.
    WRITE:/      sy-vline,
        (10) it_success-SALESDOCUMENT, sy-vline.
    CLEAR it_success.
ENDLOOP.
WRITE:/ sy-uline(15).
REFRESH: it_success.
FORMAT COLOR COL_BACKGROUND.
ENDFORM.                               "
DISPLAY_REPORT
*&      Form errorreport
      text
FORM errorreport.
LOOP AT it_error.
    WRITE:/      sy-vline,
            (10) it_error-SRNO, sy-vline,
             (40) it_error-err_msg, sy-vline.
ENDLOOP.
WRITE:/ sy-uline(104).
REFRESH: it_error.
endform.                    "errorreport
*&      Form ERRORHEADINGS
      text
FORM ERRORHEADINGS.
SKIP.
WRITE:2 ' Error Report '(007) COLOR COL_NEGATIVE.
SKIP.
WRITE:2 'The following records failed during
update:'(008).
WRITE:/ sy-uline(104).
FORMAT COLOR COL_HEADING.
WRITE:/      sy-vline,
          (10) 'ERROR.'(009), sy-vline.
WRITE:/ sy-uline(104).
FORMAT COLOR COL_NORMAL.
ENDFORM.                    "ERRORHEADINGS
**&      Form value_help
      text
--> p1        text
<-- p2        text
FORM value_help .
CALL FUNCTION 'DSVAS_DOC_WS_FILENAME_GET_50'
    EXPORTING
      DEF_FILENAME     = ' '
      DEF_PATH         = ' '
      MASK             = ',.,..'
      MODE             = 'O'
      TITLE            = ' '
    IMPORTING
      FILENAME         = p_infile
    EXCEPTIONS
      INV_WINSYS       = 1
      NO_BATCH         = 2
      SELECTION_CANCEL = 3
      SELECTION_ERROR = 4
      OTHERS           = 5.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.                    "value_help
Regards,
Amit.

How to header and item data of sales order using bapi interface

hi friends,
   i am geetha, i having a problem like how to upload sales oder header and item data through va01 tcode using BAPI FUNCTION MODULES.
i need bapi function modules for header adn item data and brief explation on that , how to pass importing and tables parameters to get exact output .
regards
geetha.

Use : BAPI_SALESORDER_CREATEFROMDAT2
Sales order: Create Sales Order
Functionality
You can use this method to create sales orders.
You must enter at least sales order header data (via ORDER_HEADER_IN structure) and partner data (via the ORDER_PARTNERS table) as input parameters.
Enter the item data via the ORDER_ITEMS_IN table. You can allocate item numbers manually, by filling in the relevant fields, or the system does it, according to the settings for Customizing, by leaving the relevant fields blank.
If you have configurable items, you must enter the configuration data in the ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF and ORDER_CFGS_VALUE tables.
Credit cards can be transferred via the BAPICCARD structure, on the one hand, data for card identification, on the other, data for a transaction which has taken place in an external system.
Once you have created the sales order successfully, you will receive the document number (SALESDOCUMENT field). Any errors that may occur will be announced via the RETURN parameter.
If no sales area has been created in the sales order header, then the system creates the sales area from the sold-to party or ship-to party, who has been entered in the partner table. If a clear sales area cannot be created, you will receive a system message, and the sales order will not be created.
Notes
1. Mandatory entries:
ORDER_HEADER_IN : DOC_TYPE     Sales document type
                   SALES_ORG    Sales organization
                   DISTR_CHAN   Distribution channel
                   DIVISION     Division
ORDER_PARTNERS..: PARTN_ROLE   Partner role, SP sold-to party
                   PARTN_NUMB   Customer number
ORDER_ITEMS_IN..: MATERIAL     Material number
2. Ship-to party:
If no ship-to party is entered, use the following: Ship-to party =
sold-to party.
3. Commit control:
The BAPI does not have a database commit. This means that the relevant application must leave the commit, in order that can be carried out on on the database. The BAPI BAPI_TRANSACTION_COMMIT is available for this.
4. German key words:
The following key words must be entered in German, independantly of
the logon language:
DOC_TYPE     Sales document type, for example: TA for standard order
PARTN_ROLE   Partner role, for example: WE for ship-to party
Further information
You can find further information in the OSS. The note 93091 contains general information on the BAPIs in SD.
Parameters
SALESDOCUMENTIN
ORDER_HEADER_IN
ORDER_HEADER_INX
SENDER
BINARY_RELATIONSHIPTYPE
INT_NUMBER_ASSIGNMENT
BEHAVE_WHEN_ERROR
LOGIC_SWITCH
TESTRUN
CONVERT
SALESDOCUMENT
RETURN
ORDER_ITEMS_IN
ORDER_ITEMS_INX
ORDER_PARTNERS
ORDER_SCHEDULES_IN
ORDER_SCHEDULES_INX
ORDER_CONDITIONS_IN
ORDER_CONDITIONS_INX
ORDER_CFGS_REF
ORDER_CFGS_INST
ORDER_CFGS_PART_OF
ORDER_CFGS_VALUE
ORDER_CFGS_BLOB
ORDER_CFGS_VK
ORDER_CFGS_REFINST
ORDER_CCARD
ORDER_TEXT
ORDER_KEYS
EXTENSIONIN
PARTNERADDRESSES
Exceptions
Function Group
2032

Display dates in sales order via CIC0

Dear experts,
In SAP CRM 5.0, we've configured sales orders and dates. Via CRMD_ORDER transaction, dates are correctly displayed.
But we're using interaction center (CIC0) and the screen with dates is not displayed.
We've tried screen sequence control (CRMV_SSC) but we don't manage to display this ALV grid.
Can someone help us?
Thank you!

to pass the values into order u have to create in follow up document . if u still so get the values populated over there . check Spro -> crm->ic win clt->component configration ->visible compnents ->action box ->D p action box config -> go inside
Give the BOR componet and appropiate metod and give the field .
Hope this helps u

How to add material characteristics in sales order via BAPI?

Hi all!
I'm trying to use BAPI_SALESORDER_CREATEFROMDAT1 to create a sales order with one item that has some characteristics, but i can't seem to get it work. It creates the salesorder with the item but without characteristics data. Can somebody tell me what could be wrong?
Here's the code:
header-doc_type   = 'TA'.
header-sales_org = '3000'.
header-distr_chan = '10'.
header-division   = '00'.
items-itm_number = '000010'.
items-material   = 'CP-12'.
items-req_qty    = '1000'.
APPEND items.
partners-partn_role = 'AG'.
partners-partn_numb = '0000050000'.
APPEND partners.
c_ref-posex     = '000010'.
c_ref-config_id = '000001'.
c_ref-root_id   = '00000001'.
APPEND c_ref.
c_ins-config_id = '000001'.
c_ins-inst_id   = '00000001'.
c_ins-obj_type = 'MARA'.
c_ins-obj_key   = 'CP-12'.
c_ins-complete = 'T'.
c_ins-consistent = 'T'.
c_ins-quantity = '0'.
c_ins-quantity_unit = 'ST'.
c_ins-class_type = '300'.
APPEND c_ins.
c_val-config_id = '000001'.
c_val-inst_id   = '00000001'.
c_val-charc     = 'CP_12_ADD_ON'.
c_val-value     = 'F'.
c_val-valcode   = '1'.
APPEND c_val.
c_val-charc     = 'CP_12_COLOUR'.
c_val-value     = 'M'.
APPEND c_val.
c_val-charc     = 'CP_12_MODEL'.
c_val-value     = 'M'.
APPEND c_val.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
EXPORTING
    order_header_in           = header
    convert_parvw_auart       = 'X'
IMPORTING
   salesdocument             = salesdoc
   return                    = return
TABLES
    order_items_in            = items
    order_partners            = partners
   order_cfgs_ref            = c_ref
   order_cfgs_inst           = c_ins
   order_cfgs_part_of        = c_prt
   order_cfgs_value          = c_val

BAPI_SALESORDER_CREATEFROMDAT1
"(obsolete from 4.6 version)
BAPI_SALESORDER_CREATEFROMDAT2
please see the version and change the BAPI
reward points if it is usefull ....
Girish

How to create sales order using bapi( test purpose)

Hi all,
       while i was creating sales order using the BAPI_SALESORDER_CREATEFROMDAT1 it is giving some error,
version 0 is not defined for the fiscal year ****.
I have given the fallowing parameters as input
ORDER_HEADER_IN
     DOC_TYPE     OR
                SALES_ORG 1000
     DISTR_CHAN 10
                DIVISION         00
ORDER_PATNERS
     PARTN_ROLE     SP
     PARTN_NUMB     1000
ORDER_ITEMSIN
     MATERIAL     M-13
I need to create sample sales order . Please help me how to create sales order with an example( for test purpose).
Regards
Deviprasad.

Hi Prasad,
Try using BAPI_SALESORDER_CREATEFROMDAT2.
While creating sales order using FM: BAPI_SALESORDER_CREATEFROMDAT2, please make sure ORDER_ITEMS_IN, ORDER_ITEMS_INX, ORDER_SCHEDULES_IN, ORDER_SCHEDULES_INX.
Pricing Conditions will not be mandatory to create a sales order via BAPI.
As you were saying, you can create a sales order but not with items. Do populate the internal tables that i have specified above.
Also try to pass the item number internally, this will help you in identifying the schedule lines.
Regards,
Priyanka.

Copy contract PO number and Date to Sales Order

Hi freinds,
I have one requirement. I want to copy contract PO number and date to Sales order PO Number and Date while creating the sales order with reference to contract.
Thanks,
Satya

Hi,
You have to modify your data transfer routine with the help of ABAPer.
You have to give him the requirement that these value should be copied to sales order from contract.
He will do the needful changes in the data transfer routine.
Then assign that routine to the copy control of sales order from contract.
Regards
Raj.

Setting user specific contract data while creating sales order using BAPI

Hi all,
I am creating sales order using BAPI - BAPI_SALESORDER_CREATEFROMDAT2.
Now my problem is that there is no structure for contract data (i.e. VEDA), system automatically set contract data using customization values.
I am doing some validations on cotract data in MV45AFZZ which fails, because these validations are performed on standard values, user specific values r not set.
How to handle this issue, your small clue may help a lot.
Regards,
S@meer

HI
Pricing will be carried basing on the pricing
procedure.
Case1: Prices will be carried out automatically if
necessary condition records are maintained for the
condition type.
For this you can go to Sales Order-> Item Conditions
In the screen you can click on command button Analysis,
which gives you the list of condition types associated
to the pricing procedure. By clicking on the condition
type you can know the action that has taken place.
Case2: Manually forcing prices for Items.
To do this, you have to populate ORDER_CONDITIONS_IN &
ORDER_CONDITIONS_INX. Also note to identify the item
numbers, you manually pass the item number for each item
in the sales order, use the same item number for
populating conditions.
Parameters required:
ORDER_CONDITIONS_IN:
ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
ORDER_CONDITIONS_INX:
ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
Hope the above info helps you. Do revert back if you
need more info.
Kind Regards
Eswar

Copy mode of payment from customer master data to sales order,

Hi Gurus,
Hope all is fine.
I have a small doubt. If we want to transfer the mode of payment from customer master data to sales order, do we have to use Exit- MV45AFZZ.
Can't we transfer the data without the exit?

Hi,
I have tested this in sand box.Thought the customer master is having payment method ( payer ) ,It is not copying from customer master to sales order but if you maintain manually in sales order ,it is copying into billing document level.FYI see below snap shot.
Note:If you want it from customer master into sales order,may be you need to take help of abaper on this.
BR's,
Naren

User exit to copy the data from sales order to billing document

hi everyone,
Is there an user exit to copy the data from sales order to billing document?
Regards
Prabudh

hi
copy control would be the better option to choose.. but still u can a give a search in list below and opt for the right one..Refer to the link below..
http://www.planetsap.com/Userexit_List.htm
User exits for Sales order
1USEREXIT_DELETE_DOCUMENT
2USEREXIT_FIELD_MODIFICATION
3.USEREXIT_MOVE_FIELD_TO_VBAK
4.USEREXIT_NUMBER_RANGE
5.USEREXIT_SAVE_DOCUMENT
User exits for billing
1.USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
2.USEREXIT_ACCOUNT_PREP_KOMPCV
3USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
4USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Reward if Useful
Thanx & Regards..
Naren..

Copy control and program name for Sales Order to Delivery

Hi,
Please provide the copy control and program name to split a single delivery into multiple invoices depending on the sales order it belonged to and to split a single sales order into multiple deliveries depending on the shipping type.
Thanks in advance.

Hi there,
In VTFL, at item level, there is a field called "Data VBRK/VBRP". Routine 001 & 007 are for invoice split. Those may be relevant for your case.
In VOFM, select data transfer --> billing docs in the menu bar. It will give you the requirement numbers & their description.
Select the required routine num & click on Source text (note pad icon) on the above. It will give you the prog / include names.
For eg for 001 its FV60C001, for 007 its FV60C007.
Regards,
Sivanand

Copying multiple contract's data to sales orders via BAPI.

Similar Messages

Maybe you are looking for