cancel
Showing results for 
Search instead for 
Did you mean: 

Process order type?

former_member224727
Active Participant
0 Kudos

For the FERT material packing we have two different process order type. Type1 and Type2.

When we convert planned order of material1 to process order, it always picks type1 while for material2 it pickes Type2.

I like to understand where we define this relationship? How system knows to pick order type1 or type2?

Reply apprecaited.

Accepted Solutions (1)

Accepted Solutions (1)

sjeevan
Active Contributor
0 Kudos

You maintain order type in production scheduling profile  and you maintain that scheduling profile in each material.

You can also look at other options and their priorities in my first reply below:

https://scn.sap.com/message/11058639#11058639

former_member224727
Active Participant
0 Kudos

Thanks for reply. It helps me to understand my question. I have one more question to get clarify.

Now I have order1 for the material1. This order1 was converted from planned order1. I want to know what drive to planned order1? How I know that?

I'm going in MD63 but system says no req exist. How I know the reason to creates planned order1?

Answers (2)

Answers (2)

former_member208199
Active Participant
0 Kudos

Hi Eric,

When you convert the planned order from MD04, COR7, COR8 to process order system will pick the Process Order type based on following following priorities provided by settings.

1. Production scheduling Profile- CORY, Profile assigned in Work scheduling view of material

2. Carry Out Overall Maintenance of MRP Groups- OPPR

3. Carry Out Overall Maintenance of Plant Parameters

Go to Maintain >> Conversion tab >> Assign the appropriate Order type for Process order

Please check and revert back,

Thanks

former_member224727
Active Participant
0 Kudos

This helps Raj..

Now I have order1 for the material1. This order1 was converted from planned order1. I want to know what drive to planned order1? How I know that?

I'm going in MD63 but system says no req exist. How I know the reason to creates planned order1?

sjeevan
Active Contributor
0 Kudos

Go to MD04 and you will see the net requirement there.

milind_kulkarni5
Contributor
0 Kudos

Hi,

Conversion of Planned order to Prod.Order is related to 'Work scheduling view ' in respective material master.It causes the conversion planned to prod.

Pls. check planning strategy used in MRP 3 also.

Regards,

Milind

svs_sap
Active Contributor
0 Kudos

Hi

Once the planned order is fully converted to process order and you do not have any reference of it in MD04. If you are working in make to stock scenario , you will not come to know, what drives you to get that planned order which was converted to some process order for execution until history is maintained.

In case of make to order scenario you can fine the process order and for which sales order it is related and hope this can answer your query.

Regards,

Sharat

former_member208199
Active Participant
0 Kudos

Dear Eric sun,

1. If demand is there from MD61, you can check the pegged requirements in MD09 screen by putting      the planned order in that.

2. If demand is not there from MD61, say directly they have created, no Pegged retirements will be      available for that planned order in MD09 screen,

3. As MR. Sharat said if demand is there from Sales order(MTO), you will have traceability in planned      order assignment tab and production order assignment tab.

4.Once you converted the planned order to Production, no planned order details can exist.

Please check and revert.

former_member224727
Active Participant
0 Kudos

Hi Sharat,

I'm talking about make to stock scenario only. I can see planned order in process order screen, but if I go to MD04 I can't see the order number that screen. So if business ask me the reason of planned order it becomes difficult for me to explain what drives it?

Appreaiated if you can through some light on this!!!

sjeevan
Active Contributor
0 Kudos

If there are no requirements existing in MD04 then somebody might have manually created the planned order, there is no concrete way of proving that though. You can checkout the field PUSER in table PLAF to see who manually ran MRP which created the planned order or created that planned order manually.

Planned orders are what one would call are "soft" orders SAP did not provide many auditing features for them (keep a log of who created/changed them) as it is not necessary. MRP can always delete and re-create un-firmed planned based on changes in net requirements.

svs_sap
Active Contributor
0 Kudos

Dear Eric

when we create PIRs and run MRP and then PIR is revised with future dates, we don't get history of what was my initial requirements until unless we store such PIR requirements in some form of customized data.

Once such requirement was addressed by me by making a custom table in which customer wanted me to capture the requirement from sales, then how many iterations they edited that demand and finally agreed to produce etc. They were not ready to go with SOP. We captured this through module pool but a complex customize, but it is going well till date, i have not heard any problems after few years. And we asked them to archive data after few months and get back of data into some form in other hard drive if they need for analysis.

I do not know whether such a customization helps you, if it helps then you need a ABAP support and explain them the process of PIR creations, they can able to create module pool for you.

Regards,

Sharat

Former Member
0 Kudos

Determination of process order type could happen from multiple sources, some noted ones are below

1.Production scheduling profile in work scheduling view  of the material master

2.Plant parameters for MRP (OPPQ)

3.MRP Group

Production scheduling profile (PSP)  is first/primary contact to determine process order type, if not maintained, SAP checks for MRP group and lastly plant parameters for MRP (OPPQ).

Note: Process order type determination via PSP could be overwritten via default order type maintained in program PPBICO40 {if production orders are created in background mode}