Output of SNP
Hi gurus,
recently i faced a question.The output of DP is demand Plan..Then,what is the output of SNP?
Thanks in Advance..
Regards..
Yogi..
Dear Yoganand
SNP is a bucketed ,medium term, cross plant planning process.
As the output of SNP, Planned orders, purchase requistions and stock transport requistions are transferred to OLTP systems so that the medium to long term plans are available.
Hope this clarifies your doubt.
Regards
Nav
Similar Messages
-
Difference between SNP and PPDS.
Hi all,
i want to know the functional diff betwn Snp and PPDS. .
i mean what activities come under Snp, after what activities it is under PPDS. . .
Any info on the same will be highly appreciated.
Regards,
Prasad.Hi Prasad,
SNP basically does rough cut capacity planning on a constrained or unconstraint situation whereas PPDS does time continous finite capacity based on constraint or unconstaint situation.
SNP & PPDS works on horizons. There are scenarios were SNP horizon can overlap with PPDS horizon.
SNP uses SNP PPM as master data whereas PPDS PPM as master data. The output are SNP orders and PPDS orders.
The minimum day for SNP planning is 1 day whereas PPDS can go upto even 1 sec(ie microscopic planning)
Starting from a demand plan, Supply Network Planning determines a permissible short- to medium-term plan for fulfilling the estimated sales volumes. This plan covers both the quantities that must be transported between two locations (for example, distribution center to customer or production plant to distribution center), and the quantities to be produced and procured. When making a recommendation, Supply Network Planning compares all logistical activities to the available capacity
We use the Production Planning and Detailed Scheduling (PP/DS) component
a) To create procurement proposals for in-house production or external procurement to cover product requirements
b) To optimize and plan the resource schedule and the order dates/times in detail
Regards
R. Senthil Mareeswaran. -
Hello Gurus -
I have a few questions in planning version management. Appreciate if you can help me out.
<b>Scenario</b>: I have some planning data in the active version 000 and I have used "/SAPAPO/VERCOP - Copy Planning Version" to create a new version 001. Now I have the same data in both 000 and 001.
Then I went on to change some planning data in 001 to do my what if analysis and I arrived at a final plan which I want to see in 000.
Question: How do I do this? Since we cannot just copy it back to 000. Do we have to replan it in 000? Or do I have to delete the existing 000 and then copy/create 001>000? How is this normally done?
Appreciate your help!
VarunThanks Harish -
I am copying order series data, so I would be using the merge functionality. However the help document says :
<i>SNP orders are not permitted to be published directly into the SAP R/3 system. Communication with the SAP R/3 system is only permitted to take place using the Production Planning and Detailed Scheduling (PP/DS) component. The system performs a technical check of the corresponding Customizing for this.
It is not permitted for any releases to be made into or out of SNP until all the planning versions that came from an active version have been copied back into this active version</i>.
AND when I tried to copy my simulation version results back into the active version, system does not let me do it and gives a message "<b> Function not possible because of transfer to OLTP systems"</b> and says I should try avoiding transfer to OLTP system.
But I do need to transfer the Preqs(both SNP and Deoplyment and POs from TLB) to R/3 and my SPRO settings for " Configure Transfer to OLTP System" is setup in such a way that I transfer all output of SNP/DEP/TLB to R/3.
Any idea what could be done here?
Thanks a lot..
Varun -
To build query related to SNP: Planned Order
Hi,
System: SCM 5.0
Scenario: SO received at plant and planning creates PR against SO at plant and accordingly SNP:Planned Order at Vendor location. If SO is cancelled/deleted (manually), sometime only the PR gets cancelled/deleted (automatically during planning run) but corresponding SNP:Planned Orders still remains at vendor location and so the dependent requirements. PR and Planned Orders are pegged to SO so one-to-one relation is maintained.
I could not find any reason why system is not deleting Planned Order at vendor location despite SO and PR is deleted at plant location. So I am planning to build query where SNP:Planned Orders are not pegged to any PR or SO.
Can anyone help with list of SNP:Planned Order tables so that I can build query around it to identify ghost Planned Orders.
Hope I was clear with my query but let me know if any further information is require.
Thanks and regards,
DevangHI Marius,
Sorry for delay reply.
I was working on on some other more critical issues to business.
Finally we decided to built report to identify obsolete Planned Orders for which PR is not available in ordering plant. I have listed below logic for that report:
Get Location ID from table /SAPAPO/LOC based on Location entered in selection screen
Get PEGIDs from FM /SAPAPO/DM_MATLOC_GET_PEGIDS based on IV_SIMID as 000 and location id from step 1
In FM /SAPAPO/OM_PEG_CAT_GET_ORDERS, use SIMVERSION as 000 and in Import Para IS_GEN_PARAMS insert all PEGIDs from step 2.
From Export Para ET_PEG_INPNODE take From_OrderID and store in internal table.
Execute T.Code /SAPAPO/RRP4 with following selection (Use Selection Variant: OBSOLETE PR and add Location as entered in Selection Screen)
Planning Version: 000
From: Current date – 60 days
To: Current date +180 days
Location: 0000201328
Product: *
Order Type: 1F
6. Compare output of step 4 and step 5 and display result.
From FM /SAPAPO/DM_MATLOC_GET_PEGIDS the output (step 4) will be Order ID (22 characters) while step 5 (T.Code /SAPAPO/RRP4) will give Planned Order number (8 character). I am not sure how to compare Internal Order ID (22 characters) for corresponding Planned Order Nos. (8 characters).
I have not marked your post as correct answer as still need to find answer of above query.
Thank you in advance for your guidance.
Regards,
Devang Shah -
How to use partial number of PPMs to generate SNP planned order
Hi all,
I have a requirement for SNP where I have got X number of identical work centers, on which an SKU can be manufactured. Now there are limitations at the operational level on the labour force or any other constraints, due to which only Y number of work centers can be operational on any day (X>Y). So effectively an SKU can use only Y number of PPMs out of X PPMs in the system on any particular day. X and Y are fixed.
I have tried to map the same by creating a bucket resource with bucket capacity Y and attached to all X PPMs and taken SNP optimizer run. It restricts the output quantity of the planned order by that of the bucket resource defined.
Is there a way to map this requirement, i.e. restricting the number of PPMs which the SKU can use on any day?
regards,
biplabHi,
You can try this by defining the down time for the particular resource in APO under downtime tab page.
Ex for a entire week.
I tried by locking the resource for the entire week and also removed the Maximum delay specified in the product master in our case.
Took the opt run and system is not suggesting the plans.
Or
You can make the PPM inactive before your run.
Request you to test and confirm this
Thanks,
nandha
Edited by: S.Nandakumar on Oct 4, 2010 9:34 AM
Edited by: S.Nandakumar on Oct 4, 2010 9:38 AM -
SNP planned order availability date difference between APO and ECC
Hi,
I have observed that SNP Planned order availability date is not matching between APO and ECC. Details are as follows.
I ran SNP Optimizer with bucket offset of 0.5. After publishing the optimizer created planned orders to ECC, only start date is matching.
Example:
I am using PDS as a source of supply.
Fixed production activity in SNP PDS is 1 day.
GR processing time: 3 day
After running optimizer planned order is created with dates explained below.
Start date/time: 09.05.2011 00:00:00
End date/time: 12.05.2011 23:59:59
Availability date: 16.05.2011 00:00:00
Because of bucket offset defined as 0.5 optimizer planned order availability is start of next monday.
After publishing this planned order to ECC dates on the planned order is as follows.
Start date: 09.05.2011
End date: 09.05.2011
Availability date: 12.05.2011
I have not maintained any scheduling margin key in ECC. Also if I dont define the GR processing time, planned dates between APO and ECC always match. Can anyone explain the impact of GR time on the availability date.
Regards,
VenkatHi Venkadesh,
What's "state stamp"? Do you mean different time zone?
note : 645597 mentioned by Nandha is very helpful:
In standard, CCR will use duedate - "the available date of the output product".
Nandha's words "In SAP APO, if the receipt date of the primary product deviates from the
end date of the last activity of the order, the receipt date
always identifies this as inconsistent. You cannot rectify
inconsistencies of this type by using CCR."
I guess in your PDS or PPM, the output product is not assigned to the End of the last activity. Someone changed it?
Please CIF the PDS or PPM again.
If you really want to apply a note, please use note 815509 as you're using planned order,
and system will use order end date in CCR instead.
GR time is always considered. BR/Tiemin -
Creation of SNP PDS using planned delivery time
Dear Experts,
How do i control creation of PDS because of operaion generated from planned delivery time,although planed delivery ime is zero.
the scenario is as follows:
Material :XXXXX
Planned Delivery time
Procurement Type:E
Plant:XXXX
in transaction /sapapo/curto_simu: there are two PDS displayed with PDS usage as PDS for Supply Network Planning(SNP)
the first one is because of operation generated fromm planned delivery time,output qty is the same a s that maintained as base qty in BOM and mode is blank,activity field is even blank.
the other PDS is created because of the valid production version in R/3.
Thanks in advance
AmrishHi Dutta,
Thanx for a quick revert.
Yes we are using reciepe and we have a valid PDS being generated because of Production Version.
The problem lies with the creation of other PDS from planned delivery time whereinplanned delivery time is zero.I want a resolution so as the system doesnot create thses PDS which are invalid in nature.
These invalid PDS are hamperring result out of SNp optimizer for the reason these are considered in the input log of optimizer.
Regards,
Amrish -
Office 2013 .SNP files can't be opened by Snapshot Viewer
I understand that the option of exporting a report to a Snapshot was removed from Access 2010 onwards. Our users are currently running Office 2013.
Both the "Email" option from the menu and the "EmailReport" function in the macro builder however still offer the Snapshot report format as an available option, although the .snp files created by these processes cannot be opened by the
current version of the Snapshot Viewer client.
Is there a version of the viewer that will open .snp files created by these processes in Office 2013? If not, why is this format still being offered to the users and/or is there a way to remove this option from the selection list?
Many thanks
RickSanne wrote:
Yup, same here, with fully updated 64 bit system with vlc 2.0.4-4.
The png file gets written and is always 2.0 MB in size. Opening it with Gimp gives the error message:
Opening '/home/me/vlcsnap-2012-11-25-13h57m02s145.png' failed: Error while reading '/home/me/vlcsnap-2012-11-25-13h57m02s145.png'. File corrupted?
Using imagemagick's identify to get info about the file results in:
~$ identify vlcsnap-2012-11-25-13h57m02s145.png
identify: improper image header `vlcsnap-2012-11-25-13h57m02s145.png' @ error/png.c/ReadPNGImage/3743.
Setting output to jpg also works for me.
So, it's not just you, seems to be something's broken somewhere. Sorry, can't help more, but at least I can confirm the behaviour.
Thank you,it looks like that we should report it as a bug -
Hi Experts,
I have scenario where bottleneck resources changes with time. Lets say that I have two workcenters WC1 & WC2. Operation 10 will be performed through WC1 and operation 20 will be performed through WC2. SFG1 is input material for operation10 and FG1 is output material through WC2. So SFG1 will be processed through WC1 & WC2 and output material is FG1. Operation 10 & 20 are sequential operations. WC1 & WC2 have the same scheduling time for both the operations 10 & 20
Now, WC1 runs in three shifts in May'10 and WC2 runs 2 shifts in May'10. So WC2 is bottleneck resource in May'10. In June'10 WC1 runs in two shifts and WC2 runs in three shifts so WC1 is the bottleneck resource in June'10. Simply, bottleneck resource can be either WC1 & WC2 depends on time.
So in my routing I have two operations and operation 10 contains WC1 & operation20 have WC2. Further, we created Production Version (PV) and CIFed as PPM. When converting PP/DS PPM to SNP PPM I can chose only one mode so only one work center (resource) in one PPM and another work center in another PPM. We need both workcenters in one SNP PPM.
Could any one guide to meet this scenario.
Thanks,
Naveen
Edited by: Wilian Segatto on May 14, 2010 11:54 AMHi Bandana,
I am trying the same but I am not able to create single Resource,
Would u plz briefly explain me what parameters u are providing,
Thanks,
Radhey -
SNP and DP T.Code and Tables
Hi
Can anyone send me SAP APO (SNP, DP) module transaction code and standard Tables
Thanks & Regards,
RamFollowing are some transactions:
Hope it helps:::::
TCode Text
/INCMD/UI Maintenance of Interchageable groups
/SAPAPO/86000118
/SAPAPO/AC03 Product Availability
/SAPAPO/AC04 ATP Simulation
/SAPAPO/AC05 Time Series
/SAPAPO/AC06 Temporary Quantity Assignments
/SAPAPO/AC07 Exclusive Lock Records
/SAPAPO/AC08 Generate Safety Stock Requirement
/SAPAPO/AC42 Display Product Allocation Situation
/SAPAPO/ADVM Macro Workbench
/SAPAPO/AHTS1 Start-up of Action Handler
/SAPAPO/AMON1 Alert Monitor
/SAPAPO/AMONMSG Settings 'Automatic Sending'
/SAPAPO/AMONMSG_SEND Sending Alerts
/SAPAPO/AMON_REORG Delete Database Alerts
/SAPAPO/AMON_SETTING Alert Monitor Settings
/SAPAPO/ATP2PPDS ATP -> PP/DS Conv. in Background
/SAPAPO/ATPC00 Global Settings
/SAPAPO/ATPC01 ATP Group
/SAPAPO/ATPC02 Business Event
/SAPAPO/ATPC03 Maintain Categories
/SAPAPO/ATPC04_05 Maintain ATP Check Control
/SAPAPO/ATPC06 Maintain Check Mode
/SAPAPO/ATPC07 Maintain Check Mode
/SAPAPO/ATPC08 Maintain Requirements Profile
/SAPAPO/ATPCH01 Maintain ATP Characteristic View
/SAPAPO/ATPCLOG_DEL ATP: Delete C Log Files
/SAPAPO/ATPCQ_AREA Maintain Plng Area Assignments
/SAPAPO/ATPCQ_CHECK Check Prod. Allocations Customizing
/SAPAPO/ATPCQ_CUBE Maintain InfoCube Assignment
/SAPAPO/ATPCQ_GENER Generate Objects
/SAPAPO/ATPCQ_GRP Maintain Product Allocation Group
/SAPAPO/ATPCQ_LST Maintain Seq. of Prod. Alloc.Proced.
/SAPAPO/ATPCQ_OBJ Maintain Product Allocations Object
/SAPAPO/ATPCQ_PRO Maintain Product Alloc. Procedure
/SAPAPO/ATPCQ_RESET Reset Time Stamp
/SAPAPO/ATPCQ_TSTMP APO: Generation Status, Transfer
/SAPAPO/ATPLOG Activate ATP Application Log
/SAPAPO/ATPLOG_DEL ATP: Delete Application Log
/SAPAPO/ATPLOG_DSP ATP: Display Application Log
/SAPAPO/ATPQ_ALERT APO: Product Allocations, Shortage
/SAPAPO/ATPQ_CHKCHAR Check Characteristics Combinations
/SAPAPO/ATPQ_CHKCUST Product Alloc. Assgmt, Sales Order
/SAPAPO/ATPQ_CHKUSG Check Product Allocation Assignment
/SAPAPO/ATPQ_COLLECT Generate Coll. Prod. Alloc. Charact.
/SAPAPO/ATPQ_KCGRP_U Product Allocations: Update Assgmt
/SAPAPO/ATPQ_PAREA_C Copy Characteristics Combinations
/SAPAPO/ATPQ_PAREA_K Copy Characteristics Combination
/SAPAPO/ATPQ_PAREA_R Product Allocations from Plan. Area
/SAPAPO/ATPQ_PAREA_W Product Allocations in Plan. Area
/SAPAPO/ATPTUBE_DISP Display Parameter Buffers
/SAPAPO/ATREE_DSP ATP: Display ATP Tree Structures
/SAPAPO/BLRG01 Generation of Reqmnts from Blocks
/SAPAPO/BOP ATP: Batch Backorder Processing
/SAPAPO/BOPI Backorder Processing (Interactive)
/SAPAPO/BOP_COMPARE Backorder Processing: Comparison
/SAPAPO/BOP_DELETE Delete Backorder Processing
/SAPAPO/BOP_MONITOR Monitor Backorder Processing
/SAPAPO/BOP_RESULT Backorder Processing Results
/SAPAPO/BOP_RUNTIME Backorder Processing: Runtimes
/SAPAPO/BOP_UPDATE Backorder Processing: Update
/SAPAPO/BOP_VS ATP: Backorder Processing for VS
/SAPAPO/BOP_WORKLIST ATP, BOP: Worklist
/SAPAPO/BP1 Send Transaction Data
/SAPAPO/BP2 Delete Transaction Data
/SAPAPO/C3 Display Application Log
/SAPAPO/C4 Maintenance of global parameters
/SAPAPO/C41 Activate/Deactivate Login
/SAPAPO/C5 Send Planning Results to OLTP
/SAPAPO/C6 Delete Application Log
/SAPAPO/C7 Find Entries
/SAPAPO/CALENDAR Calendar
/SAPAPO/CC Core Interface Cockpit
/SAPAPO/CCR CIF_DELTAREPORT3
/SAPAPO/CCRR CIF Compare/Reconcile Reorganization
/SAPAPO/CDPS0 DPS Variable View
/SAPAPO/CDPS1 DPS View 1
/SAPAPO/CDPS2 DPS View 2
/SAPAPO/CDPS3 DPS View 3
/SAPAPO/CDPSB0 Production Planning Run
/SAPAPO/CDPSB1 Prod. Planning Run in the Background
/SAPAPO/CDPSC6 Customizing: Setup Group Maintenance
/SAPAPO/CDPSC7 Maintenance of Setup Matrices
/SAPAPO/CDPSS0 Simulation Version
/SAPAPO/CDPS_REPT Evaluations
/SAPAPO/CDPS_SETUP List Output for Setup Matrix
/SAPAPO/CLPIPCAL Collaborative Promotion Planning
/SAPAPO/CLPISDP Collab. Supply and Demand Planning
/SAPAPO/CLPITPL Collaborative Transport. Planning
/SAPAPO/CLPRPDEL CLP: Delete RFQs
/SAPAPO/CLPRPIN Incoming RFQ Processes
/SAPAPO/CLPRPOUT Outgoing RFQ Processes
/SAPAPO/CLPRPSTART CLP: Publish RFQs
/SAPAPO/CLP_PBPULL Read Time Series
/SAPAPO/CLP_PBPUSH Send Time Series
/SAPAPO/CLP_SETTINGS Collaboration Partners
/SAPAPO/CMDS_DEFCNF Maintain Default Confirm. Profiles
/SAPAPO/CMDS_DEFCNTR Maintain Default Control Profiles
/SAPAPO/CMDS_DEL Delete Releases and Confirmations
/SAPAPO/CMDS_SCO1 Maintain Sales Scheduling Agreements
/SAPAPO/CMDS_SCO2 Delete Sales Scheduling Agreements
/SAPAPO/CMDS_SCO4 Manage Fiscal Year
/SAPAPO/CMDS_STPD Define Sold-To Party Determination
/SAPAPO/CMDS_STPSR Define Inbound Release Processing
/SAPAPO/COMP_VARIANT Comparison of Product Variants
/SAPAPO/CONSCHK Model Consistency Check
/SAPAPO/CONSPRF Model Consistency Check: Profile
/SAPAPO/CONSSHOW Read log from database
/SAPAPO/CPP CIF Postprocessing
/SAPAPO/CPP1 CIF Postprocessing: Multiple Call
/SAPAPO/CPP2 Display CIF Postprocessing Records
/SAPAPO/CPPA CIF Error Handling: Alert
/SAPAPO/CPPR Reorg. CIF Postprocessing Records
/SAPAPO/CQ SCM Queue Manager
/SAPAPO/CQINW qRFC Monitoring for Inbound Queues
/SAPAPO/CSNP Costs Maintenance: SNP
/SAPAPO/CSPRF Maintain TSP Profile
/SAPAPO/CTM Capable-to-Match: Main Screen
/SAPAPO/CTM01 CTM: Consistency Check
/SAPAPO/CTM02 CTM: Stock Limits
/SAPAPO/CTM10 CTM: Distribute Receipt Objects
/SAPAPO/CTMAPLOG CTM Logs
/SAPAPO/CTMB Execute CTM in Background
/SAPAPO/CTMCUST CTM: Global Customizing
/SAPAPO/CTMMSEL Selection of CTM Master Data
/SAPAPO/CTMORDSEL CTM: Maintain Order Selection
/SAPAPO/CTMSCPR Profile Maint. Supply Categorization
/SAPAPO/CTMSSTRAT Define CTM Search Strategy
/SAPAPO/CTMTP Transport CTM Profile
/SAPAPO/CTMTSTR Define CTM Time Stream
/SAPAPO/CTMVIEWER CTM: Call Viewer
/SAPAPO/CTRP Costs Maintenance - Vehicle Sched.
/SAPAPO/CULL_RTO_DEL Delete Production Data Structure
/SAPAPO/CURTO_GEN_DP Generate DP PDS
/SAPAPO/CURTO_SIMU Display Production Data Structures
/SAPAPO/CW qRFC Monitoring
/SAPAPO/DFCT Maintain Distribution Function
/SAPAPO/DISPLAY_CONF Display of DelSched and Confirmation
/SAPAPO/DMP1 Display Consumption Situation
/SAPAPO/DMP2 Generate Planned Independent Reqmts
/SAPAPO/DM_PEGCHECK Consistency Check Pegging Areas
/SAPAPO/DPC3 Change Overview
/SAPAPO/DPLSPLIT Deployment Stk Transfer Prioritizatn
/SAPAPO/GEN_CHK_PDS Generate iPPE Check PDS
/SAPAPO/GEN_PDS Generation of iPPE PDS
/SAPAPO/INCMD_MODEL Model Assignment
/SAPAPO/IPM01 integrated profile management
/SAPAPO/LCOUT Release from SNP -> DP
/SAPAPO/LOC3 Master Data: Locations
/SAPAPO/LOCTZCALC Calculate transport zone coordinates
/SAPAPO/LOC_CD_READ Change Documents for Location
/SAPAPO/LOC_DEL_LOG Location: Delete Application Log
/SAPAPO/LOC_DISP_LOG Location: Display Application Log
/SAPAPO/MASSGEOCODE Location: Mass-Geocoding
/SAPAPO/MAT1 Product
/SAPAPO/MC62 Maintain Characteristic Values
/SAPAPO/MC77 Change Selection
/SAPAPO/MC7A Location Split
/SAPAPO/MC7B Product Split
/SAPAPO/MC8D Mass Processing: Create Planning
/SAPAPO/MC8E Mass Processing: Change Planning
/SAPAPO/MC8F Delete Planning Job
/SAPAPO/MC8G Schedule Mass Processing
/SAPAPO/MC8I Mass Processing: Check Planning
/SAPAPO/MC8J Copy Mass Processing Jobs
/SAPAPO/MC8K Logs
/SAPAPO/MC8S Transfer Profiles
/SAPAPO/MC8T Activity
/SAPAPO/MC8U Transfer Profile
/SAPAPO/MC8V Calculate Proportional Factors
/SAPAPO/MC90 Release to Supply Network Planning
/SAPAPO/MC96B Maintain Forecast Profile
/SAPAPO/MCPSELDEL Delete selections
/SAPAPO/MD74 Reorganization: Adapt Indep.Reqmts
/SAPAPO/MNTPROF01 Maintain Display Profile
/SAPAPO/MP31 Maintain Promotion Attribute Types
/SAPAPO/MP32 Maintain Cannibalization Group
/SAPAPO/MP33 Maintain Promotion Key Figures
/SAPAPO/MP34 Supply & Demand Planner: Init.Screen
/SAPAPO/MP40 Maintain Promotion Bases
/SAPAPO/MP41A Maintain Settings for Report
/SAPAPO/MP41B Promotion Reports
/SAPAPO/MP42 Promotion Management
/SAPAPO/MSDP_ADMIN S&DP Administration
/SAPAPO/MSDP_FCST1 Lifecycle Settings
/SAPAPO/MSDP_FCST2 Assign Forecast Profiles
/SAPAPO/MSDP_SB Safety Stock Calculation
/SAPAPO/MSP01 Maint. and Service Planning Board
/SAPAPO/MSP_CYCMAINT Cycle Maintenance
/SAPAPO/MSP_ESIM MSP Easy Simulation
/SAPAPO/MSP_MOBJ Maintenance of one Maint. Object
/SAPAPO/MSP_PERFPROF Maintenance of Performance Profile
/SAPAPO/MTL01 Maintenance Task List
/SAPAPO/MVM Model/Planning version
/SAPAPO/OM03 Test Program for liveCache and LCA
/SAPAPO/OM04 Display of Current LCA Version
/SAPAPO/OM11 Log
/SAPAPO/OM12 Delete Log
/SAPAPO/OM13 Analyze liveCache and LCA Objects
/SAPAPO/OM16 Data Viewer
/SAPAPO/OM17 Data Reconciliation
/SAPAPO/OM25 Daily Reorganization of APO
/SAPAPO/OO_PPM_CONV Maint. Mode Comb. for PPM Conversion
/SAPAPO/OPT03 Optimizer User Display
/SAPAPO/OPT09 Optimization Version Display
/SAPAPO/OPT11 Log display
/SAPAPO/OPT12 Opt. server process overview
/SAPAPO/OPT_PRIOPROF SNP Opt.: Priority Profile
/SAPAPO/OPT_STOP Terminate Optimization Runs
/SAPAPO/PCMT Production Campaign
/SAPAPO/PDSLOG Log of PDS Generation
/SAPAPO/PEG1 Pegging Overview
/SAPAPO/PMON Plan Monitor
/SAPAPO/PMONDEF Definition: Key figure schema
/SAPAPO/POM1 Planned Order Management
/SAPAPO/POV1 Product Overview Transaction
/SAPAPO/PPC1 Backflush Entry
/SAPAPO/PPC2 Display Backflush
/SAPAPO/PPE iPPE Workbench Professional
/SAPAPO/PPELUI iPPE Workbench Express
/SAPAPO/PPFSCO Output of Confirmations
/SAPAPO/PPL1 Production List
/SAPAPO/PPM_CONV Conversion of PP/DS PPMs to SNP PPMs
/SAPAPO/PPM_CONV_310 Report for Generating SNP PPMs
/SAPAPO/PPM_CONV_LOG Log of SNP-PPM generation
/SAPAPO/PPM_DEL Mass Deletion of Plans and PPMs
/SAPAPO/PPT1 Product Planning Table
/SAPAPO/PROD_CD_READ Change Documents for Produkt
/SAPAPO/PSTRUCONS Plng Obj. Struct. Consistency Check
/SAPAPO/PWBSCH1 Create SA Release(s)
/SAPAPO/PWBSCH2 Release Output
/SAPAPO/PWBSCH3 Process Sched. Agreement Releases
/SAPAPO/PWBSCH4 Enter Confirmation
/SAPAPO/PWBSRC1 Ext. Procure. Rltnshps Maintenance
/SAPAPO/PWBSRC2 Delete External Proc. Relationships
/SAPAPO/RBA04 Integrated Rule Maintenance
/SAPAPO/RBAC01 Maintain Rule Strategy Determination
/SAPAPO/RELHSHOW Hierarchy Maintenance
/SAPAPO/REL_TO_OLTP Direct Release InfoProvider to R/3
/SAPAPO/REL_TO_SNP Direct Release InfoProvider to SNP
/SAPAPO/REORG_WUL Reorg. of Where-Used-Lists in LC
/SAPAPO/RES01 Change Resources
/SAPAPO/RET2 Restrictions Maint.- Create & Change
/SAPAPO/RET_EVAL Restriction Evaluation
/SAPAPO/RET_RP Restrictions & Reservation Planning
/SAPAPO/RLCDEL Delete Orders from Livecache
/SAPAPO/RLGCOPY Realignment
/SAPAPO/RRP1 Requirements View
/SAPAPO/RRP2 Process Order
/SAPAPO/RRP3 Product View
/SAPAPO/RRP4 Receipts view
/SAPAPO/RRP7 Mass Conversion of Orders
/SAPAPO/RRP8 ATP Check for REM Planned Orders
/SAPAPO/RRPEVAL Log for Last Planning Run
/SAPAPO/RRPLOG1 Display Logs
/SAPAPO/RRPLOG2 Delete Logs
/SAPAPO/RRP_ATP2PPDS ATP Tree Structure Conversion
/SAPAPO/RRP_NETCH Planning File Entries
/SAPAPO/RRP_SNP2PPDS Conversion SNP -> PP/DS
/SAPAPO/RSP_CONSIS Cons. Check RSC + Per.-Slot Creation
/SAPAPO/RSP_DBORSHOW Display Configuration for Orders
/SAPAPO/RSP_DCR Releasing Daily Packages
/SAPAPO/RSP_DICP Daily Package Creation
/SAPAPO/RSP_D_DEL Delete Delta Records
/SAPAPO/RSP_EXPLAIN Explanation Facility
/SAPAPO/RSP_G1 Planning Table
/SAPAPO/RSP_INFO Information Center RP
/SAPAPO/RSP_LC01 Initialize Time Series
/SAPAPO/RSP_LC03 Update Time Series
/SAPAPO/RSP_LC04 Restore Time Series
/SAPAPO/RSP_MCSC Manuf.Compl. Proposed Orders f.Stock
/SAPAPO/RSP_P1 Copy Orders
/SAPAPO/RSP_P2 Start Medium-Term Planning
/SAPAPO/RSP_P3 Reset Result of Medium-term Planning
/SAPAPO/RSP_RD_SIMU Simulation of Restriction Explosion
/SAPAPO/RSP_RSC Rescheduling
/SAPAPO/RTO_ORD_COMP Compare PP/DS PDS (R/3)
/SAPAPO/SCC02 Supply Chain Cockpit
/SAPAPO/SCC03 PPM Maintenance
/SAPAPO/SCC07 Supply Chain Engineer
/SAPAPO/SCC_TL1 Transportation Lanes
/SAPAPO/SCC_TL2 Mass Creation of Transport Rltnships
/SAPAPO/SCC_TQ1 Quota Arrangements
/SAPAPO/SCC_USR_PROF SCC Cockpit User Settings
/SAPAPO/SCE_USR_PROF SCC Engineer User Settings
/SAPAPO/SCHED_TEST Simul. Transp. & Shipment Scheduling
/SAPAPO/SDP8B Define Planning Book
/SAPAPO/SDP94 Supply & Demand Planner: Init.Screen
/SAPAPO/SDPALPR Assign Planners to Alert Profiles
/SAPAPO/SDPPLBK Assign User to Planning Book
/SAPAPO/SDPT SD Sched. Agrmt. Prod.Planning Table
/SAPAPO/SDPUSET SDP User Settings
/SAPAPO/SDRQCR21 Correction Report /sapapo/sdrqcr21
/SAPAPO/SEQ1 Interactive Sequencing
/SAPAPO/SEQ2 Model Mix Planning Run
/SAPAPO/SNP01 SNP Run
/SAPAPO/SNP02 Deployment
/SAPAPO/SNP03 Call Deployment Optimizer
/SAPAPO/SNP04 Transport Load Builder
/SAPAPO/SNP05 Capacity leveling
/SAPAPO/SNP06 Hierarchical Planning Disaggregation
/SAPAPO/SNP103 Maintain TLB Profile
/SAPAPO/SNP113 SNP: Maintain Costs
/SAPAPO/SNP2PPDS SNP -> PP/DS Conv. in Background/SAPAPO/SNP94 SNP: Interactive Planning
/SAPAPO/SNPAPLOG Application Logs
/SAPAPO/SNPDRP DRP: Interactive Planning
/SAPAPO/SNPFCST Release SNP Forecast
/SAPAPO/SNPLLC Low-Level Code Determination
/SAPAPO/SNPOP Call Up SNP Optimizer
/SAPAPO/SNPOPLOG SNP Optimizer Log Data
/SAPAPO/SNPSA Sched. Agreemt: Interactive Planning
/SAPAPO/SNPSOP SOP: Interactive Planning
/SAPAPO/SNPSRC Call: Sourcing of Forecast in SNP
/SAPAPO/SNPTLB TLB: Interactive Planning
/SAPAPO/SNPVMI SNP: Interactive Planning with VMI
/SAPAPO/SUPCAT CTM Supply Category Maintenance
/SAPAPO/TI01 Evaluation of Production Tracking
/SAPAPO/TLBPRF TLB Profile Maintenance
/SAPAPO/TR30 Maintain DP/SNP Time Buckets Profile
/SAPAPO/TR32 Periodicities for Planning Area
/SAPAPO/TR_CD_QUOTA Change Docs for Quota Arrangements
/SAPAPO/TR_CD_TLANE Change Docs for Transportation Lanes
/SAPAPO/TR_DELTRPR Deletion of Prod.-Spec. Trnsp. Lane
/SAPAPO/TR_IGS_BPSEL Scheduling of GIS Preselection
/SAPAPO/TR_IGS_BUTRM Update of GIS Data
/SAPAPO/TR_IGS_RPSEL Reorganization of GIS Preselection
/SAPAPO/TSCONS Time Ser. Network Consistency Check
/SAPAPO/TSCOPY Copy/Version Management
/SAPAPO/TSCUBE Load Planning Area Version
/SAPAPO/TSKEYFMAIN Mass Maint. for Time Series Key Fig.
/SAPAPO/TSLCREORG Check LC Time Series Master Data
/SAPAPO/TSPSTRU Toolbox for Planning Object Struct.
/SAPAPO/TTC1 Schedule Maintenance
/SAPAPO/TTV1 Maintain Validity Area
/SAPAPO/TTW1 Itinerary Maintenance
/SAPAPO/VERCOP Copy Version
/SAPAPO/VERDELLD Delete a planning version
/SAPAPO/VERMER Merge Planning Versions (SNP)
/SAPAPO/VERMRM Merge Versions: Messages
/SAPAPO/VS01 VS Interactive Planning
/SAPAPO/VS05 Schedule optimization run
/SAPAPO/VS10 Transportation Service Provider Sel.
/SAPAPO/VS11 TPVS: Define Delivery/Pickup Windows
/SAPAPO/VS12 TP/VS: Define Compatibilities
/SAPAPO/VS50 Orders for Delivery Generation
/SAPAPO/VS501 Schedule Delivery Generation
/SAPAPO/VS51 Change Plan. Shipments to Shipments
/SAPAPO/VS511 Transfer Planned Shipments to OLTP
/SAPAPO/VS52 Check Release of Planned Shipments
/SAPAPO/VS521 Check Release of Planned Shipments
/SAPAPO/VS53 Deleting deliveries
/SAPAPO/VS531 Delete Deliveries
/SAPAPO/VS54 Deleting Shipments
/SAPAPO/VS541 Delete Shipments
/SAPAPO/VS551 Release Shipments in the Background
/SAPAPO/VS60 Monitor for OLTP Publication
/SAPAPO/VS70 Apply Split Rules
/SAPAPO/VS71 Determine Split Rules
/SAPAPO/VS72 Maintain Access Sequence for Splits
/SAPAPO/VS73 Maintain Split Rules
/SAPAPO/VSHIST Display the Change History
/SAPCND/AO01 Conditions: V_T681F for O RB
/SAPCND/AO03 Create condition table
/SAPCND/AO04 Change condition table
/SAPCND/AO05 Display condition table
/SAPCND/AO06 Condition Type: Rules-Based ATP
/SAPCND/AO07 Access: Maintain (Rules-Based ATP)
/SAPCND/AO08 Conditions: Procedure for O RB
/SAPCND/AO11 Create Rule Determination
/SAPCND/AO12 Change Rule Determination
/SAPCND/AO13 Display Rule Determination
/SAPCND/AO14 Copy Rule Determination
/SAPCND/AU11 Create Scheduling Step
/SAPCND/AU12 Change Scheduling Step
/SAPCND/AU13 Display Scheduling Step
/SAPCND/AU14 Copy Scheduling Step
/SCMB/ODM_CHECK ODM: Check Customizing
/SCMB/ODM_DATA_CHECK ODM: Check Data Consistency
AHTGL01 Action and Parameter Maintenance
AHTGL02 Definition of Action Points
BAPI BAPI Explorer
CL02 Classes
CL20N Object Assignments
CL22N Assign Class to Superior Classes
CL24N Class Assignments
CT04 Characteristics
LC10 liveCache Assistant
LSMW Legacy System Migration Workbench
MASSD Mass Maintenance
MDEM Orders with Explosion Errors
MDMD Matrix for Product/Location
MDRPM Control Data for RPM Products
OPPE13 User Assgmt: iPPE WB Professional
OPPELUI02 User Assignment: iPPE WB Express
PPECHK iPPE Consistency Check (Prod. Vers.)
PPEHDR01 Create a Production Version
PPEHDR02 Change a Production Version
PPEHDR03 Display a Production Version
RPMBAL Line Balancing for Demand Program
RPMCALL Explosion for RPM
RPMEVAL Evaluations
RPMLOG RPM Log
RPMPERF Display Performance Data
RPMPLF Planning Flags for Planning Matrices
RPM_DATEVECTORS_REOR Reorganize Table of Periods in LC
RPM_DATEVECTOR_COMPU Calculate Table of Periods f. Res.
RPM_OM_DATEVECTOR_SH Display Table of Periods from LC
RPM_RESOURCE_TSTREAM Display Resource Time Stream
RSKC Maintaining the Permittd Extra Chars
RSPC Process Chain Maintenance
RSSM Authorizations for Reporting
RZ20 CCMS Monitoring
SLG2 Application Log: Delete logs
SM37 Overview of job selection
SMQ1 qRFC Monitor (Outbound Queue)
SMQ2 qRFC Monitor (Inbound Queue)
S_AP5_28000002
S_AP8_94000074
S_AP8_94000284
S_AP9_75000079 IMG Activity: APO_PPS_CDPSC0
S_AP9_75000085 IMG Activity: APO_PPS_CDPSC8
S_AP9_75000086 IMG Activity: APO_PPS_CDPSC5
S_AP9_75000087 IMG Activity: APO_PPS_CDPSC4
S_AP9_75000088 IMG Activity: APO_PPS_CDPSC3
S_AP9_75000089 IMG Activity: APO_PPS_CDPSC2
S_AP9_75000090 IMG Activity: APO_PPS_CDPSC1
S_AP9_75000095 IMG Activity: APO_SNP_SNP112
S_AP9_75000101 IMG Activity: APO_SNP_SNP107
S_AP9_75000102 IMG Activity: APO_SNP_SNP105
S_AP9_75000130 IMG Activity: APO_ALLG_TRANS
S_AP9_75000138 IMG Activity: APO_ALLG_CAL
S_AP9_75000141 IMG Activity: APO_PPS_ROUNDPRF
S_AP9_75000142 IMG Activity: APO_DEMPL_BEDARF
S_AP9_75000146 IMG Activity: APO_DEMPL_WORK
S_AP9_75000169 Call the IMG Activity
S_AP9_75000183
S_AP9_75000184
S_AP9_75000202
S_AP9_75000203
S_AP9_75000206
S_AP9_75000212
S_AP9_75000249
S_AP9_86000053
S_AP9_86000062 IMG Activity: APO_SNP_SNP120
S_AP9_86000161
S_APO_12000024
S_APO_12000025
S_APO_12000026
S_APO_12000035
WUF Where-Used List
Tables:
Tables where SALES ORDER Data is stored in APO
In addition to the requirements in SAP liveCache, the SD order tables are also included in the comparison with SAP R/3. Data is stored in these tables that is required for SAP APO functions from the area of Global ATP, such as the check against product allocations and backorder processing.
Both the existence and the consistency of the stored data is checked, based on the most important fields, as well as on the connection between main item(s) and subitem(s) in the following tables:
· /sapapo/posmapn (mapping the item)
· /sapapo/ordadm_h (order header)
· /sapapo/ordadm_i (order item)
· /sapapo/schedlin (order schedule line)
· /sapapo/obref (object reference)
· /sapapo/sdfield (SD order/delivery: Item additional data, also called 'field catalog')
· /sapapo/ciflooku (CIF lookup table)
The following inconsistencies can arise:
· r3obj : R/3 object of item in table /sapapo/posmapn
· atpcat: ATP category of item in table /sapapo/ordadm_i
· chmod: Check mode of item in table /sapapo/ordadm_i
· pstyv: Item category of item in table /sapapo/ordadm_i
· from_time: Schedule line date in table /sapapo/schedlin
· to_time: Schedule line date in table /sapapo/schedlin
· uepos: Assignment of higher-level (main) item
(Mapping in table /sapapo/posmapn and entry table in /sapapo/sdfield)
· wmeng: Requested quantity in table /sapapo/schedlin
· edatu: Requested delivery date in table /sapapo/schedlin
· obref: Object reference between order and delivery item in table /sapapo/obref
· matnr (MainItem)/matnrMItem: Product of main item in table /sapapo/ordadm_i
· werks (MainItem)/werksMItem: Plant of main item in table /sapapo/ordadm_i
· lgort (MainItem)/lgortMItem: Storage location of main item in table /sapapo/ordadm_i
· Account assignment (MainItem)/accMItem: The account assignment of the main item, that is, the pegging area from table /sapapo/ordadm_i does not correspond to the account assignment in SAP R/3 (vbap-sobkz, vbap-vbeln and vbap-posnr)
Important Tables in R/3
Table Remarks
QTVB Product Allocation: Allocation used by Customer Order* Use this table to find allocation assignment by Sales Order
Important Tables in APO
Table Remarks
/SAPAPO/TBQTVB ATP: Parameter Buffer, Product Allocation Assignment
/SAPAPO/PAGZE001 PAG-Z001 Product Allocations: Characteristic Value* This table is generated when a Product Allocation Group is defined. Use it to convert the GUID into a CVC.
/SAPAPO/MATKEY Product Master* Use it to convert Material GUID into a material number.
/SAPAPO/MATLOC Location product Master* Use it to see valid material plant combinations (GUIDs) in APO.
/SAPAPO/MATMAP Mapping Table for Products* Use it to see mapping of material numbers in R/3, APO and GUID
/SAPAPO/LOC Locations* Use it to convert Location GUID into a Location number.
/SAPAPO/QTTAB Product Allocations: Schedule Line
/SAPAPO/SDQTVB SD Order: Product Allocation Assignment* Use it to see detailed allocation assignment by Sales Order
/SAPAPO/POSMAPN Order Items Mapping Table*Use to get GUID for Sales Orders
/sapapo/treqires- All the confirmed qty and confirmed timestamp for order transaction GUID
CDHDR, CDPOS- Broader- All changes
/sapapo/DMCP
R-Delete
N-Create
C-Change -
Hello,
I need to add a new key figure in SNP PB to input values manually.
I was trying to use a standard KF that is already in PA and that we are not using but when I try to change this KF in tcode /SAPAPO/SDP8B to set an input/output row, system gives me this message when saving:
"Key figure <Aggregated distribution receipt (plnd)> must not be set to ready for input".
I only have a few KF left to use and all gives me this error except 9AAFCST, but this one does not allow negative values (system set to 0) and the row I need is to input values than with a macro should change the Total Demand (to add or diminute).
Anyone knows how can I do this?
Thanks,
TeresaHi,
what do you mean by a Z Time-series keyfigure, how can I do that?
We can create a new keyfigure Z and add it to PA and PB? I just want a simple input keyfigure to use in a macro to sum to the real standard forecast that comes frm DP.
Regards,
Teresa -
WORK FLOW & PROCEDURE FOR FOR SNP CAPACITY LEVELLING HEURISTICS RUN
Dear Sir / Madam,
Currently, we are taking only SNP Heuristics Run and the output viz. planned stock transfer requisitions are being passed to PPDS as such. But now we feel, SNP capacity leveling can play a vital role in getting more fine tuned results from PPDS. So, We wants to start using the SNP Capacity leveling run. We shall like to know the work flow / procedure for taking the SNP capacity level run i.e. what inputs should be properly reviewed before taking the SNP capacity level run and what shall be its output..? Kindly let us know the procedure / work flow for taking the SNP Capacity Levelling Run.
Your early reply in this regard shall be really appreciable.
Thanks & Best Regards,
Sanjeev Chugh
25-Mar-10Hi Sanjeev,
as in any other module, correct master will play a key role in getting effective results in capacity levelling. you will need to check the following master data while setting the system for capacity levelling :
Consistency in BOM in R/3 and PPM/PDS
Consistency in Routing in R/3 and PPM/PDS - the actual through put on the shop floor should be the same as that in the routing and in the PPM/PDS. unless this is in sync, no amount of levelling can return good results.
Maintenance of shift - again as present in the shop floor.
you can provide the dump of the above master data and ask the shop floor engineers to validate the data as it exists in the ssytem. you can do the consistency check between R/3 and APO yourself using queries. Once they have validated this master data and the the actual master data reflects in your system, i think, the job is more than 50 % complete.
also you need to check the lot sizes, rounding profiles, and period factor, becasue all three combined play a major role in giving good or better results after levelling.
you may also check at what level you want to run the levelling. whther the bottleneck is at the finished component level, or 2nd level, etc. you may check whther you have discrete manufacuring or REM and if you really want to levelling on REM order.
then you need to analyse, what is the lengh of horizon you want to run the capacity leveling on. sometimes it makes no sense to run on the entire horizon because if capcities are already overlaoded, you will not achieve the desired results.
hence depending upon the level of your understanding and comfort of the planner (who will be using this result), the horizon can be increased grdually.
if you are starting to implemement capcity levelling, you can sumulate runs and show the results to the planner and check if the standard capacity heursitics satisfies their requirement. else you can go for custom requirement.
you will also have to decide on the stratagies, priorities,etc based on the business requirement.
i think the above should give some starting direction to implement capcaity levelling in your system.
award points if you find this useful.
Rgds, Sandeep
Edited by: Sandeep Budhiraja on Mar 25, 2010 11:49 AM -
Distribution Receipt Confirmed Keyfigure - Input/Output
Hi Experts,
In SNP planning book, we would want key figure "Distribution Receipt Confirmed" to be editable.
When I tried to make this key figure Input/Output, I got a message "Key figure Distributionreceipt confirmedmust not be set to ready for input".
Can you tell me how can I make this key figure Editable in Planning book-data view.
Thanks,
VipulThanks Somnath,
Our client would like to change distribution receipt confirmed for shipping directly from plant to DC if ther is a full truckload but system may suggest shipment via Warehouse as it was defined as a least cost route. In our case, 70% shipment will happen via warehouse rest directly from plant to DC.
As APO can't suggest the route based on truckload building, we were thinking about this approach.
Let me know if you know any alternative as we are not using SAP TM.
Vipul -
Wtz d role of SNP Consultant in supptng Projct
HI 2 All SAP PPL
Whats the role of SNP Consultant in Supportng project i mean what exactly he have to do(JOB PROFILE).
Ur help l be grtful
Regards
RonaldHi Ronald,
Typical roles are
1) Monitoring background jobs
2) Check application logs
3) Check optimisation logs
4) Check Dep/TLB outputs
5) Check CTM runs, logs
6) Corrective action for failures
7) Interactive planning
8) Capacity levelling
9) Conversion of SNP to PPDS orders
10) Master data maintenance
11) Profile maintenance
12) Safety stock planning
Regards
R. Senthil Mareeswaran. -
Hi, all guru
I'm new to SNP, would like to clarify the process flow .
What is the output of each SNP process after release the forecast from DP to SNP
1. is the first process is DRP ? when we run optimizer, what is the output , any order send to R3
2. how about Deployment and TLB run , any output , any order type created ? any data sent to R3
3. when R/3 received those data , what R/3 do with it .
4 what is the flow between SNP and MM/PP at R3
5. what is Rough cut capacity planning , it is seperate data being load to SNP, how to relate to SNP process
it will be very helpful if we can have a scenario base of example
many thanksHi :
following are the steps :
Once the demand plan is released form DP to SNP , Planned Independent Requirements are created for SNP / PPDS.
Now performing SNP Runs through Heuristics , CTM or Optimizer Results in Distribution & Production Plan for
Medium to long term horizon . After SNP run you can generate alerts for any exception and resolve them .
SNP plan now consist of Transaction data (Purchase requisition , SNP Stock transfer order or SNP Planned order) . If you are using PPDS , SNP orders can be converted to PPDS orders which are more detailed .
After production planning is complete , Deployment confirms stock transfer order based on current receipts and demand .
TLB runs groups together stock transfer orders into shipments .
All these transaction data is passed to R/3 through CIF .
SNP planning is rough cut only if you are utilizing SNP PPM which only contains critical resources and material .
Maybe you are looking for
-
Trying to get downloads to go into iTunes automatically
hey all - I want my downloads from ares to go into my iTunes without adding them file by file... my friend has his go in no problem - he'll download a song, click on iTunes, and it'll already be there. i've gone into prefences and tried to do this wi
-
Pop up warning message while creating PO
Hi, How to give a Genral or a POP up Warning Message while creating and checking a PO in ME21n and ME22n. Even i tried in changing the local setting in the menu bar, but it doesnt work. Help and suggestions will be much appreciated. Thanks & Regards.
-
iTunes Match keeps "gathering information" on my library, in a loop, without ever making to step 2. I know others have experienced the same issue, but the only advice given was for PC users. Am on Mac. Admittedly, my library is huge (over 10,000 song
-
Xperia Z1 Android 4.3 14.2.A.0.290 firmware ROLLING NOW
Xperia Z1 Android 4.3 14.2.A.0.290 firmware Update Rolling Officially. Update available and confirmed in India, UK, Sweden, Finland, Singpore. Confirmed on Both C6902 and C6903 Source - http://www.xperiaguide.com/2013/12/16/xperia-z1-z-ultra-android
-
Computer randomly crashing and restarting.
I recently upgraded my 2010 Macbook Pro to Mountain Lion OSX. Ever since I upgraded my computer has been randomly crashing and restarting itself. I have looked online for many solutions. I have tried editing settings in system prefereneces, a hard dr