KI235 – Requires a CO Account Assignment Logic
[Account Assignment] [G/L Account] [KI 235] [KI235] [Settlemen] [Settlement]
Symptom
When executing a transaction, the system generates error message KI235 “Account & requires an assignment to a CO object”.
Other terms
Settlement, G/L Account, KI235, KI 235, Account Assignment, Settlement Rule, Cost Center, Projects, Order
Reason and Prerequisites
Further explaination of the system logic and options avaialable to satisfy this error message is required.
Solution
Account assignment objects in Controlling are orders, cost centers, projects, cost objects, networks, special make-to-order sales orders, and profitability segments. As of Release 4.5A, activity types (together with cost centers) can be assigned to an account, as of Release 4.6A business processes can be used as account assignment objects. From a point of view CO, profit centers are objects which can be posted to in in addition to one of the above-mentioned account assignment objects. They may also be derived from these objects.
In general, the system logic for KI235 is that it performs several checks for the CO Account Assignment which can be maintained in several locations, but the system checks are performed in a particular order. Therefore, if the system does not find the Account Assignment in the first check it will proceed to the next step and so on until it finds an Account Assignment and if it does not the system will issue KI235.
The following is the order of Checks used by the system sequentially:
CHECK 1:
The system will check if the Account Assignment is provided by the calling application or entered manually by the user. If the Account Assignment is found then the system will use the provided Account Assignment.
CHECK 2:
OKC9 – Substitutions – System will check if a substitution is setup to provide the account assignment. (Further information in relation to OKC9 see Note: 105024). If there is no subsitution in place to provide the Account Assignment then the next check will be performed
CHECK 3:
OKB9 – System will check for Default Account Assignments in transation OKB9. If they are not maintained then the next check is performed. (Further information in relation to OKB9 see Note: 105024)
CHECK 4:
If still no Account Assignment exists, the master data of the cost element will be assigned (can be an Order or Cost Center). If the master data has not been maintained with the necessary Account Assignment then the Error Message KI235 will occur unless the following modification is implemented in your system.
CHECK 5:
MODIFICATION from Note: 483340. Normally this would be the point where KI235 would appear due to not finding a CO Account Assignement but if this modification from Note: 483340 is present in the system then the system will check the ‘Details’ section of the Senders Settlement rule and use this information to provide the account assignment.
To find this account assignment area open the settlement rule being used in the settlement (E.g. Transaction CJ20 for particular WBS element > Details > Settlement Rule. In Settlement rule Maintenance screen then goto menu option “Goto > Details”. In this screen you will see fields for the account assignment which will now be used once the modification from Note: 483340 are in place)
If at this point the system does not find an Account Assignment then if will issue the Error message KI235. If this error occurs then simply check your Account Assignment settings in accordance with system checks as outlined to ensure the system configuration is correct.