Hierarchical Service Bundle Account Assignment Object

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current financial reporting and controlling systems face increased complexity and computational load when managing bundled services at an individual item level, making it difficult to evaluate profitability and generate reports efficiently.

Innovation Solution

Implementing a method that creates an account assignment object for a service bundle in a hierarchical structure, where a main item represents the bundle and subitems are associated with it, allowing for simplified processing and generation of billing documents based on the bundle's price, reducing the need to process each item separately.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If separate line items are used for each component of a bundled service, then detailed tracking of individual costs is improved, but computational load and processing time increase

Engineering Contradiction:
Improvedetailed tracking of individual costsVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The service bundle is segmented into a hierarchical structure with a main item representing the bundle and subitems representing individual components. This segmentation allows detailed tracking of subitem costs while enabling aggregated processing at the main item level, thus reducing computational load for reporting and billing operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple subitems are merged under a single main item in a hierarchical relationship. This merging enables the system to process and report on the bundled service as a single unit while maintaining the ability to access individual subitem details when needed, thereby improving processing efficiency without sacrificing measurement precision.

Inventive Principle:
Principle #5Merging (Combining)

2Measurement precision

If separate line items are used for each component of a bundled service, then individual cost tracking is improved, but complexity of service reporting increases

Engineering Contradiction:
Improveindividual cost trackingVSAvoidcomplexity of service reporting
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The reporting structure is segmented into hierarchical levels (main item and subitems), allowing reports to be generated at different granularities. Users can view aggregated bundle-level information or drill down to individual subitem details as needed, simplifying the overall reporting complexity while maintaining individual cost tracking capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The main item serves multiple functions: it represents the bundled service for high-level reporting, aggregates costs from subitems, and provides a parent reference for hierarchical navigation. This multi-functionality reduces reporting complexity by eliminating the need for separate aggregation logic while preserving detailed cost tracking.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Measurement precision

If individual processing is performed for each item in a bundled service, then accuracy of profitability evaluation is improved, but processing time increases

Engineering Contradiction:
Improveaccuracy of profitability evaluationVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The hierarchical structure pre-organizes subitems under their parent main item, establishing relationships and aggregating costs in advance. This preliminary organization enables rapid profitability evaluation by allowing the system to sum subitem costs through the hierarchical structure without performing individual processing for each item during the evaluation phase.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Cost data from multiple subitems is merged at the main item level through the hierarchical relationship. This merging enables accurate profitability evaluation by aggregating all relevant costs while performing a single processing operation at the bundle level, thereby maintaining accuracy without increasing processing time.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11443352B2Service bundles in service order management
Publication Date: 2022.09.13 SAP SE
  • US11443352B2 patent drawing
  • US11443352B2 patent drawing
  • US11443352B2 patent drawing

AI summary

Systems and processes for managing service orders for service bundles are provided herein. An account assignment object may be created in a service order database corresponding to a main item and a plurality of subitems may be linked to the account assignment object, the main item representing the service bundle and the plurality of subitems offered collectively as the service bundle. The main item and subitems may be part of a hierarchy structure in which the main item is at a higher level than the subitems. A value of the main item may be set corresponding to a price of the service bundle. Follow-up processing may be automatically performed and a billing document may be generated for the service order using the account assignment object. Entries for each of the main item and the plurality of subitems for the order may be displayed in a hierarchical line item view.