sapnote_0001085921

13.01.2013 of 17

SAP Note 1085921 - Document split

Note Language: English Version: 7 Validity: Valid Since 27.09.2012

Summary

SymptomThis note introduces document split consulting issues.

Other terms

New general ledger, passive split, active split, document splitting method,business transaction variant, document split, item category, processingcategory, splitting rule, zero balance.

Reason and Prerequisites

The current note describes the document split functionality within new G/L.New Installation: Before the first productive posting is done in new GLwith the usage of document splitting, the customizing (e.g. assignment ofscenarios, definition of split criteria and activation of documentsplitting, etc.) has to be done completely.New g/l should be active and the relevant scenarios have been assigned tothe ledger(s) in your system.Document split should be active for the relevant company codes in yoursystem.Migration: If an upgrade to ERP has been done, the classic FI is stillactive and can be used in the usual way.In addition if a customer wants to migrate to new G/L, he has to contact"SAP New G/L Migration" for further information on new general ledgermigration. Please, refer to note 812919.

For customers who use new g/l without document split and are planning touse document split please contact "SAP New G/L Migration" for furtherinformation. Please, refer to note 812919.

In case of subsequent changes in document splitting are needed, pleaserefer to note 891144.

Solution

1 Introduction

The note provides information regarding the document splittingfunctionality in new g/l for customers in phase before go live with new g/land document split.

New g/l is delivered with SAP ERP systems and is active per default in newInstallations. If an upgrade to ERP has been done, the classic FI is stillactive and can be used in the usual way.

Document Splitting is a function delivered within the new g/l, similar toFI-SL splitting available from release 4.7 onwards.

13.01.2013 of 17


Document splitting is an essential tool for drawing up complete financialstatements for the selected dimensions (e.g. SEGMENT, PROFIT CENTER,business area, fund, grant or customer field) at any time. Please see thedocumentation of the relevant customizing path for further information onthat.

Document splitting splits up line items during the posting for selecteddimensions such as receivable lines by PROFIT CENTER. Also, to affect azero balance setting in the document for selected dimensions such asSEGMENT, document splitting can be used. The zero balance setting maygenerate additional clearing lines in the general ledger view.

Entry view is based on table BSEG as used in classic g/l.G/l view is based on the new g/l tables.

You can choose between displaying the document either in its original formin the entry view or with the generated clearing lines from the perspectiveof a ledger in the general ledger view.

Issues and error messages for example "the balancing field is not filled"may arise while you are working with relevant business processes. Theseissues are usually based on missing or incorrect document splitcustomizing.

Subsequent activation of document split functionality within a productiveenvironment (with existing transactional data) is critical. It has to behandled with a separate migration project. Please address "SAP new g/lMigration" for the appropriate migration scenario.

Processes in a customer system are dynamic and changes in document splitcustomizing may arise. If subsequent changes are necessary, please refer tothe long text of the warnings and also to note 891144.

An example for vendor processes in detail is attached to the note.

An example for customer processes in detail is attached to the note.

An example for additional clearing line items in detail is attached to thenote.

An example for leading item is attached to the note.

2 Document split functionality

With the functionality 'document splitting' a complete financial statementfor selected dimensions can be provided at any time. Document splittingsplits up line items for selected dimensions such as SEGMENT, PROFITCENTER, etc.

Special terms such as item category, splitting rule, splitting method, etc.are used to adequately describe and customize document splittingfunctionality.

Document splitting method: A splitting method contains the splitting rulesgoverning how the individual item categories are dealt with.

13.01.2013 of 17


Splitting rule: Depending on the business transactions the rule governs howthe individual item categories will be processed by the system.

Business transaction: A business transaction describes the structure of abusiness process for each document type. For each business transaction, youcan determine which item categories (can) appear in the transaction.Business transactions are only used in document splitting. SAP delivers 10business transactions.Refer to: Document types classification for document split and Businesstransaction and business transaction variant

Item category: The item category characterizes the items of an accountingdocument. You need to classify the individual document items so that thesystem knows how to handle them. Therefore, an item category has to beassigned to all g/l accounts.Refer to: G/l accounts classification for document split (transaction codeGSP_LZ2).

Processing category: The processing category controls how the amounts aresplit. There are three options available:" Transfer a fixed value (no splitting)," Splitting by base item categories specified," Splitting based on current account balance.

Further information is available within Processing category

When using document splitting SAP recommends to avoid posting mixedbusiness processes.A new document type for each business process needs to be defined in orderto separate them.Example: Within SAP standard delivered customizing for business transaction0300 (vendor invoices) it is not possible to post customer or bank accountlines.Generally it has to be ensured that each business process is posted with anappropriate document type.

In any case - it is a consulting project to analyze and identify thecustomer's business processes and to customize document types according tothe customer's business processes.

2.1 New g/l scenarios

In order to define the relevant fields to be updated within open items andtotals, scenarios have to be assigned to the ledgers used.SAP standard delivers 6 scenarios. Also custom fields can be assigned.

In order to split the posted items of a particular ledger by the selectedcriteria (SEGMENT, PROFIT CENTER, custom field [ZZxxx], etc.), the relevantnew g/l scenario has to be assigned to this ledger.

2.2 Define document splitting method

The document splitting method contains the rules governing how theindividual item categories are dealt with.

13.01.2013 of 17


In case changes need to be applied to standard customizing, SAP recommendscopying the standard method 0000000012 and applying the changes.Sequence:- Create an own defined method (e.g. Z000000012):IMG-path: Financial Accounting (New) - General Ledger Accounting (New) -Business Transactions - Document Splitting - Extended Document Splitting -Define Document Splitting Method

- Select all rules included in the standard method and copy it to theZ000000012:IMG-path: Financial Accounting (New) - General Ledger Accounting (New) -Business Transactions - Document Splitting - Extended Document Splitting -Define Document Splitting Rule

- Apply the changes needed

- Activate the new to be used document splitting method

2.3 Activate document splitting

Document splitting can be activated in IMG:Financial Accounting (New) - General Ledger Accounting (New) - BusinessTransactions - Document Splitting - Activate Document Splitting.Also the document splitting method has to be assigned.

The indicator "Inheritance of Account Assignments" transfers the accountassignments which are defined as split criteria. The values of the splitcriteria are always taken into consideration together as a combination ofthe account assignments. The field values are inherited only in case theaccount assignment combination is unique within the complete document.That means the account assignments are being inherited if the values of thesplit criteria in the complete document are the same.

There is also a possibility to deactivate inheritance for some specificbusiness transactions.This indicator 'no inheritance of A/c Assignments' can be set/removed inthe definition of the business transaction (TA GSP_RD). The indicator isavailable only in ERP2005.A second option is to set a constant on the splitting method level. Theconstant defines default account assignments for all line items for whichit is not possible to derive any account assignments via the splitting ruleor the inheritance. To activate this function select indicator 'StandardA/C Assgnmt' and assign the constant. There is also a possibility todeactivate the default account assignment (constant) set on method levelfor some specific business transactions.For the definition of a constant refer to: Constant definition.Document split can be deactivated at company code level. In case one ormore company codes in your system should not use document splittingfunctionality, then choose the "inactive" indicator at company code level.If you perform any cross company code postings please make sure that allcompany codes involved use document splitting. In addition the companycodes which are used in cross company postings have to be assigned in OBY6to companies in a 1:1 relation.

2.4 Document splitting characteristics

13.01.2013 of 17


Document splitting is a tool for drawing up complete financial statementsfor selected dimensions. Additional zero balance items are automaticallycreated in case the balance of account assignment objects is not zero.Document splitting characteristics can be defined for general ledger,controlling and assets.In detail, you define:" Characteristics for general ledger in IMG "Define document splittingcharacteristics for general ledger accounting"." Additional characteristics to apply document splitting for controllingin IMG "Define document splitting characteristics for controlling"" For cash discounts capitalized to assets in IMG "DefinePost-Capitalization of cash discount to assets".

2.4.1 Document splitting characteristics for general ledger

In this IMG-step the account assignments taken into consideration indocument splitting are defined.It can be defined if a zero balance setting for the characteristic and apartner field has to be used. If the zero balance flag has been activated,the system makes sure that the document balances to zero on accountassignment level.The account assignment can also be defined as mandatory. The system acceptspostings if the account assignment has been filled in the general ledgerview. Either it can be filled in the entry view by entering it or it isderived from the document splitting rules.If a field is defined as a splitting characteristic, but the relevantscenario or custom field is not assigned to a ledger, then it will not beupdated in certain new g/l tables. The account assignments specified haveto be maintained at least in one of the ledgers. Otherwise the mandatorycheck is not processed.

2.4.2 Define Document Splitting Characteristics for Controlling

Document splitting characteristics for controlling are being transferredonly into relevant line items. The CO account assignments are just neededfor the cost elements. Therefore the accounts of the corresponding lineitems need to be defined as a cost element.

2.4.3 Define Post-Capitalization of Cash Discount to Assets

The activation of the "Post-Capitalization of Cash Discount to Assets" hasthe effect that the cash discount of an asset-relevant payment is notposted to the cash discount account, but directly to the asset.

2.4.4 Zero balance indicator and balance zero clearing account

The zero balance indicator setting, ensures that the document is balancedaccording to document split characteristics for the selected dimensionssuch as SEGMENT. In case the balance of account assignment objects is notzero after document splitting the system generates additional clearingitems. The triggered line items in the document are posted to the zerobalance clearing account defined for each account key in customizing(transaction code: GSP_KD1).Therefore, a clearing account has to be created for the additional clearingline items.

2.5 Account key assignment (define zero-balance clearing account)

13.01.2013 of 17


As explained above in some business processes additional clearing lineitems have to be created automatically so a full financial statement persplitting criteria is available.The automatic posting is made to a zero-balance clearing account defined inthe account key (transaction code: GSP_KD1). One or more zero-balanceclearing accounts may be used.

To post to one zero-balance clearing account, check the example inDoc_Split_Addit_Clear_Lines_v1_EN.pdf.

To post to different clearing accounts, each clearing account has to beassigned to a separate account key and each account key to the relevantbusiness transaction variants.

Check the example for multiple clearing line itemsDoc_Split_Add_Mult_Clear_Lines_EN.pdf.

Further information about the zero balance account master data creation isincluded in note 961937.

2.6 Constant definition

In order to set default account assignments within the document splitting,one or more constants can be defined.

IMG path:Financial Accounting (New) - General Ledger Accounting (New) - BusinessTransactions - Document Splitting - Edit Constants for Non-assignedProcesses

For defining the constant only the defined split criteria can be chosen. Adefault value can either be assigned to all or just to several splitcriteria. The default values are always set as a combination, meaning allor nothing.Example:Split criteria A and B is set as default- If fields A and B are both not filled during posting, the defaultvalues of the constant are set.- If field A is set with the default value of the constant and B is notfilled, the constant fills the value of field B.- If field A is set but not with the default value of the constant,nothing is done by the constant.- If any other split criteria is filled which is not defined within theconstant, the constant fills fields A and B.- If an assigned split criteria is set with default 'blank', the systemconsiders 'blank' as a value.

Two different ways of using a constant exist:- General constant for all business processes- Specific constant assigned to explicit item categories

General constant:The assignment of the general constant is done on the screen of 'activatedocument splitting'.If a general constant has been assigned, the default account assignment

13.01.2013 of 17


will be set in case if no other assignments have been derived frominheritance or the defined splitting rules.The general constant could be used, to make sure that a document is postedwith a default account assignment rather than a termination with anerror-message occurs.

Specific constant:In the definition of the splitting rule a constant can be assigned forcertain item categories. To assign a constant, processing category = 0 hasto be chosen.In case such a specific constant is assigned, the account assignment is setfor the line items posted with this item category and only if this specificbusiness transaction variant is used.The specific constant could be used, to make sure that some specificbusiness processes (e.g. integration with HR) can be posted. This would bethe case if the account assignment cannot be set via the splitting rule.Further information about processing category can be found: Processingcategory

The difference between these two ways how to use a constant is that for thegeneral constant the splitting rule is checked and the rule cannot set theaccount assignment.If a specific constant is assigned to an item category, no splitting rulehas been defined. Via this customizing the decision has been made to usethe specific constant rather than the splitting rule (for certain businessprocesses).

2.7 G/l accounts classification for document split

The first step to customize document splitting is to classify the g/laccounts. Classification of the g/l accounts is the process to assign g/laccounts to an item category (transaction code GSP_LZ2).The following item categories are available in the system:01000 Balance Sheet Account01001 Zero Balance Posting (Free Balancing Units)01100 Company Code Clearing01300 Cash Discount Clearing02000 Customer02100 Customer: Special G/L Transaction (available only in ERP2005)03000 Vendor03100 Vendor: Special G/L Transaction (available only in ERP2005)04000 Cash Account05100 Taxes on Sales/Purchases05200 Withholding Tax06000 Material07000 Asset20000 Expense30000 Revenue40100 Cash Discount (Expense/Revenue/Loss)40200 Exchange Rate Difference80000 Customer specificWith the classification of the g/l accounts, document splitting recognizeshow the individual line items are handled. The following accounts need tobe assigned in the system:" Revenue account" Expense account" Bank account/cash account

13.01.2013 of 17


" Balance sheet accountYou can enter one account or an account interval.Generally, the classification of other accounts is derived online by thesystem. In certain cases additional classification of other accounts mightbe needed.

With note 1069228 it is not possible to assign the item categories 01001and 01100 manually any more.

2.8 Document type classification for document split

To classify the document types assign the corresponding businesstransaction variant (transaction code GSP_VZ3).

The following business transactions are available in the system:

" Unspecified posting" Transfer posting from P&L to B/S account" Customer invoice" Vendor invoice" Bank account statement" Advance tax return (regular tax burden)" Goods Receipt for Purchase Order" Payments" Clearing transactions (account maint.)" Resetting cleared items

It is not possible to create own defined business transactions. However,own business transaction variants for the standard business transactionscan be defined (see chapter 'Business transaction and business transactionvariant').With the document types delivered in the standard customizing, SAP deliversa classification for document types. This is a proposal that needs to bechecked against the document types available in the customer system.Within document splitting a mix of several business processes posted withone document type is prohibited. Meaning each business process has to beposted with an own document type. Therefore it might be required to createmore document types.

2.9 Business transaction and business transaction variant

A business transaction describes the structure of a business process foreach document type. The split method together with the business transactionand the business transaction variant determine the splitting rule for eachparticular document. The splitting rule describes how the line items of adocument receive the account assignments. Each business transactiondetermines which item categories (can) appear in the document.

Business transactions:SAP delivers 10 business transactions. Own business transactions cannot becreated. Only the already existing business transaction can be used. Foreach of the SAP business transactions certain settings are delivered. Thesesettings cannot be reset. These settings describe the allowed itemcategories for each business transaction as well as if these item

13.01.2013 of 17


categories are set as obligatory or can occur only once within thedocument.

Business transaction variants:To adjust the settings to the required needs, the business transactionvariants can be used. For each business transaction SAP delivers thestandard business transaction variant 0001. These business transactionvariants contain the standard settings of the business transactions.These business transaction variants can be copied and adjusted accordingly.The adjustments allow only limitations of the already existing settings.

Even though no new business transactions can be created, with adjusting thevariants of the business transaction 0000 'unspecified posting' allbusiness requirements can be covered.

2.10 Splitting rules

The splitting rules describe the split behavior for each splitting method,business transaction/variant. Within the customizing of the splitting rulesthere are three hierarchy levels:Header dataItem categories to be editedBase item categories

In the header data the corresponding splitting rule can be chosen. Pleasemake sure that the activated splitting method and assigned businesstransaction/variant is selected.

In the list of the item categories to be edited those item categories aredefined that need to be processed and receive account assignments by thedocument splitting. It needs to be ensured that all item categories thathave no account assignments in the entry view of the document are includedin this list.

Base item categories determine for each line item all the possible lines inthe document that account assignments should be derived from. From all thepossible base item categories only the ones are taken into considerationthat do exist in the document to be split.

The delivered splitting methods are meant to act as a proposal for thepossible customizing. In general if further adjustments to the customerspecific business processes are required, the needed changes should be donein an own defined splitting method and business transaction/variant. TheSAP standard customizing should not be changed.

2.10.1 Processing category

In 'Control data' of the 'Item categories to be edited', in the definitionof the splitting rule (TA GSP_RD) the following three options for theprocessing category can be chosen:

0 Transfer a fixed value (no splitting)If this indicator is chosen, a constant needs to be defined and assigned tothis item category.

13.01.2013 of 17


In this case the system takes the fixed value maintained in the constant.

1 Splitting by base item categories specified (active split)The most common way of processing is '1 Splitting by base item categoriesspecified'. In that case the item category will be split on basis of thechosen base item category.

2 Splitting based on current account balanceWith this setting the system splits the posting by the splitting portionsbased on the current account balance per account assignments. Thisindicator was needed for 'Advance Return for Tax on Sales/Purchases'(RFUMSV00). Since note 889150 and related notes it is not recommended touse this indicator anymore.

2.10.2 Leading Item / Cross Company posting

An inter-company posting creates at least two documents, one per eachcompany code. There are two possible solutions to process inter-companydocuments:

1. Split each document in each company code separately.In this case there should be only one entry in the splitting rule for theitem category to be edited - 01100 CC <> CC of leading item.The split is performed locally. Only the line items which belong to thecurrently processed company code are taken into consideration.

2. Process all documents together as one inter-company document.In this case there should be two entries in the splitting rule for the itemcategory to be edited:" 01100 CC = CC of leading item" 01100 CC <> CC of leading itemThe split is performed for all the documents. Line items of all companycodes involved are taken into consideration.

The Leading Item category needs to be defined in case account assignmentsneed to be transferred across the company codes (only case 2.). It isneeded in order to identify the leading document where the accountassignment will be transferred to.The Document which does not contain the leading item will be processedfirst. The Company Code Clearing line (01100) of the document, which doesnot contain the leading item, is split based on the local document.

The Company Code Clearing line (01100) of the document, which does containthe leading item, is split on basis of the documents that have already beensplit locally in the first step.

For an example see attachment Doc_Split_Leading_Item_EN.pdf.

3 General Principles

3.1 Assignment string in document splitting

Case 1: Account assignment overwriting not allowed in document splitting

13.01.2013 of 17


Generally speaking, document splitting will not overwrite an accountassignment which has already been provided entering the document (entryview). For exceptions please see case 2. This fact should always beconsidered as well as the fact that the account assignments defined assplitting characteristics are treated as one assignment string in the lineitem. For that reason, in most of the cases we should not consider theaccount assignments as simple individual entities.It is an important fact that the different functionalities of documentsplitting will be processed for this complete assignment string. Wheneither the rule-based split functionality, inheritance or setting astandard account assignment (constant) in non-assigned lines is beingprocessed in order to derive the account assignment values, the completeassignment string (defined in customizing and recorded in tableFAGL_SPLIT_FIELD) will be considered to provide the assignment values tofurther lines. In case the splitting characteristics have been defined withtheir corresponding partner fields and the 'zero balance' option active,these partner assignments will also be considered during the splitting toform the assignment string.This logic is followed in order not to create new combinations of accountassignments which were not used in the original document.

We have to look at the combination of the split-criteria-assignments in aline item as one only assignment. This can easily be perceived in anposting example along with its corresponding customizing:

FIELD FTYPE_SPLIT PRTFIELD B_BALANCE B_MANDATORYSEGMENT XPRCTR X

SPLITMETHD SPLIT_INHERIDITY SPLIT_DEFAULT SPLIT_DEF_CONST0000000012 X

Vendor InvoiceBusiness Transaction: 0300Transaction Variant: 0001

If we try to post this invoice with the following account assignments:

BUKRS BLART HKONT KTOSL KOART PRCTR SEGMENTCC01 |KR |0000160000 |EGK |K | |SEGMENT02 CC01 |KR |0000223000 | |S |PC01 |SEGMENT01

Although the splitting rule 0300-0001 has been defined in standard to splitthe vendor line (item category 03000) from the expense item (item category20000), only the combination of PRCTR + SEGMENT ('PC01' and 'SEGMENT01')from the second line could be populated into the first one. Since the firstline already contains the segment value 'SEGMENT02', document splittingwill not overwrite the account assignment from the entry view. The profitcenter value 'PC01' from line 002 is not populated into the line 001.Therefore the PRCTR field is left as blank after splitting, even though thePRCTR was originally blank in the entry.

Result after splitting:

HKONT BLART LINETYPE PRCTR SEGMENT0000160000 |KR |03000 | |SEGMENT020000223000 |KR |20000 |PC01 |SEGMENT01

13.01.2013 of 17


Consequently, it will be inappropriate to set an account assignment valuein one of the splitting characteristics in case you are expecting anyaccount assignment to be populated from document splitting in that lineitem. In this particular case segment 'SEGMENT02' might have been derivedinto the vendor item by a customer substitution.

Case 2: Account assignment overwriting allowed in document splitting

Case 2.1: Dummy profit center

When posting a document which contains more than one profit center valueand at least one of them is defined as dummy profit center, documentsplitting may overwrite the dummy profit center with another value frominheritance, rule-based splitting (as long as the item with the dummyprofit center is not defined as base item in the splitting rule being usedin the posting) or constant. The dummy profit center can only beoverwritten, when classic Profit Center Accounting is active (TKA00-PCRCH,transaction 0KE5). In case the classic Profit Center Accounting is notactive, the dummy profit center is treated as any other default value andtherefore not overwritten by the document splitting even when defined inTKA01-DPRCT.

This circumstance is mainly due to the fact that the dummy profit centershould only be considered when no other possibilities have been found inorder to derive a 'real' profit center. Dummy profit center is assigned tothe controlling area when the profit center accounting is activated (TableTKA01, field 'DPRCT'). There can be only one dummy profit center definedfor each controlling area.

Case 2.2: Automatic split for clearing processes

For clearing lines, the account assignments are derived by referring to theoriginal line items to be cleared. During the automatic splitting, only thecleared items of the original documents are considered in order derive therelevant account assignments for the clearing lines and to split the lineaccordingly if necessary. If a clearing line contains a different accountassignment in the entry view (which normally should not happen in thestandard) it will be overwritten by the account assignments from thecleared items. This logic is followed in order to make sure that the wholeclearing process does balance to zero also on the account assignment level.The exception is the so called follow-up costs as realized exchange ratedifferences, cash discount lines and penalties which are split already inthe entry view (not only in the entry view). The account assignments forthe follow-up costs are also derived from the cleared items of the originaldocuments analog to the clearing lines, but already in the entry view.

The reason for the different logic in this case is to ensure theintegration with the CO. The g/l accounts for follow-up cost are normallyrelevant for Controlling and are defined as cost elements. Since CO is onlyintegrated with the entry view (and not with g/l view) of the FI document,it is important that the relevant account assignments are derived alreadyin the entry view and are transferred to Controlling. The option of whetherthe splitting characteristic fields are considered in splitting during thistype of splitting is defined in view V_FAGL_SPLIT_FL2. Refer to section"Document Splitting in Realized Exchange Rate Differences" in the onlinedocumentation for more information.

13.01.2013 of 17


Case 2.3: Online payment update in Public Sector Funds Management

Overwriting the account assignments is allowed in case of using the onlinepayment update functionality within the Public Sector Funds Management. SeeOSS notes 1431816, 951473 for more information.

Case 2.4: Previous Releases to ERP

Document splitting can be used not only for new g/l, but also for SpecialPurpose Leders (SL). Infact the document splitting in SL is also availablein earlier releases such as Enterprise 4.7. In this release the abovementioned logic of the account assignment string was not yet in place.Since the document splitting in the new General Ledger is used within legalreporting, the logic for the account assignment derivation needs to be morestrict, in this case not overwriting account assignments set in the entryview. The document splitting for new g/l and SL starting from ERP 5.0 usealmost the same coding. Consequently, the document splitting functionalityis more restrictive in the ERP compared to previous releases.

4 Recommendations and Examples

4.1 Changes in the master data

The profit center assignment to cost objects or the assignment of a SEGMENTto a PROFIT CENTER may change in case there aren't any transactional data.

In some cases you change the assignments even though transaction dataexists and the system issues the relevant warning message. The warningmessage is issued because such changes may lead to incorrect report resultsif transaction data already exists.

The postings in the previous validity period cannot be transferred to thenew assigned PROFIT CENTER or SEGMENT therefore we recommend the creationof a new master data.

If by any chance this is not possible then you have to consider thatprevious postings must be transferred manually to the new one in order tohave correct reports.

For further information refer to note 1037986.

4.2 Tips for setting up the customizing

Error messages like "Balancing field "Profit Center" in line item XXX notfilled" or "Item category XXXX is not allowed" are usually caused by thewrong customizing or by using inappropriate document types/accounts for theposted business processes.

In general it is very critical to change document split customizing aftergo-live. If due to wrong setting customizing changes are still needed,these should be done for new document types and new g/l accounts. Werecommend to create a new document type which will be used for postingslike this and assign it to a new business transaction variant.

In order to identify the root cause of the problem, follow the sequencebelow:

13.01.2013 of 17


1. Identify the business process that causes the error.2. Check which kind of line items are posted and which g/l accounts areinvolved.3. Identify which line items should have the account assignments in theentry view (i.e. entered manually) and for/from which lines the accountassignments should be derived in the g/l view.4. Check the active split method.5. Check the assignment of the involved g/l accounts to the itemcategories.6. Check the assignment of the document type to the business transactionvariant.7. Check the definition of the business transaction variant.8. Check in the definition of the splitting rule the "item categories tobe edited" and the according to basis lines.

Example 1: Vendor invoice

1. Vendor invoice.

2. The posting for vendor invoice is a credit amount to the vendorreconciliation account, a debit amount to the expense and automaticallycreated tax line (the example can use also multiple tax codes).

3. The account assignments on the expense lines are usually enteredmanually on the entry view. The account assignments for the vendor and taxlines have to be derived from the expense lines.

4. The SAP standard method 000000012 or a copy of it is assigned.

5. The item category assigned to the g/l accounts of the expense lineitem should be 20000. The item categories for the vendor (03000) and tax(05100) lines are being derived automatically.

6. The standard document type for vendor invoice KR is assigned e.g. tobusiness transaction variant 0300 / 0001.

7. For the documents posted with the standard business transactionvariant 0300 / 0001 at least one vendor line is obligatory. It isprohibited to post cash accounts within the same document.

8. In the splitting rule the item categories 03000 for vendor lines and05100 for tax lines are entered as "item categories to be edited, sincethey need to get the account assignments. Both item categories 03000 and05100 are to be split on the basis of the expense (20000).

Example 2: Posting to cash account and balance sheet account.

Correctly the cash account should be split according to balance sheetaccount. When customized incorrectly, the account assignments in the cashaccount are left blank. In this case either an error message being raisedor additional lines to zero balance accounts are triggered with blankaccount assignments. For print screens see the attachmentDoc_Split_unspecified_04000_EN.pdf

1. For example payment on account without clearing

13.01.2013 of 17


2. Cash accounts and balance sheet accounts are involved.

3. The account assignments for the cash accounts should be derived fromthe balance sheet accounts.

9. The SAP standard method 000000012 or a copy of it is assigned.

4. The cash account is assigned to 04000 (cash account) item category andthe balance sheet account to 01000 (balance sheet account) item categories.

5. New document type YY is assigned e.g. to business transaction variant0000 / Y001.

6. Business transaction variant 0000 / Y001 can be restricted on the itemcategories 04000 and 01000 if it used only for this business process.

7. For the business transaction variant 0000 / Y001 item category to edit04000 and the base item 01000 is maintained. So the cash account will besplit according to the balance sheet account (base item).

4.3 Consulting issues already documented with notes

" Tax line item remains without account assignment in the general ledgerview when you execute a down payment or a down payment clearing with taxes.

Refer to note 887794.

" Short dump CONVT_OVERFLOW or the system creates disproportional highamounts in the split rows in the general ledger view of the FI document.


" Cash journal postings using Transaction FBCJ end to error message GLT2201 occurs 'Balancing field "&1" in line item &2 not filled'.


" Invoices from SD that contain down payment clearing lines could notpreviously be split.Refer to note 1071612.

" You run the batch input session, which you created with reportSAPF103, and you receive error message GLT2 201.


" Master data of zero balance account

Refer to note 961937

" Integration of new g/l and HCM.

Refer to the note 1039346

13.01.2013 of 17


Header Data

Release Status: Released for CustomerReleased on: 01.10.2012 07:19:19Master Language: EnglishPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: FI-GL-FL Flexible Structures

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

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

Related Notes

Number Short Text

1652002 CO account assignmts/customer fields as doc splitting chars

1492963 Changing assgmt of item categories to bus. transac. variant

1330814 Restrictions for "Online Split for Follow-Up Costs"

1075371 Additions to Note 1040017

1074451 NewGL analysis: Trace for new general ledger documents

1072850 Field overflow or very large amounts due to doc splitting

1071612 Down payment clearing with final invoice from SD

1067344 Too many entries in FAGL_SPLINFO or FAGL_SPLINFO_VAL

1061741 Error GLT2 201 for follow-on documents from FI-CA

1058804 RAPOST2000/RAPOST2001: Problems with document handling

1058676 PCP0: No additional RF048 entry for document split in FI

1050082 Incorrect split w/ partially maintained constant definition

1049706 FICORE 704: Tax code '**' not defined

1046814 Partner assignment to company code clearing lines II

1041694 Online-Split:Documents with incorrect debit/credit indicator

1029426 ERP: No distribution information with reversed documents 2

1024005 Doc splitting: Dump during neg posting w/ ext doc number

1011599 Split: Version management for generated include programs

1005749 NewGL: Error GLT2 002 for invoice references

1000955 ERP: Error GLT0 003 for report FAGL_FC_TRANSLATION

996852 Down payment on AUC and document splitting

993752 RFUMSANF: Integration of document splitting

13.01.2013 of 17


Number Short Text

981614 ERP: Parked documents and document splitting

979435 ERP: Error GLT0 002 with foreign currency valuation

973342 Doc splitting: Creation of the zero balance clearing items

961937 Document splitting: Master data zero balance clearing acct

948737 Settlement of an asset: Clearing lines by online split

944352 SAPF104: Split account assignments in provision postings

937436 NewGL: No generation of document splitting after import

922743 New GL with doc splitting - document types in cash journal

909278 FS on additional account assignments at cash receipt example

900702 Inhrtd & dft acct assgmt lines w/o FAGL_SPLINFO acct assgmnt

891144 New GL/Document splitting: Risks w/ subsequent changes

890237 New GL with document splitting: Legacy data transfer

889893 FI-GL (new)- Line items without posting key

889404 Tax payable posting assignd to an accnt w/ advnce tax return

889146 Missing account assignments in balance valuation

888389 Incorrect currency-related distributions in docmnt splitting

887794 Document splitting: Handling of down payment clearing

840077 ERP: Message GLT2 201 on lines with zero amounts

Attachments

FileType

File Name Language Size

PDF Doc_Split_Add_Mult_Clear_Lines_EN.pdf

E 275 KB

PDF Doc_Split_Addit_Clear_Lines_v1_EN.pdf

E 261 KB

PDF Doc_Split_Leading_Item_EN.pdf E 336 KB

PDF Doc_Split_Overview_Customer_EN.pdf E 648 KB

PDF Doc_Split_Overview_Vendor_EN.pdf E 881 KB

PDF Doc_Split_unspecified_04000_EN.pdf E 249 KB

sapnote_0001085921

Documents

Transcript of sapnote_0001085921