Ansicht
Dokumentation

Transfer transaction type in areas for historical transfer ( RELNAA_30E_ZUGANG_VBUND )

Addresses (Business Address Services)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Short text

Transfer transaction type in areas for historical transfer

Description

As of Release 3.0E, when posting an acquisition from an affiliated company, the system will check the original transaction type used for posting the orginal asset. The system will determine if the orginal transaction type was for asset acquisitions from previous years, or for current asset acquisitions. The system then sets the appropriate transfer transaction type in the asset line items.

The system does this, based on the assumption that the transaction type that is specified as the default transaction type is of the type for asset acquisitions from previous years.

When you use the standard transaction type 150, then the system changes to 380, as of Release 3.0E, instead of 360.

In your enterprise, you may need to distinguish between acquisitions from previous years and acquisitions in the current year. You can achieve this end by creating an additional transaction type, that corresponds to transaction type 150, but is assigned to transaction type group 40.

You should then enter the values separately according to whether they represent acquisitions from previous years or the current year.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

Fill RESBD Structure from EBP Component Structure   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 1940 Date: 20240419 Time: 070217     sap01-206 ( 36 ms )