# US 2013/0159909 A1 · Virtual business object node associations

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0159909 A1
- Document ID: US20130159909A1
- Status: Published application
- Kind: A1
- Application number: 13/328,849
- Filed: 2011-12-16
- Published: 2013-06-20
- Earliest claimed: 2011-12-16
- Assignees: Sap SE
- Inventors: Tim Kornmann; Gerd M. Ritter; Dirk Stumpf; Rene Gross
- Web page: https://patentgrep.com/patent/US20130159909A1

## CPC

- G06Q 10/00: Administration; Management
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A computer-implemented system may include reception of an instruction to create an association for an element of a UI component model, determination of a first business object model of the association, determination of a second business object model of the association, definition of foreign key parameters associating an attribute of the first business object model with an attribute of an element of the second business object model, reception of an instruction to bind the element of the UI component model to a second attribute of the element of the second business object model, and creation of metadata in the UI component model associating the element of the UI component model with the second attribute of the element of the second business object model, the metadata comprising the foreign key parameters.

## Claims

### Claim 1

A non-transitory computer-readable medium storing program code executable by a processor of a computing system to:
receive an instruction to create an association for an element of a UI component model;
determine a first business object model of the association;
determine a second business object model of the association;
define foreign key parameters associating an attribute of the first business object model with an attribute of an element of the second business object model;
receive an instruction to bind the element of the UI component model to a second attribute of the element of the second business object model; and
create metadata in the UI component model associating the element of the UI component model with the second attribute of the element of the second business object model, the metadata comprising the foreign key parameters.

### Claim 2 (depends on 1)

A medium according to claim 1,
wherein the first business object model and the second business object model are a same business object model.

### Claim 3 (depends on 2)

A medium according to claim 2, the program code further executable by a processor of a computing system to:
receive a second instruction to bind a second element of the UI component model to a third attribute of the element of the same business object model; and
create second metadata in the UI component model associating the second element of the UI component model with the third attribute of the element of the same business object model, the second metadata comprising the foreign key parameters.

### Claim 4 (depends on 1)

A medium according to claim 1, wherein the element of a UI component model comprises a data structure.

### Claim 5 (depends on 1)

A medium according to claim 1, wherein the element of a UI component model comprises a data list.

### Claim 6 (depends on 1)

A medium according to claim 1, the program code further executable by a processor of a computing system to:
receive a second instruction to bind a second element of the UI component model to a third attribute of the element of the second business object model; and
create second metadata in the UI component model associating the second element of the UI component model with the third attribute of the element of the second business object model, the second metadata comprising the foreign key parameters.

### Claim 7

A computing system comprising:
a memory storing processor-executable program code; and
a processor to execute the processor-executable program code to cause the system to:
receive an instruction to create an association for an element of a UI component model;
determine a first business object model of the association;
determine a second business object model of the association;
define foreign key parameters associating an attribute of the first business object model with an attribute of an element of the second business object model;
receive an instruction to bind the element of the UI component model to a second attribute of the element of the second business object model; and
create metadata in the UI component model associating the element of the UI component model with the second attribute of the element of the second business object model, the metadata comprising the foreign key parameters.

### Claim 8 (depends on 7)

A system according to claim 7,
wherein the first business object model and the second business object model are a same business object model.

### Claim 9 (depends on 8)

A system according to claim 8, the processor to execute the processor-executable program code to cause the system to:
receive a second instruction to bind a second element of the UI component model to a third attribute of the element of the same business object model; and
create second metadata in the UI component model associating the second element of the UI component model with the third attribute of the element of the same business object model, the second metadata comprising the foreign key parameters.

### Claim 10 (depends on 7)

A system according to claim 7, wherein the element of a UI component model comprises a data structure.

### Claim 11 (depends on 7)

A system according to claim 7, wherein the element of a UI component model comprises a data list.

### Claim 12 (depends on 7)

A system according to claim 7, the processor to execute the processor-executable program code to cause the system to:
receive a second instruction to bind a second element of the UI component model to a third attribute of the element of the second business object model; and
create second metadata in the UI component model associating the second element of the UI component model with the third attribute of the element of the second business object model, the second metadata comprising the foreign key parameters.

### Claim 13

A method implemented by a computing system in response to execution of program code by a processor of the computing system, the method comprising:
receiving an instruction to create an association for an element of a UI component model;
determining a first business object model of the association;
determining a second business object model of the association;
define foreign key parameters associating an attribute of the first business object model with an attribute of an element of the second business object model;
receiving an instruction to bind the element of the UI component model to a second attribute of the element of the second business object model; and
creating metadata in the UI component model associating the element of the UI component model with the second attribute of the element of the second business object model, the metadata comprising the foreign key parameters.

### Claim 14 (depends on 13)

A method according to claim 13,
wherein the first business object model and the second business object model are a same business object model.

### Claim 15 (depends on 14)

A method according to claim 14, further comprising:
receiving a second instruction to bind a second element of the UI component model to a third attribute of the element of the same business object model; and
creating second metadata in the UI component model associating the second element of the UI component model with the third attribute of the element of the same business object model, the second metadata comprising the foreign key parameters.

### Claim 16 (depends on 13)

A method according to claim 13, wherein the element of a UI component model comprises a data structure.

### Claim 17 (depends on 13)

A method according to claim 13, wherein the element of a UI component model comprises a data list.

### Claim 18 (depends on 13)

A method according to claim 13, the program code further executable by a processor of a computing system to:
receive a second instruction to bind a second element of the UI component model to a third attribute of the element of the second business object model; and
create second metadata in the UI component model associating the second element of the UI component model with the third attribute of the element of the second business object model, the second metadata comprising the foreign key parameters.