ALE client dependent or independent

Hi All,
We are using client 100 for development, 200 for config and 300 for test. If I configure ALE in 100, can I transfer data from 200 and 300 also or can i do it only from 100 and I need to configure the same in 200 and 300.
Thanks.

Hi,
ALE is a combination of RFC connections and Port and configuration..
so genrally configuration need to done on each and every systems or clients.
Prabhudas

Similar Messages

Are risks client dependent or independent in GRC 10.0?

Hi Experts!
My bosses has a question:
Are risks client dependent or independent in GRC 10.0?
Logically I would say client dependent, but they need a much official answer.
Could you please someone give this info, who has an installed system.
Thanks for your help!
Peter!

Hi if you're referring to risks generated after analysis 'YES' it's client dependent, basically you analyse risk against the user/role assignment. If you're talking about the risk for initial load I've no system to check but since they're considered as database table entries from technical standpoint, they're client dependent objects only.
Regards,
Asok Christian

Sapscript is a client dependent or independent?

sapscript is a client dependent or independent?how we can downlod sap script?plzz tell
Edited by: Alvaro Tejada Galindo on Feb 12, 2008 10:17 AM

Hi
sapscript is client dependent.
Use ABAP program: RSTXSCRP
It will download and upload your sapscripts as a text file in your local harddisk.
copy SAP Script from one client (512) to client (500).
Login to Client (512)
Goto SE38 or SA38 and execute the abap program: RSTXSCRP
Mode : EXPORT
Login to Client (500)
Goto SE38 or SA38 and execute the abap program: RSTXSCRP
Mode : IMPORT
or
Login to Client (500)
Goto SE71 - Click Utilities - Copy from client
Edited by: Jyothsna M on Feb 12, 2008 4:21 PM

XI Repository objects client dependent or independent

Hi All,
As our XI installation is specific to perticluat client
I have the following doubt.
XI repository objects are client dependent or independent.
Venu.

Hi Sravya,
Thank u very much for responding.
Here i Suggested my basis gui based on the suggestions earlier i got from this post.
I suggested the following things.
1) Install 3 instances DEV/QAV/PRD one clinet in each of the instance..
2) For the question they have raised regarding my IR/ID objects Client Dependent / Independ, I answerd both are client Independent and we can transport the objects from one instance to another.
3) here the confusion for them is if they are client independent , if we do change in ur objects that might effect in other instance objects since they are client independent. I told them unless we transport the objects from one instance to other there would not be any problem.
Please confirm my answer. and suggest.
Thanks,
venu.

List of client dependant and independent

Hi All,
Can any one let me knw the list of objects which are client dependent and which are not.
Thanks,
Vibha

Hello Vibha
The following list shows the client-dependent repository objects:
LIMU     FSEL     Field Selection
LIMU     VARI     Report Program System Variant
R3TR     COC1     CO: Cost Centers
R3TR     COC2     CO: Activity Types
R3TR     FORM     SAPscript form
R3TR     LODS     HRDSYS: Logical information object client-dep. table E SYST
R3TR     PCYS     HR: Transport standard personnel calculation rules
R3TR     PHDS     HRDSYS: physical information object client-dep. table E SYST
R3TR     SBNL     Logical Information Object for BDS
R3TR     SBNP     Logical Information Object for BDS
R3TR     SBNR     BDS: Relationship Between Information Objects
R3TR     SBPL     Logical Information Object for BDS: Bid Invitation
R3TR     SBPP     Physical Information Object for BDS
R3TR     SBPR     BDS: Relationship Between Information Objects
R3TR     SBRL     Logical Information Object for BDS
R3TR     SBRP     Physical Information Object
R3TR     SBRR     BDS: Relationship Between Information Objects
R3TR     SBSL     Logical Information Object for BDS
R3TR     SBSP     Physical Information Object
R3TR     SBSR     BDS: Relationship Between Information Objects
R3TR     SBTL     Logical Information Object for BDS
R3TR     SBTP     Physical Information Object
R3TR     SBTR     BDS: Relationship Between Information Objects
R3TR     SBWL     Logical information object for BDS
R3TR     SBWP     Logical information object for BDS
R3TR     SBWR     BDS: Relationship between information objects
R3TR     SRHL     SRM: Hierarchical Lists
R3TR     SRLD     Language-Dependent Client-Specific Retrieval Index Objekt
R3TR     STYL     SAPscript Style
In contrast to client-independent repository objects which can be imported into any client these objects must be transported into their specific target client.
Regards
Uwe

Hi abapers doubt in client dependent and independent

i am having a doubt could you please explain me
i created a dependent table using mandt in client 100(development).
if transfered this table to quality 110(quality). it is possible access data?
when i see development 100 it's having data but i can't find any records in quality it's not showing the records.
how we can see data in quality110 , if table is dependent.

Hi Sayeed,
Data in the table will only we transported accross a system landscape if you have marked the recording routine in your development system.
Regards,
John.

Client independant and client dependant

can anybody explain me what exaclty is clientdependant and independant..also cross client means?
thanks and regards
vijaya

Hi Durga,
    As the name says
    Client - for example assume there is company called
             "sony". It can have many plants across the
             countires. Sony divides these plants into
             different groups based on functionality.
             These groups are called client.
    Mostly which ever the object that is developed in the SAP will developed in a way that is usefull across users.
    But there will some sepcific needs for users/clients of SAP like language barriers....units..currecies....etc...etc. Which will be not same for all.
    Client dependent - if object is prepared taking
                       into consideration of above
                       example barriers it is dependent
                       ELSE.
                       It is client indpendent.
   Client dependent or independent can be know for the filed sy-mandt. and also in SE09

Client dependant/independant

Hello All,
Can anybody please tell me, Configuration and Desing in Integration Builder is client dependant or independant?
Thanks.

Hi Kinnari,
I complety mistook ur question. IR and ID are based on Java Stack.
lets say you are doing Xi development on XI Client 10. Add you want to access interface definitions in Client 20 on the same machine. then you can. all the clients on the same machine will have access to every thing. say if you go to tcode: sproxy in client 20 , you can see all the interfaces defined in client 10.
so for testing you dont have to transport anything between clients.
Naveen

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

Use of client dependent tables

Hi Gurus,
I have read many threads on difference between client dependent and independent data/objects etc.
But, someone tell me please, wheat exactly the 'Use or Advantage' of client dependent tables/data.
Thanks in advance.
V

HI,
The use of client dependent tables is that if data in one table of a particular client is updated then that data wont be seen in any other clent it provides a security to the data we retrict users with their authorizations in differen clients
When you log on to an SAP System, you log on to a particular client of this system. Any activities you carry out in the system are always carried out in one client. When you plan your SAP system landscape, you must consider which clients you need for which activities.
By assigning activities to be performed in a client, you give each client a particular role. This section describes the most important client roles.
Since you need to adapt the SAP software for your own business needs, each SAP system landscape requires a client where Customizing settings, and possibly ABAP Workbench developments, can be made. This client is known as the Customizing and development client, or Customizing client for short. The abbreviation CUST is used for this client.
Before you can use the Customizing settings and Workbench developments productively, you need to test them extensively for errors. Any faulty settings can seriously disrupt productive operations, and at worst, lead to the loss of productive data. The integrated nature of the various SAP applications means that there are many dependencies between the different Customizing settings. Even an experienced Customizing developer may not discover these dependencies immediately. The correctness of the settings can only be guaranteed with extensive testing. The client where these tests are made is the Quality Assurance Client, QTST for short.
A separate client is required for productive use of the SAP System. So that this client can be used without disruption, it is essential that no Customizing settings or Workbench developments are made here, and also that no tests are carried out. This client is known as the Production Client, PROD for short.
These three clients, CUST, QTST and PROD, are the central clients that exist in every system landscape. Standard system landscapes have precisely one client for each of these client roles.
We recommend that you make all your Customizing settings in a single Customizing client, and then use the CTS to transport them to the other clients.
We also recommend that you do not make any Customizing settings or Workbench developments in the quality assurance or production clients. You can make sure of this by making appropriate client settings.
In addition to the central clients, you can also set up other clients for other tasks. However, you must remember that each extra client takes up additional system resources (main memory and database space). They also need to be administrated. For example, you need to set up and administrate access authorization for the users, and also distribute any changes to other clients with the CTS. You must weigh up the advantages and disadvantages of setting up other clients.
Examples of other client roles are:
Development test client (TEST): Developers can use this client to test their Customizing settings and Workbench developments, before they release their change requests. In this client the developers can create test application data for realistic tests. If they discover errors, they can remove them in the Customizing client. A development test client is always set up in the same SAP System as the Customizing client. This means that any changes that are made to cross-client data in the Customizing client are also immediately visible in the development test client. Changes to client-specific data are copied from the Customizing client to the development test client using a special client copy function. The client copy function uses the unreleased change requests from the Customizing client to do this. The development test client is set so that you cannot make changes to Customizing data and Repository objects.
Prototype or sandbox client (SAND): You can use this client to test any client-specific Customizing settings if you are not sure whether you want to use them in this form. Any settings that you want to keep are then entered in the Customizing client. To prevent conflicts between the prototype client settings and real settings in the Customizing client, you cannot make changes to cross-client Customizing data and Repository objects in the prototype client. The CTS does not record changes made to client-specific Customizing data, and does not transport them from the prototype client. You can make sure of this by making appropriate client settings.
Training client (TRNG): To prepare end users for new functions that are to be transported into the production client, you can set up a training client. The users can use the new functions in this client with specially created application data. This client is set so that you cannot make changes to Customizing data and Repository objects.'''
plzz reward if this information is usefull to u plaa dont forget to reward

Urgent:Why Script is cliend dependant and smartform is not client dependant

Hi all,
Can any one pls tell me why script is client dependent and smartform is not client dependant.
<b>Please give some real time examples in brief</b>
regards
tapu

Hi
DIFFERENCE BETWEEN SMARTFORMS AND SAPSCRIPTS ARE:
1. script is client dependent one while smartform is client independent.
2. In scripts we have to write print program while in smart forms it is not necessary.
3. In scripts we can print background logo while in smartforms we cant print background logo
4. In scripts we have 99 main windows while in smartforms we have only 1 main window.
5. In scripts we should write paragraph format otherwise we cant execute program while in smartforms no need to create paragraph formats .
6. In scripts we can print the text in only two character formats.
while in smartforms we can do with more.
7. In scripts we dont have line types while in smartforms we have linetypes.
8.Multiple page formats are possible in smartforms which is not the case in SAPScripts
9.It is possible to have a smartform without a main window .
10.Labels cannot be created in smartforms.
11.Routines can be written in smartforms tool.
12.Smartforms generates a function module when activated.
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. Client dependence is a fundamental one. Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively ...
also refer
difference between smartforms and scripts
Diff betwen Scripts & smartforms
advantages of smartforms over scripts
Whenever a smartform is created, a funciton module gets generated. So, we can access the smartform in different clients. But in case of scripts, it is not so.. So, scripts are client dependent.
Smart Forms are implemented using the Function Module SSF*, and all the logic lies in the FM. Function Modules are client independent objects, so Smart forms are also client independent
SAP Scripts are the Layout Forms that you design and there are aviable in the client in which you have created them, for making them available you have to copy across the clients.
Because, Sapscripts are saved in ITF format as text in client dependant tables STXH and STXL. smartforms are not saved in client dependant tables and visible across clients.
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.
I suspect 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).
<b>Reward points for useful Answers</b>
Regards
Anji

Differentiating Between Dependent and Independent Data

HI,
How can I make a differentiation between dependent and independent data?

HI,
If you double click a Transfer requirement in SE10 or SE09 and then press F4 in the field category, you will find some helpful information.
Client dependent or independent transfer requirements include client specific or cross client objects in the change requests. Workbench objects like SAPscripts are client specific, some entries in customizing are client independent.
If you display the object list for one change request, and then for each object the object attributes, you will find the flag client specific.
If one object in the task list has this flag on, then that transport will be client dependent.
You can also find a list of the high class objects in SAP, here you will see the flag on/off. Use TCODE SOBJ.
Start STMS and double click on the request itself, you will see which type of request it is (Workbench -> client independent or Customizing -> client dependent).
I recommend you to import every request on each client without looking inside the request.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Why the sapscript called as client dependent? y smartform not?

why the sapscript called as client dependent? y smartform not?

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).
Thanks,
Santosh

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.

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

ALE client dependent or independent

Similar Messages

Maybe you are looking for