Planning of HALB on correct PDS

Hello,
I have requirement where we have more than one production versions for FERT and HALB. Say there are three production versions for FERT and three for HALB. So there are 3 PDS for FERT and HALB in APO respectively.
Users decide upon which source of supply for the FERT. After that heuristic is run for HALB(STANDARD LOT) and orders are genearted for the HALB. Now the requirement is that if "A" source of supply is used for FERT then "A" source of supply should be picked for HALB. If "C" source of supply is selected for FERT then "C" source of supply should be picked for HALB and so on.
In short if FERT is planned on line A then HALB should also be planned on line A.
But the heuristic is planning HALB based on PDS priority and everytime it is creating orders on the same source of supply irrespective of which source of supply is selected for FERT.
Thanks,
Rajesh Jain

Hi Rajesh,
As this is the standard functionality in heuristics which is
expected, I suggest you try with the following ways (but
not sure how extend it works for your scenario)
1) Try through alternate sequence
2) Try assigning same priority for both HALB and FERT
3) Try maintaining the offset (start-start) indicator
4) Try badi /SAPAPO/CURTO_CREATE
Regards
R. Senthil Mareeswaran.

Similar Messages

  • 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

  • Creation of SNP planned order based on PDS

    Hi,
    I'm a APO developer and I have the following problem:
    I would like to create a SNP planned order based on a PDS (like e. g. in the planning book when you input a number into a cell in the "Production (Planned)" line).
    Up to now I've only managed to create such an order without using the PDS.
    Can you name me a function module which allowes me to do that?
    Thanks in advance.

    Hi,
    I've now managed to create this kind of order.
    I set a breakpoint at the function module /SAPAPO/DM_PROD_ORDER_CHANGE and checked how it was filled in the planning book.
    For those who want to know:
      INCLUDE /sapapo/constants_om.
      CONSTANTS:
        lc_order_type_1f        TYPE /sapapo/om_order_type VALUE '1F'.
      DATA:
        ls_prod               TYPE /sapapo/msnp_prod,
        lt_prod               TYPE /sapapo/msnp_prod_tab,
        ls_sources            TYPE /sapapo/sources,
        lt_sources            TYPE /sapapo/sources_tab,
        lv_matid              TYPE /sapapo/matid,
        lv_locid              TYPE /sapapo/locid,
        lv_vrsioid            TYPE /sapapo/vrsioid,
        lv_tstfr              TYPE /sapapo/timestamp,
        lv_tstto              TYPE /sapapo/timestamp,
        lv_simsession         TYPE /sapapo/om_simsession.
    lv_vrsioid = '000'.
    * Create SimSession
    CALL FUNCTION '/SAPAPO/TSIM_SIMULATION_CONTRL'
        EXPORTING
          iv_simversion              = lv_vrsioid
          iv_simsession             = lv_simsession
          iv_simsession_method = 'N'
          iv_perform_commit       = space
        EXCEPTIONS
          lc_connect_failed        = 1
          lc_com_error             = 2
          lc_appl_error            = 3
          multi_tasim_registration = 4.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Get PDS
      CALL FUNCTION '/SAPAPO/MSDP_SNP_PPM_VALIDITY'
        EXPORTING
          iv_vrsioid      = lv_vrsioid
          iv_matid        = lv_matid
          iv_locid        = lv_locid
          iv_tstfr        = lv_tstfr
          iv_tstto        = lv_tstto
          iv_planstart    = lv_tstfr
          iv_planend      = lv_tstto
        CHANGING
          ct_sources      = lt_sources
        EXCEPTIONS
          wrong_interface = 1
          error_occured   = 2
          OTHERS          = 3.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      READ TABLE lt_sources INTO ls_sources INDEX 1.
      ls_prod-version       = lv_vrsioid.
      ls_prod-matid         = lv_matid.
      ls_prod-locid         = lv_locid.
      ls_prod-plobid        = '9AMALO'.
      ls_prod-tstmp         = lv_tstfr.
      ls_prod-catgr         = 'PP1'.
      ls_prod-categ         = 'EE'.
      ls_prod-categ_prku    = 'EE'.
      ls_prod-categ_prse    = 'EL'.
      ls_prod-kz_prod       = '9APPROD'.
      ls_prod-kz_prku       = '9APPROD'.
      ls_prod-kz_prse       = '9ADMDSE'.
      ls_prod-produ         = '1000'.
      ls_prod-proid         = ls_sources-trpid.
      ls_prod-mosta         = gc_new.
      ls_prod-order_type    = lc_order_type_1f.
      ls_prod-is_fixed      = 'X'.
      ls_prod-snp_is_header = 'X'.
      APPEND ls_prod TO lt_prod.
      CALL FUNCTION '/SAPAPO/DM_PROD_ORDER_CHANGE'
        EXPORTING
          ic_database           = 'LC'
          ic_application        = '4'
          iv_simsession         = lv_simsession
          it_prod               = lt_prod
          iv_netch              = 'X'
        EXCEPTIONS
          material_not_supplied = 1
          location_not_supplied = 2
          OTHERS                = 3.
    * Merge simulation version (to commit order changes)
      CALL FUNCTION '/SAPAPO/TSIM_SIMULATION_CONTRL'
        EXPORTING
          iv_simversion                = lv_vrsioid
          iv_simsession                = lv_simsession
          iv_simsession_method         = 'M'
        EXCEPTIONS
          lc_connect_failed            = 1
          lc_com_error                 = 2
          lc_appl_error                = 3
          multi_tasim_registration     = 4
          target_deleted_saveas_failed = 5
          OTHERS                       = 6.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.

  • Error while simulating Pay Plan

    Hi
    I created a pay plan item and trying to simulate the pay plan.I am getting the error "Error in debit entry Simulation".  Could anyone suggest how to get around this error
    Thanks and Regards
    Varadarajan B

    Hi Varadarajan,
    At first I assume that you are talking about an FS-CD Payment Plan. Is this correct? At second I assume you are referring to the Structure "SVVSCPOS_B" (Direct Input Structure of Payment Plan Items). Is this correct as well?
    If, and only if both assumptions are right: what 'nature' does the underlaying Payment Plan Item have? I assume it isn't a One-Time Payment (means: PSNGL = ' ' blank), when you execute 'Simulate Payment Plan' for a particular Insurance Object - Business Partner - Relationship, based on at least one item, or multiple items in table "VVSCPOS" (Payment Plan Item).
    Moreover: Are all important FS-CD Posting Areas (for example see transaction "FQC0", and table "TFK033C") properly configured?
    How did you create the Payment Plan and the Payment Plan Item(s)? I strongly recommend pretending being a feeder system and utilizing the special transaction 'VKTT'. Starting with "Read Partner - Application Server partner_std.txt > Continue" you will find in the main menu "Goto" for branching to Partner, Account, Ins. Object, or Payment Plan. Thus, you should create via VKTT
    a Business Partner,
    a Contract Account (with Relationship to this Business Partner),
    an Insurance Object (with Relationship to this Business Partner) and assigned to the Contract Account, see 2.;
    Thereafter you should create 4. an appropraite Payment Plan, of course with at least 5. one Payment Plan Item. Don't forget to save all your cases ;-)
    This approach will enable and support you to retest your scenario, and to analyze errors fast and easily, when you launch Collections/Disbursements > Master Data > Insurance Object > Change (transaction "INSOCHANGE") for the Insurance Object - see 3. - and the Payment Plan/Payment Plant Item - see 4. and 5. - you created through VKTT.
    If an error message occur, you should go to the Help and analyze the provided text. The AGS xSearch could help you in finding the root cause, please see "Home | SAP Support Portal"  <Login with your S-User or C-User) > "Knowledge Base &amp;amp; Incidents | SAP Support Portal" > "Search for a Solution | SAP Support Portal".
    Does this help?
    Kind regards,
    Jochem

  • Planning File Entry not generated for items releveant to PM

    MRP procedure used for material is reorder based planning , in April -09 the stock for this material is consumed and becomes
    zero (reorder point is 8 ,Maximum Stock Level is 8 ) and after that in MRP run the requirement is not generated .
    But as per the setting of reorder point PR should be initiated.
    When checked the MD21 , material is not flagged ,
    I want to know the specific reason why only  this material is not flagged for MRP run.
    What all settings i can check ?
    MATERIAL TYPE : YMRO   OP Maint/ Repair/OperSup
    Lot size : Repl. to max. stock level after cov. req
    Procurement type   :  F

    Hi,
    Run the reports MDRE & MDAB to ensure the planning file entries are correct.
    About your query what might have caused a entry not to be in planning file, well it could be many. So run the above reports & then run MRP & check the results.
    Regards,
    Vivek

  • Forcing a query to use a differnet plan

    I have one database where a sql plan appears to be correct through tests. In another database the join order is flipped. Data is relatively close. Hinting the query would require a code change. What is the easiest to force the plan from the other database?
    if this new plan does not work, what is the easiest way to revert back.

    Hi,
    Another option is SQL Plan Management
    SQL Plan Management (SPM) prevents performance regressions resulting from sudden changes to the execution plan of a SQL statement by providing components for capturing, selecting and evolving SQL plan information. Changes to the execution plan may result from database upgrades, system and data changes, application upgrade or bug fixes. When SPM is enabled, the system maintains a plan history that contains all plans generated by the optimizer and stores them in a component called plan baseline. Among the plan history in the plan baseline, plans that are verified not to cause performance regression are marked as acceptable. The plan baseline is used by the optimizer to decide on the best plan to use when compiling a SQL statement. Repository stored in a data dictionary of plan baselines and statement log maintained by the optimizer is called SQL Management Base (SMB).
    http://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/11g-sqlplanmanagement.html
    Regards,

  • Uploading planning book data error

    Hi Emmanuel,
    I think you can help me with this qn.
    When i am trying to upload the planning book data after using the save locally function, i am not able to load the data back to the planning book. I am getting a dump.
    I am not able to resolve it. can u please guide me.
    Thank you very much in advance

    Hi Sandeep,
    When you saved the file using the "Save locally" functionality in the Interactive Planning transaction, did you choose the option "Prepare file for upload at a later time" ? You have to choose that option so that an upload later will work.
    Also, please check out OSS note Note "925933 - Interactive Planning Excel up/download corrections".
    Please tell me if this helps to solve your problem

  • DP macros are not being calculated correctly using process chain

    Hello all!!
    I have this DP planning book with two grids, which the second grid has some macros. I have to put this macros execution in a Process Chain, but it´s very strange because, when I execute the macro directly in the interactive planning the result is correct, but when I execute it using the process chain, the result is wrong.
    The selection profile and the aggregation level in the Process Chain is the same that is being used in the selection profile.
    I´ve already created the activities and also the planning job to be used in the process chain.
    Could you help me?
    Best regards
    Angela

    I would suggest to create a test selection Id with a few products (say 5) and create a new job with this selection profile and include that job in the process chain and execute it. Please monitor the job log while porcessing... for this right click on the process in the process chain and select 'Display all jobs'..it will take you to the SM37 screen..there click the job log and spool file and observe what exactly the job is doing i.e whether its executing correctly or its skipping that process or something else is doing...
    The second thing you can try out is by creating a separate dataview for the second grid in the test sytem and replicate the scenario and check if it has any impact, my guess is if process chain is not supporting the macros in the second grid
    Edited by: sai balakavi on Dec 12, 2008 8:14 PM

  • COPA Plan values not appearing in report

    Hi
    I posted COPA Plan values using KEPM and line items are appearing in KE25 but no values are not being appeared in COPA line item report we created using report painter. We used KE94 and KE91.
    Actual values appearing correctly in report.
    Any help??

    Check if you have Plan/Act indicator maintained correctly with the plan value. If it shows up in other reports, I don't see any reason why it will not show up here. I would also check other parameters entered in the report and see if any other characteristic is preventing plan values from populating.
    Shail

  • Explain plans differ:  same query, cloned databases.

    oracle 10.2.0.2.0
    solaris 10
    same query, different databases (cloned from same source), different explain plans.
    db parameters are identical.
    Any ideas?
    DB1 (production)
    SQL> explain plan for
      2  SELECT  V__101.*,   SHAPE.fid,SHAPE.numofpts,SHAPE.entity,SHAPE.points,
      3    SHAPE.rowid
      4  FROM
      5   (SELECT b.OBJECTID,b.CRT_DTE,b.CRT_SRC_CDE,b.CRT_AQUI_MTHD_CDE,b.CRT_USR_ID,
      6    b.ADT_ACTN_CDE,b.ADT_ACTN_DTE,b.ADT_ACTN_SRC_CDE,b.ADT_ACTN_USR_ID,
      7    b.TP_SITE_POINT_ID,b.SHAPE,b.SRC_ID,b.SRC_CRT_DTE,b.SRC_TYPE_CDE,
      8    b.LCTN_STAT_CDE,b.FRZN_LCTN_IND,b.TP_NOTES   FROM AMSOWNER.TP_SITE_POINT b
      9    WHERE b.OBJECTID NOT IN (SELECT /*+ HASH_AJ */ SDE_DELETES_ROW_ID FROM
    10    AMSOWNER.D101 WHERE DELETED_AT IN (SELECT l.lineage_id FROM
      SDE.state_lineages l WHERE l.lineage_name = :source_lineage_name AND
    11   12    l.lineage_id <= :source_state_id) AND SDE_STATE_ID = :"SYS_B_0") UNION ALL
      SELECT a.OBJECTID,a.CRT_DTE,a.CRT_SRC_CDE,a.CRT_AQUI_MTHD_CDE,a.CRT_USR_ID,
    13   14    a.ADT_ACTN_CDE,a.ADT_ACTN_DTE,a.ADT_ACTN_SRC_CDE,a.ADT_ACTN_USR_ID,
    15    a.TP_SITE_POINT_ID,a.SHAPE,a.SRC_ID,a.SRC_CRT_DTE,a.SRC_TYPE_CDE,
    16    a.LCTN_STAT_CDE,a.FRZN_LCTN_IND,a.TP_NOTES   FROM AMSOWNER.A101 a,
    17    SDE.state_lineages SL WHERE (a.OBJECTID, a.SDE_STATE_ID) NOT IN (SELECT /*+
    18    HASH_AJ */ SDE_DELETES_ROW_ID,SDE_STATE_ID  FROM AMSOWNER.D101 WHERE
    19    DELETED_AT IN (SELECT l.lineage_id FROM SDE.state_lineages l WHERE
    20    l.lineage_name = :source_lineage_name AND l.lineage_id <= :source_state_id)
    21    AND SDE_STATE_ID > :"SYS_B_1") AND a.SDE_STATE_ID = SL.lineage_id AND
    22    SL.lineage_name = :source_lineage_name AND SL.lineage_id <=
    23    :source_state_id ) V__101 , AMSOWNER.F15 SHAPE where SHAPE.FID(+) =
    24    V__101.SHAPE;
    Explained.
    SQL>  @?/rdbms/admin/utlxplp.sql;
    PLAN_TABLE_OUTPUT
    Plan hash value: 254376361
    | Id  | Operation                         | Name             | Rows  | Bytes |TempSpc| Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT                  |                  |   113K|    49M|       |  2926   (1)| 00:00:41 |
    |*  1 |  HASH JOIN RIGHT OUTER            |                  |   113K|    49M|    17M|  2926   (1)| 00:00:41 |
    |   2 |   TABLE ACCESS FULL               | F15              |   113K|    15M|       |   344   (2)| 00:00:05 |
    |   3 |   VIEW                            |                  |   113K|    34M|       |   331   (2)| 00:00:05 |
    |   4 |    UNION-ALL                      |                  |       |       |       |            |          |
    |*  5 |     HASH JOIN RIGHT ANTI          |                  |   113K|  8948K|       |   332   (2)| 00:00:05 |
    |   6 |      VIEW                         | VW_NSO_1         |     1 |    13 |       |     2   (0)| 00:00:01 |
    |   7 |       NESTED LOOPS                |                  |     1 |    50 |       |     2   (0)| 00:00:01 |
    |   8 |        TABLE ACCESS BY INDEX ROWID| D101             |     1 |    39 |       |     1   (0)| 00:00:01 |
    |*  9 |         INDEX SKIP SCAN           | D101_IDX1        |     1 |       |       |     1   (0)| 00:00:01 |
    |* 10 |        INDEX UNIQUE SCAN          | LINEAGES_PK      |     1 |    11 |       |     1   (0)| 00:00:01 |
    |  11 |      TABLE ACCESS FULL            | TP_SITE_POINT    |   113K|  7512K|       |   329   (2)| 00:00:05 |
    |* 12 |     HASH JOIN ANTI                |                  |     1 |   375 |       |     5  (20)| 00:00:01 |
    |  13 |      NESTED LOOPS                 |                  |     1 |   349 |       |     2   (0)| 00:00:01 |
    |  14 |       TABLE ACCESS BY INDEX ROWID | A101             |     1 |   338 |       |     1   (0)| 00:00:01 |
    |* 15 |        INDEX RANGE SCAN           | A101_STATEID_IX1 |     1 |       |       |     1   (0)| 00:00:01 |
    |* 16 |       INDEX UNIQUE SCAN           | LINEAGES_PK      |     1 |    11 |       |     1   (0)| 00:00:01 |
    |* 17 |      VIEW                         | VW_NSO_2         |     1 |    26 |       |     2   (0)| 00:00:01 |
    |  18 |       NESTED LOOPS                |                  |     1 |    50 |       |     2   (0)| 00:00:01 |
    |* 19 |        INDEX FULL SCAN            | D101_PK          |     1 |    39 |       |     1   (0)| 00:00:01 |
    |* 20 |        INDEX UNIQUE SCAN          | LINEAGES_PK      |     1 |    11 |       |     1   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       1 - access("SHAPE"."FID"(+)="V__101"."SHAPE")
       5 - access("B"."OBJECTID"="$nso_col_1")
       9 - access("SDE_STATE_ID"=TO_NUMBER(:SYS_B_0))
           filter("SDE_STATE_ID"=TO_NUMBER(:SYS_B_0))
      10 - access("L"."LINEAGE_NAME"=TO_NUMBER(:SOURCE_LINEAGE_NAME) AND "DELETED_AT"="L"."LINEAGE_ID")
           filter("L"."LINEAGE_ID"<=TO_NUMBER(:SOURCE_STATE_ID))
      12 - access("A"."OBJECTID"="$nso_col_1" AND "A"."SDE_STATE_ID"="$nso_col_2")
      15 - access("A"."SDE_STATE_ID"<=TO_NUMBER(:SOURCE_STATE_ID))
      16 - access("SL"."LINEAGE_NAME"=TO_NUMBER(:SOURCE_LINEAGE_NAME) AND
                  "A"."SDE_STATE_ID"="SL"."LINEAGE_ID")
           filter("SL"."LINEAGE_ID"<=TO_NUMBER(:SOURCE_STATE_ID))
      17 - filter("$nso_col_2"<=TO_NUMBER(:SOURCE_STATE_ID))
      19 - access("SDE_STATE_ID">TO_NUMBER(:SYS_B_1))
           filter("SDE_STATE_ID">TO_NUMBER(:SYS_B_1))
      20 - access("L"."LINEAGE_NAME"=TO_NUMBER(:SOURCE_LINEAGE_NAME) AND "DELETED_AT"="L"."LINEAGE_ID")
           filter("L"."LINEAGE_ID"<=TO_NUMBER(:SOURCE_STATE_ID))
    47 rows selected.DB2 (staging)
    SQL> explain plan for
      2  SELECT  V__101.*,   SHAPE.fid,SHAPE.numofpts,SHAPE.entity,SHAPE.points,
      SHAPE.rowid
    FROM
      3    4    5   (SELECT b.OBJECTID,b.CRT_DTE,b.CRT_SRC_CDE,b.CRT_AQUI_MTHD_CDE,b.CRT_USR_ID,
      b.ADT_ACTN_CDE,b.ADT_ACTN_DTE,b.ADT_ACTN_SRC_CDE,b.ADT_ACTN_USR_ID,
      6    7    b.TP_SITE_POINT_ID,b.SHAPE,b.SRC_ID,b.SRC_CRT_DTE,b.SRC_TYPE_CDE,
      8    b.LCTN_STAT_CDE,b.FRZN_LCTN_IND,b.TP_NOTES   FROM AMSOWNER.TP_SITE_POINT b
      9    WHERE b.OBJECTID NOT IN (SELECT /*+ HASH_AJ */ SDE_DELETES_ROW_ID FROM
    10    AMSOWNER.D101 WHERE DELETED_AT IN (SELECT l.lineage_id FROM
    11    SDE.state_lineages l WHERE l.lineage_name = :source_lineage_name AND
    12    l.lineage_id <= :source_state_id) AND SDE_STATE_ID = :"SYS_B_0") UNION ALL
    13    SELECT a.OBJECTID,a.CRT_DTE,a.CRT_SRC_CDE,a.CRT_AQUI_MTHD_CDE,a.CRT_USR_ID,
    14    a.ADT_ACTN_CDE,a.ADT_ACTN_DTE,a.ADT_ACTN_SRC_CDE,a.ADT_ACTN_USR_ID,
    15    a.TP_SITE_POINT_ID,a.SHAPE,a.SRC_ID,a.SRC_CRT_DTE,a.SRC_TYPE_CDE,
    16    a.LCTN_STAT_CDE,a.FRZN_LCTN_IND,a.TP_NOTES   FROM AMSOWNER.A101 a,
    17    SDE.state_lineages SL WHERE (a.OBJECTID, a.SDE_STATE_ID) NOT IN (SELECT /*+
      HASH_AJ */ SDE_DELETES_ROW_ID,SDE_STATE_ID  FROM AMSOWNER.D101 WHERE
    18   19    DELETED_AT IN (SELECT l.lineage_id FROM SDE.state_lineages l WHERE
    20    l.lineage_name = :source_lineage_name AND l.lineage_id <= :source_state_id)
    21    AND SDE_STATE_ID > :"SYS_B_1") AND a.SDE_STATE_ID = SL.lineage_id AND
    22    SL.lineage_name = :source_lineage_name AND SL.lineage_id <=
    23    :source_state_id ) V__101 , AMSOWNER.F15 SHAPE where SHAPE.FID(+) =
    24    V__101.SHAPE;
    Explained.
    SQL>  @?/rdbms/admin/utlxplp.sql;
    PLAN_TABLE_OUTPUT
    Plan hash value: 4287458713
    | Id  | Operation                         | Name             | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT                  |                  |   145 | 68150 |   401   (1)| 00:00:06 |
    |   1 |  NESTED LOOPS OUTER               |                  |   145 | 68150 |   401   (1)| 00:00:06 |
    |   2 |   VIEW                            |                  |   145 | 47125 |   328   (1)| 00:00:05 |
    |   3 |    UNION-ALL                      |                  |       |       |            |          |
    |*  4 |     HASH JOIN ANTI                |                  |   144 | 10224 |   324   (1)| 00:00:05 |
    |   5 |      TABLE ACCESS FULL            | TP_SITE_POINT    |   145 |  8410 |   322   (1)| 00:00:05 |
    |   6 |      VIEW                         | VW_NSO_1         |     1 |    13 |     2   (0)| 00:00:01 |
    |   7 |       NESTED LOOPS                |                  |     1 |    50 |     2   (0)| 00:00:01 |
    |*  8 |        TABLE ACCESS BY INDEX ROWID| D101             |     1 |    39 |     1   (0)| 00:00:01 |
    |*  9 |         INDEX SKIP SCAN           | D101_IDX1        |     1 |       |     1   (0)| 00:00:01 |
    |* 10 |        INDEX UNIQUE SCAN          | LINEAGES_PK      |     1 |    11 |     1   (0)| 00:00:01 |
    |* 11 |     FILTER                        |                  |       |       |            |          |
    |  12 |      NESTED LOOPS                 |                  |     1 |   349 |     2   (0)| 00:00:01 |
    |  13 |       TABLE ACCESS BY INDEX ROWID | A101             |     1 |   338 |     1   (0)| 00:00:01 |
    |* 14 |        INDEX RANGE SCAN           | A101_STATEID_IX1 |     1 |       |     1   (0)| 00:00:01 |
    |* 15 |       INDEX UNIQUE SCAN           | LINEAGES_PK      |     1 |    11 |     1   (0)| 00:00:01 |
    |* 16 |      FILTER                       |                  |       |       |            |          |
    |  17 |       NESTED LOOPS                |                  |     1 |    50 |     2   (0)| 00:00:01 |
    |* 18 |        TABLE ACCESS BY INDEX ROWID| D101             |     1 |    39 |     1   (0)| 00:00:01 |
    |* 19 |         INDEX RANGE SCAN          | D101_IDX1        |     1 |       |     1   (0)| 00:00:01 |
    |* 20 |        INDEX UNIQUE SCAN          | LINEAGES_PK      |     1 |    11 |     1   (0)| 00:00:01 |
    |  21 |   TABLE ACCESS BY INDEX ROWID     | F15              |     1 |   145 |     1   (0)| 00:00:01 |
    |* 22 |    INDEX UNIQUE SCAN              | F15_UK1          |     1 |       |     1   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       4 - access("B"."OBJECTID"="$nso_col_1")
       8 - filter("DELETED_AT"<=TO_NUMBER(:SOURCE_STATE_ID))
       9 - access("SDE_STATE_ID"=TO_NUMBER(:SYS_B_0))
           filter("SDE_STATE_ID"=TO_NUMBER(:SYS_B_0))
      10 - access("L"."LINEAGE_NAME"=TO_NUMBER(:SOURCE_LINEAGE_NAME) AND
                  "DELETED_AT"="L"."LINEAGE_ID")
           filter("L"."LINEAGE_ID"<=TO_NUMBER(:SOURCE_STATE_ID))
      11 - filter( NOT EXISTS (SELECT /*+ HASH_AJ */ 0 FROM "AMSOWNER"."D101"
                  "D101","SDE"."STATE_LINEAGES" "L" WHERE :B1>TO_NUMBER(:SYS_B_1) AND
                  "DELETED_AT"="L"."LINEAGE_ID" AND "L"."LINEAGE_NAME"=TO_NUMBER(:SOURCE_LINEAGE_NAME) AND
                  "L"."LINEAGE_ID"<=TO_NUMBER(:SOURCE_STATE_ID) AND "SDE_STATE_ID"=:B2 AND
                  "SDE_DELETES_ROW_ID"=:B3 AND "DELETED_AT"<=TO_NUMBER(:SOURCE_STATE_ID) AND
                  "SDE_STATE_ID">TO_NUMBER(:SYS_B_1)))
      14 - access("A"."SDE_STATE_ID"<=TO_NUMBER(:SOURCE_STATE_ID))
      15 - access("SL"."LINEAGE_NAME"=TO_NUMBER(:SOURCE_LINEAGE_NAME) AND
                  "A"."SDE_STATE_ID"="SL"."LINEAGE_ID")
           filter("SL"."LINEAGE_ID"<=TO_NUMBER(:SOURCE_STATE_ID))
      16 - filter(:B1>TO_NUMBER(:SYS_B_1))
      18 - filter("DELETED_AT"<=TO_NUMBER(:SOURCE_STATE_ID))
      19 - access("SDE_DELETES_ROW_ID"=:B1 AND "SDE_STATE_ID"=:B2)
           filter("SDE_STATE_ID">TO_NUMBER(:SYS_B_1))
      20 - access("L"."LINEAGE_NAME"=TO_NUMBER(:SOURCE_LINEAGE_NAME) AND
                  "DELETED_AT"="L"."LINEAGE_ID")
           filter("L"."LINEAGE_ID"<=TO_NUMBER(:SOURCE_STATE_ID))
      22 - access("SHAPE"."FID"(+)="V__101"."SHAPE")
    58 rows selected.

    rocr wrote:
    oracle 10.2.0.2.0
    solaris 10
    same query, different databases (cloned from same source), different explain plans.
    db parameters are identical.
    DB1 (production)
    | Id  | Operation                         | Name             | Rows  | Bytes |TempSpc| Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT                  |                  |   113K|    49M|       |  2926   (1)| 00:00:41 |DB2 (staging)
    | Id  | Operation                         | Name             | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT                  |                  |   145 | 68150 |   401   (1)| 00:00:06 |
    If you check the execution plans it's quite obvious that the two environments can not be identical. If you have the same (amount of) data, then one of the two estimates is way off. Which one is in the right ballpark, how many rows are returned by the query? The same applies to the remaining operation ids of the plan, which estimate is correct?
    It's very likely that the underlying table/index statistics are not the same, and therefore you get different plans.
    By the way, you're using bind variables, therefore the output of the EXPLAIN PLAN is only of limited use, since the actual plan at run time might be completely different due to bind variable peeking and potentially histograms created on some of the columns (which is the default in 10g due to the "FOR ALL COLUMNS SIZE AUTO" method_opt default parameter value).
    If you haven't disabled the pre-configured statistics collection job that runs every night in 10g, you might get different statistics due to this job already.
    Regards,
    Randolf
    Oracle related stuff blog:
    http://oracle-randolf.blogspot.com/
    SQLTools++ for Oracle (Open source Oracle GUI for Windows):
    http://www.sqltools-plusplus.org:7676/
    http://sourceforge.net/projects/sqlt-pp/

  • Report Painter - What is value type 10 Statistical Plan

    One of my customers is running report 6o00-001 Orders: Actual / Plan / Variance. This report is displaying a plan value when, they say, no plan value has been entered. I have checked normal planning and this is correct - there is no plan value. However, when I check the report painter definition, the column in question will display value type 1 (Plan) and value type 10 (Statistical Plan).
    Can anyone tell me:
    - what is a statistical plan on an order?
    - how can I remove the statistical plan value?
    Many thanks in advance.

    Hi Szymon
    Thanks for your answer.
    But checking the correction constructions the code do reference to the operation RKP5 and the posting are being recording with operation RKP1.
    I'm checking for a similar note but with this operation but I can't find it.
    Do you know if it is something like that?
    Regards
    This is like the record looks in the table COSP.
    Client
    130
    MANDT
    130
    Ledger
    0
    LEDNR
    00
    Object number
    OR000000760636
    OBJNR
    OR000000760636
    Fiscal Year
    2014
    GJAHR
    2014
    Value Type
    10
    WRTTP
    10
    Version
    1
    VERSN
    001
    Cost Element
    56650101
    KSTAR
    0056650101
    CO subkey
    HRKFT
    Business Transaction
    RKP1
    VRGNG
    RKP1
    Trading Partner
    VBUND
    Trading Part.BA
    PARGB
    Dr/Cr indicator
    D
    BEKNZ
    S
    Transaction Currency
    BRL
    TWAER
    BRL
    Period block
    016
    PERBL
    016
    Unit of Measure
    MEINH
                                                                                                                                        *  modification to post revenues - Note 604092 if coeja-wrttp = '10' and uf-activ = 'RKP5'. elseif coeja-wrttp ge '01' and coeja-wrttp le '04'. else. continue. endif. *  end modification to post revenues - Note 604092
    Code in correction instruction.
    *   modification to post revenues - Note 604092 if coeja-wrttp = '10' and uf-activ = 'RKP5'. elseif coeja-wrttp ge '01' and coeja-wrttp le '04'. else. continue. endif. *   end modification to post revenues - Note 604092

  • Planning Layout Execution

    Dear all,
          I have a scenario would like to discuss and share. I have 2 planning folders, First planning folder has the correct volume, where as the 2nd planning folder the volume will get lesser, both also using the same planning version.
    when i Click the planning layout in the 2nd planning folder, i save the data in the cube( i dint do anything in the input layout,system seem got some records generated after opening the layout) thus i go back to that bw infopackage, volume got  some value has been minus out.
    Question:Why the sytem behave in this way?how come i dint execute any planning function there is records generated? can we stop that? if not my volume will vary from one folder to another.
    Feel free to give comment or solution,
    THanks

    Check if in your planing folder there is any function that start automaticlly on layout open or befor save.
    Also check if both layout has the same selection condition in planing package an level and if they have same logic (based on existent data or generate all possible combination).
    Hope it helps.
    Regards

  • CANNOT CHANGE PLANNING DATE

    HI GURUS,
    We posted a SD document 180000XXXX Base line date 16.12.2008 and Payt terms C003 (30 days) thE planning date must be 15.01.2009 but the Planning date is 12.01.2008. We intented change the base line date, the Payment terms and the Planning date doesn´t change. Can someone knows how can we fix the date line??

    We have  the OBB8 terms OK. but in this document in particular when we use FB03 the planning date is not correct, the Net Due Date is correct(15.01.2009), but for Treassury the Planning date is not correct
    Payment Terms: C003 (30 days)
    Bline Date:    16.12.2008
    The planning date (claculated by SAP): 12.01.2008  (This day is not correct, SAP is not taken 16.12.2008 + 30 days)
    I tried changing the bline date and the Payment Terms but it doesn´t work for this particular document? Anybody knows WHY?

  • Planned cost in service order does not reflect PO price change

    Dear experts:
    I set up a service order for external processing using control key SM02. I enter the purchasing data e.g. price, vendor, info record. I determine costs and the system calculates the planned cost for purchasing correctly.
    On saving the service order, a PR is automatically created. Then I raise a PO for the PR, and change the PO net price.
    I now return to the service order and determine costs again. However, the system still calculate the planned cost based on the price in the external operation, not the changed PO net price. Only if I remove the price in the external operation and determine costs, will the system calculate the planned cost based on the PO net price.
    I have played around with the Customzing setting for valuaiton variant (transaction OKP8). Changing the strategy sequence for External processing does not seem to make any difference.
    Has anyone encountered this issue before?
    Thank you.
    With regards,
    Dan

    Hi,
    In standard functionality the System will calculate the Planned price from the filed where you maintain the price for that operation.
    The Planned price is PR price only for any order.The PO price is actual price/Market price,Once the GR will be done then the PO price will get update in the Actual cost of the Service order.
    This is standard Functionality,If you want to update the planned price with the PO price then try with User exit to update the price.The field is PKOSTEN for the planned price.
    Regards,
    Raj

  • Excel 2007 error when displaying GL Planning Data (GP12NA)

    Dear All,
    T-code:GP12NA
    When i display the GL Planning Data using the integration with office excel 2007, the cell automatically becomes to date and time format on the value field.
    But when i display using integration with office excel 2003, the GL Planning data is displayed correctly.
    Appreciate if someone could address me on this issue.
    Many thanks.

    Hi Jason,
    I did not able to solve the problem.
    Alternatively, I created 2 planning layout assigned to one planning profile.
    1. Layout 1 - Integrated with excel (tick)
    I used this layout for for uploading GL planning figures using the t-code GLPLUP.
    2. Layout 2 - Integrated with excel (do not  tick)
    To display the GL Planning figures, i used this profile in t-code GP12NA. By this way, the figures are correctly displayed without any formatting error.
    I assume this due to patches that needs to be upgraded in order display excel 2007 correctly.
    Please reply me if you need further clarification.

Maybe you are looking for