Print Business Objects (ttadv7400m100)

A set of related modules that implements a complete part of the functionality, for example, Enterprise Planning, Financials, or Warehouse Management. Packages are designed to function as independent as possible, to enable a customer to implement only particular packages.

A package code consists of two characters. For example, tt is the code of the Tools package.

Each package has a unique version structure, the VRC structure.

A set of related modules that implements a complete part of the functionality, for example, Enterprise Planning, Financials, or Warehouse Management. Packages are designed to function as independent as possible, to enable a customer to implement only particular packages.

A package code consists of two characters. For example, tt is the code of the Tools package.

Each package has a unique version structure, the VRC structure.

A part of a package consisting of a number of related software components, such as sessions, tables, program scripts, reports, forms and menus. For example, the General Ledger module in Financials.

A module code consists of three characters. For example, the General Ledger has the code "gld".

A part of a package consisting of a number of related software components, such as sessions, tables, program scripts, reports, forms and menus. For example, the General Ledger module in Financials.

A module code consists of three characters. For example, the General Ledger has the code "gld".

A business object is an object understandable by the business, such as a purchase order or an organizational unit. A business object has information stored in the business object attributes, such as the purchase order number or the organizational unit name. A business object also contains a set of actions, known as business object methods, that can manipulate the business object attributes, such as create purchase order and list organizational units.

From a development perspective, a business object is a collection of tables and functions that manipulate these tables that are implemented simultaneously as one group during the development phase. A business object is identified by the combination of a package code, module code, and business object code.

A business object is an object understandable by the business, such as a purchase order or an organizational unit. A business object has information stored in the business object attributes, such as the purchase order number or the organizational unit name. A business object also contains a set of actions, known as business object methods, that can manipulate the business object attributes, such as create purchase order and list organizational units.

From a development perspective, a business object is a collection of tables and functions that manipulate these tables that are implemented simultaneously as one group during the development phase. A business object is identified by the combination of a package code, module code, and business object code.

An upgrade of a package, for example, B61. Each change in the functionality of a package results in a new version. A version can contain several releases.

An update in a version. For example, 'B61 a', where 'B61' represents the version code, and the 'a' represents the release code. Each update results in a new release with a new release code.

A code that identifies a customized software package. For example, B61O_a_cus1, where 'B61O' represents the version, 'a' represents the release, and 'cus1' represents the customer extension of the customized software.

If this check box is selected, you can print the relations between business objects, components and tables, according to the check boxes you select in this group.

Clear this check box if you do not want to print the relations in this group.

If this check box is selected, the relations between business objects are printed.

These relations are defined in the following sessions:

Relationships between Business Objects (ttadv7520m000)
Relationship Details (ttadv7119m000)

If this check box is selected, the relations between the business object components are printed.

These relations are defined in the following sessions:

Business Object Component Relations (ttadv7133m000)
Business Object Component Relation Details (ttadv7132m000)

If this check box is selected, the relations between the business objects or business object components and the related tables are printed.

These relations are defined in the following sessions:

Tables (ttadv7111m000)
Business Object Component Table Relations (ttadv7134m000)

If this check box is selected, you can print the elements of the protected layer of the business objects or business object component, according to the check boxes you select in this group.

If this check box is selected, the attributes and methods you want to print are ordered per component.

The arguments of the method are always printed together with their methods, regardless the selection of this check box.

If this check box is selected, the protected attributes of the business objects or business object components are printed.

The protected attributes are defined in the Protected Attributes (ttadv7104m000) session.

If this check box is selected, the protected methods of the business objects or business object components are printed.

The protected methods are defined in the Protected Methods (ttadv7112m100) session.

If this check box is selected, the protected method arguments of the business objects or business object components are printed.

The protected method arguments are defined in the Business Object Method Arguments (ttadv7113m000) session.

Note: You can only select this check box if the Methods check box is selected, because arguments are always printed per method.

If this check box is selected, you can print the elements of the public layer of the business objects, according to the check boxes you select in this group.

If this check box is selected, the public attributes of the business objects are printed.

The public attributes are defined in the Public Attributes (ttadv7114m000) session.

If this check box is selected, the public methods of the business objects are printed.

The public methods are defined in the Public Methods (ttadv7112m000) session.

Note: Because public methods always have the same arguments, although their content can differ, the arguments are not printed.