Single level hierarchy

Hi,
I'm looking at converting some of our existing olap applications to Oracle OLAP, but have hit a brick wall. I can't seem to get Oracle to create a hierarchy with only 1 level. Is it possible for a hierarchy to have only 1 level in Oracle? If not, does anyone know of a workaround? I could create a "fake" rollup, like a top level of "Total all..." but since it won't be a meaningful value, its just going to look like noise to the users, so I'd like to avoid doing that.
TIA,
Beth

Hi,
Thanks for your reply. I'm glad to hear that it should be possible. Hopefully, I'm just having a problem getting the right syntax. Initially, I was trying to create this dimension in OWB. Its a geography dimension with 4 levels. There are 4 hierarchies each with one level. This is the code that OWB generates.
CREATE DIMENSION "AUSTRALIA_MARKET_DIM"
LEVEL "MKTTOT" IS "AUSTRALIA_MARKET_DIM"."MKTTOT_ID"
LEVEL "NATCUST" IS "AUSTRALIA_MARKET_DIM"."NATCUST_ID"
LEVEL "ASTATE" IS "AUSTRALIA_MARKET_DIM"."ASTATE_ID"
LEVEL "ASTORE" IS "AUSTRALIA_MARKET_DIM"."ASTORE_ID"
ATTRIBUTE "MKTTOT" DETERMINES ("MKTTOT_LONG_NAME","MKTTOT_SHORT_NAME" )
ATTRIBUTE "NATCUST" DETERMINES ("NATCUST_LONG_NAME","NATCUST_SHORT_NAME" )
ATTRIBUTE "ASTATE" DETERMINES ("ASTATE_LONG_NAME","ASTATE_SHORT_NAME" )
ATTRIBUTE "ASTORE" DETERMINES ("ASTORE_LONG_NAME","ASTORE_SHORT_NAME" )
OWB doesn't even attempt to create the hierarchies for the dimension object.
So I tried adding a hierarchy and executing it in sqlplus, but can't find a syntax that works. It seems the CHILD OF clause is mandatory.
CREATE DIMENSION "AUSTRALIA_MARKET_DIM"
LEVEL "MKTTOT" IS "AUSTRALIA_MARKET_DIM"."MKTTOT_ID"
LEVEL "NATCUST" IS "AUSTRALIA_MARKET_DIM"."NATCUST_ID"
LEVEL "ASTATE" IS "AUSTRALIA_MARKET_DIM"."ASTATE_ID"
LEVEL "ASTORE" IS "AUSTRALIA_MARKET_DIM"."ASTORE_ID"
HIERARCHY STATES ("ASTORE")
ATTRIBUTE "MKTTOT" DETERMINES ("MKTTOT_LONG_NAME","MKTTOT_SHORT_NAME" )
ATTRIBUTE "NATCUST" DETERMINES ("NATCUST_LONG_NAME","NATCUST_SHORT_NAME" )
ATTRIBUTE "ASTATE" DETERMINES ("ASTATE_LONG_NAME","ASTATE_SHORT_NAME" )
ATTRIBUTE "ASTORE" DETERMINES ("ASTORE_LONG_NAME","ASTORE_SHORT_NAME" )
SQL> /
HIERARCHY STATES ("ASTATE")
ERROR at line 6:
ORA-00905: missing keyword
Thanks for your help,
Beth

Similar Messages

Failed validation as a level hierarchy

Hi,
I have dimension called SKU in my analytic workspace with a hierarchy PRODUCTS defined as ALLPRODUCTS<--MD<--MG<--PG<--STYLE<--PRODUCT. I have used composite keys as Members to maintain uniqueness. For example the member expression for PG is CUBE_DEV.DIMSKU.MDID || CUBE_DEV.DIMSKU.MGID || CUBE_DEV.DIMSKU.PGID. I'm not using Surrogate keys. When I hit the maintain Dimension SKU, LOAD NO SYNCH succeeds but the compile step fails with error
"INI: error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>INI: XOQ-01712: "SKU.PRODUCTS" failed validation as a level hierarchy., Generic at TxsOqStdFormCommand::execute"
I looked at the rejected records and every record has the error "(XSRWLD13) Cannot change the level of a dimension member within a single load." Can anyone help me resolving this issue ?
I'm using AWM 11.2.0.1.0 on Oracle 11g R2 server.
Thanks,
RK

David,
I looked at the data and found out that there were NULLs in many key columns. I updated all of them to the value 'Unknown'. Also I re-implemented Composite keys because I thought Type 2 dimension would pose problem in determining uniqueness. Now there are no errors and I could successfully load data into the dimension.
Below is the latest definition
<!DOCTYPE Metadata [
<!ENTITY % BIND_VALUES PUBLIC "OLAP BIND VALUES" "OLAP METADATA">
%BIND_VALUES;
]>
<Metadata
Version="1.2"
MinimumDatabaseVersion="11.2">
<StandardDimension
Name="SKU"
ETViewName="SKU_VIEW"
ETKeyColumnName="DIM_KEY"
ETLevelColumnName="LEVEL_NAME"
ETMemberTypeColumnName="MEMBER_TYPE"
ETDimensionOrderColumnName="DIM_ORDER"
DefaultHierarchy="PRODUCTS"
ETHierarchyOrderColumnName="HIER_ORDER"
ShortValueDescriptionAttribute="SHORT_DESCRIPTION">
<Organization>
<AWPrimaryDimensionOrganization
AW="&AW_NAME;"
AddUniqueKeyPrefix="True"
MVOption="NONE"
HierarchyConsistencyRule="CONSISTENT">
<MVCreationOptions
RefreshType="COMPLETE"
RefreshOn="DEMAND"
UsingConstraintsClause="TRUSTED">
</MVCreationOptions>
<DefaultBuild>
<![CDATA[BUILD SPEC SYS_DEFAULT
LOAD,
COMPILE
)]]>
</DefaultBuild>
<AttributeOrganization
Attribute="SHORT_DESCRIPTION">
</AttributeOrganization>
</AWPrimaryDimensionOrganization>
</Organization>
<DimensionLevel
Name="MERCHDIVISION"
ETKeyColumnName="MERCHDIVISION">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
</DimensionLevel>
<DimensionLevel
Name="MERCHGROUP"
ETKeyColumnName="MERCHGROUP">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
</DimensionLevel>
<DimensionLevel
Name="PRODUCTGROUP"
ETKeyColumnName="PRODUCTGROUP">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
</DimensionLevel>
<DimensionLevel
Name="STYLE"
ETKeyColumnName="STYLE">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="STYLE">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="STYLE">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="STYLE">
</Description>
</DimensionLevel>
<DimensionLevel
Name="PRODUCT"
ETKeyColumnName="PRODUCT">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCT">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCT">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCT">
</Description>
</DimensionLevel>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="sku">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="sku">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="sku">
</Description>
<Hierarchy>
<LevelHierarchy
Name="PRODUCTS"
IsSkipLevel="True"
IsRagged="True"
ETParentColumnName="PARENT"
ETDepthColumnName="DEPTH"
ETViewName="SKU_PRODUCTS_VIEW">
<HierarchyLevel
DimensionLevel="MERCHDIVISION">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="MERCHGROUP">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="PRODUCTGROUP">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="STYLE">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID || DIMSKU.STYLE"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID || ':' || DIMSKU.STYLE">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="PRODUCT">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID || DIMSKU.STYLE || DIMSKU.SKU"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID || ':' || DIMSKU.STYLE || ':' || DIMSKU.SKU">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
</LevelHierarchy>
</Hierarchy>
<Attribute>
<BaseAttribute
Name="SHORT_DESCRIPTION"
IsVisibleForAll="True"
SQLDataType="NVARCHAR2(100)"
ETAttributeColumnName="SHORT_DESCRIPTION">
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="Short Description">
</Description>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="Short Description">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="Short Description">
</Description>
<Classification
Value="STAR"/>
</BaseAttribute>
</Attribute>
</StandardDimension>
</Metadata>
But I'm facing problem if I put Names in Short Description attribute. I have fields MerchGroupName, MerchDivisionName, ProductGroupName, StyleName in the database table which I would love to use for short description. When I use them, the error is
INI: error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>INI: XOQ-01600: OLAP DML error "ORA-34034: 1 is already a value of DEMANTRADW!SKU_MERCHDIVISION_SURROGATE." while executing DML "SYS.AWXML!R11_LOAD_DIM('SKU.DIMENSION' SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) 'MATCH' 'YES' 'YES' 'SKU.MERCHDIVISION.LEVEL' 'SKU.MERCHGROUP.LEVEL' 'SKU.PRODUCTGROUP.LEVEL' 'SKU.STYLE.LEVEL' 'SKU.PRODUCT.LEVEL' 'SKU.SHORT_DESCRIPTION.ATTRIBUTE' 'SKU.PRODUCTS.HIERARCHY')", Generic at TxsOqStdFormCommand::executeINI: XOQ-01601: error while loading data for Cube Dimension "CUBE_DEV.SKU" into the analytic workspace, Generic at TxsOqStdFormCommand::execute

Issue with Skip Level Hierarchy in OBIEE 11g

Hi,
I have implemented Ragged and Skip Level Hierarchy as explained in the links below in OBIEE 11g RPD.
(checked the 'Ragged' and 'Skipped Levels' check boxes)
http://www.rittmanmead.com/2010/07/obiee-11gr1-support-for-ragged-skip-level-value-based-hierarchies/
http://docs.oracle.com/cd/E17904_01/bi.1111/e10540/dimensions.htm#BABFBBFG
When the Presentation Hierarchy is dragged in the OBI Answers, the leaf level beyond the skip (null) levels is not shown in the report.
When any level finds intermediate null values, OBIEE is failing to show the existing value of the leaf level (Most Granular Level) or any values after Skipped Levels.
For example, following is the values in database for different levels of department hierarchy.
A -> B -> C -> Null -> Null -> F
The OBIEE Presentation Hierarchy can only drill down till C, not beyond that. (does not show the leaf level value 'F').
Could you please suggest whether I am missing any step?
Thanks.

Hi, My problem is that in my report it is showing me that levels as -- A -> B -> C -> Null -> Null -> F, however I want to show data as A -> B -> C -> F, i.e the null valus(columns) should be skipped. Please help.
Thanks and Regards,
Deepak

WC27 - Single Item, Single Level(?)

Hello,
I would just like to ask if there is a way in transaction WC27 (for MRP Batch Run) to only run Single Item, Single Level Materials during processing?
I ask because I have a requirement (in addition to filtering material codes) to only run single item, single level entries for WC27 similar to MD03 but the customer wants the batch run feature.
Hope to hear from you soon.
Regards

Hi,
As it is correctly answered by the gurus above that it's difficult/not possible to run Batch structured MRP for only run Single Item, Single Level plannings..
Hoiwever it can be mapped with the help of ABAPer to ask him/her to do some coding for standard report RMMRP000 .this is a standard ABAP report available within your SAP system (depending on your version and release level). there is also some standard documentation available for this report and a few details of other objects it interacts with such as tables, function modules, includes etc. If you would like to see the full code listing simply enter the object name( RMMRP000 ) into the relevant SAP transaction such as SE38 or SE80
Within the comments section below there is also an opportunity for anyone to be able add useful hints and information specific to this SAP object. This means that you and other users will be able to find these details quickly by simply searching on the object name.
Hope it could work for you.
All the best!
Regards
Chandra

ML single-level determination problems

Hi,
we have some problems about single-level determination:
category                        quantity                  prelimval                   price diff             price
Beginning Inventory      55,821,791.824      4,326,188.88            0.00                     77.50
Receipts                        84,472,000             7,301,759.68            3,116,204.28      123.33
   Cumulative Inventory 140,293,791.824    12,126,995.37          3,116,204.28      108.65
Consumption                 93,890,170             8,115,866.30            2,085,487.50       108.65
     Not Allocated           0                             0.00                          *592,153.96*
     Production               48,880,000              4,225,187.20            *493,568.10*
         6.1111004 LG01 387,000                   33,452.28                 8,596.04              108.65
         6.1111009 LG01 693,000                   59,902.92                 15,392.91            108.65
         6.4510111 LG01 39,939,000              3,452,327.16            *298,671.23          93.92*
         6.1111005 LG01 387,000                   33,452.28                 8,596.04              108.65
         7.5710050200 LG01 94,000               8,125.36                   2,087.93               108.65
Ending Inventory          46,403,621.824       4,011,129.07            1,030,716.78        108.65
material 6.4510111 was allocated 298,671.23, but 887,124.66 (2,085,487.50 * 39,939,000 / 93,890,170) is the correct amount, who can tell me y ? tks..

Hi
Single level price determination is to calculate the unit price of material for a period. It takes into account the price differneces arising out of Price Differences like GR/IR Differences, Exchange Rate Differences, and revaluation differences to calculate the actual price of a material.
You can have more information of Single Level Price Determination at the following link:
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb4f37455611d189710000e8322d00/frameset.htm
Regards,
Suraj

Single level planning

What setting to be done for single level planning of following BOM.
M1
    M1.1
           M1.3
    M1.2
           M1.5
When MRP is run for M1...it shud create planed order for M1 only.....and when MRP is run for M1.1 then it shud create planed order for M1 .1 only...similarly for M1.2.

JJ,
Lets see, you are using ETO, which by design is a multilevel planning process, using project/WBS as MRP segments, but you want to only plan the first level, and then the second level, at your discretion?
Standard SAP does not support this requirement. To me, it seems to defeat the whole concept of project planning. However, I will assume that you have a valid business requirement.
I suggest you speak to your developers to create a specialized selection userexit for MD01. You could craft it to select only M1 material. You could also craft it to select only M1.* materials on a subsequent run. Specifications of the selection process would have to be created by you.
Standard userexit for MD01 can be found in IMG>Production>MRP>Planning>User Exit Material Selection for planning run.
Rgds,
DB49

Aggregation level on single level basis or multiprovider

Hello,
we use IP 7.0 and have a planning cube for CO-PA data, as well as a multiprovider combining the actual cube and the planning cube for COPA data. We need to implement a planning tool in which planning simple planning functions are needed on the single basis (copy, revaluation, multiply,manual planning ...) as well as on the multi-provider (top-down with reference data).
-> on which level(s) should we define the aggregation level? Do we need to define it on the multiprovider (in order to do the top-down) or can we split it up (single level and multi-provider) and define a workbook with a manual planning function on the single level AND including the top-down based on the multiprovider?
thanks
Dries

I agree with Gregor,
I think it is more logical to configure your Aggregation Level on top of your Multi-Provider, especially since you already have a need to view ref data from Actuals to perform calculations on your Planned. You can always restrict your 'simple' functions to the appropriate InfoProvider.
As for the FOx question, you can always restrict to each InfoProvider when writing your FOx (either inside the FOx code or using the FOx conditions).
Regards,
Zane

FCC for Multi-level Hierarchy

Hi Friends,
Can someone please help me out with this.Below is my Sender Data Type which needs to be converted:
DT_TRAC_MESG
(Hierarchy 1)         TRAC_INFO
                  (Hierarchy 2)   TRAC00
                     (Hierarchy 2)GROUP1
                                (Hierarchy 3)TRAC05
                                (Hierarchy 3)GROUP2
                                             (Hierarchy 4)TRAC10
(Hierarchy 4)                                             GROUP3
                 (Hierarchy 5)                                         TRAC11
and my input data is as below :
XXXXXXXXX TRAC00 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (occurance 1)
XXXXXXXXXXXXXXXXXXTRAC05XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (occurance 1)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC10XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC10XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC10XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
I know Std SAP XI doesnt support more than 3 hierarchies but we are using a JMS adapter and this support more than 3 hierarchies.So please help us in achieving this mutli hierarchy conversion.Please atleast provide me the procedure to convert a 3 level Hierarchy structure.
It would be of great help for me if someone can answer this and asap.
Thanks & Regards,
Pradeep.

Hi
follow this weblog
File Content Conversion for Multi Hierarchical Structure
or
you can use seeburger to use multi level hierarchy
SAP PI/XI : Content conversion using Generator mapping functionality of SeeBurger : Part 1.
SAP PI/XI : Content Conversion using Generator mapping functionality of SeeBurger : Part 2.
regards
sandeep
Edited by: sandeep sharma on Dec 15, 2008 10:45 AM

OBIEE 10g - Ragged & Skip Level Hierarchy

Hi Frnds,
I'm aware of the fact that OBIEE 11g supports Ragged & Skip Level Hierarchy. But I'm looking for some heads up while implementing the same on OBIEE 10g using Oracle DB as source. I have done this before for Essbase Data Source but now waiting for my Oracle dataset for design.
Has anyone actually implemented in Real Time Project? Pls share your challenges like:
- Dimensional Hierarchies Challenges
- Drill Down Challenges
- Report Challenges
Thanks,
Deepak
Edited by: Deepak Gupta on Aug 11, 2011 5:18 AM

Deepak,
10g does not handle the idea of Skip hierarchies and the ragged hierarchies definitely has its limitations.
We've implemented several projects using Essbase and SAP BW for Oracle BI 10g. The biggest issue is that in Answers creates a new column for each drill down selection when attempting to navigate down a hierarchy. Though this is klugy it does work and provides the data the user is looking for. It is however, not aesthetically please when compared to other tools or now Oracle BI 11g which satisfies this issue with a native drill-down tree folder structure.
My opinion and advice would be to upgrade to 11g as soon as possible to enjoy these new features.

Ragged Hierarchy and Skip Level Hierarchy

Hi all,
I am confused with ragged and skip level hierarchy, as i read some documents related to obiee 11g.
Will you please explain with an example the difference between ragged hierarchy and skip level hierarchy and also when to use these hierarchies?
regards
chandra kanth.

Chandra Kanth,
Hope this helps you
http://blogs.simba.com/.a/6a00e3932f172e88340133f4d758b5970b-800wi
Thanks,
Saichand.v

OBIEE Essbase skip-level hierarchy

Is it possible to setup OBIEE and Essbase to be able to model skip-level hierarchy? It is obvious with connection to the relational database. How the essbase should designed and populated with data to faciliate this type of hierarchy?

Refer this http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/overview/obiee-essbase-modeling-guide-130897.pdf for Modeling. And for any Essbase releated question post it in Essbase forum Essbase

Material ledger single level run error

Hi All,
During last month ML run, we faced a problem. For some of the Material of certain Material Type even Single level run could not be done. On analysis we found that for these materials previous periods ML run was not done. We are not sure why in previous months system did not select these materials for ML. Because in the Change data for Material master there is nothing of that sort which discriminate those materials in the earlier periods but picked the same in the last period.
Now we have closed last month ML with errors for those materials, but we cannot let this continue for future months.
Can any one tell me how to exclude those materials in future runs, because those materials are not to be used for any movement in future and the stock balance has already been made to zero.
And give the probable cause, or where can we find the reason why those materials got picked last month ML run but not in periods prior to that.
Regards,
Vaskar

Thanx Karl,
Firstly this is to inform you that for most of those materials there has not been any movements for past few months and not even in the last month. So I am not able to understand what change has triggered system to select those materials in the last month but left out in prior periods.
Secondly I am not able to understand the MLHELP_SET_PP_STATUS_70 thing. I have never used it and I am not sure whether we have it installed or not. Is it an add-on to standard SAP? Please tell me how can we run that report. Or if not installed, is there any other way by which we can change the status of the Material to 70.
Thanks
Vaskar

Can I use User Exit u2013 IWOC0004 u2013 Change Single-Level List for TCODE IW37N?

Hi All,
Can I use User Exit u2013 IWOC0004 u2013 Change Single-Level List for TCODE IW37N?
In documentation of the User Exit I can see that I can use this user Exit for IW37(Program - RIAFVC20) , but I want to use this for IW37N (RIH_ORDER_OPERATION_LIST).
Please tell me is it possible.
With best regards,
Narendra

Hi Pete Sir,
I am on 4.7 , how to work with it. I am going to use screen exit IW0110018 and I want to add User fields in the IW37N.
Thanks with best regards,
Narendra

Upload single level variable cost in SNP PPM in mass by MASSD

Hi experts,
I am trying to upload single level variable cost in SNP PPM in mass by MASSD by following selections:-
Selection
Object Type:- PPM
Selction Criteria:-
Component:- Plan        Attrib:- Use of Plan
Component:- Plan        Attrib:- Plan
Components & Attributes to be Maintained
Component:- Plan        Attrib:- Var.Sing.Lvl Costs
While maintaining the cost, under selection criteria, compoment: PLAN and attribute: PLAN I am unable to maintain multiple plan names.
The single level variable cost that I have to maintain for all these plans is the same and therefore was trying to use transaction MASSD
Can you please throw some light on how multiple PLAN selections can be done?
Regards
Chetan

DEAR GURUS,
*There is a question regarding the resoucre consumptions relevant to PDS in SNP,*
****The inputs are:****
****1) Base Qty= 7700 TH****
****2) Set Up =45 MIN****
****Resource consumed by operation activity is 112 207 seconds = 31,17 hours.****
****Unfortunately we didnu2019t understand how this figure is calculated.****
****Can you please help us in this****

Single level price determination in material ledger

What is the meaning of single level?Doe it include only the price determination of procured raw materials or will it also include semi finished and finnished goods?

Hi
Single level price determination is to calculate the unit price of material for a period. It takes into account the price differneces arising out of Price Differences like GR/IR Differences, Exchange Rate Differences, and revaluation differences to calculate the actual price of a material.
You can have more information of Single Level Price Determination at the following link:
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb4f37455611d189710000e8322d00/frameset.htm
Regards,
Suraj

Single level hierarchy

Similar Messages

Maybe you are looking for