Demantra: Level Id in mdp_matrix

What does the level_id values of 0, -1 in the mdp matrix table signify ?
Since the forecast levels are from 1 to 6 - the level_id should never be 0 or -1 ?
Any idea what are the references for this field in the mdp_matrix
thx and rgds,
Pankaj
Edited by: pankajkum on May 13, 2009 2:54 PM

Hi Pankaj,
Do you have any valid combinations for which level_id is < 1. Usually if prediction_status is '99' (which stands for dead combinations), the engine doesnt generate forecast for these combinations and you see level_id = -1.
Hope this helps.
Regards
Raj

Similar Messages

The three members in Demantra level Forecast System Status represent what?

There are three members in Demantra level Forecast System Status. Good For Forecast, Young Address, and Dead Address. What do each of these mean and how does it work?

Hi,
98 (Young) — Sales for this combination are too new to be used for prediction.
99 (Dead) — Sales for this combination are not recent enough to be used for prediction.
1 (Live or Active)—Neither young nor dead.
Tks
MJ

Demantra - Create New Series - Mdp_matrix - Data Type String Issue

I created a new series (MDP_matrix) that has the data type as String. The display format is BLANK.
I was able to load the data into mdp_matrix table for the series i created.
However, when i look at the series in a worksheet, it does not display the string value. It display zero. for some reason, it considers the series as numeric and not string. Any idea why that would be happening?
This is on version 7.2 using SQL server/tomcat

Hi
1. Have you tried giving display format i.e ###?
2. Is your server expression something like max (mdp_matrix. column_name)?
Tks
MJ

Level Id in the mdp_matrix ( Oracle Demantra)

The level id in the mdp_matrix signifies the level at which the forecast gets generated for a given item-location combination.
I have six levels defined in the forecast tree.
When I see the results for level id in mdp_matrix after having run the analytical engine I am seeing values of -1, 0 and 6 - what do they signify.
Which table stores these level id and equivalent forecast tree level.
I am bringing sales historical data at the lowest level - for both item and ship to code.
I am atleast expecting some/few/most of the forecast should be generated at the lowest level - level 1 (level_id) - but hardly do I find records in the mdp_matrix as level_id =1 (the min level in the forecast model library is set to 2 / 3 and max level to 999999.
Any pointers appreciated.
thx and rgds,
Pankaj

Hi Pankaj,
The level_id field is updated dynamically when you run the analytical engine. The range of values in level_id field is determined by number of forecast levels you choose in forecast tree definition. But while generating forecast, which values to use among is determined by max_fore_level and min_fore_level parameters as mentioned by Rubellah.
Take the following example: (This is the log generated by Analytical Engine, stored in "engine2k" folder)
In this log statement [x,y,z] values signify, x - level_id, y - item_node and z - loc_node respectively.
The Analytical engine analyses every set of data available for forecast for each item-location combination. But always generate forecast at lowest possible level.
1) 10:36:44:967 [3,22,1] has a usable number of observations. (52)
2) 10:36:44:998 [2,22,1] has a usable number of observations. (52)
3) 10:36:45:280 [2,22,1] forecast succeeded using models B,C,E,X
4) 10:37:24:219 [3,53,8] has a usable number of observations. (52)
5) 10:37:24:265 [2,53,8] has a usable number of observations. (52)
6) 10:37:24:922 [2,53,8] forecast failed.
7) 10:37:25:578 [3,53,8] forecast failed.
8) 10:37:25:797 [3,55,8] has a usable number of observations. (4)
9) 10:37:25:828 [2,55,8] has a usable number of observations. (4)
10) 10:37:25:844 [2,55,8] forecast failed.
11) 10:37:25:859 [3,55,8] forecast failed.
12) 10:37:26:047 [3,57,8] has a usable number of observations. (51)
13) 10:37:26:078 [2,57,8] has a usable number of observations. (51)
14) 10:37:26:078 Node has Intermittent data.
15) 10:37:26:125 [2,57,8] forecast succeeded using models F
16) 10:37:26:906 [4,3,8] forecast succeeded using models B,C,E
17) 10:37:27:250 [4,4,8] has a usable number of observations. (52)
As you see line 1, shows that there is usable no of observations it found item_node 22 & loc_node 1 combination at higher level_id 3. But according to line 2 it also found good enough observations at lower level_id 2. Hence it generated the forecast at level_id 2 as sighted in the 3rd line.
The exceptions might occur like in lines 4,5,6 & 7 where engine is not able to generate forecast at lower as well as upper level too. The first try is made at lower level [2,53,8](It failed) the 2nd try made at upper level [3,53,8](It failed here too).
From the third set of lines 8,9,10 & 11 we can guess the reason of forecast being failed as very less number of observations (only 4).
The forth set of lines 12,13,14 & 15 shows that there is intermittent data available so it generated forecast at lower level using model "F".
Line 16 states that forecast is generated at upper level_id 4.
Line 17 states that there were usable no of observations but didn't generate any forecast for that combination.
Hope this might help you.
Milind...

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

Can demantra(7.2) forecast at hourly level??

I have a requirement where the forecast needs to be done at hourly level .
Can it be done in demantra ?
As per implementation guide for demantra 7.2 , it seems it can be done. Implementation guide says :
"The base time unit is specified during configuration to a length that is appropriate for
your planning cycle. Oracle provides three sizes of base time unit (day, week, or month)
and *can support hourly time units if needed*."
Please let me know, if you know the details of such setup
Regards

Hi,
I think i was not able to explain the question well . I know that the forecast cycle can be run each hour.
My question is : can the forecast be generated at hourly bucket ?
can we give history in terms of hourly bucket and get the forecast in hourly bucket too?
The time level aggrgation may look like : - hour -> day -> week -> month
As per data model, there seems to be only three time bucket option is there i.e. day , week and month.
But as per implementation guide , we can also forecast in hourly bucket. if it can be done , can some body let me know what the extra step required .
Regards

Populating level values in Demantra.

Hi Guru's,
We have a requirement to create a new level on top of item level in item hierarchy. I took one of the exisiting level (t_ep_p2) and changed the its level title. The thing got reflected in the configure levels. I upgraded the data model and used level value and level value association dat file to populate the level member. The request went through without any errors but I could not see the same in staging tables. The level members are also getting reflected in the worksheets.
Does any one faced this issue. Am I missing anything here?
Thanks
Ram

Ram,
Why are you using level value and level value association dat file in Demantra? As far as I know, they were meant for ODP, not for Demantra.
I recommend to use custom_hook procedure (if you are using EBS-Demantra integration) OR direclty populate staging table (standalone Demantra).
Follow the steps mentioned in implementation guide for Adding a new level.
Thanks,
Amit

Item and Item description as Levels ?? In Demantra

I have Item defined as the lowest level and its description also being defined (as level description) in oracle Demantra.
From the staging table - I bring in item and item description.
In the Oracle Demantra seeded model - I find that Item has been defined as the lowest level - (has description with the same item code as its reference in staging table). As parent I have another level defined "Item Description" and this has the description as in the staging table.
Is it required - why is item description defined as another level rather than it should be the description of the item level ?
Can somebody throw some light on this.
thx and rgds,
Pankaj
Edited by: pankajkum on May 1, 2009 3:09 PM

Hi Pankaj,
As Karthi has sighted, whenever we talk about any upper level its a grouping of its child level members. There is always being Many-to-One relationship between the child level members and parent level members.
Comming to the seeded Demantra data model that Oracle has provided, Item Description is taken as an attribute for item level. Similarly You can see other attributes like "Media Type" and "Platform".
The purpose of making these attributes as parent levels is to use them in a unique Demantra feature called "Attribute Based Forecasting". As you might have read that Demantra also supports attribute based forecasting, we have to convert these attributes in parent levels and have to set them as item-location combinations in the Forecast Tree definition. The forecast result you will see will be different from what you see when you use the default Forecast Tree definition.
Hope this answers your query.
Milind...

How to load item level and location level member in demantra

This is in context where we are not using any integration of demantra with either Ebiz or E1 system.
Data is present in flat file.
As per i know, integration interface can only export the data for item level and location level but can not import data for these level.
the second thing i know is that when we create data model then load_data.bat file should have been created in Demand Planner/Desktop directory. But this didn't got created. So i am not able to use load_data.bat file for uploading data.
The third place ,i think is from worksheet thru edit method ( i am not sure about this).
But i want to upload the data in bulk for item level and location level. Can it be done without any customization i.e without creating any sql loader file etc ??

Hi Abhishek,
The standard practice to load data for items/ locations and sales is through the DATA MODEL definition only. One should use LOAD_DATA.BAT file in normal scenario for loading data into Demantra staging tables from tEXT files.
In case you are having trouble with loading data using LOAD_DATA.BAT file, then do the following:
- modify your DM definition to Data tables instead of flat files
- use SQL loader to upload data in correct format into Demantra's staging tables "T_SRC_XXX"
- Run EBS Full Download workflow to download data into demantra's main tables.
Integration interfaces should not be used to load basic sales data into Demantra.
Hope this helps.
Thanks
Raj
(http://oracledemantra.blogspot.com)

Demantra - Cannot view a level in Worksheet

I have populated data in Item Branch Category 1 in t_src_sales_tmpl table. After 'EBS Full Dowload' data is populated into t_ep_e1_it_br_cat1 (Item Branch Category definition table) and is also updated in mdp_matrix. Now I want to add this level 'Item Branch Category 1' into worksheet. However I cannot view the level in worksheet editor [Worksheet Designer --> Aggregation. In the Available Levels box]. Is there anything that I need to do to make a level visible in 'Available Levels' of the Worksheet?

What's the word on this? I am still having the same issue. This is very problematic for many pdfs on many websites! Can someone from Adobe please answer this???

Data Interface to mdp_matrix in demantra

Hi,
What all ways we have in demantra for data interface esp for mdp_matrix?
Other than custom proc, integration interface, is there any other way to interface data from staging table to mdp_matrix table in demantra.
Thanks & Regards,
Ankur Dawra

Hi MJ,
Can we really update data in MDP_MATRIX table thru integration interface that is custom? As read in oracle guide that we cannot update data in mdp_matrix thru integration interface.
Thanks & Regards,
Ankur Dawra

EBS -Demantra Integration - Item Status attribute

Hi,
We would like to bring Item status attribute to Demantra from Oracle Inventory.
APS standard collection don't bring this data into APS server. Any suggestion?
How to map in Demantra, as Item Attribute or MDP_Matrix combination level or any type of series?
Possibility it will be a unique combination of Item and Org.
Thanks
Dheeraj

You can create a new combination level or use one of existing seeded combination level in Data model and put the correct status attribute values in T_SRC_SALES_tMPL for the item-org combinations in it. EP_LOAD will then download this as a combination level and it's population into Demantra, which you can use in worksheets based on need.
Thanks
Raj

Techniques for New Product Introduction in Demantra 7.3.0.1

Hi,
In Demantra 7.3.0.1 there are two ways for New Product Introduction:-
1) Demand Planner: Member & chaining management
2) Collaborative Workbench: Create Similar product
Can someone please tell me the pros and cons of each technique.
The new product introduction will be handled by our clients, so I wanted to know if all the required features can be handled by just one method so we can propose that to be used by the client. Or do we need to use both techniques for different scenarios?
As I understand with Chaining one can link one item to many sites at one go, while with CW the similar item is created linked to one particular location.
Also CW allows for adding cannibalization factor which is not accounted for in chaining.
Apart from this it would be really helpful if someone could throw some more light on the issue.
Thanks.

Hi Gaurav,
I personally feel that 'Create Similar product' is a much required improvement over the original way of NPI using Member & Chaining Management.
Also with CW as well, a new and similar item created can also be linked to multiple location, same as Source Item, depending on the filters used in the Worksheet from which the create similar product is invoked.
some of the PROS and CONS of the 2 methods are as follows:
Demand Planner: Member & chaining management
Pros: 1) Can be used to specify the time range for copying the history date.
2) Can be used to specify the Percentage by which the source data needs to be adjusted while copying into the target combination
3) An important feature is that this can be used to do chaining at an aggregated level.
Cons: 1) It takes a long time to setup a New Member, combination and Chaining relationship.
2) High User involvement since user has to perform muliptle tasks and more error prone.
Collaborative Workbench: Create Similar product
Pros: 1) User-friendly
2) Users needs to enter a few datapoints in single form and does not need to navigate through multiple forms/screens
3) Ability to specify Cannibalization parameters as well as Launch dates
4) Good performance.
5) Ongoing Chaining
6) When coupled with features like 'End of Lifecycle date', it provides a complete Business solution
Cons: 1) Can not be used for only performing Chaining.
2) While it can be used to create a New Similar Product, it cannot be used to create a new similar Customer based on an existing item-location combination data. This,though, may not be a very common scenario.
3) Apart from copying other Item attributes, the method also copies the same 'Item Description' level from source to the new similar product, which sometimes can be very confusing.
Hope this helps.
Thanks,
Rohit Goyal

How to load data thru flat file in demantra?

Hi,
I am using seeded data model for loading data for DM module in demantra.
As per data model there is 3 staging tables for item, location and sales_data i.e. t_src_item_tmpl,t_src_loc_tmpl,t_src_sales_tmpl respectively.
I have seen the final table for sales data i.e. sales_data table. ther is only one item_id and location_id column against which sales_date and quantity is loaded.
I have same sales_data and quantity to be loaded for different location hierarchy and item hierarchy .
How the data file is created ? if you have any sample data files , can you please share with me ? If any changes needs to be done in data model for loading datardsa in custom hierarchies ?
Regards

Welcome user10979220 to the wonderful forum.
"How many rows will be there in item flat file ?
How many rows will be there in location flat file ?
How many rows will be there in sales data flat file ?"
Answer to these questions are based on the number of sales that has occured as well as the item hierarchy and the product hierarchy.
From the example
Item_name | organization | ship to site | Sales date | quantity
item 1 org1 site1 19-Jan-2008 80
item1 org1 site2 20-Jan-2008 100
I can say that the number of rows in sales data is 2 while that in item file is 1 and location file is 2.
The answer to how the flat file will look is
Item file can have
Item_Id|Item_Name
01     Item1
Location file can have
Org_Id|Org_Name|Site_Id|Site_name
O_01     Organization 1     S_01     Site 1
O_01     Organization 1     S_02     Site 2
Sales file can have
Item_Id|Item_Name|Org_Id|Org_Name|Site_Id|Site_name|sales_date|Quantity
01     Item1     O_01     Organization 1     S_01     Site 1     19-Jan-2008 80
01     Item1     O_01     Organization 1     S_02     Site 2     20-Jan-2008 100
Once you define the data model and load the data it is advisable not to change the data model since the next time when you load the incremental data it will error out due to the mismatching columns. So its better that you define the data model first and then create the files accordingly.
Hence after loading data if you want to view sales data at the product_category1 level then you should already have the product_category1 level defined in the data model.Else You have to create the product_category1 level and associate it in the item hierarchy.Also the sales file should have columns for product_category1.
Then the item file will look like
Item_Id|Item_Name|Product_category1_Id|Product_category1_desc
01     Item1     PC_01     Product_category 1
and the sales file will look like
Item_Id|Item_Name|Org_Id|Org_Name|Site_Id|Site_name|sales_date|Quantity
01     Item1     O_01     Organization 1     S_01     Site 1     19-Jan-2008 80
01     Item1     O_01     Organization 1     S_02     Site 2     20-Jan-2008 100
This is just a basic overview about loading the data into the staging tables.In short the item table should have the item hierarchy in it, the location file should have the location hierarchy in it and the sales file must contain the details about the sales at the lowest item-location level.
Hope I answered your query.
Thanks and Regards,
Shekhar

Export and Import Integration Profile - Demantra

Hi All,
I am working on demantra workflow in export and import integration profiles through workflow.
I want to avoid a customization to integrate the export profile data created from series A and import the data into other import profile created from series B.
I have done the following:
1. Create an export integration profile from series A and when launch the workflow found the below:
1. view_name BIEO_view_name and table_name BIIO_table_name got created in transfer_query table.
when i did
select * from BIIO_view_name got records and when i did select * from BIIO_table_name, no data found.
2. I want to populate data into the BIIO_table_name created from export profile. Is there any standard process to populate the data into the biio_table_name from bieo_view_name without writing the custom pl/sql.
I need this data to populate into a import profile which got created through series B.
I want to avoid the customization of wriring a custom pl/sql and want to know is there any seeded process of integrating the export profile from series A to import profile from Series B.
Any help is appreciated.
Regards,
AK
Edited by: Ajaykunde on Nov 28, 2009 8:53 AM

Hi,
Before to import your BS, did you import the Technical System?
Before to import your Technical System, did you import the SWCV ?
Before to import your SWCV, did you import the Product?
if no, you have to respect a sequence for the import: from highest to lowest level
if answer is yes. then In your BS defined in Dev, do you have a transport Group which says "BS_dev -> BS_Qua"?
If yes, both BS have to be defined in Qua SLD, else your transport link... has no link.
Moreover, when you import something, normally you have a detailed error message which explain you what is missing.
>> Question: How many business system should i maintain in SLD?
no limit I think.
>> Question: Should i do any config at the Transport Group?
Only if you want that your BS_dev becomes automatically a BS_Qua after the transport.... so for me, it's yes
regards.
Mickael

Demantra: Level Id in mdp_matrix

Similar Messages

Maybe you are looking for