Ansicht
Dokumentation

EXIT_SAPLC107_001 - DE-EN-LANG-SWITCH-NO-TRANSLATION

Addresses (Business Address Services)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Functionality

This function exit is always called by the system when changes are made to a value assignment instance or its characteristic values, or to other detail data (source, usage, and so on). You can use it to log changes to the instances and make simple corrections to the characteristic values if necessary.

When the function exit is called, no data save needs to have taken place. This is done at a later stage within the application. It is possible that the user may decide not to save the data changes to the value assignment instances and to discard them.

Before you use this function exit, you should check whether your requirements cannot be better fulfilled by the method AT_SAVE_CHECK of the Business Add-In EHSS_SPEC_CHECKS, which is called by the system immediately before the data save. You should give priority to the method of the Business Add-In particularly for larger corrections you may want to make to the characteristic values.

Description of parameters:

I_CALL_SCENARIO

This parameter describes the scenario in which this function exit is called. It can have the following values:

• 1

With this parameter value, the function exit is called when the user makes changes to value assignment instances outside the Value Assignments tab page. It is called, for example, when changes are made on the Usage, Source, or Assessment tab pages.

• 2

With this parameter value, the function exit is called when the user makes changes to value assignment instances on the Value Assignments tab page.

I_ACTYPE

The values of this parameter can be found in the include CBUI03 (only relevant in scenario 1).

I_TRTYPE

The values of this parameter can be found in the include CBUI03 (only relevant for scenario 1).

I_KEYPATH

Compare this with the structure RCGKPATH in the dictionary. The ESTCAT field contains the current value assignment type. (This field is relevant for scenarios 1 and 2. The other fields are only relevant for scenario 1.)

I_ADDINF

In the fields VALDAT and AENNR, this parameter contains the current key date and the current change number. Compare this with the structure RCGADDINF in the dictionary.

I_OKCODE

This parameter contains the current OK code (when calling scenario 1).

I_VA_IORECORD

This parameter contains the values of the current value assignment instance that are stored in the ESTVA table (EHS: Value Assignment) (only relevant for scenario 1).

E_FLG_CHANGED

This parameter indicates that a change has been made to the characteristic values during the processing of this function exit. The parameter is only relevant for scenario 1 as scenario 2 occurs when the X_API_PROP_DATA_TAB table is being written to the classification system. In scenario 1, E_FLG_CHANGED = TRUE must be set so that the changes to X_API_PROP_DATA_TAB take effect. (The parameter was introduced to prevent unnecessary writing and thus improve performance. Writing takes place, however, in scenario 2.)

X_API_PROP_DATA_TAB

This internal table contains the characteristic values for the current value assignment instance. You can compare its structure with the type ESPRH_APIPR_TAB_TYPE in the ESPRH type group.

X_ADD_PARAMETERS

(This parameter is not in use at the current time. It was introduced so that the function exit interface can be enhanced to include new parameters in later versions of EH&S. These new parameters will then simply be added to the type ESP7_ADD_PARAMS_TYPE in the ESP7 type group as new components.)

Example

Notes

The module is called in the function C107_CUSTOMER_FUNCTION_CALL.

Before testing your source code, it may be useful to position a 'soft' breakpoint (by choosing Utilities -> Breakpoints -> Set) within the C160_BREAK_POINT function at the position indicated. This function is then called at points in the standard coding of the EH&S System at which internal checks are carried out. If an error occurs, you go directly into the debugging mode. By choosing 'Execute' you can go to the point in the coding at which the error occurred. Also note the relevant comments in the coding of the C160_BREAK_POINT function and the BREAK_POINT macro in include CBUI18. (This procedure means that you do not have to find the appropriate point in the coding if a program error occurs. You can also use the BREAK_POINT, RAISE_ERROR, CHECK_SUBRC macros and the C160_BREAK_POINT function to implement checks in your own source code.)

The C14P_TREE_REPORT and C14P_TREE_REPORT_WITH_CHARACT function modules generate a list that contains technical data for a property tree.

Further information

Parameters

E_FLG_CHANGED
I_ACTYPE
I_ADDINF
I_CALL_SCENARIO
I_KEYPATH
I_OKCODE
I_TRTYPE
I_VA_IORECORD
X_ADD_PARAMETERS
X_API_PROP_DATA_TAB

Exceptions

ILLEGAL_INPUT
INTERNAL_ERROR

Function Group

XC1A

TXBHW - Original Tax Base Amount in Local Currency   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 5995 Date: 20240604 Time: 065001     sap01-206 ( 127 ms )