Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: GA - Allocations
Message number: 776
Message text: Acumul.no posible, dado que no existe red de imputac.estable para el ejer
When you executed the
<DS:GLOS.3526B655AFAB52B9E10000009B38F974>cumulative</> &V3& for cycle
&V1&, start date &V2& the system determined that the allocation network
has shrunk compared to the periods already updated.
Object &V4& occurred in the updated periods, but is not contained in the
allocation network for the current cycle. In this case, the cumulation
results will be incorrect as demonstrated in the following example.
For receiver objects this can occur due to the following changes to the
cycle:
The interval or the group of receivers has been changed.
The receiving trace factor has been changed.
Receiver rule 'fixed percentages' or 'fixed amounts': a percentage rate
or an amount has been set to zero.
Receiver rule 'variable portions', type of variable portions 'actual
costs': cost element groups of the receiving tracing factor have been
changed in such a way that no record is found on the database for the
receiver.
Receiver rule 'variable portions', type of variable portions 'actual
statistical key figures': the statistical key figures or statistical key
figure groups have been changed in such a way that no record is found on
the database for the receiver.
The list is not complete, but should for instance show that only the
combination of receiver object and receiver tracing factor results in a
valid receiver for the cycle.
Always applicable for receiver rule 'variable portions': a totals record
with value zero for the execution period results in a valid receiver in
a cumulated cycle. If no record is found at all, then no receiver is
created.
If a receiver is missing for this purpose, the results of the cumulation
are incorrect, as the following example shows.
Cycle Z1 consists of one sender S and 3 receivers E1, E2, E3. In period
1 the sender and the 3 receivers each have the same tracing factor. $1,2
00 is posted on the sender and allocated to the receivers. Each of the
receivers is debited with $400.00.
In period 2 receiver E2 is removed from the cycle.
Receivers E1 and E3 both have the same tracing factor once again. An
additional $800.00 is posted on the sender in this period. The cumulated
sender amount for periods 1 to 2 therefore amounts to $1200,00 + $800,00
= $2000,00. Both receivers are now debited with a cumulative total of
$1000,00.
In period 2 the differences to the debit amounts from period 1 are
updated. Receivers E1 and E3 are each debited in period 2 with $1000,00
- $400.00 = $600.00. Compared to the original sender amount of $800.00,
there is an excess debit of $400.00 in this period on the receiver side
or a corresponding excess credit of $400.00 on the sender side. This
amount corresponds exactly to the allocation amount in period 1 for
receiver E2.
Period,,,,S,,E1,,E2,,E3
------------------------------------------------------------------------
1,,,,1200,,400,,400,,400
------------------------------------------------------------------------
2,,,,800
Cumulation,,,,2000
Allocation,,,,1200,,600,,--,,600
------------------------------------------------------------------------
Total,,,,,,1000,,400,,1000
Although the cumulative amount for periods 1 and 2 is $2,000, the sender
is credited with $2,400 and the receiver is debited with $2,400.
To avoid inconsistencies, the results are not updated. In the list of
results or in the line item report you can analyze the results
calculated from the cumulated &V3&.
You can only execute the cumulated &V3& with allocation networks that do
not shrink within a fiscal year. Therefore, you should change your cycle
so that object &V4& is included once again in the allocation network.
In the example above, you can select the tracing factor for receiver E2
in period 2, so that a cumulated tracing factor of 0 is produced. This
receiver is then debited with -$400.00 and the excess/under applied
credit is avoided.
Period,,,,S,,E1,,E2,,E3
------------------------------------------------------------------------
1,,,,1200,,400,,400,,400
------------------------------------------------------------------------
2,,,,800
Cumulation,,,,2000
Allocation,,,,1200,,600,,-400,,600
------------------------------------------------------------------------
Total,,,,,,1000,,0,,1000
Extracto de mensaje de error del sistema SAP. Copyright SAP SE.
GA776
- Acumul.no posible, dado que no existe red de imputac.estable para el ejer ?Get instant SAP help. Sign up for our Free Essentials Plan.
GA775
Desbordamiento campo en la imputac.valores emisores (BCD_FIELD_OVERFLOW)
¿Qué causa este problema? Processing segment &V1& caused a field overflow during the calculation of the sender values to be allocated to th...
GA774
No hay datos maestros válidos para el receptor & contabilizado dos veces
Mensaje autoexplicativo Dado que SAP cree que este mensaje de error específico 'se explica por sí mismo', no se ha proporcionado más información. ...
GA777
Suma de las bases de ref.receptoras igual a cero; normalización realizad.
¿Qué causa este problema? In segment &V1& you have defined receiver tracing factors that result in the total zero. Therefore, a division by...
GA778
Segmento &1 bloqueado
¿Qué causa este problema? You have selected segment &V1& for processing through a reverse and rebook. The segment, however, is locked.Respu...
Haga clic en este enlace para buscar todos los mensajes de SAP.