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

Inserting the ZPMSENDSTATUS ABAP Program

Inserting the ZPMSENDSTATUS ABAP Program

Before you can insert the ZPMSENDSTATUS ABAP program into a process chain, you must have imported the program into SAP BI.
  1. In the
    Process Chain Maintenance Planning View
    window, click
    Process Types
    .
  2. From the
    Process Types
    menu, click
    General Services
    ABAP Program
    .
    The
    Insert ABAP Program
    dialog box appears.
  3. Click
    Create
    .
    The
    ABAP Program
    dialog box appears.
  4. Enter a unique name for the ABAP program process variant and enter a description.
  5. Click
    Enter
    .
    The
    Process Maintenance: ABAP Program
    window appears.
  6. In the
    Program Name
    field, click the
    Browse
    button to select the ZPMSENDSTATUS ABAP program.
  7. Click
    Change
    next to the
    Program Variant
    field.
    The
    ABAP: Variants - Initial Screen
    window appears.
  8. Click
    Create
    .
  9. In the
    ABAP: Variants
    dialog box, enter a name for the ABAP variant and click
    Create
    .
    The
    Maintain Variant
    window appears.
  10. For the
    DEST
    field, select the name of the RFC destination.
  11. For the
    INFPARAM
    field, enter one of the following options:
    • PSA if the previous process loaded to the PSA.
    • Data Target if the previous process loaded to a data target.
  12. For the
    CONTEXT
    field, enter BW LOAD.
  13. For the
    INFOPAK
    field, enter the technical name of the InfoPackage.
    For example, ZPAK_439OS93K56GKQT7HQT5TFV1Z6.
  14. Click
    Save and Exit
    in the
    Maintain Variant
    window.
  15. Click
    Save and Exit
    in the
    ABAP Variants
    window.
  16. Click
    Save and Exit
    in the
    Process Maintenance: ABAP Program
    window.
  17. Click
    Enter
    in the
    Insert ABAP Program
    dialog box.
    The ABAP program appears in the
    Process Chain Maintenance Planning View
    window.
  18. Click the InfoPackage process description and drag to link the InfoPackage process to the ABAP program.
    When prompted, click
    Successful condition
    .
    When you use a 7.x DataSource to load to the PSA, you must link the InfoPackage process to the Data Transfer Process and then link the Data Transfer Process to the ABAP program.
  19. Optionally, insert additional loading processes into the process chain.
    Use the instructions in Inserting an InfoPackage Process.
  20. Insert the ZPMSENDSTATUS program after each loading process.
  21. In the
    Process Chain Maintenance Planning View
    window, click
    Checking View
    and then click
    Activate
    .
  22. Click
    Execute
    and assign the process chain to a specific SAP BI server.
    If you scheduled the process chain to run immediately, the process chain starts running on the assigned SAP BI server.
  23. Optionally, to view the status of the process chain, click
    Job Overview
    .
    The
    Simple Job Selection
    window appears.
  24. Enter selection criteria to specify which process chains you want to monitor and click
    Execute
    .
    The
    Job Overview
    window appears.
  25. Select the BI_PROCESS_ABAP job and click
    Job Log
    .
    The
    Job Log Entries
    window appears. It includes an entry about the status of the PowerCenter workflow that the process chain was configured to start.

0 COMMENTS

We’d like to hear from you!