Manual cration on planned order in Planning w/o Final Assly segment
Hello everyone,
Is there any way to change/create SNP planned orders manually in SNP Planning book or product view in Planning w/o final assly segment.
I am not able to create manual order in RRP3 view in Planning w/o final assly segment. It is giving below error.
Note: I am able to create planned order in MTS segment.
I am not sure whether SAP has purposfully not given this functionality. However, I believe user should able to create/change planned order in planning w/o final assly segment.
Regards,
Abhay
Hi,
If the planning strategy is Make to order, planned orders should not be created manually in RRP3 view and it comes from sales order only.
Regards,
LV
Similar Messages
-
Dispatching of Planned Order in Planning Table
Hi Gurus,
What do we understand by dispatching of planned orders?
When the orders are need to be dispatched?
Is it after firming of order?
What impact it will have on the system after we dispatch the planned order?
I observe that after dispatching the planned order, we have tick on capacity dispatched. In MD04, for the planned order there are double stars for dispatched orders?
Can anyone explain the this functionality in simple way.
Points will be rewarded.
SriniHi,
Normally we can do the capacity leveling for Plannend order and Production Order. In R/3 , MRP run dosenot consider Capacity Over load, Capacity leveling is required to for Planned order.
U reserve the Capacity on particular date by despatching the planned order at Planning Table. Which results in Capacity is scheduled on that Particular date & time for that Planned order.System will not allow to despatch another order in the same date.
Firm & Capacity scheduled check box is activated when u despatch the Order. MRP will not reshedule that Planned order.
when u convert that Planned order to production order, system will schedule the order with same date & set the despatch status for Each opeartion.No need to despatch the Prod order Again.
Pradeep -
After firming planned order, new planned order is generating in MRP run
Hi Experts,
I am using SAP AFS. Planning strategy is 21- MTO with Project settlement. MRP type is PD. Lte size is EX. Procurement type is X.
We are using the production versions. Individual / collective reqmts is 1. Planning time fence is not maintained.
In sap AFS T.Code for MRP run is /n/afs/md02. After receiving the Sales order, MD04 screen gets updated accordingly and I am running the MRP.Planned orders are generated accordingly. I am firming the planned order manually through MD04. The satr mark is also appearing.
My problem starts now. If I am running the MRP again for the same requirements another planned order of the same qty. is getting generated. That means after the second MRP run, I am having two planned orders (one firmed plnd order) and second is the new planned order. My requirement is that MRP should not generate any new Plnd. order / PR's if there is no new Sales order.
The parameters for MRP run are "1" for "Create PR's", '1" for "Plng Mode" and '"1" for "scheduling ".
I have tried in all the possible ways, but of no use. Still new plnd order is generated after firming the 1st plnd. order in MRP run.Thanks all for your feedback..
@ Vishal
1. Yes, Both Old firmed planned order and newly generated planned order have the same grid value
2. For both the planned orders :
Special Stock is E u2013 Orders on hand,
Consumption is V,
Sales order is the same (As we are using MTO , Strategy 21) and same WBS element.
3. First planned order is not in the assigned tab of MD04. This means that has been allocated to some object. u2013 I didu2019nt got this point. Can u please elaborate?
@ Nikhil
1. Quantity of sales order is not reducing after firming the sales order
2. Account assignment category for both the planned orders is u201CZu201D - Indiv.cust./project
I have made some more observations and found the following differences between the two planned orders
From MD04 , keep the cursor on corresponding planned order
& click on upward arrow ( available on bottom side of the report).
It will show what will be the originating requirements i e. for which requirements this planned order generated.
For Firmed planned order it is taking me to screen u201CPegged Requirements
u201D*And the following data is present:
Planned dates: 04.07.2010
MRP element No. 3100001185 (Sales Order No.)
MRP element item 100
Scheduling No. is 1
MRP element indicator - VC u2013 Order
MRP element data- 3100001185/000100/0001
Plng segment u2013 3100001185000100000
P.O / Order Type u2013 ZX
Rec/reqd Quantity 10
MRP element u2013 Order
For new planned order generated, I am going to Screen *u201CProcurement without Requirementsu201D
*The following data is present
Planned date 03.07.2010
MRP element No. 0000123522 (Planned order No. of the newly generated after MRP Run)
MRP element Ind. u2013 PA
MRP element data 0000123522/SO
MRP element item 1
Scheduling No. 1
MRP segment 20
Plng segment u2013 3100001185000100000
Rec/reqd Quantity 10
P.O/Order type- KD
MRP element u2013 Plnd Order -
Planned order MD11/Planned order MD02 for sale order
hi
How to identify a planned order ref to sale order created manually MD11 or created by MRP run MD02.
is there any table entries plaaned order and transaction codes?
i got two planned orders qty1 and qty5 from a client for same sale order item.
what could be possibilites.
-ashokDear,
Couple of check,
1) Check Lotsize ?
2)Planning strategy?
3)Individual /collective requirements indicator in MRP4 view?
For MTO, you will get one Planned Orders per one requirement element.
So, you are getting number of Planned Orders for FG?
For MTS Scenarion, the Lot Size EX will work just like the Daily lotsize (TB).
So, system will club all the requiremnts per day and propose the Planned Orders for 1 day requirements.
You will get separate planned orders for the Next day.
Hope clear to you.
Regards,
R.Brahmankar -
Planning Planned order in planning table graphic (PP-PI)
Is it true that cannot plan planned orders, that will be destined to process orders in the table of graphical planning? (CM25).
Because I tested with all the profiles standard and no one leaves me to dispach planned order....
Thanks regardsHi
Try following things in spro in development & test
goto
Capacity requirement Planning-Operation-scheduling-scheduling paramets for Planned order
This may of help.
regards
Prakash -
Collective display of LTP planned orders (inactive planned orders)
Hi All,
Is there any standard t-code/report which gives list of all inactive planned order and material combination?
If yes please let me know the same..
Regards,
Sonal.Dear Sonal,
The list of planned order can be fetched using the transaction code COOIS.
In the above transaction in the top left corned,check the "planned order" option and execute.
Table "PLAF" can also be used to view the planned orders.
Regards,
Joseph Charles Vaikathussery -
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 AntonioYou 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 -
"CLOSED": HOW TO LOAD FIRM PLANNED ORDERS OF ANOTHER PLAN INTO ASCP PLAN?
Hi everybody,
How to load firm planned orders of plan 1 into plan 2?
Business Case:
Customer uses a separate planning for order intake. During order intake the requested due date is validated based on ASCP Gantt Chart. Bottlenecks are resolved. For make items firm discrete jobs are created, if adjusted suggested due dates are manually changed. For buy items firm planned orders are created for manually changed suggested due dates.
If the order is accepted the demand is transferred from the Order Intake MDS into the so called Operational MDS. The firm discrete job will be automatically visible in the operational ASCP Plan (after data collection/running ASCP Plan).
But how is it possible to include ONLY firm planned orders of another plan into your current plan?
PLAN1 asigned master demand schedules
- O_MDS1
- O_MDS2
PLAN2 assigned master demand schedules
- O_MDS1
- O_MDS2
- T_MDS
I want to transfer the firm planned orders from plan2 to plan1.
Thanks for all your inputs,
Catalina
Message was edited by:
user447176Since you need to run a data collection to load the new discrete job, I suggest you to add a custom step in the data collection.
This custom step will
1) select all firmed planned order in plan 2
2) put the firm planned order into a new schedule through staging tables (MST_ST_SUPPLIES) .
3) collect the data
Then run plan1 with this schedule defined as demand schedule for your new plan. -
Prevent Planned orders creation in Sourcing Org
Hi,
We have a customer requirement as below:
Supply Chain : Org1 <-- Org2 <--Org3
Item Name: X
Item X has demand in Org1 procured from Org 2 by Sourcing "Transfer From"
Item X in Org2 has planned order demand which triggeres a Planned Order in Org2 and to be procured from Org 3 by sourcing type "Transfer From" and it will create a Planned Order in Org3 which has sourcing "Buy from" External supplier.
Org1 : Sales Order -->Planned Order1 for Item X
Org2: Planned Order Demand2 -->Planned Order2
Org3: Planned ORder deamand3-->Planned Order3
Planners are different for Org2 and Org3 wan to do releases indivudually on their own schedules.
Planner in Org2 want to ensure Planned order3 in org3 not to be released earlier than ISO creation in Org2 for item X.
How to prevent planned order creation in Org3 having transfer planned order from Org2 to org3 for ISO creation.
Need your valuable inputs.
Regards,
Kumar KancherlaHi Kumar
If I understand your question, the requirement is not truely about Planned Order Creation but releasing a planned order in Org3 before ISO is recieved in Org2 from Org1?
This is more of a business process issue than planning since plan will provide a replenishment suggestion when there is a requirement based on sourcing rule. I'm assuming that these 3 orgs are planned in single ASCP Plan.
One way to enforce this business process is by using "Auto-Release within Time Fence". Since lead times for Item X will be longer in Org1 vs. Org2 and Org3, planned order in Org1 will be released first triggering Internal Req/ ISO between Org1 & Org2 first and then between Org2 & Org3. While this may be OK if you plan to implement all suggestions from ASCP without manual intervention, it may not be acceptable to some planners who may want to control the release process manually.
You may try it out with a limited set of items initially before rolling it out for all item/ orgs.
I re-iterate that this issue is more of a discipline that planners need to use their discretion and due diligence to collaborate with other planners to ensure that lower level supplies are released only after a firm demand is released from higher level.
Please feel free to let me know of any further concerns in this respect.
Thanks
Navneet -
User exit/ badi needed for planned order create/change,collective ATP check
Dear All,
I'm looking for a user exit/ badi which can be used for planned orders at the stage of
mass collective availability check (COMAC tcode) update; or at some other relevant stages of mass update of planned orders.
I need after collective availability check to perform the following:
1) to copy date from "total comitment" field on header tab of planned order and paste it (replace old date) to order finish date on header screen
then
2) to start a scheduling.
Very appreciate your help.
Best Regards,
Andrey
Edited by: Andrey Kruglov on Apr 15, 2010 3:06 PM
Edited by: Andrey Kruglov on Apr 15, 2010 3:07 PMDear,
Use the BAPI : BAPI_PLANNEDORDER_CHANGE
Or use the function module MD_SET_ACTION_PLAF for Schedule planned order.
and the transaction MDAC Execute action for planned order
This function module includes the following actions:
Explode BOM
Explode BOM, check availability
Check availability, only explode BOM in the case of a requirement
Check availability, do not explode BOM
Reset availability
Change planned order data
Schedule planned order
Delete planned order
Assign the key for the respective action control to the materials in the material master (MRP 4 view).
Please refer this thread,
Re: MDVP for collective orders
Regards,
R.Brahmankar -
BAPI for Scheduling Planned Order
Hi,
Please tell me if there are any BAPIs for Scheduling a Pllaned Order and for Deleting a Planned Oredr.
Thankes & Regards,
RahulBAPI_PLANNEDORDER_CHANGE Change planned order
BAPI_PLANNEDORDER_CREATE Create planned order
BAPI_PLANNEDORDER_DELETE Delete planned order
BAPI_PLANNEDORDER_EXIST_CHECK Planned order existence check
BAPI_PLANNEDORDER_GET_DETAIL Get details for planned order
BAPI_PLANNEDORDER_GET_DET_LIST Get detailed planned order list
All bapi's related to planned order processing
BR
Manthan. -
Query on open planned orders details with process order GR details
Dear Experts,
I need to create a query in SQ01 where the requirement is as given below,
Query output should display the open planned orders (Planned orders which is not converted to process order details) details for a material like Planned order number, Planned order quantity, Start date, Finish date and also the details of the list of process orders created for the same material with its details like PO qty, GR qty, Basic start date, Finish date, Actual finish date, BOM Component material codes, component quantity.
But i tried creating this query by joing the tables PLAF+ AFPO+AUFK+ AFKO+RESB . My input parameter will be the Material Number for which Planned order and Process orders are being created.
But i am unable to generate the output when i create a query by joining these tables
Is it possible to obtain the output for open planned order details and process order details in a single query ?
I am failing in my repeated attempts
Please provide your suggestions for developing this query
Regards,
J.BalakrishnanDear Bala,
as alternative , for use a query report and not a custom abap report, you can try to read data from MRP tables MDKP and MDTB . In these one tables you can find both elements (planned order and production orders) for to start to research all details that you need.
You can also use MDTB-DELKZ to filter only planned order (PA) and Production order (FE).
With the number order you can read the RESB table in order to define components details.
With this table would you the advantage to have always the opened orders.
If the following table are empty you should make a little customizing modification so that once MRP run will write them.
Give me feedback if i have been useful for you.
Daniele -
Planned Order, with first Prod Version.
Dear All,
I am Trying to use Production version for diffrent style of Production Req for same product.
When i Gave PV in MD61, for diff days, diff PVs,
Is is not reflecting in PLanned ORders.
Planned Order have only one PV. for all RIRs.
Kindly let me know the,
Where cud i miss .
In MRP 4 Selection is 3,
Ind/Coll : 1
Stratgy :40
Regards
RaghuRaghu,
1)check material master selection/explosion of BOM is always by by production.
2) lots size should not have oevrlapping.
3) and you cant create PIR in same period with differnt versions.
4)You might want to check whether the In-house Prod Time in Material Master has been maintained. I would think that this is the cause of the inconsistencies.
By right, if you run MRP by lead time scheduling, you don't need to enter the In-house Prod Time in MRP 2 view, because MRP will calculate the prod time by using your routing data.
5)Message no. MD425 ,
Please check the routing for all level in CA02 and do the consistance check through CA02ExtraConsistance check.
6)The error is talking about the Scheduling Master data.
What was the scheduling type selected during the MRP run
Basci scheduling: make sure the In house production data in material master is maintained.
Lead time scheduling: make sure the Scheduling data in routing is maintained properly.
7)Check the setting of *OPU5 *check the selection ID and also check setting in OPJH. And also check routing selction id COR4 . Also check the status usage and validity date of routings
another thing is , please describe what exact results you are expecting.
Regards
Ritesh -
Planned order number range in apo
Where planned order number range can be maintain in apo.
I am converting agreed plan into planned order but planned order number has generated.
Please somebody tell me.
Regards,
SunillPlanned order number ranges can be maintain in
sproaposupply chain planningppdsglobal settings--maintain number ranges for orders.
and then you assign the number ranges in
sproaposupply chain planningppdsglobal settings--maintain global parameters and defaults (in planning tab ) -
Dear All,
I am trying to create one planned order with planned order profile LA in Trx MD11. But in first screen after entering material number,qty & date. when I press enter planned order profile get changed to KD.
I do not know why it is happening? Please suggest me on this.
In OMDD Trx, is there any dependency between plant and planned order profile??
While creating a new order profile where we define the order type related to this??
Thanks & Regards
Kundan KumarHi
The problem is because of Account assignment category (E) which is getting copied to Planned order in MD11 and resulting to convert the order in to individual customer order (PP-SD-FI integration).Plz chk the Planning stg assigned to the material in MRP-III view
Regards
Brahmaji
Maybe you are looking for
-
How to retrieve data from a table?
I creat a Java application that connect to a database at address 10.4.4.204 and I also creat a table in this database by SQL Navigator. This table contain colums PID, Name, history. How can I retrieve these colums and put results to Microsoft Word. I
-
Request status in Manage data targets
Hi I have an ODS, which loads from a flat file. When I load data, during activation I am getting error on subsequent processing stage with status 5. What is interesting to me is, request is available for reporting icon is turned on, but I am seeing a
-
What's the difference between Transferred Records and Added Records?
When right click an ODS or a cube to select Manage, then under the 3rd tab called Requests, there are two columns called Transferred Records and Added Records, what's the difference between these two? Thanks
-
Swing component fires an event to non-GUI code
Hi all -- this is my first post in forums.sun.com. Question to get me started - I have a Swing component that fires an ActionEvent. I would like that ActionEvent to trigger code that does not run on the AWT Event Queue thread (some code that will tak
-
Setting Org Assignment defaults
Is is possible to change the default setting for Org assignments after the fact? Currently the org assignments are done manually, but due to an uninformed choice made during the initial implementation of the software, all items should be assigned AT