What must you do to fix the issue?

The Orders form has three blocks: Orders, Orders_Items, and inventories. It also has a button
labeled Next Block with a When-Pressed trigger.
IF :SYSTEM.cursor_block = ‘orders’ THEN
GO_BLOCK(‘order_items’);
ELSIF :SYSTEM.cursor_block = ‘order_items’ THEN
GO_BLOCK(‘inventories’);
ELSIF :SYSTEM.cursor_block = ‘inventories’ THEN
GO_BLOCK (‘orders’);
END IF;
The button is not functioning correctly; it does not cause navigation to occur. What must you do to
fix the issue?

A.
Change all occurrences of :SYSTEM.cursor_block to :SYSTEM.trigger_block.

B.
Use system variablesinthe GO_BLOCK statements.

C.
Change the block names to uppercaseinthe GO_BLOCK statements.

D.
Change the block names to uppercaseinthe condition (IF …THEN) statements.

E.
instead of naming the block to navigate to, replace the GO_BLOCK built-inwith NEXT_BLOCK

F.
Move the code to a PL/SQL program unit.

Explanation:
SYSTEM.trigger_block: The block that the input focus was in when the trigger
initially fired.
Note: Uses for Trigger Focus Variables
The variables for locating trigger focus are useful for navigating back to the initial block, record,and
item after the trigger code completes. For example, the trigger code may navigate to otherblocks,
records, or items to perform actions upon them, but after the trigger fires, you may wantthe cursor
to be in the same item instance that it was in originally. Because the navigation in thetrigger

occurs behind the scenes, the user will not even be aware of it.