05 Document Online Split

8/8/2019 05 Document Online Split

1/30

SAP AG

Document OnlineSplit


2/30

SAP AG 2004 / 2

Actual

line items

Split

info table

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

Totals

table

Enhancement

Entry View General Ledger View

(Flexibility)

Balances

Vendor Invoice

PK Account Prctr CostCtr Amount

40 Expense PC01 CC01 400.00

40 Expense PC02 CC02 600.0031 Vendor 1000.00-

Vendor Invoice

PK Account Prctr CostCtr Amount



31 Payable PC01 400.00-

31 Payable PC02 600.00-Document number 4711

FAGL_SPLITINFO

FAGL_SPLITINFO_VAL

Posting


3/30

SAP AG 2004 / 3

Enhancing the Follow-up Costs

Vendor payment for 4711

PK Acc. Prctr CoCtr Amount

25 Payable 1,000.00

50 Bank 970.00 -50 Discount 30.00 -

Vendor payment

PK Acc. Prctr CoCtr Amount

25 Payable. 1,000.00

50 Bank 970.00 -50 Disc. PC01 CC01 12.00 -

50 Disc. PC02 CC02 18.00 -

Split Info

4711

001

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

Projection

Entry View 4712 Entry View Enhanced Document

< reference to invoice


4/30

SAP AG 2004 / 4

Document Split: Payment

Totals

table

GLFLEXT

Split info

table

Enhancement

UpdateBalances

Cleared document

4711

4711

Enhanced Document

Vendor payment

PK Account Prctr CoCtr Amount

25 Payable 1000.00

50 Bank 970.00 -

50 Discount PC01 CC01 12.00 -

50 Discount PC02 CC02 18.00 -

General Ledger ViewVendor payment

PK Account Prctr CoCtr Amount

25 Payable PC01 400.00

25 Payable PC02 600.00

50 Bank PC01 388.00 -

50 Bank PC02 582.00 -

50 Discount PC01 CC01 12.00 -50 Discount PC02 CC02 18.00 -

Enhancement of the document (in RWIN)


5/30

SAP AG 2004 / 5

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 itemtypes (see below) assigned to the business transaction can berestricted (customer specific).

Item type: Classification of lines for document splitting, such as itemtype customer line item (only relevant for the part of documentsplitting that is rule based - see below). The split is not rule based incase of clearing and if a zero balance is generated. The split is alwaysperformed 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 tocustomers).

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).


6/30

SAP AG 2004 / 6

0200 (customer 0001 (standard)

invoice)

Splitting method

0000000012

Business

transaction

Business

transaction

variant

Document type CI (customer

invoice)

Item type to

be processed

02000 customer

line item

Basis item type

RULE

30000 revenue

According to the basic item

Classification as a business transaction

for document splitting

What is the source of

the split information?

What is the target

of the split

information?

Split Logic


7/30

SAP AG 2004 / 7

Classify G/L Accounts for Document Splitting


8/30

SAP AG 2004 / 8

Classify Document Type for Document Splitting


9/30

SAP AG 2004 / 9

Define Document Splitting Characteristics for GeneralLedgers


10/30

SAP AG 2004 / 10

Additional Document Splitting Characteristics


11/30

SAP AG 2004 / 11

Splitting Method


12/30

SAP AG 2004 / 12

Defining Splitting Rule Header Data


13/30

SAP AG 2004 / 13

Splitting Rules Detailed View of Header Data


14/30

SAP AG 2004 / 14

Splitting Rule Item Category to be Edited


15/30

SAP AG 2004 / 15

Work Steps for Splitting Documents (within the program)

Interpretation of Customizing

Passive splitClearings and similar processes

Not customizable

Active split

Customizable

Balance 0 creation

Can be adjusted in Customizing

Example: Payment with residual items without invoice reference

1

2

3

4


16/30

SAP AG 2004 / 16

Derivation and Passive Split

Account Amount Acc. Assignment Item Category

Payment Enter View

Bank 900 S3

Receivable -1000

Residual Items 100

Interpretation of Customizing BTV 1000/ 0001

Bank 900 04000

Receivable -1000 02000

Residual Items 10 02000

Passive split in Clearing BTV 1000/ 0001

Bank 900 S3 04000

Receivable -400 S1 02000


Residual Items 100 02000

Clearing line!

Passive Split

Determined from

original invoice document.

Not customizable!!!

Initial Situation

-Derivation of the business transaction-Assignment of the item category

-Checking the validity of the item

category for the business transaction

(see definition of the transaction variant)

1

2


17/30

SAP AG 2004 / 17

Active Split

Account Amount Acc. Assignment Item Category

Active Split in Clearing

Bank 900 S3 04000



Residual Items 40 S1 02000

Residual Items 60 S2 02000

Active Split - Customizing!

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

3


18/30

SAP AG 2004 / 18

Creating Zero Balance

Account Amount Acc. Assignm./ Item Category

Partn.-Acc. Assignm.

Creating Zero Balance

Bank 900 S3 04000



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

Acc. Assignment +540 S2 S3 01001

Passive Splitcreating 0-balance per segment.

If, in Customizing, 0-balance

is activated for the respective

dimension.

4


19/30

SAP AG 2004 / 19

Check Tax Code

Receivable 1100Revenues A1 400 S1

Revenues A2 600 S2

Tax A1 20

Tax A2 80

Check Tax Code

Tax A1 20 S1

Tax A2 80 S2

Different split in position

category tax line to be editedCheck Tax Code is not activated

Tax A1 8 S1

Tax A1 12 S2

Tax A2 32 S1

Tax A2 48 S2

a)

b)

Tax table:

A1 = 5 %A2 = 13 % (approx.!)

Tax lines determined at time

before the split

Split results a) and b)


20/30

SAP AG 2004 / 20

Items to be Edited Detailed View


21/30

SAP AG 2004 / 21

Cross-Company Code Document Split I


22/30

SAP AG 2004 / 22

Cross-Company Code Document Split II


23/30

SAP AG 2004 / 23

Cross-Company Code Document Split III

Leading company code

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

Revenues 3 300- S3

Entering

Assignment Clearing CC3 700- Clearing CC1 700Clearing. CC2 300- Clearing CC 1 300

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

1

CC1 CC2 CC3

2 2


24/30


25/30

SAP AG 2004 / 25

Activating the Document Split


26/30

SAP AG 2004 / 26

Business Transaction Transaction Variants


27/30

SAP AG 2004 / 27

Transaction Variants


28/30

SAP AG 2004 / 28

Assigned Item Categories


29/30

SAP AG 2004 / 29

Insert Additional Fields to Totals Table 3 Possibilities

1. Activate SAPs 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 customerenhancement per Ledger in totals table.

2. More Standard Fields (Set of SAP-Default-Fields) :ZZAUFNR - Internal order numberZZGRIRG - 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 customerenhancement per Ledger in totals table.If further fields are required, please contact SAPs 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 enhancementper ledger in totals table.


30/30

SAP AG 2004 / 30

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission 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 othersoftware vendors.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks ofMicrosoft 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 andInformix 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 otherCitrix 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 hereinas well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves information purposes only. National product specifications may vary.

Copyright 2007 SAP AG. All Rights Reserved

05 Document Online Split

Documents

Transcript of 05 Document Online Split