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

Similar Messages

Why overdued pr is not deleted during DRP planning run in APO?

the PR information still contain external PR created in DRP planning mode and it was not deleted.
I am doubt about that the planning run in ROP planning mode cannot delete old PR before recalculating PR.

I found the root cause of this symptom and have a plan to fix them.
The root cause of it is that DRP planning run has not performed successfully.
1. Details.
For material: P174552
This material’s BOD hierarchy is
4860 (Reorder point based)
└ 6000 (Reorder point based)
└ 6080 (Period based)
For both 4860, 6000 Reorder point based planning mode, but for 6080 Period Based planning mode.
This 6080’s Period based is incorrect because this material’s ABC grade is ‘N’; it should be Reorder point based.
As you see it in below screen-shot, there is error log in DRP planning for this material.
I found that about 5% of materials has incorrect planning mode.
2. Fixing Plan:
This weekend I will recalculate all material’s planning mode again and
will Run DRP planning process chain in monthly job again.

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

Planning run issue

Good morning,
I am planning a product in a sim version in APO, if I do a regen planning run it works but if I run the same scenario (and reset the results) with a net change it is not included (not planned) in the planning run.
Am I missing something obvious??
Thanks in advance.

Hi Prasad,
Planning run can be performed both with netchange as well as with
regenerative mode.
Every time, when planning relevant changes are done in system, system
automatically sets up planning file entry for the location product
combination.
If you select net change method, only those items with plannning file
entries will be planned in planning run.
If you select regen mode, the entire sequence will be replanned
irrespective of planning file entries.
Again, the selection of net change or regen mode is purely depends
upon the client/business depending upon the requirement.
Regards
R. Senthil Mareeswaran.

CTM run in APO

Dear All,
I am learning APO.I can do the
DP & SNP (Network ,Multilevel)
heuristics Runs on APO 3.1 very well.
I would like to know how to Run CTM ? What is CTM? and most important what are the settings required for CTM run in APO?
Can anybody help & guide me.
I am awaiting for your valuable answer.Many thanks in advance.
Warm Regards,
Vishwesh Rajguru

Waht is CTM
Capable-to-Match (CTM) functions match a large set of
prioritized customer demands and forecasts to a set of
categorized supplies considering the current production
capacities and transportation capabilities in a multistage
production environment, as in the semiconductor
industry. CTM is based on constraint-based propagation
techniques and goal-oriented programming.
Preprocessing tools provide a set of categorized supplies
and prioritized demands as input to the CTM Engine,
which then performs a fast check of production
capacities while considering transportation capabilities.
Prioritize by Demand
CTM prioritizes demands, such as customer orders
or forecasts from SAP APO Demand Planning, based
on such characteristics as customer priority, location,
and product priority.
Supply Categorization
CTM performs supply categorization based on the
available supply and user-defined inventory limits, such
as amount of inventory or planned deliveries.
CTM Engine
The CTM engine delivers the functions you need to
control supply and demand. The CTM engine process
can be divided into two steps. In the first step, the
CTM engine builds the CTM application model using
the specified supply network model. In a second phase,
the CTM engine matches demand to supply considering
production capacities and transportation capabilities
and using constraint-based propagation. CTM searches
before production and after production.
In before production searches (or most to least), the
system first searches through all supply categories for
finished or semifinished products before it resorts to
ordering production for that item. The search is
conducted top down. The system first searches the
production process model for finished products, then
intermediate products, then raw materials.
In after production searches (or least to most), the
system searches for categories after an attempt is made
to produce the item.
Time-Dependent Production Processes
You can define different production processes,
including product flow, for different time intervals. The
CTM engine chooses only production processes that
are valid at the representative time.
Model Alternative Components
You can implicitly model alternative components by
annotating a list of alternatives within the bill of
material, or you can model alternative components
explicitly by defining a set of product substitutions for
a given product.
Identification of Raw Material
A special product category identifies material that is
available in an infinite quantity. But for the consumption
of this product, a purchase requisition must be
created.
Process Flows Based on Demand
You must select a specific process flow based on the
set of characteristics of a given demand. For a planning
process that covers several physical plants, you must
be able to restrict the production and distribution
network to a set of allowed plants. In addition, the
CTM engine can handle the plant substitution rules of
SAP APOs Global ATP component.
Product Substitution Rules
CTM considers a set of demand characteristics for each
product and a prioritized list of substitute products
using Global ATP rules.
Customization/Settings
Global customizing settings
The package size is the key parameter that can improve the performance if you are using the asynchronous liveCache (LC) update.
In asynchronous update the system creates the orders in the LC after planning the specified number of demands. At the same time, the system continues with the CTM planning for the other demands.
The performance depends on the amount of planned orders that are created per demand.
If you set up a package size of 1000 demands, this means that each 1000 demands CTM writes the results to the LC. If there are only 1000 planned orders created for fulfilling these 1000 demands then the package size is too small for an asynchronous run with a good performance because the CTM run needs to stop each 1000 planned orders for triggering the LC writing. This increases then the run time. In case there are 100.000 planned orders created then the package size is too big because the CTM run for creating these 100.000 planned orders needs probably longer than the parallel writing of the results to the LC.
So the optimal package size makes the planning and writing to LC almost parallel.
Apart from the package size of the asynchronous LC writing, there are three more areas where packages must be defined.
- Package Size for Creating Orders. The value indicates how many orders can be created in the LC at one time.
- Package Size for Creating Pegging Relationships. The value indicates how many pegging relationships can be created in the LC at one time.
- Package Size for Order Selection. The value indicates for how many location products a LC request can be started at one time (package size for reading orders from LC in a way that CTM can use them for planning).
It is difficult to give recommendations regarding these package sizes because one needs to play around in a specific situation to improve the performance. So consider the following values as an orientation.
Regarding the package size of the Order Creation a value smaller than 1000 can be recommended (default value is 500 orders), but also a value up to 5000 can be efficient. In case of performance issues it is recommended to run CTM with different package sizes : 500, 1000, 2500, 5000 and see whether one of these settings can improve the performance.
Regarding the package size for Creating Pegging Relationships a value bigger than 1000 is recommended. The default value is 5000 pegging relationships.
The setting for the Order Selection is based on location-products, which implies that if the setting is currently 5000, CTM reads the orders for the first 5000 location-products and sends them in one package from the LC. If the average amount of orders per location-products combination is 10 (each location-product has in average 10 orders) the result is 50.000 orders transferred in the package.
As this setting depends on the amount of orders existing per location-product, one needs to play again with different settings in case of performance issues. Generally it is recommended to have a value smaller than 10.000.
3) Planning profile (business improvements)
Apart from the customizing settings, the performance depends on many other criteria like the Master Data Selection, Order Selection, Selected Demands, Planning Period, Product-Location restrictions.
If you want to improve the performance you should create a master data selection which contains only the objects in the model which are actively planned by the CTM run.
You can check whether it is possible to divide your supply chain in separate independent model parts. This covers a big performance improvement potential because the independent parts of the chain can be planned in parallel.
Then the order selection, especially the size and data requirements, is one of the major areas where you can improve the performance.
During the deletion of orders in a CTM planning run, several checks that are not always required are run. The parameter 'FAST_DEL' skips some checks of the normal planning run to improve the planning run time. The parameter is activated if you set Value1 of the planning parameter to X. In this case, no information is analysed on pegging, input or output nodes during order selection. Therefore, the parameter can only be reasonably used with the planning mode "Regenerative planning" (Replan all Orders) and the deletion mode "All unfirmed orders" (Delete all Orders that are not firmed). Note that in this case, only the status and the type of the order are analyzed for the deletion decision. This means that all planned orders or purchase requisitions are deleted, if they were not firmed manually (Output fix) and contain at least one location product that is contained in the CTM master data selection. This parameter must not be used if you use a subcontracting scenario. In this case, inconsistencies can occur between the data in APO and the R/3 System because subcontracting purchase requisitions are deleted but not the subcontractor planned order at the subcontractor side.
Notice that since release SCM 4.0 the parameter 'FAST_DEL' is obsolete and has been replaced with the planning step (Technical Settings tab) End Planning Run after Oder Selection in combination with Do Not Check Order Details.
CTM run time depends on the number of demands. Consequently if your business need for CTM does not require all demands simultaneously, you can perform CTM runs using a demand selection. You can cut down on run time if you can first reduce the amount of demands considered in the planning run.
Another factor to take into account is the planning period set for the CTM profile. You can implement a horizon in the work area which includes only those demands that can be planned during the horizon of the CTM run. That is, exclude any periods containing demands which cannot be planned.
Consider also whether you can meet your business requirements by restricting your demands by product-location. You can experience long run times because in a large supply chain you do not restrict the demands by product-location combination.

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
 04:37:59 optsvr_main.cpp(1363) 'SuperVisor' => Commandline : 4 respected parameters ...
Args:
m0001006
sapgw04
28812935
IDX=1
 04:37:59 optsvr_main.cpp(645) 'SuperVisor' * SAP APO CTM Engine [CTM/ctmsvr]
 04:37:59 optsvr_main.cpp(646) 'SuperVisor' * Copyright u00A9 SAP AG 1993-2009
 04:37:59 optsvr_main.cpp(647) 'SuperVisor' *
 04:37:59 optsvr_main.cpp(648) 'SuperVisor' * Version : 7.0_REL SP05, 407661, Nov 25 2009 22:59:47
 04:37:59 optsvr_main.cpp(649) 'SuperVisor' * Platform : ntamd64/x64
 04:37:59 optsvr_main.cpp(650) 'SuperVisor' * Interface : 2.0
 04:37:59 optsvr_main.cpp(651) 'SuperVisor' * Build date : Nov 25 2009 22:59:47 [1259186387]
 04:37:59 optsvr_main.cpp(652) 'SuperVisor' * Build machine : PWDFM163
 04:37:59 optsvr_main.cpp(653) 'SuperVisor' * Latest change : 407661
 04:37:59 optsvr_main.cpp(654) 'SuperVisor' * NW release : 7100.0.3300.0
 04:37:59 optsvr_main.cpp(655) 'SuperVisor' * Perforce branch: 7.0_REL
 04:37:59 optsvr_main.cpp(656) 'SuperVisor' *
 04:37:59 optsvr_main.cpp(676) 'SuperVisor' * Hostname : m0001006
 04:37:59 optsvr_main.cpp(677) 'SuperVisor' * OS version : 5.2.3790 (WinServer2003, NTAMD64) SP2.0 (Service Pack 2), SERVER ENTERPRISE TERMINAL SINGLEUSERTS
 04:37:59 optsvr_main.cpp(678) 'SuperVisor' * PID : 6768
 04:37:59 optsvr_main.cpp(683) 'SuperVisor' * CWD : D:\usr\sap\SC6\DVEBMGS04\log
 04:37:59 optsvr_main.cpp(684) 'SuperVisor' *
 04:37:59 core_sysinfo.cpp(453) 'SuperVisor' * free disk space: 190433 MB
 04:37:59 core_sysinfo.cpp(454) 'SuperVisor' *
 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' * Memory information:
 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' * physical memory: 10238 MB total, 6511 MB available [63% free]
 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' * page file : 73212 MB total, 60889 MB available [83% free]
 04:37:59 core_sysinfo.cpp(409) 'SuperVisor' * virtual memory : 8388607 MB total, 8388499 MB available [99% free]
 04:37:59 optsvr_main.cpp(693) 'SuperVisor' *
 04:37:59 optsvr_main.cpp(783) 'SuperVisor' * running in invoke mode
 04:37:59 optsvr_rfcconnection.cpp(871) 'MsgMgr' <RFC> RfcPing(RFC_HANDLE=1) received in thread#6912
 04:37:59 optsvr_rfcconnection.cpp(692) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PARAM_SET' for sending of parameters/options
 04:37:59 optsvr_rfcconnection.cpp(703) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PARAM_GET' for receiving of parameters/options
 04:37:59 optsvr_rfcconnection.cpp(712) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PROGRESS' for progress informations
 04:37:59 optsvr_rfcconnection.cpp(721) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_MESSAGE' for messages
 04:37:59 optsvr_rfcconnection.cpp(730) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_RESULT' for (intermediate) result informations
 04:37:59 optsvr_rfcconnection.cpp(739) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_SYSINFO' for system informations
 04:37:59 optsvr_rfcconnection.cpp(748) 'MsgMgr' <RfcConnection> using function module 'RCCF_COMM_PERFINFO' for performance informations
 04:37:59 optsvr_rfcconnection.cpp(1269) 'MsgMgr' <RFC> skipping empty profile value [GENERAL] sPROFILE_CUST_ID
 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
 04:37:59 optsvr_main.cpp(1110) 'SuperVisor' * Starting MainScript ...
 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 **************************** *
 04:37:59 core_msgmgr.cpp(440) 'MsgMgr' * Sending progress number 802 to OutputInterface from []
 04:37:59 core_supervisor.cpp(728) 'SuperVisor' <M> Invoking module 'CTMModelGenerator' [6]->download
 04:37:59 core_msgmgr.cpp(440) 'MsgMgr' * Sending progress number 806 to OutputInterface from [MG]
 04:37:59 ctm_modelgen.cpp(166) 'CTMModelGenerator' ======================================================================
 04:37:59 ctm_modelgen.cpp(167) 'CTMModelGenerator' MG::download
 04:37:59 core_msgmgr.cpp(1110) 'MsgMgr' renaming tracefile
 04:37:59 core_msgmgr.cpp(1111) 'MsgMgr' old name: optsvr_trace20091201_043759_1a70.log
 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
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PRDAT_RFC_READ
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PLPAR_RFC_READ
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_LOC_RFC_READ
 04:37:59 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PPM_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_TRANS_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_RES_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_SSTCK_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_CAL_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_PLPER_RFC_READ
 04:38:02 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_INCMD_RFC_READ
 04:38:03 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
 04:38:03 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_DEM_RFC_READ
 04:38:04 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_SUP_RFC_READ
 04:38:04 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_UCMAP_RFC_READ
 04:38:04 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
 04:38:04 core_msgmgr.cpp(440) 'MsgMgr' * Sending progress number 810 to OutputInterface from [MG]
 04:38:04 ctm_modelgen.cpp(735) 'CTMModelGenerator' MG::download done
 04:38:04 ctm_modelgen.cpp(736) 'CTMModelGenerator' ======================================================================
 04:38:04 core_supervisor.cpp(750) 'SuperVisor' <M> Returning from module 'CTMModelGenerator' [6]->download = success [ctx size : 1]
 04:38:04 core_supervisor.cpp(692) 'SuperVisor' <SCR> Starting script 'CTM Solve' with 9.22337e+012 seconds left
 04:38:04 core_supervisor.cpp(692) 'SuperVisor' <SCR> Starting script 'CTM Match' with 9.22337e+012 seconds left
 04:38:04 ctm_executionmanager.cpp(102) 'SuperVisor' ======================================================================
 04:38:04 ctm_executionmanager.cpp(103) 'SuperVisor' statistics:
 04:38:04 ctm_executionmanager.cpp(104) 'SuperVisor' number of demands: 7
 04:38:04 ctm_executionmanager.cpp(105) 'SuperVisor' ======================================================================
 04:38:04 ctm_executionmanager.cpp(107) 'SuperVisor' ======================================================================
 04:38:04 ctm_executionmanager.cpp(108) 'SuperVisor' parameters:
 04:38:04 ctm_executionmanager.cpp(118) 'SuperVisor' time continuous planning
 04:38:04 ctm_executionmanager.cpp(125) 'SuperVisor' backward scheduling
 04:38:04 ctm_executionmanager.cpp(184) 'SuperVisor' CBCLP enabled
 04:38:04 ctm_executionmanager.cpp(457) 'SuperVisor' ======================================================================
 04:38:04 core_supervisor.cpp(728) 'SuperVisor' <M> Invoking module 'CtmEngine' [7]->run
 04:38:04 ctm_executionmanager.cpp(523) 'SuperVisor' ======================================================================
 04:38:04 ctm_executionmanager.cpp(524) 'SuperVisor' EM::execute for packet 1
 04:38:04 ctm_executionmanager.cpp(1570) 'SuperVisor' EM::execute for packet 1 done
 04:38:04 ctm_executionmanager.cpp(1571) 'SuperVisor' ======================================================================
 04:38:04 core_supervisor.cpp(750) 'SuperVisor' <M> Returning from module 'CtmEngine' [7]->run = success [ctx size : 1]
 04:38:04 core_supervisor.cpp(728) 'SuperVisor' <M> Invoking module 'CTMModelGenerator' [6]->upload
 04:38:04 ctm_modelgen.cpp(1097) 'CTMModelGenerator' ======================================================================
 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
 04:38:05 rfc_connection.cpp(599) 'MsgMgr' <rfc> calling function module /SAPAPO/CTM_INT_STATUS_SET
 04:38:05 optsvr_main.cpp(1166) 'MsgMgr' Current check values:
[CHECK_EQUAL]
[CHECK_UPPERBOUND]
nPEAK_MEMORY_NTAMD64 = 45344
[CHECK_LOWERBOUND]
 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
 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
 04:38:05 optsvr_dsr.cpp(96) 'MsgMgr' <writeDSRdata> tracing not active => no DSR written
 04:38:05 optsvr_main.cpp(1256) 'SuperVisor'
Finished->FAILED ...
 04:38:05 core_memmgr.cpp(564) 'MsgMgr' transferring memory of heap 6912 to main heap
 04:38:05 core_memmgr.cpp(606) 'MsgMgr' finished transfer of heap 6912
 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
 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.

User Exit for Planned Shipment in APO

Hi,
Pls let me know, if you know the user exit which triggers when a planned shipment is deleted in APO.
Thanks,
Kumar

Hi,
You can try the following BAdIs:
You can use the Business Add-In (BAdI) MD_PLDORD_CHANGE to change, before posting, data from planned orders, which have been created, changed, or deleted as a result of planning a material or manual processing.
The Business Add-In allows you to fill and change fields from planned orders in the PLAF table. It also supports filling of customer-specific fields in the customer include CI_PLAFDB.
You can execute the Business Add-In in the planning run in the following areas:
Material requirements planning
Master production planning
Long-term planning
You can also carry out the Business Add-In in all applications, which execute manual planned order changes. Examples of this kind of application are:
The dialog transactions for creating and changing planned orders (MD11, MD12, MS11, MS12)
The Business Application Programming Interfaces (BAPI) for creating and changing planned orders
Regards,
R.Brahmankar

Unable to see planned order in APO

Dear Experts,
I'm creating a Project manufacturing order in ERP. After that I do MRP run in SCM7.0. When I check in Product View (transaction /SAPAPO/RRP3), I do not see any planned order, though I can see orders in ERP (Tcode-md04).
I guess transfer of network to APO is not happening.
Same problem arises when I schedule a dummy project in ERP and after I do MRP run in SCM7.0, I do not see any planned order in planning board.
The MRP run in SCM7.0 shows no error and no warnings and everything appear in green.
I was able to see planned orders in APO before there was system upgrade from SCM 4.2 to SCM 7.0.
Please provide some clue to solve this problem.
Regards,
Jyoti

Hi Jyoti,
There will be an "Iterate" button on the left hand corner in the result display of CCR. Please click on this button so that these errors will get iterated and goes to the respective distinations. After this, you go to smq1 and smq2 trasnaction codes of R/3 and clear all the queues. Similarly you clear the queues in smq1 and smq2 transaction codes of APO. Afterwards, check whether you are able to see the planned order.
Please confirm
Regards
R. Senthil mareeswaran.

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

Error while production planning run

Hi,
I got this error "No gap for activity ||| found within the planning horizon" during production planning run.
Diagnosis
    There is not a large enough gap for the activity ||| on the mode
    1- in the planning period specified in the time profile.
System Response
    The system does not schedule or reschedule.
What could be the reason for this error ? Kindly help.

Hi,
   One reason could be the Time Bucket.
Please check your time series assigned for production planning run.
Check the PPMs and maintain the scheduling data .
Please let me know that whether you have transferred the data from R/3(Materials, WorkCenters, BOMs,PPMs) or you are doing manually in APO.
Let me know then i can tell you the right approach.
Regards,
Santosh

CTM Planning run Error

Hello,
I tried to execute CTM planning run, it prompts me with this error message.
"Check the settings in SAP APO Customizing for the optimization server."
I already assigned "CM01" as Optimization Server Id in CTM Profile, but it still prompts the error message.
Does anyone encountered this error ?
Thanks in advance.
D'Gee

Please go through Note 886103 - System Landscape Copy for SAP SCM and make sure you did right settings .
Manish

How do I maintain storage location for Planned Orders in APO

Dear all,
Can you help us in maintaining storage location for planned orders in APO. The storage location from material master need to be updated in product master of APO and the same shall be automatically picked from product master during Supply Network Planning run.
Material master CIF is live.
We have got the following content error in CIF consistency check. How ever this is nt goging to harm any thing, but we would like to maintain in both R/3 and APO.
Error:
Plant and storage location in SAP APO: 2004
Plant and storage location in SAP R/3: 2004 FGPA
Thanks in advance
Ram Mohan Rao Kolanupaka

Instead of maintaining additional master data, i would rather use CCR user exits to switch off comparison of planned order at storage location level if the APO storage location is blank. This way you would not have to make changes to PPMs everytime a new scale out of the solution happens.
In SE18 check the user exit /SAPAPO/CIF_DELTA3 (interface RELEVANT_FOR_COMPARE_ORDHEAD)
If it is not possible to switch off this comparison then I guess changing master data is the next step. Do explore with a developer though about the first option.

Characteric change in SO and corresponding planned order in APO

Hello Experts,
In a CDP enviornment i have a scenario where a characteristic value is changed in SO. The new values is visble in APO SO and the corresponding Planned order characteristic value is also changed with regenerative plan.
Is there way where any change in SO characteristics would reflect in Firmed Planned Order(F) also which already exists against the SO in APO
Regards
Alin

To have a UK app store account you need a bank card from a UK bank with a verifiable UK billing address
What the heck is this for a weird rule ?????
Since 2 weeks I have an iMac 27" i5. Some days ago I tried to download Sketchbook Express. But it seems that if you download for the first time something you have to give your billing address and creditcard data.
Since more than a year I live in Romania, but my home country is Holland. There I have my bank account, because my pension is paid there and from there is my creditcard. But it is controllable a valid card.
To buy my iMac with this card in Romania was no problem !! But to download F R E E software is not possible with this card.
Another annoying point: As soon as you as you fill in your billing address, they change the language in the language of your billing address. I think it would be more polite if they asked you if you want to change the language.

PPDS Planning run

Hi Gurus,
I had created in APO for my test planning run
1. Location
2. Products
3. Resources
4. PPMs
5. Stratergic profiles
I had run my heuristic plan in rrp3 at finished product level, it had generated planned orders.
My question is what about my SF( semi finished products) and raw materials requirements?
Do i need to run even for SF and Raw materails?
Please let me know if had done anything wrong
Please any one can help me giving step by steps how we need to configure Detail scheduling with finit planning run?
Thanks & Regards,
Kumar

Hi,
You can plan Finished Goods (FG's), SFG's and RM's in APO and PP/DS. Of course, typically you only want to plan critical materials in APO that are constrained and have long lead times / expensive.
The following are the steps that you can try to run planning run including all FG's, SFG's and RM's.
Identify PP/DS heuristic that best meets your planning planning needs.
Use transaction code /SAPAPO/CDPSB0 (Planning run in foreground) or /SAPAPO/CDPSB1 (Production Planning run in the Background) to run planning for all the products in a single shot i.e. FG's, SFG's, RM's
In the first step, run low-level code heuristic before you run actual planning run heuristic. Low-level code will determine the lowest level a product will appear in all the PPM's in a given location. For example, if an SFG is appearing in the 1nd level in one BOM and same SFG is appearing in 2nd level in another BOM, then low-level code for this SFG is 2 (Low level code for a finished good is 0). Once low-level code heuristic is run, you can evaluate the results in transaction code /SAPAPO/RRP_NETCH and see if low-level codes are calculated correctly. Low-level codes will ensure the planning run happened in the sequence FG's planning first <followed by> SFG's planned next <followed by> RM's i.e. system runs planning for low-level code '0' products first <followed by> low level code '1' products <followed by> low level code '2' and so on......ok...that's enough on low-level codes.
In the second step in the planning run, use the heuristic that you want to run for planning all FG's, SFG's & RM's and include all products together in the selection criteria. No need to split and create selections for FG's planning run in to one step, SFG's in to next step and RM's in to another step. All can be included in one step and the low-level code will ensure the planning happened in sequence.
In case, if you run planning run for one FG product in it's Product View and you want the dependent requirements to be covered immediately i.e. dependent planned order's created immediately, use the "planning procedure = 3 cover dependent requirements immediately" in the PP/DS tab of product master for SFG's and RM's. This will ensure that as soon as the system see's dependent demands for SFG's and RM's, it will immediately create planned orders to cover them. This planning procedure is typically used to meet 'CTP' (Capability to Promise) requirement.
Low-level code heuristic - SAP_PP_020 (Stage-Numbering Algorithm)
MRP Planning run - SAP_MRP_002 (Product Planning (Plan Comp. Immdiately)
Good luck.

Planning in planning run procedure doubt

Hi All,
I am new to APO i have a doubt for planning in planning run procedure.
I was going through the SCM250 PP/DS and i found this in the book for planning in planning run procedure
"You use this setting, for example, if you do not want to trigger production from the
ATP check in the CTP scenario for this product"
I lost in this.
Can some one please elaborate the meaning for above it would be highly appreciable?
Thanks
Shaiil

Shaiil,
In APO PP, there is bit of Master Data called "Planning Procedure". Planning Procedure can influence when planning is done. You can trigger a heuristic to be executed automatically, based on defined events. One of the events that can trigger an automatic heuristic is an ATP check Planning Procedures can be assigned to a Product in the Product Master.
Planning Procedure
http://help.sap.com/saphelp_scm70/helpdata/EN/64/dca63be2bc331be10000000a114084/frameset.htm
In APO, there is a specialized type of availability check (ATP) which is called Capable To Promise (CTP). In CTP, it is common to assign a Planning Procedure that immediately covers dependent requirements. This means that upon ATP, the system will generally automatically create a planned order, schedule it, and generate dependent demand.
Capable To Promise
http://help.sap.com/saphelp_scm70/helpdata/EN/4c/56297de7c33a0de10000000a42189c/frameset.htm
These types of automatic planning are totally separate from a planning run. It is possible to run a product line with only automatic planning, only planning run planning, or various combinations of both types of planning.
If you wish to learn about APO, you should first search through online help before posting a question.
Best Regards,
DB49

Regenerative planning run in APO

Similar Messages

Maybe you are looking for