SAP note 409520 - Goodsinvoice receipt Default account assignment does not work
目录
409520 - Goods/invoice receipt: Default account assignment does not work
Version 13 from 25.06.2019 in EnglishShow Changes
DescriptionSoftware Components
References
AttributesLanguages
Symptom
1. You want to post an invoice receipt for a purchase order.
The invoice contains price differences or unplanned delivery costs that are to be posted to an account for minor differences or for delivery costs. This account is defined as a cost element for which a detailed default account assignment is defined in transaction OKB9 (details by business area or valuation area or profit center). Despite this, the system displays error message KI 235 ("Account & requires an assignment to a CO object").
2. Or: For the price difference account, you specified a default account assignment that the system does not take into consideration when you post an invoice receipt or a goods receipt. The system generates a CO posting that does not contain the account assignment you expect.
Other Terms
MIRO, MIGO, OKB9, KI 235, invoice receipt, valuated goods receipt, default account assignment, MR01, MRHR, MR1M, MB01, logistics invoice verification, CO account assignment check, CO interface, DIF, KDT, BWKEY
Reason and Prerequisites
1. The invoice is to be posted for a purchase order with valuated goods receipt and the purchase order items do not contain any account assignment.
The system displays the error message for an automatically generated line item (for example, minor differences -> ACCIT-KTOSL = 'DIF' or unplanned delivery costs -> ACCIT-KTOSL = 'UPF').
Since no account assignment has been explicitly specified, the business area and the valuation area cannot be uniquely assigned for the automatically generated line. Thus, the fields for the business area and valuation area remain empty. It is therefore not possible to determine a default account assignment based on these fields.
2. Or: For the automatically generated lines (such as price differences), the system always uses the account assignment from the purchase order.
Solution
1. In transaction OKB9, you also enter a default account assignment, regardless of the business area or valuation area.
For more information, see also SAP Note 32654.
2. If you require an account assignment that differs from the one in the purchase order, you must use CO substitution. For more information, see SAP Note 105024.
If you want to define your default account assignment on the basis of the business area, you can also implement the following modification as an alternative. This causes the system to call function module FI_SUBST_GSBER to determine a business area for automatically generated line items - in this case, this call occurs earlier than in the standard system.
To implement the modification, proceed as follows
1. Call transaction SM31 for maintaining table TRWPR.
2. Select the entry with the key
BusTran. = DOCUMENT
Time = CHECK
Sequence number = 60
3. Copy the entry.
4. Change the value of the sequence number in the copy from 60 to 49. The new entry then reads as follows:
DOCUMENT CHECK 49 FI FI_SUBST_GSBER
5. Then delete the old entry
DOCUMENT CHECK 60 FI FI_SUBST_GSBER
6. The list should now contain the following entries
DOCUMENT CHECK 45 FI FI_DOCUMENT_CHECK
DOCUMENT CHECK 49 FI FI_SUBST_GSBER
DOCUMENT CHECK 50 RK-1 CO_DOCUMENT_CHECK
DOCUMENT CHECK 70 COPA COPA_DOCUMENT_CHECK_START
CAUTION: Depending on the Support Package level in your system, other entries may also exist that differ from those shown above. You must not delete these. If you delete them, this can lead to serious data inconsistencies.
Important
In S/4 Hana (S4CORE 100 to 103), sequence number 49 is already populated with FCO_TRANS_REPOST_SUBSTITUTE. Here, prior to the above steps, FAA_RWIN_ACDOC_CHECK must be changed from 47 to 46, FMRE_DOCUMENT_CHECK from 48 to 47 and FCO_TRANS_REPOST_SUBSTITUTE from 49 to 48. Then, FI_SUBST_GSBER can be set to number 49.
Important: As a result of the modification, the account assignment check is only called after you set the business area, and the account assignment check generally derives the business area from the account assignment object. Consequently, the system may make changes to the business area again, or other undesired effects may occur (see SAP Note 196485).
Software Components
References
This document refers to
This document is referenced by
Attributes
Languages
日本語
Deutsch (Origin)
Português (Machine Translation)
Español (Machine Translation)
中文 (Machine Translation)
Français (Machine Translation)
Italiano (Machine Translation)
| Software Component | From | To | And Subsequent |
This document is not restricted to any software component | This document is not restricted to any software component | This document is not restricted to any software component | This document is not restricted to any software component | This document is not restricted to any software component | This document is not restricted to any software component
| Number | Title |
| 397239 | INFO:CO-OM Interface/actual postings/commitment/down payment |
| 32654 | Automatic account assignment at high level |
| 105024 | Automatic account assignment (OKB9) does not work |
| Number | Title |
| 105024 | Automatic account assignment (OKB9) does not work |
| 32654 | Automatic account assignment at high level |
| 753635 | MIRO: Error KI248 during subcontracting for sales order |
| 397239 | INFO:CO-OM Interface/actual postings/commitment/down payment |
| Name | Value |
| Other Components | MM-IV Invoice Verification |
