Importing BAPI Wrappers as Data Objects

Use

BAPI wrappers can exist in the back-end systems connected to the Data Orchestration Engine (DOE). You can import existing BAPI wrapper definitions from the back-end system to the DOE and create data objects that map these definitions.

The type of BAPI wrappers that can be imported are GetDetail , GetList or Create . The DOE creates the root nodes and the child nodes based on the type of BAPI wrappers. The following table lists the nodes created for the various types of BAPI wrappers:

BAPI Wrapper Type	Root Node	Child Nodes
GetDetail	Export parameter	Table parameters
GetList	Table parameter	N/ A
Create	Import parameters	Table parameters

If a BAPI wrapper has multiple types defined, the DOE selects a type based on the order shown in the table above, with GetDetail as the first selection. Additionally, when you import the BAPI wrappers, the back-end adapters are created automatically.

After you import the BAPI wrappers as data objects, you can have the following situations:

You modify the BAPI wrappers in the back-end system.

If you modify the BAPI wrappers after importing them as data objects, you must adjust the data objects and the back-end adapters, accordingly.
You cannot activate the data objects because the node names start with a number.

Note

In the back-end system, BAPI wrappers can be stored with structure names that begin with a number. When these BAPI wrappers are imported, the data object nodes are stored with the same name. However, you cannot activate these data objects. After importing the BAPI wrappers as data objects, you must rename the nodes to start with a letter.

This is because when you activate a data object, its data is converted into an XML format by the Extensible Stylesheet Language Transformations (XSLT) processor. The XSLT standard states that node names cannot start with a number and therefore the data objects are not activated. So, the node names must be renamed to start with a letter.

Steps for these two situations are also provided in the procedure.

Prerequisites

You have created a software component version (SWCV) to store the data objects.

Procedure

Importing BAPI Wrappers as Data Objects

Log on to the SAP NetWeaver AS.
In the Navigation pane, choose Data Orchestration Engine Development Data Orchestration Workbench.
Click the SWCV that you want to use with the secondary mouse button and choose Import BAPI Wrapper as Data Object.
Enter the required details.
On the Import BAPI Wrapper as Data Object tab page, enter the required details.

Note

On the Customize Node Relationship tab page, you can modify the node hierarchy.
Choose Save .

Adjusting Data Objects and Back-End Adapters

Select the back-end adapters for the BAPI wrappers.
Choose Change .
Choose Adjust Adapter and Data Object .

After you have imported the BAPI wrappers as a data object, you must manually select the back-end key fields ( BE Key checkbox) for all the child nodes of the data object.

Renaming and Activating Data Object Nodes That Start with a Number

Choose the node, whose name starts with a number, and from the menu choose Data Object Display<->Change.
Double-click the back-end adapter and choose the Mapping Tool tab.
Select the node and its mapped BAPI wrapper structure.
To remove the mapping for the node, select all the fields for the node and choose Undo Selected Mapping .
Choose Save .
Choose Data Object Display<->Change.
In the node details area, rename the data object node.

Note

Node names must start with a letter. If you want to retain the number in the node name, you could place the number after a letter. For example, you can rename the node name 1_payroll to payroll_1 .
To activate the data object, click the data object with the secondary mouse button and choose Activate .
Double-click the back-end adapter and choose the Mapping Tool tab.
To map the nodes to the BAPI wrapper fields, select all the structure fields and choose Map Selected Fields .
To activate the adapter, select the back-end adapter with the secondary mouse button and choose Activate .