(Glue 2402) (Obsolete) BEx Query Fetcher

This fetcher type is obsolete. Use the (Glue 2402) BEx Query Fetchers (BICS) instead.


BEx Query Fetchers uses a BEx query as their data source. They provide the BEx query name and the BEx query view name (optional) for the data read. They also support filtering on query variables.

Creating BEx Query Fetchers

Perform the steps provided under Creating Fetcher Objects and selectBEx queryFetcher from the Component implementation the drop-down of step 4.

Activating BEx Query Fetchers

After creation, the object is in the saved state.

The following information is mandatory before the activation:

  • BEx Query
    • Name of the BEx query for the data read
  • BEx Query View (optional)
    • Name of the BEx query created on top of the BEx query for the data read
  • Use customer-exit (optional)
    • Checkbox (deselected by default)
    • If selected, the query is executed with the values for variables provided by the customer-exit (CMOD)
    • Can be changed before each extraction

The following information is optional 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

You can use the BEx query view to extract data from the modified navigational state of your query, for example 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 the extraction.


Customer-Exit (CMOD) Support

The BEx Query Fetcher supports customer-exit in query variables (CMOD). For more information, see example below.

Usually, when you execute a BEx query via the Query Monitor (transaction 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.

The Extraction Process report does not display these values as in transaction RSRT. If you select the option 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 option Use customer-exit values check-box.