SAP BASIS --TMS (IMPORT PROCESS)

Summary

This video script delves into the backend processes of SAP transport systems, focusing on the critical roles of tp.exe and R3trans.exe in exporting and importing data. It outlines the steps involved in a transport request, from selecting files to the execution of background jobs, and emphasizes the importance of the TP profile for successful operations. The script provides troubleshooting tips, including checking the existence of files, the functionality of TP, and the status of TRBAT and TRJOB tables in the database, ensuring a comprehensive understanding of transport system mechanics.

Takeaways

• 📚 Understanding the backend processes of exporting and importing in SAP is crucial for effective troubleshooting.
• 🔍 Two key executable files in SAP handle exporting and importing: tp.exe and R3trans.exe, with tp.exe initiating the process and R3trans.exe performing the actual work.
• 🔑 The TP profile is essential for tp.exe to function correctly; it contains information about host names, database names, and transport routes.
• 🔄 When importing a transport request, the process involves reading the profile, copying the go file to the temp directory, and initiating R3trans.exe to perform the import.
• 🔧 Troubleshooting transport issues involves checking the existence of go and data files, the functionality of tp.exe, and the status of the temp directory and log files.
• 📈 The RS TP test report (transaction code SC38) is used to verify the functionality of tp.exe and to ensure that the transport process is not encountering issues.
• 🗂️ At the database level, the TRBAT and TRJOB tables are important for transport troubleshooting, as they store the job names needed for importing data.
• 🕒 The R3trans.exe initiates the rdd impdp job, which is responsible for checking and performing import tasks at scheduled intervals.
• 📝 Logs are generated and stored in the log subdirectory, providing a record of the import process's success or failure.
• 🛠️ If transport is hanging or not progressing, checking the temp directory for running jobs and the log directory for any generated logs can provide insights into the issue.
• 🚫 Clearing old entries from the TRBAT and TRJOB tables and ensuring that the rdd impdp job is scheduled correctly can resolve transport importation problems.

Q & A

What are the two executable files in SAP responsible for exporting and importing?

The two executable files in SAP responsible for exporting and importing are tp.exe and R3trans.exe. tp.exe initiates the process, while R3trans.exe does the actual work of connecting with the database and performing the export and import tasks.

What is the purpose of the TP profile in the context of transport requests in SAP?

The TP profile contains all the necessary information such as hostnames, database names, and transport route information that participate in TMS and transport layers. It is essential for tp.exe to know what steps to perform during the import process.

How can you check the application connectivity between the application and the database in SAP?

You can check the application connectivity between the application and the database in SAP by using the R3trans.exe with the -D command, which checks the link between the application and the database.

What happens at the backend when you import a transport request in SAP?

When you import a transport request, the tp.exe reads the co-file from the profile subdirectory to understand the necessary steps, then copies the go file from the cofile subdirectory to the temp subdirectory, and initiates R3trans.exe to perform the import job.

Why is the temp directory used during the import process in SAP?

The temp directory is used as a temporary storage area for the execution of background jobs that are needed during the import process. It is essential for the temporary storage of data and logs during the import operation.

What is the significance of the TRFM table in transport troubleshooting?

The TRFM table is not mentioned in the script, but it is likely a typo for TRFM (Transport File Management), which is crucial in transport troubleshooting as it contains information about the transport requests and files.

How can you verify if tp.exe is working correctly in SAP?

You can verify if tp.exe is working correctly in SAP by running the RS TP test report through transaction code SC38. If everything is working fine, you should see a green check mark.

What are the two tables in the database level that are important for transport troubleshooting in SAP?

The two tables in the database level that are important for transport troubleshooting in SAP are the TRBAT table, which contains the necessary jobs for import, and the TRJOB table, which records the execution of these jobs.

What is the role of the R3trans.exe in the import process?

The R3trans.exe reads the control information from the temp directory, performs the necessary actions as defined in the TP profile, and leaves logs in the temp directory, which are then moved to the log subdirectory by tp.exe.

What should you do if the transport importation is taking too long or hanging?

If the transport importation is taking too long or hanging, you should check the temp directory for running jobs, verify the existence of go and data files, check if tp.exe is working correctly, and ensure that the TRBAT and TRJOB tables do not have old entries that might be causing issues.

How can you ensure that the import dispatcher job (RDD IMPDP) is scheduled in all SAP systems?

You should check the system's job scheduler to ensure that the import dispatcher job (RDD IMPDP) is set to run at the specified interval, which is typically every minute according to the system's parameters.

Outlines

00:00

📚 Understanding SAP Transport Process

This paragraph delves into the backend processes involved in SAP's import and export functionalities. It emphasizes the importance of understanding these processes for effective troubleshooting. The speaker introduces two key executable files, tp.exe and R3trans.exe, which are responsible for exporting data from the database to the application level and vice versa. The paragraph explains the role of the TP profile and how it contains crucial information for transport routes and system connectivity. The focus is on the initial steps of the transport process, including reading the control file, initiating the R3trans.exe, and the significance of the TP profile for successful import and export operations.

05:02

🔧 Backend Operations and Troubleshooting

The second paragraph continues the discussion on SAP transport processes, focusing on the backend operations that occur during import. It describes the sequence of actions initiated by the tp.exe file, including reading the profile, copying the go file to a temporary directory, and initiating R3trans.exe to perform the import job. The paragraph also highlights the importance of the temporary directory for background job execution and the role of R3trans.exe in reading the control file and performing necessary actions, leaving logs in the temporary directory. The speaker advises on how to check if the transport process is functioning correctly, including verifying the existence of go and data files, checking the TP's operation through the RS TP test report, and ensuring the temp directory and log directory are updating correctly.

10:06

🛠 Deep Dive into Database-Level Transport Troubleshooting

This paragraph provides a deeper insight into the database-level aspects of SAP transport troubleshooting. It discusses the importance of checking the TRBAT and TRJOB tables for old entries that might hinder new imports. The speaker explains the process of how TP reads the go file and pastes the necessary job information into the TRBAT table, which is then executed in the TRJOB table. The paragraph also introduces the concept of the R3trans.exe initiating the 'RGD IMPDP' job, which checks for pending imports every minute and is crucial for the import process. The speaker stresses the need to ensure that this job is scheduled in all SAP clients for a smooth transport process.

15:08

🗂️ Finalizing Transport Troubleshooting Steps

The final paragraph wraps up the discussion on transport troubleshooting by summarizing the key steps and checks that need to be performed at both the application and database levels. It reiterates the importance of verifying the operation of TP, the presence of go and data files, the status of the temp and log directories, and the scheduling of the 'RGD IMPDP' job. The paragraph also reminds the audience to check for old entries in the TRBAT and TRJOB tables and to ensure that the log directory is updated correctly. By mentioning these keywords and steps, the speaker equips the audience with the necessary knowledge to effectively troubleshoot transport issues in SAP.

Keywords

💡Export

Export in the context of the video refers to the process of transferring data from the database level to the application level within an SAP system. It is a critical operation for moving data, such as configurations or code changes, out of a development environment and towards a production or testing environment. The script mentions 'exporting' as one of the functions performed by the tp.exe and r3trans.exe executables, indicating its importance in the transport process.

💡Import

Import is the counterpart to export, representing the process of bringing data into a system. In the video script, import is discussed extensively as the operation that follows the selection of a transport request and involves the use of a go file and data file. The script explains that import is facilitated by the same executables mentioned for export, emphasizing that import is about receiving data into the application or database.

💡Transport Request

A transport request is a collection of objects that need to be moved between different SAP systems or clients. The script describes the process of selecting a transport request as part of the import operation, highlighting its role in the workflow of data transfer within SAP environments. It is the mechanism through which changes are propagated through different stages of the SAP system.

💡Profile

In the SAP context, a profile contains settings and parameters that define how certain processes, such as transport, should be executed. The script mentions the TP profile, which is essential for the transport process, as it contains information about hostnames, database names, and transport route information. The profile is read by tp.exe to understand the steps required for the import or export operation.

💡tp.exe

tp.exe is an executable file in SAP responsible for initiating the transport process. As described in the script, it does not perform the actual work of exporting or importing data but rather initiates the process by calling upon r3trans.exe. It is a key component in the backend operations of data transfer within SAP systems.

💡R3trans.exe

R3trans.exe is another executable file in SAP that performs the actual work of exporting and importing data. The script explains that while tp.exe initiates the process, r3trans.exe is responsible for connecting with the database and executing the necessary actions for data transfer, making it a central player in the transport process.

💡TRBat Table

The TRBat table in the database is where the necessary jobs for importing data are written. The script mentions that the information from the profile is pasted into the TRBat table, which then manages the execution of these jobs. It is a crucial part of the database-level operations for transport troubleshooting.

💡TR Job Table

The TR Job table is where the jobs for importing data are executed. The script describes a process where jobs are copied from the TRBat table into the TR Job table and then executed. It is another key database table involved in the transport process and is important for monitoring and troubleshooting.

💡RGDIMPDP Job

RGDIMPDP, or Import Dispatcher, is a job that is scheduled in all SAP clients to check for pending imports and execute them. The script explains that this job is initiated by TP and is responsible for the regular checking and execution of import jobs, ensuring that data is transferred as needed.

💡Log

In the context of the script, a log is a record of the actions performed during the transport process, indicating whether they were successful or not. The script mentions that logs are left in the temp directory and then moved to a log subdirectory, serving as a crucial record for monitoring and troubleshooting the transport process.

Highlights

Importing and exporting in SAP involves backend processes handled by two executable files: tp.exe and R3trans.exe.

Understanding the backend processes is crucial for effective troubleshooting of transport issues in SAP.

The tp.exe file initiates the export and import processes, while R3trans.exe performs the actual database operations.

The TP profile is essential for tp.exe to know the host and database names involved in transport layers.

R3trans.exe connects with the database to perform export and import tasks, as initiated by tp.exe.

The R3trans.exe is responsible for the actual data transfer between the application and the database.

Importing a transport request involves selecting a transport equation and executing it with specific parameters.

The TP profile file (e.g., TP_domain_SID.pfl) contains critical information for transport route management.

Missing TP profile files can cause tp.exe to malfunction, highlighting the importance of this configuration.

The process of importing a transport request includes reading the CO-file, pasting into the TEMP directory, and initiating R3trans.exe.

Background jobs for import are controlled by information kept in the profile, which is read by tp.exe.

The TEMP directory is used for temporary storage during the execution of background jobs.

Logs generated during the import process are moved from the TEMP directory to the LOG subdirectory.

Transport troubleshooting involves checking the existence of GO files, data files, and the functionality of TP.

The RS TP test report (transaction code SC38) can be used to verify the functionality of the TP system.

Checking the TEMP directory for updates and logs in the LOG subdirectory is part of the troubleshooting process.

At the database level, transport troubleshooting involves examining the TRBAT and TRJOB tables for old entries.

The RDD IMPDP job is crucial for checking and performing pending imports in SAP systems.

Scheduling the RDD IMPDP job in all clients ensures timely checking and execution of import tasks.

Keywords for transport troubleshooting include TRBAT, TRJOB tables, and the RDD IMPDP job.

Transcripts

when you say export and when you say

import what is happening in a packet as

a basis consultant if you know what is

happening in the back end then only you

can troubleshoot if you get any problem

right

so today we'll see what happens in the

back end when you import a transport

just you are selecting a transport

request just you are putting your go

file and data file into quality system

so profile and data file and selecting

your transport equation you are saying

button

and you are selecting the trial Target

client and the options and say okay it

is importing how it is importing what is

happening in a backend that we will see

today

there are two executable files in sap

which are responsible for this exporting

and importing one is

tp.exe second one is R3

trans dot

exc.exe so remember here

directory

So when you say x when you say release a

transport request what have what is

happening in a backend releasing is

nothing but exporting from the database

level to application Level so this

export and when you say import both the

things are done by this tp.exe and

r3trans.exe

remember here your TP won't do any well

TVP just initiates R3 trans actually who

will connect with your database means R3

trans R3 trans will connect with your

database that is the reason uh to check

the application connectivity between

application to database we use R3 trans

hyphen D command to check the link

between application to database so

actual work is done by R3 trans TP only

initiate the works

r3trans.exe is responsible for exporting

the data from a database to application

and importing the data from application

to database both export work and import

were both done by R3 trans dot exe

actual work is done by R3 trans dot exe

so when you import a transport request

how this TP and R3 transfer working to

work this TP properly you should have

that TP profile where you will get the

TP profile USR sap trans bin under that

bin you will be having TP underscore

domain underscore sid.pfl file is there

now if that file is missing your TP

won't know what to do so that file

contains all the host names all the

database names uh which are participated

in this in TMS and the transport layers

transport routes information everything

will be there so TP will read that

profile TP profile if the TP profile is

working not for not there TP won't work

remember the interrelationship between

this tp.exe and that TP profile

who will do the actual work R3 trans who

will initiate

tp.exe when you import a transport

request what happens so you will be

having for example One Core file what is

your profile name for example K sum 9

lakh 2.

and what is your data file

are some 9 lakh 2.

now you said stms underscore input stms

underscore

import

and select your transport request Sid K9

lag 2 and set single track button so

what is happening in a backend at

operating system level what is happening

this is OS level only now

OS level what is happening

TP reads the co-file from where

profile subdirectory

to know the necessary steps to be taken

to import this data into the database

this is at application Level right

database is here in the bottom

in the bottom I am having database

this is my database

now you are at application Level

application from application to database

you have to input to import this data

this R9 lakh to data into this database

what some background jobs need to be run

that background jobs information will be

kept in your profile controlling

information

first who will Who is responsible TP and

R3 terms right so TP first comes and

reads the profile from cofile

subdirectory it will go to co-files of

directory and read that

profile

and TP will understand okay these are

the steps I need to perform fine then it

will copy that go file from kofile

subdirectory and paste it into your

Tempo subdirectory where it is running I

told you why we use temp directory

execution of that background jobs you

need is a temporary storage area right

so it will use that area

that is the reason it will copy that

entire profile to Temp subdirectory

first

TP reads profile from kofile

subdirectory and copies that go file

into temp subdirectory what is this

profile is having

all the necessary jobs we need to run

everything is written in that

then

I'll write down otherwise

first thing what happens TP

reads

core file

from

direct rate

any doubt here

please if you are having any doubt stop

me

anyone

when you say Import in a backend this

will happen

second

paste into

temp subdirectory

what is this pasting

paste profile

into temp subject okay done

third point

TP initiates

R3 trans now R3 trans is coming

TP initiates R3 trans TP is ordering R3

truss to do the import job

now how are three trust know what are

the steps I need to perform

R3 trans

[Music]

from

temp directory

and perform

[Music]

necessary actions

[Music]

finally

leaves log at

template

so who is a TPC Builder R3 trans is a

worker so I I ordered R3 task to perform

some task at that location so you finish

that work and from that location only

you will inform me right sir the you

whatever the work you have sent me I

have completed the same way R3 trans

read control for from subdirectory term

subdirectory and perform necessary

actions and leaves the log log means

what whether it is successful canceled

everything whatever at the tempo

directory only

it will finish the work and it will

leave the log there itself finally the

hero will come into picture

TP comes

and reads log from

which directory

temp directory directory and

moves

log to

log sub directory

there is another subdirectory right log

is there

first first of the log will generate

here

from here it will move that log to

log sub directory

the first thing is TP reads the go file

and paste it into temp directory first

process second one

TB calls R3 trials to do the TPA Shades

R3 trans R3 trans will come and read the

profile from temp side directory and

perform the necessary actions and the

leaves the logs it itself there

finally TP comes and read the log from

temp directory and finally give log to

logs update this will happen at

operating system level

transport is hang if your transport is

running for so long time where you will

check now

see observe something

few things here see temp in temp it is

running all the jobs means in this step

if you open that terms of the retainer

some job names will come and vanish come

and manage that means your import is

happening

and you will get the login log directory

first of all you have to check whether

go file and data file exist or not

the second thing you have to check

whether TP is working or not how you

check whether TP is working or not there

is one report called RS TP test

go to sc38t code and run that

rstp test report

if you get everything Nike symbol I'll

show you otherwise

oh

[Music]

go to sc38

and hit rstp test rsdp

test and enter

execute

so you have to check whether your TP is

working fine or not and you got Kofi in

data fill or not and your temp directory

is updating or not and did you get a log

in that lock subdirectory

everything is green here no all these

things are not green

so some problem is there in your TP

definitely you will get transport

importation problem everything should be

in green

then only that means your tip is working

fine like this we have to check

so till now you know what is happening

in a backended application Level so go

file data file TP you need to check

Tempo directory you need to check log

data yes or no

any doubts here

[Music]

no

everyone please

so if anybody asks you about transport

troubleshooting you should know all

these things okay we have to check

whether TP is working or Not by using

rstp test report then first of all you

have to check whether profile and data

file generated or not then you have to

check Tempo directory whether it is

updating or not okay then we have to

check the log

okay in log directory also we checked

law fine

and what is happening in that database

level that is second one database now in

database level uh if you go with a

database level there are two tables

called first what happens in database we

will see first TP

rates

profile

from

co-file subdirectory

business

now

yeah okay

directory

then

uh we need to discuss about two things

here one is a TR bat table

second one is TR job table there are two

tables in the database level in

transport troubleshooting you have to

mention about these two tables one is TR

bat second one is a TR job table

subdirectory

and this profile contains what all the

necessary jobs right what are the jobs

you need to run to import that data the

job names will start from rgd jobs rdd

some name will be there so I'm going

with star star

some rgd jobs you need to run to import

the data that all the jobs will be

written to your

TR bad tip okay

one by one job will be copied to tr job

table and it will execute

for start is a finish executed secondary

teacher will be copied to tiaja executed

third order is your fourth art like this

all your rdd jobs which are needed for

import that transport requests the data

into your target database all the jobs

name will be written in your profile

that co-files information is this

will be pasted into your trback table

later all that jobs will be executed in

TR job table so if somebody asks you

about a transport troubleshooting you

have to tell them whether trback and TR

job got any old entries

if there are any old entries that new

entries is not accepting that so you

have to delete that two tables entries

then you have to re-import that

transport then you will get it so first

TP reads go file from code file

subdirectory

second thing

paste cofi into

TR bat table

tier bat

table this you know

so it application Level TP reads profile

and paste it into

tempo subdirectory

at a database level it is pasting into

TR bad table it is pasting into

TR a bad table remember that table name

third at application Level TP initiates

R3 trans right here TP initiates Punjab

called rgd impdp job

remember these keywords rgd impdp what

is this rddi mpdp means

import dispatches rdd jobs I told you

rgd and then job name I import

dispatcher job so this rdd impdp job is

scheduled in all SAP systems what is

this job security means import to

dispatcher so this job will run for each

and every one minute according to the

parameter time whatever time you set

according to that this job will check in

your system whether is there any Imports

I have to perform for every one minute

the job will run and it will check the

job will run it will check is there any

Imports I need to perform yes if there

are any Imports are pending it will

important to the retailers so to do

input anything into your database this

job must be scheduled in your all the

clients

so TP initiates that job okay it will go

and kick the job okay here some import

job is there you perform then rdda mpdp

will start one job another job from one

the rdd job into trback then second

order job into TR job it will copy this

rdd job into TR jab and execute and

vanish this job copy execute and vanish

finally they leave login

log subdirectory

foreign

log

subdirect at application Level

subdirectory means

this will happen at a database so paste

it into oh okay here

it keep initiates a TR bat okay fourth

one we will write this

copy

1 by 1

job into TR job table now you can say TR

job table

and execute

okay table and execute then leaves log

at log subdirectory this is happen at a

database level so see at application

Level the troubleshooting part is

whether TP is working or not whether go

file data file generated or not third

one

check the temp directory check log

subdirectory at database level

you have to check whether TR bat and TR

job tables got any old entries whether

our GDI and PDP job is scheduled or not

then you have to check this log also so

you have to mention trback table name TR

job table name

and

rdd impdp if anybody asks you

about your

this transfer troubleshooting

what are the job names TR bat and TR job

these two are tables remember

TR bat and TR Java tables rdd impdp's

job

job

so if you mention all these keywords

that is enough for transport

troubleshooting