PPDS - Product hurestic giving planned orders six month later

Dear All
I m facing a prooblem while executing the product heurisitc in APO-PPDS. Problem is that planned orders are scheduled six month later even though the requirments are in early period. I hv checked the resource capacity and time profile. In addition I hv also run the report /SAPAPO/CRES_CAPACITY_LENGTHEN. Still the orders are postponed.
Please suggest what can be the possible causes for this error.
Thnx
VS

I faced a similar problem but while creating orders manually in APO. Here is the link to the thread; you may like to refer it if some of the solutions provided would be of help:
Order created with Delay in RRP3 page
In my case the Transportation Lead Time + GR Processing time was making the orders shifted in the future...

Similar Messages

Creation of SNP planned order in Monthly Bucket though CTM plan

Hi,
Can anyone advise how to aggregate the SNP planned order generated after CTM run in Monthly bucket.
Can it be done through customizing?
Regards.
Punit

system switches over to external procurement in place of in house production only when you use optimizer.
Heuristic will do this only if there is a SNP PPM/PDS and the resource calendar prevents timely production.
Regards
Nitin Thatte

Restrict Product Allocation if Planned order is not getting created

Hello All,
We have a scenario that when ever a Sales Order is getting created, Product allocation assignment will be done automatically and planned orders will be created for that requirement in APO.
There are some cases where in because of wrong Variant Configuration, Planned orders wont be created. Our requirement is to delete the Product Allocation automatically or to stop the product allocation assignment if the planned orders are not created.
Do we have any standard setting for doing so or Kindly suggest me some BADI's which can be used for it.
Thanks in advance.
Best Regards,
Srinivas.D

Srinivas,
A rather odd requirement.
Have you tried in SCM APO 'Maintain check instructions' to perform the product check first, then allocation? I would think that if the product check failed, then allocation would not be consulted, and no allocation therefore assigned.
IMG > APO > GATP > General Settings > Maintain check instructions
Best Regards,
DB49

Basic dates and production dates in planned order

Dear all,
I have a planned order (for material A) which has "order finish date" same as "End of production date".
I have another planned order (for material B) where "End of production date" is eariler than "order finish date".
Scheduling margin key is same in both the cases.
Why they are different? Can you please help?
Regds.,
Chaitanya

Dear
Please Check in the MRP 2 And SchedMargin key it defines the floats
SCHEDULING MARGIN KEY
Takes effect only for Lead Time Scheduling
Configure scheduling horizon OPU5
which lead time scheduling and capacity planning should be carried out. scheduling horizon is the period in working days. If a planned order has its basic start date within this period in future, lead time scheduling is carried out using the selected routing.
The production times are calculated from the float times of the scheduling margin key in the material master record and the time from the individual operations.
If the planned order has its basic start date further in the future than this scheduling horizon, the basic dates are calculated from the in-house production times in the material master and are transferred to the production times
with Regards
Pushpalas

Production Center in Planned Order

Hi,
I would like to set the production center 1800 as default in planned order (before converting the planned order to production order).
Does anyone know where I configure it?
Thank you

Hi Caetano,
I made the recommended settings, and the process worked as expected.
Thank you very much for your help.
Thanks also to Kumar.
Willian.

Production version of planned order

When the planned orders are generated in PP/DS, I want to change the production version of certain planned orders. However I cannot find out where I can implement the enhancement. Anyone can help me? Thank you very much.

Hi Rui.
During order creation, you can use either
BAdI /SAPAPO/PWB_SOS, Method PWB_USEX_SOS (internal table CT_SOURCES_EXTEND)
or
BAdI /SAPAPO/RRP_SRC_EXIT, Method RRP_USEX_SOURCE_FILTER (internal table CT_SOURCES)
to sort the available sources of supply or to filter those that are unwanted.
Regards,
Tiago

Six months later: still cannot get Time Capsule to back up my PowerBooks

I have a 500g TC and two Powerbook G4 (Al) computers. I have the same problem with both computers. I reinitialize the TC disk ("Erase" in the Airport Utility) then do an initial backup over hardwired Ethernet. Both PBs have about 60GB of data on them. The initial backups take the expected 12-18 hours. Thereafter, the automatic Time Machine backups work for about 3-5 days, then they stop. Time Machine gets into the "Preparing Backup" state and stays there for hours (I give up after 24 hours).
I tried turning off TM and doing the backups manually (selecting "Backup Now" from the TM menu). That has the same problem, although it takes longer to appear.
I have no reinitialized my TC disk 5 times and had the same problem 5 times.
I have turned off Spotlight indexing of the backup disk and of the PB disk. That has not helped.
Can anyone suggest anything to get this to work?

Rob & tubwreck,
Thanks for the redirect. However, I have already revised that info with new data. See below...
*_Spotlight And Time Machine_*
*Runaway MDS Process*
For Spotlight searching to work, it needs to have metadata. Every time a file is created, modified or deleted, the system notifies Spotlight that it needs to update the meta-data store (mds). First, Spotlight (mdworker) seizes the file, determines its’ type, and then assigns an appropriate importer (mdimport).
While some bits of metadata (modification dates, file type, path name) are easy to gather, most of the interesting data is embedded inside the file. To gather this embedded information Spotlight must use an importer (mdimport), a small plug-in that extracts information from files created by various applications. Each file type has its’ own importer. For instance there are unique Spotlight importers for JPEG, MP3, Word, PDF files and so on.
It’s the importer’s responsibility to read the data file and construct a dictionary that contains the appropriate metadata. When finished, the dictionary is delivered to Spotlight (mdworker), which then updates the meta-data store (mds). The original file is then released to the system to complete the originally intended action.
Ordinarily, this process is virtually instantaneous and invisible to the user. At times, however, it can hang, or loop causing Spotlight (mdworker) and the meta-data store (mds) to monopolize the CPU and interfere with other system events like Time Machine backups. The Console logs may report the following over and over again for perhaps hundreds of times.
+“mds(32): (Error) Import: importer:0x8f8c00 Importer start failed for 503”+
Eventually, the Time Machine backup may fail with the Console logs reporting
+“Indexing a file failed” / “Copy stage failed with error: 11”.+
Or a backup may be completely stalled in midstream, never seaming to end.
Go to Applications --> Utilities folder and launch Activity Monitor.
Clicking the “Process Name” column and scrolling down to the “m”s will reveal that one or all of the Spotlight components (mds, mdworker, mdimport) is maxing out your CPU.
Highlight “mds” and click “Quit Process” in the toolbar.
In the dialoge box that appears click “Quit”.
Enter our Admin password and click “OK”
The stalled backup should now resume and complete. If not, choose “Stop Backing Up” from the Time Machine menu or click the tiny “x” icon in the Time Machine Preferences. When the backup has completely stopped, select “Backup Now” from the Time Machine menu.
*Waiting for index to be ready (909 > 0)*
One of the processes Time Machine relies on for accurate backups is the indexing of the backup disk. With this index, Time Machine can quickly search the backup disk for files the user wishes to restore. When a routine backup begins, often the “Preparing…” stage will include a phase that permits Spotlight to update its’ index of the backup disk. Momentarily the Spotlight icon in the menu bar will pulsate and the Console logs will report “Waiting for index to be ready”. Generally, this phase is so quick that the user is unaware that it occurred.
Unfortunately, this phase can hang thus preventing Time Machine from completing a backup. During this period, the Spotlight icon will continuously pulsate. Clicking on the Spotlight icon will reveal a progress bar with no estimate of the remaining time or it will indicate many hours of indexing still remains. The Console logs will continually report “Waiting for index to be ready”.
Ordinarily, Spotlight indexing is a good thing. And at times, if an index has become corrupt or untrustworthy, Spotlight will require a period of time to rebuild the index. If it has only been a couple of hours then let the process continue. However, if it has been many hours, and the Spotlight menu progress bar still does not indicate an estimated time of completion, then things have hung. You will need to force Spotlight to clear its’ indexes and re-catalogue all volumes. [http://support.apple.com/kb/HT2409]
*Force Spotlight to Rebuild Indexes*
Go to System Preferences --> Time Machine.
Using the slider on the left, turn OFF Time Machine backups for now.
Next, click “Show All” in the toolbar.
Select the Spotlight Preferences.
Click the Privacy Tab.
First, drag your Macs’ internal hard disk from the desktop to the Privacy list.
Wait 10 seconds, then highlight the Macs’ hard disk in the list and click the tiny “-” button at the bottom to remove it from the list.
Spotlight will initiate a reindex of the hard disk. If you click on the Spotlight menu icon you may see the message:
+“Spotlight helps you quickly find things on your computer. Spotlight will be available as soon as the contents of your computer have been indexed.”+
A progress bar will indicate perhaps 10-20 minutes remaining depending upon how much data there is.
Once completed, drag your Time Machine backup disk into the Privacy list of the Spotlight Preferences.
Wait 10 seconds, then highlight the Time Machine backup disk in the list and click the tiny “-” button at the bottom to remove it from the list.
Spotlight will now initiate a reindex of the hard disk.
Once completed, if you have any other hard disk attached to your Mac that are also being backed using Time Machine, then force a reindex as well using the procedure outlined above.
*For Time Capsule / AirDisk Users*
To properly force a reindex of networked disks, you will need to mount the Time Machine disk image so that it appears on the desktop. This will appear as a white drive icon. There is no need to index the green Time Machine drive with the clock icon on it.
Drag the white backup disk image to the Spotlight Privacy list.
Wait 10 seconds, then remove it using the “-” button.
Reindexing disk images can often take much more time, particularly if this is being done wirelessly. Initially it may report upwards of 15-20 hours of indexing remaining. However after a period if time this estimate can begin to drop to just a few hours. Let is proceed without interruption. (Note: This period of reindexing can be reduced by connecting the Time Capsule to your Mac via ethernet cable, and then forcing the reindex to occur.)
Once completed, turn Time Machine Preferences back ON.
Now initiate a backup.
Naturally, the first backup after a Spotlight reindex may be a lengthy one.
*Deleting the .Spotlight-V100 Directory*
At times, simply forcing Spotlight to reindex a volume is not enough to clear corrupt indexes. Additionally, stopping a Spotlight index while in progress can itself introduce further anomalies. In these instances, it may become necessary to delete the .Spotlight-V100 directory on the backup disk entirely. [http://www.thexlab.com/faqs/stopspotlightindex.html] This can be accomplished with the following Terminal command:
+sudo rm -ri /pathtovolume/.Spotlight-V100+
where /pathtovolume is the path of the volume in question.
The volume can then be reindexed by any of the following methods:
Restarting your Mac.
Using Disk Utility to first unmount, then mount the volume.
Issuing the command: +sudo mdutil -E /pathtovolume+
*Redirect the Backup to a Different Hard Disk*
It may be that directing backups to a different hard disk, performing a full backup, then redirecting Time Machine back to the original hard disk clears this issue up.
One contributor reported: “However, I have fixed the problem by accident! Concerned at not having a backup, I did a new backup to an external USB drive which worked fine. I then set my backup device back to the Time Capsule, ran backup and it now works fine. Doing the backup to a different device appears to have cleared the Spotlight problem.” [http://discussions.apple.com/thread.jspa?messageID=8272650#8272650]
Let us know if any of this helps further.
Cheers!

Modeling dummy product and planned orders

Hi SAP Gurus,
I have requirement where i need to model particular business requirements on subcontracting and the same is resulting in need of modeling of dummy product and dummy planned orders. Please share your inputs on what would be impact of dummy product and dummy planned orders in ECC. and also how to make sure that it does cause any issues in costing.
I am modeling subcontracting requirement and i need to create following master data.
All the below products are at plant P.
P has the components as Q_D
Q_D has the components as Q
Q has the components as R
Where Q_D is the dummy product produced at plant P.
P and Q are subcontracted items to the vendor V.
P is the finished good, Q and Q_D are Semi finished goods, R is raw material.
When we plan we are creating Purchase orders for P and Q. And Q_D is made inhouse and we need to create planned order for it. how do we handle the planned orders created for Q_D. we dont want them to convert to production orders. we want a way to clear off these dummy planned orders once we close the POs of P and Q.
Please advise.
Thanks.
Jagadeesh

Hi senthil,
Check if the forecast date is beyond PPDS horizon.
Also in product master on PPDS tab, you should maintain 4 in PP Planning procedure.
Bye.
Nitin

Planned order Vs Actual Production report

Hi Experts
We are running MRP make to stock means we maintain PIR(MD61) in system. On the basis of PIR system create planned order and we declare production against these planned orders. I need a report which show the detail of planned order and actual production declare against that planned order. Please guide.
Regards
Parkash Chand

Dear Parkash,
second possible soluction could be create a custom report using this standard Bapi BAPI_MATERIAL_STOCK_REQ_LIST in order to read MRP element and to summarize the elements desired   (DELKZ field):
MRP Ele Ind   Object
PP     Planned independent requirement
FE     Production order
Pa     Planned order
Third possible soluction setting in customizing the writing of the MRP table MDKP for header data and MDTB for item data and create a Query on these mrp table.
Let me know if i've been useful for you.
Daniele

How to see planned orders for P3 mrp type products in APO?

Dear experts,
I have materials with P3 MRP type (not planned in APO but in R/3 using MRP)
I have active integration models with P3 and X0 mrp type products for planned orders
however I can not see in APO product view the planned orders for P3 materials,
is this normal or should I see those planned orders in APO?
Thanks for your answer,
best regards
Elynn

Hi,
The following prerequisites must be met so that planned orders can be transferred from SAP R/3 to SAP APO
and vice versa:
1.The material masters must be transferred to SAP APO.
2. PPMs must exist for planning in SAP APO.
3. The relevant integration models must be active.
4. An active integration model for planned orders must exist in SAP R/3.
5.An active integration model must also exist for materials, so that the components of the planned order are transferred.
6.The relevant distribution definitions must be maintained in SAP APO, so that planning results can be
transferred from SAP APO to SAP R/3.
Thanks,
nandha

MRP run - misalignment for planned order between Date and Production Date

Hi All,
We've just integrated SAP for a new plant.
The MRP runs based on Routing Lead Time for Make materials instead on Material Master Lead Time, for Capacity Assessment purpose.
When requirements dates lay in the past, MRP performs forward scheduling starting from current date and properly defines Production End Date according to Routing.
By checking MD04, for the proposed Planned Order, the basic date is same as Current Date (= same as Requirement Date) instead of being same as Production Date.
It works as it if checks stil the MAterial MAster LEad time instead of Routing. In fact if I updated the LT of MM the MD04 provides the right Date.
For future requirements, the MRP works properly, by having basic dates (both start and end date) aligned with Production Dates of Planned Order.
How can I do the alignment w/o updating In House Production LT?
Thanks,
D

Hi Caetano,
we have already done this configuration in OPU5 but it doesn't provide any benefit.
Below how we configured it:
Scheduling level: Via detailed scheduling
Adjust dates: adjust basic dates, adjust dep. reqmts to operation date
For capacity scheduling: Always basic dates, dep. reqmts to operation dates
Scheduling type: Backwards.
Regards,
D.

Error trying to convert planned order to production order

Hello Experts,
In MD04, I am trying to convert a Planned order to a production order. The error message is "Planned Order is not to be converted". The details of the message is
"You tried to convert a planned order in which the conversion indicator has not been set. Set the conversion indicator (detail screen, make-to-stock production) in the planned order 100147670."
Is there something in setup I need to do to have this conversion indicator automatically set ?
Also, system is not even allowing me to set the conversion indicator in the Md12 screen.
Please help.
Thanks,
Raman

Brahmaji
How to activate the BOM for release? I am able to create a production order for the material with no problems.
The strategy is set to 10. Also, order type for conversion is set to PP01 in OPPQ. The plant special status for material is A-Active.
Prasobh, what is meant by Planned Order type. How to check it.
The system is not even allowing me to delete the planned order using MD12.
Please help.
Thanks
Raman

SNP Planned order not following resource bucket capacity/factory calendar

Hi gurus,
SCM 5.0
I am running SNP heuristics for a product and expecting planned orders for it. It has corresponding production data structure and multimixed resource. The resource has an assignd factory calendar and SNP bucket capacity. The bucket capactiy availablity dates of the resouce is consistent with the factory calendar workdays/holidays. Using simple lot for lot strategy, I am expecting heuristics to schedule the planned orders on the dates of the demand in compliance with teh SNP bucket capacity availability of the resource. APO does not schedule on holidays consistent with bucket capactiy. This is true until...
We have a public holiday in factory calendar that needs to become a workday. To remedy this, we put a special rule for the factory calendar and explicitly made that holiday into a workday. The changes were synchronized with APO, and this is also reflected in the bucket capacity of the resourc: former holiday now has bucket capacity after the calendar change. However, when running heuristics, it still does not create SNP planned order on that former holiday that has been changed into workday. Even if it is a public holiday, there is already a special rule for the factory calendar and the resource bucket capacity reflects this correctly. But SNP heuristics seems not to follow this change.
Any ideas on this? looks like a bug.

Hi Edgar,
Yes, when your resource reflects the addional capacity of the holiday turned working day, then it is expected to be considered for the SNP planned order.
Instead of SNP heuristics, you may try to check interactively in SNP planning book, if manual order creation in the bucket works out.
Since this is a mutlimix resource , it can also be checked if in PPDS planned order can be created on the day.
The above checking may not solve your problem , but will get to know if at least manully the bucket is being considered or not.
regards
Datta

Production declaration based on order creation date in R/3

Hi,
Can we do the production declaaration in R/3 (mfbf) for PPDS planned orders sent to R/3 from APO based on order creation date?
This is because we need to differentiate between SNP and PPDS planned orders in R/3.
As there is no differentition in SNP and PPDS orders in R/3, while production decalration,
it's not possible that only PPDS orders will get consumed (in mfbf).
SO can we do production declaration based on order creation date instead of order number?
Please share the information.
Thanks,
Vinayak

Hello Santosh
Production versions are selected on the standard system according to the basic finish date, however, you can change the standard system behavior with the implementation of the following note:
351773 - Selection of production versions for planned order
Alternatively, you may use BAdI MD_MODIFY_PRODVERS to create your own logic to select the production versions.
BR
Caetano

Planned Order no. ranges in SAP.

Hi Pp Gurus,
Whenever I access REM planning table and check any Planned order in 'Not yet assign' row it is giving planned order no. generated after MRP run for LA (stock) or KD (individual customer stock) planned order type and whenever I assign any planned order to Production line it gets converted to Order type PE. But when I do backflush using MFBF at the time of Actual Activity posting system is giving some other Order no. Are these all Orders same? Why they are taking different nos.? Where from no. ranges for (planned)
order type can be maintained?
Please reply.
Thanks & Regards,
Abu Arbab

Hi,
I am in ECC 6.03 so i cannot view settings for RSH / RSQ since it is no longer mandatory in SAP.
Please refer th message from SAP below in the entry screen of T code MF 02 - Change run schedule headers.
The creation of run schedule headers is now no longer necessary,
Creating the production versions and the product cost collector
is now sufficient for repetitive manufacturing.
Only the function "Change run schedule headers" is still available so
that you can set the delete indicator for RS headers that are not completed.
Also refer link below :
http://sap.ittoolbox.com/documents/popular-q-and-a/run-schedule-header-4069
But if you are in older versions of SAP, this is where you define the number range for RSH (planned order type PE).
IMG>Production>Repetitive Manufacturing>Cross-Process Settings>Define and Assign Number Ranges...
you can also click on the doc+spec icon to thr left of te execute button of this transaction to confirm this.
And system converts LA/KD order types to PE on assigning to a line because, RSH (previously) was the actionable document for production in REM. Just like planned order is changed to Production order in Discrete system, LA/KD changes to PE in REM system.
Regards,
Ashok

PPDS - Product hurestic giving planned orders six month later

Similar Messages

Maybe you are looking for