Transport to consolidation system doesnot reflect in components

Hi There,
We have configured a separate Consolidation system for our WebDynpro developments. and we are using TCS for deployment. After import to consolidation system and TCS deployment , changes are not reflecting in Consolidation system.
We defined new track and its components and after initial imports we got development configuration in Development studio and made changes.
Thereafter we have followed these steps
1) We released and transported all our changes from Webdynpro Studio.
2) started Import on Consolidation tab and all components were successfully imported.
3) started TCS deployer for selected track_c and that also completed, without any error messages
4) test in consolidation system shows webdynpro changes have not been moved.
This is first round of imports on this track, if there is anything we might have missed out.
Please suggest.
Thanks a lot for your time.
Rgds

Solved this..
Created one more request with application files and followed the cycle.. and this time it deployed application. Weird though worked.
Cheers

Similar Messages

Transport to Consolidation system doesn't work

First of all, sorry if this is a silly question but I have to admin I am a little missed with NWDI. Every step we did we have a new error
In this case, we have trying to move a iView using NWDI and process to transport from
Development Environment to Consolidation doesn't work.
We have done all steps to deploy changes in Development and iview
has been updated correctly. But then, when we release the DC in NWDS
and go to Transport View - Consolidation tab and we do the import
althougth we have a successfully message with "Import Finished", the
iview has not been updated in Consolidation system .
We have doublechecked server, port and SDM password in Runtine System
tab for this server and everything is OK.
I have analyzed all logs generated during Import process in Transport
Studio and no error is showed.
I have find in CBS Consolidation builspace and we don't have any activities pending, and additionally the DC doesn't appear in this buildspace. However in Development buildspace it is.
Could somebody help us putting some ligth on it? Where can I to try to obtain log information about why this change is not moved to Consolidation?
Thanks in advance.

Hi Javier,
I have sometimes a similar problem: we are developing WebDynpro applications. The activities are checked in and transported correctly, but on the destination system only the old release shows up.
My solution of this situation is not elegant, but effective (steamroller tactics or in german "Holzhammermethode"):
- Log on to the console of the machine where your destination system for your deployment is running. Start up the (really slow) standalone SDM application and select the components, which are not updated correctly, for undeployment and undeploy them manually.
- After successful undeployment reimport the component/activity in the JDI transport studio again.
As mentioned before, not elegant, but effective. It worked for all the situations now, when the deployment did not work, but there was no obvious reason available.
Regards
Karsten

Transport to consolidation system

Hi ,
A scenario, where multiple developers have worked on multiple DCs. If, we want to release only 3 Dcs (1 Dc + 2 used Dcs) into a consolidation system, we are faced with a very peculiar problem.
The developers have worked with no naming conventions on large number of Dcs. And, now we want to transport only 3 Dcs from them to the Consolidation system.
The approach we are taking is: Synch the latest copy of these 3 DCs from active space, using NWDS open all possible files for edit, associate them with new activity name. (No modifications are done on these files). Check it in again, activate , release this activity from the Transport View of the NWDS.
If in the CMS - Transport Studio, we import only this activity in the Import queue to the Consolidation system, will these 3 DCs get imported Consolidation system?
Or, should we go into all the developer's NWDS, open all checked in activity from the Transport Studio of NWDS, identify all activities related to these 3 Dcs , release them individually and then go to CMS - Transport Studio and import all these activities into the consolidation system to get these 3 Dcs into the consolidation system.
Which approach will work?

1. Will the 3 dcs get imported only if all activities (1st to last) related to them are released from NWDS Transport studio and then Imported from CMS - Transport Studio ?
2. Will single activity in the end which has opened all files for edit, work???
Regards,
Sandeep

Hi Pascal,
I do know that for ACTIVATION (after checkin), if the current activity has predecessor activities, then they will tagged along with this last activity, for the Activation process.
Is this the same case for Activities Transport Release as well (In NWDS-Transport View)?
So, In NWDS, Transport View under Waiting section, when my last checked out for Edit Activity, which has been activated already, and is awaiting release, is Released, all predecessor activities (which has been activated & awaiting release as well) will get associated automatically???
Therefore,
1. I do not have to ask all developers to go open their NWDS-Transport View and hunt for activities pertaining to the DCs to be released.And, then ask them to release it? RIGHT?
2. All I need to do is to release the last activity under Waiting and the rest of all activities by other developers will get automatically attached??? RIGHT?
Thanks,
Sandeep

Business system Doesnot change while transporting

Hi All,
When Transporting my business system from DEV to QA, my business system doesnot change. I already checked in SLD that my DEV business system is pointing to the correct system in QA. Also DEV and QA are on one SLD only.
You guys will be highly appreciated.
Regards,
---Satish

You also have to make sure that the DEV/QAS Business Systems are associated to the respective DEV/QAS XI system. For that, open the BS in SLD, go to the "Integration" tab and check the "Related Integration Server".
Also, make sure that both the DEV BS & DEV XI are inside the same "DEV" transport group in SLD, as well as the QAS BS & QAS XI are both in the same "QAS" group.
Regards,
Henrique.

CHARM activation check failing on "consolidation system for development system SSA-200 in project ZTEST2

Hello,
We are implementing Charmlite and want to activate in project landscape.
We are Solution Manager 7.1 SP11 and testing this scenario in sandbox.
Steps completed:
1. in sandbox domain controller, created two virtual systems and made 3 system landscape, where, I can release the transport and see it in QA system (Virtual system buffer)
2. The LMDB has been updated with Virtual system and in SMSY, the entries of virtual system shows up. The logical components have the client information.
Issue:
in /nsolar_project_admin ->System landscape -> change management, When consistency check is performed, we get error message saying
Virtual RFC is miising (I am guessing, it should be okay)
The logical component is incosistent (This might be the reason the CHARM is not getting activated.
"No consolidation system for development system SSA-200 in project ZTEST2
No track for project ZTEST2 with log. system SSA/200"
For me, when i look in satellite system, the consolidation system is a virtual system and it should be fine.
Please advise
Regards,
Durga PK Saitana

Thank you Karthik. Still the problem persists
I went through the blog earlier. I created l ABAP instance manually in SLD and moved into LMDB and can see the entry in SMSY. (I did not see any option of putting virtual flag)
We were trying harmonization of RFC from note 1384598 and since we had virtual systems, went with domain links.
After domain links, the virtual systems are read. the Dev ABAP system is not able to find the consolidated system. In the satellite system, I can release transport and move the transport.
Not sure, why this issue is persistent.

Import into Consolidation system failed

Hello,
We are on NW04s and tryign to import ESS component and other standard components like SAP_JEE,SAP_BUILDT into the Consolidation system and import fails in between with the CBS Log as:
Build number assigned: 7851
Change request state from QUEUED to PROCESSING
INTERNAL BUILD request in Build Space "D77_ESS11ADC_C" at Node ID: 778,177,350
     [id: 7,845; parentID: 7,539; type: 32]
REQUEST PROCESSING started at 2007-12-14 23:25:37.149 GMT
===== Pre-Processing =====
Calculate all combinations of components and variants to be built...
     "sap.com/ess/jp/fam" variant "default"
Prepare build environment in the file system... started at 2007-12-14 23:25:37.227 GMT
     Synchronize development configuration... finished at 2007-12-14 23:25:37.227 GMT and took 0 ms
Development line state verification started at 2007-12-14 23:25:41.336 GMT
Verification of the development line [ws/ESS11ADC/sap.com_SAP_ESS/cons/active/] SUCCEEDED
Development line state verification finished at 2007-12-14 23:25:41.352 GMT and took 16 ms
Cache verification, level 2 (Comparison of attributes) started at 2007-12-14 23:25:41.352 GMT
Verification of the following object:
     [DC: sap.com/ess/jp/fam, group: 0] SUCCEEDED
Cache verification finished at 2007-12-14 23:25:41.368 GMT and took 16 ms
     Synchronize component definitions... finished at 2007-12-14 23:25:41.446 GMT and took 4 s 219 ms
     Synchronize sources...
===== Pre-Processing ===== finished at 2007-12-14 23:25:50.227 GMT and took 13 s 78 ms
Change request state from PROCESSING to FAILED
ERROR! The following error occurred during request processing:java.lang.OutOfMemoryError
Unknown reason (java.lang.OutOfMemoryError)
REQUEST PROCESSING finished at 2007-12-14 23:25:50.243 GMT and took 13 s 94 ms
What can be dome to fix the OutOfMemory Error...?
Any help would be highly appreciated..

Hi Shikhil,
Please do the follwoing
1. Incrrease the memory size by navigating to Check the CBS settings in the Visual Administrator->Services->Component Build Service-> Tab 'Properties'
2.Refer to this thread
CMS Error importing into Consolidation System
3.SAP NOTE 723909
Thanks
Pankaj

No consolidation system found for FMD-121 (project EU_FMPM01)

I have created the maintenance project EU_FMPM01. Added the logical components. Created the IMG project. When I go and try to create a maintenance cycle I am getting the error explained in the subject
"No consolidation system found for FMD-121 (project EU_FMPM01)"
What could be the reason for this ?
Thanks & Regards : Bobby Bal

Hi Bobby,
Which is your TMS landscape for the systems in project EU_FMPM01
DEV---->TST----->PRD
       ! zdev
       !------>
        sap
From DEV to TST this are consolidation routes SAP and ZSID
From TST to PRD delivery route
Ensure that you have follow all SPRO activities for TMS in solman and satellite systems.
If you go in solman to /nstms you can see the above systems routes?
Hope this helps,
Dolores

Response message became too slow, after transported to Consolidation Sys!

Hi guys,
I have a sync interface with BPM who calls an HTTP service.
In development system things work fine and the interface is really fast. It gets a response from HTTP service in a few seconds (also with big messages, over 2 mega bytes). After transported to the consolidation system, the response message became too slow and after 600sec it gets a timeout.
No parameters on Integration Server and RZ10 were changed
Anyone knows whats happening or have an idea?
Thanks in advance,
Ricardo.
Message was edited by: Ricardo Quintino

Hi Udo,
What do you mean "the channels are not transported 1:1"?
One thing, the difference between Development XI and Consolidation XI is that Consolidation is in Cluster.
I need to do some extra configurations for HTTP in Cluster systems?
Thanks in advance.
Regards,
Ricardo.
Message was edited by: Ricardo Quintino

No consolidation system found for SID in solman

Dear All
I am configuring Change Request Management is Solution manager EHP1
I have created required Domain Link in Solman and satellite (dev) system
And it is working fine
When I am creating project in System LandscapeChange Request under
Project Landscape, Activate Change Request Management tick
It gives me following error when I click on Check button
Error:-     No consolidation system found for SID-300 (project SOLMAN_CON)
Error:-      No track for project SOLMAN_CON with log. System SID/300
Error:- Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for SID-300
Pl suggest
Regards
Gopal

Hi,
My Transport route looks something like
[System GND] ZGND > 300 [System GNQ] 300> 300 [System GNP]
Its a standard 3 system landscape with transport routes configured as mentioned above. I followed the write up as mentioned and have kept only one transport route but how do i create a transport route from GND-140 to GNQ-300 .
The layer ZGND has been associated with client 140 which is the development client here. The layer ZGND is the consolidation layer, how else should i associate it with the client 140.
Please advice.
Regards
Ankan

CHARM Configuration Error - No Consolidation System

Hi
Im facing following errors in solution manager's CHARM.
No consolidation system found for SSD-150 (project ZCHARM_GIL)
No track for project ZCHARM_GIL with log. system SSD/150
i have more queries.
1.solar_project_admin > system Landscape> systems i have following config
Logical Component : SAP SOLUTION MANAGER
Product: SAP SOLUTION MANAGER [Solution Manager ABAP Stack]
Product Version : SAP SOLUTION MANAGER 7.0
DEvelopment SYstem : SSD: 150 ( SSD is my solution manager SID)
QAS : Blank
PRD : Blank
Do i need to maintain values GSD , GSQ , GSP (satelite system DEV, PRD, GSP)
2. in my satelite system DOMAIN_GSD transport route
System GSD - GSQ Transport Group - System GSQ
             /GSQTRG
System GSD : Transport Stratergy - Mass Transport Checked
          Transport Layer - ZGSD
target group: /GSQTRGRP/ GSQ 200
                GSQ 300
System GSD : Transport Stratergy - Mass Transport Checked
          Transport Layer - NONE
Transport Route : GSD - ZGSD/SAP - /GSQTRG - 300/200- GSQ
Can i configure charm with above scenarion where transport groups have been defined

Hi
This error occurs if you dont define the client dependent tms route in satellite system.
First visit this blog
First steps to work with Change Request Management scenario in SAP Solution Manager 7.0
then in spro change request management general settings....visit the img help for TMS settings of
further
TMS
TMS Setup
http://help.sap.com/saphelp_nw04/helpdata/en/14/c795388d62e450e10000009b38f889/frameset.htm
more help
http://wiki.sdn.sap.com/wiki/display/SM/ChangeRequestManagement
Regards
Prakhar

What is a Consolidation system

What is a Consolidation system? Especially with respect to BW-Transports.
What is its role and pupose?
Thanks

I think you are talking abuot a 'test' or 'quality' system; after development of a project, all is trasnported in that system (that generally is a fresh copy of production system) to test that everything works well.
If somthing is wrong, correction are made in dev and transported to test again.
When everithing is consolidated, it is transported in prod.
Hope it helps.
Regards

Error when creating Task List: No Consolidation System found

All-
Configuring my Retrofit Scenario. My Project Landscape is maintained as following:
Dev(100) --> QA (200) --> Prod (300) with Retrofit (XXX)
Dev(XXX) --> QA 250
I am getting this error when I try to refresh the project or create a Task List
*No consolidation system found for <SID>-250 (project RETROFIT3)
Message no. /TMWFLOW/TRACK_N806*
If my QA client (250) is already maintained as a QA logical component. What else is missing?

Hi,
I have done something similar and getting error /TMWFLOW/TRACK_N806
My Transport route looks something like
System GND ZGND > 300 System GNQ 300> 300 System GNP
Its a standard 3 system landscape with transport routes configured as mentioned above. I followed the write up as mentioned and have kept only one transport route but how do i create a transport route from GND-140 to GNQ-300 .
The layer ZGND has been associated with client 140 which is the development client here. The layer ZGND is the consolidation layer, how else should i associate it with the client 140.
Please advice.
Regards
Ankan

BUSINESS CONSOLIDATION SYSTEM

Hi Gurus...
Could you please send any document related to BCS (BUSINESS CONSOLIDATION SYSTEM )

HI. Sudheer
Business Consolidation (SEM-BCS)
The following sections contain the documentation on the BW-based component Business Consolidation.
The documentation on the R/3-based component Business Consolidation is located elsewhere. This documentation can be accessed, for example, by calling up Application Help in your R/3-based Business Consolidation system.
Purpose
You can use the SEM component Business Consolidation (Consolidation) to determine the resources of a group (or a similar enterprise or organizational unit), the claims by others to those resources, and the changes to those resources. Consolidation also provides the means for internal and external enterprise reporting.
You can consolidate on the basis of customer-defined consolidation units. Consolidation units can represent, for example, companies, plants, business areas, profit centers, and cost centers. You can also portray matrix organizations (for example, using a combination of companies and profit centers).
You can standardize the financial data reported by individual consolidation units to adhere to the accounting and valuation standards of the group. You then translate the standardized financial data from the various local currencies into the group currencies. Finally, you can eliminate the effects of group-internal relationships (for example, from interunit trade and services). Thus, you calculate the consolidated financial statements as if the group were a single entity.
You can use the analysis functions of SAP Strategic Enterprise Management (SEM) and those of SAP Business Information Warehouse (BW) to analyze and report on your consolidated financial statement data.
Integration
The Consolidation component provides functions to collect master data and individual financial statement data from data files from non-SAP systems as well as SAP systems.
All SEM components are based on BW. These are:
Business Consolidation (SEM-BCS)
Business Planning and Simulation (SEM-BPS)
Corporate Performance Monitor (SEM-CPM)
Stakeholder Relationship Management (SEM-SRM)
Business Information Collection (SEM-BIC)
The data processed by Consolidation is written to the BW system. There you can share the data between Consolidation and the other SEM components. For example, you can:
Collect SEM-BPS planning data for use as reported financial data in consolidation
Use consolidated actual data as the basis for further planning in SEM-BPS.
Features
Versions
You can use versions to execute parallel consolidations with different categories of data (for example, actual data, planning data, forecasting data), using different accounting principles (for example, US GAAP, IAS, German HGB), using different valuations, and/or for simulations.
Hierarchies
You can create hierarchies for almost all characteristics (for example, consolidation units and financial statement items), where some hierarchies have special, consolidation-specific properties.
Consolidation Charts of Accounts
The component enables you to use different charts of accounts for consolidation. For example, this allows you to generate several consolidated financial statements in parallel to accommodate different accounting principles.
Collection and Standardization of Reported Data
You can use online data entry or flexible upload to collect individual financial statement data and other consolidation-relevant data into the consolidation system.
You can post manual entries, for example, to standardize the reported data to meet the accounting and valuation requirements of the group.
Consolidation Tasks
You can automatically execute the following consolidation tasks:
Currency translation (which translates the financial data into the currency of the consolidation group)
Validation
Interunit eliminations (for example, for payables and receivables, revenue and expense, or investment income)
Elimination of interunit profit/loss in inventory
Consolidation of investments
Reclassification
Allocation
Balance carryforward
The automated postings are controlled by the task settings you define once beforehand in Customizing.
Reporting
After performing the consolidation tasks, you can use BW reports to analyze your data. SAP provides pre-defined BW business content (InfoCubes, queries, etc.) for this purpose.
You can use XBRL to create individual or consolidated financial statements.
Execution and Monitoring of the Consolidation Process
You use the consolidation monitor to execute the consolidation tasks and to monitor the entire consolidation process.
Constraints
The automated execution of the elimination of IU profit/loss in transferred assets is presently not available.
The automated execution of consolidation of investments presently only covers the purchase method with the activities first consolidation and subsequent consolidation.
You can use manual posting to perform the consolidation tasks that are not yet automated to meet the statutory requirements for creating consolidated financial statements.
http://help.sap.com/saphelp_sem320bw/helpdata/en/62/f7e73ac6e7ec28e10000000a114084/frameset.htm

Probelms while replicating Data Source and transport into test system

I find the following error messages whilre transporting into test system.
DataSource 0EC_PCA_1 does not exist in source system of version A.
Mapping between data source 0EC_PCA_1 and source system is inconsistent.
DataSource 0EC_PCA_1 does not exist in source system of version A.
Field AFABE will not be delivered from DataSource 0EC_PCA_1 in source system.
any ideas please..........
Enhanced the Extract structure and activated the data source in Source system
Replicate the Data source in BI and install the Infosource through BI Content activated and transport them to Test system.

Hi,
1.First transport the data source from R/3 dev to R/3 quality
2.Replicate the data source in BI Quality ( make sure you that in the data source tab, you are searching the data source below the appropriate source system ---otherwise you data source may not appear)
3.goto rsd1in BI development for activataing the info objects which you have added extra in the info source (z info objects )
activate these info objects and collect in another request
4.transport these info objects from BI dev to BI quality
5.transport entire data source to bw quality.
Thanks,
Tarun Brijwani.
Edited by: Tarun Brijwani on Apr 6, 2009 4:26 PM
Edited by: Tarun Brijwani on Apr 6, 2009 4:26 PM

Condition doesn't work after transport to QAS system.

Hi all:
the condition doesn't work after the workflow transported to QAS system. the workflow designed has a constraint that only the creation of the document of Type M4 can trigger the workflow, but creation of Type M5 document can also trigger the workflow, could you please tell me the possible reason?
Thank you very much

Hi,
Once Try checking as pavan suggested whether the Customizing requested is transported.
To Maintain Workflow start conditions you can also maintain through SWB_COND and ensure its transported.
Regards
Narin

Transport to consolidation system doesnot reflect in components

Similar Messages

Maybe you are looking for