Get Example source ABAP code based on a different SAP table
ABAP_AMDP in ABAP Release 7.72 ITOC
ABAP_MODIFICATION_NN AMDP Scalar Functions>
AMDP> scalar functions are now supported alongside AMDP table functions>. The AMDP function implementation> of an AMDP scalar function has an elementary return value and can be used in ABAP like a regular function method.
ABAP_MODIFICATION_NN Restrictions Removed>
When a replacement parameter declared using DEFAULT>> is specified for an elementary input parameter of an AMDP method>, the following (previously undocumented) restrictions were lifted:
Constants declared using the addition VALUE IS INITIAL>> can now be specified for the data types d>, t >, and x>. This previously produced a syntax error.
Constants declared using the addition VALUE '00010101'>> can now be specified for the data type d>, or the literal '00010101'> can be specified directly. Both previously produced a syntax error.
Constants declared by specifying numeric literals after VALUE>> and whose lengths are not precisely 8 or 6 can now be specified for the data types d> and t>. This previously produced a syntax error. Until now, values of literals with lengths of precisely 8 or 6 were handled like a string. This incorrect behavior was also modified and the numeric value is handled as the number of days since 01.01.001 or as the number of seconds since 00:00:00. This modification is incompatible if an AMDP procedure> or function> with an input parameter of this type is called from other database procedures> or functions> without an actual parameter being assigned to the parameter in question. In AMDP methods, the addition DEFAULT> now behaves in the same way as in regular methods. It still cannot be specified for the data types string>, xstring>, decfloat16>, and decfloat34>, however, and no literals can be specified that cannot be converted into the data type of the input parameter.