Direct Drilldown from EBS Forms to Blitz Reports

You must use the Form assignment feature . First, identify the standard form name (e.g., ‘GL Enter Journals’) and the specific block names containing the data items (like Batch Name/Journal Name) by navigating through Help > About Oracle Applications > Current Form . Then, in the Blitz Report setup for the ‘GL Account Analysis’ report, you assign the form name and define the parameter passing logic . You configure the parameter default values to pull values from the specific form item names .

Once configured successfully, the Blitz Report is accessed from the Oracle standard form through a custom icon . When the user clicks this icon, the report launches with the parameters (such as GL Batch and Journal names) automatically defaulted based on the record they currently have focused on in the EBS form . This enables instant, context-sensitive drilldown.

You use the Block Restriction field in the assignment setup . If you enter the name of the navigation block (e.g., ‘GL_JE_LINES’), the report will only be accessible when the user is positioned within that block . If you leave the Block Restriction field empty, the Blitz Report will be available on *all* blocks of the assigned form, assuming the passed parameter values are identical across blocks .

Reports launched directly from custom forms, such as via the custom icon (e.g., on a `when-button-pressed` trigger), typically utilize a PL/SQL API call that returns a BLOB output, often bypassing the standard concurrent program submission , . If the execution fails, the resulting error message or status is captured by the API wrapper (e.g., `x_return_status` and `x_msg_data` in the `XXEN_API.RUN_REPORT` procedure) and would need to be handled and displayed by the custom form’s error logic , . If you are using the setup procedure provided, the report execution status would appear in the output.