Question : Different planning strategies in SAP PP
Hi PP gurus ,
Help me in understanding purpose with suitable example different planning strategies say Strategy 10 , 11 , 20 , 30 , 26 , 40 and 50 . Find below an
example for which how the above said strategies will act wrt .
Ex : You have Unrestricted stock of say X = 100 pcs and stock in quality
inspection is X = 10 pcs .
You have PIR ( X ) = 100 pcs , Production order( X ) = 50 pcs ,
Sales order( X ) = 150 pcs , Production order against sales order (X) =150
pcs , Inprocess (X) = 30 Units , sales order stock (X) = 25 units .
Thanx in advance
Regards,
Raj
Raj,
Have you gone through the help doc for planning strategies:
http://help.sap.com/saphelp_47x200/helpdata/en/cb/7f9b7043b711d189410000e829fbbd/frameset.htm
In overall terms:
In make to stock - 10, 11, 40
In MTS the general stock and general prod orders in warehouse are considered incalculating the net requirement. The diff between 10 and 11 is that in 11 irrespective of Warehouse stock prod takes place as per Planned Ind requirements. But in 10 the warehouse stock is considered.
In MTO (20/ 50):
The sales order stock and prod order w.r.to sales order aone is considered.
Hope this will give you an overall idea.
regards
ram
Similar Messages
-
Hi,
Dear Experts,
I have some confusion about strategies which i want to discuss which is as follows,
For MTS -10
MTD-20
Production with final assemble-40 etc.
Is is correct that i am using for make to stock,
for ROH-10, SFG-10, FG-40.
if not please tell me what are the others which i have to use also want to know more about how a industry choose a planning strategy.
Your suggesstions are weelcome.
Thank you.Hi,
Make to stock: These are the following strategies 10,30,40 and 70 used in MTS
In a made-to-stock scenario, the incoming customer requests are fulfilled from the inventory. The made-to-stock products are normally the consumer products or products which have a monopoly market and are sold out of the existing inventory. Such products are developed and produced continuously over the years till the product comes to the end of its life cycle.
In such scenarios, the shop floor or the production team never knows, for whom the product is being produced. The customer demands and the market situations can only be forecasted and used as a basis for future production. In SAP the forecasted quantity is evidently used in a form of planned-independent-requirement.
Made-to-stock production quantities are entered in SAP through the use of u201CPlanned independent requirementsu201D (transaction code MD61) which are subsequently planned by SAP MRP run. The planned independent requirements can be entered manually or the requirement can be pulled in from forecast or it can be pulled in from the sales and operation information structures (information structures which carry the sales information at levels defined by the organization).
Make to Order: Strategy no 20 and 50 used in MTO
In a make-to-order scenario, the incoming customer requests are accepted and produced thereafter and ultimately delivered to the very customer. The example of such a scenario can be high end products like jewelry or high end equipments or very costly product. These products are normally configured by the customer and the order is produced according to the customer requirements or by the design provided by the customer. The Sales order is created or configured according to the customer requirements and passed on to the production team.
In such a scenario, the tracking of the sales order from its creation to planning to production to inventorying to delivery can be easily tracked unlike in made-to-stock scenarios, where the incoming sales orders are not tracked in the plant, but are fulfilled by the existing stocks.
Coming to your question, using of strategies is purely depends on the business requirement. If it is make to stock, then you can use the same way you have posted (ROH-10, SFG-10, FG-40)
Hope it clears your doubt.
Regards / US -
Different planning strategy in defferent planning scenario
Hi ,
Is anybody can explain me how can use different planning strategy in different planning scenario ?
Thanks !Hello Denny
Planning strategies represent the business procedures for the planning of production quantities and dates. A wide range of production planning strategies are available in the SAP R/3 System, offering a large number of different options ranging from pure make-to-order production to make-to-stock production. Depending on the strategy you choose, you can:
Use sales orders and/or sales forecast values to create the demand program
Move the stocking level down to the assembly level so that final assembly is triggered by the incoming sales order
Carry out Demand Management specifically for the assembly
<b>Choose a make-to-stock strategy, if:</b>
The materials are not segregated. In other words, they are not assigned to specific sales orders.
Costs need to be tracked at material level, and not at sales order level.
You should always use make-to-stock production if you produce stock independently of orders because you want to provide your customers immediately with goods from that stock later on. You might even want to produce goods without having sales orders, if you expect that there might be customer demand in the future. This means that make-to-stock strategies can support a very close customer-vendor relationship because your objective here is to provide your customers with goods from your stock as quickly as possible. Returns that have passed quality inspection and other unexpected goods receipts can be used for other sales orders.
This does not mean that you have unreasonably high stock levels. You can avoid them by doing one of the following:
Create a production plan in advance (in Demand Management) to plan your stock.
If you make use of this option, you may also want to decide whether sales orders exceeding your plan are to affect production or not.
Receive sales orders relatively early on (using scheduling agreements, for example).
<b>Choose a make-to-order strategy, if:</b>
The materials are segregated. In other words, they are uniquely assigned to specific sales orders.
Costs must be tracked at sales order level and not on material level.
reward if it is useful
thanks
kedar -
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 PMHi 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 -
Two different plans in TEST & Prod
hi,
we have a problem in production database where we find some sql statements running very slow.
but if you run same SQL statement in TEST it runs < 2 secs.
Production DB Prod.SchemaA is exported into TEST DB as Test.SchemaA
When study the explain plan, we find Prod explain plan is different than test. if you create sql profile, by copying TEST explain plan, it would run faster in Production.
Now our question is why optimizer goes through two different plans when the schema structure same and data almost same in two databases?
Note that, we have two almost identical schema's in Production. Prod.SchemaA and Prod.SchemaB has same object names but some Prod.SchemaB may have small difference in indexes/constraints.
Users would run same SQL statement both in Prod.SchemaA & Prod.SchemaB time to time.
thanks
nealYou can have a clear picture about the accuracy of your statistics by getting the execution plan from memory into the TEST and PROD environment. You can proceed as follows
PROD> alter session set statistics_level=ALL;
PROD> execute your query;
PROD> select * from table (dbms_xplan.display_cursor(null,null, 'ALLSTATS LAST'));
TEST> alter session set statistics_level=ALL;
TEST> execute your query
TEST> select * from table (dbms_xplan.display_cursor(null,null, 'ALLSTATS LAST'));
This will give an execution plan showing the estimations(E-Rows) done by the CBO and the Actual (A-Rows) rows generated allowing you to judge the accuracy of your statistics.
The predicate part of the execution plan can also show inportant information.
Best regards
Mohamed Houri
www.hourim.wordpress.com -
Re: Questions about Plan structure
Reply-To: "Duncan Kinnear" <[email protected]>
Q. if you have an Employee class with related EmployeeSubordinate and
EmployeeSalaryHistory classes, should these all be in the same plan?
A It is better to have them in the same plan.It depends on the design
you have
Q Why should the Managers be separated from their business classes?
A Managers are usually service objects which might require different
resources.
These managers when deployed might be required by several other
applications.
Seperating them as a different plan will help in just using one
installed partition to be
Used by different applications (refer about Reference Partition)
Q If you have the Database managers separate, what scope does each DB
manager cover?
A It is better to have the DB managers in user scope.
It depends on the numbers of users, u have for the system.
Since u are talking about 100 tables. It's a huge system.
It also depends on the user licenses u have for the backend.
Take care that u use proper load balancing of DB Managers for the
system.
Krishna CVSR
GoldStone Softech Inc
>
Hi there,
We are in the middle of designing the structure of a new system.
I have read/heard that it is best to break down the plans into the
following categories:
Business Classes
Managers/Services
Clients
I have a few questions about this structure:
Should related business classes be grouped together in Plans? E.g. if
you have an Employee class with related EmployeeSubordinate and
EmployeeSalaryHistory classes, should these all be in the same plan?
Why should the Managers be separated from their business classes?
E.g. if there is an EmployeeMgr service which deals with anything to do
with the Employee business class, why separate them in different
plans? If you need the manager to access the class, you will always
need both.
Some of the Forte documentation talks about "Policy" managers and
"Database" managers. How do the functions of these managers differ
for a simple CRUD (Create Read Update Delete) class?
If you have the Database managers separate, what scope does each
DB manager cover? I.e. do you have one for the entire database (over
100 tables in our case), or do you break it down by sub-system?
Thanks in advance for any answers.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email: [email protected]
PO Box 764, McLean Towers, Phone: +64 6 834 3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834 3369
Providing Integrated Software to the Meat Processing Industry for over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>Reply-To: "Duncan Kinnear" <[email protected]>
Q. if you have an Employee class with related EmployeeSubordinate and
EmployeeSalaryHistory classes, should these all be in the same plan?
A It is better to have them in the same plan.It depends on the design
you have
Q Why should the Managers be separated from their business classes?
A Managers are usually service objects which might require different
resources.
These managers when deployed might be required by several other
applications.
Seperating them as a different plan will help in just using one
installed partition to be
Used by different applications (refer about Reference Partition)
Q If you have the Database managers separate, what scope does each DB
manager cover?
A It is better to have the DB managers in user scope.
It depends on the numbers of users, u have for the system.
Since u are talking about 100 tables. It's a huge system.
It also depends on the user licenses u have for the backend.
Take care that u use proper load balancing of DB Managers for the
system.
Krishna CVSR
GoldStone Softech Inc
>
Hi there,
We are in the middle of designing the structure of a new system.
I have read/heard that it is best to break down the plans into the
following categories:
Business Classes
Managers/Services
Clients
I have a few questions about this structure:
Should related business classes be grouped together in Plans? E.g. if
you have an Employee class with related EmployeeSubordinate and
EmployeeSalaryHistory classes, should these all be in the same plan?
Why should the Managers be separated from their business classes?
E.g. if there is an EmployeeMgr service which deals with anything to do
with the Employee business class, why separate them in different
plans? If you need the manager to access the class, you will always
need both.
Some of the Forte documentation talks about "Policy" managers and
"Database" managers. How do the functions of these managers differ
for a simple CRUD (Create Read Update Delete) class?
If you have the Database managers separate, what scope does each
DB manager cover? I.e. do you have one for the entire database (over
100 tables in our case), or do you break it down by sub-system?
Thanks in advance for any answers.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email: [email protected]
PO Box 764, McLean Towers, Phone: +64 6 834 3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834 3369
Providing Integrated Software to the Meat Processing Industry for over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/> -
What is the best expression to name the planning flow on SAP?
I am working on my graduating project in this topic: configuring the planning flow on SAP for the different types of industries.
By planning flow, I am talking about S&OP -> Demand Management -> MRP. But what's the best way to refer to this flow?
I already thought about:
"industrial planning" but it's too general and not precise.
"production planning" but it already refers to the PP module, which deals with other functions than what i am meaning.
"logistic planning" but it refers mainly to the operational level (ressources, workshop management, scheduling) while my work stops at MRP (tactical level)
Can you help me to find the best designation?OK, I got it now... You are going to love this!
"Advanced Planner and Optimizer", or in short "APO".
The abbreviation even has a website shortcut already www.sap.com/apo and there is a whole instant community already there waiting for you.
What a bargain! :-)
Cheers,
Julius -
Hi Experts,
I have been working for almost 3 and half years on SAP ABAP. Now i am planning to Learn SAP BI/BW and move my carrier to SAP BI/BW Completely.
What would be the opportunities and carrier growth in the coming years for this combination. Please suggest.
I have read all the previous posts which were posted a year back about the same combination. But please suggest according to the present trend.
I will definitely consider your each and every suggestion of you as a priority one to my carrier growth.
Thanks and Regards,
V ShankarHI V
if you already know it's better opportunities then it sounds like you have already answered your question
if you are not familiar with the concept of big data or HANA I recommend you enter those terms in your search engine or look at SCN Front page and start reading
as far as how to retrain and transition that will really depend on your current employment situation. What would be a great combination is a mix of ABAP with HANA. Without going into further detail I think you will gain more insight by your own research
regards
Colleen -
HI ALL,
What are some of the different ways of backing up SAP Data?HI,
There are many backup strategies for SAP.
1) If you can shutdown your server at night, you can take an offline database backup with redo logs.
2) If your server needs to remain on all 24 hrs, you can take an online backup with redo logs.
3) Once in 15 days or a month, you can take an O.S. level backup.
Also devise a strategy to keep a copy of backup at a different location and follow it. There should be at least one copy of O.S. Level backup at any other location other than your office premise.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar. -
i have done my b.tech in mechanical and automation. now i am planning to join sap mm module. tell me it will help me to groom my future???
what are the job opportunites as in fresher after doing this course. which is the best insititute for this course??Hi Nishant,
Welcome to SCN.
Questions like these have been asked many times in these forums. I suggest you search for relevant information and if you are not satisfied, then post a specific question.
Also, spend some time reading the The SCN Rules of Engagement
pk -
Question in HR module in SAP Queries ( transport changes)
Question in HR module in SAP Queries.
One infoset is attached to multiple queries.
If there are some changes in infoset, these changes are done in Development box and saved to the transport request. (queries related to infoset are not attached to the transport request).
These changes have to be moved to the Quality box and further to the Production.
1. When I move the infoset to Quality and production, do the related queries get affected? Will they work?
Or do we need to attach all the queries related to the infoset in development. ?
2. What would be the status of the queries that are not attached ?
3. When the changes to infoset is moved to different boxes, is the original infoset OVERWRITTEN or CHANGES APPENDED.
friends plz clarify and send them ASAP.Hi,
form read_infotype .
call function 'HR_READ_INFOTYPE'
exporting
TCLAS = 'A'
pernr = pernr-pernr
infty = '0002'
begda = pn-begda
endda = pn-endda
BYPASS_BUFFER = ' '
IMPORTING
SUBRC =
tables
infty_tab = i0002
EXCEPTIONS
INFTY_NOT_FOUND = 1
OTHERS = 2
if sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
regs,
Hema. -
"conect" 2 different companies that use SAP
hi all!
My question is:
We have 2 different companies that use SAP. Is there a way to "conect" both companies, so that company A gets information than company B has.
For example inventory levels from B, so that A can replenish when B has certain level?
Thanks a lot!Hi Mflores,
If you implement BW the you can get complete information n number of companies.
Regards,
Anil -
Creation Of A Single Purchase Requisition From Different Planned Orders
Hi,
After MRP run i get different Planned Orders for different raw materials . My requirement is that can i combine all the Planned Orders for diiferent materials into a single Purchase Requisition.This is a urgent requirement.
If useful i will award points.
Regards
JimmyHi,
it is not possible to combine with planned orders for different materials into single PR but differet PR can combine into a single Purchase Order.
pls let me know any clarification.
thanks
mohan
Message was edited by:
Mohan Ramalingam -
I bought a 16gb iphone 5 about 3 months ago and got applecare. yesterday I had to get on a different plan within the same company so i traded in my phone and got a new 32gb iphone 5. can i transfer my applecare to this new phone or would I have to buy it again?
As this is a WW forum with different AppleCrare offerings you need to specify which Country
as in North America has AppleCare+ and everywhere else AppleCare ,very different products
So to avoid incorrect guidance suggest you specify Country -
Planned Values in SAP R/3 ECC6.0
Hi
There are many Trial Balance report, which tells, run trial balance plan v/s actual (Tcode: S_PL0_86000029).
I want to know where i can enter planned values in SAP R/3 and what all activities i need to do to maintain planned values.
I am in SAP EHP5.
Please help
Edited by: Deepak Agrawal on Feb 4, 2012 11:07 AMHi Deepak,
As suggested by Mr.Srinivas ,you have to upload planned values through FSE5N and also mentioned customization also required to do in SAP to achieve the same
V_T001B_PL
Rgds
SumaMani
Maybe you are looking for
-
Anyone in the community know how I can fix a cracked screen of about 1mm in length? (felt the uneven surface and screen displays colour through the crack, what you normally find in a chipped screen) I understand that by using toothpaste it will only
-
Funky producer/consumer behavior
So this is a weird one... I've got a producer/consumer loop taken (mostly) from the template labview builds. For some reason, when I click the stop button, instead of stopping the program, it wants to run through the default case (shown in image) a s
-
Dreamweaver CS3 Problems Saving to Network
Hello! I recently started having a problem where any HTML files I open from my network volume (an Airport Disk) are becoming corrupt upon saving. What happens is that once I save and close the file, next time I open it (or try to preview it in a brow
-
SAP PP BOM Synchronization in mass plant
If BOM A exist in Plant 1000 ,Plant 2000 and Plant 3000, Once BOM A changed,How to update the BOM information in plant 1000,2000,3000. Mustn't we do the changes in BOM A three times? Is there any solution in standard SAP system with BOM Synchronizat
-
I have checked the apple support page but nothing there explains what is happening to my iPod clickwheel. The icon goes from an Apple icon to a sad ico with an exclamation mark to a non-charging battery icon. I have tried to reset or restore and it k