Message type: E = Error
Message class: GA - Allocations
Message number: 627
Message text: Customizing error: Business transaction groups are not current.
For the execution of assessments, distributions, periodic repostings or
indirect activity allocations in the CO-OM application, groups have to
be defined in the current client which summarize all actual or planned
transactions. In the current client, these groups are either not
available or do not have the latest status.
To avoid subsequent errors, processing cannot be continued until these
transaction groups are consistent again.
Such errors are mostly caused by problems during a release upgrade or
by incomplete client copies; they can be solved by starting report
RK811XST (only in the current client) or
RK811XUP (in all clients).
Start one of these two reports and then restart processing. If the
error still occurs, inform your system administrator.
&Note&
You can execute the correction reports either via the development
workbench or immediately by choosing one of the two following
pushbuttons:
<DS:REPO.RK811XST>Execute report RK811XST (current client)</>
<DS:REPO.RK811XUP>Execute report RK811XUP (all clients)</>
Note that the transaction groups are client-specific. Therefore, this
Customizing inconsistency may also occur in other clients of your
system. Report RK811XST only repairs the transaction groups in the
current client while report RK811XUP corrects all clients.
Error message extract from SAP system. Copyright SAP SE.
GA627
- Customizing error: Business transaction groups are not current. ?The SAP error message GA627, which states "Customizing error: Business transaction groups are not current," typically occurs in the context of financial accounting or controlling modules when there is a mismatch or inconsistency in the configuration of business transaction groups. This error can prevent users from executing certain transactions or processes.
Cause: Outdated Customizing Settings: The business transaction groups may not be updated in accordance with the latest configuration or changes made in the system. Missing Entries: There may be missing entries in the customizing tables related to business transaction groups. Transport Issues: If changes were transported from a development environment to a production environment, there may have been issues during the transport that led to incomplete or inconsistent data. Version Mismatch: The version of the customizing settings may not match the version of the application or module being used.
Solution: Check Customizing Settings: Go to the customizing settings in the SAP system (transaction code SPRO) and
Get instant SAP help. Sign up for our Free Essentials Plan.
GA626
Syntax error during generation of run report.
What causes this issue? A syntax error occurred in line &V2& of INCLUDE &V1& during the generation of the cycle run report. Error mes...
GA625
System error: Generated program rows too long.
What causes this issue? A system error or Customizing error occurred during the generation of the cycle run report: Program line &V1& has &am...
GA628
Cycles have different settings for indicator "Transfer prices active".
What causes this issue? Transfer prices are active in your controlling area. You start several cycles in a collective execution, but these cycles hav...
GA629
Field overflow in iteration
What causes this issue? Within iteration for &V3&, a field overflow occurred for the allocation relationship between &V1& and &V2...
Click on this link to search all SAP messages.