PI 7.11: Import of CTS+ transport fails (Integration builder only)

Hi,
I've released a transport from DEV to QUAL system.
I've imported via STMS.
But I don't see the transported objects.
The imported change list is already closed and I cannot activate the contained objects.
There's no open change list available for my user.
When I try to transport those objects again, I get an error in STMS:
com.sap.aii.ibtransportclient.XiTransportException: caused by: ClientServerException exception:Unable to transfer object Configuration Scenario SetEmployeeSOAP (DirContext) to change list 'XI 7.1 Import' (c6a9ea7b-57db-11e1-a930-000025876142) since object is already in your change list 'XI 7.1 Import' (e1586c72-57c2-11e1-bf9c-000025876142).
How can I activate the objects contained in the mentioned change lists?
Thanks in advance!

Unfortunately, I've crowned too early
The target systems are not filled in correctly.
We have a 3-tier environment (DEV, QUAL, PROD).
I've setup the same SLD settings in SLD in DEV and QUAL system.
SAP_DEV has target SAP_QUAL and SAP_QUAL has target SAP_PROD.
But in the scenario that I've imported into PI QUAL it didn't replace SAP_DEV with SAP_QUAL (e. g. in CC, Receiver determination etc.).
What can be the reason for that?
Are my target settings not correct?

Similar Messages

XSS SCA import in CMS error: failed to build

We are getting error when trying to build XSS Track in NWDI. There are 2 brocken DC for development track.
Here is the error message that we get:
Development Component Build (2008-11-28 22:04:10)
Component name: mss/mol
Component vendor: sap.com
SC compartment: sap.com_SAP_MSS_1
Configuration: <SID>_XSS_D
Location: <SID>_XSS_D
Source code location: http://server01:55100/dtr/ws/XSS/sap.com_SAP_MSS/dev/active/DCs/sap.com/mss/mol/_comp/
DC root folder: /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/DCs/sap.com/mss/mol/_comp/
DC type: Web Dynpro
Host: server01
DC Model check:
   All used DCs are available locally
   validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
   validating dependency to public part "FloorplanManager" of DC "sap.com/pcui_gp/xssfpm"
   validating dependency to public part "default" of DC "sap.com/tc/wd/webdynpro"
   validating dependency to public part "default" of DC "sap.com/com.sap.exception"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/ddicruntime"
   validating dependency to public part "default" of DC "sap.com/tc/col/api"
   validating dependency to public part "default" of DC "sap.com/tc/wdp/metamodel/content"
   validating dependency to public part "Isrlpd" of DC "sap.com/pcui_gp/isrlpd"
   validating dependency to public part "default" of DC "sap.com/com.sap.mw.jco"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
   validating dependency to public part "default" of DC "sap.com/tc/logging"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.util.misc"
   validating dependency to public part "FPMUtils" of DC "sap.com/pcui_gp/xssutils"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/metamodel/content"
   validating dependency to public part "default" of DC "sap.com/tc/cmi"
   validating dependency to public part "FinUtils" of DC "sap.com/mss/finutils"
   DC model check OK
Start build plugin:
   using build plugin: sap.com/tc/bi/bp/webDynpro
   starting build plugin from : /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/DCs/sap.com/tc/bi/bp/webDynpro/_comp/gen/default/public/webDynpro/
Build Plugin 'WebdynproPlugin', Version 7.00 SP 16 (645_VAL_REL, built on 2008-06-09 20:46:40 CEST, CL83275)
   development component: mss/mol (sap.com)
      software component: SAP_MSS (sap.com)
       support component: EP-PCT-MGR-CO
                location: <SID>_XSS_D
                    type: Web Dynpro
           build variant: default
         output location: /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/DCs/sap.com/mss/mol/_comp/gen/default
       generation folder: /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/t/64CE6536D7BD962CDCB65DC8A7640047
       plugin start time: 2008-11-28 22:04:11 GMT-07:00 (MST)
                 Java VM: Java HotSpot(TM) Client VM, 1.4.2_12-b03 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Warning: Source folder "META-INF" exists but is empty and will be ignored.
Warning: Source folder "src/configuration" exists but is empty and will be ignored.
Preparing data context..
No public part descriptor found for component "tc/wd/webdynpro" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.exception" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/ddic/ddicruntime" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/col/api" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/wdp/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.mw.jco" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.aii.proxy.framework" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/logging" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.aii.util.misc" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/ddic/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/cmi" (vendor "sap.com"), public part "default", using legacy mode.
No 'default' JDK defined, will use running VM.
Data context preparation finished in 0.934 seconds
Creating Ant build file..
Creating output file: /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/DCs/sap.com/mss/mol/_comp/gen/default/logs/build.xml
Using macro file:     /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/DCs/sap.com/tc/bi/bp/webDynpro/_comp/gen/default/public/webDynpro/macros/build.vm
Build file creation finished in 1 second
Starting Ant..
Using build file:     /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/DCs/sap.com/mss/mol/_comp/gen/default/logs/build.xml
Using build target:   build
Using Ant version:    1.6.2
compile:
      [echo] Starting dictionary generator
     [ddgen]
     [ddgen] [Info]    Property deployment is true: Deployment information is provided!
     [ddgen] [Info]    Property sourcepath: /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/DCs/sap.com/mss/mol/_comp/src/packages
     [ddgen] [Info]    Property targetpath: /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/t/64CE6536D7BD962CDCB65DC8A7640047/gen_ddic
     [ddgen] [Info]    Property archivename: sap.commssmol
     [ddgen] [Info]    Property vendor: sap.com
     [ddgen] [Info]    Property dcname: mss/mol
     [ddgen] [Info]    Property projectlanguage: de
     [ddgen] [Info]    Property language: Available languages are automatically determined!
     [ddgen] [Info]    Property addpaths ...
     [ddgen] [Info]    Generating datatypes/com/sap/mss/mol/monitor/model/types/MolModel.gdictionary
     [ddgen] [Info]    Generating datatypes/com/sap/pcuigp/xssutils/objectselection/model/types/FcObjectSelection.gdictionary
     [ddgen] [Info]    Generating datatypes/com/sap/pcuigp/xssutils/pernr/model/types/RHXSS_SER_EMPLOYEE.gdictionary
     [ddgen] [Info]    Generating dbtables/sdmDeployDd.xml
     [ddgen] [Info]    Generation finished (8 seconds)
     [ddgen]
     [timer] Dictionary generator finished in 8.499 seconds
      [echo] Starting WebDynpro generator
     [wdgen]
     [wdgen] [Info]    Property deployment is true: Deployment information is provided!
     [wdgen] [Info]    Property sourcepath: /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/DCs/sap.com/mss/mol/_comp/src/packages
     [wdgen] [Info]    Property targetpath: /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/t/64CE6536D7BD962CDCB65DC8A7640047/gen_wdp
     [wdgen] [Info]    Property archivename: sap.commssmol
     [wdgen] [Info]    Property vendor: sap.com
     [wdgen] [Info]    Property dcname: mss/mol
     [wdgen] [Info]    Property projectlanguage: de
     [wdgen] [Info]    Property language: Available languages are automatically determined!
     [wdgen] WARNING: Metadata of component FcLineItemMonitor is not valid! Component "//WebDynpro/Component:com.sap.mss.mol.monitor.FcLineItemMonitor", Role "ComponentController": A minimum of 1 object(s) is required
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView rulename_editor [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView count_editor [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView evaldate [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView evaltime_2 [text]: Context element and property are not compatible
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> TransparentContainer tcActionBar [Children]: Container does not contain children
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> Button btnEditRule [visible]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> Button btnCreateRule [visible]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> Button btnCopyRule [visible]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> Button btnDeleteRule [visible]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> Button btnPersonalize [visible]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView itemtxt_editor [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> LinkToURL verakUser_url [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> LinkToURL verakUser_url [reference]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView itemdate_editor [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView value_editor [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView waers_editor [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> Image confirmedImage [tooltip]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> Image confirmedImage [alt]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> Image confirmedImage [source]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView actionTaken_editor [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView tvCurrency [text]: Context element and property are not compatible
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> TransparentContainer DetailContainer [Children]: Container does not contain children
     [wdgen] [Error]   com.sap.mss.mol.monitor.VcLineItemMonitorView --> UIElement UpdateTrigger [enabled]: Context element and property are not compatible
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView tvStatus: UIElement does not have a label
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView evaldate: UIElement does not have a label
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView evaltime_2: UIElement does not have a label
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> LinkToAction LinkUpdate: UIElement does not have a label
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView tvUpdateRunning: UIElement does not have a label
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> Caption RuleGroup_Header: UIElement does not have a label
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> TextView tvCurrency: UIElement does not have a label
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> Caption Details_Header: UIElement does not have a label
     [wdgen] [Info]    com.sap.mss.mol.monitor.VcLineItemMonitorView --> Caption ItemDetails_Header: UIElement does not have a label
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> TextView rulename_editor [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> TextView ruleid_editor [text]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> InputField inDescription [value]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> CheckBox cbShowAlert [checked]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> DropDownByKey ddKF1 [selectedKey]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> DropDownByKey ddSign [selectedKey]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> InputField inLimitAbs [value]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> DropDownByKey ddAbsRel [selectedKey]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> InputField InputTimestamp [value]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> Tree treeObject [title]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> Tree treeObject [tooltip]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> Tree treeKfspecgl [title]: Context element and property are not compatible
     [wdgen] [Error]   com.sap.mss.mol.monitor.RuleMaintView --> Tree treeKfspecgl [tooltip]: Context element and property are not compatible
     [wdgen] [Info]    com.sap.mss.mol.monitor.RuleMaintView --> Caption tableRulesHeader: UIElement does not have a label
     [wdgen] [Info]    com.sap.mss.mol.monitor.RuleMaintView --> CheckBox cbShowAlert: UIElement does not have a label
     [wdgen] [Warning] com.sap.mss.mol.monitor.RuleMaintView --> DropDownByKey ddSign: UIElement does not have a label
     [wdgen] [Warning] com.sap.mss.mol.monitor.RuleMaintView --> InputField inLimitAbs: UIElement does not have a label
     [wdgen] [Warning] com.sap.mss.mol.monitor.RuleMaintView --> DropDownByKey ddAbsRel: UIElement does not have a label
     [wdgen] [Info]    Catching throwable null
     [wdgen] [Info]    com.sap.webdynpro.generation.ant.GenerationAntTaskError
     [wdgen]      at com.sap.webdynpro.generation.ant.GenerationAnt.showCheckResult(GenerationAnt.java:157)
     [wdgen]      at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
     [wdgen]      at com.sap.tc.buildcontroller.CBSBuildController.main(CBSBuildController.java:168)
     [wdgen] ERROR: Unknown exception during generation null (com.sap.webdynpro.generation.ant.GenerationAntTaskError)
     [wdgen] ERROR: Generation failed due to errors (7 seconds)
Error: /usr/sap/<SID>/JC51/j2ee/cluster/server0/temp/CBS/27/.B/6448/DCs/sap.com/mss/mol/_comp/gen/default/logs/build.xml:99: [Error]   Generation failed!
     at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:254)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
     at com.sap.tc.buildcontroller.CBSBuildController.main(CBSBuildController.java:168)
Ant runtime 16.597 seconds
Ant build finished with ERRORS
[Error]   Generation failed!
Error: Build stopped due to an error: [Error]   Generation failed!
Build plugin finished at 2008-11-28 22:04:32 GMT-07:00 (MST)
Total build plugin runtime: 20.648 seconds
Build finished with ERROR
What can be done to resolve these error and trigger the build again.
Bhavin

Resloved with SAP help.
1. Ran configuration wizard for CBS, CMS & DTR
2. Changes few JVM parameters (increased heap size, jdbc pool size)

Unable to import Basis (R3) objects to Integration Builder

I am trying to import RFCs and Idocs to the Integration Builder, but am getting the following message.
Unable to establish connection to R/3 system sapdtdb (system=00, client=010) Troubleshooting tips:
Is the target system online?
Check the connection data (note that server names and groups are case-sensitive)
Tips for administrators (see the configuration guide for more details):
Does the user have the required authorizations in the target system?
Is the target system configured correctly in "etc/services"?
I have checked the radio button on the software component for allowing Import Of RFC and Idoc interfaces.
I have checked on both the PI and the R3 system that the entries in SM59 are correct and that login and connections are permitted.
On our old XI system, I am able to import objects, but on our new PI system I am getting the above error.
Does anyone have any other possible solutions to this please?

Chris,
Please check whether have done all the steps given in this link or not for your new PI system:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
If you done all this you should be able to import the IDocs and RFCs without any problem.
---Satish

How to import stuff from SLD to Integration Builder ?

Hi All ,
I have done all my definition and configuration in SLD - Product definiton, Technical System, Business system, SWCV , SWC , logical system - everything is in SDL.
When I go to' IB:design' and 'IB:config' I don't see anything I created in SLD?
I guess this is because the very next step should be to import all this stuff from SLD into Integration Builder.?.I read some posts on the forum but it is not clear where this is done :
1.should I do it first in IB:design or in IB:configuration ?
Can you please tell me how this is done technically and in what order - from wich menu and how?
2.And what is Enviroment->Clear SLD Data Cache used ? Do I have to use it and at which point?
Looking forward to your reply asap..Thanks all in advance..
Regards,
Boby

Boby,
If you do all the configuration in SLD only thing you have to import is the software component into Design and create your namespace and all the objects.
In Configuration you have to import your business systems and do all the routing rules.
Check this weblogs for step by step procedure for an end to end scenario:
/people/srinivas.vanamala2/blog/2007/02/05/step-by-step-guide-xml-file-2-xml-file-scenario-part-i
/people/srinivas.vanamala2/blog/2007/02/05/step-by-step-guide-xml-file-2-xml-file-scenario-part-ii
<i>
2.And what is Enviroment->Clear SLD Data Cache used ? Do I have to use it and at which point?</i>
If you change anything in IR and ID and this new changes do not reflect in your scenario then we do this normally.
Also check this document for all the caches in XI:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34
---Satish

CTS transport in Integration Directory

Hello,
We are running NW70 SP13 and have fully configured CTS+ as per the SAP documentation for SP13 specifically.
In Integration Repository we can see the export option using CTS but in the Integration Directory for scenarios we do not see the "Transport with CTS mode" option...it is defaulted to File Transport and the field is not changeable.
Any ideas?

In the exchange profile make the following entry
com.sap.aii.ib.client.properties: com.sap.aii.ibrep.core.cms.,com.sap.aii.ibdir.core.cms.
for Integration Repository com.sap.aii.ibrep.core.cms.*
for Integration Directory com.sap.aii.ibdir.core.cms.*
Note:
Do not replace existing values; add the new value to the existing values.
Note:
These settings specify that the CMS transport entries are transferred from the server to the web client front end.
Refresh the Exchange profile parameter.
You can refer to link below
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db6306
Try now.
Gaurav Jain
Reward points if answer is helpful
Edited by: Gaurav Jain on Jun 17, 2008 10:01 AM

Not able to import SLD objects into Integration Builder

Hi,
while importing objects from SLD into Integration Builder , am getting no authorization to import objects from SLD.
Plz let me know how to solve this issue.
Thanks,
Satya.

Hi Satish,
Check the link and aks your Basis/Authorization team to provide proper Roles to your user.
http://help.sap.com/saphelp_nw04s/helpdata/en/c4/51104159ecef23e10000000a155106/content.htm
http://help.sap.com/saphelp_nwpi71/helpdata/en/56/361041ebf0f06fe10000000a1550b0/content.htm
Regards,
Naveen

Import CTS+ transport into Portal failed with Returncode:'12'

Hi, Gurus!
I have encountered the problem while deploying CTS+ transport to the Portal (system XO3): Returncode:'12' class java.io.IOException:
The file (
\solman.mycompany.com\sapmnt\trans\data\BIGK900007\ctsplus.par) does not exist on the filesystem.
Full log text:
| ######################################
| Deployment
| Transport request : BIGK900007
| System : XO3
| tp path : tp | Version and release: 372.04.71 700
| Deploy Service called with following parameters:
| CommunicationData-Type:0
| CommunicationData-Address:http://portalXO3.mycompany.com:50218
| CommunicationData-Host:portalXO3.mycompany.com
| CommunicationData-Port:50218
| CommunicationData-User:'filled'
| CommunicationData-Password:'filled'
| Deployable(0) | Deployable-Type:0
| Deployable-Id:
solman.mycompany.com\sapmnt\trans\data/BIGK900007/ctsplus.par
| Returncode:'12' | class java.io.IOException:The file (
\solman.mycompany.com\sapmnt\trans\data\BIGK900007\ctsplus.p
| >>>ar) does not exist on the filesystem.
| Deployment
| End date and time : 20100106154329
| Ended with return code: ===> 12 <===
| ######################################
The file ctsplus.par does exists at the right place and available from the Portal machine.
Especially strange looks the Deployable-Id: *
solman.mycompany.com\sapmnt\trans\data/BIGK900007/ctsplus.par*
Maybe the different slashes "\" and "/" are the cause of the porblem? Both systems (Portal and Solution manager) run on Windows 2003 Servers.
I have checked the "Note 1232674 - class java.io.IO exception during import" and set up the full control permissions to access "\sapmnt\" for the local (solman) user SAPServiceXO3 but it does not help.
I've created a local "SAPServiceXO3" user in the server of Solman and have given to it highest permissions to the file share. Has anybody any idea how to resolve the problem?
Thanks in advance.
Edited by: Mikhail Palstsianau on Jan 28, 2010 8:47 AM

Hi,
Due you have common trans directory for all the system ???
Thanks
Anil

Transport Fail -com.sap.aii.utilxi.misc.api.ResourceException:Import

Hi Experts,
My Transports through Solution Manager is failing in Production PI. Transports are imported, deployed successfully in Test and Regression environments and working fine. Transport requests are of type Workbench and we are attaching '.tpz' files as Non abap objects. All contain ESR objects, no ID components. Import and Check version steps are good but failing at Deployment step in Production PI.
Please find the log which I can see in SE10. All the transports failed with the same below error description.
CTS Import Service - Version 0.94 04.04.2008
==============================================================
Deploy Web service destination = CTSDEPLOY
Directory = /usr/sap/trans/data
SDM Deploy URL =
SLD Deploy URL =
XI Deploy URL = http://ABC2159161:50000
Start import with id:4E8B872CA9F100F2E10080000A32109F
DeployProxy (patch level:0) called with followingparameters:
Deployable(0)
Deployable-Type:1
Deployable-Id:4E6E38F506B601AAE10080000A321063
Deployable-TransportContainerId:DI1K900677
Deployable-ContentLocator:/usr/sap/trans/data/DI1K900677/XI7_1
>>>63.tpz
Property(0)
Property-key:TARGETSYSTEMID Property-value:PI1
Begin CommunicationData-Type[0]:1
CommunicationData-Address:http://ABC2159161:50000/rep
CommunicationData-Host:ABC2159161
CommunicationData-Port:50000
CommunicationData-User:'filled'
CommunicationData-Password:'filled'
Importing archive:XI7_1_A_SAPPI_CM_1.0_of_ABC.com-objs_6
com.sap.aii.ibtransportclient.XiTransportException: caused by:
>>>rt failed: Internal error when importing object [Lcom.sap.a
>>>aused by: com.sap.aii.utilxi.misc.api.ResourceException: Im
>>>g object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d
>>>ethodFault: caused by: ClientServerException exception:Impo
>>>object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d c
>>>sourceException: Import failed: Internal error when importi
>>>IWorkspace;@7ffc92d
End CommunicationData-Type[0]:1
End import with returncode:'8'
Deployment
End date and time : 20111009003401
Ended with return code: ===> 8 <===
Thanks,
Nabendu.

Hi,
I have already informed Basis about these. But do we have any way to check the exact reason for this failure?
All the above points can ensure the successful transport to Production or not, I am not sure.
Thanks,
Nabendu.

Transport request import scheduled in background fails

Hi folks,
In our landscape we have PRD and an Application server. We want to import transport requests in background at a defined time. Though the job status shows up as finished however in the job log it reports - Transport control program tp ended with error code 0232.
In the STMS queue, the request is in still being imported status for long time unless SAP is restarted.
If I change the job in SM37 and give one of the servers (PRD or Appl server) as the execution target the job finishes successfully and request is imported.
My Question is how can I get the job to finish properly without having to enter the execution target each time? I should schedule the transport in background in STMS and it should finish without error.
Regards,
Sai Rolla

Hi SAI,
See this SAP Note 165708 - Test call for tp ended with error code 0232 :
Cause and prerequisites
In the transport configuration file TP_DOMAIN_<TDC_SID>, where <TDC_SID> is the SID of the R/3 system which is used as transport domain controller, the database name of the affected R/3 system is written in lower case, thus you will find the following entry:
     <SID>\DBNAME = <<sid>>
Solution
From within the transport domain controller <TDC_SID> change the transport log in the affected system. To do this, proceed as follows:
      1. Call up Transaction STMS.
      2. Choose "Overview/Systems". On the following screen select the affected system.
      3. Choose "Transport tool" and "Display <--> Change".
      4. For DBNAME write the SID in upper case.
      5. Save and let configuration distribute immediately.
      6. Exit maintenance.
To ensure that no incorrect transport configuration file is generated with a new setup or an enhancement of the transport domain and subsequent activation and distribution, change function module TRINT_PP_GET_DEFAULT_VALUES as described in the attachment or apply the respective Hot Package. (You should do this for all systems participating in the transport domain and not only in the transport domain controller <TDC_SID>.)
Best Regards
AK

Diffrence between File Transport and CTS+ Transport in PI

Hi Guys,
Can you please explain me the diffrence between File Transport and CTS+ Transport in PI.
What are the advantages of CTS+ Transportation over FILE Transportation...
Thanks,
Siva...

The file transfer will simply export the objects to a TPZ file, allowing you to import on the target system. This requires manual copying and paste of the object and have no further control.
CTS+ on the other side, allows the environment to maintain transport requests with control over objects audit. For example, an object must be created on DEV, then after being developed it must go to QA system and will only be sent to PROD when this object was approved by the respective team on QA. For more information on CTS+, please check the help page below.
http://help.sap.com/saphelp_nwpi71/helpdata/en/9a/775de286874bc78dcb1470bc80f0f9/frameset.htm
Also the documentation below will provide a more complete overview and configuration steps for the CTS+ usage
"http://www.sdn.sap.com/irj/scn/go/portal/prtroot/com.sap.km.cm.docs/library/application-lifecycle-management/lifecycle-management/software-logistics/new%20features%20in%20sap%20enhancement%20package%201%20for%20sap%20netweaver%207.0.pdf"
Please also refer to the SDN thread below
How to move PI objects in IR and ID from DEV to QAS

Import and Export transport requests on Netweaver 2004s Sp11 Sneak Preview

Hi Experts,
I have configured the transportation system <STMS> in order to import and export transport requests on the NSP system. The configuration is working properly as files can be imported and exported out of the C:\sapmnt\trans directory. (configuration distributed by STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration, Folder SAPMNT shared).
The problem I'm facing with the import of some example transports is given by the hanging import queues. In phase 'Import ABAP Dictionary Objects' I have the following message for almost all objects -> '... was not imported in this step'.
I tried to solve this issue by running SE38->RDDNEWPP with DDIC user to schedule job RDDIMPDP for TP imports. I also made the config in TP_DOMAIN_NSP.PFL with SYSTEM_PF = C:\SAP\NSP\SYS\profile\DEFAULT.PFL.
The error is still in logfile SLOG0732.NSP
ERROR:       The following call returned with exit code 7:
ERROR:         sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=NSP
and logfile dev_evt
ERROR ***: MsSndTypeOnce, rc = -20
ERROR ***: Event raise failed
With the exports there is a similar issue in the EXPORT phase, given the note
0 entries from WDY_APPLICATIONT exported.
Batch process is available (parameter rdisp/wp_no_btc = 1)
Profile has been activated by rz10->utilities->import profile->ofactive servers.
Any ideas what still can be wrong? Does the import export and DDIC activation really work with the sneak preview?
Thanks
Christoph

Hi Peter
First of all thanks for your advice.
I did No. 1. 2. 3. steps.
Step 4. reacts with the folowing error message.
Transport control program tp ended with error code 02008.
Errors: error in transportprofile (param missing, unknown).
My license expires in four days. I tried to extend it via http://www.sap.com/minisap
1. System-ID *
2. Hardware-Schlüssel (HWID) *   ?
3.Systemnummer ?
What is to be entered in 1 and 2.
Where should I look for HWID and Sysnr ?
Thanks a lot again for your help
With regards
Fisseha

When transporting multiproviders and cubes transport failed.

HI Experts,
When transporting cubes and multiproviders in a request the transport failed with return code 8.
The described below as:
Start of the after-import method RS_CUBE_AFTER_IMPORT for obje
Error/warning in dict. activator, detailed log    > Detail
/BIC/L101078 (specify a primary key)
Table /BIC/L101078 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101078 has not been activated
Error when activating InfoCube 101078
Error/warning in dict. activator, detailed log    > Detail
/BIC/L101077 (specify a primary key)
Table /BIC/L101077 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101077 has not been activated
Error when activating InfoCube 101077
Error/warning in dict. activator, detailed log    > Detail
/BIC/L101078 (specify a primary key)
Table /BIC/L101078 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101078 has not been activated
Error when activating InfoCube 101078
Error/warning in dict. activator, detailed log    > Detail
/BIC/L101077 (specify a primary key)
Table /BIC/L101077 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101077 has not been activated
Error when activating InfoCube 101077
Error/warning in dict. activator, detailed log    > Detail
/BIC/L101078 (specify a primary key)
Table /BIC/L101078 could not be activated
Please let us know if anyone has come across similar kind of issue.
Regards,
Monalisa Mohanty

Issue seems to be with the aggregates maintained in the cube.
Is your aggregates were properly maintained in your Dev system when you have collected it in your transport?
Check the same and also use overwrite option when you are trying to import the transport in the target systems.
If the aggregates are properly maintained then check the import once again and see if that works fine with the overwrite mode. If not then you need to collect your objects again in a new transport.
Hope this helps.
Murali

CTS+ Transport Strategy

Dear all,
We are planning to setup CTS+ in our system landscape.
Please provide your inputs, on the pros and cons of this strategy.
Also direct me to links of CTS+ documents on SDN.
Thanks for the help.
Regards,
Younus

Hi,
CTS+ transport is like ABAP way of doing transport of ABAP objects in r/3..........after deploying CTS+ in your XI system, you can release your objects for CTS+ transport from IR, ID and then a transport request for it will be created for you, which you can then release and finally import it in target system.
Regards,
Rajeev Gupta

JDI moved; XI CMS transports fails now

Hi there!
Our NWDI/CMS/SLD system was moved to another host. We changed all kind of settings to the new hostname of our SLD/NWDI server.
We updated all SLD content and associations, Exchangeprofiles etc.
We cannot find any link anymore to our old hostname...but....
Our XI transports through CMS still fails because it keeps looking for the old host as the CMS server.
What i found is that in de Integration Builder --> Administration --> CMS Transport Settings all SWCS related to the XI track are stored. Also the CMS URL is mentioned there, and this still points to the old host!
And there is no way to change that there. Just the True/False option for transport changelist option...
I have tried to kick out an SWVC from the XI track, save it. Put it back in on the new host and save again. Update CMS, but still the CMS URL points to the old hostname:port (grmbl)
Does anyone now where to adjust this CMS URL for the XI track related SWVC's?
Any help is welcome since we are stuck with transports for XI and we cannot fix production problems now...
Björn

Hi Bjorn
Please go thru these links....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db6306
How to configuring the CMS for XI?
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e
Where can I get installation files of DTR, CBS, and CMS?
https://websmp201.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
I'm confirming that with the same XI instance you can't import/export. Please find the below document for reference.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff72d822b109
Page 3 , 2.4.2 Track Data
This will also help you
How to Use CMS in XI 3.0.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff72d822b109
CMS based transport in XI
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
Thanks !!
reward points if useful

Problem during import of 121 transport requests to productive system

Hello
We have problem during import of transport requests to productive system. Import of 121 transport requests stopped very soon in phase "N" (in TRBAT I have only one entry and in TRJOB as well).
In sm50 there is an BGD running under user DDIC in client 000 now for 14453 seconds (program SAPLSDB2). This should be import.
In SM37 I can see it as job "RDDGEN0L" with repport"RDDGENBB". Based on some literature it should perform "Converting all structure changes generated by the import and recorded in table TBATG, other than the structure changes to matchcode objects." Very interesting that TBATG has only four entries related to 2 indexes in table "DFKKOPK" , one in table "DFKKREP06" and one" ENQU" for EFKKEXC". (only this last one has not status error)
For fist two indexes I know they are not present as objects "LIMU""INDX" in any transport request beeing imported.
Also on productive system there is no"VOL" and "ZOL"indexes for table "DFKKOPK"(instead they are created on test system ie. not transported from development to test system)
Last command for that process is "CREATE INDEX "DFKKOPK~HKO" ON "DFKKOPK" ("MANDT", "HKONT", "OPBEL") PCTFREE 10 INITRANS 002 TABLESPACE PSA
PTR3 STORAGE (INITIAL 0000000016 K NEXT 0000000016 K MINEXTENTS 0000000001 MAXEXTENTS UNLIMITED PCTINCREAS"
There is enaught space on disk and in tablespaces (it is an oracle/HPux server).
Does anyone knows workaroun to solve production

are you importing these transport requests simultaneously into production?
I would suggest you try doing in smaller groups of 5 or 10 and then see whether you are able to import the requests
Rohit

PI 7.11: Import of CTS+ transport fails (Integration builder only)

Similar Messages

Maybe you are looking for