Sapdatabase for all sap modules

sapdatabase provides you all sap modules information,latest updates

Sapdatabase for sap education

sapdatabase provides you all sap modules material,interview needs

Sapdatabase for all sap information

Sapdatabase makes you as a sap professional

Sapdatabase for outsourcing and online training

Sapdatabase provides you online training,outsource services for all sap modules in econamic fee

Sapdatabase for sap jobs

Sapdatabase makes job searching for you

Saturday, March 17, 2012

CUP Process Failure Monitoring IN SAP

We have been tasked with monitoring CUP processes for any failures caused by an infrastructure or system issue.  Typically, we could see requests fail for issues like one of the target systems (NA1 for example), is down and the provisioning request failed, or the CUP connector is down for a system, or the GRC_CPIC account was locked, or the auto-provision failed because of a lock caused by someone working on a user-id at the same time a CUP request came in for processing, thus locking out the automated request from completing (to name the most common issues).
Process Criticality
·         CRITICAL:  LOCK Account Requests
The critical processes that MUST be resolved within 24 business hours (Monday thru Friday) are userid LOCK account requests.  If we see a lock request fail, we must resolve the cause of the failure and notify Userid Administration via a Remedy ticket to manually complete the required account lock if we are unable to push the request through to completion (via REROUTE).
·         NORMAL: Create/Change account
These are not critical, but need to  be reviewed for problems that are caused by the infrastructure, so those issues can be resolved by the SAP Basis team, and try to reprocess the request to completion (via REROUTE).  In some cases you may need to manually recreate and resubmit the request referencing the original request in the reason box.
There will be some cases where the process failed for other reasons (for example, they reference a role for provisioning that is either named incorrectly in CUP or does not actually exist in the target SAP system).    In cases where it is NOT an SAP infrastructure issue, but a CUP functional administration issue, create a Remedy Priority 2 ticket for the appropriate group (Michelle Wilde, Pat Decuir or Userid Administration) as-required.
Custom Script Description:
To automate the daily checking of failed open CUP requests, a VB script has been developed to do this daily checking.  There are 2 scripts that run on irapps183:
E:\agnsapbasis\getCUPreports.vbs -  This script automates an IE session, launches CUP, logs on as j2ee_admin, runs the auditing report and captures all open CUP requests for Creations/Changes created by users, or via Web Services (IAM), and for user account LOCK requests.  This script runs Mon-Fri at 6:00am PST.
E:\agnsapbasis\generateCUPalerts.vbs - This script evaluates the open requests captured by script  looking for ones that failed to complete due to errors. It creates an email notification to the ACS SAP Basis team, detailing which CUP requests failed due to errors.  This script runs Mon-Fri at 6:30am PST

Sgen functionality in sap

 Select the task of the generation.
On the initial screen of transaction SGEN you can select the task that suits the purpose of the generation:

Generate all Objects of Selected Software Components

Choose this strategy if you want to generate the loads of all objects of certain software components. This may be the case, for example, if your system has been re installed. Here, the loads that are required for operations are not yet available and must be regenerated. After selecting this task, the Selection by Software Components of Generation Set screen appears. Here you are able to restrict the amount of objects to be generated by selecting software components. Use the push buttons to select the software components you require.

Regenerate After an SAP System Upgrade

After an upgrade, you have to regenerate the load of the ABAP objects in the system. Here, the following are required:

- The run time of the generation process in transaction SGEN must be as short as possible.
- The storage space required by the ABAP loads in the database must not be too large.
- The generation effort on the part of the user must be as small as possible.
The following generation set takes the above requirements into account. It consists of all objects with loads that were available in your system before the upgrade (that is, objects that you already used before the upgrade), and all objects that were redelivered in the release interval between start release and target release of your upgrade. The names of the objects that were generated before the upgrade were stored in the REPLISTfile in the current directory of your system during the upgrade (profile parameter DIR_HOME). After selecting this task, the Selection by Software Components of Generation Set screen appears. Here you are able to restrict the amount of objects to be generated by selecting software components. Use the pushbuttons to select the software components you require.
 Regenerate the Objects of the Last Run
This task is suitable, for example, in the following cases:
- The generation of objects of the generation set that was used in the previous run was terminated and you want to regenerate the remaining objects.
- You want to regenerate all objects of the generation set that was used in the previous run.
After selecting this task, the following two options are available to you:
- Resume
The generation set that was used in the previous run of transaction SGEN is used. Only those objects that were not generated in the previous run or whose generation was terminated due to a system error are generated.
- Regeneration
All objects of the generation set used in the previous run of transaction SGEN are generated.
Regenerate Existing Loads
This task allows you to regenerate all ABAP loads and invalidated loads that exist in your system, and to generate loads for objects of a Support Package queue. The following options are available to you:
- Generate all Objects with Existing Load
- Generate Objects with Invalidated Load Only
The load of an object is invalidated if, since the time the load was generated, activated changes were made to the object or to objects used by this object, such as includes or tables. This may occur by importing a Support Package (transaction SPAM) or a kernel patch. If you want to generate loads for objects of a Support Package queue, start the task after importing the queue. The task determines the generation set using the invalidated loads in the system. In contrast to the Generate objects of a transport request task, this task also takes into account ABAP loads that were invalidated by modified Dictionary objects.
Additional Note
You can also periodically schedule an automatic regeneration of invalidated loads (every night, or at other times when the system load is low, for example). To do this, schedule the 
RSGENINVLAS report for the relevant time and period. The report then determines the invalidated loads for every type of host in your system at the specified time, and regenerates them.
Generate Objects of a Transport Request
You can use this generation task to regenerate the ABAP load for all objects in a transport request that can be generated. This task does not, however, take ABAP loads into consideration that were invalidated by modified Dictionary objects. To include these loads, choose Regenerate Existing Loads > Generate Objects with Invalidated Load Only. After choosing this task, a screen appears that allows you to search for the name of the transport request using the selection button, or to specify it directly.
 Generation of BSP Applications
This task enables you to generate BSP applications of selected software components. Each Business Server Page is realized technically by an ABAP object class. When BSP applications are generated, these classes and their ABAP loads are generated. BSP applications are not included in the generation sets of the Generate All Objects of Selected Software Components, Regenerate After an SAP System Upgrade and Regenerate All Existing Loads tasks, since they are optional. You can use this task to deal with these. After selecting this task, the Selection by Software Components of Generation Set screen appears. Here you can restrict the amount of BSP applications to be generated by selecting software components. Use the pushbuttons to select the software components you require.
If you quit the generation of BSP applications before it has finished, or if the system terminates generation, the Regenerate the Objects of the Last Run task allows you to resume the generation.
Select the servers for parallel generation.
The generation is based on a method where the generation set is divided into small subsets that are processed by parallel processes. Depending on resources, available servers are included in the parallel processing, whereby multiple parallel processes run on one server. From the Selection of Servers for Parallel Generation screen, you can select the servers that are to be used in the parallel processing. Note that loads depend on the machine type (MT) of a host. This means that it only makes sense to parallel process the generation set of servers of the same machine type.
The default selection uses the server that you are logged on to. It corresponds to your logon server and all servers on your system that have the same machine type. If you want to use the default selection, choose Continue. If you want to exclude individual servers from the generation, or if you want to generate the load for a particular machine type that is different to that of the logon server, then use the pushbutton to select the corresponding servers and choose Continue. After you have selected the servers, the system starts to automatically define the generation set, and stores it in the database (GENSETC DB table). This can take several minutes.  

Sap Software deployment manager (SDM) functionality & deploying java support packages

This is used to deploy and undeploy the support packages, small developments that are coming with extension .sca (SAP component Archive) .sda (SAP Deployable archives), .zip, .jar (JAVA Archives), .ear (Enterprise archives), .war (Web archives) etc.
SDM is started as a process using the executable jlaunch. There will be only one SDM in the entire system.
SDM has its own directory which contains binaries, config, log and libraries.
It is started by using in the \sdm\program\config.
SDM is initialized by using remotegui.bat from \usr\sap\sol\DVEBMGS\SDM\program.
It requires SDM Server data like hostname & SDM port 50018
During initialization it will read the repository information from sdmrepository.sdc (\sdm\prog\config)
During deployment (applying the support pack) it takes backup of the repository. The major advantage of SDM is to undeploy the support packages(during conflicts) but its a disadvantage when compared with system consistency because it can undeploy the dependent packs also. SAP recommends to use JSPM from 7.0 onwards. In WEBAS 640/ NETWEAVER 640 JSPM is not available and in NW710 SDM is not available.
SDM Directory contains a document related by SDM itself (SDMKIT.JAR)
Changing the SDM Password: if SDM password is unknown we can set a new password using command line interface sdm change password.
Note: In order to change the password SDM should be running in standalone mode.
SDM can be started in standalone or in integrated mode using command
sdm jstartup sdmhome =<.....> [mode = integrated/ standalone]
Note: it is always recommended to logoff from the SDM instead of closing the window. the window is closed but the SDM Client is still connected to the server in this case we need to restart the SDM.

Deploying a support pack through SDM
1. Download the support pack from the market place.
2. Deploy (or) copy the patches into the shared folder so that (DEV, QTY, PRD) are accessed (Not mandatory to EPS) directory
3. login to SDM Tool
4. click on Deployment Tab.
5. Click add browse for .sca file  and hit next
6. patch location can be a database, file system or J2ee engine.
Depending upon the nature of the patch it updates any one of the above
Click on next and click on start deployment
Logviewer tab provides the deployment status along with the duration of the deployment.
SDM reads the files from the specified location not eps/in and it has its own inbox to process the deployment.

The patch status is obtained from system - information option in the home page

SDM startup modes are standalone/ Integrated. Default mode is integrated and standalone mode is used to change the password.

Java stack start up procedure & request flow steps

JAVA Request Flow
User submits the request
request is handled by JAVA Dispatcher
Dispatcher assigns the least loaded server process
Server process assigns application thread manager to process the request
Server process processes the requests till it is completed/ or the memory is exhausted/ timeout
ATM Handles the user request Internal process/ Intra process (For Locking)is handled by Server process.
Server process communicates with DB and the response is sent back to the user.
Central services are used for load balancing and locking purposes.(During an update)
JAVA Start up
 Use MMC
 Startsap command
 or rdisp/j2ee_start=true used to start along with ABAP Engine but consumes at least 10 Mins to 30 Mins.
Process of JAVA Start up
Database Instance
Central Services Instance
Central Instance
JAVA Dialogue Instance (Optional) 
Process Flow
1. User uses any of the above startup methods to start the JAVA Engine
2. The system is started by using startup profile
START_DVEBMGS_<Hostname> (Integrated Engine)
START_JC00_<Hostname> (Standalone JAVA Engine)
3. It also uses start_scs01_<Hostname> for starting SAP Central Services
4. It uses default profile to start the engine with minimal parameters that are required by all the Dialogue Instances.
5. It uses the instance profile to start the engine with instance specific (Memory Buffer etc)
     <SID>_SCS01_Hostname for SCS and
     <SID>_DVEBMGS00_hostname for Integrated Engine and
     <SID>_JC00_Hostname for Standalone Java Engine
6. In order to start the JAVA engine Jcontrol process is used to initialize the
7. JControl initializes the bootstrap process to read the parameters from
 8. JControl starts JLaunch process by reading
                        JLaunch         -  Dispatcher
                        JLaunch         -  server process
JAVA Engine Start up Flow

It consumes more time to start because bootstrap reads the parameters from the database to and bootstrap initializes Jlaunch for dispatcher, jlaunch for SDM and while initializing Jlaunch for server process it synchronize the binaries(All logs) of the dispatcher and the servers.

Thursday, March 15, 2012


Sapscript and smartforms
Sap script is client dependent and smart form is client independent.
Smartforms has Only 1 main window while Sap script has 99 main windows
You can not print labels using smart forms

sapscript smart forms and adobe forms
Sapscript is client dependent whereas smartform is client independent.Main window is compulsory in scripts whereas main window not compulsory in form.
Smartform output can be seen in web while in scripts it is not possible.smartform generates function module while scripts dont generate function module.

screen and subscreens in module pool.
Screen has it’s own gui status while subscreen does not have any gui status.Sub screens are part of main screen.

What is the difference between Clustered Tables and Pooled Tables?
A pooled table is used to combine several logical tables in the ABAP/4 dictionary. Pooled tables are logical tables that must be assigned to a table pool when they are defined.Cluster table are logical tables that must be assigned to a table cluster .when they are defined.Cluster table can be used to store control data they can also used to store temporary data or text such as documentation.

 user exits and customer exit.
User exit is sap defined includes so to modify it we need key from SAP.while customer exit like function exit , screen exit we don’t need any key.

standard table and hashed tables.
Standard table can be accessed by key as well as index while You can only access hashed tables by specifying the key. The system has its own hash algorithm for managing the table.

In BDC we have to take care of field mapping whereas field mapping is taken care by sap in lsmw.
BDC is mostly used for customised data upload while LSMW is used for uploading Master data.
In BDC we need to write large code but in LSMW small coding is needed.

BADI is business add ins, it is used to customize the standard business flow
BAPI is Business application programming interface. It is nothing but Remote enabled function module which can be called from outside the SAP System.

user exit and customer exit
User exit is an include program given by SAP in that you can write your code , It needs Access key from SAP while key is not required in case of customer exit

Select single and select up to one row
Select single will fetch only one record while select up to n row. Will fetch n rows from database

Normal (Classical) report and ALV report
To display the output in classical report you use WRITE Statement. To display the output in ALV we have different function modules and class like REUSE_ALV_GRID_DISPLAY , REUSE_ALV_LIST_DISPLAY and CL_SALV_TABLE.If you run the classical report in background after JOB finished you can see it’s output which stored in spool, While in case of ALV you need code
extra to store the output as it will not generate the spool.

 ALV list display and ALV grid display
You cannot retrieve the output for the report which is displayed using
ALV GRID Display.As spool Request will not be created for the same. While in case of list display Report out put will be there in spool request.

BAPI and RFC function module
BAPI is nothing but remote enabled function module
BAPI is provided as a method of business objects

sap 4.7 and ECC 6.0
SAP 4.7 is based on Web AS
ECC 6.0 is based of Netweaver 7.0.

 get cursor and hide in interactive report
Get cursor will provide the location cursor position in the report
While hide is use to pass the data from basic list to secondary list

Normal function module and RFC
You cannot call normal function module from outside the current system
while RFC function module can be called from outside the SAP system.

Subroutine and function modules.
Subroutine is local to the program while function module is global.
To call subroutine from outside its main program you need to write its main program name in the bracket

At selection screen and At selection screen output.
At selection screen output is called first
All dynamic commands and screen modification is done in AT selection screen output.

direct input and batch input
The basic difference is validation is not done in direct input by pre-defined function while in batch input it is covered.

synchronous and asynchronous in BDC
Synchronous mode will wait until the BDC session gets over while asynchronous mode will not wait for that

At selection screen and at selection on field name
At selection screen is used to validate the whole screen elements while at selection field is used to validate the particular field.When you display the error message in at selection on field the focus will
be on that particular field while in case of At selection screen the focus will not be on any particular field.

PBO and PAI event in module pool
Process Before Output and Process after input.
PBO will be called before the screen is displayed to the user while process after input is called once user interact with screen.

Stop , check and exit
If you use the STOP statement within an event block, the system stops processing the block Immediately.If you use the EXIT statement within an event block but not in a loop, the system stops Processing the block immediately If you use the CHECK <expr> statement within an event block but not within a loop, and the Condition <expr> is not fulfilled, the system exits the processing block immediately. <expr> can be any logical expression or the name of a selection table. If you specify a selection table and the contents of the corresponding table work are do.

free and refresh in internal table
You can use FREE to initialize an internal table (along with header line ) and release its memory space.
REFRESH will only initialize an internal table (along with header line)

Clear and delete.
The major difference is clear is used with internal table while delete is used with database table.

Collect and sum
COLLECT <line> INTO <itab>. The statement first checks whether the internal table contains an entry with the same key. If not,it acts like INSERT. If there is already a table entry with the same key, COLLECT does not insert new line. Instead, it adds the values from the numeric fields of the work area <line> to thevalues in the corresponding fields of the existing table entry.
SUM.Can only be used in loops through internal tables. Calculates the sums of the numeric fields in all lines of the current control level and writes the results to the corresponding fields in the work area.

call transaction and session method
Call transaction is Synchronous Processing while session (classical) method is Asynchronous Processing In call transaction we can update the database both synchronously and asynchronously. We can specify the mode in the program. While in session method it is Synchronous Database update.
In call transaction No batch input processing log is maintained while in session method details log is maintained.Call Transaction method is faster than the session method.

 At first and at last control break event
As the name suggest AT FIRST executed for the first time while AT LAST executed in last.

 Enhancement point and Enhancement Section
Both the enhancement-point and section are available for you to change standard SAP code. Difference is in fact that you use Enhancement-point to add ABAP code to standard SAP and enhancement-section to replace/extend standard SAP code.

Classical and drill down report

In classical report user cannot interact with report whereas in drill down report user can interact with report.Drill down facility is not provided in classical report while in drill down  it is provided.
If they ask you in detail then tell the interviewer that interact with the report means in drill down report we have one basic list and 20 secondary lists so we can directly go to 5th list or 10th list as per our requirement.similarly we can come back to any list. Drill down means showing data in basic list first and when we double click on any field we get summarized list. NOTE:- to go to next list in drill down report use following syntax
SY-LSIND = < list number> example: to go to 15th list SY-LSIND = 15 to come to 5th list from 15th list use F3 KEY OR PRESS BACK BUTTON

end of page and top of page
Top of page trigger when report encounter the first write, skip or new-line statements.
End of page trigger when page size is over or report display gets over.

 Table and structure
Table has physical definition into the underline database while structure does exist physically in the data base.

table and views
Table has data init while view does not contain data in it. Both exist in the data base. when u run the view it queries the database and gives the respective data.

inner joins and for all entries
Inner join joins the table at database level whereas For..All..Entries joins the table at application level.
In For..All..Entries when the condition gets satisfied data is fetched in one single shot from database table whereas in inner join data is fetched iteration by iteration It is always good programming practice to join tables at application level because if we join tables at database level then there might be performance issue

Transparent table pool table and cluster table
Transparent Table: Exists with the same structure both in the dictionary and database exactly with same data and fields. it’s to store transaction data. It’s one to one Relation table Pool tables: These are logical tables must be assigned to a table pool when they are defined. Its use to store control data. its many to one relation table Clustered tables: these also logical tables and must be assigned to table cluster when they are defined. It’s also used to store control data, temporary data or text ex. documentation. It’s also many to one relation table.

Top of page and top of page during line selection
Top of page is triggered for the basic list while top of page at line selection triggers at secondary list.

 Start_form and End_form in sap script
start_form function module is called if we want to use different forms with similar characteristics in a single spool request ,it must be closed by END_FORM function module
open dataset and close dataset
Open dataset is use to read / write file into application server while  close data set is use to close that file.

 Data element and domains
Domain gives technical details like length , decimal etc..while data elements gives description and business details

set screen and call screen
Set screen <no> set the next screen value and temporarily override the next screen value in screen attribute. While call screen <no> jump to the screen specified in <no>.

 Internal Session and External Session
External session is nothing but the window you have opened in your screen By Default you can open 6 external sessions( 6 windows = you can increase it via basis’s setting). Internal session is created when you call any Functional module or any other task in your program. counts for internal sessions are 9.

 Elementary and collective search help
An Elementary Search help defines the flow of a standard input help. It is composed of a selection method that defines where to get the data that will make up the hit list, An interface consisting of search help parameters that define the exchange of data between the screen and the selection method and a dialog type that controls how the hit list will be displayed.A Collective Search help is a combination of several elementary search helps giving the user a different search paths. The interface parameters of the elementary search help are assigned to the parameters of the collective search.

Netweaver Installation inputs & users

1. Use Installation Master
2. Select the respective Sapinst. (sapinst.exe for windows and ./sapinst on UNIX)
3. Select the installation Database (Oracle, SQL, MaxDB..)
4. Provide the following inputs
1. SID
2. Instance Number (00 to 97)
3. JCE Policy (Java Cryprography - which is used to provide secure communication over the web.
4. Master password for the users
OS                   : <SID>adm
                        : SAPService<SID>
DB                  : ORA: Sys, System, Outln,
MSS (Microsoft SQL Server): <SID>
OS (UNIX)                 : ORA<SID>
R/3 Specific application users          : SAP*, DDIC
                        R/3 DB Owners         : SAP<SID>   upto WAS640
                        : SAPSR3 for ABAP on WAS700
                        : SAPSR3DB fro JAVA on WAS700
MSS                            : <SID>
Select username from DBA_USERS;
5. Provide the path for Software dump (Kernel, Exports, JAVA Components) on UNIX we may need to abrupt the installation and install the database but on windows the database can be installed before in hand.
6. Ports
3600 - 3697     - ABAP Message Server
3900 - 3999     - JAVA Message Server
3200 - 3297     - Dispatcher port
4700 - 4797     - Dispatcher security port
3300 - 3397     - Gateway port
4800 - 4897     - Secured gateway port
50000              - JAVA instance port if instance number is 00

Say for eg if the instance number is 25 then
50000 (100 + 25)        = 52500
04 is for Administration port : 52504
Say for eg 99   - 59904 - 59916
50008              - Telnet Port
50026              - SDM Ports    (00 - Instance Number)
50001              - SSL (Https) 

Thursday, March 8, 2012

Sap Xi errors in daily monitoring

Serial Number
Error Message
Timed out while processing the message BE Messages
ABAP Dump shows that message is timed out
increase keep/alive_timeout  parameters in RZ11/RZ10
Oracle Errors with 12504,1631,1632,1653,1654,1555,255,272
Message Not Processed Successfully
open the XML Message in Sxi_monitor and check the ICON Status and look for error in the SOAP Header
Message not received into IS
Check the outbound queue of Sender(SMQ1)
Message not received in the Receiver, but processed in the IS
Check the inbound queue of Receiver(SMQ2)
File Problems in a F2F Scenario
File Corrupted, outdated, file permissions, incorrect Format or extension
Logical Routing Does not find a Receiver no_receiver_case_BE.No_receiver_case_asynch
check the receiver determination in Sxi_Cache, refresh cache or adjust the info in ID. If it is BE it cannot be restarted, if it asynch it can be restarted after changing the info in ID
Do not change info manually in the soap header.
sender service, interface, namespace doesnot match
BE(synch) Does not support too many receivers
outbound binding not found
check the receiver agrrement in ID,refresh Sxi_CACHE and restart the message
Mapping errors :message was Failed to process after mapping
1.examine Error Header 2.Check Xi Services are started in VA tool and ensure they are running 3.check Jco RFC Connections and ensure that they are started mapping program found(check in IR)
Message Stuck in status "Scheduled for Outbound processing
Check in SMQ1.if one of the message in the queue is stuck the complete transaction stucks because it is EOIO Scenario. Check the Status of the Message in SMQ1/SMQ2 example error "sysfail".it indicates that there is a problem in database,disk full
Exceede Maximum Number of ICM Connections
increase the parameter icm/min and max threads
Proxy Problems
Specify the URL in the IE http://<host>:<port>/sap/xi/engine?type=entry
Adapter Issues
Look in detail into that specific Adapter(File,IDOC,SOAP,HTTP,etc).Use the Message Display Tool with URL/mdt
HTTP to RFC Scenario Problem
Unable to get any response from the RFC
Use BE for the Quality of Service
SOAP Client Problem
Invalid Channel(Communication)
Make sure that the URL is according to the Template (http://<server>:<port>/XISOAPAdapter/MessageServlet?channel=<Party>:<Service>:<Channel>)
Unable to see the objects developed in the Reposiory or Directory, when logged in as another user
refresh the contents uaing Sxi_CACHE
Inactive Adapter
Activarte them in SICF
Objects are Locked
Release them upon approval in Administration
Unable to Import the IDOC/RFC's in IR
while importing IDOC/RFC's we need to pass Application server IP address and UserName & Password are capital letters.
RFC Connections
Trasactional RFC
Logical Systems
Model for SAP Systems
Idoc Monitoring
IDOC Ports
Q Monitor
outbound queue
inbound queue
to provide PIAPPL User
to check connectivity to LSD
to populate info to SLD
Integration Engine Configuration and Administration
Monitor Messages
Daily Monitoring Activity and Resolve the errors accordingly
Integration Engine Monitoring
BPE Trace
Display BPE Trace
to display and Refresh Cache
to launch XI Home Page
to generate Proxy
J2ee Engine
NWA Tool
visual Admin Tool
jcorfc, security provider service, log configurator, log  viewer, pmi, http, thread manager ,application thread manager, monitoring service, UME Service, SLD Data Supplier Service
Template Config Tool
Standalone Log viewer
Administration, namespace, products, SWCV,XI Domain, Technical Systems, CIM Import, export and Backup
XI Home Page
Import, export, URN, Clear SLD Cache, Update and Import SLD info
Activate the Objects
Administration, namespace, products, SWCV,XI Domain ,Technical Systems, CIM Import, export and Backup
component monitoring, message ,,E2E,Cache Monitoring, performance
IR,ID and Runtime
Exchange Profile
to save the Content of XI(hostname, user id,sid, passwords, instance numbers, ports ,it used to export and import the XI Profile)