WF Transport 4.6B to ECC6

Hi all,
     I need to transport the workflow objets from SAP 4.6B to ECC6, but the transport finishes with the follow warning:
u201Cu2026
Comienza import R3TRPDWS90000026...
different nametabs for table SWDSHEADER (field ORIG_VERS).
u2026u201D
     After transporting the workflows, it exists in the transaction SWDD but its definition does not.
     is there any way to transport the workflow objetf from 4.6B to ECC6 correctly??
     Thanks for all..
Martín.

I checked the active version plan and it's ok.
I try to transport  WS* and TS* objects, with a transport order from enviroment of development 4.6B to enviroment of development ECC6.
The tasks TS* are ok in ECC6, but the workflow model is empty (it hasn't definition). All tables SWD* (SWD_HEADER, SWD_STEPS, etc.) are also empty for the WF that i try to transport.
Trank for your help.
Martí

Similar Messages

  • Error while uploading Transport request from SAP ECC6.0 EHP4 to SAP ECC 5.0

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

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

  • Is it possible to transport objects from 4.6C to ECC6?

    Hello,
    Apologies if I am posting this in the wrong forum. I have developed some custom z-tables and an application in ABAP / Screen Painter on a 4.6C server. Is it possible to transport these to an ECC6 system? Otherwise I will have to recreate everything on the ECC6 server. Help is appreciated, thanks.
    Regards

    Hi,
    Yes it is possible, Please login into target system(ECC6) get data and cofiles from source system (4.6c) using ftp method then import the transport objects using tp addtobuffer and tp import with the help of below example.
    Ex:
    tp addtobuffer transportname SID pf=\usr\sap\trans\bin\PROFILE_NAME
    tp import transportname SID client=nnn U16 pf=\usr\sap\trans\bin\PROFILE_NAME
    With Regards,
    Krishna.

  • ECC6.0 - upgrade from EHP4 to EHP6 - cross release transports.

    Hi Experts
    We are planning to upgrade our system from ECC6.0 -EHP4 to EHP6.
    Source - ECC6.0-EHP4
    Target - ECC6.0-EHP6(Enhancement pack6)
    Current ECC version -
    SAP_BASIS 701 0014 SAPKB70114 SAP Basis Component
    SAP_APPL 604 0013 SAPKH60413 Logistics and Accounting
    We would like to know during the project if we can do a transport
    between upgraded development ECC6.0 -EHP6 to non upgrade production ECC6.0-EHP4.
    We have data from note 1090842 and 1273566.
    But last 10 lines of note 1090842 are contradictory wherein on one side it says you can do transports between Releases 7.0*, 7.3* and 7.4* and
    on other it says it can be problem if support pack levels are different on same release.(if problem can happen on same release with different pack
    level then there are greater chances of issues between different releases).Note 1273566 is clear and suggest no issues exist yet for
    technical and logical transports between suggested version 700/701 to >=702
    Also below is the extract from SUM guide - (SUM-1.0-SP07)
    RECOMMENDATION
    We strongly recommend that you perform transports only between systems of the same release or enhancement package level, and where the same business functions are activated. If you do not follow this recommendation, you do so at your own risk regarding potential problems.
    Please suggest if we need to create Dual maintainance parallel landscape during the tenure of project where two development system co-exist.One
    with current and one with upgraded version and changes need to be done on both in parallel.Support fixes and LTO’s go from non upgraded dev to non upgraded prod.
    Thanks

    Hello
    I won't perform cross version transport even if it can be possible.
    As of 7.02 cross version transport are prevented by default with option SP_TRANS_SYNC (see here under note).
    The best way is, if possible, to have a manual dual maintenance. All corrections created in the Ehp4 dev should be manually recreated in the Ehp6 dev.
    What is usually done is to upgrade at first a copy of production for test/discovery purpose, the aim is to identify most of the regressions/evolutions. This will reduce the time you will have to spend in the migrated dev to adjust your system. You then migrate dev and enter in a freeze period where you reduce activity on legacy Ehp4 system to the minimum (bug correction for prod).
    One good thing with the manual reprocessing of changes on the Ehp6 system is that this kind of constraint will help consultants to reduce their activity.
    Regards
    1742547 - Information about component version check in TMS

  • Open Authorization Objects in role after role Transport

    Hi All,
    I have transported a R/3 (ECC6, support) role from Dev to QA and Dev (Multiple clients). After transport, Role has authorization tab with status (green) but when i display authorization data i found one new open authorization object (yellow).
    I already have generated profile before tranporting. Role is also okay in  Dev other clients (We have multiple clients in Dev) with status green and no open authorizations (yellow)
    Any feedback/suggestions ?
    Thanks in advance
    Khasim.

    This happens when PFUD runs at the same time as you are generating the role. Refer to this note: 355030 - Loss of authorizations after profile generation. Another remote reason could be if your source (DEV) and target (QA) systems use different characters sets. (Note #535554).
    If it is the former case, re-transporting your role may just be the solution for you. Just re-generate the role in DEV and initiate a new transport.
    Hope this helps.
    Ashutosh

  • Transport Customizing using IDOC + Transport request generation

    Environment :
    HR DEV Env --> HR Quality --> HR Production
    ECC6 Dev Env --> ECC6 Quality Env --> ECC6 Production Env.
    I want to transfert HR Customising done on my HR Dev env to my ECC6 Dev Env.
    We have isolated custom table to transfert (like T500P or T529T ...).
    My question, If I use IDOC/ALE to transfert table T500P from HR Dev to ECC6 Dev, is "standard" transport request generated to transport this customizing to ECC6 Quality then Prod ?
    I know that SolMan is the best to do this (http://help.sap.com/saphelp_sm32/helpdata/en/44/abe83bd199883de10000000a11402f/frameset.htm) but I want to study this solution.
    Any inputs ?
    Best regards

    Solution Manager is the best way for doing this

  • What're the steps for transport??

    Hi All
    I have the new task, we want to pass the informatión from ECC 5.0 to ECC 6.0, then I have to finish the process of transport, but I don't know What are the next steps after the status of transport is released?
    Can you help me  with information about this topic?
    thanks very much
    danny

    First of all, i dont understand why you want to transport from ECC5 to ECC6.
    SAP does not recommended to do transport from older version of SAP to a new version of SAP. Its because the same objects in the older version may not be similar when it comes to new version and some of the older versions may be obsolete in the new version which can bring inconsistencies especially if its customizing requests.
    If its z programs, you should compare the objects in the old and new systems which you are going to transport and if there is no conflicts, you can.. But its not recommended to do the transport from old to new version.

  • Stms problem

    Dear experts:
    I was troubled in my transport system. Our ECC6.0 system run on AIX server, the transport system is very simple, there are only two systems in the landscape,filesystem /usr/sap/trans is export from development server and then mount on production server by NFS. However, as the user ID and group ID in DEV and PRD OS are different, so everytime a change request is released in DEV system, when I try to import it into PRD system, there is a popup with error infomation "Transport control program tp ended with error code 0212 Errors: could not access file as supposed (see dev_tp or". And this error is caused by OS authorization according to the log, the two transport file generated in DEV system couldn't be read by prdadm dur to the authorization limited. So how can I solve this problem?
    Thanks all very much!

    Thanks for your reply.
    Yes, there are only two systems in transport route, and DEV is the domain controller.
    I have checked in SAP system and the result is ok.
    To avoid authorization problem, I grant 777 to directory trans and then prdadm is able to cotrol files in this folder, but the problem is even the folder authorization is 777, after I release a new change request, the new files are generated with 664, usr and group is devadm:sapsys in DEV system, however, in PRD side, prdadm doesn't have authrization to control this file, as sapsys group ID isn't same in DEV and PRD system.
    So everytime I need to change anthorization for the two files manully before it can be imported.

  • How to create Transport request in R/3(ECC6)

    Hi all,
    Can somebody tell me how to create the transport request in ECC6.0
    Regards
    Kiran Kumar

    Kiran,
    From RSA5 --> Choose datasource and select "Activate Datasource" --> system prompts for transport request. Do not save as local object. assign package and assign to transport request.
    From RSA6 --> Select datasouce --> choose transport(truck icon) --> follow same as above
    From LBWE --> if you do any changes or customization system prompt for transport request.
    Hope it Helps
    Srini

  • ECC6 V_TIBAN Transport for House Banks IBAN

    Hi SAPer,
    I wonder if you have experienced this.
    As I am now implementing ECC6 and  trying to transport IBAN for house bank account.
    The IBANs are stored in the application table TIBAN ane even though I
    transport House Banks, NO IBANs were transported
    As 4.7 or before, I would normally  use transaction SM30, enter the table V_TIBAN and transport, which is OK because it set as maintenance is allowed
    However, in ECC6 system, V_TIBAN does only have "Display/Maintenance only allowed with restriction" hence am not able to SM30 transport. The change in View setting appears to be out of SAP box.
    Would any of you shed some light on how I would be able to work around this?
    Thanks for your tips
    taro

    Hello,
    We have ECC 6.0 and is able to create entry in V_TIBAN successfully.
    Please go to SE11 > View V_TIBAN. Go to tab "Maintainance Status"
    In "Access" part, radio button selected should be "Read, Change, Delete, INsert"
    In "Delivery Class" it should be "A Application table (master and transaction data)"
    In "Data Browser/Table View Maint" it should be "X Display/ Maintainance Allowed"
    However if your setting is different, then you must have a support pack restricting the access to V_TIBAN in SM30. See the below OSS note 983944, which provides and alternative in such scenario:-
    [https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=983944]
    This should solve your issue.
    Regards,
    Gaurav

  • Report painter transportation from 4.6b to ecc6

    Dear Report painter expert
    We have two deferent servers one is 4.6 b and another one is ecc 6.0. In 4.6 b they are created 130 reports by using report painter. Now they are doing Migration to 4.6 b to ecc6 and globalization (clubbing all the servers into one server).
    My query is it possible to transport all the 130 report from 4.6 b version to ecc6.0 or else we have create the all the report manually.
    Regards,
    Venkataswamy

    Hi
    Read the SAP help which talks about "Dependant objects" tick.. It says dependant objects except Cost Center and Cost ele groups are transferred..
    Does the Set 0102DBAGXE_INVEST  pertains to Cost centers or cost elements
    If yes, Go to GS03, and Menu UTILITIES > Export .. Export it in a flat file and import it in ECC 6.0 before importing the reports
    Regards
    Ajay M
    SAP HELP TEXT ENCLOSED BELOW
    Indicator: Export/import all dependent objects
    If you set this indicator, all dependent objects in addition to the desired objects are exported or imported.
    Example
    If you export or import a report group and the indicator is set, all reports in the report group, all sets (or set hierarchies) contained in the reports, the set and value variables as well as the library will also be exported or imported.
    Exception
    Groups from CO (such as cost center groups, cost element groups) are not transported as dependent objects. If you want to transport groups from CO, this must be done explicitly.
    Does the

  • Transport from ECC6 to 4.6C

    Hi there,
    I need to transport a whole lot of custom development objects including ABAP, screens, functions, tables etc. They are all contained in a single workbench request.
    The original system is a unicode ECC6 (700) system running off Win 2008 R2, MaxDB 7.6. The target system is non-unicode R/3 4.6C
    I am no Basis Administrator - my problem is that this is an unusual request that basis admins don't really have experience with, so I am being left to find a solution myself...
    When I try to import the transport files into the 4.6 system I get an error related to unicode to non-unicode transporting.
    I have checked the following notes:
    Note 330267 - https://service.sap.com/sap/support/notes/330267
    Solution: First import into a byte-oriented system (that is, a system where one byte is used for each character) with Release >= 6.10. Then export the data from this system. The resulting export can then be imported into earlier releases.
    This is not an option as I don't have a non-unicode system available with version 610 or later.
    Note 1090842 - https://service.sap.com/sap/support/notes/1090842
    A general prerequisite for this type of transport is that the R3trans belonging to the system is used during both the import and export processes.
    I don't really know what this means - can anyone shed some light on what I need to do to try this?
    Note 638357 - https://service.sap.com/sap/support/notes/638357
    Up to now, such transports have not been possible, because in Basis releases prior to 6.10, R3trans cannot understand the internal format of the transport files that result from the export from Unicode systems.
    Transport profile parameter "exporttoascii" is available as of the tp and R3trans versions listed below. If you set "exporttoascii=true" in the export system, a transport file is created during the export from Unicode systems that can also be imported into old Basis releases.
    I have tried to use the following command with no luck - "D:\usr\sap\<SID>\DVEBMGS00\exe\tp export <SID>K900079 "-D exporttoascii=true"". I run this command while logged in as <SID>ADM, but get the following error - "Connection failed (RTE:could not create comm. shared memory \[51\])". When using STMS in SAP to release a transport normally it works fine, so not sure why the TP command will not work??
    Note 1113226 - EXPORT/IMPORT: UC converter for R3TRANS - https://service.sap.com/sap/support/notes/1113226
    A converter was developed that
    u2022     converts the internal format of the exported data into the older format and
    u2022     converts Unicode characters that are contained in the exported data into code page 1100 and adjusts the length accordingly.
    The transport tool R3TRANS uses this converter.
    Patch text: EXP/IMP: UC converter for R3TRANS
    Check SAP Service Marketplace to see whether the patch is already available for your platform and apply it in accordance with Note 19466.
    I checked this but again, I don't fully understand this note - it does not seem very clear what should be done. I have searched the downloads center and have not found any converter utility...
    I would really appreciate any help on this!
    Thanks very much
    David

    Hi David,
    In my opinion, Note 1090842 should solve your requirement.
    I hope the following section from the note is already taken into consideration for your import procedure:
    Furthermore, general logical transport problems occur that are not specific to a certain release, especially concerning the usage of functions that are not available in the previous release.  When you, for example, use functions that exist only as of Release 7.1, especially ABAP statements, the return transport to lower releases is not recommended. At least, you must manually repair these objects after the import. In cross-release development projects with regular transport requirements, we recommend that you carry out your developments in the earliest target release and then transport these developments to subsequent releases because this is usually linked to fewer complications.
    A general prerequisite for this type of transport is that the R3trans belonging to the system is used during both the import and export processes.
    The R3trans is an executable file which is a part of the SAP system's kernel (in location /usr/sap/<sid>/SYS/exe/run). This tool is used by the tp program while perfoming any export/import activities. The R3trans is usually different for different releases - the same way that you need different kernel files for different releases. However as per the above prerequisite, it is suggested to have the same R3trans executable file being used during the export from source system and import to target system. Means you would have to copy the ECC 6.0 system's R3trans file to the 46C system kernel directory before performing the import.
    Regarding the R3trans version required on your systems, as per Note 638357, you need to use the tp and R3trans files with release date later than June 02, 2008. So taking the latest tp and R3trans files available on the SMP should be enough.
    Also suggest you to check thread:
    Transport objects from 4.6C to ECC 6.0?
    Regards,
    Srikishan

  • Transporting of z objects form Older version(4.6c) to newer version(ecc6.0)

    Hi All,
    Now i am involving in Technical Upgradation from 4.6C to ECC60.I want to know some information regarding  transportation of Z objects in older version to newer version(ECC6.0).Please help me in this regard.
    like tables,dataelements,domains,reports,scripts,smartforms,userexists,Variants,report layouts(all are z objects),text elements.In the above list which will be transported automatically and regarding which abapers have to takencare i mean to say which will be not transported automatically...
    and tell me obsolete keywords information..which will be obsoleted in ECC6.0...
    thanks in advance
    awaitinf for reply..
    Points will be Rewarded for helpfull Answeres
    Thanks & Regards
    Samit

    Hi Julio,
    you can find the answer in the SAP note
    Note 552711 - FAQ: Client copy
    point 4.
    So the answer is : NO
    Kind regards
    Imre Takácsi-Nagy
    Senior Support Consultant II.
    SAP Global Support Center Austria
    Netweaver WEB Application Server ABAP / JAVA

  • Moving/Transporting programs from 46c to ECC6

    Guys,
    For our upgrade we will start with a ECC6 system from scratch.  The questions are - is there a tool to transport ABAP programs/functions from 46C to ECC6?  Or in your experience it is better to manually do a download from 46C then manually upload to ECC6?
    Thanks for your input.
    Yan Guan.

    Hi Yan,
    If you are upgrading an existing 46C system to ECC 6.0 then the Z and Y programs  in the system will be there even after your upgrade.
    We will start with a brand new ECC system from scratch
    means you are creating a system for the first time as ECC 6.0 ?. Then if there is transport path between your 46C sytem and ECC 6.0 sytem, you can transport the objects. Otherwise go for download/upload option. But I think creating a transport path is the better option.
    Regards,
    Soumya.

  • Transporting BAPI from ECC5 to ECC6 - FM definition isn't avail at target

    Hi
    I have a BAPI developed in ECC5 System - ZBAPI_TEST, under a function group - ZFG_TEST within a package - ZPKG_TEST.
    All these objects are assigned to the same TR number.
    I have released, generated Co/Data Files and moved these TR (Co/Data Files)  to ECC 6 System.
    The associated structures are available in ECC6 System - where the Function Module name is present - BUT NO SOURCE CODE!!!
    Is there any special rules we need to follow while transporting a BAPI from one system to other?
    Thx
    Rich

    Please check if the the two includes also have activated and moved or not.
    if yes try a re transport.

Maybe you are looking for