MRP Creation Indicator

Hi Experts,
Just want to seek help regarding the MRP Creation Indicator. What would be the effect if the Opening Period set is "0" or zero for the MRP item in SMK of Material Master but when we run MRP in the Selection Parameters we uses the parameter "2"- Purchase requisitions in Opening Period in the Create Purchase Requisition field.
We have MRP items wherein MRP still generates Planned Orders (STPO) even if the Opening Period is Zero or "0". The MRP Planned Orders contains Planned Opening Date which is the same date when MRP run and yet MRP did not created PR for the item. Hope you can help enlighten us.
Thanks,
SD

Hello ,
The Opening period define at SMK is used to calculate the "Opening date" of either planned order or Pur req. Opening date is calculated as below.
Open date = Opening period - Order start date of Planned order or Release date of Pur req.
According to cont ind 2 , If Opening date falls before the "MRP Run date" system will create Pur req directly.In your case the Opening date and MRP date are same it will create Planned order Only. You have to convert ot manually.
Opening period is nothing but a buffer period for MRP controller t o convert the Planned order to Pur req
To check the same, increase your Opening Period at SMK and check with MRP
Regards
Pradeep
Edited by: Pradeep Kumar on Jun 16, 2009 1:33 PM

Similar Messages

Creation indicator purchase requisition in md02

Hello SAP Gurus,
     This is regarding creation indicator purchase requisition in md02.In this creation indicator purchase requisition if we keep setting as 2 than it will create purchase requisition if the dates of PR are in the opening period and will create planned order if dates of PR falls out of opening period.And it takes the opening period from schedule margin key.
     My question is , as system calculate the opening date by subtracting the number of days which we have given in opening period in schedule margin key from the order start date.suppose if order start date is 10.03.2008 and we have given the opening period of 5 days,than the opening date will be 05.03.2008 if there are no holidays between it.So how it comes that PR date will fall in opening period?I am confused that when system will create planned order and when system will create PR if we keep creation indicator purchase requisition as 2.
      Plz help me with this query.If you could explain with one example than it would be great.
                     Thanking all in advance.And obviously for suitable answer i will definately give good points.

Hi,
System calculates the opening date by subtracting the number days given as opening period at SMK from order start date.
For creation ind =2 ,
MRP run date decides the PR / Planned order creation even if u set procurement F.
If MRP run date falls bettwen the opening date & order start date , it will create PR only,
If run MRP run date falls outside the opening preriod ie earlier than the order opening date, system will create planned order and it has to converted to PR
For examble, Order start date is 28.03.2008 and 2 day is defined as opening period SMK for ROH.
If u run MRP on today it will create planned order.
Hope u understand , ifso reward and close.
Regards
Pradeep

Creation Indicator in PR: B Material Requirement planning

Hi All,
I am facing an unusal scenario.
User is claming that PR is getting generated for a material after running the MRP, even there is enough stock.
I checked material & I found that MRP type is ND, there is no entry in the planning file for this material.MRP list & stock requirement list of this material is showing nothing. So there is no way that PR will be created automatically via MRP run for this material.
When I checked one PR for this material, Plant & storage location, creation indicator is showing as B Material Requirement planning.
Could you please help me that why creation indicator is showing as B>
I further checked these PRs are created long back when MRP type was V1. Later they changed it to ND.
How to delete MRP generated PR manually when PO has been created for these PR.
Regards
Shilpi
Edited by: sapmm1234 on Dec 14, 2011 6:10 PM

As you said; the PR was created long ago by MRP, when it was not ND.
If it was already converted into a PO, there's no need to delete it, right? If not, just delete it manually.
In the future, when you change MRP type from a valid type to ND, always remember to do 2 additional things, as the system will not do them automatically:
1- delete the MRP list
2- delete any planning elements if they exist, like planned orders and MRP generated PRs.

Authorization object for field, EBAN-ESTKZ (creation indicator)

Dear All,
Does anyone know if there is an authorization object for field, EBAN-ESTKZ?
I need to control the PR's authorization at creation indicator level. i.e. we need to remove the ability for all users to change Purchase Requisitions created by MRP.
Thanks,
Arun.

Hi Jay,
Thanks for your response.
I didnt find it there. You have any Z options?
Thanks,
Arun.

Defining planning time fence and creation indicator with out oppr settings

Hi, we dont use mrp groups and accordingly i did not set oppr settings. i observed that planning time fence and the creation indicator (omdz & oppr) are defined thru mrp goups. please advise how to define those w/o oppr settings? is there any seperate settings or oppq settings for them? please advise.

Hi,
Maintain it directly in the Material Master.
Best Regards,
Siva

PO creation Indicator in SRM

Hi Experts,
I have a question for you?
Where can i find the PO creation indicator in SRM?
We are in Extended Classic scenario. POs are created from Shopping carts either manually by Purchaser from SOCO or autmatically by the system for catalog items & for items with Contract.
I want to know whether there are any status indicators for a PO in SRM from which i could know whether the PO was created manually or automatically...similar to the field we have in EKKO for a R/3 PO.
Thanks in advance!
Cheers - Aakash

Hello Aakash,
You can determine whether PO hasbeen created automatically from a preceeding document or created manually at line item level only. If the PO is created from a preceeding documents like shopping cart then the fields SRC_GUID and SRC_OBJECT_TYPE of the table BBP_PDIGP will be filled. If the PO is created manually then these fields will be empty.
Hope this will answer your question.
Best Regards,
Mani

Bapi_pr_change error Creation Indicator G invalid

Has anybody come across this error?
I tried searching in sdn forum and google, could nt find it.
If i try to change the PR manually it allows, but using the above BAPI it gives this error.
'Creation Indicator G invalid'.
How do I solve this?

Hi,
Creation indicator G stands for store order .
I think you should give F...
else try from all the remaining possible combinations
B, D, R, U, V, M, Y, A
Regards

Cross Plant Planning- MRP activation indicator turned after the creation of Material code

Dear Experts,
Working on Cross plant planning, where 1001 Production plant will stock transfer material to 8 different plants.
Right now, only 10001 plant had MRP and planning file entry ticked in customizing OMDU.
The other 8 plants have Materials codes created and MRP views extended but no MRP activation is ticked.
Now, to have Cross plant planning MRP set, I have done necessary configurations, Scope of Planning, Special Procurement 40, and parallel processing is configured. All master datas are set properly. Tested few scenarios in IDES, working fine.
If my understanding is clear, than I thin I need to run MDAB, activation of planning file and MDRE, Planning file Consistency Check, because MRP will run in background?
Is this correct or something more needs to be done ?? Please suggest
Please also tell what is the use of MDRE t code.
Best regards
Shailesh

Hello Shailesh
MDAB (RMMDVM20) is at plant level, you need to create different variants as per your plants
Create a variant for the new plants and then schedule a job for these variants.
Check customizing transaction OMDU -> set up planning file
entry and consistency check of planning file entries.
Best Regards,
R.Brahmankar

Creation indicator in MRP

Hai PP Gurus,
              Whenever we run the transaction MDO1,MD02 & MDO3 it shows some default values for creation indicators like 1/2/1.But i want to set default values like 2/2/2 that means whenever i call this T-code it shows 2/2/2. This default values are maintained by PP or ABAPER through program.
             So please throw some light on this....
             Thanks in advance
Regards,
S.ganeshraja

Dear Mr.Ganeshraja,
Check this,
Maintenance
You can only create transaction variants for dialog transactions and reporting transactions.
Only "normal" screens, dialog boxes, and subscreens can be included in the variant.
Screen Variants are automatically created anytime you create a transaction variant.
Initial Screen
Enter the name of the transaction and the transaction variant on the initial screen. The system creates a cross-client transaction variant. If you want to create a client-specific transaction variant, choose Goto -> Client-specific transaction variants tp branch to the client-specific transaction variant maintenance transaction.
Client-specific transaction variants only exist in the client in which they are created. The field contents of the transaction variant must be available in this client. Cross-client transaction variants are available throughout the system, regardless of the client currently being used. The field contents of these transaction variants must be available in all clients.
Creating the Transaction Variant
Choose Create to create a variant.
The system calls the application transaction that you want to create a variant for. Enter the values you want to use in the in the input fields. Each time an action is completed, a Dialog Box, appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed (see Requirements).
Here you can determine:
if you want to save the field values you have inserted on the current screen (the "Adopt field values" checkbox)
if you want to hide the entire screen (the "Do not display screen" checkbox). This is only possible if settings are copied to your variant ("Adopt field values")
if field contents are saved (the "With contents" checkbox)
if the ready for input status of specific fields should be revoked (the "Output only" checkbox)
if specific fields should be hidden (the "Invisible" checkbox)
if specific fields should be mandatory the "Mandatory" checkbox)
You may or may not be able to select each of these checkboxes for every field depending on the field's type (--> Requirements).
Screen variants are created automatically for each screen where values have been saved (adopted). Enter screen variant names in the "Name of screen variant" field. These names must be unique. If the system is able to find a unique name for a screen variant it is automatically inserted into this field. The convention reads like so: (< name_of_transaction_variant>_(<client>)_<screen_number>).
Choose the function Continue to proceed. The following pushbuttons are available:
The Cancel function displays the current application transaction screen again. Here you can make changes to your settings.
The Menu functions function displays an additional dialog box wher you can deactivate menu functions.
The GuiXT function allows the user to edit a GuiXT script for the current screen (--> GuiXT).
The Exit and Save function exits and saves the application transaction. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).
Enter a short text for your transaction variant here.
Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.
Choose "Save". The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.
You can also branch to this list using the Change values function during the function selection process.
Deleting Preassigned Values
You can delete all of the values you assigned to fields of a single screen in a transaction variant by resetting (deselecting) the Adopt field values checkbox. This deletes the screen from your variant, even those entries that were transferred to the variant during previous processing.
If a screen variant has already been created for this screen, then the system simply deletes the screen variant's transaction variant assignment; the screen variant itself is not actually deleted.
Individual fields can be deleted from transaction and screen variants by resetting (deselecting) their corresponding checkboxes.
Regards
Mangal

MRP Creation

Forum,
If I have the following scenario:
1. Purchase Order on system for 10 widgets with a delivery date of 1st October
2. New Sales Order for 5 widgets entered with a Delivery date of 20th September
3. On running MRP wizard, it suggests we need to order 5 widgets to satisfy Sales Order as 10 on order will not be delivered on time.
Is it possible for MRP not to suggest the creation of the PO for 5 widgets?
Regards,
Juan

Hi,
Try to use the planning horizon in MRP to avoid the suggestion
JimM

PR and PO through MRP run

hi,
What are all settings to generate Purchase Requisitions through MRP run? Also, if, i wanna automate creation of Purchase order from Purchase Requisition (not manually). how to achieve this?
thanks..

Hi,
1. Get PR trough MRP run
1a, You have to have proper master data settings (e.g. material master: MRP type "PD", procurement type "F")
1b, Proper MRP creation indicator shoudl be used in MD01 / MD02 / MD03.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/f4/7d2da044af11d182b40000e829fbfe/frameset.htm
1c, Your planning situation also influences whether you get PR or not. If there's no need to procure anything (e.g. you have sufficient stock level or you have no demand for the goods > MRP won't generate procurement proposal)
2. Convert PR to PO
It depends on your master data settings (material master, source list, QA, outline agreeemts, etc)
If you have proper master data settings and during MRP run it is possible to determine the source of supply, you can use ME59 to get the POs from the PReqs (otherwise you have to use ME57, ME58 too).
http://help.sap.com/erp2005_ehp_04/helpdata/EN/4c/420d29470a11d1894a0000e8323352/frameset.htm
But you can't get PO as the result of MRP run in standard system - you get PR (or PldOrd) and you have to convert the PR to PO (or PldOrd > PR > PO).
Regards,
Csaba

Automatic PR creation

dear sap guru,
How to create automatic PR with MRP?
Regards,
babu

Hi,
To get PR trough MRP run
1. You have to have proper master data settings (e.g. material master: MRP type "PD", procurement type "F") and Maintain a soursce list if req.
2. Proper MRP creation indicator shoudl be used in MD01 / MD02 / MD03 to create PR
3. Your planning situation also influences whether you get PR or not. If there's no need to procure anything (e.g. you have sufficient stock level or you have no demand for the goods > MRP won't generate procurement proposal)
Please refer below link for clarity of MRP. I hope this will resolve your issue. Thanking you.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30f4d6c1-0808-2d10-2ea5-f9b2863cfed8?quicklink=index&overridelayout=true

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

Creation of SDEB's for MRP type = VB materials.

Hi Gurus,
When we run plant wise MRP, SDEB's are created instead of Purchase requisitions for all Manual re-order point materials. We understand that SDEB's are created when the stock of tha material is above tha Re-order point, and this SDEB's indicate tha MRP controller whether he can create manually Purchase requisitions or not.
But, we are getting these SDEB's for the materials that have stock below the Re-order point as well. Which is not correct i think.?
For your information, when we run material wise MRP there are no SDEB's at all.
Please explain what might be the Root cause and the solution to over come this..
Thanks for your understanding..
Naveen.A

Dear colleague,
without checking the issue it is difficult to know if there is an error.
Please check if the following information can explain the behaviour of your system:
A)When you do MD01 or MDBT the creaton indicators defines in the
customising are used . whereas when you run MD02 or MD03 the creation
indicator on the individual screen is used.
Single-item planning and total planning follow a different logic
concernng the creation indicators.This is also described in the
documentation for Master Planning/Materials Planning (Chapter 4, Section
2) and in the Implementation Guide.
Single-item planning:
        The entered creation indicators are generally valid.
Total planning:
       The entered creation indicators are used as default values.
       For materials from an MRP group, the values from the MRP group
       apply (if available).
       The creation indicator for delivery schedules can additionally be
       specified per plant. This is used if nothing was specified via
       the MRP group.
       Thus, the priority is as follows:
      1. MRP group
      2. Plant
      3. Initial screen
B)In MD02 system can de multilevel (For components of a header Materia)
or/and Multiplant (Stock Transfre ) planning. In such cases for all the
materials involved the creation indicator used in the screen is used.
C)The creation indicator makes sense only for materials having
procurement type external procurement (F) in material master. For the
materilas which are produced in house (Procurement type E) system will
always create planned orders.
    And Materials having procurement type X(Both procurement types ) is
treated as Inhouse produced material by planning . Thus for such
materials system will always create a planned order. Now this planned
order can be converted into a production orer or into a purchase
order(via purchase Requisition).
    When you run MRP with "Create Purchase Requisition " in the opening
period , then the syetm uses in the opening period defined via the
scheduling margin Key. In material master , MRP 2 View we maintain
scheduling margin key. And in Transaction OPP1->Planning->Scheduling and
Capacity Parameters ->Define floats we maintain the opening periods per
plant. I am attaching details of Opening period :
   opening period: Opening period is the time which the MRP controller
needs to analyse.Thus he has this buffer with him to rectify any issues
before converting the planned order into purchase requisition.
The opening period is only used in backward scheduling.
Suppose There is a requirement for a material on date =RD1
Let the Goods receipt processing time is= T1
Let the planned delivery time =L1
Let the purchasing Processing time = X1
Let the opening period for this material is P1
Time line for external procurement:
        Planned Del   Pur proc         GR Process
          Time            Time          Time
___|__________|_________|___________|___
              L1            X1         T1
   SD                                         RD1
Now accoring to Basic scheduling:
   Receipt/Requirements Date(RD1)
   Release/Start Date(SD) = RD1-T1-L1-X1
Now let me explain to you when the planned order an purchase
Requisitions are created:
Let us say the date on which you do MRP be MR1
OD = Opening Date
From above diagram :
                                 Opening Per
                                 In Sch Mar Key
__________________|______________|
XX                          OD                 SD
                                              Release/Start Date
If your MRP date(generally Today) is lying between XX and OD (and
excludind OD)then
MRP creates planned order and if it lies between (and indclind OD)
OD and SD then we create purchase req.
when your MRP date comes between the period OD and SD then you do not
have time left to analyse and therefore instead of you in such cases
forgetting and delaying system automatically creates purchase req.
      In general if , if your order start date or release date is after
the opening period from today then MRP will create planned order.
Oterwise it creates Purchase req.
Check also if you have the note 1063969 applied in your system.
I hope it solves the issue. Otheriwse I think you should open an OSS message with connection to your system,
best regards,
maria

Report for MRP PO

1. I want a report which diplays POs & PRs created through MRP & created manually. How?
2. Through Document type we can easily distinguish between the Purchase Requisitions that have been generated through MRP and those created manually. How?
Regards
VS

YOu can get the report for req created by MRP/Manually or any other criteria by using transaction ME5A
Use ME5A then from dynamic selection (On Maib screen color button) select the creation indicator by double clicking on it and entr the value B for MRP same way for any other REqs
This will give you the exact reports which you are looking for it so you don;t need to create the new document type for this purpose
rewards the points

MRP Creation Indicator

Similar Messages

Maybe you are looking for