Scheduling in SNP

how is scheduling done for orders in SNP
Thanks

Hi,
The main process in SNP before scheduling is the source determination. The Source of supply for a demand will be determined based on various factors like procurement type, Quota arrangements, priority, procurement costs etc. Then based on the determined SoS, the scheduling will be done as a normal scheduling like ECC MRP (with inhouse production time maintained in PDS or other procurement times).
Please refer the below link for details on Source determination
http://help.sap.com/saphelp_scm70/helpdata/EN/ef/22b1e4947a324285c2d7b24f117a82/frameset.htm
If you want to know anything specific, please revert with your question.
Regards,
Manimaran M.

Similar Messages

Best Practises for doing Master Scheduling using SNP

Hello Gurus ,
Can you please suggest the best practises for doing Master Scheduling using SNP . Which engine to use , what would that mean etc
Regards,
Nick

APC Back-UPS XS 1300. $169.99 at Best Buy.
Our power outages here are usually only a few seconds; this should give my server about 20 or 25 minutes run-time.
I'm setting up the PowerChute software now to shut down the computer when 5 minutes of power is left. The load with the monitor sleeping is 171 watts.
This has surge protection and other nice features as well.
-Noel

Shift scheduling in SNP Run

We are trying to use APO for Shop Floor Planning.
I want to know, can SAP - APO (Optimizer Run) give shiftwise planning instead of day bucket ? i.e. instead of daily requirement, 3 shifts requirement saperately ?
Thanks in advance.
Rajan

Hi Rajan,
SNP is bucketed planning and the most granular bucket is a DAY.
So in SNP you cannot do shiftwise planning. You need to use PPDS for shiftwise planning.
Thanks,
Somnath

Difference between SNP PDS and PPDS PDS

HI Experts.
Can you tell the major differences between SNP PDS and PPDS PDS.
Thanks
Raja kiran R

Hi Raja,
Unlike PPDS planning (time-continuous planning), the least time bucket in SNP planning (bucket oriented planning) is a day, not seconds. Which is why the duration of individual activities in SNP PDS are planned in days only. Scheduling in SNP is based on the fixed duration of an activity and not based on order quantity or capacity load. If a plan contains 3 activities each with fixed duration of 1 day, then the SNP planned order will have duration of 3 days.
On the other hand in PPDS, the duration of an acitivity is calculated based on the resource load that generates the order quanitity, which means larger the qty to be produced, the longer the duration of the activity.
Hope this helps!
Regards,
Umesh

SCM 2007 and SCM 5.0 difference and benefits

Hello,
We are planning to upgrade our APO solution to the next version. I wanted to know if anyone has done any analysis between SCM 5.0 and SCM 2007 which points outs it differences and it's benefits.
Also SCM 2007 being the latest version, is it stable version to upgrade.
Please advise.
Regards,
Sanju

SCM 2007 Vs. SCM 5.1:
Product name is SCM 2007. SCM 5.1 is component under SCM 2007. However it is noted that these names are typically used interactively.
As product is newly introduced...unless you need critical functionality being newly provided, you could wait till initial stabilization happens.
Benefits:
Enterprise Service bundle
DP: Flexible graph generation, usability for context menu, identify/delete obsolete CVCs, enhancements in <<
Graphics, Selection Mgmt
>>
SNP: Profitability driven SCM, Optimization - prioritization, sequence dep. setup costs, quota arrangements , receipt bounds, BADIs for master data edit thru CIF, enhancements in <<
Shelf-life, subcontracting, Prod. Interchangeability, graphics, CTM
>>
PP/DS: User maintained capacity reservations, MRP based detailed scheduling, download SNP blocks, Enterprise Services, enhancements in <<
Campaign Planning, CTP
>>
SCM 7.0: This is still in development by SAP.

Procurement Scheduling Agreements in Heuristic-Based SNP

Hi,
I have a question about Procurement Scheduling Agreements in Heuristic-Based SNP. I was reading through
<a href="http://help.sap.com/saphelp_scm40/helpdata/en/d6/07783b12fc9f20e10000000a11402f/frameset.htm">this topic</a> in help.sap.com
The last paragraph: "If the confirmation quantity is less than ....... as described in step ", says that the first Heuristic run is executed, then plan is sent to supplier and he either changes or confirms the supply qty Then if the qty. from the Heuristics result is more than what he can supply, the Heuristics run is rerun <u>"taking supplier capacity into consideration"</u>.
As far as I understand Heuristics, it is a qty. based rapid cross plat planning that do not take capacities into consideration. But here it's saying that the Heuristics is rerun taking capacities into consideration. That confuses me! Can somebody please explain this to me? What difference in the second run makes the Heuristics take capacity into consideration?
Thank you.

Hi Visu
SNP heuritics based planning involves heuristics(infinite) and heuristic based capacity levelling (with constraints) together.
the first run and second run are run with different settings. the first infinite and the second with the capacty constraint.
in the help page you refer to pl see point 2
also see point 8 on http://help.sap.com/saphelp_scm40/helpdata/en/4a/563a18305211d3b6270000e82de178/content.htm -
you can set up capacity constraints and still run heuristics (the real meaning of heuristics being a set of rules)
the terms being used sure make it confusing

Scheduling Lines from SNP Run

Hi,
R3 by MRP Run system automatically cretes Scheduling Lines (Procurement)
Same thing is possibles in APO also after SNP run?
Sorry, I dont know about APO.
But my client is having APO and R3.
Thanks
Prasad

Dear Prasad
SNP run also generates Schedule lines required the followin is mapped
1. PIR is Ciffed to APO
2. Scheduling Agreement is Ciffed to APO.
IN Case of Sub contracting Schedule lines
1. PIR should carry the production version
2. Sub contracting PPM should be ciffed to APO
3. Scheduling agreement should be ciffed to APO
-Regards
Virender S Thakur

Rolling schedules for steel options between SNP and PPDS

We are trying to set up something within the APO SNP/PPDS tool to
plan rolling schedules for steel.
eg multiple resources, most of which are 100 percent rolling schedules,
with many different "blocks", and common rolls may occur say every 4 weeks, or
every 14 weeks.
And so each roll we need to plan "Quantity required before the next roll" - eg
a 14 week quantity.
We have set up PPDS Blocks using CDP settings with characteristics in our
test system.
Seperate to that we have an SNP model where we plan across multiple plants,
for a 12-24 month period, and we have multiple level BOMS where there may
be 2 semi-finished products between the Finished and Raw material. Eg heat
treated and non-heat treated.
Sometimes one of the interim semi-finished products is the bottleneck, so we
need to use capacity leveling to reduce quantities at all levels of the BOM.
Our main issue is that the SNP quantities that we plan, we are not able to feed into
the PPDS blocks, as SNP does not deal with characteristics.
So in our test, all we can do is use the SNP quantities for higher level plans.
Then delete the SNP orders, and re-run a new PPDS plan to get quantities in our blocks,
but we then have lost all the capacity levelling information from SNP.
Does anyone have any method to deal with this scenario? ie how to model rolling schedules
by utilising the strengths of the SNP mult-plant and capacity leveling data, and then
somehow also taking into account "blocks", or "rolling schedules"?

In our testing. With CDP setting, we create a fcst element with a characteristic on the material. eg RED/BLUE/GREEN, and in PPDS, I can then create a PPDS order with the characterstic linked and visible in the PPDS order, and linked to the BLOCK on the resource (Blocks of RED GREEN for example)
But SNP orders do not work with these characteristics.
This is backed up by various documentation from SAP.
eg
http://help.sap.com/saphelp_scm50/helpdata/en/b0/3c2463c7cbb54bacfb75c789100ad4/content.htm
SNP cannot plan with characteristics. However, the characteristic assignments remain and can be evaluated in PP/DS.
CDP in SNP
CDP cannot be used in SNP as the SNP does __not support__ characteristics.
http://books.google.com.au/books?id=KjvOY_4P8JEC&pg=PA13&lpg=PA13&dq=CDPSNPcharacteristics&source=bl&ots=tG9-FGeIo9&sig=CzW-hktRFP2DrlOaied2QMY7gNE&hl=en#v=onepage&q=CDP%20SNP%20characteristics&f=false
(In this book - a list of which APO areas do and do not work with Characteristics. SNP does not)

SNP PPM schedule duration

Hi dear APO experts,
In SNP PPM, for each activity duration only days allowed. So if there are 2 activities in one PPM and each take 1 day, then SNP planned orders created with such PPM will take 2 days in scheduling. Is it possiblle to set the schedule duration to only 1 day in such case?
Best regards

Hi,
the details of SNP PPM is as below:
For example, the SNP PPM only have one operation and under this operation there are 2 activities -
activity 1 and 2, which are both of type Produce. Each activity will take a fix duration of 1 day. The sequence relationship between these two activities will be activity 2 to follow activity 1.
And dear Digambar Narkhede, could you kindly tell me where in PPM to define the "increment"?

Can we use SNP PDS in Multi level ATP ?

Hi All,
We do CTM planning with existing SNP PDS In APO and now we want to explore to use the Multi level ATP functionality for GATP. I know, MATP can create the ATP trees if the stock is not available and these can be converted into PPDS order.
My question is, can we use SNP PDS for this purpose?
Thanks,
Abhilasha

Hi Abhilasha,
There is no such specific mention anywhere in the literature that you cannot use SNP PDS for MATP. The only downside to using SNP PDS is that SNP PDS are meant for mid to long term planning and the activities/operations in SNP PDS are usually not in detail i.e only important activities or bottle neck components are usually used which will not always facilitate detailed scheduling.
On the other hand MATP creates ATP tree structures by plan exlosion(which can be SNP/PDS) and saves the requirements groups(component requirements of header level) with dates/qts and source of supply. It uses PPDS component to convert these ATP tree structures into PPDS planned orders depending on the conversion horizon/requirements dates. It does that by reading the source of supply, requirements dates and quantities from ATP tree structure and by plan explosion.
When MATP planned orders are created you should no longer plan them with automatic planning run as that will cause re-explosion of the plan and might cause incorrect down stream requirements if you had had substitutions at component leve during MATP check. In planned orders, you have an option of changing the allowed sources of supply (in source of supply section). But for orders created by MATP, you will not be allowed to change the source of supply field from SNP PDS to PPDS PDS in the planned order because it will re-explode the plan. So you can decide for yourself if you can use SNP PDS as source of supply for PPDS planned orders.
Hope that answers your question.
Regards,
Mohan

Master recipes operations not getting transfered in SNP PDS to APO from R3

Hello APO Gurus,
I am trying to transfer SNP PDS for master receipes from R3 to APO.
Issue description::
The operation is not getting transfered correctly , some system default operation "010 generated Operation (from Planned Delive)" is getting generated in APO, also activity and resource capacity is not getting transfered. This situation exist for one plant 1000, for other plant 1100 the SNP PDS created correctly.
i have following points:
1. Is there some customizing setting missing on R3 or APO side for plant 1000 tbefore SNP PDS transfer
2. What need to be checked on master recipes data in R3,
i have checked on below points
1. FG Materials and all the Component Material to be in APO in a Active Integration Model.
2. BOM & Routing and Production Version setup correctly.
3. The Routing Operations have to Relevant to 'SCHEDULING'.
4. Try deleting the existing Integration model for materials & re-create new IM & activate.
Please help me to send SNP PDS correctly to APO to take heuristic run.
Regards
Gajendra
Edited by: Gajendra_APO on Aug 23, 2011 1:14 PM

Hi,
It is good that you have given your already checked points.
Please check the following things also and try to retransfer the PDS.
1. Check your resource in ECC, whether you have maintained the Process formula.
2. Check you have maintained some values in Master Recipe for processing time
3. Check whether the resource has been transferred for your plant 1000 to APO and an active IM exists.
4. Also check the type of the resource transferred to APO. It should be a single-mixed/ multi-mixed or bucket resource.
Hope this will help you to solve the issue.
Regards,
Manimaran M.

Scheduler Agent Installed as Service Encrypted Password Change

All,
We have a Scheduler Agent installed as a service in Windows Server 2003, SP2. We want to change the password of the Master Repository. When I change the ODI_SECU_ENCODED_PASS in the odiparams.bat file it doesn't reflect this change in the service. I tried looking around in the snpsagent.conf wrapper file to see if the password is stored anywhere but dont' see it. I see it references a file called snpparams.bat, unfortunately I cannot find this file on our machine. If anyone knows how to get the new password to take effect without having to drop the agent and recreate it, thus losing all schedules that we've created, I would greatly appreciate the help.
Thanks in Advance,
Josh

Hi Josh,
the snpparamens.bat is exactly the same of odiparameter.bat. It had this name when the software was Sunopsis (SNP). Probably you saw the reference at some old document...
If you drop the service nothing will be loose, just recreate it to get the new parameters. The scheduling list is stored, as everything in the ODI, at the repository, it means that all scheduling orders are at tables. Because of that you need to made a "update scheduler" when create a new scheduling.
If you are still afraid, just create a new agent at another port (as service) and change the logical agent to it. Update the scheduller list an take a look if everthing is OK.
After that you can drop the old service.
Does it make any sense to you?

Unable to convert SNP planned order to PP/DS planned order in RRP3

Hi,
This is an in-house production scenario. SNP planned order are created based on forecast, now i want to convert those SNP planned orders to PP/DS planned orders in product view. While converting i am getting the following error message.
Conversion canceled with error
Message no. /SAPAPO/RRP707
I have checked the SNP, PP/DS PDS, it looks good.
Regards,
LV

Hi Lingaiah,
Conversion SNP -> PP/DS SAP002 is scheduling heuristic
Heuristic for Conversion SNP->PP/DS as SAP_SNP_SNGL used for order conversion.
Regards,
R.Brahmankar

Converting SNP Planned Order /Purch Req to Prod.Order/Purch.Order

Guys
What is the standard process to Convert the SNP Planned Order /Purch Req. into a Prod.Order/Purch.Order ?
Can the conversion indicator be set in APO for SNP Planned Order /Purch Req.and then transferred to R3 as Prod.Order/Purch.Order or can the convesrion of Planned Order /Purch Req to Prod.Order/Purch.Order can be done in R3 itself ?
I am not clear on how exactly this works. Would appreicate if you could provide me with the standard process and any config involved in the same such as Number Ranges and how to set the conversion indicator automatically through SNP planning runs ?
Thanks

When you set this indicator for a planned order or a purchase
requisition, the system automatically converts the order into a
Production order or purchase order after the transfer to the
connected SAP R/3 system.
The converted orders are then retransferred to the SAP APO system with a
different category; a purchase requisition with category BS-ANF becomes
a purchase order delivery schedule line with category BS-EIN.
Please check configuration setting in SPro for transfer setting to R/3.
1. Configure Transfer to OLTP Systems(SNP)
2.Maintain Global Parameters and Defaults(PPDS)
Also on R/3 side you can see it in MD04/MD07 collectively for a product . or individually on
MD13 : planned order
MB51n: PR
Manish

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

Scheduling in SNP

Similar Messages

Maybe you are looking for