Show TOC

Procedure documentationCreating a Back-End Adapter Locate this document in the navigation structure

 

A back-end adapter is the interface between the Data Orchestration Engine (DOE) and back-end systems and is required in order for a data object to receive data from the back-end system. The back-end adapter maps a data object's node attributes to the corresponding fields in the business data in the back-end system.

Note Note

A data object must be activated before you can create a back-end adapter for it. The reason for this is when mapping the data object to the back-end business data, the system must refer to the table created for the data object in the DOE data dictionary. A BAPI wrapper must also exist for the business data in the back end. In addition, you must know for which business data you are writing the back-end adapter, and which function modules exist for it. These are important components of your work.

Whenever back-end adapters are activated, the signatures of the BAPI wrappers are imported from the back-end system to the DOE's local repository. During generation, the DOE does not connect to the back-end system for getting the signatures; it gets the signatures from its local repository.

End of the note.

Note Note

This feature of back-end adapter generation is available for adapters you create in the DOE from version SP03 onwards. To activate the same behaviour for adapters created on versions prior to SP03, you must run the SDOE_UPDATE_METADATA report. You must select the SWCVs that contain the previously created adapters and then execute the report.

End of the note.

Procedure

  1. Log on to the NetWeaver AS server and start transaction SDOE_WB.

  2. In the Data Orchestration Engine Workbench, click the data object for which you want to create a back-end adapter with the secondary mouse button and choose   Create   Backend Adapter  .

  3. In the Select an adapter dropdown list, select the BAPI WRAPPER ADAPTER.

  4. Choose Continue.

    Note Note

    The Data Object Details section is read-only.

    End of the note.

  5. In the Adapter Overviewgroup box, enter the appropriate information using this table.

    Field name

    User action and values

    Adapter Name

    Enter a name for the adapter.

    Default adapter

    Select this option if you want this adapter to be the default adapter.

    Synchronization Type

    Select the appropriate value.

    • MIDDLEWARE TRIGGERED indicates that mobile middleware triggers synchronization.

    • BACKEND TRIGGERED indicates that the back-end system triggers synchronization.

    back-end BO Name (active when the BACKEND TRIGGERED option is selected)

    Enter the name of the business object (BO) that should trigger the back-end adapter. The BO is present in the back-end system.

    The back-end business object name for the adapter should be same as the object name sent from back end to the DOE.

    Status

    A read-only field that indicates the current status of the adapter.

    Version

    The version number of the back-end adapter.

  6. If you want to add BAdI exits, enter the appropriate information in the respective fields, using this table. If you do not want to add BAdI exists, continue with step 7.

    Field name

    User action and value

    Enhancement spot name

    Enter the place in which you want to insert the BAdI exit in the back-end adapter code.

    BAdI name

    Enter the name of the BAdI exit that you want to use.

    Interface name

    Enter the name for the interface you are calling.

  7. Under Bapi Wrapper Adapter, enter the following details:

    Field name

    User action and values

    Get list

    Specify the function module to be used to transfer a list of business object header data.

    Note Note

    You must know which function modules this data object must use to extract data from the back-end system at runtime.

    End of the note.

    Use Mass Data

    Select this option if the data volume to be transferred from the back end is high; it allows multiple instances of items to be retrieved in a single call to the back end..

    Get detail

    Specify the function module to be used to transfer items associated with the business object header data.

    Use Bulk

    Select this option if subscriptions are to be provided without validation checks for each record of data.

    Create

    Specify the function module to be used to create an object.

    If you do not specify a create BAPI wrapper, you can select the message that must be sent to the client when the device user tries to create the data object.

    Select the Send Confirmation indicator to send a confirmation message. If you do not select this message, a rejection message is sent.

    Modify

    Specify the function module to be used to modify an object.

    If you do not specify a modify BAPI wrapper, you can select the message that must be sent to the client when the device user tries to modify the data object.

    Select the Send Confirmation indicator to send a confirmation message. If you do not select this message, a rejection message is sent.

    Delete

    Specify the function module to be used to delete an object

    If you do not specify a delete BAPI wrapper, you can select the message that must be sent to the client when the device user tries to delete the data object.

    Select the Send Confirmation indicator to send a confirmation message. If you do not select this message, a rejection message is sent.

    Instance push function

    Only relevant for back-end-triggered synchronization. Specify the function module to be used for pushing an object instance to the middleware. The instance push function has the advantage that only one call is made from the DOE to the back end.

    Note Note

    You cannot use Instance push function when you want to use Attachments of type BLOB and CLOB.

    End of the note.

    Corr Cleanup function

    Specify the function for correcting or cleaning up an object.

  8. Choose the Mapping Tool tab.

  9. In the Mapping object details table in the Table Name field, select the name of the table containing the fields you want to map.

    Note Note

    The tables that appear in the dropdown list are generated when you activate a data object. The node attributes that are available for mapping appear in the following table.

    End of the note.

  10. In the Mapped object details table, enter the following details:

    Field name

    User action and values

    Mapped Object Type

    A read-only field showing the type back-end adapter being used. In this case it is a BAPI wrapper.

    Object Name

    Select the required method from the dropdown list.

    Note Note

    These methods are associated with the business object specified under the Adapter Overview section on the Adapter Details tab.

    End of the note.

    Table Name

    Select the name of the table containing the fields you want to map.

  11. Perform the mapping by using the arrow keys and the Propose button.

  12. Choose Save.

Result

You have created a back-end adapter, specified the function modules it uses to extract data from the back end, and mapped the data object table fields to the business data fields in the back end. Your next steps include checking the back-end adapter and activating it.