BPC 10.1 - Install EnvironmentShell - Transport request or $tmp

Hello,
We installed SAP BPC 10.1 and in the final steps, install the environmentshell, the system send us a window to put a package. We put as a local object, $tmp, but we are not sure if we done it properly. The installation guide doesn't refer this step and we don't know if we will have issues with this.
Does anyone knows if we done right or any document with this info?
Many thanks
Sílvia

Hi Silvia,
You made a right decision. Actually it will work in either case, no matter what Package you select. Installation guide says that you don't transport ENVIRONMENTSHELL, but install in each box. So, $TMP or any other non-transportable Package is fine.
Regards,
Gersh

Similar Messages

How to install transport request files into the SAP system

Hi Experts,
I want to install transport request files into my SAP source and target system . I am from BW/BI background so can anyone help me out with the step by step procedure for the above installation.
Thanks in advance
Regards
Shiva

Hi,
What I understand is, you want to transport request from one server to another.
for example, Development to Qualtiy or Quality to Production.
For this your transport system must be configured. Please search help.sap.com or google for "How to configure Transport System (STMS)".
If you want to copy transport request from one system to another system which is not in your landscape, you need to physically move/copy transport request (cofile and datafile) to the target system in /usr/sap/trans/cofiles and /usr/sap/trans/data
Then import that request using SCC1.
You can alos perform TEST import for result.
Regards.
Rajesh Narkhede

Error while importing a transport request

Hi,
I installed two SAP ECC6 EHP6 IDES sytems and created a transport route between them.
When I try to import a Transport request I get the following error:
HALT: inconsistent preview tables E071K_STR (size=344) and E071KS_PREVIEW (size=128)
Please help me find a solution to this problem.

Hello Occoro,
There are multiple steps you need to do, I am not sure if the following note is applicable to your version of SAP.
1730009 - Import queue does not work
Downloading R3trans and tp is similar to downloading kernel.
Download the versions relevant to your SAP Kernel 7.20, the latest patch should be available at http://service.sap.com/swdc
In the same area where you get SAP Kernels, you should be able to get files such as:
R3trans_xxx-xxxxxx.SAR
tp_xxx-xxxx.SAR
Download these files, uncar them to your kernel directory typically /sapmnt/<SID>/exe
Refer to the following note for more details:
19466 - Downloading SAP kernel patches
Good luck.
Regards,
Siddhesh

Error while Releasing a transport request - DSO 0SD_O03: Active version

Hi all,
I am getting below error when I am trying to release a transport request.
Object ODSO 0SD_O03: Active version differs from modified version.
I activated DSO again,but I was not successful to correct the error.Please help me correcting this error.
Regards,
Bob

check
match and copy while installing the business content
Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.With the most important object types, the active version and the SAP delivery version can be matched.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually.
A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content.
When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Installindicator separately.
The active version is overwritten with the delivery version if
 the match indicator is not set and
 the install indicator is set.
check following thread
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/102906a4-f13d-2e10-7199-ce316ff254b8?QuickLink=index&overridelayout=true
Thanks and regards
Kiran

Error in FM DDIF_NAMETAB_GET when deleting BI objects via transport request

Dear all,
when importing a transport request in which several types of BI objects are deleted (Infocubes, DSO's, transformations, routines, DTP's, query elements, infosets, process chains). The import terminates only when transporting from acceptance to production with return code 12 due to an uncaught exception:
Transporting from development to acceptance did not raise this exception.
The ST22 dump (see below) refers in the "contents of system fields" section to a DSO, and to post-import activities. The DSO and the associated tables could not be found (rsa1 & se16), since they are deleted as desired.
Some of the relevant notes that I have found do refer to DSO related problems, but they all indicate to install SP19 which we already have installed (BW 7.0 Patch Level 23)
Could you please assist in pointing out potential solutions based on the information from the ST22 Runtime Error below?
Kind regards,
PJ
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_RS_PROGRAM_ERROR
Date and Time          08.02.2011 10:48:14
Short text
    An exception occurred that was not caught.
What happened?
    The exception 'CX_RS_PROGRAM_ERROR' was raised, but it was not caught anywhere
    along the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_RSDD_DS====================CP' has to be
    terminated.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RS_PROGRAM_ERROR', was not caught
    and therefore caused a runtime error.
    The reason for the exception is:
    Error in BW: Error in DDIF_NAMETAB_GET
How to correct the error
    If the error occurs in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_RS_PROGRAM_ERROR"
    "CL_RSDD_DS====================CP" or "CL_RSDD_DS====================CM001"
    "APPEND_DS_TEC_FIELDS"
System environment
    SAP-Release 700
    Application server... "dp1ci"
    Network address...... "<removed>"
    Operating system..... "HP-UX"
    Release.............. "B.11.23";
    Hardware type........ "ia64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 45
    Shortdump setting.... "full"
    Database server... "spisap02"
    Database type..... "ORACLE"
    Database name..... "DP1"
    Database user ID.. "SAPBIW"
    Terminal................. " "
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Dec 14 2009 20:47:35"
    create on........ "HP-UX B.11.23 U ia64"
    Database version. "OCI_102 (10.2.0.1.0) "
    Patch level. 236
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 700
    Operating system..... "HP-UX B.11";
    Memory consumption
    Roll.... 5979936
    EM...... 0
    Heap.... 1459888
    Page.... 40960
    MM Used. 6988880
    MM Free. 415648
User and Transaction
    Client.............. 000
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4D5111661004210BE10000000AFA2502"
    Program............. "CL_RSDD_DS====================CP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    Termination occurred in the ABAP program "CL_RSDD_DS====================CP" -
     in "APPEND_DS_TEC_FIELDS".
    The main program was "RDDEXECU ".
    In the source code you have the termination point in line 61
    of the (Include) program "CL_RSDD_DS====================CM001".
    The program "CL_RSDD_DS====================CP" was started as a background job.
    Job Name....... "RDDEXECL"
    Job Initiator.. "DDIC"
    Job Number..... 10475900
Source Code Extract
Line SourceCde
   31         RAISE EXCEPTION TYPE cx_rs_program_error
   32           EXPORTING
   33             text = 'Invalid DSO subtype'.                   "#EC NOTEXT
   34     ENDCASE.
   35
   36 *   get table name from DDIC
   37     CALL METHOD cl_rsd_odso=>get_tablnm
   38       EXPORTING
   39         i_odsobject = n_infoprov
   40         i_tabt      = l_tab
   41       IMPORTING
   42         e_tablnm    = l_tablnm
   43       EXCEPTIONS
   44         OTHERS      = 1.
   45
   46     IF sy-subrc <> 0.
   47       RAISE EXCEPTION TYPE cx_rs_program_error
   48         EXPORTING
   49           text = 'Error in CL_RSD_ODSO=>get_Tablnm'.        "#EC NOTEXT
   50     ENDIF.
   51
   52     CALL FUNCTION 'DDIF_NAMETAB_GET'
   53       EXPORTING
   54         tabname   = l_tablnm
   55       TABLES
   56         dfies_tab = l_t_comp
   57       EXCEPTIONS
   58         not_found = 1
   59         OTHERS    = 2.
   60     IF sy-subrc <> 0.
>>>>>       RAISE EXCEPTION TYPE cx_rs_program_error
   62         EXPORTING
   63           text = 'Error in DDIF_NAMETAB_GET'.        "#EC NOTEXT
   64     ENDIF.
   65
   66
   67   ELSE.
   68 *   model table only needed for standard datastore objects, for
   69 *   write optimized DSOs target table is a changelog that is fully described by
   70 *   dta_pro (infoobjects)
   71     CHECK n_s_dta-odsotype = rsdod_c_type-standard.
   72
   73 *   get model table fields to add
   74     CALL METHOD cl_rsd_odso=>get_mod_tab
   75       IMPORTING
   76         e_mod_fld_ur = l_t_comp.
   77   ENDIF.
   78
   79 * according to T.B. ( 13.04.2007) the correct position is
   80 * not needed in the D version
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 1
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY E
SY-MSGID DA
SY-MSGNO 300
SY-MSGV1 /BIC/AV_AMOFCB40
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20110208
SY-UZEIT 104759
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET

Hi All
We are also experiencing this same error when transporting deletions of multiple objects.
Although the transport was cancelled in the destination system (production) it appears to have largely deleted all objects successfully except for DSOs.
The DSOs still appear in the table RSDODSO (via SE11) but are not visible anywhere else. When you try to view the DSO via RSDODS a warning appears saying "DataStore object to be deleted by transport -> delete only allowed". If you try to delete them in this transaction the same ABAP runtime error as the transport appears.
Any assistance would be greatly appreciated!
Regards
David

Error in creating Transport Request for a view table

Hello all,
I have an ECC IDES 6.0 system named EC1 and another one which is ECC EhP4 IDES named EA1 which I have just installed.
One of my requesters has a view table named ZVAITM_TBLE in EC1 and she wants it to be transported to EA1.
So I created a workbench transport in SE10 and included the following:
PgmID = R3TR
Obj = VDAT
Object name = ZVAITM_TBLE
But when I press enter, I encountered the following error:
No object definition exists for Customizing object ZVAITM_TBLE
Message no. TK427
Diagnosis
The Customizing object R3TR VDAT ZVAITM_TBLE is not defined in the tables of the Change and Transport System.
This means that you cannot use the Transport Organizer to edit it.
System Response
The function terminates.
Procedure
First check whether the name of the object is correct. Then you (or the system administrator) should check the object definition, to ensure that the object was created correctly (transaction SOBJ).
If the object does not exist, then create it or delete it from the request/task.
I am new to transports so I have no idea how to proceed.
Please advise.
Thanks a lot!
Cha Cha

Hello Cha,
Kindly open this custom table using SM30 and try creating a transport request from there.
Regards
Vivek

Error during import of Transport Request in PI 7.1

Hi Friends,
I have installed PI 7.1 server on HP-UX 11.23 with Oracle 10g.
After completing all the post-installation activities,I configured CTS for moving objects developed by PI consultant to Quality & Production server.
Using CTS I Successfully imported all objects in Integration Repository but When Iam trying import objects of Integration directory,it is showing the error during deployment phase.
Copy File Between Transport Groups       23.10.2008 13:04:07    (0) Successfully Completed
Import                                   23.10.2008 13:04:26    (0) Successfully Completed
Check Versions                           23.10.2008 13:04:26    (0) Successfully Completed
Deployment                               23.10.2008 13:04:28   (12) Canceled
When I go to Log of above it displays follow
Deployment
Transport request   : SPDK900031
System              : SPT
tp path             : tp
Version and release: 375.30.40 710
CTS Deploy Service - Version 0.92 06.03.2007
========================================================================
Deploy Web service destination = CTSDEPLOY
Directory = /usr/sap/trans/data
SDM Deploy URL =
SLD Deploy URL =
XI Deploy URL = http://srstlspt:50000
Double-stack system SPT
Deploy for XID
Deploy File = 60913470a0d511dd873000306eeac205
Communication error in Web service CTSDEPLOY , exception is CX_AI_SYSTEM_FAULT
SoapFaultCode:1 Authentication failed. For details see log entry 00306EEAC205004E0000091A00000EC703
>>>51C766E6CBB4F0 in security log.
Return Code = 12
Highest Return Code = 12
Deployment
End date and time : 20081023151500
Ended with return code: ===> 12 <===
Regards,
Sunil

hi,
I am looking forward to implement SAPKW70017, I need to know the CONS of SP17, what was the reason which made you implement SP17, just to have updated Version of SP or did you face with any problems and decided to update the SP? what was the previous SP which you had,
We have problems in F4 search help when running queries, SAP asked us to implement latest which is SP17, but wanted to make sure what would be the CONS before we do it, we are having SP15 in BI 7.0
Please update the post for this.

Transport request from one server to another

Hi All, We have two servers AB1 and AB2. We would like to transport request from client 101 (AB1) to client 110(AB2). How do i make transport route between these two servers. Thanks, Sam

Hi Sam,
You need to configure Transport Management System between these two system by following Configuring TMS - Software Logistics - SAP Library and by considering below detailed steps:
1. After SAP Gui installed. (Development system is always domain controller.)
2. Logon to Client :000User: DDIC.Pwd: ******
3. Put a T-code (se06) in the command field
4. Click standard installation and click post installation (yes)
5. Put a T-code (STMS) in the command field and give a description then save it.
6. Click System overview push botten, click extras option from the menu and click Distribute and activate configuration. (Yes)
7. Back to the stms main screen and click Transport routes from the push botten
8. Click Configuration button from the Menu.
9. Click Distribute and activate from the configuration menu.
10. Now your sap system is activate in domain controller.
11. Now logon to QAS system.
12. Client: 000User: DDICPwd: ****
13. Put a T-code (se06). In the command field.
14. Click standard installation and click post installation (yes)
15. Put a T-code (STMS) in the command field.
16. Click other Configuration push butten in the bottom of appear screen.
17. Give information about development system.
18. Then save it. OK
19. Now QAS is waiting for include domain controller.
20. Logon to Development system.
21. Click system overview push butten.
22. Click sap system from the menu.
23. Select the QAS systems.
24. Click Approve butten from the sap system menu.
25. Now QAS is member system of domain Controller. (Development system)
26. Suppose if you want configuring Production also, following the same step in the QAS.
Also you can follow links SAP Basis Tutorials/ Training: Transport Management System ( TMS ) Configuration In SAP Step By Step With Snap Shots
Hope this will help you.
Regards,
Gaurav

R/3 Transport requests

HI,
i raised a transport request for install & activate data source in R/3.I released the request in development system,But it is not showing in the transport queue
stms_import
What am i missing.....what is the tcode for transport queue.
Thanks

there is a possibility if there is filter in the list you see in stms_import transaction.click on the filter icon and view if there is any userid specifically given..
But there shouldnt be any problem in transport if it is in se09..ask your basis to import to QA..and check if they have the transport path setup form dev to QA properly then it should not be problem in transport..

How to create transport request for standard web template

hi all
can any one tell me the step by step procedure to create transport request for standard template?
thanks
shalini

Business Content --> Choose & Install the standard web template & then collect the object for transport...Assign a Package & when prompted for Transport Request --> Opt for a new transport request.
Message was edited by:
Jerome

Transport requests from dev to prod

Hello,
It's possible to transport requests from a BW developing system with
HP-UX IA 64 (with itanium processor) operating system, to a production
system with HP-UX 11i v1(with risc processors) operating system.
We installed BW 3.0 for developing on HP-UX IA 64 and BW 3.0 on HP-UX
11i v1.
Thank you,
Florin

You could, if you configure your transport connection correctly.

HR data input creates transport request dialog

Hello
I am trying to configure some basic HR functionality on my system (PA, OM) for a couple of infotypes. Every time I enter or change master data for an employee on my development server, a dialog appears for me to input a transport request number as if I am making a new program or changing tables in a system. Also in a production system when i do this a message appears that client is not modyfiable and when i confirm, data gets saved normally.
How can i disable these dialogs? I know this is more of a development / instalation question but i hope someone understands my problem here.

Hi,
Ask you Basis person to disable these prompts. Basis people will set these transport requests, authorizations to modify, view etc.
Regards,
Suhasini

Need help on Transport Requests in BI

Hi All,
I am doing BW Transports. I have collected all info Objects with Option "Necessary Objects" in one request.
In 2nd Request, i have selected Data target with the Option "Data Flow before", so that i can get all the objects from Datasource to Data target. By Default, the Info Objects Checkboxs are disabled and transport requests are displayed for Infobjects alone.
My Query is, there is a info Object called 0PLANT, which is having seperate data flow for master data. Do i need to install seperately for Master data flow. ie)0PLANT_ATTR of transfer rules and other Objects.
Or it will automatically be installed while collecting the 1st request itself.Please help on this issue.
Thanks,
Siva.

HEllo,
First check whether 0PLANT is already in the prod box and whether its loading. Its a part of global master data and there are chances that it already may be in use.
If so then there is no need to capture and re send it.
Secondly, if its not available till prod, then you need to analyze whether you really need to load 0PLANT master, if your requirement does need it then only you need to capture it and sent it ahead.
Check your first request and verify if its already captured. If so then no need to capture it again, rather the system wont allow you to capture the objects which are already locked in some other active transport request.
Regards,
Shashank

Transport request files creation

Hi to all,
I have one stand alone system which is not connected to any transport layer.
In this system we do lot's of development and now we install Development system We want to transport some requests from this stand alone system to our development system.
Problem is that after release of our transport requests files on usr\sap\trans\.... are not created. Becasue of that we can not copy files for transport on develeopment and import then there.
It's there some program, FM or tool so I can create transport files from transport requests.
Thanks a lot,
Drazen

Hi DL ,
one way to get changes is Manual Copy of Cofiles and Datafiles into ur DEV server.
Hi DL ,
just tell me Y SAP will not create Cofile and Data files , when i am creating Transport Request ?<b> So u mean to say Transport Request contains nothing ?</b>
Regards
Prabhu
Message was edited by:
Prabhu Peram

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

BPC 10.1 - Install EnvironmentShell - Transport request or $tmp

Similar Messages

Maybe you are looking for