Vendor with alternative data

Hi all,
I am tring to create a PO using a regular vendor.
The system fails to create purchase orders and suggests using a stock transport order instead.
The error message says:
"Please use a stock transfer document type in this case"
Diagnosis
You wish to create a purchase order or a scheduling agreement for a vendor to whom a supplying plant has been assigned. This corresponds to a stock transport order for a cross-company-code stock transfer, for whose items shipping data will be determined, deliveries and billing documents will be generated and, finally, incoming invoices will be posted (in the standard system, this corresponds to order type NB).
This transaction must involve more than one company code. However, with the data entered this is not the case: the supplying plant that is assigned to the vendor belongs to the same company code as the purchasing organization entered.
what the root cause of the problem is? is any setting in the vendor master that I need to correct?
Many thanks

Please check
Procedure : Choose – XK03 enter the vendor
In the views select” purchasing data “ (ie) check  the box.
In the menu  extras Addl purchasing data
Here the supplying  plant is defined as the vendor ( ie that plant is treated as a Vendor –as the SUPPLYING PLANT )
That is why you are not able to create P.O
G.Ganesh Kumar

Similar Messages

  • Use View Object with Alternative Data Sources in View Link

    In my case, I created a view object based on alternative data source (not with SQL query). I have setQuery(null) in the override create() function for this View Object. When I use this View Object at the destination end of the View Link, the setQuery(null) will raise Jbo-26016 exception (You cannot set customer query (calling setQuery()) on a view object if it is the detail view object in a master detail view link.) which does not allow me to do that. I looked Avrom's Framework for Database API-Based ADF BC, in which he override the DBTransaction and CallableStatement in order to intercept the default query clause set by the View Link. I'd like to see if there is any alternative ways to achieve my objective?

    Just following up what I found so far. I'm trying to use customized View Object based on alternative data source at the destination end of View Link with ADF 10.1.3.
    1. For the View Object at the destination end of View Link, I can not call setQuery() which will raise Jbo-26016 exception.
    2. I can omit the setQuery(null) call in my customized ViewObjectImpl, and as long as there is no SQL statement in the View Definition XML, it won't cause problem when calling the executeQueryForCollection() of the super class.
    3. The override executeQueryForCollection() must call the super.executeQueryForCollection() in order to get appropriate result (I tried to skip the call and it does not give back any results)
    4. The funny thing is, when I make getQuery() call in my customized ViewObjectImpl (I'm just trying to double check if the Query object is clean or not), the query object is set to "SELECT FROM" following the getQuery() call, and which causes the exceptions when I call super.exeuteQueryForCollection(). I found out later from the Javadoc API which is implemented in that way.
    So I guess my case is resolved by not making specific call to setQuery(null).

  • ECH - ECM -- Change leaders and change packages using alternative dates

    Our company is an engineer to order business.  The Engineering Managers would like to be able to see all the work/changes to objects that occurred for a customer project.  So, the use of a change leader and change packages seems to make sense to allow the managers to see all the objects related to a project, but at the same time allow various sub-assemblies be released at different dates. 
    I was planning to set the change leader with the date of the final erection of the piece of equipment and then use the change packages with alternative dates to release the drawings and sub-assemblies as needed to ensure the appropriate delivery time. 
    However, even though I can use alternative dates in the change package, I don't get a pop-up window when assigning the change package to the document or BOM for selecting the appropriate date for the object. 
    Is there a setting I need to enable for this to work? 
    Thanks!
    -J

    I didnt understand what your requirement exactly is....
    but if you are trying to shift all BOM data from 4.6 C to some higher version of SAP , to my knowledge ...
    SAP does not support upward compatibility......

  • Vendor Texts per VSR/Site (Alternative data)

    Hi all
    How can I define Vendor Texts, to be used as Purchase Order Header Texts, per Alternative data, i.e. per Vendor Subrange (VSR) and/or Site/Plant?
    This would correspond to a text with Application Object (TDOBJECT) LFM2 instead of LFM1 (which is used for normal POrg specific Vendor Texts).
    I am using IS Retail and my Vendor Account Group has "Data Retention Levels: Purchaing" set for both VSR and Site/Plant.
    Steps (the way I hoped it would work):
    - Tcode: MK01/MK02/MK03
    - Select: Purchasing Data (this is where you normally enter texts via menu Extras - Texts)
    - Click: Alternative Data
    - Select: Specific alternative data (e.g. VSR)
    - Click: Purchasing
    - Menu: Extras - Texts (unfortunately not enabled at this step)
    The second step would of course be to enable the automatic copy to PO (Define Copying Rules for Header Texts) but let us take that later...
    Regards
    Dan

    the docu for retail says: text are possible at vendor sub-range
    http://help.sap.com/saphelp_470/helpdata/en/12/084445470311d1894a0000e8323352/frameset.htm
    I have not seen such option in core ERP system, and I never worked with Retail, so I cannot give you an reliable answer where to check.
    I usually would check in purchasing customizing OLME > Vendor master > define purchasing org specific texts.
    In core ERP I do not have an option to switch the text object.

  • How use of alternative data in Vendor master and fn??

    Hi
    Here is the scenario
    We have the vendor master where, in alternative data all the plants is linked to the vendor with some plant specific data to it such as planning calender by night, plan delivery time, and purchasing group.
    and all these info is fed to the system through ABAP forms, so when i try to amend some of the plant specific data through the form it does erase the existing data  and doesn't overwrite the new data into it
    to find the root cause i need the following
    Question -
    1. How do we make the alternative data active in vendor master- either through config changes or is there anything else??
    2. what may be the possible reasons for the plant data not overwriting
    Please do reply in detail and if config changes with steps
    Thanks for everyone
    Regards/Suresh

    1. How do we make the alternative data active in vendor master- either through config changes or is there anything else??
    It is std functionality in Vendor master, could be created thru XK01 or XK02.
    2. what may be the possible reasons for the plant data not overwriting?
    Check the ABAP part, might be missing something...
    Regards
    TGB

  • J1i2 report error ? if the vendor is attached with alternative payee

    Dear MM experts,
    I  am having an  issue with regard to J1i2 report. I have raised PO with JVCS tax condition on vendor (this vendor master has been attached with alterntive payee) .
    J1I2 report is not able get the data  of POs/MIROs detaile for such vendors (alternative payee attached). J1I2 is considering and pulling report for only Vendors (who are not having alternative payee code in vendor master data)
    Can i get help from experts, how I can get details of Vendors (attached with alternative payee vendor code).
    Thanks in advance,
    Thanks & regards
    Srihari
    Edited by: Ediga Srihari on Dec 24, 2009 11:37 AM

    problem/issued solved by sap service market place by suggesting us to go for Zreport.
    thanx
    Srihari

  • Alternative data for Vendor

    Hello,
    I would like to use the alternative data for the vendors. But, I canu2019t manage information such as planning cycle at the vendor level.
    The information comes from the material and not from the alternative data of the vendor.
    For example, the MRP always consider the planning cycle from the material and not from the vendor.
    Help would be appreciated.
    Regards

    Hello,
    I dont think u can maintain information relating to material in vendor master..instead u can try in souce list for vendor-material combination.
    Since MRP/Planning will be pertainied to plant-material, you can maintin them at material level and at plant level for proper planning....
    BR,
    Krishna

  • Vendor with last transaction date

    Hi,
    Can I generate any report which contains all vendors with last transaction date? THis is for audit purpose.
    Thanks & Regards,
    Rajaneesh.C

    Hi,
    You can take the report of the  FI accounting document for all vendors based on the company code and the posting date ( input the present date) in the T code- S_ALR_87012991.
    regards,
    Kannan B

  • Activate Alternative data button in Vendor Master

    Dear experts ,
    How can I activate alternative data button in vendor master . This button appears gray 2 me , and is there in purchasing & partmer functiopns screens
    reagrds
    anis

    Hi
    Goto OMSG tcode select the relevant account group , there select the check boxes under Data retention level purchasing
    for both Vendor subrange & Plant level.
    Now if you go to XK01 in purchasing org data you can see the alternative data open for data entries.
    Hope it solves your issue
    Thanks /karthik

  • Automatic debit / data carrier with alternative payer

    Hello,
    Does anybody know how to configure the data carrier to have a file with data records per alternative payer and not per main payer? Example:
    Payer 1: Markt 10
    Payer 2: Markt 11
    Alternative Payer for both: Head Office 20
    The postings are in the payers. The automatic debit uses now the "alternative payer" and its bank, but generates a file with one data record for each "payer". Our client requests one single posting per Head Office (alternative payer). I am looking for a solution to have the data carrier program add up the items and generate a file with single records per "alternative payer". Postings in the Head Office are not possible.
    Does anybody know if there is a user-exit for this? PMW? Any ideas?   Many thanks!!!!

    Hi
    A customer who pays on behalf of another customer is known as an u2018Alternate Payeeu2019 (or Alternate Payer). Though the alternate payee pays on behalf of another, the system maintains all the transaction details in the account of the original customer. Designating u2018alternate payeeu2019 does not absolve the customer of his/her obligation for payment.
    The u2018alternate payeeu2019 can be maintained in Client-specific data or in the Company Code area. When maintained in the Company Code area you can use that payer only in that Company Code; if defined at the Client level you can use it across all Company Codes.
    There are three ways to u2018selectu2019 the alternate payee when an invoice is processed:
       1. The alternate payee (say, 1000) entered in the customer master record is the one selected by the system as the default.
       2. When there is more than one alternate payer (say, 1000, 1900, 2100, etc.) defined for a single customer in the master record (you will do this by clicking on the u2018allowed payeru2019 button and create more than one payer), you may select a payer (say, 2100) (other than the default, 1000) while processing the invoice. Now the system will ignore the alternate payer (1000) coming from the master record.
       3. If you have put a check mark in the u2018individual entriesu2019 check box in the u2018alternate payer in documentu2019 section in the customer master record, then this will allow you to propose a new alternate payer, say, 3000 (other than those already defined in the system). Now, after defining this alternate payer you can use it to process the invoice. In this case, the alternate payer (3000) takes precedence over the payers (1000 and 2100) in step 1 and 2 above.
    Regards
    Tanmoy

  • Vendor with 2 VAT numbers and MIRO tr

    Hello,
    If I have a vendor  with 2 VAT numbers (t-code xk03), i.e.,  one for PL by default and another one for FR. When the customer in t-code MIRO wants to choose VAT number for FR it let him do it, but then if we go to the FI document xxxxxxxxxxx,  in the "additional data" still comes up PL unspite was chosen FR.
    So, the question is why does it happen this way and how we can choose and keep FR?
    B. Regards
    Francisco

    Hello,
    What I see from MIRO is that if you work with a vendor with VAT reg. number"PL", (also thi vendor has alternative VAT no. for FR,and this is what I need for the invoice), and change in MIRO Reporting country to "FR" the alternative vendor VAT, the financial invoice (51........) will take the original VAT vendor number "PL", (that I change it before to FR with Rep. country in MIRO).
    How can I create a financial invoice with the other VAT no. (FR) for this vendor?
    Regards

  • Vendor Hierarchy Validity Dates

    Hi
    I have a scenario where we need o create Vendor Hierarchy with past validity dates to support rebate aggrements, SAP standard will only allow you to create Vendor Hierarchy with validity date as current date.
    What is the alternative approach for this, is there any way we can maintain vendor hierarchy with historic past date as validity date.
    Appreciate your inputs on this.
    Regards
    Vickey

    Hi venkat,
                    I have worked in Territory but never encounter any mass update issue. I dont think that there is any standard API to do so. You would have to write a program/API to do so.
    Why mass update of validity dates for Territories ? I am interested to know the current Territory model at your site. When you create any terriotry then its Valid to date remains as 31.12.9999 by dafualt. As per your requirement you can create more valdiity period within this period. Had you delimit the valid to date during Terriotry creation ?
    Regards,
    Piyush

  • Unable to Archive Customer only with General Data

    Hi,
    I am trying to archive the Customer master only with General Data. I followed the below steps.
    1.Execute SAPF047 - To establish the link b/w customer and vendor
    2.Tran: XD99 , Set the del flag and confirm the same in xd03
    3.Tran: F56A , Select FI_ACCRECV object and perform the following
       1. Preproc => Preprocess resulted that no data found in this category
       2.Write => Preprocess resulted that no data found in this category
       3.Delete  => No data found
    Note : I selected "General Master Records" and also tried with "SD Data" and "FI Data".
    All resulted the same. Any Hints on this ?
    Regards
    Prasath

    Hi Prasath,
    Please follow the following steps...
    1)Go to Transaction <SARA> and give the object name FI_ACCRECV and press ENTER
    2)Go to Customizing -> Application-Specific Customizing->Mark customer for deletion (centr.) and mark the customers for deletion(This screen can alternatively be reached using transaction XD06).
    3)Schedule the Write variant and execute the jobs
                   Data To Be Archived ---> General Data
                   Customer -
    > Give Customer No to be archived
                   Consider Del Indic----
    > Checked (If you are not doing step2, this can be unchecked)
                   Processing option----
    > Select Production mode
    4)Select Delete in SARA and run the delete jobs for the data which has been archived in step 3.
    I dont see a preprocessing program available for the archiving object FI_ACCRECV. If you have that option available then it should automatically set the deletion indicator when u run the program , ie in that case step 2 can be avoided)
    Hope this input helps you.
    Regards
    Asish

  • Vendor with multiple bank details....paid to the 1st bank account while inv

    Hello Experts,
    We have a vendor with two bank accounts in the vendor master. Now while making the payment, I mean, which account will the money goes? at the time of F110 , we paid to the 1st bank account in the vendor master..
    Settings in vendor master:
    I 'name' the bank accounts in the vendor master, in the field Bank Type. While posting through MIRO, insert this code into the line item 'Patner bank' and the payment program will pick up the bank account accordingly BUT If I don't add this information to the Patner bank account, than always the first bank account will be picked up..
    I want that even if don't add any info in partner bank in the line item,  at the time of F110 , it should paiy to the 2nd bank account in the vendor master..
    This is a very stupid requiremnt but our users wants like this only.
    Kindly show me some light in this dark tunnel...please.
    regards,
    nupur

    Hi Nupur,
    In vendor master data under 3rd tab where we record all bank details of the vendor left hand side you will find one column 'C' .i.e., Collection authorisation......kindly check this option for your second bank to which you want to make the payment.
    Hope this helps you.
    Regards,

  • Reg: Creation of BOM along with Alternative BOM

    Hi Experts,
    I have written the below code for creating BOM along with Alternative BOM, I'm getting the following error.
    W BAPI1080             028
    Error/warning when checking the structure of the BOM group with ID=
    A BAPI1080             002
    Basic data for (BOM) group available twice
    A BAPI                 001
    No instance of object type BOMGroup has been created. External reference:
    W BAPI1080             028
    Error/warning when checking the structure of the BOM group with ID=
    A BAPI1080             002
    Basic data for (BOM) group available twice
    A BAPI                 001
    No instance of object type BOMGroup has been created. External reference:
    Please find the piece of code below.
      SORT it_bom01 BY matnr idnrk posnr ASCENDING.
      LOOP AT it_bom01 INTO wa_bom01.
        AT NEW matnr.
          CLEAR:
            it_bomgroup[],
            wa_bomgroup,
            it_variants[],
            wa_variants,
            it_items[],
            wa_items,
            it_matrel[],
            wa_matrel,
            it_itemas[],
            wa_itemas,
            it_return.
        ENDAT.
    * Material BoM Group Header Data
        wa_bomgroup-bom_group_identification = 'IDENTIFICATION'.
        wa_bomgroup-object_type = 'BGR'.
        wa_bomgroup-object_id = 'ID'.
        wa_bomgroup-bom_usage = wa_bom01-stlan.
        wa_bomgroup-ltxt_lang = sy-langu.
        wa_bomgroup-technical_type = ' '.
    *   wa_bomgroup-bom_text = .
        wa_bomgroup-created_in_plant = wa_bom01-werks.
        APPEND wa_bomgroup TO it_bomgroup.
    * Header Details of the different variants
        wa_variants-bom_group_identification = 'IDENTIFICATION'.
        wa_variants-object_type = 'BOM'.
        wa_variants-object_id = 'ID'.
        wa_variants-alternative_bom = wa_bom01-stlal.
        wa_variants-bom_status = wa_bom01-stlst.
        wa_variants-base_qty = wa_bom01-bmeng.
        wa_variants-valid_from_date = wa_bom01-datuv.
        wa_variants-alt_text = wa_bom01-alt_text.
        wa_variants-function = 'NEW'.
        APPEND wa_variants TO it_variants.
    * Details of the items of the variants
        wa_items-bom_group_identification = 'IDENTIFICATION'.
        wa_items-object_type = 'ITM'.
        wa_items-object_id = 'ID'.
        wa_items-item_no = wa_bom01-posnr.
        wa_items-item_cat = wa_bom01-postp.
        wa_items-component = wa_bom01-idnrk.
        wa_items-comp_qty = wa_bom01-menge.
        wa_items-valid_from_date = wa_bom01-datuv.
        APPEND wa_items TO it_items.
    * Details of the materials of the different variants
        CLEAR it_matrel.
        wa_matrel-bom_group_identification = 'IDENTIFICATION'.
        wa_matrel-material = wa_bom01-matnr.
        wa_matrel-plant    = wa_bom01-werks.
        wa_matrel-bom_usage = wa_bom01-stlan.
        wa_matrel-alternative_bom = wa_bom01-stlal.
        APPEND wa_matrel TO it_matrel.
    * Linking items to the corresponding variants
        CLEAR it_itemas.
        wa_itemas-bom_group_identification = 'IDENTIFICATION'.
        wa_itemas-sub_object_type = 'ITM'.
        wa_itemas-sub_object_id = 'ID'.
        wa_itemas-super_object_type = 'BOM'.
        wa_itemas-super_object_id = wa_bom01-matnr.
        wa_itemas-valid_from_date = wa_bom01-datuv.
        wa_itemas-function = 'NEW'.
        APPEND wa_itemas TO it_itemas.
        AT END OF matnr.
          CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'
            EXPORTING
              all_error         = 'X'
            TABLES
              bomgroup          = it_bomgroup
              variants          = it_variants
              items             = it_items
              materialrelations = it_matrel
              itemassignments   = it_itemas
              return            = it_return.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
          LOOP AT it_return.
            WRITE:/ it_return-type, it_return-id, it_return-number,
            it_return-message.
          ENDLOOP.
        ENDAT.
      ENDLOOP.
    Thanks and Regards,
    Abdur Rafique

    Hi Sree,
    I used your code, I removed the levels because, i have only one level 'the lineitems'. Please find the modified code below. I'm not able to create the BOM, it throws an error as "BOM is recursive". I checked the header and item contents before passing to FM, it is correct.
    Please help me with the solution.
    REPORT  zbom_sdn.
    TYPE-POOLS: truxs.
    DATA: bom_header     LIKE cad_bicsk,
          bom_item       TYPE TABLE OF  cad_bom_item WITH HEADER LINE,
          bom_sub_item   TYPE TABLE OF cssubitem WITH HEADER LINE,
          dms_class_data TYPE TABLE OF cls_charac  WITH HEADER LINE,
          sap_field_data TYPE TABLE OF rfcdmsdata  WITH HEADER LINE,
          e_return       LIKE cad_return-value,
          e_message      LIKE message-msgtx,
          e_message_len  LIKE cad_return-message_len.
    DATA v_item  TYPE i.
    TYPES : BEGIN OF ty_data,
             matnr TYPE cad_bicsk-matnr," Material
             werks TYPE csap_mbom-werks," Plant
             stlan TYPE csap_mbom-stlan," BOM Usage
             datuv TYPE csap_mbom-datuv," Valid From
    *         posnr TYPE stpo_api03-item_no," Item Number
             idnrk TYPE stpo_api03-component," BOM Component
             postp TYPE stpo_api03-item_categ," Item category
             menge TYPE cad_bom_item-menge," Quantity
             bmeng TYPE stko_api01-base_quan," Base Qty
             stlst TYPE stko_api01-bom_status," BOM Status
             stlal TYPE csap_mbom-stlal," Alternative BOM
             alt_text TYPE stko_api01-alt_text," Alternative BOM text
            END OF ty_data.
    DATA : it_data TYPE TABLE OF ty_data ,
           wa_data TYPE ty_data.
    DATA:   wa_raw TYPE truxs_t_text_data.
    SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-001.
    PARAMETER : p_file TYPE rlgrap-filename OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK b2.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
      CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
        EXPORTING
          program_name  = syst-repid
          dynpro_number = syst-dynnr
        CHANGING
          file_name     = p_file.
    START-OF-SELECTION.
      CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
           EXPORTING
    *       I_FIELD_SEPERATOR          =
             i_line_header              = 'X'
             i_tab_raw_data             = wa_raw     " Work Table
             i_filename                 = p_file
           TABLES
             i_tab_converted_data       = it_data[]  " Actual Table
           EXCEPTIONS
            conversion_failed          = 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.
      CLEAR: bom_header, bom_item, bom_sub_item.
      REFRESH: bom_item, bom_sub_item.
      DATA : v_lineitem TYPE sposn VALUE '0000',
             v_slineitem TYPE sposn VALUE '0'.
      LOOP AT it_data INTO wa_data.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            input  = wa_data-matnr
          IMPORTING
            output = wa_data-matnr.
    * fill BOM header
        CLEAR  bom_header.
        bom_header-matnr = wa_data-matnr. "'000000000200000016'.
        bom_header-stlal = wa_data-stlal. " Alternative Bom
        bom_header-werks = wa_data-werks.                       "'1000'.
        bom_header-stlan = wa_data-stlan.                       "'3'.
        bom_header-bmeng = wa_data-bmeng.
        bom_header-cadkz = 'X'.
        bom_header-stktx = wa_data-alt_text.
    *      bom_header-ztext = wa_data-text.
        bom_header-datuv = wa_data-datuv."'01.10.2010'.
    * fill item
        v_lineitem = v_lineitem + 10.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            input  = v_lineitem
          IMPORTING
            output = v_lineitem.
    *    bom_item-upskz     = 'X'.     " If We hav the Sub items Enable it.
        bom_item-idnrk     = wa_data-matnr. "'000000000200000017'.
        bom_item-posnr     = v_lineitem.
        bom_item-postp     = wa_data-postp."'L'.
        bom_item-menge     = wa_data-menge.                     "'1'.
    *    bom_item-fmeng     = wa_data-fqty.
        APPEND bom_item.
        CLEAR: bom_item.
        AT END OF matnr.
          CALL FUNCTION 'CAD_CREATE_BOM_WITH_SUB_ITEMS'
               EXPORTING
                    i_bom_header   = bom_header
                    i_auto_posnr   = ''
               IMPORTING
                    e_return       = e_return
                    e_message      = e_message
                    e_message_len  = e_message_len
                    e_bom_header   = bom_header
               TABLES
                    bom_item       = bom_item
                    bom_sub_item   = bom_sub_item
                    dms_class_data = dms_class_data
                    sap_field_data = sap_field_data
               EXCEPTIONS
                     OTHERS         = 1.
          REFRESH bom_item.
          WRITE : e_message.
        ENDAT.
        CLEAR wa_data.
      ENDLOOP.
    Thanks and Regards,
    Abdur Rafique

Maybe you are looking for