Transport Control in SAP BPC 7.0 M

Hi,
We are an IT company with more than 250 reporting units.  We intend to implement SAP BPC 7.0 M in our organisation to unify our forecating and reporting process across reporting units. I gather that there is no transport tool available in BPC to transport from development to quality to production. I am curious to know if SAP has provided a best practice for controlling changes to production. What is the best method to ensure that an administrator or a developer does not incorrectly make changes in the production system?
  Also how do we convince our internal infra guys that changes have to be made directly in production? We have a central team for remote hosting all our systems and they have raised some following questions related to the security/disaster recovery aspects.
a. What is the backup and recovery procedure in case something happens to the production system.
b. Is there a best practice that I could refer to with respect to transports to convince them.
I am trying to prepare a document to convince them. I have got come inputs from sdn but I would really like an authoritative source to better understand this. Any answers/help would be highly appreciated!
Rgds
Shivram.

Hi Shivram,
for diaster recovery, you can just use the backup/restore functionality in BPC server manager. Where an admin can schedule it. Even you can use the SQL backup functionality, but if you use this you need to manually backup the fileshare folder.
Regarding Transports, yes when the project is already in production, it is a bit dangerous to use the backup/restore functionality as we will loss the production system data. So need to use the dev/QA system to develop and test it and later do the changes manually in production system. Before take a backup of production system, then you will be safe.
regards,
Sreedhar

Similar Messages

  • 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 while uploading Transport request from SAP ECC6.0 EHP4 to SAP ECC 5.0

    Hi friends,
    Error while uploading transport request to the transport directory,
    we downloaded the transport request from one sap system which have a set of developments(contains screen programs)
    for example downloaded all co files and data files
    control file: K900470.SAD and Data file: R900470.SAP from transport directory.
    we are trying to upload the transport to another Sap system
    we have
    Uploaded the controlling file K900470.sad to the location  /usr/sap/transpad/cofiles/
    Uploaded the controlling file R900470.sad to the location  /usr/sap/transpad/data/
    we tried to add in the import queues using TCODE: STMS and trying to import.
    During import we get the below error:
    HALT: unknown dynpro format: d021s_length() returned 0 Please contact the SAP support.
    End with rc : 16
    Please help me on this
    We are trying to copy from ECC 6.0 EHP4 to SAP 5.0 and SAP 4.7EE
    Thanks & Regards
    Murali Papana

    Did you see that you tried to transport to an older release!! You should have expected such a result.
    Before doing such a thing, you should have looked at SAP notes to see SAP recommendations, if any. And you're lucky, there are ones: [Note 1090842 - Composite note: Transport across several releases|http://service.sap.com/sap/support/notes/1090842]. You need to know that ECC6 corresponds to SAP Basis 7.0, and ECC5 corresponds to SAP Basis 6.40.

  • Test call of transport control program (tp) ended with return code 0200 Message no. TK094

    Hello Expert,
    My SAP System environment as follow
    SAP Product : SAP NetWeaver 04
    Operating System : Windows 2003 32 bit
    SAP Database : MS SQL 2005 32 bit
    I have installed SAP NetWeaver 04 system with system copy option. I have installed Application server & Database server on different physical server. App server : SSC2PAS3SFWBW and Database Server : SSC2PAS3SFSQW1.
    After SAP NetWeaver 04 installation with system copy I have done TMS configuration with virtual system for a test, It is working fine but while releasing request form SFD system (Development system) it get error  “Test call of transport control program (tp) ended with return code 0200. Message no. TK094”
    I have reconfigured the TMS and check but it can’t help. TR gets release and import with OS level but at SAP level it gets error.
    Trans --> Log
    1 ETP199 ######################################
    1 ETP199X######################################
    1 ETP182 CHECK WRITEABILITY OF BUFFERS
    1 ETP101 transport order     : "SFDK905838"
    1 ETP102 system              : "SFD"
    1 ETP108 tp path             : "tp"
    1 ETP109 version and release : "340.16.72" "640"
    1 ETP198
    2EETP128 No target system defined. "SFDK905838" is not a transport request.
    1 ETP182 CHECK WRITEABILITY OF BUFFERS
    1 ETP110 end date and time   : "20140602150208"
    1 ETP111 exit code           : "12"
    1 ETP199 ######################################
    Steps for Reconstruction                                            
    # Upgraded latest SAP Kernel Non-Unicode 640_Rel Patch level 404
    # Reconfigured the TMS
    # Full User Permission has been set to all SAP Directory.        
    Rgds,
    Ashok      

    Hi Ashish,
    I have removed virtual system form TMS and configured with Development & Production system, but the same error. Not able to release TR.
    SLOG as below.
    ERROR SFDK905832           SFD f 0012 20140602090930 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602093923 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602094059 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602102854 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602103633 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602104142 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602111140 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602112723 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113109 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113704 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113722 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113753 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113809 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905834           SFD f 0012 20140602125959 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905834           SFD f 0012 20140602130035 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    START EXPORT PREPARATION   SFD e      20140602132917              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    START tp_getprots          SFD E      20140602132917              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    STOP  tp_getprots          SFD E      20140602132920              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    STOP  EXPORT PREPARATION   SFD e      20140602132920              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    ERROR SFDK905836           SFD f 0012 20140602133526 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905836           SFD f 0012 20140602133540 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602144313 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602144350 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602144430 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602150202 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602150208 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603080634 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603081006 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603083952 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603084005 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603091608 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603091617 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905842           SFD f 0012 20140603091826 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603093805 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603101944 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603102709 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603114753 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603121948 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603122039 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603123438 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603135937 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603140114 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603140233 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603140339 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603141743 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603150924 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603152403 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603152753 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603153518 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162013 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162544 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162639 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162755 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603163347 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603163740 default_user A559420      SSC2PAS3SFWBW                    
    Rgds,
    Ashok

  • Transport control program tp ended with error code 0211

    Dear Experts,
    I have a problem in doing the import after the client export was successfully done.
    I am actaully tring to do a client import/export from the PRD server to DEV server.
    On PRD the client is 900 and on the DEV the client is 240.
    I have manually copied the transport requests created into the
    /usr/sap/trans/cofiles and /usr/sap/trans/data folders to the same on the DEV server.
    After coping them,
    I have tried to add these transport requests to the DEV server queue, i get the following error message
    Transport control program tp ended with error code 0211
    Message no. XT200
    Diagnosis
    An error occurred when executing a tp command.
      Command: ADDTOBUFFER RT2KT00014 RT1 pf=/usr/sap/trans/bin/T
      Return code: 0211
      Error text: no info about transport request found
      Request: RT2KT00014
    System Response
    The function terminates.
    Procedure
    Correct the error and execute the command again if necessary.
    After this I have tried to add the transports to the buffer at the OS level using the command
    ./tp pf=TPPARAM addtobuffer "RT2KT00014" RT1 U18 by going to the folder
    /usr/sap/trans/bin
    But it says that the tp is not found.
    I have also checked the permissions for the TRANS folder, it has full access i.e 777
    This is where i am struck, and the client has to be imported asap as the requirement for the SUPPORT TEAM is very urgent.
    We are on AIX, Oracle 10G and ECC6
    Thanks and regards
    Harry

    Dear Imtiaz,
    Thanks for your quick fire reply...
    The link helped me but it could not resolve my issue..
    Infact i found it my self that the transport requests had to be given full FILE PERMISSIONS at the OS level
    I logged in as ROOT
    and changed directory to /usr/sap/trans/cofile and gave the command
    chmod 777 RT00014.RT2 and
    chmod 777 RX00014.RT2
    and then went to STMS>SYSTEMS>Import View>Extras>Other requests--> Add ..
    Here i added the request nos and then it added up in the queue and then i started the import.
    Anyway thank you very for your reply..
    Awareded points to you.
    Thanks and regards
    Harry...

  • STMS: Transport control program tp ended with error code 0232

    Dear ERP Gurus,
    I just encountered problem with STMS in my PRD system. The import is just stuck up on "tp connecting to database". It won't continue unitl the system gives me this error message:
    Transport control program tp ended with error code 0232
    Errors: connect failed
    The tp System log says:
    ERROR: Connect to PRD failed (20090227135454, probably wrong environment)
    I have verified that the suggestion in SAP Note 165708 has already been implemented in our DEV, QAS, and PRD instances.
    Any idea why I am having this problem? Imports were running fine yesterday. Please help.
    Your prompt response is highly appreciated.
    Thanks a lot.
    Best Regards,
    Albert

    Hi Albert,
    First check import monitor and delete all requests from queue, which are still getting imported.
    And go to /usr/sap/trans/tmp and mv all those tmp files to other location.
    Then kill all OS jobs which are getting execute with tp.
    Check all jobs are runnig fine, related to transportation. If not reschedule the same.
    Then start importing.
    Before doing this just check whether your stms related RFCs are working fine.
    I think One of your RFC is getting struck. just try to change ip or hostname accordingly and try.
    Regards
    Nick Loy

  • Transport control program tp ended with error code 0232

    Dear all
    I've change password for user SAPSR3 by mistake
    the result from brtools is "password changed successfully in table OPS$CAPADM.SAPUSER for user SAPSR3"
    after that i can not transport to my production client
    with error : TP_REPORTED_ERROR
    Transport control program tp ended with error code 0232
    Can anybody help me please
    thanks & rgds,
    Della

    I've changed my SAPSR3 password to sap but still error
    this is the error log from Check Transport Tool
    DB Connect            Link to database failed
    This is tp version 372.04.70 (release 700, unicode enabled)
    Warning: Parameter DBLIBPATH is no longer used.
    ERROR: Connect to CAP failed (20091217174435, probably wrong environmen
    TRACE-INFO: 1:  [dev trc     ,00000]  Thu Dec 17 17:44:35 2009
    0.007435
    TRACE-INFO: 2:  [dev trc     ,00000]  DlLoadLib() success: dlopen("/usr
    0.007448
    TRACE-INFO: 3:  [dev trc     ,00000]  Got
    LIBPATH=/usr/sap/CAP/DVEBMGS32/exe:/usr/sap/CAP/DVEBMGS32/exe:/usr/lib
    lient from environment
    TRACE-INFO: 4:
    0.008053
    TRACE-INFO: 5:  [dev trc     ,00000]  Oracle Client Version: '10.2.0.2.
    0.008140
    TRACE-INFO: 6:  [dev trc     ,00000]    >oci_initialize(con_hdl=0, char
    0.008158
    TRACE-INFO: 7:  [dev trc     ,00000]  application info callback registe
    0.008173
    TRACE-INFO: 8:  [dev trc     ,00000]  OCIEnvCreate(mode=16384=OCI_UTF16
    0.010330
    TRACE-INFO: 9:  [dev trc     ,00000]  Client character set UTF16 -> UTF
    0.010421
    TRACE-INFO: 10:  [dev trc     ,00000]  Client NLS setting (OCINlsGetInf

  • Transport control program tp ended with error code 0249

    Hello guys,
          I am facing an when importing transport.  After I click import to the transport in STMS, before it runs, a message window is displayed immediately. This was working find until last week, any kind of transport is followed by the same error.
    Transport control program tp ended with error code 0249
    Message no. XT200
    Diagnosis
    An error occurred when executing a tp command.
      Command: IMPORT BWDK903312 BIW client200 U0 pf=
    sapbiw1a\s
      Return code: 0249
      Error text: connect failed due to DbSL load lib failure
    Has anyone faced this error while trying to import a transport? I have not found the same error in sdn (0249)
    help will be appreciated.
    thanks
    DGF

    Your are right, but which is the Basis forum?
    Business Process Expert 
    Database & OS Platforms  ABAP Development 
    Enterprise SOA  Portal 
    Emerging Technologies 
    SAP Solutions 
    Business Intelligence 
    Scripting Languages 
    SAP Business One  Industries 
    Community Discussions 
    SAP NetWeaver  Application Server  Integration and Certification Center (ICC) 

  • 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.

  • Transport control program tp ended with error code 0212 | URGENT

    Hi All,
             We are trying to import requests in our PRD system. As soon as we select the request and try to import it , we get the error "Transport control program tp ended with error code 0212".
    This is tp version 305.12.42 (release 46D) for ANY database            
    /usr/sap/trans/cofiles/K915883.<SID> for transport: <SID>K915883: Permissio
    HALT 20070222114323                                                    
    ERROR: /usr/sap/trans/cofiles/K915883.<SID> : cant open                  
    : Permission denied                                                    
    ERROR: EXIT(16) -> process ID is: 6878                                 
    tp returncode summary:                                                 
    TOOLS: Highest return code of single steps was: 16                     
    ERRORS: Highest tp internal error was: 0212                            
    Output from tools called by tp:                                        
    This is R3trans version 6.05 (release 46D - 18.10.01 - 11:30:00).      
    R3trans finished (0000).                                                                               
    When i checked the transport tool and rfc destinations, everything was successful.
    When i tried to do tp connect -
    23> tp connect <SID> pf=/usr/sap/tran/bin/TP_DOMAIN_<SID>.PFL
    This is tp version 305.12.42 (release 46D) for ANY database
    E-/usr/sap/tran/bin/TP_DOMAIN_<SID>.PFL could not be opened.
    EXIT
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0212
    tp finished with return code: 212
    meaning:
      could not access file as supposed (see SLOG for more details)
    We are having SAP 4.6C with DB -Oracle and OS HP-UX.
    Please let me know whow to rectifiy the issue. The situation here is getting worse.
    Regards,
    NK

    Hi Ruchit, Sorry for the delay. Here is the file you wanted -
    steic25q:root>ls
    DOMAIN.CFG          TPPARAM.bak         TP_DOMAIN_ID1.PFL   TP_DOMAIN_IQ1.PFL
    TMS_TEST.IS1        TPPRAMA0918         TP_DOMAIN_ID1.orig  nik.dev_evt
    TPPARAM             TP_DOMAIN_ID1.BAK   TP_DOMAIN_IP1.BAK
    steic25q:root>more TP_DOMAIN_ID1.PFL
    #TMS:0078:DOMAIN_ID1
    Caution !
    This file was generated by the Transport Management System.
    Do not change this file using a text editor.
    For more information, refer to the online documentation of the
    Transaction STMS.
    If this file was destroyed, it can be regenerated in the TMS.
    To do this, log on to the domain controller (system ID1) and call
    transaction STMS. In the System Overview, you can distribute the TMS
    configuration. This regenerates the file.
    STMS -> Overview -> Systems -> Extras -> Distribute TMS configugration
    TRANSDIR            = /usr/sap/trans
    DU1/CTC             = 1
    DU1/DUMMY           = 1
    DU1/NBUFFORM        = 1
    DU1/TP_VERSION      = 266
    DU2/CTC             = 1
    DU2/DUMMY           = 1
    DU2/NBUFFORM        = 1
    DU2/TP_VERSION      = 266
    ID1/CTC             = 0
    ID1/DBHOST          = steic24q
    ID1/DBLIBPATH       = /usr/sap/ID1/SYS/exe/run
    ID1/DBNAME          = ID1
    ID1/DBSWPATH        = /oracle/ID1/817_64
    ID1/DBTYPE          = ora
    ID1/NBUFFORM        = 1
    ID1/TP_VERSION      = 266
    IP1/CTC             = 0
    IP1/DBHOST          = steic25q
    IP1/DBLIBPATH       = /usr/sap/IP1/SYS/exe/run
    IP1/DBNAME          = IP1
    IP1/DBSWPATH        = /oracle/IP1/817_64
    IP1/DBTYPE          = ora
    IP1/NBUFFORM        = 1
    IP1/TP_VERSION      = 266
    IQ1/CTC             = 1
    IQ1/DBHOST          = cbnysap2
    IQ1/DBLIBPATH       = /usr/sap/IQ1/SYS/exe/run
    IQ1/DBNAME          = IQ1
    IQ1/DBSWPATH        = /oracle/IP1/817_64
    IQ1/DBTYPE          = ora
    IQ1/NBUFFORM        = 1
    IQ1/TP_VERSION      = 266
    TRN/CTC             = 1
    TRN/DUMMY           = 1
    TRN/NBUFFORM        = 1
    TRN/TP_VERSION      = 266
    steic25q:root>

  • Transport control program (tp) ended with return code 0200

    Hi Gurus,
    Please help, we have a fresh system copy of our prod. I already configure new domain controller with one virtual system. it was meant for 2 system lanscape. PRD -> VIR. The problem now is everytime we try to release a config it shows an error
    "Test call of transport control program (tp) ended with return code 0200"
    System error shows that calling   "C:\>tp EXPCHK BWPK900060 pf=
    SCWOSAPBW3\sapmnt\trans\bin\TP_DOMAIN_BWP.PFL -Dtransdir=
    SCWOSAPBW3\sapmnt\trans" Error text from tp: ERROR: Buffer check failed.
    But doing it in OS level it has no issues
    C:\>tp EXPCHK BWPK900060 pf=\\SCWOSAPBW3\sapmnt\trans\bin\TP_DOMAIN_BWP.PFL -Dtr
    ansdir=\\SCWOSAPBW3\sapmnt\trans
    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.16.63 (release 640)
    createinfo succeeded
    Buffer check succeeded
    tp finished with return code: 0
    meaning:
      Everything OK
    STMS are all ok connection test, transport directory test and transport tool test.
    Kindly help me to resolve issue.
    OS platform is windows 2003, Netweaver 04 640, MSSQL2005.
    Thank you in advance.
    Joel

    Hi Anil,
    Here is the result after the tp check all command.
    D:\usr\sap\trans>tp check all pf=d:\usr\sap\trans\bin\TP_DOMAIN_SID.PFL
    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.16.63 (release 640)
    check>Log file is written to \\hostname\sapmnt\trans\tmp\CHECK.LOG
    check>
    check>Collected 3 filenames from [\\hostname\sapmnt\trans\buffer\.]
    check>Collected 2 Systemnames from [\\hostname\sapmnt\trans\buffer\.]
    check>Collected 00001 out of 00001 entries from buffer BWP.
    check>Collected 00001 entries from buffers
    check>
    check>Collected 1 filenames from [\\hostname\sapmnt\trans\cofiles\.]
    check>Found 0 invalid filenames on Cofile-directory
    check>
    check>
    check>Collected 1 filenames from [\\hostname\sapmnt\trans\data\.]
    check>Found 0 invalid filenames on Datafile-directory
    check>
    check>Collected 14 filenames from [\\hostname\sapmnt\trans\log\.]
    check>Found 2 invalid filenames on Logfile-directory
    check>
    check>Collected 3 filenames from [\\hostname\sapmnt\trans\sapnames\.]
    check>
    check>WARNING: BWPK900060 has status T_STEP_UNKNOWN in  sapnames/TEST
    check>WARNING: BWPK900058 has status T_STEP_UNKNOWN in  sapnames/TEST
    check>WARNING: BWPK900056 has status T_STEP_UNKNOWN in  sapnames/TEST
    check>WARNING: SAPKD64038 has status T_STEP_UNKNOWN in  sapnames/SAPUSER
    check>WARNING: BWPK900060 has status T_STEP_UNKNOWN in  sapnames/SUPPORT
    check>Elapsed time 0m 1s
    tp finished with return code: 0
    meaning:
      Everything OK
    Kindly advise on what to do next.
    Thank you.
    joel
    Edited by: Joel Cancio on May 31, 2010 11:47 AM

  • Error: Test call of transport control program (tp) ended with return code 0

    Hi Experts,
    When we are trying to transport Request.
    Error: Test call of transport control program (tp) ended with return code 0208
    in STMS what are the steps to fallow to just back up the code.
    Any Solutions is Greatly Appreciable...
    Thanks in Advance,
    Ram,

    Hi,
    a)If your system is UNIX check /usr/sap/trans is mounted or not?
    b)After configuring TMS did you save and activate?that can be one reason.
    c)tp might be corrupted.u need to upgrade your tp. (or you can upgrade to the latest kernel)
    Please check the below link
    could not start transport control program tp
    However as suggested by NIbu, you should restart the server once before doing any other checks
    Thanks
    Debdeep
    Edited by: Debdeep  Ray on Jul 13, 2009 4:28 PM

  • Test call of transport control program (tp) ended with return code 0249

    Hi,
    When i release a TR i get the following error
    Pls let me know of what can be the reason for the same
    I did a kernel upgrade 2 days back
    Test call of transport control program (tp) ended with return code 0249
    Message no. TK094
    Diagnosis
    Your transport request could not be exported, since all requirements were not fulfilled.
    Calling the transport control program tp
       "tp EXPCHK BWDK900308 pf=
    WDBSSAPBWD01\sapmnt\trans\bin\TP_DOMAIN_BWD.PFL -Dtransdi"
    which checks the export requirements, returned the following information:
    Return code from tp: 0249
    Error text from tp: ERROR: No connect due to DbSl Load Lib Failure
    System Response
    Further processing is terminated.
    Procedure
    Check the following points:
    u2022     Feasibility of the transport control program tp
    u2022     Parameter settings in the transport profile
    u2022     Availability of the transport directory and the subdirectories (cofiles, data, log, sapnames, bin)
    u2022     Write authorization for the subdirectories
    u2022     Write authorization for the files of the subdirectories cofiles, data, log, sapnames
    Release the request again when the error has been removed

    Hi Balaji,
    End of your question contains the areas to be varified.
    Your SAP seems to be installed in windows environment
    Check transport profile paramater and file permissions.
    Try to browse the directory
    WDBSSAPBWD01\sapmnt\trans\bin\ from start->run
    Check with tp connecting to DB  with tp connect <SID>
    chceck file permission to datafile and cofiles (in case of OS UNIX)
    Regards,
    Ganesh

  • Re: Transport control program tp ended with error code 0212

    Hi ,
              When transport request is added to import queue, getting following error :
    "Transport control program tp ended with error code 0212 "
    Please find the slog file description as follows:
       HALT 20110530001050
    ERROR: /usr/sap/trans/cofiles/K904416.<SID>: cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 2273
    HALT 20110530004629
    ERROR: /usr/sap/trans/cofiles/K904416.<SID> : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 14341
    HALT 20110530004703
    ERROR: /usr/sap/trans/cofiles/K904416.<SID> : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 14514
    How to correct this ?
    Thanks
    Srikanth

    Hi,
    It may happen happen due to permission issue when you are having SAN and sharing common trans directory now to check the permission of the file you have to login at os level and check the permission of the TR.
    cd /usr/sap/trans/cofiles/
    ls -l K904416<SID> - now here it will show the permission of the file please paste the output
    Thanks,
    Saleem

  • Transport control program tp could not be started

    Hi,
    While importing a request to Quality Server , transport terminates with an error "Transport control program tp could not be started" RFC error.
    Function TMS_TP_IMPORT
    Message  TP_CALL_FAILED
    Tp output says "This is tp version 340.16.37 (release 640)
    Warning: Parameter DBLIBPATH is no longer used.
    Warning: Parameter DBSWPATH is no longer used."
    340.16.37.kernel release 640,patch number 193.
    RSTPTEST was successful .
    Changed auth/rfc_authority_check to value '0' in the profile and restarted.
    user id provided in RFC connection is TMSADM and the user is
    having "S_RFC" authorization object.
    This error started after putting the oracle patchset 9.2.0.8.
    SAP version 4.7, Oracle 9.2.0.8, on AIX 5.2
    It will be appreciable if any one can help me out in this issue.
    Regards,
    Saji Kumar

    Hi,
    provide result for
    tcode -  stms_import -> import queue -> check -> transport tool
    also execute RSTPTEST report on QAS,
    RFC error indicate problem in RFC connection , check it using SM59
    regards,
    kaushal

Maybe you are looking for