Table of Contents


  1. Preface
  2. Using the Designer
  3. Working with Sources
  4. Working with Flat Files
  5. Working with Targets
  6. Mappings
  7. Mapplets
  8. Mapping Parameters and Variables
  9. Working with User-Defined Functions
  10. Using the Debugger
  11. Viewing Data Lineage
  12. Comparing Objects
  13. Managing Business Components
  14. Creating Cubes and Dimensions
  15. Using the Mapping Wizards
  16. Datatype Reference
  17. Configure the Web Browser

Creating Breakpoints

Creating Breakpoints

Before you run the Debugger, use the Breakpoint Editor in the Mapping Designer to create breakpoint conditions in a mapping. You can create data or error breakpoints for transformations or for global conditions. When you run the Debugger, the Integration Service pauses the Debugger when a breakpoint evaluates to true. You can review and modify transformation data, and then continue the session.
You cannot create breakpoints for mapplet Input and Output transformations.
A breakpoint can consist of an instance name, a breakpoint type, and a condition. When you enter breakpoints, set breakpoint parameters in the following order:
  1. Select the instance name.
    Choose to create a global breakpoint or a breakpoint against a single transformation within the mapping or mapplet.
  2. Select the breakpoint type.
    Choose to evaluate error or data conditions. You can also choose the number of rows to skip for the breakpoint type.
  3. Enter the condition.
    Enter data conditions for global or transformation data breakpoints. You cannot enter conditions for error breakpoints.
After you set the instance name, breakpoint type, and optional data condition, you can view each parameter in the Breakpoints section of the Breakpoint Editor:
  • Instance name.
    From the Instance Name parameter.
  • Breakpoint enabled flag.
    Enable in the View Breakpoints section.
  • Breakpoint number.
    The Designer assigns a number based on the quantity of breakpoints you create in the mapping. These numbers are sequential. If you remove a breakpoint, the Designer renumbers them when you close and reopen the Breakpoint Editor.
  • Breakpoint type.
    From the Breakpoint Type section.
  • Number of rows to skip.
    From the Breakpoint Type section.
  • Data condition.
    From the Condition section.
The following figure shows the parameters in the Breakpoints section:
The Breakpoints section displays global breakpoints and breakpoints for the Lookup and Aggregator transformations.
For the Lookup transformation, LKP_Store, the check indicates the breakpoint is enabled. “#2” is the sequential breakpoint number, “Data” indicates the breakpoint type, “0” indicates the number of breakpoint rows to skip, and “STORE_ID=[2641]” is the data condition.

Updated July 02, 2020