Resolution:
Here are the details about the pre-commit stored procedure. This is normally used with Oracle apps deployments.

ADB will call the pre-commit stored procedure with the following syntax: {call &ltsp_name>(?, ?, ?)}

The stored procedure can be any name, but must have a fixed parameter list:
no return code and three OUT parameters:
??       RETURN_CODE int
??       SP_TEXT varchar
??       DO_ROLLBACK int

For ORACLE, the PL/SQL declaration would look like:

CREATE PROCEDURE &ltsp_name>
(RETURN_CODE OUT NUMBER, SP_TEXT OUT VARCHAR2, DO_ROLLBACK NUMBER) ??

Inside designer, the "Pre Commit Stored Procedure" option should be the &ltsp_name> only.
Because this store procedure is fixed on interface, you do not need to specify the parameters.

ADB will react differently depending on the values of the OUT parameters.
If DO_ROLLBACK = 0, ADB will commit the transaction and confirm the original message.

If DO_ROLLBACK <> 0, ADB will rollback the transaction and not confirm the message. Note, not confirming the message changes

the RVCM behavior. All subsequent RVCM messages will not be confirmed. It should only be done when this RVCM behavior is

really desired.
If RETURN_CODE = 0, ADB will assume the procedure was successful and write a success message to the SDK INFO trace role when

the verbose mode is used.
If RETURN_CODE <> 0, ADB will assume the procedure was not successful and write SP_TEXT to the SDK ERROR trace role (whether

verbose mode is on or off).
If the original message was sent with a reply subject, the status and return text will be sent back to the sender on the specified reply subject.