Client level data & Plant level data

Dear ,
what exactly client level data & Plant level data.
In Material master Whats the reason that Purchasing is displaying in Client level data & also in Plant level data
*Client level Datas:--
Classification
Purchasing
Basic data
Storage
Plant level Datas:-
Accounting
MRP
Purchasing
Costing
Storage
Forecasting
Quality management
Sales
Regards,
Suresh.P

hi
the client level data is the field data which will be common for all plants
plant level data is the field data which is plant specific
also in purchasing view many fields are plant specific
to check it just do one goto mm03
give material and only select the pur view
at now give only plant and check fields
now repeate same without plant ,at this time u will see the client specific field
the UOM is the client level filed ,it is also in mRp view but as the mrp is used for plant it is in plznt specific data
hope it clears
regards
kunal

Similar Messages

How identify the data is client level,plant level or company code level

Dear sirs,
GM
How identify the data is client level,plant level or company code level?
If there is any T.code for same in SAP plz send me otherwise any procedure?
Hopeeeeeeeeee....

Hi,
Once you gain experience, you will not look at any table any field or any view...You will do it just like how you use keyboard once you pass type writing....
That is why every area of work, including master data is handed over to specialized teams...that will be their work day in and out....for some one newly entering, it will be little bit tough...once you practice, you will not be worried any more. Of course, basic data at client level, purchasing data plant level etc...some thumb rules are there...still, you will take big blow by following such thumb rules because if you verify storage condition assigned in the storage location is not storage location level!!!!!!!!!!!!!!!
that is experience!! In this forum, it is good to practice rewarding...else, there may not be any more replies
Good Luck
Message was edited by:
Gopala Turaga

Reg : client level data,plant level data,storage location level data

hi
when we enter the data mm01 we select views.these views are based on cleint level,plant level,storage location level .i want the difference between all the three levels.how do we differentiate.

As per our business process there are one company and in which many plants and storage location are available. In which many materials are available in different plant in different storage location.
As per SAP Standard structure: -
Company >> Company code1 & Company code2... >> Plant 1 & Plant 2 & Plant 3 .... >> Storage location 1 & 2 & 3........
And in all plant and storage location have different data.
Suppose in one plant we do quality testing for material and it may be possible in other plant we not perform quality testing for material. So in this case for same material quality data is different for different plants.
Client Level: - Means data is same for all plant level like Basic data
Plant Level: - Means data is based on plant level like Purchasing, Plant data, Quality data, Accounting view.
Storage location level: - Means data is based on storage location level, for different storage location data will be different like Storage location stock data ..
Due to this you can maintain different data on plant level & storage location level.
Regards,
Mahesh Wagh

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

Client level, plant level and material level batch

Hi,
Can any body tell me wat is the actual meaning of
!) Client level batch,
2) plant level batch,
3) material level batch
with exa. please.
Thanks
Nilesh Ithape

Hi,
Below is the extract from the IMG Documentstion..
====================================================================
Batch numbers can be unique at the following levels:
at plant level
at material level
at client level for a material
If you choose plant level, the batch number is unique in conjunction with the respective material and the plant. If you choose material level, the batch number is unique together with the material. At client level, the batch number is unique in the whole client.
To change the batch level, you have to start a conversion program. This program first checks whether conversion is possible and outputs an error log containing all batch numbers that occur more than once at the new level. Now you need to manually transfer these batch records to batch numbers within Inventory Management using a transfer posting 'material to material'.
If you change the level from plant level to a higher level, it is possible that batches with the same batch numbers in different plants are actually identical. In this case, all you have to do is remove stocks (including previous period stocks) so that all batches with the same batch numbers, except one, can be reorganized.
When you convert from plant level to material level, the material is then to be handled in batches in all plants in which it is defined.
=========================================================
Hope this helps..
Regards,
Siva

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-

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.

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

Difference Between "Client Level & Company Code Level"

Hello
Can any explain me the difference between client level and company code level?
What is the configuration that we do on client level and company code level?

Message: Dear,
Client : Unit within SAP system, self-contained, separate master data with independent set of tables. It represent corporate group.
Company Code : Smallest organizational unit of external account for which a complete, self-contained bookkeeping system can be replicated.
e.g, company within a corporate group
Note: You will do the configuration at company code level by logging into the client for master tables etc..

Client level setting and company code level setting

Hi Friends,
Can you tell me the client level settings and company code level settings in Configuration and master data?
Ex : Material type configuration - client level
Thanks in advance
Rgds
Madhavan

Dear,
For complete detailed information about SAP MM configuration, you can find on first thread or self exploration through net search.
Please have a look at: http://help.sap.com/SAPHelp_46c/helpdata/EN/e0/71369adc56d11195100060b03c6b76/frameset.htm
Regards,
Syed Hussain.

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

Client Level & Company Code Level Settings.

Hi
Which are the Settings in SD are At Client Level & At Company Code Level.???
I know that Batch management & Serial number profile is at Client Level.
Regards,
Amol

Hi
SD strat with Sales Organization assign to company code, next is Distribution channel and Divisions, combination these 3 called as sales area. next is sales offcie and sales groups.
Client and company codes top most level in SAP and Company code defined in FI.
Batch mangement activate at Plant level and warehouse level, settings need to done on Material master and plant level not at company code level, but plant assigned to company code.
Same as Serial number profiles related to Plant and Material master, again here plant is link to company code and material created under plant.
So, no where direct link to Company codes.
hopes it helps
thanks
Satish

Client specific data

Hi all,
What is the client specific data? Give two examples of client specific data

Organizational units in Enterprise Structure such as Company Code, sales Organization, Plant, shipping Pint, etc are Client specific.
Similarly Sales Document Type, etc are Client specific
To Check if it is client specific, in SPRO --> goto Additional Data --> Technical Data --> Client-Dependend.
Regards,
Rajesh Banka
Reward points if helpful.

Client bank data in F110

Hi,
I'm creating a file with F110 - Domiciliary Receipt - using program RFFOES_D ( Spain ). The output is ok with all the data except the client bank data !!
this information is maintained in TR: FD03, which has the adress from the client that appears in my file, but the bank client data is missing. I dont know why the info doesnt appear since is in FD03.
Do you think something is missing in costumizing ? Or on the other hand the standart doesent include this info ?
Thanks a lot
Mário.

Hi,
Thanks for your answers, i checked TR: FBZP and FI03, there were 2 checkbox's that had to be marked.
Full points
Best Regards,
Mário.

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 data & Plant level data

Similar Messages

Maybe you are looking for