Vinoth,
your solution not working,
Arpit,
how you solved this problem?
BR, Dmitry
Vinoth,
your solution not working,
Arpit,
how you solved this problem?
BR, Dmitry
method #3 is worked
You may also try using the report /sapapo/delete_pp_order.
Check in /sapapo/rrp3 transaction whether the planned individual requirements of category got created or not.
just my thoughts
Vinoth
I have FA category of requirements in /sapapo/rrp3, but reports /sapapo/delete_pp_order and /sapapo/rlcdelete can not delete them. He writes that it is not found.
BR, Dmitry
Hi,
The only correct way to delete FA orders is using transaction /sapapo/md74.
RLCDEL only deletes orders with application type 'SNP', FA is not SNP orders.
Best Regards,
Ada
Hi ,
We have a scenario were we have shortage(demands on 06.07.2016) within the planning time fence (5 days) and when we run PP heuristics we can see that the planned orders start within the PTF and are available on 11.07.2016 with PP firmed indicator (creating an overload).
In DS board there is a fixing interval of 2 days (until 08.07.2016) and there are sufficient slots available to schedule the orders after the 8th. Now when we run backward re-scheduling with earliest date in DS strategy the orders are re-scheduled only from 10.06.2016 leaving out the slot between the 8th and 9th empty, if we run the rescheduling with forward and earliest date in DS strategy the orders are scheduled right after 08.07.2016, utilizing all the slots.
We expect that when we run backward scheduling the orders should utilize all the slots after the fixing interval as the demands lie in the past.
Please help understanding the behavior.
Thanks,
Rajan,
I think this is the most proper answer for this issue, from SNP perspective.
Though we have sales orders in system, we can still exclude them from total demand calculation by modifying the macros.
RLCDEL only delete SNP orders, thus has no effect on sales orders. To delete sales orders from APO, please use report /SAPAPO/SDORDER_DEL.
Hello,
The job status is green because the job finished successfully.
You get some red lights in job log, it means the report detected some inconsistency, but this does not mean the job itself failed.
The inconsistency is on storage bucket profile, which is a kind of inconsistency that could not be corrected by this report.
You'll have to:
1) Backup the time series data into infocube for corresponding planning area / planning version
2) De- and re-initialize the planning area / planning version
3) Load the backup data back
Best Regards,
Ada
Hello,
yes, basically you need to check "upplercase/lowercase" first and then input data into the input tables, and make sure the lower/upper case are kept if you reopen the input tables.
also, you do not need to input simsession I suppose, if you have input simversion in gen_params.
I would also suggest you to use SAP standard supported FM BAPI_POSRVAPS_GETLIST3 to achieve similar functionality.
BR,
Ada
The issue with modifying macros is that the sales orders would have consumed the forecast already. So the best way is to use a planning strategy that simply ignores sales orders.
Ken
Are you sure your forecast is of type FA? You confirmed by using gt_io in RRP3?
MD74 is used to "reorganize" forecast that is no longer needed but the forecast consumption remains.
If RLCDELETE and DELETE_PP_ORDER are not deleting it then you have an issue. Do you know how the order was created?
Ken
Hi Raja,
What function/heuristic are you executing? Could you please take a screenshot of the strategy settings?
Regards,
Tiago
Ashu,
It is not clear what are the business requirements that drove you into this predicament, nor why setting the max time is not a valid solution for your situation.
PDS content is typically controlled in standard by settings in ECC. What ECC settings have you tried to prevent BOM explosion?
To me, the easiest standard solution for the business requirement to prevent explosion of these material BOMs would be to remove these materials from the BOMs. Since you do not intend to explode them, there is no reason to have them in the PDS at all.
It is my practice in SCN forums never to recommend enhancements.
Best Regards,
DB49
Hi dongmei,
SNP Production horizon - After planning run (SNP and CTM)planned order generate after this horizon days.
&
Extend Production horizon - Time period, during which Supply Network Planning (SNP) does not plan production; that is, does not create any SNP planned orders. SNP moves production to the first day after this horizon. This horizon is an extension of the SNP production horizon. However, in contrast to the SNP production horizon, the user can manually create SNP planned orders in this extended horizon in interactive Supply Network Planning.
Refer : Difference between SNP horizon, SNP production ... | SCN
Hi Arpit,
Are you sure if you still have orders ? Have you checked it in RRP3, ideally the FA category orders should be deleted using the RLCDELETE. In case you still have the order as suggested by other try using md74 which is re-org. If this doesn't, try and get the GUID number for all these orders which you can by using GT_IO and later you can delete them by using the program /sapapo/om_delete_incon_orders program.
Regards
Sasi
Hi Dinesh,
If you don't want the sales orders to impact production or net requirement calculation or consume forecasts. Please use requirement strategy 10. I suppose that should solve the problem.
Regards
Sasi
Hi DB,
By setting max time, just because of the recursive product it drops the demand for FG which we do not want it to happen. There is a compliance because of which we have to maintain it on the BOM and in practical we use some portion of the output as our input. It way be a weird but we have this process.
We did try in ECC configuring explosion type but it has not CIF to APO. On reading the document for prevent product explosion which is only applicable to CTM we thought to leverage this setting and prevent planning the recursive product. Since this field is non editable we would like to know how to enable for editing.
We also have a process where on the BOM multiple component is maintained. Just before the planning run it will be decided which all of those component will be included on the BOM and the component excluded from BOM.
This is the very reason we want to enable the field "Prevent Product Explosion" on the CTM PDS.
Regards,
Ashu
Ashu,
I don't believe there is any standard program or transaction that will allow editing that field directly.
As you have probably surmised, such editing is achievable through enhancement.
Best Regards & Good Luck,
DB49
sasibhushan
Can you explain why with backward it is scheduled on 10th versus 8th when using forward?
The demand is in the past so the desired date should be today as you can't create orders in the past.
Can I ask a stupid question: What is difference between "Backwards" and "Backwards + Reverse"?
If I select Backwards only , I would think the system would simply "Skip" the demand in the past?