|
Нота длинная.
Обратите внимание на фразу в ноте:
Never start these reports yourself. The use of these tools is reserved for experienced SAP Support employees only, because incorrect usage may cause additional inconsistencies.
Ниже текст ноты (может быть, что-то неудачно скопировалось - из PDF очень неудобно копировать).
Надеюсь, САП не обидится за то, что нота for internal use only is published on the sapboard.
Description
Symptom New general ledger accounting (new G/L) is active in your system. You discover the following inconsistencies in the tables of new G/L: Documents with incorrect posting keys in new G/L or/and incorrect debit/credit indicators in new G/L or/and line items with changing +/- signs.
Other terms
FIINCON, all-in-one device suitable for every purpose
Reason and Prerequisites
This problem is due to inconsistencies. The update in new G/L with changing +/- signs in a line item, incorrect posting keys, or incorrect debit/credit indicators in new G/L is due to program errors. To correct this for new documents to be posted, implement the notes mentioned below, and then execute the report SAPFGIDB for new documents to be posted.
Incorrect debit/credit indicators in new G/L.
Note 992566 - (debit line, even though there is only a credit amount in WSL - all other amounts in new G/L are zero). The inconsistencies for documents already posted are supported by SAP Support and can be corrected using the analysis report ZF_ANALYZE_PK_DC_NEWGL or ZF_ANALYZE_PK_DC_NEW_PSM. Before documents already posted are corrected, you have to start the report SAPFGIDB in an update-free time of the production system (no postings are performed in any client); (it takes less than two minutes to execute the report). This ensures that the corrections of Note 992566 are generated in the source code of the include LGLINF90. Before documents affected are corrected, you have to check the last generation time of the include LGLINF90, or execute the report SAPFGIDB.
Note 1047458 - reversal documents that were generated using the accounting interface as a negative posting (AC_DOCUMENT_REVERSE) of documents from SD, and for which the document to be reversed was already generated as a negative posting (BSEG-XNEGP is set) in ALL line items, are updated with incorrect debit/credit indicators in the new general ledger. (For BAPI or the cash journal, both of which may also use AC_DOCUMENT_REVERSE, the problem cannot occur because the negative posting logic is not supported for original documents.)
Note 992566 - in the new General Ledger Accounting, the system incorrectly updates some reversal documents that were generated using the accounting interface as a negative posting (AC_DOCUMENT_REVERSE) and for which you want a negative posting (=BSEG-XNEGP is set) despite having implemented Note 1047458.
Note 1024404 - reversal documents that were posted locally in FI using SAPMF05A (for example, transaction FB08), with the "Negative Posting" indicator (BSEG-XNEGP) set for all available BSEG lines, were not generated with the negative posting logic in the zero balance clearing lines of new G/L before you implemented this note. From a commercial point of view, the documents posted before this note was implemented are generated correctly. However, in the case of a reversal with negative posting for all BSEG lines, you expect that the balance update of the zero balance clearing account is also reversed by a negative posting, and that it is not canceled by an offsetting entry on the debit/credit item that is opposite to the original posting to be reversed.
Modification (for example, negative posting of documents that were posted using the AC interface with the indicator BSEG-XNEGP set or substituted line by line using a modification, which is incorrect).
You can use the reports mentioned below to determine further inconsistencies regarding incorrect debit/credit indicators. For example, these may occur due to the following modifications: Negative posing documents from the accounting interface (AC_DOCUMENT_REVERSE - used by SD, BAPI, and the cash journal) may be in new G/L with incorrect debit/credit indicators (but with the correct amount type), if the indicator BSEG-XNEGP was set line by line in the document to be reversed. The report can support the analysis only; it cannot clean up the inconsistencies. In the case of fiscal years not closed, the cleanup can be performed by consulting (subject to separate remuneration). In the case of closed fiscal years, you have to consult the external auditor before inconsistencies like these are corrected.
Other causes for incorrect debit/credit indicators are currently not known. Before incorrect debit/credit indicators are corrected, you must always clarify the causes. This is to prevent further inconsistencies, exclude other causes, or - if additional causes are recognized - to document this here.
Incorrect posting keys in new G/L
In the tables of new G/L, there are debit posting keys instead of credit posting keys, and the other way around. In contrast to the debit/credit indicator, it is relatively uncomplicated to correct incorrect posting keys of new G/L, because posting keys are not updated in the totals record. Therefore, the balances are always correct, even if the posting keys are incorrect.
IMPORTANT: Initial posting keys, which may be generated in new G/L when document splitting is used, are not an error. This correct function of initial posting keys in new G/L is described in Notes 889893 and 1145748.
Note 966988 - incorrect posting keys in new G/L for negative posting documents. Documents that were updated using AC_DOCUMENT_REVERSE before this note was implemented (negative posting from SD, BAPI or cash journal) have the posting keys of the document to be reversed instead of the corresponding reversal posting key in the line item table in new G/L. The inconsistencies for documents already posted are supported by SAP Support and can be corrected using the analysis report ZF_ANALYZE_PK_DC_NEWGL or ZF_ANALYZE_PK_DC_NEW_PSM.
Incorrect posting keys - cases that occur in connection with active document splitting only:
Note 1041694 - incorrect posting keys in new G/L in the case of line items to be split individually, for which the transaction currency amount (TSL) to be updated is zero for all line items of this document. The transaction currency amount to be updated may be zero if no transaction currency has been entered (for example, this may be the case for FBB1 postings), or if the "Only balances in local crcy" indicator is active for accounts to which postings have been made in the document currency, and the local currency is zero due to the translation of the document currency amount. The inconsistencies for documents already posted are supported by SAP Support and can be corrected using the analysis report ZF_ANALYZE_PK_DC_NEWGL or ZF_ANALYZE_PK_DC_NEW_PSM. After (!!!) the line item table of new G/L has been corrected, the shadow table of document splitting has to be analyzed using the postprocessing reports ZF_ANALYZE_PK_DC_NEWGL_SPLI or ZF_ANALYZE_PK_DC_NEW_PSM_SPLI, and corrected by SAP Support.
Note 1170400 - incorrect posting keys in new G/L in the case of individual line items to be split by rule-based document split, for which base lines for this line item have different posting keys (debit posting key AND credit posting key), and the line to be split receives the same account assignment in the entry view as it will receive after the split due to the base lines described here. This may occur, for example, if the balancing fields of document splitting are not defined as required entry field, and an initial account assignment is therefore also valid. The line to be split and the base lines have only initial account assignments like these. The incorrect posting keys can also occur if, before document splitting is processed, a balancing required entry field (for example, the business area) is already filled completely and matching in all lines of a document like this, and if there are no other split characteristics. The customized document split of a line item then has identical account assignments before and after the split (as the defined base lines regarding different debit and credit posting keys). The inconsistencies for documents already posted are supported by SAP Support and can be corrected using the analysis report ZF_ANALYZE_PK_DC_NEWGL or ZF_ANALYZE_PK_DC_NEW_PSM. After (!!!) the line item table of new G/L has been corrected, the shadow table of document splitting has to be analyzed using the postprocessing reports ZF_ANALYZE_PK_DC_NEWGL_SPLI or ZF_ANALYZE_PK_DC_NEW_PSM_SPLI, and corrected by SAP Support.
Changing amount types in a line item
If document splitting is active, a line item may be split into positive and negative amounts. In the update, split line items are summarized depending on the account assignments that are update-relevant for the ledger affected. If Note 887505 was not implemented, or if the includes LGLINF90 and LGLINF51 were not generated after the source code of this note was implemented, line items that contain different amount types (positive and negative values) in new G/L may be generated after the summarization. Note 887505, including the subsequent source code generation using SAPFGIDB, must be implemented to ensure that new line items to be posted do not contain changing amount types like these in an individual line item line of new G/L. Important: The date when you implemented the note (using SNOTE or by importing a Support Package) is NOT decisive for the creation of correct postings; instead, the time of the subsequent generation using SAPFGIDB into the source code of the posting is the determining factor.
The same problem can also occur when you use correction reports to subsequently create zero balance clearing lines, if a report version of ZF_CORR_VAL_0_PRCTR_SEG_ECC6 that does not (yet) take into account the logic of the includes LGLINF90 and LGLINF51 regarding the document splitting with the appropriate +/- sign was used for the correction of documents by SAP Support.
The problem that lines like these occur can be analyzed using the tools listed below; however, this problem cannot be solved using these tools. Additional tools are required for this.
Line items in new G/L that contain quantities only
Note 886382 - Before you implemented this note, line items that contain quantities only were updated in new G/L. These line items did not have a corresponding entry in BSEG. Therefore, the number of the posting item (BUZEI) of this quantity-only-line in new G/L is initial. The line items are based on posting items of the non-valuated balance. Quantities like these are not updated in FI, because FI is considered to be value-based, and not quantity-based. This note provides tools to analyze and remove such line items that are not update-relevant.
Additional inconsistencies that cannot be analyzed here
When using document splitting:
Note 1049224 - documents in the the new General Ledger Accounting do not balance to zero - the zero balance clearing lines of the document splitting do not balance to zero. It is possible to analyze the inconsistencies that arose prior to implementing Note 1049224 by looking at the balance of the technical zero-balance clearing account; this does not balance to zero. Here, make sure that it was only posted to in the general ledger view (that means Customizing always as per Note 961937) so that there are no corresponding lines for any single line item of this account in the entry view. This inconsistency can be analyzed using TFC_COMPARE_VZ.
Independent of the use of the document splitting:
Note 878281 - there is no general ledger document for some material postings. This involves individual postings from BKPF-AWTYP = 'MKPF' provided these were generated prior to implementing this note and contained lines of the non-valuated balance (KSTAT = 'U' in the first line) in the posting interface. This inconsistency can be analyzed using TFC_COMPARE_VZ.
Note 1081187 - Indian company code using country-specific development for subsequent posting of specific tax to goods movement (EXCISE - transaction J1IIN). For a negative posting of SD documents (AC_DOCUMENT_REVERSE) that were subsequently linked with an EXCISE document, only the SD document is reversed completely. For the excise document, the system only generates a reversal document in the entry view; the system does not update the excise document reversal in the general ledger (or in FI-SL). This inconsistency can be analyzed using TFC_COMPARE_VZ.
Solution
First, implement the corrections from Notes 886382, 887505, 1041694, 1047458, 992566, 966988, and, if you use document splitting, also Notes 1170400 and 1024404, to avoid further inconsistencies. The following is an overview of the notes that are relevant in each Release or Support Package: The individual notes are delivered with the following support packages:
Note ERP 2004 ERP 2006
878281 SAPKH50010 SAPKH60002
887505 SAPKH50011 SAPKH60002
886382 SAPKH50012 SAPKH60004
966988 SAPKH50015 SAPKH60007
992566 SAPKH50015 SAPKH60008
1041694 SAPKH50017 SAPKH60010
1047458 SAPKH50017 SAPKH60010
1258687 SAPKH50021 SAPKH60015 SAPKH60205 SAPKH60304 SAPKH60402
with document splitting also:
1049224 SAPKH50017 SAPKH60010
1024404 SAPKH50017 SAPKH60009 SAPKH60201
1170400 SAPKH50020 SAPKH60014 SAPKH60204 SAPKH60303
Then execute the generation report SAPFGIDB in the production system, even if you imported a Support Package to implement these notes. You must execute the report SAPFGIDB at a time when no postings are created in the entire system; otherwise, the update may terminate. It takes less than two minutes to execute the generation. After you have implemented the notes, implement the following analysis report and open a message under the component FI-GL-FL (if you use document splitting in new G/L) or under the component FI-GL-GL-X (if you do not use document splitting in new G/L). You must under no circumstances make the changes or correct the error yourself. Never start these reports yourself. The use of these tools is reserved for experienced SAP Support employees only, because incorrect usage may cause additional inconsistencies. In particular, a fixed sequence of procedures is required when operating these reports. This sequence is not apparent in the reports. Important: If table groups of the customer namespace are used in the new General Ledger Accounting, Support has to adjust the reports provided with this note with regard to each of the customer tables used. Note 1155429 currently only delivers an analysis of the FAGLFLEXA and FMGLFLEXA tables. In the event you use table groups of the customer namespace, contact SAP Support directly. To run the report, the parameter rdisp/max_wprun_time may have to be temporarily increased to 1800 using transaction RZ11, if restrictions of individual company codes, fiscal years, and individual periods are not sufficient. However, in general, the analysis can also be performed in the background. FOR EMPLOYEES OF SAP SUPPORT, the supplementary memo explains exactly how to operate these reports.
 |
|
Вход
Регистрация
FAQ пользователя
Поиск
