Generating Master Data Export DataSources in BW BI

Use

The export DataSource is needed to transfer data from a source BI system into a target BI system.

You can generate an export DataSource for master data, and thus for individual InfoObjects. By doing this, all the metadata is created that is required to extract master data (all attributes, texts, and hierarchies) from an InfoObject.

Prerequisites

The source BI system must have been created and actively saved in the target BI system as a BI source system.

More information: Creating SAP Source Systems

Procedure

...

1. Select the InfoObject tree in the Data Warehousing Workbench in the source BI system.

2. Generate the export DataSource from the context menu of your InfoObject. To do this, choose Additional Functions ® Generate Export DataSource.

The technical name of the export DataSource is

8******M for attributes (M stands for master data)

8******T for texts

8******H for hierarchies.

(The asterisks (*) stand for the source InfoObject).

When you create an InfoObject or a master data InfoSource in the source BI system, you must therefore make sure that the length of the technical name of each object is no longer than 28 characters.

Data Transfer Using the Data Mart Interface in BW BI

The data transfer is the same as the data transfer in an SAP system. The system reads the data, taking into account the specified dimension-specific selections, from the fact tables of the delivering BI system.

Delta Process

Using the data mart interface, you can transfer data by full upload as well as by delta requests.

A distinction is made between InfoCubes and DataStore objects.

● The InfoCube that is used as an export DataSource is first initialized, meaning that the current status is transferred into the target BI system. When the next upload is performed, only those requests are transferred that have come in since initialization. Different target systems can also be filled like this.

Only those requests are transferred that have been rolled up successfully in the aggregates. If no aggregates are used, only those requests are transferred that are set to Qualitative OK in the InfoCube administration.

● For DataStore objects, the requests in the change log of the DataStore object are used as the basis for determining the delta. Only the change log requests that have arisen from reactivating the DataStore object data are transferred.

Restriction:

You can only make one selection for each target system for the delta.

You first make a selection using cost center 1 and load deltas for this selection. Later on, you also decide to load a delta for cost center 2 in parallel to thecost center 1 delta. The delta can only be fully requested for both cost centers, meaning that it is then impossible to separately execute deltas for the different selections.

Open Hub Service in BW BI

Use

As of SAP NetWeaver 7.0 SPS 6, the new Open Hub Destinationobject replaces the InfoSpoke that was previously used for the open hub service. You can still use existing InfoSpokes, however we recommend that you do not create any new InfoSpokes, but use the new open hub destination concept instead.

More information: Open Hub Destination

The open hub service allows you to distribute data from a BI system to non-SAP data marts, analytical applications, and other applications.It ensures controlled distribution across multiple systems. The InfoSpoke defines the object from which data is taken and the target into which it is transferred.

With the open hub service, the BI system is now the hub of an enterprise data warehouse. The distribution of data is made transparent by central monitoring of the distribution status in the BI system.

Features

BI objects such as InfoCubes, DataStore objects, or InfoObjects (attributes or texts) can function as open hub data sources. Note that DataSources may not be used as the source.

You can select database tables or flat files as open hub destinations. Both a full mode and a delta mode are available as extraction modes.

Components of the Open Hub Service in BW BI

The open hub service is made up of the following objects:

InfoSpoke

The central object for the data export is the InfoSpoke.

The InfoSpoke defines the following:

● The open hub data source from which the data is extracted

● The extraction mode

● The open hub destination into which the data is delivered.

In addition, you can select which selection of data is extracted from which InfoProvider. The selection ensures that a destination can be provided with data from the same InfoProvider at different times using a delta. As long as extraction has not yet taken place in delta mode, the selection set is freely configurable. Once it has, this no longer applies.

Open Hub Data Source

BI objects such as InfoCubes, DataStore objects, MultiProviders or InfoObjects (attributes or texts) can function as open hub data sources. If you use an InfoCube with non-cumulative key figures as a data source, refer to the note regarding the settings on the Selection tab page in Creating InfoSpokes.

Extraction Mode

An InfoSpoke can extract data in two ways: in full mode (F) and in delta mode (D). See InfoSpoke Extraction Mode.

Open Hub Destination

Database tables (from the database in the BI system) and flat files (CSV) can act as open hub destinations. See Database Tables As Destinations and Files As Destinations. You can extract the data from a database to a non-SAP system using APIs with a third-party tool. See Third-Party Tools As Destinations.

The open hub destination contains all the information about the target system for the InfoProvider data: type of destination, name of the flat file or database table. It also contains a logical target system. The logical target system is used to structure the individual open hub destinations in the open hub monitor. The open hub monitor groups the requests according to logical target system, open hub destination and InfoSpoke. By specifying a logical target system, you get a better overview of the individual open hub requests.

Components of the Open Hub Service in BW BI

The open hub service is made up of the following objects:

InfoSpoke

The central object for the data export is the InfoSpoke.

The InfoSpoke defines the following:

● The open hub data source from which the data is extracted

● The extraction mode

● The open hub destination into which the data is delivered.

In addition, you can select which selection of data is extracted from which InfoProvider. The selection ensures that a destination can be provided with data from the same InfoProvider at different times using a delta. As long as extraction has not yet taken place in delta mode, the selection set is freely configurable. Once it has, this no longer applies.

Open Hub Data Source

BI objects such as InfoCubes, DataStore objects, MultiProviders or InfoObjects (attributes or texts) can function as open hub data sources. If you use an InfoCube with non-cumulative key figures as a data source, refer to the note regarding the settings on the Selection tab page in Creating InfoSpokes.

Extraction Mode

An InfoSpoke can extract data in two ways: in full mode (F) and in delta mode (D). See InfoSpoke Extraction Mode.

Open Hub Destination

Database tables (from the database in the BI system) and flat files (CSV) can act as open hub destinations. See Database Tables As Destinations and Files As Destinations. You can extract the data from a database to a non-SAP system using APIs with a third-party tool. See Third-Party Tools As Destinations.

The open hub destination contains all the information about the target system for the InfoProvider data: type of destination, name of the flat file or database table. It also contains a logical target system. The logical target system is used to structure the individual open hub destinations in the open hub monitor. The open hub monitor groups the requests according to logical target system, open hub destination and InfoSpoke. By specifying a logical target system, you get a better overview of the individual open hub requests.

Database Tables As Destinations in BW BI

Use

You can select a database table as an open hub destination.

Features

Deleting Data from the Table

With an extraction to a database table, you can either retain the history of the data or just store the new data in the table. Choose Delete Table Before Extraction when defining your destination if you want to overwrite the fields. In this case, the table is completely deleted and regenerated before each extraction takes place. We recommend that you use this mode if you do not want to store the history of the data in the table. If you do not select this option, the system only generates the table once before the first extraction. We recommend that you use this mode if you want to retain the history of the extracted data.

Generating Database Tables

The generated database table has the prefix /BIC/OHxxx (xxx is the technical name of the destination).

How the database table is generated differs depending on whether you use a BAdI for the transformation:

...

1. If you do not use a BAdI, the table is created with the field list of the extract structure for the InfoSpoke (prefix /BIC/CY).

2. If you do use a BAdI, the table is created with the field list of the target structure for the BAdI. If the field list for your database table differs from the generated extract structure, you should create your own target structure for each BAdI and then change the field list using dictionary maintenance.

...

Table Key Fields

Note that when extracting to a database table, the generated DB table can have a maximum of 16 key fields. Check whether your field list includes too many key fields. If this is the case, you can set the Technical Key indicator. A unique key is then added that consists of the technical fields OHREQUID (open hub request SID), DATAPAKID (data package ID), and RECORD (running number of a data record to be added to the table within a data package). These fields display the individual key fields for the table.

Using a target table with a technical key is useful in the following instances:

...

1. Delta extraction from DataStore objects: the data is read in the change log in which several records with different RECORDMODEs can exist for a specific semantic key (after/before image). Otherwise extracting to a table with the semantic key of the DataStore object leads to duplicate records and, ultimately, a short dump.

2. Delta extraction from an InfoCube: first the system reads records from the fact table (F table) and then records from the table of compressed InfoCube data (E table). If there are records for a specific characteristic key in both the F table and the E table, a short dump is produced in the open hub target table when the system tries to add the record from the E table. To solve this problem you can either set the Technical Key indicator or, as an alternative, compress all data found in the InfoCube before extraction.

3. Extracting in full mode to a table that does not need to be deleted before the extraction: if, for an extracted record, a record already exists with the same key, a short dump is produced because of the duplicate records.

4. If the source has more than 16 key fields, no DB table can be created with these key fields. In this case, the table has to include a technical key.

Files As Destinations in BW BI

Use

You can select flat files in format .CSV as an open hub destination.

Features

The only file format that is supported for extraction to flat files is .CSV. A control file with information about the metadata is also generated. You can either save the file on the application server or in a local directory.

If you save the file locally, the file size must not exceed a half GB. When transferring mass data, you should save the file on the application server.

If the data is to be written to a BI system application server, you can determine the file name in two ways:

● File name:

The file name is made up of the name of the HOME directory (DIR_HOME in transaction AL11), the technical name for the InfoSpoke and the suffix .CSV. You cannot change this name.

● Logical file name:

You can use input help to select a logical file name that you have already defined in Customizing. Create a logical path and assign a logical file name to it (see Defining Logical Path and File Names).

When you define a logical file name you can also specify a data format. However, the InfoSpoke ignores this specification. Extraction always takes place in CSV format.

A logical file name can be made up of fixed path information, but also of variables such as calendar day and time. Logical file names can be transported.

If you save the file in a local directory, you cannot change the name of the file. It consists of the technical name of the InfoSpoke and the suffix .CSV. The associated control file also has the prefix S_.

Extraction Mode for the InfoSpoke in BW BI

Use

An InfoSpoke can extract data in two ways:

...

1. Full mode (F): the data corresponding to the selection criteria of the InfoSpoke is transferred from the data source into the respective destination.

2. Delta mode (D): records that were added since the last extraction only are transferred in this mode. This is only possible for the source objects InfoCube and DataStore object.

Features

The extraction mode can be switched from full to delta mode at any time. You can only switch from delta to full mode if you have not loaded any delta yet.

Note: with delta extraction into DB tables from DataStore objects or InfoCubes, the indicator Technical Key should be set. See also Extraction to Database Tables.

Delta Administration:

Delta Administration displays the requests available in the open hub data source as well as information about whether they have already been read or whether the open hub destination has not yet received them. If that is the case, the requests can be found under the category Requests Not Yet Read. Delta administration offers you the following functions:

· You can deactivate delta administration. An additional delta request is subsequently not possible. At the same time, the status of all source requests that have already been read is reset to Not Yet Read.

Delta administration is also deactivated if one of the following events occurs:

§ A request that has already been extracted is deleted in the open hub data source.

§ A request that has not yet been extracted is compressed in the open hub data source (InfoCube).

· You can reactivate delta administration. A delta request is then possible again.

· In the context menu, you can choose Delete Requests. The request is deleted from delta administration and can be requested again (repeat). You may want to do this if a request does not arrive correctly in the target system.

Creating InfoSpokes in BW BI

Procedure

...

1. In the main menu of the Data Warehousing Workbench, choose Tools ® Open Hub Service ® Edit InfoSpoke Enter a technical name for your InfoSpoke. You can also select a template.

2. Choose Create InfoSpoke.

3. Enter a description for your InfoSpoke.

Tab Page: General

4. On the General tab page, select a data source. You can use InfoCubes, DataStore objects, MultiProviders or InfoObjects (attributes or texts). Note that you cannot use input help to select a MultiProvder, you have to enter it manually.

5. Select a destination. You can also enter the technical name of a destination that you are about to create.

6. Select an extraction mode. See InfoSpoke Extraction Mode.

7. Specify the number of rows per data package for the data records to be extracted. You can use this parameter to control the maximum size of a data package and thereby control the number of main memories that need to be made available to structure the data package.

Tab Page: Destination

8. Choose the Destination tab page and enter a description.

9. Select a Logical Target System.

10. Select one of the following destination types:

○ Database table: For the Deleting the Table Before the Extraction and Technical Key settings, see Extraction to a Database Table. You can also use the Notification to Third-Party Tool indicator to extract data from a third-party tool. See Extraction to Non-SAP Systems. In the RFC Destination field, enter the name of the RFC destination for your third-party tool. You can then choose Parameters to display the parameter table for the third-party tool.

○ File (CSV): Either choose Application Server or specify a local directory; specify a delimiter of type Character. If you choose the application server as the storage for the file, you can selectFile Name or Logical File Name from the dropdown box. If you choose Logical File Name, you get to the transaction for creating logical file names by double clicking on the field for the file name. See Extraction to Flat Files.

Tab Page: InfoObjects

11. On the InfoObjects tab page, select the InfoObjects that you want to transfer. The available fields are displayed on the right half of the screen. You use the arrow keys to transfer them into the left half of the screen.

The Key Fields for the Table Start pushbutton allows you to place key fields at the start of the field list. With extraction to database tables, you have to extract a field list of this type. With flat files, you need to specify the field list sequence yourself.

Tab Page: Selection

12. On the Selection tab page, you can restrict the selected fields even further. Only simple selections of single values and intervals are possible as restrictions. After you have confirmed your selection, you can use the Selection Category to exclude single values or intervals. To do this, click icon or (included) and then switch to or (excluded). The default setting is Included.

Extraction of InfoCubes with non-cumulative key figures:

Set the filter value for 0RECORDTP (record type) to ‘1’. This ensures that all markers in the compressed data of the InfoCube are extracted. You can extract non-cumulatives by compressing the InfoCube in regular intervals and extracting using 0RECORDTP = ‘1’.

Tab Page: Transformation

13. On the Transformation tab page, you can transform the data to be transferred using a BAdI. See InfoSpoke with Transformations using BAdI.

Activating and Executing InfoSpokes

14. Choose Activate InfoSpoke .

15. When the InfoSpoke has been activated successfully, choose Extraction in the Dialog Process. A status log is displayed.

If you do not want to start extraction straight away, that is, you want to schedule it to take place at a later time, you have to include the InfoSpoke in a process chain. See Including InfoSpokes in Process Chains.

Result

You have extracted data from an open hub data source into a database table or a flat CSV file.

Including InfoSpokes in Process Chains in BW BI

Use

If you want to automatically execute and schedule an InfoSpoke, you can include this as an application process in the procedure for a process chain. The scheduling of an extraction by using an InfoSpoke is only possible by using a process chain in its start process.

Prerequisites

You have created an InfoSpoke and have saved it as being active. If you extract the data to a file, the file has to be on the application server. Extraction to a local file requires a GUI connection and cannot be executed in the background as is the case for a process chain.

Procedure

...

1. Call up the process chain maintenance. Choose Process Chain Maintenance from the Administrator Workbench toolbar. The Process Chain Maintenance Planning View screen appears.

2. In the left-hand screen area of the required display component, navigate to the process chain in which you want to insert your InfoSpoke. Double-click to select it. The system displays the process chain plan view in the right-hand side of the screen.

If no suitable process chain is available, you need to create a new process chain. You can find additional information under Creating a Process Chain.

3. To insert a process for extraction by means of an InfoSpoke, choose Process Types in the left-hand area of the screen. The system now displays the process categories available.

4. In the process category Loading Process and Post Processing, choose the application process type Data Export into External Systems.

5. Insert the Data Export into External Systems application type with Drag&Drop into the process chain. The dialog box for inserting a process variant appears.

6. In the Process Variant field, enter the name of the InfoSpoke that you want to include in the process chain, or select it by means of the input help.

7. Proceed further as described in Creating Process Chains.

Result

You have included your InfoSpoke in a process chain. As soon as you activate the process chain, the extraction starts according to your specifications in the start process.

Example

The following graphic illustrates an example of how a process chain is used to include an InfoSpoke. The processes for deleting and building indexes are optional, because they help to improve performance.

Third-Party Tools As Destinations in BW BI

Use

You can use the open hub service to extract data to non-SAP systems. Various APIs allow you to connect a third-party tool (such as Ascential) to the BI system and then distribute the data to other non-SAP systems.

Features

First you extract the data from BI InfoProviders into a database table in the BI system. The third-party tool receives a message when the extraction process is complete. You can define parameters for the third-party tool. You can also use the monitor to oversee the process.

You can use a process chain to start the extraction process not only in the BI system itself, but also using the third-party tool.

The Following APIs Are Available:

RSB_API_OHS_DEST_SETPARAMS: You use this API to transfer the parameters of the third-party tool that are required for the extraction to the BI system. These parameters are saved in a parameter table within the BI system in the metadata for the open hub destination.

RSB_API_OHS_3RDPARTY_NOTIFY: This API sends a message to the third-party tool after extraction. It transfers the open hub destination, the request ID, the name of the database table, the number of extracted data records and the time stamp. In addition, you can add another parameter table that contains the parameters that are only relevant for the third-party tool.

RSB_API_OHS_REQUEST_SETSTATUS: This API sets the status of extraction to the third-party tool in the open hub monitor. Red means that the existing table is not being overwritten. If the status is green, the request is processed further.

RSB_API_OHS_DEST_GETLIST: This API delivers a list of all open hub destinations.

RSB_API_OHS_DEST_GETDETAIL: This API determines the details of an open hub destination.

RSB_API_OHS_DEST_READ_DATA: This API reads data from the database table in the BI system.

Optional:

RSB_API_OHS_SPOKE_GETLIST: This API delivers a list of all InfoSpokes.

RSB_API_OHS_SPOKE_GETDETAIL: This API determines the details of an InfoSpoke.

Process Flow:

Extraction to the third-party tool can be executed as follows:

...

1. You define an InfoSpoke with destination type DB Table and Notification to Third-Party Tools.

2. You create an RFC destination for your third-party tool and enter it in the definition of the open hub destination.

3. You use API RSB_API_OHS_DEST_SETPARAMS to define the parameters for the third-part tool that are required for the extraction.

4. You can use the InfoSpoke either to start the extraction directly or include it in a process chain. You can also start this process chain from the third-party tool using process chain API RSPC_API_CHAIN_START. The extraction process then writes the data to a database table in the BI system.

5. When the extraction process is finished, the system sends a notification to the third-party tool via API RSB_API_OHS_3RDPARTY_NOTIFY.

6. The third-party tool reads the data from the database table. Afterwards it transfers the status of the extraction to the monitor using API RSB_API_OHS_DEST_SETSTATUS.

API: RSB_API_OHS_DEST_SETPARAMS in BW BI Data Distribution

You use this API to transfer the parameters of the third-party tool that are required to extract data to the BI system. These parameters are saved in a parameter table within the BI system in the metadata for the open hub destination.

Parameters:

	Parameter	Type	Description
Import	OHDEST	RSOHDEST	Name of the open hub destination
	3RDPARTYSYSTEM	LOGSYS	Third-party system (logical system)
	EXTEND	RS_BOOL	Extending the parameter
Export	RETURN	BAPIRET2
Tables	PARAMETERS	BAPI6107PA	Parameter table

EXTEND: If the value is true, new parameters are added to the existing parameters. If the value is false, the existing parameters are deleted and the new parameters are inserted. The default setting is false.

The PARAMETERS table contains all the parameters required by the third-party system and saves these parameters in the metadata of the open hub destination. When extraction is finished, these parameter are sent to the third-party system (3RDPARTYSYSTEM) using API RSB_API_OHS_DEST_SEND_NOTIFICATION.

API: RSB_API_OHS_3RDPARTY_NOTIFY in SAP BW BI Data Distribution

This API sends a message to the third-party tool after extraction. It transfers the open hub destination, the request ID, the name of the database table, the number of extracted data records and the time stamp. In addition, you can add another parameter table that contains the parameters that are only relevant for the third-party tool.

Parameters:

	Parameter	Type	Description
Import	OHDEST	RSOHDEST	Name of the open hub destination
	REQUESTID	RSBREQUIDOUT	Request ID
	NUMB_OF_PACKETS	I	Number of packages extracted
	DBTABNAME	RSBTABNAME	Name of DB table
	DBRECORDS	SYTABIX	Number of records extracted
	TIMESTAMP	BAPIBP_TIMESTAMP	Time stamp of extraction (request)
Export	RETURN	BAPIRET2
Tables	PARAMETERS	BAPI6107PA	Parameter table
Exceptions	COMMUNICATION_FAILURE
	SYSTEM_FAILURE

API: RSB_API_OHS_REQUEST_SETSTATUS in SAP BW BI Data Distribution

This API sets the status of extraction to the third-party tool in the monitor. If the status is green, the request is processed further. Red means that the existing table is not being overwritten. The third-party tool sets the status to red when there is a processing error in the third-party system. This ensures that the existing data is not overwritten until the error has been corrected.

The status is written to table RSBREQUID3RD.

The following diagram shows how the status entry is processed:

The OHD state is the status of extraction to the BI system; it is dependent on the status of the third-party tool. This status is set by the third-party tool.

STOP means that the request has not been started. The BI system waits until the status of the third-party tool is set to green. Only then does it start extraction.

Parameters:

	Parameter	Type	Description
Import	REQUESTID	RSBREQUIDOUT	Request ID
	STATUS	RSBSTAT3RD	Status of processes in third-party tool; G = Green, R = Red
	MESSAGE	BAPI_MSG	Message for the monitor. This text can contain 220 characters, however only 200 characters are displayed in the monitor.
Export	RETURN	BAPIRET2

API: RSB_API_OHS_DEST_GETLIST in SAP BW BI Data Distribution

This API delivers a list of all open hub destinations.

Parameters:

	Parameter	Type	Description
Import	OHDEST	RSOHDEST	Name of the open hub destination
	DESTTYPE	RSDESTTYPE	Type of destination: TAB = DB table TAB3 = Third-party tool FILE = flat file
Export	RETURN	BAPIRET2
Tables	DEST_TAB	RSBOHDESTS	List of open hub destinations

Table DEST_TAB contains all the destinations that the import parameter accesses.

API: RSB_API_OHS_DEST_GETDETAIL in SAP BW BI Data Distribution

This API identifies the details of an open hub destination.

The target system gets the structure and the table with the metadata of the open hub destination.

This API is used at design time and at runtime.

Parameters:

	Parameter	Type	Description
Import	OHDEST	RSOHDEST	Name of the open hub destination
	SKIP_TECKEY	RS_BOOL	Skip technical key (X)
Export	RFCINFOSPOKE	RSINFOSPOKE	Name of InfoSpoke (not relevant for new open hub destination; remains initial)
	RFCUPDATEMETHOD	RSBUPDMODE	Extraction mode of InfoSpoke (not relevant for new open hub destination; remains initial)

API: RSB_API_OHS_SPOKE_GETLIST in SAP BW BI Data Distribution

This API returns a list of all InfoSpokes.

Parameters:

	Parameter	Type	Description
Import	INFOSPOKE	RSINFOSPOKE	Name of the InfoSpoke
Export	RETURN	BAPIRET2
Tables	SPOKE_TAB	RSBO_S_SPOKE	List of InfoSpokes

API: RSB_API_OHS_SPOKE_GETDETAIL in SAP BW BI Data Distribution

This API identifies the InfoSpoke details.

Parameters:

	Parameter	Type	Description
Import	INFOSPOKE	RSINFOSPOKE	Name of the InfoSpoke
Export	RFCOHDEST	RSOHDEST	Name of the open hub destination
	RFCUPDATEMETHOD	RSBUPDMODE	Extraction Mode for the InfoSpoke
	RFCPROCESSCHAIN	RSPC_CHAIN	Process chain
	RFCOHSOURCE	RSOHSOURCE	Open hub data source
	RFCTLOGOSRC	RSTLOGOSRC	TLOGO type of data source
	RFCMAXPACKSIZE	RSIDOCSIZE	Maximum number of records per package
	RETURN	BAPIRET2
Tables	T_MESSAGES	BAPIRETTAB	Messages

InfoSpoke with Transformation Using a BAdI in SAP BW BI Data Distribution

Use

You have the option of transforming the data to be transferred using a Business Add-In (BAdI). The original structure for transfer is thereby the InfoObject list. Possible user scenarios for a transformation would be, for example, the reading of texts or a currency conversion.

For more information about using Business Add-Ins (BAdIs), read the detailed documentation for Business Add-Ins.

Prerequisites

For the Transformation tab page, set the indicator for InfoSpoke with Transformation Using BAdI so that the InfoSpoke is activated first. Then you arrive in the BAdI builder.

Procedure

The definition for the BAdI is called OPENHUB_TRANSFORM. For this, you create your implementation.

You can find detailed information about implementing a BAdI under: Implementing Business Add-Ins.

Implementing the BAdI

...

1. You are in the BAdI builder. Enter a short text for the implementation. The implementation name is always the same as the technical name of the InfoSpoke.

2. The implementation of this BAdI is always filter-dependent. Enter your InfoSpoke on the Properties tab page under Filter Specifications. You can only have one implementation for each InfoSpoke.

If you do not specify an InfoSpoke under Filter Specifications, then this implementation is valid for all InfoSpokes. This means that this is called up for all InfoSpokes during the extraction.

3. Activate your class.

4. From the Interface tab page, you arrive at the TRANSFORM method in the class builder by double-clicking. There you can enter your code:

method IF_EX_OPENHUB_TRANSFORM~TRANSFORM .

your code

endmethod.

5. Activate your method. Return to the BAdI builder. Return to your InfoSpoke.

Result

You can now write the data into the open hub destination using your own transformations.