Frequency of Planning Run ?

Hi Experts,
I have a query with respect to the frequency of planning run in APO SNP..
1. If i receive forecast from DP once a month, shoud the frequency of SNP planning run should also be month ?? What all conditions should prompt me to take the SNP planning run on weekly basis inspite of getting the forecast from DP once a month ??
2. If i take SNP planning run monthly, then what should be the frequency of Deployment and TLB runs..?? What factors should be considered before deciding on the frequency of deployment and TLB runs..?
Your inputs would be highly helpful in deciding on the frequecy of plng runs in my project..
Thanks & Regards,
Krishna

Hi Krishna,
The frequency of your planning run will depend on the type of ur network. You havent given any details of ur network(the Supply chain) over which the SNP run will happen.
SO, let me assume that you r dealing with a Customer,DC and Factory, basically 3-level N/W.
Now, u r releasing demand from DP once a month and that forecast is on the Customer level, then the main factor is that whether you have any business process of capturing the sales from the Customer level. If you have that, then in which frequency?
If you can decide upon the frequency of the Sales updation from the Customer level, then we come to a scenario where the Customer requirement on the next level(D.C) is getting changed depending on the frequency of the Stock updation at the customer.
If the scenario is some sort of this, then ur SNP run should be in parallel with the frequency of the Stock/Sales updation at the customer level, because fresh requirement should flow to the lower level(D.C).
This can be one factor to decide ur frequency of ur SNP run. Like this, there may be many depending upon various Business Scenarios and Ur Supply Chain.
Now, coming to the Deployment and TLB run frequency, the main point of decision will come after gathering the business requirements. The frequency of TLB can be dependent on:
a) Stock holding capacity of ur source location--if there is a scenario that ur source location is not capable of holding stocks, then the frequency of ur TLB run should increase in order to Push the Stock to the next level.
b)Suppose you have found that, the demand of one of ur D.C is very less for a month. In that case u can run Depl and Tlb for it in lesser frequency in respect to other D.C whose demand may be much more.
So in a nutshell, Ur Deployment and TLb should depend on ur Business Scenario, the Products( fast moving, medium moving..), Capacity Constraints of ur factories, ur Parameters for ur modes of transport.
I hope i am able to clarify queries to some extent.
Regards
Sunshine

Similar Messages

  • How to exclude Sales Orders from a planning run

    Hi,
    I run MD02 and i discover that planned orders are being created as procurement proposals for sales orders and the planned independent requirement.
    I want planned order to be created only for the Planned independent requirements ONLY.
    Is there a way that sales orders can be excluded from the planning run?
    Thanks in advance for your suggestions.

    Dear,
    Check the requirement type of your sales order line item in VA02 procurement tab it should be Reqmt type of customer reqmt   KSL
    Also check the strategy assign in material master and MRP group OPPR and then check the setting of strategy 10 in OPPS there should be
    Customer Requirement planning
    Reqmt type of customer reqmt   KSL  Sale frm stck w/o ind.req.red.
    Requirements class  030  Sale from stock
    Allocation indicat.     No consumption with customer requirements
    No MRP   :-               1 Requirement not planned, but display.
    Please try and come back.
    Regards,
    R.Brahmankar

  • Safety stock not covered by schedule lines in planning run

    Hi !
    In our organization we are trying to implement scheduling agreements and automatic creation of delivery schedule lines through MRP. We have MRP type PD and it considers the reservations created by PM orders and Production orders as requirement elements. When I do the planning run, it creates schedule lines for the PM order reservations and purchase requisition for safety stock. I need it to create schedule lines for all scenarios. Kindly help and suggest a solution.
    Regards,
    Satya

    Hi,
    Please refer the below links.
    Schedule Lines not getting created in MRP
    Re: No Scheduling line is generated when RUN MRP
    Hope it helps you.
    Thanks.

  • SNP Optimiser issue (Annual Planning Run)

    Dear Friends,
    My fiscal year is 01.04.2010 to 31.03.2011, Now I am trying to run Annual planning run for the current FY.
    After the run, If i see in SNPOPLOG, all demand is showing as unfulfilled. If i run for the next FY it is planning.
    I want to run for the current FY, what settings I need to do?
    sree

    What is the time bucket profile of data view in which u are running optimizer.  If it is a single yearly bucket you cannot run optimizer in current year.  (your first bucket cannot have the start date in past)
    Choose 12 monthly buckets. and run planning.  You may 'view' the planning results in single annual bucket.
    even if you do this, there will be no plan in current month.  system will plan from next month onwards.
    Hope this helps.
    Regards,
    Nitin
    Edited by: Nitin Thatte on Apr 13, 2010 6:01 PM

  • Error occurred during CTM planning run

    Hi folks,
    Appreciate your co-operations!
    I am facing the problem while running the CTM with the profile DEMO2.
    CTM Planning Run gives one error and alert.
    Error: Error occurred during CTM planning run
    Technical Data
    Message type__________ A (Cancel)
    Message class_________ /SAPAPO/CTM1 (CTM: Messgaes)
    Message number________ 401
    Problem class_________ 1 (very important)
    Number________________ 1
    Environment Information
    CTM Action____________ G
    Message type__________ A
    Alert: Internal error has occurred (<!> Segmentation fault)
    Technical Data
    Message type__________ E (Error)
    Message class_________ /SAPAPO/CTM1 (CTM: Messgaes)
    Message number________ 571
    Message variable 1____ <!> Segmentation fault
    Number________________ 1
    Environment Information
    CTM Action____________ G
    Message type__________ C
    Log file display
    <i> 04:37:59 optsvr_main.cpp(1363) 'SuperVisor' => Commandline : 4 respected parameters ...
    Args:
    m0001006
    sapgw04
    28812935
    IDX=1
    <i> 04:37:59 optsvr_main.cpp(645) 'SuperVisor'  * SAP APO CTM Engine [CTM/ctmsvr]
    <i> 04:37:59 optsvr_main.cpp(646) 'SuperVisor'  * Copyright u00A9 SAP AG 1993-2009
    <i> 04:37:59 optsvr_main.cpp(647) 'SuperVisor'  *
    <i> 04:37:59 optsvr_main.cpp(648) 'SuperVisor'  * Version        : 7.0_REL SP05, 407661, Nov 25 2009 22:59:47
    <i> 04:37:59 optsvr_main.cpp(649) 'SuperVisor'  * Platform       : ntamd64/x64
    <i> 04:37:59 optsvr_main.cpp(650) 'SuperVisor'  * Interface      : 2.0
    <i> 04:37:59 optsvr_main.cpp(651) 'SuperVisor'  * Build date     : Nov 25 2009 22:59:47 [1259186387]
    <i> 04:37:59 optsvr_main.cpp(652) 'SuperVisor'  * Build machine  : PWDFM163
    <i> 04:37:59 optsvr_main.cpp(653) 'SuperVisor'  * Latest change  : 407661
    <i> 04:37:59 optsvr_main.cpp(654) 'SuperVisor'  * NW release     : 7100.0.3300.0
    <i> 04:37:59 optsvr_main.cpp(655) 'SuperVisor'  * Perforce branch: 7.0_REL
    <i> 04:37:59 optsvr_main.cpp(656) 'SuperVisor'  *
    <i> 04:37:59 optsvr_main.cpp(676) 'SuperVisor'  * Hostname       : m0001006
    <i> 04:37:59 optsvr_main.cpp(677) 'SuperVisor'  * OS version     : 5.2.3790 (WinServer2003, NTAMD64) SP2.0 (Service Pack 2), SERVER ENTERPRISE TERMINAL SINGLEUSERTS
    <i> 04:37:59 optsvr_main.cpp(678) 'SuperVisor'  * PID            : 6768
    <i> 04:37:59 optsvr_main.cpp(683) 'SuperVisor'  * CWD            : D:\usr\sap\SC6\DVEBMGS04\log
    <i> 04:37:59 optsvr_main.cpp(684) 'SuperVisor'  *
    <i> 04:37:59 core_sysinfo.cpp(453) 'SuperVisor' * free disk space: 190433 MB
    <i> 04:37:59 core_sysinfo.cpp(454) 'SuperVisor' *
    <i> 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' * Memory information:
    <i> 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' *   physical memory: 10238 MB total, 6511 MB available [63% free]
    <i> 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' *   page file      : 73212 MB total, 60889 MB available [83% free]
    <i> 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' *   virtual memory : 8388607 MB total, 8388499 MB available [99% free]
    <i> 04:37:59 optsvr_main.cpp(693) 'SuperVisor'  *
    <i> 04:37:59 optsvr_main.cpp(783) 'SuperVisor' * running in invoke mode
    <i> 04:37:59 optsvr_rfcconnection.cpp(871) 'MsgMgr' <RFC> RfcPing(RFC_HANDLE=1) received in thread#6912
    <i> 04:37:59 optsvr_rfcconnection.cpp(692) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PARAM_SET' for sending of parameters/options
    <i> 04:37:59 optsvr_rfcconnection.cpp(703) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PARAM_GET' for receiving of parameters/options
    <i> 04:37:59 optsvr_rfcconnection.cpp(712) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PROGRESS' for progress informations
    <i> 04:37:59 optsvr_rfcconnection.cpp(721) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_MESSAGE' for messages
    <i> 04:37:59 optsvr_rfcconnection.cpp(730) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_RESULT' for (intermediate) result informations
    <i> 04:37:59 optsvr_rfcconnection.cpp(739) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_SYSINFO' for system informations
    <i> 04:37:59 optsvr_rfcconnection.cpp(748) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PERFINFO' for performance informations
    <i> 04:37:59 optsvr_rfcconnection.cpp(1269) 'MsgMgr' <RFC> skipping empty profile value [GENERAL] sPROFILE_CUST_ID
    <i> 04:37:59 optsvr_rfcconnection.cpp(1835) 'MsgMgr'
    Sender/Receiver RFC_HANDLE#1:
    <RFC> * RFC connection attributes:
      Own Host    : m0001006
      Partner Host: m0001006
      Destination : OPTSERVER_CTM01
      Program Name: SAPLRCC_COMM_ENGINE
      SystemNr    :              04       SystemId    : SC6
      Client      :             700       User        : MBATCHA    
      Language    :               E       ISO Language: EN
      CodePage    :            1100       Partner CP  : 1100
      Kernel Rel. :            701        Partner Rel.: 701
      Own Release :            711        CPIC ConvId : 28812935
      Own Type    :               E       PartnerType : 3
      Trace       :                       RFC Role    : S
    <RFC> * RFC statistic information:
      number of calls        : 7
      number of received data: 10569
      number of sent data    : 1349
      overall reading time   : 9073
      overall writing time   : 162
    <i> 04:37:59 optsvr_main.cpp(1110) 'SuperVisor' * Starting MainScript ...
    <i> 04:37:59 optsvr_main.cpp(1445) 'SuperVisor'
    ***************************** OPTSVR - OPTIONS ***************************** *
    [CTM_PROFILE]
    nCTMENGINEPACKAGESIZE = 500
    sCOMPONENT = SCM
    sCTMLOGFILE = ctm.DEMO2.0000_0001.20091201043758.log
    sCTMLOGFLAG = 0
    sCTMPROFILE = DEMO2
    sRELEASE = 700
    [general]
    bUNICODE = true
    nSLOT_MAXIMUM = 1
    nSLOT_MINIMUM = 1
    nSLOT_RESERVED = 1
    sAPO_RELEASE = 700
    sAPPLICATION = CTM
    sExeDir = d:\apoopt\ctm\bin
    sExeName = ctmsvr.exe
    sHOST = m0001006
    sInvokeMode = invoke
    sLANGU = E
    sMANDT = 700
    sPRODUCT_NAME = APO
    sPRODUCT_PATCHLEVEL = 0001
    sPRODUCT_RELEASE = 700
    sPROFILE = DEMO2
    sSESSION = tju5Bmz21}6WVG0Sn6pv3W
    sSYSTEM = SC6
    sUNAME = MBATCHA
    [init]
    sSECTION0001 = INIT
    sSECTION0002 = GENERAL
    sSECTION0003 = PASSPORT
    sSECTION0004 = CTM_PROFILE
    [PASSPORT]
    bIS_REMOTE = false
    nACTION_TYPE = 1
    nSERVICE = 1
    sACTION = /SAPAPO/CTMB
    sPRE_SYSID = SC6
    sSYSID = SC6
    sTRANSID = 2205DEDE7A5BF16DA07D001CC46CF90E
    sUSERID = MBATCHA
    ************************** OPTSVR OPTIONS - END **************************** *
    <i> 04:37:59 core_msgmgr.cpp(440) 'MsgMgr' * Sending progress number 802 to OutputInterface from []
    <i> 04:37:59 core_supervisor.cpp(728) 'SuperVisor' <M> Invoking module 'CTMModelGenerator' [6]->download
    <i> 04:37:59 core_msgmgr.cpp(440) 'MsgMgr' * Sending progress number 806 to OutputInterface from [MG]
    <i> 04:37:59 ctm_modelgen.cpp(166) 'CTMModelGenerator' ======================================================================
    <i> 04:37:59 ctm_modelgen.cpp(167) 'CTMModelGenerator' MG::download
    <i> 04:37:59 core_msgmgr.cpp(1110) 'MsgMgr' renaming tracefile
    <i> 04:37:59 core_msgmgr.cpp(1111) 'MsgMgr' old name: optsvr_trace20091201_043759_1a70.log
    <i> 04:37:59 core_msgmgr.cpp(1112) 'MsgMgr' new name: ctm.DEMO2.20091201_043759_1a70.log
    logfile reopened : Tue Dec 01 04:37:59 2009
    logfile name     : ctm.DEMO2.20091201_043759_1a70.log
    <i> 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
    <i> 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PRDAT_RFC_READ
    <i> 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PLPAR_RFC_READ
    <i> 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_LOC_RFC_READ
    <i> 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PPM_RFC_READ
    <i> 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_TRANS_RFC_READ
    <i> 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_RES_RFC_READ
    <i> 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_SSTCK_RFC_READ
    <i> 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_CAL_RFC_READ
    <i> 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PLPER_RFC_READ
    <i> 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_INCMD_RFC_READ
    <i> 04:38:03 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
    <i> 04:38:03 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_DEM_RFC_READ
    <i> 04:38:04 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_SUP_RFC_READ
    <i> 04:38:04 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_UCMAP_RFC_READ
    <i> 04:38:04 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
    <i> 04:38:04 core_msgmgr.cpp(440) 'MsgMgr' * Sending progress number 810 to OutputInterface from [MG]
    <i> 04:38:04 ctm_modelgen.cpp(735) 'CTMModelGenerator' MG::download done
    <i> 04:38:04 ctm_modelgen.cpp(736) 'CTMModelGenerator' ======================================================================
    <i> 04:38:04 core_supervisor.cpp(750) 'SuperVisor' <M> Returning from module 'CTMModelGenerator' [6]->download = success [ctx size : 1]
    <i> 04:38:04 core_supervisor.cpp(692) 'SuperVisor' <SCR> Starting script 'CTM Solve' with 9.22337e+012 seconds left
    <i> 04:38:04 core_supervisor.cpp(692) 'SuperVisor' <SCR> Starting script 'CTM Match' with 9.22337e+012 seconds left
    <i> 04:38:04 ctm_executionmanager.cpp(102) 'SuperVisor' ======================================================================
    <i> 04:38:04 ctm_executionmanager.cpp(103) 'SuperVisor' statistics:
    <i> 04:38:04 ctm_executionmanager.cpp(104) 'SuperVisor' number of demands: 7
    <i> 04:38:04 ctm_executionmanager.cpp(105) 'SuperVisor' ======================================================================
    <i> 04:38:04 ctm_executionmanager.cpp(107) 'SuperVisor' ======================================================================
    <i> 04:38:04 ctm_executionmanager.cpp(108) 'SuperVisor' parameters:
    <i> 04:38:04 ctm_executionmanager.cpp(118) 'SuperVisor' time continuous planning
    <i> 04:38:04 ctm_executionmanager.cpp(125) 'SuperVisor' backward scheduling
    <i> 04:38:04 ctm_executionmanager.cpp(184) 'SuperVisor' CBCLP enabled
    <i> 04:38:04 ctm_executionmanager.cpp(457) 'SuperVisor' ======================================================================
    <i> 04:38:04 core_supervisor.cpp(728) 'SuperVisor' <M> Invoking module 'CtmEngine' [7]->run
    <i> 04:38:04 ctm_executionmanager.cpp(523) 'SuperVisor' ======================================================================
    <i> 04:38:04 ctm_executionmanager.cpp(524) 'SuperVisor' EM::execute for packet 1
    <i> 04:38:04 ctm_executionmanager.cpp(1570) 'SuperVisor' EM::execute for packet 1 done
    <i> 04:38:04 ctm_executionmanager.cpp(1571) 'SuperVisor' ======================================================================
    <i> 04:38:04 core_supervisor.cpp(750) 'SuperVisor' <M> Returning from module 'CtmEngine' [7]->run = success [ctx size : 1]
    <i> 04:38:04 core_supervisor.cpp(728) 'SuperVisor' <M> Invoking module 'CTMModelGenerator' [6]->upload
    <i> 04:38:04 ctm_modelgen.cpp(1097) 'CTMModelGenerator' ======================================================================
    <i> 04:38:04 ctm_modelgen.cpp(1098) 'CTMModelGenerator' MG::upload of packet 1
    <e> 04:38:05 ctmsvr_script.cpp(229) 'SuperVisor' <!> STRING EXCEPTION : <!> Segmentation fault
    <i> 04:38:05 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
    <i> 04:38:05 optsvr_main.cpp(1166) 'MsgMgr' Current check values:
    [CHECK_EQUAL]
    [CHECK_UPPERBOUND]
    nPEAK_MEMORY_NTAMD64 = 45344
    [CHECK_LOWERBOUND]
    <i> 04:38:05 optsvr_main.cpp(1209) 'MsgMgr' Performance values:
    bSuccess     false
    nCPU_TIME     0
    nPEAK_MEMORY     45344
    nPEAK_VIRTUAL_BYTES     141844
    nREAL_TIME     6
    tracefile     ctm.DEMO2.20091201_043759_1a70.log
    <i> 04:38:05 optsvr_main.cpp(1235) 'MsgMgr' Performance Monitor values:
    ENGINE_VERSION     7.0_REL SP05, 407661, Nov 25 2009 22:59:47
    nCPU_TIME     0
    nHD_FREESPACE     190433
    nPEAK_MEMORY     45344
    nPEAK_VIRTUAL_BYTES     141844
    nREAL_TIME     6
    <i> 04:38:05 optsvr_dsr.cpp(96) 'MsgMgr' <writeDSRdata> tracing not active => no DSR written
    <i> 04:38:05 optsvr_main.cpp(1256) 'SuperVisor'
    Finished->FAILED ...
    <i> 04:38:05 core_memmgr.cpp(564) 'MsgMgr'   transferring memory of heap 6912 to main heap
    <i> 04:38:05 core_memmgr.cpp(606) 'MsgMgr'   finished transfer of heap 6912
    <i> 04:38:05 optsvr_rfcconnection.cpp(1835) 'MsgMgr'
    Sender/Receiver RFC_HANDLE#1:
    <RFC> * RFC connection attributes:
      Own Host    : m0001006
      Partner Host: m0001006
      Destination : OPTSERVER_CTM01
      Program Name: SAPLRCC_COMM_ENGINE
      SystemNr    :              04       SystemId    : SC6
      Client      :             700       User        : MBATCHA    
      Language    :               E       ISO Language: EN
      CodePage    :            1100       Partner CP  : 1100
      Kernel Rel. :            701        Partner Rel.: 701
      Own Release :            711        CPIC ConvId : 28812935
      Own Type    :               E       PartnerType : 3
      Trace       :                       RFC Role    : S
    <RFC> * RFC statistic information:
      number of calls        : 116
      number of received data: 420457
      number of sent data    : 39262
      overall reading time   : 5.30093e+006
      overall writing time   : 3831
    <i> 04:38:05 optsvr_main.cpp(1332) 'MsgMgr'
    OptimizeServer says  GOOD BYE
    Please help me to resolve this issue.
    Thanks & Regards,
    Khadar

    Hi Khadar,
    1) The information you have provided is the CTM optimiser log.
    Run the job in background and in  sm37 and click on job log &
    analyse the exact error happened.  In case if you are not able
    to do, please provide the error log.
    2) Check the livecache is stable in its operations when the job
    runs (check with basis team)
    3) Run consistency check for master data before CTM run
    4) Check for any struck queues and clear those and rerun
    5) If you feel more inconsistencies in system, run livecache
    consistency and rerun CTM run
    Regards
    R. Senthil Mareeswaran.

  • Error - Background Processing: Planning Run

    Hey Guys,
    I want to schedule a background planning run. The report /SCMTMS/CL_TS_VSR_BGD is terminated
    because of the following error. Has anyone an idea how to solve this issue?
    Kind reagards,
    Christian
    Error in the ABAP Application Program
    The current ABAP program "/SCMTMS/VSR_OPT_BGD" had to be terminated because it
    has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "/SCMTMS/CL_TS_VSR_BGD=========CP " in include
    "/SCMTMS/CL_TS_VSR_BGD=========CI " in
    line 42:
    "Direct access to the components of the global interface /SCMTMS/IF_SRV"
    "MGR_TYPES is not allowed (INTERFACE /SCMTMS/IF_SRVMGR_TYPES LOAD state"
    "ment is missing)."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SANNG "
    Error in the ABAP Application Program
    The current ABAP program "/SCMTMS/VSR_OPT_BGD" had to be terminated because it
    has
    come across a statement that unfortunately cannot be executed.

    Can you refer the following SAP Notes will help you to resolve your problem.
    1230638 Memory consumption for VSR planning run too high
    1285772 Planning: Write application log from VSR batch reports
    1279704 Planning: Various performance improvements

  • Reschedulig Date Problem in Planning Run

    Hello All,
    Need Clarification..
    The Scenario:
    The Requirement date (OrdRes) is 13.02.2009, The planned Order generated is on 13.02.2009.
    Now the OrdRes Date Changed Manually to 27.01.2009.
    After Background MRP Run, in MD04 against the planned order, the Rescheduling date proposed is 27.01.2009 and exception message is 30 ( Plan process according to schedule).
    System is Proposing the date, but not actually shifting the planned order.
    If I re-run the MRP Manually, the Rescheduling is happening.
    What at first place the rescheduling not happened? after manual MRP run the rescheduling happening?
    P.N:
    1. The Planned Order is not Firmed
    2. The Planning Parameters are same for Background Run and Manual one.
    Your inputs are highly appreciated..
    Regards,
    Siva

    Hi Siva Kumar,
    Once u change the delivery date (order rervation of Header), system will create planning file entry for Child materail and set Exception message 30 of child planned order
    When u run the MRP  next, child material should be included in the Planning Run and rescheduling should be happened .
    This is what my finidings, Please check.
    Pradeep

  • Error Mrp: Total Planning Run stopped due to 25 Terminations of 202 Matls

    Hi
    We are trying to run the Mrp Job I.e  steps (RMMRP00) with variant PLVH_NETCHNG)..
    I have 1 db server and 2 apps servers and it the starts to run for about 2 minutes and then  crashes with the ffg error:
    Total Planning Run stopped due to 25 Terminations (dumps)of 202 Matls.
    Apps Guys  says its a basis issue and i cant see an issue.
    ANy help will be appreciated

    Hi,
    Please check the MRP setting some times we define mrp value upto 3-4 decimal and our setting upto 2 decimal points. If you send error log then that will be helpful for us to see the exact problem in the dump.
    In case you want to send this by mail send [email protected]
    Regards,
    Anil

  • Lot size exclusion from planning run

    Hi Gurus
                   My scenario is some materials are maintained with lot sizes as EX , VB, HB ,  when planning run executed , the system should not consider the VB and HB lot sizes ( these are not bom components) and no procurement proposal should exist , we are not following storage location MRP ,
    Pl come back in full thanks in advance
    Regards
    Ram

    Hi ramki
    VB is MRP type not lot size. VB consumption based planning with manual reorder point. The planning proposal will be created based on your reorder level.
    HB is lot size of " Replinishment to maximum lot size "
    Normally oils and others are procured where the storage tank capacity is restricted. The max replish level will be your max tank capacity.  You can define them as cosumable materials or bulk materials.
    Regards
    J . Saravan

  • End Planning Run After Order Selection - issue not clearing down all plans

    Hi,
    We are using the CTM Profile with "End Planning Run After Order Selection" ticked in the basic settings tab in order to clear down previous CTM runs. So we have a CTM deletion profile.
    The issue is that it requires more than one execution to clear down the Planned Orders / Purchase Requisitions. You execute the Deletion CTM Profile once and it will clear down some of the Purchase Requisitions and Planned Orders and leave some still in place. You then have to execute the deletion CTM profile one or two more times in order to delete the remaining Planned Orders / Purchase Requisitions.
    This is clearly not realiable for a batch process to clear down plans. Has anyone else experienced this and does anyone have a solution. The solution cannot be based on RLCDELETE or /SAPAPO/DELETE_PP_ORDER
    Mark

    Hi,
    Can you check your planning mode and deletion mode combination defined in the ctm profile.
    Prerequisties for deleting the orders:
    u2022 They are within the planning and deletion periods
    u2022 They do not have pegging relationships with demands outside of the planning period
    They lie outside of the production horizon, stock transfer horizon and the planned delivery time
    In addition, all location products of an order must be included in the Master Data Selection so that CTM can
    delete the order. Also, CTM cannot delete any manually fixed orders.
    If you have selected the SNP Order order type in the CTM profile, CTM cannot delete any PP/DS orders. This
    restriction is also valid the other way round for the PP/DS Order order type. If you select this order type, CTM also
    deletes SNP orders.
    Thanks,
    nandha

  • Exclude stock at a storage location from the Productionn Planning run

    Hi,
    We have to exclude a storage location from the Production Planning run. We already implemented a user exit in CIF and changed the stock at the storage location to a category Z1 that is not relavant to SAP, but the stock at the location is still being consitered for production planning.
    Please suggest a way so that it is excluded from the Production planning
    Regards,
    Sireesh

    Hi Sireesh,
    Please try these following options.
    1) Filter this storage location in the programme /SAPAPO/RMSDPDEP by writing customised code with an abapper, so that it will drops the storage location stocks not getting planned during deployment
    2) Try anyof these user exists
    APOBP011 Enhancement for Stock BAPIs (BUS10504)
    APOCF011 Inbound Processing: Stock
    APOCF027 Customer-Specific Enhancements: Stock
    3) Exclude the category from the ATD receipts category group maintained in the master data
    Regards
    R. Senthil Mareeswaran.

  • How to Check Error Log for Supply Planning Run

    Hi All
    I am getting error in supply planning run. I see the status under Excel Add-in >Supply Planning > Status. However there is no detailed error message here
    How can I check the detailed log of this error to understand what is going wrong.
    Can anybody guide on what can be probable causes of the error
    Any help is highly appreciated
    Thanks
    Vijay

    Hello Vijay, Wade
    Can you run the Supply Planning in Simulation mode? Under the simulation drop-down you can also see 'Show Message'.
    Open it after your planning run to see list of any data inconsistencies.
    Thanks
    Pramod

  • Launch ASCP plan run very long time

    Hi,
    I launched constrained ASCP plan and it took very long time. I launch ASCP plan in friday and it still not finished yet till monday, Memory Based Shapshot & Snapshot Delete Worker are still running, Loader Worker With Direct Load Option is still in pending phase. MSC: Share Plan Partitions has been set to Yes.
    When I run query below :
    select table_name,
           partition_name
    from   all_tab_partitions
    where  table_name like 'MSC_NET_RES_INST%'
    OR     table_name like 'MSC_SYSTEM_ITEMS%'
    order by substr(partition_name,instr(partition_name,'_',-1,1)+1);
    The results are:
    MSC_SYSTEM_ITEMS
    SYSTEM_ITEMS_0
    MSC_NET_RES_INST_AVAIL
    NET_RES_INST_AVAIL_0
    MSC_SYSTEM_ITEMS
    SYSTEM_ITEMS_1
    MSC_SYSTEM_ITEMS
    SYSTEM_ITEMS__21
    MSC_NET_RES_INST_AVAIL
    NET_RES_INST_AVAIL__21
    MSC_NET_RES_INST_AVAIL
    NET_RES_INST_AVAIL_999999
    MSC_SYSTEM_ITEMS
    SYSTEM_ITEMS_999999
    Please help me how to increase the performance when launching the plan. Is change MSC: Share Plan Partitions to No the only way to increase the performance in running plan?
    Thanks & Regards,
    Yolanda

    Hi Yolanda,
    a) So does it means that plan was working fine earlier but you are facing this issue recently.. ? If so then what you have changed at server side or have you applied any recent patches.. ?
    b) If you have not completed plan for single time,
    I will suggest that run data collection in complete refresh mode for one organization which is having relatively small data. Further, you can modify plan options in order to reduce planning calculation load like
    - disable pegging
    - remove any demand schedule / supply schedule / global forecast etc
    - enable only single organization which having relatively small demand and supply picture
    - disable forecast spread
    Once one plan run will be completed, then expand your collection scope to other organizations and also enabling above mentioned setting.
    There are lots of points need to consider for performance issue like server configuration, hardware configuration,  num of demands etc. So you can raise SR in parallel while working on above points.
    Thanks,
    D

  • Regenerative planning run in APO

    Hi experts,
    I need your input on the following scenario.
    We have APO PPDS implemented for our Manufacturing industry client. We have designed to run only Net Change Planning every day and there is no design to run Regenerative Planning.
    What is the importance of running Regenerative Planning? What do we lose if we don't run a regenerative planning?
    We have CTP scenario, so there are lot of parts planned automatically.
    Is there any impact of automatic planning on Regenerative planning and vice versa?
    What is the best practice to follow with respect to Regenerative Planning?
    I appreciate if someone could answer these questions. Thanks in advance.
    Regards,
    Manimaran M.

    Hello Mani
    Following are details are from old SAP Handbook,  good information to understand the concept.
    ====
    Net Change Planning
    Automatic material requirements planning is especially hard on system performance for production processes with complicated BOM structures. To guarantee frequent planning runs of those materials which are relevant for planning despite this problem, you can carry out the planning run with the "net change planning" procedure. This process only plans those materials which have undergone a change relevant to material requirements planning (for example, change in a production order due to excessive scrap, a new sales order, and so on) since the last planning run.
    The so-called planning file exists especially for the planning run and contains all the materials and their respective MRP types. If a material is changed in a way that is relevant to the planning run, it is given a net change indicator meaning that it will be included in the next net change planning run. In a net change planning run, only these materials are planned.
    Net Change Planning in the Planning Horizon
    Performance can be improved even further by using the net change planning run in the planning horizon.  Here, only those changes relevant to requirements planning that fall within a specific period (defined by the user and known as the planning horizon) are included in the planning run. It is advisable in this situation to carry out a total planning run in regular intervals (for example, weekly or monthly) to keep the planning results completely up-to-date.
    Regenerative Planning
    It is also possible to carry out a regenerative planning run. In this planning run, the system plans all materials that are relevant for planning. Usually, the regenerative planning run is only carried out in the implementation stages.
    ===
    Hope this will help.
    Thank you
    Satish Waghmare

  • Planning Run through MD01

    I was trying to take planning run for several plants,
    made necessary config in spro, but unable to generate plan orders,
    when i taking planning run through MD02, Plan order for material is generated, Kindly help me to find where i have missed the settings, no error is cooming when i am taking planning run

    Hello Abhay,
    MD01 is not advisable to run for all plants (if you are working with scope of planning). Run the same from MDBT transaction in background and check the spool log once this MRP finish...This will be better advisable from SAP. here you will come to know which materials are planned or which are not.
    1) Check the controller parameters are same of your MD02 and MD01 to create planned orders.
    2) Check indicator 3 delete and recreate data in controller parameter for MD01.
    3) Check planned all components from the sane screen.
    4) Run with regenerative planning if it is first time.
    Run the job from SE38 with variant to create plannig file entries for all parts in plants.
    Check whether MRP area activate check box is active or not in customizing...check the same whether plant level MRP indicator activated in customizing.
    Please let me know whether your problem is solved. Thanks
    Regsrds...
    TAJUDDIN

Maybe you are looking for