Cannot execute planning operators Unconstrained and Profit Optimization in SAP2

Hi,
We cannot execute supply planning operators Unconstrained and Profit Optimization with user JSMITH in planning area SAP2, although these jobs were successfully executed by the same user in the past.
Any idea as to what could be the problem?
We are using SOP 3.0.2.1, EPM version 10.0 SP 18 patch 2 build 8873.
Thanks,
Bernard

looks like you are running in batch mode. perhaps the background user for your system is not set up (an operational issue for which you can file a message).
if you run in simulate  mode (using simulate button), does it work? if not perhaps you're current period is not may 2014 and the data set assume this.. (you can change the current period offset similar to: update "SAP_SFND"."sap.sop.sopfnd.catalogue::SOPDM_PLANAREASET" set planoffset = 0 where plset = 'SM1BASESAPMODEL1'

Similar Messages

  • Where and how to enter plan data cost and profit center wise to get data in grr1

    Hi Gurus,
    Appreciate you can tell me where and how to enter plan amount cost center wise for cost elements and profit center wise for revenue elements????
    So that we can get this data in grr1 report.....
    Can we upload this planned data, if yes how??
    Thank you

    Hi..
    If you use classic PCA, refer to Plan Data Transfer - Profit Center Accounting (EC-PCA) - SAP Library.
    If you use new gl pca, refer to Transferring Plan Data from Controlling - General Ledger Accounting (FI-GL) (New) - SAP Library

  • Cannot execute .

    I downloaded Firefox 10.0.2 for Linux, unpacked it, tried launching run-mozilla.sh in console, but saw "Cannot execute ." (with user and root rights). My system - Xubuntu 11.04

    Ok. This script file launched an old version of firefox (4), installed by package manager of Ubuntu.
    I have deleted the old version, and now it launches new version.
    Thank you.

  • Cost Center and Profit Center Planning

    Hi,
    I have one  Co issue.  Pls Suggest me the wiseful solution.
    Cost Center and Profit Center Planning.
    For F-2008 Planning  data they have updated in the month of Aug, 07 for Profit and Loss Items and they have revised the plan data of some cost elements in the month of oct, 2007 (say 5% Increas).  when comparing the cost center report to profit center report, both are not matching.  the reason when i see and reconcile the document nos and values in between cost center and profit center reports  i found out that there are some documents are missing in the profit center report. 
    wherever plan data had revised e.g for cost element Salaries they have updated 100000 Planning cost in the month of Aug, 07.  In the month of Oct, 07 increased 5% i.e.5000. In cost center line items details i found 2 documents for Rs.100000/- and Rs.5000/-  But in Profit Center Line Items i am getting only Rs.5000/- Value Document.
    Note.  As and when KP06 Plan data has been updated Profit Center line items are generating.  It is not necessary to run any programme inorder to transfer Plan Data from cost center to profit center.
    Observations From My Side:-
    I tried to run the transaction code 1ke0. i have selected the cost object is Cost Center, version and had given Cost Center Parameter in development and quality clients and executed the same.By this time already existing data either deleting/ riversing and creating new documents fully except manually changed data in profit center through 7ke1.
    My Question is
    1.Upto what extent it will work.
    2.will it be possible to transfer data from cost center to profit center only missing documents which are available in cost center, without disturbing of existing data in profit center.
    3.suppose if i done this activity, there are some data which was already transferred from other cost objects like internatl orders & wbs elements to Profit Center. will the data get disturbed (deleted/riversed).
    Pls suggest me the wiseful way to solve the

    Hi
    Try This
    BAPI_COSTCENTER_CREATEMULTIPLE
    BAPI_COSTCENTERGROUP_CREATE
    BAPI_PROFITCENTER_CREATE
    BAPI_PROFITCENTERGRP_CREATE.
    Regards,
    V.balaji
    Reward if usefull

  • PP/DS Optimizer u2013 Planning for HALB and FERT in sequence with Optimizer

    We are using PP/DS optimizer to plan the two level BOM items. FERT and HALB planned orders are converted from SNP. ROH products are not planned in APO. PPDS is not used to create or delete orders. Only scheduling is done by optimizer. Only one mode exists in PDS. Setup matrix is used for both HALB and FERT.
    The requirement is to schedule HALB products in time on their own resources in time for multiple FERT orders. The optimizer does not appear to do this consistently. We use the following steps in planning run:
    1.     Stage numbering.
    2.     Schedule orders at the earliest with infinite planning. This is done to ensure there are no blank spaces at the beginning of the planning interval on resources after optimization. The result is all orders starting at the same time with multiple loading on resources.
    3.     Optimization with weightage for makespan and setup time. Key settings are: Forward planning, finite resource loading, pegging relevance, considering inter order relationships. All HALB and FERT resources are selected in this step. (Delays are not important within the Optimization interval and there are no stocks of HALB except when there are time gaps between HALB Orders and FERT orders. HALB order is finished earier than FERT order start.)
    The question is: Is Optimizer capable of scheduling HALB and FERT on their own resources  but at the right iner order timings while optimizing the setup time. Are there any key setting to watch out for in Optimization profile or Strategy profile to enable this?
    If this is not possible, we will have optimize only at one BOM level and then use top down or bottom up heuristics to plan the other level.

    HI TemYogi,
    Assumptions:
    1. One PDS each for HALB & FERT level with one resource
    2. HALB to be scheduled first. Based on HALB schedule, FERT has to be scheduled
    To achieve this
    Maintain "Maximum Lateness of a Receipt"  in Pegging tab in Demand tab in Product master
    in FERT PDS maintain the consumption type of HALB components as continious/ start/end of the the operation
    use the planning direction as backward and reverse in DS strategy profile
    Use schedule mode as Insert operation / insert operation and close gaps until end in DS strategy profile
    Fix all the previous run orders in DS board for HALB and then Schedule all the HALB orders considering u r setups through optimization
    Now run the optimizer for FERT
    Regards
    Sravan maturu
    +91 9392602314

  • How To... Execute Planning Functions and Sequences from MS Office Ribbon

    Dear all,
    I am working with a SAP how to paper, which is called:
    How To... Execute Planning Functions and Sequences from MS Office Ribbon.
    It is working absolutely fine and I am pretty satisfied, but as you probably know "Control the visibility of a button based on the visibility of a related crosstab: the  button just disappears once the related crosstab is not located on the active sheet."
    This means, when I insert different queries in different crosstabs, only one crosstab will have my own created ribbon. Is it also possible to set another specific ribbon with other buttons for another crosstab? Can I change the macro, included in the appendix of the how to paper, regarding this issue?
    Thanks in advance!
    Kind regards
    Dominik Drebinger

    Hey Martin,
    thanks for your reply, but I solved the problem on my own. Unfortunately my colleague did not see that the crosstabs had to be defined differently.
    Like this:
    Label
    Screentip
    Msolmage name
    Crosstab name
    Copy Initial Aligned
    Copy Initial Aligned
    CacheListData
    SAPCrosstab1
    Copy Initial Aligned 
    Copy Initial Aligned
    CacheListData
    SAPCrosstab3
    Copy Initial Aligned
    Copy Initial Aligned
    CacheListData
    SAPCrosstab5
    The macro, provided by the HowTo, is therefore working perfectly fine.
    Thanks though
    Dominik

  • ABAP Runtime Error while executing planning folder

    Hi experts.
    We have a situation where I can access our planning folders but that's not the case for one of our user. She encountered with an ABAP Runtime Error as follow:
    Appreciate if anyone can help me out with this.
    Runtime Error          RAISE_EXCEPTION
    Date and Time          20.04.2007 16:50:23
    ShrtText
    Exception condition "X_MESSAGE" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    A RAISE statement in the program "SAPLRSSBR" raised the exception
    condition "X_MESSAGE".
    Since the exception was not intercepted by a superior program
    in the hierarchy, processing was terminated.
    Short description of exception condition:
    Cancel
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    How to correct the error
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "RAISE_EXCEPTION" C
    "SAPLRSSBR" or "LRSSBRU03"
    "RSSB_AUTHORITY_IOBJVL_CHECK"
    or
    "SAPLRSSBR" "X_MESSAGE"
    or
    "UPB_PM_CUST_START " "X_MESSAGE"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "S53KJ165"
    Network address.......... "10.1.53.165"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C3A11F4C00"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 3
    Short dump setting....... "full"
    Database server.......... "S53KJ170"
    Database type............ "ORACLE"
    Database name............ "BWP"
    Database owner........... "SAPBWP"
    Character set............ "en_US.ISO8859-1"
    SAP kernel............... "640"
    Created on............... "Oct 29 2006 20:42:11"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "155"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16128
    EM....................... 16759712
    Heap..................... 0
    Page..................... 57344
    MM Used.................. 10079624
    MM Free.................. 2487240
    SAP Release.............. "640"
    User and Transaction
    Client.............. 350
    User................ "S51643"
    Language key........ "E"
    Transaction......... "UPSPL "
    Program............. "SAPLRSSBR"
    Screen.............. "SAPLUPB_PM_ALV 1000"
    Screen line......... 2
    Information on where terminated
    The termination occurred in the ABAP program "SAPLRSSBR" in
    "RSSB_AUTHORITY_IOBJVL_CHECK".
    The main program was "UPB_PM_CUST_START ".
    The termination occurred in line 416 of the source code of the (Include)
    program "LRSSBRU03"
    of the source code of program "LRSSBRU03" (when calling the editor 4160).
    Source Code Extract
    Line
    SourceCde
    386
    l_s_range-low  = l_activity.
    387
    APPEND l_s_range TO l_sx_auth_check_detail-range.
    388
    INSERT l_sx_auth_check_detail INTO TABLE <l_sx_auth_check>-auth_check_detail.
    389
    390
    CALL FUNCTION 'RSSB_AUTHORITY_IOBJVL_REDUCED'
    391
    EXPORTING
    392
    i_infocube              = g_sx_iobjvl_check-infocube
    393
    i_uname                 = l_uname
    394
    i_th_hierarchy          = g_sx_iobjvl_check-hierarchy
    395
    i_message               = i_message
    396
    i_activity_force_check  = i_activity_force_check
    397
    CHANGING
    398
    c_tsx_auth_check_detail = <l_sx_auth_check>-auth_check_detail
    399
    c_tx_no_auth            = l_tx_no_auth
    400
    c_ts_auth_tlevel        = e_ts_auth_tlevel
    401
    EXCEPTIONS
    402
    user_not_authorized     = 1
    403
    auth_check_failure      = 2
    404
    auth_check_error        = 3
    405
    inherited_error         = 4
    406
    x_message               = 5.
    407
    IF sy-subrc = 0.
    408
    REFRESH l_tx_no_auth.
    409
      CR 20050826 HW873685 SP29 Part 2/3 begin
    410
      SY-SUBRC = 2 means Auth-Obj missing in users profiles, we need this later
    411
    ELSEIF sy-subrc = 2.
    412
    ao_missing = rs_c_true.
    413
    e_subrc = 2.
    414
      CR 20050826 HW873685 SP29 Part 2/3 end
    415
    ELSEIF sy-subrc = 5.
    >>>>>
    RAISE x_message.
    417
    ELSE.
    418
    e_subrc = 2.
    419
    ENDIF.
    420
    421
      correct the kid now
    422
    LOOP AT l_tx_no_auth INTO l_sx_no_auth.
    423
    l_sx_no_auth-kid = <l_sx_auth_check>-kid.
    424
    APPEND l_sx_no_auth TO  e_tx_no_auth.
    425
    ENDLOOP.
    426
    427
    ENDLOOP.
    428
    429
    End LOOP: Check all SUBNR (FEMS)
    430
    431
    432
    CR 20050826 HW873685 SP29 Part 3/3 begin
    433
    If an Auth-Obj. is missing, no SUBNR can be authorized. Due to OLAP-logic
    434
    this means empty no_auth table
    435
    IF ao_missing = rs_c_true.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    5
    SY-INDEX
    1
    SY-TABIX
    0
    SY-DBCNT
    0
    SY-FDPOS
    1
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    210
    SY-UCOMM
    SELECT
    SY-TITLE
    Execute All Cost Element
    SY-MSGTY
    E
    SY-MSGID
    R7
    SY-MSGNO
    057
    SY-MSGV1
    0CO_AREA
    SY-MSGV2
    A
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    40 FUNCTION     SAPLRSSBR                           LRSSBRU03                             416
    RSSB_AUTHORITY_IOBJVL_CHECK
    39 FORM         SAPLRSDRC                           LRSDRCF15                             113
    AUTHORITY_CHECK
    38 FORM         SAPLRSDRC                           LRSDRCF27                              57
    BASIC_QUERY_DATA_GET_ROLAP
    37 FUNCTION     SAPLRSDRC                           LRSDRCU05                              44
    RSDRC_BASIC_QUERY_DATA_GET
    36 FUNCTION     SAPLRSDRC                           LRSDRCU15                             189
    RSDRC_BASIC_CUBE_DATA_GET
    35 FORM         SAPLRSDRC                           LRSDRCF25                             373
    DATA_GET
    34 FUNCTION     SAPLRSDRC                           LRSDRCU02                             249
    RSDRC_CUBE_DATA_GET
    33 FUNCTION     SAPLRSDRI                           LRSDRIU01                             352
    RSDRI_INFOPROV_READ
    32 FORM         /1SEM/UPCBW_350TMWPA01              UPC_BWINTERFC__FIX                    174
    DATA_READ
    31 FUNCTION     SAPLUPCBW                           LUPCBWU06                              56
    UPC_BW_DATA_READ
    30 FUNCTION     SAPLUPC1                            LUPC1U06                               67
    UPC_DATA_READ
    29 METHOD       /1SEM/CL_DATA_350TMWPA01======CP    UPC_DATA_READ_DB                       25
    /1SEM/CL_DATA_350TMWPA01=>IF_SEM_DATA_INTERNAL~READ_DB
    28 METHOD       /1SEM/CL_BUFFER_350TMWPA01====CP    UPC_BUFFER_GET                        167
    /1SEM/CL_BUFFER_350TMWPA01=>IF_SEM_BUFFER~GET
    27 METHOD       /1SEM/CL_BUFFER_350TMWPA01====CP    UPC_BUFFER_READ                         5
    /1SEM/CL_BUFFER_350TMWPA01=>IF_SEM_BUFFER~READ
    26 METHOD       /1SEM/CL_DATA_350TMWPA01======CP    UPC_DATA_READ                          46
    /1SEM/CL_DATA_350TMWPA01=>IF_SEM_DATA~READ
    25 FORM         45AJEHYBGH37F61DTX80Q9ZFP           UPP_PLAN                              395
    READ_TRANSACTION_DATA
    24 FORM         45AJEHYBGH37F61DTX80Q9ZFP           UPP_PLAN                              561
    GET_DATA
    23 FORM         45AJEHYBGH37F61DTX80Q9ZFP           UPP_PLAN                              800
    EC500_SELECT_DATABASE
    22 FORM         SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELF97                     575
    SELECT_DATABASE
    21 FORM         SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELF97                     464
    SELECT_AND_FIND_HEADER_COMBI
    20 FORM         SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELF97                     217
    LOGICAL_SCREEN_FILL_HEADER
    19 FORM         SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELF97                      60
    LOGICAL_SCREEN_FILL
    18 FUNCTION     SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELU01                     114
    UPP_PP_KERNEL_CONSTRUCTOR
    17 METHOD       CL_UPB_PL_ALV=================CP    CL_UPB_PL_ALV=================CM01E   176
    CL_UPB_PL_ALV=>CONSTRUCTOR
    16 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF01                        623
    OUTPUT_CREATE
    15 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF01                        202
    OUTPUT_INIT
    14 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF01                       1062
    OUTPUT_PROCESS
    13 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF01                       1225
    OUTPUT_SWITCH_TO_LAYOUT
    12 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF05                        748
    INIT_CONTROLS
    11 MODULE (PBO) SAPLUPB_PM_ALV                      LUPB_PM_ALVO01                         13
    STATUS
    10 FUNCTION     SAPLUPB_PM_ALV                      LUPB_PM_ALVU01                         24
    UPB_PM_ALV_START
    9 METHOD       CL_UPB_PM_APPLC===============CP    CL_UPB_PM_APPLC===============CM00A    88
    CL_UPB_PM_APPLC=>EXECUTE_PM
    8 METHOD       CL_UPB_PM_ADMIN===============CP    CL_UPB_PM_ADMIN===============CM00L    76
    CL_UPB_PM_ADMIN=>PAI_ONE_NODE
    7 METHOD       CL_UPB_PM_ADMIN===============CP    CL_UPB_PM_ADMIN===============CM00L    23
    CL_UPB_PM_ADMIN=>PAI_ONE_NODE
    6 METHOD       CL_UPB_PM_ADMIN===============CP    CL_UPB_PM_ADMIN===============CM003   121
    CL_UPB_PM_ADMIN=>PAI
    5 FORM         SAPLUPB_PM                          LUPB_PMF04                             80
    USER_COMMAND_0210
    4 MODULE (PAI) SAPLUPB_PM                          LUPB_PMI04                             11
    USER_COMMAND_0210
    3 FUNCTION     SAPLUPB_PM                          LUPB_PMU22                             86
    UPB_PM_MAIN
    2 FORM         UPB_PM_CUST_START                   UPB_PM_START_ADMIN                    251
    PM_START
    1 EVENT        UPB_PM_CUST_START                   UPB_PM_START_ADMIN                     14
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.      40 Ty.          FUNCTION
    Name  RSSB_AUTHORITY_IOBJVL_CHECK
    I_ACTIVITY
    03
    33
    03
    I_ACTIVITY_FORCE_CHECK
    2
    0
    I_MESSAGE
    X
    5
    8
    I_SX_IOBJVL_CHECK
    ZCTMWMA05                                                                                ####
    5454544332222222222222222222222222222222222222222222222222222222222222222222222222222222220000
    A34D7D1050000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    I_UNAME
    S51643
    533333222222
    351643000000
    E_SUBRC
    0
    0000
    0000
    E_TS_AUTH_TLEVEL
    Table[initial]
    E_TX_NO_AUTH
    Table[initial]
    RSSB_C_AUTH_KEYFIGURE
    1KYFNM
    3454442222
    1B96ED0000
    SY-REPID
    SAPLRSSBR
    5454555452222222222222222222222222222222
    310C233220000000000000000000000000000000
    SYST-REPID
    SAPLRSSBR
    5454555452222222222222222222222222222222
    310C233220000000000000000000000000000000
    %_SPACE
    2
    0
    RS_C_RANGE_SIGN
    IE
    44
    95
    SY-SUBRC
    5
    0000
    0005
    L_TX_NO_AUTH
    Table[initial]
    SY-XFORM
    CONVERSION_EXIT
    444545544454545222222222222222
    3FE65239FEF5894000000000000000
    SYST
    0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1. ###################################################à##############
    0000000000000000000000000002000000000000000000000000000000000000000000000000000E00000000000000
    0001000000000000000000000000000000000000000000010001000000010000000000000000000000000000000000
    L_SX_NO_AUTH
    ############ÿÿÿÿ
    000000000000FFFF
    000000000000FFFF
    L_SX_NO_AUTH-KID
    Table[initial]
    <L_SX_AUTH_CHECK>-KID
    Table IT_33029[1x4]
    FUNCTION-POOL=RSSBRDATA=G_SX_IOBJVL_CHECK-AUTH_CHECK[1]-KID
    Table reference: 2052
    TABH+  0(20) = 07000000908D2FD0000000000000000000000000
    TABH+ 20(20) = 00000804000081050000000100000004FFFFFFFF
    TABH+ 40(16) = 040002F1000003480001432821000000
    store        = 0x07000000908D2FD0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 2052  (0x00000804)
    label        = 33029 (0x00008105)
    fill         = 1     (0x00000001)
    leng         = 4     (0x00000004)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000003
    occu         = 1     (0x00000001)
    access       = 2     (ItAccessSorted)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 1     (ItUnique)
    keyKind      = 2     (table_line)
    cmpMode      = 5     (cmpSingle)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000908E0CC8
    pghook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    refCount     = 1     (0x00000001)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 1     (0x00000001)
    lineAlloc    = 1     (0x00000001)
    store_id     = 6998  (0x00001B56)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    No.      39 Ty.          FORM
    Name  AUTHORITY_CHECK
    I_TH_SFC
    Table IT_32090[14x128]
    FUNCTION=RSDRC_BASIC_CUBE_DATA_GETDATA=L_TH_SFC
    Table reference: 1757
    TABH+  0(20) = 070000009052D8F8070000009081372800000000
    TABH+ 20(20) = 000006DD00007D5A0000000E00000080FFFFFFFF
    TABH+ 40(16) = 040002DB000017C80010839401000000
    store        = 0x070000009052D8F8
    ext1         = 0x0700000090813728
    shmId        = 0     (0x00000000)
    id           = 1757  (0x000006DD)
    label        = 32090 (0x00007D5A)
    fill         = 14    (0x0000000E)
    leng         = 128   (0x00000080)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000099
    occu         = 16    (0x00000010)
    access       = 4     (ItAccessHashed)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 1     (ItUnique)
    keyKind      = 3     (user defined)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000090811F18
    pghook       = 0x0000000000000000
    idxPtr       = 0x070000009052D950
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 6872  (0x00001AD8)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0700000090813588
    hsdir        = 0x0000000000000000
    ext2         = 0x0000000000000000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    CL_RSO_REPOSITORY=>P_C_BAL_LOG_SUBOBJEC_INST
    SY-REPID
    SAPLRSDRC
    5454554542222222222222222222222222222222
    310C234230000000000000000000000000000000
    L_S_RANGE-LOW
    1ROWCOUNT
    354544545222222222222222222222222222222222222222222222222222
    12F73F5E4000000000000000000000000000000000000000000000000000
    <L_S_SFK>-KYFNM
    1ROWCOUNT
    354544545222222222222222222222
    12F73F5E4000000000000000000000
    RSDRC_C_QUERYMODE-CUMULATIVE
    C
    4
    3
    S_S_COB_PRO
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_SX_SELDR-RANGE+8(8)
    Table IT_32110[2x136]
    FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_SX_SELDR
    Table reference: 1902
    TABH+  0(20) = 0700000090813D10000000000000000000000000
    TABH+ 20(20) = 0000076E00007D6E0000000200000088FFFFFFFF
    TABH+ 40(16) = 040002DB00001AA00010254421000000
    store        = 0x0700000090813D10
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 1902  (0x0000076E)
    label        = 32110 (0x00007D6E)
    fill         = 2     (0x00000002)
    leng         = 136   (0x00000088)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000112
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 2     (table_line)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000908800F8
    pghook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    refCount     = 1     (0x00000001)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 6876  (0x00001ADC)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    L_S_RANGE
    IEQ1ROWCOUNT
    4453545445452222222222222222222222222222222222222222222222222222222222222222222222222222222222
    95112F73F5E40000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_TSX_SELDR
    Table IT_32094[13x120]
    FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_TSX_SELDR
    Table reference: 1870
    TABH+  0(20) = 0700000090813AE007000000908DF36800000000
    TABH+ 20(20) = 0000074E00007D5E0000000D00000078FFFFFFFF
    TABH+ 40(16) = 040002DB000018A8000C4B9C01000000
    store        = 0x0700000090813AE0
    ext1         = 0x07000000908DF368
    shmId        = 0     (0x00000000)
    id           = 1870  (0x0000074E)
    label        = 32094 (0x00007D5E)
    fill         = 13    (0x0000000D)
    leng         = 120   (0x00000078)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000103
    occu         = 12    (0x0000000C)
    access       = 2     (ItAccessSorted)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 1     (ItUnique)
    keyKind      = 3     (user defined)
    cmpMode      = 3     (cmpSingleMcmpU)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x070000009087FB40
    pghook       = 0x0700000090813D68
    idxPtr       = 0x0700000090813DA0
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 36    (0x00000024)
    lineAlloc    = 36    (0x00000024)
    store_id     = 6875  (0x00001ADB)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x07000000908DED00
    hsdir        = 0x0000000000000000
    ext2         = 0x0000000000000000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    L_SX_SELDR
    00001KYFNM                          ########300   0     ####ÿÿÿÿ####  0 ########        ####ÿÿ
    333334544422222222222222222222222222000000003332223222220000FFFF0000223200000000222222220000FF
    00001B96ED00000000000000000000000000000000003000000000000000FFFF0000000000000000000000000000FF
    G_RUNNING
    0
    0000
    0000
    L_BASICCUBE
    ZCTMWMA05
    545454433222222222222222222222
    A34D7D105000000000000000000000
    L_TH_FREE
    Table IT_32093[6x30]
    FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_TH_FREE
    Table reference: 1763
    TABH+  0(20) = 0700000090813760000000000000000000000000
    TABH+ 20(20) = 000006E300007D5D000000060000001EFFFFFFFF
    TABH+ 40(16) = 040002DB00001B800010831401000000
    store        = 0x0700000090813760
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 1763  (0x000006E3)
    label        = 32093 (0x00007D5D)
    fill         = 6     (0x00000006)
    leng         = 30    (0x0000001E)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000116
    occu         = 16    (0x00000010)
    access       = 4     (ItAccessHashed)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 1     (ItUnique)
    keyKind      = 2     (table_line)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000908137B8
    pghook       = 0x0000000000000000
    idxPtr       = 0x07000000908139B0
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 6874  (0x00001ADA)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    SYST-REPID
    SAPLRSDRC
    5454554542222222222222222222222222222222
    310C234230000000000000000000000000000000
    L_SX_IOBJVL_CHECK
    ZCTMWMA05                                                                                ####
    5454544332222222222222222222222222222222222222222222222222222222222222222222222222222222220000
    A34D7D1050000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_ACTIVITY
    03
    33
    03
    SY-UNAME
    S51643
    533333222222
    351643000000
    S_MULTICUBE
    222222222222222222222222222222
    000000000000000000000000000000
    E_SUBRC
    0
    0000
    0000
    %_VIASELSCR
    0
    4
    S_CHANM
    222222222222222222222222222222
    000000000000000000000000000000
    I_RAISE_EXCEPTION
    X
    5
    8
    RS_C_TRUE
    X
    5
    8
    SCREEN
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.      38 Ty.          FORM
    Name  BASIC_QUERY_DATA_GET_ROLAP
    E_T_DATA
    Table[initial]
    E_END_OF_DATA
    2
    0
    C_FIRST_CALL
    X
    5
    8
    S_S_QPARAM
    XX 0 ##ÿÿÿÿ####DB-VIEW                                               R ###dABAP-TABLE
    25523200FFFF0000442544522222222222222222222222222222222222222222222222520006444525444422222222
    08800000FFFF000042D6957000000000000000000000000000000000000000000000002000041210D412C500000000
    C_S_QPARAM-AUTHORITY_CHECK
    R
    5
    2
    RSDRC_C_AUTHCHK-NONE
    2
    0
    RSJOBINFO
    00000000000000                                  ####
    222222222222222222222222222222223333333333333322222222222222222222222222222222220000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RSD_C_DPANM
    0REQUID                       0CHNGID                       0RECORDTP                     0IOB
    3545544222222222222222222222223444444222222222222222222222223544454552222222222222222222223444
    025159400000000000000000000000038E794000000000000000000000000253F244000000000000000000000009F2
    SPACE
    2
    0
    I_BASICCUBE
    ZCTMWMA05
    545454433222222222222222222222
    A34D7D105000000000000000000000
    I_TH_SFC
    Table IT_32090[14x128]
    I_TH_SFK
    Table IT_32091[2x128]
    FUNCTION=RSDRC_BASIC_CUBE_DATA_GETDATA=L_TH_SFK
    Table reference: 1767
    TABH+  0(20) = 0700000090887AC00700000090813CD800000000
    TABH+ 20(20) = 000006E700007D5B0000000200000080FFFFFFFF
    TABH+ 40(16) = 040002DB000018380010839421000000
    store        = 0x0700000090887AC0
    ext1         = 0x0700000090813CD8
    shmId        = 0     (0x00000000)
    id           = 1767  (0x000006E7)
    label        = 32091 (0x00007D5B)
    fill         = 2     (0x00000002)
    leng         = 128   (0x00000080)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000101
    occu         = 16    (0x00000010)
    access       = 4     (ItAccessHashed)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 1     (ItUnique)
    keyKind      = 3     (user defined)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000090884C90
    pghook       = 0x0000000000000000
    idxPtr       = 0x0700000090827A98
    refCount     = 1     (0x00000001)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 6857  (0x00001AC9)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0700000090813B38
    hsdir        = 0x0000000000000000

    Have you check or trace Authorization??
    In DUMP:
    Information on where terminated
    The termination occurred in the ABAP program "SAPLRSSBR" in
    "RSSB_AUTHORITY_IOBJVL_CHECK".
    The main program was "UPB_PM_CUST_START ".

  • Macro Error while executing planning functions or saving data

    Dear All,
    I am getting following error in BEx Analyzer while executing planning function or pressing a save button.
    Note: Excel is 2007 version.
    Cannot run the macro "XXXXXX.xlsx". The macro may not be available in this workbook or all macros may be disabled.
    I changed the settings in Macro Settings (Office Button -> Excel Options -> Trust Center -> Trust Center Settings-> Macro Settings) eventhough it is showing that above message.
    selected ->
    Enalble all macros
    Trust access to VBA project object model.
    If anybody faced this issue kindly reply to this.
    Best Regards,
    SG

    Hello everybody,
    i am facing exactlythe same issue! I am currently running GUI Patch Level 14 and BI Add on Patch Level 10.
    I have also adjusted all necessary settings in Excel Options like Activate all Macros and Trust VBA Coding.
    Does anybody have another Solution.
    As mentioned before Gui Patch 13 and BI Add On Patch 10 obviously arent the solutiuon.
    Best regards
    Janos

  • Account Recievables Extractor and Profit Center

    Hi Gurus,
    I have a requirement of creating an Aging report ( which i am planning will be based on AR DataSource , 0fi_ar_4).
    Now , i have a requirement to show the Profit Center data in this report.
    I am not sure how to go ahead with this. If anybody has any suggestions please pass it on. 
    Regards,
    Dennis

    Dennis we are going to need some more info on this
    Have you got ECC6 segment ledgers set up for AR and does those post the AR side of the posting to the individual profit centres
    IF you are not using segment ledgers then because of the way FI documents are posted you CANNOT add profit centre to the report
    This is the reason why
    Example FI journal
    dr Customer  117.50
    cr VAT        17.50 default profit centre
    cr revenue    50.00 profit centre A
    cr revenue    50.00 profit centre B
    Now all you have in the AR4 extractor is the 117.50
    The way R3 handles this is that you have a special job which posts via 1KEK or 1KES (I forget which) at month end into the PCA ledger the net balance but not aged per profit centre for the AR sub ledger
    (this month end job is one of the reasons that PCA is being replaced by segment ledgers in ECC6 - 30 days is too late to produce a "segmented" balance sheet as per the IAS 14 and SoX regulations) anyway....
    Unless your process says - there is a 1:1 mapping between each debtor posting and a revenue posting and that revenue posting cannot to be more than 1 profit centre (HIGHLY unlikely)..
    then unfortunately you cannot produce the report
    Somebody has seriously messed up the FICO config andd esign if they request this at the end of the project and haven't designed segment ledgers to handle this...
    (you could have a look at the 0EC_PCA_1 extractors for the PRC4 activity type for the month end postings - but i seriously dount whether the month end PCA jobs are posting document by document - 99% of the time they post by total customer balance and that is not aged)
    Sorry!
    (note: I have had a similar requirement in one of my past projects - the way I did it was to allocate a customer to a "profit centre" - this I did by utisling one of the user defined fields on the customer master and allocating that customer to that "grouping" - ie not physically a profit centre but some sort of grouping that resembled a profit centre - this of course can only happen if logically you can do this irrsptive of the revenue postings to other "profit centres")

  • Cost center and profit center in the same report

    I am working on creating a report using report painter/writer. my question is, will it be possible to create a report with cost center group in one column and profit center group in another column and the rows with GL account groups.
    I know that GLPCT table dosent have the field KOSTL(cost center) in it. The library I am using is from GLPCT table. But when I checked the characteristics of the library that I am using, it has KOSTL field in it. So I checked that field on and tried to use it in the report. But when I execute the report, an error pops up saying "Characteristic KOSTL cannot be combined with the key figures".
    Can someone explain what exactly that error means. and if there is a possible way of using both P.Ctr and C.Ctr in two different colums in the same report.

    I am asked to create a report which has information of both profit centers and cost centers. some of the fields on columns are cost centers and others are profit centers. This report is basically a P&L summary report for various divisions.
    Infact, when I use one basic key figure for cost center and other for profit center and execute the report, it is working!!!!....Is it ok to use two different key figures on two different columns? i dont understand where it is picking the values from..cos cost centers are not present in GLPCT table.

  • Can we take Balance sheet and profit & Loss account as per plant & Sales

    Hi Team,
    Can we take Balance sheet and profit & Loss account as per plant wise & sales office wise also.
    Regards
    JKM

    hi jkm
    Hi
    This can solve your issue could be helpful to you.
    Go to this menu path for report painter
    Accounting - Financial Accounting -Special Purpose Ledger - Tools - Report Painter - Report Writer - Report Group - Display
    T code GR53, GR55
    Enter the report group you want for b/s and p/l statement and choose execute and give the report group again and choose execute.
    After that give the year, period from to, company code, fiscal year, ledger and plan version 01 and choose execute
    Choose in front of the item Production Variances. The system displays the account to which the line items were posted. Material consumption is posted to account OEM Products Consumed.
    To call up detailed data, double-click on account
    In the dialog box, choose Actual Line Items for Table GLFUNCT, and then choose
    To display the original document, simply double-click on it to call up the detailed data. In this case, the original document is a Materials Management document.
    You document is listed under the FI-SL document number that you noted in the step Display Goods Issue Document. Select the Doc. info tab and simulate .
    Select one of the items relevant for material consumption by double-clicking it. This should be item 002, 004, or 006.
    Choose enter go back and cost of sales appear now switch to your first session.
    kind regards
    Arman
    sap fico

  • Re: Full Optimize and Lite Optimize Disabled

    Hi,
    We have an BPC App.
    What we need now is that for a particular group of users to have no access to run Full Optimize or Lite Optimize rights to trigger it.
    Please can any one advice how to disable this functionality or un authorize this for particular set of users so that they cannot execute any optimization.
    Regards.

    Hi,
    Follow below steps:
    1. Create a Team and assign users those should have an access for Full and light optimization
    2. Goto  Manage data>Maintain data management>Manage Packages
        -->Select the team which you created in step 1
         -->Select add package
        --> Choosee process chain as /CPMB/LIGHT_OPTIMIZE
        --> Give package name and description
        --> Select Taks type as User Package
        -->Click Save
    3. Create one more package for Full Optimization as expalined in step 2 under same team
    Now users who are related to this new team can able to run both Full and light optimizations provided Execute task assigned under task profile.
    By following above steps you can assign many package to team and can modify team access from Manage Team user package access  if you need.
    Hope it helps..
    Regards,
    Raju

  • Differece between SNP Optimizer and Deployment Optimizer

    Hi,
    Can anyone please list down the difference in the planning method for a deployment optimizer and SNP Optimizer?
    Thanks & Regards,
    Sanjog Mishrikotkar

    Hi Sanjog,
    First of all if we understand the difference between SNP Heuristic Planning run which finds the 'Source' of Supply with dates and quantities and Deployment Planning run which CONFIRMs the Supply .... then it is easy to understand the difference between SNP & Deployment Optimizer.
    The Optimizer as you know Optimizes based on Costs and Objectively tries to MINIMIZE it.  Therefore while the SNP Optimizer finds the most cost effective way of finding the Source of Supply with dates and quantities, identifying where in SC it is better to Store or move the Product,  while the Deployment Optimizer generates the Best way to CONFIRM whether the Supply can ACTUALLY be done for the next few days.  Deployment precedes the TLB Run which after confirmation we put the Quantities on a Transport Load to build Orders for Execution (Shipping).
    Both are Cost based & use the Same Costs Information ... however one Plans and the Other Confirms.  During Deployment Optimization run, the Optimizer may decide to confirm the supply from a different source than what the SNP Optimizer planned based on the Available to Deploy Stock Quanties and the Cost of Confirming the Supply.  The Deployment Optimizer will apply Fairshare & Push/Pull Rules and looks at the Push and Pull Deployment Horizons which SNP Optimizer cannot.  The Difference is also in Planning Time Range.  You plan SNP Supply for mid to long term time range.  The Deployment looks at Confirming the supply in the next few days from TODAY. 
    So in short first understand the Difference between a SNP Heuristic and Deployment Heuristic and apply the same principle to a cost based optimization. This should tell you the difference between the two.
    Try read this ...  First para on Deployment Optimizer ...
    http://help.sap.com/saphelp_scm50/helpdata/en/1c/4d7a375f0dbc7fe10000009b38f8cf/frameset.htm
    Read the First Paragragraph as well as 'Distribution based on Lowest Costs' section
    Hope you find this answer usefull.  Reward Points if it is.
    Regards,
    Ambrish Mathur

  • Differences listed between ASCP Optimization and Inventory Optimization ?

    Does anyone has a listed readymade document listing the differences between ASCP optimization and Inventory optimization modules.
    thx for your help.
    thx and rgds,
    Pankaj

    Hi,
    As explained IO will recommend time phased Safety stocks it also provides various constraint option, we can make use of it as per our requirement.
    In ASCP, following optimization are available:
    1. Maximize inventory turns
    2. Maximize plan profit
    3. Maximize on-time delivery
    If you want to use the same optmization in IO, we can fulfill the requirement by available IO constraints say max on-time delivery thro enforce service level constraint.
    Hope it will help u.
    Tks
    M J

  • Sql execute plan

    create table m_tables nologging
    as select * from dba_all_tables
    create table m_objects nologging
    as select * from dba_objects
    analyze table m_objects compute statistics
    analyze table m_tables compute statistics
    select /*+ordered use_nl(t,o)*/*
    from m_tables t,
    m_objects o
    where o.owner=t.owner
    and o.object_name=t.table_name
    and o.object_type='TABLE'
    and t.owner='SYSTEM'
    Plan hash value: 4144020635
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
    | 0 | SELECT STATEMENT | | 64 | 17984 | 16285 (2)| 00:03:16 |
    | 1 | NESTED LOOPS | | 64 | 17984 | 16285 (2)| 00:03:16 |
    |* 2 | TABLE ACCESS FULL| M_TABLES | 104 | 20280 | 14 (0)| 00:00:01 |
    |* 3 | TABLE ACCESS FULL| M_OBJECTS | 1 | 86 | 156 (1)| 00:00:02 |
    Predicate Information (identified by operation id):
    2 - filter("T"."OWNER"='SYSTEM')
    3 - filter("O"."OBJECT_TYPE"='TABLE' AND "O"."OWNER"='SYSTEM' AND
    "O"."OBJECT_NAME"="T"."TABLE_NAME")
    select /*+use_nl(t,o)*/*
    from m_tables t,
    m_objects o
    where o.owner=t.owner
    and o.object_name=t.table_name
    and o.object_type='TABLE'
    and t.owner='SYSTEM'
    Plan hash value: 4245804632
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
    | 0 | SELECT STATEMENT | | 64 | 17984 | 934 (1)| 00:00:12 |
    | 1 | NESTED LOOPS | | 64 | 17984 | 934 (1)| 00:00:12 |
    |* 2 | TABLE ACCESS FULL| M_OBJECTS | 64 | 5504 | 158 (2)| 00:00:02 |
    |* 3 | TABLE ACCESS FULL| M_TABLES | 1 | 195 | 12 (0)| 00:00:01 |
    Predicate Information (identified by operation id):
    2 - filter("O"."OBJECT_TYPE"='TABLE' AND "O"."OWNER"='SYSTEM')
    3 - filter("T"."OWNER"='SYSTEM' AND
    "O"."OBJECT_NAME"="T"."TABLE_NAME")
    I am confusing which the driving table should be:m_tables t?m_objects? are the two pathes executed from above to blow?

    user649343 wrote:
    create table m_tables nologging
    as select * from dba_all_tables
    create table m_objects nologging
    as select * from dba_objects
    analyze table m_objects compute statistics
    analyze table m_tables compute statistics
    select /*+ordered use_nl(t,o)*/*
    from m_tables t,
    m_objects o
    where o.owner=t.owner
    and o.object_name=t.table_name
    and o.object_type='TABLE'
    and t.owner='SYSTEM'
    Plan hash value: 4144020635
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
    | 0 | SELECT STATEMENT | | 64 | 17984 | 16285 (2)| 00:03:16 |
    | 1 | NESTED LOOPS | | 64 | 17984 | 16285 (2)| 00:03:16 |
    |* 2 | TABLE ACCESS FULL| M_TABLES | 104 | 20280 | 14 (0)| 00:00:01 |
    |* 3 | TABLE ACCESS FULL| M_OBJECTS | 1 | 86 | 156 (1)| 00:00:02 |
    Predicate Information (identified by operation id):
    2 - filter("T"."OWNER"='SYSTEM')
    3 - filter("O"."OBJECT_TYPE"='TABLE' AND "O"."OWNER"='SYSTEM' AND
    "O"."OBJECT_NAME"="T"."TABLE_NAME")
    select /*+use_nl(t,o)*/*
    from m_tables t,
    m_objects o
    where o.owner=t.owner
    and o.object_name=t.table_name
    and o.object_type='TABLE'
    and t.owner='SYSTEM'
    Plan hash value: 4245804632
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
    | 0 | SELECT STATEMENT | | 64 | 17984 | 934 (1)| 00:00:12 |
    | 1 | NESTED LOOPS | | 64 | 17984 | 934 (1)| 00:00:12 |
    |* 2 | TABLE ACCESS FULL| M_OBJECTS | 64 | 5504 | 158 (2)| 00:00:02 |
    |* 3 | TABLE ACCESS FULL| M_TABLES | 1 | 195 | 12 (0)| 00:00:01 |
    Predicate Information (identified by operation id):
    2 - filter("O"."OBJECT_TYPE"='TABLE' AND "O"."OWNER"='SYSTEM')
    3 - filter("T"."OWNER"='SYSTEM' AND
    "O"."OBJECT_NAME"="T"."TABLE_NAME")
    I am confusing which the driving table should be:m_tables t?m_objects? are the two pathes executed from above to blow?optimizer behavior is version specific
    do as below so we can know complete Oracle version & OS name.
    Post via COPY & PASTE complete results of
    SELECT * from v$version;

Maybe you are looking for