SAP Note 25559 - Allocation: Frequent Customizing errors

Symptom:

This note describes errors that are frequently made when customizing allocations in FI-SL, resulting in allocations not working or working incorrectly.
Note: Where the "Company code" field (BUKRS or RBUKRS) is referred to in this note, the same also applies to the "Company" field (RCOMP) unless specified that this is not the case.

• Check the field usage for distribution (transaction GCA6) or assessment (transaction GCA1) to see whether the following settings were made in the 'Field usage in allocation' for field BUKRS or RBUKRS:
  Control Single value Interval
  Cycle + X
  
  Explanation: The company code must be a single value at cycle level and CANNOT be activated as a receiver or receiver tracing factor!
  
  A cross-company code distribution or assessment, during which for example you allocate from one company code to another company code, is not possible at the moment. In this case, during the cyclic check, the message GA 404 occurs: The field usage for required field RBUKRS is not correctly maintained. Correct the field usage accordingly.
  

• Use transaction SM30 to check the field usage for table T811I and see whether the NVFlag (technical name T811I-NVFLG) is set to 'X' for field RVERS.

• Check whether an entry exists in the integrated master data (table T800D) for each field that is referred to in the cycle definition. The allocation only works correctly when master data is deposited for each dimension that is processed in the allocation. Dimensions, which are used to summarize with, are not affected.
  Furthermore, check the entries for the integrated master data in table T800D to see if the higher-level fields are entered. Typical errors are missing higher-level fields for the following dimensions:
  RACCT, PRCTR or RPRCTR, RCNTR, RVERS
  You may use the entries for tables GLT1 and GLPCT as a reference.
  

• Check the integrated master data (transaction GCS1) to see whether '1' is entered in the field "Additional information" (exit for period-independent values) during the master data validation for field 'BUKRS' or 'RBUKRS'. Only then can the local currency be determined from the company code.
  Caution: Except for the fields RLDNR and RPMAX, the field 'Additional information' should not be filled. It must also not be filled for the field 'RCOMP'.

• Check the field usage for distribution (transaction GCA6) or assessment (transaction GCA1) to see whether the dependencies are maintained correctly. You do this by selecting a user-defined field and entering '=ABHA' in the OK code.
  
  For releases PRIOR TO Release 4.5A, the settings must be as follows:
  
  Field Higher-level Depending on
  GCURR 1
  LCURR 2
  RBUKRS (BUKRS) 2
  RLDNR 1
  
  For releases AS OF Release 4.5A, the settings must be as follows:
  
  Field Higher-level Depending on
  GCURR 1
  LCURR 1
  RBUKRS (BUKRS)
  RLDNR 1
  

• If your user-defined FI-SL table contains field SACCT (sending account) and if you use assessment, make sure that 'A' (account field) is not entered in the field "Field type" for the field usage (transaction GCA1) in the general settings. 'A' can only be entered in the field 'RACCT' (account).
  

• Check the "Field usage for assessment" (GCA1) and the "Field usage for distribution" (GCA6) for table GLPCT (Release 3.x):
  If there are entries for the field RHOART, delete them.
  Furthermore, use transaction SM31 to delete the entries for the field RHOART (for table GLPCT) from table T811X.
  If these entries are in the system, there is a risk that no recipients are found when executing the allocation.

• Check the field usage for assessment (transaction GCA1) and distribution (transaction GCA6) whether the field "Field type" is empty for the Fields "RUNIT" and "AUNIT". A "Q" must not be entered there.
  

• Check the data control (transaction GCA2) and field group definition (transaction GCA3) for your table.
  
  The following must be true for all FI-SL tables (except GLPCT and GLTPC) up to and including Release 3.0C:
  In the data control for the field groups TSL, HSL, KSL and MSL, the field "Plan/act.Altern." must be empty.
  In the field group definition, the fields "Additional field" and "Value additional field" must be empty.
  
  For tables GLPCT and GLTPC in all releases and all FI-SL tables in Releases after 3.0D, the following must be true:
  In the data control, 2 entries must exist for each field group in your table (for example, HSL-0 and HSL-1).
  For example, the field "Actual/plan replacement" for field group HSL-0 must contain HSL-1, and vice versa.
  In the field group definition, you must have "RRCTY" in the additional field and "0" in the Value additional field for the database field HSL-0. For Database field HSL-1, Value additional field must be "1".
  
  We recommend that you compare the data control and the field group definition for each FI-SL table with that for table GLT1 or GLT2. The entries for these two tables are delivered with the standard system and are usually correct.
  

• Check, up to and including Release 3.0F, whether the field 'do not summarize' is filled for some dimensions in the field usage.
  You should use transaction SE16 to check whether the field T811I-NVFLG in table T811I is also filled for dimensions other than 'RRCTY' and 'RVERS'.
  If this is the case, remove the indicator for the relevant dimension from table T811I as it does not work correctly up to and including Release 3.0F (see Note 53512).
  To do this, enter the allocation field usage in FI-SL Customizing, and go to the detail screen for the relevant dimension.
  Enter '=MAST' in the OK code, and remove both the 'not summarized' indicators.

Other terms

GA109, GA709, GA710, GA714, GA715, GA733

Solution
Check the points listed above.
As of Release 3.0E, you can, in most cases, check and automatically correct the Allocation Customizing using transaction GCA9.
It is essential to check the points mentioned in this note in addition
to GCA9.