Hi
OSS Note 36353:
Summary
Symptom
When you post documents using the AC interface (from SD, MM or other applications), items appear in the FI document which are identical in all or in almost all fields.
This can also cause error message F5 727 ("Maximum number of items in FI reached"). The system issues this error if more than 999 items occur in an FI document.
Other terms
SAPLFACI, VF01, VF02, VF04, MB01, MB11, MR1M, CO15, BSEG, totaling,
document summarization, CKMI_RUN, F5 272, F1 807
Reason and Prerequisites
The system will only total items in the FI document if you made the proper settings for this action in Customizing (= sending application, for example: VBRK for SD, MKPF for MM Position Management, RMRP for MM Logistics Invoice Verification).
There is no summarization, for documents which are entered in FI (object type BKPF) application (for example EDI invoice receipt, FB01, MR0) or in invoice verification (MR01) (with object type BKPF).
The system can only total items in the FI document if they have the same account assignments and only differ in the value fields.
It is therefore not possible to carry out the totaling across different G/L accounts.
The summarization can be achieved by deleting certain fields in all items (can be configured in Customizing).
As a consequence, these fields will not contain data in the FI document. They are therefore no longer available for selection, clearing or reconciliation with other applications.
This field deletion only affects the FI document, not documents from other AC applications.
The field contents deleted in the FI document are still available for the other AC applications and can be updated there. The AC applications are not updated on the basis of the FI document. In addition, there are other summarization procedures in other applications, for example in CO (Note 147766).
Solution
Procedure for configuring summarization:
Carry out the following actions for each object type (sending application, AWTYP field), for which you want to summarize FI documents.
You can find the AWTYP object type on the detail screen 'Document header' under the 'Name' field when you display the document using transaction FB03.
1. If you think an FI document has too many items, find out in which fields the items differentiate.
To do so, display the FI document (FB03) or table BSEG and ONE FI document (SE16).
2. If there are items which are the same in all same account assignments:
Make the following entry in the TTYPV table (transaction OBCY):
Table Field name
As a consequence, items which are the same in all fields except value fields are totaled, that is, they are combined into a single item.
(The '* ' entry can only be made in Release 3.0D or higher.) If you use a release lower than 3.0D, enter any field which, when deleted, will not disrupt transactions from the affected application. As of Release 4.0, the ' ' entry can no longer use transaction SM31 (view maintenance) to make the entry in the TTYPV table. Check whether you can replace the entry ' ' with a field name. The corrections from this note enable you to use the report ZTTYPV to enter ' *' for the relevant object type.)
3. If there are ITEMS which differ in specific fields:
Enter the fields in the TTYPV table.
The contents of the fields entered in the TTYPV table are deleted.
This has a higher summarization effect than entry '* *'!
Typical fields for each application are:
Application AWTYP Table Field name
SD VBRK BSEG MATNR
Billing MEINS
MENGE
PAOBJNR
POSN2
VBEL2
WERKS
MM MKPF BSEG BPMNG
Position Management BPRME
ERFME
ERFMG
MATNR
MEINS
MENGE
PAOBJNR
POSN2
WERKS
BWTAR
MM RMRP BSEG BPMNG
Logistics BPRME
Invoice Verification ERFME
ERFMG
MATNR
MEINS
MENGE
PAOBJNR
WERKS
As of 4.0A
HR HRPAY see Note 116523
Payroll accounting
The list of the allowed fields in Release 3.1I includes the following entries in the TTYPS table:
BSEG BPMNG
BSEG BPRME
BSEG BWTAR
BSEG ERFME
BSEG ERFMG
BSEG MATNR
BSEG MEINS
BSEG MENGE
BSEG PAOBJNR
BSEG POSN2
BSEG PPRCT
BSEG VBEL2
BSEG WERKS
BSEG PRCTR (for restrictions see below)
BSEG FKBER (Note 413418)
General remarks:
Items with identical account assignments but different debit/credit codes (BSEG-SHKZG) will NOT be put together as a single item (for example, revenues and sales deductions in billing documents).
In releases lower than 3.0F, the system did not allow all of these fields as entries for the TTYPV table. To expand the number of fields allowed for the TTYPV table, enter the fields in the TTYPS table. (Call transaction SM31 (view maintenance) to add an entry to the V_TTYPS view.) (You can only add the BSEG BWTAR field using transaction SE16 (table maintenance) for the TTYPS table). The standard system only contains the BSEG-PRCTR field is only contained in the TTYPS table as of Release 4.6B.
This is an SAP table modification. Only enter the fields listed above. Do not enter any other fields without first contacting SAP, since these fields will then be deleted in every FI document from the application in question.
Notes:
When you carry out summarization using the material number (MATNR) during position management or invoice verification transactions, the 'material number' information is lost in the BSEG document table of Financial Accounting. Therefore no entries are written to the BSIM table. This can have the following consequences:
Transactions such as MR51 (accounting documents for material) or MB5B (balance at posting date) produce incorrect results.
The evaluation of balances at material number level (characteristic 0MATERIAL) in the SAP Business Information Warehouse displays faulty or incomplete results.
You can no longer use the Value Flow Monitor (transaction CKMVFM) to compare differences at material level between price difference accounts and the relevant FI postings.
If you delete the material number (MATNR), the amount (MENGE), the unit of measure (MEINS) or the plant (WERKS) in position management, this information is no longer available in financial accounting. The RMVKON00 report (transactions MRKO and MRPI) however, which indicates and settles the consignation stock, is based on the documents of financial accounting. This has two consequences:
If the FI documents are not summarized, each individual withdrawal is indicated in the report and can also be individually settled. If the FI documents are summarized, several withdrawals can be displayed in one single report line and can no longer be separately settled. Furthermore, certain data, such as material number, amount and unit of measure, may no longer be displayed.
If in the FI documents the material number or the plant is deleted and you settle the withdrawal, the tax codes that you defined using the tax indicator (in the material master) or in a purchasing info record can no longer be found. Instead, only the tax code that you defined as default value in the Customizing settings for the invoice verification (transaction OMR2) is determined. If no valid tax code has been defined there, the settlement terminates with message FF 704.
Read Note 38982 to learn how to determine the tax code.
In Release 4. 0A, these restrictions no longer apply to the RMVKON00 report.
Clearing of the GR/IR clearing account for each purchase order item: The account assignments to the purchase order (EBELN) and to the purchase order item (EBELP) are NOT deleted by default. In both the goods receipt with reference to the purchase order (MB01) and the invoice verification, they are assigned to an account in the FI document and thus PREVENT the summarization of the FI document.
This makes it possible to clear the GR/IR clearing account at purchase order item level.
Using Profit center for summarization
If you summarize using the Profit center field in FI, only FI and PCA balances can be reconciled at account level.
A summarization using the Profit center field is only worthwhile if other CO account assignments are also summarized. These account assignments are therefore also not available for a derivation of the Profit center field when the FI document are subsequently posted to Profit Center Accounting using transaction 1KE8. Since summarized documents are always postings the original of which is not posted in FI, you should subsequently post such documents from the sending application component anyway. However, you can directly transfer unoriginal FI documents using Note 102634 or, as of Release 4.5B, using the standard system. In this case, you must make sure that this function is not used for the summarized documents.
For the reason stated above, a summarization using the Profit center field is only worthwhile for transaction HRPAY. Note that HR only supports a subsequent posting from the sending application component as of Release 4.5A. In the releases 4.0A up to and including 4.0B, no programs are available in the standard system to generate subsequently the profit center document. You should implement Note 118533 in these releases beforehand to make sure that the online document flow from HR to PCA works.
A summarization using the Profit center field should definitely not be carried out in Releases 4.0A and 4.0B if the online update to Profit Center Accounting has not been activated in the fiscal year or if it should be activated subsequently (mid-year).
Header Data
Release Status: Released for Customer
Released on: 11.10.2007 08:21:39
Priority: Correction with medium priority
Category: Customizing
Primary Component: FI Financial Accounting
Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_APPL 30 300 31H
SAP_APPL 40 40A 40A
SAP_APPL 45 45A 45A
SAP_APPL 46 46A 46A
SAP_APPL 470 470 470
SAP_APPL 500 500 500
SAP_APPL 600 600 600
Highest Implemented Support Package
Support
Packages Release Package
Name
SAP_APPL 40B SAPKH40B28
SAP_APPL 45B SAPKH45B09
SAP_APPL 46B SAPKH46B01
SAP_HR 40B SAPKE40B28
Related Notes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.