Release results to snp or r/3
helo sir
good morning
how r u??
could u plz tell in which format the planning we release to SNP OR R/3???
where the unconstrained demand pland stores in SNP, in which key figure stores the demand plan in snp???
help me out sir....
thanx a lot...waiting for u r response.
Hi Dallyanusha,
Like profile is the profile containing similar set of CVC's that
will be used up by system during forecast planning.
ie If you are having characteristic combinations that are
very much similar in properties and usage, then you can
define like profile with those CVC's.
Like Modelling is the approach or process that replaces
one set of CVC with another similar set of CVC's that are
defined in like profile during forecast planning.
Hope it is clear now
Regards
R. Senthil Mareeswaran.
Similar Messages
-
Difference in the Demand and the Released Demand to SNP for the month M0
Hi evryone,
I have released the demand from DP to SNP of a market on 03.02.2010 .
Demand of M0 there is difference between the Forecast of the user and the demand released to the SNP.
For rest of the months the demand Forecasted by the user and the demand released to the SNP is matching.
I hope this difference is because I had released the demand on 03.02.2010, so the demand of the 01.02.2010 & 02.02.2010
was not released to SNP. This is my guess only.
Please tell me whether I am correct or not ?
If I am wrong, please tell me the reasons for the difference in the month M0.
with regards,
baluHi Balu ,
If your forecast is released on 03022010 and you have a setting for period split as 2, then your understanding is correct .
The M0 demand /forecast volume will be reduced by the qty of deliveries you made on 01 & 02022010 due to the requirement stateliest and forecast consumption process which is a std functionality.
So please check if diff in original demand and released demand is same as of invoiced qty .. this will ensure your understanding.
Also other factor that could affect the SNP released demand qty is 'Backward/Forward consumption period' in material master/product master.This is the period for forecast consumption and the direction depends on the defined consumption mode-
so in future you could have a scenario that you have maintained forward consumption as ex. 60 days and there is no forecast in M0 but have some excess deliveries on 01M02010 and then the next months forecast will be consumed by that excess qty of delivery in M0 2010 and you would get diff volume in M12010 month.
Hope this clears the doubt...
Regards,
Digambar -
Difference between Release DP to SNP and Release profile
Hi Experts,
What is the difference between Release DP to SNP
And maintain Release profile. Can u suggest am lot of confusion about these?
Explain in brief.
prasadHi Prasad,
Aparna point is absolutely correct. From usage point of view, date is the only difference.
There are 2 options to release forecast from DP to SNP.
1. Demand Planning -> Planning -> Release -> Release to Supply Network Planning.
2. By creating Rlease profile, activity , planning job, etc
1 is used for online purpose & for few product/location combinations. However 2 is used for the mass processing.
Use 1 to release a limited amount of data (a few product / location combinations only) from Demand Planning to Supply Network Planning. Do not use it for mass releases, for example large planning books.
If you try to release too much data with this transaction, memory problems are likely, since the system tries to read all the data
simultaneously. For mass processing, use 2 - Releasing the Demand Plan with Mass Processing.
Decision is based on data volume & performance.
Hope this helps.
Regards,
Nawanit -
Release demand to SNP - Strange requirement
Hi,
We have some strange requirement during release demand from DP to SNP.
We use demand planning system to plan future demands and release to SNP for supply planning. And we use TDP ( 10 days, a posting period) as storage bucket profile in DP and 9ASNP in SNP.
Now the requirement is to release demand of 1 TDP to SNP on one fixed day.
For example, my TDP is 1 - 10 (dates) and demand is 100 tons. I want to release total demand on only 5th i.e. on 5th my demand should be 100 tons and remaining all days it should be 0 tons.
Like that we need to release for every TDP demand into one day in that TDP.
The issue here is DP will have information of demand daily wise and hence am not able to release total demand on a fixed day.
I have referred some user exits for doing this, but not able to figure it out whether it will fulfill my requirement or not (Infact i could not able understand the purpose of the user exits). Can anyone please tell me, the user exits which can be used in demand release to SNP and how those will work???
Also can anyone please let me know how i can proceed on this requirement?
Will defenitely appreciate your answer by rewarding the points.
Thanks & Regards,
Jagadeesh.pl try enhancement APODM017 for changing the
have you also already seen BADI /SAPAPO/SDP_RELSPLIT ?
maybe using a time based distribution will help
http://help.sap.com/saphelp_scm50/helpdata/en/01/cdc94140496024e10000000a1550b0/content.htm -
How to genrate Report for Result of SNP & PP/DS ?
Hi All,
Currently i am working on SCM 5.0 Version.
I need to prepare a Report for Product Wise Planned Order or Production Order & Resource Wise Planned Orders or production Orders.
Can anyone tell me How can achive the above requirement?
Thanks in Advance!
Regards
Sujayyou should be able to find standard reports to do this (in the main menu)
you can also use rrp7 to get the list -
Release Planned Orders from SNP to R/3
Hello Experts:
I have a business request to release the Production Planned KF from SNP into a frozen MPS (or even an inactive fcst version) in R/3. Since we have only released a forecast from the DP side to R/3 in the past, can anyone tell me the best practice to release from SNP to R/3? Do I need to create an info cube to perform the release?
The business runs a Heuristic in SNP at the finished good level and the makes modifications and would like to release this to be used in the R/3 MRP run for some groups of materials, as opposed to releasing the forecast for MRP to run on.
Currently, I can send the data from SNP Production Planned KF to a time series KF in DP and release to MD63 from there, but they would like to release directly from SNP in the future.
Any suggestions are greatly appreciated!
AndreaHi Andrea,
If you want to release SNP planning data to ECC, you need to make following settings.
In customizing
Maintain Distribution definitions
Maintain Settings in Configure transfer to OLTP system in SNP customizing-Global Settings.
If you maintain periodic setting in SNP setting, you need to run transaction /SAPAPO/C5 to transfer data.
As well as u can do this also :
1) You need to create a release profile using transaction /sapapo/mc8s
2) In release profile, you need to maintain planning area, key figure to
be transformed, plg version, category, etc.,
3) Once it is created, using transaction /sapapo/mc8t, maintain the
R/3 transfer steps
4) Then create a planning job in background using transaction
/sapapo/mc8d -
Releasing the Demand Plan to SNP
Dears,
I need more illustration when you using Transaction Code /SAPAPO/MC90 to release demand to SNP
APO Help Say :-
"independent requirements is not restricted to planning in SCM SNP. Planned independent requirements within the production horizon are planned in production planning and detailed scheduling in SCM PP/DS."
What he means by data will be available n PP/DS?
Did APO System Generate Capacity Requirement? is that what he means ?
Regards
RamiRami
There are two horizons in the product master - SNP production horizon and SNP stock transfer horizon. In your company if you are using both SNP and PP/DS then after the forecast is released to SNP, you will execute SNP and then for the short term you will execute PP/DS.
In such a scenario (where SNP is used for mid term planning and pp/ds for the short term) , you need to maintain the SNP production horizon (in case of inhouse production) and stock trans horizon(for external procurement / branch to branch transfers) to define the boundary between sNP and PP/Ds. that is you need to specify till what day /week /month you need PP/DDS plan and for what time frame you need SNP plan. The SNP production / stk trans horizon is the horizon during which SNP will not generate any plan. That is if your stk trans horizon is say 10 days , then SNP will not genearate any supply within this 10 days even if there is demand . Supply will be generated for the next 10 days only by PP/DS. SNP will generate supply only outside the production /stock transfer horizon.
As specified by SAP , your planned independent requirement is thus not restricted to SNP. That is if the demand is within the prod / stk trans horizon it is fulfilled by the pp/ds run and demands outside the horizon are planned by sNP
Thanks
Saradha
Edited by: Saradha Ramesh on Sep 27, 2010 4:13 PM -
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 -
Demand on VC material not visible in SNP planning book
Hi Experts,
Is there any way to plan VC (Variant Configuration ) materials in SNP at the group level ?
I will explain the scenario more in details below
I have an VC material say X. Material X has end product Y attached to it (material variant). When material X is cifed to APO, it appears as configurable product in APO & is a top level product. Now when I create a demand on material X through DP, the demand appears in product view (RRP3). However the demand does not appear in the SNP planning book nor it gets selected during background planning run. The system is configured as Variant Configuration & not CDP.
Is it possible to plan material X in SNP ? If possible how can the demand be read in SNP ?
Thanks in advance
Regards
SandeepHi Sandeep,
One of the limitations of Characteristics Based Forecasting is, CBF results can only be used in PPDS and not in SNP, hence it is not possible to plan that material X in SNP. Even though you use MC90 transaction which is release DP to SNP, but the data will not be available in SNP
That material X will be planned only in PPDS, there are two ways to plan, those are
1. one way is by releasing CBF results to active version using MC90 transaction, during this release, you should maintain consumption group in release settings and in product master, in this case you have to use Forecast Check/Allocation check as a part of ATP/GATP, here you can not use CTP or MATP
2.the other way is by releasing CBF results to inactive version using MC90 transaction, during this release you should not define consumption groups, generate the dependent requirements in inactive verison using heuristics in PPDS , and convert dependent requirements from inactive version to Forecast - active version using /SAPAPO/DMP2 transaction, in this case you can use MATP/CTP as a part of GATP
-Deepak -
Hi Experts,
1.How to Group PRs considering the future PRs to make a container load of single product of a single vendor .
2. How to group the PR's of different products to make a container load of a single vendor .
Like in TLB we club STR's to STO to make a full container load ,Can we also use TLB which should use the results of SNP Heu or Opt or CTM i.e PR's to vendor , and Club then using the TLB profile.
Pls Confirm .
Thanks.
BallackHi Ballak,
Yes you can use TLB functionality for heuristic results. Please go through the following Note.
Note: 514947
Regards,
Kishore Reddy. -
Forecast Consumption in SNP for shipped qty's
Hello experts,
I got a question for forecast consumption in SNP and whether forecast stays "consumed" or not after a customer orders gets shipped (Post Goods Issue).
My example is: I have a weekly bucket forecast qty of 100 in DP and release this to SNP. Now in SNP planning book I have 30 units of open Customer Demand against it ... means I have 70 in Forecast line (30 units got consumed correctly). Once I create a shipment for the open Customer Order of 30 units in R3 the situations remains the same .. but if I post the Goods Issue now on the delivery document the Customer Demand disappears (which is correct) but my Forecast line increases again from 70 to 100. I thought forecast consumption in APO would "remember" the already shipped quantities ? I know that you can reorganize open forecast but want I'm looking for is the standard R3 behaviour of keeping already shipped qty's as consumed. Can anybody help here or explain ?
Regards
Thomas
Using SCM5.0Hi Datta,
I checked the note - there is only point 9 in the list saying:
"9. During goods issue for the delivery in R/3, the forecast is always reduced to the date requested by the customer. In addition, overdeliveries are ignored."
Unfortunately this doesn't explain how it works or needs to be done to have FCST consumption happen in APO_SNP based on shipped qty's. In my case FCST consumption works okay up to the point of posting the goods issue on a delivery document. I wonder if there something I need to activate somewhere to have this working since I can't see any "with drawn qty" in APO.
Any other hints ?
Regards
Thomas -
hello Gurus,
I am using target stock level method 1 in product master;this setting works fine in interactive planning but not in back ground planning run.
Can you please throw some light on significance of the below attribute and where/how to set this attribute
Indicator for Selecting the SDT Profile from /SAPAPO/SCZPRF
Use
The selection you make here determines how the target stock level is calculated.
You have the following options to calculate the target stock level:
(0) Use the safety stock and target days' supply on the Product master.
(1) Use target days' supply and safety stock only for the time period covered by the Time buckets profile.
(2) Use target stock level specified in the Planning parameters only for the time period covered by the time buckets profile.
(3) Use target days' supply and safety stock specified in the Planning parameters and apply the last target stock level value found in the past to additional periods that fall beyond the period defined in the Time buckets profile.
(4) Use the target stock level specified in the Planning parameters and apply the last target stock level value found in the past to additional periods that fall beyond the period defined in the Time buckets profile.
SAP recommends that you choose option (0) initially. For simulation purposes, you can change this setting by choosing, from supply network interactive planning, Planning -> Set Planning Parameters. After you have you have had an opportunity to run supply network planning in interactive planning mode using the different settings for simulation purposes, you can change this setting in the product master to make it valid for all supply network planning runs.
Dependencies
You must define options (1) to (4) in supply network interactive planning (Planning -> Set Planning Parameters) before you select an option in the product master data.Ha ha, I like this. New challenge!
What about this scenarios.
1. Forecast 500.000 unit per month. Lot size procedure Lot-for-Lot. Run SNP heuristic with time bucket month. Result - 1 SNP Pl.Order = 500.000 unit per month
2. Forecast not important. Lot size procedure Fixed Lot size = 500.000 (or min/max lot size). Run SNP Heuristic with time bucket month. Result - 1 SNP PL.Order = 500.000 per month.
You can have a separate job (separate selection loc/prod) for these SKUs with time bucket months (this is in the case when you are working with time bucket weeks).
3. At transportation lane level. Create transport capacity resource and assign it to the t.lane. In the resource you have the possibility to restrict the capacity at 500.unit per time bucket month.
Me too I have some issue at PPDS level. Can you give me some ideas for this issue http://scn.sap.com/thread/3596884
Regards, Marius -
From a weekly view we release the fcst to r3 and SNP in daily buckets. Its getting release correctly to SNP but not to R3. The data in R3 is off setted by a day. We dont have any user exits in CIF. I dont see any problem in publication setting. Any input is greatly appreciated.
Hi,
Did you check if there is any difference in Time Zones between the APO and R/3 systems? APO is always at UTC but R/3 could be at the local time. May be this helps. Check your calendars as well, like shipping, planning etc. -
SNP - Capacity Leveling question
Hi All:
I am trying to do Capacity leveling in one resource and for one material.
After CIFing the material, resource, location and BOM (PDS), I entered some forecast for the specific material in DP and released it to SNP.
Then I ran the product heuristics and when I looked at the planning book 9ASNP94 and Data View SNP94 I noticed that the capacity utilization where more than 100 % in some periods.
Next I executed the 'Capacity leveling button'. and entered the following parameters and executed.
Combined Scheduling
100 % max util
Product priority
Ascending
Heuristics Method
All Relevant Resources
In the Log checked all the three options
The log comes out as follows:
Green status on Resource and Parameters
Yellow status and 'Resource xxxx not used in any PPM/PDS'
Red status Resource utilization
I checked the PDS for the resource xxxx and i found it to be there.
When I go back to the Capacity view the leveling has not happened.
What am I doing wrong? Pl. help.
Thanks
NarayananHi Narayanan,
I think there should be any issue. I hope You selected the data view snp94(2), and loaded your resource in the planning book. then You executed the 'Capacity leveling button' in the planning Book, Right? Try without checking the 'consider alternative resource' check box, and dont give any priority in your capacity levelling profile.
Thanks,
Satyajit -
Hi,
I released forecast to SNP from DP. The released Forecast values in the standard planning book shows with negative values. To cross check the problem I tried to create Forecast from RRP3. The entered values shows up negative values in the SNP planning book. Any inputs in this regard would be appreciated.
Thanks and Regards,
K7Hi,
This is a bug. You never get negative values into SNP through release. You either need to upgrade the service packs or open a OSS message.
Refer to this [post.|Re: Forecast Values appear negative in SNP Planning Book; that talks about a similar issue.
Thanks.
Maybe you are looking for
-
ADF Mobile App integration with webservices, connection refused error
I created an ADF application for department search with business components and exposed this as a webservice. I can access the WSDL locally from a browser. Then created an ADF mobile application and deployed it to android emulator. I am able to deplo
-
support.skype.com/en/faq/FA297/How-do-I-request-a-refund I needed to send a refund request ongoing year $40.68. Charged on 6/27/14. Please help. Thank you.
-
I know I can add folders to IPhoto but I would like to create new rolls for separating my pictures as well and was wondering if it can be done.
-
How do i know how much disc space is left
need to have 5 gb of disc space to download snow leopard but i can;t figure out how to find out how much space i have
-
Extending Reader Rights causing Initialize event to fire twice?
I have a few drop-down boxes populated by scripts on their respective Initialization events. Everything worked great through development--except, when I demonstrated the form for a group, I noticed the drop-down boxes were populating twice. I wasn't