What is client independent customizing....Newbie

Gurus
Client has Application data(master + transactional data)
Customizing data pertaining to the client
Then what is client independent customizing...I read on SAP...but I do not understand its weird definition...please explain me in simple English
During client copy when should i choose client independent data to be copied? if my target client already exists.

Hi
A client is an independent business unit within an R/3 System, Data in the R/3 are classified as cleint-Dependent and client-independent.
Client-independent data such as ABAP Programs, R/3 repository objects throught the entire system.
Other data is client-dependent. meaning, it can be viewed from one client.Cleint-dependent data includes customizing application and user data.
enterprise IMG is cleint independent.
REgards
Anwer Waseem
SAP BASIS

Similar Messages

Client Independent Customizing

Hi Experts,
Can anyone help me to find all the client independent customizing that may affect PS module?
Thanks in advance,
Neil

In Spro include the column which shows the technical data >Client-Dependency (Menu>Additional Information>Technical Data>Client Dependency). Now under each lowest node of PS you should find the information required
Regards
Sreenivas

Client Independent custom table create

Hi ,
As per the requiremnts i have created a custom table in Client DEV1... and updated the table through an interface.
The custom table have 12 entries in that Client.
Now the same custom table when checked in another DEV Client DEV2 which is almost the replica of DEV1.. i.e if any custom table or custom program is ctreated in DEV1 it reflects in DEV2,,,, the entries are not found.
COuld anybody let me know incase some settings needs to be checked for checking the same entries in Client DEV2 as in Client DEV1 for the same custom table?
Or there are some steps included while creating thre custom table so that its entries are found in both clients ?
Or execute the interface in DEV2 can create entries.
Which odf the above approach needs to be considered ?
Thanks
Kritika

Hi Kritika !!
If you want to reflect the same records in different clients, you have to delete the MANDT field from your Custom table. then only the records will reflect in all the clients of the same Custom Table.
If you are not willing to remove the Field MANDT from Custom table and U need the same records in all the clients, U have to create records through Utilities -> Table Contents -> Create Entries or with the Help of TMG or with the help of Ur Interface.
Regards
valluru

What exactly is the diff between client dependant and client independant te

Hi gurus,
What is the diff between client independant and client dependant term.. I initially had a confusion related to client independant and client dependant Transport requests, where else are these words applicable, do they apply to data as well, if so how? any links to help me understand the difference..
regards,
kishore

Hi Kishore,
Client Independant: These objects are not specific to any client. And it is universal which can be viewed,changed across the clients.
Client Dependant: These are the objects can be viewed, changed for the client for which it has been assigned. Other clients do not have access on these objects.
In SAP, all objects are finally stored as tables. "Mandt" is key field which determines whether the object is client dependant or not.
Client Independant transport requests will make the transported objects available across the clients. and Client dependent transport request make the objects available only for the client mentioned by field "Mandt"
Regards,
Dinesh D

If custom programs, reports and FM are client independent

Hi,
If custom programs, reports and FM are client independent why we need to transport them and why they are not visible in other clients............
Thanks,
Tanmaya

Yes Tanmaya you are right,
Say You DI2 system & you have 410, 420 ,430 clients in it, then these objects will be visible in all these clients.
say you have DI4 system 410, 420, 430 clients so you have to transport them to DI4 & to other sytems also like QD1, PD1 etc.
Hope this clears your doubt.
Close the thread if this solves your query.
Regards
Abhii

Client independent and dependent

Hi All,
What are the Client dependent objects and independent objects in Financial Accounting and Controlling?
Urgent please
Thanks and regards
Krishna

Go to SPRO-Additionl information-Technical data- Client specific.
The to the right of the implementation guide categories you'll see either Client-specific (customizing) dependent or Cross-client (workbench-independent)
pls assign points to say thanks.

Why sapscripts are client dependent & smart forms are client independent?

why sapscripts are client dependent & smart forms are client independent?

You developed the script in development client , you can't find the same in testing client even though the server is same.
Where are You developed the smartform in development client , you can find the same in testing client even though the server is same.
Few more reasons why....? Please read below:
SAPscript technology is based on a mainframe product from the 1980s,
while Smart Forms have only been around since (roughly) 2001. With that sort of time gap,
there are bound to be significant differences between the two tools. As you have noted correctly, client dependence is a fundamental one.
Although SAPscript has had some incremental improvements over time,
its forms have always been -- under the hood -- relatively passive objects, with minimal embedded logic.
These forms were designed to be driven and controlled by ABAP programs,
much in the way ABAP programs read in database tables to produce reports;
if you ever download a SAPscript form (e.g., via utility program RSTXSCRP),
and look at the portable text file it produces you'll see what I mean.
Many text objects (e.g., invoice header texts) are bound directly to documents which are client-dependent, so it makes sense for these text objects to also be client-dependent. From a complexity standpoint, SAPscript forms are close enough to these text objects where I can see how it made sense at the time to make them client-dependent too.
Conversely, a Smart Form is significantly more robust and complex. For instance, it can contain program nodes and nested tables with patterns. When a Smart Form is compiled, it generates an ABAP function module and these are always client-independent. This is appropriate, given that this form has more in common with an ABAP program than its predecessor. For instance, when a print program calls a Smart Form, the form itself takes over to produce output, without any further direction from the print program. In fact, the join is so seamless that I often find myself using a Smart Form's Initialization section for logic to handle any data gathering not handled by the print program. I would never even think to attempt this with SAPscript.
Several factors figured into SAP's decision to make Smart Forms client-independent, including customer feedback. There are significant advantages to client-independence. For instance, a change made in one development client happens immediately across all development clients. Among other things, this means we don't have to waste time figuring which client contains the most recent version -- they all do! In addition, transporting Smart Forms is easier, since we can safely bundle them together in the same transport as their client-independent print programs (no worry about mixing client-dependent and independent objects).
Check the beloe links for more information
script and smart forms
http://www.sap-img.com/smartforms/smartform-sapscripts.htm

Client dependent and client independent in ALE

I am going through pdf learning of an ALE scenario,i couldnot get wat is meant by client Independent and client dependent.
How can i conclude
Create message type (WE81){color:green} Client independent {color}
To create a new message type, follow these next few steps:
u2022 Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
u2022 Choose Create logical message type by double clicking on it
u2022 Click on change icon to enter change mode
u2022 Click on New entries to add a new type
u2022 Enter the required message type, in our case it is ZINVRV and an appropriate description
u2022 Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) {color:green} Client independent {color}
To link the message type to the IDoc type follow these next few steps:
u2022 Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
u2022 Click on change icon to enter change mode
u2022 Click on New entries to create the link
u2022 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
u2022 Save and exit
u2022 Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
u2022 Click on change icon to enter change mode
u2022 Click on New entries to create the link
u2022 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
u2022 Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
u2022 Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
DOC NAME: ALE_SCENARIO_DEVELOPMENT_PROCEDURE
Version 1 Page 6 of 16
ALE Scenario Development Guide
u2022 Type in your message type ZINVRV and press enter
u2022 Click on New entries
u2022 Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
u2022 Save and exit.
You have now created an object that weu2019ll use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) {color:green} Client dependent {color}
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
u2022 Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
u2022 Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
u2022 Choose the receiving systems to which the sending system must forward message type ZINVRV to.
u2022 For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
u2022 Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
u2022 Save the entries.
Refer my query within color:green
Edited by: aditya sharma on Jul 14, 2010 12:57 PM
Edited by: aditya sharma on Jul 14, 2010 1:01 PM

A client is an independent business unit within an R/3 System, Data in the R/3 are classified as cleint-Dependent and client-independent.
Client-independent data such as ABAP Programs, R/3 repository objects throught the entire system. Other data is client-dependent. meaning, it can be viewed from one client. Cleint-dependent data includes customizing application and user data.
Eg.
Scripts are client dependent, means the changes done to SAP scripts in particular client will not be reflected in other client.
Smartforms are client independent, means changes done in one client will be reflected in all the clients.
Server : ECC6
Client : 100 , 200 , 300 , 400
Now suppose you have developed report in DV server client 100.
Then you will be able to see that in all clients.
Hence this is called as client independent. You can change anywhere and changes will be reflected to all ...
Now suppose you have developed a script in DV client 100.
You will not be able to see that in client 200 or 300 or 400 unless ytou copy that from client since it is client dependent.

Client dependent & client independent objects

Hi All,
What is meant by client independent & client dependent ?
I know that sapscripts are client dependent while smartfiorms are client independent. Also reports & FMs are client independent.
Want to have a better idea on this concept....
Thanks in advance..
Sweta

If you create a table in 010 client in DEV server with CLNT as its first fields type, then you will find that table structure in all clients in DEV server. (i.e client independent)
example: function module, abap program, smart form.
If you create a record in that table in 010 client, you will not find that record in other clients. (i.e client dependent)
Example: script.
Sap script was developed a long back.
smartform is developed to avoid these type of some restrictions
Also:
Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients
Like SAP SCRIPTS and STD texts data
where as Client Independent means the data if you create in one client that is available in that as well as in other clients
Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..
There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!
As for SAP -- Scripts are called client dependent because if you create client in say,200 it would be available in that only.If you want to test the script in client 300 then it won't be there,you will have to go to transaction se71 in 300 .Then Utilities-> Copy from client.Give the source as 200 & form name(i.e. script name) & copy.
Few more reasons why....? Please read below:
SAPscript technology is based on a mainframe product from the 1980s.SAPscript forms have always been -- under the hood -- relatively passive objects, with minimal embedded logic. These forms were designed to be driven and controlled by ABAP programs, much in the way ABAP programs read in database tables to produce reports;
if you ever download a SAPscript form (e.g., via utility program RSTXSCRP), and look at the portable text file it produces you'll see what I mean.
Many text objects (e.g., invoice header texts) are bound directly to documents which are client-dependent, so it makes sense for these text objects to also be client-dependent. From a complexity standpoint, SAPscript forms are close enough to these text objects where I can see how it made sense at the time to make them client-dependent too.
MANDT is the field which differenciates the table from Client Dependent and Client Independent Tables.
All the Scripts are Client Dependent Objects
Smart Forms, Function Modules are Client Independent Objects.

Client copy,customer systems

The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance. what is client copy and customer systems?

2 possibilities:
client export/import: tcode SCC8 (then important transport with STMS)
remote client copy: SCC9 (after creating RFC connection through SM59)
all docs are available in help.sap.com

Client independent and dependent transport request

Hi
I have a list of transport requests, I need to find which is a client independent and which is client dependent request.
I am aware that workbench req is client independent and customizing req is client dependent.
But i think i need to look someting else also, please help
Regards

Very interesting!
As we all know that customizing requests are always client dependent, the question obviously target workbench requests.
To my knowledge tables are always cross-client, but their contents are not necessarily.
As one can put table -contents- into a workbench request as well, this one would thus be client dependent. Same applies e.g. for forms.
But E070* does not give any information about the transport contents.
E071* however states the objects included, but not if those are client dependent or not.
How are table -contents- and forms reflected in E071* ? Can I filter for those somehow?
Thanks
Christoph

Client Independent

What is the client concept in SAP? What is the meaning of client independent?

HI
http://www.sap-img.com/sap-introduction.htm
http://www.sap-img.com/general/what-is-sap--landscape.htm
Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients
Like SAP SCRIPTS and STD texts data
where as Client Independent means the data if you create in one client that is available in that as well as in other clients
Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..
There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!
As for SAP -- Scripts are called client dependent because if you create client in say,200 it would be available in that only.If you want to test the script in client 300 then it won't be there,you will have to go to transaction se71 in 300 .Then Utilities-> Copy from client.Give the source as 200 & form name(i.e. script name) & copy.
Few more reasons why....? Please read below:
SAPscript technology is based on a mainframe product from the 1980s.SAPscript forms have always been -- under the hood -- relatively passive objects, with minimal embedded logic. These forms were designed to be driven and controlled by ABAP programs, much in the way ABAP programs read in database tables to produce reports;
if you ever download a SAPscript form (e.g., via utility program RSTXSCRP), and look at the portable text file it produces you'll see what I mean.
Many text objects (e.g., invoice header texts) are bound directly to documents which are client-dependent, so it makes sense for these text objects to also be client-dependent. From a complexity standpoint, SAPscript forms are close enough to these text objects where I can see how it made sense at the time to make them client-dependent too.
In commercial, organizational, and technical terms, a self-contained unit in an SAP system with separate master records and its own set of tables.
There are different meanings.
Functionality point of View CLIENT is the highest hierarchial Orgn entity in any module
Clients again are different from each box/system like DEV,Quality and PRD.
Generally we create more clients in DEV system one for technical and other for sandbox and other for Customization etc.
This is a Mandatory field in all tables.
Each client has its own set of Application,master,data. Hence we need to populate data for each clinet separatly.(I think you cant say "implementing the SAP for the client")
Client Independant: These objects are not specific to any client. And it is universal which can be viewed,changed across the clients.
Client Dependant: These are the objects can be viewed, changed for the client for which it has been assigned. Other clients do not have access on these objects.
In SAP, all objects are finally stored as tables. "Mandt" is key field which determines whether the object is client dependant or not.
Client Independant transport requests will make the transported objects available across the clients. and Client dependent transport request make the objects available only for the client mentioned by field "Mandt"
look here:
http://help.sap.com/saphelp_nw04/helpdata/en/b7/8a9a3aaf894871e10000000a114084/frameset.htm
Client Independent(cross client) objects can be accessed from any client without transporting. For example, Reports and smartforms are client independent that means if you create a report or smartform in one client, this report and smartform can be viewed in another client without transporting.
Where as client dependent objects can be viewed or accessed only in the client in which you create them.
All scripts are client dependent and some tables are client dependent.
There are two types of objects in SAP, client dependent and client independent. Objects used in several clients are called client independent while objects used in a specific client is called client dependent. To identify if a table is client dependent, one can use tcodes SE11 or SE12. In the table field attributes, if the MANDT field is present that table is client dependent.
Almost all the programs and database objects are client independent.
Only the data in Database tables are client dependent.
Go through the below PDF file, it is having 4 pages which explains why SAP has Client independent and Client dependant..
http://www.sappoint.com/basis/clntadm.pdf#search=%22ABAP%20%2B%20client%20independent%20and%20client%20dependant%20%22
Create client????
Goto Tcode su01,
Client 810
Give user name sap*
password:06071992.
presss continue.
In the next screen :
User: Sapuser
Press creat buttom in the application tool bar ,
In address tabstrip : give ur name last name and first name ,
click on logon data: here u give the initial password, suppose password is = nihar
click on profile give : SAP_ALL
SAP_NEW
Press save buttom .
Now ur client 810 created
Goto the SAP EASY Access Screen
Give client : 810
User: sapuser
password: nihar
press enter
Again system will ask for final password.
Give here exiting password: nihar
new password: india.
check this
needed very urgently: ABAP real time questions and answers
check the below link u will find lot of info..
https://forums.sdn.sap.com/click.jspa?searchID=1815764&messageID=1967306

Client Independent & client dependent tables

Hello,
Can anyone please tell me what is client dependent and client independent tables?
Thanks in advance.
Regards
Srini

In SAP, highest level of organisation structure is client which you are entering at the time of log-in itself.
In most of the tables are client dependant where first column is client (MANDT) by default and entry in that field is complusory. so that is client dependant table.
There are few tables which are client independents, effect of any change in this table will affect all the clients. In that table client field is not there.
Whenever you making any change in value of such table, system will give you message that "this is client independance, whether you want to change it".
Hope it is clear.
Regards,
Vinod

Client independent objt

Hello again
as far as my knowledge.. tables and programs are client independent objects
so what are the client dependent objects??
can anybody plz tell me sm examples ??
i think forms , text are client dependent
plz correct me if m wring and give me sm more examples
Thanks

Hi Rashmi,
Standard Texts, SAP Scripts are client dependent objects. And as you told tables are client indpendent but the data in those tables is client dependent as we have there is a field called MANDT.
And when ever you have made changes in thes standard texts or scripts in your development client you have to transport the same to your quality and production.
Thanks and Regards,
Bharat Kumar Reddy.V
Message was edited by: Bharat Kumar Reddy Vaka

Client Independent settings

Hi Experts,
Please explain me some of client independent settings in FICO
Regards,
Vineela

Hi,
Client independent settings means when you logon to SAP you have to give some 3 digit number in client filed say 100, 200 or 800, etc. There can be many clients in one SAP system, but some are client specific(Client dependent) and some are Cross client(Client Independent).
Ex of cross client are operatin Concern, General master data of customer and vendor. There will be three tabs in Customer\Vendor Master data;
1)General Data;
2)Company Code data;
3)Purch Org\Sales Org;
Of these three data tab, general data is cross client, means available in all other clients.
Hope this answers your question.
Regards;
Haider
Assign points if useful.

What is client independent customizing....Newbie

Similar Messages

Maybe you are looking for