APO DP Forecast profile consistency check

I am using APO DP V5.
Has anyone any experience of using the 'forecast profile consistency check' pgm /sapapo/rmdp_fcst_prpfl_consis?
What exactly does it do?
Thanks,
Bob Austin, Atos Origin

Hello,
This report /SAPAPO/RMDP_FCST_PRPFL_CONSIS is consistency for forecast profiles
While there is no need to schedule the report automatically at regular intervals, there are some special situations in which it can be very useful.
When must this report be run?
1. When you transport forecast profiles from a system A to a system B. In this case, you must convert the internal version indicator (Id).
2. If you are having problems with the date display or if the system changes from the relative date specification to the absolute specification for no obvious reason.
When should you run this report?
1. If you are working with generated forecast profiles (user parameter /SAPAPO/FCST_GUIDS).
2. If you are using a manual forecast.
What exactly does this report do?
1. The internal version ID is checked.
2. Date fields are checked. Fields filled with 00000000 are initialized.
3. Overall profiles without any single profiles are deleted.
4. Generated forecast profiles that are no longer assigned to a selection are deleted.
5. The assignment of forecast profiles to a selection is deleted if the forecast profile no longer exists.
6. Parameters for the manual forecast are deleted for any forecast profiles that no longer exist.
Source of above details : Note 558995 - Advice on consistency report for forecast profiles

Similar Messages

Profile consistency check when operation mode change

If the number of work processes in the profiles is changed, the system can no longer switch operation modes until after a restart of the instance. It's therefore necessary to adjust the configuration of the operation modes after a change to the profiles.
In above paragraph, I don't understand why the system can not switch mode if the number of wp in profile is changed? Does system will compare wp number in profile with currently running wp number before the operation mode switch? Please advise.
Thanks.
James

Yes, I can understand it, when the number of work processes is changed, we need redefine the operation mode.
But I am confused this sentence "If the number of work processes in the profiles is changed, the system can no longer switch operation modes until after a restart of the instance. "
After the number of work processes in profile is changed, I think it will not impact instance immediately until restart the instance. According to this sentence, it seems when I change the parameter in profile, it impacts the instance immediately and the system can not switch operation mode right now if we don't restart the instance. Is it reasonable? And I think the operation mode still need redefine even if we restart the instance, since scenario in Ralph's description. Is my thought right?
Thanks so much.
James

APO DP - loading of selections and forecast profiles assigned to selections

I am using APO DP V5.
I am forecasting at a 'product at customer' level.
I have a flat file containing the 'product at customer' combinations - of which there are several thousand - and the proposed forecast profile for each combination.
Is there a good way for:
1. loading these combinations as a set of 'selection ids' into APO DP?
2. loading the set of 'selections assigned to forecast profiles'
I note that the 'selections assigned to forecast profiles' are in table /sapapo/dp_fcst2, but this table includes the GUID for selection ids, so I assume the selection ids must be generated first.
Thanks for any advice.
Regards,
Bob Austin

Hi Bob,
There was a similar question asked sometime back in this forum, and am attaching the replies given to that.
Re: APO DP assignment of selections to forecast profiles
Check this link, it might help you.
Regards,
Jagadeesh.

APO DP - validation of correct forecast profile

We are using APO DP V5.0.
In interactive DP, we forecast at the level of 'product at customer'. For the 'product at customer' characteristic we have navigation attributes, such as 'history type' (eg EPOS, despatch)
The 'history type' determines which key figure we use as history, and so we have forecast profiles which are relevant for the different history types.
If a user assigns a forecast profile in interactive DP to a 'product at customer', we want to get the system to check that the forecast profile is actually valid for the relevant 'history type'. We have named the profiles carefully so that, for example, the first x characters of the profile name reflect the history type; so we could have validation logic saying 'if history type = EPOS, check that forecast profile starts with 'EPOS'.
But how could this validation logic be triggered?
Any ideas?
Thanks,
Bob Austin, Atos Origin

Hi Bob,
Wow, what a brain bender!
I think this would require some fairly serious ABAP...
You can't get the value of an attribute interactively (via a macro function, for example using ACT_IOBJNM_VALUE()). You would need a Function Module that could manipulate the Planning Object Structure to grab the attribute of the characteristic in question, based on the current selection.
The name of the forecast profile also can't be done with a standard APO macro function. We had something similar where we wanted to get the name of the forecast strategy via a macro function, but we ended up needing to create a short Function Module in ABAP that could called as a User Exit Macro. The trick with the Function Module is that you will need is to tell the system to get the GUID of the current selection, then use that to find the name of the Forecast Profile (field PRPFL) from the /SAPAPO/DP_FCST2 table.
Once you have that, you could tell the Function Module to pass just the first four letters ('EPOS') back to the planning book user exit macro so that you could then compare that with the attribute value.
Probably you didn't need me to write this short functional spec, but it was a very interesting problem to consider. Hopefully somebody else will read this and tell us a much simpler way to do it.
Dan

Error BM311 during Model Consistency Check in APO

Hi APO Experts
I find error BM311 - Units of different dimensions cannot be converted during Model Consistency Check in APO.
How can I get to know the code or Unit of Measure, where the inconsistency is there to rectify?
Please suggest.
Thank you.
Pradipta Sahoo

Hi Pradipta,
Can you check below notes:
943543
928502
837310
Regards,
Mukesh Pandey

Consistency checks in APO

Can anybody please explain the reasons for doing the
1.Model consistency check
2. Re-org Consistency check(/SAPAPO/TS_LCM_REORG)
What would be the frequency for these consistency checks?

Okay I'll try and keep the answer simple:
1) The model consistency check results in an overview of the (in) completeness of the master data
objects within the model concerned. Missing data (for example, coordinates of a location are
initialised) will be displayed by error, warning or information messages. It can be checked and if
necessary be corrected from the log. Should be done when maintaining master data or after
activating the integration models (master data transfer).
2) For Time Series the memory consumption in the liveCache increases because of superfluous time series if the master data containing the time series information is deleted or removed from the planning version model. This report removes these superfluous data and tidies up livecache. Should be run daily.
For more info on consistency checks (mostly SNP and related) see the following document:
[Internal and External Consistency Checks|https://websmp203.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000330202007E]
Regards
Ian

SCM 5.1 APO -DP Master Forecast Profile - Change Details

Hi All
If existing Master Forecast Profile has been changed by some authorised user, will it possible to view What changes has been made,when,by whom..etc....??...need functionality which should give all details.
Current functionality giving only changed user name and date.
Regards
Poongunran

It is not available.

Steps to transport the forecast profiles from development server to the pro

Hello All,
We have a scenario wherein we need to transport forecast profiles from APO development server to the APO production sever.
Can anyone suggest me proper steps to include the forecast profiles into the transport request.
Thanks in advance.
Regards,
Jacky.

Hi Sujay ,
Thanks again.
I did check the transaction mentioned by you. But it din't help in my scenario.
I got the sloution for my problem,
we have two tables for forecast profiles, i,e /SAPAPO/DP440G and /SAPAPO/DP440P (these gets updates as and when we create a forecast profiles ) ,
we have to add the entries from this table for the particular forecast profile into the transport request and then we have to transport those requesets , then the profiles would be transported accordingly.
Anyways thanks for replying.. i am giving you points for helping me..:-)
Regards,
Jacky Jain.

Transport of forecast profile

Hello,
I setup a forecast profile in APO Demand Planning. But I do not know how to tranport this new forecast profile. There was no popup with a transport assignment after creating the profile.
The forecast profile is included in an activity and a job - the job is assigned to a transport.
I do not know whether the forecast profile will be transported within the job transport.....
Does anybody know how to transport this forecast profile?
Thanks for your help!
Kind regards
Heinz

Hello Heinz,
Use the transaction /sapapo/tsobj. In this transaction you will have a check box below the planning area which reads "with forecast profile transport". This would transport the forecast profiles along with your plannign area.
Cheers!
Jacky.

LiveCache Consistency Check question, OM17

I have a general question about a LiveCache Consistency Check (transaction OM17). I know that it is a data inconsistency b/w the SAP APO database and SAP APO LiveCache. But what does that mean to a functional user? Can someone explain this in layman's terms?

In Layman terms, you can say that this checks the INCONSISTENCY between LiveCache and Database.
Here is a detailed documentation on each of the Object Types
Consistency Check for Setup Matrices
The consistency check for setup matrices contains:
· A check whether the setup matrices exist in liveCache
· A check whether the setup transitions exist in liveCache
· A field comparison between the setup transitions in the database and those in liveCache
When the setup matrices are corrected, the setup matrices in liveCache are completely generated from those in the database. Previously nonexistent setup matrices and setup transitions are newly created in liveCache. Superfluous setup transitions are deleted from liveCache. Setup transitions that differ at the field level are adjusted to match the database status.
Consistency Comparison for Block Basis Definitions
Use
When you set this indicator, checks are performed in liveCache and in the database on characteristic values for block basis definitions:
· The existence of block basis definitions is checked.
· The consistency of the characteristic values is checked.
After the checks you can call a correction function in the check results display. When correcting the error, the system deletes obsolete block basis definitions in liveCache. The system completes or corrects missing or inconsistent block basis definitions in liveCache.
Note
The check is performed independently of the planning version.
Consistency Check for Resources
The consistency check for resources contains:
· A check that the resource and corresponding time stream exist in liveCache
· An check that a resource's characteristic blocks exist in liveCache
· A field comparison between the database resource and the liveCache resource
When correcting the resources, the resources in liveCache are completely generated from the database resources. Previously nonexistent resources are created in liveCache.
Consistency check for downtimes caused by maintenance order
The consistency check for maintenance downtimes contains:
A check that the maintenance downtime has a reference to an existing maintenance order.
A check that the dates of maintenance downtime correspond to the exisiting maintenance order.
When correcting the maintenance downtime errors, downtimes without maintenance order are deleted and wrong dates of downtimes are corrected in relation to the maintenance order.
Consistency Check for Product Location Combinations
Use
If you set this indicator the system executes a consistency check for product location combinations. The consistency check for product location combinations includes:
· A check for the existence of a product location combination in the database and in liveCache
· A field comparison between product location combinations in the database and in liveCache
· The determination of obsolete entries for product location combinations in the database
· A check for the existence of characteristic value assignments for product location combinations in the database and in liveCache
· A field comparison of characteristic value assignments for product location combinations in the database and in liveCache
After the check you can call a correction function from the display of check results. For the correction, the system deletes obsolete product location combinations from the database and in liveCache. The system corrects inconsistent product location combinations and characteristic value assignments for product location combinations in liveCache.
Consistency Check for Stocks
Use
If you set this indicator the system executes a consistency check for stocks. The consistency check for stocks includes:
· A check for the existence of a stock in the database and in liveCache
· A field comparison between stocks in the database and in liveCache
· The determination of obsolete entries for stocks in the database
· A check for the existence of characteristic value assignments in the database and in liveCache
· A field comparison between characteristic value assignments for batch stocks in the database and in liveCache
After the check, you can call a correction function from the display of check results. For the correction, the system attempts to correct inconsistent stocks in the database and in liveCache. If a correction is not possible, the stocks are deleted in the database and in liveCache. The system corrects characteristic value assignments for batch stocks in liveCache.
After inconsistent stocks have been corrected, it may be necessary to start the delta report in order to reconcile SAP APO and SAP R/3.
Consistency Comparison of Configuration/CDP for Orders
Use
When you set this indicator, the system performs a consistency check with regard to configuration or CDP (characteristic value assignments/ requirements) for receipts/requirements belonging to orders:
· In the case of products with variant configuration and product variants, the system checks whether there is a referenced configuration in the database.
· In the case of products with CDP, the system checks whether CDP characteristics exist.
Note
In the area Restrictions, you can use the indicator CDP: Detailed Check to define a detailed check for CDP characteristics. If you set this indicator, the CDP data used for the orders is also compared with the product master.
· For products without configuration/CDP, the system checks whether invalid references to variant configuration or invalid CDP characteristics data exist.
After the check, you can call a correction function in the check results display. When executing the correction, the system tries to adjust inconsistent orders in liveCache.
After inconsistent orders have been corrected, you may need to start the delta report to compare the SAP R/3 system and SAP APO again.
Dependencies
The consistency check for configuration or CDP data is very time-consuming. You should therefore limit the comparison as far as possible to certain products or locations.
Consistency Check for Production Campaigns
If orders are assigned to production campaigns that do not exist in the database, this leads to inconsistent campaigns.
You can correct inconsistent production campaigns by removing all orders from them. That means that the campaign assignments are removed from the orders in liveCache.
Consistency Check for Operations
In the database table of /SAPAPO/OPR operations, there may exist operations that have no orders in liveCache, no orders for a simulation version, orders for deleted simulation versions, or no external operation number. These operations place an unnecessary load on the database table and can hinder system performance.
Consistency Check for Planning Matrices
As planning matrices are not master data, they are only located in liveCache. For each production version, there is a record in the database with information about matrices that must exist for this production version and whether the last matrix explosion was successful.
The consistency check for planning matrices checks:
· Whether the matrices associated with each record on the database exist in liveCache
· Whether the records associated with all the matrices in liveCache exist on the database
· Whether the last matrix explosion was successful.
If inconsistencies are discovered, they can be corrected. As corrections are made by recalculating the inconsistent matrices, the process can take a while and should only be done for large matrices (with many orders or many item variants) at times when it can be guaranteed not to hinder any other system processes.
Consistency Check for Simulation Versions
This is a check for whether simulation versions exist in liveCache.
Correction does not take place automatically. Simulation versions that still exist in the database but no longer exist in liveCache do not influence the running of the system. If necessary, they can be deleted using transaction /SAPAPO/CDPSS0.
Consistency Check for Product Allocations
The consistency check for product allocations checks the data for product allocation assignment from the database and compares this with the incoming orders quantity in Demand Planning. Surpluses or shortages are displayed and can be corrected.
The reconcile is only executed for product allocation groups with a direct connection to the product allocation group in the planning area if the connection is also fully defined.
There may be long runtimes during the consistency check due to the data structure. The following factors can hinder performance:
· Number of characteristics combinations
· Number of periods in a time series
· Number of sales orders that take product allocations from a time stream
Error in the reconcile
If it is not possible to reconcile the incoming orders quantity, the data records are issued again with a relevant error message. Check the following causes and attempt again.
Check:
· If the planning area to be checked is locked
· If the time streams are initialized (after liveCache has been initialized)
· If all characteristics combinations area available in the planning area
· The wildcard indicator for collective product allocation
· The settings for your planning area
Due Delivery Schedules/Confirmations Consistency Check
When a scheduling agreement release is received from a customer for sales and distribution scheduling agreement items, a due delivery schedule is created and stored in liveCache. As soon as a confirmation for a due delivery schedule containing at least one schedule line with a quantity larger than zero is generated, an object is also created for it in liveCache. The transaction data for sales and distribution scheduling agreement items contains, amongst other things, an entry with the key of the due delivery schedule object currently located in liveCache and an entry with the key of the confirmation that is currently valid in the database. During the check, the system checks whether liveCache objects exist for sales and distribution scheduling agreement items and whether the transaction data entries are correct.
The following individual checks are made for active sales and distribution scheduling agreement items:
· Is there an operative scheduling agreement release and/or forecast/planning delivery schedule in the database, but no associated liveCache object?
· Is there a confirmation in the database, but no associated liveCache object?
· Is there a due delivery schedule in liveCache, without at least one existing operative scheduling agreement release and/or forecast/planning delivery schedule?
· Is there a confirmation in liveCache, without an existing confirmation in the database?
· Is the key in the transaction data in the database that shows the current due delivery schedule in liveCache, also that of the actual liveCache object?
· Is there actually a confirmation in the database for the key in the transaction data that shows the currently valid confirmation in the database?
If a sales and distribution scheduling agreement item is inactive, there are not allowed to be any due delivery schedules or confirmations in liveCache. In this case, the following checks are made:
· Is there a due delivery schedule in liveCache for an inactive sales and distribution scheduling agreement item?
· Is there a confirmation in liveCache for an inactive sales and distribution scheduling agreement item?
Consistency Check for Production Backflushes
Partially confirmed orders cannot be deleted from liveCache. For each partially confirmed order of the database table, there must be a corresponding order in liveCache. If no order exists, there is a data inconsistency that can only be rectified by deleting the order from the database tables of the confirmation.
Entries for orders that have already been confirmed exist in the status matrix. The entry in an order's status matrix is deleted when the confirmed order is deleted by the /SAPAPO/PPC_ORD archiving report. Each status matrix entry for which database tables of the confirmation do not exist, present an inconsistency that can only be removed by deleting the status matrix entry.
Consistency Check for iPPE Objects
The iPPE object is not an iPPE master data structure. It is a data extract that is generated for each iPPE access object.
The consistency check for the object checks that it exists in liveCache and also determines its identity using the backup copy in the database. When correcting the object, the copy from the database is written to liveCache.
It is necessary to check the object if the following error message occurs: 'Error while calling COM routines via application program' (/sapapo/om 102) with return code 1601, 1602, or 1603. This does not apply to liveCache initialization.
Consistency Check for Procurement Scheduling Agreement Items
The following three objects represent procurement scheduling agreement items (scheduling agreement in short):
1. Scheduling agreement schedule lines
2. Release schedule lines
3. Confirmations
All these objects are located in liveCache. Release schedule lines and confirmations are also located in the database with a historical record. Depending on the process that was set up for the scheduling agreement, not all objects exist in liveCache or have historical records.
If goods movements exist for an object, there must always be at least one entry in liveCache. If all schedule lines are covered by goods receipts, at least one schedule line will exist in liveCache with the number '0000000000' and an open quantity of 0.
A liveCache crash, operator errors, and program errors can all cause inconsistencies. Below is a list of all the inconsistent statuses that have been identified and that can be removed:
1. The object is not in liveCache but goods receipts exist.
2. The number of input nodes and output nodes is different.
3. There are no input nodes at the order, but the material exists in the source location for the order.
4. The original quantity at the source of an order is different from that at the destination.
5. The accumulated quantities in liveCache are different from those in the database (the cumulative received quantity, for example).
6. The set process is compared with the status in liveCache.
7. A check is made to see whether the scheduling agreement is being planned in APO or in R/3 and whether the schedule lines have the appropriate specification.
If a schedule line inconsistency is identified, no more checks for inconsistencies are made, instead it moves on to the next schedule line.
Consistency Check for MSP Orders
Provides a list of maintenance and slot orders that
·     Exist in the database but have no corresponding orders in the liveCache
·     Exist in the liveCache, but have no corresponding orders in the database
Procedure
From within the list, you can either
·     Correct the inconsistencies
If you choose to do this, the system deletes the selected orders from the database and/or liveCache.
You receive a message that the selected order(s) have been deleted.
·     Leave the inconsistencies in the database and/or liveCache
Such inconsistencies place an unnecessary load on the database and/or liveCache. Moreover, those orders that exist in the liveCache, but have no corresponding orders in the database, influence the scheduling results of subsequent orders in the liveCache
Hope this helps
Regards
Kumar Ayyagari

Creating a New Forecasting profile for MRP

Hi there,
Please can somebody let me know how do I create a new Forecasting profile for MRP.
I want to see this in table MRPR once created. (field PROPR).
Kind Regards,

Dear marelizen
Use transactio code MP80.
Creating a Profile
The information contained in this info object is relevant to the material master for industry and to the article master for retail. Retail customers are requested to substitute:
article for material
requirements planning for material requirements planning or MRP
1. In the Material Master menu, choose Profile ® MRP profile or Forecast profile ® Create.
The initial screen appears.
2. Enter the name you want to give the profile.
If you want to use an existing profile as a reference, enter its name under Copy from so that the system can copy its values to the new profile.
3. Choose Selection screen.
The selection screen appears. It shows all the fields that can be copied to the MRP or Forecasting screen in the material master record.
4. Enter a profile description and select the fields you want the profile to contain, specifying whether each field is to be copied to the material master record as a fixed value or as a default value.
It is not possible to select Fixed lot size and Maximum stock level in a single MRP profile. However, if you select Maximum stock level, you must also select Lot size (materials planning).5. Choose Data screen.
MRP profile data is spread over two screens. To switch from one screen to the other, choose Data screen 1 or Data screen 2.
When you access the data screen from the selection screen, the system checks whether the fields selected are allowed to appear in the same profile.
The data screen appears, containing only the fields you selected on the selection screen. The fixed values and default values are displayed in different colors. All fixed values are required fields except where the field can also be left blank.
If, in the forecast profile, you enter N or 0 as the forecast model, no forecast is made.
Like forecast model N, if you enter forecast model 0 when maintaining a forecast profile, you will be unable to maintain any other field in the profile.
Unlike forecast model N, forecast model 0 deletes any existing forecast values when you change the material. This ensures that these values are no longer included in materials planning.
6. Enter the corresponding values and save the profile.
If the system detects inconsistencies or errors, it asks you to change the fields selected on the selection screen and/or to correct the values. Otherwise, the initial screen appears, where you can begin to create another profile.
warm regards
Ramakrishna

MRP & Forecast Profile

Hi there,
When we mainatain Forecast Profile (T-code - MP30).. we have two colums to be checked for differrent fields Fixed value & Default value.
But we cannot set both the indicator at the same time for a field i.e both the fixed value & default value checked.
Same is also applicable for MRP Profile - MMD1
Then why SAP has provided a check box instead of radio button .
Please suggest me the same .
Regards
Kaushik Choudhury

Hi kaushik,
Default value - Indicator that specifies whether the field is copied to the material master record as a default value; that is, the value can then be overwritten in the material master record
whereas
Fixed Value - Indicator that specifies whether the corresponding field is copied to the material master record as a fixed value; that is, the value cannot then be overwritten in the material master record

Composite Forecast Profile

Hi,
     I tried to create Composite forecast profile. I got this error message when I tried to run it , "No suitable single profile is assigned to master profile." Not sure what happened. This is the steps that I did:
       1) Create Master Profile in forecast profile.
       2) Select "Composite Forecast" at the selection model and type in the name of Composite forecast profile.
       3) Go to Composite forecast tab and select my created univariate profiles.
       4) Assign weight to each univariate profile.
       5) Click "Save Single" profile button at the top.
       6) Click the clock icon (or F8) to adopt the change.
      Could anyone tell me what went wrong ? Thanks in advance for your help.
Paranee

Hi Paranee,
Did you check that your planning book had the check box composite forecast activated?
This could be the reason.
You can check this in transaction /SAPAPO/SDP8B
I hope this can help you.
Regards.
Marín.

Selection generated with Navigational Attribute and store forecast profile

Hi,
Our business has a requirement that will require for the solution a Forecast Profile to be stored against a selection which was generated with a navigational attribute in the selection. I have found two SAP Notes 329707 and 394076 shown below which point to BAdi /SAPAPO/SDP_FCST5 method SEL_CHANGE to do the job. Can anyone help me in understanding what coding we need to do within the BAdi to get this to work. Does anyone have an example?
SAP Note 329707
Method:
    SEL_CHANGE (as of SCM 4.1)
    This method can be used to change the selection to be stored in
    in the generated selection table. Navigation attributes can be
    removed, such as the function of assigning a forecast
    profile to the selection can also be allowed for selections with
    navigation attribute without a basic characteristic.
    Parameter
     IV_PAREAID      Importing Type /SAPAPO/TS_PAREAID
     CT_SELECTION    Changing   Type /SAPAPO/TS_IOBJ_SELECTION_TAB
Sample code:
    DATA: lv_tabix     TYPE sytabix.
    DATA: lt_chars     TYPE /sapapo/dm_int_chars_tab.
    DATA: ls_chars     TYPE /sapapo/dm_int_chars.
    DATA: ls_selection Type /SAPAPO/TS_IOBJ_SELECTION.
    IF iv_pareaid = 'PAREA1'.
      CALL FUNCTION '/SAPAPO/TS_PAREA_SINGLE_GET'
        EXPORTING
          iv_pareaid   = iv_pareaid
        IMPORTING
          et_chars     = lt_chars
        EXCEPTIONS
          not_found    = 1
          OTHERS       = 2.
      CHECK sy-subrc EQ 0.
      LOOP AT ct_selection INTO ls_selection
                          WHERE iobjnm NE '9AVERSION'.
        lv_tabix = sy-tabix.
        READ TABLE lt_chars INTO ls_chars
                            WITH KEY iobjnm = ls_selection-iobjnm.
        IF sy-subrc EQ 0 AND NOT ls_chars-atrnavfl IS INITIAL.
           DELETE ct_selection INDEX lv_tabix.
        ENDIF.
      ENDLOOP.
    ENDIF.
SAP Note 394076
As of Release SCM 4.1, you can use the method SEL_CHANGE of the BadI /SAPAPO/SDP_FCST5 to process the selection before saving it to the generated selection tables. This allows you to save selections with navigation attributes, for example, where the selections do not have a specified basis characteristic. You simply need to delete the navigation attributes from the selection.

Is all the Navigational attribute checked for display during cube creatiion?
Prathish

Apply custom GUID forecast profile to reforecasting activity?

Hi APO Experts,
My company currently uses only one master forecast method (auto model selection 2, forecast method 56) for every individual customer that we have in APO (~10,000 customers.) I would like to fine tune the process and be able to specify a forecast for certain individual accounts. We use SAP APO version 3.1.
In interactive forecasting mode, I have found the option to "Save assignment with unique forecast profile" (under Settings -> Forecast Profile) and I am now able to create customer specific forecasts with a unique "GUID." However, I am not sure how to utilize these forecasts through a roll forward. I roll my customer forecast window forward every month (ie, i change it from April 2011 - April 2012 to May 2011 - May 2012) by running a Mass Processing activity. But I can not find the GUID forecast profiles when I set up the mass processing activity. I tried deactivating the "always use job profile" button but that still doesn't work - instead of using the GUID specific forecast profiles during the reforecasting, APO will populate those customers with the default master forecast profile. Is there a step that I am missing?
I appreciate your time and help,
-- K

Hi arun,
If i understand your situation,
You put
Validity start date as may and validity end date as dec
constant factor before start date '0'
constant factor after end date '100'
still you see forecast for march april.
if that is the issue, This might happen as per default settings, i think the default settings are constant factor before start date as 100%.
do the following
I dont know how the screens look in 4.1
But in the phase in profiles go to Menu option GOTO> settings
there you can define if constant factor by default should be zero or hundred.
The main reason why this happens is if you try to put 0 as the constant factor before the start date, it does not save anything. so you need to make the default settings that constant factor before the start date is 0 %.
let me know if this helps you or if the problem still persists.
Thanks,
Mythilee

APO DP Forecast profile consistency check

Similar Messages

Maybe you are looking for