US 7,461,091 B2
Controlling data transition between business processes in a computer application
Andreas Schneider, Bobenheim-Roxheim (Germany); Igor Kalenderian, Heidelberg (Germany); and Renzo Colle, Rastatt (Germany)
Assigned to SAP Aktiengesellschaft, Waldorf (Germany)
Filed on Jun. 09, 2005, as Appl. No. 11/148,245.
Prior Publication US 2006/0282448 A1, Dec. 14, 2006
Int. Cl. G06F 7/00 (2006.01); G06F 17/00 (2006.01); G06F 17/30 (2006.01); G06F 15/16 (2006.01)
U.S. Cl. 707—104.1  [707/4; 707/6; 707/9; 709/219] 26 Claims
OG exemplary drawing
 
1. A computer program product tangibly embodied in a computer-readable storage medium, the computer program product including instructions that, when executed, cause a data-transformation handling component to perform operations comprising:
receiving, from a preceding transaction process of a computer application, multiple transaction data entries of a preceding transaction type, wherein:
a transaction data entry includes attribute values, each attribute value corresponding to an attribute of the preceding transaction type,
the computer application includes instructions that, when executed, process transaction data that is applicable to many different business enterprises, and
the multiple transaction data entries include a first preceding transaction data entry having a first attribute value for a particular attribute and a second preceding transaction data entry having a second attribute value for the particular attribute, the first preceding transaction data entry being different from the second preceding transaction data entry;
receiving an indication of a processing transition point;
accessing user-defined configuration information that is associated with the indicated processing transition point, wherein the configuration information identifies 1) information related to how to generate a transaction data entry of a succeeding transaction type based on the preceding transaction type, and 2) information related to how to transform an attribute of the preceding transaction type to an attribute of the succeeding transaction type; and
using the accessed configuration information to determine transaction data entries of a succeeding transaction type that are generated based on the multiple transaction data entries of the preceding transaction type, wherein:
conditioned on the first attribute value matching the second attribute value, the transaction data entries of the succeeding transaction type that are generated include a first succeeding transaction data entry including data based on the first preceding transaction data entry and the second preceding transaction data entry, and
conditioned on the first attribute value not matching the second attribute value, the transaction data entries of the succeeding transaction type that are generated include i) a first succeeding transaction data entry including data based on the first preceding transaction data entry and ii) a second succeeding transaction data entry including data based on the second preceding transaction data entry, the first succeeding transaction data entry being different from the second succeeding transaction data entry.