Hierarchy Accesses
`
`Hierarchy Accesses I3E
`
`Description
`
`Hierarchy accesses
`
`VERSATA EXHIBIT 2083
`SAP v. VERSATA
`CASE CBM2012-00001
`
`Hierarchy accesses are used to optimize pricing for hierarchy data constellations such as a product hierarchy. \Nhen using
`hierarchies of this kind, it may be necessary to use any number of partial quantities (taken from the specified quantity of
`characteristics) to define the keys of the condition tables. A simple example of this would be a price which is fixed for sales
`organization and distribution channel but otherwise depends upon either customer, material or both.
`
`Without hierarchy accesses, you would need to create a condition table for every combination and assign all accesses to this
`table in a hierarchy within an access sequence. This would not only take a great deal of time, but it would also reduce system
`performance and force the system to use a rigidly fixed sequence of accesses.
`
`This is a major drawback, especially for hierarchical data such as that representing a product hierarchy or a customer hierarchy.
`
`Using the hierarchy access function, the system can find variants of this kind with a single access to a condition table containing
`all the necessary fields as possible fields in the variable key. It can then determine the required condition record according to the
`relevant criteria.
`
`Prerequisites
`
`When creating an access sequence in a condition table for the fields of an access, the user has the option of defining which part
`of the key remains fiXed and which part can vary (these are the free fields and the optional fields in condition maintenance).
`During access sequence maintenance, you assign priorities to the fields in the variable part of the key. These priorities are used
`to evaluate the relevance of the condition records detennined using the fixed part of the key.
`
`In Customizing for Pricing, you need to make the following settings in the access at field level:
`
`Processing type in access (Field PType): A= free field. Free fields are optional fields during condition record maintenance, so that
`any combination of characteristics can be created for an access.
`
`Evaluation of characteristics (Field Prio): Priority Is measured from 01 (high) to 99 (low).
`
`The records with the highest priorities are then made available in pricing.
`
`VERSATA EXHIBIT
`PX 1894
`C.A. No.2:07-CV-OOIS3-CE
`
`The quick entry screen for the condition records is not used. Mandatory entry is simply not used for the optional fields.
`
`Example of pricing with free fields:
`
`You want to set up pricing for materials which are assigned to a product hierarchy. You mark the hierarchy levels as free fields
`
`http://help.sap.com/saphelp_ 4Sblhelpdata/en/35/b0e83d87a62488e 10000009b38f9b7fcontent.htm (I of 2)318/2011 5:30:49 PM
`
`VER0002036673
`
`

`
`Hierarchy Accesses
`
`and enter a priority. As a rule, the priority should increase as you move from general to more specific criteria:
`
`Field I Processing type in access I Evaluation
`
`Sales organization I
`
`Material group I A I 5
`
`Main group I A I 4
`
`Group I A 13
`
`Sub-group I A I 2
`
`Material I A I 1
`
`The advantage of this is that only one access needs to be created in the access sequence during master data maintenance. This
`is because the free fields represent optional entries during condition record maintenance, allowing any number of combinations of
`characteristics for an access.
`
`You also get a much better overview of master data maintenance, because the different condition records can be created for a
`condition type in the condition maintenance quick entry screen.
`
`Example data in the standard system
`
`,··'
`
`In pricing procedure RVAA01 you can use condition type K148 with access sequence PRHI to test hierarchy accesses.
`
`•)"Pricing control"
`
`http://help.sap.com/saphelp_ 45b/helpdata/en/35/b0e83d87a62488el0000009b38f9b7/content.htm (2 of2)3/8/2011 5:30:49 PM
`
`VER000203667 4