ESYU: Planner Workbench Release process가 다른 user로부터 planned orders를 release

Purpose
Materials Requirement Planning - Version: 11.5.9 to 12.1
Information in this document applies to any platform.
11.5.9 ~ R12 version:
두 명의 users가 MRP Planner Workbench에서 Release를 위해 records updating을 진행하는 경우, 두 명 중 한명만이 update 후 실제로 release를
submit 했으나 두 명 user의 모든 records가 release 되어 버린다.
User1은 자신의 Planned Orders 만을 release 할 수 있고, User2 또한 자신의 저장된 Planned Orders 만을 release 해야 한다.
STEPS:
1. User 1이 MRP Planned Workbench로 log
2. User 1은 특정 planner code를 위한 current planned order recommendations 을 찾는다.
3. User 2가 MRP Planned Workbench로 log
4. User 2가 특정 planner code를 위한 current planned order recommendations 을 찾는다.
5. User1은 All for Release를 선택
6. User2도 All for Release를 선택
7. User1은 checking process를 끝낸 후 저장
8. User2는 아직 checking process를 끝내지 못해 save를 아지 않은 상태로 남아 있다.
9. User1이 [Release] button을 선택
10. User1이 [Release] button을 선택시 User1과 User2에 의해 저장되거나 check 된 모든 planned order recommendations이 Work in Process와
Puchasing modules로 released 되어 버림
Cause
이 issue의 원인은 현재 MRP planning의 경우 expected functionality 이다.
MRP Workbench Release process는 모든 planner에 의해 check 되거나 저장된 모든 planned orders를 항상 release 한다.
Bug 891669 : Enhancement Request
PLANNER'S WORKBENCH SHOULD RELEASE ORDERS BASED ON PLANNER NAME NOT BY BATCH
It is explained that this is current functionality in the following rejected Enhancement Request:
Bug 891669 : PLANNER'S WORKBENCH SHOULD RELEASE ORDERS BASED ON PLANNER NAME NOT BY BATCH
Solution
Solution을 적용하기 위해 아래 steps을 실행:
1. 모든 planner에 의해 check 되거나 저장된 모든 planned orders가 [Release] button에 의해 항상 release 되는것은 현재 MRP Workbench
Release process에서는 correct functionality 이다.
2. ASCP Planning의 경우엔 Planner/User에 의해 Release process가 아래 option에 의해 처리 가능하다.
-- profile MSC:Released Only By User
-- Standard MRP에서는 이 option은 사용할 수 없고 고려되지 않는다.
Reference
Note 311053.1

Similar Messages

Release status for planned order

Hi All
I am running MRP weekly,system is generating the Planned order once MRP is completed.Here my requirement is i want release status for planned order, at the same time once planned order is released i dont want user to change any data in planned order.
Somebody explain me about the settings of action control of planned order.
Regards
Srinivasan.P

Hi,
Sorry to say but there is nothing like system status for Planned orders.
Check below thread,
[Release of Plan orders|Planned Order Release]
Regards,
Dhaval

Planned Order Release from SNP to R/3

Hello All -
We are facing a situation where in we just want to release only a certain number of planned orders that are there in a particular horizon...
Now i am not sure as to can we or we cannot do that? can anyone please confirm and explain as to what transaction code we use to release the data into R/3.
Regards,
Suresh

In Spro,you can configure
Supply Chain planning>Supply Network Planning>Basic Settings-->Configure Transfer to OLTP system
as "period transfer"
and use /n/sapapo/c5 to process the change pointer with creation time stamp date range as horizon you want to transfer
I wonder why you need to transfer SNP transfer Orders to R/3..SNP being rough cut planning for critical compenents and resources.
Edited by: Thukral on Sep 11, 2008 7:35 PM

What is the difference between Release process and Prchase order process?

Like both processes are used to replenish, but than whats the need of both the processes.One of the process can be used to come up with request.Correct me if i am wrong.Kindly explain with an example

Hi Nandan, 
In purchase Order we have fixed date , quantity and schedule on which supplier has to deliver the items . 
Example:PO with Item A: 
to be deliver on 12-May-2010 20 quantity 
to be deliver on 12-Jun-2010 40 quantity 
In Release process we have quantity/price schedule agreement of item between supplier and customer.it specifies certain amount of quantity of the products that a supplier is to deliver to the customer in a specific time period. Customer uses MRP run at regular intervals and determines what exact requirement quantities are to be released from the scheduling agreement on certain dates.this schedule lines then releases to SNC to inform supplier about current demand 
In schedule agreement schedule lines have the following status : 
1)Fixed dates and quantities:Quantity and date of the schedule line are fixed and will remain unchanged. The schedule line belongs to a delivery-relevant release. The supplier can deliver the quantity without waiting for another acknowledgement or the customeru2019s request. 
2.Production and material go-ahead:The schedule line belongs to a forecast delivery schedule that is not relevant for delivery and is in the production go-ahead period. The supplier can, therefore, procure the materials for manufacturing the ordered products and start with production. If the customer cancels a schedule line, the supplier can invoice the material and production costs. 
3.Material go-ahead:The schedule line belongs to a forecast delivery schedule that is not relevant for delivery and is within the material go-ahead period. The supplier can, therefore, procure the materials that s/he requires for production. If the customer cancels a schedule line, the supplier can invoice for the material costs. 
4.Preview:The schedule line belongs to a forecast delivery schedule that is not relevant for delivery. The schedule line is not binding and may possibly change. The supplier can use the data for his or her own planning, however. 
Exmaple:We have schedule agreement of 1000 quanity for Item A and time period start date:30-Apr-2010 end date:1-May-2011 
Customer runs MRP/planning from he gets following schedule line with status as mention above 
quanti ty 100 with schedule line status Fixed dates and quantities which means Quantity and date of the schedule line are fixed and will remain unchanged. The schedule line belongs to a delivery-relevant release. The supplier can deliver the quantity without waiting for another acknowledgement or the customeru2019s request. 
quanti ty 200 with schedule line status Production and material go-ahead which means schedule line belongs to a forecast delivery schedule that is not relevant for delivery and is in the production go-ahead period. The supplier can, therefore, procure the materials for manufacturing the ordered products and start with production. If the customer cancels a schedule line, the supplier can invoice the material and production costs. 
quanti ty 300 with schedule line status .Material go-ahead which means schedule line belongs to a forecast delivery schedule that is not relevant for delivery and is within the material go-ahead period. The supplier can, therefore, procure the materials that s/he requires for production. If the customer cancels a schedule line, the supplier can invoice for the material costs. 
quanti ty 500 with schedule line status Preview which means The schedule line belongs to a forecast delivery schedule that is not relevant for delivery. The schedule line is not binding and may possibly change. The supplier can use the data for his or her own planning, however. 
Note that total quantity of product is 1000.,Depending upon schedule line supplier can plan his/her activity. 
Summary: In Purchase order supplier has to deliver fix amount of quantity on fixed date and time to the customer .
In Release process supplier can deliver the product depending upon schedule line status as mention above so advantage of using release process we fixed period and fix quantity in that period customer can send his demand to supplier whenever customer requires in schedule agreement time period. 
Thanks,
Nikhil

Mass Processing of Planned orders

Hi all,
We can do mass availability check for the planned orders and we can firm the planned orders for which the materials are available through COHV but can we have a output log after the mass processing so that we can see the list of planned orders got firmed and for any other messages.
Regards
Kumar

Dear,
In COHV or COMAC.
in mass processing gtab page
select function = material availability check, execute it.
In selection tab page
Plant
Order type
System status - MSPT.
Or
Start the report PPCOXPR1 with the T.code SE38
Then try with Tcode CO24..
Regards,
R.Brahmankar

Output message of PO in ECC not processed automatically after order released in GTS

Dear Experts
PO created in cobalt was blocked in GTS due to legal control. output message of PO was blocked, after the PO was manually released by the user next day, AU open the PO and saved it. output message got processed.
Can you please let me know, why system is not processing the output automatically after the PO is released in GTS.
Is this the standard process?
Thanks
Kiran

Hi Kiran,
This is called follow on function in GTS.
When document is released, you could trigger background job regularly to process these document.
Open the area menu for SAP GRC Global Trade Services in your feeder system (with transaction code/SAPSLL/MENU_LEGALR3) and choose Recovery Follow-On Functions in Feeder System .
Choose one of the following entries to configure the follow-on functions for the selected application level: Materials Management Trigger Follow-On Functions for Purchasing Documents
Check more details in help document.
Trigging Follow-On Functions after Document Release in SAP GTS - System Administration - SAP Library
Best regards,
Vincent

User exit in planned Orders

Hello all.
I have been search for a user exit in planned orders that allow me to define some code in it to triger some changes. this user exit should be at time of planned order is saved.
I have already search in this forum and I found out how to find the user exits by transaction. I have tried for transaction MD12 but did not found any suitable user exit.
Does any one know any user exit that could make my life easiser
thanks
Manuel Antonio

You can try the following BAdIs:
You can use the Business Add-In (BAdI) MD_PLDORD_CHANGE to change, before posting, data from planned orders, which have been created, changed, or deleted as a result of planning a material or manual processing.
The Business Add-In allows you to fill and change fields from planned orders in the PLAF table. It also supports filling of customer-specific fields in the customer include CI_PLAFDB.
You can execute the Business Add-In in the planning run in the following areas:
Material requirements planning
Master production planning
Long-term planning
You can also carry out the Business Add-In in all applications, which execute manual planned order changes. Examples of this kind of application are:
The dialog transactions for creating and changing planned orders (MD11, MD12, MS11, MS12)
The Business Application Programming Interfaces (BAPI) for creating and changing planned orders
all applications that explicitly or implicitly create or change planned orders, for example the planning table of repetitive manufacturing, repetitive manufacturing confirmation, capacity planning, assembly order processing and so on.
Requirements
When planning a material or manually processing a planned order, you must change individual fields in the planned order or provide entries for customer-specific enhancements of the planned order structure.
Standard settings
The Business Add-In is not active in the standard.
The Business Add-In cannot be used multiple times.
The Business Add-In is not filter dependent.
Activities
To activate the Business Add-In, you must create an active implementation. To do this, choose the following path in the SAP Menu: Tools -> ABAP Workbench -> Utilities -> Business Add-Ins -> Implementation
For more information about this procedure, see the SAP Library under
Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.
Further notes
Documentation on the BAdI method CHANGE_BEFORE_SAVE_MRP
Documentation on the BAdI method CHANGE_BEFORE_SAVE_MAN
You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:
1. Choose the tab page Interface.
2. Double-click on the relevant method.
3. Click on the right mouse button and choose Component documentation.
Update Planned Orders (MD_PLDORD_POST)
Use
Application components: PP-MRP, PP-MP-MPS, PP-MP-LTP, PP-REM
Function group: M61P, M61U
You can use the Business Add-In (BAdI) MD_PLDORD_POST to further process data from planned orders, which have been created, changed or deleted through the planning of a material or as a result of manual processing.
The Business Add-In allows you to publish the created and changed data from planned orders and can be used to update customer-specific tables or to connect to information systems and workflows.
You cannot use the methods of the Business Add-In to change the planned orders themselves. The planned orders are always posted in the communicated form.
You can execute the Business Add-In in the planning run of the following areas:
Material requirements planning (PP-MRP)
Master production planning (PP-MP-MPS)
Long-term planning (PP-MP-LTP)
You can also execute the Business Add-In in all applications, which carry out manual planned order changes, for example:
The dialog transactions for creating and changing planned orders (MD11, MD12, MS11, MS12)
The Business Application Programming Interfaces (BAPI) for creating and changing planned orders ( PlannedOrder Create, PlannedOrder Change)
All applications that explicitly or implicitly create and change planned orders, for example the planning table of repetitive manufacturing, repetitive manufacturing confirmation, capacity planning, assembly order processing, and so on.
Standard settings
The Business Add-In is not active in the standard.
The Business Add-In can be used multiple times.
The Business Add-In is not filter dependent.
Activities
To activate the Business Add-In, you must create an active implementation. To do this, choose the following path in the SAP Menu: Tools -> ABAP Workbench -> Utilities -> Business Add-Ins -> Implementation
For more information about this procedure, see the SAP Library under
Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.
Note that the Business Add-In can be used multiple times and therefore all active implementations are called and run through.
Example
The following is a possible use for the methods of this Business Add-In:
When planning a material or manually processing planned orders, you want to log the changes made to the planned orders or the triggered subsequent functions.
The subsequent processing of certain planned orders or individual data from the planned orders occurs in an external planning system. In this case, you can log the corresponding changes to these planned orders in a user-defined table during planning. Using a separate report, you can select the data from the log table and process it further.
Further notes
Methods
Update Planned Orders: Requirements Planning - POST_AFTER_SAVE_MRP
Update Planned Orders: Manual Processing - POST_AFTER_SAVE_MAN
You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:
1. Choose the tab page Interface.
2. Double-click on the relevant method.
3. Click on the right mouse button and choose Component documentation.
Regards
Ram

Differemce between PROCESS ORDER,PLANNED ORDER AND PURCHASE ORDER??

what is th edifference between PROCESS ORDER,PLANNED ORDER AND PURCHASE ORDER ??? can any one explain with some examples?
n.bhardwaj
[email protected]

Process Order:
Process order / Production order are activities within a business, where the production planning team team creates to absorb costs / evaluate costs / and check against planned figures. There would integration between MM/FI/PP to create such orders and process.
Planned Order:
A request created in the planning run for a plant to trigger the procurement of a plant material for a certain quantity for a specific date.
Purchase Order:
A request or instruction from a purchasing organization to a vendor (external supplier) or a plant to deliver a quantity of material or to perform services at a certain point in time.
Regards
AK

Material shortage for Planned Order (Discrete Job) in PWB

Client has planned orders on planner workbench (PWB) ready to release as Discrete Jobs but, because they have frequent revisions, they waits till all components (required to build job) are onhand before releasing from PWB.
They would like an easy way to either check or be notified when the last component required for job is received into inventory so they can release from PWB. They cannot use the standard "Discrete Job Shortage Report" as the job is not created yet. And they don't want to release from PWB till ALL material is onhand
Could we create a custom report perhaps (using same logic as "WIP Mass Load" to determine all component required versus onhand), but does anyone have a better solution how we can solve this?
Regards,
Hugh
Edited by: user13050057 on 13-May-2010 02:09
Edited by: Hugh Parker on 13-May-2010 08:13

1) Why would you check for components of subassemblies? e.g. Say your BOM looks like this.
FG1 is made up of SA1 and SA2 and COMP1.
SA1 is made up of COMP2 and COMP3.
Say you are releasing planned order for FG1. As long as the planned order is pegged to onhand for SA1, SA2 and COMP1, you are good. Right?
2) If you have to add custom logic, I would do it using a when-validate-record personalization on the PWB. The personalization will call a function that accepts order number ; does all pegging checks and returns true or false. If it returns false, then the personalization returns error and does not allow release of the planned order. The function will have to be an interative program that traverses the pegging loop to ensure that all lowest level demands are pegged to onhand.
Hope this helps
Sandeep Gandhi

Workflow for P.O release process.

Hi Guys,
As per the one of the thread I have done setting as per the below. Ref last 10 line for the details of the problem.
Hi,
1) Work flow: - Work flow is standard functionality of SAP.
I give one example to u.
In the case of purchase order creation, First purchase person create purchase order, then first purchase order approved by purchase head and then auditor approved purchase order on print of purchase order.
With work flow you can send soft copy of purchase order to both person purchase head and auditor to approve your purchase order.
Due to this your process for purchase material is faster then manual process.
2) You can implement work flow in purchase order release strategy with below mention detail.
For mail facility, you need to activate workflow for PO release procedure;
*Go to SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders *
Define Release Procedure for Purchase Orders > Release Codes >
here assign Workflow indicator as "1" against each Release Code
Now come to SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders >
Define Release Procedure for Purchase Orders > Workflow >
Here against each release code assign OT as US and respective User ID's for Release Codes.
Now Go to OOCU > here under MM, go to MM-PUR,
Now click on "activate event linking"
Here open "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button
Here activate "Event linkage activated" and also activate "Enable usage of event queue" and Save data.
Same way and click on "Assign agents" and proceed all above steps.
Now create a PO and check the SBWP for SAP Mail of respective Users
This was the details given by the thread but now I have completed till
OOCU > here under MM, go to MM-PUR,
Now click on "activate event linking"
Here open "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button
Here activate "Event linkage activated" and also activate "Enable usage of event queue" and Save data.
For proceeding futher as said in the above procedure. I am getting User ID inside WS20000075 when I click on Assign Agents but I am not getting the details button to repeate the step as said.
Please let me know whatever I have done is enough to get the mail or is there any thing else need to be done.
Thanks
Dhanu

Hi,
release code and release group should be assigned in the authorization object for the approving authorities.
apart from this the settings looks ok and it will work

Core Interface: Planned Order Integration

Hi
We are planning a product in both systems (ECC & APO). We want to restrict the Planned Order Integration b/w ECC & APO which are generating in ECC. At a same time we want a Planned order integration which are generating in APO.
Is there any standard BADI, USER Exit ?
Kindly give your valuable inputs for my mentioned query.

Hi Gurvarender,
Find this Customer exist for planned order
In SAP APO
Customer Exits For Planned Orders
●      APOCF004 u2013Inbound processing of planned orders
●      APOCF020 u2013 User-specific fields in the order interface
●      APOCFPIP u2013 Publication of in-house production orders (planned orders)
In SAP R/3
Customer Exits For Planned Orders
●      CIFORD01 u2013 Enhancement for order inbound interface .
●      CIFORD02 u2013 Enhancement for the transfer of customer-specific order fields )
●      CIFORD03 u2013 Enhancement for inbound customer-specific fields in the in-house production order
Regards,
MJ

Repetitive Manufacturing planned order long text

In our scenario, we will use the repetitive manufacturing process with planned order. However, the users would like to attach the long text for each planned order.
Is there any use exit or BADI to support this?
Regards,

Hi ,
i think there is no user exit or BADI which can work in your case.
When we required similar functioanolity we landd up in desigining entirely new Z tocde which would accept the long text ofr the plan orders and save it.
we created coplue of ztables to store the plaf link.

Availability of components at order release

Hi pp guys,
Can anybody tell me what setting is required so that user can come to know that all components are available in the prodn.order otherwise cancel the release of order
Thanks in advance

Hi,
Use tcode OPJK,
select your plant, order type and business process 2 (for order release).
1.Remove tick mark in No availability check.
2.Checking rule - Input your rule (std PP)
3. Type of comp check - ATP check.
4.Material release - 3- No release if parts are missing.
With these setting, if missing parts found when releasing the order,system pop up the message & release rejected.
Regards,
Dharma

VSF and planned orders same day

Hello,
When running MD04, forecast (VSF) and planned orders are landing on the same day. This is causing confusion for the users. Is there a setting that's causing this to happen? We are using checking rule PP. Should we be using A instead? The planned order should actually be showing up before the forecast because we don't want the inventory to show negative from the forecast. Any help will be appreciated.
Thank you.
MZ

Hi MZ
On the standard MRP process, the planned order basic finish date will generally match the requirement date.
Check this document which explains the scheduling in more detail:
Backward Scheduling for In-House Production - Material Requirements Planning (PP-MRP) - SAP Library
BR
Caetano

Planned Order to Purchase Order report in SAP

Dear All
The Business process is Planned Order - Converted to Purchase Requsition - Converted to purchase order .
Is there any report in SAP , which shhows the direct link between Planned order to Purchase Order ?
Regards
Shyam

I have never seen a standard report, build a query based on tables PLAF, EBAN and EKET should be involved

ESYU: Planner Workbench Release process가 다른 user로부터 planned orders를 release

Similar Messages

Maybe you are looking for