How to migrate win_api_shell functions

Hello,
I am migrating a C/S Forms 6i application to webforms 10g. Most of the old d2kwutil.pll functionality is ported/replaced by webutil 1.0.5. But it seems that there is no ported version of the old win_api_shell functionality. As far as I can see only some of the old functionality is ported to client_win_api, but not all.
What I like to know is which webutil call do I use instead of win_api_shell. Please help.
Kind regards,
Harm

What function are you actually trying to migrate. Most of the fuctions in _shell cannot be migrated to the Java client because they use a Window handle, which for various reasons we can't use from Java.

Similar Messages

How to migrate ADE content to a new computer

At some point, everybody needs to upgrade to a new computer.
After reading a great many postings in this forum, it seems obvious to me that many of us would greatly benefit from some specific guidance on how to install Adobe Digital Editions and Sony Reader Library Software (and reader device) or some other e-book application on the new computer, and then move the previously purchased e-book content from the old to new computer in a way that will ensure that the e-books can still be read.
Specifically, I think that some/better guidance needs to be provided on the sequence of steps that must be taken, and the options that should (or should not) be selected to accomplish these actions. For example, does ADE software get installed on the new PC first, or after installing the Sony reader library (or other reader) software? Should we authorize the new computer? How about the portable reader devices (Sony P600), do we leave the content on these or will we need to reload it? Is there a way to ensure the Adobe ID for both SW applications (ADE & Sony Library) are the same so we don't get new or different ID assigned? Will a reader device (which may already contain ebook content) be recognized and automatically resynch with the new computer? and can it move its content from reader to PC, or must the purchased content first be loaded onto the new PC from the old PC, and then be moved (again) to the reader device?
I can't help but think that answers to these (and many other) questions could be far more easily communicated by proactively publishing some basic (if general) procedures for accomplishing common actions like these, rather than repeatedly providing help to each of us after we have already done the wrong thing. While technical help is always greatly appreciated, and it may be easier to address a specific problem, it is more effective to provide information that will help us avoid the problem in the first place, and thus reduce the case load and improve response time.
If I were sufficiently knowledgable to be capable of providing this general guidance myself, I would certainly do so, but count me among the ignorant masses that are simply trying to buy, download, and read their e-books without rendering all their purchased content inaccesible. I certainly wouldn't want to inadvertently provide misinformation that might cause even greater problems.
In short, I think that all of us (forum readers) would greatly like to have some simple instructions presented on what to do, (or not to do), to initially set up our computers and to accomplish other basic functions once this has been done.
Won't somebody with the needed expertise undertake to provide some instructions in this forum?
Thanks (in advance) for you support.
P.S. - Keeping purchased content on original (old) and new computers is NOT an option.

How to migrate ADE from one computer to another:
1.) Ensure that your current content is authorized to an AdobeID
In ADE select "Authorize Computer" from the "Library" menu if it shows you your AdobeID you are good to go.
2.) Copy files - the files are the .epub and .pdf files in your Digital Editions folder in your Documents directory. Alternatively you can simply copy the whole Digital Editions folder. If you copy the whole folder make sure you place it into your Documents directory.
Note: on Windows the folder names are "My Digital Editions" and "My Documents"
3.) Install ADE on the new computer, make sure you enter in the AdobeID from step 1 and the password when asked
The AdobeID that registred and shown (in step1) above is the same for ADE as it is for Sony EBL (the Sony desktop software) - they both pull from the same place.
Unfortunately I don't know the steps for migrating Sony EBL.
For the content on the reader device, you can leave them alone.

How to convert 6i function keys file to 10g

Hi,
is there any way how to migrate 6i Forms binary resource file with function keys to 10g Forms text-based resource file with function keys (e.g. fmrcsw.res -> fmrweb.res)?
Thx.

this is a manual way of migration you have to do, as I know. Extracting from Oracle Terminal and importing in fmrweb.res is not supported

How to migrate 'responsibility' level personalizations?

Hi all,
We have done a set of personalizations at responsibility level in our UAT instance.
We have no problem migrating the 'site' level personalization. We use the 'Functional Administrator' -> Import/Export utility.
But, We find that the responsibility level personalizations are stored under a folder hierarchy as below:
Eg:
Responsibility: XXRecruitment Manager
Responsibilty Key: XXRECRUIT_MAN
Responsibility ID: 50977
Personalization is exported in this folder:
/oracle/apps/per/irc/vacancy/webui/customizations/responsibility/50977/RectrDetsRN
It is stored under a folder '50977' corresponding to the responsibility id of the responsibility that we personalized.
Our problem is, the responsibility id's and responsibility key's are different in UAT and production instances:
Responsibility: XXRecruitment Manager 01
Responsibilty Key: XXRECRUIT_MAN_01
Responsibility ID: 50900
Now, how to migrate such personaliations? Our client have personalized atleast 25 pages at various responsibilty levels. Please suggest a suitable way to migrate these personalizations.
thanks in advance,
Hem

Hem,
We had the similar discussion in past once, but I guess the user didn't update the final results. As far as I think, 'Functional Administrator' -> Import/Export utility should be handling this scenario.
Did you try it atleast on one such responsibility level personalization?
--Shiv

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 migrate BPM 11g server to another BPM 11g server

Hi All,
There is no change on BPM version (BPMN Editor 11.1.1.3.0.6.84 )
just simply a physical migrate, changed application server, DB and server domain/IP
Now we met questions when migrate DB date, there are four schemas DEV_MDS、DEV_SOAINFRA、DEV_ORABAM、DEV_ORASDPM, cannot used including install config settings, could not be used any more, could not be started.
Is there any guide of how to migrate just user data please?
Thanks for any help!
Regards,
Katherine

Migration of environment should really be done through backup tools that ensure a consistent point-in-time view of the data. We recently had a need to use import/export for an environment. I'll post those notes here hopefully save some time if you have to use this approach. But I'll emphasize again that a backup/restore model is the better way to go.
What we did
We took an environment that had a small set of BPM processes and exported the data from the three core schemas.
•     PS2_MDS
•     PS2_SOAINFRA
•     PS2_ORASDPM
We then loaded that data into another domain, started the server, and interacted with the composites that had originally been deployed in another domain.
What we didn’t do
•     Export complex composites. We didn’t have access to things like AIA applications
•     Export large amounts of data
•     Test a broad set of features. We did use Workspace to create roles, view dashboard, and interact with task lists.
What we learned
We believe this confirmed the basic assumption that data can be exported from one BPM/SOA environment, then loaded and run in another environment. However the issues around user privileges, starting queues, etc, highlight the need to test the process in a broader context.
Tools Used
Data Pump
Data Pump is an import/export tool provided by Oracle. A summary of features can be found at:
http://wiki.oracle.com/page/Data+Pump+Export+%28expdp%29+and+Data+Pump+Import%28impdp%29
SQL*Plus
Used to run scripts
Setup
Create Users
The data pump export will include privilege information in the export. And the data pump import will create users in the target database (assuming sufficient privileges for the user running the import). However we found that some roles related to AQ were not granted during the import. To resolve that issue we created scripts to pre-create the schema users and grant required privileges in the target environment.
TODO:
1.     Review the required privileges to see if there are data pump options that would resolve this
2.     Verify that there are no additional privileges needed by applications in the target integration environment.
Create Output Directory
Data Pump needs to have access to the file system from the database.
Make sure that the output directory is writable by the DB process.
From SQL*Plus:
create directory dbexport as '/scratch/ dbexport';
grant read,write on directory dbexport to system;
Export Data For Selected Schemas
The Data Pump tool supports providing a list of schemas to export as part of a single operation. In this test case we exported the following core BPM schemas to a single file. The commands are in the do_exp.sh script.
•     PS2_MDS
•     PS2_SOAINFRA
•     PS2_ORASDPM
TODO:
1.     Verify space required for the target database to ensure that there is sufficient space to export the data.
Import Data into Target Schemas
Data Pump supports mapping schema names and table spaces as part of the import specification. In this case we used the same Oracle instance, so the schemas were mapped to new names. The PS2 prefix was mapped to XYZ.
Note that the OID transform property is required to avoid conflicts with existing object Identifiers.
impdp system/welcome1 DIRECTORY=dbexport DUMPFILE=bpm.dmp transform=oid:n \
REMAP_TABLESPACE=PS2_MDS:XYZ_MDS \
REMAP_TABLESPACE=PS2_SOAINFRA:XYZ_SOAINFRA \
REMAP_TABLESPACE=PS2_IAS_ORASDPM:XYZ_IAS_ORASDPM \
REMAP_SCHEMA=PS2_MDS:XYZ_MDS \
REMAP_SCHEMA=PS2_SOAINFRA:XYZ_SOAINFRA \
REMAP_SCHEMA=PS2_ORASDPM:XYZ_ORASDPM \
TODO:
1.     Check the log for errors. The only errors we saw were related to trying to build stats on empty indexes.
2.     Identify any other schemas being used
3.     Verify if any other transform operators are needed
Post Import
Start Queues
SOA infrastructure makes use of queues in the DB server. While the queue structures were created, they were not started as part of the import. The start_queues.sql script starts the queues.
TODO:
1.     Verify if there are any other queues that need to be started/configured
2.     Verify if there are any other Stream/Queuing configuration tasks needed
Update Data Sources on WLS
Assuming an existing installation of SOA, the datasources need to be updated to use the new schemas.
Start Domain and Verify Logs
It’s important to check the admin and managed server logs for errors related to composite instances and MDS operations.
Verify Composite State
Log into EM and ensure that the state of instances is consistent with the prior state.
Verify Application Roles and Role Mappings
Since the composites are loaded from MDS, there will be no deployment to create application roles. If the environment is using LDAP or DB, then the validation is to check the mappings through Workspace. If the old environment used a file store, then you’d have to crate the role mappings through Workspace.
Verify Workspace Operations on Existing Instances
Verify that task list operations and dashboards are functional.

How to migrate WindowsAPI GetDiskFreeSpace to Solaris

I don't know how to migrate windowsApi GetDiskFreeSpace to Solaris. Is there one SolarisAPI which can implement the function of getdiskfreespace ?
If there is , please tell me the name of the corresponding
SolarisAPI. If there isn't, please tell me tell how to migrate the WindowsAPI . thanks a lot!
The WindowsAPI GetDiskFreeSpace is descripted as following :
GetDiskFreeSpace
The GetDiskFreeSpace function retrieves information about the specified disk, including the amount of free space on the disk.
This function has been superseded by the GetDiskFreeSpaceEx function. New Win32-based applications should use GetDiskFreeSpaceEx.
BOOL GetDiskFreeSpace(
LPCTSTR lpRootPathName, // pointer to root path
LPDWORD lpSectorsPerCluster, // pointer to sectors per cluster
LPDWORD lpBytesPerSector, // pointer to bytes per sector
LPDWORD lpNumberOfFreeClusters, // pointer to number of free clusters
LPDWORD lpTotalNumberOfClusters // pointer to total number of clusters

I am sorry to say that the WindowsAPI is not there !
In fact, I only want to know how to get the free disk space in Solarisb. I have found the two SolarisAPI
stafvfs, fstatvfs. But i am not sure whether the two APIs can get the free disk space . Could anyone tell me ?
Or tell me where can i find the Solaris file system format ? thanks a lot !

CRS Migration: Repository functions Only

Hello,
by the migration of a CR Server XI to CR2008 the Repository functions failed by the migration.
Is there any possibility to migrate only Functions without the other repository elements. Or is it possible to manipulate the BIAR File in order to select only Repository functions by the import and how ..?
Thanx

There is plenty of tablespace space left.
I was able to do the migration by installing the migration repository in a 10.2.05 database and then migrating the access database into this same 11.1.0.7 database. Just couldn't get the repository created in this db.
Using SQLDeveloper 3.0.04 Build Main 04.34
NLS_Characterset = US7ASCII
NAME VERSION DETECTED_USAGES
Automatic Maintenance - Optimizer Statistics Gathering 11.1.0.7.0 16
Automatic Maintenance - SQL Tuning Advisor 11.1.0.7.0 16
Automatic Maintenance - Space Advisor 11.1.0.7.0 16
Automatic SGA Tuning 11.1.0.7.0 16
Automatic SQL Execution Memory 11.1.0.7.0 16
Automatic SQL Tuning Advisor 11.1.0.7.0 16
Automatic Segment Advisor 11.1.0.7.0 6
Automatic Segment Space Management (system) 11.1.0.7.0 16
Automatic Segment Space Management (user) 11.1.0.7.0 2
Automatic Storage Management 11.1.0.7.0 16
Automatic Undo Management 11.1.0.7.0 16
Character Set 11.1.0.7.0 16
LOB 11.1.0.7.0 16
Locally Managed Tablespaces (system) 11.1.0.7.0 16
Locally Managed Tablespaces (user) 11.1.0.7.0 16
Logfile Multiplexing 11.1.0.7.0 16
Materialized Views (User) 11.1.0.7.0 16
Oracle Utility Metadata API 11.1.0.7.0 16
Parallel SQL Query Execution 11.1.0.7.0 16
Partitioning (system) 11.1.0.7.0 16
RMAN - Disk Backup 11.1.0.7.0 15
Real Application Clusters (RAC) 11.1.0.7.0 16
Recovery Area 11.1.0.7.0 16
Recovery Manager (RMAN) 11.1.0.7.0 15
Resource Manager 11.1.0.7.0 15
Segment Advisor 11.1.0.7.0 6
Server Parameter File 11.1.0.7.0 16
Services 11.1.0.7.0 16
Edited by: 875118 on Jul 26, 2011 2:40 PM

How to migrate rtf Templates in XML Publisher ?

Hi All,
I want the script so that i can download and upload the RTF files directly from my development instance to my production instance.
For this i have come across 3 links
How to migrate rtf Templates in XML Publisher?
http://download.oracle.com/docs/cd/B40089_10/current/acrobat/120xdoig.pdf
unable to migrate physical files using XDO Loader utility
and from here i am running this command from /home/aryan directory
java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD -DB_USERNAME apps -DB_PASSWORD fnd -JDBC_CONNECTION sharp.apps.com:1522:tst1 -LOB_TYPE TEMPLATE -APPS_SHORT_NAME CUSTOM -LOB_CODE ZEMP -LANGUAGE en -TERRITORY US
but it is giving me error "ksh: java: not found". could anyone can tell me how and from where i have to run the download and upload command
Thanks
Aryan

Hi Hussein,
I tried with applmgr also and still for java -version it is giving me error ksh Java not found
and for which java it is giving me error no java found in different directories path.
Thanks
Aryan

How to keep multiple function modules under one Web service

Hi Experts,
I have Three RFC function modules and i need to create one web service for these three RFC function modules. I know How to crearte a web service for one function module.
please suggest me How to keep multiple function modules under one Web service.
Thanks in advance
Lakshminarayana

Hi Lakshmi,
The best way to do it is to assign all the three RFC Enabled FM's to one function group. Later on the top menu in Utilities you get an option to Create a Webservice from a Function Group.
You can create one single Webservice using all the the 3 FM's.
I hope this helps.
Thanks,
Manu

OIM11gR2 - How to migrate an Application Instance Form

Hello,
I'm trying to migrate an Application Instance Form from my Dev env to my QA env.
My target system is SAP
I performed the following steps in Dev:
1. Installed and configured the SAP Connector (no problem here)
2. Created a sandbox
3. Created an Application Instance
4. Created the Application Instance Form
5. Ran a target reconciliation to confirm everything is working properly
6. Exported the sandbox
7. Published the sandbox
8. Via Deployment Manager I exported all objects related to SAP (Resource object, Process Forms, Lookups etc.)
In QA I did:
9. Installed and configured the SAP Connector (no problem here)
10. Via Deployment Manager I imported the objects related to SAP
11. Imported the sandbox
Problem:
To my surprise, the Application Instance does not have a Form in the QA env.
I had to create it manually by performing the following:
12. Create a sandbox
13. Open the Application Instance definition
14. Click on create (to create a form)
15. Entered the same name I used in my Dev environment
16. Received an error message saying that the form already exists
17. Entered a different name for the Form
18. Saved
19. Exported the sandbox (to import in Prd)
20. Published the sandbox
21. Ran a target reconciliation to confirm everything is working properly
I tried to reproduce the problem with another (test) destination environment because I don't want to have the same problem when migrating to Prd.
I repeated the steps 9,10,11 except that I imported the sandbox exported from QA (step 19) instead.
The same problem: Application Instance definition has no Form attached to it in my test destination environment.
If I try to create the form with the same name, it gives an error message saying it is already there.
Is my procedure wrong?
Is there an official procedure explaining how to migrate only Application Instance Form from one env to another?
My env:
OS: Windows 2008 R2 SP1
OIM: 11gR2 BP7
SAP connector: 9.1.2.2.0
Thanks,
Adr

This is a bug: Bug:16027176
Check the [Article ID 1515225.1] which proposes a workaround that might be useful in your case (it was not in mine).
In short the workaround is:
The following order should be observed to export :
- IT Resource & Application instance in one xml
- Request DataSet in another xml
- SysAdmin Sandbox (the one defined while creating the Application Instance and the Form)
- Identity URL Sandbox (defined while customizing the fields on the Form, in the Catalogue page)
Adr

How to use read_text function module

Hi how to use read_text function module to read purchase order header text .what are all tht things to pass in ID,Name and Object
thanks,
Mahe

Dear,
Use below code.
DATA:IT_LINE LIKE TLINE OCCURS 0 WITH HEADER LINE,
V_TDNAME LIKE THEAD-TDNAME.
V_TDNAME = PO_NUMBER.
CALL FUNCTION 'READ_TEXT'
EXPORTING
*   CLIENT                        = SY-MANDT
    ID                            = 'F01'
    LANGUAGE                      = 'EN'
    NAME                          = V_TDNAME
    OBJECT                        = 'EKKO'
TABLES
    LINES                         = IT_LINE.
Thanks and Regards,

How to Create a Functiona Query

Dear all,
Could any body detail me how to create a functional query. Please give me step by step procedure to create a query.
I would appreciate if you can give me a material with screen shots. Your help will be highly appreciated.
Thank you
Raghu Ram

Hi Raghu,
Go through this document it may help you,
SAP Query
Step 1: Create User Group SQ03
Follow the menu path SAP Menu > Tools > ABAP Workbench > Utilities > SAP Query > User Groups
a) In the User Group: Initial Screen -
Enter User Group Code (self named)
Click on Create
b) In the User Group (Code): Create or Change pop-up window -
Enter the User Group Description
Click on Save
c) In the Create Object Directory Entry pop-up window -
Ö Click on Local Object button
Ö The User Group Created is saved
Step 2: Create User Group SQ02
Follow the menu path SAP Menu > Tools > ABAP Workbench > Utilities > SAP Query > Infosets
a) In the Infoset: Initial screen -
Ö Enter Infoset Code (self named)
Ö Click on Create button
b) In the Infoset: Title & Database Screen -
Ö Enter Description of Infoset in the Name field
Ö In the Data Source selection: Select appropriate Data Source by clicking
the radio button
· Source the data can either be multiple tables OR single table. There are 4
options for the user to select from
Ö Click on Continue (Enter)
Ö Selected Table gets displayed in the Infoset : Initial Screen
c) In the Infoset: Initial Screen -
Ö Click on Insert Table button
d) In the Add Table Screen -
Ö Enter the Table Name that is to be inserted
Ö Click Continue (Enter)
e) In the Infoset: Initial Screen -
Ö Click on Back button
f) In the Field Group Defaults pop-up Screen -
Ö Select Appropriate Field Group Option by clicking on the radio button
· there are 3 options to select from. User can select Empty Field Group
option and then select the data fields in the steps explained further.
Alternatively, User can select an option which clubs all the data fields
From all the tables selected
Ö Click Continue (Enter)
g) In the Change Infoset Screen -
· the left side lists the Tables that the user has selected in step b, c & d
· In the right side, system creates field groups, one for each table listed in the
left part. Initially, the Field Groups are empty
Ö In the Left Side, Click on the arror next to the table name and expand and
display all the data fields in the table
Ö Select a Data Field from the expanded Table view, which is to be added to
the Field Group on the right.
Ö Select a Field Group on the right side, in which Data Field selected above
has to be added
Ö Right click on the Data Field selected and click on Add Field to Field Group
Ö The selected Data Field gets added to the selected Field Group, which is
indicated by an arrow next to the Field Group.
Ö Carry out the steps above to add the required Data Fields to the respective
Field Groups
Ö After transferring Data Fields to Field Groups click on Generate button
h) In the Create Object Directory Entry Screen -
Ö Click on Logical Object button to generate the infoset
i) In the Change Infoset Screen -
Ö Click on the Back button
j) User is taken back to the Infoset: Initial Screen which displays the
created Infoset record.
Step 3: Assigning User Group to Infoset SQ03
Follow the menu path SAP Menu > Tools > ABAP Workbench > Utilities > SAP Query > User Groups
a) In the User Groups: Initial screen -
Ö Enter the User Group for which Infoset is to be assigned
Ö Click on Assign Users & Infosets button
b) In the User Group: Assign Users Screen -
Ö Click on Assign Infosets button
c) In the next screen, select the Infoset, which needs to be attached to the
User Group selected
d) Click on the Back button
Step 4: Creating Query SQ00 & SQ01
Follow the menu path SAP Menu > Tools > ABAP Workbench > Utilities > SAP Query > Queries
a) In the Query from User Group: Initial Screen -
Ö Click on Other User Groups button
Ö In the pop-up screen, User Groups, select the User Group for which the
Query has to created. The pop-up screen closes.
Ö Enter the Query Code in the Query field
Ö Click on Create button
b) A pop-up screen Restrict Value Range shows the list of Infosets assigned to
the User Group
Ö Select the Infoset for which Query has to be created
c) In the new screen Create Query: Title, Format -
Ö Enter the Description of the Query in the Title field
Ö Click on the Next Screen button
d) In the Select Field Group screen
Ö Select the Field Groups from which Data Fields have to be selected for the
Output
Ö Click on the Next Screen button
e) In the Select Field screen -
Ö Select the Data Fields, which should appear in the output
Ö Click on the Next Screen button
f) In the Screen Selection -
Ö Select the Data Fields for the selection criteria
Ö Enter the sequence in which the selected fields would appear in the input
screen of the query.
Ö Define if the selection criteria should be Single Value or Multiple Value Range
by clicking in the appropriate check boxes
Ö Click on the Basic List button
g) In the screen Query Layout Design -
Ö Select the Output Fields from the Data Fields section by clicking the
appropriate check box
Ö Change the sequence of Data Field columns if required
Ö Click on the Test button to test the query created
h) On the Test Query screen click Continue
i) In the Query screen -
Ö Enter the selection criteria
Ö Click on Execute button
j) Save the Query created
Step 5: Running the Query SQ00
a) In the Query From User Group: Initial screen
b) Click on Other User Groups button to select the User Group
c) In the pop-up screen User Groups select the User Group
d) System lists all the queries created for the User Group
e) Select the appropriate Query
f) Click on Execute button
g) User is taken to the Selection screen
h) Enter the selection criteria and click on Execute button
i) System runs the query and gives the output
Regards,
Murali.

How to write Boolean function (If Then Else)?

Hi all,
I have a logic to write in the query. It is:
If (A = 0 and B = 0)
Then 0
Else
        If (A = 0 and B > 0)
        Then 100
        Else
               A/B (we want to show %)
How to use boolean function to write this Netted If Else statement? Thank you in advance!

Hi
If (A = 0 and B = 0)
Then 0
Else
If (A = 0 and B > 0)
Then 100
Else
A/B (we want to show %)
1. create a formula in the query designer. and use this formula for if - else
( ( (A==0) AND (B==0) ) * 0) + ( ( a==0 ) AND (B >0 ) * 100 + (A/B*100) )
: denotes THEN
+ : denotes ELSE
See if this works.
Assign points if helpfull
From
ManesH

How to migrate mails from Google Apps to MS Exchange Online IMAP (Getting error)

Any tips on How to migrate mails from Google Apps to MSOL? What is required? When I am trying to migrate using IMAP but getting fpollowing error
=======================
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:11
[email protected]
Failed
Error:
Failed to log on successfully for the following reason:
Server rejected Basic login with following message : * CAPABILITY IMAP4rev1 UNSELECT LITERAL+ IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE.
Exchange Management Shell command attempted:
'Microsoft.Exchange.Transporter.Provider.PopImap.InternetMailboxMeta' | Move-XsIMAPMailboxToExchangeOnline -AllowUnsecureConnection $false -TargetCredential 'System.Management.Automation.PSCredential' -MaxThreadCount '10' -Quiet
Elapsed Time: 00:00:11
======================
Any help will be much appreciated.
Regards
Sunil DK

I just finished migrating a client from Google Apps to Microsoft Exchange Online using the IMAP option in the Microsoft Online Services Migration Tool.
I added the mailboxes by creating a CSV file [i.e. GoogleApps(Gmail)_Mailboxes.csv] in the following format:
SourceIdentity,SourceServer,SourceLoginID,SourcePassword,TargetIdentity
[email protected],imap.gmail.com,[email protected],P@ssword1,[email protected]
[email protected],imap.gmail.com,[email protected],P@ssword2,[email protected]
[email protected],imap.gmail.com,[email protected],P@ssword3,[email protected]
Then I created a custom folder map XML file [i.e. GoogleApps(Gmail)_FolderMap.xml] to map the Google Apps (Gmail) labels to the appropriate Exchange (Outlook) mailbox folders and create those that didn't exist (i.e. Important, Starred, Follow up,
Misc, Priority) as sub-folders under the Inbox:
<?xml version="1.0" encoding="utf-8"?>
<FolderMappings xmlns="http://tempuri.org/FolderMap.xsd">



<Folder path = "INBOX">
<Property SpecialFolder = "Inbox"/>
</Folder>
<Folder path = "New Mail">
<Property SpecialFolder = "Inbox"/>
</Folder>
<Folder path = "[Root]">
<Property SpecialFolder = "Inbox"/>
</Folder>
<Folder path = "">
<Property SpecialFolder = "Inbox"/>
</Folder>
<Folder path = "Calendar">
<Property SpecialFolder = "Calendar"/>
</Folder>
<Folder path = "Tasks">
<Property Name = "Migration items/Tasks"/>
</Folder>
<Folder path = "Sent Items">
<Property SpecialFolder = "Sent Items"/>
</Folder>
<Folder path = "Sent Mail">
<Property SpecialFolder = "Sent Items"/>
</Folder>
<Folder path = "Sent">
<Property SpecialFolder = "Sent Items"/>
</Folder>
<Folder path = "Deleted Items">
<Property SpecialFolder = "Deleted Items"/>
</Folder>
<Folder path = "Trash">
<Property SpecialFolder = "Deleted Items"/>
</Folder>
<Folder path = "Drafts">
<Property SpecialFolder = "Drafts"/>
</Folder>
<Folder path = "Draft">
<Property SpecialFolder = "Drafts"/>
</Folder>
<Folder path = "Junk E-mail">
<Property SpecialFolder = "Junk E-mail"/>
</Folder>
<Folder path = "Spam">
<Property SpecialFolder = "Junk E-mail"/>
</Folder>
<Folder path = "Contacts">
<Property Name = "Migration Items/Contacts"/>
</Folder>
<Folder path = "Outbox">
<Property SpecialFolder = "Outbox"/>
</Folder>
<Folder path = "Journal">
<Property SpecialFolder = "Journal"/>
</Folder>
<Folder path = "Notes">
<Property SpecialFolder = "Notes"/>
</Folder>
<Folder path = "Public Folders">
<Property ExcludeFolder = "true"/>
</Folder>

<Folder path = "[Gmail]/All Mail">
<Property ExcludeFolder = "true"/>
</Folder>
<Folder path = "All Mail">
<Property ExcludeFolder = "true"/>
</Folder>
<Folder path = "[Gmail]/Drafts">
<Property SpecialFolder = "Drafts"/>
</Folder>
<Folder path = "[Gmail]/Important">
<Property Name = "Inbox/Important"/>
</Folder>
<Folder path = "[Gmail]/Sent Mail">
<Property SpecialFolder = "Sent Items"/>
</Folder>
<Folder path = "[Gmail]/Spam">
<Property SpecialFolder = "Junk E-mail"/>
</Folder>
<Folder path = "[Gmail]/Starred">
<Property Name = "Inbox/Starred"/>
</Folder>
<Folder path = "[Gmail]/Trash">
<Property SpecialFolder = "Deleted Items"/>
</Folder>

<Folder path = "Follow up">
<Property Name = "Inbox/Follow up"/>
</Folder>
<Folder path = "Misc">
<Property Name = "Inbox/Misc"/>
</Folder>
<Folder path = "Priority">
<Property Name = "Inbox/Priority"/>
</Folder>
</FolderMappings>
Additionally, I had to tell the Internet E-mail Mailbox Migration Wizard to use the "Individual Account Credentials" option since I was able to specify each account password in the CSV file when adding the mailboxes to Microsoft Online Services Migration
Tools console.
Just to note, the users had to manually export their contacts to a CSV file and calendars to iCal (ICS) files in order to import those items into Outlook.
I hope this will benefit others since Microsoft doesn't seem to have a custom, specifically defined migration strategy for this scenario. With Google Apps being in direct competition with BPOS/Office365, I assumed that Microsoft would have a simple
strategy using something like ActiveSync to facilitate the migration of email, contacts, calendar entries, etc. Hopefully we'll see something along those lines become available in a future release of the migration tools.
--Jon Payne

How to migrate win_api_shell functions

Similar Messages

Maybe you are looking for