Display Sales Order Hierarchies
Application component: Information System
App type: SAP GUI
Description:   Report that shows the sales order items of a sales order with the associated orders in a hierarchy graphic.  The data is displayed with the ABAP List Viewer (ALV Tree). The report provides predefined layouts with associated data. For example, you can display the following data with the standard layout plan/actual comparison supplied by SAP: planned costs, actual costs, planned output quantity, actual output quantity, and currency.  You can create custom layouts containing the information you are most interested in. See also: Defining Current Layouts  Functions of the ABAP List Viewer   You can switch between the following display formats:  No aggregation  Exclude plan values  Note Note on the display format exclude plan values: : With collective orders and joint production, the difference between the debit and credit in the planned data is aggregated upwards (up to the object beneath the sales order item). This means that with collective orders, the cumulative planned value of the entire collective order is shown on the leading order. In joint production, you can display the cumulative planned value of the production process on the order header.You use the display format exclude plan values in sales-order-related production when a sales order cost estimate exists. If you used the display format include plan values in this case, the planned costs of the assigned orders would be added to the planned costs of the sales order cost estimate, resulting in the planned costs being reported twice.  Include plan values   Note Note on the display format include plan values: : You use the display format include plan values when no sales order cost estimate exists. The total planned cost of all assigned orders is aggregated upwards (to the sales order item).  Note on the display formats exclude plan values and include plan values: and : Displaying the aggregated values ( exclude plan values and include plan values ) is only appropriate when you are using a nonvaluated sales order stock. If you are using a valuated sales order stock, aggregating the data may result in meaningless data in some cases (especially with include plan values without a sales order cost estimate). In the actual data , both include plan values and exclude plan values aggregate the value upwards (to the sales order item). To ensure that you get meaningful data, particularly with the display formats include plan values and exclude plan values , you should do the following before executing the report:  Settle the assigned orders Debit the sales order item with the actual costs of the period (such as with sales and administrative costs)  No aggregation displays the values updated on the object.   The report can be displayed in the following currencies:  Controlling area currency Company code currency / object currency  You can define exceptions in the report. Exceptions are used to display traffic light symbols (red/yellow/green) at objects whose variances exceed a predefined threshold. You specify the reference for the threshold values by choosing a rule basis (such as actual costs absolute ). The percentage and absolute threshold values you specify tell the system by how much the reference value must be exceeded before it displays a traffic light symbol on the object.