SAP R/3 Tips & Tricks

Logging on without being authorized

Client 066 usually exists in a SAP system due to EarlyWatch services. Often this client does not have
master users. If it is true, anyone can log into the system using the client 066, user SAP*, and password
PASS. Enjoy yourself.

Special copy and paste

Click on the area and press CTRL+Y. It allows you to copy many lines at once and paste them
afterwards.

Long messages on footer

Click on the message and hold the mouse button. After moving the mouse to the left side.

Direct input logs

The transaction BMV0 (direct input logs) shows all direct input logs.

Graphics on SAPscript
The program RSTXLDMC can be used to upload graphics (file extension .tif on PC files) into
individual standard text.

Adding icons
Check the icon code using transaction ICON. A technical view can be found at the include named
ICON. Sequences of characters begin and finish with the symbol @. Even plain files under
operating system can contain those strings.

Filling up an empty date field quickly

Strike the key F4 (or click on matchcode symbol) and press ESCAPE. The current date is
automaticly set.

Setting up module FI/CO without using IMG

Almost all parameters can be set using the transactions ORFA (Asset Accounting), ORFB
(Financial Accounting), and ORKS (Cost Center Accounting).

Displaying check object when not authorized

Soon after the lock try to access the transaction SU53. It reports the last objects verified and also
the respective values.

Table analyses between two systems

The contents of a table between two systems can be checked through the transaction OY19.

Correction and transport system

The transaction SE10 provides the easiest way to manage any request/transport and corrections.

General command field formats

/n
/bend
/nend
/nxxxx
/o
/oxxxx
/i
/h
/$tab
/$sync

Skip to the next record if you are processing one batch input session
Cancel a batch input foreground process
Close all R/3 sessions and logoff
Call the transaction xxxx in the same session
Generate a session list
Call the transaction xxxx in an additional session
Delete the current session
Turn the debug mode on
Reset all buffers (for System Administrators)
Synchronize instances buffers (for System Administrators)

Report command field formats

%pri
%pc
%sc
p+
pp++
p--

Print the current report

Download the current report
Call the find function
Go to the next page
Go to the previous page
Go to the last page
Go to the first page

Helpful reports
RSCLTCOP
RSAVGL00
RSINCL00
RSBDCSUB
RSTXSCRP
RSORAREL
RGUGBR00
RSPARAM
RSUSR003
RSUSR006

Copy tables across clients

Table adjustment across clients
Extended program list
Release batch-input sessions automaticly
Transport SAPscript files across systems
Get the Oracle Release
Substitution/Validation utility
Display all instance parameters
Check the passwords of users SAP* and DDIC in all clients
List users last login

Unconditional mode when importing or exporting a request/transport

Run the command R3trans -u under user SysIDadm.

Main return codes of tp program

0
4
8
12
16

Successfully done
Warnings occurred
Errors occurred
Fatal errors occurred
Internal errors occurred

Scheduling of system maintenance jobs

RSBTCDEL
RSDBCREO
RSPO0041
RSSNAPDL

Clean the old background job records

Clean batch input session log
Removing old spooling objects
Clean the old ABAP error dumps

Locking the whole system

Using the command tp locksys SysID only the user SAP* will be allowed to login. The
command tp unlocksys SysID cancels the lock.

Connection between SAP R/3 and operating system

The command sapevt can be used to trigger an event from the operation system. Thus, a job
previously defined within R/3 will be released.

SQL code help

Run the command oerr ora error number under user oraSysID.

Oracle import and export explanations

Run the command imp help=yes under user oraSysID. This format can also be used with exp,
impst, and expst.

SAP R/3 Hints

TOP

Of course it does not guarantee a successful implementation. It is a great deal of summed up aid, though.

Team integration has to be enhanced

Set high standards of performance for implementation team

IT teams and users have to work closely during the implementation

New ways of thinking and acting must not be discarded

Do not underestimate the user training needs

Project management should be on the critical list

The nearest SAP branch should be your partner

Consultants are not always the key to succeed

Consultants are a good source of knowledge. On the other hand, letting them make configuration
changes the transfer of knowledge will be harmed

Foreign consultants usually do not know country-specific details

Deepening your basis knowledge is always useful

Avoid changing standard R/3 objects as much as possible

Always follow the SAP rules to give names to your own objects

Establish SAP connection as soon as possible

Exchange information with other companies

Focus on interfaces with non-R/3 applications

Plan the whole environment carefully (servers, network, protocols, etc.)

Development and production environment should be totally independent

SAP R/3 Enhancements

TOP

Some special features allow you wide modifications without changing standard SAP R/3 objects. Those
techniques are not as widespread as they should be. In fact they are powerful tools.

Field exit
After entering a value in a field, it can be checked through a field exit. The system makes the
field value available to be checked and changed in an ABAP/4 function.

User exit
Points previously set in the system that let you evaluate data. The fields available are also
previously defined by SAP. All fields value available can be checked in an ABAP/4 program.

Validation
It allows solid data entry regarding special rules. According to previous rules, the system can
evaluate an entry and a message can appear on the user's terminal if a check statement is not met.
A validation step contains prerequisite statement and check statement. Both of them are defined
using Boolean Logic or calling an ABAP/4 form.

Substitution
Fields contents can be changed using substitution. When data are being entered, the data can be
substituted by another value regarding rules previously defined. A substitution step contains
prerequisite statement, substitution value and substitution exit. All of them are defined using
Boolean Logic or calling an ABAP/4 form.

Set
Values or ranges of values are specified under a set name. Sets are easier to create and maintain
instead of using tables. They give you more flexibility when maintaining your system.

Key words
It allows changes on field description according to data element. The short key word used on
most screen to identify the corresponding field contents can be changed too.

Requirements & formulas

ABAP/4 forms that can be used to handle pricing procedures, rounding rules, copy and data
transport Sales activities.

SAP R/3 Troubleshooting

TOP

System gets stuck

It happens mostly when archive area is overloaded. Run the program brarchive with deletion
option to release disk space.

Short dump
Not always the problem is technical. Try to create all SAPoffice users through transaction SO32
(create all SAPoffice users) and review your application data carefully.

Field exits are completely ignored

Make sure your SAP profile parameter contains the option abap/fieldexit = yes.

Transaction SE16 (table contents) does not work properly

Make usage of the menu option to regenerate the display program. You can also try changing key
words according to field names. Choose Option -> Parameters users.

Rollback segments are too small

Before increasing up the rollback segment size you should verify your programs. Very often the
problem belongs to them.

Files for rollback segments are already enormous

Check the rollback segments configuration. It has to match the allocated area on tablespaces.
Changes have to be done using Oracle tools.

Extended help under windows does not link correctly

Check the file sapdoccd.ini under your presentation server. It must be present in the main
windows directory and should assign to help files directory.

Release procedure with classification does not work

As a matter of fact you are not the only one to notice it. It hardly works. Before using release
strategy you should apply all notes on OSS. Pray might be useful too.

Transport area is overloaded

The command tp clearold SysID cleans up the transport area according to parameters
previously set on the plain file TPPARAM.

Instance does not establish communication

Shutdown the whole system and check the Interprocess Communication Facilities. Any
references should be found. Either the command IPCS (UNIX) or showipc INSTANCE
NUMBER (SAP) show all message queue, semaphore set and shared memory identifier. Before
trying again you have to remove them using the command IPCRM (UNIX) or cleanipc
INSTANCE NUMBER (SAP).

Note: Research based on version 3.0f under Unix, Oracle data base and Windows.

SAP R/3 Security

TOP

Simple changes can rise your system security. Usage of SAProuter is a good choice when correctly
implemented. Login through SAP LogonPad (from version 3.0f onwards) improve the access control.
SAP profile parameters shall also contain:

Rdisp/gui_auto_logout = 1800
The user connection is closed after 30 minutes without usage.

Login/fails_to_session_end = 3
After 3 wrong password the connection is automaticly closed.

Login/fails_to_users_lock = 5
After 5 wrong password the user is locked.

Login/min_password_lng = 6
Password length at least 6 characters.

Login/password_expiration_time = 90
Password expires after 3 months.

Note: I do not have to waste my time telling you to change all default passwords.
Make sure to have the master user SAP* in all clients otherwise anyone can log into
your system. See Tips & Tricks.

SAP R/3 Programming

TOP

Indeed these powerful ABAP/4 functions are very interesting and can bring some advantages. Improve
your home development easily. They belong to standard objects and should never be changed.

Ws_upload
Transfer files from the frontend to the application server.

Ws_download
Transfer files from the application server to the frontend.

Ws_excel
Download files at the frontend in excel format.

Bp_joblog_read
Fetch job log executions.

Rs_send_mail_for_spoollist
Send message from ABAP/4 program to SAPoffice.

Bp_event_raise
Trigger an event from ABAP/4 program.

So_wind_spool_list
Browse printer spool numbers according to user informed.

So_spool_read
Fetch printer spool according to the spool number informed.

G_set_get_all_values
Fetch values from a set.

Rzl_sleep
Hang the current application from 1 to 5 seconds.

Rzl_submit
Submit a remote report.

Ws_execute
Execute an external program on the presentation server.

Ws_file_delete
Delete file at the frontend.

Ws_volume_get
Get the label from a frontend device.

Ws_msg
Create a dialog box in which you display an one-line message.

Popup_to_display_text
Create a dialog box in which you display a two-line message.

Popup_to_confirm_step
Create a dialog box in which you make a question whether the user wishes to perform the step.

Popup_to_confirm_with_message
Create a dialog box in which you inform the user about a specific decision point during an action.

Popup_to_confirm_with_value
Create a dialog box in which you make a question whether the user wishes to perform a
processing step with a particular object.

Popup_to_confirm_loss_of_data
Create a dialog box in which you make a question whether the user wishes to perform a
processing step with loss of data.

Popup_to_decide
Create a dialog box in which you require the user between the two processing alternatives, or to
cancel the action.

Popup_to_decide_with_message
Create a dialog box in which you inform the user about a specific decision point via a diagnosis
text.

Note: These functions have been used and have worked as well as they were supposed to
do.

SAP R/3 Glossary

TOP

Information Technology has many key words and SAP R/3 has introduced many others. In order to
understand even better this field you should keep in mind those terms.

ALE (Application Link Enabling)

It provides integration for separate R/3 systems, keeping full interaction. This makes possible
distributed enterprise applications.

Application server
The application server is used to run the business application programs in the R/3 client/server
concept. The application modules are loaded from the data base server to the application server as
required. Thus the application server requires only storage capacity to accommodate UNIX,
Swapping and the SAP runtime environment.

Batch Input
A technique to input data safely. It ensures application data integrity for background interfaces. It
pretends to be someone typing. See also direct input.

CATT (Computer Aided Test Tool)

It allows you to combine and automate sequences of repeatable transactions in test procedures.
CATT reduces the number of manual tests, and forces you to test systematically, defining input
values and expected test results.

CCMS (Computer Center Management System)

It allows you to monitor, control and configure your R/3 system. This toolset lets you analyze and
distribute client workloads and report on resource consumption for system components.

Central System
In an R/3 central system, both application and data base software are run on one computer.

Client
In commercial, organizational and technical terms, a self-contained unit in an R/3 system with
separate master records and its owns set of tables.

Client/Server System
Client/server systems are structured modularly, with components working in a sender/receiver
relationship. Software components can also be used in a client/server relationship.

Communication Server
It provides the connection between local area and wide area networks and may be either a router,
a bridge or a gateway. In R/3 installations, the communication server must support the TCP/IP
protocol over wide area networks.

Company code
The smallest organizational unit for which a complete self-contained set of accounts can be drawn
up for purposes of external reporting. This involves recording all relevant transactions and
generating all supporting documents for legally-required financial statements, such as balance
sheets and profit and loss statements.

Computer type
The R/3 system supports various computer types of SAP's platform partners, such as Bull, DEC,
IBM and HP. The suitability of a particular computer type depends on sufficient CPU
performance.

CPI-C (Common Programming Interface-Communications)

Common Programming Interface of Communication has been introduced by IBM as a high-level
interface to SNA/LU6-2. CPI-C has become the subject of the X/Open stardarlization and is used
by SAP to facilitate program-to-program communication between R/3 and external system. SAP
offers CPI-C libraries based on TCP/IP.

Correction
It contains all the objects that a developer has changed or created. It also controls customizing
that has been maintained.

CSP
A system to help SAP employees to give comprehensive support to their clients.

Data base server

The data base server stores the SAP application programs and data in the R/3 client/server
concept. It also handles the SAP update program and batch jobs.

Direct Input
A recent technique to input data safely. It ensures application data integrity for background
interfaces. See also batch input.

Dispatcher
The system R/3 agent that identifies the type of task (on-line, update, batch, etc.) and sends the
job to an idle work process.

EarlyWatch
It is a service that entails having your R/3 installation regularly inspected by SAP employees, in
other to ensure high system availability and high data throughput at all time.

Ethernet
It is a LAN architecture using bus topology. The transmission speed is 10 MBit/s.

FDDI (Fiber Distributed Data Interchange)

It is a local high-speed network with ring topology based on light wave conductors. The
transmission speed is 100 MBit/s.

Field status
Indicator that specifies whether a field can take an entry in the entry screen or if it must be filled.

Firewall
It is a means of controlling access through a public network to a private network.

FTP (File Transfer Protocol)

It is the most commonly used file transmission protocol of the TCP/IP protocol family.

GUI (Graphic User Interface)

A graphical interface used by SAP environment as part of the three tiers. It is normally called user
frontend.

IDES (International Demonstration and Education System)

It is a model of an international firm. It is a separate demonstration and education system for
speeding up the pilot process.

IMG (Implementation Management Guide)

It is a hierarchical structure that reflects the R/3 component hierarchy and contains every
configuration activity. Released from version 3.0 onwards.

Instance
It means application server and each one has its own set of work processes.

IDoc (Intermediate Document)

An IDoc is a data container for data exchange between SAP systems or between an SAP system
and an external system.

ITS (Internet Transaction Server)

It links the R/3 application server with one or more Web servers, thus enabling the R/3 to
communicate with the Internet.

Kernel
It means a standard core previously configured. A set of default parameters delivered with the
system.

LAN (Local Area Network)

It is a network foa a tightly limited area with high level data transmission performance. Common
LANs include Ethernet, Token Ring and FDDI. These LANs support different transport protocols,
such as TCP/IP and IPX.

Matchcode
A tool for finding specific record. It is made up of search terms. It is used to find possible entries
for an input field.

Number range
A range of numbers that are laid down per file for the assignment of document numbers. It can be
internal (carried out automatically by the system) or external (carried out manually by the user).

OLE
It is a technique introduced by Microsoft to incorporate objects of one application into another.

OSS (Online Service System)

SAP's Online Service System offers fast and effective help for R/3 System problems. It is also the
basic element of communications between customers, partners, and SAP.

Repair
It contains all the objects that a developer has changed but the originals of the objects are located
in another system.

RFC
A way to implement communication between application programs via Abap/4 function call.

Semaphores
When a work process locks a resource, it sets a semaphore. Another work process that also wants
to access it must then wait.

SysID
A set of three letters or number that identify a system. Some sets are not allowed because they are
used by SAP. They are informed when the system is installed.

TCP/IP
It is the most widely used transport protocol for open systems. R/3 clients and servers
communicate using TCP/IP.

Telnet
It provides terminal access to hosts using TCP/IP protocol. It is a well-known command among
Systems Administrators.

Token Ring
It is a LAN architecture with ring topology. The transmission speed is 4 MBit/s or 16 MBit/s.
This involves a 'free token' which circles the loop picking up transmissions. The receiver station
places a confirmation bit into the busy token. As soon as the busy token reaches the sender station
again, it is converted back to a free token and sent on to the next station.

Transport
It is a request to transport objects from the software development environment, identified as the
source system, to the specified target system.

WAN (Wide Area Networks)

They are normally operated either by the telephone company or by private companies that offer
leased lines, switched lines or packet lines.

Work process
Work processes perform the bulk of the processing carried out by SAP systems. They perform
dialog steps in user transactions and carry out updates, lock management, printing services, and
so on.

Workbench
The ABAP/4 Workbench, a graphical programming environment, is used to create application
programs. The programming tools are accessed using buttons, dialogs and windows.

Workflow
It consists of time and logical sequence of work items, which are precessed by human agents or
mechanical processing units.

X.25
It is a standardized network access protocol for the packet switching network. The maximum
transmission speed is 64 KBit/s.

Thanks to Ricardo Fernandes de Miranda for submitting this document.

SAP Tips SE10 Transport Organiser Search for Requests

by Glynn Williams
You may want to search for a specific Transport you can do the following:
Transaction SE10
Select Goto>Transport Organizer Tools
Select Search for Objects in Requests Tasks
Here you can search for a specific , Program, Function Group, Class, Table/Structure, View, Table
Type, Data Element.
If you wish you can search for other objects too by doing the following:
Enter TABU in the object field press enter, this will create a line which says R3TR-TABU where you can
then enter the table name which you would like to search on. (R3TR-TABU will give you transports with
the content of the table has been transported, should you wish to see the actual movement of a table you
can use R3TR-TABL.)
There are over 800 valuees you can use on R3TR, which can be seen from using F4 on the object key and
once you get the result limited to 500 values, select Shift+F5 to increase the number of values to 900 and
select Program ID R3TR.
Other good values to use for example are R3TR-VDAT and R3TR-VIEW.
There is an even quicker way to finding a BADI and BADI implementations for a transaction:
1. SE37 display Function Module - SXV_GET_CLIF_BY_NAME.
2. Set a BREAKPOINT on call function SXV_ADD_PREFIX .
3. In another SESSION run the desired transaction,

SAP Tips Great tip Data browser cross client

You know how to use SE16N to view the contents of a table. Should you desire to view the contents of a
table across clients you can do this with transaction UASE16N.
SAP Tips Upload/Download files to/from application server
You can upload a file from your PC to the SAP application server with transaction CG3Z
You can download a file from the SAP application server to your PC with transaction CG3Y
List of fields across multiple tables
SE11 will show you 1 table with a list of fields. However if you wish to see a list of all fields for a range
of tables without going into each table individually simply use SE16N on table DD03L. Then use the
tables as a range.
How to see if the system/client is locked for customising changes
Question: How do I see if the system and client is locked for customising changes and who changed the
client control values last?
Answer: You can view the contents of table T000 which is the Clients table. Look at the value of
changes and transports T000-CCCORACTIV, to see if the client can be changed, for example value 2
How do I get a list of all Z* tables?
How do I get a list of all Z* tables?
You could use SE11 or SE16 or SE16n and then view F4 to see a list of all tables. But then you need to
extract them.
A better solution is to do the following, use SE16n on table DD02T and search on all Z* tables. (This will
give the table and table text.)
Can I compare the values inside a table across clients?
Hi There, I have a table with many entries in it. Is there a way to compare the data values across clients
without having to export both tables and do a Vlookup / Hlookup in excel?Yes, there is You can compare
the values of records in tables across clients by using transaction SCMP.

1 Object Listing In The

Transport Request

R/3 records (tables E070/E071/E071K) all the objects which have be

In our example we will include the following parts in the request.

a) some data element

b) a new table definition which uses that data element

2 when released, all objects

are written to a file

c) an ABAP which uses that table

d) some customizing settings

e) data for the new table

f) a program that must be executed after generating the tab

When the transport request is released, all objects are written to an

snap shot of all the objects in the version of the moment, when the

The generation of the object in the proper order is a very difficult ta

Objects may depend on each table at the same time, you have to create and activate the data el
other
table, which may use the data element.

When the TP-Utility starts to import the objects, it tries to determin

3 The TP utility will import the my be interdependent. According to this sequence the objects are g
program in the target system
in the required sequence
Transport requests are administered both in a collection of SAP tables E07* and in special directories of
the operating system. If your transport requests got complete messed up or you are searching for special
items, the following information may be helpful.

E070 Transport
header

The table E070 stores the names of all transport requests in the
system, both the released and open ones. Tasks are treated as
transport requests with a link to the parent transport.

The table contains the master entry for all orders ever since created in
the development system along with the status
E071 object list
E071K Keys for
TABU
objects
E070 Transport
header View with
texts
E070CRE
ATE Creation
Informati
on

The names of the objects of a transport request is stored in table

E071.
If table contents R3TR TABU are stored in a transport request, you
need to specify the keys of the table entries which shall be
transported. Those keys are stored in table E071K.

Annotating texts will be stored in E070T. E070 and E07T (sic! ) are
combined in view E070V.

The table E070CREATE contains the creation information of nonreleased transport orders. If the TO is released the entry is removed
from E070CREATE. Thus E070CREATE contains and only contains those
TOs which are open for current work.

E070C Client
informati
on

Erroneous
Transport
s

Transport
Status
Retrieval

E070 Transport
header

E070 Transport
header

E070 Transport
header

The table E070C information for client specific tarnsports. It contains

especially the name of the client, where the transport is created. It
happens sometimes, that a customzing request is created in a client,
which has been deleted or made otherwise unaccessible. In that case
you have no access to this transport request anymore. You can change
the name of the client in the table E070C with a little ABAP
Erroneous transport can be displayed with the standard report
RDDPROTL. The same report is also called if you choose to display
faulty reports within the SE10 or SE09 transactions

There is convenient function module that return all transports assigned

to a user along with its current release status. The transports are
returned in an internal table of the structure type trsapnames

data gt_sapnames like trsapnames occurs 10 with header line.

call function 'STRF_ACCESS_SAPNAMES'
exporting
iv_function = 'R'
iv_user = pv_user
iv_dirtype = pv_dir_t
tables
tt_sapnames = pt_sapnames
exceptions
could_not_access = 1
wrong_call = 2
others = 3.

The table has a field INT_STATUS that determines the actual state the
tarnsport is in. The list of stati is taken from the report RDDPROTL:

What Happens When a

Transport Request Is
Exported?

Do not distribute objects

in different requests, if
they might have
dependencies
The transport systems
tries to solve ties between
objects when importing in
the target system

Ties cannot be solved

when transports are
imported seperately

Splitting requests blocks

SAP from automatically
solve interdependencies

No coding is recorded in an open transport request. Rather it is a

simple directory, which records the names of modified repository
objects. Repository objects are all data dictionary objects, ABAPs,
SapScripts and a lot of table entries which are relevant for
development. The objects or the nature of the changes are not
recorded. When the request is finally exported, the TMS looks up all
the objects and exports then the current instance of the object. NB: if
you modify an ABAP several times, the TMS will export the saved
version of the moment the export is executed. The same is valid for
any other object e.g.. table definitions, data elements etc.
The basic idea of a transport request is to collect all objects which
belong together and may interact. The transport request is meant to be
sent to the target system.

When SAP imports a transport request in a target system it will also try
to generate the objects. It happens that objects cannot be generated
because another object is not ready yet. If you created a new field in a
table with a new data element, then the new table can only be
generated when you also imported and generated the data element
before. SAP checks thoroughly for those dependencies and sorts and
generates the objects in its correct sequence.
If you transport an ABAP that uses a newly created function module,
you should always put the function group into the same request as the
ABAP. Do not split it up, because the purpose of transport request is to
remind you, that the ABAP needs the function. That is what transport
requests are made for. If you forget to transport the function the ABAP
will compile correctly but will eventually get a run-time error, maybe
long after you transported and have already forgotten about it.
If you also use the new field in an Function Module, the Function
Module will only compile successfully, if the table is generated correctly
before. If you transport a modified table and the Function Module in
one request and the data element in another, the Function Module
generation will fail, because the table does not generate. If you then
transport the data element in a second request, the table will
automatically be generated, not so the Function Module, because it is
not informed about the modification of the table.

Transport requests are log files, that record all the modifications in a system.
These log files can then be used to copy the modifications to a master system.

Every time you modify a development object in R/3, the

repository records a note of this modification in a transport

request. This record keeps track of the identity of the modified

object and of the date, time and user who did the changes.

Transport request
logs all
modifications

The transport does not store the modified object itself. It is

rather a part list, which will be used later to extract a copy of all
modified objects in order to replicate them in a target system.,

Upon transport all

logged objects are
extracted and
exported

Once you decide to transport your modifications, the transport

management system will collect the objects listed in the
transport request and write a copy of them in a transport file.
This file is stored as a operating system file in the transport
queue directory.

TP-Utility

The created file can then imported in the target system. This is
done by the TP-Utility which is a program, that
1. reads the file,
2. replaces or inserts all the objects in the target system by
the ones found in the transport file
3. generates all modifies objects and their dependent
objects in the proper order

4. executes additional programs which may be required to

make the system consistent after the modification
Objects may
depend on each
other

ABAPs can be
triggered
automatically from
a transport

The generation of the object in the proper order is a very

difficult task. If you create a data element and a new table at
the same time, you have to create and activate the data
element first, then you can activate the new table, which may
use the data element.
Especially in the logistic information system, it happens very
often, that the structure of tables are changed by means of
customizing. E.g. the LIS administrator would add a new
statistics column to a table. When the table is generated the
contents of this column will be empty. So you want to execute
an ABAP which will automatically fill or update that column. You
can include this ABAP as an object in the transport, so that it will
be executed automatically when the transport is done.

The TP-Utility is a command line utility, which must be executed

TMS a visual front- from the UNIX or DOS-prompt. While the transports should be
end for TP
better done by the person who did the modification, the tool
TMS is provided, which allows a developer to easily trigger the
transport of an object.

SAP's Transport and repair Management System (TMS) provides a unique facility, which allows
to easily remember all modifications, a developer or customizer made in a development system.
Any modification is recorded in a transport request, which are structured into transport tasks.
After finishing a section of work, the transport tasks are released and the request is exported
into a UNIX file.

What Happens
When a Transport
Request Is
Exported?

No coding is recorded in an open transport request. Rather it is a

simple directory, which records the names of modified repository
objects. Repository objects are all DDIC objects, ABAPs,
SAPSCRIPTS and a lot of table entries which are relevant for
development. The objects or the nature of the changes are not
recorded. When the request is finally exported, the TMS looks up
all the objects and exports then the current instance of the
object. NB: if you modify an ABAP several times, the TMS will
export the saved version of the moment the export is executed.
The same is valid for any other object e.g.. table definitions, data
elements etc.

As the TMS records only what you touch and not what you did,
What Do I Do, if I the solution is straight forward. You must delete the undesired
Created An Object object in your development system. When the transport request
By Mistake
is exported, the TMS will realize, that the object does no longer
exist. However, it cannot know, if it has been eventually
transported to the target system before. It will export thus the
information, that the object has been deleted, and try to delete
the object in the target system as well. If the object never
existed in the target, there is actually no problem. It is simply
trying to kill a phantom.
Make it local. Every repository object belongs to a development
What, If I Do not class (Entwicklungsklasse). Every development class is marked
Want To Transport as either local or transportable. There is one default local
An Object
development class, called $TMP. This class is automatically
assigned, if you press the local object button, when being ask for
a transport request, the first time you try to save a modified
object.