SAP Reports / Programs

SPI_ALERT_TEST_HANGQUEUE SAP ABAP Report - PMI Alerting: Hanging Queue Test Report







SPI_ALERT_TEST_HANGQUEUE is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). Below is the basic information available for this SAP report including which OBJECTS it interacts with such as TABLES, FUNCTION MODULES, INCLUDES ETC. Also check out the submitted Comments related to this SAP report or see any standard documentation available.

If you would like to execute this report or see the full code listing simply enter SPI_ALERT_TEST_HANGQUEUE into the relevant SAP transactions such as SE38 or SE80


ABAP code to call this SAP report using the submit statement

This report can be called from another progam/report simply by using the ABAP SUBMIT statement, see below for example ABAP code snipts of how to do this.






SUBMIT SPI_ALERT_TEST_HANGQUEUE. "Basic submit
SUBMIT SPI_ALERT_TEST_HANGQUEUE AND RETURN. "Return to original report after report execution complete
SUBMIT SPI_ALERT_TEST_HANGQUEUE VIA SELECTION-SCREEN. "Display selection screen of submitted report to user
    See more syntax options for the ABAP SUBMIT statement


Text pool values


Selection Text: PBRCH_B = Branch B (Metric RT-MB-EB)
Selection Text: PBRCH_A = Branch A (Metric RT-S-EA)
Title: PMI Alerting: Hanging Queue Test Report
Text Symbol: R07 = Error Runtime B
Text Symbol: R08 = Event Runtime B
Text Symbol: S01 = Start Test
Text Symbol: S02 = Analyze Tests
Text Symbol: T01 = Test Configuration
Text Symbol: T02 = Time for creating all instances (step S) in minutes
Text Symbol: T03 = Number of instances to be created
Text Symbol: T04 = Select Error Situation
Text Symbol: T05 = In Branch A, a 'hanging queue' is simulated so that the end A
Text Symbol: T06 = steps are created only after the error situation is created, however some
Text Symbol: T07 = In branch B, runtimes are generally longer, with the runtimes of some
Text Symbol: T08 = instances being particularly long.
Text Symbol: T09 = end A steps are skipped.
Text Symbol: T10 = Approximate expected test runtime (minutes)
Text Symbol: TB1 = Display Events
Text Symbol: TB2 = Display Logs
Text Symbol: TD1 = Total number of instances
Text Symbol: TD2 = Number of instances per package:
Text Symbol: TD3 = Number of Packages:
Text Symbol: TD4 = Approximate test runtime (min.):
Text Symbol: TD5 = Number of expected events:
Text Symbol: TD6 = Runtime for 'error' instances B (sec.):
Text Symbol: TD7 = Runtime for 'event' instances B (sec.):
Text Symbol: TI1 = Tests for Process <&>
Text Symbol: VF1 = Before error situation:
Text Symbol: WF1 = During error situation:
Text Symbol: R06 = Error Runtime A
Text Symbol: A01 = Queue hanging in branch A (metric RT-S-EA)
Text Symbol: B01 = Queue hanging in branch B (metric RT-MB-EB)
Text Symbol: BN1 = of which have a considerably increased runtime
Text Symbol: E01 = The required metrics are not configured for this process.
Text Symbol: EVE = of which no end A step or with considerably increased runtime (in B)
Text Symbol: FC1 = Time Stamp
Text Symbol: FC2 = Metric
Text Symbol: FC3 = Total Instances





Text Symbol: FC4 = Expected Events
Text Symbol: FC5 = Created Events
Text Symbol: FC6 = Result
Text Symbol: FC7 = Test Date
Text Symbol: FC8 = Test Time
Text Symbol: IC1 = Events are (still?) missing.
Text Symbol: IC2 = The result is correct.
Text Symbol: IC3 = Too many events.
Text Symbol: M01 = Only select one test for this function
Text Symbol: NF1 = After error situation:
Text Symbol: NMA = of which without step end A
Text Symbol: NO1 = Number of instances without runtime overrun
Text Symbol: NOE = Events within the problem situation:
Text Symbol: NOT = Total:
Text Symbol: NW1 = Number of instances with runtime overrun
Text Symbol: P02 = Process (taken from Test Alerting)
Text Symbol: R01 = Total No. Instances
Text Symbol: R02 = Error in A
Text Symbol: R03 = Events in A
Text Symbol: R04 = Errors in B
Text Symbol: R05 = Events in B


INCLUDES used within this REPORT SPI_ALERT_TEST_HANGQUEUE

No INCLUDES are used within this REPORT code!


TABLES used within REPORT and the associated SELECT statement:

No SAP DATABASE tables are accessed within this REPORT code!


Function Modules used within report and the associated call statement:

LVC_FIELDCATALOG_MERGE call function 'LVC_FIELDCATALOG_MERGE' exporting * I_BUFFER_ACTIVE = i_structure_name = 'SSPITSTHGQOV' * I_CLIENT_NEVER_DISPLAY = 'X' * I_BYPASSING_BUFFER = changing ct_fieldcat = et_fcat.

ICON_CREATE call function 'ICON_CREATE' exporting name = icon_yellow_light info = text-ic1 importing result = is_stat-result exceptions icon_not_found = 1 outputfield_too_short = 2 others = 3.

ICON_CREATE call function 'ICON_CREATE' exporting name = icon_green_light info = text-ic2 importing result = is_stat-result exceptions icon_not_found = 1 outputfield_too_short = 2 others = 3.

ICON_CREATE call function 'ICON_CREATE' exporting name = icon_red_light info = text-ic3 importing result = is_stat-result exceptions icon_not_found = 1 outputfield_too_short = 2 others = 3.

ICON_CREATE call function 'ICON_CREATE' exporting name = icon_yellow_light info = text-ic1 importing result = -result exceptions icon_not_found = 1 outputfield_too_short = 2 others = 3.

ICON_CREATE call function 'ICON_CREATE' exporting name = icon_green_light info = text-ic2 importing result = -result exceptions icon_not_found = 1 outputfield_too_short = 2 others = 3.

ICON_CREATE call function 'ICON_CREATE' exporting name = icon_red_light info = text-ic3 importing result = -result exceptions icon_not_found = 1 outputfield_too_short = 2 others = 3.

PROGRESS_INDICATOR





call function 'PROGRESS_INDICATOR' exporting i_output_immediately = spi_on i_text = l_text.

SPI_ALERT_TEST_HANGQUE_EVENTS call function 'SPI_ALERT_TEST_HANGQUE_EVENTS' starting new task l_task exporting ip_total_time = gc_total_time ip_no_events = g_err ip_perc_of_time = 90 ip_proctype = g_proctype ip_metric_name = l_metric_name exceptions ex_unknown_metric = 1 system_failure = 2 message l_msg_v2 communication_failure = 3 message l_msg_v2 others = 4.

SPI_ALERT_TEST_HANGQUE_OTHERS call function 'SPI_ALERT_TEST_HANGQUE_OTHERS' starting new task l_task exporting ip_no_insts = l_no_insts * IP_RUNTIME_A = 0 * IP_RUNTIME_B = 0 ip_proctype = g_proctype exceptions system_failure = 1 message l_msg_v2 communication_failure = 2 message l_msg_v2 others = 3.

SPI_ALERT_TEST_HANGQUE_OTHERS call function 'SPI_ALERT_TEST_HANGQUE_OTHERS' starting new task l_task exporting ip_no_insts = l_no_insts ip_runtime_a = l_runtime_a * IP_RUNTIME_B = 0 ip_proctype = g_proctype exceptions system_failure = 1 message l_msg_v2 communication_failure = 2 message l_msg_v2 others = 3.

SPI_ALERT_TEST_HANGQUE_OTHERS call function 'SPI_ALERT_TEST_HANGQUE_OTHERS' starting new task l_task exporting ip_no_insts = l_no_insts * ip_runtime_a = l_runtime_a ip_runtime_b = g_limit_b ip_proctype = g_proctype exceptions system_failure = 1 message l_msg_v2 communication_failure = 2 message l_msg_v2 others = 3.

SPI_ALERT_TEST_HANGQUE_OTHERS call function 'SPI_ALERT_TEST_HANGQUE_OTHERS' starting new task l_task exporting ip_no_insts = l_no_insts * IP_RUNTIME_A = 0 * IP_RUNTIME_B = 0 ip_proctype = g_proctype exceptions system_failure = 1 message l_msg_v2 communication_failure = 2 message l_msg_v2 others = 3.

PROGRESS_INDICATOR call function 'PROGRESS_INDICATOR' exporting i_output_immediately = 'X' i_text = l_indicator.

PROGRESS_INDICATOR * call function 'PROGRESS_INDICATOR' * exporting * i_output_immediately = spi_on * i_text = l_text.

SPI_ALERT_TEST_HANGQUE_EVENTS * call function 'SPI_ALERT_TEST_HANGQUE_EVENTS' * starting new task l_task * exporting * ip_total_time = gc_total_time * ip_no_events = p_event * ip_perc_of_time = l_perc * ip_proctype = p_proctp * ip_metric_name = l_metric_name * exceptions * ex_unknown_metric = 1 * system_failure = 2 message l_msg * communication_failure = 3 message l_msg * others = 4.

SPI_ALERT_TEST_HANGQUE_OTHERS * call function 'SPI_ALERT_TEST_HANGQUE_OTHERS' * starting new task l_task * exporting * ip_no_insts = l_no_insts ** IP_RUNTIME_A = 0 ** IP_RUNTIME_B = 0 * ip_proctype = p_proctp * exceptions * system_failure = 1 message l_msg * communication_failure = 2 message l_msg * others = 3.

SPI_ALERT_TEST_HANGQUE_OTHERS * call function 'SPI_ALERT_TEST_HANGQUE_OTHERS' * starting new task l_task * exporting * ip_no_insts = l_no_insts * ip_runtime_a = l_runtime_a ** IP_RUNTIME_B = 0 * ip_proctype = p_proctp * exceptions * system_failure = 1 message l_msg * communication_failure = 2 message l_msg * others = 3.

SPI_ALERT_TEST_HANGQUE_OTHERS * call function 'SPI_ALERT_TEST_HANGQUE_OTHERS' * starting new task l_task * exporting * ip_no_insts = l_no_insts ** ip_runtime_a = l_runtime_a * ip_runtime_b = l_runtime_b * ip_proctype = p_proctp * exceptions * system_failure = 1 message l_msg * communication_failure = 2 message l_msg * others = 3.

SPI_ALERT_TEST_HANGQUE_OTHERS * call function 'SPI_ALERT_TEST_HANGQUE_OTHERS' * starting new task l_task * exporting * ip_no_insts = l_no_insts ** IP_RUNTIME_A = 0 ** IP_RUNTIME_B = 0 * ip_proctype = p_proctp * exceptions * system_failure = 1 message l_msg * communication_failure = 2 message l_msg * others = 3.



Contribute (Add Comments)

Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.

The contribute/comments section below therefore offer's an opportunity for anyone to add additional information. This can be anything from useful hints, tips and screen shots to relevant SAP notes or anything else you feel is relevant to this report.

This will then be available for everyone to easily find by simply searching on the report name SPI_ALERT_TEST_HANGQUEUE or its description.