How to transport the object in XI?

Hi friends,
Anybody can give me the idea or any document for transporting the objects in XI from Development system to Quality system.As per my knowledge we can transport using File and CMS, but i don't have clear idea. Anybody explain me clearly or provide me any document?

Hi,
There are two ways to Transport XI objects-
1) File Import/Export
2) CMS
CMS is somewhat standard way to do. Becuase you can track the objects. But for this you need to install the CMS separately.
just go thru these quick links-
http://help.sap.com/saphelp_nw04/helpdata/en/e1/69a740aa053a13e10000000a155106/frameset.htm
/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
Also check in service.sap.com- for how to guides-
https://websmp201.sap-ag.de/nw-howtoguides
Refer
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi - Transport in XI
Configuration of CMS in Central NWDI & SLD to transport XI objects
/people/praveen.mayalur/blog/2007/05/31/configuration-of-cms-in-central-nwdi-sld-to-transport-xi-objects
CMS Trnasport
How to Use CMS in XI 3.0.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff72d822b109
CMS based transport in XI
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
Change and Transport Lists for CMS Transports
How ToTransport XI Content Using CMS
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db6306
File Transport
Configuring Groups and Transport Targets.
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
also have a look at:
Transporting XI Objects
http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/content.htm
Thanks
Swarup

Similar Messages

OBJECT SKIPPED while transporting the objects from DEV to QA.

Hi All,
While transporting the objects to Quality, I'm getting a warning saying Objects are skipped.
Can anyone please explain how to get rid of this error? We are facing this issue almost for all the transports which we are moving and the objects do not get transported to the next environment. We have to ask BASIS to use overwrite functionality while transporting to fix this each and every time we face an error.
If any SAP notes are available then please share it to me.
Thanks in Advance.

Hi Srikanth,
Objects of the selected object types exist in your system as changeable even if this system is globally set to not changeable. As a result, these objects are no longer connected to the transport system.
check here........
http://help.sap.com/saphelp_nw04/helpdata/en/0e/a7343e8c7f6329e10000000a114084/content.htm
for this try contact basis team.
Thanks,
Vijay.

How to transport the data contains in the table from development to product

How to transport the data contains in the table from development to production.
Please let me know ASAP.

Hello Dilip
Create a workbench request and add the following entries to the request:
Object key: R3TR TABU <name of z-table>
For this object add the following value key:
- client-independent table: '*'
- client-dependent table (e.g. client 100): '100*'
See also: [SAP Network Blog: Transport Table Entries|/people/community.user/blog/2007/01/07/transport-table-entries]
Regards
Uwe

How to transport the text elements in Reports?

need answer to this question.
how to transport the text elements in the reports?
Edited by: venkata kumar on Feb 18, 2008 1:33 PM

Hi Venkata,
Text Elements are a component/part of the SAP script and are not individual ABAP objects within the SAP environment hence they cannot be transported independently.
You would need to make changes in your text elements in the SAP script which would result in the SAP script being saved under a transport and moving the transport across the landscape would result in the text elements also getting transported.
In short: Move SAP script - to move text elements.
Cheers,
Aditya

How To transport the Routines with UR

i HAVE THE ur WHICH I SELECTED from Object types in Transport connection now how to transport the routines
please tell what to select
soniya

Hi Soniya,
If you have collected the UR, the routines would also get collected. You can verify this in the RSA1? Transport connection screen, or if you have assigned to a request, open up the request and see if you can see R3TR ROUT entries.
Hope this helps...

How to Transport development object in SAP BI

Hi to all,
Please can any body tell me , How to transport development object from one server to another server.
i am fresher in SAP Bi , so i need to know in depth , please also send me website link so i can get more depth knowledge.
Please also send step by step process for that.
i shall be thankfull to you for this.
Regards
Pavneet Rana

<Removed by Moderator>
You can surf through https://help.sap.com for referring the material or surf in SDN forums..where you can lots of info for getting in depth knowledge on this.
hope this is clear for you.
Regards
Ramsunder
Edited by: Pravender on Jun 8, 2010 6:41 PM

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 transport proxy object abap part

Hi ,
I am working with one outbound proxy . The proxy was working fine in production ,now one requirement came in which we have to add one extra field to Proxy .field has been added in message type and proxy was generated in respective ABAP box
abap coding every thing was done and it worked fine in Dev . I transported the PI part ( DT,MT,MI and MM ) .
However I am not sure how to transport the ABAP proxy in ECC from dev to prod .
Can you kindly please tell me all steps I tried to search in SDN but getting confused in what object I have to transport and how from ECC .
Regards,
Saurabh

Hi Sarvesh ,
Thanks a lot for all your reply .
It partially worked as I created the transport with proxy object but not toatally as all my objects are not included in the transport .
when I am doublicking the My proxy interface and then going in used object TAB then I am able to see the structures .
Abap team wants to include these structure in the transport .
Actually the code has already been transported and it is throwing the dump value as it is unable to find the new field as the new strucutre is not transported .
Should I tell Abap team to manually make some random change in the str now and save them again so that when I re generate proxy then it will be added to transport.
Regards,
Saurabh

Personas 2.0: How to "Transport" the whole Personas app to QA sys?

Hi Personas experts,
I have developed some Personas (2.0) apps on Sandbox/Devlopment sys. Now I want to "move" the whole program to QA sys for testing. Can anyone give some details about how to use SAP transpotation to move the "Whole" app?
I am thinking that the followings need to be moved (pls correct me):
1. The configuration of Personas (eg, made by tcode spro) - can this part to be transported directly?
2. The settings such as users, groups made by admin_ui. Can this be transported directly?
3. The app impelmentations - such as all the flavours. Can this part be transported directly? If so, how?
Thanks a lot in advance!
Best regards,
Dong Zhu

Hi Dong
To answer your questions:
1. The configuration of Personas (eg, made by tcode spro) - can this part to be transported directly?
     No this is not transportable ... not in our system anyway ... we had to do this config manually in each client
2. The settings such as users, groups made by admin_ui. Can this be transported directly?
    No, users are setup in each client and assigned their Personas roles per client, groups however are transportable
3. The app impelmentations - such as all the flavours. Can this part be transported directly? If so, how?
     Flavours, groups and media files are transportable via /persos/admin_ui, you must use the 'Transport Objects' option in the 'General Actions' folder.... here you specify each object to be transported and create a transport to include them. Note, if you are using a unique SAP ITS and Personas backend per client, after transporting the object, you will need to go and assign each flavour to your new system in the admin_ui tcode.
Hope this helps,
Neil

How to avoid the objects dependency in the packages by standard settings?

Hi,
How to avoid the objects dependency in the packages by standard settings?
Example Scenario -> Our project uses two packages u2018ZZP1u2019 and u2018ZZP2u2019 for developments in the system u2018SN1u2019. We created a domain u2018ZZ_DO_TESTu2019 in the Package u2018ZZP1u2019. Now we have to make sure that the developer should not use or refer domain u2018ZZ_DO_TESTu2019 for the developments in the package u2018ZZP2u2019.
u2026Naddy

Evevn i felt that in the CTS at least a warning can be given if the included objects refer to any other object(s) which arre:
1. Local Objects
2. Locked under other requests,
3. Lastly able to detect cyclic dependency as in we had a situation where we had a program locked in request A which calls an FM locked in request B. Now Request B refers to a message which is locked in request A.Since it was a message it gave only requrn code 4 in transport and transport ended with warnings. But if it is some other object then it is going to give compile error in at least one transport and neither can be moved without the other.
Anyways, i will check the BAPI he has mentioned and see if any workaround can be done,
Request: Please keep the post active until we arrive at a good solution,Thanks.

How to transport CU02 objects from one system to another?

Hi,
How to transport CU02 objects from one system (Development) to another (Quality)?

You need to set up the object dependency IDOC in the partner profile.Message type is KNOMAS. The transaction to send is CLD2.

How to transport the BW query's variable to BO webi report

Hi all
I'd like to know how to transport the BW query's variable to BO 's webi . today ,I created a sap customer varible in my bw system to get the max calmonth in the active table.The varible in the BW side run's well ,but I use this query to build a new univers ,and created a new webi report base on this univers ,but the question is the webi report can't get the varible's value I wann to know how to transport the bw varible value to BO webi report
Thanks and regards,
Peter .zhu

I have changed my variaable in my bw query ,I found if you use SAP default variable it is ok in BO side . So I get a guidline by SAP default variable ,I changed my customer variable in variables edite ,don't use 'ready for input' .And then the variable can be useful in BO side .
Edited by: peter zhu on Jun 16, 2008 11:43 AM

How to see the object while moving on the artboard?

hello everyone;
maybe a silly question; how to see the object while moving on the artboard? i dont wanna see only the objects bounding box(outline of the object). i wanna see the object it self. thank you.

What have they gone and messed up now?
When I drag an object (with bounding boxes turned on), the object moves and the bounding box stays still until I stop dragging, upon which it snaps to the object’s new position.
If I don’t have bounding boxes turned on (as I usually work), the object moves when dragged.
If what Bedri says is right, they’ve gone and mended something that wasn’t busted.

While transporting the objects from dev to q or production what are the err

Hi all,
While transporting the objects from one system to another what are the errors we get?
Thanks
Kiran Kumar

Hi Kiran,
The purpose of the Forums is to help people with problems, not to "fish" for answers to what appear to be interview questions. There are many ways to become educated in SAP Administration, such as training classes and help documetnation. Please choose these avenues for your questions instead of making these kind of posts in the Forums.
Best Regards,
Matt

How to get the object class field value in CDHDR table for vendor

hi
how to get the object class field value in CDHDR table for vendor

Try KRED/KRED_N as object class in CDHDR for Vendor.

How to transport the object in XI?

Similar Messages

Maybe you are looking for