Unexpected result of Production Plan

Hi Experts
We are doing finite planning for 4 weeks in PPDS.
Heuristic which is used for FinitePlanning:
Step 1: SAP_PP_020
Step2: SAP_REM_014
Planning time fence for Finite Planning: 2 weeks (As the Users Manually Update the Production Plan)
We are running finite planning on every week
Please find the below example:
PIRS:
Mon= 100
Tues= 0
Wed = 200
Thus= 0
Fri=0
Sat=900
The result of production plan by monday= 1200
Stock levels are increasing by Monday itself. Which should not happen.
Production is ready by monday for the Wednesdays and Saterdays requirment.
Please provide your valuable suggesstions.
Thanks
Edited by: kck.0623 on Mar 14, 2010 11:38 AM

Similar Messages

Daily Production Plan query changes

Dear Experts,
I was tried to do a daily production plan query, but i need to add one more feild in the below query, (ie) In sale order Document, Row level feild of Quantity ( RDR1,Quantity) should be in that query,
SELECT T0.[ItemCode],T1.[ItemName], T0.[PlannedQty] as 'Planned Qty', T0.[DocNum] as 'Doc No', T0.[PostDate], T0.[OriginNum] as 'Sale Order No', T0.[CardCode], T0.[CmpltQty] as 'Completed Qty' FROM OWOR T0 join OITM T1 on T0.Itemcode = t1.ItemCode WHERE T0.[PostDate] >='[%0]' and T0.[PostDate] <='[%1]'
Plz help me.
Thanks and Regards,
Manikandan

Hello Manikandan,
You can add the sales order into the production order, but you should now: there is no connection defined between sales order lines and production order, only the item code can be used as reference to sales order lines
I mean:
*if you have the same item in sales order lines in different position the query always multiplies the result. *
So you can join the sales order header for Origin Number and DocNum, and sales order lines by Itemcode
SELECT
     T0.[ItemCode],T1.[ItemName], T0.[PlannedQty] as 'Planned Qty', T0.[DocNum] as 'Doc No', T0.[PostDate],
     T0.[OriginNum] as 'Sale Order No', T0.[CardCode], T0.[CmpltQty] as 'Completed Qty',
     T3.[Quantity] [Sales order Qty], T3.LineNum [Sales order Postion]
FROM
     OWOR T0 join OITM T1 on T0.Itemcode = t1.ItemCode
     left outer join ORDR T2 on T0.[OriginNum] = T2.[DocNum]
     left outer join RDR1 T3 on T2.[DocEntry] = T3.[DocEntry] and T3.[ItemCode] = T0.[ItemCode]
WHERE T0.[PostDate] >='[%0]' and T0.[PostDate] <='[%1]'
Regards
J.

Tuning : Inconsistent result between Explain plan VS Execution Time

Dear Experts,
Need your suggestions belongs to contrary result between Explain plan VS Execution Time
Environment :_
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
PL/SQL Release 10.2.0.4.0 - Production
CORE     10.2.0.4.0     Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Red Hat Enterprise Linux 5.4
There's same query but : 1st query access Loan_Account, 2nd query access Loan_Account_Han
*1st.*
Query Access Via : Loan_account (Partition Type : Hash (5) with column Contract_Number)
Explain Plan : cost: 4,432, bytes: 716, cardinality: 2
Execution Time : 13 seconds
*2nd.*
Query Access Via : Loan_Account_Han (Partition Type : List(5) with column Loan_Status)
Explain Plan : cost:188,447 bytes: 1,661,088, cardinality: 4,719
Execution Time : 10 seconds
Note :_
all tables and all indexes belong to the table which included in query has been analyzed.
my question :
1. why it could become like this ? I even confusing with Jonathan Lewis Theory : Cost-Based Fundamental Book.
with this result, I even not believed with the result from Explain Plan anymore.
2. If analyze tables and indexes to update statistics which help CBO to choose the best path as part of Daily Performance Tuning,
is there a way that could do in enviroment 24x7 ?
Note : if original query is needed, I'll posting it here.
Any help is very appreciated and thanks very much.
Regards,
Sigcle

The DBMS_XPLAN.DISPLAY_CURSOR output
Query no 1
PLAN_TABLE_OUTPUT
SQL_ID bq7avs72xvmkv, child number 0
SELECT /*+ gather_plan_statistics */ la.office_code, la.currency_code AS currency, mf.NAME multifinance_id,        la.contract_number, mc.customer_name,
dco.os_principal_on_schedule AS os_principal_on_schedule,        f_get_param_value (la.financing_type,                           'FinancingType'
       ) AS financing_type,        CASE la.financing_type           WHEN 11                    -- Asset Purchase              THEN NVL (tp.os_principal_cust,
                  la.os_principal_cust                       )           WHEN 12                                            -- JF Channelling              THEN
NVL (tp.os_principal_mf, la.os_principal)        END AS os_principal_actual,        CASE           WHEN dco.bi_collectibility_with_gp >= 3              THEN 0
      ELSE CASE           WHEN la.financing_type = '12'              THEN   NVL (ia.accrue_interest_pl, 0)                   + NVL (ia.accrue_interest_npl, 0)
      ELSE   NVL (ia.accrue_
Plan hash value: 4011856754
| Id | Operation                                  | Name                           | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads | OMem | 1Mem | Used-Mem |
|   1 | TABLE ACCESS BY INDEX ROWID               | COLLECTIBILITY_CODE            |      3 |      1 |      3 |00:00:00.01 |       9 |      2 |       |       |          |
|* 2 |   INDEX SKIP SCAN                          | UNQ_COLLECTIBILITY_CODE        |      3 |      1 |      3 |00:00:00.01 |       6 |      1 |       |       |          |
|   3 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    501 |      1 |    501 |00:00:00.03 |    2004 |    796 |       |       |          |
|* 4 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    501 |      1 |    501 |00:00:00.02 |    1503 |    377 |       |       |          |
|   5 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    333 |      1 |    333 |00:00:00.10 |    3220 |   1074 |       |       |          |
|* 6 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    333 |      1 |    333 |00:00:00.09 |    2887 |   1074 |       |       |          |
|   7 |   TABLE ACCESS BY GLOBAL INDEX ROWID       | CUST_SCH_INSTALLMENT           |    168 |      1 |    167 |00:00:00.05 |    1464 |    495 |       |       |          |
|* 8 |    INDEX UNIQUE SCAN                       | UNQ_CUST_SCH_INSTALLMENT1      |    168 |      1 |    167 |00:00:00.05 |    1297 |    495 |       |       |          |
|   9 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    333 |      1 |    333 |00:00:00.06 |    3167 |      0 |       |       |          |
|* 10 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    333 |      1 |    333 |00:00:00.06 |    2834 |      0 |       |       |          |
| 11 |   TABLE ACCESS BY GLOBAL INDEX ROWID       | CUST_SCH_INSTALLMENT           |    168 |      1 |    167 |00:00:00.03 |    1447 |      0 |       |       |          |
|* 12 |    INDEX UNIQUE SCAN                       | UNQ_CUST_SCH_INSTALLMENT1      |    168 |      1 |    167 |00:00:00.03 |    1280 |      0 |       |       |          |
| 13 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    333 |      1 |    333 |00:00:00.06 |    3167 |      0 |       |       |          |
|* 14 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    333 |      1 |    333 |00:00:00.06 |    2834 |      0 |       |       |          |
| 15 |   TABLE ACCESS BY GLOBAL INDEX ROWID       | CUST_SCH_INSTALLMENT           |    168 |      1 |    167 |00:00:00.03 |    1447 |      0 |       |       |          |
|* 16 |    INDEX UNIQUE SCAN                       | UNQ_CUST_SCH_INSTALLMENT1      |    168 |      1 |    167 |00:00:00.03 |    1280 |      0 |       |       |          |
| 17 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    333 |      1 |    333 |00:00:00.06 |    3167 |      0 |       |       |          |
|* 18 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    333 |      1 |    333 |00:00:00.06 |    2834 |      0 |       |       |          |
| 19 |   TABLE ACCESS BY GLOBAL INDEX ROWID       | CUST_SCH_INSTALLMENT           |    168 |      1 |    167 |00:00:00.03 |    1447 |      0 |       |       |          |
|* 20 |    INDEX UNIQUE SCAN                       | UNQ_CUST_SCH_INSTALLMENT1      |    168 |      1 |    167 |00:00:00.03 |    1280 |      0 |       |       |          |
|* 21 | TABLE ACCESS FULL                         | COLLECTIBILITY_CODE            |      3 |      1 |      3 |00:00:00.01 |      12 |      1 |       |       |          |
| 22 | NESTED LOOPS OUTER                        |                                |      1 |      2 |    501 |00:00:01.02 |   96112 | 20091 |       |       |          |
| 23 |   NESTED LOOPS                             |                                |      1 |      2 |    501 |00:00:00.28 |   13445 |   5358 |       |       |          |
| 24 |    NESTED LOOPS                            |                                |      1 |      2 |    501 |00:00:00.26 |   11441 |   5071 |       |       |          |
| 25 |     NESTED LOOPS OUTER                     |                                |      1 |      2 |    501 |00:00:00.24 |    9433 |   5014 |       |       |          |
|* 26 |      HASH JOIN                             |                                |      1 |      2 |    501 |00:00:00.03 |     329 |    325 | 1206K| 1206K| 341K (0)|
|* 27 |       TABLE ACCESS FULL                    | CURRENCY                       |      1 |      1 |      1 |00:00:00.01 |       3 |      2 |       |       |          |
|* 28 |       HASH JOIN                            |                                |      1 |     61 |    501 |00:00:00.02 |     326 |    323 |   868K|   868K| 947K (0)|
|* 29 |        HASH JOIN                           |                                |      1 |     10 |     13 |00:00:00.01 |       7 |      6 |   947K|   947K| 1030K (0)|
| 30 |         TABLE ACCESS BY INDEX ROWID        | MULTIFINANCE                   |      1 |      5 |      9 |00:00:00.01 |       2 |      2 |       |       |          |
|* 31 |          INDEX RANGE SCAN                  | IDX_STATUS_MF                  |      1 |      5 |      9 |00:00:00.01 |       1 |      1 |       |       |          |
|* 32 |         TABLE ACCESS FULL                  | AGREEMENT                      |      1 |     18 |     13 |00:00:00.01 |       5 |      4 |       |       |          |
| 33 |        VIEW                                |                                |      1 |    110 |    501 |00:00:00.02 |     319 |    317 |       |       |          |
|* 34 |         HASH JOIN RIGHT OUTER              |                                |      1 |    110 |    501 |00:00:00.02 |     319 |    317 | 1011K| 1011K| 317K (0)|
| 35 |          TABLE ACCESS BY INDEX ROWID       | TENANT_PARAMETER               |      1 |      1 |      1 |00:00:00.01 |       2 |      2 |       |       |          |
|* 36 |           INDEX UNIQUE SCAN                | PK_TENANT_PARAMETER            |      1 |      1 |      1 |00:00:00.01 |       1 |      1 |       |       |          |
|* 37 |          TABLE ACCESS BY GLOBAL INDEX ROWID| LOAN_ACCOUNT                   |      1 |    110 |    501 |00:00:00.02 |     317 |    315 |       |       |          |
|* 38 |           INDEX RANGE SCAN                 | IDX_STATUS_LA1                 |      1 |   4394 |   3025 |00:00:00.01 |      15 |     14 |       |       |          |
|* 39 |      TABLE ACCESS BY INDEX ROWID           | TX_PAYMENT                     |    501 |      1 |      0 |00:00:00.16 |    9104 |   4689 |       |       |          |
|* 40 |       INDEX RANGE SCAN                     | FK_TX_PAY_LOAN_ACCT            |    501 |     12 |   8799 |00:00:00.02 |    1038 |    207 |       |       |          |
| 41 |     TABLE ACCESS BY INDEX ROWID            | DL_CL_OUTSTANDING              |    501 |      1 |    501 |00:00:00.02 |    2008 |     57 |       |       |          |
|* 42 |      INDEX RANGE SCAN                      | IDXLO_CNUM                     |    501 |      1 |    501 |00:00:00.01 |    1507 |     37 |       |       |          |
|* 43 |    TABLE ACCESS BY INDEX ROWID             | MF_CUSTOMER                    |    501 |      1 |    501 |00:00:00.02 |    2004 |    287 |       |       |          |
|* 44 |     INDEX UNIQUE SCAN                      | MF_CUSTOMER_PK                 |    501 |      1 |    501 |00:00:00.01 |    1503 |     24 |       |       |          |
|* 45 |   TABLE ACCESS BY INDEX ROWID              | TX_INTEREST_ACCRUE             |    501 |      1 |      0 |00:00:00.73 |   82667 | 14733 |       |       |          |
|* 46 |    INDEX RANGE SCAN                        | FK_TX_INTEREST_ACCRUE_LOAN_ACC |    501 |     67 | 40581 |00:00:00.14 |   42084 |    451 |       |       |          |
Predicate Information (identified by operation id):
   2 - access("XX"."COLLECTIBILITY_CODE"=:B1)
       filter("XX"."COLLECTIBILITY_CODE"=:B1)
   4 - access("LOAN_ACCOUNT_ID"=:B1 AND "INSTALLMENT_NUMBER"=1)
   6 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
   8 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
10 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
12 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
14 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
16 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
18 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
20 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
21 - filter(TO_NUMBER("COL"."COLLECTIBILITY_CODE")=:B1)
26 - access("from$_subquery$_016"."CURRENCY_CODE"="CURR"."CURRENCY_CODE")
27 - filter(UPPER("CURR"."STATUS")='A')
28 - access("from$_subquery$_016"."AGREEMENT_ID"="A"."AGREEMENT_ID")
29 - access("A"."MULTIFINANCE_ID"="MF"."MULTIFINANCE_ID")
31 - access("MF"."SYS_NC00052$"='A')
32 - filter(UPPER("A"."STATUS")='A')
34 - access("LA"."TENANT_ID"="TENANT_ID")
36 - access("TENANT_PARAMETER_ID"=23)
37 - filter((UPPER("LA"."LOAN_STATUS")='AC' OR ("LA"."CLOSED_DATE"=TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
              UPPER("LA"."LOAN_STATUS")='CN')))
38 - access("LA"."SYS_NC00118$"='A')
39 - filter(("TP"."APPROVAL_DATE"=TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "TP"."DATA_SOURCE"=152 AND UPPER("TP"."APPROVAL_STATUS")='A'))
40 - access("TP"."LOAN_ACCOUNT_ID"="from$_subquery$_016"."LOAN_ACCOUNT_ID")
42 - access("DCO"."LOAN_CONTRACT_NUMBER"="from$_subquery$_016"."CONTRACT_NUMBER")
43 - filter(UPPER("MC"."STATUS")='A')
44 - access("from$_subquery$_016"."MF_CUSTOMER_ID"="MC"."MF_CUSTOMER_ID")
45 - filter("IA"."ACCRUE_DATE"="XX"."PREV_DATE")
46 - access("LA"."LOAN_ACCOUNT_ID"="IA"."LOAN_ACCOUNT_ID")
The DBMS_XPLAN.DISPLAY_CURSOR output after : alter system flush buffer_cache; alter system flush shared_pool;
Query no 2
PLAN_TABLE_OUTPUT
SQL_ID cxmg4jfvr9pz0, child number 0
SELECT /*+ gather_plan_statistics */ la.office_code, la.currency_code AS currency, mf.NAME multifinance_id,        la.contract_number, mc.customer_name,
dco.os_principal_on_schedule AS os_principal_on_schedule,        f_get_param_value (la.financing_type,                           'FinancingType'
       ) AS financing_type,        CASE la.financing_type           WHEN 11                    -- Asset Purchase              THEN NVL (tp.os_principal_cust,
                  la.os_principal_cust                       )           WHEN 12                                            -- JF Channelling              THEN
NVL (tp.os_principal_mf, la.os_principal)        END AS os_principal_actual,        CASE           WHEN dco.bi_collectibility_with_gp >= 3              THEN 0
      ELSE CASE           WHEN la.financing_type = '12'              THEN   NVL (ia.accrue_interest_pl, 0)                   + NVL (ia.accrue_interest_npl, 0)
      ELSE   NVL (ia.accrue_
Plan hash value: 2072372033
| Id | Operation                            | Name                           | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT                     |                                | 4719 | 1622K|   188K (32)| 00:37:42 |       |       |
|   1 | TABLE ACCESS BY INDEX ROWID         | COLLECTIBILITY_CODE            |     1 |    12 |     3   (0)| 00:00:01 |       |       |
|* 2 |   INDEX SKIP SCAN                    | UNQ_COLLECTIBILITY_CODE        |     1 |       |     2   (0)| 00:00:01 |       |       |
|   3 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 4 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
|   5 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    15 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 6 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
|   7 |   TABLE ACCESS BY GLOBAL INDEX ROWID | CUST_SCH_INSTALLMENT           |     1 |    15 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 8 |    INDEX UNIQUE SCAN                 | UNQ_CUST_SCH_INSTALLMENT1      |     1 |       |     2   (0)| 00:00:01 |       |       |
|   9 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    15 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 10 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
| 11 |   TABLE ACCESS BY GLOBAL INDEX ROWID | CUST_SCH_INSTALLMENT           |     1 |    15 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 12 |    INDEX UNIQUE SCAN                 | UNQ_CUST_SCH_INSTALLMENT1      |     1 |       |     2   (0)| 00:00:01 |       |       |
| 13 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 14 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
| 15 |   TABLE ACCESS BY GLOBAL INDEX ROWID | CUST_SCH_INSTALLMENT           |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 16 |    INDEX UNIQUE SCAN                 | UNQ_CUST_SCH_INSTALLMENT1      |     1 |       |     2   (0)| 00:00:01 |       |       |
| 17 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 18 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
| 19 |   TABLE ACCESS BY GLOBAL INDEX ROWID | CUST_SCH_INSTALLMENT           |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 20 |    INDEX UNIQUE SCAN                 | UNQ_CUST_SCH_INSTALLMENT1      |     1 |       |     2   (0)| 00:00:01 |       |       |
|* 21 | TABLE ACCESS FULL                   | COLLECTIBILITY_CODE            |     1 |    12 |     3   (0)| 00:00:01 |       |       |
| 22 | NESTED LOOPS                        |                                | 4719 | 1622K|   188K (32)| 00:37:42 |       |       |
| 23 |   NESTED LOOPS                       |                                | 4719 | 1460K|   183K (33)| 00:36:45 |       |       |
| 24 |    NESTED LOOPS OUTER                |                                | 4719 | 1354K|   180K (33)| 00:36:07 |       |       |
| 25 |     NESTED LOOPS OUTER               |                                | 4719 | 1225K|   130K (46)| 00:26:01 |       |       |
|* 26 |      HASH JOIN                       |                                | 4719 | 1106K| 23591   (2)| 00:04:44 |       |       |
| 27 |       TABLE ACCESS BY INDEX ROWID    | MULTIFINANCE                   |     5 |   130 |     2   (0)| 00:00:01 |       |       |
|* 28 |        INDEX RANGE SCAN              | IDX_STATUS_MF                  |     5 |       |     1   (0)| 00:00:01 |       |       |
|* 29 |       HASH JOIN                      |                                | 8494 | 1775K| 23589   (2)| 00:04:44 |       |       |
|* 30 |        TABLE ACCESS FULL             | AGREEMENT                      |    18 |   360 |     3   (0)| 00:00:01 |       |       |
|* 31 |        HASH JOIN                     |                                | 8494 | 1609K| 23585   (2)| 00:04:44 |       |       |
|* 32 |         TABLE ACCESS FULL            | CURRENCY                       |     1 |     4 |     3   (0)| 00:00:01 |       |       |
| 33 |         VIEW                         |                                |   212K|    38M| 23579   (2)| 00:04:43 |       |       |
|* 34 |          HASH JOIN RIGHT OUTER       |                                |   212K|    32M| 23579   (2)| 00:04:43 |       |       |
| 35 |           TABLE ACCESS BY INDEX ROWID| TENANT_PARAMETER               |     1 |    74 |     1   (0)| 00:00:01 |       |       |
|* 36 |            INDEX UNIQUE SCAN         | PK_TENANT_PARAMETER            |     1 |       |     0   (0)| 00:00:01 |       |       |
| 37 |           PARTITION LIST ALL         |                                |   212K|    17M| 23575   (2)| 00:04:43 |     1 |     5 |
|* 38 |            TABLE ACCESS FULL         | LOAN_ACCOUNT_HAN               |   212K|    17M| 23575   (2)| 00:04:43 |     1 |     5 |
| 39 |      TABLE ACCESS BY INDEX ROWID     | TX_INTEREST_ACCRUE             |     1 |    26 |   130K (46)| 00:26:01 |       |       |
| 40 |       BITMAP CONVERSION TO ROWIDS    |                                |       |       |            |          |       |       |
| 41 |        BITMAP AND                    |                                |       |       |            |          |       |       |
| 42 |         BITMAP CONVERSION FROM ROWIDS|                                |       |       |            |          |       |       |
|* 43 |          INDEX RANGE SCAN            | FK_TX_INTEREST_ACCRUE_LOAN_ACC |    67 |       |     0   (0)| 00:00:01 |       |       |
| 44 |         BITMAP CONVERSION FROM ROWIDS|                                |       |       |            |          |       |       |
|* 45 |          INDEX RANGE SCAN            | IDX_TX_INTEREST_ACCRUE         |    67 |       |    12 (100)| 00:00:01 |       |       |
|* 46 |     TABLE ACCESS BY INDEX ROWID      | TX_PAYMENT                     |     1 |    28 |    11   (0)| 00:00:01 |       |       |
|* 47 |      INDEX RANGE SCAN                | FK_TX_PAY_LOAN_ACCT            |    12 |       |     0   (0)| 00:00:01 |       |       |
| 48 |    TABLE ACCESS BY INDEX ROWID       | DL_CL_OUTSTANDING              |     1 |    23 |     1   (0)| 00:00:01 |       |       |
|* 49 |     INDEX RANGE SCAN                 | IDXLO_CNUM                     |     1 |       |     0   (0)| 00:00:01 |       |       |
|* 50 |   TABLE ACCESS BY INDEX ROWID        | MF_CUSTOMER                    |     1 |    35 |     1   (0)| 00:00:01 |       |       |
|* 51 |    INDEX UNIQUE SCAN                 | MF_CUSTOMER_PK                 |     1 |       |     0   (0)| 00:00:01 |       |       |
Predicate Information (identified by operation id):
   2 - access("XX"."COLLECTIBILITY_CODE"=:B1)
       filter("XX"."COLLECTIBILITY_CODE"=:B1)
   4 - access("LOAN_ACCOUNT_ID"=:B1 AND "INSTALLMENT_NUMBER"=1)
   6 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
   8 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
10 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
12 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
14 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
16 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
18 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
20 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
21 - filter(TO_NUMBER("COL"."COLLECTIBILITY_CODE")=:B1)
26 - access("A"."MULTIFINANCE_ID"="MF"."MULTIFINANCE_ID")
28 - access(UPPER("STATUS")='A')
29 - access("from$_subquery$_016"."AGREEMENT_ID"="A"."AGREEMENT_ID")
30 - filter(UPPER("A"."STATUS")='A')
31 - access("from$_subquery$_016"."CURRENCY_CODE"="CURR"."CURRENCY_CODE")
32 - filter(UPPER("CURR"."STATUS")='A')
34 - access("LA"."TENANT_ID"="TENANT_ID"(+))
36 - access("TENANT_PARAMETER_ID"(+)=23)
38 - filter((UPPER("LA"."LOAN_STATUS")='AC' OR "LA"."CLOSED_DATE"=TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss')
              AND UPPER("LA"."LOAN_STATUS")='CN') AND UPPER("LA"."STATUS")='A')
43 - access("LA"."LOAN_ACCOUNT_ID"="IA"."LOAN_ACCOUNT_ID"(+))
45 - access("IA"."ACCRUE_DATE"(+)="XX"."PREV_DATE")
46 - filter("TP"."APPROVAL_DATE"(+)=TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "TP"."DATA_SOURCE"(+)=152
              AND UPPER("TP"."APPROVAL_STATUS"(+))='A')
47 - access("TP"."LOAN_ACCOUNT_ID"(+)="from$_subquery$_016"."LOAN_ACCOUNT_ID")
49 - access("DCO"."LOAN_CONTRACT_NUMBER"="from$_subquery$_016"."CONTRACT_NUMBER")
50 - filter(UPPER("MC"."STATUS")='A')
51 - access("from$_subquery$_016"."MF_CUSTOMER_ID"="MC"."MF_CUSTOMER_ID")Typically both query running on 10-12 seconds (or same execution time).
And I can't provide autotrace and tkprof output cause I cannot access via sqlplus.
Thanks very much for the link HOW TO: Post a SQL statement tuning request - template posting
Regards,
Sigcle
Edited by: SigCle on Feb 25, 2013 4:22 AM

CTM does not consider orders from ECC process, to calculate the master production plan

Hi gurus, Any of you worked in a scenario where CTM should consider the process firm orders from ECC? I am currently working on a stage of planning, whereby CTM should consider orders from fixed ECC, as projected inventory available for the planning of needs. However at present not the underway. any idea or suggestion? Thank

Hello:
Thanks for the prompt reply. Unfortunately, profile selection orders, are all ATP category.
Here I put an example of behavior that has the result set of CTM
SCENARIO CTM
WEEKS
INITIAL
1
2
3
4
5
6
DEMAND
-100
-100
-100
-100
-100
-100
PRODUCTION (PLANNED)
100
100
100
100
100
50
PRODUCTION (FIXED)
50
STOCK
0
50
50
50
50
0
SCENARIO EXPECTED
WEEKS
INITIAL
1
2
3
4
5
6
DEMAND
-100
-100
-100
-100
-100
-100
PRODUCTION (PLANNED)
100
50
100
100
100
100
PRODUCTION (FIXED)
50
STOCK
0
0
0
0
0
0
thanks for your comments

MRP II in Production Planning and Control

Dear all,
I am studing SAP Production planning and control. What is Manufacturing Resource Planning (MRP II) and what is the role of MRP II in PPC? What all modules MRP II covers in ERP?
Thanks in advance
Jenisha

Hi,
MRP-II includes following SAP modules:
Materials Management
Production Processes
Quality Management
Product Costing
The end result of MRP that supports enhanced inventory tracking, limited product and project costing, quality management, and process order management. Despite its complexity, the system is both flexible and easy to use.

Optimizer creating high production plan in few buckets

Hi,
Optimizer is creating high production plan in few buckets though there is less demand.
Findings
1. system in not preplanning to cover future demand.
2. there is one resource used by three different products for one product optimizer is doing excess planning while it is showing supply shortage for other products.
3.If I again take optimizer run for all the three products at all the location system is giving correct results (all receipt elements in line with the demand.
Now i need to understand the reasons why optimizer gave high production plan in last run ?
Regards
Abhi

1. system in not preplanning to cover future demand.
check storage cost and penalty cost , i think storage cost is more then penalty cost.
2. there is one resource used by three different products for one product optimizer is doing excess planning while it is showing supply shortage for other products.
if you run all three one by one it plan only first product on that particular resource, if you run all three same time system will plan according to the cost optimisation logic, that means it checks all cost and calculate which product needs to be manufacture on that resource and how much.
you can check the log of snp optimisation run in
/SAPAPO/SNPOPLOG - SNP Optimizer Log Data

Production Plan Generation Issue

Hi Gurus,
Scenario: I am running SNP heuristics to generate production plan at plane level. before making the same I made GR time for that SKU_Plant combination "0" to ensure start date and end date of production plan generation should be same and also made SNP checking horizon for eg. 5 days to ensure PP should generate on 6th day.
Result: PP is generating within SNP checking horizon i.e PP is seating on 4th day which I don't want.
Please suggest what settings to be maintained for my desired result.
Thanks
Prasanta

Hi Prasanta,
normally SNP heuristic enhance the validity of the source of supplies, i.e. here PDS or PPM considering the production horizon. Could it be that you are looking the data in interactive planning in local time zone hence you see it in the production horizon? What is the time you see in the detail view in interactive planning, is it 23:59:59 or something else?
Could you please provide a screenshot of your data in planning book with the detail view opened on the order? Of course execute SNP heuristic before provide such screenshot.
Best regards,
Cyrille.

Sales order reference at the time of Production Planning

Hi all,
Is there any Hard check (or) Validation at the time of assigning sales order in Production order?
to be more specific
At the time of creating production plann, we assign open sales order to that. Again if new production plan is created and with out knowing if he assign the same Sales order number system should block it.
Is there any solution for this
Regards
Shashi

Shashi,
Couple of important things to be noted.
1. How could you determine if the first user linking the SO to the Production Order really selected the correct one. It could be very much possible that the same Sales Order linked to the another Prod Order is actually correct.
Unless you have a business validation procedure to check this it will not be of much value to prevent duplicated.
You can read about the transaction notification stored procedure using the link below
https://service.sap.com/sap/support/notes/1011154
This transaction notification is a stored procedure available in a company database and can be accessed from SQL Server Management Studio
Suda

Table for Product Plan Status

Hi,
In "Basic Data" tab of Product Plan Detail, there's Status field which is the "User" status for the Product Plan. I am looking for the table which contains this Status field. DPR_PROJECT table only contain "System" Status field.
Thanks & Regards,
Tony

Hi
PO status is stored in Structure not in the table.
Please use the List displays to get the information like ME2N,ME2L, ME2M, ME2K etc
You can also get the information from the table EKKO, EKPO, EKET,EKBE
Hope it helps
thanks/karthik

Sending Production Plan to Vendor / Supplier

Dear Sir
Ours is a production unit (assembly line) we use lot of components. So I want to know is it possible to send plan directly to Vendor by E-mail from SAP.
Thanks & Regards
Vishal

Hi Vishal,
Sending out Production Plan to Vendors by email is possible but given nature of dataset involved (not documents in form of Production Orders) it may not be a very feasible option. Instead either develop a report to extract relevant Production Plan data and send it out as email.
But better look at Supply Chain Collaboration applications like SNC Supply Network Collaboration that has Outsourced Manufacturing processes catering to these kind of supplier / vendor collaboration requirements.
Hope this helps.
Somnath

Daily production plan in manufacturing shop floor

Hi, we want to generate 2 different weekly production plans based on 1) roh available 2)customer delivery date. pls advise how to generate same.

Hi
There is no planning method in SAP based on raw materials. if you know how much finished product can be made out of one raw material then you can use SOP and create a prodcution plan as inactive version.
For customer delivery date, if you know the cumulative requirements then place this quantity in SOP as the sales plan with delivery dates and create synchronous production plan and save it as another inactive version.
Once you take a decision on which version to be used you can copy the version to a active version and transfer to demand managment and run mrp which creates planned orders.
Make sure you use backward scheduling in the material master
Thanks
Krishna

G/L's in production planning

Dear all,
i have on question kindly answer me if any one knows.
in standared practies of (SAP) PRODUCTION PLANNING how maney G/L's has to be assigned and what are they.
thanks in advance.
best regards,
irfan

HI
generally it depends on your production process. at the time of implementation, consultant maps as per the requirments given by FI team
for example if you have production stages like finished product(stage 1 ,stage 2) this willl have one GLs,other semifinished (stahes) will havwe GLs, RMs,and consumptions GLs,GRs GLS etc.
-ashok

Production Planning Report

Hi,
My Requirement is This report should provide comparision of Standard V/s Actual Machine hours utilization for a particular resource or for all the resources utilized in a given period and its variance. If the variance percentage is more than 10% it should be highlighted in Red colour as it is an area having potential / scope for improvement.
For this Scenerio please give me solution and tell me which info cubes, data sources , info objects i have to take please tell me i am new to production planning.
Thanks & regards,
Rajesh.

Hi,
Check below thread for more information,
[Production planning Business Content Data sources and cubes;
Regards,
Durgesh.

SAP PP (Production Planning) Master Data Definitions

SAP PP (Production Planning) Master Data Definitions and Transaction codes.

SAP PP (Production Planning) Master Data Definitions
• Factory Calendar
• Material Master
• Resource • Bills of Material (BOM)
• Production versions
• Master recipe
Factory Calendar: The factory calendar is defined on the basis of a public holiday calendar. The public holiday and factory calendar is a central module in the SAP System. It is assigned to a specific plant during the initial system setup and therefore used in many areas (e.g. in Logistics and in Human Resources) in the system.
Material Master: Material master comprises if all the basic data of the material for each department. The data covers all the relevant information required for the transactional flow e.g. sales, Planning, Production, Quality, Purchasing, Costing etc. Material master covers all the descriptive and control data and the flow of information depends on fields maintained within it. The integration of all material data in a single database object eliminates redundant data storage. Material Masters are created once and can be changed or extended whenever required
Bill of Materials: Bill of Materials or commonly called BOM is a formally structured list of components that make up a product or assembly. The list contains the material number of the component together with the quantity and unit of measure. BOMs are used in their different forms in various situations where a finished product is assembled from several component parts or materials. Resources: Resources are production facilities and persons involved in a production process that have capacities. They are subdivided into categories to specify their suitability for certain purposes or their use in certain processes
Product Versions: A production version determines which alternative BOM is used together with which task list/master recipe to produce a material or create a master production schedule. For one material, we can have several production versions for various validity periods and lot-size ranges. The production version determines the following:
• The BOM alternative for a BOM explosion.
• The task list (master recipe) and any alternate, as needed.
• Lot-size restrictions and validity parameters.
Master Recipes: A master recipe defines the following data that is required for the production of materials without relating to a particular order: processing steps, resources, material components, and control information for the process control level. Master Recipe enables to plan the production of materials (products). Therefore, Master Recipe is used as a template for process orders and run schedules as well as a basis for product costing. In a Recipe
• The Phases (work steps) to be carried out during production.
• The activities to be performed in the operations as a basis for determining dates, capacity requirements and costs.
• The use of materials during production.
• The use of resource.

Clear the History Data Automatically in Production Planning Table MF50

Dear Friends,
I have the problem to set the Production Planning Table (Txn MF50) to
clear the history data automatically. Currently, all the history data
in the planning table has to be cleared manually.
Appreciate your help.
Rgds
Zahari Yusof

instead of just removing the whole history like private browsing do, i just want to remove browsing/download history and form&search. i didn't want to remove cookies and active logins, heheh. thank you

Unexpected result of Production Plan

Similar Messages

Maybe you are looking for