How to migrate the concurrent manager to another server

Dear all,
My EBS structure is DB+APP. but now, the APP pressure is very high because this server includes another test intsance. I want to migrate the concurrent manager from the APP server to DB server, How I can do this?
My EBS is 11.5.10.2 and the platform is AIX 5.2
Thanks

Can I use the following the Note:230672.1 step to add this DB node as the application node:
========================================================
You can use Rapid Clone to clone a node and add it to the existing Application System. The new node will run the same or a subset of the server types running on the source node. Follow the instructions in the Application Tier part of Clone Oracle Applications 11i:
Prepare the source system, copy it to the new node and configure it.
After adcfgclone.pl completes, source the Applications environment and run the following commands on the target system:
cd <COMMON_TOP>/clone/bin
perl adaddnode.pl
=======================================================
Devon

Similar Messages

How to migrate the concurrent managers definations from one instance to another

How to migrate the concurrent managers definitions from one instance to another instance by using FNDLOAD in R12.1.3
Greatly appreciate any help on this.
Thanks!

Concurrent managers can't be migrated using FNDLOAD -- Tips and Examples Using FNDLOAD (Doc ID 735338.1)
What are you trying to achieve here? Why migrating CMs from one node to another?
Thanks,
Hussein

How to Migrate the 12 Hives to new server in new farm

Dear All,
How could I migrate the 12 hives to new folder ??
Are there specific folder I just copy/past or I just copy everything and override the original ?
Thank you

My first question would be why? Any customizations, hopefully, should be in .wsp format.
Assuming you have manually copied files into the hive folder and are looking to get them to the new server, copying the whole hive across is a really bad idea. What I have done in this situation (more than once) is to use a differencing app such as Notepad++
(with plugins) or WinMerge (my personal fave).
1) Copy the hive from the source server to a temp folder on the destination server
2) Use one of the apps above to compare the two directory structures
3) Copy across just the missing files from the source folder to the destination hive
By doing it this way you ensure you don't damage your fresh clean hive on the new server, and you should be able to get across the manual customizations you need.
Good luck!
-Corey

How do we migrate the OWB mapping from one server to another server?

Here is my situation.
Source server
================
Project name : SOURCEOWB
Under this project, we have two module(MBTSOURCE, MBTTARGET).
In connection explorer, the locations are DW_MBT_SR, DW_MBT_TR.
We have 15 mappings on this project.
Source schema name is TXMBT_DW.
Target schema name is MBTTX_DW.
I want to migrate the whole thing to new server.
Here are the info about target location. After migrating to new server, i need to rename
as below.
Project name : CA_SOURCEOWB
Under this project, we have two module(CA_MBTSOURCE, CA_MBTTARGET).
In connection explorer, the locations are CA_DW_MBT_SR, CA_DW_MBT_TR.
Source schema name is CA_TXMBT_DW
Target schema name is CA_MBTTX_DW
Here are my steps i followed.
===============================
1. Created the source and target schemas in new machine.
2. Create a new workspace
3. Export the mapping with dependent objects from source server and imported in new server.
4. changed the source and target location successfully.
5. Renamed the project namd, module names as i needed successfully.
But only issue is, i am not table to change the location name.
Again, i tried the below steps.
1. uninstall the workspace and create the workspace
2. create source and target locations as i needed(CA_DW_MBT_SR,CA_DW_MBT_TR).
3. import only mapping
4. Able to register the mapping
Here i am not able to configure the module for newly created locations.
I right clicked on module and click Configure, go to Stream Administrator and not able to find
the source and target locations over there.....
How do we resolve this?
My data warehouse is runing for each state. I want to copy one state mapping and import into
another state and customize the mapping. I have hard time to change the location name. Because,
location name has state code. I can not use the same location name for all other state.
Any help is highly appreciated.

Hello Oleg, Thanks for your input.. It helps... but the problem is not completly solved.
let me explain my whole steps. Plesae review and let me know if i missed anything.
1. Created new workspace. the workspace is successfully created.
2. Login to new workspace.
3. Go to Locations, create source location(entered host name,username, password etc)
4. Created target location(entered host name,username, password etc), go to db connector on target location, created new db connector and linked the source location here.
5. Exported mapping and import into new workspace.(I can not use the location name in the exported workspace).
6. Renamed the project name, module name as i needed.
7. Double click the module name under Oracle and changed the meta data location and data locations.
8. Right click on soure and target module and click configure, change the the location and streams administrator.
9. Right click on mapping and go to configure, go to table operators and change the location as i need.
10.Right click on target module(under oracle), click generate. On this step, i get the below error
VLD-1141: Internal error during mapping generation.
Java.lang.ArrayIndexOutOfBoundsExeception
11. Go to control center, register the source and targert and followed the step 10. I get the same error.
I am almost close to complete this task. But i got stuck in the last step.

How to run EBS:CP:Executable Synchronous, outside the concurrent manager

Is there any way , the executable, defined in Concurrent Manager can run Synchronously ie outside the concurrent manager.
Thanks.

If you run the executable through CM, it sit in the Queue and CM run the job based on the resource availability and that is asynchronous process.
We can access the Executable information based on the CP Report short name, What I am looking for is some logic/API, where I can execute/run this executable (example Oracle Report ) directly, by-passing the CM and get the output. May be some Synchronous process to display report/output as online not as schedule.
Or I can hold of API, which CM use to submit the Job from the Q. here I am not talking about the FND_REQUEST.Submit_Request API. this actually submit the request to CM Q. I am looking for the API, which further pick the request from the Q and call executable and run the request and generate the data.
Thanks.

How to get the concurrent request id while running a concurrent program

Hi All,
I am working with oracle apps r12.
I have created a custom report with some parameter. And i have created a parameter P_CONC_REQUEST_ID.
And in the report i have used SRW.USER_EXIT('FND SRWEXIT'); in after report and SRW.USER_EXIT ('FND SRWINIT'); in before report trigger.
when i ran the report from the application, I didnt get the conc request id in the parameter. It not passing the concurrent request id.
Can any one tell me how to bring the concurrent request id.
Thanks & regards
Srikkanth
Edited by: Srikkanth.M on Mar 14, 2012 1:56 PM

Hi;
FND_CONCURRENT_REQUESTS
This table contains a complete history of all concurrent requests.
FND_RUN_REQUESTS
When a user submits a report set, this table stores information about
the reports in the report set and the parameter values for each report.
FND_CONC_REQUEST_ARGUMENTS
This table records arguments passed by the concurrent manager to each program it starts running.
FND_DUAL
This table records when requests do not update database tables.
FND_CONCURRENT_PROCESSES
This table records information about Oracle Applications and operating system processes.
FND_CONC_STAT_LIST
This table collects runtime performance statistics for concurrent requests.
FND_CONC_STAT_SUMMARY
This table contains the concurrent program performance statistics generated by the Purge Concurrent Request and/or Manager Data program. The Purge concurrent Request and/or Manager Data program uses the data in FND_CONC_STAT_LIST to compute these
Also see:
concurrent request details
Find history of concurrent request details
How to determine the user who placed a certain concurrent request?
Regard
Helios

How to check Internal, Concurrent Manager status in Oracle Apps R12 from fr

Step by step how to check Internal, Concurrent Manager status in Oracle Apps R12 from front end and how to start them.

Richa wrote:
Step by step how to check Internal, Concurrent Manager status in Oracle Apps R12 from front end Concurrent Processing - Concurrent Manager Generic Platform Questions and Answers [ID 105133.1]
and how to start them1) Using adcmctl.sh (from the backend)
2) Using Activate button (from the front-end) -- http://docs.oracle.com/cd/E18727_01/doc.121/e12893/T174296T174302.htm#4334248
Thanks,
Hussein

How to migrate the Objects from 3.1c to BI7

Hi,
We are in Functional Upgradation.
How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
Please help me to doing this....
regards,
anil

BW Upgrade tasks (BW 3.1C to BI 7.0)
Prepare Phase:
Task     How-To     Who
Review BI 7.0 feature lists     Review BI 7.0 feature lists for possible inclusion in developments.     Basis/BW
Obtain the BI 7.0 upgrade guide     Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
     Basis/BW
Review all upgrade SAP notes     In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
     BI 7.0 Upgrade notes
     SAP Web Application Server 6.40 upgrade notes
     OS and DB specific upgrade notes
     SAP BW Add-on upgrade notes
(e.g. SAP SEM, ST-PI, etc)
     Plug-In upgrade SAP notes
     Other notes identified in above notes and/or upgrade guides.
     Basis/BW
Check DB and OS requirements for the target SAP BW release     Check DB version/patch level and OS version/patch level required for upgrade
     First check the most current information from the SAP BW homepage http://Service.sap.com/BW -> <SAP BW release> -> Availability
     Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
     Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
     Basis
Check SAP BW Add-on upgrade requirements     Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
     SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
     WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
     Basis
Check SAP BW upgrade requirements          Minimum Support Package and kernel levels for upgrade
     SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
     Source system Plug-In requirements     Basis
Check compatibility requirements with 3rd party software          3rd Party Reporting tools (example: Crystal)
     ETL Tools (example: Ascential, DataStage, etc)
     Scheduling tools (example. Control-M, Maestro, etc)
     Monitoring tools (example: HP OpenView, Patrol, etc)
     Other OS or DB related tools     Basis
Check new component requirements for BI 7.0          If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
The IGS chart migration will also be required after the SAP BW web report conversion.
     If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
     If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0. (ArcView 8.2?).
     If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides -> SAP NetWeaver).
     Basis
Test and distribute new SAP BW Frontend
          Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
     A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
     After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
     Basis
Alpha Conversion:
Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool)      Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
Transaction RSMDCNVEXIT
Check the system status:
     u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
     u201CNo Check yet/Inconsistent Internal Vales existu201D:
The Alpha converter check has not been executed.
     u201CCharacteristics have Inconsistent Internal Valuesu201D:
The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
     BW
Upgrade SAP Note updates     Check for newer versions of your SAP notes for the Upgrade.
Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
     Basis/BW
Confirm SAP BW support package, kernel and DB/OS configuration     Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
     Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
     Basis
Alignment of SAP BW objects within your SAP BW system landscape     Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
     This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
     Basis/BW
Confirm all developments are deployed.     Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
     In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
For SAP BW developments not already collected in the transport collector, a decision must be made:
Deploy the developments or wait until the upgrade has completed to deploy.
o     Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
o     Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
     In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
     BW
Implement BI 7.0 Business Explorer Frontend     Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
     Basis/BW
Pre-upgrade Process:
Download required BI 7.0 support package Stack for inclusion in the upgrade     Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
     There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
     It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
     BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
     You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
     Basis
Apply latest Support Package tool patch     Apply latest SPAM patch before executing PREPARE     Basis
Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency     Check Database consistency
     Transaction DB02:
o     Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
o     Check missing database objects (indices, tables, etc)
o     Missing indices may identify erred data loads or process problems
Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
Note: check for running data loads before executing a repair!
o     Check DDIC/DB consistency
     Verify database objects and consistency
(e.g. SAPDBA check for offline data files)
     BW
Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
     This reduces the numbers of database objects that need to be copied during the upgrade.
     Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
     BW
Validate your SAP BW Objects for correctness prior to your upgrade     Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
Note: this test should be repeatable so you can re-validate after the upgrade!
     Ensure that any inconsistencies are identified and corrected
     RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
     Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
     BW
Ensure DB Statistics are up to date prior to the upgrade          Check DB statistics for all tables.
Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
     Check DB statistics for missing Indexes for InfoCubes and Aggregates
o     User transaction RSRV to check      BW
Check SAP BW Support Package status     Check the status of all support packages (via transaction SPAM)
     Ensure the Support Package queue is empty
     Confirm all applied Support Packages     Basis
Check all u2018Repairsu2019     Check for unreleased repair transports
     Release all unreleased transports
In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
     Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
     BW
Check InfoObject status          Check for revised (modified) InfoObjects that have not been activated.
All InfoObjects should be active or saved (not activate):
o     Check all inactive InfoObjects:
Transaction RSD1 (Edit InfoObjects),
click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
Modified InfoObjects are denoted by yellow triangles!
o     Determine if revision should be activated or removed.
     'Reorgu2019 or u2018Repairu2019 all InfoObjects
This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
     Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
     BW
All ODS data loads must be activated.          Activate all inactivated ODS Object requests.
All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
o     Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
     BW
All Transfer and Update rules should be active          Check for inactive Update and Transfer Rules
o     All update rules and transfer rules should be active or deleted.
o     Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure.     BW
All InfoCubes should be active          Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
o     All InfoCubes should be activated or deleted.
o     Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
     BW
All Web Report objects should be consistent prior the upgrade.          Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
o     For Original release SAP BW 3.x:
A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
Please see SAP note 484519 for details.
     BW
Backup your system before starting PREPARE     Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
     Database admin
Address any instructions/errors generated by PREPARE          Address any issues listed in log files Checks. Log generated by PREPARE.
o     Repeat PREPARE until all checks are successful.     Basis
Complete any Logistic V3 data extractions and suspend V3 collection processes          Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
o     The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
     Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
     BW
Complete any data mart data extractions and suspend any data mart extractors          Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
o     The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
     Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
     BW
Check that your customer defined data class definitions conform to SAP standards          Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
o     Check your data class definitions as detailed in SAP Notes 46272 and 500252.
o     Incorrect data classes could create activation errors during the upgrade.
     BW
Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
     This reduces the numbers of database objects that need to be copied during the upgrade.
     Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
     Basis/BW
Backups!     Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
     Database Admin
Before Execution:
All SAP BW administration tasks should have ceased          Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
     Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
- timing depends on the type of upgrade selected
     Basis/Admin
Remove unnecessary SAP BW temporary database objects     Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
- timing depends on the type of upgrade selected
     BW
Check system parameters     Check OS, DB, and Instance profile parameters.
     Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
     Check for any DB specific parameters for BI 7.0
     Check for any new OS parameters     Basis
Check Database archiving mode     Turn database archive log mode back on if it was disabled during the upgrade!
     Database Admin
After Execution:
Check the systemu2019s installation consistency     Execute Transaction SICK to check installation consistency
     BW
Check the system logs     Perform a technical systems check.
     Example: Check system and all dispatcher logs (inc. ICM logs)
     Basis
Apply latest executable binaries     Apply the latest 6.40 Basis Kernel for all executables
     Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
     Basis
Review BI 7.0 Support Packages for follow-up actions.          Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
o      Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o     Follow any required instructions identified in the SAP Notes
     Basis
Apply latest patches          Apply the latest SPAM patch
     Apply any required support packages that were not bound into the upgrade.
     Basis
Apply additional BI 7.0 Support Packages
(if required)          SAP recommends that customer remain current on SAP Support Packages.
     Review SAP Notes for all SAP BW Support packages applied in previous task.
o      Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o     Follow any required instructions identified in the SAP Notes
     Basis
Resolve any modified SAP delivered Role issues      If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
     Review and implement SAP note 569128 as required     Basis
Configuring Information Broadcasting EP/KMC Connections
     If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
     Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
     Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
     For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
     Basis
Re-check SAP BW Object and consistency     Execute RSRV to check SAP BW Object consistency
     Repeat tests that we executed prior to the upgrade.
     Validate results      BW
Check InfoCube views for consistency     Check consistency of InfoCube fact table views
     It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
     BW
Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks          If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
     The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
     It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
o     Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
     Check that all other Source Systems are active.
o     Activate as required.     Basis/BW
Check SAP BW Personalization is implemented     (SAP BW 2.X upgrades will have performed this in the previous task).
Validate that personalization has been activated in your SAP BW system.
Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
     Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
     To activate highlighted Personalization, click Execute.     BW
For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert ODS secondary indexes to new standard     For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
     Re-create all indexes in the ODS Object definition screen in transaction RSA1.
     ODS indexes must conform to the new naming convention
     BW
Converting IGS chart settings
     Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
     Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
o      Test via transaction RSRT
     Execute the conversion process as directed the BI 7.0 upgrade guide.
     Note: This step is required for all BI 7.0 upgrades     Basis
Backup your SAP BW system     Perform a full database backup (including the File system)
Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
     Database Admin

How to find the senior manager

hi gurus ,
i am involved in the extension of the standard workflow of leave approval , i want to extend the approval level. in std the is one approval level which identifies the manger of the employee who requested for leave . my work is to extend to another appoval level to his senior manager . so when manager approves the workitem , then it should go to senior manger for final approval .
for the first approval i got the agent through RULE 0000168 . how to find the senior manager ?
Message was edited by:
arumugam shanmugam

You can also try Rule AC00000157. In this rule you get the manager by providing the Position Id. This is useful when you know only the Position Id of the user.
<b>Reward points if useful</b>

How to Migrate the Existing Content

Hi every1,
I want to know how to Migrate the existing content in Interwoven to new Content Management system
Thanks & Regards
Vasu

Hi Vasu,
as said, I don't know Interwoven in detail. But if you would get the Interwoven Business Package, maybe you could get some insight how to access Interwoven content per API (at least, Interwoven <i>has</i> a Java API, see http://blogs.ittoolbox.com/km/content/archives/005150.asp for example; but I would ask Interwoven or within some Interwoven forum for the details, and on this site for the details of SAP KM API... ).
Hope it helps
Detlev
PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

How to migrate the Hyperion Enterprise to HFM 11.1.1.3

Dear All,
Can any one know how to migrate the Hyperion Enterprise to HFM 11?
What are the pre requisits?
Thanks in Advance....

Hi,
I assume the decision of changing software is due to some specific requirements regarding the information for the actual customer. So the question should probably focus on an analyse of what kind of information the new system should cover and how to provide it, rather than having a focus around a technical solution. If you just migrate to another software you will not take in to consideration the new specific advantages in that new software.
Good Luck
Annika

How to migrate the SAP KM Content to MS SharePoint

Hi
How to migrate the SAP KM Content to MS SharePoint
Is there any links that can give me brief view on this

we can integrate portal content to share point check this below link for[ Integrating SAP Portal Content into Microsoft SharePoint Portal Server|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6844e48d-0901-0010-b4b2-d5666689ca8b] and [Integrate Microsoft Sharepoint Services into Knowledge Management|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ba1508-27e7-2a10-2295-9dab5b78c614]. hope these helpful.
regards
Mahesh

Script to completely shutdown the concurrent manager

Use this script to shutdown the concurrent manager completely. It will wait till all processes die.
#!/bin/sh
# Author: Praveen Gattu
# Created: June 2007
# Figure out how you want to pass the variables DB_USER (username
# for APPS schema) and DB_PSWD (password for APPS). You can
# hardcode in this script (not recommended), prompt the user
# to enter them, etc.
# stop the concurrent manager
$SCRIPTS_TOP/adcmctl.sh stop $DB_USER/$DB_PSWD
# check if the processes are alive
SPOOL_FILE="$APPLTMP/stop_cm_$TWO_TASK.tmp"
while [ "$RETURN_VALUE" != "0" ]; do
sqlplus -silent $DB_USER/$DB_PSWD << EOF
spool $SPOOL_FILE
select concurrent_queue_name, running_processes
from fnd_concurrent_queues
where running_processes > 0;
spool off
EOF
egrep --silent "no rows selected" $SPOOL_FILE
RETURN_VALUE=$?
if [ $RETURN_VALUE -ne 0 ]; then
echo "Concurrent manager processes are still active. Sleeping for 10 seconds..."
sleep 10
fi
done
rm $SPOOL_FILE
echo "** Concurrent Manager and its processes are stopped **"

Far as I know DSH exist by default in AIX env, but you can create it on Linux\Unix env.
Creating DSH in a Linux Env.
1 - Configure passwordless SSH between Nodes using root user.
2 - Create a file /etc/dsh.conf with all hostsname separated with space in a line ( ex. node1 node2 node3)
3- Create a script "/usr/local/scripts/dsh" as follow:
#!/bin/bash
COMANDO=$*
NODES=`cat /etc/dsh.conf`
     for NODE in $NODES
     do
     echo $NODE:
ssh $NODE $COMANDO
     done
exit 0
4 - Change permission of file /usr/local/scripts/dsh to 775
Just run
# /usr/local/scripts/dsh date
or
# /usr/local/scripts/dsh /u01/app/grid/bin/crsctl stop crs

How to acquire the concurrent request id in data template?

Hi all,
I want to know how to acquire the concurrent request from my report data template. I've created a placeholder for my parameter +<parameter name="p_conc_request_id" dataType = "number" defaultValue="0"></parameter>+ and for nothing ... i've got the 0 value.
I need the concurrent request id in order to detect the user who launched the report. Is there other way on getting the user ??
Thank you!
All the best,
Laurentiu
Edited by: laurentiu on Jul 8, 2009 5:29 PM

Hi,
I read your previous post about this solution but i was not able to retrieve it. Here is step by step what i've done:
- added the parameter to my data template
- added the parameter to my concurrent program
- added the parameter in my pl/sql package
- i've run my concurrent request and the value returned in my xml is 0 for the concurrent request id parameter
I don't know where i'am getting wrong ?!?
Thank you!
All the best,
Laurentiu
Edited by: laurentiu on Jul 8, 2009 6:47 PM

How secure is the password manager?

How secure is the password manager?
Can someone hack into it and steal my password?

You can protect stored password using master password. See:
* https://support.mozilla.com/en-US/kb/Protecting%20stored%20passwords%20using%20a%20master%20password

How to migrate the concurrent manager to another server

Similar Messages

Maybe you are looking for