Ansicht
Dokumentation

Availability control: New features in Release 3.0C ( RELNPS_30C_VERFÜGKONTR )

RFUMSV00 - Advance Return for Tax on Sales/Purchases   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Short text

Availability control: New features in Release 3.0C

Description

The following new features have been implemented to simplify the handling of availability control for projects, internal orders and maintenance orders :

1. Activation type indicator in the budget profile
2. Changes in tolerance limit definition
3. Changes to assigned value reconstruction

Until now, it was the entries in the "Tolerance Limits for Availability Control" table which determined how availability control was activated. The options were as follows:

1. No entry for the budget profile -> Availability control not activated
2. Active entries, but no entry for transaction group 99 -> Availability control activated automatically during budget allocation.
3. Entry for transaction group 99 -> Availability control only activated by background activation

This control is now represented by the Activation type indicator in the budget profile.
There are three different types:

• 0 = Cannot be activated

Availability control cannot be activated - that is, active availability control is not possible for projects/orders with this budget profile.

Note:
This activation type can cause an already active availability control to be deactivated.

• 1 = Automatic activation during budget allocation

Availability control is activated automatically during budgeting - that is, availability control is active as soon as a budget is entered for the project/order.
Note:
Budgeting is only possible if at least one tolerance limit is defined for the budget profile.

• 2 = Background activation when credit limit is exceeded

Availability control can only be activated using the background activation function. A credit limit used is stored in the budget profile. The credit limit used represents relationship between funds committed and the budget as a percentage. Availability control is activated by the system for all projects/orders whose funds committed exceed the credit limit stored in the budget profile. An entry of 80% means that availability control is activated by the background activation program as soon as the funds committed exceed 80% of the budget.

For this, you must, as before:

• stipulate the projects/orders, for which availability control should be activated by background activation.

• plan the frequency of background processing for availability control activation.

(For detailed information on this topic, please refer to the section "Availability control" in the document "Project System".)
Note:
You also need to maintain the tolerance limits for the budget profile to check postings.

Activation type 2 makes maintenance of a tolerance limit for transaction group 99 unnecessary.

Changes to the budgeting function

The "Activation type" indicator has brought about the following changes in the budgeting function:

• The system issues a warning for a profile that is not maintained

If availability control detects that an activation type is not maintained for the current budget profile, the system issues a warning. The system tries to derive an activation type from the "old" tolerance limits (that is, limits defined in releases prior to 3.0C).

• The system issues an error message if tolerance limits are missing for activation type 1 or 2.

If you have specified in the budget profile that active availability control is to be used, you must define tolerance limits.

• The function "Save without checking" (budget allocation) is not possible with activation type 1.

• The system issues a warning if a budget is not entered

If activation type 1 or 2 is set, the system checks whether the budget has already been entered according to the settings "against overall" or "against released". If this is not the case, the system issues a warning. Availability control is, however, also activated for a budget = 0 currency units.

• Activate availability control function for a chosen object

The "Availability control" function for explicit activation of availability control for a project or an order is no longer used.

Tolerance limits are determined in relation to an organizational unit (controlling area or financial management area). The absolute tolerance limit is specified in controlling area currency.

The maintenance of the tolerance limit in percentage form (credit limit used) is set to 100% by default. The corresponding action is then triggered when xx% of the available budget is exceeded.

Maintenance of the active indicator is redundant.

Example:

Old entry	New entry
-10%	90%
+20%	120%

+20%

Up to now, certain system tables were read for a potential budget object (WBS element, internal order, maintenance order; an order for the project is not a potential budget object since orders for the project cannot be budgeted) to establish whether availability control is active or not. These database accesses cause unnecessary performance losses for customers who do not use availability control.

For this reason, the system status "availability control active", that displays whether availability control is active on an object or not has been defined for Release 3.0C.

When posting to an object, the new status is now checked first. If this does not yet exist, the system checks according to the previous logic whether availability control is active or not. If availability control is active on the object, the status "availability control active" is set.

+20%

The reconstruction of assigned values is carried out using a separate function independent of background activation. You can also select projects or orders according to a particular budget profile. It makes sense to carry out a reconstruction of assigned values after changes have been made to the budget profile affecting the setting for availability control.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

For more information about availability control, read

• Projects

• Internal orders

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

General Material Data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 8174 Date: 20240523 Time: 080918     sap01-206 ( 162 ms )