Forecast Inconsistency

Hi All,
I have sme problems with forecast. I can see foreacast for some materials in Planning book ( /SAPAPO/SDP94), but I can't see them in Product View- Forecast Tab ( /SAPAPO/RRP3).
Moreover, I have set backward comsumption for 30 days and still SOs are not consuming forecast>
We had thsi problem earlier, but that time we deleted the Forecast and Rerun the Univariant Forecast.
What could be the rootcause for this?
Thanks ..
Denish

Hi Denish,
1) Try running /SAPAPO/TSCONS to check any inconsistencies
2) Check whether sales order integration models are available to
bring up sales orders into APO for consumption
3) Check whether the sales order data key figures are maintained
correctly. (category, category group etc.,)
Regards
R. Senthil Mareeswaran.

Similar Messages

Depreciation forecast after Asset revalution with AR29N inconsistent

There is a need to revalue assets on a certain date in the current
fiscal year. We did all the steps necessary to carry out revaluation
using Transaction AR29N, using the "new valuation of an asset"
function. After the reval the asset master was updated with the new Depreciation key and new useful life/dep start date.
SAP calculated the forecasted depreciation incorrectly in the
first few attempts, but after some testing it worked fine and we posted
periodic depreciation. This worked as expected. Using the same settings
in the same company code a new asset was revalued with a new value
date. The problem has returned although nothing was changed in the
system, The fore casted depreciation does not make sense.
Examples:
1. Asset Original Value at FY start - $100 with a planned dep of $1 for
the remaining useful life. Depreciation for 4th FP posted. Asset revalued
with a value date corresponding to FYP 04/2011. Revalued at $1200 with
new useful life of 24 months and new Dep start date corresponding to
start FYP 03. Expected depreciation PM is $50. This scenarion worked
fine.
2. Asset Original Value at FY start - $100 with a planned dep of $1 for
the remaining useful life. Depreciation for 4 FP posted. Asset revalued
with a value date corresponding to FYP 05/2011. Revalued at $2400 with
new useful life of 24 months and new Dep start date corresponding to
start FYP 03. Expected depreciation PM is $100. SAP shows forecasted
monthly depreciation of $108 per month

Hi Manish,
Are revaluated values appearing correctly in asset explorer (AW01N) both APC and depreciation.
If no then I would suggest to run AFAR for recalculate depreciation.
Thanks!!!
Murlidhar Khatri

Forecast accuracy and Inconsistency check reports in APO-BW

Hi Guru's,
Can some of you provide some info on How I can go ahead with Forecast accuracy report to compare actulas and planned versions . This info we have to receive from APO demand planner . What shold I consider befroe proceeding to these reports . How can I generate data sources and transfer into BW .
Any useful docs please send to [email protected] .
Thanks ,
Ananth.

Hi Ananth,
Check Business content Query -
http://help.sap.com/saphelp_nw04s/helpdata/en/43/25b2946b3e0d24e10000000a1553f7/frameset.htm
and other available query, if you find some thing relevant, activate the relevant objects and start extracting data.
hope it helps
Regards
Vikash<a href="http://http://help.sap.com/saphelp_nw04s/helpdata/en/43/25b2946b3e0d24e10000000a1553f7/frameset.htm">http://http://help.sap.com/saphelp_nw04s/helpdata/en/43/25b2946b3e0d24e10000000a1553f7/frameset.htm</a>

CBF: Inconsistency with the forecast in charactetistics values level

Hi Guys:
I`m working with CBF, trying to make prototype, and the main problem than I have is when I release the forecast, and I check the forecast for each characteristics values, I've obtained the same forecast for different characteristics values.
EXAMPLE:
HISTORY
CH color:
V1    x
V2    y
FORECAST
CH color
V1    q
V2    q
So my question is how can I get a forecast in characteristics values level correctly?
What sould be wrong?
Thnx so much!!!
Rgds
Felipe
Edited by: felipe seydewitz on Jan 9, 2008 12:40 PM

Hi,
Have u put demand mannually at aggregated level? or Did u take forecast run at aggregated level?If u did forcast run at aggregated level,then u should have proportional factor to disaagregated at detailed level or u should take forecast run at V1, V2 level.So that u will find the difference in two Characteristic values.
Actully,currently i am working on same scenariao i.e. CBF for one STEEL PLANT.eventhough i through with CBF,means 95 % work is over,but 5 % left becz prob. with some characteristics.
Just go through following scenario...
Actually i have done the setting related to CBF in R/3 as well as in APO.We have one material having one class & some characteristic s with some dependancies.In that class i have added two more characteristic which is i have created.Eventhoug that 2 char. also having some dependencies.
Now,scenario is that whenever i am using my characteristic for CBF,then forecasting consumption is happening,but whenever i am using other characteristic for CBF,forecasting consumption not happenning.
So,have u done all CBF configuration & Do u know the solution for this issue? Kindly check this issue & let me know pls..I would really appreciate you regarding the same.
Thanks & Regards'
Sujay Joshi

Inconsistent forecast consumption in APO and R/3

Hi Experts,
We have a couple of issues with consumption in our system.
We have a situation where APO is showing us consumption in the /SAPAPO/DMP1 view but no consumption showing in the planning books and the RRP3 requirements screen. Interestingly, when we go and change the sales order in R/3, the consumption then gets triggered in APO. So there seems to be some kind of delay and the consumption seems to be lagging a step behind or somehow a trigger isnt hapenning first time around.
The other is more a question...
If you do the F1 help on Fwd consumption in APO and R/3, it tells us that in R/3 consumption is based on workdays as defined by the factory calendar whereas in APO, it talks about consumption considering calendar days and not workdays and that its not possible to define a calendar to make it work with workdays.
We have fwd consumption set to 2 days and we have noticed that if e.g the order comes on a Friday, consumption gets lost due to the following two days being Saturday and Sunday. Whereas in R/3 it jumps forward and consumes Monday and Tuesday and ignores Satuday and Sunday (We are using 5day calendars). This is causing a big headache and consumption is all over the place.
any ideas?

OK, I have found the solution to half the problem. It was a system bug and the last sales order wasnt being consumed and there is already a note out for that.
Still confused about the workday vs calendar day issue in R/3 and APO. How do we align the two systems and get the consumption happening in APO for 5 days and not 7 days?
Regards,
Usman

Error logs in job releases forecast from DP to SNP-"Matl does not exist"

Hi Everyone,
I am facing error logs in the batch job which releases forecast from DP to SNP
Forecast release job - Weekly - Through background job
Forecast category - FA
Error 1: - Characteristic combination appears on batch job log with an error that
"GMC does not exist " Even though it exist in R/3 and APO
All products with error message "Product does not exist" from do exist and have Forecast in Product View
Error 2: - Deleted KCC keep showing up on the Demand Forecast release job log as errors even though they are invalid KCC and were deleted previously. How do they get removed from error log so they don't get created again
Material does not exist on the APO Product Master, in R3 there is a delete flag and the MRP type is set to X1 ,it does not exist in the APO Product Master and does not exist in R3.
Request you to kindly provide any way forward which may be causing error logs of the job
Thanks in advance,
Mrigendra Sharma

Hi Mrigendra,
Please re-initialize the SNP planning area (program : /SAPAPO/TS_PAREA_INITIALIZE) and then check the consistency by executing the program: /SAPAPO/TS_LCM_CONS_CHECK. If you observe any inconsistency in the log/spool, then re-run the program: /SAPAPO/TS_LCM_CONS_CHECK to observe all green.
It is recommended to run the consistency program after any master data change. The initialization program should be run at least weekly.
Try transfering the data again from DP to SNP to see if the error reappear.
Hope this helps.
Regards,
Nawanit

PWA 2013 "Add a new task" - inconsistent task insertion behavior

Hi all!
New to the forum and wondering if anyone out there has insight into what I've encountered with the "Add a new task" feature in on-prem Project Server 2013.
First some context... I am setting up 12-month projects for different teams to forecast and log their administrative and reactive time for the year.
We are tracking this within enterprise projects. The projects have a series of summary tasks that serve to categorize work. There is a placeholder task within each summary task that establishes duration and where we may assign generic resources
to establish a baseline cost for the 12 month period for that category of work. The vision is for team members to go to their PWA Tasks list, "Add a new task", select the project and the summary task to categorize and add their new task to
the project, enter the task information, and submit for approval.
My issue appears when the Project Manager approves a task and opens the project in Project Professional because the system appears to exhibit inconsistent
behavior - Scenario 1 vs Scenario 2 below.
Scenario 1 – Project structure prior
to adding a new task:
Project Summary Task, 260d
-Summary Task, 260d
--Placeholder Task, 260d, generic resources assigned, ID=n
-Summary Task, 260d
Team member adds a new task and submits. The new task is inserted as a child task to the summary task selected when adding
the new task. This is what PWA Approval Preview shows and what is found when file is opened in Project Professional:
Project Summary Task, 260d?
-Summary Task, 260d?
--New task just added, 2d?, named resource assigned, ID=n
--Placeholder Task, 260d, generic resources assigned, ID=n+1
-Summary Task, 260d
Scenario 2 – Same project structure as scenario 1... team member submits a new task
and the new task is inserted per below. This is NOT what PWA Approval Preview shows. PWA shows the new task as a child of the summary task. Once approved and the file is opened in Project Professional, the task instead reflects as a child
task to the placeholder task, and impacts the duration of the original summary task:
Project Summary Task, 260d?
-Summary Task, 2d?
--Placeholder Task, 2d?, generic resource assignments, ID=n
---New task just added, 2d?, named resource assigned, ID=n+1
-Summary Task, 260d
I am using separate project files to produce the scenario, and as far as I can tell they are set up exactly the same, but one file consistently produces
scenario 2 behavior and the other consistently produces scenario 1 behavior. It seems that something is different between the two files and causing the issue, but I can't figure out what it is.
Any idea what I could do to establish consistent (preferably Scenario 1) task insertion behavior from PWA?

Anyone else running into this? We're now on the April CU and still experiencing this apparent bug. I've replicated it in different PWA instances using "Add a new task" from both the timesheet and tasks.
It only happens on certain projects as Greg mentioned... One way we've been able to pinpoint where it's taking place: since the bug causes a task to become a summary task, and since most of our tasks have assignments, if a project contains any summary
tasks with assignments, those may be an early indicator of the bug (after we rule out PM-induced summary task assignments).
We're seeing this impact our project actuals and reports, so there is a fair amount of going back through approval history and restoring actual hours to the correct calendar dates in the Project Client. Not ideal, because we are planning to lock that
capability down in the near future.
On a whim, I tried using the "Save for sharing" method to fix the issue, and new tasks appeared to insert correctly after that. Seems OK for a workaround (we'll see how durable it is), but better yet would be consistent new task insertion
behavior.

OPEN_INTERFACE_REJECTS- INCONSISTENT SUPPL SITE

Payables Open Interface Import program is throwing INCONSISTENT SUPPL SITE, when a third party vendor site code and third party vendor site id is passed along with matching PO number for creating an invoice for third party vendor site.
Can any one let me know, how to resolve this issue.
Thanks in advance

Hi,
this could be due to passing values which are not correct for the vendor_site_id field ....do compare this transaction with other transactions that are imported successfully past, so that we can narrow down on the data which is different ...
Reference:
Expense Report Export Rejects Expense Reports With 'Supplier Site Id And Supplier Site Code Do Not Match' [ID 1408830.1]
Regards,
Ivruksha

About selecting Scheduling Agreement and Forecast delivery schedule

Hi Experts,
i want to write a Report, with 2 parameters for the selection : Sold-to-party and Period
For this Sold-to-party/Period, I want to list all scheduling agreement + Forecast delivery schedule.
I already found the Function SD_VBEP_READ_WITH_VBELN to read all Forecast delivery schedule lines using Sales Doc.No. , but how can I select all Scheduling Agreement for the Period ?
Regards,
David

Solution:
by selecting data from table VEPVG (Delivery Due Index) and using function SD_VBEP_READ_WITH_VBELN for each SD Document.
Regards,
David

Can Demantra Forecast at a National level?

Good afternoon Forum,
I posted a thread about a month ago and am back again to hear some more good advice and information. I work in a business group which supplies spare parts nationally through regional distribution centers for a large industrial equipment installed base. Despite me being against this, our management has decided to use Demantra to forecast parts usage at the National level and then force down to the regional distribution centers to take a percentage of parts based on past percentage of the total, rather than roll up the individual regional forecasts to create a total.
My question is can Demantra be set to do this? What would it take? Besides being less accurate at a regional level, what other drawbacks are there?
Thanks in advance for any assistance you can provide.
Best regards,
ABoyNamedJoe

Hi Maggie,
To solve the proble, I think the best way is to create something like dummy entity, which is usually called adjustment entity as Alwin mentions.
Please remember not making any child entity of the adjustment entity. Otherwise, the adjustment entity won't be base-level member anymore, and you can not post data.
Hope it helps.
Atsushi

Creation of forecast delivery in Sceduling agreement

Hi experts,
I would like to know if it is possible to create a forecast delivery line in scheduling agreement using IDOCs. The scheduling agreement is already existing but it has no forecast delivery line. If it is possible, kindly give me the basic type, message type and the fields to be populated with what data.
Thanks in advance,
Lalyn

The actual scenarois is this:
I am getting AUFNR(prodcutoin order),LGNUM(whs number) ....etc from XI system. I hav to use this data and have to create an Inbound delivery from expected GR in EWM and POST GR in EWM and Creation of Whs task in EWM again.
The transaction to create the inbound delivery from expected GR is /SCWM/GRPI (GR Preparation: From Production).
we do not have any BAPI or FM in EWM to acheive this. Pleas help me in resolving the issue.

Can't See Historical Forecast in SPP

Hi
We have loaded the sales order data using a flat file.We were able to load the data into the cube 9ADEMAND (but not into the ODS 9ARAWDAT).
We are also able to see the demand data in the forecasting planning book and even forecast is also getting generated.
The problems which we are facing are
1. Standard Deviation of Demand, MAD etc are all 0.
2. Not able to see Historical Forecast ( tcode /SAPAPO/SPPFCSTTARK) . The error message says " No historical forecast time series can be determined".
Can anybody tell us what could be the problem ?
Thanks in Advance
Mitesh

We are having a similar issue, could you provide the configuration done to the planning profile for recalculation of historical forecast?

SAP System inconsistency for Inbound delivery / MIGO and a "sap note"

Hello Friends ,
After following SAP instruction on how to remove the inconsistency between posting GR through MIGO (Inv. mang.) and the reflection of the goods movement status in the inbound delivery document - done that using sap note 570991
the problem is that the system start behaving in a weird way throwing unjustified Error messages for any suggested goods receipt using MIGO with reference to inbound
for example after creating an inbound delivery document and trying to post it via migo , an error will pop up
- Inbound delivery storage location cannot be changed to here Message no. VLA316
the thing is i didn't even maintain any storage location entry up to that point and yet i cannot post any stock !!
also another error like
- Inbound delivery batch cannot be changed to *** here
which doesn't make any sense because there is not batches in the inbound document !!
i think this behavior is coming from the "Document Flow Update for Stock Postings" inbound indicator at the shipping parameter at client level customization
i need help on how to overcome this annoying SAP Bug/Problem specially i am in a post go live critical situation

Hi,
The messages you mentioned were introduced to avoid inconsistency between inbound delivery and IM, through the note: 1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
If the messages are issued incorrectly, then you may check for SAP notes (I couldnt find anything relevant) or raise an OSS ticket to SAP.
Regards,
AKPT

Inconsistency between catalog authoring tool & Search engine

Hi,
We are on CCM2.0 and SRM5.0 with catalog deployment in the same client as SRM.
In our implementation we are using master catalog and product catalog. We have very recently deleted around 65 items from our product catalog which is mapped to mater catalog and hence those 65 items are not found anymore in master catalog in CAT (Catalog authoring tool).
This master catalog when published, we expect that these 65 products should not be available for end users.
But end users can still see the deleted items through CSE (Catalog search engine). Thus there is data inconsistency between CAT & CSE.
Has anyone faced similar issue before if yes can you please share the same with us.
Edited by: Manoj Surve on Mar 24, 2009 7:05 AM

Run TCODE SE38 program /CCM/CLEANUP_MAPPING to look for errors/orphaned records in test mode.
If you want to clear out orphaned records uncheck the Test Mode but:
Warning: This program can slow down a production system as it clears out the memory buffers for user catalog searches and these have to be built up again by the users doing searches. This can be hours to days depending upon the size of your system and the number of users.
In Dev or UAt no problem.
Hope this helps?
Regards
Allen

Inconsistency between get-childitem -include and -exclude parameters

Hi,
Powershell 2.0
Does anyone else consider this a minor design bug in the Get-ChildItem command?
# create dummy files
"a","b","c" | % {$null | out-file "c:\temp\$_.txt"}
# this "fails", returns nothing
get-childitem c:\temp -include a*,b*
# this "works", returns desired files
get-childitem c:\temp\* -include a*,b*
# this "works", excludes undesired files
get-childitem c:\temp -exclude a*,b*
# this "fails", excludes undesired files BUT RECURSES sub-directories
get-childitem c:\temp\* -exclude a*,b*
I'm writing a wrapper script around the GCI cmdlet, but the inconsistency between the two parameters is problematic. My end user will surely just type a path for the path parameter, then wonder why -include returned nothing. I can't unconditionally
add an asterisk to the path parameter, since that messes up the exclude output.
I'm just wondering why Microsoft didn't make the parameter interaction consistent???
# includes desired files in the specified path
get-childitem -path c:\temp -include a*,b*
# excludes undesired files in the specified path
get-childitem -path c:\temp -exclude a*,b*
# combine both options
get-childitem -path c:\temp -include a*,b* -exclude *.log,*.tmp
# same as above, the asterisk doesn't matter
get-childitem -path c:\temp\* -include a*,b*
get-childitem -path c:\temp\* -exclude a*,b*
get-childitem -path c:\temp\* -include a*,b* -exclude *.log,*.tmp
# same as above, but explicitly recurse if that's what you want
get-childitem -path c:\temp\* -include a*,b* -recurse
get-childitem -path c:\temp\* -exclude a*,b* -recurse
get-childitem -path c:\temp\* -include a*,b* -exclude *.log,*tmp -recurse
If I execute the "naked" get-childitem command, the asterisk doesn't matter...
# same results
get-childitem c:\temp
get-chileitem c:\temp\*
If this isn't considered a bug, can you explain why the inconsistency between the two parameters when combined with the -path parameter?
Thanks,
Scott

The Get-ChildItem cmdlet syntax is horrific for advanced use. It's not a bug in the classic sense, so you shouldn't call it that. However, feel free to call it awful, ugly, disastrous, or any other deprecatory adjective you like - it really is
nasty.
Get-ChildItem's unusual behavior is rooted in one of the more 'intense' dialogues between developers and users in the beta period. Here's how I recall it working out; some details are a bit fuzzy for me at this point.
Get-ChildItem's original design was as a tool for enumerating items in a namespace -
similar to but not equivalent to dir and
ls. The syntax and usage was going to conform to standard PowerShell (Monad at the time) guidelines.
In a nutshell, what this means is that the Path parameter would have truly just meant Path - it would not have been usable as a combination path specification and result filter, which it is now. In other words
(1) dir c:\temp
means you wanted to return children of the container c:\temp
(2) dir c:\temp\*
means you wanted to return children of all containers inside
c:\temp. With (2), you would never get c:\tmp\a.txt returned, since a.txt is not a container.
There are reasons that this was a good idea. The parameter names and filtering behavior was consistent with the evolving PowerShell design standards, and best of all the tool would be straightforward to stub in for use by namespace
providers consistently.
However, this produced a lot of heated discussion. A rational, orthogonal tool would not allow the convenience we get with the dir command for doing things like this:
(3) dir c:\tmp\a*.txt
Possibly more important was the "crash" factor. It's so instinctive for admins to do things like (3) that our fingers do the typing when we list directories, and the instant failure or worse, weird, dissonant output we would get with a more pure Path
parameter is exactly like slamming into a brick wall.
At this point, I get a little fuzzy about the details, but I believe the Get-ChildItem syntax was settled on as a compromise that wouldn't derail people expecting files when they do (3), but would still allow more complex use. I think that this
is done essentially by treating all files as though they are containers for themselves. This saves a lot of pain in basic use, but introduces other pain for advanced use.
This may shed some light on why the tool is a bit twisted, but it doesn't do a lot to help with your particular wrapping problem. You'll almost certainly need to do some more complicated things in attempting to wrap up Get-ChildItem. Can you describe some
details of what your intent is with the wrapper? What kind of searches by what kind of users, maybe? With those details, it's likely people can point out some specific approaches that can give more consistent results.

Forecast Inconsistency

Similar Messages

Maybe you are looking for