Wrong CFOP determination via BAPI BAPI_SALESORDER_CREATEFROMDAT2

Hello Gurus,
I need some help on the following:
When I create a Sales document manually (tcode VA01), CFOP code is determined correctly. But when I try to do the same process, using BAPI BAPI_SALESORDER_CREATEFROMDAT2, with same data ( Sold-To Party and Ship-To Party, material code...), CFOP code is determined wrong.
The SD consultant already checked the configuration in SPRO and everything looks fine.
I went thru debug and found that the FM SD_PARTNER_DATA_GET is called for both process, but internal table GVT_LOCAL_MEMORY is NOT filled when running BAPI and it IS filled when running VA01 (this internal table has VBPA - Partners - data).
This causes a NO_OBJECT_FOUND exception, which makes the program to read the address data from KNA1 (FM J_1B_SD_ADDRESS_READ), with the wrong address number, instead the address form Sales Order, since it's an On Time Customer - WE.
The weirdest thing is that it was working perfectly 3 days ago. We first noticed the problem in QAS environment, but in DEV Sandbox the error is the same now.
The scenario is an Interstate Sales Order. We are about 30 days from Go-Live and now this came thru.
Thanks in advance!

Hi Thiago,
I succeeded to let it work even without SD_SALES_DOCUMENT_INIT.
You have two tables used by BAPI_SALESORDER_CREATEFROMDAT2 order_items_in and order_items_inx
Field cfop_long in all order_items_in lines and in all order_items_inx should be empty
Don't forget the BAPI_TRANSACTION_COMMIT after the BAPI_SALESORDER_CREATEFROMDAT2
Tell me if it's not working for you ...
Moez.

Similar Messages

Problem for bapi: BAPI_SALESORDER_CREATEFROMDAT2

Hi all,
when creating sales order via BAPI_SALESORDER_CREATEFROMDAT2 in the testing mode,
it returns a sales order no successfully.
But when a veiw it via VA03, the system says that this sales order doesn't exist.
What's wrong? Thanks

Hi Macy,
The Sales order will not be saved in the database till the time you call the bapi from an ABAP Program.
Also you have call the FM BAPI_TRANSACTION_COMMIT after the calling the BAPI BAPI_SALESORDER_CREATEFROMDAT2.
If you are simply testing the BAPI from SE37, no Sales Order will be saved in the database tables and hence will not be seen in VA03. Testing BAPI from se37 is simply a simulation of the sales order.
So create a test program, call the bapi
BAPI_SALESORDER_CREATEFROMDAT2.. pass all the required data.
Then if sy-subrc = 0
call FM BAPI_TRANSACTION_COMMIT....
It will work...
Lokesh
Pls. reward appropriate points

Data transfer thru lsmw via bapi

how to perform data transfer thru lsmw via bapi.
Thanks.
Regards
Rama

HI
BAPI stands for Business API(Application Program Interface).
A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sappoint.com/abap/bapiintro.pdf
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
u can check the below the material also
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
[for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/5e114a4a1611d1894c0000e829fbbd/frameset.htm
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
BAPI - BAPIs (Business Application Programming Interfaces) are the standard SAP interfaces. They play an important role in the technical integration and in the exchange of business data between SAP components, and between SAP and non-SAP components. BAPIs enable you to integrate these components and are therefore an important part of developing integration scenarios where multiple components are connected to each other, either on a local network or on the Internet.
BAPIs allow integration at the business level, not the technical level. This provides for greater stability of the linkage and independence from the underlying communication technology.
LSMW- No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.
The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.
So although it was designed for uploading of legacy data it is not restricted to this use.
We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.
The SAP transaction code is 'LSMW' for SAP version 4.6x.
Check your procedure using this Links.
BAPI with LSMW
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI
For document on using BAPI with LSMW, I suggest you to visit:
http://www.****************/Tutorials/LSMW/BAPIinLSMW/BL1.htm
What are the methods to migrate data from a legacy system to SAP?
LSMW is used for migrating data from a legacy system to SAP system, or from one SAP system to another.
Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods for processing the legacy data.
The LSMW comprises the following main steps:
Read data (legacy data in spreadsheet tables and/or sequential files).
Convert data (from the source into the target format).
Import data (to the database used by the R/3 application.
But, before these steps, you need to perform following steps :
Define source structure : structure of data in the source file.
Define target structure : structure of SAP that receives data.
Field mapping: Mapping between the source and target structure with conversions, if any.
Specify file: location of the source file
Of all the methods used for data migration like BDC, LSMW , Call Transaction which one is used most of the time?
How is the decision made which method should be followed? What is the procedure followed for this analysis?
All the 3 methods are used to migrate data. Selection of these methods depends on the scenario, amount of data need to transfer. LSMW is a ready tool provided by SAP and you have to follow some 17 steps to migrate master data. While in BDCs Session method is the better choice because of some advantages over call transaction. But call transaction is also very useful to do immediate updation of small amout of data. (In call transaction developer has to handle errors).
SO Bottom line is make choice of these methods based of real time requirements.
These methods are chosen completely based on situation you are in. Direct input method is not available for all scenario, else, they are the simplest ones. In batch input method ,you need to do recording for the transaction concerned. Similarly, IDoc, and BAPI are there, and use of these need to be decided based on the requirement.
Try to go through the some material on these four methods, and implement them. You will then have a fair idea about when to use which
You can create lsmw for data migration as follows (using session method):
Example for xk01 (create vendor)
Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
1. TCode : LSMW.
2. Enter Project name, sub project name and object name.
Execute.
3. Maintain object attributes.
Execute
select Batch Input recording
goto->Recording overview
create
recording name.
enter transaction code.
start recording
do recording as per ur choice.
save + back.
enter recording name in lsmw screen.
save + back
Now there will be 14 steps.
2. MAINTAIN SOURCE STRUCTURES.
Here you have to enter the name of internal table.
display change
create
save + back
3. MAINTAIN SOURCE FIELDS.
display change
select structure
source_fields->copy fields.
a dialogue window will come .
select -> from data file
apply source fields
enter No. of fields
length of fields
attach file
save + back
4. MAINTAIN STRUCTURE RELATIONS
display change
save + back
5. MAINTAN FIELD MAPPING & CONVERSION RULE
display change
click on source field, select exact field from structue and enter
repeat these steps for all fields.
save+back
6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
execute
save + back
7. SPECIFY FILES.
display change
click on legacy data
attah flat file
give description
select tabulatore
enter
save + back
8. ASSIGN FILE
execute
display change
save + back
9. IMPORT DATA.
execute
display change
save + back
10. DISPLAY IMPORTED DATA
enter ok, it willl show records only.
back
11. CONVERT DATA
execute
display change
save + back
12. DISPLAY CONVERTED DATA
execute
display change
save + back
13. CREATE BATCH INPUT SESSION
tick keep batch input folder
F8
back
14. RUN BATCH INPUT SESSION.
sm35 will come
Object name will be shown here
select object & process
Regards
Pavan

Order quantity in BAPI BAPI_SALESORDER_CREATEFROMDAT2

Hi,
I'm using BAPI 'BAPI_SALESORDER_CREATEFROMDAT2' to create a sale order.
But the order quantity isn't upadate when I check the sales order number.
The field I used is target_qty in BAPISDITM.
Is the field wrong or some other problems?
Best Regards,
Rachel

Hi,
I created SO using BAPI_SALESDOCU_CREATEFROMDATA1. while filling the header and item data, i used to do the following,
If you are passing some value to 'target_qty', make sure that you are filling the sales_items_inx-req_qty with 'X'. then pass them to the tables import parameters. Please refer the following code.
fs_sorder-doc_type = w_auart.
fs_sorderx-doc_type = c_flag.
fs_sorder-sales_org = w_vkorg.
fs_sorderx-sales_org = c_flag.
fs_sorder-distr_chan = w_vtweg.
fs_sorderx-distr_chan = c_flag.
fs_sorder-division = w_spart.
fs_sorderx-division = c_flag.
fs_sorderx-updateflag = c_flag.
fs_partner-partn_role = c_pship.
fs_partner-partn_numb = w_pship.
APPEND fs_partner TO t_partner.
fs_partner-partn_role = c_psold.
fs_partner-partn_numb = w_psold.
APPEND fs_partner TO t_partner.
loop at t_mdata into fs_mdata.
    fs_item-itm_number = fs_mdata-posnr.
    fs_itemx-itm_number = c_flag.
    fs_item-material    = fs_mdata-matnr.
    fs_itemx-material   = c_flag.
    fs_item-target_qty = fs_mdata-kwmeng.
    fs_itemx-target_qty = c_flag.
    fs_item-item_categ = fs_mdata-pstyv.
    fs_itemx-item_categ = c_flag.
    fs_itemx-updateflag = c_flag.
      APPEND fs_item TO t_item.
      APPEND fs_itemx TO t_itemx.
    fs_sline-ITM_NUMBER = fs_mdata-posnr.
    fs_slinex-ITM_NUMBER = c_flag.
    fs_sline-SCHED_LINE = c_sline.
    fs_slinex-SCHED_LINE = c_flag.
    fs_sline-REQ_QTY     = fs_mdata-kwmeng.
    fs_slinex-REQ_QTY    = c_flag.
      APPEND fs_sline TO t_sline.
      APPEND fs_slinex TO t_slinex.
endloop.                             " Loop t_mdata
ENDFORM.                               " data_fill
* FORM CREATE_SO                                                     *
* This subroutine calls a BAPI BAPI_SALESDOCU_CREATEFROMDATA1 for    *
* creating a sales document.                                         *
* There are no interface parameters to be passed to this subroutine. *
FORM create_so .
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
    EXPORTING
      sales_header_in     = fs_sorder
      sales_header_inx    = fs_sorderx
    IMPORTING
      salesdocument_ex    = w_sonum
    TABLES
      return              = t_return
      sales_items_in      = t_item
      sales_items_inx     = t_itemx
      sales_partners      = t_partner
      sales_schedules_in = t_sline
      sales_schedules_inx = t_slinex.
ENDFORM.                               " create_SO
Hope this helps.

Problems with running BAPI   BAPI_SALESORDER_CREATEFROMDAT2

Hi all,
I’ve got a problem running BAPIs in SD invironment.
I’m creating contract releases in SD via BAPI.
First I run BAPI BAPISORDER_GETDETAILEDLIST in my program to get detaildata of the contract.
Then I run the BAPI   BAPI_SALESORDER_CREATEFROMDAT2 filled with contract reference data and in addition with order data to create the contract release.This works properly so far. On both sides in the contract and in he contract release I find the correct document flow. Means: in document flow of the contract I find all the releases created . Also I find the contract in the documentflow of the releases.
But…something does not work: In the contract the released values are not updated. When I create a release manually, the release values are accumulated in the contract in field ‘value released’ under flag ‘item detail’. But this does not work, when the leases are created via BAPI. However I checked several parameters in the BAPIS but I cannot find something that leads to an update .
Can somebody help me and can tell me what is to be done to get this field updated? Thanks in advance.
same in German...
Ich habe ein Problem mit BAPIs im SD.
Ich erzeuge Abrufe zum Kontrakt im SD mittels BAPIs.
Zuerst lasse ich den BAPI BAPISORDER_GETDETAILEDLIST laufen, um mittels Kontraktnummer alle Daten zum Kontrakt zu bekommen. Dann lasse ich den BAPI   BAPI_SALESORDER_CREATEFROMDAT2 gefüllt mit SD-Abrufdaten und den Referenzdaten des Kontraktes laufen Dies funktioniert soweit sehr gut. Sowohl im Kontrakt als auch im Abruf sind jeweils die übergeordneten bzw. untergeordneten Vertiebsbelege zu sehen. Die Referenz wird also hergestellt. Jedoch wird im Kontrakt nicht die Abrufwerte aufsummiert. Normalerweise wird bei manueller Erstellung der Abrufe im Kontrakt die jeweilgen abgerufenen Werte gegen den Kontraktwert aufsummiert (Feld abgerufene Werte im Kontrakt unter Reiter ‚Positionsdetail‘. Ich habe alle möglichen Parameter im BAPI geprüft und getestet aber nichts gefunden, was mir die abgerufenen Werten aufsummiert.
Kann mir dazu einen Tip geben, was ich tun kann, damit auch die Werte richtig referenzieren ? Danke im Voraus.

the usage of exactly this BAPIs in the way I described is in according to SAP note 370988.
BAPI_SALES_DEL_SCHEDULE_CREATE ist for SD schedule agreements and not for SD contracts and does not offer Input parameters for e.g. adding price conditions what is needed for my task.
The field in contract I mentioned e.g. in Transaction VA42 VA43 is filled / gets its Information out of Infostructure/table S135. The BAPI seems not be able to fill this structure while creating the contract release.
I'm looking for example an input parameter I did not found already or any other option that leads to an update of infostructure S135 while creating/posting a release via BAPI.

Referencing Sales Order to a Quotation via BAPI

Dear all,
I encouter problems to reference a Sales Order to a Quotation when I try to use the SAP BAPI 'BAPI_SALESORDER_CREATEFROMDAT2'. Even though later when I managed to create the referencing on both the Sales Order Header and Sales Order Line to the Quotation, the system still doesn't closed the Quotation status as Completed. This has caused the Quotation remains active and open for other Sales Order for referencing. Any ideas?
Thank you and regards;
-ah tiang-

Hi!
According to OSS note 370988 it seems you can't create sales order properly with reference to quotation using BAPI_SALESORDER_CREATEFROMDAT2 in straight-forward way:
Symptom
This note describes the problems of the 'Create with reference' function when using BAPIs to create sales documents.
If you are working online, you can use this function module to create a sales document with reference to an existing sales document or a billing document (for example, a debit or credit memo request) according to fixed rules. The rules for transferring information from the source document to the target document are defined in the copying control on header and item level. The creation with reference permits an item selection.
When you use BAPIs in SD, a function of this type is not fully available. A reference is only possible for a quantity contract, so that the target quantity of the contract can be reduced by the order quantity of the sales document. Furthermore, the document flow is also updated.
As an alternative to 'Create with reference' in Transaction VA01, two variants are provided for solving the 'Create with reference' problem in the BAPI.
1. Create a '1:1 ' - that is, a document copy of a sales document (customer quotation, order) with 'BAPI_SALESDOCUMENT_COPY'. At this point, you cannot create the 1:1 copy of either a billing document or a delivery.
2. Create a sales document that refers to an existing document with 'BAPISDORDER_GETDETAILEDLIST' and 'BAPI_SALESORDER_CREATEFROMDAT2'.
Reason and Prerequisites
As of yet, no method exists for creating a sales document that refers to an existing document.
Solution
For solution No. 1
1. Create the documents using the BAPI_SALESDOCUMENT_COPY function module. However, this only permits a 1:1 copy without factoring out individual items.
2. After you have created the document copy, you can use a change BAPI to edit this copy.
For solution No. 2
1. Collect the data for the reference document (for example a customer quotation) with the 'BAPISDORDER_GETDETAILEDLIST' function module. In the example code, focus exclusively on the partners, items, schedule lines and conditions.
2. Prepare the Data. Execute the 'copying control' manually. This way, you decide which values are to be transferred.
3. Create the sales document using the 'BAPI_SALESORDER_CREATEFROMDAT2' function module by transferring the prepared data.
4. Finally, you must remove a COMMIT WORK so that the sales document can be written into the database.
An example of solution 2 is attached as a text file. You are allowed to select items and quantities for example, if you use input parameters. If there are no entries, then transfer 1:1 from the reference document. When you enter the 'condition type' parameter, you can determine whether conditions are copied or recalculated ('G' for transferring from the preceding document; 'B' or ' ' for re-determining, and 'C' for re-determining with transfer of the manual elements).
Hope it helps.
And welcome here on SDN!
Regards,
Maxim.

Error in bapi BAPI_SALESORDER_CREATEFROMDAT2

Hi,
I am using BAPI BAPI_SALESORDER_CREATEFROMDAT2 for sales order upload.
Now the problem is that i am entering value in condition type PR00 in condition table for BAPI.
After data gets uploaded and saled order is created; In VA02 when i check for the conditions it shows me 2 values for PR00 . One which i entered in BAPI and other which is coming from system.
I have made the settings , So while calculating final value its taking manual enter value only but it
still displays the system generated value and thats what i dont want.
Can there be a way with which i can overwrite(using BAPI) the system generated value for condition type 'PR00'.
regards
vivek

Vivek-
You need to set the BAPI data to overwrite the pricing conditions that automatically generate.
When you set up the pricing condition table to be passed to the BAPI, you need to set the "Step Number" - COND_ST_NO and "Condition Counter" - COND_COUNT so it overwrites the standard pricing that wants to automatically determine. You can get the step number from your pricing procedure. For the counter, just check the counter number of a sales order that was created manually and match it. In my case, it was '01', which I believe is typical.
Hope this helps,
Mark

Not able to create sales order using BAPI - BAPI_SALESORDER_CREATEFROMDAT2

Hi Experts,
I am not able to create sales order . I am using BAPI - BAPI_SALESORDER_CREATEFROMDAT2
to create sales order .I am passing external sales order number to the parameter
SALESDOCUMENTIN.
I am getting following error.
"524   |Only quantity 1 EA is allowed (Item 00001"
Here EA is UOM(Unit of measurement).
Below is the sample program through which i am trying to create the sales order.
*& Report ZSDC_SALES_TEST
report zsdc_sales_test.
*DATA: wa_bapi_header    TYPE bapisdhd1.
Include Name    - ZSDC_SALES_ORD_UPLOAD_TOP
Program Name    - ZSDC_SALES_ORD_UPLOAD_1393
Program Title   - Include for Data Declaration and selection screen
Created by      - Lalitha W
Created on      - 18-Nov-2008
Object ID       - SD_C_1393_SALES_ORDER_UPLOAD
Request Id      - SD3K905579
Description - This is a common INCLUDE for data declarations and
*selection screen details.
                        HISTORY
Date    |Developer |Req by    | Description              |Reference ID
        |          |          |                          |
        |          |          |                          |
                           TYPE-POOLS
*TYPE-POOLS: truxs, abap, slis.
                          TABLES
*TABLES: t100.
                           TYPES
types:begin of   ty_header,
        auart(4)    type c,    " Sales Order Type
        vkorg(4)    type c,    " Sales Organization
        vtweg(2)    type c,    " Distrubution Channel
        spart(2)    type c,    " Division
        kunnr_1(10) type c,    " Sold to Party
        kunnr_2(10) type c,    " Ship to Party
        augru(3)    type c,    " Order Reason
        bstkd(35)   type c,    " PO Number
        bstdk(10)   type c,    " PO Date
        ketdat(10) type c,    " Required Delivery Date
        zterm(4)    type c,    " Payment Terms
        inco1(3)    type c,    " Inco Terms -1
        inco2(28)   type c,    " Inco Terms -2
        prsdt(10)   type c,    " pricing date
        waerk(5)    type c,    " Document Currency
        vkbur(4)    type c,    " Sales Office
        vkgrp(3)    type c,    " Sales group
        pltyp(2)    type c,    " Price List type
        kdgrp(2)    type c,    " Customer Group
        bstkd_e(35) type c,    " Ship-to-party PO number
        submi(10)   type c,    " Collective Number
        bname(35)   type c,    " Name
        ihrez(12)   type c,    " Your Reference
        kschl_1(4)   type c,    " Condition Type
        kbetr_1(11) type c,    " Amount
        kschl_2(4)   type c,    " Condition Type
        kbetr_2(11) type c,    " Amount
        kschl_3(4)   type c,    " Condition Type
        kbetr_3(11) type c,    " Amount
       partner_1(25) TYPE c,    " Partner(Bill To Party Number)
       partner_2(25) TYPE c,    " Partner(Payer Number)
       partner_3(25) TYPE c,    " Partner(Sales Responsible Number)
       partner_4(25) TYPE c,    " Partner(Order admin)
       partner_5(25) TYPE c,    " Partner(Contact person)
        partner_1(10) type c,    " Partner(Bill To Party Number)
        partner_2(10) type c,    " Partner(Payer Number)
        partner_3(10) type c,    " Partner(Sales Responsible Number)
        partner_4(10) type c,    " Partner(Order admin)
        partner_5(10) type c,    " Partner(Contact person)
        tdspras_1(2) type c,
        text_1(500)   type c,    " Text Before Items Z012
        tdspras_2(2) type c,
        text_2(500)   type c,    " Invocie Up Z034
        tdspras_3(2) type c,
        text_3(500)   type c,    " Invocie Down Z035
        tdspras_4(2) type c,
        text_4(500)   type c,    " Customer Reference Continue Z018
        tdspras_5(2) type c,
        text_5(500)   type c,    " Dispatch Marks/ Order Z019
        tdspras_6(2) type c,
        text_6(500)   type c,    " Ordered By Z003
        tdspras_7(2) type c,
        text_7(500)   type c,    " Sales Parameters Z002
        kvgr1(3)      type c,    " Industry
        kvgr2(3)      type c,    " customer BU
end of ty_header.
types: begin of ty_item,
          bstkd(35)     type c,    " PO Number
          bstdk(10)     type c,    " PO Date
          bstkd_e(35)   type c,    " Ship-to-party PO number
          posnr(6)      type c,    " POSTION NUMBER
          matnr(18)     type c,    " Material Number
          kwmeng(18)    type c,    " Order Quantity
          pstyv(4)      type c,    " Sales doc. item categ
          kursk(18)     type c,    " EXCHANGE RATE****
          ffprf(8)      type c,    " DIP PROFILE
          werks(4)      type c,    " Delivering Plant
          vstel(4)      type c,    " SHIPPING POINT
          lgort(4)      type c,    " STORAGE LOCATION
          route(6)      type c,    " Route
          kurrf(18)     type c,    " EXCHANGE RATE-FI
          ntgew(18)     type c,    " Net Weight
          brgew(18)     type c,    " Gross Weight
          gewei(3)      type c,    " Weight Unit
          prctr(10)     type c,    " profit center
          abgrs(6)      type c,    " RESULT ANALYSIS KEY
          kalsm_k(4)    type c,    " COSTING SHEET
          kschl_1(4)    type c,    " Condition Type
          kbetr_1(11)   type c,    " Amount
          kschl_2(4)    type c,    " Condition Type
          kbetr_2(11)   type c,    " Amount
          kschl_3(4)    type c,    " Condition Type
          kbetr_3(11)   type c,    " Amount
          text_1(500)    type c,    " material Text 0001
          tdspras_1(1)   type c,
          text_2(500)    type c,    " Pr Text 9001
          tdspras_2(1)   type c,
       end of ty_item.
types: begin of ty_schedule_line,
         bstkd(35)       type c, "PO number
         bstdk(10)       type c, "PO date
         bstkd_e(35)     type c, "Ship-to-party PO number
         posnr(6)        type c, "sales doc.Item
         etdat(10)       type c, "Schedule line date
         wmeng(2)        type c, "Order Quantity
        end of ty_schedule_line.
types: begin of ty_err ,
        auart(4)    type c,    " Sales Order Type
        vkorg(4)    type c,    " Sales Organization
        vtweg(2)    type c,    " Distrubution Channel
        spart(2)    type c,    " Division
        kunnr_1(10) type c,    " Sold to Party
        kunnr_2(10) type c,    " Ship to Party
        augru(3)    type c,    " Order Reason
        bstkd(35)   type c,    " PO Number
        bstdk(10)   type c,    " PO Date
        ketdat(10) type c,    " Required Delivery Date
        zterm(4)    type c,    " Payment Terms
        inco1(3)    type c,    " Inco Terms -1
        inco2(28)   type c,    " Inco Terms -2
        prsdt(10)   type c,    " pricing date
        waerk(5)    type c,    " Document Currency
        vkbur(2)    type c,    " Sales Office
        vkgrp(3)    type c,    " Sales group
        pltyp(2)    type c,    " Price List type
        kdgrp(2)    type c,    " Customer Group
        bstkd_e(35) type c,    " Ship-to-party PO number
        submi(10)   type c,    " Collective Number
        bname(35)   type c,    " Name
        ihrez(12)   type c,    " Your Reference
        kschl_1(4)   type c,    " Condition Type
        kbetr_1(11) type c,    " Amount
        kschl_2(4)   type c,    " Condition Type
        kbetr_2(11) type c,    " Amount
        kschl_3(4)   type c,    " Condition Type
        kbetr_3(11) type c,    " Amount
        partner_1(25) type c,    " Partner(Bill To Party Number)
        partner_2(25) type c,    " Partner(Payer Number)
        partner_3(25) type c,    " Partner(Sales Responsible Number)
        partner_4(25) type c,    " Partner(Order admin)
        partner_5(25) type c,    " Partner(Contact person)
        tdspras_1(2) type c,
        text_1(500)   type c,    " Text Before Items Z012
        tdspras_2(2) type c,
        text_2(500)   type c,    " Invocie Up Z034
        tdspras_3(2) type c,
        text_3(500)   type c,    " Invocie Down Z035
        tdspras_4(2) type c,
        text_4(500)   type c,    " Customer Reference Continue Z018
        tdspras_5(2) type c,
        text_5(500)   type c,    " Dispatch Marks/ Order Z019
        tdspras_6(2) type c,
        text_6(500)   type c,    " Ordered By Z003
        tdspras_7(2) type c,
        text_7(500)   type c,    " Sales Parameters Z002
        kvgr1(3)      type c,    " Industry
        kvgr2(3)      type c,    " customer BU
        message(600) type c,
end of ty_err.
types: begin of ty_t685a,
        kschl type kschl,
        krech type krech,
      end of ty_t685a.
                   INTERNAL TABLES
***header
data: g_krech_1(4)    type c,    " Calculation type for condition
       g_krech_2(4)    type c,    " Calculation type for condition
       g_krech_3(4)    type c.    " Calculation type for condition
      g_krech_4(4)    TYPE c,    " Calculation type for condition
      g_krech_5(4)    TYPE c,    " Calculation type for condition
      g_krech_6(4)    TYPE c,    " Calculation type for condition
      g_krech_7(4)    TYPE c,    " Calculation type for condition
      g_krech_8(4)    TYPE c,    " Calculation type for condition
      g_krech_9(4)    TYPE c,    " Calculation type for condition
      g_krech_10(4)   TYPE c,    " Calculation type for condition
      g_krech_11(4)   TYPE c,    " Calculation type for condition
      g_krech_12(4)   TYPE c,    " Calculation type for condition
      g_krech_13(4)   TYPE c,    " Calculation type for condition
      g_krech_14(4)   TYPE c,    " Calculation type for condition
      g_krech_15(4)   TYPE c,    " Calculation type for condition
      g_krech_16(4)   TYPE c,    " Calculation type for condition
      g_krech_17(4)   TYPE c,    " Calculation type for condition
      g_krech_18(4)   TYPE c,    " Calculation type for condition
      g_krech_19(4)   TYPE c,    " Calculation type for condition
      g_krech_20(4)   TYPE c.    " Calculation type for condition
Items
data:   g_krech_item_1(4)   type c,    " Calculation type for condition
        g_krech_item_2(4)   type c,    " Calculation type for condition
        g_krech_item_3(4)   type c.    " Calculation type for condition
       g_krech_item_4(4)   TYPE c,    " Calculation type for condition
       g_krech_item_5(4)   TYPE c,    " Calculation type for condition
       g_krech_item_6(4)   TYPE c,    " Calculation type for condition
       g_krech_item_7(4)   TYPE c,    " Calculation type for condition
       g_krech_item_8(4)   TYPE c,    " Calculation type for condition
       g_krech_item_9(4)   TYPE c,    " Calculation type for condition
       g_krech_item_10(4) TYPE c,    " Calculation type for condition
       g_krech_item_11(4) TYPE c,    " Calculation type for condition
       g_krech_item_12(4) TYPE c,    " Calculation type for condition
       g_krech_item_13(4) TYPE c,    " Calculation type for condition
       g_krech_item_14(4) TYPE c,    " Calculation type for condition
       g_krech_item_15(4) TYPE c,    " Calculation type for condition
       g_krech_item_16(4) TYPE c.    " Calculation type for condition
data: it_t685a type standard table of ty_t685a.
data: wa_bapi_header    type bapisdhd1,
     wa_bapi_headerx   TYPE bapisdhd1x,
      it_bapi_item      type table of bapisditm,
     it_bapi_itemx     TYPE TABLE OF bapisditmx,
      it_bapi_cond      type table of bapicond,
     it_bapi_condx     TYPE TABLE OF bapicondx,
      it_bapi_partner   type table of bapiparnr,
      it_bapi_shdl      type table of bapischdl,
     it_bapi_shdlx     TYPE TABLE OF bapischdlx,
     it_bapi_order_text type TABLE OF BAPISDTEXT,
      it_bapireturn     type table of bapiret2.
data: wa_bapi_item       like line of it_bapi_item,
      wa_bapi_itemx      LIKE LINE OF it_bapi_itemx,
       wa_bapi_cond       like line of it_bapi_cond,
      wa_bapi_condx      LIKE LINE OF it_bapi_condx,
       wa_bapi_partner    like line of it_bapi_partner,
       wa_bapi_shdl       like line of it_bapi_shdl,
      wa_bapi_shdlx      LIKE LINE OF it_bapi_shdlx,
      wa_bapi_order_text like LINE OF it_bapi_order_text,
       wa_bapireturn      like line of it_bapireturn.
*DATA: zmode(1) VALUE 'N'.
data: it_header      type standard table of ty_header.
*DATA: it_temp_header TYPE STANDARD TABLE OF ty_header.
data: it_item        type standard table of ty_item.
*DATA: it_temp_item   TYPE STANDARD TABLE OF ty_item.
data: it_err         type standard table of ty_err.
data: it_fline1 type standard table of tline,
      wa_fline1 type tline.
data: it_thead1 type thead.
data: it_fline2 type standard table of tline,
      wa_fline2 type tline.
data: it_thead2 type thead.
data: it_fline3 type standard table of tline,
      wa_fline3 type tline.
data: it_thead3 type thead.
data: it_fline4 type standard table of tline,
      wa_fline4 type tline.
data: it_thead4 type thead.
data: it_fline5 type standard table of tline,
      wa_fline5 type tline.
data: it_thead5 type thead.
data: wa_header         like line of it_header,
      wa_item           like line of it_item,
      wa_err            type ty_err,
     wa_bill           LIKE LINE OF it_bill,
     wa_bill1          LIKE LINE OF it_bill,
      wa_iterr          like line of it_err,
      wa_t685a          like line of it_t685a.
     wa_bill_item TYPE ty_bill_item.
data: it_schedule_line type standard table of ty_schedule_line,
      wa_schedule_line type ty_schedule_line.
data: sales_order_no     type bapivbeln-vbeln.
data: ext_sales_order_no type bapivbeln-vbeln.
Variable to be used to separate the fields which are concatenated by a
runtime character
*DATA: g_tabchar(1) TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.
*DATA: wa_truxs_t_text_data TYPE truxs_t_text_data.
*DATA: g_filename      TYPE string,
     g_path          TYPE string,
     g_fullpath      TYPE string,
     g_user_action   TYPE i,
     g_file_encoding TYPE abap_encoding.
*DATA : g_text(8192),
data : g_mstring1(100) type c,
      g_mstring2(100) type c,
      g_mstring3(100) type c,
      g_mstring4(100) type c,
      g_mstring5(100) type c.
data: g_count1 type ebelp,
      g_str_count1(6) type c.
data: g_count type ebelp,
      g_str_count(6) type c.
*DATA: f_subrc      LIKE sy-subrc,
     f_subrc1     LIKE sy-subrc,
     f_error(500) TYPE c,
     item1(27)    TYPE c,
     item2(27)    TYPE c,
     item3(27)    TYPE c,
     item4(27)    TYPE c,
     i            TYPE ekpo-ebelp.
*DATA: g_billplan_header TYPE c,
     g_billplan_item TYPE c.
data : g_external_so type vbak-vbeln. "SO
                      SELECTION-SCREEN
selection-screen begin of block frame1 with frame title text-001 .
parameters:p_file1 type rlgrap-filename, "OBLIGATORY, "Header data.
           p_file2 type rlgrap-filename, "OBLIGATORY, "Item Data.
           p_file3 type rlgrap-filename,            "Schedule line.
           p_file4 type rlgrap-filename ."OBLIGATORY. "Error file.
selection-screen end of block frame1.
start-of-selection.
wa_bapi_header-doc_type     = 'Z0MX'. "order type
wa_bapi_header-sales_org    = '0130'."sales org
wa_bapi_header-distr_chan   = '13'. "distr channel
wa_bapi_header-division     = '13'. "division
Old code from copied program
wa_bapi_header-purch_no_s   = wa_header-kunnr_2. " Ship to party
New code as required in Finland project
We are using to Header ->Order Tab -> Ship to Party -> Purchase order no (BSTKD_E) to store Old legacy SO number
wa_bapi_header-purch_no_s   = 'MX100443'. "External SO i.e Old legacey SO number
wa_bapi_header-ref_1_s      = '0000666666'. "Sold to party
wa_bapi_header-ord_reason   = wa_header-augru.
wa_bapi_header-purch_no_c   = 'ddr1234'.    " PO number
wa_bapi_header-purch_date   = sy-datum.    " PO date
wa_bapi_header-req_date_h   = sy-datum.   " Required Delivery Date
wa_bapi_header-pmnttrms     = '01'.    " Payment Terms
wa_bapi_header-incoterms1   = wa_header-inco1.
wa_bapi_header-incoterms2   = wa_header-inco2.
wa_bapi_header-price_date   = wa_header-prsdt.    " Pricing date
wa_bapi_header-currency     = wa_header-waerk.    " Document Currency
wa_bapi_header-sales_grp = wa_header-vkgrp. " Sales group
wa_bapi_header-price_list   = wa_header-pltyp. " Price list type
wa_bapi_header-cust_group   = wa_header-kdgrp.   " Cust Group
wa_bapi_header-ship_type    = wa_header-vsart.   " Shipping Type
wa_bapi_header-purch_no_s   = wa_header-bstkd_e. " Ship-to-party po number
wa_bapi_header-collect_no   = wa_header-submi.   " Collective No.
wa_bapi_header-name         = wa_header-bname.   " Name
wa_bapi_header-ref_1        = wa_header-ihrez.   " Your Reference
wa_bapi_header-cust_grp1    = wa_header-kvgr1.   " Industry
wa_bapi_header-cust_grp2    = wa_header-kvgr2.   " Customer BU
*ENDFORM.                    " f_header
IF wa_header-partner_1 IS NOT INITIAL.
    wa_bapi_partner-partn_role = 'AG'.
    wa_bapi_partner-partn_numb = '0000666666'.
    wa_bapi_partner-itm_number = '000000'.
    append wa_bapi_partner to it_bapi_partner.
    clear wa_bapi_partner.
ENDIF.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
    exporting
      input = wa_header-partner_2
    importing
      output = wa_header-partner_2.
IF wa_header-partner_2 IS NOT INITIAL.
    wa_bapi_partner-partn_role = 'WE'.
    wa_bapi_partner-partn_numb = '0000666666'.
    wa_bapi_partner-itm_number = '000000'.
    append wa_bapi_partner to it_bapi_partner.
    clear wa_bapi_partner.
ENDIF.
perform f_item.
data : order_items_inx type table of bapisditmx with header line.
order_items_inx-material          = 'X'. "
order_items_inx-target_qty        = 'X'. "
order_items_inx-comp_quant        = 'X'. "
order_items_inx-trgqty_den        = 'X'.
order_items_inx-rnddlv_qty        = 'X'.
order_items_inx-updateflag = 'I'.
order_items_inx-target_qu = 'X'.
order_items_inx-plant             = 'X'. "
append order_items_inx.
call function 'BAPI_SALESORDER_CREATEFROMDAT2'
    exporting
      salesdocumentin = 'MX11111152'
order_header_in      = wa_bapi_header
         order_header_inx     = wa_bapi_headerx
importing
salesdocument        = sales_order_no
tables
return               = it_bapireturn
order_items_in       = it_bapi_item
order_items_inx      = order_items_inx
order_partners       = it_bapi_partner
   order_conditions_in = it_bapi_cond.
if sy-subrc is initial.
commit work.
endif.
*&      Form f_item
      text
form f_item .
call function 'CONVERSION_EXIT_ALPHA_INPUT'
    exporting
      input = wa_item-posnr
    importing
      output = wa_item-posnr.
wa_item-posnr = '000010'.
IF sy-subrc EQ 0. "IS INITIAL.
move wa_item-posnr to g_str_count."commented out by shakti
ENDIF.
wa_bapi_item-itm_number        = wa_item-posnr. " Line item
WA_BAPI_ITEM-PO_ITM_NO         = WA_ITEM-EBELP.
wa_bapi_item-division          = wa_item-spart.
wa_bapi_item-purch_no_c        = 'ddr1234'.   " po number
wa_bapi_item-purch_date        = sy-datum.   " po date
wa_bapi_item-purch_no_s        = 'MX11111112'. " Ship-to-party po number
wa_item-matnr = 'MAXIMO_SERVICE'.
call function 'CONVERSION_EXIT_MATN1_INPUT'
    exporting
      input        = wa_item-matnr
    importing
      output       = wa_item-matnr
    exceptions
      length_error = 1
      others       = 2.
if sy-subrc is initial.
    wa_bapi_item-material        = wa_item-matnr. "material
endif.
wa_bapi_item-target_qty        = '1'. " Order qty
wa_bapi_item-comp_quant = '1'.
wa_bapi_item-target_qu = 'EA'.
    wa_bapi_item-fixed_quan = '1'.
wa_bapi_item-comp_quant        = wa_item-kwmeng.
wa_bapi_item-trgqty_den        = '1'.
wa_bapi_item-rnddlv_qty        = wa_item-kwmeng.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
   EXPORTING
     input = wa_item-ps_psp_pnr
   IMPORTING
     output = wa_item-ps_psp_pnr.
IF sy-subrc = 0.
   wa_bapi_item-wbs_elem          = wa_item-ps_psp_pnr.
ENDIF.
wa_bapi_item-item_categ        = 'ZMAX'.
wa_bapi_item-ex_rate_fi        = wa_item-kurrf.
wa_bapi_item-dli_profil        = wa_item-ffprf.   " Dynamic item processor profile
wa_bapi_item-route             = wa_item-route.   " route
wa_bapi_item-exchg_rate        = wa_item-kursk.
wa_bapi_item-plant             = '2090'.   " Plant
wa_bapi_item-ship_point        = 'FN11'.   " Shipping point
wa_bapi_item-store_loc         = wa_item-lgort.   " stg loc
REPLACE ALL OCCURRENCES OF ',' IN wa_item-ntgew WITH '.'.
REPLACE ALL OCCURRENCES OF ',' IN wa_item-brgew WITH '.'.
wa_bapi_item-net_weight        = wa_item-ntgew. "
wa_bapi_item-gross_wght        = wa_item-brgew. "
call function 'CONVERSION_EXIT_CUNIT_INPUT'
    exporting
      input    = wa_item-gewei
      language = sy-langu
    importing
      output   = wa_item-gewei.
   EXCEPTIONS
     unit_not_found = 1
     OTHERS         = 2.
IF sy-subrc <> 0.
ENDIF.
wa_bapi_item-untof_wght        = 'KG'. " weight unit
replace all occurrences of ',' in wa_item-kursk with '.'.
replace all occurrences of ',' in wa_item-kurrf with '.'.
wa_bapi_item-profit_ctr        = wa_item-prctr.   " Profit center
wa_bapi_item-resanalkey        = wa_item-abgrs.   " RESULT ANALYSIS KEY
wa_bapi_item-cstg_sheet        = wa_item-kalsm_k. " COSTING SHEET
append wa_bapi_item to it_bapi_item.
endform.                    " f_item
Thanks & regards,
Chetan

see the following to create sales order:-
*& Report ZSALESORDER
*&DEVELOPED BY JANI KRUPA 4.10.2008
REPORT ZSALESORDER.
Parameters
Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
    header-COMPL_DLV = p_autlf.
    header-COMPL_DLV = 'X'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Fill schedule lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.

Create Support Message via BAPI with additional partners

Hi all,
i need to create a support message (slfn) via bapi / function module. The basic creation is no problem with BAPI_NOTIFICATION_CREATE.
But i need to set additional partner(functions) like "approved by" in the support message. With this bapi i can only set the processor and creator of the message.
How can i add additional partners via BAPI call?
Any help would be much appreciated.
Daniel

Hi Daniel,
i do not think there is a standard functionality for this.
you can use function module CRM_DNO_UPDATE_PARTNER to set partner functions to a message. You will have to build your own RFC enabled function module around this, though.
Then you can use it to add your partners after the message was created.
Regards,
Christoph

Problem in sales order change via BAPI

We are in AFS system and we try to reduce a quantity in sales order via BAPI.
We recive back an error 8w 280. We are not able to find wich is and where is a problem.
Does anyone have experince on that problem/error message
Thanks in advance
Andrea

Hi Andrea,
Since BAPI invloves more programming stuff, I adivce you to post this thread in the ABAP forums also.
Regards,
Senthilkumar SD

Reg BAPI BAPI_SALESORDER_CREATEFROMDAT2

Hi All,
We are creating the sales order using the BAPI BAPI_SALESORDER_CREATEFROMDAT2 the BAPI is successfully creating Sales order successfully with out any issues,but the problem is the sales order line item which has been created through BAPI is being greyed out it is not allowing changes changes to be done for the line item.
The same we checked manually executing the BAPI from Se37 it is creating sales order and also it is allowing to change the line item details manually(by going through VA02).We cross checked the parameters that we are passing through SE37 and through program both are same but I am not getting what is cause for the error.Please suggest some body some resolution for this.
Regards
Mahesh

Hi All,
We are creating the sales order using the BAPI BAPI_SALESORDER_CREATEFROMDAT2 the BAPI is successfully creating Sales order successfully with out any issues,but the problem is the sales order line item which has been created through BAPI is being greyed out it is not allowing changes changes to be done for the line item.
The same we checked manually executing the BAPI from Se37 it is creating sales order and also it is allowing to change the line item details manually(by going through VA02).We cross checked the parameters that we are passing through SE37 and through program both are same but I am not getting what is cause for the error.Please suggest some body some resolution for this.
Regards
Mahesh

Problem in lock Sales order create with BAPI BAPI_SALESORDER_CREATEFROMDAT2

Hi All,
i have the z program to create the sales order with reff quotation in SD With BAPI BAPI_SALESORDER_CREATEFROMDAT2.
this program will excute every 30 mins .
Problem: Some times if i excute the program in background it is taking morethan 30mins so second batch excution also gets starting to create the sales order for same quotation then it is creating 2 sales orders at atime with 1 quotation.
here i am getting duplicate sales orders so i want to lock the creation of duplicate sales order.

Some solutions
- Just lock (ENQUEUE) any object at the start of the job(*), if not locked, you can exit or wait in a loop, will be released at end of job (use a _SCOPE '3' so commit work wont release the lock)
-> This will insure the job runs only once at a time
- Lock the quotation before calling the BAPI, will be released by the COMMIT_WORK (from where do you fetch the quotation, if it is a customer Z_table, you can use the lock object that you have surely created ?) (use a _scope '2')
-> This will insure that at most one job will convert a quotation (i suppose you set a "done" flag or status in the quotation record)
Read [SAP Locks |http://help.sap.com/abapdocu_70/en/ABENSAP_LOCK.htm] if you are not familiar with the concept of lock in SAP.
Regards,
Raymond
(*) E_TABLEE for table, E_TRDIR for program, anything not required by another process

Program for Sales Order cretaion using BAPI BAPI_SALESORDER_CREATEFROMDAT2

Hi All,
Can any one please give me one modal program which uses the BAPI 'BAPI_SALESORDER_CREATEFROMDAT2' to create Sales Orders...
Thank You very much in advance.....................

Hi Krishna ,
Please check the below links .
[http://www.sap-basis-abap.com/abap/bapi-sample-to-upload-data-from-flat-file-to-va01.htm]
[http://abapreports.blogspot.com/2008/06/bapi-sample-code-for.html] -- > Select and Copy from this one.

Rg: Open Sales Order Uplaod Using BAPI (BAPI_SALESORDER_CREATEFROMDAT2)

Hi Frinds..
I am Creating Program Sales Order Uplaod Progrm using BAPI BAPI_SALESORDER_CREATEFROMDAT2.
All header and Po data uploaded Properly . But Item Leal data not updated.. Please let me know any Conditions need to pass to update item data.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
        EXPORTING
          salesdocumentin      = v_extr
          order_header_in      = l_vbak
          order_header_inx     = l_vbakx
          behave_when_error    = 'P'
        IMPORTING
          salesdocument        = v_vbeln
        TABLES
          return               = return
          order_items_in       = l_vbap
          order_items_inx      = l_vbapx
          order_partners       = l_vbpa
          order_schedules_in   = l_shline
          order_schedules_inx = l_shlinex .
I can pass like that.

hi Prabu,
It is not uploading for company code 1100 ..

How to give all input parameter in creation of po via bapi

sir plez tell clear process of create po via bapi, i have done upto "BAPI_PO_CREATIVE1, then what to do, plez stepwise explain
thank Q

Dear Baskhar,
After BAPI_PO_CREATE1, you have to run BAPI_TRANSACTION_COMMIT to post
the data.
For example, from SE37:
You can goto menubar: Function Module
Test-> Test sequence,
Fill in BAPI_PO_CREATE1 then follow by BAPI_TRANSACTION_COMMIT .
Best Regards,
Ian Wong

Wrong CFOP determination via BAPI BAPI_SALESORDER_CREATEFROMDAT2

Similar Messages

Maybe you are looking for