Planning considering the expiry of materials

Dear All ,
We belong to Pharmaceutical industry .We want to carry out material requirement planning for raw materials considering the expiry dates of raw materials .The materials which are due to expire in say next two months should not be considered in planning as unrestricted stock . Kindly suggest the config and master settings for this requirement .

HI
MRP will not check expiry related logics.
it will chekc wether the stock is there or not.
better you need to run the deadline monitoring in back ground that is QA07.
for that your materials should have the batch classification data.
and at the time of GRNs systen will update the expiry dates in the BTCHES.(in material master you need to maintain the shelf life)
So at the time of ruuning the QA07 system will transfer to blocked stock ( all the materials which are expired).
-ashok

Similar Messages

  • Will a explain plan consider a function in a select statement.

    Hi gurus,
    I have a question regarding explain plan.
    I ran a query, which returns me explain plan with multiple CPU costs around 300K.
    now i use a function, and the number of lines displayed in explain plan reduces from 12 to 8 lines.
    What i dont understand is.. Is the explain plan considering the function in the select statement ?
    ex.
    explain plan for
    select column1,
             column2,
             function(value1)
    from case
    where case_no = 1will a explain plan consider the functions in a select statement ?
    Thank you.

    What i dont understand is.. Is the explain plan considering the function in the select statement ?Maybe there are tweaks which reveal more information from the explain plan, but a straightforward way won't necessarily expose any function call:
    SQL> create or replace function get_dname (i_deptno integer)
       return varchar2
    as
       l_dname   dept.dname%type;
    begin
       select   dname
         into   l_dname
         from   dept
        where   deptno = i_deptno;
       return l_dname;
    end get_dname;
    Function created.
    SQL> explain plan
       for
          select   ename, deptno, get_dname (deptno) dname
            from   emp
           where   deptno = 10
    Explain complete.
    SQL> select   * from table (dbms_xplan.display ())
    PLAN_TABLE_OUTPUT                                                                                                                                    
    Plan hash value: 3956160932                                                                                                                          
    | Id  | Operation         | Name | Rows  | Bytes | Cost (%CPU)| Time     |                                                                           
    |   0 | SELECT STATEMENT  |      |     5 |    45 |     3   (0)| 00:00:01 |                                                                           
    |*  1 |  TABLE ACCESS FULL| EMP  |     5 |    45 |     3   (0)| 00:00:01 |                                                                           
    Predicate Information (identified by operation id):                                                                                                  
       1 - filter("DEPTNO"=10)                                                                                                                           
    13 rows selected.
    SQL> truncate table plan_table
    Table truncated.
    SQL> explain plan
       for
          select   ename, deptno
            from   emp
           where   deptno = 10
    Explain complete.
    SQL> select   * from table (dbms_xplan.display ())
    PLAN_TABLE_OUTPUT                                                                                                                                    
    Plan hash value: 3956160932                                                                                                                          
    | Id  | Operation         | Name | Rows  | Bytes | Cost (%CPU)| Time     |                                                                           
    |   0 | SELECT STATEMENT  |      |     5 |    45 |     3   (0)| 00:00:01 |                                                                           
    |*  1 |  TABLE ACCESS FULL| EMP  |     5 |    45 |     3   (0)| 00:00:01 |                                                                           
    Predicate Information (identified by operation id):                                                                                                  
       1 - filter("DEPTNO"=10)                                                                                                                           
    13 rows selected.

  • How to consider the Purchase Orders in Long Term Planning

    Hi All,
    I wanted to include the Purchase Orders of Finished Material in Long Term Planning.
    I have selected the check box "Long-term planning: include firmed issues and receipts" in the Planning Scenario  but after LTP run system is not considering the Purchase Orders of Finished Materials for Planning.
    Regards,
    Shailendra
    Edited by: Shailendra Hadkar on Apr 5, 2010 12:41 PM

    Dear,
    Could you please explain usage of purchase orders for Finished product?
    Regards,
    SAP CONS

  • HT4285 i have been using my mac book pro for almost an year..My  use is pretty safe as i use it only at my home and do not carry it at office... my sues is shall i consider the APPLECARE PLAN....the plan is almost 20% of the laptops cost.

    i have been using my mac book pro for more than 11 months.
    .My  use is pretty safe as i use it only at my home and do not carry it to office...
    my  confusion is that shall i consider the APPLECARE PLAN....the plan is almost 20% of the laptops cost....Will spending so much money be worth it

    Like any other insurance, it's only worth it if you have a problem.  I've purchased it on my "high risk" Macs and not purchased on the others.  So far I've never needed it. 

  • Consider the pending PO and Purchase requisition fore cast base planning (vv)

    Dear friends,
    Our client at presently they are using Forecast  based planning for RAW material , in that requirement will not consider Pending Pur req and PO, Is that any option for consider pending PO for Forecast based planning , kindly do the needful.
    Regards,
    Sabhapathy R

    Hello Sabhapathy,
    I am not sure why you would need to consider pending PurReqs and POs. These pending documents are considered during the MRP run, but not to generate the forecast.
    Forecast-based planning is based on material consumption.
    The MRP will generate PurReq or Planner Orders considering the open documents. For example:
    + Current stock  = 1000 CS
    + Open PRs and POs to arrive = 400 CS
    - Forecast Requirement =1500 CS
    - Safety Stock policies = 100 CS (safety stok)
    - New replenishment orders = 200 CS
    Thanks and Regards,
    Mariano

  • Can system consider the unrestricted stock when planned with MD50???

    Hi,
    We have scinerio where FERT with Strategy 20 (MTO Process) is planned with MD50 against the sale oder. Every time Dependent items stock needs to be posted with Movement type 412E against that sale order or else dependent items stock though available in unrestricted is shown as unable against that sale order no. Enitre cost of the FERT material is accounted against sale order number.
    Can we avoid posting of sales order stock?? can we make system to consider the unrestricted stock when planned with MD50.
    Thanks in advance,
    Regards,
    John

    if u want to consume the unrestricted stock, why u implemented MTO??
    what was the requirement to implement MTO, when u r asking such question in support............
    check first requirement of the client.......if u think they need to consume unresc stock...i will say...implentation was very poor,
    regards,
    Pravin M

  • The system is not considering the free stock in planning strategy grp - 25

    Dear Frndz,
    The system is not considering the free stock of child items available in the system.For the parent item, I have maintained a planning srategy of 25 (Make to order variant config).My client would like the system to consider the free stock available for child items.pls help me...
    Regards,
    Srini

    Dear,
    Strategy 25 will not consider the existing stock.
    What you enter in MRP4 view ind/collective rquirement is applicable only for dependent requirement.
    Also refer this thread?
    Re: Strategy group 20
    Run MRP in MD50 and then MD02 with palnning mode 3 deleted and recreated and check your result.
    Regards,
    R.Brahmankar

  • Assignments of materials and vendors to inspection plans for the plant 1500

    Hi to all,
    Please give me solution for make assignments of materials and vendors to inspection plans for the plant 1500.
    Thanks,
    NAgesh

    hi gang,
    try to make usage decision ,kindly check in material document which you have created while making the GR, check in which storgare location you have specified and try to transfer the stock from quality to unrestricted.and also make a note on batch number also if you have activated the batch management
    regards
    thyagarajan

  • CM38 considering orders of operative planning on the simulative scenu00E1rio

    Dear friends,
    I'm trying to use the T-code CM38 to analise the capacity load of one LTP planning, but this transaction is taking into account some production orders of the operative planning.
    I already checked in T-code MS32 to be sure that my planning scenario is not considering the "receipts", and all those options is not flagged.
    I'm using the profile SAPPLAN01 or YBLTP01 to analise the capacity on CM38.
    How can I see only the capacity load of simulation orders (my LTP scenario orders) in this transaction? Is it possible?

    Hello,
    Your question should go to ERP  Manufacturing (PP)  forum [SAP ERP Manufacturing - Production Planning (SAP PP);
    This forum is for SAP Manufacturing Execution.
    Thanks

  • CM38 considering orders of operative planning on the simulative scenario

    Dear friends,
    I'm trying to use the T-code CM38 to analise the capacity load of one LTP planning, but this transaction is taking into account some production orders of the operative planning.
    I already checked in T-code MS32 to be sure that my planning scenario is not considering the "receipts", and all those options is not flagged.
    I'm using the profile SAPPLAN01 or YBLTP01 to analise the capacity on CM38.
    How can I see only the capacity load of simulation orders (my LTP scenario orders) in this transaction? Is it possible?
    Thanks in advance,
    Rodrigo

    Dear Rodrigo,
    In CM38,under detailed settings check whether this planning scenario is mentioned before entering into the capacity details.
    Also refer this thread,
    Re: Capacity planning
    Check and revert
    Regards
    S Mangalraj

  • CBO generating different plans for the same data in similar Environments

    Hi All
    I have been trying to compare an SQL from 2 different but similar environments build of the same hardware specs .The issue I am facing is environment A, the query executes in less than 2 minutes with plan mostly showing full table scans and hash join whereas in environment B(problematic), it times out after 2 hours with an error of unable to extend table space . The statistics are up to date in both environments for both tables and indexes . System parameters are exactly similar(default oracle for except for multiblock_read_count ).
    Both Environment have same db parameter for db_file_multiblock_read_count(16), optimizer(refer below),hash_area_size (131072),pga_aggregate_target(1G),db_block_size(8192) etc . SREADTIM, MREADTIM, CPUSPEED, MBRC are all null in aux_stats in both environment because workload was never collected i believe.
    Attached is details about the SQL with table stats, SQL and index stats my main concern is CBO generating different plans for the similar data and statistics and same hardware and software specs. Is there any thing else I should consider .I generally see environment B being very slow and always plans tend to nested loops and index scan whereas what we really need is a sensible FTS in many cases. One of the very surprising thing is METER_CONFIG_HEADER below which has just 80 blocks of data is being asked for index scan.
    show parameter optimizer
    optimizer_dynamic_sampling integer 2
    optimizer_features_enable string 10.2.0.4
    optimizer_index_caching integer 0
    optimizer_index_cost_adj integer 100
    optimizer_mode string ALL_ROWS
    optimizer_secure_view_merging boolean TRUE
    **Environment**
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE     10.2.0.4.0     Production
    TNS for Solaris: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    Note: : There are slight difference in the no of records in the attached sheet.However, I wanted to tell that i have tested with exact same data and was getting similar results but I couldn't retain the data untill collecting the details in the attachment
    TEST1     COMPARE TABLE LEVE STATS  used by CBO          
    ENVIRONMENT A
    TABLE_NAME     NUM_ROWS     BLOCKS     LAST_ANALYZED
    ASSET     3607425     167760     5/02/2013 22:11
    METER_CONFIG_HEADER     3658     80     5/01/2013 0:07
    METER_CONFIG_ITEM     32310     496     5/01/2013 0:07
    NMI     1899024     33557     18/02/2013 10:55
    REGISTER     4830153     101504     18/02/2013 9:57
    SDP_LOGICAL_ASSET     1607456     19137     18/02/2013 15:48
    SDP_LOGICAL_REGISTER     5110781     78691     18/02/2013 9:56
    SERVICE_DELIVERY_POINT     1425890     42468     18/02/2013 13:54
    ENVIRONMENT B
    TABLE_NAME     NUM_ROWS     BLOCKS     LAST_ANALYZED
    ASSET     4133939     198570     16/02/2013 10:02
    METER_CONFIG_HEADER     3779     80     16/02/2013 10:55
    METER_CONFIG_ITEM     33720     510     16/02/2013 10:55
    NMI     1969000     33113     16/02/2013 10:58
    REGISTER     5837874     120104     16/02/2013 11:05
    SDP_LOGICAL_ASSET     1788152     22325     16/02/2013 11:06
    SDP_LOGICAL_REGISTER     6101934     91088     16/02/2013 11:07
    SERVICE_DELIVERY_POINT     1447589     43804     16/02/2013 11:11
    TEST ITEM 2     COMPARE INDEX STATS  used by CBO          
    ENVIRONMENT A
    TABLE_NAME     INDEX_NAME     UNIQUENESS     BLEVEL     LEAF_BLOCKS     DISTINCT_KEYS     AVG_LEAF_BLOCKS_PER_KEY     AVG_DATA_BLOCKS_PER_KEY     CLUSTERING_FACTOR     NUM_ROWS
    ASSET     IDX_AST_DEVICE_CATEGORY_SK     NONUNIQUE     2     9878     67     147     12982     869801     3553095
    ASSET     IDX_A_SAPINTLOGDEV_SK     NONUNIQUE     2     7291     2747     2     639     1755977     3597916
    ASSET     SYS_C00102592     UNIQUE     2     12488     3733831     1     1     3726639     3733831
    METER_CONFIG_HEADER     SYS_C0092052     UNIQUE     1     12     3670     1     1     3590     3670
    METER_CONFIG_ITEM     SYS_C0092074     UNIQUE     1     104     32310     1     1     32132     32310
    NMI     IDX_NMI_ID     NONUNIQUE     2     6298     844853     1     2     1964769     1965029
    NMI     IDX_NMI_ID_NK     NONUNIQUE     2     6701     1923072     1     1     1922831     1923084
    NMI     IDX_NMI_STATS     NONUNIQUE     1     106     4     26     52     211     211
    REGISTER     REG_EFFECTIVE_DTM     NONUNIQUE     2     12498     795     15     2899     2304831     4711808
    REGISTER     SYS_C00102653     UNIQUE     2     16942     5065660     1     1     5056855     5065660
    SDP_LOGICAL_ASSET     IDX_SLA_SAPINTLOGDEV_SK     NONUNIQUE     2     3667     1607968     1     1     1607689     1607982
    SDP_LOGICAL_ASSET     IDX_SLA_SDP_SK     NONUNIQUE     2     3811     668727     1     2     1606204     1607982
    SDP_LOGICAL_ASSET     SYS_C00102665     UNIQUE     2     5116     1529606     1     1     1528136     1529606
    SDP_LOGICAL_REGISTER     SYS_C00102677     UNIQUE     2     17370     5193638     1     1     5193623     5193638
    SERVICE_DELIVERY_POINT     IDX_SDP_NMI_SK     NONUNIQUE     2     4406     676523     1     2     1423247     1425890
    SERVICE_DELIVERY_POINT     IDX_SDP_SAP_INT_NMI_SK     NONUNIQUE     2     7374     676523     1     2     1458238     1461108
    SERVICE_DELIVERY_POINT     SYS_C00102687     UNIQUE     2     4737     1416207     1     1     1415022     1416207
    ENVIRONMENT B
    TABLE_NAME     INDEX_NAME     UNIQUENESS     BLEVEL     LEAF_BLOCKS     DISTINCT_KEYS     AVG_LEAF_BLOCKS_PER_KEY     AVG_DATA_BLOCKS_PER_KEY     CLUSTERING_FACTOR     NUM_ROWS
    ASSET     IDX_AST_DEVICE_CATEGORY_SK     NONUNIQUE     2     8606     121     71     16428     1987833     4162257
    ASSET     IDX_A_SAPINTLOGDEV_SK     NONUNIQUE     2     8432     1780146     1     1     2048170     4162257
    ASSET     SYS_C00116157     UNIQUE     2     13597     4162263     1     1     4158759     4162263
    METER_CONFIG_HEADER     SYS_C00116570     UNIQUE     1     12     3779     1     1     3734     3779
    METER_CONFIG_ITEM     SYS_C00116592     UNIQUE     1     107     33720     1     1     33459     33720
    NMI     IDX_NMI_ID     NONUNIQUE     2     6319     683370     1     2     1970460     1971313
    NMI     IDX_NMI_ID_NK     NONUNIQUE     2     6597     1971293     1     1     1970771     1971313
    NMI     IDX_NMI_STATS     NONUNIQUE     1     98     48     2     4     196     196
    REGISTER     REG_EFFECTIVE_DTM     NONUNIQUE     2     15615     1273     12     2109     2685924     5886582
    REGISTER     SYS_C00116748     UNIQUE     2     19533     5886582     1     1     5845565     5886582
    SDP_LOGICAL_ASSET     IDX_SLA_SAPINTLOGDEV_SK     NONUNIQUE     2     4111     1795084     1     1     1758441     1795130
    SDP_LOGICAL_ASSET     IDX_SLA_SDP_SK     NONUNIQUE     2     4003     674249     1     2     1787987     1795130
    SDP_LOGICAL_ASSET     SYS_C004520     UNIQUE     2     5864     1795130     1     1     1782147     1795130
    SDP_LOGICAL_REGISTER     SYS_C004539     UNIQUE     2     20413     6152850     1     1     6073059     6152850
    SERVICE_DELIVERY_POINT     IDX_SDP_NMI_SK     NONUNIQUE     2     3227     660649     1     2     1422572     1447803
    SERVICE_DELIVERY_POINT     IDX_SDP_SAP_INT_NMI_SK     NONUNIQUE     2     6399     646257     1     2     1346948     1349993
    SERVICE_DELIVERY_POINT     SYS_C00128706     UNIQUE     2     4643     1447946     1     1     1442796     1447946
    TEST ITEM 3     COMPARE PLANS     
    ENVIRONMENT A
    Plan hash value: 4109575732                                             
    | Id  | Operation                       | Name                   | Rows  | Bytes |TempSpc| Cost (%CPU)| Time     |                                             
    |   0 | SELECT STATEMENT                |                        |    13 |  2067 |       |   135K  (2)| 00:27:05 |                                             
    |   1 |  HASH UNIQUE                    |                        |    13 |  2067 |       |   135K  (2)| 00:27:05 |                                             
    |*  2 |   HASH JOIN                     |                        |    13 |  2067 |       |   135K  (2)| 00:27:05 |                                             
    |*  3 |    HASH JOIN                    |                        |     6 |   900 |       |   135K  (2)| 00:27:04 |                                             
    |*  4 |     HASH JOIN ANTI              |                        |     1 |   137 |       |   135K  (2)| 00:27:03 |                                             
    |*  5 |      TABLE ACCESS BY INDEX ROWID| NMI                    |     1 |    22 |       |     5   (0)| 00:00:01 |                                             
    |   6 |       NESTED LOOPS              |                        |     1 |   131 |       | 95137   (2)| 00:19:02 |                                             
    |*  7 |        HASH JOIN                |                        |     1 |   109 |       | 95132   (2)| 00:19:02 |                                             
    |*  8 |         TABLE ACCESS FULL       | ASSET                  | 36074 |  1021K|       | 38553   (2)| 00:07:43 |                                             
    |*  9 |         HASH JOIN               |                        | 90361 |  7059K|  4040K| 56578   (2)| 00:11:19 |                                             
    |* 10 |          HASH JOIN              |                        | 52977 |  3414K|  2248K| 50654   (2)| 00:10:08 |                                             
    |* 11 |           HASH JOIN             |                        | 39674 |  1782K|       | 40101   (2)| 00:08:02 |                                             
    |* 12 |            TABLE ACCESS FULL    | REGISTER               | 39439 |  1232K|       | 22584   (2)| 00:04:32 |                                             
    |* 13 |            TABLE ACCESS FULL    | SDP_LOGICAL_REGISTER   |  4206K|    56M|       | 17490   (2)| 00:03:30 |                                             
    |* 14 |           TABLE ACCESS FULL     | SERVICE_DELIVERY_POINT |   675K|    12M|       |  9412   (2)| 00:01:53 |                                             
    |* 15 |          TABLE ACCESS FULL      | SDP_LOGICAL_ASSET      |  1178K|    15M|       |  4262   (2)| 00:00:52 |                                             
    |* 16 |        INDEX RANGE SCAN         | IDX_NMI_ID_NK          |     2 |       |       |     2   (0)| 00:00:01 |                                             
    |  17 |      VIEW                       |                        | 39674 |   232K|       | 40101   (2)| 00:08:02 |                                             
    |* 18 |       HASH JOIN                 |                        | 39674 |  1046K|       | 40101   (2)| 00:08:02 |                                             
    |* 19 |        TABLE ACCESS FULL        | REGISTER               | 39439 |   500K|       | 22584   (2)| 00:04:32 |                                             
    |* 20 |        TABLE ACCESS FULL        | SDP_LOGICAL_REGISTER   |  4206K|    56M|       | 17490   (2)| 00:03:30 |                                             
    |* 21 |     TABLE ACCESS FULL           | METER_CONFIG_HEADER    |  3658 | 47554 |       |    19   (0)| 00:00:01 |                                             
    |* 22 |    TABLE ACCESS FULL            | METER_CONFIG_ITEM      |  7590 | 68310 |       |   112   (2)| 00:00:02 |                                             
    Predicate Information (identified by operation id):                                             
       2 - access("METER_CONFIG_HEADER_SK"="METER_CONFIG_HEADER_SK")                                             
       3 - access("NETWORK_TARIFF_CD"="NETWORK_TARIFF_CD")                                             
       4 - access("SERVICE_DELIVERY_POINT_SK"="TMP"."SERVICE_DELIVERY_POINT_SK")                                             
       5 - filter("ROW_CURRENT_IND"='Y' AND ("NMI_STATUS_CD"='A' OR "NMI_STATUS_CD"='D'))                                             
       7 - access("ASSET_CD"="EQUIP_CD" AND "SAP_INT_LOG_DEVICE_SK"="SAP_INT_LOG_DEVICE_SK")                                             
       8 - filter("ROW_CURRENT_IND"='Y')                                             
       9 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")                                             
      10 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")                                             
      11 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")                                             
      12 - filter("REGISTER_TYPE_CD"='C' AND (SUBSTR("REGISTER_ID_CD",1,1)='4' OR                                              
                  SUBSTR("REGISTER_ID_CD",1,1)='5' OR SUBSTR("REGISTER_ID_CD",1,1)='6') AND "ROW_CURRENT_IND"='Y')                                             
      13 - filter("ROW_CURRENT_IND"='Y')                                             
      14 - filter("ROW_CURRENT_IND"='Y')                                             
      15 - filter("ROW_CURRENT_IND"='Y')                                             
      16 - access("NMI_SK"="NMI_SK")                                             
      18 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")                                             
      19 - filter("REGISTER_TYPE_CD"='C' AND (SUBSTR("REGISTER_ID_CD",1,1)='1' OR                                              
                  SUBSTR("REGISTER_ID_CD",1,1)='2' OR SUBSTR("REGISTER_ID_CD",1,1)='3') AND "ROW_CURRENT_IND"='Y')                                             
      20 - filter("ROW_CURRENT_IND"='Y')                                             
      21 - filter("ROW_CURRENT_IND"='Y')                                             
      22 - filter("ROW_CURRENT_IND"='Y' AND "CONROL_REGISTER"='X')                                             
    ENVIRONMENT B
    Plan hash value: 2826260434                                   
    | Id  | Operation                            | Name                   | Rows  | Bytes | Cost (%CPU)| Time     |                                   
    |   0 | SELECT STATEMENT                     |                        |     1 |   181 |   103K  (2)| 00:20:47 |                                   
    |   1 |  HASH UNIQUE                         |                        |     1 |   181 |   103K  (2)| 00:20:47 |                                   
    |*  2 |   HASH JOIN ANTI                     |                        |     1 |   181 |   103K  (2)| 00:20:47 |                                   
    |*  3 |    HASH JOIN                         |                        |     1 |   176 | 56855   (2)| 00:11:23 |                                   
    |*  4 |     HASH JOIN                        |                        |     1 |   163 | 36577   (2)| 00:07:19 |                                   
    |*  5 |      TABLE ACCESS BY INDEX ROWID     | ASSET                  |     1 |    44 |     4   (0)| 00:00:01 |                                   
    |   6 |       NESTED LOOPS                   |                        |     1 |   131 |  9834   (2)| 00:01:59 |                                   
    |   7 |        NESTED LOOPS                  |                        |     1 |    87 |  9830   (2)| 00:01:58 |                                   
    |   8 |         NESTED LOOPS                 |                        |     1 |    74 |  9825   (2)| 00:01:58 |                                   
    |*  9 |          HASH JOIN                   |                        |     1 |    52 |  9820   (2)| 00:01:58 |                                   
    |* 10 |           TABLE ACCESS BY INDEX ROWID| METER_CONFIG_HEADER    |     1 |    14 |     1   (0)| 00:00:01 |                                   
    |  11 |            NESTED LOOPS              |                        |     1 |    33 |   116   (2)| 00:00:02 |                                   
    |* 12 |             TABLE ACCESS FULL        | METER_CONFIG_ITEM      |     1 |    19 |   115   (2)| 00:00:02 |                                   
    |* 13 |             INDEX RANGE SCAN         | SYS_C00116570          |     1 |       |     1   (0)| 00:00:01 |                                   
    |* 14 |           TABLE ACCESS FULL          | SERVICE_DELIVERY_POINT |   723K|    13M|  9699   (2)| 00:01:57 |                                   
    |* 15 |          TABLE ACCESS BY INDEX ROWID | NMI                    |     1 |    22 |     5   (0)| 00:00:01 |                                   
    |* 16 |           INDEX RANGE SCAN           | IDX_NMI_ID_NK          |     2 |       |     2   (0)| 00:00:01 |                                   
    |* 17 |         TABLE ACCESS BY INDEX ROWID  | SDP_LOGICAL_ASSET      |     1 |    13 |     5   (0)| 00:00:01 |                                   
    |* 18 |          INDEX RANGE SCAN            | IDX_SLA_SDP_SK         |     2 |       |     2   (0)| 00:00:01 |                                   
    |* 19 |        INDEX RANGE SCAN              | IDX_A_SAPINTLOGDEV_SK  |     2 |       |     2   (0)| 00:00:01 |                                   
    |* 20 |      TABLE ACCESS FULL               | REGISTER               | 76113 |  2378K| 26743   (2)| 00:05:21 |                                   
    |* 21 |     TABLE ACCESS FULL                | SDP_LOGICAL_REGISTER   |  5095K|    63M| 20245   (2)| 00:04:03 |                                   
    |  22 |    VIEW                              |                        | 90889 |   443K| 47021   (2)| 00:09:25 |                                   
    |* 23 |     HASH JOIN                        |                        | 90889 |  2307K| 47021   (2)| 00:09:25 |                                   
    |* 24 |      TABLE ACCESS FULL               | REGISTER               | 76113 |   966K| 26743   (2)| 00:05:21 |                                   
    |* 25 |      TABLE ACCESS FULL               | SDP_LOGICAL_REGISTER   |  5095K|    63M| 20245   (2)| 00:04:03 |                                   
    Predicate Information (identified by operation id):                                   
       2 - access("SERVICE_DELIVERY_POINT_SK"="TMP"."SERVICE_DELIVERY_POINT_SK")                                   
       3 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK" AND                                    
                  "SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")                                   
       4 - access("ASSET_CD"="EQUIP_CD")                                   
       5 - filter("ROW_CURRENT_IND"='Y')                                   
       9 - access("NETWORK_TARIFF_CD"="NETWORK_TARIFF_CD")                                   
      10 - filter("ROW_CURRENT_IND"='Y')                                   
      12 - filter("ROW_CURRENT_IND"='Y' AND "CONROL_REGISTER"='X')                                   
      13 - access("METER_CONFIG_HEADER_SK"="METER_CONFIG_HEADER_SK")                                   
      14 - filter("ROW_CURRENT_IND"='Y')                                   
      15 - filter("ROW_CURRENT_IND"='Y' AND ("NMI_STATUS_CD"='A' OR "NMI_STATUS_CD"='D'))                                   
      16 - access("NMI_SK"="NMI_SK")                                   
      17 - filter("ROW_CURRENT_IND"='Y')                                   
      18 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")                                   
      19 - access("SAP_INT_LOG_DEVICE_SK"="SAP_INT_LOG_DEVICE_SK")                                   
      20 - filter((SUBSTR("REGISTER_ID_CD",1,1)='4' OR SUBSTR("REGISTER_ID_CD",1,1)='5' OR                                    
                  SUBSTR("REGISTER_ID_CD",1,1)='6') AND "REGISTER_TYPE_CD"='C' AND "ROW_CURRENT_IND"='Y')                                   
      21 - filter("ROW_CURRENT_IND"='Y')                                   
      23 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")                                   
      24 - filter((SUBSTR("REGISTER_ID_CD",1,1)='1' OR SUBSTR("REGISTER_ID_CD",1,1)='2' OR                                    
                  SUBSTR("REGISTER_ID_CD",1,1)='3') AND "REGISTER_TYPE_CD"='C' AND "ROW_CURRENT_IND"='Y')                                   
      25 - filter("ROW_CURRENT_IND"='Y')Edited by: abhilash173 on Feb 24, 2013 9:16 PM
    Edited by: abhilash173 on Feb 24, 2013 9:18 PM

    Hi Paul,
    I misread your question initially .The system stats are outdated in both ( same result as seen from aux_stats) .I am not a DBA and do not have access to gather system stats fresh.
    select * from sys.aux_stats$
    SNAME     PNAME     PVAL1     PVAL2
    SYSSTATS_INFO     STATUS     NULL     COMPLETED
    SYSSTATS_INFO     DSTART     NULL     02-16-2011 15:24
    SYSSTATS_INFO     DSTOP     NULL     02-16-2011 15:24
    SYSSTATS_INFO     FLAGS     1     NULL
    SYSSTATS_MAIN     CPUSPEEDNW     1321.20523     NULL
    SYSSTATS_MAIN     IOSEEKTIM     10     NULL
    SYSSTATS_MAIN     IOTFRSPEED     4096     NULL
    SYSSTATS_MAIN     SREADTIM     NULL     NULL
    SYSSTATS_MAIN     MREADTIM     NULL     NULL
    SYSSTATS_MAIN     CPUSPEED     NULL     NULL
    SYSSTATS_MAIN     MBRC     NULL     NULL
    SYSSTATS_MAIN     MAXTHR     NULL     NULL
    SYSSTATS_MAIN     SLAVETHR     NULL     NULL

  • How do the Procurement of materials from projects?

    Hi Friends'
    How do the Procurement of materials from project s, here our Process is:
    Whenever our engineers on site see any shortages he will send a report thro our customized InfoPath request form. Then we decide depending on the material whether to order to USA or Procure locally. Some mechanical parts we procure locally. For this in PR we give reference of WBS element. Purchase department raise PO, we receive material, sent to site And finally we charge USA(parent Company)  for this amount against this project.
    For the items like electronic cards, Critical mechanical parts to be ordered to USA we send the InfoPath form to USA. We get weekly shipments from USA. We create PR and also PO. No action by our purchase dept. The FREE OF CHARGE (FOC) material is received to us. Stores will do MIGO and then we dispatch to Site.
    Friends please suggest how to do this Process through project systems. I need the entire configuration setting that we need to do and the process also, plz friends... I need these settings step by step.
    Regards,
    Hari
    Edited by: Hari  Krishna on Jan 3, 2009 12:39 PM

    suggest attend course PLM220
    If using only WBS then you have to raise PR from MM module and the material demand will not be driven from PS (except Easy Cost Planning)
    If using networks then assign material component to network activity and set the item category as non stock item - this will trigger PR from activity

  • FI-AP Tax Code not considering the excise duty while calcuating the VAT

    Sub: A/P Tax Code not considering the excise duty while calcuating the VAT
    Hi Frnds.
    I have a typical problem.
    Till now we are using a "W6" as a tax code, where Excise-10%, Ed Cess-2%, SEd Cess-1% and VAT-4%.
    But as the Govt. rules changed I have created a new tax code "W8" by copying the W6 and modified the VAT to 5% by changing the condition record JVRD.
    The new tax code is not calculating VAT part correctly. It is taxing into consideration Invoice Base value, Ed Cess & SEd Cess (Omiting the Excise Duty).
    I have checked my Tax Procedure, there everything is fine. Even my old tax code "W6" is working correctly.
    Let me know where the error lies.
    Here is the scenario
    00. Tax code                       -   W6   -   W8   - Current Staus of W8
    01. Invoice Base               - 355181 - 351798 - 353324 (by SAP Document Simulation View)
    02. Excise @ 10% on 01.        -  35518 -  35180 -  35332
    03. Ed Cess @ 2% on 01.        -    710 -    704 -    707
    04. SEd Cess @ 1% on 01.       -    355 -    352 -    353
    05. VAT @ 4% on (010203+04)  -  15671 -   0     -  0
    05.    VAT @ 5% on (010203+04)  -    0    -  19401 -  0
    05.     VAT @ 5% on (010304)     -   0     -    0    -  17719
    INVOICE TOTAL VALUE            - 407435 - 407435 - 407435
    Pls. let me know how to come over the issue.
    By the way I am using the above tax code at FB60 transaction code.
    Regards
    Krishna
    Edited by: Gopi Krishna Gutti on Oct 17, 2011 10:18 AM

    Hi Vivek
    Acutually we planned to implement SAP - FI & MM Modules only, and all the configuration is done in the system, but at the final stage our management is not satisfied with MM area, so finally we have gone live with only FI Moudle.
    By the way thankyou for the reply. I have maintained 100% in JMX1 for the new tax code and it is working fine.
    I will give you full points.
    Once again thanks a lot.
    Regards
    Krishna

  • The necessary shipping materials and the means of transport

    The answer of the question below is "d. Shipping point". On the other hand, shipping type (shipment type determines how the goods will be transported - tuck, train, ship etc....) is entered in the "shipment type" at the customization.
    Taking into consideration this fact, why is the answer of this question is given as "shipping point"?
    What part of the company is responsible for the type of shipping, the necessary shipping materials and the means of transport?
    Only one answer is correct.
    a. Sales Organization
    b. Transportation planning point
    c. Shipping condition
    d. Shipping point
    e. Warehouse

    hi
    As per my knowledge, normally goods are transported from Plant through shipping point, So ultimately shipping point is the responsible for that.

  • MTO Strategy consider the stock in hand

    Dear Experts,
    AM new in MRP Field, pls advise me about pure MTO Strategy which consider stock in hand. MRP run should consider the available stock for net requirement calculation. I tried with strategy 20,but it is not consider the stock.Pls advise,
    Regards,
    Vijesh

    Vijesh,
    MTO by definition will only consider Sales order stock.  This is the main planning difference between MTO and MTS.  Thus, if you have generic stock on hand (not sales order specific) it is supposed to be  excluded from MRP planning.
    If you wish for MTO planning to consider generic stock, you have to first convert the stock to Sales Order specific stock (Special stock type 'E') using a Material Movement transaction.  Or, you can stop using MTO and use an MTS strategy, such as 40.
    For more info about MTO planning see http://help.sap.com/erp2005_ehp_06/helpdata/EN/f4/7d2ed844af11d182b40000e829fbfe/frameset.htm
    Best Regards,
    DB49

Maybe you are looking for