1628607 - Document splitting: Business process assigned in entry view
Symptom
In document splitting, you expect that certain business processes already contain all necessary account assignments and are no longer split, because an account assignment according to cause is not recognizable from the document to be posted. This note describes how to handle these processes in configuration.
Other Terms
CO, FI, real-time integration, company code clearing, company code clearing lines, BUV, MM, goods receipt, goods issue, item category, Customizing, document splitting, account assignment, GSP_RD, GSP_VZ3, HCM, HR, constant, document type, RFUMSV00, GLT0004, RFUMSV00, GLT2201, field overflow, CX_SY_ARITHMETIC_OVERFLOW, ELIM_ROUND_DIFF
Reason and Prerequisites
You have activated the new general ledger and document splitting with at least one document splitting characteristic as a required entry field.
Solution
During the configuration of the document splitting, you must ensure that an account assignment according to cause can be derived for all relevant business processes. There are various modules/processes that already provide all line items with the required account assignments, so that no further derivation of account assignments by document spiltting is required. There are also some technical restrictions so that cause-related splitting is not possible.
Note that all statements in this note refer to the standard GL characteristics (PRCTR, SEGMENT and GSBER). The "Segment" field plays a special role here, because the new field introduced for Release ERP 5.0 cannot be determined in some source applications and is therefore not derived until the posting in FI. For special account assignments, such as fund for public sector functionalities, other regulations may apply, because these are not known in many sending applications and must therefore be additionally derived and processed by the document splitting. The following statements are not valid for customer-defined account assignments. However, it is always the responsibility of the customer to ensure the correct derivation of customer-defined fields.
1. CO-FI Real-Time Integration (RTI)/CO Settlement
If RTI is active, corresponding documents are automatically posted in FI according to the set RTI variant in the case of transfer postings in CO (for example assessment or distribution). These documents should have already been provided with all necessary account assignments or partner assignments on the CO side. In this case the account assignments already appear in the entry view of the FI document. Normally, the account assignments are derived from the master data of the sender or receiver objects. You must therefore ensure that the master data is maintained correctly in the relevant objects. For objects that have no account assignments, for example when settling to a GL account, the account assignments can be manually added to the settlement rule directly. The partner assignments are derived from the partner relationship of the sender and receiver. In the case of cross-company code transactions that are posted from CO to FI, the company code clearing lines are also already assigned in the entry view or split if necessary. For this, Notes 995055 and 1039189 must be implemented in your system.
Because all required account assignments must already be set for the RTI, these types of documents are posted with a document type that no longer performs an additional splitting. The document type used should be assigned to a business transaction variant that contains no item categories to be processed. The standard characteristics of business transaction variant 0000/0001 is unsuitable in this case, because these contain rules for the assignment of the company code clearing lines.
2. Goods Receipt or Goods Issue from Materials Management (MM)
When posting the goods receipt or issue, the account assignments relevant to the general ledger are normally already set in MM in all lines. In the case of a purchase order with account assignment, the account assignments relevant to the general ledger are derived from the CO account assignment in the purchase order. In the case of a purchase order without account assignment, the account assignments for the general ledger are derived from the corresponding Customizing settings (for example material master record). It is therefore very important in this case that the required assignments or master records are maintained accordingly. The company code clearing lines are not created and assigned by the sending application (MM) in this case.
Because all required account assignments for this MM transaction (except in the company code clearing lines) must already be set, we recommend that you use business transaction 0600 (for goods receipt for purchase order) or 0000 in Customizing for document splitting. In the standard delivery, the standard business transaction variants 0600/0001 and 0000/0001 do not contain any splitting rules except for the company code clearing lines (item category 01100).
Note that all statements in this note refer to the standard GL characteristics (PRCTR, SEGMENT and GSBER). The "Segment" field plays a special role here, because the new field introduced for Release ERP 5.0 cannot be determined in some source applications and is therefore not derived until the posting in FI. For special account assignments, such as fund for public sector functionalities, other regulations may apply, because these are not known in many sending applications and must therefore be additionally derived and processed by the document splitting. The following statements are not valid for customer-defined account assignments. However, it is always the responsibility of the customer to ensure the correct derivation of customer-defined fields.
1. CO-FI Real-Time Integration (RTI)/CO Settlement
If RTI is active, corresponding documents are automatically posted in FI according to the set RTI variant in the case of transfer postings in CO (for example assessment or distribution). These documents should have already been provided with all necessary account assignments or partner assignments on the CO side. In this case the account assignments already appear in the entry view of the FI document. Normally, the account assignments are derived from the master data of the sender or receiver objects. You must therefore ensure that the master data is maintained correctly in the relevant objects. For objects that have no account assignments, for example when settling to a GL account, the account assignments can be manually added to the settlement rule directly. The partner assignments are derived from the partner relationship of the sender and receiver. In the case of cross-company code transactions that are posted from CO to FI, the company code clearing lines are also already assigned in the entry view or split if necessary. For this, Notes 995055 and 1039189 must be implemented in your system.
Because all required account assignments must already be set for the RTI, these types of documents are posted with a document type that no longer performs an additional splitting. The document type used should be assigned to a business transaction variant that contains no item categories to be processed. The standard characteristics of business transaction variant 0000/0001 is unsuitable in this case, because these contain rules for the assignment of the company code clearing lines.
2. Goods Receipt or Goods Issue from Materials Management (MM)
When posting the goods receipt or issue, the account assignments relevant to the general ledger are normally already set in MM in all lines. In the case of a purchase order with account assignment, the account assignments relevant to the general ledger are derived from the CO account assignment in the purchase order. In the case of a purchase order without account assignment, the account assignments for the general ledger are derived from the corresponding Customizing settings (for example material master record). It is therefore very important in this case that the required assignments or master records are maintained accordingly. The company code clearing lines are not created and assigned by the sending application (MM) in this case.
Because all required account assignments for this MM transaction (except in the company code clearing lines) must already be set, we recommend that you use business transaction 0600 (for goods receipt for purchase order) or 0000 in Customizing for document splitting. In the standard delivery, the standard business transaction variants 0600/0001 and 0000/0001 do not contain any splitting rules except for the company code clearing lines (item category 01100).
The additional material ledger documents that are posted together with MM documents (both MM goods movements and invoices from logistics invoice verification) within an LUW should also already contain all the G/L-relevant account assignments. Refer to Note 1884540 for information about the Customizing settings in this case.
3. Payroll (HCM)
Due to the summarized posting method of documents from HR, the document splitting does not have the required information in order to guarantee a cause-based splitting of the account assignments. For this reason, as of Release ERP 6.0 the splitting is performed directly in the HR module and transferred to FI fully assigned.
Because all required account assignments must also be set for this transaction, these types of documents should be posted with a document type that no longer performs an additional splitting. For HR postings the documents are very large and are posted to FI together within the payroll run. An exception to this is return postings to the old year if the splitting of payables was performed retrospectively on the HCM side. In this case, you must define a special constant in the business transaction variant. Splitting the company code clearing lines is not relevant in this scenario, because the payroll is posted for each company code and therefore no company code clearing lines are created. If a business transaction variant is assigned for the HR document type used, and this variant processes the rule-based document split, this largely results in performance and memory problems.
In exceptional cases, a rule-based split for tax items can be required for HR documents, because the tax items are not assigned based on cause from the HR side for technical reasons. If tax is supposed to be posted in HR, a splitting rule must be created for the item category 05100 (tax). The tax must always be defined taking into account the "Check tax code" indicator.
The technical split lines are another exception. These auxiliary lines are created if a HR document contains more than 999 lines and must technically be split in several FI documents. In this case, the technical split lines ensure that each partial document balances to zero in FI. The technical split lines also balance to zero and therefore have no business-related effect on the overall process. For this reason, they remain unassigned in the standard system and are excluded from the required field check during document splitting. You can find more details in Note 511614.
You can find further information about splitting payables in payroll in Note 1039346.
4. Periodic Closing Operations
Periodic closing entries in FI, for example foreign currency valuation, advance return for tax on sales/purchases and so on, are based on existing transaction data. You must ensure that the account assignments of the closing entries correspond to the line items referred to by the periodic postings. In order to guarantee these account assignments according to cause, a mechanism was implemented in the closing programs to derive account assignments from the corresponding line items. These are then transferred to the entry view when the FI documents are created. As a result, these documents must not be processed further by the document splitting.
The prerequisite for this are the corresponding settings in the view V_FAGL_SPLIT_FL2 (transaction SM30 - Display). For example, the indicator in the column "Val.ExchRateDif" must be set for all account assignments that are relevant for the foreign currency valuation documents. Of course you must also ensure that the original postings are assigned correctly.
An exception is the assessment and distribution in the general ledger. The allocation does not contain an item reference and therefore cannot automatically derive any account assignments. In this case, all required account assignments must be entered manually (in the cycle, for example).
Because all required account assignments must already be set for the closing entries, these types of documents are posted with a document type that no longer performs an additional splitting. The standard business transaction variant 0000/0001 (unspecified posting) is one possible allowed entry.
5. Asset Accounting (FI-AA)
For lines that are created in Asset Accounting, the account assignments are derived from the asset master record according to Customizing. The prerequisites for this are described in Note 684659.
In general, all documents that refer to a fixed asset or are created by Asset Accounting (for example depreciations, balance sheet adjustments and so on) are already provided with the account assignments in the entry view. For fixed asset lines, item category 07000 is derived automatically. In the splitting rule, item category 07000 should not be defined as an item category to be processed.
6. Contract Accounts Receivable and Payable (FI-CA)
Documents from FI-CA are posted in summary to the document splitting and do not contain the level of detail that is necessary to perform a cause-based splitting in FI. Therefore, the FI-CA documents are deliberately excluded from processing by the document spitting and from the required field check. This is based on the document origin (field AWTYP = FKKSU), regardless of the assigned business transaction variant.
As of Release ERP 6.0, there is an option to provide the "Segment" field with correct values directly in FI-CA and to post them to FI already assigned. As of Release ERP 6.04 (ERP 6.0 with Enhancement Package 4), there is also a solution for profit center in FI-CA. You can find more detailed information about this in Note 1070629, point 3 of the appendix ("Is the new general ledger compatible with FI-CA (FI - Contract Accounting)?") The following notes are relevant for the supply of general ledger-relevant fields in FI-CA: 1285775, 1269687, 1469556, 1469741, 1468167, 1473984, 1171402.
3. Payroll (HCM)
Due to the summarized posting method of documents from HR, the document splitting does not have the required information in order to guarantee a cause-based splitting of the account assignments. For this reason, as of Release ERP 6.0 the splitting is performed directly in the HR module and transferred to FI fully assigned.
Because all required account assignments must also be set for this transaction, these types of documents should be posted with a document type that no longer performs an additional splitting. For HR postings the documents are very large and are posted to FI together within the payroll run. An exception to this is return postings to the old year if the splitting of payables was performed retrospectively on the HCM side. In this case, you must define a special constant in the business transaction variant. Splitting the company code clearing lines is not relevant in this scenario, because the payroll is posted for each company code and therefore no company code clearing lines are created. If a business transaction variant is assigned for the HR document type used, and this variant processes the rule-based document split, this largely results in performance and memory problems.
In exceptional cases, a rule-based split for tax items can be required for HR documents, because the tax items are not assigned based on cause from the HR side for technical reasons. If tax is supposed to be posted in HR, a splitting rule must be created for the item category 05100 (tax). The tax must always be defined taking into account the "Check tax code" indicator.
The technical split lines are another exception. These auxiliary lines are created if a HR document contains more than 999 lines and must technically be split in several FI documents. In this case, the technical split lines ensure that each partial document balances to zero in FI. The technical split lines also balance to zero and therefore have no business-related effect on the overall process. For this reason, they remain unassigned in the standard system and are excluded from the required field check during document splitting. You can find more details in Note 511614.
You can find further information about splitting payables in payroll in Note 1039346.
4. Periodic Closing Operations
Periodic closing entries in FI, for example foreign currency valuation, advance return for tax on sales/purchases and so on, are based on existing transaction data. You must ensure that the account assignments of the closing entries correspond to the line items referred to by the periodic postings. In order to guarantee these account assignments according to cause, a mechanism was implemented in the closing programs to derive account assignments from the corresponding line items. These are then transferred to the entry view when the FI documents are created. As a result, these documents must not be processed further by the document splitting.
The prerequisite for this are the corresponding settings in the view V_FAGL_SPLIT_FL2 (transaction SM30 - Display). For example, the indicator in the column "Val.ExchRateDif" must be set for all account assignments that are relevant for the foreign currency valuation documents. Of course you must also ensure that the original postings are assigned correctly.
An exception is the assessment and distribution in the general ledger. The allocation does not contain an item reference and therefore cannot automatically derive any account assignments. In this case, all required account assignments must be entered manually (in the cycle, for example).
Because all required account assignments must already be set for the closing entries, these types of documents are posted with a document type that no longer performs an additional splitting. The standard business transaction variant 0000/0001 (unspecified posting) is one possible allowed entry.
5. Asset Accounting (FI-AA)
For lines that are created in Asset Accounting, the account assignments are derived from the asset master record according to Customizing. The prerequisites for this are described in Note 684659.
In general, all documents that refer to a fixed asset or are created by Asset Accounting (for example depreciations, balance sheet adjustments and so on) are already provided with the account assignments in the entry view. For fixed asset lines, item category 07000 is derived automatically. In the splitting rule, item category 07000 should not be defined as an item category to be processed.
6. Contract Accounts Receivable and Payable (FI-CA)
Documents from FI-CA are posted in summary to the document splitting and do not contain the level of detail that is necessary to perform a cause-based splitting in FI. Therefore, the FI-CA documents are deliberately excluded from processing by the document spitting and from the required field check. This is based on the document origin (field AWTYP = FKKSU), regardless of the assigned business transaction variant.
As of Release ERP 6.0, there is an option to provide the "Segment" field with correct values directly in FI-CA and to post them to FI already assigned. As of Release ERP 6.04 (ERP 6.0 with Enhancement Package 4), there is also a solution for profit center in FI-CA. You can find more detailed information about this in Note 1070629, point 3 of the appendix ("Is the new general ledger compatible with FI-CA (FI - Contract Accounting)?") The following notes are relevant for the supply of general ledger-relevant fields in FI-CA: 1285775, 1269687, 1469556, 1469741, 1468167, 1473984, 1171402.
No comments:
Post a Comment