Impact of Migrating the Multiple maintenan Project to Single project

Hi,
I would like to know more details on the Impact of migrating/consolidating Multiple Maintenance Project to Single Solution Magager Maintenance Project.
For exapmple: I have 4 Maintenance Projects with different logical systems running with CHARM functionality, but instead of maintaining these multiple Maintenance project, I can have one Maintenance project and muntiple IMG projects associated with it. If I do so what is the impact to the current CHARM functionality. Based on the IMG projects the CTS projects will be created and CHARM should work fine. But I need a clarity if someone have already the same kind of setup.
Also what is the scope of creating and maintaining the Maintenance projects to a Solution. Please Provide an Impact Analysis.
Appreciate a quick response.
Thanks
Shashi

Make a Buffered Image large enough to handle the size of the final image... say you have 10 jpegs each 100x100, and you want them in a configuration with 5x2... 500x200.
Once you have the images loaded and the new BufferedImage, just paint them into the appropriate (x, y) value of the graphics context of the image.
g.drawImage(image1, 0, 0, null);
g.drawImage(image2, 100, 0, null);
g.drawImage(image3, 300, 0, null);
.

Similar Messages

Need same logical path for multiple objects in a Single project

Dear All,
I have a requirement where I wish to ensure that whenever an object is created in the LSMW transaction (In a Single Project), that object has to be created always under the same logical path name.
This logical path I want to define under the transaction FILE.
Is it possible to get this done?
Please help,
Regards,

Nimish,
Please tell me how to ensue that for every object created we get the same logical path without entering any value.
The path i mean is the one defined in the transaction FILE
Thanks for your input.
Regards,

Multiple Applications in a single Project

I currently have a Flex project that has multiple Applications created within it.
The first application opens the second application via code as follows:
var str:String="event_home.html";
var link:URLRequest = new URLRequest(str);
var v_selectedEventIDCode:String;
this globalEventId = dg_event_listing.selectedItem.ID;
navigateToURL( link, "_blank" );
My 1st question is, can the 2nd application that I open grab values of variables declared
within the application that opened it?
2nd question is, if I have a project with only 1 application defined within it, how can I
open a 2nd Internet Explorer window with some other Flex page in my project without creating a 2nd
application in this project? for example I may have a single Application in this project, and then another
file in this project that is a Canvas component, the app starts up with the Application page, how do I open
a 2nd Internet Explorer page with that Canvas component within it?
Thanks in advance,
Wes

> Is it possible to package multiple applications into a single .air file?
No, Flash Builder (and AIR) does not support that.
-Anirudh

Simplest way to disassemble the multiple xml records to single xml record?

Guys,
I just want to know the what can be the simplest way to disassemble the input xml file into single records.
Can we use built in XML disassemble component in custom pipeline to disassemble? If yes, how can we do it.
Or what is other way to do it.

Why you don't want to use Envelop Schema? Is there any specific reason for that?
Creating envelope schema won't be a tough task you just need to make Envelop property of Schema to Yes and set Body Xpath to the container record for the child records you wish to process individually.
Also you will have to create schema representing your child xml structure.
Refer
this article, it gives step by step description of the same.
Also, as John suggested you don't even have to create a custom pipeline as the debatching can be done using default XML Receive pipeline itself.
Let us know if you have any further question.
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

How to display the multiple rows in a single column ?

Hi,
I have the Query like this :
SELECT MS.SUBJECT, MS.MESSAGEDESC, MS.MSGDATE, MAT.ATTACHMENT
FROM MESSAGES MS, MSESAGEATTACHEMTASSO MAA, (select pga.programid,
act.accountname,
row_number() over(partition by pga.programid order by act.accountname) rn
from accounttypes act, programpursesasso pga
where act.accounttypeid = pga.accounttypeid ) MSGATTACHMENTS
WHERE MS.MESSAGEID = MAA.MESSAGEID
AND MAA.MSGATTACHMENTID = MAT.MSGATTACHMENTID
AND MS.MESSAGEID = 1;
If i have multiple messageAttachments for single message ., i want to display them in a single row.,
like :
subject messagedesc msgdate attachment1 attachment2 .....attachmentn
test test 10/10/2007 test test test
can any one help me out ., how can i do this using simple sql query ?

Hi,
Thanks for the Reply .,
I have the 2 table like :
DESC MESSAGES;
Name Type Nullable Default Comments
MESSAGEID NUMBER(16)
EMAILFROM VARCHAR2(50) Y
EMAILTO VARCHAR2(50) Y
SUBJECT VARCHAR2(500) Y
MESSAGEDESC VARCHAR2(2000) Y
MSGDATE DATE Y
MSGSTATUS NUMBER(1) Y
MSGDELETESTATUS NUMBER(1) Y
SQL> DESC MESSAGES;
Name Type Nullable Default Comments
MESSAGEID NUMBER(16)
EMAILFROM VARCHAR2(50) Y
EMAILTO VARCHAR2(50) Y
SUBJECT VARCHAR2(500) Y
MESSAGEDESC VARCHAR2(2000) Y
MSGDATE DATE Y
MSGSTATUS NUMBER(1) Y
MSGDELETESTATUS NUMBER(1) Y
SQL> DESC MSGATTACHMENTS;
Name Type Nullable Default Comments
MSGATTACHMENTID NUMBER(16)
ATTACHMENT CLOB
ATTACHMENTDATE DATE Y
SQL> DESC MSESAGEATTACHEMTASSO;
Name Type Nullable Default Comments
MSGATTCHID NUMBER(16)
MESSAGEID NUMBER(16) Y
MSGATTACHMENTID NUMBER(16) Y
What I need Is :
If One Msg is having multiple attachement , then i want to display all the attachment in a single row along with MsgSubject, MsgDate, MsgDesc like
I want to dipaly the MsgSubject, MsgDesc, MsgDate, Attachment1
MsgSubject MsgDate Msgdesc Attachment1 Attachment2 Attachment3 ...etc

Re: Multiple Data sources in single project

Hi Experts,
I am working in JDEV 11.1.1.3.0.
In my model project i have configured 2AM with 2 different data base connections, both are working fine. Now in the 2nd AM i am trying to execute VO and getting the value, but the query is not executing, if i execute the Same VO from data base then it's working fine.
Code:
AllTabColumnsROVORowImpl allTableColumnRow = null;
AllTabColumnsROVOImpl allTabColumnVO = getAllTabColumnsROVO();
Iterator tableItr = tableNameLst.iterator();
while (tableItr.hasNext())
String tableName = tableItr.next().toString();
allTabColumnVO.setBindTableName(tableName.trim());
allTabColumnVO.executeQuery();
System.out.println("query: " + allTabColumnVO.getQuery());
while (allTabColumnVO.hasNext())
allTableColumnRow =
(AllTabColumnsROVORowImpl) allTabColumnVO.next();
System.out.println("Column name: " +
allTableColumnRow.getColumnName());
columnMap.put(tableName + "_" + allTableColumnRow.getColumnName(),
allTableColumnRow.getDataType());
Bind variable i am getting from list, that's coming fine, but the while statement is not executing, method is ending after printing query.
Can any one help me what is wrong here.

You have to put the options -Djbo.jdbc.debug=true -Djbo.debugoutput=console in the 'javaOptions' field of your run configuration (in the view controller project).
Then you'll get the info.
Steve Muench filed a new blog entry https://smuenchadf.samplecode.oracle.com/samples/hroug2010_debugging_adf_applications_muench_final.pdf about debugging 'no data' issue.
Timo

Adobe captivate multiple quizzez within a single project

Hello I am trying to create a test that includes 6 different exams, but i want the usert to have to pass each exam with at least a 75% before they can access the next quiz. I am very new to captivate. Any help would be very appreciated.
Thank you

You will need 6 different Captivate projects, each of which will have one quiz (exam). You can set the passing percentage for each project file to 75% under Quiz Settings > Pass Fail. To force the user to pass each module of your course before they can do the next one, you really need to be serving up your course content via a Learning Management System. The LMS usually handles that side of it. If packaging your course modules as a multi-SCO SCORM course for your LMS, you'll ideally be using Adobe's Elearning Suite 6, which comes with the Multi-SCORM Packaging tool. The version that comes with ELS 6 can accommodate more of the SCORM rules than previously possible in earlier versions.

Multiple Agreement for Single Project

Hi All,
In our Implementation client generally gets multiple agreements for a single project. How to specify the Agreement Reference when we are creating an Event for billing? By the way have set up the funding option at the Project Level.
Thanks in Advance
Saptarshi

Hi
The problem you are raising has no solution by standard functionality.
Oracle promised to solve that for the first time in release 12.1 that should be available during 2009.
There could be customized solution which involve several parts:
Add a DFF on the event, so user can enter the agreement number.
Guide the user to run the GDI process for range of projects with the parameters - project number and agreement number
Develop a billing extension called on pre-processing of the GDI and another one called on the post processing step of the GDI.
The pre-process billing extension will put all project events that are not of the requested agreement on Hold, and any different agreement should also be "put aside in a non billable situation". The post process billing extension will release the hold from the events, and return the agreements to "normal".
I can admit such customization is ugly and risky. However, we have done it and it is working for us on production for several years. I have presented a paper regarding that on Collaborate 2007. You may look for the paper called: "Is it possible to invoice by contract using Projects Billing", on the OAUG web site.
Dina

Multiple Billings for Single Project

Hi Gurus,
Is there any possibility to do multiple billings for one contract / one project from Project Level.
How can we perform for Milestone / RRB? I appreciate with possible steps / process.
Regards
Naveen

Hi Naveen,
If i understood your query correctly, yes it is possible to do multiple billings for a single project, rather a single sales order.
As far as Milestone/RRB process is concerned, i would suggest you to go through SAP Help or search the forum. The query is very basic in nature and i am sure you will find the required answers in SAP Help.
You can revert with more specific queries once you are done with SAP Help.
Regards,
Gokul

Publishing multiple swfs from a single flash builder project

I have a flash builder 4.5 pure as3 project. Originally there was one document class and it was publishing a swf with the same name. Except for the standard flash builder bugs, that was working most of the time.
Now I need to add a preloader in to the mix.
So I made a Preloader.as class in my classpath and added that to my runnable applicaiton files in the projects menu. (I need this to be a seperate swf and not deffered loading on frame two)
Then I go to run/debug settings to set it up so that preloader can compile out a preloader.swf.
It doesn't work. It gives me a missing html file error.
Also, I want different comiler settings between the preloader and the main document class, yet only seem to have the option to add a single project wide compiler settings.
Can some one please explain to me the best practice for setting something like this up, or point me to documentation that covers this?

Hi,
You would need to make invisible buttons on the image.
For example, keep the image in layer 1.
Create a new layer say layer 2.
Now draw the button shapes, select them individually and press F8 to make buttons selecting Button option.
Once the shapes are converted into buttons, double-click on them to enter the edit mode.
Remove all the frames except the last frame which is known as the hit state.
Come back to stage view and you are ready to implement the scripts.
Warm Regards
Deepanjan Das
http://deepanjandas.wordpress.com

Combine the concat value in a single textfield.

hi there,
How to make the concat function, combining the multiple textfield into a single textfield
It doesnt work when i'm inserting the data in the last of textfield.It should appear when i have finished inserting the data.. should i put the onChange function to make it appear..
and what is the diferent between concat and bufferString...
below is my example program which is not function...
<input type="text" name="neg" size="35" value=''>
<input type="text" name="dae" size="35" value=''>
<input type="text" name="jdhm" size="35" value=''>
<input type="text" name="mbp" size="35" value=''>
<input type="text" name="notkt" size="35" value=''>
<input type="text" name="noptk" size="35" value=''>
<input type="text" name="nobgn" size="35" value=''>
<input type="text" name="nodhm" size="35" value=''>
<% String hak1="",hak2="",hak3="",hak4="",hak5="",hak6="",hak7="",
tempNOPTK=request.getParameter("NOPTK"),
tempNOTKT=request.getParameter("NOTKT"),
tempNOBGN=request.getParameter("NOBGN"),
tempNODHM=request.getParameter("NODHM"),
tempJHM=request.getParameter("jdhm"),
tempMBP=request.getParameter("mbp"),
tempDAE=request.getParameter("dae"),
tempNEG=request.getParameter("neg");
if (tempNEG !=null && tempJHM !=null && tempMBP !=null && tempDAE !=null && tempNODHM !=null && tempNOBGN !=null && tempNOTKT !=null && tempNOPTK !=null)
hak1=tempNEG.concat(tempDAE);
hak2=hak1.concat(tempMBP);
hak3=hak2.concat(tempJHM);
hak4=hak3.concat(tempNODHM);
hak5=hak4.concat(tempNOBGN);
hak6=hak5.concat(tempNOTKT);
hak7=hak6.concat(tempNOPTK);
System.out.println(hak7);}
%>
<input type="text" name="id hakmilik" size="35" value='<%=hak7%>'>
i want the id hakmilik textfield to appear the result..

if (tempNEG !=null && tempJHM !=null && tempMBP !=null
&& tempDAE !=null && tempNODHM !=null && tempNOBGN
!=null && tempNOTKT !=null && tempNOPTK !=null)
{What happens if one of them is a null? That is why you are getting '""' displayed in the 'id hakmilik' field.
One more point, try to avoid spaces in field names.(id hakmilik).
Sudha

Import/export issue to migrate the project

Hi,
I am trying to migrate a project from 1 server to another server.
I exported the project and model from my current server, and imported them to the new server. the thing is, the senario can be run successfully, but when I open the interface in designer, the source table cannot get any definition, all the columns in the source table won't show up. it looks like to me is that the interface lost the connection of the data store in the model.
Anybody has any idea how to fix it?
Thx

Hi
If its a fresh imploementation then its fine.
Say yu migrated the ODI objects to prod and you face an issue.
you have fixed it in development and want to move it to prod.
How do you handle this scenario.
Please let us know the process that you are following

Impact of migrating to a new database on the existing code

There is a java application that connects to postgreSQL as the database server. postgreSQL is installed under LINUX. I am planning to migrate the existing postgreSQL database to a SQL Server 2000 database under windows. In case of such an action will the application code need to be changed? If yes will it be a major change? Pls advise.

I left my crystal ball at home today; plus, I've never seen the code for the application in question,so it's kind of hard for me to say. Maybe this is a bit of a stretch, but isn't that what you, as a developer, should be determining? Based on the question(s) in your original post, do you truly believe someone is going to respond with a concrete answer? Do you think everyone but you knows if the application will need to be changed; and, if so, how big of a deal it will be? Come on, give me a break.
As for a few pointers that might help you come up with some answers:
- Is the SQL SQL-99 compliant (i.e. least common denominator kind of stuff) or is it postgreSQL-specific?
- Is the SQL fairly well contained within the code; or better yet in a separate file (.properties or XML)?
- Are you using any kind of persistence layer?
Jamie

Use two VIs with the same name, different functionality on a single Project

Hi, I'm working with vision builder al labview, I need to integrate the vision builder migration Vis into my main program, (Is not an option), but I have multiple Vis autogenerated with the same name, how can i integrate them in the same project without dependency problems
Thanks in advance

Hi,
Unless you really need tight integration between the Vision code and the rest of your LabVIEW application, or would rather not have to pay for a Vision Builder AI runtime license on the targets on which you want to deploy your final application, I would recommend you look into using the Vision Builder AI LabVIEW API instead of migrating the inspection to LabVIEW.
The API allows to control Vision Builder AI by launching a Vision Builder AI engine, running the inspection and retrieving resulting images and results.
The advantage of the API is that it allows for easier modification and debugging of the Vision Inspection that you designed in Vision Builder, if you need to make changes later. (i.e. all you need to do is open the inspection in Vision Builder AI, modify parameters, add steps etc).
You won't have to change your LabVIEW application, unless you want to output additional results.
When you build and deploy your application, you will need to install Vision Builder AI on the target machine and get a runtime license for it.
Migrating the inspection to LabVIEW is a one way deal. If you need to make changes to the inspection, you will have to migrate the inspection again, or modify the code outside of the Vision Builder AI environment.
As you might have noticed, the code generated is quite complex, and it is recommended to go this route only if you need really tight integration/synchronization between the vision code and the rest or your LabVIEW code, or if you would rather pay for a cheaper Vision runtime license rather than a VBAI runtime license for the deployment machine (in case of deploying multiple systems where cost is a big consideration).
Vision Builder AI API examples are located in this folder:
C:\Program Files (x86)\National Instruments\Vision Builder AI\API Examples\LabVIEW Examples
Hope this helps clarify the use cases and help you make the right decision for your design.
Best regards,
Christophe

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

Impact of Migrating the Multiple maintenan Project to Single project

Similar Messages

Maybe you are looking for