CHARM: UCs - Import error in transports

Hi, 
in UC, when any transports imported in production with result error code 8, how do we proceed?  currently BW developers make manual correction in production and we can't change status completed for UC. It remains as production.
Thanks,
Digesh
Edited by: digeshjoshi on Jul 28, 2009 11:36 AM

solved myself.

Similar Messages

  • Import error in Transporter

    Hi
    I Tried to import a zip.file in my QA environment from dev (export was successful).
    I have an error when importing. Do you where to locate the log file indicated in the error message. I don't know where to search on the server .
    Thanks
    Anthony

    Anthony,
    What SSM version are you on? And are both DEV and QA at the same SP level?  An important thing to remember is that the either the bootstrap.zip or import.zip files you transport into SSM have to be the ones that are matched with the SP level. In other words, you couldn't transport a SP5 import.zip file into a system that is at SP6.
    The Default Trace log file is <drive>\usr\SAP\<Netweaver 3 letter instance name, like default CE1>\J00\j2ee\cluster\server0\log
    the file you want to look at will be the one with the most recent Date Modified time.
    The HOME directory is where the transport files will reside after successfully being deployed and this path is slightly different depending on whether you are using SSM 7.0 or SSM 7.5 - the path below is for SSM 7.5
    <drive>\Program Files (x86)\SAP BusinessObjects\Strategy Management\Application Server\home
    For others reading this, when transporting into SSM you have two choices, import.zip and bootstrap.zip. The difference between these two zip files is that IMPORT brings with it the sample data and BOOTSTRAP does not. Because that is the only difference, you do NOT have to load both, only one or the other.
    Regards,
    Bob

  • **urgent**Transport Import error

    Hi All,
    I tried to access Import screen under Transport. But Im getting following error:
    An exception occurred while processing your request
    Exception id: 11:36_07/03/08_0027_73601150
    See the details for the exception ID in the log file.
    The following is the exception from Trace file:
    #0003BA9B25FE00710000021C00005A76000447DAF4D496E9#1204905642855#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#73##n/a##82f11c40ec5f11dcbc240003ba9b25fe#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#/System/Server#Java###Exception ID:11:00_07/03/08_0018_73601150
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.system_admin_ws/com.sap.portal.transport/com.sap.portal.transport_packages/com.sap.portal.import
    Component class : com.sapportals.portal.transport.ui.ImportComponent
    User : Administrator
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.sapportals.portal.transport.ui.ImportComponent.doContent(ImportComponent.java:266)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         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:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         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:524)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Error occurs during the compilation of java generated from the jsp
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:116)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 36 more
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2189)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
         ... 39 more
    Can some one through some light on it. Appreciate your respo

    Ravi,
    Looks like the import folder had "Read only" access set.
    You might want to refer to this SAP Note : 681323.
    You can also refer to this link( Though is talks about EP 6) :
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f570c7ee-0901-0010-269b-f743aefad0db
    Cheers,
    Sandeep Tudumu

  • Error in transporting request through charms

    Dear Experts ,
    recently refreshed my quality systems data with production data ..and finished successfully, but we did not take any screenshots before doing refresh in quality
    my problem is we already configured charms in solution manager to transport requests to production system ...
    now we are  not able to transport request through charms .. because rfc connections are changed in quality ...
    please let me how can i recollect quality rfc connections for charms ...
    i dont have idea about charms configuration to reconfigure in quality.... please help in this
    Regards

    Hi,
    You need to transport the ODS 1st and then the transformation.
    The main reason for most of the transports to fail is:
    1)Transporting each and every object in the same transport request.
    Ideally,
              u2022The Infobjects should be transported first in a separate request.
              u2022Then the Data source and the Info providers (Cube, ODS, Data source and Multiproviders) together in a separate request.
               u2022At the end the transformations and the DTPu2019s in an another separate request.
    If the above mention sequence is followed while transporting the transport failures can be avoided.
    2)Also when a change is made to an ODS (I object added or deleted) it should again be transported along with the transformation but in separate request.
    I.e. the ODS 1st and the transformation.
    hope this helps.
    Regards,
    Mahesh

  • Error While Transporting Transformation

    Hi Gurus, I have this issue that I am getting an error while transporting Transformation. I made sure that that only transformation is sected and nothing else. I am getting this error message while importing it in BWQ environment "Formula 4AY060939P5D2NKRXKMJFECLS is already locked in the requests of other users or the system is set so that formula 4AY060939P5D2NKRXKMJFECLS can no longer be changed."
    I was wondering, if this is locked by some other object or transport request, how can I find that out? Thanks in advance for all the help.

    Hi,
    You can check if the request is locked by another transport in BWQ by using the transaction SE03.
    First find the object directory entry for your object(you can take this from your transport. Go to SE03 --> 'Search for Objects in Requests/Tasks '. Under object selection enter the details as in your transport and select the check box against your new entry. Under Request/Task selection, select 'Modified' and 'Released'. Execute. You will now see a list of transport requests that contain your transformation. Check these & either release them or delete your object from the modifable transports. Re import your transport.
    You can check if this object was locked by a person using the transaction SM12.
    Regards,
    Shilpa

  • Error while transporting the TR to production

    Dear experts,
    I am facing the issue of TR error while transporting it to PRD. I have already checked, the table is active both on DEV & on QUI. What should I do to transport this without any error? Thanks in advance.(Please find attached screenshot.)

    Hi,
    this looks like you forgot a transport request or have transported in the wrong order.
    Check that the table ZPLANTS is active (or has been activated with this transport request in step IMPORT).before the generation starts. Please check also the complete IMPORT protocol.
    Regards,
    Klaus

  • Error while transporting 0MAT_PLANT

    Hi Experts
    I am getting error while transporting 0MAT-PLANT to Prod System.It going fine to QA system.
    it is giving the follwoing error with return code 8
    Characteristic 0MAT_PLANT: Master data has to be activated before conversion
    Start of the after-import method RS_IOBJ_AFTER_IMPORT for object type(s) IOBJ (Delete Mode)
    Errors occurred during post-handling RS_AFTER_IMPORT for DTPA L
    RS_AFTER_IMPORT belongs to package RS
    The errors affect the following components:
    BW-WHM (Warehouse Management)
    I have deleted one Info-object (Key figure) and added one info-object(Key figure) to 0MAT_PLANT ,transported still it is giving errors it is going fine to QA.
    1.Is it because we have large no of records in Prod system ..??
    2.Do we need to delete the data in Prod for 0MAT_PLANT and transport....????
    3.Is it related to any database error in adjusting P table in Prod...?
    Please let me know anybody faced this kind of problem.
    Regards
    Prasad

    Hi Prasad,
    Just to summarise the discussion. If you need to send the transport successfully you need to the following steps:
    1. MD (complete) needs to be deleted from IOBJ. Please note, unless you delete the TD data involving the IOBJ, you will not be able to delete MD completely.
    The reason being, the SID's for the MD are being used in the various IC/DSOs. So you need to go by deleting related TD and then MD.
    2. Secondly, if you forcibly delete for 'P' and 'S' table using the SE14-> Table Name -> Delete Data & adjust Db. This will cause lot of inconsistencies on Drill Down in reports and even on execution as SID values are missing!
    Moreover, as you said there are around 10/12 InfoProviders involved here, then this forcefull deletion can cause a real imapct to your Prod system and make many reports unsusable! So pls be careful!
    Please decide accordingly as there is a trade off here!
    -VA
    Edited by: Vishwa  Anand on Sep 27, 2010 12:15 PM

  • Error while transporting - Source RSDS 8ZRF_O01 LOGDBQ151 does not exist

    Hi,
        I am getting following error while transporting export DataSource to quality system.
    Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)
    No rule exists
    Source RSDS 8ZRF_O01 LOGDBQ151 does not exist
    Start of the after-import method RS_DTPA_AFTER_IMPORT for object type(s) DTPA (Activation Mode)
    Transformation does not exist (see long text)
        Although, the request is failing, I can see the DataSource 8ZRF_O01 present in the QA system. Only the transformation is set inactive.
    Regards,
    Pranav.
    Edited by: P D on Sep 20, 2010 9:02 AM

    Hi
      might be your data source not collected into transport request.
    If you are moving data source from once system to other system, this may missed.
    RSA1->Transport connection>all objects>Datasource --> Select your data source as only neecessary to move
    When ever we are moving objects from one system to other follow below are order to avoid failures
    1).New Infoobjects.
    2). Data source/Infosource
    3). Info Providers ( Cube/DSo)
    4). Update rules/Transformation
    5).Impacted objects and other
    Mahesh.

  • Error while Transporting Update Rules.

    hi xperts,
       I am getting Error while Transporting the Update rules,i already transported the INFOCUBE,INFOPACKAGE EVERYTHING.
        Start of the after-import method for object type R3TR ROUT (Delete Mode)
    Errors occurred during post-handling RS_AFTER_IMPORT for ROUT L
    The errors affect the following components:
        BW-WHM (Warehouse Management)
    Is the  error,I didn't change any thing in the Cube or changes to Update rules.
    Can anybody Help me?.
       thanking you,
                                   with regards,
                                   Narendra.

    Hi,
    Are you still facuing the issue ?
    No need to worry about the routines, once you save the update rules if there is any routines in it it will be saved in the same request. If you want to check the routines you can check in the transport connections. Transfer the update rule to the right hand side of the screen and you can see all the routines that belong to the UR.
    If you know the technical names of the routines you can check in the TADIR table.
    Have you transported the info-sources for this update rules ? why not you again capture the info-source and the update rule in a single request and transport again.
    Hope it helps.
    Thanks,
    Soumya

  • Error while transporting Transformation: Syntax error in Start Routine

    Hi Everyone,
    I'm facing a strange problem during transporting one of the Business Content cubes from Dev. to Quality.
    I'd activated the DSO 'Purchase Order Items (0PUR_O01)' and its entire data flow from the 4 datasources 2LIS_02_CGR, 2LIS_02_SCN, 2LIS_02_SGR, and 2LIS_02_ITM from BC. Then I migrated the Transfer/Update rules to transformations and the DataSources to BI7 DataSource. So far so good. The migration was successful and all the objects were activated.
    Now when I transport the same to Quality, the import fails with return code 8 and the error message says:
    'Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)'
    'Start Routine: Syntax error in routine'
    I verified that the transformation where the error orrured was the one from InfoSource Z2LIS_02_ITM to DSO 0PUR_O01. I went and checked the start routine and it did indeed have a syntax error:
    'In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter SOURCE_PACKAGE" is incompatible with the formal parameter DATA_PACKAGE". '
    But when I check in the Dev. system, there is no syntax error for the same routine. Later, I tried to transport only the said transformation by re-activating it in Dev, and again I got the same error.
    I have no idea why I'm getting a syntax error in the start routine when there are non in the Dev. system. Also none of the coding is customised, it was only the BC code, migrated to a transformation.
    Any suggestions on the steps I could take to transport the transformation to my quality system?
    Thanks,
    Ram

    Hi Ajay, Shanthi, svu and Ray
    I do indeed have a start routine in my transformation and it was migrated from a 3.x update rule to a BI 7 transformation routine.
    The migration was successful and the Start Routine has NO syntax errors in the start routine in the Dev. system. I only encounter the error while transporting it to the Quality system. I cannot modify the code in the Quality system because it is non-changelable and there is no point in trying to change the code in Dev. because there are no errors over there.
    I've also made sure that I've transported all the necessary objects required by the transformations to quality. The routine does not perform a lookup, it simply deletes some records from the data package based on the processkey value (which is itself present in the data package).

  • Error when transporting a transformation (Update rule) BI 7.0

    Error when transporting a transformation (Update rule) BI 7.0
    Hi all,
    I’m trying to transport the transformation between the infocube 0FIGL_C10 and the ODS 0FIGL_010 from BI Dev into BI QAS. I kept getting a return code 12.
    Transport message:
       Program terminated (job: RDDEXECL, no.: 18141700)
       See job log
       Execution of programs after import (XPRA)
       End date and time: 20070620181432
    I go to the log and I got the following message:
    Job started
    Step 001 started (program RDDEXECL, variant, user ID DDIC)
    All DB buffers of application server vrxsapq1 were synchronized
    ABAP/4 processor: ASSERTION_FAILED
    Job cancelled
    I’m using BI 7.0
    I don’t know what it is. Can someone tell what should I do or what I’m missing?
    Thanks a lot
    Regards
    Vic

    Hi Victor,
    check this thread may it solves your problem
    Re: Error during the creation of transport request
    one more thread
    /message/2785863#2785863 [original link is broken]
    cheers
    Sunil
    Message was edited by:
            Sunil John

  • Error in TRansportation

    Hi Experts,
    I am getting error while transporting co_area(Data source)
    Error Msg is like this
    Transfer structure 0CO_AREA_TEXT_PA does not exist
    in my request I Included Transfer structure 
    why Iam getting Error Msg
    it,s showing one more error Msg
    Error RSAR 440 during after import handling of objects with type(s) ISTS
    Message no. RSO857
    Diagnosis
    When handling objects of type(s) ISTS, an error message (RSAR 440) was not caught. The error message can be found directly before this message in the log.
    This message was caused by a program error. The error occured in module RS_ISTS_AFTER_IMPORT.
    System Response
    The objects of type(s) ISTS cannot be activated correctly.
    Procedure
    In the SAP Support Portal, search for SAP Notes with the error message RSAR 440 and key words
    After Import Handling
    RS_ISTS_AFTER_IMPORT
    ISTS
    Create a customer message if you cannot find a suitable message for the error.

    Hi Shilpa / All,
    We are getting the same problem. Can you please let us know how you solved this issue?
    We are transporting some business content and getting the following error.
    "Transfer structure 0TCTISOURC_TEXT_SA does not exist
    Message no. RSAR440"
    If somebody know the solution, please let us know.
    Thanks,
    Kul

  • Source System Error While transporting

    Hi SDN,
    We are transporting requests to a deployment test box SN1 and we are getting this error message while we never got this error message transporting to QAS and in QAS we did not need to create DEV010 as a source system - setting up RFC connection was sufficient.
    Any thoughts?
    ===========================================================
    Source system DEV010 does not exist
    Message no. RSAR409
    Diagnosis
    Source system DEV010 is not known.
    System response
    The imported data for data source 8ZM_C42 was deleted again as the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP to an available productive source system.
    Procedure
    Create the referenced source system in the Administrator Workbench or define a mapping to a known source system in table RSLOGSYSMAP.
    You get to the maintenance using Tools -> Conversion of the logical system names.

    Speak to your basis team and ask them to make entries in table:
    RSLOGSYSMAP .
    Are you trying to transport info source or any source system dependt object? If so, this error is understandable.
    This has been discussed several times and pl search the forum.
    Ravi Thothadri

  • Error while transporting Enhancement set to QA

    Hello All,
    We are implementing AAK for a product. We have imported all the Transport Requests from DEV to QA. We have created a Change Piece List Package and did object check list. We got errors regarding table contents of Enhancment set like 'Table Contents(Cross-client, delivery class C) : No import'. Contents in the table are BSPWD_EHSET_DEF, BSPWD_CMP_C_REPL, BSPWD_COMP_EXT, BSPWD_EHSET_ASGN.
    Please suggest me a solution.

    YOu can try transporting the entries using generic keys.

  • Error checking transport group configuration in System BQS

    Hi Everyone,
    I made a client export from Production to Quality. It went successfully,, I noted the requests numbers and transported them from PRD to Quality, but while transporting there was a tp error(which i did not note), next i went to the quality import queue and saw all the 3 requests had come. But when i click the adjust queue icon im getting the following error message "Error checking transport group configuration in System BQS" .  Afterwards i tried to delete the requests from quality to retransport  from production but still im not able to delete those requests from quality. Can anyone help me solve this.
    Regards,
    Rahul

    Hello Rahul,
    regarding the error message:
    "Error checking transport group configuration in system"
    It's mostly related to the TMSADM RFC destination. Kindly follow the below mention steps:
    1. Logon to client 000 with user DDIC.
    2. STMS   > System   > Overview   > Select the system in which you are logged in   > Click on the menu says EXTRAS   > Generate RFC Destinations
    Perform the above steps in all the systems configure in your TMS. This should resolve the issue.
    Best regards,
    Tomas Black

Maybe you are looking for