Chnages in order type dependent parameters for various production senarios

Hello PP experts,
Order type dependent parameters are are very important for configuration of order type. OPL8 is the tcode used for the same.There are three screens like planning, implementation and controlling in OPL8.
Please let me know what will be the changes in these order type dependent parameters for following senarios,
1. Make to order with sale order
2. Make to stock with production order
3.Make to stock with collecive order
4. Engineer to order with the use of project and WBS.
Which fields and parameters will be changed as per the senario changes.
please elaborate.
Waiting for your reply with cross hands.
regards,
Mona Tiwari

Hi,
For MTS with production orders Normal settings will be ok.
For MTS with collective orders apart from normal settings you need to enable the check box in opjh ( define order type) for the goods movemnts in collective orders.
For MTO with sales order i think the normal settings will be ok.
These different order types are linked to production scheduling profile in opk4
Regards,
nandha

Similar Messages

Order type dependent parameters for process order

Hello friends,
In Order type dependent parameters for process order (T.C COR4), there is subscreen for Process data documentation.Inside it we have three options :a) Batch Record Required
b) Order Record Required
c) No Process Data Documentation Reqd.
Through F1 help whatever information i have got regarding them, is not cleared.
According to it, if i select Order Record Reqd, than first of all i will have to delete (archieve) the order record than only i can delete (archieve) the process order.The same is with Batch Record Required.
So according to it if i want to delete the process order than first i will have to delete order record.So guys may i know which order record firstly i have to delete?Than only the system status for process order will not have the status ORRQ (Order Record Reqd).
And one more thing friends,if i select the third option No Process Data Documentation Reqd than which process data documentation system will not create?Or what will happen if i select this third option?
Thankingy you guys in advance.

HI
For process data documentaion pls check the following link:
http://help.sap.com/saphelp_47x200/helpdata/en/89/a43ea8461e11d182b50000e829fbfe/frameset.htm
Thanks

Set up/maintain order type dependent parameters for order type PI01

hello all,
i would like to know how to set up/maintain order type dependent parameters for order type PI01 for a particular plant.
thanks,
maxx

Hi Maxx
Order types are maintained in T Code OPJH
Thereafter go to T Code OPL8 to maintain there dependent parameters and assign it to desired plant
Hope this helps
Rgds

Production order type dependent parameters

Dear Frndz,
plz help me out with the various parameters which can be set based on the production order type. and the step by step procedure to configure the same.
Regards,
Srini.

Hi,
Pls. find the step by step procedure as below :
Define order type-dependent parameters
In this step, you define the parameters that are valid for each order type and plant. The parameters are split up as follows on the tab pages:
Planning
Master data
Here, you define the data that influences master data selection or order master data maintenance:
You can decide whether production versions are selected automatically or manually.
The task list application is predefined as 'P'. However, you can also specify an additional task list application.
The routing selection ID defines, for example, the ranking order for routing selection.
Routing selection defines whether routings are to be selected and if so, how (manually or automatically) and whether reference operation sets can also be selected.
Alternative sequences and sequence exchange define whether alternative sequences are permitted and how the sequences are to be exchanged.
The task list type defines which routing type is permitted for production orders.
Operation dtl check defines whether operation detail screens are to be checked when the operations are transferred to the order.
Routing text defines that the text from the routing header is copied into the order.
You can activate the entry tool for operations to help you when you create operations.
BOM application defines how the BOM alternatives are to be automatically selected.
Search procedure defines how batch determination is to take place.
General
Substitute MRP controller/substitute production scheduler are proposed when you create production orders if an MRP controller or production scheduler are not specified in the material master, or if there is no reference to material.
Reservation/Purch. req. specifies whether certain order objects (operation, components) are relevant to MRP.
Collective purch.req. enables collective purchase requisition per order for externally processed operations or non-stock items.
Inspection type defines how a quality inspection is to be carried out.
Implementation
Status change documents
Here, you define whether you want change documents to be written if a status change occurs. You also define the level at which the change documents are to be written.
A status change document contains the following:
which status has been changed
who changed the status
whether the status has been activated or deactivated
the transaction in which the status change has been carried out
In the production order, you can define the status at the following levels:
order header level
operation level
material component level
production resource/tool level
Status change documents can also be defined independently of each other, at each of these four levels.
Note
If you have defined these parameters such that status change documents are written for a particular order level, the SAP System only writes a status change document for a status change from this point in time if the order (or operation/component/PRT) has been created since the status change documents have been activated.
Shop Floor Information System
You can specify, for example, whether order data is to be stored in the Shop Floor Information System. You can carry out reports using this system, for example, for materials, orders and work centers.
Documentation of goods movements
Here, you can specify that goods movements are to be documented with reference to an order. Then you can display goods movements, for example, using the order information system.
You can enter a profile for displaying documented goods movements on the tab page "Display profiles".
PDC
PDC active allows data to be exchanged with a PDC system.
Workflow
Workflow for PO chg. defines that a workflow is generated when quantities or dates that affect existing purchase orders are changed in the order. In addition, a default rule for the split is displayed on this screen.
So that this indicator is also valid for production orders the appropriate settings must be made in Customizing for the Project System.
Progress determination in orders
You can determine that progress values are calculated for order progress reports.
Controlling
Controlling
Here, you define the parameters relevant to controlling, such as, for example, costing variants for planned and actual costs and a results analysis key.
Distribution rule
Default (distribution) rule defines an automatically generated distribution rule for CO settlement.
Display profiles
Collective order display
Graphics profile defines how the collective order is to be displayed.
Graphic:
Here, you define parameters for displaying graphics of operations and sequences in the order.
Missing parts list
ProfMissPrtsLstOrdNo/PrfMissPrtLstCollOr defines how the missing parts list is to be displayed.
Documentation of goods movements
Goods movements defines which profile is used for displaying documented goods movements.
Activities
Create the necessary parameters for the order type.
HOpe this helps.
Regards,
Tejas
Edited by: Tejas Pujara on Oct 1, 2008 6:35 AM

Setting in Order Type Dependent Parameters

Hi Gurus,
Can anyone tell me the importance of Setting in Order Type Dependent Parameters ( T.Code OPL8) -
setting of purchase requisitions -
Reservation / purchase requistion - 1, 2 or 3.
What is the significance?
Srini

Hi,
If it is mainteaind 3 then, if there is any external operation if your production order then the purchase requisition will be created immediately upon creation of the order.
and the Collective request: Collective purch.req. enables collective purchase requisition per order for externally processed operations or non-stock items.
Hope this helps..
Regards,
Siva

Deleting order type dependent parameters

While deleting ordr type dependent parameters, the system is giving the foll error:
Deletion not permitted. An order still exist for plant XYZ and order type XYZ

I don't know if your project lead has approved of the steps you're taking. All I can say is you're setting yourself up for more trouble.
I don't know how far you have proceeded with this process & what all you have deleted, but if there is still time, I would strongly suggest to disband your present approach & instead work with your basis team to remove authorization for all activities pertaining to this plant for PP scope. At a later date if you wish to re-start the activities relating to PP, basis would just need to re-assign back the roles.
Anyway the above is just my personal views, I leave it your wise judgement.

Inspection type in OPL8 (order type dependent parameters)

HI,
Inspection type we are giving in material master in inspection type field, why we need inspection type field in OPL8 transaction. Is there any specific reason the field having in OPL8. Please advise me if any one knows the reason.
Srini

Hi,
Lets see it with the help of an example.
Lets say there is a material - X, which is supplied to two customers - A & B.
Customer A requires a quality certificate, while the customer B does not need any Quality Certificate or Quality Control. In such case, you can not assign the inspection type at material level.
Here, in this case, you would have 2 order types, one with Inspection Type assigned and the other order type without any Inspection type to meet such requirements. And that looks more practical in terms of monitoring the specific orders, costs incurred for specific order etc.
Revert for more clarifications.
Regards,
Rohit.

OPL8 Order type dependent parameters

Hi
In transaction opl8 routing selection some one changed the selection criteria due to this while creating order routing is not picking hence help me to capture the change done by whom and when.

Hi srinivasch:
I think that you can get this infor in the next path:
Into OPL8 Tcode access to the entry in wich were done the changes, then, go to Utilities(M) -> Change Logs, so then:
Enter the time period, the kind of changes taht you are tracking and execute it.
You can view the changes acordding with you criteria selection.
I hope this information be useful for you
Please letme know.
Regards
Omar Perea

Default rule in Order type dependend parameters - OPL8 - Order Settlement

Hello,
We are doing settlement of production orders via Tcode - Ko88.
After execution of the same, system is passing an FI entry to GL - which is mentioned in the Material Master (Valuation Class - 7900) i.e. through OBYC setting.
We have also checked the OPL8 setting (Order Type dependend Parameters - Controlling Tab) in which "Default Rule" is mentioned as - PP1 - Production Material full Settlement.
As the system is passing an entry via "Default Rule - PP1" stored in Order Type Dependend Paramenters:
1. What is the use of Settlement Profile (OKO7) & Allocation Structure (OKO6)?
2. Can we make "Default Rule" field as optional (In Tcode - OPL8) ? since all the settlements are resulting in same Material GL.
Waiting for a positive answer. Points will be assigned definitly.
Thanks & Regards,
Shridhar Sawant

Hi,
Settlement Profile:
In the settlement profile, you define a range of control parameters for settlement. You must define the settlement profile before you can enter a settlement rule for a sender.
If you want to settle the costs each time to just one cost center or just one G/L account, you need a settlement profile. As you cannot maintain the settlement parameters during settlement to a receiver, you must save the settlement profile either in the order type or in the model order or reference order.
Allocation Structure:
During settlement, costs incurred under the primary and secondary cost elements by a sender are allocated to one or more receivers. When you settle by cost element, you settle using the appropriate original cost element.
An allocation structure comprises one or several settlement assignments. An assignment shows which costs (origin: cost element groups from debit cost elements) are to be settled to which receiver type (for example, cost center, order, and so on).
You have two alternatives in settlement assignment:
You assign the debit cost element groups to a settlement cost element.
You settle by cost element - that is, the debit cost element is the settlement cost element.
This is a good idea, for example, if the required capital spending for an asset you are building yourself is to be monitored. These costs are settled by cost element to an inventory account in Asset Accounting at the end of the year, or when the measure is complete.
Each allocation structure must fulfil the following criteria:
Completeness
An allocation structure is assigned to each object to be settled. All cost elements in which costs are incurred, must be represented in the appropriate allocation structure.
Uniqueness
Each cost element in which costs are incurred may only appear once in an allocation structure. Only one settlement cost element may be assigned to a source within a particular allocation structure.
Source Structure:
A source structure contains several source assignments, each of which contains the individual cost elements or cost element intervals to be settled using the same distribution rules.
In the settlement rule for the sender you can define one distribution rule, in which you specify the distribution and receivers for the costs for each source assignment.
Thanks,
Rau

OPL8 (Order type dependent parameter)

Hi All,
        Please clarify the following will be grateful.
I have a inhouse material thatu2019s having alternative sequence. The above material uses order type PP01, so OPL8 (Order type dependent parameter) configured in such a way that ALTERNATIVE SEQUNCES is (Checked) and SEQUENCE EXCHANGE is u201C0u201D (i.e., No Selection).
For the above settings what I meant is, even though if a material is having alternative sequences that wonu2019t get copied in to the order.
But here is the issue starts for the following setting
u2022     ALTERNATIVE SEQUNCES is (Checked) and
u2022     SEQUENCE EXCHANGE is u201C0u201D (i.e., No Selection)
Alternative sequence operations are available for the order on COOIS screen for the following selection
LIST : Operations
Layout: 000000000001 (Standard)
Please explain me how ALTERNATIVE SEQUNCES and SEQUENCE EXCHANGE will work.
Thanks in Advance

Dear Madhan,
Assign value 2 for sequence exchange and check the impact at the time of order creation.
Check and revert back.
Regards
Mangalraj.S

Getting error wrong number or type of parameters for EAM_PROCESS_WO_PUB

Hi All,
I am Getting error wrong number or type of parameters for EAM_WO_PROCESS_PUB.PROCESS_WO API, pls any body can help me,pls send code for
EAM_WO_PROCESS_PUB.PROCESS_WO API.
Thanks&Reagrds,
Hanimi Reddy.

Hi srini,
I developed code for work order api EAM_PROCESS_WO_PUB.PROCESS_MASTER_CHILD_WO following and i am getting error wrong number or types of arguments in call to 'PROCESS_MASTER_CHILD_WO, pls see the code and help me
CREATE OR REPLACE PROCEDURE SANG_WR_TO_WO_API/*(ERRBUF OUT VARCHAR2, RETCODE OUT VARCHAR2)*/ IS
v_created_by number;
v_updated_by number;
v_updated_name varchar2(30);
V_ENTITY_ID VARCHAR2(30);
l_EAM_WO_RELATIONS_TBL EAM_PROCESS_WO_PUB.EAM_WO_RELATIONS_TBL_type ;
--:= EAM_PROCESS_WO_PUB.g_miss_EAM_WO_RELATIONS_rec;
l_eam_wo_tbl EAM_PROCESS_WO_PUB.eam_wo_rec_type; --:= EAM_PROCESS_WO_PUB.G_MISS_EAM_WO_rec;
l_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type ;--:= EAM_PROCESS_WO_PUB.G_MISS_eam_op_tbl;
l_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_op_network_tbl;
l_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;--:= EAM_PROCESS_WO_PUB.G_MISS_eam_res_tbl;
l_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_res_inst_tbl;
l_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_sub_res_tbl ;
-- l_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type := EAM_PROCESS_WO_PUB.G_MISS_eam_res_usage_tbl;
l_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_mat_req_tbl ;
l_eam_direct_items_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_direct_items_tbl ;
l_x_eam_wo_tbl EAM_PROCESS_WO_PUB.eam_wo_rec_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_wo_rec;
l__x_EAM_WO_RELATIONS_TBL EAM_PROCESS_WO_PUB.EAM_WO_RELATIONS_TBL_type ;--:= EAM_PROCESS_WO_PUB.g_miss_EAM_WO_RELATIONS_TBL;
l_x_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_rec_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_op_rec ;
l_x_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_op_network_tbl;
l_x_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_res_tbl;
l_x_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_res_inst_tbl ;
l_x_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_sub_res_tbl;
-- l_x_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type := EAM_PROCESS_WO_PUB.G_MISS_eam_res_usage_tbl ;
l_x_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_mat_req_tbl;
l_x_eam_direct_items_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_direct_items_tbl ;
l_x_return_status VARCHAR2(30);
l_x_msg_count NUMBER;
l_x_debug VARCHAR2(30);
l_output_dir VARCHAR2(30);
l_debug_filename VARCHAR2(30) ;
l_debug_file_mode VARCHAR2(30) ;
CURSOR CUR_WTW IS
SELECT
EWR.WIP_ENTITY_ID
,EWR.WIP_ENTITY_NAME
,EWR.ORGANIZATION_ID
,WAC.ORGANIZATION_CODE
,EWR.DESCRIPTION
,EWR.ASSET_GROUP_ID
,EWR.ASSET_NUMBER
,EWR.ASSET_NUMBER_DESCRIPTION
,WAC.ACCOUNTING_CLASS
,WAC.MATERIAL_ACCOUNT
,WAC.MATERIAL_OVERHEAD_ACCOUNT
,WAC.RESOURCE_ACCOUNT
,WAC.OUTSIDE_PROCESSING_ACCOUNT
,WAC.MATERIAL_VARIANCE_ACCOUNT
,WAC.RESOURCE_VARIANCE_ACCOUNT
,WAC.OUTSIDE_PROC_VARIANCE_ACCOUNT
,WAC.STD_COST_ADJUSTMENT_ACCOUNT
,WAC.OVERHEAD_ACCOUNT
,WAC.OVERHEAD_VARIANCE_ACCOUNT
,EWR.WORK_REQUEST_OWNING_DEPT_ID
,EWR.WORK_REQUEST_OWNING_DEPT
,EWR.WORK_REQUEST_PRIORITY_ID
,EWR.WORK_REQUEST_PRIORITY
,EWR.WORK_REQUEST_STATUS_ID
,WAC.ORGANIZATION_NAME
FROM
WIP_EAM_WORK_REQUESTS_V EWR
,WIPFV_ACCOUNTING_CLASSES WAC
,WIP_EAM_PARAMETERS WAP
WHERE
EWR.ORGANIZATION_ID = WAC.ORGANIZATION_ID
AND WAC.ORGANIZATION_ID = WAP.ORGANIZATION_ID
AND WAC.ACCOUNTING_CLASS = WAP.DEFAULT_EAM_CLASS
AND EWR.WORK_REQUEST_STATUS = 'Awaiting Work Order';
BEGIN
--i number := 1;
FND_GLOBAL.apps_initialize (1001255, 50326, 700, 0);
V_CREATED_BY := FND_GLOBAL.USER_ID;
V_UPDATED_BY := FND_GLOBAL.USER_ID;
v_updated_name := FND_GLOBAL.USER_name;
for rec in cur_wtw loop
l_eam_wo_tbl.WIP_ENTITY_ID := rec.wip_entity_id;
l_eam_wo_tbl.ORGANIZATION_ID := rec.ORGANIZATION_ID ;
l_eam_wo_tbl.ASSET_NUMBER := rec.ASSET_NUMBER;
l_eam_wo_tbl.ASSET_GROUP_ID := rec.ASSET_GROUP_ID ;
l_eam_wo_tbl.DESCRIPTION := rec.DESCRIPTION ;
--SELECT WIP_ENTITIES_S.NEXTval INTO V_ENTITY_ID FROM DUAL;
EAM_PROCESS_WO_PUB.PROCESS_MASTER_CHILD_WO
(P_PO_IDENTIFIER => 'EAM'
,P_API_VERSION_NUMBER => 1.0
,P_INIT_MSG_LIST => FALSE
,P_EAM_WO_RELATIONS_TBL => l_EAM_WO_RELATIONS_TBL
,P_EAM_WO_tbl => l_eam_wo_tbl
, p_eam_op_tbl => l_eam_op_tbl
, p_eam_op_network_tbl => l_eam_op_network_tbl
, p_eam_res_tbl => l_eam_res_tbl
, p_eam_res_inst_tbl => l_eam_res_inst_tbl
, p_eam_sub_res_tbl => l_eam_sub_res_tbl
--, p_eam_res_usage_tbl => l_eam_res_usage_tbl
, p_eam_mat_req_tbl => l_eam_mat_req_tbl
, p_eam_direct_items_tbl => l_eam_direct_items_tbl
, x_eam_wo_tbl => l_x_eam_wo_tbl
, X_EAM_WO_RELATIONS_TBL => l__x_EAM_WO_RELATIONS_TBL
, x_eam_op_tbl => l_x_eam_op_tbl
, x_eam_op_network_tbl => l_x_eam_op_network_tbl
, x_eam_res_tbl => l_x_eam_res_tbl
, x_eam_res_inst_tbl => l_x_eam_res_inst_tbl
, x_eam_sub_res_tbl => l_x_eam_sub_res_tbl
-- , x_eam_res_usage_tbl =>l_x_eam_res_usage_tbl
, x_eam_mat_req_tbl => l_x_eam_mat_req_tbl
, x_eam_direct_items_tbl => l_x_eam_direct_items_tbl
, x_return_status => l_x_return_status
, x_msg_count => l_x_msg_count
,p_commit =>'N'
, p_debug => 'N'
, p_output_dir => NULL
, p_debug_filename => 'EAM_WO_DEBUG.log'
, p_debug_file_mode => 'w'
END LOOP;
END SANG_WR_TO_WO_API;
COMMIT;
Thanks ,
Hanimi

How to identify which Internal order type is relevant for Budget manager

Hi,
How to identify which Internal order type is relevant for Budgeting i.e Budget Manager.
regards,
Rajesh

controlling-internal orders-budegeting and availability control -define tolerance limits for availabilty control
in which it is defined whether mail be sent to budget manager against the budget profile(budget profile is assigned to order type).
controlling-internal orders-budegeting and availability control -define tolerance limits for availabilty control-maintain budget manager
here budget manager is assigned to order type
assign me points if it is useful

Develop a report to track discount for various product

hi
i need to develop a report to track discount for various product depending upon the client

Hello Noor,
I'm not sure but if you are talking about the marketing attributes, you can definitely use FM - CRM_MKTBP_ASSIGN_ATTRIBUT_TAB
You need to pass the profile id, partner id and marketing attributes data. Thats it.
I think the FM you ar eusing for terrritory is fine. It should work.
I hope this helps.
Thanks
Vishal

Different order type to use for iStore

Hi,
We have 2 sites as per OU1 and OU2.
Set ASO: Default Order Type to IBE_CUSTOMER_1, IBE_CUSTOMER_2.
Now if we want to use more than this order type what we need to do apart from creation of new responsibility.
Thanks,
Ashish

Hello Ashish,
For release 12, the order type is now a Quoting Parameter which is setup at the OU level and not responsibility. However, there is a new iStore profile option introduced, "IBE:Default Order Type" which can be set at the User, Application or Site level. To get this profile option you need to apply Patch 7042892:R12.IBE.B - "R12: ASO: DEFAULT ORDER TYPE NOT AVAILABLE BY RESPONSIBILITY".
**Please note that the patch does NOT allow profile to be updated at Responsibility level. This is a MOAC limitation.
As per MOAC mandate, profile options at the responsibility level that are dependent on the operating unit have to be removed, or not supported at the responsibility level.
References:
R12: Is It Possible To Control Order Type by Responsibility Or Minisite Id in Oracle iStore ? (Doc ID 833163.1)
Regards,
Debbie

Overhead/order type - DEPENDENCY

Hi all,
I have created a cost sheet. We have 3 different processes in our operation and each process have different overheads rate.
I have assigned the dependency: overhead/order type D050 for each overhead in the cost sheet.
But when I executingCK11N the system is not calculating the o/h for the material. Itu2019s showing zero value for the o/h but in the process order it is showing the cost estimation value.
Can any one please guide me through this, whether I have missed out anything any where?
We have only one cost sheet and we are in ECC6.0 version.
Regards
SAP4ME

Hello
You have to define the different dependency based on the requirement and under each dependency you have to configure the different types overhead with different validity period and different percentage. Similary the samy may be assigned to the costing sheet. While assigning the costing sheet, ple clearly specify the base, what are the overheads willbe costed and enter the cost center as the credity key.
Please check all these above settings and come back if it is not solved.
Regards
Madhav

Chnages in order type dependent parameters for various production senarios

Similar Messages

Maybe you are looking for