Vendor creation using fm 'Vendor_insert'

Hi experts,
I want to create vendor using the FM 'VENDOR_INSERT'. But the problem is I am unable to know what are the required fields to be given in the import structures (ie LFA1,LFB1,LFM1) .
Could you please suggest the way to run this FM with minimum data?
Thanks and regards,
Ramkishore

hI,
Why don't you use the Function module BAPI_VENDOR_CREATE to create a Vendor
Regards
Sudheer

Similar Messages

Need Sample Code for Vendor creation using JAVA API

Hi,
I have a scenario like Vendor creation using Java API.
1.I have Vendors (Main) Table.
2.I have look up tables like Account Group.
3.Also Qualifier table(Phone numbers) too.
Could you please give me the sample code which helps me to create Vendor records using Java API?
I need Code samples which should cover all of the above scenario.
Marks will be given for the relevent answers.
Best Regards
PK Devaraj

Hi Devraj,
I hope the below code might solve all your problem:-
//Adding Qualified field
//Creating empty record in Qualifed table
//Adding No Qualifiers
Record qualified_record = RecordFactory.createEmptyRecord(new TableId(<TableId>));
try {
qualified_record.setFieldValue(new FieldId(<fieldId of NoQualifier), new StringValue(<StringValue>));//Adding No Qualifier
catch (IllegalArgumentException e2) {
// TODO Auto-generated catch block
e2.printStackTrace();
catch (MdmValueTypeException e2) {
// TODO Auto-generated catch block
e2.printStackTrace();
//Creating Record in Qualified table
CreateRecordCommand create_command = new CreateRecordCommand(connections);
create_command.setSession(sessionId);
create_command.setRecord(qualified_record);
try
create_command.execute();
catch(Exception e)
System.out.println(e.toString());
RecordId record_id = create_command.getRecord().getId();
//Adding the new record to Qualifed Lookup value and setting the Yes Qualifiers
QualifiedLookupValue lookup_value = new QualifiedLookupValue();
int link = lookup_value.createQualifiedLink(new QualifiedLinkValue(record_id));
//Adding Yes Qualifiers
lookup_value.setQualifierFieldValue(0 , new FieldId(<FieldID of Yes Qualifier>) , new StringValue(<StringValue>));
//Now adding LookUP values
//Fetch the RecordID of the value selected by user using the following function
public RecordId getRecordID(ConnectionPool connections , String sessionID , String value , String Fieldid , String tableid)
ResultDefinition rsd = new ResultDefinition(new TableId(tableid));
rsd.addSelectField(new FieldId(Fieldid));
StringValue [] val = new StringValue[1];
val[0] = new StringValue(value);
RetrieveRecordsByValueCommand val_command = new RetrieveRecordsByValueCommand(connections);
val_command.setSession(sessionID);
val_command.setResultDefinition(rsd);
val_command.setFieldId(new FieldId(Fieldid));
val_command.setFieldValues(val);
try
 val_command.execute();
catch(Exception e)
RecordResultSet result_set = val_command.getRecords();
RecordId id = null;
if(result_set.getCount()>0)
 for(int i = 0 ; i < result_set.getCount() ; i++)
 id = result_set.getRecord(i).getId();
return id;
//Finally creating the record in Main table
com.sap.mdm.data.Record empty_record = RecordFactory.createEmptyRecord(new TableId("T1"));
try {
 empty_record.setFieldValue(new FieldId(<FieldId of text field in Main table>),new StringValue(<StringValue>));
 empty_record.setFieldValue(new FieldId(<FieldId of lookup field in Main table>), new LookupValue(<RecordID of the value retrieved using the above getRecordID function>));
empty_record.setFieldValue(new FieldId(<FieldId of Qualified field in Main table>), new QualifiedLookupValue(<lookup_value>));//QualifiedLookUp value Retrieved above
} catch (IllegalArgumentException e1) {
// TODO Auto-generated catch block
 e1.printStackTrace();
} catch (MdmValueTypeException e1) {
 // TODO Auto-generated catch block
 e1.printStackTrace();
//Actually creating the record in Main table
CreateRecordCommand create_main_command = new CreateRecordCommand(connections);
create_main_command.setSession(sessionId);
create_main_command.setRecord(empty_record);
try
 create_main_command.execute();
catch(Exception e)
 System.out.println(e.toString());
Thanks
Namrata

Vendor creation using bapi

Hi experts,
I am new to bapi concept I done vendor creation by using bdc and lsmw and now I want to create by using bapi can anyone send program code for creating so that I can go through it.
thanks in advance,
points will be rewarded,
Srinivas.D

hi
I gone to the bapi function module for bapi_vendor_create etc but the problem their is no input parameters or tables so I am little bit of confused if any body has the code plz send me.
Regards,
SrinivasD

Vendor creation using LSMW

Hi All,
I m trying to do vendor creation in LSMW method using RFBIKR00 program,please any one guide me I strucked in 2 Maintain Source Structures after this cursor not moving to next radio button even though I done for next steps final it is not reading the data,pls help me out..
Thanks n regds,
sree.

Hi
Check these links..might prove useful
[http://www.sapdb.info/wp-content/uploads/2008/08/lsmw.pdf|http://www.sapdb.info/wp-content/uploads/2008/08/lsmw.pdf]
Regards
Raj

Vendor creation using RFC

hi,
I want to use RFC FM for creating the vendor. So far i have used VENDOR_INSERT, but it doesnt updates ADRC table(I think so) so is there any alternate FM apart from BAPI_VENDOR_CREATE(coz it need data to be filled online).
Please suggest any FM which satisfies the above need.
Regards,

Hi,
Not sure about a RFC other than BAPI_VENDOR_CREATE..
can you use batch input program RFBIKR00
Thanks
Naren

Error creating vendor w/ JCo FM VENDOR_INSERT- Missing parameter w/ PERFORM

Dear all,
I have followed the following thread and found it very useful as we need to create vendors from an external system in R/3 using the JCo as well. We are doing all the steps specified in previous posts and calling FM VENDOR_INSERT but when I execute the function it returns an exception:
JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: Missing parameter with PERFORM.
We have checked and all the needed BAPIs are enabled but we are stuck at this first step. I have tried a variety of things but nothing seems to work. Not sure how I can specify the PERFORM parameter using JCo. Did anyone else fase this issue?
Here is what some of the relevant Java code looks like:
        JCoFunctionTemplate tmplt1 = repository.getFunctionTemplate("VENDOR_INSERT");
        JCoFunction vfunc = tmplt1.getFunction();
        JCoParameterList vparams = vfunc.getImportParameterList();
        JCoStructure jcs= vparams.getStructure("I_LFA1");
        try
             LocalSupplier s = getSupplier1();
             jcs.setValue("MANDT", "010");
             jcs.setValue("NAME1", s.getSupName());
             jcs.setValue("NAME2", s.getSupName2());
             jcs.setValue("PSTLZ", s.getSupPostalCode());
             jcs.setValue("ORT01", s.getSupCity());
             jcs.setValue("LAND1", s.getIdCountry().getIsocode());
             jcs.setValue("STRAS", s.getAddress1() +", " + s.getAddress2());
             jcs.setValue("MCOD1", "test");
             jcs.setValue("KTOKK", "ZKRE");
             jcs.setValue("SPRAS", s.getIdmasterSupplier().getIdlanguage().getLocale());
             jcs.setValue("STCD1", s.getIdmasterSupplier().getTaxId());
             jcs.setValue("TELF1", s.getTelephone());
             jcs.setValue("TELFX", s.getFax());
             execute(vfunc, destination);
        catch(Exception e)
            System.out.println(e.toString());
            e.printStackTrace();
            return;
      * Method execute will call a function. The Caller of this function has
      * already set all required parameters of the function
     public static void execute(JCoFunction function, JCoDestination dest) {
          try {
               JCoContext.begin(dest);
               function.execute(dest);
               JCoContext.end(dest);
          } catch (JCoException e) {
               e.printStackTrace();
Any help from some of view that have succesfully implemented vendor creation using the JCo would be highly appreciated.

Hi,
as I just wrote in the previous thread,
don't use function module VENDOR_INSERT.
As written before it is an update task FM. And also it do not check any field validity.
This is the best way to face inconsistencies in the future.
As you have also noticed, troubles and difficulties will come very soon related to the address management.
In standard there is NO FM or BAPI to do so.
The only supported option is via batch-input or idocs. Eventually, LSMW could help
See [note 384462|https://service.sap.com/sap/support/notes/384462]
With ECC 2005, a synchronisation class can help a lot. See class VMD_EI_API.
With ECC 2005 ehp3, you have an eSOA service to create vendor asynchronously. Not all fields are supported.
In other words, just create a BAPI to transfert your own parameters then either make a batchinput which will call XK01/XK02 in batch, either trigger class VMD_EI_API
BR
Alain

Validation of (Type of business & Industry) - vendor creation - FK01

Hi All,
        While creating vendor creation using transaction 'FK01' I get a screen namely 'control screen' where there are couple of fields called 'Type of business' and 'Type of Insustry'. These two fields have F4 help available. The issue is that the system is allowing to feed in any kind of data into these two fields. The requirement is that it should allow only those values that are available in F4 help.
      But right now system allows what ever junk values that we enter ( Not by selecting F4 ) through key board.
      Is there any validation in config to restrict the system to accept only those from F4 help ?
      The standard program 'SAPMF02K' is also calling a user exit but it is not taking any parameters like these two values. The names of these fields are
   Type of business : J-1KFTBUS
   Type of industry : J-1KFTIND
Thanks for help.
Vinod

Hello,
Looking at the name of the fields (starting with J-) it looks like you have some special development in your system?
On the control screen in our system there is only a field Industry (LFA1-BRSCH).
Regards,
John.

Vendor master record creation using interactive form

hi all,
i have a requirement to create a vendor once the user enters the data related to vendor similar to xk01 data on an interactive form and submits it .it goes thru a series of approvals and then at the final approval if the form is approved and say submit it has to create a vendor in the sap system i have searched for good bapis for vendor creation but found nothing . also searched the forums but I didnt get any idea or solution. i thought that i can use the bapi in the service call i use in webdynpro component and create a context for the form similar to the structure in bapi.
could you please help me out on how this can be done . i just need to post all the vendor data into sap and get a new vendor created automatically in background and get the vendor number again back to form to notity the person that it has been created.
appreciate if you could reply me asap.
thanks.
regards
sp
Edited by: SOHA PATHAN on Jun 6, 2011 12:40 PM

Hi Ashwani,
thank you for replying . my question was how to post the vendor data entered on the form into sap i.e using xk01 as u have done in your project. i have created a structure with all the fields required by user and required for a vendor creation in xk01 to create a vendor . this structure iam using in my form context. now iam not sure about how to post the data, can you please give me an idea of what code the FM's shoild have and also please tell me how to initiate workflow with the submit button and i want to send the URL of the form and not as PDF attachment , the approving person will click the URL and modify the interactive form and then clicks approved button in the same form.
I hope you got my questions.
Thanks,
Soha.

Regarding vendor master creation using xk01,fk01,mk01.

hi
i have created vendor master using xk01.what is the diffeerence between creation of vendor master using xk01 and FK01,MK01.

Hi
You can split vendor master data into two parts - purchasing (MK01) and accounting (FK01).
Purchasing veiw (MK01) is important if you want to create purchase documents like PO on vendor. This veiw is created for purchase organization with bank details and partner functions.
Accounting view (FK01) is important for finance people to post invoice and pay to vendor. This view is created for company code. The terms of payment which purchase dept specifies will be entered in accounting view again and bank details entered by purchasing people will be confirmed by accounting team.
You can create collectively these two views in XK01.
Thanks

Vendor Creation Via OAWD using workflow

Hi,
We are currently using SAP Archvelink for attaching vendor invoices to FI docuemnt via FB60 and MIRO using a basic workflow function
We want to be able to use the same process ie OAWD to be able to initiate the process of creating a vendor via XK01. The user woudl receive an authorised vendor creation PDF form that they woudl then attach to the vendor when cretaing
I have tried to configure a new document type and have assigned to object type LFA1 in transaction SOA0. However, when I try to maintain the workflow parameters to link to transaction code XK01 in transaction OACA I get the following message
Parameter TRANSACTIONCODE does not exist for method CREATE of object type LFA1
I dont know what to do (or if it is possible) to enable the "CREATE" method for object type LFA1
Thanks in advance

I solved my own problem.
I had to configure OAWS first then it allowed me to add create in SOA0
Edited by: Tracee on Sep 14, 2010 7:43 AM

Error in : Purchase order Creation using BAPI_PO_CREATE1

Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
 i_create_order,
 i_cycle TYPE cycle,
 i_qty_acpt TYPE dzmeng,
 i_dly_date TYPE vbak-vdatu,
 i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
 i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
 i_vbap TYPE vbap,
 i_ekko TYPE ekko,
 i_ekpo TYPE ekpo,
 i_bsoh TYPE bapisdhd1,
 i_bsohx TYPE bapisdhd1x,
 i_bpoh TYPE bapimepoheader,
 i_bpohx TYPE bapimepoheaderx,
 i_vbeln TYPE vbeln_va,
 i_posnr TYPE posnr_va,
 i_contr TYPE vbeln_va,
 i_conit TYPE posnr_va,
 i_ebeln TYPE ebeln,
 i_ebelp TYPE ebelp,
 i_pargr TYPE pargr,
 i_thead TYPE thead,
 i_line TYPE tline,
 i_note TYPE txw_note,
 i_new_vbeln TYPE vbeln_va,
 i_new_ebeln TYPE ebeln,
 i_wa_bsoi TYPE bapisditm,
 i_wa_bsoix TYPE bapisditmx,
 i_wa_bsop TYPE bapiparnr,
 i_wa_bsos TYPE bapischdl,
 i_wa_bsosx TYPE bapischdlx,
 i_wa_vbpa TYPE vbpa,
 i_wa_vbkd TYPE vbkd,
 i_wa_bpoi TYPE bapimepoitem,
 i_wa_bpoix TYPE bapimepoitemx,
 i_wa_bpos TYPE bapimeposchedule,
 i_wa_bposx TYPE bapimeposchedulx,
 i_wa_bpop TYPE bapiekkop,
 i_wa_ekpa TYPE ekpa,
 i_message TYPE char72,
 i_bapiretn TYPE bapiret2,
 i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
 i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
 i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
 i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
 i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
 i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
 i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
 i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
 i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
 i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
 i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
 i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
 i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
 i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
 i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
 i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
 c_char_e VALUE 'E',
 c_char_p VALUE 'P',
 c_char_g VALUE 'G',
 c_char_i VALUE 'I',
 c_char_s VALUE 'S',
 c_char_x VALUE 'X',
 c_zsw(3) VALUE 'ZSW',
 c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
 IF NOT i_create_order IS INITIAL .
 CLEAR: i_create_order .
 MOVE: wa_order_split_create-docnr TO i_ebeln,
 wa_order_split_create-docitm TO i_ebelp .
 CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 IMPORTING
 po_ekko = i_ekko
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
 ENDIF .
* Fill PO Header
 i_bpoh-comp_code = i_ekko-bukrs .
 i_bpoh-doc_type = i_ekko-bsart .
 i_bpoh-vendor = i_ekko-lifnr .
 i_bpoh-langu = i_ekko-spras .
 i_bpoh-pmnttrms = i_ekko-zterm .
 i_bpoh-purch_org = i_ekko-ekorg .
 i_bpoh-pur_group = i_ekko-ekgrp .
 i_bpoh-currency = i_ekko-waers .
 i_bpoh-agreement = i_ekko-konnr .
 i_bpoh-incoterms1 = i_ekko-inco1 .
 i_bpoh-incoterms2 = i_ekko-inco2 .
* Fill PO update indicator 'X'
 i_bpohx-comp_code = c_char_x .
 i_bpohx-doc_type = c_char_x .
 i_bpohx-vendor = c_char_x .
 i_bpohx-langu = c_char_x .
 i_bpohx-pmnttrms = c_char_x .
 i_bpohx-purch_org = c_char_x .
 i_bpohx-pur_group = c_char_x .
 i_bpohx-currency = c_char_x .
 i_bpohx-agreement = c_char_x .
 i_bpohx-incoterms1 = c_char_x .
 i_bpohx-incoterms2 = c_char_x .
 CALL FUNCTION 'ME_EKPO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 pi_ebelp = i_ebelp
 IMPORTING
 po_ekpo = i_ekpo
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF .
* Fill PO Item
 i_wa_bpoi-po_item = i_ekpo-ebelp .
 i_wa_bpoi-material = i_ekpo-matnr .
 i_wa_bpoi-plant = i_ekpo-werks .
 i_wa_bpoi-stge_loc = i_ekpo-lgort .
 i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
 i_wa_bpoi-po_unit = i_ekpo-meins .
 i_wa_bpoi-tax_code = i_ekpo-mwskz .
 i_wa_bpoi-val_type = i_ekpo-bwtar .
 i_wa_bpoi-item_cat = i_ekpo-pstyp .
 i_wa_bpoi-acctasscat = i_ekpo-knttp .
 i_wa_bpoi-agreement = i_ekpo-konnr .
 i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
 APPEND i_wa_bpoi TO i_bpoi .
* Fill PO Item update indicator 'X'
 i_wa_bpoix-po_item = i_ekpo-ebelp .
 i_wa_bpoix-po_itemx = c_char_x .
 i_wa_bpoix-material = c_char_x .
 i_wa_bpoix-plant = c_char_x .
 i_wa_bpoix-stge_loc = c_char_x .
 i_wa_bpoix-quantity = c_char_x .
 i_wa_bpoix-po_unit = c_char_x .
 i_wa_bpoix-tax_code = c_char_x .
 i_wa_bpoix-val_type = c_char_x .
 i_wa_bpoix-item_cat = c_char_x .
 i_wa_bpoix-acctasscat = c_char_x .
 i_wa_bpoix-agreement = c_char_x .
 i_wa_bpoix-agmt_item = c_char_x .
 APPEND i_wa_bpoix TO i_bpoix .
* Fill PO Item Schedule
 i_wa_bpos-po_item = i_ekpo-ebelp .
 i_wa_bpos-sched_line = '0001' .
 i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
 i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
 APPEND i_wa_bpos TO i_bpos .
* Fill PO Item schedule update indicator 'X'
 i_wa_bposx-po_item = i_ekpo-ebelp .
 i_wa_bposx-sched_line = '0001' .
 i_wa_bposx-delivery_date = c_char_x .
 i_wa_bposx-quantity = c_char_x .
 APPEND i_wa_bposx TO i_bposx .
 CLEAR: i_pargr .
 SELECT SINGLE pargr
 INTO i_pargr
 FROM t161
 WHERE bstyp = i_ekko-bstyp
 AND bsart = i_ekko-bsart .
 CLEAR i_ekpa[].
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa[].
 LOOP AT i_ekpa INTO i_wa_ekpa .
 i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
 i_wa_bpop-langu = sy-langu .
 IF NOT i_wa_ekpa-lifn2 IS INITIAL .
 i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
 ELSE .
 i_wa_bpop-buspartno = i_wa_ekpa-parnr .
 ENDIF .
 APPEND i_wa_bpop TO i_bpop .
 CLEAR: i_wa_ekpa, i_wa_bpop .
 ENDLOOP .
 CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
 CALL FUNCTION 'BAPI_PO_CREATE1'
 EXPORTING
 poheader = i_bpoh
 poheaderx = i_bpohx
 IMPORTING
 exppurchaseorder = i_new_ebeln
 TABLES
 return = i_bapiret2
 poitem = i_bpoi[]
 poitemx = i_bpoix[]
 poschedule = i_bpos[]
 poschedulex = i_bposx[].
 i_order = i_new_ebeln .
 SHIFT i_order LEFT DELETING LEADING '0' .
 i_return-errortype = c_char_i .
 i_return-workarea = c_zsw .
 i_return-message = '064' .
 i_return-variable1 = i_order .
 loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
 append i_bapiretn to t_bapi_return .
 endloop .
 if t_bapi_return[] is initial .
 i_create_order = c_char_x .
 CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
 EXPORTING
 act_return = i_return. "Popup with new PO no.
 ENDCASE . " Docind
 ENDIF .
ENDLOOP.

Hi Shareen,
I think in the following parts of the code,
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa[].
Error in : Purchase order Creation using BAPI_PO_CREATE1
Posted: Mar 20, 2006 7:39 PM Reply E-mail this post
Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
 i_create_order,
 i_cycle TYPE cycle,
 i_qty_acpt TYPE dzmeng,
 i_dly_date TYPE vbak-vdatu,
 i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
 i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
 i_vbap TYPE vbap,
 i_ekko TYPE ekko,
 i_ekpo TYPE ekpo,
 i_bsoh TYPE bapisdhd1,
 i_bsohx TYPE bapisdhd1x,
 i_bpoh TYPE bapimepoheader,
 i_bpohx TYPE bapimepoheaderx,
 i_vbeln TYPE vbeln_va,
 i_posnr TYPE posnr_va,
 i_contr TYPE vbeln_va,
 i_conit TYPE posnr_va,
 i_ebeln TYPE ebeln,
 i_ebelp TYPE ebelp,
 i_pargr TYPE pargr,
 i_thead TYPE thead,
 i_line TYPE tline,
 i_note TYPE txw_note,
 i_new_vbeln TYPE vbeln_va,
 i_new_ebeln TYPE ebeln,
 i_wa_bsoi TYPE bapisditm,
 i_wa_bsoix TYPE bapisditmx,
 i_wa_bsop TYPE bapiparnr,
 i_wa_bsos TYPE bapischdl,
 i_wa_bsosx TYPE bapischdlx,
 i_wa_vbpa TYPE vbpa,
 i_wa_vbkd TYPE vbkd,
 i_wa_bpoi TYPE bapimepoitem,
 i_wa_bpoix TYPE bapimepoitemx,
 i_wa_bpos TYPE bapimeposchedule,
 i_wa_bposx TYPE bapimeposchedulx,
 i_wa_bpop TYPE bapiekkop,
 i_wa_ekpa TYPE ekpa,
 i_message TYPE char72,
 i_bapiretn TYPE bapiret2,
 i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
 i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
 i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
 i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
 i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
 i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
 i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
 i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
 i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
 i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
 i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
 i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
 i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
 i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
 i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
 i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
 c_char_e VALUE 'E',
 c_char_p VALUE 'P',
 c_char_g VALUE 'G',
 c_char_i VALUE 'I',
 c_char_s VALUE 'S',
 c_char_x VALUE 'X',
 c_zsw(3) VALUE 'ZSW',
 c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
 IF NOT i_create_order IS INITIAL .
 CLEAR: i_create_order .
 MOVE: wa_order_split_create-docnr TO i_ebeln,
 wa_order_split_create-docitm TO i_ebelp .
 CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 IMPORTING
 po_ekko = i_ekko
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
 ENDIF .
Fill PO Header
 i_bpoh-comp_code = i_ekko-bukrs .
 i_bpoh-doc_type = i_ekko-bsart .
 i_bpoh-vendor = i_ekko-lifnr .
 i_bpoh-langu = i_ekko-spras .
 i_bpoh-pmnttrms = i_ekko-zterm .
 i_bpoh-purch_org = i_ekko-ekorg .
 i_bpoh-pur_group = i_ekko-ekgrp .
 i_bpoh-currency = i_ekko-waers .
 i_bpoh-agreement = i_ekko-konnr .
 i_bpoh-incoterms1 = i_ekko-inco1 .
 i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
 i_bpohx-comp_code = c_char_x .
 i_bpohx-doc_type = c_char_x .
 i_bpohx-vendor = c_char_x .
 i_bpohx-langu = c_char_x .
 i_bpohx-pmnttrms = c_char_x .
 i_bpohx-purch_org = c_char_x .
 i_bpohx-pur_group = c_char_x .
 i_bpohx-currency = c_char_x .
 i_bpohx-agreement = c_char_x .
 i_bpohx-incoterms1 = c_char_x .
 i_bpohx-incoterms2 = c_char_x .
 CALL FUNCTION 'ME_EKPO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 pi_ebelp = i_ebelp
 IMPORTING
 po_ekpo = i_ekpo
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF .
Fill PO Item
 i_wa_bpoi-po_item = i_ekpo-ebelp .
 i_wa_bpoi-material = i_ekpo-matnr .
 i_wa_bpoi-plant = i_ekpo-werks .
 i_wa_bpoi-stge_loc = i_ekpo-lgort .
 i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
 i_wa_bpoi-po_unit = i_ekpo-meins .
 i_wa_bpoi-tax_code = i_ekpo-mwskz .
 i_wa_bpoi-val_type = i_ekpo-bwtar .
 i_wa_bpoi-item_cat = i_ekpo-pstyp .
 i_wa_bpoi-acctasscat = i_ekpo-knttp .
 i_wa_bpoi-agreement = i_ekpo-konnr .
 i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
 APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
 i_wa_bpoix-po_item = i_ekpo-ebelp .
 i_wa_bpoix-po_itemx = c_char_x .
 i_wa_bpoix-material = c_char_x .
 i_wa_bpoix-plant = c_char_x .
 i_wa_bpoix-stge_loc = c_char_x .
 i_wa_bpoix-quantity = c_char_x .
 i_wa_bpoix-po_unit = c_char_x .
 i_wa_bpoix-tax_code = c_char_x .
 i_wa_bpoix-val_type = c_char_x .
 i_wa_bpoix-item_cat = c_char_x .
 i_wa_bpoix-acctasscat = c_char_x .
 i_wa_bpoix-agreement = c_char_x .
 i_wa_bpoix-agmt_item = c_char_x .
 APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
 i_wa_bpos-po_item = i_ekpo-ebelp .
 i_wa_bpos-sched_line = '0001' .
 i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
 i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
 APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
 i_wa_bposx-po_item = i_ekpo-ebelp .
 i_wa_bposx-sched_line = '0001' .
 i_wa_bposx-delivery_date = c_char_x .
 i_wa_bposx-quantity = c_char_x .
 APPEND i_wa_bposx TO i_bposx .
 CLEAR: i_pargr .
 SELECT SINGLE pargr
 INTO i_pargr
 FROM t161
 WHERE bstyp = i_ekko-bstyp
 AND bsart = i_ekko-bsart .
 CLEAR i_ekpa[].
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa[].
 LOOP AT i_ekpa INTO i_wa_ekpa .
 i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
 i_wa_bpop-langu = sy-langu .
 IF NOT i_wa_ekpa-lifn2 IS INITIAL .
 i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
 ELSE .
 i_wa_bpop-buspartno = i_wa_ekpa-parnr .
 ENDIF .
 APPEND i_wa_bpop TO i_bpop .
 CLEAR: i_wa_ekpa, i_wa_bpop .
 ENDLOOP .
 CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
 CALL FUNCTION 'BAPI_PO_CREATE1'
 EXPORTING
 poheader = i_bpoh
 poheaderx = i_bpohx
 IMPORTING
 exppurchaseorder = i_new_ebeln
 TABLES
 return = i_bapiret2
 poitem = i_bpoi[]
 poitemx = i_bpoix[]
 poschedule = i_bpos[]
 poschedulex = i_bposx[].
it should be only i_bpoi, i_bpoix, i_bpos, i_bposx but not i_bpoi[], i_bpoix[], i_bpos[], i_bposx[].
CHange the code as follows:
DATA: i_insert,
 i_create_order,
 i_cycle TYPE cycle,
 i_qty_acpt TYPE dzmeng,
 i_dly_date TYPE vbak-vdatu,
 i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
 i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
 i_vbap TYPE vbap,
 i_ekko TYPE ekko,
 i_ekpo TYPE ekpo,
 i_bsoh TYPE bapisdhd1,
 i_bsohx TYPE bapisdhd1x,
 i_bpoh TYPE bapimepoheader,
 i_bpohx TYPE bapimepoheaderx,
 i_vbeln TYPE vbeln_va,
 i_posnr TYPE posnr_va,
 i_contr TYPE vbeln_va,
 i_conit TYPE posnr_va,
 i_ebeln TYPE ebeln,
 i_ebelp TYPE ebelp,
 i_pargr TYPE pargr,
 i_thead TYPE thead,
 i_line TYPE tline,
 i_note TYPE txw_note,
 i_new_vbeln TYPE vbeln_va,
 i_new_ebeln TYPE ebeln,
 i_wa_bsoi TYPE bapisditm,
 i_wa_bsoix TYPE bapisditmx,
 i_wa_bsop TYPE bapiparnr,
 i_wa_bsos TYPE bapischdl,
 i_wa_bsosx TYPE bapischdlx,
 i_wa_vbpa TYPE vbpa,
 i_wa_vbkd TYPE vbkd,
 i_wa_bpoi TYPE bapimepoitem,
 i_wa_bpoix TYPE bapimepoitemx,
 i_wa_bpos TYPE bapimeposchedule,
 i_wa_bposx TYPE bapimeposchedulx,
 i_wa_bpop TYPE bapiekkop,
 i_wa_ekpa TYPE ekpa,
 i_message TYPE char72,
 i_bapiretn TYPE bapiret2,
 i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
 i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
 i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
 i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
 i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
 i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
 i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
 i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
 i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
 i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
 i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
 i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
 i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
 i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
 i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
 i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
 c_char_e VALUE 'E',
 c_char_p VALUE 'P',
 c_char_g VALUE 'G',
 c_char_i VALUE 'I',
 c_char_s VALUE 'S',
 c_char_x VALUE 'X',
 c_zsw(3) VALUE 'ZSW',
 c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
 IF NOT i_create_order IS INITIAL .
 CLEAR: i_create_order .
 MOVE: wa_order_split_create-docnr TO i_ebeln,
 wa_order_split_create-docitm TO i_ebelp .
 CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 IMPORTING
 po_ekko = i_ekko
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
 ENDIF .
Fill PO Header
 i_bpoh-comp_code = i_ekko-bukrs .
 i_bpoh-doc_type = i_ekko-bsart .
 i_bpoh-vendor = i_ekko-lifnr .
 i_bpoh-langu = i_ekko-spras .
 i_bpoh-pmnttrms = i_ekko-zterm .
 i_bpoh-purch_org = i_ekko-ekorg .
 i_bpoh-pur_group = i_ekko-ekgrp .
 i_bpoh-currency = i_ekko-waers .
 i_bpoh-agreement = i_ekko-konnr .
 i_bpoh-incoterms1 = i_ekko-inco1 .
 i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
 i_bpohx-comp_code = c_char_x .
 i_bpohx-doc_type = c_char_x .
 i_bpohx-vendor = c_char_x .
 i_bpohx-langu = c_char_x .
 i_bpohx-pmnttrms = c_char_x .
 i_bpohx-purch_org = c_char_x .
 i_bpohx-pur_group = c_char_x .
 i_bpohx-currency = c_char_x .
 i_bpohx-agreement = c_char_x .
 i_bpohx-incoterms1 = c_char_x .
 i_bpohx-incoterms2 = c_char_x .
 CALL FUNCTION 'ME_EKPO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 pi_ebelp = i_ebelp
 IMPORTING
 po_ekpo = i_ekpo
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF .
Fill PO Item
 i_wa_bpoi-po_item = i_ekpo-ebelp .
 i_wa_bpoi-material = i_ekpo-matnr .
 i_wa_bpoi-plant = i_ekpo-werks .
 i_wa_bpoi-stge_loc = i_ekpo-lgort .
 i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
 i_wa_bpoi-po_unit = i_ekpo-meins .
 i_wa_bpoi-tax_code = i_ekpo-mwskz .
 i_wa_bpoi-val_type = i_ekpo-bwtar .
 i_wa_bpoi-item_cat = i_ekpo-pstyp .
 i_wa_bpoi-acctasscat = i_ekpo-knttp .
 i_wa_bpoi-agreement = i_ekpo-konnr .
 i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
 APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
 i_wa_bpoix-po_item = i_ekpo-ebelp .
 i_wa_bpoix-po_itemx = c_char_x .
 i_wa_bpoix-material = c_char_x .
 i_wa_bpoix-plant = c_char_x .
 i_wa_bpoix-stge_loc = c_char_x .
 i_wa_bpoix-quantity = c_char_x .
 i_wa_bpoix-po_unit = c_char_x .
 i_wa_bpoix-tax_code = c_char_x .
 i_wa_bpoix-val_type = c_char_x .
 i_wa_bpoix-item_cat = c_char_x .
 i_wa_bpoix-acctasscat = c_char_x .
 i_wa_bpoix-agreement = c_char_x .
 i_wa_bpoix-agmt_item = c_char_x .
 APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
 i_wa_bpos-po_item = i_ekpo-ebelp .
 i_wa_bpos-sched_line = '0001' .
 i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
 i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
 APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
 i_wa_bposx-po_item = i_ekpo-ebelp .
 i_wa_bposx-sched_line = '0001' .
 i_wa_bposx-delivery_date = c_char_x .
 i_wa_bposx-quantity = c_char_x .
 APPEND i_wa_bposx TO i_bposx .
 CLEAR: i_pargr .
 SELECT SINGLE pargr
 INTO i_pargr
 FROM t161
 WHERE bstyp = i_ekko-bstyp
 AND bsart = i_ekko-bsart .
 CLEAR i_ekpa[].
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa.
 LOOP AT i_ekpa INTO i_wa_ekpa .
 i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
 i_wa_bpop-langu = sy-langu .
 IF NOT i_wa_ekpa-lifn2 IS INITIAL .
 i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
 ELSE .
 i_wa_bpop-buspartno = i_wa_ekpa-parnr .
 ENDIF .
 APPEND i_wa_bpop TO i_bpop .
 CLEAR: i_wa_ekpa, i_wa_bpop .
 ENDLOOP .
 CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
 CALL FUNCTION 'BAPI_PO_CREATE1'
 EXPORTING
 poheader = i_bpoh
 poheaderx = i_bpohx
 IMPORTING
 exppurchaseorder = i_new_ebeln
 TABLES
 return = i_bapiret2
 poitem = i_bpoi
 poitemx = i_bpoix
 poschedule = i_bpos
 poschedulex = i_bposx.
 i_order = i_new_ebeln .
 SHIFT i_order LEFT DELETING LEADING '0' .
 i_return-errortype = c_char_i .
 i_return-workarea = c_zsw .
 i_return-message = '064' .
 i_return-variable1 = i_order .
 loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
 append i_bapiretn to t_bapi_return .
 endloop .
 if t_bapi_return[] is initial .
 i_create_order = c_char_x .
 CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
 EXPORTING
 act_return = i_return. "Popup with new PO no.
 ENDCASE . " Docind
 ENDIF .
ENDLOOP.

Error in the LSMW for vendor master using standard batch/direct input

I am facing the problem in the LSMW for the Vendor master data. The vendor is initially created for the company code 350 by using LSMW. NOw when I try to uploasd the same vendor using the same LSMW for the company code 450 then I get the error in the Bach input creation as follows:
Batch Input Interface for Vendors
FB012                    Session 1 : Special character for 'empty field' is /
FB007                    Session 1 session name VNDR_CREATE_ was opened
FB104                    Trans. 2 XK01 : Acct already exists; general area not being processed
FB125                    ... Data in table BLFA1 cannot be processed
FB016                    ... Last header record ...
FB014                    ... BLF00-STYPE 1
FB014                    ... BLF00-TCODE XK01
FB014                    ... BLF00-LIFNR 300951
FB014                    ... BLF00-BUKRS 402
FB014                    ... BLF00-EKORG /
FB014                    ... BLF00-KTOKK VEND
FB017                    ... Last data record ...
FB014                    ... BLFA1-STYPE 2
FB014                    ... BLFA1-TBNAM BLFA1
FB014                    ... BLFA1-ANRED /
FB014                    ... BLFA1-NAME1 SAVOIE AUTOMATISME DEXIS
This is because when we use XK01 to create the vendor by using the

Please check this answered link:
Re: LSMW for Vendor Master
LSMW Upload vendor master data
Edited by: Afshad Irani on May 5, 2010 12:42 PM

Workflow for Vendor Creation through a portal.

Hi All Workflow Experts,
I have a scenario here.In my project vendor is created through a portal.On submit button from portal the workflow is to be triggered.I have to design the workflow process.So can you please guide me through what all should i consider while i design this workflow?
This is my first workflow assignment so if you explain in detail it will be a great help.
I will just pen down what all scenarios i can think of:
1.Start workflow after vendor creation or modification.
2.Check whether approver are maintained in Org structure through standard FMu2019s.
3.Check If approvers are maintained ?
4.If yes,approve or reject the vendor.
5.If no,get the agents from the custom table who can take an action on this.
This is what i can think of.
Please guide me.
Thanks in Advance,
Saket.

The corresponding BO related with the vendor creation or changing is LFA1 but this Business object doeanot have any events that are related to Create and Change , so try to create a ZLFA1 and add you own events or make use of delegation concept where you will create a delegation for LFA1.
For your first isssue
Start workflow after vendor creation or modification
EXIT_SAPMF02K_001 Vendors: User Exit for Checks prior to Saving is the user exit where in you can call the workflow when ever you change or create , because this user exit will trigger when ever you try to save the vendor. so i think you can make use of this user exit
For your second Issue
Check whether approver are maintained in Org structure through standard FMu2019s.
Make use of SWI_GET_USERS_OF_ORG_UNIT this fucntion mdoule to get the user of the ORG unit
or you can create a Rule(for determining the agents dynamically) to find the approvers.

Auto PO creation using purchase requisition

Hi,
I have tried the following steps for auto PO creation using purchase requisition.
i. Maintain Auto PO in Material master Purchasing view
ii. Select Automatic purchase order in Vendor master- Purchase data
iii. Maintain info-record
iv. Create PR through ME51
v. enable source determination during creation of PR
vi. Execute using ME59N
But Auto PO is creating with the same document type (e.g NB) which is used while creating purchase requisition (e.g NB). Following steps have done in SPRO.
1. SPRO - MM - Purchasing - purchase requisition - define document type
a. NB- PR document type LINK TO DI01- PO document type
2. SPRO - MM - Purchasing - Purchase order - Define document type
a. DI01- PO document type LINK TO NB- PR document type
3. There is no linking from NB - NB & DI01 - DI01 but still it is creating auto PO with document type NB iif requisition has been created with document type NB.
Please suggest on this . waiting for ur quick response.
Thanks...
ARATI.
Thanks!
Arati.
Edited by: Rakesh Gupta on Aug 20, 2009 11:00 AM

Hi
Please check the below thread
PR to PO via ME59 -Doc type issue
Thanks/karthik

Function module for offline vendor creation.

Hi Xperts,
I have searched all threads but i didn't find it, plz help me its urgent,
Is there a Function Module or BAPI for vendor creation. The BAPI_VENDOR_CREATE works online. I am looking out for an offline. This is for avoiding the use of BDC that we are currently using.
thanx in advance
Regards,
Naresh.

Hey whats up xperts............

Vendor creation using fm 'Vendor_insert'

Similar Messages

Maybe you are looking for