4. What is ODS?
It is a component of SAP System, act as a technological platform that support the entire range of SAP applications. It acts as an operating system on which SAP applications run.
SAP IDES stands for SAP Internet Demonstration and Evaluation System. This system is used to demonstrate the functionality of various SAP solutions used by important customers. This system uses data of the IDES model company.
SAP Data sets are the sets of information which are required to solve some queries which cannot be solved by using the method interfaces.
ODS is Operational Data Store. It is a component of business warehouse. It is mainly used for reporting of details.
Physical data stores:
a. Basic InfoCubes
b. Transactional InfoCubes
Virtual data stores:
a. Remote Cube
b. SAP Remote Cube
c. Virtual Info Cube with Services
Business KPIs are Key Performance Indicators. They indicate the performance of a company at strategic level. They also help in leading the company on the desired track by comparing company’s performance with the previous performances and with that of market leaders in the same sectors. SAP is building a project called “Business KPI wiki” to standardize the process of indication.
Multi Cube is a Info cube which is a collection of several Basic Cubes. Using Multi Cubes one can test the data from Basic Cubes in a single context. Multi Cubes itself doesn’t contain any data but works only on data from Basic Cubes.
Profile is what a user can do within that role that is assigned to the user. When a role is created; a profile is created based on the authorization data i.e. object class, authorization object, filed and values.
The word “profile” is used in 2 different concepts.
1) Authorization Profiles
2) System Profiles
- Authorization Profile: This profile is the one created when a role is created and is called as authorization profile.
- System Profile: This profile exists to change the parameters for the instances.
- Dialog (D)
- Update (U)
- Enqueue (E)
a. Copying or over writing to existing client called as client refresh.
b. Copying to newly created client called client copy.
Table T000 contains a list of defined clients, which you can maintain with transaction SCC4.
A support package contains fixes to the ABAP code within a SAP instance. It must be applied using the SPAM transaction in the SAP instance. A kernel replacement is the replacement of the SAP executables on the OS level.
It is a process which runs as defined by the parameter rdisp/btctime to check the scheduled background jobs and to execute them. The parameter defines the delay between two runs which means that a job start can delay at the most for that much time.
Go to ->SM51 tcode and click “Release Notes” button or click System->Status->check UNICODE values is YES or NO under SYSTEM DATA in SAP Easy Access page or execute command “disp+work-version” at command prompt
- Return code 4 –> Imported with warnings
a. Generation of program, columns or row missing.
- Return code 8 –> Imported with errors
a. Syntax error
b. Program generation error
c. Dictionary activation error or method execution error
- Return code 12 –> Indicates Import Cancelled
a. Program cancelled due to job
b. Import cancelled due to object missing
c. Import cancelled due to object not active
- Return code 18 –> Indicates Import Cancelled
a. Due to system down while import
b. Due to user expired during import
c. Due to insufficient roles or authorization
To transport users within a system(same SID) go to tcode–>SCC1 –>give source and target client –>select profile SAP_USER –> schedule in background job execution.
Note: if you want to transport from different system(SID) means we can use SCC9 or SCC8 tcode by selecting SAP_USER profile in other terms called client copy or client refresh.
OK code is used within a program to execute a function.
Tcode is “Shortcut” which helps to run a program.
1. Synchronous Transport – Dialog or batch process are blocked until import is ended
2. Asynchronous Transport –Dialog or batch process is released after import started.
Queued RFC (QRFC) : This RFC communication is an extension to the transactional RFC. In this method, all the requests are queued up(inbound queue and outbound queue) and are processed in a sequence only if it is certain that all preceding calls are processed correctly. This method guarantees that all the requests are processed in the sequence in which they are received. This type of RFCs will be used in SCM (APO) systems for CIF queues etc where requests have to be processed in an order.
There are 4 types of transport requests in SAP –
- Customizing Request
- Workbench Request
- Transport of Copies
Transactional RFC (TRFC): This type of RFC communication is similar to Synchronous RFC but by allocating a transaction id(TID) it guarantees that if a request is sent several times because of network problems it is processed only once. Unlike asynchronous RFC, in Transactional RFC the remote system does not have to be available at the moment the RFC client program start the call. The data is held in the source system until the target system is available. The report program RSARFCSE is called in the background at regular intervals and tries to place the unsuccessful requests, identified by their transaction id again.