Vendor Creation at Client Level

Hi Experts,
Would like to take your suggestion Plz.
My Client has 5 Company codes, and when we are craeting any vendor in XK01 we are creating the vendor specific to that company, 1) How could we extend the same vendor to different Company Codes ?
In Certain cases they doesn"t want the Certain vendor details to share for other Company Code. How could we go about this scenario ?
Plaese Advice
Best Regards
Javeed Ahamed

Hello Javed,
U can create Vendor in other company codes using T Code : XK01, using copying aids. ie wrt to a particular company code u can extend it to other company code as required.
and the data which is not required for some specific company can be removed , but its should company specific data ,
U cannot have different data for different companies which is client specific
Hopes this helps.
Regards

Similar Messages

  • MM Brazil localization - Mat. origin field used for CFOP at client level

    Hello All,
    I'm currenctly participating in the implementation of Brazil.
    I'm taking care of purchase module.
    In the PO, you can find fields necessary to the correct determination of CFOP code. among this fields, you have "Origin".
    This field indicates if the goods are provided from the same "tax area", from another "tax area" or from the country.
    This field is populated from the material master wher you can find a field 'origin' but at client level.
    Problem: how to handle a material bought from different vendor (one local, one outside the country?
    I very surpised SAP didn't didn't include this field in the Info record. Does some of you already had this case ? how did you handled the situation ?
    I was thinking to modify the logic for the population of the field at PO creation. that system is taking the value from a field stored in info record in priority (that would have to be created). How complex this enhancement could be ?
    Thanks for any information !

    Hi again,
    I am not sure if this change was made already per other customers. I got a couple of messages regarding this subject per month, however is quite complicated. I understand how complicated would be double the materials. The feasible solution would be the split. Is not that complicated, I promise to you!!!
    I do not know the points and where exactly the fields are retireved and possible changes points...I am sorry!
    I will recomend to you, make lots of regressition tests after finish the deploy of your solution. This is very important, as I said for the Nota Fiscal and have some legal implications. I would work close with a brazilian fiscal law, in order to check the results in genarally: Calculation taxes, accounting documents, Nota Fiscal, CFOP determination, etc...
    I would like to indicate this forum for you:
    /community [original link is broken]
    This is specific for Brazil localization subjects, such process, Nota Fiscal eletronica, etc....
    however there, the whole comunication should be in portuguese.
    The best regards

  • Bank details missing at Client Level

    Hi,
    We have created Vendor in R/3 system with Address and other detail including Bank details also.
    But At the time of record checking at client level .
    We are not getting the record releated to the Bank details .
    Can any body in the forum put some light on this issue.
    Thanks in Advance.
    Regards
    Rohit

    Rohit,
    I think that is the difference, Bank being a qualified table. In MDM you need to do load the tables individually. You need to extract the bank details from the R/3 separately and load in to the qualified table.
    Then when you load the Vendor Master table and the Bank code you are assigning to the Venodr if it exists in the qualified table, you should be able to see it there.
    Check out my blog
    /people/ravikumar.allampallam/blog/2005/09/06/mdm-import-manager--get-data-for-check-tables
    Hope this helps.
    Regards,
    Ravi
    Note : Please reward points if this solves your issue.

  • Data at Client Level

    What are the master data maintained at the client level?
    What is the system to avoid the duplication of data records?
    How to see the client specific master data?
    Regards,
    Komal

    Hi Komal
         The master datas maintained at client level are
          >Material Master
          >Vendor Master
          >Purchasing Info record
          >Customer master(SD Module)
          Access authorization is assigned on a client specific basis.A user master record must be created for every user for the client in which he or she wishes to work.If the Client field has not been prepopulated,each user must specify a client key when loggin on to SAP system.in this way ,the user specifies the client in which she or he works to work.All user input is stored,seperated by client.The processing and evaluation of data is like wise carried out on a client specific basis.So chances of duplication will give error message
    Hope this will help you
    Reward if useful
    Thanks and Regards
    SHYAM.R

  • Batch active at client level

    Hi All,
    Batch status is active at client level.
    However, in the inbound delivery I am able to receive an existing batch for some other material.
    Ideally, I should get an error that the batch already exists etc because the batch is active at the client level.
    Please help.
    Regards,
    Ankur

    Hi,
    Thanks for your inputs. Batch is active at client level.
    The check happens when we do the GR. At the time of GR, the system checks for existing batches and gives the error.
    Is there a way to put this check at the inbound delivery level itself ? Requirement is to give an error if there is an existing batch for other material during inbound delivery creation itself.
    Thanks !
    Ankur

  • Client level , company code level , chart of account level

    Hi experts
    Pls expline me which are we define under client level , company code level and COA level
    like :
    1) field status variant:
    2) Dunning procedure:
    3) document types:
    4) doc.number range:
    4) posting periods variant
    5) controlling area
    6) account groups
    7) vendor/cust master data
    8) dep key
    9) chart of dep area
    10) like...............................
    get points
    Geeta

    hi geeta,
    ClientA Client is the highest unit within an SAP system and contains Master records and Tables. Data entered at this level are valid for all company code data and organizational structures allowing for data consistency. User access and authorizations are assigned to each client created. Users must specify which client they are working in at the point of logon to the SAP system.
    A CompanyA Company is the unit to which your financial statements are created and can have one to many company codes assigned to it. A company is equivalent to your legal business organization. Consolidated financial statements are based on the companyu2019s financial statements. Companies are defined in configuration and assigned to company codes. Each company code must use the same COA( Chart of Accounts) and Fiscal Year. Also note that local currency for the company can be different.
    Company CodesCompany Codes are the smallest unit within your organizational structure and is used for internal and external reporting purposes. Company Codes are not optional within SAP and are required to be defined. Financial transactions are viewed at the company code level. Company Codes can be created for any business organization whether national or international. It is recommended that once a Company Code has been defined in Configuration with all the required settings then other company codes later created should be copied from the existing company code. You can then make changes as needed. This reduces repetitive input of information that does not change from company code to company code as well as eliminate the possibility of missed data input.
    Business Area Business Area is optional and is equivalent to a specific area of responsibility within your company or business segment. BA (Business Area) also allows for internal and external reporting.
    Another configuration requirement for set-up in SAP are the Basic settings consisting of the following:
    Chart of Accounts(COA)
    Fiscal Year Variants.
    Currencies
    The COA(Chart of Accounts)
    The COA(Chart of Accounts) lists all General Ledger accounts that are used by the organization. It is assigned in configuration to each company code and allows for daily General Ledger postings.
    Fiscal Year configuration
    Fiscal Year configuration is a must and can be defined to meet your companyu2019s reporting periods whether Fiscal (any period combination that is not calendar) or Calendar( Jan-Dec).
    Posting Periods are defined and assigned to the Fiscal Year.
    Within the periods you specify start dates and finished dates.
    SAP allows for 12 posting periods along with specially defined periods that can be used for year-end financial closing.
    Rohit Agrawal

  • Vendor creation-suggestion

    Hi,
    I request for a suggestion on creation of vendors.
    I have got @ 8 company codes involved in my implementation.
    Out of these 8 company codes, 2 company codes looks after the entire procurement..
    One company code (say A) looks after procurement requirement of 6 other company codes and the remaining company code (say B) does its purchasing.
    Company code A then transfers the goods to other 6 company codes as a Intercompany transfer.
    However the other 6 company codes can at times buy directly from these import vendors.
    This effectively means that all these vendors shall be available for all the company codes for procuring goods on their own.
    Based on this I would like to have recommendation on the level at which the vendors needs to be created.
    If I create a vendor on C Code level then it will be specific to that company code.
    I can have vendor created at P Org level (Assign P Org to all the plants.) which will allow me to use this vendor in all company codes. However, if I do so then I can  not enter data such as recon account data, double invoice check tick mark etc at the time of creation.
    I am not convinced the way I can create these vendors. Please suggest
    Thanks in advance
    Regards,
    manOO

    You have to create vendor at both company code and purchasing org level.
    You can create PO for a purchasing org only if the vendor is created at purchasing org level.
    You can do invoice verification for that PO, only if the vendor is created at the company code level for the company code mentioned in the PO. Otherwise you will need a payee partner function vendor who is created for the company code.
    Please look at the combinations you mentioned and you can work out the organization levels at which the vendors should be created.
    Regds,
    Lakshman

  • Client level, chart of accounts level, company code level

    Generally what are the areas under client level, chart of accounts level, company code level.
    For Ex. document types are client level, number range company code level
    like the above does we have any list which is falling in the above levels.

    1. Generally during customising when co code data is not asked , then settings are client level.
    Country, Currency, Document types, all variants of diff types, chart of accounts, etc
    2. Every master is having data - General data level (client level) for use by all co codes, Co code data level(basically for accounting purposes) and so on.
    These are applicable to GL, Vendor, Customer, Asset, Matlerials, etc
    For particular application we have more information at another object level also- Vendor- Purchasing, Customer-Sales, materials-Plant- controlling, etc
    3. Chart of accounts level assignments are done for all automatic posting definitions-which is applicable to all company codes which are using same chart of accounts.
    4. In material setting- valuation can be grouping level, co code level or plant level as these are related to costing and product costing.
    Hope the above will give some idea.
    In the above nothing is written about CO as you have not asked-

  • Make to order Scenario...any client level settings

    Hi
    please guide me as there any settings which are  at Client level or company code level.....
    shailesh

    Hi harshad,
    If you are asking about MTO please go through below notes:
    The Made TO Order Cycle:
    The sale department passes on the Made to order-Sales Order to the Material department so that material requirement is analyzed. This is done in SAP by carrying on an MRP Run for all the levels of the product BOM. This MRP Run would create Planned Orders for the shortages. Here the planned orders for fert sub assemblies, Components etc, are created. This planned orders for materials produced in house are converted in to Production order and planned orders for materials 
    procured from outside are converted in to Purchase order. The creation of Production order through the planned orders will convert all the dependant requirements in to dependant reservations.
    The dates of production or purchase are decided through the total replenishment time mentioned in the material master, If it is, in-house production, then the Route times precede over the total replenishment time entered in the material master. And the availability of all the components is ruled by the availability checking rules and by availability checking scopes. Thus whenever the system declares a product to be ready or available by a date it implies that the system has checked the availability of the material with respect to the Ware house stock, in coming stock   (Receipts) and all other planned orders already existing for the product or material. 
    In the Made to order production, sales order produced for Fert and Sub assemblies are converted in to production order during MRP run. The production orders created have a specific quantity, specific Basic start date and a specific Basic Finish Date, a set of operations and a set of component attached from the BOM. In course of production the quantities produced in the operation for an order should be confirmed so that the current status of work is available in real time situation. The components required for production are issued to the production order through goods issue by a movement type 261 and the issue is always made to the reservations or to the order, thereby clearing the reservations. Issues of unplanned components are made as new items issue and not as order issue. The quantities, for an order which are produced completely are the put in to stock i.e. a Goods Receipt is done. 
    Thus the made to order cycle starts with the sales orders and converting them to Production Orders through MRP Run and there off confirming produced quantities for an order and finally putting the order in to stock.  
    The Cycle of Made to order: Steps: MTO Scenario
    1. Material Creation (Made To order Material with major changes of: Item Category: 0004-make to order/assem.,or 0001-make to order)
    2. Route Creation
    3. Creation of BOM
    4. Sales order
    5. Production order Scheduling, Costing, Release and Save
    6. Production order Quantity confirmations for operations, Parallel task of material issue to order or to reservations (261) 
    7. Fully Produced Production Quantities will be put into stock (GR)
    8. Delivery against sales order
    9. Invoicing.                              
    You have to configure following;
    1. OVZG - Defining Requirements Classes SD
    Requirements
    Availability X
    Requirement Transfer X
    Allocation ind. 2
    Assembly
    Special Stock E
    Account assignment
    Acct Assgt Cat. M
    Changeable 0
    2.  Maintain Account Assignment/Costing  Basic Functions Sales and Distribution  Requirement Classes For Costing/Account Assignment
    Assembly/Requirements
    Assembly type 0
    Account assignment
    Acct Assgt Cat. M
    Valuation M
    Without Val. Strategy X
    3. OVZH - Defining Requirements Types
    4. VOV8 - Defining Sales Document Types
    5. Sales and Distribution   Assign sales Area to Sales Sales Document Header  Sales Documents Sales  Document Types
    6. VOV7 - Maintaining Item Categories
     Sales Documents  Sales 7. Sales and Distribution   Assign Item CategoriesSales Document Item
    8. VTFA / VTAA - Copy Control: For Billing document and Sales document
    9. KE4I - Assigning SD Conditions to CO-PA Value Fields
    10. VOK0 - Pricing Procedure Setup for MTO Sales
    Thanks and Regards,
    Sateesh.Kandula

  • Error in Vendor Creation

    Hi,
    In Vendor creation , while  selecting  the Country as United States ( US) in Vendor address the following error message is displayed
    "Communication error with the external tax system (VERTEX_MS0018)
    Message no. TAX_TXJCD864 "
    How to solve this issue?????
    Regards,

    Hi,
    Check the following entries.
    OBCO   : Check the schema TAXUSX  (VERTEX Standard Jurisdiction Code)
    OBCP   :  Select the costing sheet TAXUSX, check the tax jurisdiction codes
    IMG>Financial accounting new > Financial accounting Global settings > Tax on sales/puchases >basic settings > External tax calculation.
    Take FI consultant help make necessary settings.
    Regards,
    Chandra

  • 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.

  • Vendor Creation ,Partner role OA not allowed for Vendor of a/c group ZLOV

    Dear Freinds,
    I am facing problem of  Vendor creation , i am getting message  PARTNER ROLE OA NOT ALLOWED FOR VENDOR OF ACCOUNT  GROUP ZLOV.
    While creation of  Vendor in Partner function  i  could not  enter  partner number, system is not accepting any data, message is getting as above.due to which i could not create any vendor.
    Presently I am in process/ setting of  ERS functionality in MM,
    now all my Vendor creation is stuck up ,
    please help me how to solve the problem
    Regards
    Dilip

    Hi Dilip,
    Check first have you Define Permissible Partner Roles per Account Group..
    Check the path:
    SPRO-Materials Management-Purchasing-Partner Determination-Define Permissible Partner Roles per Account Group
    Here check whether OA is assigned with ZLOV or not...If no then click on new entries and enter partner function as OA and Vendor account group ZLOV...Save nd come out...
    Now proceed...Hope it helps..
    Utsav

  • 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............

  • Need Sample Code for Vendor creation using JAVA API

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

  • Employee vendor creation

    Hi ,matically
    how to create automatic vendor creation via PRAA.
    Is this prgm can run in back ground and will updat enewly hired employees automatically.
    GK

    Hi GK,
    Yes this can be done.
    Follow the steps mentioned in this doc - http://scn.sap.com/docs/DOC-27098
    Thanks
    Vipin

Maybe you are looking for