PO Hierarchy Setup

Hi,
We are Oracle 11.0.3. Would like to know if anyone has setup the hierarchy such that individual personal assistant can make the changes to hierarchy? As an example, Dept A has sub-depts A1, A2. Each dept and sub-depts has their own personal assistant(PA) say PA1 for dept A, PA2 for sub-dept A1 and PA3 for sub-dept A2.
1) Can we setup the hierarchy such that PA2 can only see the hierarchy for sub-dept A1 but cannot see the hierarchy for Sub-dept A2 and vice versa for PA3?
2) PA1 should be able to see the whole hierarchy.
If the above can't be setup, anyone has the experience to customize it?
Thanks for your reply.

Oracle Purchasing hierarchy will not look at the DFF. It will go only by your hierarchy setup (either position based or emp-supervisor based.)
Sandeep Gandhi

Similar Messages

Customer Hierarchy setup

HI Experts,
Please guide me how to setup the customer Hierarchy in system and what is the table for customer hierarchy.
thanks in advance.
Vivek.

Hi,
The table for customer hierarchy is KNVH.
All the customizing is in SD/Master Data/Bussiness Partner/Customers/Customers hierarchy
1) Define hierarchy type: just put and ID and a name to the new hierarchy.
2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this informacition, in the order, you obtain the bussiness partner for each partner function.
3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses hierarchy in pricing determination.
It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
Customer hierarchy setup, firstly decide the hierarchy type to be used.
The standard is type A.
You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
regards
Vivek.
Edited by: Vievk Vardhan on Dec 7, 2009 1:02 PM

Dimension Hierarchy Setup

Hi
I am new to BusinessIntelligence.
I have business model 3 dimension table(package, incident, product) and one fact table. I want to apply hierarchy in a order of package #, incident# and product #.
I right click businessmodel and select new object->Dimension
I applied in the order and last level as product #.
When I did chekc consistency it throws error as....
BUSINESS MODEL IDS:
[nQSError: 15001] Could not load navigation space for subject area IDS.
[nQSError: 15003] Missing most detailed table for dimension tables: [Incident,Package].
Please let me know If I miss something

Dimension hierarchies can only use one Logical Dim table.. It sounds like you trying to build a hierarchy that contains 3 different logical dim tables ?
If so, create 3 individual hierachies and use the 'prefered drill path' to jump from one to the other, in the order you want ( package -> incident -> product )

Advise on median MDX query and/or dimension hierarchy setup

Hey guys,
I have a fairly weird situation with SSAS/Dimension Hierarchies and an MDX based median-calculation that is actually not working as I would like it to work.
Hierarchy
- State
- County
- Town
- Neighborhood
- Filing Date
- Usage Category
- TransactionID (PRIMARY KEY)
I have a hierarchy set up which shall be used in order drill down the cube. The median, which shall be calculated based off the Sales Price measure and all the affected records, shall be available at every single level of the hierarchy. That is also why
I decided to use a hierarchy: I am at least not aware of a do-able alternative that would allow to use any available dimension without a hierarchy and calculate the median dynamically based off on that.
This is the MDX expression I use in order to calculate the median.
Median
      NONEMPTY(EXISTING Descendants( [Statistics Hierachy1].[Hierarchy].CurrentMember,
                   [Statistics Hierachy1].[Hierarchy].[Transaction Id])),
        [Measures].[Sale Price]
It works, and the numbers are correct, but it is way too slow in order to use it properly.
The hierarchy of dimension states that there is no relationship between the attributes of the hierarchy. That is right, because every single attribute is an attribute to the primary key (TransactionId).
So for me there are three ways to solve this:
1) Set up relationships. That, for some reason, brings up only a very limited subset of my data. Not sure why?
2) Get the hierarchy to work properly so it calculates the underlying median FASTER!
3) Set up a different measure (maybe my MDX is totally wrong?) to calculate the median the right way? In the end the median needs to be calculated based off on all underlying transactions that make up to the current level of the hierarchy.
In the end we are not talking about a ultra-large cube. Right now it only has like 3.1 Million rows in its one single partition.
Can anybody of you help me to address either the issue I am facing with the hierarchy (one I set up the relations I only see a subset of data) and/or let me know how to set up the median measure the right way ?
Thanks in advance! I really appreciate any help!
Thanks,
Lars

Hi L,
I would encourage you to set up the attribute hierarchies. That will make your calculation much faster, the further down the user is in the hierarchy. This is because the nonempty set you are getting the median from will be much smaller.
As you point out, to have an attribute hierarhcy, you need to have keys that cascade down, which you haven't got, at least yet. One simple way around this is to use composite keys all the way down the hierarchy. ie. State just has State as key,
County has State and County as key, Town has State, County and Town in key etc. I can assure you that this will make you calc much faster down the hierarchy.
One side effect you will have is that attributes will now be unique based on their parents. Two towns with the same name in different states or counties will appear as separate towns. You may or may not want this. If you don't want it,
simply have two Town attributes, call one TownKey (with composite key) which will be invisible as an attribute but used in the hierarchy. The other Town attribute simply has Town as the key, so it can be used as an attribute on its own. Town attribute
can be an attribute of TownKey.
Hope that makes sense,
Richard

Need Hierarchy Information to move setups in 11.5.10.2

Hi,
We are trying to migrate the setups to a fresh 11.5.10.2 instance. Our both source and target instances are in same patchset level with 11i.AZ.H.Delta2 Patch applied. We successfully moved the General Foundation. Now we have to move Product Foundation Selection set in that also we moved almost all the setups. Now we have to move freight carriers. As per OTN discussion [threadID=888663|http://forums.oracle.com/forums/thread.jspa?threadID=888663&tstart=15] we found that "Inventory Organizations" and "Inventory Parameters" has to be moved before moving freight carriers. While trying the move "Inventory parameters" we are facing some errors. So It'll be helpful if anybody can share the hierarchy information to be followed in 11i to move setups.
Since I'm a DBA i easily moved the General Foundation. But for Product Foundation i feel some difficulty to move the setups. so please guide us with the hierarchy setups to be followed.

Hi,
I'm posting the Error log message.
API Name: INV_Parameters
API Type: BC4J
Data File Name: INV_Parameters_2.xml
Commit If Warnings: true
Time Taken: 0
Importing rows from xml file, and validating rows ......
An error occurred in API 'ParametersAM'
View Object 'ParametersVO'
Organization Code = 'H01'
Lot Number Zero Padding = '2'
Matl Interorg Transfer Code = '1'
Defer Logical Transactions = '2'
Invoice Price Var Account Name = '2449.1000.9999.806.105.149016.2449.9999'
Default Pick Op Plan Code = 'Default (LPN)'
Crossdock Flag = '1'
Material Account Name = '2449.1000.9999.806.105.330001.2449.9999'
Organization Name = 'IIS INV ORG_HYDERABAD'
Wsm Enabled Flag = 'N'
Pm Cost Collection Enabled = '2'
Stock Locator Control Code = '1'
Wms Enabled Flag = 'N'
Lot Number Length = '30'
Serial Number Type = '4'
Lot Number Uniqueness = '1'
Ucc 128Suffix Flag = 'N'
Qa Skipping Insp Flag = 'N'
Business Group Name = 'OPERATIONS'
Encumbrance Reversal Flag = '2'
Default Cost Group = 'CG-1006'
Interorg Receivables Account Name = '2449.1000.9999.806.105.339002.2449.9999'
Serial Number Generation = '2'
Interorg Payables Account Name = '2449.1000.9999.806.105.339002.2449.9999'
Cost Organization Code = 'C01'
Carrier Manifesting Flag = 'N'
Purchase Price Var Account Name = '2449.1000.9999.806.105.149016.2449.9999'
Cartonize Sales Orders = 'Y'
Cost Of Sales Account Name = '2449.1000.9999.806.105.149014.2449.9999'
Primary Cost Method = '1'
Outside Processing Account Name = '2449.1000.9999.806.105.339023.2449.9999'
Material Overhead Account Name = '2449.1000.9999.806.105.330005.2449.9999'
Mo Source Required = '2'
Eam Enabled Flag = 'N'
General Ledger Update Code = '1'
Calendar Code = 'INV_CAL'
Ap Accrual Account Name = '2449.1000.9999.806.105.330001.2449.9999'
Direct Shipping Allowed = 'N'
Interorg Price Var Account Name = '2449.1000.9999.806.105.149016.2449.9999'
Pregen Putaway Tasks Flag = '2'
Master Organization Code = 'C01'
Resource Account Name = '2449.1000.9999.806.105.330006.2449.9999'
Prioritize Wip Jobs = '1'
Project Reference Enabled = '2'
Intransit Inv Account Name = '2449.1000.9999.806.105.339003.2449.9999'
Expense Account Name = '2449.1000.9999.806.105.111001.2449.9999'
Distributed Organization Flag = 'N'
Lot Number Generation = '3'
Overhead Account Name = '2449.1000.9999.806.105.339024.2449.9999'
Process Enabled Flag = 'N'
Interorg Transfer Cr Account Name = '2449.1000.9999.806.105.339004.2449.9999'
Cartonize Manufacturing = 'N'
Mo Pick Confirm Required = '2'
Sales Account Name = '2449.1000.9999.806.105.419071.2449.9999'
Starting Revision = 'A'
Mo Approval Timeout Action = '1'
Cartonization Flag = '1'
Negative Inv Receipt Code = '1'
Txn Approval Timeout Period = '0'
The following attribute is mandatory. Please enter a not null value.
Primary Key : OrganizationCode = 'H01'
Attribute : Organization Name, Business Group Name
Like wise same kind of messages repeated throughout the log.
Regards,
Subramaniam

ICR: msg FB_ICRC110 Recon. Process 003: Error in setup of recon. display

hello,
following with my tread [ICR: Define Reconciliation Process Detail Attributes|Intercompany reconciliation - help with customizing] I have already make trx FBICS3 - Select Documents store 2 documents at table FBICRC003T, looks good. But unfortunately when I run trx FBICA3 - Assign Documents Automatically or FBICR3 - Reconcile Documents Manually the system shows the following error message:
Reconciliation Process 003: Error in setup of reconciliation display
Message no. FB_ICRC110
Diagnosis
Your customizing for the reconciliation display is invalid.
when I go to customizing "Set Up Reconciliation Display" the system shows a "Run time error"
Runtime Errors         SYNTAX_ERROR
Date and Time          19.09.2008 20:20:30
Short text
     Syntax error in program "SAPLFB_RC_UI_VIEWS ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLSVIM" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "SAPLFB_RC_UI_VIEWS " in include
      "LFB_RC_UI_VIEWSF00 " in
     line 1308:
     "The data object "V_FBRC0070C" does not have a component called "AUTO"."
     The include has been created and last changed by:
     Created by: "SAP "
     Last changed by: "SAP* "
     Error in the ABAP Application Program
     The current ABAP program "SAPLSVIM" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     The following syntax error was found in the program SAPLFB_RC_UI_VIEWS :
     "The data object "V_FBRC0070C" does not have a component called "AUTO"."
Trigger Location of Runtime Error
     Program                                 SAPLSVIM
     Include                                 LSVIMU04
     Row                                     92
     Module type                             (FUNCTION)
     Module Name                             VIEW_MAINTENANCE_LOW_LEVEL
Does any body knows what is happening? Should I implement a SAP Note?
Thanks in advance

Hello Rafael,
Apparently you did not generate the customizing using FBICC. If you have not invested much effort in customizing settings I suggest that you implement note 1172591 and generate the customizing via transaction FBICC. After you run this and make sure that the transaction data tables are activated the programs should run (provided the customizing for the companies in FBIC032 is correct). Please go through the generated customizing settings and make sure that everything looks OK...
I also recommend implenting note 1161993. Whether you run FBICC or not it will help when going through the customizing settings. The most likely cause for the error messages is that there are some incorrect settings in your field catalog and due to this also in the display hierarchy setup.
I hope this helps you in your efforts,
Ralph

Parent Child Hierarchy for Type 2

I have read the articles on Parent Child hierarchy setup in OBIEE 11g, however, most are based on what seems to be a current snapshot of the Employee-Manager relationship. Has anyone tried to build out a Parent-Child hierarchy/table off a Type 2 dimension. Being able to navigate what the hierarchy may have been on a specific date.
I would welcome any feedback, thanks.

Hi,
Thanks for the reply, I'm actually using snapshots. But even with the Type 2 Dim I don't think it will work.
When OBIEE generates the very first sql against the Parent-Child table the fact table is not included in the query. It seems to create 2 queries - one to find the top level parent (ancestor key is null) and then one to find all the leaf nodes.
It does not have any join to the fact table when it does this. So if you have multiple rows in the table (with date stamps) for a single row (person in this case) - it picks up both rows. Therefore, when you have a person who was, say, promoted to manager, and WAS a leaf node, and is now a manager, they show up in the leaf query and don't display in the hierarchy as a manager.
Once it has the leaf nodes and it joins to the fact table everything works (ie the surrogate key join).
I'm trying to figure out if there is any way to influence those initial queries against the parent-child table.
Hopefully that made sense.
Thanks,
Tori

** DRM - Hierarchy maintenance

Hello Friends,
We are planning to use DRM (Data Relationship Management) for our hierarchy setup and Maintenance. One of the main usage of this would be to have alternate hierarchy populate for Hyperion planning/Essbase with version controls etc...
Like to know couple of things:
- Any CONS (Or) things that we can't do that we should be aware?
- Ideal Deployment? /* We are thinking to have DRM on Win2003 Server. Not sure Web Logic be optimal for having has a Web Server? */
Any feedbacks are appreciated.
Thank you!!

DRM is typically used to manage this type of environment. The only thing I would suggest is that you read up on the difference between global and local properties. When building alternate hierarchies, you want to share property values (or avoid populating property values twice) between hierarchies. Beisdes that, DRM has worked well for us here at the bank.
We also use Windows 2003.
D

OBIEE 11g: Skip a level in a parent-child hierarchy

Hi everyone,
I've got a parent child hierarchy setup. It's basically Total Company -> Continent -> Country. It's working fine.
For one particular report, the end user would like to bypass continent for just Asia. The rest of the countries should go through their continent first.
For example,
Total Company -> Europe -> Germany
Total Company -> North America -> Canada
Total Company -> Japan
Total Company -> Korea
We do not want to change the hierarchy as it is a corporate standard and eventually we want the grouping there. Just for a single report, we want to bypass.
Is there anyway to do this?
I tried to remove the "Asia" node while building the report, but it also removes the children. So then I tried adding back in the children and they weren't part of the hierarchy. They were off in their own duplicate hierarchy.
Hopefully this is possible.

Hi,
you mean for example you want to create a level 3 WBS under a level 1 WBS?
is that what you mean by skip a level?
that is not possible, i cant even think of a scenerio why you might want to do that. (but i'm curious why you asked)
it isnt even logically feasible. you can create WBS levels only one at a time.
Good day.

Problems importing new values into existing hierarchy

I have a hierarchy setup with name and code fields. I have already imported the majority of the records and manually setup the hierarchy in Data Manager (as we never had hierarchy setup in the past). I now have 100 or so new entries to add to this table, but it will not let me add the new values to the hierarchy table in Import Manager. I can map the code field fine, but when I try to map the name field, the Add button is grayed out no matter what I try to do. What am I doing wrong?
Thanks!

Hi Ryan,
Kindly go through the below links to understand Hierarchy importing in MDM:
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=mdmhierarchyimporting&cat=sdn_all
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=mdmhierarchyimporting&cat=sdn_all
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0e122d4-40ab-2a10-4a82-fe7db431fd5e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903c9530-52be-2a10-7d97-a48dc8082905
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80aa6fa7-4dbe-2a10-8b8f-8f1ce6fa2f95
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/mdm/how%2bto%2bimport%2bhierarchy%2bin%2bmdm
Hope It Helped
Thanks & Regards
Simona Pinto

Capacity cumulation in work center hierarchy

Hello
Does anyone uses workcenter hierarchies to cumulate capacity requirements ?
I've created a hierarchy but in the capacity evaluation transaction cm01,
the capacity requirements are not cumulated from the underlying work center.
Instead a capacity requirement of zero is shown on the hierarchy work center.
Is there any specifics to cumulate the capacity requirement to work center hierarchy header
Best regards
Pascal

Hi,
In the transaction CM01, choose the pull-down menu Settings-> General. In the pop-up screen, under the "Herarchy" tab, select the check boxes "Cumulation of reqmts" and "Dyn. capacity cumulation", choose the "Hierarchy" and "Plant" and click on "Continue".
Now the "Available Capacity" will be as per hierarchy setup and Rem. avail cap = Reqmts-Available capacity.
Hope this solves the requirement.
-Thaila Shree

Customer Hierarchy and product Hierarchy

Hi friends what is customer Hierarchy and what is product hierarchy?
please explain step by step with examples.
mail id: [email protected]
Thanx.

Hi Sirivas,
CUSTOMER HIERARCHY:
Customer hierarchies are available in Sales and Distribution, so that you can create flexible hierarchies to reflect the structure of customer organizations. If your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, for example, you can create hierarchies to reflect the structure of these groups. Use customer hierarchies during sales order processing and billing for determining pricing and running statistics.
 A customer hierarchy consists of nodes.
 To create a customer hierarchy:
1. Create master records for each node.
2. Assign the nodes to each other.
3. Assign the customer master records to the relevant nodes.
 Hierarchy nodes are only valid for a certain period of time. They may also be moved. If a node is moved, the system automatically reassigns all related nodes and customer master records.
With customer hierarchies, you can assign price or rebate agreements to a higher level node. The agreements are then valid for customers at all subordinate levels to this node. You can create pricing condition records for each node indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes them into account automatically during pricing.
'How to check'
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
1) Define hierarchy type: just put and ID and a name to the new hierarchy.
2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this information, in the order, you obtain the business partner for each partner function.
3) Assign account groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: simple you indicate which sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
5) Assigning hierarchy type for pricing: you indicate which classes of documents uses hierarchy in pricing determination.
It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
Customer hierarchy setup, firstly decide the hierarchy type to be used.
The standard is type A.
You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
Product Hierarchy:
The product hierarchy on the Basic Data screen is used to depict the competitive materials of competitor 1 in relation to those of competitor 2. Here, your own company and its materials are also regarded as a competitor and as competitive materials respectively. You can use this representation as a basis for market analyses.
Normally we enter competitive materials using material type WETT. When entering your own materials as competitive materials, you can, however, display the product hierarchy on the Basic Data screen for other material types too.
Requirement type determination is based on the "Origin of requirement type in requirement type determination"
In this field you can select an alternative search strategy (source):
Source 0 = Material master strategy, then item category and MRP type
Source 1 = Item type and MRP type strategy
Source 2 = Item type and MRP type strategy (as for source 1) with additional check of the allowed requirements type
e.g. If you set value "0" system will first strategy group in material master based on that it will determine requirement type and no value found then it will determine requirement type based on item category and MRP type.
Above settings can be found at SD --> Basic Functions --> Availability Check and transfer of requirement --> Transfer of Requirement --> Determination of Requirement type using Transaction
For make to order std strategy group 20 is used to which req type KE is assigned.
Check
Check in Tcode OVZH, what requirement class is assigned to your requirement type
Check in Tcode OVZG, what value is assigned to field "Consumption" in requirement class because that determines consumption posting.
The product hierarchy is used to group materials by combining different features. It is used for analyses and pricing. A product hierarchy can consist of up to Eighteen characters. Its features can be combined in various ways.
Example: A dishwasher can be described by product hierarchy 000010000200000002. This series of characters states that dishwashers belong to the category electrical appliances (series of characters 00001, position 1-5), and also to wet appliances (series of characters 00002, position 6-10) and, finally, to dishwashers (series of characters 00000002, position 11-18).
One can maintain the product hierarchy via transaction "OVSV" and "V/76.
Path = IMG-Logistics General-Material master-Setting for Key fields-Data relevant to SD-Define Product hierarchy.
The product hierarchy is maintained in the Basic Data view of the material master record, and is used for evaluation as well as price determination in materials management.
The standard SAP allows only 3 levels, but you can go up to 6 levels, for additional 3 levels u will have to take abapper help and add 3 more fields and corresponding data element into structure. So that in material master drop down you will see 6 levels.
The transaction which will be useful to change product hierarchies for material master will be V/76.
Yes, You can print the levels of the product hierarchy through a report.
Use the view SE16 - V_T179 (Table Name) to display Product hierarchy with level numbers.
Field Name is PRODH
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

What's use for Customer Hierarchy

Dear Guru
What's use for Customer Hierarchy? give me a step to config?
regards
Mohammed Renu.I

Hi Mohammed Renu,
CUSTOMER HIERARCHY:
Customer hierarchies are available in Sales and Distribution, so that you can create flexible hierarchies to reflect the structure of customer organizations. If your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, for example, you can create hierarchies to reflect the structure of these groups. Use customer hierarchies during sales order processing and billing for determining pricing and running statistics.
 A customer hierarchy consists of nodes.
 To create a customer hierarchy:
1. Create master records for each node.
2. Assign the nodes to each other.
3. Assign the customer master records to the relevant nodes.
 Hierarchy nodes are only valid for a certain period of time. They may also be moved. If a node is moved, the system automatically reassigns all related nodes and customer master records.
With customer hierarchies, you can assign price or rebate agreements to a higher level node. The agreements are then valid for customers at all subordinate levels to this node. You can create pricing condition records for each node indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes them into account automatically during pricing.
'How to check'
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
1) Define hierarchy type: just put and ID and a name to the new hierarchy.
2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this information, in the order, you obtain the business partner for each partner function.
3) Assign account groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: simple you indicate which sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
5) Assigning hierarchy type for pricing: you indicate which classes of documents uses hierarchy in pricing determination.
It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
Customer hierarchy setup, firstly decide the hierarchy type to be used.
The standard is type A.
You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

CUSTOMER & PRODUCT HIERARCHY

Dear SAP Gurus,
Can any one provide me step by step of Customer and Product Hierarchies?
my mail id is [email protected]
Highly rewarded.
Regards.

hi
Customer Hierarchy
All the customizing is in SD/Master Data/Bussiness Partner/Customers/Customers hierarchy
1) Define hierarchy type: just put and ID and a name to the new hierarchy.
2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this informacition, in the order, you obtain the bussiness partner for each partner function.
3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses hierarchy in pricing determination.
It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
Customer hierarchy setup, firstly decide the hierarchy type to be used.
The standard is type A.
You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
Can also refer to http://help.sap.com/bestpractices/BBLibrary/documentation/J04_BB_ConfigGuide_EN_UK.doc
Product Hierarchy Configuration:
http://help.sap.com/bestpractices/BBLibrary/documentation/Q10_BB_ConfigGuide_EN_US.doc
Reward if USeful
Thanx & regards..
Naren..

HAI SD EXPERS KINDLY LET ME KNOW

HERE ARE SOME INT QUESTIONS , KINDLY LET ME KNOW THE ANSWERS
1.In a sales order, if you want to give rs 10000 more than the credit limit to your customer how do you process this scenario
2.Mention some latest tickets L1 solved in ur support project
3.how will u configure batch jobs
4.what are the fields in purchase requisition
5.what is RMA process
6.how you will create nodes in customer hierarchy
7.suppose you want to offer two different materials as free for one material , how do u process this
8.you find terms of payment in two pages in customer master data, what is the role of the two
9.what is the difference b/n item cat group and general item cat group found in material master
10.what is the link b/n pricing procedure and credit management
11.what is as is & to be process
12.tell me about your experiences in support & imp projects
13. what do u know abt documetation and how u have done that in ur project
14.diff b/n user exits and enhancements
15.If the business offer diff rates on the material basing on the quantity, and the break up should appear in the sales order which carries the net value how do u customize this
THESE ARE VERY MUCH PRACTICAL KINDLY EXTEND UR HELP
KISHORE
[email protected]

1.In a sales order, if you want to give rs 10000 more than the credit limit to your customer how do you process this scenario
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
   Check which credit control area is assigned to the company code.
   Company code:
   Credit control area:
2. Transaction OVFL
   Check which credit control area is assigned to the sales area.
   Sales area:
   Credit control area:
3. Transaction XD02 or VD02
   Check which credit control area is assigned to the payer.
   Payer:
   Credit control area:
4. Transaction SE37
   is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
   For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
   OB45, or the credit control area must be entered under the relevant company code in table
   T001CM of the credit control areas allowed.
   Company code:
   Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
   which settings do exist for the sales document type used?
   Sales document:
   Check credit:
   Credit group:
8. Transaction OVAD
   which settings do exist for the delivery type used?
   Delivery type:
   Credit group for delivery:
   Credit group for goods issue:
9. Transaction OB01
   Credit management/Change risk category
   Definition of the risk category for each credit control area. This risk category can be
   assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
    Here, the individual credit checks for key fields
    o credit control area
    o risk category
    o credit group are set. Take these key fields from the above settings and go to the detail
      screen. In particular, check whether fields "Reaction" and "Status/block" are set
      correctly. To carry out follow-up actions in case of a credit block, the credit check
      status must be set (field "Status/block").
11. Transaction FD32
    Credit master data for the payer of the relevant document.
    Credit account:
    Credit limit:
    Risk category:
    Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
    check (static or dynamic credit limit check).
13. Transaction OVA7
    Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
    field "Active receivable" in Transaction VOV7.
    Item type:
    Active receivable:
14. Transaction V/08, Pricing
    In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
    determining the credit value (mark the pricing procedure and double-click on "Control").
    Usually, the net value plus taxes is used. This way the system is determined to use this
    subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
    update and credit check.
    You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
    Pricing procedure:
    Line with subtotal = 'A':
15. Transaction OB45
    which update group (field "Update") do you use in the relevant credit control area? The
    default setting is "12". If you use another update group, check whether this is fine with
    you. If you open an OSS message, please tell us the alternative update group.
    Credit control area:
    Update:
16. Transaction OMO1
    which kind of update did you choose for structure S066?
     In any case, "Synchronous update (1)" has to be chosen as the kind of update.
     All other settings will lead to errors.
4.what are the fields in purchase requisition
http://www.olemiss.edu/projects/sap/Purchasing-_New_Required_Fields_on_PR_and_PO.pdf
5.what is RMA process
Return Materials Authorization
6.how you will create nodes in customer hierarchy
All the customizing is in SD/Master Data/Bussiness Partner/Customers/Customers hierarchy
1) Define hierarchy type: just put and ID and a name to the new hierarchy.
2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this informacition, in the order, you obtain the bussiness partner for each partner function.
3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses hierarchy in pricing determination.
It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
Customer hierarchy setup, firstly decide the hierarchy type to be used.
The standard is type A.
You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
7.suppose you want to offer two different materials as free for one material , how do u process this
Free goods processing - Exclusive method

PO Hierarchy Setup

Similar Messages

Maybe you are looking for