Inactive INfoobjects

Hi,
May I know how to find all the Inactive infoobjects of the BW system
Thank you
Savitha

to be more specific:
If your cube has been working well, there's must be a cube (at least in development system or Q-System) with all the InfoObjects - you can transport this data model into the system, where the InfoObject is missing. Of course, on this way you can transport the missing Info Object as well.
Normally there will be an inconsistent in the database caused of missing InfoObject. Adding a new field (missing InfoObject) means also, that you change the structure of the table. If you hold data of 1yr (which is large), it's better to save the data in a back-up table (via SQL-Script for example) and then delete all data in your data target before you do the transport. Then restore the data from the backup table. The problem is more, how you fill the new column (missing object). If it's a master data attribute - just reading from the correspodent master data table or convert from another Info Object. If it's a key figure it' more difficult and in this case you may have to reload the whole data from ECC.
However to identify a cube as a table in SQL-Language is complicated. This interview question sounds simple, there may be a simple answer which is not coming to my mind at the moment. Maybe I haven't understand the question correctly. I'd be interrested on another suggestions!

Similar Messages

  • Error while activating all inactive infoobjects in DEV

    Hai
    Im trying to activate all inactive infoobject by using program RSDG_IBOJ_ACTIVATE. But it says the following error
    <b>System error in lock management
    Message no. AD025
    Diagnosis
    A system error has occurred in the lock management function.
    The system was unable to determine whether a lock entry existed for the selected object.
    System Response
    The selected object could not be locked.
    Only display mode can be used.
    Procedure
    Make a note of the error code and inform your system administrator.</b>
    why it is like this
    how can i activate all inactive infoobjects in development server.
    kumar

    Hi,
    It seems objects are locked in transport request. Check the 'object directory entry' for the object and find out the transport request/task under which objects are locked. Remove the objects from TR or release the request and then try to activate.
    Hope it helps.
    Regards,
    Aditya

  • Inactive InfoObjects in MultiProvider based on InfoSet after Upgrade NW04s

    We are upgrading our sandbox environment from BW 3.5 to NetWeaver 2004s or BI 7.0. We have done a technical upgrade and are currently using the obsolete authorizations. In testing we have discovered that our MultiProviders that are based on InfoSets contain inactive InfoObjects. Has anyone else had this problem. In running a query that uses this MultiProvider we get the message to activate our MultiProvider again.
    Is it necessary to activate all existing MultiProviders based on InfoSets after upgrading to NetWeaver 2004s?
    Thanks for your help,
    Jeri

    Hi Jeri,
    Yes this is sometimes required.
    Infosets are sometimes deactivated because additional checks are available after the upgrade or because new attributes become part of your info-object.
    When you change something to an underlying data provider of a multiprovider, the multiprovider is automatically inactivated and you have to reactivate it.
    I also had this problem with other upgrades.
    In general, activation is not too much of an effort.
    Please assign points if this solved your problem,
    Best Regards,
    Filip Ledoux

  • Inactive infoobjects in Production system

    Hi All,
    I have started the transportation from BI dev to BI production and I am facing a problem all the objects are inactive in BI production while as those objects are active in BI dev.
    I cannot use infoobject activation program in production and niether I can do it manually.
    I will appreciate  your replies.
    Let me tell you this is fresh transport and only first unassigned infoobjects were transported.
    Regards
    Rahul Bindroo

    Hi Rahul,
    Any message after transport?
    Did you replicate your R/3 data sources first before transporting anything. I think you need to replicate r/3 datasources first and than try others. Replicate datasources going to your BW server RSA1->Source Systems and replicate.
    Here are the sequence I maintain for transporting but different people do differently. I find it very helpful transporting staffs piece by piece so that if there are any errors, I can solve the problem easily.
    BW  Transport Sequence:
    Info Object – Transport only infoobject.
    Info Area
    Info Catalog
    Cube & ODS –togather
    Multi-Provider/Multicube -
    Infoset
    Transfer /Update Rules
    Role and Authorization
    Report
    Workbook
    Hope it helps..

  • Inactive InfoObject after Transport

    We modified an InfoObject and transported the change; however, our BWQ system still does not recognize the InfoObject has active.  And the InfoObject is active in BWD. 
    Our BWD system has the automatic transport connection active; then we went back and manually assigned it to a transport using RSA1 (Before and After) grouping mode.

    Yes it should not require a deletion of data. But can you tell me what the error message is?? It might be that you have to transport just the object first without turning on nav. attr and then send nav.attr turned in the next transport.
    Let me know if you resolved it, or if you are facing the same problem.

  • InfoObject Inactive

    Experts,
    There are two fields on calmonth level and I pulling the data to DSO. One field I have sap delivered 0calmonth infoobject. Another I was asked to custom create as zcalmonth using 0calmonth reference char. I did that and typed 0calmonth in reference char. After creating this I activated it. But, when I created the DSO and tried to get the required fields to data fields, it is still showing this zcalmonth as inactive infoobject on the DSO creation screen. Can anyone help me out in rectifying this?
    Thanks,
    Pooja

    hi Pooja,
    perhaps you did that at the different session when system not yet refreshed, check again that infoobject and make sure it's in active version, try RSA1 to refresh.
    hope this helps.

  • Program To Activate Infoobject Catalog

    Hi Friends,
    Can you please share the program that is used to activate the inactive infoobject catalog.
    I require this because the catalog is inactive in quality after transport.
    I am in need of the program as all my transports are failing.
    Catalog is notassigned characteristics catalog. (mismatch in the objects in the system turned the catalog to inactive status.
    Regards,
    Ramesh

    Hi Ramesh,
    Since the catalaog is a Not assigned char catalog, why do you want to transport it?
    If you have info objects under them you can just transport the objects with out transporting the catalog.
    If it is not a new catalog there is no need to transport it.
    I have done this quite a few times and it has transported sucessfully and all my new info objects were in the active state.
    thanks,
    rahul

  • Mass Infoobject reactivation timing out

    hello all
    my transports have been failing due to inactive infoobjects (huge number of iobj which are inactive) and i have used rsdg_iobj_activate program to reactivate all my infoobjects. But after the program ran for a while it timed out ..is there a work around for this ?
    Your suggestions are appreciated.
    Thanks

    Kamal,
    When we get any Timeout error, only option is we can schedule as Back ground Job or split the work into peices.
    Regards,
    Nagesh Ganisetti.

  • Infoobject deletion

    hi
    i have few doubts regarding the infoobject deletion.
    1. If we delete the Standard infoobject, will it just delete active version of the object or deleivery version also ?
    2. Is there any way other than RSD1 to delete inactive infoobjects.

    Hi,
    It deletes only the active version of the info-object and you would always be able to reactivate once you need it.
    RSD1 is the best place to delete it. Other option would be use a fn module to delete the inactive info-objects. But deleting the info-objects one-by-one after checking is the best option to avoid any confusion.
    Bye
    Dinesh

  • 2lis_13_vdkon

    We are getting the following error when transporting to bi qlty.
    Further I find the info objects 0KAPPL, 0KINAK, 0CONDRECNO, 0kstat, 0KINAK  are missing in BI QAS system. Do we need to do activate KBETR, KNUMH, MWSK1 in R/3 as I find the standard data source is highlighted in BLUe and the appended fields are black  in maintenance structure of lbwe
    quote
    =======
    Activation of Objects with Type DataStore Object
         InfoObject 0KAPPL is not available in version A
         InfoObject 0KAPPL is not available in version A
         InfoObject 0KAPPL is not available in version A
         Checking Objects with Type DataStore Object
         Checking DataStore Object ZSD_O36
         InfoObject 0KAPPL is not available in version A
         Inconsistencies found while checking DataStore object ZSD_O36
         Saving Objects with Type DataStore Object
         Start of the after-import method RS_ISTD_AFTER_IMPORT for object type(s) ISTD (Activation Mode)
         Start of the after-import method RS_ISCS_AFTER_IMPORT for object type(s) ISCS (Activation Mode)
         InfoObject Condition is Used for Statistics ( 0KSTAT ) is not active, total of 3 inactive InfoObjects
         InfoObject Application ( 0KAPPL ) is not active
         InfoObject Condition Status (Active/Inactive) ( 0KINAK ) is not active
         InfoObject Condition is Used for Statistics ( 0KSTAT ) is not active
         Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Activation Mode)
         Mapping between data source 2LIS_13_VDKON and source system QASCLNT900 is inconsistent
         InfoObj. 0KAPPL from fld KAPPL of dataSource 2LIS_13_VDKON is not active but BCT ex. -> Dtl
         Field KBETR will not be delivered from DataSource 2LIS_13_VDKON in source system QASCLNT900
         InfoObj. 0KINAK from fld KINAK of dataSource 2LIS_13_VDKON is not active but BCT ex. -> Dtl
         Field KNUMH will not be delivered from DataSource 2LIS_13_VDKON in source system QASCLNT900
         InfoObj. 0CONDRECNO from fld KNTYP of dataSource 2LIS_13_VDKON is not active but BCT ex. -> Dtl
         Field KNUMV will not be delivered from DataSource 2LIS_13_VDKON in source system QASCLNT900
         InfoObj. 0KSTAT from fld KSTAT of dataSource 2LIS_13_VDKON is not active but BCT ex. -> Dtl
         Field MWSK1 will not be delivered from DataSource 2LIS_13_VDKON in source system QASCLNT900
         Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Activation Mode)
         Reference to transfer structure 2LIS_13_VDKON_RA not available. No activation possible.
         Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)
         No rule exists
         Source RSDS 2LIS_13_VDKON QASCLNT900 does not exist
         Target RSDS 2LIS_13_VDKON QASCLNT900 does not exist
         Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Delete Mode)
         Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Delete Mode)
         Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Delete Mode)
         Start of the after-import method RS_ISCS_AFTER_IMPORT for object type(s) ISCS (Delete Mode)
         Start of the after-import method RS_ISTD_AFTER_IMPORT for object type(s) ISTD (Delete Mode)
         Start of the after-import method RS_ODSO_AFTER_IMPORT for object type(s) ODSO (Delete Mode)
         Start of the after-import method RS_IOBJ_AFTER_IMPORT for object type(s) IOBJ (Delete Mode)
         Errors occurred during post-handling RS_AFTER_IMPORT for IOBJ L
         RS_AFTER_IMPORT belongs to package RS
         The errors affect the following components:
            BW-WHM (Warehouse Management)
         Post-import method RS_AFTER_IMPORT completed for IOBJ L, date and time: 20090310171850
         Post-import methods of change/transport request RBDK906162 completed
              Start of subsequent processing ... 20090310171841
              End of subsequent processing... 20090310171850

    Hi,
    First u replicate the datasource in quality bw from quality r/3 ,then in error which r the objects are not active ,install those objects in dev bw and first collect those objects then u can transport these datasource.
    Thanks & Regards
    sathish

  • Source system in Production doesnt exists Error RC- 8

    Hello experts!
    We connected a second source system to our 7.0 BW. We transported from development to quality system and everything is fine. Now we want to transport to production and we got RC=8 and the message that our "source system does not exist"
    First we checked our source system. It is ok. we can replicate datasources, load units and currencies. But when we want to transport something what is directly connected to the source system we got everytime a RC=8 because of source system. For sure, we checked our "Conversion of logical source systems names". We checked if the mapping from development to productive is correct many times but we can find no error.
    Is there something I can not see?
    I tried to transport Transformations, DataSource Migration, other things connected to 7.0 and 3.x DataSources. Nothing works. I transported a transformation got a little different error like no rules exist because missing infoobjects in source or target or they are not activated. But target seems to be ok and source also have the fields.
    Also I have searched the previous threads I have got what I have done but for sure some thing I am missing !!
    Any Ideas???
    Best regards,
    Yash

    Thanks Murali for your prompt reply,
    I have manged to do the conversion settings again and now the source system client problem subsides !!!
    But when I import the requests again from QA to PRD it says that some DS cannot be activated due to inconsistency in CRM production system. Actual message is.
    Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Activation Mode)
    Mapping between data source 0CRM_SRV_CONTRACT_H and source system PC4CLNT400 is inconsistent
    Start of the after-import method RS_ISCS_AFTER_IMPORT for object type(s) ISCS (Activation Mode)
      InfoObject Source System of Preceding Doc. ( 0PRELOGSYS ) is not active, total of 4 inactive InfoObjects
      InfoObject Exchange Rate Date ( 0CRM_EXCDAT ) is not active
      InfoObject Exchange Rate Type ( 0CRM_EXCTYP ) is not active
      InfoObject Quotation GUID ( 0CRM_QUOGUI ) is not active
      InfoObject Source System of Preceding Doc. ( 0PRELOGSYS ) is not active
      InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
      InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
      InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
      InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
    is that due to the DS .. some are in BI 7 cannot be mapped with 3.X  ?
    I will be importing a new request all the way from DEV to QA and Then in PRD as of now to see the inconsistency once again.
    Cheers
    Yash

  • Activation Problem from Dev to QA through transport

    We are tryiing to do a transport from Dev to QA and we are getting the following error even after several re-import of a request. We have also checked and rechecked the activated infoobjects and also if any of the objects are locked by some other request or not.
    The request gets cancelled with error code -12.
    It looks like when we transport the InfoObjects in small bunch, it gets successfully transported, otherwise if there are lots of InfoObjects in a request then it fails.
    Error log is :
    tart of the after-import method for object type R3TR IOBJ (Activation Mode)
    System error in lock management
    Error AD 025 when handling objects with type R3TR IOBJ
    Start of the after-import method for object type R3TR ODSO (Activation Mode)
    Lock table overflow
    Start of the after-import method for object type R3TR CUBE (Activa
    Error when checking InfoCube 0CSAL_C01
    InfoObject 0BP_ACTIVIT is not available in active version
    InfoObject 0BP_CONTPER is not available in active version
    InfoObject 0CRMPU_OG_R is not available in active version
    InfoObject 0CRMSA_OG_R is not available in active version
    InfoObject 0CRMSE_OG_R is not available in active version
    InfoObject 0CRM_CAT is not available in active version
    InfoObject 0CRM_DIRECT is not available in active version
    InfoObject 0CRM_OBJECT is not available in active version
    InfoObject 0REJECTN_ST is not available in active version
    InfoObject 0REASON_REJ is not available in active version
    InfoObject 0NET_VALUE is not available in active version
    InfoObject 0CML_OR_QTY is not available in active version
    InfoObject 0NET_PRICE is not available in active version
    Check the InfoCube online
    Start of the after-import method for object type R3TR MPRO (Activation Mode)
    Lock table overflow
    Lock table overflow
    Lock table overflow
    Start of the after-import method for object type R3TR ISTD (Activation Mode)
    Start of the after-import method for object type R3TR ISCS (Activation Mode)
    InfoObject FA COMPLETION DATE ( ZFCOM_DT ) is not active, total of 175 inactive InfoObjects
    InfoObject Business Transaction Type ( 0CRM_PRCTYP ) is not active, total of 33 inactive nfoObjects
    InfoObject ACTIVITY: Sloution Description ( ZSOLDESC ) is not active, total of 67 inactive InfoObjects
    Activation of communication structure /BIC/CS0PLANT_ATTR in Dictionary failed
    Activation of communication structure /BIC/CS0PLANT_TEXT in Dictionary failed
    Activation of communication structure /BIC/CS0WBS_ELEMT_ATTR in Dictionary failed
    Activation of communication structure /BIC/CS0WBS_ELEMT_TEXT in Dictionary failed
    InfoObject Value Type for Reporting ( 0VTYPE ) is not active, total of 19 inactive InfoObjects
    InfoObject Value Type for Reporting ( 0VTYPE ) is not active, total of 13 inactive InfoObjects
    InfoObject Number of orders ( 0ORDERS ) is not active, total of 8 inactive InfoObjects
    InfoObject Long Number for Configurable Material ( ZMATCFG ) is not active, total of 46 inactive InfoObjects
    InfoObject Cumulative order quantity in sales units ( 0CML_OR_QTY ) is not active, total of  inactive InfoObje
    InfoObject Net Price per 1*VKME ( 0NETPR_VKM ) is not active, total of 13 inactive InfoObjects
    InfoObject Record deleted ( 0REC_DELETD ) is not active, total of 24 inactive InfoObjects
    InfoObject Delivery ( 0DELIV_NUMB ) is not active, total of 15 inactive InfoObjects
    InfoObject Preceding document category ( 0PRVDOC_CTG ) is not active, total of 28 inactive InfoObjects
    InfoObject Goods Issue Date: Delivery Header ( 0GI_DATE_DH ) is not active, total of 34 inactive InfoObjects
    InfoObject No.of billing docs ( 0NO_INV ) is not active
    Activation of communication structure /BIC/CS2LIS_13_VDITM in Dictionary failed
    Activation of communication structure /BIC/CS2LIS_13_VDKON in Dictionary failed
    InfoObject 0REJECTN_ST is not available in active version
    InfoObject 0REASON_REJ is not available in active version
    InfoObject 0NET_VALUE is not available in active version
    InfoObject 0CML_OR_QTY is not available in active version
    InfoObject 0NET_PRICE is not available in active version
    Check the InfoCube online
    Start of the after-import method for object type R3TR MPRO (Activation Mode)
    Lock table overflow
    Lock table overflow
    Lock table overflow
    Start of the after-import method for object type R3TR ISTD (Activation Mode)
    Start of the after-import method for object type R3TR ISCS (Activation Mode)
    InfoObject FA COMPLETION DATE ( ZFCOM_DT ) is not active, total of 175 inactive InfoObjects
    InfoObject Business Transaction Type ( 0CRM_PRCTYP ) is not active, total of 33 inactive InfoObjects
    InfoObject ACTIVITY: Sloution Description ( ZSOLDESC ) is not active, total of 67 inactive InfoObjects
    Activation of communication structure /BIC/CS0PLANT_ATTR in Dictionary failed
    Activation of communication structure /BIC/CS0PLANT_TEXT in Dictionary failed
    Activation of communication structure /BIC/CS0WBS_ELEMT_ATTR in Dictionary failed
    Activation of communication structure /BIC/CS0WBS_ELEMT_TEXT in Dictionary failed
    InfoObject Value Type for Reporting ( 0VTYPE ) is not active, total of 19 inactive InfoObjects
    InfoObject Value Type for Reporting ( 0VTYPE ) is not active, total of 13 inactive InfoObjects
    InfoObject Number of orders ( 0ORDERS ) is not active, total of 8 inactive InfoObjects
    InfoObject Long Number for Configurable Material ( ZMATCFG ) is not active, total of 46 inactive InfoObjects
    InfoObject Cumulative order quantity in sales units ( 0CML_OR_QTY ) is not active, total of 9 inactive InfoObje
    InfoObject Net Price per 1*VKME ( 0NETPR_VKM ) is not active, total of 13 inactive InfoObjects
    InfoObject Record deleted ( 0REC_DELETD ) is not active, total of 24 inactive InfoObjects
    InfoObject Delivery ( 0DELIV_NUMB ) is not active, total of 15 inactive InfoObjects
    InfoObject Preceding document category ( 0PRVDOC_CTG ) is not active, total of 28 inactive InfoObjects
    InfoObject Goods Issue Date: Delivery Header ( 0GI_DATE_DH ) is not active, total of 34 inactive InfoObjects
    InfoObject No.of billing docs ( 0NO_INV ) is not active
    Activation of communication structure /BIC/CS2LIS_13_VDITM in Dictionary failed
    Activation of communication structure /BIC/CS2LIS_13_VDKON in Dictionary failed
    How do we get rid of this?
    Thanks
    Sachin

    Hi,
    There are many info objects which are not activate, because of this all other objects are failed, so create seperate trasport request for info objects and another request for Data source and info providers.
    Cheers,
    Malli.

  • How to revert back the changes that have made to Infoset

    Dear Experts,
    Can any one help me with solution for the below issue?
    I have activated(checked) some navigational attributes to the infocube "XYZ".This "XYZ" infocube is used in Infoset and as well as in multiprovider.Instead of activating navigational attributes in the infoset ,mistakenly i have removed the infocube and reassigned(reconnected with previous settings) in the infoset.Now i realized that the technical reference names in infoset(For ex:"ABC_F12,ABC_F13") got changed and giving the problem in Multiprovider.And there are n number of queries build based on the multiprovider.
    While iam trying to activate the inactived Multiprovider iam getting an error message saying "inactive infoobjects ...(.ABC_F12,ABC_F13 are not available)....
    Can any body help me how to revert back the changes for the Infoset that i have made or anyother process to sort out this issue.
    Earlier solutions will be appreciated.
    Thanks & Regards,
    Prathish.

    Hi,
    If the changes have been saved, then there is no automatic way of reverting the changes. To get the Infoset in the reqd state, you will have to move an unchanged copy into the dev sys. The easiest way would be to transport a copy from the Prod sys. But first you have to check whether the transport path exists. With the help of Basis team, you can do this.
    wish u luck.
    Regards,
    Rahul

  • 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

  • HELP  Regarding Problem Found during transportation

    Hi Experts
    I was transported my request from DEV  to PROD
    When i am Importing my Objects in Producton server System is throwing
    this Error.
    --Start of the after-import method for object type R3TR UPDR (Activation Mode)
    Info object VV00B is not available in version A
    ERROR R7 245 when handling objects with type R3TR UPDR .
    --Start of the after-import method for object type R3TR IOBC (Activation Mode)
    InfoObject VV00B is not available in active version.
    InfoObject VV175 is not available in active version
    InfoObject VV176 is not available in active version
    --Start of the after-import method for object type R3TR ISCS (Activation Mode)
    InfoObject <No Text Available in this Language> ( VV00B ) is not active, total of 3 inactive InfoObjects
    --Errors occurred during post-handling RS_AFTER_IMPORT for CUBE L
    Ended with return code:  ===> 12 <===
    I am in a very confusing state
    THIS IS THE FIRST TIME I AM FACING THIS TYPE OF PROBLEM
    its very urget
    <b>Any thing and Every thing will  Rewarded</b>

    Hi Raj,
    check this OSS note 1033750
    Symptom
    When you collect Content with transaction RSOR the system issues error message R7 245: 'InfoObject &1 is not available in version A'.
    Other terms
    R7 245
    Reason and Prerequisites
    This problem is caused by a program error.
    Solution
    SAP NetWeaver 2004s BI
               Import Support Package 13 for SAP NetWeaver 2004s BI (BI Patch 13 or SAPKW70013) into your BI system. The Support Package is available once Note 991093 "SAPBINews BI 7.0 Support Package 13", which describes this Support Package in more detail, has been released for customers.
    In urgent cases, you can implement the correction instructions as an advance correction.
    You must first read Note 875986, which provides information about transaction SNOTE.
    To provide information in advance, the notes mentioned above may already be available before the Support Package is released. In this case, the short text of the note still contains the words "Preliminary version".
    Before you implement an advance correction (if one exists and you want to implement it), see Note 875986. This collective note contains all corrections that refer to the SAP Note Assistant and prevent problems during the implementation. You must call transaction SNOTE again after you have implemented the collective note.
    Hope this helps,
    Sudhakar.

Maybe you are looking for