The WebSphere business integration system provides two utilities that enable you to define business objects and the metadata required to support the processing of those business objects in the SAP application:
SAPODA generates individual business object definitions for the Hierarchical Dynamic Retrieve Module. If you use this utility to create hierarchical business object definitions, you must manually specify the relationships between the generated parent and child business object definitions.
To use SAPODA to generate a business object definition for this module:
For information on using SAPODA, see Appendix C, Generating business object definitions using SAPODA. For information on launching Business Object Designer and using it to manually modify a business object definition, see the Business Object Development Guide.
SAPODA generates a business object definition for every table you specify. When it completes generating, you can open all tables in Business Object Designer for editing.
To create a hierarchical business object definition from the individual business object definitions generated by SAPODA, do the following:
Assume, for example, the top-level business object is SAP_Customer. This business object has a single key, Customer_KUNNR. SAPODA specifies the following application-specific information for this attribute:
TN=KNA1:CN=KUNNR
For example, most business objects that are a direct child of SAP_Customer contain the Customer_KUNNR attribute. In the application-specific information for Customer_KUNNR, specify the following:
TN=KNVI:CN=KUNNR:FK=..Customer_KUNNR
For information on specifying foreign keys, see Table 46.
For example, SAP_Customer_ADRC is a second-level business object with no key the same as its parent's. SAPODA generates this business object definition with the Address_number_ADDRNUMBER attribute, which is a non-key field in SAP_Customer.
In the application-specific information for this attribute, specify the foreign-key relationship as:
TN=ADRC:CN=ADDRNUMBER:FK=..Address_ADRNR
The WebSphere business integration system enables users to define business objects and the metadata required to support the processing of those business objects in the SAP application. Advanced Outbound Wizard records and interprets your actions as you step through an SAP Display Transaction.
The wizard supports the definition of flat and hierarchical business objects that use the Retrieve verb.
To use Advanced Outbound Wizard to generate a business object definition for this module:
The CW Hierarchical Outbound Wizard screen displays. The business object displays closed at the top of the screen.
The wizard displays each field's length to the right of its name. To the right of the field's length, the wizard displays cumulative field length. If the cumulative length exceeds 512 bytes, the wizard marks the field with a red X and turns the field's display from yellow to red. By default, the wizard stops adding attributes to a business object when the length exceeds 512 bytes. To include desired attributes that are removed by default, you can:
The Download Object Definition screen displays.
For information on the business object and attribute names created by the wizard, see Business object names.
When generating the business object definition, Advanced Outbound Wizard creates a list of all tables involved in the SAP transaction. You can view the list of tables by pressing the Show Tables button at the top of the wizard's screen. Table 48 illustrates the tables used to generate SAP_Customer. Table.
Table 48. illustrates the tables used to generate SAP_Customer.
Name | Table Description |
---|---|
TFDIR | Function module |
KNA1 | General Data in Customer Master |
T001 | Company Codes |
KNB1 | Customer Master (Company Code) |
KNVV | Customer Master Sales Data |
TOBJ_OFF | Objects that were disabled |
ADRC | Addresses (central address admin.) |
ADRCT | Address texts (central address admin.) |
ADRG | Assignment of addresses to other address groups (cent.adr.) |
ADRV | Address where used list (central address administration) |
T002 | Language keys |
TBE01 | Business Transaction Events: Publish & Subscribe Interfaces |
TBE31 | Application components per Publish & Subscribe interface |
TBE32 | Partner function modules per Publish & Subscribe interface |
TBE34 | Customer function modules per Publish & Subscribe interface |
T100 | Messages |
DOKIL | Index for Documentation Table DOKH |
KNVI | Customer Master Tax Indicator |
TVKWZ | Org.Unit: Allowed Plants per Sales Organization |
T001W | Plants/branches |
KNVL | Customer Master Licenses |
TSADVC | Customizing international address versions |
TMODU | Cross Reference Field Name - MODIF1 |
TCONV_ADR | Conversion of Old Address Fields to CAM Address Fields |
TSAD7 | Address groups (central address management) |
T005T | Country Names |
T005U | Taxes: Region Key: Texts |
TZONT | Customers: Regional Zone Texts |
TSAD7T | Description of address groups (central address admin.) |
TOJTD | Customizing Object Types |
TOJTB | Business object repository: Basic data |
The wizard makes three passes through the tables to determine their hierarchy and the relationship among them. It uses the information to specify foreign-key relationships in the application-specific information of business object attributes. It names the attributes based on the field's description in SAP's data dictionary in the user's language.
In its three passes, the wizard does the following:
Typically this is the first table the wizard locates that has only one key field.
Typically several tables contain the parent's key field as well as multiple other keys. Grandchild tables typically contain more keys than their parent. Tables with identical keys are siblings (peers) of the parent.
The wizard establishes the relationship by locating a non-key field in the parent that matches the child's primary key.
Table 48 illustrates the results of all three of these passes through the list of display-Customer tables:
It has a single key, Customer_KUNNR. The wizard specified the following application-specific information for this attribute:
TN=KNA1:CN=KUNNR
The wizard identified the following three key fields, one of which is found as a key field in the parent:
In the application-specific information for the Customer_KUNNR attribute, the wizard specified the foreign-key relationship to the key field in the parent:
TN=KNVI:CN=KUNNR:FK=..Customer_KUNNR
For information on specifying foreign keys, see Table 46.
The wizard identified the following three key fields, one of which is found as a non-key field in the parent:
In the application-specific information for the Address_number_ADDRNUMBER attribute, the wizard specified the foreign-key relationship to a non-key field in the parent:
TN=ADRC:CN=ADDRNUMBER:FK=..Address_ADRNR
Attention: Verify the definition that the wizard generates. Although the wizard performs most of the work in creating a business object definition, the generated definition cannot meet the precise needs of your implementation. There are anomalies in table relationships that may cause the wizard to make incorrect decisions. For example, if two tables have the same set of keys and a child table has the same keys plus one, the wizard assigns the child to the first table.