SUMARIZAÇÃO DE LANÇAMENTOS CONTABEIS
NOTAS COM MAIS DE 999 ITENS
Uma solução complexa é aplicar a nota 36353.
Para notas com mais de 999 itens, uma solução é sumarizar o lançamento das linhas de impostos do documento contábil.
Outra solução é solicitar o bondoso fornecedor a emitir duas notas, e transformar isso como regra para o processo para as notas que ultrapassarem 150 itens, para cada item um lançamento de cinco linhas de impostos teremos 750 itens.
Agora, não tem como aplicar a nota, nem mesmo solicitar novo faturamento ao fornecedor
Devemos dividir a miro, em duas. Uma sem categoria e a outra com a categoria.
Em seguida, lançar a nota fiscal complementar dos itens do documento sem categoria de nota. Associando este a Nota lançada.
Aff, uma questão é certa, notas com muitos itens prejudica até mesmo o processo de recebimento e conferência.
Antecipe-se a isto!
SAP Note 36353 - AC interface: Summarizing FI documents
SAP Note 36353 -AC interface: Summarizing FI documents
Note Language: English Version: 56 Validity: Valid Since 11.10.2007
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.
More Terms
SAPLFACI, VF01, VF02, VF04, MB01, MB11, MR1M, CO15, BSEG, totaling,
document summarization, CKMI_RUN, F5 272, F1 807
Cause 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.
19.07.2009
Page 1 of
SAP Note 36353 -AC interface: Summarizing FI documents
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
19.07.2009
Page 2 of
SAP Note 36353 -AC interface: Summarizing FI documents
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:
o
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.
o
If you delete the material number (MATNR), the amount (MENGE), the
19.07.2009
Page 3 of
SAP Note 36353 -AC interface: Summarizing FI documents
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.
o
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
19.07.2009
Page 4 of
SAP Note 36353 -AC interface: Summarizing FI documents
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.12.2008 19:34:52
Original Lang.: German
Priority: Correction with medium priority
Category: Customizing
Main Component: FI Financial Accounting
Valid Releases
Software Component Release From
Release
To
Release
and
Subsequent
SAP_APPL 30 300 31I
SAP_APPL 40 40A 40B
SAP_APPL 45 45A 45B
SAP_APPL 46 46A 46B
SAP_APPL 46C 46C 46C
SAP_APPL 470 470 470
SAP_APPL 500 500 500
SAP_APPL 600 600 600
SAP_APPL 602 602 602
SAP_APPL 603 603 603
SAP_APPL 604 604 604
SAP_APPL 605 605 605
Support Packages
Support Packages Release Package Name
SAP_APPL 40B SAPKH40B28
SAP_APPL 45B SAPKH45B09
SAP_APPL 46B SAPKH46B01
SAP_HR 40B SAPKE40B28
Related Notes
19.07.2009 Page 5 of
SAP Note 36353 -AC interface: Summarizing FI documents
Number Short Text
1318938 BAPI: tax data in ACCTX for Accounting Interface
1268872 RGFLC1F: Incorrect balance for FI item summarization
819188 JIT: Accounting doc. cannot be created for ESP delivery.
728740 IS-M/SD: FI/CO interface - FI document summarization
687873 MRKO: Short dump during IDOC settlement
645356 No summarization of FI documents from MM due to BSEG-XREF3
571928 Summarization of tax items with external tax system
545137 FAQ Interface - summarization
517768 (FI) FI057 due to BUZEI in connectn w/ doc. split in FI (1)
497992 XXX MB5B : Composite SAP Note for Release >= 4.0B 05/2002
485236 (SD) FI057 with 'Buzei in LFMPRF04'
426100 (CC) split processor and reference to clearing document line
413418 AC-INT: Summarization of FI documents using functional area
408681 Follow-up posting: Long text FI057 no info on source documnt
406420 IS-M/SD: FI documents not summarized when transferring
402381 IS-M/SD: FI interface - FI document summarization
310837 Simulation for document summarization in FI
301077 User exits for the interface to accounting
213546 HPR collective note: POS inbound
207340 Termination of program SAPLFACI
205438 Note 36353 and JVA
201039 Missing accounting documents in MB5B and MR51
199467 Info: New act assignment table as of Release 4.5
178487 High increase of table BSIS, RFBLG
166880 Incorrect tax company code in FI document
166487 TABLE_INVALID_INDEX in FI/CO interface
147766 Document summarization in CO available as of Release 4.0A
144638 M/AM - AC interface: FI document summarization
141899 Transfer price: lines with zero posting in FI document
123223 Obsolete: GI: 'Maximum number of items in FI reached'
117708 A maximum of 999 items can be posted in the FI doc
116523 Q&A: How to customize Payroll Accounting postings in Rel.4.x
108583 RWIN: Document summarization for doc.s with MR1M
94868 SD/FI: Document summarization for valuated materials
85982 Summarizing the tax line items from SD
79265 GI: Collective note for FI problems with GI
77161 Summarization of FI postings w.ref.to purchase orders
73907 Specl development: Summarization dependent on doc type in FI
67640 Summarizing FI documents from MM does not work
42347 GI182: System error in SAPLGIN3 during update
28292 MR01: Zero lines on GR/IR clearing account
9150 Cancellation of an invoice list
Correction Instructions
19.07.2009 Page 6 of
SAP Note 36353 -AC interface: Summarizing FI documents
Correcti
on
Instruct
ions
Valid
from
Valid
to
Software
Component
Typ
e
*)
Reference
Correction
Last
Changed
1258 300 605 SAP_APPL C 11.12.2008
14:33:34
*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work
19.07.2009 Page 7 of
Nenhum comentário:
Postar um comentário