Product : Errors in attribute hierarchy structure SAP BCA 000164

Hi All ,
When ever i create /Display /Change Product in
Financial Supply Chain Management --> In House Cash > Master Data>Product Definition--> Product --> Create /Change/Display
system through below mentioned error .
I tryed to resolve problem as per below mentioned program through se38 , but still getting same error
Errors in attribute hierarchy structure SAP BCA 000164
Message no. FIPR217
System Response
An error was found in the attribute hierarchy.
In some cases, it is not possible to display the attribute hierarchy without having to correct the errors first.
Procedure
It is recommended that you run the FIPR_CLEAN_ATTRIBUTES (by using transaction SE38). This report can recognize errors, and it attempts to correct them automatically.
Caution: This report can change your table entries permanently.
Once this report has run, you need to check the hierarchy structure, and make any necessary changes.
Regards
Prakash Sharma

Hi,
the realignment (KEND) does not change the line item tables (CE1***, CE2***), thats why they remain unchanged.
The line items in CE1**** can not be changed. If you really want to have new line items (with the new prod. hierarchy) try in test-client if the use of report RKECADL1 and the new transfer to CO-PA for the deleted line items (KE4S, KE4SFI,...) can help you (SAPNET-note 69370 for details).
CE2**** + SQL-error: As per now, I don't have an idea how to deal with that cases.
best regards, Christian

Similar Messages

Error in the hierarchy structure - Data Load Failure

Hi
We are having a regular Master data hierarchy Full load: 0WBS_ELMT. This data load is from the SAP R/3 source system. It was failed today with following message:
Error in the hierarchy structure
Node ID 00016749 does not exist.
Node ID 00005867 starts an endless loop
Node ID 00001367 has not been included in the hierarchy
Can any one help me out to solve this issue?
Best Regards,
Venkata.

hi,
refer to this thread.
No hierarchy displaying in the Maintain Hierarchies

Error in the Hierarchy structure

Hi All,
We faced error an hierarchy load. Error records written to application log.The level of the node ID 000284 does not suit the lev. of the higher lev. node.
Help to solve this error.
Thanks,

Hi Hema latha...
Please find the below link this may helpful ........
http://help.sap.com/saphelp_nw04/helpdata/EN/80/1a6729e07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/52/671595439b11d1896f0000e8322d00/frameset.htm
/people/kristoffer.engh2/blog/2007/04/03/roles-and-authorizations
Regards
Sudheer

How to Report a product error in SAP Business One

Hi Experts
I have found a product error in SAP Business one
i need to know how it can be notified to SAP
Thanks
Krish

Hi Krish,
If You Post a Meessage to SAP Support Center
Require S-user ID and Password
First post a message to SAP Support Center with what problem you are facing.
then he analyse your problem and told its a BUG or some other workaround.
Check the following thread
Re: How to Send message to SAP Support center
*Close the thread if issue solved.
Regards
Jambulingam.P
Edited by: Jambulingam P on Aug 13, 2009 12:35 PM

Product Group Hierarchy in SAP BI for 0SD_MP03

Hello Guru,
I am working on BI 7.0. I have activated Sales Infocubes, DSO and Multiprovider on BI side. I am working on 0SD_MP03 multiprovider. I have a field called 0PROD_HIER which represents Product Hierarchy which we can see for any material in MM03 t-code. how ever in MM03 t-code we can go upto 3 level (Main Group, Group and Sub group) how ever on BI side we can see only 1 level.
I want to see all 3 levels when i click on 0PROD_HIER because i want to see a relation of a material and it belongs to which main group and group but i see that there is no standard content for Product Hierarchy in SAP BI or ECC . Can any body help me on how to get this hierarchy on BI side ?
Regards,
Komik Shah
Edited by: komik shah on Nov 30, 2010 7:51 AM

Hi Mti,
Thanks for your reply.
I have done 2 scenarios which is mentioned below..
1, I created a hierarchy for 0MATERIAL info object with 0MATERIAL_LPRH_HIER data source. I ran infopackage and it showed a popup "DATA WAS REQUESTED" but when i went to Hierarchy symbol -> Maintain Hierarchies, i am not able to see any hierarchies there.. am i missing something ?
2. I have activated 0PROD_HIER_LPRH_HIER dat sorce ECC. replicated it on BI side and created transfer rules wit 0PROD_HIER infoobject. I created infopackage and it has shown me hierarchy in selection. I ran infopackage and it said that "DATA WAS REQUESTED" but i din't see any hierarchies in RSH1... am i missing something here as well ?
You help is much appeciated in advance.
Regards,
Komik Shah

Error : No basis hierarchy for product type 01

Hi
When i am trying to create product hierarchy in CRM 5.0 the following error
"no basis hierarchy for product type 01" is futuring in the system,I would rquest you help in this issue.
Regards
Krishna

Hi All,
While congiguring the material system showing the same mssg like "No basis hierarchy for product type 01". Even If I created the hierarchy. Plz any body is there to solve this issue.
Thanx
Chinmaya

Report designer error for hierarchial structure on Columns

Hello,
I have a query with a structure in rows and another one in columns. I also have a 0COMPANY hierarchy Dimension within the Columns.
When I insert the data provider into a report designer report, I receive the following error:
"Query contains a hierarchial structure on Column(s)..."
Has any one encountered this issue before? Is there a note or workaround available?
Thank you.
Sri Yalla

Hi,
the report designer need to have a fixed number of columns. If you have a Hierarchical Structure in the Columns, the number of columns can change. Therefore Report designer does not allow to use this DP in this drill down. You should place the Row structure to the columns and the hier-structure to the rows. then it should work.
best regards,
kai

BI Production errors

Hi,
Can anybody please give me SAP-BI Production Issues pdf,
i search on google t i got BW Production Isusues pdf. but i want exclusively bi production error pdf.
Thanks and Regards.
Asim.
this is a commonly discussed topic - please search the forums before posting

. Time Stamp errors:     This can happen when there is some changes done on data source and data source is not replicated.
Execute T code SE38 in BW give program name as RS_Transtruc_Activate_All and execute the program. Give Info source and Source System and activate. This will replicate the data source and its status is changed to active. Once this is done, delete the request by changing technical status to red and trigger Info package to get delta back from source system.
2. Error log in PSA- Error occurred while writing to PSA: This is because of corrupt data or data is not in acceptable format to BW.
Check the cause of the error in Monitor in Detail tabsrip.This gives the record number and Info object having format issue. Compare the data with correct values and determine the cause of failure. Change the QM status of request in data target to red and delete the request. Correct the incorrect data in PSA and then upload data into data target from PSA.
3. Duplicate data error in Master data uploads: This can happen if there are duplicate records from the source system. BW do not allow duplicate data records.
If it is a delta update, change the technical status in the monitor to red and delete the request from the data target. If it is full upload delete the request.
Schedule again with the option in the Info package, u201Cwithout duplicate datau201D for master data upload.
4. Error occurred in the data selection: This can occur due to either bug in the info package or incorrect data selection in the info package.
Data selection checked in the info package and job is started again after changing the technical status to red and deleting the error request from the data target.
5. Processing (data packet) Errors occurred-Update (0 new / 0 changed): This can be because of data not acceptable to data target although data reached PSA.
Data checked in PSA for correctness and after changing the bad data uploaded back into data target from PSA.
6. Processing (data packet) Errors occurred-Transfer rules (0 Records): These errors happen when the transfer rules are not active and mapping the data fields is not correct.
Check for transfer rules, make relevant changes and load data again.
7. Missing messages - Processing end Missing messages: This can be because of incorrect PSA data, transfer structure, transfer rules, update rules and ODS.
Check PSA data, Transfer structure, transfer rules, Update rules or data target definition.
8. Activation of ODS failed: This happens when data is not acceptable to ODS definition. Data need to be corrected in PSA.
Check for Info object which has caused this problem in the monitor details tab strip. Delete request from data target after changing QM status to red. Correct data in PSA and update data back to data target from PSA.
9. Source System not available: This can happen when request IDOC is sent source system, but the source system for some reason is not available.
Ensure that source system is available. Change technical status of request to red and delete request from data target. Trigger Info package again to get data from source system.
10. Error while opening file from the source system: This happens when either file is open or file is not deposited on server or not available.
Arrange for file, delete error request from data target and trigger Info package to load data from file.
11. While load is going on in R/3 table is locked: This happens when some data source is accessing R/3 transparent table and some transaction takes place in R/3.
Change the technical status of job to red in the monitor and retrigger the job again from R/3.
12. Object locked by user: This can happen when user or ALEREMOTE is accessing the same table.
Change the technical status of job to red, delete request from data target and trigger Info package again. If its delta update it will ask for repeat delta, Click on Yes button.
13. Process Chains Errors occurred in Daily Master Data: This occurs when Transaction data is loaded before Master data.
Ensure to load Master data before Transaction data. Reload data depending on update mode (Delta/Full Update)
14. Processing (data packet) No data: This can be because of some bug in Info package, rescheduling with another Info package corrects the problem.
This type of problem we can solve with copy the Info package and reschedule the data.
15. Database errors Enable to extend Table, enable to extend the Index: This is due to lack of space available to put further data.
16. Transaction Job Fails Giving Message: u201CNO SID FOUND FOR CERTAIN DATA RECORDu201D is due to some illegal characters for the Data records.
17. Error Asking for Initialization: If you want to load data with the delta update you must first initialize the delta process. Afterwards the selection conditions that were used in the initialization can no longer be changed.
18. Job Failure at Source System: Go to the background processing overview in the source system. You can get to this with the Wizard or the menu path Environment -> Job Overview -> In the source system (This is the alternate path to see the u201CJob Overviewu201D at the Source System.)
    At source system you can see the reason for the Job Failure. Thus we need to take the action accordingly.
19. Invalid characters in load: BW accepts just capital letters and certain characters. The permitted characters list can be seen via transaction RSKC.
There are several ways to solve this problem:
1)     Removing erroneous character from R/3 (for example required vendor number that need to be changed can be found from PSA from line shown in error message)
2)     Changing or removing character in update rules (need to done by ABAP)
3)     Putting character to BW permitted characters, if character is really needed in BW
4)     If the bad character only happens once then it can be directly change/removed by editing the PSA
5)     Put ALL_CAPITAL in permitted characters. Needs to be tested first!
Editing and updating from PSA, first ensure that the load has been loaded in PSA, then delete the request from the data target, edit PSA by double clicking the field you wish to change and save. Do not mark the line and press change this will result in incorrect data. After you have corrected the PSA, right click on the not yet loaded PSA and choose u201Cstart immediately.u201D
20. Update mode R is not supported by the extraction API: This happens for loading of delta loads of MD attributes. Why has not been covered. Replicate the data source. Use SE38 and function module TRANSTRU_ACTIVATE_ALL.
Subsequently perform an initial load.
1.     Go to the info package.
2.     Delete the previous initial load
3.     Load the initial
4.     After the initial is successful check the solution by loading a delta
Thanks & Regards
Praveenyagnamurthy

Hierarchy structure changes

Hi All,
I have one requirement at clent site where hierarchy structure changes i.e. parent child relation switches or changes from one level to another level. For example WBS element hierarchy stucture for project 101014 is:
101014--root
101014-1>101014-1-01>101014-1-01-02-->101014-1-01-02-01
after above hierarchy load to bw there are chances that hierarchy nodes change their positions.
i.e.above hierarchy node 101014-1-01 can be removed from parent(101014-1) and assigned to 101014-2.
In Next load Hierarchy need to realign/restructure according to new hierarchy tree from ECC system. Right now we are BW 7.30. Thanks for you help and gurantee of points.
Regards,
Reddy

Hi Gaurav,
Thanks for quick response, we are running process chain on daily basis which will trigger full load from ECC to BW. I thought the same but when I look below error message I think we need to some how delete hierarchy data and reload with restructed or realigned data. Please find below error details and once again thanks for your help.
Node ID 00001564 has not been included as a sibling node or as a child node
Message no. RH207
Diagnosis
The node with the ID 00001564 and the node name 101014-1-02-03 is not used as a child node (field CHILDID) or a sibling node (field NEXTID) by any node in the hierarchy. The node is also not a root node because the ID of the parent node 00001565 (field PARENTID) is not equal to 0. The node is therefore not linked into the hierarchy. Therefore the node is not connected to the hierarchy.
Procedure
This message is displayed in addition to message RH 242. The node is the root node of a subtree that is not connected to the hierarchy. For further details, see the long text for message RH 242.
4 of a total of 13,846 nodes are not included in the hierarchy
Message no. RH242
Diagnosis
The root nodes are the starting point for moving through the hierarchy. The content of the fields NEXTID and CHILDID is used to move from the current node to its sibling and child nodes.
4 out of a total of 13,846 nodes cannot be reached by moving through the hierarchy in this way. These 4 nodes are not connected to the hierarchy.
System Response
The hierarchy is not consistent and therefore cannot be activated.
Procedure
The cause of the problem is usually incorrect links to sibling nodes (field NEXTID) or child nodes (field CHILDID). An incorrect value often means that an entire subtree (consisting of several nodes) is not included in the hierarchy.
To simplify the search for incorrect links, the system identifies the nodes (from all the not connected nodes) that are not used as sibling nodes or as child nodes. These nodes are usually root nodes of subtrees that are not connected to the hierarchy. You can find these nodes in the RH 207 messages that follow.
Try to localize the problem by using the RH207 messages for help. If the hierarchy is loaded from an SAP source system, you can check whether the extracted data is correct by executing transaction RSA3 in the source system. If necessary, check if the data is modified with a user exit. If the hierarchy is loaded from a file, check the contents of this file. The problem might also be due to an error in the transfer rules or in the transformation.
Thanks
Reddy

Hierarchy structure with temporal hierarchy join

Hi guys,
For characteristic Cost Element, Im using a time dependant hierarchy structure with temporal hierarchy join. In the query, Im selecting select hierarchy and From data, derivation.
If the hierarchy is created in SAP BI or if the hierarchy is imported from Excel, query is working properly.
If the hierarchy is imported from SAP ECC, the query giving me an error:
ABEND BRAIN (336): Hierarchy "xx" from characteristic 0COSTELMNT can be used here
Someone can tell me if its normal or if there is a way in order to correct this problem.
Thanks in advance,
Rubé

Hi guys,
For characteristic Cost Element, Im using a time dependant hierarchy structure with temporal hierarchy join. In the query, Im selecting select hierarchy and From data, derivation.
If the hierarchy is created in SAP BI or if the hierarchy is imported from Excel, query is working properly.
If the hierarchy is imported from SAP ECC, the query giving me an error:
ABEND BRAIN (336): Hierarchy "xx" from characteristic 0COSTELMNT can be used here
Someone can tell me if its normal or if there is a way in order to correct this problem.
Thanks in advance,
Rubé

How to rectify the error while creating hierarchy

Hi
I am working on creating a hierarchy for an info object IO_SREP. I am using the book SAP BW - A Step-by-Step guide written by Biao Fu, and Henry Fu. As mentioned in the book
1. I double clicked the info object Sales representative ID then I got the screen Change characteristic IO_SREP:Detail.
2.     Accordingly as mentioned I selected the Hierarchy tab wherein I clicked the check box with hierarchies and the radio button Hierarchy structure time-dependent.
3.     I successfully checked and activated the screen and hit the back button which took me to the screen Administrator Workbench: Modelling.
4.     <b>As mentioned in the book now I right clicked on the info object Sales representative ID and selected Create Hierarchy option.
At this stage I am getting the error The import parameters were not filled correctly. When I clicked on the question mark for help I got the screen Performance Assistant with the message The import parameters were not filled correctly Message no. RH032.</b>
But as per the book the screen Create Hierarchy should open. Can anyone please guide me as to where I am going wrong and what should I do to proceed further?
Thank you.
TR.

Try transaction RSH1 to create the hierarchy. If you are on 3.0A, this might be due to program error (OSS note 511004).

How Can I report a Production Error

When I want to report a Production error in Support portal, I got a error like this
Currently you do not have authorization to use this function. To request the authorization, please contact one of the administrators at your company:
S0004554480 Bool
But I am Bool actually, it's myself. how can I handle it? Does any know it?
Any response is appreciated.

Hi,
As per your query you are not authorised user to log a compliant on SAP Workplace. Please contact your old SAP Basis person who is working earlier you. If you are not getting any support form him then sand a latter to SAP through your Director or CEO who is responsible person. Then sap will enquiry over the phone and ask some hardware information to you, if you fullfil then the will assign the password or create new user for you.
Anil

Systems no longer exist on Report A Product Error page

When I go to SAP Support Portal and click "Report a Product Error" I am prompted to choose the system I am submitting a request ticket for.
When I use either search feature, my system (SBOP formerly known as EPM-PLA in the SAP universe) is not available. Previously I had two systems available - development and production - and now there are none and I can't even proceed.
What happened and what am I supposed to do now? Also, when I go to my message Inbox there are no messages even though I have submitted many tickets and communicated with the support several times before.

I didn't expect any support personnel to read it and respond or provide assistance but I did expect somebody might have an answer. Why would our installed systems suddenly change without authorization?
Thanks

Org unit Hierarchy structure at Key date

Hello Friends,
We have an issue with displaying HR Org unit hierarchy structure between two calendar months.
The BI Report has a selection parameter to select Org unit hierarchy , Calendar month From and Calendar month To
The BI Report is to display the no.of sick absence days for employees in a chosen Org unit hier.
Employee A had a sick absence of 5 days in the month 04.2011 in the Org unit X . The same employee had a sick absence of 4 days in 05.2011.The Org unit X then delimit in 05.2011 , the Org unit X is no longer in Org structure from 05.2011.
When we run the report for 04.2011 to 04.2011 , the employee A is showing absence   under Correct Org unit ie X with correct Org structure .
When we run the Report for 05.2011 to 05.2011 , the employee A is showing absence under hierarchy Org unit Not assigned which is OK .
But the issue is when we run the Report from 04.2011 to 05.2011 , The employee A absence days 9 (5 +4 ) showing under Not assigned Org unit hierarchy structure which is the latest Org unit .
When I deactivate the Org unit hierarchy and choose tech name of Org unit , It is showing correct Org unit key
But The user would like to see 5 days under org unit X and 4 days under Not assigned with Correct Org unit hier structure when we run the Report from 04.2011 to 05..2011 .
We have a user Exit variable for the Key date in the Bex Report which seems to be taking only one date at any time .
Is there any way to get the correct figures under Org unit hier structure where employee had absence in when we put range of calendar months on a selection screen ?
Any advice appreciated.
Thanks.

Hi,
You can try adding two more attributes to Org Unit as "Calender month from" and "Calender month to".
In these attributes maintain the validity period for the corresponding master data.
For example, in your case you can maintain the master data as:
Employee | Org Unit | Calender month from |Calender month to | sick absence
A | X | 4.2011| 4.2011 | 5 days
A |    | 5.2011 | 05.2011 | 4 days
And in report use variables for Calender month from" and "Calender month to".
Hence, when user executes the report with selection as:
Calender month from" = 04.2011
"Calender month to"    = 05.2011
The data will be read from master data based on these selections along with key date and report will show output as expected.
Employee | Org Unit | Calender month from |Calender month to | sick absence
A | X | 4.2011| 4.2011 | 5 days
A |    | 5.2011 | 05.2011 | 4 days
Hope this works for you.
Regards,
Geetanjali

Error message - attributes of the user inconsistent or not defined

Hi,
We are in SRM 7.0 have created new plant and some users assigned to this plant.
However when logged into portal page, it gives the error message ' Attributes of the user inconsistent or not defined' see PPOMA_BBP.
When checked in the org structure the data entered are correct.
What could be the reason for this error message.
Rgds,
Madhan

Hi,
Please check the following in the org structure in PPOMA_BBP for the users
1. Check whether the attribute for the ITS --URL is given.
2.Check the attribute for the company code is given.
3.Check whether the Roles for the users is given
in addition go to the check tab and check if any Red mark are there.
correct those attribute.
The error is basically related to the PPOMA_BBP only
Regards
G.Ganesh Kumar

Product : Errors in attribute hierarchy structure SAP BCA 000164

Similar Messages

Maybe you are looking for