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.

Similar Messages

How to "roll back" SAP APO PPDS planning batch run from infeasible batch mid-point to before start of planning batch run?

Hi Experts,
We are investigating if any SAP customer that implemented SAP APO PPDS has ever attempted to establish a "roll back" of the SAP APO PPDS created supply plan to a defined point before the start of the SAP APO PPDS planning batch run?
We have a situation where - in the middle of the planning batch run - randomly or intermittent the batch run hangs or runs a step for multiple hours that normally, at most days, takes only a few minutes to run. In a situation like this, the supply plan is not in a state where customer sales orders can be promised (using GATP CTP) or planned orders can be converted to production orders and published to SAP ECC, etc since the plan may be capacity infeasible or simply partial or incomplete.   To not hold the business operations hostage to wait resuming operations (promise customer sales orders, convert and release and execute orders to transfer, deliver, produce, or purchase) for hours or days, we need to find a way back to the original plan right before the nightly PPDS batch planning job started.
We already close all the queues from ECC to APO, thus, no CIF traffic from ECC to APO. We also shut down the customer sales order feed into ECC as normal process for duration of the APO PPDS batch planning run. Thus, functionally, we are theoretically in a situation to simply go back to a PPDS and active planning version save prior to the run. Yet, many more technical and BASIS-related questions remain on how to roll back to a state where the plan was not compromised.
This inquiry is to learn if any other SAP customer has ever established a process to roll back SAP APO PPDS to a previous point in time supply plan to resume operations? Whatever the reasons are, be it after a failed batch run, or any time during the normal interactive plan day.
Additional information about our design and plan:
1. We have a two year horizon supply plan in PPDS
2. We only publish to ECC 14 days worth of planned orders, stock transfer requirements, and purchase requirements
3. We convert planned orders to production orders and release production orders in ECC 2 days before first operation starts
4. We convert PR's to PO's and STR's to STO's in ECC 2 days before execution (ship or submit to vendor)
Any indication where a SAP customer has developed and uses a process to roll back an SAP APO PPDS- planned supply plan to an earlier point in time or version would be helpful to know.
Regards,
Manimaran M.

Hi Manimaran,
Saving in Simulation means in DS board when you click on save it provides you option to save sim version or adopt to active version. If you copy to inactive version you cannot copy back trasaction data specially PPDs orders back to active version again while if you save in simulation you can adope it to active version at any point of time. YOu can adopt simulation version changes to active version using T-code /SAPAPO/CDPSS0
Copying to active version means you copy data from version 000 to some other active version while here results are kept simulation,

How to change characteristics values in PPDS planned order?

Hi,
I have few PPDS planned orders. I want to change the value of few characteristics of existing PPDS planned order.
How can I do the same?
Any standard T.Code or function module or report available to update the characteristics values of PPDS planned order in APO.
Thanks in advance.
Warm Regards,
Surajit Das

Hi Surajit,
Char can be changed programatically.
If you want to change the Planned Order characteritics before its creation, you can do so at the time Planning run itself (/SAPAPO/RRP3) in BADI /SAPAPO/RRP_SRC_EXIT, Method RRP_USEX_PLORD_CREATE.
Planned Order characteritics can be changed after it creation.using BAPI BAPI_MOSRVAPS_SAVEMULTI3.

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

Plor not generated for components during Heuristic planning run

Hi experts,
i had run planning run PP_02 run in PPDS and i am able to see dependent requirment for componenets but my question is its not generating planned order for my components. Please let me know if i had missed any config.
Second point is i am planning to run 1. Infinit planning runa nd then finit planning run ( PP-02 and MRP_02).please suggest.
Third is when i run planning run (Product heuristic its giving me an error saying it space constrains.Please suugest me.
Thanks
Raj

Hi,
With the heuristics SAP_MRP_002: Product planning (plan comp. immediately) , components that are defined as being planned automatically and immediately are planned using a simple lot-sizing heuristic.
SAP_PP_001 is for Changing orders manually. Better choice may be to use SAP_PP_002: Planning standard lots. We use this heuristic to create new receipt elements in order to cover product requirements
regards
Datta

SNP and PPDS planning horizons

Hai,
        I am reading through SNP and PP/DS planning horizons. I understand that SNP doesnot plan anything within SNP production horizon whereas PP/DS plans only within the PP/DS horizon.
Now, I get confused when trying to understand the following sentences:
1. If production horizon of SNP is smaller than the PP/DS horizon, the planning horizons of SNP and PP/DS overlap with each other. In this horizon, SNP determines the receipts with most cost-effective sources of supply and lot sizes and PP/DS plans the receipts in more detail.
2. If requirements within the SNP production horizon cannot be covered by PP/DS, then SNP plans the receipt outside the SNP production horizon(this corresponds to the logic in the PP/DS planning time fence in short term planning).
3. If the PP/DS horizon in the product master is set to be greater than SNP production horizon, this gives rise to an overlapping area in both SNP and PP/DS receipts are created.
Can anyone please help me undestand the above? An example or somedocumentation reference is appreciated.
Thank you.

Hi Visu,
Good question. You missed Planning Time Fence in the equation.
|--||--
>
1.       PTF             SNP            PPDS
You execute PPDS Heuristic (Product Heuristic) then requirements upto PPDS horizon will be covered by receipt elements (beyond Planning Time Fence). If you run SNP Heuristic then receipt elements will be created from SNP Horizon out in future deleting the receipt elements created by the previous PPDS run. But note that while PPDS planning is down to the second level SNP planning is minimum at a day level. If you have weekly buckets then all requirements for one week will be clubbed and single receipt element will get created. However you can consider SNP orders as fixed during PPDS Net Requirement Calculation through appropriate development.
|--||--
>
       PTF              PPDS           SNP
2. This is also not clear to me as I cannot build the scenario as described. The above diagram is the closest I could come up with. But in this case if you run SNP Heuristic and there are unmet requirements (sitting between PPDS and SNP horizon) then the receipt for that will be created only at the start of the SNP Horizon.
3. This is correct but already explained in 1.
Hope this clarifies or at least does not add to the confusion. BTW if you are interested then please read OSS Note 481906 - SNP - PP/DS integration (documentation).
Thanks,
Somnath

Bapi for sfg dependent dem,snp planned order qty, and ppds planned orde qty

Hi Gurus,
I am not much familiar with APO, so please help me,
Input details:
Field                         Value
Planning Version     000
Source Location *     1001     Single/Multi Value
Product *                          1000061     Single/Multi Value
Production Planner *     PRC     Single/Multi Value
Start Date *
End Date *
o/p:
Source Location     Date     Semi-Finished Material     Material Description     SFG Dependent Demand     SNP Planned Orders qty     PPDS Planned order Qty     Total SFG Variance due to Lot size     Total SFG Variance reference to dependent demand
1001     15-Jul-10     1000041PP     PRIMARY FF MILK 3% FAT     340     412     420     8     80
1001     15-Jul-10     1000041PP     PRIMARY FF MILK 3% FAT
1001     15-Jul-10     1000041PP     PRIMARY FF MILK 3% FAT
Is there any bapi to fetch the data as shown in o/p.
Thanks

Hi Phani,
Tryout the below BAPIs
IF10503 (object)
BUS10503
Regards
R. Senthil Mareeswaran.

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
 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.

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

PPDS Planning run

Similar Messages

Maybe you are looking for