SAPODA prompts for additional information. The type of the top-level node (IDoc types, BOR, RFC, or Dynamic Definitions) determines:
SAPODA displays the BO Properties window to enable you to specify information required for business objects based on IDoc types. The properties displayed in this window differ depending on the source of the IDoc (an extracted file or a definition in the SAP system) and whether the definition is being defined for the ABAP Extension Module. This section describes the following topics:
Regardless of whether SAPODA is generating the business object definition from an IDoc file or an IDoc defined in the SAP system, the BO Properties window for an IDoc type allows you to specify or change:
The prefix is text prepended to the name of the business object to make it unique. If you are satisfied with the value you entered for the DefaultBOPrefix property in the Configure Agent window, you do not need to change the value here.
The module type choices are ALE or Extension. Because the ALE and the ABAP Extension Modules have different requirements for their business object definitions, it is important to specify which module will be using the business object.
Generate the attribute name from either the SAP field name or the SAP field description, the default being the SAP field description.
In addition to the prefix and module properties, the BO properties window representing an IDoc defined in the SAP system also displays the Release property. You can use this property to identify an earlier version of the IDoc type.
Figure 42 illustrates the two versions of the BO properties window, one for an extracted IDoc Type definition file and one for an IDoc defined in the SAP system.
Figure 42. Providing additional
information for an IDoc type business object
If you select Extension as the module type, SAPODA prompts whether you want to enter function module names for any of the default verbs.
By default, when generating a definition for the ABAP Extension Module, SAPODA specifies the following text for verb application-specific information at the business object level of the top-level business object:
:/CWLD/IDOC_HANDLER
If you already know the function module names to pass to the ABAP handler, select Yes at this prompt. SAPODA displays the window illustrated in Figure 43..
Figure 43. Specifying function
modules for the ABAP handler
Figure 43 illustrates a BO Properties window in which two function modules have been specified.
After you save the business object definition, the General tab in Business Object Designer displays the required application-specific information at the business object level of the topmost business object. Figure 44 illustrates such a window with the two specified function modules.
Figure 44. Specifying the ABAP
handler in business object designer
For more information about the ABAP handler, see Business object data routing to ABAP handlers.
There are two BO Properties windows for a BOR or RFC type. The properties displayed in the first window allow you to specify or change:
After you click OK to move forward from the first BO Properties window, SAPODA gives you the opportunity to reduce the size of the generated definition. You are prompted whether you want to remove from the definition any attributes that represent optional parameters. This prompt displays only if there are optional parameters to remove. Reducing the size of the definition can enhance performance later when the connector processes instances of the business object.
Figure 45 illustrates the properties displayed for a BOR or RFC-type object and the prompt that displays after you click OK.
Figure 45. Providing additional
information for BOR or RFC business objects
If you click Yes in the prompt illustrated above, the second BO Properties window displays. You can specify removal of each optional parameter of a BAPI/RFC interface by changing its Value from Yes (include a corresponding attribute in the generated definition) to No (do not include an attribute).
If you click No in the prompt illustrated above, the final wizard displays. For more information, see Save the definition.
Figure 46 Illustrates the second BO properties window.
Figure 46. Specifying atributes
for removal from the definition
In addition to the specifications you provide in SAPODA, when you create a definition for the RFC Server Module, you may want to modify application-specific information after you save the business object definition. For more information, see Developing business objects for the RFC Server module.
There are two BO Properties window for an HDR table-based object. The property displayed in the first window allows you to specify or change the business object's prefix. If you are satisfied with the value you entered for the DefaultBOPrefix property in the Configure Agent window, you do not need to change the value here.
Figure 47 Illustrates this window.
Figure 47. Providing additional
information for an HDR business object
In addition, only 512 bytes of information from a table can be
returned. When a table returns more than 512 bytes, you will be
presented with the dialog found in Figure 48.. Answering "No" returns
attributes (column descriptions) from the beginning of the table
until the 512 byte maximum is reached.
Answering "Yes" displays the second BO properties windows noted in Figure 49.. The length in bytes for each attribute is provided in the window description. You can specific the inclusion or exclusion of an attribute for the business object by toggling its value between "Yes" and "No."
Figure 49. Size and type of BO
properties for an HDR business object