Useful T-Codes and Programs related

IDOC processing and IDOC Development

Useful T-codes for IDOC's in SAP.
T-Code Purpose
Display
WE02 IDOC Display
WE05 IDOC Display
Administration
WE20 Partner Profile
WE21 Define Port
Sm59 Maintain RFC Destination
WE46 IDOC Administration
IDOC Testing
WE19 Test IDOC
WE15 Outbound from MC
WE14 Outbound processing from IDOC
WE18 Generate Status File
We17 Process Status File
WE12 Inbound procg of modified outb.file
WE16 Inbound procg of orig.inb.file
Documentation
WE60 IDOC Types
WE64 Process Codes
IDOC Development
WE30 IDOC Types
WE31 IDOC Segments
WE81 Messages Types
WE82 IDOC Types
WE41 Outbound Process Code
WE42 Inbound Process Code
Status
WE47 Status Values Maintain
WELI Maintain Status Groups
WE43 Display Status Record
Useful Programs for IDOC
PROGRAM PURPOSE
RBDMANI2 Manual IDOC Reprocessing
RBDMANIN Posting IDOC with Status 51
PROGRAM PURPOSE
RBDMOIND Process outbound IDOC's with status 03-12
RSEOUT00 Process IDOC's with Status 30
RBDAPP01 Process IDOC's with Status 64
RBDAGAIN Process incorrect outbound IDOC's
RBDAGAI2 IDOC Reprocess After ALE input error
Notepad
 SAP HANA MODELLING Interview
Questions and Answers
Question.1 Which non-SAP system can SAP HANA connect?
Answer: Oracle Enterprise, IBM Informix.
Question.2 What are the Views available in the Quick launch of Information modeler?
Answer: Navigator, Where-used list, Job log, Properties.

Question.3 For what Life cycle management perspective is used?

Answer: We use Life cycle management perspective to Upgrade/Updates for HANA
studio.
Question.4 OPD for data replication API is used in which replication?
Answer: Data services 4.0.
Question.5 How can you ensure that data is consistent in source system and HANA system?
Answer: Since any changes in the source system are tracked in dedicated logging tables,
the replication status for each changed data record is transparent. An entry of logging
table is deleted after a successful commit statement from HANA database and this
procedure ensures the data consistency between a source system and HANA system.
Question.6 Which section controls the data processing in the HANA DB?
Answer: Transaction Manager controls the data processing in the HANA DB.
Question.7 What is the component present in Persistence layer in the HANA DB?
Answer: The component present in Persistence layer in the HANA DB is Page
management & Logger.
Question.8 What are the types of joins are possible in Attribute view?
Answer:
 Referential join
 Inner join
 Outer join
Question.9 What is the role of Persistence Layer?
Answer: It ensures that the database is restored to the most recent committed state after
a restart and that transactions are either completely executed or completely undone. The
persistence layer offers interfaces for writing and reading data. It also contains SAP HANA
‘s logger that manages the transaction lo. Log entries can be written implicitly by the
persistence layer when data is written via the persistence interface or explicitly by using a
log interface.
Question.10 What does HANA DB performs During power outage?
Answer: Recovers log between last data savepoint & time of failure.

Question.11 What is the Operating System of IMDB ?

Answer: SUSE Linux Enterprise Server
Question.12 Which is the default perspective of IMCE Studio?
Answer: Administrator console
Question.13 Name the editions of SAP HANA Software?
Answer:
 Platform edition
 Enterprise edition
 Enterprise extended edition.
Question.14 What are the benefits of implementing SAP HANA with SAP ERP?
Answer:
 Performance optimization for operational reporting
 Processing of large volumes of data
 Provision of real-time analytics.
Question.15 Do we need a special driver to access data within HANA?
Answer: HANA provides both a 32-bit and 64-bit ODBC and JDBC drivers. SAP
BusinessObjects 4.0, Data Services 4.0 and many other SAP based tools have built-in
support for these drivers to help support all the features HANA has to offer.
Question.16 How can we load data in HANA and how to access the data stored in HANA?
Answer:
Loading data: There are several options available to get data into HANA. SAP provides
a real-time replication server called SLT Replication. With this server you can replicate
data from a SAP system or non-SAP RDMS systems into HANA. The data is copied in its
native format and will then need to be de-normalized on HANA using information views (
attribute views, analytic views and calculation views). According to the documentation,
you can also leverage the Sybase Replication Server for log based replication. In addition,
Data Services 4.0 can be used to move data into HANA and can update data at near real
time if needed. Data Services 4.0 can also de-normalize the data given its abundance of
data transforms and provide data quality and cleansing transforms that will help clean the
data before it is loaded into HANA.
Access the data: There are several ways to access the data within HANA. The ideal way
to access data is through SAP BusinessObjects 4.0. There are multiple tools within the
BusinessObjects 4.0 platform for accessing HANA data. You can utilize Web Intelligence,
Crystal Reports, Explorer, “Analysis Edition for Microsoft Office”, Mobile and Dashboard
(Xcelsius). In short, any tool in the platform that supports ODBC or a Universe can be
utilized to access data within HANA. These options work for SAP BW (powered by HANA)
or for HANA (Standalone). If you have SAP BW powered by HANA, you can utilize any of
the traditional query tools. For those that like viewing raw data results, you can utilize
HANA Studios to execute SQL statements and view the results.
Question.17 Why we need to go for going In-memory?
Answer: One reason is the number of CPU cycles per second is increasing and the cost
of processors is decreasing. For managing the data in memory, there is five-minute rule
which is based on the suggestion that it costs more to wait for the data to be fetched from
disk than it costs to keep data in memory so it depends on how often you fetch the data.
For example, there is a table and no matter how large it is and this table is touched by a
query at least once every 55 minutes, it is less expensive (in hardware costs) to keep it in
memory than to read it from memory and if it is frequently accessed it is less expensive to
store it in memory.

Question.18 What are the advantages of Column based tables and Row-based tables?
Answer:
Advantages of Column based tables:
 Calculations are typically executed on single or a few columns only.
 The table is searched based on values of a few columns.
 The table has a large number of columns.
 The table has a large number of rows and columnar operations are required (aggregate, scan, etc.).
 High compression rates can be achieved because the majority of the columns contain only a few distinct
values (compared to a number of rows).
Advantages of Row-based tables:
 The application needs to only process a single record at one time (many selects and/or updates of single
records).
 The application typically needs to access a complete record (or row).
 The columns contain mainly distinct values so that the compression rate would be low.
 Neither aggregations nor fast searching is required.
 The table has a small number of rows (e. g. configuration tables).
Question.19 What is Derived Attribute Views?
Answer: In some business cases, it is required to use the same attribute view more than
once
In such cases, one can derive an attribute view using the base view which acts as
reference to the base attribute view. The derived attribute view will be opened in the read-
only mode. The only editable field will be its description. The derived attribute view will act
as a reference to its base attribute view.