Incorrect Transport Requests : SAP delivery version getting collected

Hi,
In our development system, when we try to include objects in a transport request, the entries in the transport request are getting saved as the SAP Delivery version rather than the active version.
For example an ODS ( z object, newly created in development environment) entry is being logged as R3TR DODS XXXX (Obj name) rather than R3TR ODSO XXXX.This is happening for all object types ( Info objects, cubes, workbooks etc).
Also while collecting workbooks in transport request ( using transport connection) we got the following error -Logical transport object 414Q not found in table RSTLOGOPROP. Not sure if the above two issues are interlinked.
Appreciate your help on this.
Kind Regards,
Bansi

Hi KxD,
I don't expect the loading date to be equal to the delivery date but I expect it to be 2 days before the delivery date since the time specified on the route is 2 days. So I would expect my loading date = delivery date - 2 days (route time)
The way system is acting is loading date = committed date + 2 days (route time).
FYI.. when you turn on route scheduling the delivery creation date is based off of your route time and not your planned delivery time from the material master
Thanks,
Imran

Similar Messages

Error during transport request import - how to get it's text at runtime?

Good day to you, Ladies and Gentlemen!
Would be glad if someone can give me an advice.
Suppose we are importing a transport request to a system. And an error occurred during import.
In my program I want to display why the transport failed. How can I get the error message text with description of what is wrong? The same we can see at the transport log?

Hi
If you mean reading the Transport Log of a request you can use this FM
data: lines type table of TRLOG.
CALL FUNCTION 'TR_READ_LOG'
EXPORTING
   IV_LOG_TYPE             = 'FILE'
   IV_LOGNAME_FILE         = '/usr/sap/trans_UE6/log/E7DG900147.UE6'
TABLES
    et_lines                = lines
EXCEPTIONS
   INVALID_INPUT           = 1
   ACCESS_ERROR            = 2
   OTHERS                  = 3
You just have to figure out which directory is you system using to store the Transport Logs. Also note that in this case UE6 it would be the logical name of your system and E7DG900147 the transport request number.

Export and Import transport request between different version?

Hi,
I have tried to Export the transport requests from ECC5 to ECC6 via STMS .Its not throughing any error but no Master datas are transported. Anyone have idea about that?

Hello,
From my experience SAP didn't recomneded transporting from 46C -> ECC5.
The structure of tables and objects are a little bit different between different
releases.
Dimitry

Transport request failed-inactive version of query element.

I have transported 70 reports from BI development to production.
the request has failed due to inactive version of the query element.
How to find which report the query element belongs.
Please advice how should i troubleshoot this issue.

Murali, check this table :RSZELTXREF
enter the element name in field TELTUID. Then from the result, select the value of field SELTUID and enter it as value of field ELTUID to check data of table RSZELTDIR.
That will give you the query name.
Regards
Ashwin.
Edited by: ashwin kumar on Apr 27, 2010 10:11 AM

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

Transport Request Number shown as Blank in Version Management

Hi Experts,
I am creating transport request for report programs using the function modules IW_C_CREATE_TRANSPORT_REQUEST and
TR_INSERT_NEW_COMM .Once created i am able to see the transport no in SE01 .But when i tried to make any changes in the program and save ,its asking for a new transport request.Also in version management the transport request is blank .
Please suggest me where i went wrong.
Regards,
Lakshman.

Hi
Just check if your report objects are getting linked to the Transport in se01.If not then it means that this FM only creates a TP# and not attaches that to Report Objects.
You then need to manually attach the Report object to this TP#.
Regards
Gaurav A

Copy transport request in SAP BI?

Hi,
I have a doubt that how can i copy from one request to another. i can create a new request and select include objects from other requests.
But is there a way to just make copy of one request to another transport request.
Thanks

Hi,
Whenever you collect any object in TR it will be locked in that TR.Now it cannot be collected in other TR until it is collected in one TR already. So if you want to use same TR again in new TR either you have to release old TR and after that you can include old TR in new TR Or you have to delete those objects from that TR those you want to collect in new TR. You can unlock TR/task using SE03 and after that you can delete those objects.
Regards,
Abdullah

Error when adding EPA file to transport request via CTS

I have a rather strange problem. Sometimes when attempting to add an EPA file to a Transport Request via CTS I get the following error in my logs with a corresponding short dump. This does not happen all the time.
#000255D36E8F005B00015391000003DC00046C0470FF1359#1244666238275#com.sap.portal.pcdadmintools#sap.com/irj#com.sap.portal.pcdadmintools#MOROZOWSKIJO#24750##rp1.conair.com_RP1_2406850#MOROZOWSKIJO#28167c7055fe11dea0f1000255d36e8f#SAPEngine_Application_Thread[impl:3]_10##0#0#Error#1#/System/Server#Java### [com.sapportals.portal.pcd.admintools.export.ExportCTSHandling] Could not attach epa file to transport request
[EXCEPTION]
{0}#1#com.sap.tc.di.draft.ts.TsExecutionException: Error executing function (check stacktrace for details):CTS_FILE_APPEND_TO_REQUEST, (service=com.sap.tms)
     at java.lang.Throwable.<init>(Throwable.java:216)
     at java.lang.Exception.<init>(Exception.java:59)
     at com.sap.tc.di.draft.ts.TsException.<init>(TsException.java:19)
     at com.sap.tc.di.draft.ts.TsServiceException.<init>(TsServiceException.java:16)
     at com.sap.tc.di.draft.ts.TsExecutionException.<init>(TsExecutionException.java:16)
     at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoExceptions.throwTsServiceException(TmsJCoExceptions.java:74)
     at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoExceptions.throwTsException(TmsJCoExceptions.java:35)
     at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.addFileToRequest(TmsJCoAdapter.java:536)
     at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsTransportService.handOverAsStream(TmsTransportService.java:253)
     at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsTransportService.requestUpdate(TmsTransportService.java:202)
     at com.sap.tc.di.draft.ts.impl.TransportRequestImpl.transmit(TransportRequestImpl.java:97)
     at com.sap.tc.di.draft.ts.impl.TransmissionPackageImpl.transmit(TransmissionPackageImpl.java:49)
     at com.sapportals.portal.pcd.admintools.export.ExportCTSHandling.attachFileToPackage(ExportCTSHandling.java:209)
     at com.sapportals.portal.pcd.admintools.export.pages.ExportStatusPage.prepareGenericPageSettings(ExportStatusPage.java:417)
     at com.sapportals.portal.pcd.admintools.export.pages.ExportStatusPage.dispatchPageRequest(ExportStatusPage.java:241)
     at com.sapportals.portal.pcd.admintools.export.ExportMain.doContent(ExportMain.java:89)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:166)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:111)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:103)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: The current application triggered a termination with a short dump.
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Exception.<init>(Exception.java:41)
     at java.lang.RuntimeException.<init>(RuntimeException.java:43)
     at com.sap.mw.jco.JCO$Exception.<init>(JCO.java:1117)
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
     at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1224)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3909)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3417)
     at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.executeFunction(TmsJCoAdapter.java:112)
     at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.executeFunction(TmsJCoAdapter.java:133)
     at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.addFileToRequest(TmsJCoAdapter.java:531)
     ... 38 more
Edited by: Jon Morozowski on Jun 10, 2009 10:57 PM

Here is the short dump in the ABAP system.
Short text of error message:
INTERNAL ERROR UPDATING REQUEST DESC OF RP1K900690
Long text of error message:
Technical information about the message:
Message class....... "PU"
Number.............. 601
Variable 1.......... "INTERNAL ERROR UPDATING REQUEST DESC OF"
Variable 2.......... "RP1K900690"
Variable 3.......... " "
Variable 4.......... " "
I have checked the RFC destination in the J2EE Admin and that works OK. This has me kind of stumped.

Tranport Request from Higher version to Lower Version

Hello,
                  Can any One Know how to Transport Requests from Higher Version to Lower Version for Example
                   From Ecc6.0 Ehp1 to->>>>> Ecc6.0.    is there is any way or any SAP Note related to this?
                  Please, send me if any one done/ aware of it with the needful steps     ASAP
Thanks & Regards,
pavankumar.

Not sure you are in the right forum. You will have a better chance of an answer in a Basis forum.

Automatic release of Transport Request

Can we create a recurring transport request that can automatically get released daily and still can be reused to add object the next day?
If yes then how? Do we have an alternative to achieve that functionality?
Please reply. Points will be awarded

Hi Mayank,
SAP has provided transports to move objects from one system to subsequent system & it helps to track the changes moved.
Hence SAP doesnt provide ny functionality to use transport request recurringly. This will defy the purpose of tracking the changes moved from one system to subsequent system.
Best regards,
Prashant

BW Query transport request.

Hi Friends,
I have made some changes in the query and my test system is in open config.So my query is getting saved but transport request number is nt getting generated. I guess there is an option in RSA under transport connection in the menu bar....EDIT->Tranport-> Swich on /switch off standard...but i am ne sure what option needs to be selected.
Can any of u guys please help me in sorting out this issue.
Thanks in advance,
Soumya.

Hi soumya nair, Welcome to SDN.
To Collect query :
Goto RSA1 -> Transport connection --> Object Types --> Query Elements --> Query --> select required query --> drag and drop to right hand side.
Select required objects and transport.
Check: [How to Manage BW Transports|http://sapbwneelam.blogspot.com/2008/10/how-to-manage-bw-transports.html]
Hope it Helps
Srini

Transport Request import Error

Hello Experts,
When I import transport request SAP system from another SAP system then getting error as "Result of cross-total check indicates a damaged data file (9114)" with the return code 16. Please suggest any one what is problem and how to resolve it?
Thanks.

Hi,
You can generate a transport os copies for the sae request an release it to get a proper datafie and cofile.
Regards,
Nirmal.K

Transport request's

hi Frds,
plz light on the transport request purpose, importance and procedures in sap implementations, if any doc available with screen shots plz mail to [email protected]
thanks in advance and good day guys
thanks
mohan.m

Dear Mohan.M,
For more information about the SAP Change and Transport System (CTS), visit the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm
Transport Request is generated in following scenarios:
1. Customizing Request - When doing or changing some customization.
2. WorkBench Request - When configuration is cross-client. Eg Generating new Table, making changes in access sequence, Abap development, etc.
Transport request is not generated for Master Data. For eg: Customer Master, Material Master, price master, etc.
Benefit of Transport Request:
SAP Landscape normally has 3- Tier system:
Development Server - Where customization takes place. Transport request is generated at this level & then first transported to Quality server for testing whether it meets the requirement or not. Once the requirement is met in Quality server then Request is transported from Development Server to Production Server (Actual / Live System)
Quality Server - Mainly useful for testing.
Production Server Actual / Live server, where the real transactions are created & posted.
Procedure to Release & Transport Request:
1. In development server, go to T.Code: SE10 & select the check box Modifiable & enter
2. In the next screen, you will see list of transport request created.
Note: Transport request consist of main request along with sub request. These sub request hold the object to be transported.
3. Expand the main request & you will be able to view the sub requests attached to main request.
4. First release the sub requests.
Note: To release the request, select the request ni & click on release request individually (Do not select release all request)
5. Next release main request.
6. Once the request is released sucessfully, imform the basis person to import the request to QA server.
or
If the authority is with you, through T.Code: STMS, select development server --> select request no & release to QA server. Here when it pops up client no, user id & password, maintain it of QA server & release the request to QA server.
Hope this will help.
Regards,
Naveen.

Identify the transport request for released Objects from BW(any BW Object)

Hi
How do i identify the transport request in which i have collected the BW Object(Say Transfer rule) which got released to the testing system.
Please guide me.
Thanks,
Satya

Hi Satya,
Just follow these steps,
1)Go to the Update Rule and Double click on the Rule.
2)Click on Extras->Object Directory Entery>In hte Heading u can c Object.
3)This Objectr has Detials>R3TRUPDR-->Tech Name of Update Rule
4)Come to SE03
5)Come to Eiight Row-8 and Enter UPDR in the 3 Column adn the Tech Name in the 4 Column,TICK it and Execute
Now it will display when and all it gpot transported.
Similarly u can do it for Objects like MPRO for Multiprovider,ODSO for DSO,ETC
Rgds
SVU123
Edited by: svu123 on Dec 10, 2009 12:05 PM

Bex Transport request is not available

Hi guys
I want to change the Bex query from query designer, when i go for change mode it didnu2019t allow me to change and throws error message "Bex transport request " is not available or not suitable" and in second line it gives "choose an existing request.
Can any one tell me how to change the Bex query with a transport request?
Gaurav

Hi,
You get this message if you have captured the query in a transport request and released or transported the request.
You can somply capture the query in a new request again from transport connection and then you will be able to edit the query.
even after capturing the query in the request is not allowing to edit then you need to try the option as explained by our friend above.
Regds,
Shashank

Incorrect Transport Requests : SAP delivery version getting collected

Similar Messages

Maybe you are looking for