What is difference between u0091AT SELECTION SCREENu0092 & u0091AT SELECTION-SCREEN OUT

What is difference between ‘AT SELECTION SCREEN’ & ‘AT SELECTION-SCREEN OUTPT’ events?

AT SELECTION SCREEN is the event after user input at selection screen,
while AT SELECTION SCREEN OUTPUT is the event before program display output to screen.
They are similar to PROCESS AFTER INPUT and PROCESS BEFORE OUTPUT   in dialog program.
*** is usually used for entry validation , while ASSO is usually used for display formatting

Similar Messages

  • Difference between At selection-screen  and At selection-screen field

    I need to know the difference between
    Difference between At selection-screen  and At selection-screen field
    Regards
    Shashi

    Hi,
    AT SELECTION-SCREEN is the event triggered in the PAI of the selection screen.
    AT SELECTION-SCREEN on field field_name is the event specific to the field and is triggered when u press enter in that field.
    AT SELECTION-SCREEN selscreen_event.
    Effect
    This statement defines event blocks for different events selscreen_event that are triggered by the ABAP runtime environment during selection screen processing.
    Selection screen events occur immediately before sending a selection screen and after certain user actions on a displayed selection screen. They assist in selection screen processing in the ABAP program.
    AT SELECTION-SCREEN is triggered at least twice during actions on selection screens that are linked into another selection screen as a subscreen - first for the linked selection screen itself, and then for the linking selection screens.
    SELECTION-SCREEN FIELD SELECTION
    FOR {NODE|TABLE} node [ID id].
    Effect
    This statement defines a node node in the structure of the logical database for field selection. If a node belongs to type T, you can use the TABLE addition instead of NODE. The statement cannot be used for type C nodes. .
    If a node is defined for field selection, you can use an executable program linked to the logical database in the GET statement to control which fields in the node are to be read by the logical database. If you use the function module LDB_PROCESS, the FIELD_SELECTION parameter must be specified accordingly.
    for more details check this link...
    http://help.sap.com/saphelp_46c/helpdata/en/9f/db9a2e35c111d1829f0000e829fbfe/frameset.htm
    Regards,
    Priyanka.

  • Difference between standard selection screen and selection screen

    hi guyz,
    im asking this because in the table D010SINF there are two fields  sdate and idate which has different dates in it for some programs and same dates for some..bit confused:(
    thanks

    hi BrightSide 
    standard Selection means
    suppose if you are using parameters means system defaultly generate one screen under the Screen Number 1000
    Selection Screen means you are creating a screen using
    stament SElection-Screen begin of screen 100..
    this is the difference whatever the screen other than '1000' is selection Screen, where as 1000 is Standard Selection Screen
    Regards
    Deva

  • What is difference between bex analyser and bex browser

    what is difference between bex analyser and bex browser . please explain what are use of both and what we do in both.

    hi
    Bex Browser
    The Business Explorer Browser (BEx Browser) makes it possible for you to access all document types of the Business Information Warehouse that are assigned to your role or that you have stored in your favorites. You can select and open documents assigned to you in the BEx Browser or store and manage new documents in the BEx Browser.
    Document types that you can work with in the BEx Browser are:
    · BW workbooks
    · Documents that are stored in the Business Document Service (BDS)
    · Links (references to file system, shortcuts)
    · Links to internet sites (URLs)
    · SAP transaction calls.
    · Web applications and Web templates
    · Crystal Reports
    Bex Analyser
    The Business Explorer Analyzer (BEx Analyzer) is the analysis and reporting tool of the Business Explorer that is embedded in Microsoft Excel.
    Features
    You can call up the BEx Query Designer in the BEx Analyzer, in order to define queries. Subsequently, you can analyze the selected InfoProvider data by navigation to the query created in the Query Designer and create different query views of the data. You can add the different query views for a query or for different queries to a work book and save them there. You can save the workbook in your favorites or in your role on the BW Server. You can also save the workbook locally on your computer.
    Beyond that, you can precalculate the workbook and distribute it by e-mail to recipeients or you can export it to the Enterprise Portal and make it accessible to other employees in the company.
    You can start queries in a standard view (with a Standard Web Template set up in Customizing) in the Web browser and forward the URL or continue to navigate on the Web. Similarly, you can export the Web query to MS Excel 2000.
    Overview of the Functional Area of the BEx Analyzer:
    ·        BEx toolbar
    You access the functions of the BEx Analyzer from the BEx toolbar, which takes you to the BEx Open dialog box where you can open existing queries, or to the BEx Query Designer where you can create new queries or change existing queries.
    ·        Evaluating Query Data
    The BEx Analyzer offers convenient functions for evaluating and presenting InfoProvider data interactively. In the BEx Analyzer, you can add queries to workbooks, navigate within them and refresh the data. You can also process the queries further in Microsoft Excel or display them in the Web browser in a default view.
    Navigation of a query allows you, for example, to filter characteristics on a single value, drilldown on all values for a characteristic, regroup characteristics and key figures in the rows and columns of the results area, or hide key figures. Navigation results in different views of the InfoProvider data. In addition, a range of further functions is available which allow you to edit a query interactively (for example, sorting, cumulated output, among others). In addition, you can use the editing functions in Microsoft Excel in order to set up individual format templates, to print results areas, or to create graphics.
    ·        Queries in Workbooks
    Queries are inserted into workbooks so you can display them. When you insert a query, a link is made between the cell areas of the worksheet and the data of the InfoProvider upon which the query is based. A link therefore exists between the Business Explorer and the Business Information Warehouse Server (BW Server).
    When inserting a query into the workbook, a VBA routine is automatically generated in the workbook. You can also connect the Business Explorer with your own VBA programs (Visual Basic for Applications).
    You can create workbook templates, into which you can insert your queries. Workbook templates can contain pre-determined items for the area of the query, formatting settings, logos, VBA macros, and so on.
    ·        Precalculating workbooks
    You can precalculate and distribute workbooks with the BEx Broadcaster, which is a Web application you get to form the BEx toolbar. The system generates MS Excel workbooks with historical data. You determine the time for precalculation yourself: You can have workbooks precalculated at a predefined time or they can be precalculated whenever data in the underlying InfoProvider changes. You can have the precalculated workbooks sent by e-mail or you can export them into the Enterprise Portal, where you can make them available to employees within your company.
    Activities
    To start the BEx Analyzer, choose Start ® Programs ® SAP Front-end Business Information Warehouse ® SAP Business Explorer Analyzer.
    You can also access the BEx Analyzer via SAP Easy Access ® SAP Business Information Warehouse ® SAP Menu ® Business Explorer ® Analyzer or in the Business Explorer Browser using the Business Explorer Analyzer symbol in the menu bar.
    Hope this will solve your issu
    nagarjuna

  • What is difference between report programming and dialog programming?

    hi,
    what is difference between report programming and dialog programming? plz provide some example code
    bye

    ABAP programming
    Basically reports are used to read database and represent the results in lists.
    Reports are collections of processing blocks that the system calls depending on events.
    We can use reports to evaluate data from database tables.
    Reports are stand alone programs and controlled by events.
    A report itself never creates events
    steps in report:
    Processing the selection screen
    Reading the database
    Evaluating the data and creating lists
    Outputting a list.
    1st u write simple logics, after that u can enhance the code as step by step.
    http://venus.imp.mx/hilario/Libros/TeachYrslfAbap4/index.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm
    http://www.sapdev.co.uk/reporting/reportinghome.htm
    Dialog Programming
    Structure of a Dialog Program
    A dialog program consists of the following basic components:
    Screens (dynpros)
    Each dialog in an SAP system is controlled by dynpros. A dynpro (DYnamic PROgram) consists of a screen and its flow logic and controls exactly one dialog step. The flow logic determines which processing takes place before displaying the screen (PBO-Process Before Output) and after receiving the entries the user made on the screen (PAI-Process After Input).
    The screen layout fixed in the Screen Painter determines the positions of input/output fields, text fields, and graphical elements such as radio buttons and checkboxes. In addition, the Menu Painter allows to store menus, icons, pushbuttons, and function keys in one or more GUI statuses. Dynpros and GUI statuses refer to the ABAP/4 program that control the sequence of the dynpros and GUI statuses at runtime.
    ABAP/4 module pool
    Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
    All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.
    Check this link for basics.
    http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
    Check this link for Dialog Programming/Table Control
    http://www.planetsap.com/Tips_and_Tricks.htm#dialog
    Check this SAP Help for Dialog Program doc.
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
    Check this SAP Help link for Subscreens.
    http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbabfe35c111d1829f0000e829fbfe/content.htm
    Check this link for subscreen demo program.
    http://abapcode.blogspot.com/2007/05/demo-program-to-create-subscreen-in.html
    Also check this link too.
    http://abapcode.blogspot.com/2007/06/dialog-programming-faq.html
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/frameset.htm
    http://sap.mis.cmich.edu/sap-abap/abap09/sld004.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9ccf35c111d1829f0000e829fbfe/frameset.htm
    http://abapprogramming.blogspot.com/

  • What is difference between interactive list and interactive reports?

    what is difference between interactive list and interactive reports?

    hi check this..
    interactive report/list means any input(double click or single click or user command ) on the screen will results a new screen with the corresponding fields....this is upto 20 levels only check this..
    report .
    start-of-selection.
    write:/ 'this is the source list'.
    at line-selection .
    if sy-lsind = 1 .
    write:/ ' this is the 1st list'.
    elseif.
    if sy-lsind = 2 .
    write:/ ' this is the 2 list'.
    if sy-lsind = 3 .
    write:/ ' this is the 3 list'.
    if sy-lsind = 4 .
    write:/ ' this is the 4 list'.
    if sy-lsind = 5 .
    write:/ ' this is the 5 list'.
    if sy-lsind = 6 .
    write:/ ' this is the 6 list'.
    if sy-lsind = 7 .
    write:/ ' this is the 7 list'.
    if sy-lsind = 8.
    write:/ ' this is the 8 list'.
    if sy-lsind = 9 .
    write:/ ' this is the 9 list'.
    if sy-lsind = 10 .
    write:/ ' this is the 10 list'.
    endif.
    regards,
    venkat

  • What is difference between Shared ,Exclusive and Exclusive but not commulat

    what is difference between Shared ,Exclusive and Exclusive but not commulative lock modes plese tell me

    Lock objects are used to synchronize access to the same data by more than one program.
    The lock mode controls whether several users can access data records at the same time. The lock mode can be assigned separately for each table in the lock object. When the lock is set, the corresponding lock entry is stored in the lock table of the system for each table.
    There are three types of lock modes
    1.Exclusive
    2.Shared
    3.Exclusive not cummulative
    Exclusive lock: The locked data can only be displayed or edited by a single user. A request for another exclusive lock or for a shared lock is rejected.
    Shared lock: More than one user can access the locked data at the same time in display mode. A request for another shared lock is accepted, even if it comes from another user. An exclusive lock is rejected.
    Exclusive but not cumulative: Exclusive locks can be requested several times from the same transaction and are processed successively. In contrast, exclusive but not cumulative locks can be called only once from the same transaction. All other lock requests are rejected.
    please go through these links:
    http://help.sap.com/saphelp_nw04/helpdata/en/a2/3547360f2ea61fe10000009b38f839/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/af/22ab01dd0b11d1952000a0c929b3c3/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eeb2446011d189700000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eebf446011d189700000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eed9446011d189700000e8322d00/frameset.htm
    briefly :
    You can lock the table or record by using following types of locking:
    1) Exclusive (E) the locked data can only be displayed or modified by single user i.e the owner of the object. Access to other users is denied.
    2) Shared (S) several users can access the same record simultaneously, but only in display mode and except the first one, who has asked for the data in update mode.
    3) Exclusive not cumulating (X) it is similar to exclusive lock. It allows only a single user access. E can be called several times from the same transaction. In contrast, a lock type X can be called only once during the transaction. Any other call for this lock is rejected.
    Activation of Lock Object
    1) When you activate the lock object, the functions are automatically generated. And these are ENQUEUE-EZN and DEQUEUE-EZN. EZN is name of the lock object.
    2) While ENQUEUE is used in program to set the code over the selected data depending upon the lock object arguments. DEQUEUE is used to release the lock.
    Thanks
    Seshu

  • Whats the difference between list and lov ?

    Whats the difference between list and lov ?
    i can do the same things with a list what an lov can do .
    infact a list is more better. cause the list doesnt hold/show a range of values, and only has the items value iteself.
    while the lov can get all the values of items depending on the query.
    like
    select ename, job, sal from emp
    will show all the three items values in lov?

    Also, if you're looking in the US store, the prices are:
    - Airport Express (small, no ac) $99 - Has audio out for speaker connection using Airplay. Can share a USB printer only.
    - Airport Extreme (larger, ac) $199 - No audio out, can share a USB printer or hard drive.
    - Time Capsules (2TB, 3TB at $299, $399) - have ac wireless and a backup hard drive for Time Machine which the other Airports do not have.
    Matt

  • What the difference between u0093Valuate GL Account Open Itemsu0094 and u0093Valuate G/

    hi gurus
    What the difference between “Valuate GL Account Open Items” and “Valuate G/L Account Balances”?
    We found out that when we perform valuate GL account Open items there will be reversal done at the same time whereas when we perform Valuate G/L Account Balances there is NO reversal posting even though we hv entered the reversal posting date and Period.
    Pls advise which one we should perform?

    “Valuate GL Account Open Items” are for open item managed accounts including vendor/customer accounts. The valuation is performed for each (open) line items on key date specified.
    "“Valuate GL Balance" is for account NOT managed on Open Item basis but managed in foreign currency. The period balance of key date in foreign currency is valuated. Reversal document can be created by selecting 'Reverse postings' in "Postings" tab.
    Kyoko

  • What are differences between the target tablespace and the source tablespac

    The IMPDP command create so manay errors. But the EXAMPLE tablespace is transported to the target database successfully. It seems that the transported tablespace is no difference with the source tablespace.
    Why create so many errors?
    How to avoid these errors?
    What are differences between the target tablespace and the source tablespace?
    Is this datapump action really successfull?
    Thw following is the log output:
    [oracle@hostp ~]$ impdp system/oracle dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
    Import: Release 10.2.0.1.0 - Production on Sunday, 28 September, 2008 18:08:31
    Copyright (c) 2003, 2005, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Master table "SYSTEM"."SYS_IMPORT_TABLESPACE_01" successfully loaded/unloaded
    Starting "SYSTEM"."SYS_IMPORT_TABLESPACE_01": system/******** dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
    Processing object type TABLE_EXPORT/TABLE/TABLE
    ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
    CREATE TABLE "OE"."CUSTOMERS" ("CUSTOMER_ID" NUMBER(6,0), "CUST_FIRST_NAME" VARCHAR2(20) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE, "CUST_LAST_NAME" VARCHAR2(20) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE, "CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" , "PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" , "NLS_LANGUAGE" VARCHAR2(3), "NLS_TERRITORY" VARCHAR2(30), "CREDIT_LIMIT" NUMBER(9,2), "CUST_EMAIL" VARCHAR2(30), "ACCOUNT_MGR_ID" NU
    ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
    ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
    CREATE TABLE "IX"."ORDERS_QUEUETABLE" ("Q_NAME" VARCHAR2(30), "MSGID" RAW(16), "CORRID" VARCHAR2(128), "PRIORITY" NUMBER, "STATE" NUMBER, "DELAY" TIMESTAMP (6), "EXPIRATION" NUMBER, "TIME_MANAGER_INFO" TIMESTAMP (6), "LOCAL_ORDER_NO" NUMBER, "CHAIN_NO" NUMBER, "CSCN" NUMBER, "DSCN" NUMBER, "ENQ_TIME" TIMESTAMP (6), "ENQ_UID" VARCHAR2(30), "ENQ_TID" VARCHAR2(30), "DEQ_TIME" TIMESTAMP (6), "DEQ_UID" VARCHAR2(30), "DEQ_
    Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
    . . imported "SH"."CUSTOMERS" 9.850 MB 55500 rows
    . . imported "SH"."SUPPLEMENTARY_DEMOGRAPHICS" 695.9 KB 4500 rows
    . . imported "OE"."PRODUCT_DESCRIPTIONS" 2.379 MB 8640 rows
    . . imported "SH"."SALES":"SALES_Q4_2001" 2.257 MB 69749 rows
    . . imported "SH"."SALES":"SALES_Q1_1999" 2.070 MB 64186 rows
    . . imported "SH"."SALES":"SALES_Q3_2001" 2.129 MB 65769 rows
    . . imported "SH"."SALES":"SALES_Q1_2000" 2.011 MB 62197 rows
    . . imported "SH"."SALES":"SALES_Q1_2001" 1.964 MB 60608 rows
    . . imported "SH"."SALES":"SALES_Q2_2001" 2.050 MB 63292 rows
    . . imported "SH"."SALES":"SALES_Q3_1999" 2.166 MB 67138 rows
    Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."REGIONS" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."REGIONS" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."COUNTRIES" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."COUNTRIES" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."LOCATIONS" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."LOCATIONS" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."DEPARTMENTS" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."DEPARTMENTS" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."JOBS" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."JOBS" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."EMPLOYEES" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."EMPLOYEES" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."JOB_HISTORY" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."JOB_HISTORY" TO "EXAM_03"
    ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
    ORA-39112: Dependent object type INDEX:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type INDEX:"OE"."CUST_LNAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type INDEX:"OE"."CUST_EMAIL_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type INDEX:"PM"."PRINTMEDIA_PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_CREDIT_LIMIT_MAX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_ID_MIN" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"PM"."PRINTMEDIA__PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"IX"."SYS_C005192" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUSTOMERS_PK" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_LNAME_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_EMAIL_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"PM"."PRINTMEDIA_PK" creation failed
    Processing object type TABLE_EXPORT/TABLE/COMMENT
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
    ORA-39112: Dependent object type REF_CONSTRAINT:"OE"."CUSTOMERS_ACCOUNT_MANAGER_FK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39083: Object type REF_CONSTRAINT failed to create with error:
    ORA-00942: table or view does not exist
    Failing sql is:
    ALTER TABLE "OE"."ORDERS" ADD CONSTRAINT "ORDERS_CUSTOMER_ID_FK" FOREIGN KEY ("CUSTOMER_ID") REFERENCES "OE"."CUSTOMERS" ("CUSTOMER_ID") ON DELETE SET NULL ENABLE
    ORA-39112: Dependent object type REF_CONSTRAINT:"PM"."PRINTMEDIA_FK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    Processing object type TABLE_EXPORT/TABLE/TRIGGER
    ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
    ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
    ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
    ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
    Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
    ORA-39112: Dependent object type INDEX:"OE"."CUST_UPPER_NAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_UPPER_NAME_IX" creation failed
    Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
    Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
    ORA-39112: Dependent object type PROCACT_INSTANCE skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
    ORA-01403: no data found
    ORA-01403: no data found
    Failing sql is:
    BEGIN
    SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_SIGNATURE_TABLE('AQ$_ORDERS_QUEUETABLE_G');COMMIT; END;
    Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCDEPOBJ
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_V" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_N" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_R" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_E" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    Job "SYSTEM"."SYS_IMPORT_TABLESPACE_01" completed with 63 error(s) at 18:09:14

    Short of trying to then reverse-engineer the objects that are in the dump file (I believe Data Pump export files contain some XML representations of DDL in addition to various binary bits, making it potentially possible to try to scan the dump file for the object definitions), I would tend to assume that the export didn't include those type definitions.
    Since it looks like you're trying to set up the sample schemas, is there a reason that you wouldn't just run the sample schema setup scripts on the destination database? Why are you using Data Pump in the first place?
    Justin

  • Whats the difference between these two queries ? - for tuning purpose

    Whats the difference between these two queries ?
    I have huge amount of data for each table. its takeing such a long time (>5-6hrs).
    here whice one is fast / do we have any other option there apart from listed here....
    QUERY 1: 
      SELECT  --<< USING INDEX >>
          field1, field2, field3, sum( case when field4 in (1,2) then 1 when field4 in (3,4) then -1 else 0 end)
        FROM
          tab1 inner join tab2 on condition1 inner join tab3 on condition2 inner join tab4 on conditon3
        WHERE
         condition4..10 and
        GROUP BY
          field1, field2,field3
        HAVING
          sum( case when field4 in (1,2) then 1 when field4 in (3,4) then -1 else 0 end) <> 0;
    QUERY 2:
       SELECT  --<< USING INDEX >>
          field1, field2, field3, sum( decode(field4, 1, 1, 2, 1, 3, -1, 4, -1 ,0))
        FROM
          tab1, tab2, tab3, tab4
        WHERE
         condition1 and
         condition2 and
         condition3 and
         condition4..10
        GROUP BY
          field1, field2,field3
        HAVING
          sum( decode(field4, 1, 1, 2, 1, 3, -1, 4, -1 ,0)) <> 0;
    [pre]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    My feeling here is that simply changing join syntax and case vs decode issues is not going to give any significant improvement in performance, and as Tubby points out, there is not a lot to go on. I think you are going to have to investigate things along the line of parallel query and index vs full table scans as well any number of performance tuning methods before you will see any significant gains. I would start with the Performance Manual as a start and then follow that up with the hard yards of query plans and stats.
    Alternatively, you could just set the gofast parameter to TRUE and everything will be all right.
    Andre

  • What is difference between 4.7c BW and R/3 s/w

    what is difference between 4.7c BW and R/3 s/w

    Please refer
    You can find the difference in release notes of each SAP version.
    Here are the links.
    http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
    http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/sapERP6.0+Upgrade
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/transactionsChangedinECC6.0
    Please check the below link for the differences between the two releases..
    http://solutionbrowser.erp.sap.fmpmedia.com/Default.aspx
    Select the source and target versions of release and the solution area and the module...you will get the list of all the differences.
    I hope it will reach your req.
    Regards
    Chandra

  • Whats the difference between oracle9i and oracle10g

    whats the difference between oracle9i and oracle10g?

    794244 wrote:
    whats the difference between oracle9i and oracle10g?About 12...
    SQL> select utl_match.jaro_winkler_similarity('oracle9i','oracle9i') as sameness from dual;
      SAMENESS
           100
    SQL> select utl_match.jaro_winkler_similarity('oracle9i','oracle10g') as sameness from dual;
      SAMENESS
            88
    SQL>

  • Whats the difference between ALL and FIRST  in Multi Inserting

    SQL> Drop Table Sales;
    Table dropped.
    SQL> Drop Table Accounts;
    Table dropped.
    SQL> Drop Table Research;
    Table dropped.
    SQL> Create Table Sales As Select * From Emp;
    Table created.
    SQL> Create Table Accounts As Select * From Emp;
    Table created.
    SQL> Create Table Research As Select * From Emp;
    Table created.
    SQL> Truncate Table Sales;
    Table truncated.
    SQL> Truncate Table Accounts;
    Table truncated.
    SQL> Truncate Table Research;
    Table truncated.
    SQL> Select * From Sales;
    no rows selected
    SQL> Select * From Accounts;
    no rows selected
    SQL> Select * From Research;
    no rows selected
    SQL> Insert All
      2  When Deptno=10 Then
      3  Into Sales (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
      4  When Deptno=20 Then
      5  Into Accounts (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
      6  When Deptno=30 Then
      7  Into Research (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
      8  Select * From Emp
      9  .
    SQL> /
    16 rows created.
    SQL> Select * From Sales;
        EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
         7782 CLARK      MANAGER        7839 09-JUN-81       100                  10
         7839 KING       PRESIDENT           17-NOV-81       100                  10
         7934 MILLER     CLERK          7782 23-JAN-82       100                  10
         7999 ABCDEFGH   JOB            7839 09-FEB-06       100         0        10
    4 rows selected.
    SQL> Select * From Accounts;
        EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
         7901 SMITH      CLERK          7902 17-DEC-80       100                  20
         7566 JONES      MANAGER        7839 02-APR-81       100                  20
         7788 SCOTT      ANALYST        7566 19-APR-87       100                  20
         7876 ADAMS      CLERK          7788 23-MAY-87       100                  20
         7902 FORD       ANALYST        7566 03-DEC-81       100                  20
          123                                                                     20
    6 rows selected.
    SQL> Select * From Research;
        EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
         7499 ALLEN      SALESMAN       7698 20-FEB-81       100       300        30
         7521 WARD       SALESMAN       7698 22-FEB-81       100       500        30
         7654 MARTIN     SALESMAN       7698 28-SEP-81       100      1400        30
         7698 BLAKE      MANAGER        7839 01-MAY-81       100                  30
         7844 TURNER     SALESMAN       7698 08-SEP-81       100         0        30
         7900 JAMES      MANAGER        7698 03-DEC-81       100                  30
    6 rows selected.
    SQL> Truncate Table Sales;
    Table truncated.
    SQL> Truncate Table Accounts;
    Table truncated.
    SQL> Truncate Table Research;
    Table truncated.
    SQL> Insert First
      2  When Deptno=10 Then
      3  Into Sales (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
      4  When Deptno=20 Then
      5  Into Accounts (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
      6  When Deptno=30 Then
      7  Into Research (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
      8  Select * From Emp
      9  /
    16 rows created.
    SQL> Select * From Sales;
        EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
         7782 CLARK      MANAGER        7839 09-JUN-81       100                  10
         7839 KING       PRESIDENT           17-NOV-81       100                  10
         7934 MILLER     CLERK          7782 23-JAN-82       100                  10
         7999 ABCDEFGH   JOB            7839 09-FEB-06       100         0        10
    4 rows selected.
    SQL> Select * From Accounts;
        EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
         7901 SMITH      CLERK          7902 17-DEC-80       100                  20
         7566 JONES      MANAGER        7839 02-APR-81       100                  20
         7788 SCOTT      ANALYST        7566 19-APR-87       100                  20
         7876 ADAMS      CLERK          7788 23-MAY-87       100                  20
         7902 FORD       ANALYST        7566 03-DEC-81       100                  20
          123                                                                     20
    6 rows selected.
    SQL> Select * From Research;
        EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
         7499 ALLEN      SALESMAN       7698 20-FEB-81       100       300        30
         7521 WARD       SALESMAN       7698 22-FEB-81       100       500        30
         7654 MARTIN     SALESMAN       7698 28-SEP-81       100      1400        30
         7698 BLAKE      MANAGER        7839 01-MAY-81       100                  30
         7844 TURNER     SALESMAN       7698 08-SEP-81       100         0        30
         7900 JAMES      MANAGER        7698 03-DEC-81       100                  30
    6 rows selected.Both inserting insert the same records then whats the difference between ALL and FIRST clause in multi insert DML
    Khurram Siddiqui
    [email protected]

    Hello
    From the docs:
    ALL
    If you specify ALL, then Oracle evaluates each WHEN clause regardless of the results of the evaluation of any other WHEN clause. For each WHEN clause whose condition evaluates to true, Oracle executes the corresponding INTO clause list.
    FIRST
    If you specify FIRST, then Oracle evaluates each WHEN clause in the order in which it appears in the statement. For the first WHEN clause that evaluates to true, Oracle executes the corresponding INTO clause and skips subsequent WHEN clauses for the given row.
    ELSE clause
    For a given row, if no WHEN clause evaluates to true:
    * If you have specified an ELSE clause, then Oracle executes the INTO clause list associated with the ELSE clause.
    * If you did not specify an else clause, then Oracle takes no action for that row.
    See Also:
    "Multitable Inserts: Examples"
    Restrictions on Multitable Inserts
    * You can perform multitable inserts only on tables, not on views or materialized views.
    * You cannot perform a multitable insert into a remote table.
    * You cannot specify a table collection expression when performing a multitable insert.
    * In a multitable insert, all of the insert_into_clauses cannot combine to specify more than 999 target columns.
    * Multitable inserts are not parallelized in a Real Application Clusters environment, or if any target table is index organized, or if any target table has a bitmap index defined on it.
    * Plan stability is not supported for multitable insert statements.
    * The subquery of the multitable insert statement cannot use a sequence.
    So given this the following example shows the difference:
    SQL> CREATE TABLE dt_test_insert_base as select rownum id from dba_objects where rownum <=20
      2  /
    Table created.
    SQL> CREATE TABLE dt_test_insert_1 (id number)
      2  /
    Table created.
    SQL> CREATE TABLE dt_test_insert_2 (id number)
      2  /
    Table created.
    SQL>
    SQL> INSERT ALL
      2     WHEN rownum <=15 THEN
      3             INTO dt_test_insert_1 (id)
      4     WHEN rownum >=10 THEN
      5             INTO dt_test_insert_2 (id)
      6  SELECT
      7     ID
      8  FROM
      9     dt_test_insert_base
    10  /
    26 rows created.
    SQL>
    SQL> SELECT * from dt_test_insert_1
      2  /
            ID
             1
             2
             3
             4
             5
             6
             7
             8
             9
            10
            11
            12
            13
            14
            15
    15 rows selected.
    SQL> SELECT * from dt_test_insert_2
      2  /
            ID
            10
            11
            12
            13
            14
            15
            16
            17
            18
            19
            20
    11 rows selected.
    SQL>
    SQL> TRUNCATE TABLE dt_test_insert_1
      2  /
    Table truncated.
    SQL> TRUNCATE TABLE dt_test_insert_2
      2  /
    Table truncated.
    SQL>
    SQL> INSERT FIRST
      2     WHEN rownum <=15 THEN
      3             INTO dt_test_insert_1 (id)
      4     WHEN rownum >=10 THEN --This condition is ignored until the value of id is > 15
      5             INTO dt_test_insert_2 (id)
      6  SELECT
      7     ID
      8  FROM
      9     dt_test_insert_base
    10  /
    20 rows created.
    SQL> SELECT * from dt_test_insert_1
      2  /
            ID
             1
             2
             3
             4
             5
             6
             7
             8
             9
            10
            11
            12
            13
            14
            15
    15 rows selected.
    SQL> SELECT * from dt_test_insert_2
      2  /
            ID
            16
            17
            18
            19
            20HTH
    David

  • Would you please summarize what the difference between tc and alv?

    hi, experts,
      would you please summarize what the difference between table control and alv base on the function and usage practice.
    for example, as i know:
    1.edit
      tc: can edit in the same screen and save.
      alv: pop up a sub screen to let user edit, so this is unconvenient.
    2.functional button
      alv: can have many functional button as default ,eg. sort, summary and so on
      tc:  developers must implements by himself.
    3.color
      alv: can have and change color
      tc:  cann't changed color
    some client may required the data displayed in alv and edit in tc ,such as example BCALV_EDIT_02.
    above are my idea, experts, would you give me some comments on my opinion and summarize what the difference between those two components? i should make it clear in order to consult the UI with my client.hunger for your advice, thanks!
    Message was edited by:
            liu shaochang

    ALV Grid is basically used for display puropse. It is more user friendly. There are arious features ( such as coloring, sorting, saving to a local file, sedning by mail etc. ) These featurs make ALV Grid a very good option to display the data .
    However , the table control is not only used to display data take from the database table, but also you can do operation such as deletion of data from database table, insertion of data into the database table and updation also. Yeah it has not got the various features whihc ALV has.
    So table control and ALV Grid , if you are just using for display purpose, then ALV Grid is a better option due to its layout and attractive features. But if you want to do the database operations other than display, table control can be used.
    As far as execution is concerned, I think ALV Grid is faster.
    ALV grid control is faster when compared to Table control. But the comaprision is Negligible .
    One of the major differences comes in taking of line items - ALV has an advantage over Table Control when it comes to update database from it.Table control only allows maximum of 999 records at a time where as this limitation is not there in ALV.
    Also,a main feature of ALV Grid is that it contains a standard set of functions. These functions extend beyond the functions of a table control.
    These two UI elements require different keyboard navigation, with ALV Grid being more user-friendly.
    An application can display table data in ALV Grid or in a table control. In some applications you can choose between displaying and editing data in either ALV Grid or a table control. If a configurable button () appears in the right upper corner of the table, it is a table control.
    Basically ALV is a way to display the output and Table Control is designed in screen painter through which you can get entries in Table Control, can delete some records etc for further processing and its not use only for Display.
    ALV is Application List viewer:-
    Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.
    In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output.
    TABLE CONTROL:-
    ABAP offers two mechanisms for displaying and using table data in a screen. These mechanisms are table controls and step loops. Table controls and step loops are types of screen tables you can add to a screen in the Screen Painter.

Maybe you are looking for