S:NO
|
TCODE
|
DESCRIPTION
|
1
|
SE01
|
Transport
Organizer (Extended)
|
2
|
SE03
|
Transport
Organizer Tools
|
3
|
SE06
|
Set
up Transport Organizer
|
4
|
SE09,SE10
|
Transport
Organizer
|
5
|
SE11
|
ABAP
Dictionary
|
6
|
SE13
|
Technical
setting Maintenance
|
7
|
SE14
|
Utilities
for Dictionary tables
|
8
|
SE15
|
Repository
Information System
|
9
|
SE16
|
Data Browser
|
10
|
SE21
|
Package
Builder
|
11
|
SE24
|
Class
Builder
|
12
|
SE33
|
Context
Builder
|
13
|
SE36
|
Logical
Database Builder
|
14
|
SE37
|
ABAP
Function Modules
|
15
|
SE38
|
ABAP
Editor
|
16
|
SE41
|
Menu
Painter
|
17
|
SE51
|
Screen
Painter
|
18
|
SE71
|
SAP
Script Form
|
19
|
SE73
|
SAP
Script Font Maintenance
|
20
|
SE80
|
Object
Navigator
|
21
|
SE81,
SE82
|
Application
Hierarchy
|
22
|
SE91
|
Message
Maintenance
|
23
|
SE23
|
Maintain
Transaction Codes
|
24
|
SE54
|
General
Table view
|
25
|
SE84
|
Repository
Information for ABAP Data Dictionary
|
26
|
SE30
|
Runtime
Analysis
|
27
|
ST05
|
Performance
Trace, SQL Trace
|
28
|
ST01
|
System
Trace
|
29
|
SQ00
|
Start
Queries
|
30
|
SQ01
|
Maintain
Queries
|
31
|
SPOV
|
Spool
Request Overview
|
32
|
SU02
|
Maintain
Authorization Profile
|
33
|
SU3
|
Maintain
use own data
|
34
|
SW01
|
Business
Object Builder
|
35
|
SWU8
|
Work
Flow Trace
|
36
|
TUTT
|
Work
Bench Tutorial
|
37
|
TR3Q
|
Maintain
Variants
|
38
|
SM30
|
General
Table Contents Display
|
39
|
SMOD
|
SAP
Enhancement Management
|
40
|
SMWO
|
SAP
Web Repository
|
41
|
SM01
|
Lock
Transactions
|
42
|
SM02
|
System
Messages
|
43
|
SM35
|
Batch
Input Monitoring
|
44
|
SM36
|
Schedule
Background Job
|
45
|
SM37
|
Job
Selection Overview
|
46
|
SM39
|
Job
Analysis
|
47
|
SM51
|
List
of SAP Systems
|
48
|
SW01
|
Business
Object Builder
|
49
|
SWU8
|
Maintain
User Own Data
|
50
|
SCU3
|
Table
History Information
|
51
|
SH01
|
Online
Help : F1 Help Server
|
52
|
SHDB
|
Batch
Input Transaction Recorder
|
53
|
SLIN
|
ABAP
: External Programme Check
|
54
|
BD10
|
Send
Material
|
55
|
BD11
|
Get
Material
|
56
|
BD12
|
Send
Customer
|
57
|
BD13
|
Get
Customer
|
58
|
BD14
|
Send
Vendor
|
59
|
BD15
|
Get
Vendor
|
60
|
BD21
|
Select
Change Pointers
|
61
|
BD22
|
Delete
Change Pointers
|
62
|
BD41
|
Dispatch
IDocs for group
|
63
|
BD42
|
Check
IDocs for group
|
64
|
BALD
|
ALE
Development
|
Pages
Sunday, 4 May 2014
List Of Transaction Codes SAP BW/ECC
Saturday, 3 May 2014
Created InfoObject using template or reference characteristic
1. Introduction
2. Template InfoObject
3. Reference InfoObject
4. Related Content
1. Introduction
You can create an InfoObject from the scratch for your project
requirement or can create it as a reference or template of existing InfoObject.All
the technical properties like length, data type etc and master data attributes,
compounding attributes etc are copied from the existing InfoObject. Which
option you should select depends on your requirement. Below we will see how our
newly created InfoObject behaves when created using template or reference
characteristic.
2. Template InfoObject
When you are creating your InfoObject taking template of existing
InfoObject then all the master data attributes, compounding attributes and
technical properties are copied to new InfoObject. You can edit this new
InfoObject. For example, you can change the attributes, data type, length etc.
It will have its own master data table. Transformation can be created and data
load and maintain of master data is possible for this new InfoObject.
When to use: When you are going to create an
InfoObject whose most of the master data attributes and compounding attributes
are same as some existing InfoObject. It will reduce your development effort.
3. Reference InfoObject
When an info-object uses any existing info-object as the reference
it would not just have its technical properties but would use the data of the
reference characteristic. In other words, you cannot change the length, data
type, master data attributes, componding attributes etc of new characteristic
that has been created using the reference of existing InfoObject and it
will have the same master data
table (P, X, Q, Y etc) and text table.
Basic InfoObject
Reference Characteristic
Here InfoObject ZTEST_R has been created taking the reference of
InfoObject ZTEST_M. Here we can see that InfoObject ZTEST_R do not have its own
master data like /BIC/PZTEST_R, /BIC/TZTEST_R etc but its master data is same
as master data of InfoObject ZTEST_M. e.g. /BIC/PZTEST_M, /BIC/TZTEST_M etc.
Below are some important points that we should know.
Point 1. You cannot load the data into
reference characteristic
Explanation:-
Reference characteristic will have the same master data attributes and
compounding attributes, however you cannot load the data because system will
not allow you to create the transformation for this infoobject.
Point 2. When you insert this
characteristic as InfoProvider, system gives you message that it is not used as
data target.
System Message
Point 3.You cannot maintain master data
for this reference InfoObject and system will disable this option for reference
characteristic. If you insert reference characteristic as Infoprovider and try
to maintain master data, system will give you error message.
Point 4.You cannot change the master
data attributes and compounding attributes of reference characteristic.
Point 5. In reference characteristic we
only have display attributes so all the nav attributes of basic characteristic
becomes display attribute in Reference characteristic. If you are using
reference characteristic in InfoCube or in any other InfoProvider then
attributes of reference characteristic will not be available for drill-down
in reports.
Subscribe to:
Posts (Atom)