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

Session Load Mode

Session Load Mode

The PowerCenter Integration Service stores the rows in memory until the total row count reaches the packet size. It then loads the rows stored in the buffer into the SAP ECC target table as a packet. You can choose to load data into the SAP tables in normal or bulk mode.
Normal mode inserts the rows one by one into the target table. Bulk mode inserts rows into the SAP ECC target table at the same time.
Normal mode is the default load method. You must use the normal mode to load data into the SAP system for any or all of the following conditions:
  • The mapping contains an Update Strategy transformation.
  • The packet has mixed operations.
  • You want to override the default UPDATE statement for each target in a target definition.
  • You want to view the SAP rejected rows in the bad file.
  • You manually edit the primary keys in the Designer and want to update or delete rows based on the modified key.
  • You want to update select fields in the SAP target table.
When you load data using bulk mode, all the rows within a packet must have the same operation, such as insert, update, or delete. When the rows within a packet have mixed operations, then the PowerCenter Integration Service reverts to normal load for the packet.
When the PowerCenter Integration Service shifts from bulk loading to normal loading, it writes an informational message in the sessions log. When a bulk load fails, PowerCenter Integration Service updates the session log with load statistics. It updates the session log with the number of rows in the packet that were loaded into SAP and the number of rows that were rejected. The PowerCenter Integration Service does not write the reject rows rejected by SAP in the reject file that caused the bulk load to fail.

0 COMMENTS

We’d like to hear from you!