Browse Prior Art Database

Business Entity Separation Method for Different Processes, Structures and Fulfillment Methods Disclosure Number: IPCOM000149900D
Original Publication Date: 2007-Apr-12
Included in the Prior Art Database: 2007-Apr-12
Document File: 2 page(s) / 28K

Publishing Venue



The method described here pertains to large organizations with a need to consolidate or merge multiple SAP instances. This involved combining separate systems, processes, product structures and fulfillment methods into one merged environment. For this merged environment, a method was required to separate the involved processes, methods and code. Also required was the ability to identify re-usable components within the processes, function and code, to leverage the similarities while maintaining the differences of the business models implemented within the one SAP instance. This method implements a concept of "business entity" which would identify each of the unique fulfillment processes for which support was required. This business entity is associated with all end to end processes contained within fulfillment and all related transactions, documents and interfaces. The unique technical approach to accommodate this concept included: - extension of tables - use of program templates for allowing separation as well as combination of function and code - identification of common components which could be re-used across all of the business entities - coverage of all levels of processes and code and all technical components (screens, includes, data declarations, etc.)

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Business Entity Separation Method for Different Processes , Structures and Fulfillment Methods

This approach was used due to a need for an indicator to trigger different processing logic (i.e. inbound order processing, output to downstream systems, etc.) throughout the transaction cycle. The logic is governed by business processes which are unique for the different business entities supported by the application. Examples below:

Support is required to segregate reports based on business entity (ie different reports for different business entities and/or common reports but different data selection by business entity) .

Support is required for limiting access to specific transactions by business entity. This supported the S&A (Security and Authorization) design, specifically for authority profiles. Support is required for different error handling processes (failed IDOCS, etc).

Support for different customer support organizations by business entity and routing of application messages to appropriate personnel within the organization.

Technical Implementation approach:

A common SAP-System for the CHW (configured hardware) and ESW (entitled software) implementations was built. To trigger different functionality due to different product families the BEI (Business Entity Indicator) has been implemented. The BEI is available on all main header and item tables including the areas of: Order, Billing , Delivery and Accounting.

Several BEI determination rules are implemented to retrieve BEI on header and/or item le...