ABAPCALL_FUNCTION_EXC_SHORT_FORM - CALL FUNCTION EXC SHORT FORM

CPI1466 during Backup   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

CALL FUNCTION EXCEPTIONS - Short form

Obsolete Syntax

CALL FUNCTION func ...
                   EXCEPTIONS exc1 exc2 ...

Effect

This short form for specifying non-class-based exceptions in theparameterlist of the statement CALL FUNCTION is obsolete. It has the same effect as the following:

CALL FUNCTION func ...
                   EXCEPTIONS exc1 = 1
                              exc2 = 1
                              ...

Each exception listed after EXCEPTIONS that is not assigned to an explicit return code using = is given the value 1 implicitly.

Notes

• This short form is extremely error-prone and should never be used.
  
• Both the short form and the complete form can appear in a CALL FUNCTION statement.
  

Example

The syntax of the following function module call is correct, but can have unpredictable results.

CALL FUNCTION func EXCEPTIONS = 4.

The developer probably expected the following:

CALL FUNCTION func EXCEPTIONS OTHERS = 4.

The complete form of the statement is as follows, however:

CALL FUNCTION func EXCEPTIONS = = 1
                             4 = 1.

Since exceptions called "=" are not possible, and exceptions called "4" are unlikely, then this call will almost certainly not catch any exceptions, even though it is intended to catch every exception.

CPI1466 during Backup   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.


Length: 2521 Date: 20120518 Time: 200217     triton ( 69 ms )