How to identify the object type in xpress

In ui global.startdate is evalued with Date object type when use display class as DatePicker. After save, the global.startdate is String type. The other place in the code has use this global.startdate to convert to special date string. The problem is how to detect what data type the global.startdate is at one particular moment?

In my case I do the following.
1. Use the following rule to display the date in the desired format.
<invoke name='dateToString' class='com.waveset.util.Util'>
<ref>inputdate</ref>
<s>MM-dd-yyyy</s>
</invoke>
At any point in time if one wants to know, one explicity needs to convert the java.util.Date obtained from datepicker using dateToString method in the Util class.
2. When one wants to insert the date into the database then the following can be done.
     // First Convert the dates into appropriate formats
     SimpleDateFormat formater = new SimpleDateFormat("mm-dd-yyyy");
     java.sql.Date _startDate     = null;
     if(startdate != null) {
          java.util.Date parsedDate = formater.parse(startdate, new ParsePosition(0));
          _startDate = new java.sql.Date(parsedDate.getTime());
          System.out.println("_startDate::::"+_startDate);
     }

Similar Messages

  • How to initialize the object type in pl/sql

    Hi,
    I am looking for an easy way to initialize the object type in pl/sql.
    I have created a object type with around 2 attributes.
    when ever i need to initialize the object ..need to pass:
    declare
    v_obj emp_obj;
    begin
    v_obj := emp_obj(null,null);
    then i can assign the values to object.
    Since I am having more than 50 attributes.. need to pass null to all the object attributes.
    is there any other way to initialize the object.
    thanking you in advance!!!

    RTFM [url http://oraclesvca2.oracle.com/docs/cd/B10501_01/appdev.920/a96594/adobjadv.htm#1008810]Advantages of User-Defined Constructors

  • How to identify the file type in a safe way

    I need to identify the filetype of a file in my disc.
    I watched over internet and i've found this good site:
    http://filext.com/
    that supplys the "magic bytes" for many kind of files.
    I have also looked over internet for some ready class that identify different file types, and I have found FFident:
    http://schmidt.devlib.org/ffident/index.html
    Do you know any other Java package/class that is able to identify correctly the file types?
    Thank you,.

    The OS just watch the extension of the file.Not always. If you create a word doc but name it with
    some other extension, the OS still can determine that
    it is a word doc.On which OS?
    if i take foo.exe and i rename foo.doc so my OSwill
    try to open it as a MS Word Document.Again, garbage in, garbage out.What you mean?
    If I create a MS Word Document for a file .doc that is not a real .doc and it is not able to read, i will just lose cpu time and a lot of memory.
    So it is important to understand if I need really to open MS Word watching what is the real file type
    Either way, you're going to be doing way too much
    work (and wheel-reinventing) if you're going to build
    your own detection scheme.In the SDK there is not any file type checker, and if eventually really exists an OS like you say that is able to read inside the file, i prefer to have my own Java class that do that work in a safe and opensource way.
    However in my first post i've given a site with some java code that do what I need, i just was asking if anyone know if there is any ready-to-work java class that is better for doing this work.

  • How to identify the media type 32 or 64 bit from installed oracle client

    hi guys,
    I have oracle client 11g r2 installed in my machine which is a AIX. but not sure of the media type. 32 or 64 bit. this information is required further to proceed in my further application compatability.
    tilll the previous release there was many hints like.. lib and lib32 in various locations. but not in 11g r2 i guess.
    can someone please help me to find out this piece of information..
    thanks in advance.
    rgds
    Shravee

    908038 wrote:
    hi karthick,
    thanks for replying. first of all i would like to say that I was not able to find the path which you have mentioned below.
    but i understood your intentions.
    so directly looked for a executable file of sqlplus underr oraclehome/bin. and i got few error messages, saying sqlplus could not be loaded. this could be because my 10g is currently configured. and not 11g as we dont want to disturb the environment without confirmation.You said this was AIX. So when you log on to the server, your "environment" only exists for that session you have created to log on. Set ORACLE_HOME to point to your 11.2 installation, and set PATH to point to $ORACLE_HOME/bin. Those settings are only good for that session, so will not impact anything else.
    If sqlplus reports 64 bit, well, that's obviously 64 bit. If it's 32-bit, it won't say anything about it, so "not 64 bit" must be 32-bit.
    >
    however, i tried to execute the same file for 10 g to check if 10g gives any info, but only got the version not 32 or 64 bit.
    rgds.
    Shravee

  • How to identify the Encoding type in an XML

    Hi all,
    Is it possible to identify the encoding set to and XML programatically?
    for example :
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <student>
    </student>
    in this is it possible to find out the encoding value set (ISO-8859-1) ?
    Thanx in Adv,
    Potluri

    Hi, if you have a parser that is only DOM level 2 compliant then there is no way to get at the xml declaration via the JAXP and org.w3c.dom apis. It is expected that DOM level 3 will have the functionality in the Document interface to access the xml declaration attributes like the encoding. I don't know if there are any DOM level 3 parsers available, check xml.apache.org to look at the xerces parsers. However as xml files are text files you could right a program using java.io package to look for the <?xml version ...> tag and then to search that line for the encoding.
    Hope this helps.

  • How to determine the object type?

    Hi,
    I got a method that is of the following signature:
    Object result = method.invoke(object,args);The result can be any type from primitive types like double to class type.
    How can I determine whether the result object is of what type?
    I am thinking of using
    (if result instanceof Double)
          //do something
    }However, the method call invoke can return a primitive type double, so will the above method
    (if result instanceodf Double) be called?
    Thanks.

    However, the method call invoke can return a primitive
    type double, so will the above method
    (if result instanceodf Double) be called?(result instanceof Double) will be true because quoting the javadocs for Method.invoke(): "if the value has a primitive type, it is first appropriately wrapped in an object."
    http://java.sun.com/j2se/1.4.2/docs/api/java/lang/reflect/Method.html#invoke(java.lang.Object,%20java.lang.Object[])

  • How to find the file type without the file extension using indesign javascript (.jsx)

    hi,
    How to identify the file type (eg: InDesign or Quark) without knowing their file type. How can we find what kind of file is that??? without their extension like ('.indd','.qxd') before import to the document...

    Hi subha_oviya,
    Take a look at the file filtering section in the InDesign CS3 sample script ImageCatalog.jsx to see how to look for file types. I'm assuming that you're using InDesign CS3, and that you're using the Mac OS--you didn't say.
    Thanks,
    Ole

  • How to identify the type of pocketpc barcode scanner?

    How to identify the type of pocketpc barcode scanner whteher it is intermec or symbol?
    GS

    Hi,
    well, this is the brand of the PDA - the Scanner itself is build into the device. So if you have an intermec device - you have an intermec scanner and vice versa. It is not recommended to use a HP device for example with an external scanner. This scenario is not really supported by the MI setup guides.
    Hope that helps!
    Regards,
    Oliver

  • How to Identify the Type of Font Names in Illustrator

    How to identify the type of font names like "True Type font" (or) "open Type font" for illustrator file using Scripts or any language. Could you please advice me.
    Thanks,
    Prabudass

    If there is an Illustrator SDKor Illustrator Scripting forum, try
    that. ATM won't really help - it is obsolete and should not be
    installed (breaks things).
    Aandi Inston

  • How to identify the type of Fonts

    How to identify the type of font names like "True Type font" (or) "open Type font" for illustrator file using Scripts. Could you please advice me.
    Thanks,
    Prabudass

    The code below will prompt the user with the type face of a single text-frame.
    shastafir
    // 5/4/2009
    // Open a new document and create a single text box
    // with some type in it.
    // Get access to the active layer
    var aiDocument = app.activeDocument;
    var aiLayer = aiDocument.activeLayer;
    // Get access to the type-frame's font
    var textBox = aiLayer.textFrames[0];
    var theFont =
    textBox.textRange.characterAttributes.textFont;
    // Alert user with the name of the font
    alert(theFont.name);

  • How to identify the locks in oracle db objects? i dont have access to check

    How to identify the locks in oracle db objects? i dont have access to check the v$lock or v$ objects. i dont have dba access. what are the symptoms for table, row or objects lock? how v guess it would be lock?
    Thanks in advance friends..

    I believe you will have to call your DBA on the phone in that case.
    You can query something with a select ... for update nowait.
    If it raises an exception you can handle it within a when section.
    -- Running in one session
    SQL> create table t1 as select 1 col1 from dual;
    Table created
    SQL> select * from t1 for update nowait;
          COL1
             1
    SQL>
    -- now running in a different session
    SQL> select * from t1 for update nowait;
    select * from t1 for update nowait
    ORA-00054: resource busy and acquire with NOWAIT specified
    SQL> set serveroutput on
    SQL>
    SQL> DECLARE
      2    CURSOR cur1 IS
      3      SELECT col1 FROM t1 FOR UPDATE NOWAIT;
      4    v_col1 NUMBER;
      5    locking_error EXCEPTION;
      6    PRAGMA EXCEPTION_INIT(locking_error, -00054);
      7  BEGIN
      8    OPEN cur1;
      9  EXCEPTION
    10    WHEN locking_error THEN
    11      dbms_output.put_line('Busted locking my rows!');
    12  END;
    13  /
    Busted locking my rows!
    PL/SQL procedure successfully completed
    SQL> Now, surely you won't be able to tell anything else other than there was something locked there.
    But none of the details you would find in the views.

  • How to Convert OBJECT_TYPE to the Object Type Used for DBMS_METADATA?

    How do you convert the object type in ALL_OBJECTS to the object type that DBMA_METADATA.GET_DDL expects?
    Thanks,
    Kurz

    maybe one needs to find a mapping between sys.metaview$ and all_objects:
    SQL> select type, xmltag, udt, viewname from sys.metaview$ where type like '%PACKAGE%'
    TYPE                      XMLTAG                    UDT                       VIEWNAME                
    DE_S_PACKAGE                                                                                          
    DE_S_COMP_PACKAGE                                                                                     
    DE_S_COMP_PACKAGE2                                                                                    
    DE_S_COMP_PACKAGE_SPEC                                                                                
    DE_S_PACKAGE_BODY1                                                                                    
    DE_S_PACKAGE_BODY                                                                                     
    SE_PACKAGE                                                                                            
    SE_COMP_PACKAGE                                                                                       
    SE_COMP_PACKAGE2                                                                                      
    SE_COMP_PACKAGE_SPEC                                                                                  
    SE_PACKAGE_BODY                                                                                       
    PACKAGE                   PACKAGE_T                 KU$_PROC_T                KU$_PKG_VIEW            
    PACKAGE                   PACKAGE_BODY_T            KU$_PROC_T                KU$_PKGBDY_VIEW         
    PACKAGE                   FULL_PACKAGE_T            KU$_FULL_PKG_T            KU$_FULL_PKG_VIEW       
    PACKAGE_SPEC              PACKAGE_T                 KU$_PROC_T                KU$_PKG_VIEW            
    PACKAGE_BODY              PACKAGE_BODY_T            KU$_EXP_PKG_BODY_T        KU$_EXP_PKG_BODY_VIEW   
    ALTER_PACKAGE_SPEC        ALTER_PACKAGE_SPEC_T      KU$_ALTER_PROC_T          KU$_ALTER_PKGSPC_VIEW   
    ALTER_PACKAGE_BODY        ALTER_PACKAGE_BODY_T      KU$_ALTER_PROC_T          KU$_ALTER_PKGBDY_VIEW   
    18 rows selected.

  • How to identify the variable processing type

    Hi Experts,
    How to find the details of the variable whether it is filling with user exit or replacement path
    Say i have a variable xxx , how to identify the above details.
    Thanks,

    use RSZGLOBV table in VNAM give your variable and VPROCTP will give you processing type

  • How to trigging a object event which the object type has two key fields

    Hi,kind guys
    I use the object type QMSM about qualification notification task,it has two key fiedls,qualification notification number and task number (can display by t-code -QM03), I want to trigging the event 'create' in  BOR 'QMSM ' by function SWE_EVENT_CREATE(or SAP_WAPI_event_create), but it only has one object key ,
    example:
    CALL FUNCTION 'SWE_EVENT_CREATE'
      EXPORTING
        OBJTYPE                       =  OBJTYPE
        OBJKEY                        =  OBJKEY " only one key
        EVENT                         =   EVENT
    but the BOR object 'QMSM' has two keys,so it cann't be trigged rightly.
    thanks for any help.

    You have to Concatenate the Business object keys and pass it in one variable OBJKEY.
    Thanks
    Arghadip

  • 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

Maybe you are looking for

  • Pictures in iPhoto turn into tiny square

    HI... When I view my pictures in iPhoto, they turn into tiny squares. How do I get rid of this? What happened to my iPhoto? I have OS X 10.9.5 installed and iPhoto version is 9.5.1 Thanks Jen

  • Does CF really auto-decode URL parameters passed to a page?

    CF docs and livedocs state that: quote: ColdFusion automatically decodes URL parameters that are passed to a page (for example, see the URLEncodedFormat tag description, last sentence of opening paragraph) However, if you have a url-encoded url param

  • Difference in F.07 & FBL1n

    Dear Experts, I have a problem in F.07. There is some vendors have the balance in INR (company Code Currencty) and USD ( Transaction Currency). While running the F.07 its showing the balance xxxxxx. after run the F.07 we are corss checking the balanc

  • Reg:mm tables

    Hi friends, if u know table name for request for quotation date kindly tell me. thank u. regards Suchithra

  • Change password without cd or any other information

    please help me changing my admin password for mak 10.6 , without cd