BW Transport - unconditional mode
What is unconditional mode?
How and where do set this option?
Thanks
Hi GopiKrishna,
SAP transport program "R3trans" is used to transport data between SAP Systems and for the migration between different SAP releases.
And R3trans will internally call another program call "tp"
By using unconditional modes, you can override the rules of the transport system. The following modes are available:
Export:
· 1: Ignore incorrect status of a change request.
If you do not set this mode, only change requests with the status A (all locked), O (open) or R (released) are exported. If the export is successful, the change request is released by R3trans.
· 8: Allow direct selection of forbidden tables.
Some tables are part of complex objects and generally cannot be exported alone.
Import:
· 1: Ignore that this change request was already imported into this system and import everything again.
If you do not set this mode, only objects that have not already been imported successfully are imported again.
· 2: Overwrite originals
· 6: Overwrite repaired objects
· 8: Ignore the restriction resulting from table classifications and import all table entries into specified clients.
Please refer this --
about calling the R3trnas program and other info
http://help.sap.com/saphelp_nw04/helpdata/en/3d/ad5b9b4ebc11d182bf0000e829fbfe/frameset.htm
Similar Messages
-
How i can deselect in TMS the unconditional mode 0 ( overtaker )
hello
in TMS when you import a singel transport always the unconditional mode 0 is preselected;
where can i change this preselection?
thank you very much
and
best regards
brittaThe following SAP Link may help you.
http://help.sap.com/saphelp_nw70/helpdata/EN/3d/ad5b814ebc11d182bf0000e829fbfe/content.htm
example: tp import T11k904711 P11 U06
If you go through the same you may find most options required by you.
Regards
Shan -
Setting default unconditional mode(s) for a specific SID in TMS
I am working in ECC 5.0, and I'm trying to configure one of the systems in our TMS landscape to use a specific unconditional mode (u2) by default. Does anyone know a method by which I can set this in the TMS configuration? I was looking at parameter R3TRANSOPTIONS for this, but after multiple searches on help.sap.com (and other sites), I cannot verify (1) that this will even work (2) if it will work, what the syntax for the call is.
Thanks in advance for your help!Hi Katherine
This is not possible with a normal import all job for TMS or other settings as far as I know. It is also not recommended that you would use an unconditional mode by default.
The unconditional mode is specified by the tp process, so an R3trans parameter is not going to help. Their are a number of TP parameters as well, but no parameter is available for the unconditional mode in SAP.
If you would absolutely need this, I think the simplest solution would be to create a custom program to do this, you can then program a report which uses the tp command with U02. You would have to be careful with authorisation of this report as it could be dangerous for end users to perform this.
Reward points if useful.
Kind regards
Tom -
The dreaded 404 message using basicHttpBinding, Transport security mode, and certificates
I am working on setting up a WCF service using mutual authentication with both client and server certifiates. The service is hosted in IIS 7, and I'm trying to access it from a simple console app. When I try to connect to the service, I get the error ""There
was no endpoint listening at
https://localhost/IISHostedService/MyService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details." The inner exception is "The remote server returned an error:
(404) Not Found."
I have seen people all over the net reporting this error, but so far none of their fixes work for me. I have an HTTPS binding in IIS for my app, and I am able to browse to my service (using either http or https) and view it with no problems. I can get the
wsdl (also over either protocol) with no issues, but connecting from the client doesn't work.
Here is my server config:
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior>
<serviceCredentials>
<serviceCertificate findValue="ServerCertificate" storeLocation="LocalMachine" x509FindType="FindBySubjectName" />
<clientCertificate>
<authentication revocationMode="NoCheck" />
</clientCertificate>
</serviceCredentials>
<serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />
<serviceDebug includeExceptionDetailInFaults="true" />
</behavior>
</serviceBehaviors>
</behaviors>
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
<bindings>
<basicHttpBinding>
<binding name="BasicHttpBinding_MyService">
<security mode="Transport">
<transport clientCredentialType="Certificate" />
</security>
</binding>
</basicHttpBinding>
</bindings>
<services>
<service name="MyService">
<endpoint binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_MyService" contract="Namespace.IContract" />
</service>
</services>
</system.serviceModel>
And my client:
<system.serviceModel>
<behaviors>
<endpointBehaviors>
<behavior name="clientEndpointBehavior">
<clientCredentials>
<clientCertificate findValue="ClientCertificate" storeLocation="LocalMachine" x509FindType="FindBySubjectName"/>
</clientCredentials>
</behavior>
</endpointBehaviors>
</behaviors>
<bindings>
<basicHttpBinding>
<binding name="BasicHttpBinding_MyService" closeTimeout="00:10:00"
openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00"
allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
maxBufferSize="65536" maxBufferPoolSize="524288" maxReceivedMessageSize="65536"
messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"
useDefaultWebProxy="true">
<readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
maxBytesPerRead="4096" maxNameTableCharCount="16384" />
<security mode="Transport">
<transport clientCredentialType="Certificate" />
</security>
</binding>
</basicHttpBinding>
</bindings>
<client>
<endpoint address="https://localhost/IISHostedService/MyService.svc behaviorConfiguration="clientEndpointBehavior"
binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_MyService"
contract="Namespace.IContract" name="BasicHttpBinding_MyService" />
</client>
</system.serviceModel>
I am not sure if it matters, but this client and server are running on the same physical machine in a test environment. I have confirmed that both the client and the server certificates are installed, and that the issuing authority is trusted. The virtual
folder is set in IIS to "Accept" client certificates, and SSL is not required.
Does anyone have any thoughts what I may be missing? This service works without a problem over HTTP, so it has to be somehow related to the certificate that is being passed. With the Server certificate, I just trapped the ServicePointManager.ServerCertificateValidationCallback
event to manually approve the certificate if the subject matched what I was looking for (the subject does not match the domain name, since this is a test environment). Do I need to do something similar for the client certificate?
EDIT: One thing I do notice is that, in the WSDL, the soap location is always pointing to http. I'm not sure if that is correct or not:
<wsdl:service name="MyService">
<wsdl:port name="BasicHttpBinding_MyService" binding="tns:BasicHttpBinding_MyService">
<soap:address location="http://computerName.domain.com/IISHostedService/MyService.svc" />
</wsdl:port>
</wsdl:service>A little more information (since this is the main thing I have to work on today):
After some research, I decided to try using a custom certificate validator, in case something is wrong with the client certificate. In the clientCertificate\authentication node on the server, I set the certificateValidationMode="Custom" and set customValidationType="MyType.Validator,
MyType". My type is apparently being found (when it is not found I get a "service could not be activated" error), but my Validate() method is never being called.
Now this leads me to believe that it's not a problem with the client certificate, but something else, before it even gets that far. -
Transport + Message (Both mode) security in WCF ?
Hello,
In WCF, how transport + message security is implemented ?
i.e. How X.509 certificates are used to encrypt transport + message (BOTH mode) security ?
Thanks in advanceHi,
>> how transport + message security is implemented ?
It seem that you want to implement the both transport and message security mode in one wcf application, I will suggest you use the security mode
TransportWithMessageCredential.
When the TransportWithMessageCredential security mode is configured, the transport security is used to provide confidentiality and integrity for the transmitted messages and to perform the service authentication. However,
the client authentication is performed by putting the client credential directly in the message. This allows you to use any credential type that is supported by the message security mode for the client authentication while keeping the performance
benefit of transport security mode. In one word is that client authentication is provided at the message level, and message protection and service authentication are provided at the transport level.
For more information, please try to refer to:
#Message and Transport Security:
http://msdn.microsoft.com/en-us/library/ff648863.aspx .
>>How X.509 certificates are used to encrypt transport + message (BOTH mode) security
In the service side, the X.509 certificates will use to provide the message protection and service authentication. If you used the certificate authentication, then in the client side, the X.509 certificates will use to
identify itself to the server.
For more information, please try to refer to:
#How to: Secure a Service with an X.509 Certificate:
http://msdn.microsoft.com/en-us/library/ms788968(v=vs.110).aspx .
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Trying to import tables from datapump file which done using transportable mode
Hi using impdp on oracle 11.2.0.3 and have a dumpfile which contains export of tables which done using transportable tablespace mode.
Want to import 3 of the tables just form file cobncerned into another database using impd but not working
Error
ORA-39002: invalid operation
ORA-39061: import mode FULL conflicts with export mode TRANSPORTABLE
{code}
userid=archive/MDbip25
DIRECTORY=TERMSPRD_EXTRACTS
DUMPFILE=archiveexppre.964.dmp
LOGFILE=por_200813.log
PARALLEL=16
TABLES=ZPX_RTRN_CDN_STG_BAK,ZPX_RTRN_STG_BAK,ZPX_STRN_STG_BAK
REMAP_TABLESPACE=BI_ARCHIVE_DATA:BI_ARCHIVE_LARGE_DATA
REMAP_TABLESPACE=BI_ARCHIVE_IDX:BI_ARCHIVE_LARGE_IDX
{code}
Any ideasHi,
Export command
{code}
procedure export_old_partitions_to_disk (pi_SEQ_num NUMBER)
is
h1 number; -- Datapump handle
dir_name CONSTANT ALL_directories.DIRECTORY_NAME%type :='DATA_EXPORTS_DIR'; -- Directory Name
v_file_name varchar2(100);
v_log_name varchar2(100);
v_job_status ku$_Status; -- The status object returned by get_status
v_job_state VARCHAR2(4000);
v_status ku$_Status1010;
v_logs ku$_LogEntry1010;
v_row PLS_INTEGER;
v_current_sequence_number archive_audit.aa_etl_run_num_seq%type;
v_jobState user_datapump_jobs.state%TYPE;
begin
-- Set to read only to make transportable
execute immediate ('alter tablespace ARCHIVED_PARTITIONS read only');
-- Get last etl_run_num_seq by querying public synonym ARCHIVE_ETL_RUN_NUM_SEQ
-- Need check no caching on etl_run_num_seq
select last_number - 1
into v_current_sequence_number
from ALL_SEQUENCES A
WHERE A.SEQUENCE_NAME = 'ETL_RUN_NUM_SEQ';
v_file_name := 'archiveexppre.'||PI_SEQ_NUM||'.dmp';--v_current_sequence_number;
v_log_name := 'archiveexpprelog.'||PI_SEQ_NUM||'.log';--v_current_sequence_number;
dbms_output.put_line(v_file_name);
dbms_output.put_line(v_log_name);
-- Create a (user-named) Data Pump job to do a schema export.
-- dir_name := 'DATA_EXPORTS_DIR';
h1 := dbms_datapump.open(operation =>'EXPORT',
job_mode =>'TRANSPORTABLE',
remote_link => NULL,
job_name => 'ARCHIVE_OLD_PARTITIONS_'||PI_SEQ_NUM);
dbms_datapump.add_file(handle =>h1,
filename => v_file_name,
directory => dir_name,
filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE,
reusefile => 1); -- value of 1 instructs to overwrite existing file
dbms_datapump.add_file(handle =>h1,
filename => v_log_name,
directory => dir_name,
filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE,
reusefile => 1); -- value of 1 instructs to overwrite existing file
dbms_datapump.metadata_filter(
handle => h1,
name => 'TABLESPACE_EXPR',
VALUE => 'IN(''ARCHIVED_PARTITIONS'')'
dbms_datapump.metadata_filter(handle =>h1,
name => 'TABLE_FILTER',
value => 'BATCH_AUDIT');
--dbms_datapump.set_parameter(h1, 'TRANSPORTABLE', 'ALWAYS');
-- Start the datapump_job
dbms_datapump.start_job(h1);
begin
NULL;
--dbms_datapump.detach(handle => h1);
end;
dbms_output.put_line('Job has completed');
dbms_datapump.wait_for_job(h1,v_jobState);
dbms_output.put_line('Status '||v_jobState);
dbms_output.put_line('Job has completed');
execute immediate ('alter tablespace ARCHIVED_PARTITIONS read write');
exception
when others then
dbms_datapump.get_status(handle => h1,
mask => dbms_datapump.KU$_STATUS_WIP,
timeout=> 0,
job_state => v_job_state,
status => v_job_status);
dbms_output.put_line(v_job_state);
MISC_ROUTINES.record_error;
raise;
-- RAISE_APPLICATION_ERROR(-20010, DBMS_UTILITY.FORMAT_ERROR_BACKTRACE||' '||v_debug_table_name);
-- RAISE_APPLICATION_ERROR(-20010,DBMS_UTILITY.format_error_backtrace);
end export_old_partitions_to_disk;
{code} -
Error while transporting a Function Group!
HI ABAPers!
We have created many function modules in a single function group. While we are trying to transport the function group we succeeded in releasing the function group from the development server to the quality system. But while we are trying to import the same function group from the quality system, it is throwing an error 'FUNCTION GROUP NOT FIT IN SIZE'. what might be the reason for this behaviour and what would be the remedy? Please help this out and points would be awareded for the solutions.
Regards,
KiranHi,
just an hint (i don't know if it will help u).
Try in se37 trx , menu "Utilities", shoul be "Repair function group" (o something like that).
Sometimes u have to do also with standard FM.
In second step, use unconditional mode -126 in your transport (call to your system admin ho to do that).
Hope it helps
Bye
Andrea
Pls reward if it helps -
Transport control program tp ended with error code 0212
Hi all,
I have created a two system landscape of development & production server. But while I am releasing any request from develpoment server a error is showing: " Transport control program tp ended with error code 0212 Errors: could not access file as supposed (see dev_tp or S".I have chosen development server as domain controller. TMS alert viewer error message also contains the following information------>command: TMS_MGR_READ_TRANSPORT_QUEUE
service: transport service
start : online
Function: TMS_TP_SHOW_BUFFER
message: TP_REPORTED_ERROR
In import monitor it's showing : "tp finished: could not access file as supposed (see dev_tp or SLOG1113.K"
Can you tell me how to resolve this issue?dev_tp contains:
This is R3trans.exe version 6.14 (release 700 - 09.04.10 - 11:26:00).
unicode enabled version
usage: R3trans.exe [<options>] <control_file>
The control_file describes what R3trans has to do.
The following options are possible:
-c f1 f2 : Copy file f1 to f2 with character set conversion.
-d : DB connect. Test if SAP database is available.
-i file : Import from file without using a control file.
-l file : List the contents of file to the log file.
-m file : List the contents of file to allow tp to create a cofile.
-t : Test. All database changes are rolled back.
-t4 : Trace level 4. Switch on developer trace.
-u <int> : Unconditional modes. See below.
-v : Verbose. Write more details to the log file.
-w file : Log file. The default log file is 'trans.log'.
-x : DB connect without access on any SAP table.
R3trans.exe finished (0012).
& the slog file is not there in the trans/log directory -
Error when transporting BI 7.0 request
Hi Experts,
I´ve been trying to transport the first and simple request to the QAS environment and I´m getting error 12 with the log below. No one knows till now what´s going on, so I would really appreciate any help. I´m a BI Consultant and I can´t understand the whole meaning of the error description. In this request there´s just a an Infoarea object.
Thanks in advance.
Fabio
Log File: /usr/sap/trans/log/CBDI900093.CBQ
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.
Main import
Transport request : CBDK900093
System : CBQ
tp path : tp
Version and release: 372.04.29 700
R3trans version 6.14 (release 700 - 14.05.08 - 17:05:00).
unicode enabled version
===============================================
date&time : 28.08.2008 - 09:12:41
control file: /usr/sap/trans/tmp/CBDKK900093.CBQ
> #pid 1228956 on celcbq ()
> import
> buffersync=yes
> file='/usr/sap/trans/data/R900093.CBD'
> continuation='/usr/sap/trans/data/R900093_#.CBD'
> client=300
> csi=yes
> repeatimport=yes
>
> excluding 'R3TRDDDD','R3TRDOMA','R3TRDTEL','R3TRENQU','R3TRMACO','R3TRMCID','R3TRMCOB','R3TRSHLP','R3TRSQLT','R3TRTABL','R3TRTTYP
R3trans was called as follows: R3trans -u 2 -w /usr/sap/trans/tmp/CBDI900093.CBQ /usr/sap/trans/tmp/CBDKK900093.CBQ
active unconditional modes: 2
Connected to DBMS = ORACLE --- dbs_ora_tnsname = 'CBQ' --- SYSTEM = 'CBQ'.
0 0
trace at level 1 opened for a given file pointer
================== STEP 1 =====================
date&time : 28.08.2008 - 09:12:41
function : IMPORT
data file : /usr/sap/trans/data/R900093.CBD
Continuation : /usr/sap/trans/data/R900093_#.CBD
buffersync : YES
client : 300
repeatimport : YES (corresponds to unconditional mode 1)
repeatclimport : NO
c.s.i. : YES
l.s.m. : VECTOR
charsetadapt : YES
def. charset : WEUROPEAN
commit : 100000
table cache : dynamic
EXCLUDING : 'R3TRVIEW','R3TRUENO','R3TRTTYP','R3TRTABL','R3TRSQLT','R3TRSHLP','R3TRMCOB','R3TRMCID','R3TRMACO','R3TRENQU','R
Data file is compressed with algorithm 'L'.
Export was executed on 28.08.2008 at 09:10:40 by cbdadm
700
with R3trans version: 14.05.08 - 17:05:00
Source System = IBM RS/6000 with AIX on DBMS = ORACLE --- dbs_ora_tnsname = 'CBD' --- SYSTEM = 'CBD'.
language vector during export: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdi(),./:;
language vector during export: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdi(),./:;& (ISO-ARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVB
lsm during export: VECTOR
trfunction = K (transport to consolidation system)
Used Commandfile CBDK900093 (SAP237827/2)
This is a transport to consolidation system.
1 entry for E070 inserted (CBDK900093).
2 entries for E071 inserted (CBDK900093 *).
1 E071C entry created
1 entry for E070C inserted (CBDK900093).
8 entries for E070A inserted (CBDK900093 *).
1 entry for E07T inserted (CBDK900093 *).
Start import R3TRAREA0HCM ...
2910 2910
1 entry for TADIR inserted (R3TRAREA0HCM ).
1 entry for RSDAREA inserted (0HCM M).
0 entries from RSDAREAT (&0HCM M) deleted.
0 entries from RSDAREAT (;0HCM M) deleted.
0 entries from RSDAREAT (:0HCM M) deleted.
0 entries from RSDAREAT (/0HCM M) deleted.
0 entries from RSDAREAT (.0HCM M) deleted.
0 entries from RSDAREAT (,0HCM M) deleted.
0 entries from RSDAREAT ()0HCM M) deleted.
0 entries from RSDAREAT ((0HCM M) deleted.
0 entries from RSDAREAT (i0HCM M) deleted.
0 entries from RSDAREAT (d0HCM M) deleted.
0 entries from RSDAREAT (c0HCM M) deleted.
0 entries from RSDAREAT (b0HCM M) deleted.
0 entries from RSDAREAT (a0HCM M) deleted.
0 entries from RSDAREAT (90HCM M) deleted.
0 entries from RSDAREAT (80HCM M) deleted.
0 entries from RSDAREAT (70HCM M) deleted.
0 entries from RSDAREAT (60HCM M) deleted.
0 entries from RSDAREAT (50HCM M) deleted.
0 entries from RSDAREAT (40HCM M) deleted.
0 entries from RSDAREAT (30HCM M) deleted.
0 entries from RSDAREAT (20HCM M) deleted.
0 entries from RSDAREAT (10HCM M) deleted.
0 entries from RSDAREAT (00HCM M) deleted.
0 entries from RSDAREAT (Z0HCM M) deleted.
0 entries from RSDAREAT (Y0HCM M) deleted.
0 entries from RSDAREAT (X0HCM M) deleted.
0 entries from RSDAREAT (W0HCM M) deleted.
0 entries from RSDAREAT (V0HCM M) deleted.
0 entries from RSDAREAT (U0HCM M) deleted.
0 entries from RSDAREAT (T0HCM M) deleted.
0 entries from RSDAREAT (S0HCM M) deleted.
0 entries from RSDAREAT (R0HCM M) deleted.
0 entries from RSDAREAT (Q0HCM M) deleted.
1 entry for RSDAREAT inserted (P0HCM M).
0 entries from RSDAREAT (O0HCM M) deleted.
0 entries from RSDAREAT (N0HCM M) deleted.
0 entries from RSDAREAT (M0HCM M) deleted.
0 entries from RSDAREAT (L0HCM M) deleted.
0 entries from RSDAREAT (K0HCM M) deleted.
0 entries from RSDAREAT (J0HCM M) deleted.
0 entries from RSDAREAT (I0HCM M) deleted.
0 entries from RSDAREAT (H0HCM M) deleted.
0 entries from RSDAREAT (G0HCM M) deleted.
0 entries from RSDAREAT (F0HCM M) deleted.
1 entry for RSDAREAT inserted (E0HCM M).
1 entry for RSDAREAT inserted (D0HCM M).
0 entries from RSDAREAT (C0HCM M) deleted.
0 entries from RSDAREAT (B0HCM M) deleted.
0 entries from RSDAREAT (A0HCM M) deleted.
End of import R3TRAREA0HCM
E071-LOCKFLAGs 000002 - 000002 updated ('2', 1 entries).
E071C entries 000002 - 000002 deleted (1 entries).
CBDK900093 touched.
1 tables in P-buffer synchronized.
1 tables in R-buffer synchronized.
2310 5220
***LOG BZY=>unexpected return code 103 calling INS
306203 0.306203
db_syflush (TRUE, FALSE) failed 22 0.306225
db_con_commit received an error return code in before-commit action
32 0.306257
*** ERROR => missing return code handler 25 0.306282
caller does not handle code 1024 from dblink#5[293]
==> calling sap_dext to abort transaction
sap_dext called with msgnr 900:
Main import
End date and time : 20080828091241
Ended with return code: ===> 12 <===
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.Hi Fabio,
You should contact your System Admin for this error.
Since the transport tp return code is 12, that means this not because of the content of the transport. however, it may be due to some other technical settings.
http://help.sap.com/saphelp_nw2004s/helpdata/en/57/38e26c4eb711d182bf0000e829fbfe/content.htm
Regards,
Zaheer -
Transport control program tp ended with error code 0203
when i import queue and transport queue from dev to prd ,error show:
Transport control program tp ended with error code 0203
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: IMPORT DEVK900298 P01 clientP01 U0 pf=/usr/sap/tra
Return code: 0203
Error text: wrong syntax in tp call
Request: DEVK900298
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.Dear Allen,
The transport control program tp collects all return codes that occur when a tp command is executed. From all of these single return codes, a combined return code is calculated that tp outputs as a result at the end the command. During an import, for example, all return codes for individual import steps are handled. If a special return code does not occur, then the combined return code at the end is the maximum of individual return codes that occur. In addition to the value of the return code, tp also gives a short description of this return code. You can display this short description using the command explainrc.
Normally, all return codes that occur originate from individual transport steps. Since these individual return codes can only have the following values 0, 4, 6, 8, 12, 13, 14, 16, the combined return code also has one of these values. However, if a general error occurs, a single return code over 200 is generated. For example, this could arise if tp cannot establish a connection to the database. The maximum return code for all single transport steps is output in a separate message before specifying the combined returned code. In this case, the combined return code is always the return code of the general error message.
<b>tp Commands:</b>
tp addtobuffer <request> <sapsid>
As of Release 4.6A, an explicit addtobuffer command leaves the position of the entry unchanged, if the relevant transport request is already in the buffer. Only the status of the entry is changed:
Unconditional modes appearing in the command line are added to the unconditional modes in the buffer.
All the steps of the entry are re-initialized.
If the entry found is not an initial entry, the import step for the command file is set to *4000 .
Before you call this command and its options, consider the effects of changing the import sequence.
tp cleanbuffer <sapsid>
This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>. This function is contained in the commands tp import all <sapsid> and tp put <sapsid> .
tp delfrombuffer <request> <sapsid>
If the specified request is marked for import into the specified SAP System, this flag is deleted from the import list.
Before you call this command, consider the effects of changing the import sequence.
As of Release 4.6A: If a transport request was only partially imported, you can delete this type of transport request from the buffer. However, if a deleted transport request is placed in the buffer (without having been initially or completely imported), the attributes of the old entry are reactivated. This means the return codes, the unconditional modes and tags of the deleted entry appear in the new entry.
tp delstopmark <sapsid>
If the list of requests marked for import into the specified SAP System contains a STOP mark, the mark is deleted.
tp export <request>
This exports the complete request from the source system. This command starts the export of a request from the operating system level. Only use this command in exceptional cases. The SAP System uses the command expwbo to release requests from CTS transactions.
tp reformatbuffer <sapsid> [options]
This automatically reformats the entire buffer.
As of Release 4.5A, there are 2 different formats for buffer entries. (As of Release 4.5A, tp can work with both formats, and with a puffer containing heterogeneous entries. As of Release 4.6A, tp can work with 3 formats.)
However, in certain cases entries with the old formatting have to be reformatted during the normal run of tp . In this case, the entire buffer is automatically reformatted.
If you use the options downtorelease and Iagree for command reformatbuffer , you can format the buffer so that its formatting is compatible with an older release:
Option downtorelease <Release>
The command reformatbuffer with this option formats the buffer so that the formatting corresponds to the one used in an old release. This is necessary if tp writes buffer entries to the buffer of another system, but uses a buffer format that the transport control programs does not understand in this system.
Since older formats cannot store the same amount of information as the newer ones, some information contained in the original buffer may not be stored in the unformatted buffer. This may lead to data loss.
To avoid data loss, the original buffer is stored. In addition, you have the following functions:
Displaying the unformatted buffer (using showbuffer <SID> )
Displaying the original buffer (using showbuffer buffer=<SID>SAV )
Accepting the unformatted buffer (using reformatbuffer and the option Iagree yes )
Resetting the changes (using reformatpuffer and the option Iagree no )
If you call reformatpuffer using downtorelease , tp displays in detail if information was lost by reformatting, and what that information was. tp also names the commands that is has to execute to accept or reject the changes.
If you use the option downtorelease , you must also specify the option Iagree with yes or no . You cannot use the transport system until you decide to accept or reject the changes.
Option Iagree
Here are the following values for this option:
yes ( true )
Accept the change made by tp reformatbuffer <SID> downtorelease <rel>
In this case, tp deleted the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
no ( false )
Reject the change made by tp reformatbuffer <SID> downtorelease <rel> In this case, tp copies the backup of the original buffer back and deletes the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
tp setstopmark <sapsid>
A special STOP mark is added to the list of requests registered for import into the specified SAP System. The commands tp import all <sapsid> and tp put <sapsid> only process the requests in front of this stop mark.
If there is no stop mark, it is automatically generated by the commands
tp import all <sapsid> and tp put <sapsid> .
When all the requests in front of the stop mark have been imported successfully, at the end of all the calls the related marks and the mark itself are deleted.
A STOP mark can only be placed at the end of the change requests that have already been marked. In addition, it can only be set if no other mark of the same kind already exists.
tp showparams <sapsid>
This tp function displays which values the individual parameters of the transport profile have for the current SAP System.
tp verse <request>
This creates versions of the objects in the specified request. This transport step is contained in command export .
As of Release 4.5A, more actions that prepare the export are performed in this step.
Thanks and Regards,
Naveen. -
Hello,
I downloaded the necessary support packages of SAP_APPL ( Lojistik ve
Mali isler ) and P3A ( P3VA:500 Add-on Installation) on AFS Test system
and updated them on their patch level. There was no problem with P3A,
but I installed the patch level on SAP_APPL component to 009. Then I
take the message "text" while installing 0010 patch and we
cannot request the release in test system. I had a search for some
documents about this on OSS but failed. Patch levels,after updating,
are like the folloving:
P3A-V500-0005-SAPKIAF505-P3A V500 : Add-On Installation-Comp.Supp. Pkg.
SAP_APPL-500-0009-SAPKH50009-Lojistik ve mali işler- R/3 Support Pkg.
I also add our R3trans and TP version info.It is old, but we couldn't find the new version at SAP Service Marketplace for KErnel 6.40, how can we upgrade R3trans / TP ? (Do we have to upgrade Kernel patch? Our kernel level is (release 640, patch level 87).
<b>Error Message</b>,
The import was stopped, since an error occurred during the phase
IMPORT_OBJECT_LIST, which the Support Package Manager is unable to
resolve without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
- Error in phase: IMPORT_OBJECT_LIST
- Reason for error: TP_FAILURE
- Return code: 0016
- Error message: A tool used by tp broke down
Notes on phase IMPORT_OBJECT_LIST
In this phase the object lists for the Support Packages in the queue are
imported into the system. This phase can terminate due to the following
reasons:
o TP_INTERFACE_FAILURE: The tp interface could not be called.
o TP_FAILURE: The program tp could not be executed. For more
information on this, see the SLOG or ALOG log file.
o COMMAND_FILE_IMPORT_FAILURE: The object list of one or more Support
Packages could not be imported. For the cause of the error, see the
log of the command file import.
A prerequisite of the Support Package Manager is that the Change and
Transport System (CTS) is configured correctly. For more detailed
information, read the online documentation available from Help -> SAP
Library -> mySAP Technology Components -> SAP Web Application Server ->
Change and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.
<b>Support Package Error Logfile:</b>
1 ETP176 IMPORT OF COMMANDFILE ONLY
1 ETP101 transport order : "SAPKIAF506"
1 ETP102 system : "AFT"
1 ETP108 tp path : "tp"
1 ETP109 version and release : "340.07" "640"
1 ETP198
4 ETW000 R3trans.exe version 6.09 (release 640 - 28.04.04 - 16:14:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 14.03.2007 - 10:08:21
4 ETW000 control file: D:\usr\sap\trans\tmp\SAPKKIAF506.AFT
4 ETW000 > #pid 1352 on AFTHOST (APServiceAFT)
4 ETW000 > import
4 ETW000 > buffersync=yes
4 ETW000 > file='D:\usr\sap\trans\data\RIAF506.SAP'
4 ETW000 > continuation='D:\usr\sap\trans\data\RIAF506_#.SAP'
4 ETW000 > client cascade yes
4 ETW000 > repeatimport=yes
4 ETW000 >
4 ETW000 > including 'NOTHING'
4 ETW000 R3trans was called as follows: R3trans.exe -w D:\usr\sap\trans\tmp\SAPLIAF506.AFT D:\usr\sap\trans\tmp\SAPKKIAF506.AFT
4 ETW000 Connected to DBMS = MSSQL --- SERVER = 'afthost' DBNAME = 'AFT' --- SYSTEM = 'AFT'.
4 ETW690 "0" "0"
4 ETW000 COMMIT (0).
4 ETW000 trace at level 1 opened for a given file pointer
4 ETW000
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time : 14.03.2007 - 10:08:21
4 ETW000 function : IMPORT
4 ETW000 data file : D:\usr\sap\trans\data\RIAF506.SAP
4 ETW000 Continuation: D:\usr\sap\trans\data\RIAF506_#.SAP
4 ETW000 buffersync : YES
4 ETW000 clients : cascade
4 ETW000 repeatimport: YES (corresponds to unconditional mode 1)
4 ETW000 repeatclimp.: NO
4 ETW000 c.s.i. : NO
4 ETW000 l.s.m. : VECTOR
4 ETW000 charsetadapt: YES
4 ETW000 def. charset: WEUROPEAN
4 ETW000 commit : 100000
4 ETW000 table cache : dynamic
4 ETW000 INCLUDING : 'NOTHING'
4 ETW000
4 ETW000 rejected clients : 066
4 ETW000
4 ETW000 client cascade to: 000, 001, 100, 111, 300, 333
4 ETW000 Character set on this machine : ASCII (ISO 8859-1).
4 ETW000 Character set on the data file: 2 byte unicode big endian.
4 ETW000 Data file is compressed with algorithm 'L'.
4 ETW000 Export was executed on 27.06.2006 at 10:22:59 by hm3adm
3 ETW709 "640 "
4 ETW000 with R3trans version: 13.02.06 - 15:46:42
4 ETW000 Source System = SUN on SPARC CPU with Solaris 2.2 on DBMS = DB6 --- DB2DBDFT = 'HM3' --- SYSTEM = 'HM3'.
4 ETW000
4 ETW000 language vector during export: DESFIJ3TM1PN
4 ETW000 lsm during export: ALL
4 ETW000 trfunction = D (patch transport)
4 ETW000 .--============--
4 ETW000 | RSCP - Error |
4 ETW000 | Error from: Codepage handling (RSCP) |
4 ETW000 | code: 8 RSCPEIO Some I/O error. |
4 ETW000 | dbrtab error 16 in rscpddio__direct_db_io |
4 ETW000 | module: rscpgdio no: 14 line: 1515 T100: TS004 |
4 ETW000 | TSL01: F6H p3: XRTAB&0&16&UMGSETTING & |
4 ETW000 |----
|
4 ETW000 | Error propagation from: Primary key table access (RTAB) |
4 ETW000 | RTAB error 16 |
4 ETW000 | table UMGSETTING |
4 ETW000 | db key UNICONV |
4 ETW000 |----
|
4 ETW000 | Some OS information, which may or may not belong to this error: |
4 ETW000 | errno 2 No such file or directory |
4 ETW000 `----
1AETW000 ===> HALT: GetDBMigrateCodePagesLangs fails with rc=8 (twconv.c:888) Please contact the SAP support.
4 ETW000 [dev trc ,00000] Rollback Work (0) 90088 0.090088
4 ETW000 ROLLBACK (1470).
4 ETW000 End of Transport (0016).
4 ETW000 date&time: 14.03.2007 - 10:08:21
1 ETP176 IMPORT OF COMMANDFILE ONLY
1 ETP110 end date and time : "20070314100821"
1 ETP111 exit code : "16"
1 ETP199 ######################################
1 ETP199X######################################
1 ETP176 IMPORT OF COMMANDFILE ONLY
1 ETP101 transport order : "SAPKIAF506"
1 ETP102 system : "AFT"
1 ETP108 tp path : "tp"
1 ETP109 version and release : "340.07" "640"
1 ETP198
4 ETW000 R3trans.exe version 6.09 (release 640 - 28.04.04 - 16:14:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 14.03.2007 - 10:09:37
4 ETW000 control file: D:\usr\sap\trans\tmp\SAPKKIAF506.AFT
4 ETW000 > #pid 3148 on AFTHOST (APServiceAFT)
4 ETW000 > import
4 ETW000 > buffersync=yes
4 ETW000 > file='D:\usr\sap\trans\data\RIAF506.SAP'
4 ETW000 > continuation='D:\usr\sap\trans\data\RIAF506_#.SAP'
4 ETW000 > client cascade yes
4 ETW000 > repeatimport=yes
4 ETW000 >
4 ETW000 > including 'NOTHING'
4 ETW000 R3trans was called as follows: R3trans.exe -w D:\usr\sap\trans\tmp\SAPLIAF506.AFT D:\usr\sap\trans\tmp\SAPKKIAF506.AFT
4 ETW000 Connected to DBMS = MSSQL --- SERVER = 'afthost' DBNAME = 'AFT' --- SYSTEM = 'AFT'.
4 ETW690 "0" "0"
4 ETW000 COMMIT (0).
4 ETW000 trace at level 1 opened for a given file pointer
4 ETW000
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time : 14.03.2007 - 10:09:38
4 ETW000 function : IMPORT
4 ETW000 data file : D:\usr\sap\trans\data\RIAF506.SAP
4 ETW000 Continuation: D:\usr\sap\trans\data\RIAF506_#.SAP
4 ETW000 buffersync : YES
4 ETW000 clients : cascade
4 ETW000 repeatimport: YES (corresponds to unconditional mode 1)
4 ETW000 repeatclimp.: NO
4 ETW000 c.s.i. : NO
4 ETW000 l.s.m. : VECTOR
4 ETW000 charsetadapt: YES
4 ETW000 def. charset: WEUROPEAN
4 ETW000 commit : 100000
4 ETW000 table cache : dynamic
4 ETW000 INCLUDING : 'NOTHING'
4 ETW000
4 ETW000 rejected clients : 066
4 ETW000
4 ETW000 client cascade to: 000, 001, 100, 111, 300, 333
4 ETW000 Character set on this machine : ASCII (ISO 8859-1).
4 ETW000 Character set on the data file: 2 byte unicode big endian.
4 ETW000 Data file is compressed with algorithm 'L'.
4 ETW000 Export was executed on 27.06.2006 at 10:22:59 by hm3adm
3 ETW709 "640 "
4 ETW000 with R3trans version: 13.02.06 - 15:46:42
4 ETW000 Source System = SUN on SPARC CPU with Solaris 2.2 on DBMS = DB6 --- DB2DBDFT = 'HM3' --- SYSTEM = 'HM3'.
4 ETW000
4 ETW000 language vector during export: DESFIJ3TM1PN
4 ETW000 lsm during export: ALL
4 ETW000 trfunction = D (patch transport)
4 ETW000 .--============--
4 ETW000 | RSCP - Error |
4 ETW000 | Error from: Codepage handling (RSCP) |
4 ETW000 | code: 8 RSCPEIO Some I/O error. |
4 ETW000 | dbrtab error 16 in rscpddio__direct_db_io |
4 ETW000 | module: rscpgdio no: 14 line: 1515 T100: TS004 |
4 ETW000 | TSL01: F6H p3: XRTAB&0&16&UMGSETTING & |
4 ETW000 |----
|
4 ETW000 | Error propagation from: Primary key table access (RTAB) |
4 ETW000 | RTAB error 16 |
4 ETW000 | table UMGSETTING |
4 ETW000 | db key UNICONV |
4 ETW000 |----
|
4 ETW000 | Some OS information, which may or may not belong to this error: |
4 ETW000 | errno 2 No such file or directory |
4 ETW000 `----
1AETW000 ===> HALT: GetDBMigrateCodePagesLangs fails with rc=8 (twconv.c:888) Please contact the SAP support.
4 ETW000 [dev trc ,00000] Rollback Work (0) 88800 0.088800
4 ETW000 ROLLBACK (1470).
4 ETW000 End of Transport (0016).
4 ETW000 date&time: 14.03.2007 - 10:09:38
1 ETP176 IMPORT OF COMMANDFILE ONLY
1 ETP110 end date and time : "20070314100938"
1 ETP111 exit code : "16"
1 ETP199 ######################################
1 ETP199X######################################
1 ETP179 CREATE COFILE FROM DATAFILE
1 ETP101 transport order : "SAPKIAF506"
1 ETP102 system : "AFT"
1 ETP108 tp path : "tp"
1 ETP109 version and release : "340.07" "640"
1 ETP198
4 ETW000 R3trans.exe version 6.09 (release 640 - 28.04.04 - 16:14:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 14.03.2007 - 12:08:33
4 ETW000 control file: D:\usr\sap\trans\tmp\SAPKKIAF506.AFT
4 ETW000 > #pid 4020 on AFTHOST (APServiceAFT)
4 ETW000 > createcofile
4 ETW000 > file='D:\usr\sap\trans\data\RIAF506.SAP'
4 ETW000 >
4 ETW000 R3trans was called as follows: R3trans.exe -w D:\usr\sap\trans\tmp\SAPLIAF506.AFT D:\usr\sap\trans\tmp\SAPKKIAF506.AFT
4 ETW000 trace at level 1 opened for a given file pointer
4 ETW000
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time : 14.03.2007 - 12:08:34
4 ETW000 function : CREATECOFILE
4 ETW000 data file : D:\usr\sap\trans\data\RIAF506.SAP
4 ETW000 buffersync : NO
4 ETW000 clients : default
4 ETW000 l.s.m. : VECTOR
4 ETW000 commit : -1
4 ETW000 table cache : dynamic
4 ETW000
4 ETW000 Character set on this machine : ASCII (ISO 8859-1).
4 ETW000 Character set on the data file: 2 byte unicode big endian.
4 ETW000 Data file is compressed with algorithm 'L'.
4 ETW000 Export was executed on 27.06.2006 at 10:22:59 by hm3adm
3 ETW709 "640 "
4 ETW000 with R3trans version: 13.02.06 - 15:46:42
4 ETW000 Source System = SUN on SPARC CPU with Solaris 2.2 on DBMS = DB6 --- DB2DBDFT = 'HM3' --- SYSTEM = 'HM3'.
4 ETW000
4 ETW000 language vector during export: DESFIJ3TM1PN
4 ETW000 lsm during export: ALL
4 ETW000 trfunction = D (patch transport)
3 ETW692 "SAPKIAF506 "
3 ETW708 "000"
3 ETW695 "D"
3 ETW694 "SAP "
3 ETW693 "PAUSER "
3 ETW696 "20060627"
3 ETW713 "P3A V500: patch 0006, CRT for SAPKH50010 - 12 "
3 ETW691 "CORRMERGMERGEINFO HM3 20060627 102016 "
3 ETW707 "CORRMERGMERGEINFO HM3 20060627 102016 "
3 ETW691 "LIMUCUAD/AFS/ARUN_SELSET_REORG "
3 ETW707 "R3TRPROG/AFS/ARUN_SELSET_REORG"
3 ETW691 "LIMUCUADPP_ORDER_PROGRESS "
3 ETW707 "R3TRPROGPP_ORDER_PROGRESS"
R3 Trans and tp Version
C:\Documents and Settings\aftadm>tp -v
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
This is tp version 340.07 (release 640)
tp information
kernel release 640
kernel make variant 640_REL
DBMS client library SQL_Server_8.00
DBSL shared library version 640.00
compiled on NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
compilation mode Non-Unicode
compile time Jul 14 2004 19:38:55
update level 0
patch number 3
source id 0.026
supported environment
database (SAP, table SVERS) 610
620
630
640
operating system
Windows NT 5.0
Windows NT 5.1
Windows NT 5.2
tp patch information
( 0.003) Restart after error in transport request independent step (note 686580)
( 0.003) Dd activation ends with returncode 8 although there's no error (note 69
4062)
dbsl patch information
( 0.001) MSSQL: TOP n for dynamic statements (note 699014)
( 0.003) MSSQL: R3load exports too few records (note 705088)
( 0.003) MSSQL: error handling on DBCON-connect (note 705674)
( 0.007) MSSQL: Row handles must all be released (note 719273)
( 0.016) MSSQL: BindInputParams: The parameter is invalid (note 731265)
( 0.017) MSSQL: SQL 2005 SNAC Support (note 734034)
( 0.022) MSSQL: Security issue (note 744948)
( 0.025) MSSQL: $DBCMD command (note 751269)
( 0.026) MSSQL: GetNextMsst1 error (note 754819)
C:\Documents and Settings\aftadm>r3trans -v
This is r3trans version 6.09 (release 640 - 28.04.04 - 16:14:00).
R3trans information
kernel release 640
kernel make variant 640_REL
DBMS client library SQL_Server_8.00
DBSL shared library version 640.00
compiled on NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
compilation mode Non-Unicode
compile time Jul 14 2004 19:38:55
update level 0
patch number 19
source id 0.026
supported environment
database (SAP, table SVERS) 610
620
630
640
operating system
Windows NT 5.0
Windows NT 5.1
Windows NT 5.2
R3trans patch information
( 0.001) Code pages patch packet 313233 (note 447519)
( 0.001) Code pages patch packet 34 (note 695907)
( 0.003) Deletion in language dependent table (note 337224)
( 0.009) Unicode: Core Dump in build_initrec, Modul dbntab (note 717717)
( 0.009) Avoid duplicate key errors due to scrap characters (note 718511)
( 0.009) Protect customer's table entries (note 530335)
( 0.011) Wrong error message: Value of key specification field (note 720329)
( 0.013) Code pages, languages and locales, packet 37 + 38 (note 447519)
( 0.013) Code pages, languages and locales, packet 37 + 38 (note 722638)
( 0.019) Code pages patch packet 40 (NT) (note 447519)
( 0.019) Code pages patch packet 40 (NT) (note 447519)
dbsl patch information
( 0.001) MSSQL: TOP n for dynamic statements (note 699014)
( 0.003) MSSQL: R3load exports too few records (note 705088)
( 0.003) MSSQL: error handling on DBCON-connect (note 705674)
( 0.007) MSSQL: Row handles must all be released (note 719273)
( 0.016) MSSQL: BindInputParams: The parameter is invalid (note 731265)
( 0.017) MSSQL: SQL 2005 SNAC Support (note 734034)
( 0.022) MSSQL: Security issue (note 744948)
( 0.025) MSSQL: $DBCMD command (note 751269)
( 0.026) MSSQL: GetNextMsst1 error (note 754819)
Thanks in advanceHello Ismail
Update your versions of TP and R3trans and the SAP Kernal and retry the import.
The versions you have are from 2004.
Thanks
Kenny -
Transport classes and programs to another server
Except for transport routing and charm copy function, do we have other ways to do so?
for example copy or so forth.
best regards,
Blake LeHi Blake
SAP R/3 Correction and Transport System
Operating system level files in the transport process:
The SAP C program TP, requires a special file structure for the transport process. The file system is operating system dependent. TP uses a transport directory or file system, which is called /usr/sap/trans.
The /usr/sap/trans file system is generally NFS mounted form the development system to other systems unless a system is defined as a single system in the CTS pipeline. All the sub directories should have <SID>adm as the owner and sapsys as the group; and proper read, write and execute access should be given to owner and the group. The TP imports are always performed by <SID>adm.
The following are the subdirectories in /usr/sap/trans:
/data
/cofiles
/bin
/log
/actlog
/buffer
/sapnames
/tmp
/usr/sap/trans/data: holds the data of transport objects after they are released . The example of a data file is R904073.DEV. The extension DEV means the data file was released from the DEV or development system.
/usr/sap/trans/cofiles: The cofiles directory holds the command files for all change requests. These files are like a command or control files used to import the data files. The common directory for CTS system is /usr/sap/trans. After a change request is released from the source system , the data is exported immediately to the file system of the operating system. The SAP transport utility TP uses the cofile to transport a data file. The example of a file in cofiles directory is K904073.DEV.
/usr/sap/trans/bin: holds the most important file TPPARAM in the CTS system. TPPARAM file has all the information about the CTS systems in the CTS pipeline. TPPARAM file is the parameter file for the transport program TP and it is the common file for all the systems in the CTS pipeline. As you know already that /usr/sap/trans should be NFS mounted to all the systems in a CTS pipeline, TP program has access to the TPPARAM file from all the systems. The following is an example of typical TPPARAM file for five SAP systems in the CTS pipeline:
#@(#) TPPARAM.sap 20.6 SAP 95/03/28
Template of TPPARAM for UNIX #
First we specify global values for some parameters, #
later the system specific incarnation of special parameters #
global Parameters #
transdir = /usr/sap/trans/
dbname = $(system)
alllog = ALOG$(syear)$(yweek)
syslog = SLOG$(syear)$(yweek).$(system)
System spezific Parameters #
Beispiel T11 #
DEV/dbname = DEV
DEV/dbhost = sap9f
DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
QAS/dbname = QAS
QAS/dbhost = sap8f
QAS/r3transpath = /usr/sap/QAS/SYS/exe/run/R3trans
TRN/dbname = TRN
TRN/dbhost = sap17
TRN/r3transpath = /usr/sap/TRN/SYS/exe/run/R3trans
PRE/dbname = PRE
PRE/dbhost = sap19f
PRE/r3transpath = /usr/sap/PRE/SYS/exe/run/R3trans
PRD/dbname = PRD
PRD/dbhost = sap18f
PRD/r3transpath = /usr/sap/PRD/SYS/exe/run/R3trans
/usr/sap/trans/log: holds the entire log files, trace files and statistics for the CTS system. When the user goes to SE09 (workbench organizer) or SE10 (customizing organizer) transaction and opens the log for a transport, the log file for that transport will be read from /usr/sap/trans/log directory. Each change request should have a log file. Examples of log files are DEVG904073.QAS, DEVI904073.QAS and DEVV904073.QAS. The name of a log file consists of the names of the change request, the executed step, and the system in which the step was executed:
<source system><action><6 digits>.<target system>
Now we can analyze the above example DEVG904073. QAS. The <source system> = DEV, <action> = G or report and screen generation, <6 digits> = 904073 (these six digits numbers are exactly the same number as the six digits of the transport) and the <target system> = QAS
Possible values for <action> are:
A: Dictionary activation
D: Import of application-defined objects
E: R3trans export
G: Report and screen generation
H: R3trans dictionary import
I: R3trans main import
L: R3trans import of the command files
M: Activation of the enqueue modules
P: Test import
R: Execution of reports after put (XPRA)
T: R3trans import of table entries
V: Set version flag
X: Export of application-defined objects.
/usr/sap/trans/actlog: holds action log files. The example of an action file is DEVZ902690.DEV. The following are the contents of the file:
1 ETK220 u201C==================================================u201D u201C=================
=============================
1 ETK191 u201C04/30/1998u2033 Action log for request/task: u201CDEVK902690u2033
1 ETK220 u201C==================================================u201D u201C=================
=============================
1 ETK185 u201C04/30/1998 18:02:32u2033 u201CMOHASX01u2033 has reincluded the request/task
4 EPU120 Timeu2026 u201C18:02:32u2033 Run timeu2026 u201C00:00:00u2033
1 ETK193 u201C04/30/1998 18:02:33u2033 u201CMOHASX01u2033 owner, linked by u201CMOHASX01u2033 to u201CDEVK902691u2033
4 EPU120 Timeu2026 u201C18:02:33u2033 Run timeu2026 u201C00:00:00u2033
1 ETK190 u201C05/04/1998 11:02:40u2033 u201CMOHASX01u2033 has locked and released the request/task
1 ETK194 u201C05/04/1998 11:02:40u2033 **************** End of log *******************
4 EPU120 Timeu2026 u201C11:02:40u2033 Run timeu2026 u201C00:00:09u2033
~
~u201DDEVZ902690.DEVu201D 10 lines, 783 characters
/usr/sap/trans/buffer: transport buffer of the target systems; contains control information on which requests are to be imported into which systems and in what order the imports must occur. The /usr/sap/trans/buffer will have a directory for each system in the CTS pipeline. For example the buffer file for DEV system is /usr/sap/trans/buffer/DEV.
/usr/sap/trans/sapnames: holds information pertaining to transport requests for each system user. There are files for each user who released change requests from the system.
/usr/sap/trans/tmp: holds information about temporary data and log files. While the transport is occurring the Basis administrator can find a file that is related to the transport in the tmp directory; that file shows the exact status if the transport (What objects are being imported at that time).
Important SAP delivery class and table types and tables in the CTS process:
Delivery class
The delivery class defines who (i.e. the SAP system itself or the customer) is responsible for maintaining the table contents. In addition the delivery class controls how the table behaves in a client copy and an upgrade. For example when you select a SAP defined profiles to perform a client copy, certain tables are selected according to their delivery class. DD02L table can show what delevery class a table belongs to.
The following delivery classes exist:
A: Application table.
C: Customizing table, maintenance by customer only.
L: Table for storing temporary data.
G: Customizing table, entries protected against overwriting.
E: Control table.
S: System table, maintenance only by SAP.
W: System table, contents can be transported via own TR objects.
Table type
The table type defines whether a physical table exists for the logical table description defined in the ABAP/4 Dictionary and how the table is stored on the database.
The following are different table types in SAP:
Transparent Tables
There is a physical table on the database for each transparent table. The names of the physical table and the logical table definition in the ABAP/4 Dictionary are same. For every transparent table in SAP, there is a table in database. The business and application data are stored in transparent tables.
Structure
No data records exist on the database for a structure. Structures are used for the interface definition between programs or between screens and programs.
Append Structure
An Append structure defines a subset of fields which belong to another table or structure but which are treated as a separate object in the correction management. Append structures are used to support modifications.
The following table types are used for internal purposes, for example to store control data or for continuous texts:
Pooled table
Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated-pooled tables are stored.
Cluster table
Cluster tables contain continuous text, for example documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least part of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
Tables in CTS process:
TRBAT and TRJOB:
TRJOB and TRBAT are the major tables in the CTS process. After TP program has sent the event to the r3 system, RDDIMPDP checks table TRBAT in the target system to find out if there is an action to be performed. Mass activation, distribution, or table conversions are the examples of actions. If there is action to be performed, RDDIMPDP starts the appropriate program in the background task. RDDIMPDP then reschedules itself.
By checking table TRJOB, RDDIMPDP automatically recognizes if a previous step was aborted, and restarts this step. For each transport request , TP program inserts an entry into table TRBAT. If the return code 9999 in this table then the step is waiting to be performed. Return code 8888 indicates that the step is active and currently being processed. A return code of 12 or less indicates that the step is finished. In addition, TP inserts a header entry to let the RDDIMPDP program know to start processing. The column return code will therefore contain a B for begin. When RDDIMPDP is started, it sets the header entry to R(un), and starts the required program. When all the necessary actions are performed for all the transport requests, the column return code contains all the return codes received, and the column TIMESTAMP contains the finishing time. The header entry is set to F(inished). TP monitors the entries in TRBAT and TRJOB tables. When the header entry in TRBAT is set to finished. The entry in TRJOB is deleted.
Transport Tables SE06
TDEVC - Development classes
TASYS - Details of the delivery. Systems in the group that should automatically receive requests, have to be specified in table TASYS.
TSYST - The transport layers will be assigned to the integration systems. ( Define all systems)
TWSYS - Consolidation routes ( define consolidation path)
DEVL - Transport layers are defined here
In u201CConfiguring the CTS systemu201D section, We will learn more about the transport tables in SE06 transaction
Programs in the CTS process:
In the CTS table section we learned about the RDDIMPDP program. RDDIMPDP program needs to be scheduled in all the clients in an instance. It is recommended to schedule the RDDIMPDP as event driven.
RDDPUTPP and RDDNEWPP programs can be used to schedule RDDIMPDP program in the background.
The ABAP/4 programs that RDDIMPDP starts are determined by the transport step to be executed that is entered in the function field of table TRBAT.
Function Job Name Description of transport Steps
J RDDMASGL Activation of ABAP/4 dictionary objects
M RDDMASGL Activation of match codes and lock objects
S RDDDISOL Analysis of database objects to be converted
N RDDGENOL Conversion of database objects
Y RDDGENOL Conversion of matchcode tables
X RDDDICOL Export of AD0 objects
D RDDDIC1L Import of AD0 objects
E RDDVERSE Version management update during export
V RDDVERSL Version management update during import
R RDDEXECL Execution of programs for post - import processing
G RDDDIC3L Generation of ABAP/4 programs and screens
Version Management:
One of the important features of Workbench Organizer is Version Management. This feature works for all the development objects. Using the version management feature the users can compare and retrieve previous versions of objects.
Version management provides for comparisons, restore of previous versions, documentation of changes and assistance in the adjustment of data after upgrading to a new release. With the release of a change request, version maintenance is automatically recorded for each object. If an object in the system has been changed N times, it will have N delta versions and one active version. To display version management, for ABAPs use transaction SE38 and for tables, domains and data elements use SE11. The path to follow is Utilities -> Display version. Using version management the users can view existing version for previously created ABAP code, make changes to the code, compare code versions and restore original version of the code. Now the users will be restore previous versions without cut and paste steps of the past.
TP and R3trans program:
The basis administrator uses TP program to transport SAP objects from one system to another. TP is a C program delivered by SAP that runs independently of the R/3 system. TP program uses the appropriate files located in a common transport directory /usr/sap/trans. TP starts C programs, ABAP/4 programs and special operating system commands to its job. R3trans is one of the most important utility program called by TP. Before using the TP program, the basis administrator needs to make sure that the CTS system is setup properly and the right version of TP is running in the system. The TP program is located in the run time directory /usr/sap/<SID>/SYS/exe/run directory. It is automatically copied in the install process. A global parameter file TPPARAM that contains the databases of the different target systems and other information for the transport process controls TP. The global parameter file determines which R3trans is used for each system. If the parameter r3transpath is not defined properly then no export and import can be done. The basis administrator should make sure that the default value u201Cr3transpathu201D is properly defined. Later in this chapter we will learn more about TP and R3trans; also we are going to see how they are used.
Configuring the TPPARAM file:
Each time TP is started, it must know the location of the global parameter file. As we have seen before TPPARAM file should be in directory /usr/sap/trans/bin. The parameters in TPPARAM can either global (valid for each and every system in the cts pipeline) or local to one system. Th parameters are either operating system dependant (these parameters preceded by a keyword corresponding to the specific operating system) or database dependant (contain a keyword corresponding to a specific database system).
The global parameter file provides variables that can be used for defining parameters. The variables can be defined in format: $(xyz). The brackets can be substituted with the u201C\u201D-character if required.
The following pre-defined variables are available for the global parameter file:
$(cpu1): The CPU name can be sun or as4 for example. In heterogeneous networks this variable is very important.
$(cpu2): Acronym for the name of the operating system. The example for this variable can be
hp-ux, or sunos . This is an operating system specific variable.
$(dname): Used for the day of the week (SUN,MON,u2026.).
$(mday): Used for the day of the current month (01-31).
$(mname): Used for the name of the month (JANu2026DEC).
$(mon): Used for the Month (01-12).
$(system): R/3 System name.
$(wday): Day of the week (00-06, Sunday=00, Monday=01, Tuesday=02 and so on).
$(yday): Day of the current year (001-366). Using the number any day of the year can be chosen.
$(year): Year (Example:1998 or 1999).
$(syear): Short form of the year (two positions).
$(yweek): Calendar week (00-53). The first week begins with the first Sunday of the year.
For the database connection:
The transport environment also needs parameters to connect to the R/3 System database. As we know already the every instance in the R/3 CTS pipeline has its own database, therefore specific parameters should be defined for each database system. From dbtype parameter of RSPARAM file, TP program identifies the database system.
The two parameters u201Cdbnameu201D and u201Cdbhostu201D are required for ORACLE databases.
DBHOST: is the name of the computer on which the database processes execute. TCP/IP name of the host if NT is being used.
DBNAME: is the name of the database instance.
As of Release 3.0E, two new parameters have been introduced.
DBLOGICALNAME: The default value is $(system). The logical name that was used to install the database.
DBCONFPATH: The default value is $(transdir).
The parameters u201Cdbnameu201D and u201Cdbhostu201D are also used for INFORMIX databases in an installation:
DBHOST: Same as Oracle.
DBNAME: Name of the database instance, uppercase and lowercase are distinguished here.
INFORMIXDIR : u201C/informix/<SAPSID>u201D is the default value. Defines the directory namewhere the database software can be found.
INFORMIXSQLHOSTS: u201C$(informixdir)/etc/sqlhosts[.tli|.soc]u201Cis default value under Unix. The name of the SQLhosts file with its complete path is defined with this parameter.
INFORMIX_SERVER: u201C$(dbhost)$(dbname)shmu201D is the default value. The name of the database server may be specified for a local connect.
INFORMIX_SERVERALIAS: u201C$(dbhost)$(dbname)tcpu201Dis the default vlue. The name of the database server can be specified for a remote connect.
For Microsoft SQL Server database the two parameters u201Cdbnameu201D and u201Cdbhostu201D are also required. DBHOST: The TCP/IP name of the host on which the database is running.
DBNAME: The database instance name.
For DB2 in AS/400 only u201Cdbhostu201D is required.
DBHOST: System name of the host on which the database is running.
If theu201DOptiConnectu201D is used, the following line should be specified:
OPTICONNECT 1
For DB2/ AIX
The two parameters u201Cdbnameu201D and u201Cdbhostu201D are required
DBHOST: The host on which the database processes are running. It is the TCP/IP name of the host for Windows NT (As we have seen in the earlier examples).
DBNAME: Database instance name.
The DB2 for AIX Client Application Enabler Software must also be installed on the host on which tp is running.
ALLLOG: u201CALOGu201D $(syear) $(yweek)u201Dis the default value. This variable can be used in TPPARAM file to specify the name of a file in which tp stores information about every transport step carried out for a change request anywhere in the transport process. The file always resides in the log directory.
SYSLOG: u201CSLOG $(syear) $(yweek).$(system)u201D is the default value. This variable can be used to name a file in which tp stores information about the progress of import actions in a certain R/3 System. The file does not store information for any particular change request. The file always resides in the log directory.
tp_VERSION: Zero is the default value. If this parameter is set to not equal to zero, a lower version of tp may not work with this TPPARAM file. If the default value (zero) is set, the parameter has no affect.
STOPONERROR: (Numeric value) The default value is 9. When STOPONERROR is set to zero, tp is never stopped in the middle of an u201Cimportu201D or u201Cputu201D call. When STOPONERROR is set to a value greater than zero, tp stops as soon as a change request generates a return code that is equal to or greater than this value (The numeric value of the STOPONERROR parameter is stored in the variable BADRC). Change requests, which still have to be processed for the current step, are first completed. A u201CSYNCMARKu201D in the buffer of the R/3 System involved, sets a limit here. tp divides the value of this parameter between two internal variables. STOPONERROR itself is treated as a boolean variable that determines whether tp should be stopped, if the return code is too high.
REPEATONERROR (Numeric value too): The default value is 9. The REPEATONERROR parameter is similar to STOPONERROR. The difference is, REPEATONERROR specifies the return code up to which a change request is considered to be successfully processed. Return codes less than REPEATONERROR are accepted as u201Cin Orderu201D. Change requests that were not processed successfully stay in the buffer.
NEW_SAPNAMES: Default value is u201CFALSEu201D. A file is created for each user of the R/3 System group in the u201Csapnamesu201D subdirectory of the transport directory. Except some of the operating system,the name of the user is the name of the file. It is very important to remember hat the special characters or length of the file name could cause problems. If all the R/3 Systems in the transport group have at least Release level 3.0.; TP program is efficient to handle this problem. The user names are modified to create file names that are valid in all operating systems and the real user names are stored in a corresponding file.
Though we have seen so many parameters, for the minimum configuration the following two parameters are very important.
TRANSDIR: specifies the name of the common transport directory. The following is a typical example from TPPARAM of Unix as we have seen before.
transdir = /usr/sap/trans/
DBHOST: contains the name of the database host. In Windows NT environment, this is the TCP/IP host name. The following is an example in Unix:
DEV/dbname = DEV
DEV/dbhost = sap9f
DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
For TP, to control u2018Start and Stopu2019 command files and database in R/3 the following important parameters are specified in TPPARAM:
Parameters for the tp Function u201CPUTu201D: LOCK_EU (boolean) default value is u201CTRUEu201D. Though from version 3.1 onward the tp put command is used seldom in cts process still it is important to know how this parameter works. When u201Ctp putu201D is used, it changes the system change option . If the parameter is set to u201CFALSEu201D nothing gets changed. If the parameter is set to u201CTRUEu201D, the system change option is set to u201CObjects cannot be changedu201D at the beginning of the call, and gets changed back to its previous value at the end of the call. The u201Ctp putu201D command will give the exact status of the locking mechanism.
LOCKUSER (used as boolean value): Default value is u201CTRUEu201D. This parameter is about the user login while tp put call is executed. If this parameter is set to u201CFALSEu201D, no locking mechanism for the users takes affect. If this parameter is defined as u201CTRUEu201D then a character is set in the database level; so only DDIC and SAP* can log on to the system. Users that have already logged on are not affected (this is a reason for activating the parameters STARTSAP and STOPSAP). The charactertor is removed at the end of the call, and all the users can log on to the SAP R/3 System again.
STARTSAP: Default value is u201D u201C.or u201CPROMPTu201D for Windows NT . This parameter is used by TP to start an R/3 System. It is not necessary for the clients to make tp start and stop R/3 system..
STOPSAP: Default value is u201D u201Cor u201CPROMPTu201D for Windows NT. TP uses this parameter to stop an R/3 System.
STARTDB: Default value is u201D u201C. TP uses the value of this parameter to start the database of an R/3 System.
The parameter is not active under Windows NT.
STOPDB: Default value is u201D u201C. TP uses the value of this parameter to stop the database of an R/3 System.
This parameter is not active under Windows NT.
The above parameters in UNIX can be used as following:
STARTSAP = startsap R3
STOPSAP = stopsap R3
STARTDB = startsap db
STOPDB = stopsap db
In Windows NT:
STARTSAP =
$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\startsap.exe
R3 <SID> <HOST NAME> <START PROFILE>
STOPSAP =
$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\stopsap.exe
R3 <SID> <HOST NAME> <INSTANCE> <PROFILE PATH + Instance profile>
The parameters STARTDB and STOPDB are not active under Windows NT.
Parameters for the tp function u201CCLEAROLDu201D
DATALIFETIME (Numeric): Default value is u201C200u2033. When the data file has reached a minimum age, it is moved to the subdirectory old data with tp check. tp clearold all. The life span of the data files in the data sub directory can be set in days with this all, parameter.
OLDDATALIFETIME (Numeric): Default value is u201C365u2033. When a file located in the olddata subdirectory is no longer needed for further actions of the transport system and has reached a minimum age, it is removed with tp check.all, tp clearold all. The minimum age in days can be set with this parameter.
COFILELIFETIME (Numeric): Default value is u201C365u2033. This parameter is used just like DATALIFETIME parameter.
LOGLIFETIME (Numeric): Default value is u201C200u2033. This parameter applies to the life span of the log files. When the log files in log subdirectory is no longer needed for the transport system and has reached a minimum age, it is deleted with the calls tp check.all, tp clearold all. The minimum age in days can be defined with this parameter.
The Three Key Utilities of the CTS system (TP, R3trans and R3chop):
TP: Earlier in this chapter we have seen the objectives of TP. The TP transport control program is a utility program that helps the user to transport objects from one system to another. TP program is the front-end for the utility R3trans. TP stands for u201CTransports and Putsu201D. To make the TP work successfully the CTS system needs to be correctly configured. The following steps are very important for TP to run properly.
The transport directory /usr/sap/trans must be installed and NFS mounted to all the systems in the CTS pipe line.
RDDIMPDP program must be running (event driven is recommended) in each client. RDDIMPDP can be scheduled in the background by executing RDDNEWPP or RDDPUTPP. Use the tp checkimpdp <sap sid> command in /usr/sap/trans/bin directory as <sid>adm user to check RDDIMPDP program.
Use the tp connect <sap sid> command in /usr/sap/trans/bin directory to see whether the tp program is connecting to the database successfully or not. To run TP command the user has to logon as <sid>adm in source or target system.
The R/3 Systems in the CTS pipeline must have different names.
The Global CTS Parameter File TPPARAM must be correctly configured.
The source system (for the export) and target system ( for the import) must have at least two background work processes. TP always schedules the C class job, so if all the background jobs are defined as A class job then there will be problems in transport steps.
Important Tips :.It is always better to have the up to date TP version installed in your system. A user can ftp a current version of TP from SAPSERV4 of SAP. Though R3trans and other utility programs can be used to do the transport, it is recommended to use TP whenever possible for the following reasons..
The exports and imports are done separately using TP program. For example: when a transport is released from the system, the objects are exported from the source database to the operating system and then the import phase starts to transport those objects to the target system.
TP takes care of the order of the objects. The order, that was followed to export the objects; the same order will be followed to import them to the target database.
The TP command processes all change requests or transports in the SAP system buffer that have not yet been imported successfully. All the import steps are executed automatically after TP calls R3trans program to execute the following necessary steps:
Dictionary Import: ABAP/4 dictionary objects will be imported in this step.
Dictionary Activation: Name tabs or runtime descriptions will be written inactively. The R/3 system keeps running until the activation phase is complete. The enqueue modules are the exceptions in the running phase. After the activation of new dictionary structure the new actions are decided to get the runtime objects to the target system.
Structure conversion: If necessary the table structure is changed in this phase.
Move Nametabs: The new ABAP/4 Dictionary runtime objects which were inactive up to now are moved into the active runtime environment in this process. The database structures are adjusted accordingly. From the first step to the Main import step inconsistencies can occur to the R/3 system. After the main import phase all the inconsistency ca be solved.
Main import with R3trans: All the data are imported completely and the system comes to a consistent state.
Activation of enqueue-objects: The enqueue-objects cannot be activated in the same way as the objects of the ABAP/4 Dictionary, so they have to be activated after the main import in this step. They are then used directly in the running system.
Structure Conversion of match codes, Import application defined objects, versioning and execution of user defined activities are some of the steps after activation of enqueue-objects. The next step is generation of ABAP/4 programs and screens, where all the programs and screens associated with the change request are generated. When all the import steps are completed successfully, the transport request is removed from the import buffer.
It is recommended by SAP to schedule regular periods for imports into the target system (e.g. daily, weekly or monthly). Shorter periods between imports are not advisable. The transport to production should not be done in the off hours when the users are not working
TP can be started with different parameters. The u201Ctp helpu201D command can help user to generate a short description about the use of the command.
The following are the some important commands of TP:
For export:
tp export <change request>: The complete objects in the request from the source system will be transported. This command also used by SAP System when it releases a request.
tp r3e <change request>: R3trans export of one transport request.
tp sde <change request>: Application defined objects in one transport request can be exported.
tp tst <change request> <SAP system >: The test import for transport request can be done using this command.
tp createinfo <change request>: This command creates a information file that is automatically done during the export.
tp verse <request>: This command creates version creates versions of the objects in the specified request.
To Check the transport buffer, global parameter file and change requests:
tp showbuffer <sid>: Shows all the change requests ready to be imported to the target system.
tp count <sid>: Using this command users can find out the number of requests in the buffer waiting for import.
tp go <sid>: This command shows the environment variables needed for the connection to the database of the <sid> or target system.
tp showparams <sid>: All the values of modifiable tp parameters in the global parameter file. The default value is shown for parameters that have not been set explicitly.
To import the change requests or transports:
tp addtobuffer <request>.<sid>: If a change request is not in the buffer then this command is used to add it to the buffer, before the import step starts.
tp import all <sid>: This command imports all the change requests from the buffer to the target system.
tp put <sid>: The objective of this command is same as u201Ctp import all <sid>u201D, but this command locks the system. This command also starts and stops the SAP system, if the parameters startsap and stopsap parameters are not set to u201D u201C.
tp import <change request> <sid>: To import a single request from the source system to target system.
tp r3h <change request>| all <sid>: Using this command user can import the dictionary structures of one transport or all the transport from the buffer.
tp act <change request>|all <sid>: This command activates all the dictionary objects in the change request.
tp r3i <change request> | all <sid>: This command imports everything but dictionary structures of one.
tp sdi <change request>|all <sid>: Import application-defined objects.
tp gen <change request>|all <sid>: Screen and reports are generated using this command.
tp mvntabs <sid>: All inactive nametabs will be activated with this command.
tp mea <change request>|all <sid>: This command will activate the enqueue modules in the change request.
When you call this command, note the resulting changes to the import sequence.
Additional tp utility options:
tp check <sid>|all (data|cofiles|log|sapnames|verbose): User uses this command to find all the files in the transport directory that are not waiting for imports and they have exceeded the minimum time specified using the COFILELIFETIME, LOGFILELIFETIME, OLDDATALIFETIME and DATALIFETIME parameters of TPPARAM file.
tp delfrombuffer <request>.<sid>: This command removes a single change request from the buffer. In case of TMS, the request will be deleted from the import queue.
tp setstopmark <sid>: A flag is set to the list of requests ready for import into the target system. When the user uses the command tp import all <sapsid> and tp put <sapsid>, the requests in front of this mark are only processed. After all the requests in front of the mark have been imported successfully, the mark is deleted.
tp delstopmark <sid>: This command deletes the stop mark from the buffer if it exists.
tp cleanbuffer <sapsid>: Removes all the change requests from the buffer that are ready for the import into the target system.
tp locksys <sid>: This command locks the system for all the users except SAP* and DDIC. The users that have already logged on are not affected by the call.
tp unlocksys <sid>: This command unlocks the system for all the users.
tp lock_eu <sid>: This command sets the system change option to u201Csystem can not be changedu201D tmporarily.
tp unlock_eu <sid>: This command unlocks the system for all the changes.
tp backupall <sid>: This command starts a complete backup using R3trans command. It uses /usr/sap/trans/backup directory for the backup.
tp backup delta <sid>: Uses R3trans for a delta backup into /usr/sap/trans/backup directory.
tp sapstart <sid>: To start the R/3 system.
tp stopsap <sid>: To stop the R/3 system.
tp dbstart <sid>: To start the database.
tp dbstop <sid>: To stop the database.
Unconditional modes for TP: Unconditional modes are used with the TP program and these modes are intended for the special actions needed in the transport steps. Using unconditional mode user can manipulate the rules defined by the workbench organizer. The unconditional mode should be used when needed, otherwise it might create problems for the R/3 system database. Unconditional mode is used after the letter u201CUu201D in the TP command. Unconditional mode can be a digit between 0 to 9 and each has a meaning to it. The following is a example of a import having unconditional mode.
tp import devk903456 qas client100 U12468
0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.
1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.
2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.
3: When used with tp import, it overwrites the system-dependant objects.
5: During the import to the consolidation system it permits the source systems other than the integration system.
6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.
8: During import phase it ignores the limitations caused by the table classification.
9: During import it ignores that the system is locked for this kind of transport.
R3trans: TP uses R3trans program to transport data from one system to another in the CTS pipeline. efficient basis administrator can use R3trans directly to export and import data from and into any SAP systems. Using this utility transport between different database and operating system can e done without any problems. Different versions of R3trans are fully compatible with each other and can be used for export and import. The basis administrator has to be careful using R3trans for different release levels of R/3 software; logical inconsistency might occur if the up to date R3trans is not used for the current version of R/3 system.
The syntax for using the control file is following:
R3trans [<options>] <control file> (several options used at the same time; at least one option must be there)
For example: R3trans u2013u 1 u2013w test.log test
In the above example a unconditional mode is used, a log file u201Ctest.logu201D file is used to get the log result and a control file u201Ctestu201D, where the instructions are given for the R3trans to follow. The user needs to logon as <sid>adm to execute R3trans.
The following options are available for the R3trans program:
R3trans -d : This command is used to check the database connection .
R3trans -u <int>: Unconditional mode can be used as we have seen in the above example.
R3trans -v : This is used for verbose mode. It writes additional details to the log file
R3trans -i <file>: This command directly imports data from data file without a control file.
R3trans -l <file>: This provides output of a table of contents to the log file.
R3trans -n : This option provides a brief information about new features of R3trans.
R3trans u2013t: This option is used for the test mode. All modifications in the database are rolled back.
R3trans -c <f1> [<f2>]: This command is used for conversion. The <f1> file will be copied to <f2> file after executing a character set conversion to the local character set.
Important tips: Do not confuse the backup taken using R3trans with database backup. The backups taken using R3trans are logical backups of objects. In case something happens to the SAP system these backups can not be used for recovery. R3trans backups can be only used to restore a copy of a particular object that has been damaged or lost by the user.
R3trans -w <file>: As we have seen in the above example this option can be used to write to a log file. If no file is mentioned then trans.log is default directory for the log.
R3trans also can be used for the database backup.
R3trans u2013ba: This command is used for a complete backup. we will see in the next paragraph how to use
the control file for the backup.
R3trans u2013bd: This command is used for a delta backup if the user does not want a complete backup.
R3trans u2013bi: This option will display backup information.
The following are some of the examples of control files:
We have already learned how to use a command for the logical backup of the objects in the database. To get a complete backup the following example control file can be used.
backup all
file = /usr/sap/trans/backall
The option u201Cfile = u2026u201D is the name of the directory into which the data files are to be written. If you are taking a complete backup of DEV system then the backup file is going to look like u201CDEV.A000.bcku201D the next complete
Reward if useful
Regards
divya -
Re-importing Transport Request
Hi,
I think it's a basis question, but you might know the answer.
It's possible to import transport request which is already completely imported into production system, since I want to transport it to other client in production system.
Advance thanks.
Regards,
Balaji Viswanath.Hello,
Re-importing is possible as well in STMS as with parameter 'unconditional mode' of the tp-Tool. Use unconditional mode '1' to reimport when using tp from command line. In STMS, import the single request by positioning on the request in the import queue and using 'request -> import'. As Option in the following popup, choose 'Import request again'. You might have to add the Request to the import queue again manually, if it is no longer in the import queue.
regard, Kathrin! -
After transporting changes are not happening
Hi All,
As per the requirement we need a change in the pricing procedure ZJEXPS
(Export Sales Switch). We made the changes in transaction code V/08.
But after transporting the request to quality server, changes are not reflecting there.
I had checked the request number all the tasks are there and transport was completed with warning.
our consultant created another request and then also after transporting changes are not reflecting.
How it is happening particular to this request?
How to trace this? Kindly suggest me.
(Ours is two system landscape with master client 009 and quality client 007.I am trying to transport to 007)
Regards,
Nagendra.Hi
Check the import logs. If you are getting warnings that original objects cannot be replaced. You need to import the change request in unconditional mode. During performing imports select option, overwrite originals.
Some times the requests contain the objects, which are original to the target system, e.g SAP standard objects.
Check if this could help you.
Regards
Rahul -
Issues while transporting requests to an upgraded system
Hi all,
There is a development system which is upgraded.
prior to upgradation of this development system , we copied all the abap developments to a temporary system, where developments were done until development system is upgraded.
As of now , we are manually copying the changes done in temporary system to the upgraded development system,
i.e for ex; Manually copying the code of a program in temporary system to upgraded development system
Instead of manual copying of the developements/changes from Temporary system to development system, can we move the requests directly from
temporary system to development system.
Please let me know ,what are the issues raised while moving requests ( of programs,tables,scripts,smartforms..... e.t.c ) from temporary system to development system
Thanks in advance.There's a new 'check' that can be done when transporting CRs throughout your landscape. It is the unconditional mode "Ignore Invalid Component Version".
This feature (check the component version) was included with SAP_BASIS 702, so the tp checks the component version of the system where the transport was released (this information is included in the transport) and the component version of the system where the transport is going to be imported.
This component version check feature will check all the components version between source and target system. So before choosing the 'Ignore' option, please try to make sure that the software component version that the objects contained in the request belongs to, should be the same between the systems, to avoid any inconsistencies. It is recommended to transport request in systems which are on the same support level or use the same add-ons.
The component check is a hint that you will import a transport which come from a system which is different from the target system. It only checks the installed add-ons and support packages. This means if you have in the source system installed a add-on which is not present in the target system of the transport you should aware that you import no objects which depends on the add-on which is not present in the target system, the same point belongs also to different support package
releases. This option was implemented to reduce the risk of inconsistencies. If you import the transport please use transport option "ignore invalid component version".
This import option means that transport requests can be imported even if their component version does not match the current component version (including Support Package Level) of the system. This is the case if the component version of the system is either new (the Support Package Level
is higher than that of the export system) or too old (you first have to have imported the Support Packages before you can import the request). You should only use this option if you are sure that the content of the transport request is independent from the component version.
If it is required to avoid this check you could set transport parameter SP_TRANS_SYNC with value OFF and this check will be not performed from tp, but I would recommend to use import option "ignore invalid component version" before you would import the transport.
transport parameter SP_TRANS_SYNC = OFF.
Parameter SP_TRANS_SYNC is delivered ON by default.
This option will avoid the check of the component version.
Some notes regarding this feature:
1581638 - SAP component checks no longer working in TMS
1577714 - Transport requests in Check requirements phase
1650265 - TMS workflow: 'Ignore Invalid Component Version' missing
1742547 Information about component version check in TMS
1756116 TMS Component Check: Fix for excluded component logic
Maybe you are looking for
-
Itunes/Ipod with multiple Vista users - Problem
To set the stage - new Vista PC, shared by the family - so I set up individual ID's (thought that would prevent my kids from corrupting our stuff). Oh, and thought Vista was compatible......... On the admin account, which is where the iTunes Library
-
Losy images after importing Word document into RoboHelp 7 HTML
We imported a simple Word document into RoboHelp 7 HTML, as a new project (from scratch). Everything worked out pretty well (afterall, this was just a simple Word document), and we expect to have to tweak the styles, etc. That is understood. However,
-
Save Layer Visibility Settings
So, I have an Illustrator CS5 file with 30 different layers of artwork that I've been using to create PDF city maps. Is there a way that I can save layer visibility settings for each map? i.e. For one map, I want these 8 layers to be visible, for an
-
HT1750 How will i know if i have the latest 27" iMac
How will i know if i have the latest 27" Haswell imac here in the Philippines?
-
No me deja instalar el premiere
tengo adobe premiere y me sale este mensaje: El systema no es soportado para esta operacion Que quiere decir? despues sale de instalación con lo que no me deja continuar Tengo win 2000 profesional