Activar control de disponibilidad ANTES de asignar Presupuesto

Nota :

Note 602588 - Availability control before budgeting

En resumen 2 soluciones:

1. USER EXIT  
2. Asignación de un status de usuario original que impida TODO, y que sea borrado tras la operación asignación o modificación de presupuesto.

Esto impide la imputación de costos comprometidos (que se pueden realizar incluso aunque el proy/pep no esté liberado)

Symptom

You create an order or a project.
In the relevant budget profile, you determine that an availability control is to take place (activation type = 1 or 2).
You have not entered any budget for the order or for the project yet.
(With availability control against releases for the project: You have not entered any releases for the project yet.)

Problem: In this status, debits (purchase requisitions, purchase orders, as of the status 'Released' invoices also) can be posted to the order or to the WBS elements of the project, as the availability control has not yet been activated.

How can this be prevented?

Other terms

ME21, ME21N, ME51, ME51N, MR01, MIRO, FB01, FB50
No availability control

Reason and Prerequisites

Due to technical and performance reasons, the availability control can only be activated if budget already exists for the order or for at least one WBS element of the project.

Solution

There are three workaround solutions for this problem.

1. Activating availability control without any budget (user exit as of Release 4.6C)

              You can use a user exit to activate the availability control for the order or for the project without any existing budget. For further details, see Note 599813.

2. Entering a dummy budget

              Enter an original budget, for example, to the amount of a currency unit (transaction KO22 or CJ30) in the order or in a top WBS element of the project.

              If you have set

a) activation type 2 (background activation) or

b) availability control against releases (possible only with projects) for the availability control,

              subsequently activate the availability control explicitly with transaction KO30 or CJBV.

              Afterwards, reset the original budget with the same transaction (KO22 or CJ30) to zero.

              The availability control is now active in the order or project, even though the budget is still zero.

3. Solution by using a user status profile

              Restriction: You can only use this solution for WBS elements if you want to budget all account assignment elements. In other words: If account assignment elements that are to remain without a specific budget exist in a project, the solution described in the following section cannot be used.
It cannot be used either, if allotted funds are not to be assigned to WBS elements, but to subordinate orders, networks or network transactions instead.

              Preparation: If you do not use any user status profile for your orders or WBS elements, use transaction OK02 to create a user status profile and assign it to the 'Internal order' or 'WBS element' object category.
In addition, provide the relevant order types or project profiles in Customizing with the newly created user status profile so that in future newly created orders or WBS elements use this automatically.

              In the (new or existing) user status profile add a new status without status number, for example, the status NOBU ("no budget"). For this status, set the 'Initial status' indicator so that it is automatically set with the creation of orders or WBS elements.
In this status, relevant debits of all types should be forbidden. Double-click the status NOBU to navigate to the transaction control of the new status and choose 'New Entries'. A list of the business transactions with an indicator for the business transaction control is displayed.

a) Override:

                       Set all relevant debit business transactions to 'Forbidden': Purchase requisitions, purchase orders, G/L account postings, and so on .

                       In other words: For an order in the status NOBU all relevant debit business transactions are forbidden. As NOBU is in the initial status, these debit business transactions are automatically forbidden for all newly created orders or WBS elements that do not have any budget yet, in particular.

b) Follow-up action:

                       The status NOBU is to be automatically deleted ('Delete' indicator)
==> with availability control against budget through business transactions 'Budgeting' and 'Budget supplement',
==> with availability control against releases through business transaction 'Budget Release'.

                       In other words: As soon as a budget that is relevant for the availability control is assigned, the debit business transactions that are forbidden through the status NOBU are potentially possible again.
These debit business transactions are then checked by the availability control.

                       Note 1: If the 'Delete' indicator is not provided and, as a result, you cannot set it as a follow-up action, then use transaction BS32 to set the 'UsrSt' indicator for transaction KBUD (Budgeting) or KBFR (Budget Release).

                       Note 2: With availability control against releases, make sure that the corrections for Note 367984 have been implemented in your system.