Document Online

Split

SAP AG
 Document Split: Invoice (Example: Split on Profit Center)

Entry
Vendor View
Invoice
General
Vendor Ledger
Invoice View
(Flexibility)
PK Account Prctr CostCtr
PK Account Prctr CostCtr
Amount Amount

40 Expense PC01 CC01 40 Expense PC01 CC01

400.00
400.00
40 Expense PC02 CC02 40 Expense PC02 CC02
600.00 Enhancement 600.00
31 Vendor
41 Payable PC01
1000.00-
Document number 4711 400.00-
31 Payable PC02
600.00-

Split
Totals Actual
info table
table Balances line items Posting

FAGL_SPLITINFO
FAGL_SPLITINFO_VAL

ã SAP AG 2004 / 2
 Enhancing the Follow-up Costs

Clearing: Enhancing the follow-up costs (before RWIN)

Entry View 4712 Entry View Enhanced Document

Vendor payment for 4711 Vendor payment

PK Acc. Prctr CoCtr Amount PK Acc. Prctr CoCtr Amount

25 Payable 1,000.00 25 Payable. 1,000.00
50 Bank 970.00 - 50 Bank 970.00 -
50 Discount 30.00 - 50 Disc. PC01 CC01 12.00 -
50 Disc. PC02 CC02 18.00 -

Projection

Split Info
4711 < reference to invoice
001

ã SAP AG 2004 / 3
 Document Split: Payment

Enhancement of the document (in RWIN)

Enhanced Document General Ledger View

Vendor payment
Vendor payment

PK Account Prctr CoCtr Amount PK Account Prctr CoCtr Amount

25 Payable 1000.00 25 Payable PC01 400.00
50 Bank 970.00 - 25 Payable PC02 600.00
50 Discount PC01 CC01 12.00 - 50 Bank PC01 388.00 -
50 Discount PC02 CC02 18.00 - 50 Bank PC02 582.00 -
50 Discount PC01 CC01 12.00 -
50 Discount PC02 CC02 18.00 -

Cleared document
4711 Enhancement

4711

Totals Split info

table Balances table Update
GLFLEXT

ã SAP AG 2004 / 4
 Terms of the Split Logic

 Business transaction: For example, customer invoice, payment,

account statement or un-specified posting.
 Business transaction variant: The maximum (default) number of item
types (see below) assigned to the business transaction can be
restricted (customer specific).
 Item type: Classification of lines for document splitting, such as item
type “customer line item” (only relevant for the part of document
splitting that is rule based - see below). The split is not rule based in
case of clearing and if a zero balance is generated. The split is always
performed for these processes.
 Splitting method: Recognizes the business transaction variants.
The splitting methods combined with the BT variants produce a rule.
The procedure 0000000012 is the standard (recommended to
customers).
 Rule: Includes from where the split information is to be taken
(basic item type = line type, such as revenue) and the target of the split
(item type to be processed, such as customer line item).

ã SAP AG 2004 / 5
 Split Logic

Classification as a business transaction Document type CI (customer

for document splitting
invoice)

Business
Business
Splitting method transaction
transaction
variant
0000000012
0200 (customer 0001 (standard)
invoice)

RULE
02000 customer What is the target
Item type to of the split
line item be processed information?
… According to the basic item

30000 revenue What is the source of

Basis item type the split information?
…
ã SAP AG 2004 / 6
 Classify G/L Accounts for Document Splitting

ã SAP AG 2004 / 7
 Classify Document Type for Document Splitting

ã SAP AG 2004 / 8
 Define Document Splitting Characteristics for General
Ledgers

ã SAP AG 2004 / 9
 Additional Document Splitting Characteristics

ã SAP AG 2004 / 10
 Splitting Method

ã SAP AG 2004 / 11
 Defining Splitting Rule – Header Data

ã SAP AG 2004 / 12
 Splitting Rules – Detailed View of Header Data

ã SAP AG 2004 / 13
 Splitting Rule – Item Category to be Edited

ã SAP AG 2004 / 14
 Work Steps for Splitting Documents (within the program)

Example: Payment with residual items without invoice reference

1 Interpretation of Customizing

Passive split
2 Clearings and similar processes
Not customizable

3 Active split
Customizable

Balance –0 –creation
4
Can be adjusted in Customizing

ã SAP AG 2004 / 15
 Derivation and Passive Split

Account Amount Acc. Assignment Item Category

Payment – Enter View
Bank 900 S3
Initial Situation
Receivable -1000
Residual Items 100
Interpretation of Customizing BTV 1000/ 0001
-Derivation of the business transaction
Bank 900 04000 -Assignment of the item category
1 -Checking the validity of the item
Receivable -1000 02000 category for the business transaction
(see definition of the transaction variant)
Residual Items 10 02000
Passive split in Clearing BTV 1000/ 0001
Bank 900 S3 04000
2 Clearing line!
Receivable -400 S1 02000 Passive Split
Receivable -600 S2 02000 Determined from
original invoice document.
Residual Items 100 02000 Not customizable!!!

ã SAP AG 2004 / 16
 Active Split

Account Amount Acc. Assignment Item Category

Active Split in Clearing
Bank 900 S3 04000
Receivable -400 S1 02000
Receivable -600 S2 02000 3
Residual Items 40 S1 02000
Active Split - Customizing!
Residual Items 60 S2 02000
Residual items without invoice
reference split on the basis of
the receivables clearing lines
(passive split) in the previous step

Attention: Residual items with invoice reference are split passively

ã SAP AG 2004 / 17
 Creating Zero Balance

Account Amount Acc. Assignm./ Item Category

Partn.-Acc. Assignm.

Creating Zero Balance

Bank 900 S3 04000
Receivable -400 S1 02000
Receivable -600 S2 02000
Residual Item 40 S1 02000
Residual Item 60 S2 02000
Acc. Assignment -360 S3 S1 01001
Acc. Assignment +360 S1 S3 01001
Acc. Assignment -540 S3 S2 01001 Passive Split
4 creating 0-balance per segment.
Acc. Assignment +540 S2 S3 01001
If, in Customizing, 0-balance
is activated for the respective
dimension.

ã SAP AG 2004 / 18
 Check Tax Code

Tax table:
Receivable 1100 A1 = 5 %
Revenues A1 400 S1 A2 = 13 % (approx.!)
Revenues A2 600 S2
Tax A1 20
Tax lines determined at time
Tax A2 80
before the split
a) Check Tax Code
Split results a) and b)
Tax A1 20 S1
Tax A2 80 S2

Different split in position

b) Check Tax Code is not activated category tax line to be edited

Tax A1 8 S1
Tax A1 12 S2
Tax A2 32 S1
Tax A2 48 S2

ã SAP AG 2004 / 19
 Items to be Edited – Detailed View

ã SAP AG 2004 / 20
 Cross-Company Code Document Split I

ã SAP AG 2004 / 21
 Cross-Company Code Document Split II

ã SAP AG 2004 / 22
 Cross-Company Code Document Split III

CC1 CC2 CC3

Entering Leading company code

Customer 1100 Revenues 1 300- S1 Revenues 2 400- S2

Revenues 3 300- S3

Assignment Clearing CC3 700- Clearing CC1 700

Clearing. CC2 300- Clearing CC 1 300

1
2 2
Split Clearing CC 3 400- S2 Clearing CC 1 300 S1 Clearing CC1 400 S2
Clearing CC 3 300- S3 Clearing CC1 300 S3

Clearing CC 2 300- S1
1

ã SAP AG 2004 / 23
 Define Base Item Category

ã SAP AG 2004 / 24
 Activating the Document Split

ã SAP AG 2004 / 25
 Business Transaction – Transaction Variants

ã SAP AG 2004 / 26
 Transaction Variants

ã SAP AG 2004 / 27
 Assigned Item Categories

ã SAP AG 2004 / 28
 Insert Additional Fields to Totals Table –
3 Possibilities

1. Activate SAP‘s standard scenario per Ledger in IMG:

Cost Center, Preparations for consolidations, Business area, Profit center, Segmentation, Cost of sales
accounting
>Further system activity: Activate new field as customer
enhancement per Ledger in totals table.
2. More Standard Fields (Set of SAP-Default-Fields) :
ZZAUFNR - Internal order number
ZZGRIRG - Region (State , Province, County)
ZZHRKFT - Origin group as subdivision of cost element)
ZZPRZNR - Business process
ZZPS_PSP_PNR - Work break down structure element (WBS-element)
ZZWERKS - Plant

>Further system activity: Activate new field as customer

enhancement per Ledger in totals table.
If further fields are required, please contact SAP‘s development area

3. Customer Fields
First: Insert new field in Coding Block.
Then: Enter field using transaction FAGL_GINS (reference to data element)
>Further system activities: Activate field as customer enhancement
per ledger in totals table.

ã SAP AG 2004 / 29
 Copyright 2007 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of
Microsoft Corporation.
IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®,
OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and
Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
ORACLE® is a registered trademark of ORACLE Corporation.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other
Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
JAVA® is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves information purposes only. National product specifications may vary.

ã SAP AG 2004 / 30