Table of Contents

Search

  1. Preface
  2. Part 1: Getting Started with PowerExchange for SAP NetWeaver
  3. Part 2: Data Integration Using PowerExchange for SAP Dynamic ABAP Table Extractor
  4. Part 3: Data Integration Using ABAP
  5. Part 4: IDoc Integration Using ALE
  6. Part 5: Data Integration Using BAPI/RFC Functions
  7. Part 6: Data Migration
  8. Part 7: Business Content Integration
  9. Part 8: SAP BW Data Extraction
  10. Part 9: Loading Data to SAP BI
  11. Appendix A: Data Type Reference
  12. Appendix B: Code Pages and Unicode Support
  13. Appendix C: Glossary

PowerExchange for SAP NetWeaver User Guide for PowerCenter

PowerExchange for SAP NetWeaver User Guide for PowerCenter

Steps to Configure Sessions for IDoc Mappings Using ALE

Steps to Configure Sessions for IDoc Mappings Using ALE

You can configure session properties for IDoc sessions using ALE.
To configure an IDoc session:
  1. In the Task Developer, double-click an SAP session to open the session properties.
  2. If you are configuring an outbound IDoc session, select a recovery strategy from the General Options in the Properties tab.
    To enable message recovery, select Resume from Last Checkpoint.
    If you enable message recovery, you can configure a value for the recovery cache folder from the Properties settings of the Mapping tab (Sources node). Or, use the default cache folder $PMCacheDir\.
  3. In the Config Object tab, configure advanced settings, log options, and error handling properties.
  4. Click the Mapping tab.
  5. From the Connections settings on the Mapping tab (Sources node), select the connection values for the sources.
    If you are configuring an outbound IDoc session, select an SAP_ALE_IDoc_Reader application connection for the Application Source Qualifier associated with the SAPALEIDoc source definition.
  6. If you are configuring an outbound IDoc session, click Properties.
  7. Optionally, edit the values for the Idle Time, Message Count, and Reader Time Limit terminating conditions.
    The Workflow Manager assigns the following default values to the terminating conditions:
    Terminating Condition
    Default Value
    Description
    Idle Time
    -1
    SAP can remain idle for an infinite period of time before the PowerCenter session ends.
    Packet Count
    -1
    PowerCenter Integration Service can read an infinite number of packets before the session ends.
    Reader Time Limit
    0
    PowerCenter Integration Service can read IDocs from SAP for an infinite period of time.
  8. Optionally, configure real-time flush latency.
    By default, the PowerCenter Integration Service does not run the session in real time. Default value is 0.
  9. On the Targets node, enter the connection values for the targets in the mapping.
    If you are configuring an inbound IDoc session, select an SAP_ALE_IDoc_Writer application connection for the SAPALEIDoc target definition.
  10. If you are configuring an inbound IDoc session, click the Properties settings.
  11. Edit the following properties:
    Property
    Description
    Packet Size
    Number of IDocs you want the PowerCenter Integration Service to send in a packet to SAP.
    Number of Retries
    Number of times you want the PowerCenter Integration Service to attempt to connect to the SAP system.
    Delay Between Retries
    Number of seconds you want the PowerCenter Integration Service to wait before attempting to connect to the SAP system if it could not connect on a previous attempt.
    Send IDoc Based on
    Select one of the following options:
    • Packet Size. The PowerCenter Integration Service commits IDocs to SAP based on the value you set for the Packet Size property. The PowerCenter Integration Service collects IDoc messages until the total count reaches the packet size. It then sends the messages as a packet to SAP.
    • Commit Call. The PowerCenter Integration Service commits IDocs to SAP based on the commit properties at every commit point.
    Do not select Generate Request ID. Use this property only when you configure send request workflows for business content integration.
  12. On the Transformations node, edit the following properties, depending on whether you are configuring an inbound or outbound IDoc session:
    Property
    Outbound/
    Inbound
    Description
    Duplicate Parent Row Handling
    Both
    Determines how the PowerCenter Integration Service handles duplicate parent rows. Choose one of the following values:
    • First Row. The PowerCenter Integration Service passes the first duplicate row to the target. The PowerCenter Integration Service rejects rows with the same primary key that it processes after this row.
    • Last Row. The PowerCenter Integration Service passes the last duplicate row to the target.
    • Error. The PowerCenter Integration Service passes the first row to the target. Rows that follow with duplicate primary keys increment the error count. The session fails when the error count exceeds the error threshold.
    Orphan Row Handling
    Both
    Determines how the PowerCenter Integration Service handles orphan rows. Choose one of the following values:
    • Ignore. The PowerCenter Integration Service ignores orphan rows.
    • Error. The session fails when the error count exceeds the error threshold.
    Extended Syntax Check
    Both
    Checks for IDocs that are not valid. Validating IDocs can decrease session performance.
    Row Level Processing
    Outbound
    PowerCenter Integration Service can process each row of an outbound IDoc according to the IDoc metadata and pass it to a downstream transformation. If you enable row-level processing, the PowerCenter Integration Service does not validate IDocs. Select to increase session performance.
    NULL Field Representation
    Inbound
    Determines how the PowerCenter Integration Service handles fields with a null value when preparing the data in IDoc format. Choose one of the following values:
    • Blank. The PowerCenter Integration Service inserts all blanks for the field.
    • Slash (/). The PowerCenter Integration Service inserts a single slash (/) for the field.
    Cache Directory
    Inbound
    Default directory used to cache inbound IDoc or DMI data. By default, the cache files are created in a directory specified by the variable $PMCacheDir. If you override the directory, make sure the directory exists and contains enough disk space for the cache files. The directory can be a mapped or mounted drive.
    Cache Size
    Inbound
    Total memory in bytes allocated to the PowerCenter Integration Service for the caching of data prepared by SAP/ALE IDoc Prepare or SAP DMI Prepare transformations. Default is 10 MB.
  13. Click OK.

0 COMMENTS

We’d like to hear from you!