Difference between user directory and native directory in Shared Services

Hi,
Please any one can help me......
I am new to Hyperion, what is difference between Hyperion Shared services Native directory and User/Active directory.
thanks in advance..............

Hi,
Shared Services native directory, as the name suggests, is a user directory (i.e. ldap) that is native to Hyperion. It allows you to create users, groups and define access rights to Hyperion Products. User/Active directory is the directory where users in your company reside. Shared Services can connect to it and retrieve the list of users and groups. You can define the access rights for these users if you configure the system in a way that it works with Active Directory.
You can use both combined also. Meaning, you can create user groups in native directory and assign native directory users into them and define access rights onto user groups and/or users.
Cheers,
Alp

Similar Messages

Differences between SunONE, iPlanet and Netscape Directory Server

What are the differences between SunONE, iPlanet and Netscape Directory Server?
When I go to docs.sun.com - Products Categories, I saw that they've documentation regarding with SunONE, iPlanet, Netscape Directory Server listed under Directory Server.
I know that they're all different directory server, but is it one newer than other? If I'm not wrong, I assumed that Netscape transformed into iPlanet, and then from iPlanet, it transformed to SunONE. If that is the case, is that mean that all of it's console and how it works should be very similar?
Thanks!

That is exactly what I thought.
so when people refer SunONE Directory Server 5.1, then that's mean iPlanet Directory Server 5.1, right?
Because I'm looking at Solaris 9's specification and it mentioned that it bundled with SunONE Directory Server 5.1.
Thanks for answering my question! :)

What is difference between User Exits and BAPI

hello sap gurus
what is difference between User Exits and BAPIs

http://www.sap-img.com/abap/what-is-user-exits.htm
www.****************
Where as this customer exits are again divided into:
1. Menu Exits.
2. Field Exits.
3. Screen Exits.
4. Function module exits.
These all the things comes under Enhancements.
User exits
1.A user exit is a three character code that instructs the system to access a program during system processing.SXX: S is for standard exits that are delivered by SAP.
XX represents the 2-digit exit number.UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
2.USER EXITS are FORMS and are called by SAP standard programs
using PERFORM.
3.Inside the form (user exit) you can read and change almost
any global data from host program.
4. User exits are more flexible because you have more information to use in your code but on the other hand , it is very easy to manipulate erroneously global data and lead the standard program to a dump or even to make database inconsistent.
5.While changing User-exit,Access Key is required,
BAPI is nothing function module but which is remote enabled, means you can access this fm through other SAP or non-SAP system by assingning to business object,which we can crea in SWO1 transaction.
more details see WWW.****************
reward if helpful

What is difference between user group and reference user group?

hi
guys,
what is difference between user group and reference user group?
your regards
p.suresh

Hi ,
Chk the link below for your clarifiacation.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/5c/c1c81c445f11d189f00000e81ddfac/frameset.htm
Hope it helps.
Regards,
Amit
Edited by: Amit Kotwani on Sep 2, 2008 2:15 PM

Re: Difference between user-exits and enhancements

Hi ,
Can any one explain the difference between user-exits and enhancements with an exmpale.
I will give u full points.
thanks&regards,
Bhushan-karra.

Hi,
User exit - A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks. *-- Mani
The following document is about exits in SAP :-
The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications.
SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
Types of Exits
There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
Menu Exits
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.
When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.
Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
These calls have the following syntax:
CALL CUSTOMER-FUNCTION 001.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
Check these links for more details -
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1978b543b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://sap.niraj.tripod.com/id21.html
If this answers your question, please close the thread.
Check this link also,
https://forums.sdn.sap.com/click.jspa?searchID=5924777&messageID=3801056
Thanks,
Reward If Helpful.

Hyperion User Directory and Native Directory

Hi,
I am new to Hyperion and had a query related to User directory and Shared Services Native Directory.
Can a same native directory, for e.g., oracle database used by Shared services for provisioning be also used by Hyperion applications/products as user directory for user authentication?
Thanks

The term 'Hyperion User Directory' is not used in any standard documentation -- and here is where some folks would ask you is this an 'interview question'.
Shared services has two components it uses to store information 1. A Relational repository 2. OpenLDAP. Your question seems to assume 1 and 2 are one in the same and they are not.
The Relational Repository is used regardless of your use of Native Directory or an external directory provider such as LDAP or MS Active Directory.
You can house the Shared Services Relational Repository along with other databases on a single database server.
Please clarify what you are asking if John or my responses still have not answered your query.
Regards,
John A. Booth

Difference between USER-EXISTs and Customer-Exits???

Hi,
Can anyone give me the difference between the user-exits and customer-exits?
Please respond at the earliest. Thanks in advance.

Hi,
USER EXITS->
1. Introduction:
User exits (Function module exits) are exits developed by SAP.
The exit is implementerd as a call to a functionmodule.
The code for the function module is writeen by the developer.
You are not writing the code directly in the function module,
but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
CUSTOMER EXITS-> t-code CMOD.
As of Release 4.6A SAP provides a new enhancement technique, the Business Add-Ins.
Among others, this enhancement technique has the advantage of
being based on a multi-level system landscape (SAP, country versions, IS solutions, partner,
customer, and so on)
instead of a two-level landscape (SAP, customer) as with the customer exits.
You can create definitions and implementations of business add-ins at any level of the system landscape.
To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
Regards,
Lijo Joseph
*Reward if useful.

What is the difference between User exit and BADI

in user exit support to 4 types of exits(Menu exit,Screen exit,Field exit,Function module exit)in similar way is badi supported to all type

hi,
BADIs (Business Add-Ins) are the new way in which SAP allows you to enter additional logic into an application, and is based on OO ABAP. (Methods in Interfaces) Transactions SE18/SE19.
Customer Exits are the older method (which is still supported), whereby you create an include that is in a function module, which is called when the customer exit is activated. Transactions CMOD/SMOD.
In terms of terminology, people often use the terms "Customer Exit" and "User Exit" interchangeably, however, strictly speaking, User Exits are places provided in subroutines (notably in the SD module) where you can insert your own code, but require a modification to an include (although it is provided for customers to change).
They are two different methods to do the same thing: to check and update the data into std trx.
The user-exit is the old concept based on function module
The BADI is the new concept based on OO ABAP.
So you can often to find a BADI and an USER-EXIT to do the same thing and you have to decide what you prefer to use.
Anyway the new trx and the enjoy trx use BADIs as exit
User-exits are SAP's oldest way of updating data in standard programs - see MV45AFZZ - Form Userexit_Save_Document_Prepare.
Here you simply add ABAP code or add INCLUDES, etc
Customer-exits were SAP's next generation. They are built on the concept of function modules - where you add your custom within the Z func modules.
BADIs are SAP's newest and current way of updating data uisng Object-oriented concepts.
Please check this link.
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
Check the below links:
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/badi-vs-user-exit-405324
http://www.sapfans.com/forums/viewtopic.php?t=172792
User-Exit is a specific place in a transaction-process where SAP offers
third parties to include there own business functionality. Actually
User-Exit is the namespace used for Exits programmed by SAP specifically
for SD. For the other modules it's called Customer-Exit.=20
>Business Add-Ins (BADI) =20
The use of object orientated code within SAP has lead to new method of
enhancing standard SAP code called Business Add-Ins or BADI's for short.
Although the implementation concept is based on classes, methods and
inheritance you do not really have to understand this fully to implement
a BADI.
Difference between BADI's & User-Exit.
1. Check the replies for your question which asked by another person.
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/569786
2. Similar thread.
http://www.sapfans.com/forums/viewtopic.php?p=559472&sid=99caa729618b18a8f7c46cc2f047af52
3. Same question explained
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
Badi Tutorials
1. Sample program.
http://www.sap-img.com/abap/business-add-in-you-need-to-understand-abap-oo-interface-concept.htm
2. Implementing BADI.
http://www.sapdevelopment.co.uk/enhance/enhance_badi.htm
Hope it helps.
3. From help.sap.com
http://help.sap.com/saphelp_nw04/helpdata/en/5f/071eed117c11d5b37d0050dadef62b/frameset.htm
Pls : award points if it is useful

Difference between User Store and Persistence Storage.

I need to delete the user and and the user account from the SAP EP.
but i am facing a strange problem (for me), When i search for the user in EP, the search result
says that the user does not exist.
If i try to search for the user using UME Apis then i am able to find the user.
i could see 2 methods in UME API deleteUser and deleteUserAccount
so wanted to know the difference bwt the two and which one to use to delete the user completely for the datasource and EP
regards
Prashanth

Hi Prashanth,
If your EP is connected to LDAP.
then you need to delete your user from LDAP only.(if u have an access to LDAP)
if you try to delete from EP it still exists in UME.
try making use of deleteUserAccount.
Rgds
G.Srinivas

Behaviour differences between war file and exploded directory

Hi,
I'm baffled by differences in how my web app behaves when deploy in a war file and when deployed in exploded directory.
Firstly when I deploy in exploded directory format (using wldeploy in ant) - the jsps do not precompile. However, when I deploy the war file - again using ant and wldeploy - precompile works just fine - and general performance seems better.
Secondly - the webapp has a pdf file - which is used as a template to dynamically produce a document. When deployed
in exploded format - the webapp works fine and is able to read the pdf. However, when I deploy in war file, the pdf cannot be read.
Surely the behaviour should be the same whether we deploy as a war or exploded.
Someone please help
Tariq

Some behaviors will be different between a WAR file deployment and an exploded WAR deployment.
With respect to JSP precompile, you just say "they do not precompile", so I can't tell anything about that.
When you read files from an exploded WAR, you can reference them in two ways: as a resource, or as an absolute file path. When you read files from a WAR file, you can only read files as a resource, and not as an absolute file path. You're not giving any information about how you're reading the file, so I can't tell about that either.
You'd have to provide more detail to get better answers.

What is difference between Default VLAN and Native VLAN?

Answer

Cisco switches always have VLAN 1 as the default VLAN, which is needed for many protocol communication between switches like spanning-tree protocol for instance.
You can't change or even delete the default VLAN, it is mandatory.
The native VLAN is the only VLAN which is not tagged in a trunk, in other words, native VLAN frames are transmitted unchanged.
Per default the native VLAN is VLAN 1 but you can change that:
#show interface Fa0/8 trunk
Port        Mode             Encapsulation Status        Native vlan
Fa0/8       on               802.1q         other         1
(config-if)#switchport trunk native vlan 2
(config-if)#do show interface f0/8 trunk
Port        Mode             Encapsulation Status        Native vlan
Fa0/8       on               802.1q         other         2
The default VLAN is still VLAN 1.
#show vlan id 1
VLAN Name Status    Ports
1    default active    Fa0/8, Gi0/1
HTH
Rolf

Difference between customer exit and user exit?

hi experts
difference between customer exit and user exit?

These r the main differences between user exits and customer exits
1) user exits r subroutines where as customer exits r function modules
2) user exits r not upgraded where as customer exits r will upgrade
3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
4) customer exits r reusable where as user exits r not reusable.
Also:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
1. Previously there were only user-exits.
2. Then came the concept of customer-exits.
3. user exits were nothing but subroutines
FORM/PERFORM
called from standard programs.
4. The FORM defintion was placed inside
an empty include file.
5. So It was called EVERYTIME.
and we need to MODIFY/REPAIR the
standard include .
6. Then it came with concept of customer-exit
7. It consists of calling a FUNCTION MODULE,
which is called only if
the user-exit is ACTIVATED (other wise not called)
In this case, the code in put inside
a pre-defined Z include.
8. Functionality of both is same, howerver
we can note the following important differences
a) Customer exit is called only if activated.
(hence, it does not waste resources)
b) in customer exit, REPAIR does not happen
to the standard include.
Exits are basically the hooks whcih SAP has provided to add your own code.
User Exits: These are provided only SD module .
They are Empty subroutines with naming like USEREXIT_.
We need to have Access key to implement them.
Customer Exits: These are enhancement techniques.
There are defined in SMOD and implemented in CMOD.
Types of Customer exits: Function exit, Screen Exit, Menu exit.
User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
Customer Exit,
Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
User Exits: allow you to add additional functions to the SAP standard.
Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
reward points if found useful
regards
palak

Difference between user exists&badi's

difference between user exists&badi's

Hi, this may help you.
Check this link to learn more about differences between user-exits and badis:
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
Difference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
Ex:- 'Development server'>'Quality server'-> 'Production server'......
Reward If Helpful.
Regards Madhu.

Whats the exact differnrce between User-Exit and BADI ?

Hi All,
Can any one tell me whats the exact difference between User-Exit and BADI ?
Even in User Exit also we write our code and the same in BADI also. Can any one plse elaborate wats the exact difference between these ...
Thanks & Regards,
Anil Kumar.

BADI is the Object oriented concept of USER-EXIT
chk this
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
Message was edited by:
Chandrasekhar Jagarlamudi

Difference between target schema and target user

hi,
Can anyone explain to me what is the difference between target schema and target user? examples will be more welcome then theoratical explanation.
thanks so much

In Oracle database schema and user is the same things (if you use general authentication by database).
When used external authentication (for example with Windows domains/active directory) schema is a owner of database objects group and you should specify mapping between external usernames and schema to which this user has access when connects to database.
For example:
- windows domain user CORPDOMAIN\USER1 can connect to oracle database schema SCOTT;
- windows domain user CORPDOMAIN\USER2 can connect to oracle database schema SCOTT;
- windows domain user CORPDOMAIN\ADMIN can connect to oracle database schema SYSTEM;
Oleg
Message was edited by:
tsiboleg

Difference between user directory and native directory in Shared Services

Similar Messages

Maybe you are looking for