Transport in ECC

I have enhanced two 'z' fields to a standard datasource.
When I transport it to quality system, the new 'z' objects do not come over.
Please let me know the steps to collect so that the z objects are also transported with the datasource.

Hi Chris,
To transport you need to collect following things,
1) Append structure - Go to the RSA6-> datasource-> double click extractor->append structure -> activate and collect.
2)  Datasource (active version) - Go to RSA6 -> datasource in change mode  and collect it.
3) CMOD source code in any
Last but not least make sure newly added Z fields are not hidden in the extractor.
If you collect all above objects, Z fields shoudl be available in Quality.
Hope this resolves your problem
Regards,
Viren

Similar Messages

  • Re-collecting and Transporting in ECC after system copy

    Dear Friends,
    I have a situation where i had enhanced a datasource with some Z fields in ECC DEV and had transported them to ECC QA a while ago . Now the basis did a system copy from ECC PRD to ECC QA recently and all my transports are no longer in the Q to re-import to ECC QA. Please let me know if there is a methodical approach in re-collecting these transports in ECC DEV to QA so that i dont miss anything. Any help will be appreciated.
    Thanks
    Raj

    Raj,
    Try to add required request to Quality Import Queue and reimport.
    STMS --> Import Overview --> Choose Quality --> Disaplay requests --> (From Menu) Extras --> Other requests --> Add --> add required requests no.
    Once request added it will reflects in import queue of Quality. Try to re-import.
    Srini

  • How to transport query - ECC 6.0

    How can I transport a query in ECC 6.0?
    The screen has changed from the usual in the earlier versions. There is no option asking for Export / Import or Upload / Download.
    Lakshman

    Hello,
    You can generate transport request using program RSAQR3TR.
    Thanks,
    Venu

  • Transports from ECC 5.0 to ECC 6.0

    Hello,
    We are considering using transports from the 5.0 system to make configuration changes in the 6.0 system (and even some workbench items). Besides, the obvious issues with conflicting configuration, is there a technical reason why they should not attempt this? I look for notes to know it, and there are the note NOTE 1090842, but there are no answer for transports between realese ECC 5.0 to ECC 6.0. Do you know if it is a special case?
    Thanks in advance for your answer,
    Xènia

    Hello,
    This is always a bad idea.
    However, if you feel like that, I only recommend it if you are transporting Z objects that you know perfectly. This way you can make corrections at the very moment the potential problem happens.  Before the import, please compare both objects, in release 5.0 and 6.0, and look for the differences. Plan what would happen if the 5.0 object replaces the 6.0 one.
    Don't do it with standard objects.
    Regards
    Francisco

  • Transport for ECC and PI for proxy communication

    We have both Outbound and Inbound scenarios between ECC and PI and developed accordingly. We also created both client and server proxy in ECC system. While transporting to the next system is there any dependency that first we need to transport the PI transport and then ECC transport. Or this is totaly independent that ECC transport will create the proxy automatically without having the ESR objects for te corresponding PI system.

    Hi,
    There is no rule like first you need to transport PI stuff then Proxy code in ECC.
    first you have to establish the connections(proxy communication) in new environment ,after that transport ABAP stuff and PI .
    PS: don't forget to register queue's in ECC and PI.
    Regards,
    Raj

  • Solman_stms to monitor transports in ECC

    Hi There,
    I have a business requirement that we need to use solution manager to monitor the transports in our ECC landscape and some time later we should be in a position to do transports from solution manager only.
    can any one help me if they were in this situation before.Im very new beeie in solman.
    current ECC landscape
    DEV QAS AND PROD(we also have target groups configured from dev to qas and also from qas to prod)
    and solution manager EHP1 just patched to sps25.
    my thoughts:
    1. is it enough to create a domain link from solman to ECC PRD( domain controller).
         NOte:solution manager has stms configured with virtual system.
    can you please guide me through appropriate path
    Regards
    raj

    Yes, this scenario is quite feasible for SAP ChaRM.  See the Solution Manager IMG information for setting up domain links:
    If multiple transport domains are used and projects in the Solution Manager have been defined as cross-domain projects, you must define inter-domain links between the transport domains, regardless of whether change requests are moved between domains or not. If, for example, the Change Request Management system is in domain A , but the satellite systems between which requests are transported is in domain B, Change Request Management has to trigger transports in a foreign domain. This is only possible by means of domain links.
    Also see SAP Help topic at the link below for setting up the domain controller:
    http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a0b47acc11d1899e0000e829fbbd/frameset.htm
    May I ask - which system of yours is set up as a virtual system?  Why would you need a virtual system in a basic dev-qa-prd landscape?

  • Transport of ECC/SRM datasources activation

    Hello
    I want to transport the activation of standard ECC or SRM datasources.
    When I use the transportation icon (truck) in the RSA6 screen, the system indicates "action successfully completed" but it doesn't ask for a transport request.
    How can I include these activations into a transport request?
    thanks
    Crystelle

    Hey, when you are activating a data source, right then it will/should ask you for a transport request. If its not doing that, talk to your basis. If you want to move a datasource that is already transports, then you may have to change it/de-activate(delete) it and then activate it again. but its tricky job and you cannot do this safely on all datasources (especiall the ones that already has an existing delta queue).
    Just in case, talk with a basis or Sr. Consultant about the complete requirement.
    In summary, if you want to transport a new datasource, as soon as you activate it, you will get a transport request. If it didn't, Its important that you talk to basis. They have to change some parameters.
    If you want to move already transported data source, tell us why? If you are making chages to it, it will then ask for a transport request.
    Uday Chamarthy

  • Report variant not transport to ECC 6.0

    hi all,
    after migration from SAP 4.6 to ECC6, i cant see the SAP transaction report variant not transaport over....is there any SAP table store the user variant not transported ?
    Thanks .

    Pls. check manual:
    Phase SAVE_VAR_CHK
    After the upgrade, many of your variants can no longer be used because the relevant selection screens
    have changed. If your Basis Source Release is 4.5B or higher, the SAP system offers two reports to
    save the variants:
    n RASUVAR1 saves your variants on the source system.
    n RASUVAR2 restores the variants in the target system.
    During phase SAVE_VAR_CHK you can decide whether you want the upgrade tool to run report
    RASUVAR1. The report is started in phase JOB_RASUVAR1. If you have decided to run report
    RASUVAR1, phase JOB_RASUVAR2 automatically starts report RASUVAR2 towards the end of the
    upgrade.
    For more information about the reports, see SAP Note 712297.

  • Can we Transport CRM,ECC,EP request from SOLMAN 4.0

    Hi ,
    We are under NW2004s implemnetation CRM5.0,XI7,BI7,and EP7.0.
    Client wanted to Implement transport configuration from solman 4.0 to all these components.I have experiance on Individual component STMS .
    Not sure how to transport from solman.
    As i know that solman is only monitoring system.Can we transport CRM,EP,BI,XI tranport request from SOLMAN .Istaead of loggin in other systems?
    Your reply would be greatly appriciated.
    Thanks
    Kristene

    Just to elaborate a little more on the point above that "All the existing transport requests in queue will be transported to SOLMAN STMS"...
    This is quite correct, when SolMan takes control of your landscape all the old transports, however far they've gone on their way to production, are visible from SolMan (STMS)...
    However, if you've configured TMS as recommended for change request management (and you should to avoid security loopholes) and without reverting to playing around on the operating system level, you'll find that you are no longer able to do anything at all with them (via STMS for example). Stuff unreleased in development, can no longer be released, transports not yet imported in Quality or production cannot be imported... it's like a total freeze on all the 'old' stuff.
    Fairly simple to work around though - before the go live with SolMan, be sure to clear out and get live as much as you can to reduce the number of 'old' transports still in process somewhere.
    When you're live with SolMan, you'll then need to create new Change documents for the 'in process' changes. Follow the SolMan process up to the point of creating transport requests, and then, in the development system, use transaction SE10 to transfer the contents of the 'old' transports into the 'new' ones created via SolMan. You can then use the SolMan process to migrate the transports.
    Generally there's no problem with this, but occasionally, especially for workbench objects, you may find that you can't release the 'new' transports via SolMan. 99.9% of the time this is because the objects are locked in the 'old' transports, but you can usually use SE10 to delete/remove the objects/release or generally mess around with the old transport until the new transport can be released. Beware also that there is a risk of picking up the latest version of an object, rather than the version in the 'old' transport when using this process...
    Hope this helps -ILL

  • Unable to Create Transport request in more then one DEV client (in ChaRM)

    Hi,
    We are having 2 Landscapes,
    DV1 (100) --> QA1(100) --> PR1(100)
    DV1 (200)--> QA1(200) --> PR1(100)
    Both these landscapes are added in the ChaRM Project landscape. When we have created a correction and created a Workbench request, we were getting the option to choose the DEV system and we chose DV1(200). When we tried to create a TR for Customizing in DV1(100) it did not provide the pop up for DEV systems and directly created the customizing request also in DV1(200). We were unable to even create the TR in DV1 (100) - using the task 'Create Transport request' in the Task plan for the corretcion (It gave an Error that the DV1(200) is the Development system for this change).
    is this the standard behaviour? can't we have TRs from different client/ development systems under the same correction?
    Please clarify?
    Regards,
    Kathir

    Hi
    As i said earlier you will get option to choose system for creating Transport Request only in case of normal corr
    but in case of urg corr
    you need to give ibase for production of the cocerned landscape
    e.g if u have ecc and bi and want to create transport in ecc then giv ibase for prd of ecc only
    because you will not get pop up in urg corr
    Hop doubt clarified
    Regards
    prakhar
    Edited by: Prakhar Saxena on May 12, 2010 6:17 AM

  • Cannot See Transfer Rules in Transport Connection

    Hello,
    I have searched Notes and Forums and have not found a solution for this!
    I performed some configuration in our newly upgraded BI system. We
    were on BW 3.5 and upgraded to BI 7.0
    We also change how our landscape was interconnected.
    Our BW Dev system used to connect to our R3 Sandbox system.
    Now our BIDev system connects to our ECC Dev system.
    This is the first project i have worked on since the upgrade was
    successful. What I am finding is that I get the following transport
    error when I look at the STMS logs from BID to BIQ.
    Transport Error
    Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Activation Mode)
    There is no DataSource with these attributes
    Reference to transfer structure 1_CO_PA2900010_DS_BA not available.
    No activation possible.
    Here are the details when I click to get more info on the error message:
    Reference to transfer structure 1_CO_PA2900010_DS_BA not available. No
    activation possible.
    Message no. RSAR436
    Diagnosis
    Transfer structure 1_CO_PA2900010_DS_BA should be transported into this
    system.
    However, no DataSource mapping refers to this transfer structure.
    System Response
    The transfer structure was not activated or deleted.
    Procedure
    Ensure that DataSource mapping, with a reference to the transfer
    structure 1_CO_PA2900010_DS_BA is on the same transport request. Use
    the transport connection to create a consistent request.
    Wierd Behavior
    The big issue now is that when i go to the transport connection in RSA1
    and I want to collect Transfer Rules, I see a small subset of all the
    transfer rules I would expect to see. I am looking specifically for
    the transfer rules: 1_CO_PA2900010_DS PCDEVC200
    Similiar behavior occurs when i am looking for "3.x DataSources" in the
    transport connection
    I can see these rules in other areas of RSA1 such as Infosources.
    Please assist with finding these transfer rules in the Transport
    connection.
    Other then this transport both ECC and BI system landscapes are up and running normally.
    Please help
    Thanks!
    Nick

    Bryan,
    Thanks for jumping onto this thread.  I am going to complete the transports and see if i have any system name conversion issues to address.  I may need some guidance on ensuring that BID, BIQ and BIP have the correct entries in RLOGSYSMAP.
    To answer your questions:
    1. Was the new source system added as an additional source system or was the R/3 Sandbox source system renamed?
    Bryan: The new source system was added by renaming the R/3 Sandbox source system/Executing BDLS.  The original source system was PCSNDC200, and we BDLS'd that to PCDEVC200.
    2. To what Source system do the transfer Rules belong to that you are missing?
    ---Bryan: The missing transfer rules (and all source system dependent objects that are missing) belong to PCDEVC200...I fixed the  missing object issue, by going to "transport Connection" and clicking on 'Source System Assignment' (or Shift+F7) and then checking the box for my source system, in my case the box for PCDEVC200 was not checked previously.
    3. Was the "conversion of Logical System Name" entries updated correctly after the new source system was added in BID?
    ---Bryan:  The answer to this question i will find out tomorrow when I transport to Production (fingers crossed, the BID > BIQ transport went well with name conversion!)
    Thanks!
    Nick
    Edited by: Nick Bertz on Dec 21, 2009 3:11 PM

  • XI Dev. connected to ECC Dev and ECC Qas

    Hello Folks,
    I have a question -
    We have 2 XI systems: Development, and Production (no QAS)
    And 3 ECC systems: Dev, Qas and Prd.
    Now we have the XI Dev connected to the ECC Dev.
    I'd like to know if it's possible to also connect the XI Dev System to the ECC Qas system.
    I mean, to create the RFC dest. in both systems, a new Business System for ECC QAS; and all the necessary config.... and if it won't take problems when we have to transport the Interfaces from DEV to PRD.
    Thanx in advance.
      Juan

    Hi juan,
    just be carefull when you add you QUA config in ID and then when you will transport...
    1. in your ID, when will define the config with QUA, do NOT ADD the object to your Scenario.... if for the transport you choose the option "Transport all objects of my Scenario"... else you will have a problem in Prod because of the system QUA. Indeed with transport DEV become PROD but your ECC QUA cannot become ...
    2. when you will transport to your PI prod :
       - check my first point or use option "Transport by selecting each objects" and choose only object linked link to your DEV.
       - delete also the Condition option (if you have one) in the Receiver Determination if in th receivers list you have DEV and QUA.... because after the transport the ECC QUA become nothing.
    So yes we can. There is no technical issue.... if you do properly the things !!
    Regards.
    Mickael

  • MDG-Hub: Tried and tested methods for ECC customizing synchronization

    MDG Experts, I am looking for guidance on synchronizing configuration and customizing data between ECC and an MDG-Hub. I reviewed documentation on (a) synchronizing via BC set import and (b) via TMS although I was looking for a little bit more detail and steps involved in setting up ongoing synchronization between ECC and an MDG-Hub.
    I am looking for experiences and suggestions on this topic. Thanks in advance.

    Hello Karthik
    I have used - BC sets to transport the ECC configuration to MDG. Another way is to transport the tables directly from ECC environment to MDG.
    Check this -
    http://wiki.scn.sap.com/wiki/display/Basis/Business+Configuration+Sets+(BC+Sets)+and+their+use?original_fqdn=wiki.sdn.sap.com
    Kiran

  • Transport of Objects

    Hi
    I want to transport an ECC- XI - MDM scenario
    This was done by downloading SAP XI Content. The proxy code is in ECC. So when I transport, the XI content, can I include the proxy code in ECC also.
    How do I go about this?
    Regards

    Thank You guys,
    I have one more doubt. Like I said, this scenarios is ECC-XI-SRM. The XI content has been downloaded into the XI system directly from the marketp place. So like wise, the ECC content should have been downloaded directly to ECC from market place, right? I mean the PROXY code and all that. So for a scenario, we need to have two or three downloads friom the market place.
    Is that how it works?
    Regards

  • How does CHARM handle 3rd party provided exteranl transports

    Frequently  some vendors (e.g. BSI , etc) will provide some transports for ECC.
    How to use CHARM to handle those 3rd party external tp?
    Thanks for your help.

    You can import the transports manually to your Dev (save the data files and cofiles in the same /usr/sap/trans and use STMS to add to buffer, you may have to change the project status switch for that), then create a CR document in SolMan as usual, create transport(s) from SolMan and include the external transport(s).
    Regards,
    Raquel

Maybe you are looking for