This fetcher is obsolete, use (Glue-2111) BEx Query Fetcher (BICS) instead.

The BEx Query Fetcher uses a BEx Query as a data source. For data read provide the BEx Query name and the BEx Query View name (optional). The BEx Query Fetcher supports filtering on query variables.

Creation of a BEx Query Fetcher

Perform the steps outlined in How to Create a Fetcher Object with the BEx Query Fetcher option selected in Component implementation the dropdown of step 4.

Activation of a BEx Query Fetcher

After creation, the object is in the saved state.

Mandatory inputs to fill before the activation

BEx Query
- name of the BEx Query for data read
BEx Query View (optional)
- name of the BEx Query created on top of the BEx Query for data read
Use customer-exit (optional)
- checkbox (unchecked by default)
- when checked, the query is executed with the values for variables provided by customer-exit (CMOD)
- changeable before each extraction

Optional inputs before the activation

Selection
- checkbox for each variable of the BEx Query that allows you to mark the variable as relevant for selection before the extraction. The checkbox is automatically set for the mandatory variables and is read-only.

BEx Query View

The BEx Query View is useful when you need to extract data from the modified navigational state of your query, e.g. drill down a free characteristic in rows or display a hidden key figure. You can also define multiple Views for a Query and then use them for extraction.

Customer-exit (CMOD) support

The BEx Query Fetcher supports customer-exit in query variables (CMOD). Check the example below.

Normally, when you execute a BEx Query via Query Monitor (TCODE RSRT), the variable screen displays values returned by the customer-exit (“before” phase) for a specific variable. See the screenshot below from the Query Monitor (TCode RSRT).

The Extraction Process report will not display these values as in RSRT. If you select the checkbox “Use customer-exit values” and leave the variable parameter blank, it executes the Query with the values from the customer-exit. See the screenshot below from the Extraction Process generated report.

If you fill the variable parameter in the Extraction Process report, the Query is executed with the specified selection and ignores the "Use customer-exit values" checkbox.

Browser not supported