LSMW - Sales Order Migration using RVINVB10

Dear Experts,
I have decided to use LSMW to migrate the open Sales Orders using direct input report RVINVB10.
My question is:
How do I enter the WBS Element PS_POSID in the item line of Account Assignment tab? There does not seem to be a field in the direct input program structure to fill this in.
Please suggest me is it possible to create the sales orders using this report or shall I try some other methods.
Waiting for your valuable reply.
Thanks !!!
Vasanth

you can use LSMW BAPI method
Business Object      BUS2032      Sales Order
Method               CREATEFROMDAT2              Sales order: Create Sales
Message Type         SALESORDER_CREATEFROMDAT2   Sales order: Create Sales
Basic Type           SALESORDER_CREATEFROMDAT2   Sales order: Create Sales

Similar Messages

Open sales order migration using lsmw

Hello guys iam migrating open sales order and iam having header fields
AUART
VKORG
VTWEG
SPART
KUNNR
KUNNR
BSTKD
BSTDK
VBEGDAT
VENDDAT
item fields are
MATNR
ZMENG
SPART
ISMACTIVATION
what is the standard object available for this migration in lsmw.?i thought of using
0090 salesdocument standrd object using direct input method but field ismactivation is not available in that object.
if i go for bapi method salesorder_createfromdat2 i couldnt find the above fields for mapping in that object.but some of the guys in this forum used this bapi method for this type of migration i dnt how they did it can u please suggest solution for this .
Regards
Janapathi

Hi!
In the given BAPI, the field names are different. You have to match them using their description or data type.
If you check this BAPI in transaction SE37, on hte Import tab, click on the BAPISDHD1ref type.
Here you can find the field DOC_TYPE (type AUART). With this way, you can find the matching fields.
Regards
Tamá

LSMW - Sales Order creation using IDoc

Hello,
I'm receiving a file containing different category of products and need to create a sales order (using IDoc or BAPI) per category. The input file contains UPC code, I use a SELECT statement to check the category and append the UPC code to the specific internal table .(one internal table per category). The issue I have is to do loop in all internal table and then to create a sales order. I have some difficulties to update item segment. Only one UPC is populated to the required segment. Please let me know if this could be done using LSMW.
Thanks ! Thanks ! Thanks ! Thanks !
Mehdi

You can use program RVINVB10 ( Direct Input ) to create Sales Order , Before you run this program you will have to create a file with data in specific format.
Read the documenatation of the program.
LSMw can help in formatting the data but beetr write your own progarm to format data and then run above program as LSMW has limitations and I am not sure what type of file you are getting. In you custom program you will have more control.
Cheers.

LSMW Sales Order creation using Bapi method

Hi folks ,
iam doing Lsmw bapimethod ,sales order creation .In the step start idoc processing iam getting error "Has Not been Accepted for Processing ",why iam not getting plz let me know points will be awarded for all answers .

Hi,
You need to set the IDOC settings in the initial LSMW screen. It will be there in menu path.
Award points if helpful
Regards,
RamaKrishna C

Sales order creation using LSMW

Hi All,
I am creating open sales order (VA01) using LSMW where I am using BAPI: BUS2032 and Method CREATEFROMDAT2.
I need to pass multiple line items for the same Header data, but the LSMW is creating multiple sales orders with a single line item every time.
I tried giving "on_change_transfer_record" after Header record but that doesn't work.
Can anyone suggest any suitable solution for this using BAPI only other than BDC, report program etc.
Thanks in Advance
Asif Ali Khan

Hi Asif Khan,
Please check this link
BAPI_SALESORDER_CREATEFROMDAT2 - Sales Order Create
http://sap-img.com/abap/bapi-salesorder-createfromdat2.htm
Best regards,
raam

Confirmed quantity during sales order migration

Do any of you experts see any issue with the following approach to set the schedule line confirmed quantity?
We need to migrate open order from Legacy to SAP system. While migrating we need to keep the schedule lines (dates and confirmed quantities) to be same as that in legacy (Note that legacy has exactly one schedule line per order).
For Migration we are using the program RVINVB10.
On order to bring in the confirmed quantity we plan to apply the following logic
1. Add following logic to user exit - MOVE_FIELDS_TO_VBEP (in MV45AFZZ)
If the order is a migrated order then
 check if VBAP-POSEX <> '' (This an unused field so we will use this to pass the confirmed quantity)
 then VBEP-BMENG = VBAP-POSEX
 VBAP-POSEX = VBAP-MTVFP (Save Valye of Checking Group)
 VBAP-MTVFP = ''. (clear the checking group to override the ATP check)
2. The following logic is added in User Exit SAVE_DOC_PREPARE (in MV45AFZZ)
If the order is migrated order then restore the value in VBAP-MTVFP from VBAP-POSEX and clear VBAP-POSEX.
This way we are able to get the confirmed quantity in schedule lines.
Any suggestions welcome,
Regards,

Here is an alternative functional approach
Depending on what is being used by your ATP config to determine supply you can create following pseudo supplies only for Sales order migration purpose
Planned orders
Purchase requisations
reservations
you can load any max quantity such as 9999999 at an earliest Material availability date (MAD) determined from sales orders for Material Plant combination.
This will help ATP to confirm the same CDD if you pass CDD as required delivery date (assumption it uses backward scheduling)
Assumption: you are moving only completely open sales order & itu2019s not delinquent (CDD in past, schedule lines not confirmed completely)
You have to remove this pseudo supply after sales order migration is complete.

LSMW Sales Order BAPI : Header & Item Text

Hi frenz,
 I'm migrating Sales Order data using LSMW with BAPI method. We got four files...
one for header, one for item, one for header text, one for item text.
Now my problem is how do i update both header and item text.
B'cos while assigning structural relations we got only one text structure(E1BPSDTEXT) common for both header and item. So which source structure(whether header_text or item_text) should be assigned to this segment(E1BPSDTEXT)?
Else is there any other way to update both header and item texts?
With regards,
praveen.

Unfortunately, you cannot assign more than one source structure to a target structure. But you can still manipulate the code. Here is how.
Let us say your source structure defined for item texts is ITEM_TEXTS. In your field mapping section for E1BPSDTEXT, double click the '__BEGIN_OF_RECORD__' in change mode. It will pop-up a warning message, say 'yes' and proceed. Remove all the coding that is there in this section, but copy the lines to somewhere(say x buffer) before you do that. You will need those lines below. Just add the following lines there.
if v_transferred_texts = 'X'.
*-- all the texts are transferred, don't need to process again.
skip_record.
endif.
You need to define 'v_transferred_texts' in the
'__GLOBAL_DATA__' section as follows.
data: v_transferred_texts type c.
Now double click on '_END_OF_RECORD_' in change mode. It will pop-up a warning, but you can say 'yes' and proceed. This will open up the coding window with one line of code in it 'transfer_record.'. Here you need to add your coding as follows.
*-- move the header texts
LOOP AT HEADER_TEXTS.
*-- This should ALWAYS be there
g_edidd_segnam = 'E2BPSDTEXT000'.
g_edidd_segnum = '0021'.
g_edidd_psgnum = '000001'.
g_edidd_hlevel = '02'.
clear E1BPSDTEXT.
*-- fill each field of the following fields
E1BPSDTEXT-DOC_NUMBER = SALESHEADER-ORDERNUMBER.
E1BPSDTEXT-ITM_NUMBER = '000000'.
E1BPSDTEXT-TEXT_ID = HEADER_TEXTS-TEXTID.
E1BPSDTEXT-LANGU = SY-LANGU.
E1BPSDTEXT-LANGU_ISO
E1BPSDTEXT-FORMAT_COL
E1BPSDTEXT-TEXT_LINE = HEADER_TEXTS-TEXT.
E1BPSDTEXT-FUNCTION = '005'.
transfer_record.
ENDLOOP.
*-- Now move the item texts
LOOP AT ITEM_TEXTS.
*-- This should ALWAYS be there
g_edidd_segnam = 'E2BPSDTEXT000'.
g_edidd_segnum = '0021'.
g_edidd_psgnum = '000001'.
g_edidd_hlevel = '02'.
clear E1BPSDTEXT.
*-- fill each field of the following fields
E1BPSDTEXT-DOC_NUMBER = SALESHEADER-ORDERNUMBER.
E1BPSDTEXT-ITM_NUMBER = ITEM_TEXTS-ITM_NUMBER.
E1BPSDTEXT-TEXT_ID = ITEM_TEXTS-TEXTID.
E1BPSDTEXT-LANGU = SY-LANGU.
* E1BPSDTEXT-LANGU_ISO =
* E1BPSDTEXT-FORMAT_COL
E1BPSDTEXT-TEXT_LINE = ITEM_TEXTS-TEXT.
E1BPSDTEXT-FUNCTION = '005'.
transfer_record.
ENDLOOP.
*-- set the flag that the texts have been transferred
v_transferred_texts = 'X'.
Please let me know how it goes.
Srinivas

Lsmw sales order

hi folks,
Can any one send me with screenshots how to upload sales order records using LSMW bapi method ,will be rewarded with points.

Hi,
Refer this:
http://www.****************/Tutorials/LSMW/LSMWMainPage.htm
1.Similar to the PO u can do sales order.
Regards,
Shiva.

LSMW : Sales Order DI : Extend the stucture?

Hello Friends,
We are currently using Direct Input approach for LSMW Sales Order. It all working fine and SO is uploaded
But there are some 20 odd fields which our clients wants to be uploaded from legacy system [eg MUEBS (Char Display), AUDAT [Which currently is sy-datum internally]....
Now these fields are not present in BVBAKKOM, BVBAPKOM etc structures..
Over this I have following doubts...
1 If we want to extend the structure how should we go about it ?
2. If we extend the structure then do we need to regenerate the LSMW program? How to do it ?
Please consider my case as very urgent...
Thanks in advance.

hi
60000001
This direct input program creates purchase orders using function modules. In a second step, program RM06EEI1 supplements these newly created POs with the purchase order history and the necessary accounting documents.
Please note the following restrictions:
The net price is based on one condition only (standard: PBXX): additional conditions (discounts, surcharges) are not supported
Change documents cannot be compiled for the POs
PO items with multiple account assignment cannot be transferred
"Goods-receipt based" invoice verification is not supported
The PO items may not relate to materials subject to split valuation
Down payments and subsequent debits involving PO items are not possible
Inbound deliveries are not transferred
Subcontract orders, third-party orders, stock transport orders, service orders and release orders are not transferred
The program reads a sequential file containing records of the structures MBEPOH (PO header) and MBEPOI (PO item), and generates purchase orders from them.
The data is expected in the sequential file in the following order:
For each PO header, a record of the structure MBEPOH,
For each PO item, a record of the structure MBEPOI.
All PO items up to the next PO header are assigned to the last-read PO header. Accordingly, the first record of the sequential file must be a PO header, whereas the last record of the file must be a PO item.
For further information on the structure of the sequential file and on the expected field formats and contents, please refer to the Implementation Guide.
For test purposes, you can use program RM06EEEX to generate a sequential file on the basis of POs that already exist in the system.
Program parameters:
You can maintain the following parameters on the initial screen:
File name: please specify the logical file name under which the sequential file can be accessed.
Update or test run: with these parameters you specify whether or not the program is to be run in test mode only. If you specify the test mode, all the data transfer checks are carried out without the database being updated. If you decide on the update run, the purchase orders will be added to the database after successful checking.
Scope of log: via this parameter, you specify whether or not you wish to have detailed output of the error messages per PO item with error identification and short error text.
60000002
Before you begin with the actual transfer of your purchase orders using this program, certain activities must be carried out. Among other things, the data extract for this program must be created and Customizing settings checked or altered. For further information, please refer to the Implementation Guide.
60000003
The program log contains:
Program statistics (start, end, number of records read etc.)
A listing of PO numbers added
A listing of PO numbers not added (i.e. faulty POs)
The detailed error log per PO item supplements this, provided you have activated the output of this log via the relevant program parameter.
This latter log contains:
PO number
PO item
Message class
Error category
Error number
Error short text
60000004
The same checks are made as in the case of the manual creation of purchase orders.
In addition, the system checks whether the order types and item categories are allowed for automatic PO transfer (see restrictions).
If the PO history is to be compiled using program RM06EEI1, (as per the specification in field MBEPOI-WEREF), additional checks relating to the amount and quantity fields of the invoice and goods receipts are made.
A purchase order is only created if all PO items have passed the checking process without errors.
60000005
Prior to transferring purchase orders with database updating, you should carry out a database back up. Reset programs for automatically created purchase orders are currently not available.
Restarting at the existing sequential file is possible. The program recognizes that the PO in question is not to be added again by reference to the external PO number assigned by you.
A database commit is initiated after each newly created purchase order.
By means of the appropriate organizational measures, please ensure that the POs created via program RM06EEI0 are not changed manually before program RM06EEI1 has been run successfully. Inconsistencies cannot otherwise be ruled out.
The program run-time depends largely on your installation, your organization structure, and the quantity structure of your master and transaction data.
As a rough estimate, however, it can be assumed that approx. 4000 PO items per hour can be handled.
The complete documentation on data transfer with regard to purchase orders is available in the SAP Library:
CA Cross-Application Components -> CA Data Transfer Workbench -> Data Transfer Objects by Application -> MM Materials Management -> MM Purchase Orders: Data Transfer Workbench.
You may have to use one file for this. Your structure would include all of the fields for both the header and detail.
regs
Arun

Error in creation of sales order bu using BAPI_SALESORDER_CREATEFROMDAT2

Hi ,
I am trying to create sales order by using bapi.
after passing all the parameters to bapi iam getting message as shown below.
SALES_HEADER_IN has been processed successfully
SALES_ITEM_IN has been processed successfully
Order receipt/delivery not possible, credit customer blocked
I had passed scedule line data ,and BAPI_TRANSACTION_COMMIT
also still iam getting this message.
please help me out of this problem.
Thanks,
Shuja.

Hi Shuja
I guess the message is just a warning eventhough the order is created. The warning message states that Auto-Delivery can not be created.
Please check below to understand how the customer is blocked:
1. Manual Block -> Transaction XD03
-->Menupath: Extras->Blocking Data
2. Credit Block -> Transaction FD33
--> In the overview screen check the difference of value between Credit Limit & Credit Exposure
I guess in the case whereby Credit Limit value is less than Credit Exposure also this can happen.
Please try using a different Customer. Also simulate via transaction VA01.
Hope this helps.
Kind Regards
Eswar

Change only material qunatity in sales order by using BAPI

Hi All,
How to change only the material quantity in existing sales order by using BAPI.
Please help me in this regards.
Regards
Deekshitha.

Hi
See the sample code and do accordingly
REPORT Z_SALES_ORDER_CHANGE
NO STANDARD PAGE HEADING
LINE-SIZE 132
LINE-COUNT 65(0)
MESSAGE-ID ZZ.
TABLES: VBAP.
DATA:
V_FILEIN(90) TYPE C,
V_RECIN TYPE I,
V_RECVBAP TYPE I,
V_RECORDER TYPE I,
V_VBELN LIKE VBAP-VBELN,
ORDERHEADERINX LIKE BAPISDH1X.
DATA: BEGIN OF I_ORDERS OCCURS 0,
VBELN LIKE VBAK-VBELN,
POSNR LIKE VBAP-POSNR,
BRGEW(18) TYPE C,
VOLUM(18) TYPE C,
END OF I_ORDERS.
DATA: BEGIN OF I_OUTPUT OCCURS 0,
VBELN LIKE VBAK-VBELN,
POSNR LIKE VBAP-POSNR,
GEWEI LIKE VBAP-GEWEI,
BRGEW LIKE VBAP-BRGEW,
VOLUM LIKE VBAP-VOLUM,
CKWGT TYPE C,
CKVOL TYPE C,
END OF I_OUTPUT.
DATA: BEGIN OF ORDERITEMIN OCCURS 0.
INCLUDE STRUCTURE BAPISDITM.
DATA: END OF ORDERITEMIN.
DATA: BEGIN OF ORDERITEMINX OCCURS 0.
INCLUDE STRUCTURE BAPISDITMX.
DATA: END OF ORDERITEMINX.
DATA: BEGIN OF RETURN OCCURS 0.
INCLUDE STRUCTURE BAPIRET2.
DATA: END OF RETURN.
DATA: BEGIN OF BAPIRETURN OCCURS 0.
INCLUDE STRUCTURE BAPIRET2.
DATA: END OF BAPIRETURN.
PARAMETERS:
P_PATH(45) TYPE C DEFAULT '/usr/users/ftpsapom/' LOWER CASE,
P_FNAME(32) TYPE C DEFAULT '/sweetjo.txt' LOWER CASE.
START-OF-SELECTION.
CONCATENATE PATH AND FILE NAME INTO ONE VARIABLE
CONCATENATE P_PATH P_FNAME INTO V_FILEIN.
OPEN DATASET
IF V_FILEIN IS INITIAL.
MESSAGE E002 WITH 'FILE' V_FILEIN 'DOES NOT CONTAIN ANY DATA!'.
ELSE.
OPEN DATASET V_FILEIN
FOR INPUT
IN TEXT MODE.
IF SY-SUBRC = 0.
READ DATASET
DO.
READ DATASET V_FILEIN INTO I_ORDERS.
IF SY-SUBRC = 0.
APPEND I_ORDERS.
ELSE.
EXIT.
ENDIF.
ENDDO.
CLOSE DATASET
CLOSE DATASET V_FILEIN.
IF SY-SUBRC <> 0.
MESSAGE E002 WITH 'ERROR - CLOSING' V_FILEIN.
ENDIF.
ELSE.
MESSAGE E002 WITH 'ERROR - COULD NOT OPEN' V_FILEIN.
ENDIF.
ENDIF.
SORT AND REMOVE DUPLICATES FROM I_ORDERS
SORT I_ORDERS BY VBELN POSNR.
DELETE ADJACENT DUPLICATES FROM I_ORDERS.
POPULATE I_OUTPUT
LOOP AT I_ORDERS.
SHIFT I_ORDERS-POSNR LEFT DELETING LEADING SPACE.
CONCATENATE '0' I_ORDERS-POSNR INTO I_ORDERS-POSNR.
SELECT SINGLE BRGEW VOLUM
FROM VBAP
INTO (VBAP-BRGEW, VBAP-VOLUM)
WHERE VBELN = I_ORDERS-VBELN
AND POSNR = I_ORDERS-POSNR.
IF SY-SUBRC = 0.
IF VBAP-BRGEW = 0.
I_OUTPUT-CKWGT = 'X'.
ENDIF.
IF VBAP-VOLUM = 0.
I_OUTPUT-CKVOL = 'X'.
ENDIF.
I_OUTPUT-VBELN = I_ORDERS-VBELN.
I_OUTPUT-POSNR = I_ORDERS-POSNR.
I_OUTPUT-GEWEI = 'ST'.
I_OUTPUT-BRGEW = I_ORDERS-BRGEW.
I_OUTPUT-VOLUM = I_ORDERS-VOLUM.
APPEND I_OUTPUT.
CLEAR: I_OUTPUT.
ENDIF.
V_RECIN = V_RECIN + 1.
ENDLOOP.
POPULATE BAPI DATA AND RUN BAPI
CLEAR: ORDERHEADERINX, ORDERITEMIN, ORDERITEMINX,
RETURN, BAPIRETURN.
REFRESH: ORDERITEMIN, ORDERITEMINX, RETURN, BAPIRETURN.
ORDERHEADERINX-UPDATEFLAG = 'U'.
LOOP AT I_OUTPUT WHERE CKWGT = 'X' OR CKVOL = 'X'.
V_RECVBAP = V_RECVBAP + 1.
IF I_OUTPUT-VBELN <> V_VBELN AND SY-TABIX <> 1.
V_RECORDER = V_RECORDER + 1.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = V_VBELN
ORDER_HEADER_INX = ORDERHEADERINX
TABLES
RETURN = RETURN
ORDER_ITEM_IN = ORDERITEMIN
ORDER_ITEM_INX = ORDERITEMINX.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT = 'X'
IMPORTING
RETURN = BAPIRETURN.
WRITE OUT RETURN
LOOP AT RETURN.
WRITE: / RETURN.
ENDLOOP.
WRITE: / BAPIRETURN.
SKIP.
CLEAR: ORDERITEMIN, ORDERITEMINX,
RETURN, BAPIRETURN.
REFRESH: ORDERITEMIN, ORDERITEMINX, RETURN, BAPIRETURN.
ENDIF.
ORDERITEMIN-ITM_NUMBER = I_OUTPUT-POSNR.
ORDERITEMIN-UNTOF_WGHT = I_OUTPUT-GEWEI.
IF NOT I_OUTPUT-CKWGT IS INITIAL.
ORDERITEMIN-GROSS_WGHT = I_OUTPUT-BRGEW.
ORDERITEMINX-GROSS_WGHT = 'X'.
ENDIF.
IF NOT I_OUTPUT-CKVOL IS INITIAL.
ORDERITEMIN-VOLUME = I_OUTPUT-VOLUM.
ORDERITEMINX-VOLUME = 'X'.
ENDIF.
APPEND ORDERITEMIN.
ORDERITEMINX-ITM_NUMBER = I_OUTPUT-POSNR.
ORDERITEMINX-UNTOF_WGHT = 'X'.
ORDERITEMINX-UPDATEFLAG = 'U'.
APPEND ORDERITEMINX.
V_VBELN = I_OUTPUT-VBELN.
ENDLOOP.
RUN BAPI ON LAST ORDER
IF NOT ORDERITEMIN IS INITIAL.
V_RECORDER = V_RECORDER + 1.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = V_VBELN
ORDER_HEADER_INX = ORDERHEADERINX
TABLES
RETURN = RETURN
ORDER_ITEM_IN = ORDERITEMIN
ORDER_ITEM_INX = ORDERITEMINX.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT = 'X'
IMPORTING
RETURN = BAPIRETURN.
WRITE OUT RETURN
LOOP AT RETURN.
WRITE: / RETURN.
ENDLOOP.
WRITE: / BAPIRETURN.
SKIP.
ENDIF.
WRITE OUT RECORD COUNT FROM FILE
WRITE: / 'RECORD COUNT FROM FILE ', V_RECIN.
SKIP.
WRITE OUT RECORD COUNT FROM FILE
WRITE: / 'RECORD COUNT OF LINES TO CHANGE ', V_RECVBAP.
SKIP.
WRITE OUT RECORD COUNT FROM FILE
WRITE: / 'RECORD COUNT OF ORDERS TO CHANGE ', V_RECORDER.
SKIP.
TOP OF PAGE
TOP-OF-PAGE.
WRITE:/1(5) TEXT-H01, 6(8) SY-DATUM MM/DD/YY,
100(8) TEXT-H02, 126(8) SY-PAGNO.
WRITE:/1(5) TEXT-H03, 6(8) SY-UZEIT USING EDIT MASK '__:__:__',
20(77) TEXT-H04,
100(8) TEXT-H05, 108(25) SY-REPID.
WRITE:/1(6) TEXT-H06, 8(12) SY-UNAME,
20(4) TEXT-H07, 25(32) SY-HOST,
100(13) TEXT-H08, 121(8) SY-SYSID,
129 '/', 130(3) SY-MANDT.
ULINE.
SKIP.
Reward points if useful
Regards
Anji

Error in sales order creation using bapi

Hi,
Iam trying to create sales order by using BAPI_SALESORDER_CREATEFROMDAT1 and when iam trying to execute
the function module by passing all th eparameters and iam getting the error as
inspite of entering sold_to_party and ship_to_party details in table ORDER_PARTNERS
"enter the sold_to_party or ship to party details"
please help me out in this isue its an urgent.
Thanks.
sayed.

Can you share the codes ?
Thanks.
Ashish

Reena Prabhakar - Sales order creation Using BAPI

Hi Reena,
This is Dinesh,i also face problem in Sales order creation using BAPI if you can send me the code it would be great help to me.
Regards,
Dinesh

Anyhow, here is the code that I am using currently which works perfectly well. Not sure if it will be of any help to you, since the values to the BAPI come from the Webdynpro application. I have values stored in my "Test data directory" which I use for testing from the backend.
FUNCTION ztest.
Call the BAPI to create Sales Order
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
      order_header_in     = l_order_header
    IMPORTING
      salesdocument       = l_salesdocument
    TABLES
      return              = it_return
      order_items_in      = it_order_items
      order_partners      = it_order_partners
      order_schedules_in = it_order_schdl
      order_conditions_in = it_order_conditions
      order_text          = it_order_text.
READ TABLE it_return WITH KEY type = 'E'.
IF sy-subrc = 0.
*-- error occured
    CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
ELSE.
*-- no error
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ENDIF.
ENDFUNCTION.

Need sales order creation using bapi in oops

need code for sales order creation using bapi in oops

hi rocky,
could you pls give a bit explanation on what you are expecting.
regards,
Pavan

Mass sales order creation using BAPI

Dear All,
Can anyone help in mass sales order creation using Bapi BAPI_SALESORDER_CREATEFROMDAT2.
For example if i want to create 3 sales order with three item per order . i am populating
HEADER = 3 Records
Item = 9 records
schedule = 9 records
partner = 1 record.
Then after populating the records I am calling Bapi BAPI_SALESORDER_CREATEFROMDAT2
to create order. It should have created three order but unfortunately it creates
only one sales order. I debugged and found that records are correct both in header,
item, scheudle and partners.
Could you please guide me what I am missing for creation of mass orders.
I appreciate your time and many thanks in advance.
cheers
chandra

Hi Chandra,
Do like this.
Loop at Header table into wa_header.
*-- Move BAPI Header data
Loop at item table into wa_item where condition.
*-- in this move all Item and Schedule line item to the BAPI.
At end of item .
Use the below function modules.
BAPI_SALESORDER_CREATEFROMDAT2
BAPI_TRANSACTION_COMMIT.
Endloop.
Endloop.
Regards,
Balavardhan.K

LSMW - Sales Order Migration using RVINVB10

Similar Messages

Maybe you are looking for