How to Migrate RFC/BAPI Function Mappings to Use a BAPI/RFC Transformation

Size: px

Start display at page:

Download "How to Migrate RFC/BAPI Function Mappings to Use a BAPI/RFC Transformation"

Alban Strickland
6 years ago
Views:

No part of this document may be reproduced or transmitted in any form,

prior consent of Informatica Corporation.

1 How to Migrate RFC/BAPI Function Mappings to Use a BAPI/RFC Transformation 2013 Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. All other company and product names may be trade names or trademarks of their respective owners and/or copyrighted materials of such owners.

2 Abstract You can modify the mappings that you created with RFC/BAPI function mappings with BAPI transformation. This article explains how to migrate existing mappings to use a BAPI/RFC transformation. Supported Versions PowerExchange for SAP Netweaver for PowerCenter Table of Contents Overview Configuration Differences in RFC/BAPI Function Mapping and BAPI/RFC Transformation RFC/BAPI No Input Mappings Migration Modifying RFC/BAPI No Input Mappings Migrating a No Input Mapping and Session - An Example RFC/BAPI Single Stream Mappings Modifying RFC/BAPI Single Stream Mappings Migrating a Single Stream Mapping and Session - An Example RFC/BAPI Multiple Stream Mappings Modifying RFC/BAPI Multiple Stream Mapping Migrating a Multiple Stream Mapping and Session - An Example BAPI/RFC Sessions Configuring Sessions After Migration Overview RFC/BAPI function mappings contains mapplets to extract data from SAP NetWeaver. Migrate your mappings to use the BAPI/RFC transformation instead of the function mappings. 2

3 Configuration Differences in RFC/BAPI Function Mapping and BAPI/RFC Transformation Some properties that you configure in a RFC/BAPI function mapping must be configured at the session level for a mapping with BAPI/RFC transformation. The following table describes the configuration levels for the properties in a RFC/BAPI function mapping and a mapping with BAPI/RFC transformation: Property RFC/BAPI Function Mapping Mappings with BAPI/RFC Transformation Connection FunctionCall mapplet Session Continue on error Mapping parameters Session Perform Commit Mapping parameters Session RFC/BAPI No Input Mappings Migration RFC/BAPI No Input function mapping extracts data from SAP. The mapping contains the following components: Source Definition Source definition for each RFC/BAPI signature you use in the mapping. Source Qualifier An Application Multi-Group Source Qualifier transformation for each Virtual plug-in source definition in the mapping. FunctionCall mapplet A FunctionCall_No_Input mapplet for each RFC/BAPI function signature you use in the mapping. In the No Input RFC/BAPI mapping, the FunctionCall_No_Input mapplet makes the RFC/BAPI function call on SAP and interprets the data that the function call returns. Target Definition for function output Target definition for each scalar or table output parameter you use in the RFC/BAPI function. To migrate an RFC/BAPI No Input mapping, you must replace the mapplet with a BAPI/RFC transformation and reconfigure the mapping. You must edit the session to include an RFC/BAPI connection and update the session properties. Modifying RFC/BAPI No Input Mappings Ensure that you have the details of the BAPI used in the FunctionCall mapplet. 1. Open the mapping in the Designer. 2. Note the values for commit call, interval, return type, and connection properties in the AEP transformation of the mapping. 3. Delete the FunctionCall mapplet. 4. Click Transformation > Create, and select SAP BAPI/RFC transformation. 5. Enter a transformation name, and click Create. Step 1 of the wizard appears. 3

4 6. Enter connection string parameters to connect to SAP with sapfrc.ini. Or, click Host Name and enter host name parameters to connect to SAP. 7. Click Next. Optionally, enter a filter condition to filter BAPIs by name or description. 8. Click Get Objects. The wizard displays BAPIs that you can import. 9. Expand the list of objects and select the BAPI as in the FunctionCall mapplet. Note: You need not use the TransactionID values to define the commit points for a logical unit of work ( LUW) in BAPI/RFC transformation. 10. Click Finish. 11. Connect the source qualifier port to the IntegrationID input port in the BAPI/RFC transformation. 12. Connect the required output ports in the BAPI/RFC transformation to the target definition. 13. Save the mapping. Migrating a No Input Mapping and Session - An Example m_bapi_noinput is a no input mapping that contains mapplets and s_bapi_noinput is the corresponding session. You must edit the mapping and session to use a BAPI/RFC transformation. 1. Open m_bapi_noinput mapping in the Designer. The mapping contains the following components: Flat file source Source Qualifier FunctionCall_SS mapplet Oracle target 2. Note the values for commit call, interval, return type, and connection properties in the AEP transformation of the mapplet. 3. Delete the mapplet and the source definition. 4. Import a flat file source definition that contains all the Integration IDs. 5. Click Transformation > Create, select SAP BAPI/RFC transformation, enter the name of the transformation as BAPI_ACTIVITYTYPE_GETLIST_RFCSSCALLFUNCTION, and click Create. Step 1 of the wizard appears. 6. Enter connection string parameters to connect to SAP with sapfrc.ini. Or, click Host Name and enter host name parameters to connect to SAP. Click Next. 7. Optionally, enter a filter condition to filter the BAPI by name or description and click Get Objects. The wizards displays BAPIs that you can import. 8. Expand the list of objects and select the BAPI. 9. Connect the Integration ID from the source qualifier to the Integration ID in the Scalar Input and the Table Input of the transformation. 10. Open the Target Designer. 11. Drag and drop the transformation into the Target Designer. The Designer creates the target definitions for scalar output and table output. 12. Connect the output groups from the transformation to the target definitions. 4

13. Save the mapping. The following figure shows the updated mapping with the BAPI/RFC transformation: 14. Click Connections > Applications> in the Workflow Manager.

5 13. Save the mapping. The following figure shows the updated mapping with the BAPI/RFC transformation: 14. Click Connections > Applications> in the Workflow Manager. The Application Connections Browser dialog box appears. 15. Select SAP RFC/BAPI Interface and click New. The Connection Object Definition dialog box appears. 16. Enter the connection details and click OK. 17. Open the session, s_bapi_noinput. The Edit Tasks dialog box appears. 18. Select the transformation in the Mapping tab. 19. Select the type of connection as Application and the SAP RFC/BAPI connection that you created in the Connections pane. 20. Click Show Session Level Properties in the Properties pane and select Perform Commit. 21. Save the session. RFC/BAPI Single Stream Mappings An RFC/BAPI single stream mapping can extract data from SAP, change data in SAP, and write data into an SAP system. Unlike a multiple stream mapping, however, the single stream mapping does not contain RFCPrepare mapplets in the mapping to prepare source data for the function call. The mapping contains the following components: Source definition A source definition and a source qualifier for function input data. Sorter transformation Mapping includes a Sorter transformation to sort source data by TransactionID and IntegrationID. It passes the sorted data to the FunctionCall_SS mapplet. 5

6 FunctionCall_SS mapplet Mapping includes a FunctionCall_MS mapplet for each RFC/BAPI function signatures you use in the mapping. The mapplet makes the RFC/BAPI function call on SAP. The mapplet also makes commit calls on SAP for transaction control. If the RFC/BAPI function call returns output, the mapplet interprets the data that the function call returns and passes it to the targets. Target definition for function output Mapping includes a Virtual plug-in target definition for each scalar or table output parameter you use for the RFC/BAPI functions. The wizard includes the Virtual plug-in target definitions in the mapping for mapping validation. Replace the Virtual plug-in target definitions with the appropriate definitions for the target warehouse. Modifying RFC/BAPI Single Stream Mappings Ensure that you have the details of the BAPI used in the FunctionCall_SS mapplet. 1. Open the mapping in the Designer. 2. Note the values for commit call, interval, return type, and connection properties in the AEP transformation of the mapping. 3. Delete the mapplet and the sorter transformation. 4. Click Transformation > Create, and select SAP BAPI/RFC transformation. 5. Enter a transformation name, and click Create. Step 1 of the wizard appears. 6. Enter connection string parameters to connect to SAP with sapfrc.ini. You can also click Host Name and enter host name parameters to connect to SAP. 7. Click Next. Optionally, enter a filter condition to filter BAPIs by name or description. 8. Click Get Objects. The wizard displays BAPIs that you can import. 9. Expand the list of objects and select the BAPIs that you want. Note: You need not use the TransactionID values to define the commit points for a logical unit of work ( LUW) in BAPI/RFC transformation. 10. Click Finish. The BAPI/RFC mappings appear in the canvas. 11. Connect the source qualifier output ports to the BAPI/RFC transformation input mapping. The scalar and table input to the SAP system must be available in the source definition. 12. Connect the required output ports in the BAPI/RFC transformation to the target definition. 13. Save the mapping. Migrating a Single Stream Mapping and Session - An Example m_bapi_activitytype is a single stream mapping that contains mapplets and s_bapi_activitytype is the corresponding session. You must edit the mapping and session to use a BAPI/RFC transformation. 1. Open m_bapi_activitytype mapping in the Designer. 6

The following figure shows the single stream mapping: The mapping contains the following components: Flat file source Source Qualifier FunctionCall_SS mapplet Flat file target 2.

7 The following figure shows the single stream mapping: The mapping contains the following components: Flat file source Source Qualifier FunctionCall_SS mapplet Flat file target 2. Note the values for commit call, interval, return type, and connection properties in the AEP transformation of the mapplet. 3. Delete the mapplet and the target definition. 4. Click Transformation > Create, select SAP BAPI/RFC transformation, enter the name of the transformation as BAPI_ACTIVITYTYPE_GETLIST_RFCSSCALLFUNCTION, and click Create. Step 1 of the wizard appears. 5. Enter connection string parameters to connect to SAP with sapfrc.ini. Or, click Host Name and enter host name parameters to connect to SAP. Click Next. 6. Optionally, enter a filter condition to filter the BAPI by name or description and click Get Objects. The wizards displays BAPIs that you can import. 7. Expand the list of objects and select the BAPI. 8. Click the Return Structure tab to configure the ReturnParameter. 7

8 The following figure shows the return structure configuration: Optionally, you can configure the return structure after import with the Customize BAPI wizard. Note: In single stream mapping, return structure was configured in the FunctionCall mapplet. 9. Connect the Integration ID from the source qualifier to the Integration ID in the Scalar Input and the Table Input of the transformation. 10. Open the Target Designer. 11. Drag and drop the transformation into the Target Designer. The Designer creates the target definitions for scalar output, table output, and error output. 12. Connect the output groups from the transformation to the target definitions. 13. Save the mapping. 8

The following figure shows the updated mapping with the BAPI/RFC transformation: 14. Click Connections > Applications> in the Workflow Manager. The Application Connections Browser dialog box appears.

9 The following figure shows the updated mapping with the BAPI/RFC transformation: 14. Click Connections > Applications> in the Workflow Manager. The Application Connections Browser dialog box appears. 15. Select SAP RFC/BAPI Interface and click New. The Connection Object Definition dialog box appears. 16. Enter the connection details and click OK. 17. Open the session, s_bapi_activitytype. The Edit Tasks dialog box appears. 18. Select the transformation in the Mapping tab. 19. Select the type of connection as Application and the SAP RFC/BAPI connection that you created in the Connections pane. 20. Click Show Session Level Properties in the Properties pane and select Perform Commit. 21. Save the session. RFC/BAPI Multiple Stream Mappings An RFC/BAPI multiple stream mapping takes input from user defined sources and prepares the source data in the format that an RFC/BAPI function can accept. The mapping then uses the prepared data as function input to make RFC/BAPI function calls on SAP. An RFC/BAPI multiple stream mapping can extract, load, and update data in SAP. The mapping contains the following components: Source definition A source definition and a source qualifier for function input data. Prepare mapplet Mapping includes a Prepare mapplet for each RFC/BAPI function signature you use in the mapping. 9

10 RFCPreparedData target definition Mapping contains a set of flat file target definitions that receive input from the Prepare mapplets in the mapping. Each Prepare mapplet in the mapping passes data to a corresponding RFCPreparedData (flat file) target definition. The RFCPreparedData target definitions represent staging files where the Integration Service writes the prepared data from the Prepare mapplets. RFCPrepared Data source definition Mapping contains an RFCPreparedData (flat file) source definition. It represents the RFCPreparedData indirect file, which the Integration Service uses to read data from the RFCPreparedData staging files. Source Qualifier for RFCPreparedData source Mapping includes a Source Qualifier transformation for the RFCPreparedData source definition in the mapping. Transaction_Support mapplet In a multiple stream RFC/BAPI mapping, the mapping includes a Transaction_Support mapplet to ensure transaction control. FunctionCall_MS mapplet Mapping includes a FunctionCall_MS mapplet for each RFC/BAPI function signatures you use in the mapping. The Multiple Stream FunctionCall_MS mapplet makes the RFC/BAPI function call to extract data from SAP. It also interprets the data that the function call returns. Target definition for function output Mapping includes a Virtual plug-in target definition for each scalar or table output parameter you use for the RFC/BAPI functions. The wizard includes the Virtual plug-in target definitions in the mapping for mapping validation. Replace the Virtual plug-in target definitions with the appropriate definitions for the target warehouse. Modifying RFC/BAPI Multiple Stream Mapping Ensure that you have the details of the BAPI used in the Transaction_Support mapplet and FunctionCall_MS mapplet. 1. Open the mapping in the Designer. 2. Note the values for commit call, interval, return type, and connection properties in the AEP transformation of the mapping. 3. Delete all the mapplets. Ensure that you have the details of the different BAPIs used in the mapplet. 4. Click Transformation > Create, and select SAP BAPI/RFC transformation. 5. Enter a transformation name, and click Create. Step 1 of the wizard appears. 6. Enter connection string parameters to connect to SAP with sapfrc.ini. You can also click Host Name and enter host name parameters to connect to SAP. 7. Click Next. Optionally, enter a filter condition to filter BAPIs by name or description. 8. Click Get Objects. The wizard displays BAPIs that you can import. 9. Expand the list of objects and select the BAPIs that you want. Note: You need not use the TransactionID values to define the commit points for a logical unit of work ( LUW) in BAPI/RFC transformation. 10

11 10. Click Finish. The BAPI/RFC mappings appear in the canvas. 11. Connect the source qualifier output ports to the BAPI/RFC transformation input mapping. The scalar and table input to the SAP system must be available in the source definition. 12. Connect the required output ports in the BAPI/RFC transformation to the target definition. 13. Save the mapping. Migrating a Multiple Stream Mapping and Session - An Example m_bapi_activitytype is a multiple stream mapping that contains mapplets and s_bapi_activitytype is the corresponding session. You must edit the mapping and session to use a BAPI/RFC transformation. 1. Open m_bapi_activitytype mapping in the Designer. The following figure shows the multi stream mapping: The mapping contains the following components: Flat file source Source Qualifier Prepare mapplet PreparedData target PreparedData source Transaction_Support mapplet FunctionCall mapplet Flat file target 2. Note the values for commit call, interval, return type, and connection properties in the AEP transformation of the FunctionCall mapplet. 3. Delete all the components except flat file source and source qualifier. 4. Click Transformation > Create, select SAP BAPI/RFC transformation, enter the name of the transformation as BAPI_EMPATTABS_GETDETAILS, and click Create. 11

Step 1 of the wizard appears. 5. Enter connection string parameters to connect to SAP with sapfrc.ini. Or, click Host Name and enter host name parameters to connect to SAP. Click Next. 6.

12 Step 1 of the wizard appears. 5. Enter connection string parameters to connect to SAP with sapfrc.ini. Or, click Host Name and enter host name parameters to connect to SAP. Click Next. 6. Optionally, enter a filter condition to filter the BAPI by name or description and click Get Objects. The wizards displays BAPIs that you can import. 7. Expand the list of objects and select the BAPI. 8. Click the Return Structure tab to configure the ReturnParameter. The following figure shows the return structure configuration: Optionally, you can configure the return structure after import with the Customize BAPI wizard. Note: In single stream mapping, return structure was configured in the FunctionCall mapplet. 9. Connect the Integration ID from the source qualifier to the Integration ID in the Scalar Input and the Table Input of the transformation. 10. Open the Target Designer. 11. Drag and drop the transformation into the Target Designer. The Designer creates the target definitions for scalar output, table output, and error output. 12. Connect the output groups from the transformation to the target definitions. 13. Save the mapping. 12

13 The following figure shows the updated mapping with the BAPI/RFC transformation: 14. Click Connections > Applications> in the Workflow Manager. The Application Connections Browser dialog box appears. 15. Select SAP RFC/BAPI Interface and click New. The Connection Object Definition dialog box appears. 16. Enter the connection details and click OK. 17. Open the session, s_bapi_activitytype. The Edit Tasks dialog box appears. 18. Select the transformation in the Mapping tab. 19. Select the type of connection as Application and the SAP RFC/BAPI connection that you created in the Connections pane. 20. Click Show Session Level Properties in the Properties pane and select Perform Commit. 21. Save the session. BAPI/RFC Sessions You must modify the session after you migrate the mapping to use BAPI transformation. Configure the following session properties when you configure a BAPI/RFC session: Commit behavior Caching Error handling Partitioning. Each partition makes separate BAPI/RFC calls to SAP. Verbose logging. The session log contains the information about the BAPI/RFC call return code, status, and detailed messages. You must create SAP RFC BAPI Interface application connections for the BAPIs you want to connect. When you configure a session, select an SAP RFC BAPI Interface application connection for the BAPI/RFC transformation. 13

14 Configuring Sessions After Migration You must edit the session properties and update the application connection after you modify the BAPI/RFC mapping. 1. Click Tools > Task Developer in the Workflow Manager. 2. Open the session that you want to modify. 3. Click Task > Edit. The Edit Tasks dialog box appears. 4. Click Mapping. 5. Select the BAPI/RFC transformation. 6. Choose SAP RFC BAPI Interface application connection. 7. Click OK. 8. Click Repository > Save. Author Narayan Sivaramakrishnan Senior Technical Writer Acknowledgements Thanks to Poornima Srikantesh, Lead Engineer QA, for her help in completing this article. 14

Increasing Performance for PowerCenter Sessions that Use Partitions

Increasing Performance for PowerCenter Sessions that Use Partitions 1993-2015 Informatica LLC. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying,