MRP PR No. Range

I have maintained MRP for particular material like MRP type VB, Reorder Point 2, MRP Controller MR1, Lot Size HB, Maximum Stock Level 2, Safety Stock 1, Planned Delivery Time 20 days.
after that i run mrp with TCode MD02, a purchase requisition created. When i see PR with ME5A or ME53N in that PR number range is of standard document type.
I want the number range for MRP PR how can i set that whenever i run mrp, the generated PR number range should be MRP PR number range. Please help....

Hi,
Check how the PR was created in Contact person tab in PR(Creation indicator field).
PR's craeted by materials planning will have the number range maintained in OMI8 and PR's created manually will have the number range assigned to your PR document type in customizing for MM.
Regards,
Deepak
Edited by: K B Deepak on Mar 23, 2011 8:07 AM

Similar Messages

Coverage Profile in MRP

Hi All,
Please can anyone explain what is Coverage Profile in MRP and how it can be used for the MRP in simple words.
Thanks
Balaji

Hi,
The Range of Coverage profile is define specific to a plant in IMG and then assigned to materials in master data MRP 2 view. To define the profile, use menu path
IMG->PP->MRP->MRP Calculation->Define Range of Coverage Profile. In the definition, there are two sections of data that you need to fill in.
1. Parameters for calculation of average daily requirements and Period indicator.
2. Minimum, Target, and Maximum stock calculation parameters.
PARAMETERS FOR AVERAGE DAILY REQUIREMENTS CALCULATION:
Choose the period indicator as Month, Period, or Week.
Specify the number of periods. This is used by system to calculate the average daily requirements.
Select the "Type of Period Length", ie. as workdays or calendar days or standard days (days per period). If the type of period length is selected as standard days, they you have to specify the "days per period". Using these three parameters, the system calculates average daily requirements using the formula:
average daily requirements = Sum of requirements in the number of periods / number of days in the number of periods.
PARAMETERS FOR TARGET STOCK AS DAY'S OF SUPPLY
Then you have to specify how many workdays of supply you want to maintain as target stock, in your case 15 workdays. If you wanted to maintain a constant 15 days of supply as inventory through out the planning horizon, just specify the target stock as 15 days and leave rest of the fields as blank, i.e min, max, and number of periods. The number of periods in this section simply maintains the target stock for that many periods from the date of MRP run. This way you can tell the system to maintain different target stock levels for three different period intervals. For example, if you wanted to maintain 15 days stock for first 3 periods, then specify the target stock as 15 days and number of periods corresponding to it as 3. The system then will maintain 15 days supply as inventory for first 3 periods from the date of MRP run and subsequent months zero inventory will be maintained. This will allow you to maintain your 15 days supply constantly for 3 periods

Coverage profile and Stime period profile in MRP

Can anyone explain what is the importance of coverage profile and safety time period profile in MRP2 view and what is their implication in MRP and SOP ?

Hi,
Coverage profile is used in Material Requirements Planning for calculation of dynamic safety stock. This dynamic safety stock is calculated by using formula: Average daily req*range of coverage.
Average daily req is calculated by considering requirements in specific periods and no of days for the total period length.
You can find all the setting in
MRP--> Planning-> MRP Calculation---->Define range of coverage profile.
e.g.
You have maintained in coverage profile:
Period indicator: W(week)
Number of periods to be considered for ADR: 2
Period length: Standard days (5 days)
Range of coverage: 5 days
Req for 1st week: 1000
Req for 2nd week: 1000
then Ave daily req.= (1000+1000)/(5 period length*2 no. of periods)=200
then Dynamic safety stock= 200 (ADR)* 5(range of coverage)=1000
Hope you got it.
Sachin

Report performance issue in oracle database 10g to 11g

Hi All,
We have one test instance for database 10g where the report is working fine below is the plan for report.
SELECT STATEMENT
VIEW APPS
SORT UNIQUE
UNION-ALL
HASH JOIN
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS FULL ONT.OE_ORDER_LINES_ALL
NESTED LOOPS ANTI
HASH JOIN
TABLE ACCESS BY INDEX ROWID MRP.MRP_GROSS_REQUIREMENTS
INDEX SKIP SCAN MRP.MRP_GROSS_REQUIREMENTS_N2
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
We have one more instance whose database is 11g and the same report is migrated but it is taking too long time to execute the report output. Please advise why it is happening even why the plan is difference.
SELECT STATEMENT
VIEW APPS
SORT UNIQUE
UNION-ALL
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_B_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_TL_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.BOM_STRUCTURES_B
INDEX RANGE SCAN BOM.BOM_STRUCTURES_B_N2
SORT AGGREGATE
INDEX RANGE SCAN BOM.BOM_OPERATIONAL_ROUTINGS_U2
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
SORT AGGREGATE
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT AGGREGATE
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT AGGREGATE
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID MRP.MRP_ASSIGNMENT_SETS
INDEX UNIQUE SCAN MRP.MRP_ASSIGNMENT_SETS_U2
INDEX RANGE SCAN MRP.MRP_SR_ASSIGNMENTS_N3
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID PO.PO_APPROVED_SUPPLIER_LIST
INDEX RANGE SCAN PO.PO_APPROVED_SUPPLIER_LIST_N1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
HASH JOIN
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
TABLE ACCESS FULL ONT.OE_ORDER_LINES_ALL
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_B_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_TL_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
TABLE ACCESS BY INDEX ROWID BOM.BOM_STRUCTURES_B
INDEX RANGE SCAN BOM.BOM_STRUCTURES_B_N2
INDEX RANGE SCAN BOM.BOM_OPERATIONAL_ROUTINGS_U2
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT UNIQUE NOSORT
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID MRP.MRP_ASSIGNMENT_SETS
INDEX UNIQUE SCAN MRP.MRP_ASSIGNMENT_SETS_U2
INDEX RANGE SCAN MRP.MRP_SR_ASSIGNMENTS_N3
SORT UNIQUE NOSORT
TABLE ACCESS BY INDEX ROWID PO.PO_APPROVED_SUPPLIER_LIST
INDEX RANGE SCAN PO.PO_APPROVED_SUPPLIER_LIST_N1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
INDEX RANGE SCAN MRP.MRP_GROSS_REQUIREMENTS_N1
SORT AGGREGATE
INDEX RANGE SCAN MRP.MRP_GROSS_REQUIREMENTS_N1
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
NESTED LOOPS ANTI
HASH JOIN
TABLE ACCESS BY INDEX ROWID MRP.MRP_GROSS_REQUIREMENTS
INDEX SKIP SCAN MRP.MRP_GROSS_REQUIREMENTS_N2
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
}

Hi All,
We have one test instance for database 10g where the report is working fine below is the plan for report.
SELECT STATEMENT
VIEW APPS
SORT UNIQUE
UNION-ALL
HASH JOIN
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS FULL ONT.OE_ORDER_LINES_ALL
NESTED LOOPS ANTI
HASH JOIN
TABLE ACCESS BY INDEX ROWID MRP.MRP_GROSS_REQUIREMENTS
INDEX SKIP SCAN MRP.MRP_GROSS_REQUIREMENTS_N2
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
We have one more instance whose database is 11g and the same report is migrated but it is taking too long time to execute the report output. Please advise why it is happening even why the plan is difference.
SELECT STATEMENT
VIEW APPS
SORT UNIQUE
UNION-ALL
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_B_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_TL_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.BOM_STRUCTURES_B
INDEX RANGE SCAN BOM.BOM_STRUCTURES_B_N2
SORT AGGREGATE
INDEX RANGE SCAN BOM.BOM_OPERATIONAL_ROUTINGS_U2
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
SORT AGGREGATE
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT AGGREGATE
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT AGGREGATE
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID MRP.MRP_ASSIGNMENT_SETS
INDEX UNIQUE SCAN MRP.MRP_ASSIGNMENT_SETS_U2
INDEX RANGE SCAN MRP.MRP_SR_ASSIGNMENTS_N3
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID PO.PO_APPROVED_SUPPLIER_LIST
INDEX RANGE SCAN PO.PO_APPROVED_SUPPLIER_LIST_N1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
HASH JOIN
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
TABLE ACCESS FULL ONT.OE_ORDER_LINES_ALL
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_B_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_TL_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
TABLE ACCESS BY INDEX ROWID BOM.BOM_STRUCTURES_B
INDEX RANGE SCAN BOM.BOM_STRUCTURES_B_N2
INDEX RANGE SCAN BOM.BOM_OPERATIONAL_ROUTINGS_U2
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
TABLE ACCESS BY INDEX ROWID BOM.CST_ITEM_COSTS
INDEX UNIQUE SCAN BOM.CST_ITEM_COSTS_U1
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
FILTER
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_TL
INDEX RANGE SCAN QP.QP_LIST_HEADERS_TL_U1
INDEX UNIQUE SCAN QP.QP_LIST_HEADERS_B_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_HEADERS_B
BUFFER SORT
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX SKIP SCAN QP.QP_PRICING_ATTRIBUTES_N11
INDEX UNIQUE SCAN QP.QP_LIST_LINES_PK
TABLE ACCESS BY INDEX ROWID QP.QP_LIST_LINES
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
TABLE ACCESS BY INDEX ROWID QP.QP_PRICING_ATTRIBUTES
INDEX RANGE SCAN QP.QP_PRICING_ATTRIBUTES_N3
SORT UNIQUE NOSORT
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID MRP.MRP_ASSIGNMENT_SETS
INDEX UNIQUE SCAN MRP.MRP_ASSIGNMENT_SETS_U2
INDEX RANGE SCAN MRP.MRP_SR_ASSIGNMENTS_N3
SORT UNIQUE NOSORT
TABLE ACCESS BY INDEX ROWID PO.PO_APPROVED_SUPPLIER_LIST
INDEX RANGE SCAN PO.PO_APPROVED_SUPPLIER_LIST_N1
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
TABLE ACCESS BY INDEX ROWID INV.MTL_ONHAND_QUANTITIES_DETAIL
INDEX RANGE SCAN INV.MTL_ONHAND_QUANTITIES_N6
SORT AGGREGATE
INDEX RANGE SCAN MRP.MRP_GROSS_REQUIREMENTS_N1
SORT AGGREGATE
INDEX RANGE SCAN MRP.MRP_GROSS_REQUIREMENTS_N1
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
INDEX RANGE SCAN INV.MTL_ITEM_CATEGORIES_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORIES_B
INDEX UNIQUE SCAN INV.MTL_CATEGORIES_B_U1
INDEX UNIQUE SCAN INV.MTL_CATEGORY_SETS_TL_U1
TABLE ACCESS BY INDEX ROWID INV.MTL_CATEGORY_SETS_TL
NESTED LOOPS ANTI
HASH JOIN
TABLE ACCESS BY INDEX ROWID MRP.MRP_GROSS_REQUIREMENTS
INDEX SKIP SCAN MRP.MRP_GROSS_REQUIREMENTS_N2
NESTED LOOPS
NESTED LOOPS
MERGE JOIN CARTESIAN
TABLE ACCESS FULL INV.MTL_PARAMETERS
BUFFER SORT
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_LOOKUP_VALUES
INDEX RANGE SCAN APPLSYS.FND_LOOKUP_VALUES_U2
INDEX RANGE SCAN INV.MTL_SYSTEM_ITEMS_B_XX1
TABLE ACCESS BY INDEX ROWID INV.MTL_SYSTEM_ITEMS_B
TABLE ACCESS BY INDEX ROWID ONT.OE_ORDER_LINES_ALL
INDEX RANGE SCAN ONT.OE_ORDER_LINES_N3
}

Consumption based planning in implementation ??

hi
Can some body explain me about the configuration setting in consumption based planning for manufacturing company ??
FOr manufacturing industry, they have production , and plant maintaienance, and depot plant.
For above business , what setting we have to in Consumplanning and MRP???
Thanks

Dear
Configurations for CBP as explained before.
a) Plant Parameters - t.Code : OMI8, when you execute this t.Code you will get several tabs like for ex.Number ranges, MRP Controllers etc... you need to maintain those are relevant
MRP Controllers, Number ranges, Available stock most of these tabs are mandatory configurations.
MRP Controllers - Defined and assigned to the plants, MRP Controllers are the planners who are responsible when it comes to the materials.
Number ranges : Planned orders, Purchase requesitions
Available Stock : whether stocks in transit, Blocked stock, Restricted stock are to be considered or not.
Planning Horizon - 100 days.. during MRP run those materials for which planning file entry is created and within the next 100days will be calculated for MRP.
b) MRP Group is not a mandatory config.
In case you need have configured new document type this can be entered in the "External Procurement per MRP Group" tab and this MRP group can be assigned to the material mster, based on this assignment the document type is picked up.
Each tab has its own significance, Please go through the configuration notes in SPRO you will get a better idea. let me know if you have futher clarifications.
Jade
Edited by: Jade on Mar 27, 2010 3:05 PM

Process instruction

Hi
Can any one give dtails of Configuration and Tcodes for PP-Pi
regards

Hi,
Pls. find PP-PI Tcode list as below :
PP-PI TCODES:
CRC1 - Create Resource
CR24 - Create Resource Network
CR31 - Create Hierarchy
C201 - Create Master Recipe
C251 - Print Master Recipe
C223 - Maintain Production Versions
COIO - Order Info System for PP-PI
COPD - Print Process Order
COPI - Print Process Order ShopFloor Papers
COR1 - Create Process Order
COR5 - Collective Process Order Release
COR6 - Single Process Order Confirmation
COR6N - Single Screen Entry of Confirmations
COR7 - Convert Planned Order to Proc. Order
COR7_PC - Part.Conv.: Plnned Ord. to Proc.Ord.
COR8 - Coll.Conv.: Plnned Ord. to Proc.Ord.
CORK - Process Order Confirmations (Total)
CORM - Mass Processing
CORO - Create Process Order w/o Material
CORR - Collective Entry of Confirmations
CORS - Cancel Process Order Confirmation
CORT - Display Process Order Confirmation
CORZ - Process Order: Time Event Confirmat.
COA6 - Process Order: Archiving
COA7 - Process Order: Retrieval - Archive
COA8 - Process Order: Archive Management
CO56 - Display PI Sheet
CO58 - Maintain PI Sheet
CO59 - Delete PI Sheet
CO60 - Find PI Sheet
COPOC - Process Manufacturing Cockpit
CO53 - Control Recipe Monitor
O10C - Assig. Ctrl Rec. Dest./Proc. Instr.
O12C - Assign Charact. / Proc. Instr. Cat.
List of PP-PI Transport Request and their IMG Path :
1) Define Distribution Keys
IMG > Production Planning for Process Industries > Master Data > Material List > Item Data > Item Data from related areas > Define Distribution Keys
2) Determine Person responsible for Resource u2013
IMG > Production Planning for Process Industries > Master Data > Resource > General Data > Determine Person responsible
3Define Planner Group-
IMG > Production Planning for Process Industries > Master Data > Master Recipe > Define Capacity Planner
4) Define Capacity Planner u2013
IMG > Production Planning for Process Industries > Master Data > Resource > Capacity Requirement Planning > Determine Capacity Planner
5) Determine Standard Value Parameter u2013
IMG > Production Planning for Process Industries > Master Data > Resource > General Data > Standard Value > Define Parameter
6) Define Setup Groups and Setup Group Categories
Define set up groups and set up categories u2013
IMG > Production Planning for Process Industries > Master Data > Master Recipe > Data for operations and phases > Define set up groups and set up group categories
7) Define copy setting between plants-Process
IMG > Production Planning for Process Industries > Process Management > Tools > Define copy setting between plants
8) Define Set Up Control Recipe destination u2013
IMG > Production Planning for Process Industries > Process Management > Control Recipe/PI sheet > Set up control recipe destination
9Define MRP controller u2013
IMG > Material Management > Consumption based Planning > Master Data > Define MRP controller
10) Special Procurement u2013
IMG > Material Management > Consumption based Planning > Master Data > Define Special procurement types
11) Define Floats (Scheduled Margin Key)-
IMG > Material Management > Consumption based Planning > Planning > Define Floats (Scheduled Margin Key)
12Define Splitting of Forecast requirements for MRP-
IMG > Material Management > Consumption based Planning > Evaluation > Forecast > Define Splittng of forecast requirements of MRP
13) Maintain Correction Factors for Forecast
IMG > Material Management > Consumption based Planning > Planning > Procurement > Maintain Correction factors for forecast
14 Carry Out Overall Maintenance of Plant Parameters
Maintaining plant parameters in MRP u2013
IMG > Material Management > Consumption based Planning > Plant Parameters > Carry out overall maintenance of plant parameters
15) Define Planning Horizon
Define Planning Horizon u2013
IMG > Material Management > Consumption based Planning > Planning > MRP calculation > Define Planning Horizon
16) Activate Requirement Planning u2013
IMG > Material Management > Consumption based Planning > Planning > Activate Requirement Planning
17) Define Range of Coverage Profiles (Dynamic Safety Stock)
Range of coverage profile u2013
IMG > Material Management > Consumption based Planning > Planning > MRP calculation > Define range of coverage profile (Dynamic Safety Stock)
18) Define Stock in Transfer and Blocked Stock Availability
IMG > Material Management > Consumption based Planning > Planning > MRP calculation > Stocks > Define Stock in transfer and blocked stock
19) Define MRP Areas
IMG > Material Management > Consumption based Planning > Master Data > MRP areas > Define MRP areas
20) Carry out maintenance of MRP groups
IMG > Material Management > Consumption based Planning > MRP groups> Carry out maintenance of MRP groups
21) Define Scope of total Planning - MRP
IMG > Material Management > Consumption based Planning > Planning > Define Scope of total Planning
22 Define Order Types
Define Order Type-
IMG > Production Planning for Process Industries > Process Order > Master Data > Order > Define Order Type
23Define Order Type Dependent parameters u2013
IMG > Production Planning for Process Industries > Process Order > Master Data > Order > Define Order Type Dependent parameters
24) Define Production Scheduler u2013
IMG > Production Planning for Process Industries > Process Order > Master Data > Bill of Material > Define Production Scheduler
25 Define Checking Control - Process Order
Define Availability Check u2013 Define Checking Control u2013
IMG > Production Planning for Process Industries > Process Order > Operations > Availabilty Check > Define Checking Control
26) Define Checking Rule for backorder processing u2013
IMG > Production Planning for Process Industries > Process Order > Operations > Availabilty Check > Define Checking rule for back order processing
27Define Stock and batch determination for good movement u2013
IMG > Production Planning for Process Industries > Process Order > Operations > Define Stock and batch determination for good movement
28) Specify Scheduling Parameters
Specify Scheduling Parameters u2013
IMG > Production Planning for Process Industries > Process Order > Operations > Scheduling > Specify Scheduling Parameters
29) Define Reduction Strategies
Define Reduction Strategy u2013
IMG > Production Planning for Process Industries > Process Order > Operations > Scheduling > Resource data > Define Reduction Strategy
30) Define Confirmation Parameters
Define Order Confirmation u2013
IMG > Production Planning for Process Industries > Process Order > Operations >
Confirmation > Define Confirmation Parameters
31) Define Valuation of Goods Received
Define valuation of goods receive u2013
IMG > Production Planning for Process Industries > Process Order > Integration > Define Valuation of goods received
32) MRP creation indicator u2013
IMG > Material Management > Consumption based Planning > Planning > Define creation indicator
33) Define safety stock u2013
IMG > Material Management > Consumption based Planning > Planning > MRP calculation > Stocks > Define Safety Stocks
34) Define alternative determination of Production u2013
IMG > Production Planning for Process Industries > Process Order > Operations > BOM selection > Define alternate determination of production
35) Define no. ranges u2013
IMG > Production Planning for Process Industries > Process Order > Master data > Order > Number Ranges > Define number ranges for orders
HOpe this helps.
Reward if useful.
Regards,
Tejas
Edited by: Tejas Pujara on Jul 24, 2008 9:22 AM

Purchase requisition number Range in MRP Run (MD02)

Hi Experts ,
When I run the MRP through T-Code MD02 even in test mode the Purchase requisition number getting consumed with out saving the entries.
for eg:- number range = 100 to 200.
when I execute the MD02 by selecting the indicator "Display results before they are saved " system showed a Purchase requisition number 100 and exit with out saving the entries.Next time when I execute the same MD02 system is displaying the purchase requisation number as 101, where as i have not used PR number 100 at all.
Please guide me....
Regards,
Sri.

Sri,
Nothing is missing. This is standard behavior. It appears to me that SAP makes no effort to ensure that all Purchase request numbers are contiguous.
You can try turning off number range buffering. This will reduce the number of gaps in your purchase req number sequences. However, I don't know if it will eliminate all gaps. Be aware that there is a performance tradeoff when you deactivate buffering. Making this change is considered to be a system modification, and is not supported by SAP.
https://service.sap.com/sap/support/notes/62077
Rgds,
DB49

Issue on Number Range for MRP Purchase Requisition

Hi Gurus,
Please help me on the issue explained below.
We are already using SAP ECC 6.0 and SRM 5.0 and now we are implementing Plant Maintenance Module.As a result of this implementation ,we have created number of PR document types and assigned to unique number ranges in ECC. One of these document types has been maintained for MRP group for a material type in order to identify the MRP purchase requisitions created on the shortage of the materials for these material types.
This functionality is working fine. MRP run for the materials is picking the appropriate PR document but number range of the document is not the same what was assigned to the linked document type.Some other number series is getting picked by system .
There is setting under SPRO Consumption Based PlanningNumber RangesPurchase Requisitions
Here, number range assignment is against plant. This is the same number range which is being taken by system on running MRP. But the desired number range is the one which has been linked to PR document type.
If I change the number range above then number range for MRP PR in present system will get affected..
Can you please advise me on above so that PR generated on MRP run should have appropriate number range?
Thanks & Regards,
Niti

Hi,
As per my understanding, what you have mentioned above is exactly the way SAP is designed. Its SAP Standard behaviour.
But if you check your PR document type - no:range & the CBP no:range both will be same only since both refers to the same object.
Please check the PR document type that you have assigned in the CBP & its no:ranges.
Thanks & Regards,
Ram

PR number range after MRP is not triggered

Dear gurus,
              My MM consultant needs a seperate number range for Purchase Requsition during the MRP Run.I have configured in Plant Parameters number range for PR and also since we are using the MRP Group.I have configured the purchasing doccument type in MRP group.But after MRP run system generates the different number for purchase requistion other than the configured.If i create manual purchase requsition it is creating in my number range(correct number range).ie)My requirement is sytem should generate seperate(correct) number range which i configured in Plant parameters.Can any body suggest what are the configuration missing in my end.
    For your information.The Raw materials are extened to new plant
                       please give your valuable comments and suggestion
                                                                                -guna

Dear Prabosh,
we are doing the rollout implementation.
          My problem is i am not getting the correct number range for MRP generated Purchase Requistion.The PR number which is generated by the MRP system is 11194121(which is the no range configured for another existing plant.the same material is extended for new plant).(In mrp generated PR,doccument type is correct only the pr number is wrong.)But I have configured the different number range(range 2800000000) for Doccument type.Please see my configuartion.If i create manually with docc type vad it is picking the correct number range280000000.but after mrp also the number range for pr should be in 280000000 series.this is my problem.Mr.Pradeep told that "pr number range which is is generated by MPR syststem should always be different.if we create manual pr against the same material the number range will be different.".
            we are doing rollout implemenation.i checked in existing plant with existing material.first i create the manual Purchase requstion.the number is 11193212.The PR number which is generated by the MRP system is 11193215.I checked the PR no 11193213/11193214.But it is not exists.whether any configuration is left in my end? any user exits will be used by this? Please go through my configuartion and suggest.
Please help me.since we are in Testing phase.It is very urgent issue.please help me
              i have already send the screenshots to yur id also
guna

Number Range for PR converted from MRP Run

Dear Experts,
We are experiencing problems with our number range when converting our MRP generated planned orders into PRs. We convert planned orders to purchase requisitions using MD03. We have 1 Plant with 2 MRP Groups which assigned to specific document types and number ranges as well. For example:
In T-code OMI8:
Plant AAAA --> Number Range 1111111111
(Because 1 Plant only able to have 1 number ranges)
In T-code OPPZ:
Plant AAAA, MRP Group : A01--> PR Document Type : ZZZZ
Plant AAAA, MRP Group : A02 --> PR Document Type : XXXX
In T-code SPRO "PR Document Types" and "PR Document Ranges"
PR Document Type : ZZZZ --> Number Ranges 1111111111
PR Document Type : XXXX --> Number Ranges 2222222222
When I run MD03, the result is:
MRP Group : A01 --> PR Document Type : ZZZZ --> Number Ranges : 1111111111
MRP Group : A02 --> PR Document Type : XXXX --> Number Ranges : 1111111111 (Why the number ranges is not 2222222222 ???????)
Does anyone have idea? Please help. Thanks a lot..

Hi Mallinath,
thanks for your info.
Note 46919 has been implemented in the system, and also i have maintain Tcode - OMI3:
* Object Type : 2 (PR) --> PR Document Type : ZZZZ --> Internal number range : 1111111111 --> external number range : " " (blank) --> Reservations : 01
* Object Type : 2 (PR) --> PR Document Type : XXXX--> Internal number range : 2222222222 --> external number range : " " (blank) --> Reservations : 01
But still system pick wrong number ranges (1111111111, instead of 2222222222 ) for PR Document Type XXXX if generated from MRP run.
Do you have any other idea? Thank you.

Excess schedule is getting generated in Mrp.

Hi Gurus,
Excess schedule is getting generated although enough stock is available to cover the requirement why the requirement are getting generated
Mrp 2 lot size is weekly lot size
Minimum lot size 10
Covrage profile of 20
what is the effect of coverage profile 20 can any body tell me.
Quick response will be helpful
Thanks & Regards
Sandeep Praharaj

Dear Sandeep,
Coverage profile is used for dynamic safety stock. As safety stock can be define manualy in master data. But by assigning coverage profile system automatically generate requirement of safety stock on the basis of no. of days, no of period and target days. System calculate safety stock by given below formula.
Dynamic Safety Stock= Average Daily Requirement * Range Of Coverage
Average Daily Requirement =
(Requirements in the specified periods) / (Number of periods * No. of days per period)
Regards
Muhammad Umar

PR created after MRP run, instead of schedule line

Dear all,
I want to create schedule lines automatically from the planning run, for raw material. I have maintained info record, scheduling agreement, quota arrangements and also the source list.
For the raw material, safety stock of 1000 nos. has been maintained. The current stock of the material is 0.
After MRP run, based on the upper level PIRs, schedule lines are generated properly. But, against the safety stock of 1000, a PR is generated.
I donot want a PR to be generated.
Please suggest a solution.
Thanks in advance,
Shrenik
Edited by: Shrenik on Mar 8, 2008 4:17 PM

Dear all,
I checked an found that the schedule agreement date does not have any effect. Even if the requirement date falls outside the date range, i am able to create schedule lines.
I also found that if i maintained GR processing time, then always a PR is created. If GR processing time is 0, then only schedule line is created. Moreover, planned delivery time does not have any effect on the calculations, even if it is 10 days, 20 days or 900 days.
Can someone please clarify all these? How are these times taken into account?
Thanks in advance,
Shrenik
Edited by: Shrenik on Mar 9, 2008 3:04 PM

Error: Number range for object RESB does not exist

Hi
I'm trying to convert a planned order (to purch requisition) partially via trxn code MD04. Upon saving I get the above error msg. The complete text of msg is as follows. I've maitained the number ranges of all the objects specified in this error msg. Can somebody explain on how to overcome this problem?
Many thanks
BE
Error Msg Text:
Number range for object RESB does not exist
     Message no. 61501
Diagnosis
     The system cannot create a document for an MRP element if no number
     range or interval has been maintained in Customizing of MRP or if t
     number range you have maintained is not allowed.
     Below is a list of MRP elements that are affected:
     Number range object MRP element
     PLAF                 planned order (operative oder simulative)
     EBAN                 purchase requisition
     RESB                 dependent requirements
     MDSM                 simulative dependent reqmts (long-term plannin
     MDTB                 MRP list
Procedure
     Check the number ranges in Customizing. If you do not have the necessa
     authorization, please get in touch with your systems administration.

Hi
Thanks for the reply. But I have maintained the number ranges for matl. reservations/dependant requirements at OMI2. Here is the screen shot..Do find anything wrong with it? Pl advice.
NR Object                             MRES/DREQ
No.                          From Number            To Number          Curr Number          Ext
01                           0000000001               8999999999           380                    blank
02                           9000000000               9500000000           blank                  checked
RB                          9500000001               9999999999           blank                  checked
Number ranges for the plants are assigned to 01 (0000000001 to 8999999999).
thanks
BE
Edited by: Brian Elfie on Jan 10, 2008 11:27 AM

MRP type VB

Dear All,
Please someone suggest me why should we use VB and to maintain safety stock for materials which is having longer lead time?
Thanks,
Rinky

Hi,
VB is the MRP TYPE for consumption based planning. Please go through the below for understanding the CBP and safety stock.
In consumption-based planning, the following MRP procedures are available:
Reorder point procedure
Forecast-based planning
Time-phased materials planning
Reorder Point Planning
Use
In reorder point planning, procurement is triggered when the sum of plant stock and firmed receipts falls below the reorder point.
Features
The reorder point should cover the average material requirements expected during the replenishment lead time.
The safety stock exists to cover both excess material consumption within the replenishment lead time and any additional requirements that may occur due to delivery delays. Therefore, the safety stock is included in the reorder level.
The following values are important for defining the reorder point:
Safety stock
Average consumption
Replenishment lead time
The following values are important for defining the safety stock:
Past consumption values (historical data) or future requirements
Vendor/production delivery timelines
Service level to be achieved
Forecast error, that is, the deviation from the expected requirements
Manual Reorder Point Planning
In manual reorder point planning, you define both the reorder level and the safety stock level manually in the appropriate material master.
Automatic Reorder Point Planning
In automatic reorder point planning, both the reorder level and the safety stock level are determined by the integrated forecasting program.
The system uses past consumption data (historical data) to forecast future requirements. The system then uses these forecast values to calculate the reorder level and the safety stock level, taking the service level, which is specified by the MRP controller, and the material's replenishment lead time into account, and transfers them to the material master.
Since the forecast is carried out at regular intervals, the reorder level and the safety stock level are continually adapted to the current consumption and delivery situation. This means that a contribution is made towards keeping stock levels low.
Forecast-Based Planning
Use
Forecast-based planning is also based on material consumption. Like reorder point planning, forecast-based planning operates using historical values and forecast values and future requirements are determined via the integrated forecasting program. However, in contrast to reorder point planning, these values then form the basis of the planning run. The forecast values therefore have a direct effect in MRP as forecast requirements.
Features
The forecast, which calculates future requirements using historical data, is carried out at regular intervals. This offers the advantage that requirements, which are automatically determined, are continually adapted to suit current consumption needs. The forecast requirement is reduced by the material withdrawal so that the forecast requirement quantity that has already been produced is not included in the planning run again.
Reducing Forecast Requirements
Reducing forecast requirements by consumption
If consumption is higher than the forecast requirements in the current month, then the system also reduces future forecast requirements.
Reducing current forecast requirements by consumption
If consumption is higher than the forecast requirements in the current month, then the system does not reduce future forecast requirements.
Average reduction of the forecast requirements
The reduction of the forecast requirements is based on average daily consumption. Actual consumption data is not relevant.
The system calculates the average daily requirement first using the formula forecast requirement/number of workdays in the forecast period.
The forecast requirements are then reduced by the quantity resulting from the following formula: number of workdays worked x average daily requirements.
Period Pattern and Forecast Periods
You can specify the period pattern for the forecast (daily, weekly, monthly or per accounting period) and the number of periods to be included in the forecast individually for each material. It is possible, however, that the forecast period pattern is not specific enough for planning purposes. In this case, you can define per material that the forecast requirements should be divided according to a finer period pattern for planning. You can also define how many forecast periods are to be taken into account during requirements planning. The splitting indicator is defined in Customizing for MRP per plant and per period unit and is assigned to the material in the material master.
Time-Phased Planning
Use
If a vendor always delivers a material on a particular day of the week, it makes sense to plan this material according to the same cycle, in which it is delivered.
Features
Materials that are planned using the time-phased planning technique are provided with an MRP date in the planning file. This date is set when creating a material master and is re-set after each planning run. It represents the date on which the material is to be planned again and is calculated on the basis of the planning cycle entered in the material master.
The net change planning indicator and the net change planning horizon indicator are irrelevant for materials planned using the time-phased planning procedure. The system does not therefore set these if changes are made in the planning run.
If you want to plan a material earlier than the specified MRP date, you can enter an MRP date during the planning run. For example, if the planning run is set for Monday, you can bring it forward to Saturday instead.
If you use the SAP Retail System, the system proposes the planning cycle from the vendor sub-range when you create a material master record. The vendor sub-range contains all the goods of a particular vendor that, from a logistical view, can be planned similarly.
Time-phased planning can be executed using consumption-based planning or MRP:
If you want to carry out time-phased planning using consumption-based planning techniques, the requirements have to be created using the material forecast. If you use consumption-based planning, only the forecast requirements are included in the net requirements calculation. For reducing the forecast requirements, you can choose the same settings in Customizing as used for forecast-based planning.
If you want to carry out time-phased planning using MRP, all the requirements that are relevant to MRP are included in the net requirements calculation. For this purpose, the indicator Time-phased with requirements must have been selected in the MRP type. The forecast requirements can also be taken into account in this process.
Safety Stock Calculation
The safety stock depends on the service level that you specified in the MRP II view of the material master record and on the accuracy of the forecast. The more accurate the forecast, the smaller your safety stock can be.
The following figure shows that, without safety stock, customer demand can be satisfied by 50%. It also shows that it is almost impossible to satisfy customer demand 100% of the time. Factor R describes the relationship between forecast accuracy and service level (SL).
If replenishment lead time is greater than the forecast period by factor W, then the mean absolute deviation (MAD) is recalculated for this period (formula 17). The MAD is a parameter of forecast accuracy. Otherwise, see formula 18.
Safety Stock (SS) Formulas
If the material is produced in-house, the delivery time is: opening period + in-house production time + goods receipt processing time. It is expressed in workdays. The forecast period is taken from the material master record and is also expressed in workdays.
If the material is procured externally, the delivery time is: goods receipt processing time + planned delivery time + goods receipt processing time. It is expressed in calendar days. The forecast period is taken from the material master record and is also expressed in calendar days.
The safety stock calculation may lead to rounding effects.
Minimum Safety Stock
You can specify a minimum safety stock. If the result of the safety stock calculation is lower than this limit, the safety stock is then automatically set to this minimum value. You enter the minimum safety stock in the material master record (the MRP 2 screen).

Number range for object MDTB does not exist - Message no. 61501

Hi All ,
I have done the necessary configurations in PP say
Order Type
Order Type Dependent Parameters
Scheduling parameters for planned & production order
Confirmation parameters
Availabilty check etc
and iam able to create planned & production order and confirma the production order.
I want to configure for MRP: -
Settings done are
Have activeted planning file entry for all plants.
When i run MRP system throws a error <b>Number range for object MDTB does not exist - Message no.61501 </b>
Is there anything to do with plant parameters OPPQ and Mrp Group OPPR.
I just tried plant parameters,standard 0001 is not available for copying.
Suggest me how to proceed to set MRP.
Shankar

Hi shankar
it is a good practice while creating the plant copying the plant from the standard plant so that all the standard table enteries will be copied for the plant as the standard plant is not there youcan think of copying from any other plant similar to your plant which has the required entry. else
in SE16N check the NRIV table for the Object MDTB. if enteris found then make the table entry with the help of abaper.
hope this helps
regards
SK

MRP PR No. Range

Similar Messages

Maybe you are looking for