SAP Tables for Technical Consultants & also for Function Consultants !!!

Tables on below topics :

Authorisation, objects, Batch input map's, Batch jobs,Correction & transport, Countries, Currency, Data elements, Development classes, Domains, Dynpro areas, Filenames, Function modules, Function groups, Icons, Logical databases, Matchcodes, Messages, Programs, Repository objects, Purchase Requisition, SAPscript, Spool, Status (menu), Switch objects, Tables and views, Texts, Transactions, User parameters, Variants, Accounting, Accounting documents, Bill Of Material, Classification, Classification characteristics, Configurator, Cost elements, centers, activities, Customer,Equipment, Equipment status, Function location, Customising tables, General ledger accounts, Goods movement, Customising, Inventory document, Maintenance Order, Material, Material document, Notifications, Orders,Personel, Production resource tools, Customising tables, Project, Purchase Requisition, Purchasing document, Purchasing info record, Reservation, Sales Document, Sales requirements, Storage locations and stocks, Tasklist, Transfer requirement, User data, Vendor master, WM transfer, Other tables, Useful Transactions, Function modules, Standard data transfer, Helpful reports.

Click on SAP Tables for the document.

Guidelines for LSMW Data Transfer for PM, MM, and SD Modules

This document briefs about general guidelines during master data transfer via LSMW tool in PM, MM and SD modules during implementation stage. Mostly suitable for consultants who are rigorously uploads data through this tool. This will help as a handy dictionary to refer in case any kind of error occurs while data uploading in LSMW.

Click here for the full version....LSMW Data Transfer

SAP Technical Upgrade – Tips and Tricks

Overview

This article describes SAP upgrade projects: What steps to follow in an upgrade, what points to be taken care of, what are various prerequisites, etc. The SAP technical upgrade scores for a short duration project ? 20 days to around 3 months duration. In technical upgrades, we aim to get the same or better SAP functionalities in the new system (SAP ECC 6.0) as in the old system (SAP 4.6).

Click here for the full version.....Technical Upgrade

SAP - FI AR : Configuration of Dunning - Customer / Vendor

SAP Dunning, which is mainly used in processing of collecting the customer payments.

Sometimes your business partners may fall behind on payments. You can send them a payment reminder or a dunning notice to remind them of their outstanding debts. The R/3 System allows you to dun business partners automatically. The system duns the open items from business partner accounts in which the overdue items create a debit balance.

The dunning program selects the overdue open items, determines the dunning level of the account in question, and creates a dunning notice. It then saves the dunning data created for the items and accounts affected.

You can use the dunning program to dun both customers and vendors. It may be necessary to dun a vendor if he or she has a debit balance as a result of a credit memo. If a customer is also a vendor, you can offset the account balances against one another.

Click on Dunning for downloading the "Configuration of Dunning - Customer / Vendor"

How to Configure Reconciliation Account Determination

The configuration of reconciliation account determination is similar to revenue account determination.

In some cases, a company will want to separately identify customer receivables. A good example is when a customer pre-purchases a credit which it plans to use in the future against specific types of purchases, e.g., prepaid training credit which the customer gets when they purchase a large piece of machinery. In the accounts receivables, a credit will have to be shown, and when the customer purchases a training course, the cost is deducted from the credit, not billed to the customer.

This example shows how to configure reconciliation account determination for invoicing to make the cost and credit go to a separate account, and how to configure a special G/L indicator to allow manual adjustments of this account in FI-AR module.

Click on "Reconciliation account" to download the configuration.

How to enable the cache memory in SAP R/3 ?

Hi VVR,

Can you tell me how to enable the cache memory in SAP R/3? In Whole landscape, for some cache is working and for some it is not.

Please let me know the setting I can enable the cache memory.

I am facing a lot of problems like noting down all the documents and field entries i have typed earlier to test.

Good to see the site for more configurations i dont know and good portal to develop the SAP knowledge esp. in configuration.

Thanks & Regards,

Muthuvel Rajan S

Goto the SAP GUI Help :

In that you can see "Adjusting the Local Layout". If you click on that you will get more items in that select the "Local Data Settings". There you can see the options about the History. If it is "Off" you will see blank space with some text in there. In your case may be it is "off". Check with the other systems (Developemnt/Sand box) may be you can see the details. This is normally controlled by the BASIS people.

SAP BAI, BAI2 flat file format?

This file is used for SAP financial purposes and this does interact mainly with the Banks. Banks have different format like BAI, BAI2 etc. BAI and BAI2 formats differ in their level of information detail. BAI does not separate out the incoming check line items by invoice subtotal reference. Conversely, BAI2 splits the check total into separate invoice references and associated payment amounts. As a result, your hit rate percentage of payment-invoice matching from each transmission is likely to be higher when using BAI2 rather than BAI formats.

Usually how we approach (when we receive the file) is we will read the legacy file with file adapter and then will convert into the BAI file format and drop the converted file on a shared drive. There are standard programs in SAP which picks this file and loads the data in sap. If your client has different structure then the ABAPer may need to change the program accordingly.

The Bai file format you can take a look here:

DOCUMENTATION ON THE FORMAT

Also please look into this help:

Note 86952 - Electronic bank statemt:BAI format (you can see the standard programs here)

NOTES ON BANK STATEMENT

The bottom line is the standard program in SAP expects this format and using PI will make this file from your legacy file

Differences between SAP EC-CS and BCS

ECCS is R3 based consolidation system while SEM BCS is on top of BI or BW
server. There are following differences in ECCS and BCS.

BCS, integrated into SAP's Business Intelligence (BI) system, is a component of Strategic Enterprise Management (SEM)
Integration of BCS into Business Intelligence, not SAP R3, requires data to be transferred from FI R3 to the FI cube in BI
Data is consolidated in Cube thus it improves performance
The inclusion of BCS into SAP's BI allows a tight integration between Consolidation Processing and Consolidation Reporting
BCS BI Reporting provide a great deal of flexibility, allowing the user to select & analyze data to meet their specific business needs!
Can work with two conso units in one Data Set. Cost accounting values can be stored and can be used for reporting purpose.
BCS includes the following new tasks that were not included in ECCS:

Use of one monitor, including both Data and Consolidation tasks
Period Initialization
FIGL Datastream
LC Trial balance
Allocation
Elimination – IC Operating Lease

What is this darn Internal Order…, many guys keep asking?

Let me give you an example which will remove this doubt forever.

Lets say in an organization there are various events such as trade fairs, training seminars, which occur during the year. Now lets assume for a second that these Trade fairs are organized by the Marketing cost center of the organization. Therefore in this case marketing cost center is responsible for all the trade fairs costs. All these trade fairs costs are posted to the marketing cost centers. Now if the management wants an analysis of the cost incurred for each of the trade fair organized by the marketing cost center how would the marketing manager get this piece of information across to them?

Now this is where Internal Order steps in .If you go through all cost center reports this information is not readily available since all the costs are posted to the cost center.

SAP, therefore provides the facility of using internal orders which comes in real handy in such situations. In the above scenario the controlling department would then need to create an internal order for each of the trade fair organized. The cost incurred for each of the trade fair will be posted to the internal orders during the month. At the month end, these costs which are collected in the internal order will be settled from these orders to the marketing cost center. Thus the controlling person is now in a position to analyze the cost for each of the trade fair separately.

Click on the below Config on Internal Order for FREE CONFIGURATION NOTES ON INTERNAL ORDER.

Config on Internal Order

SAP FICO Reports : Most Used & Most Important

Report Name	Transaction Code	Purpose
General Ledger:
Recurring Entry Documents	S_ALR_87012346	You are able to determine which documents: · are carried out in a particular time period · are not carried out · are carried out during the next run of the recurring entry program
G/L Account Statements	S_ALR_87012332	You use this Report to create Statements for Customers / Vendors / G/L Accounts. The primary difference between this report and other item lists for the entry view (line item lists for customers, vendors, and G/L accounts) is that it can be used to produce item lists for G/L accounts without line item display in the entry view.
Financial Statement	S_ALR_87012284	You use this report to create the balance sheet and profit and loss statements for a user-defined reporting period within a fiscal year with absolute and relative comparisons for a comparison period.
Financial Statement: Actual/Actual Comparison	S_PL0_86000028	You use this report to compare actual data within a certain period to reference data from another period.
Compact Document Journal	S_ALR_87012289	You use this report to display the most important data from document headers and items in table form for the selected documents. The list can be used as a journal and for reconciliation with the lists of account balances (accounting reconciliation).
Line Item Journal	S_ALR_87012291	You use this report to create an overview of the selected posting documents.
Advance Return for Tax on Sales/Purchases	S_ALR_87012357	You use this report to create the advance return for tax on sales/purchases. If required, you can also create a batch input session for automatic transfer posting of tax payable or fill out the tax return.
Chart of Accounts	S_ALR_87012326	You use this report to display G/L account master data that is not specific to the company code and print out G/L account lists.

Fixed Assets:
…by cost center	S_ALR_87011979	You use this report to create a fixed asset report by cost center.
…by asset class	S_ALR_87011981	You use this report to create a fixed asset report by asset class.
Asset Balances	S_ALR_87011994	You use this report to create an Asset Balance and display values of fixed assets.
Asset Transactions	S_ALR_87012048	You use this report to display asset transactions. For each document, the report shows: · the change to the acquisition and production costs · the change to the value adjustments · the ordinary and special depreciation planned for this transaction
Asset Acquisitions	S_ALR_87012050	You use this report to display asset acquisitions.The following is displayed for each document: · Acquired APC · Acquired quantity · Planned ordinary and special depreciation for the acquisition
Asset Retirements	S_ALR_87012052	You use this report to display asset retirements.Each document shows the · Retired acquisition and production costs · Retired quantity · Retired proportional depreciation · Earned revenue · Gain/loss · Possible retirement costs

Cost Element Accounting:
Controlling Documents: Actual Costs	KSB5	You use this report to display actual cost documents. The program creates a Document with all actual Costs as required.
Internal Orders: Master Data Report	KOK5	You use this report to display Internal Order Documents.

Cost Center Accounting:
Cost Centers: Actual/Plan/Variance	S_ALR_87013611	You can use the Report/Report-Interface to access the following reports: · Cost Centers: Actual Line Items · Cost Centers: Planning Overview · Cost Centers: Plan Line Items · CCtrs: Period Breakdown Actual/Plan · Activity Types: Period Breakdown · Stat. Key Figs: Period Breakdown · Cost Centers: Breakdown by Partner · Cost Centers: Breakdown by B.Trans. · Area: Actual/Plan 2 Currencies · Display planning long texts
Range: Cost Centers	S_ALR_87013612	You can use the Report/Report-Interface to access the following reports: · Cost Centers: Planning Overview · Cost Centers: Actual/Plan/Variance · Area: Cost Elements · Cost Centers: Breakdown by Partner · Cost Centers: Breakdown by B.Trans
Range: Cost Elements	S_ALR_87013613	You can use the Report/Report-Interface to access the following reports: · Cost Centers: Actual Line Items · Cost Centers: Plan Line Items · CCtrs: Period Breakdown Actual/Plan · Cost Centers: Planning Overview · Cost Centers: Breakdown by Partner
Cost Centers: Planning Overview	KSBL	You use this report to create a planning overview for all cost centers.
Range: Actual/Budget/Commitments	S_ALR_87013648	You use this report to create an overview for each cost center of the · Actual costs · Commitments · Allotted costs · Budget
Cost Centers: Activity Prices	KSBT	You use this report to create a List of Activity Prices by Cost Centers or Cost Center Groups

Internal Orders:
Orders: Actual Line Items	KOB1	You use this program to create a report for Actual Line Items for Orders.
Orders: Commitment Line Items	KOB2	The program creates a Report for Commitment Cost Line Items for Orders as required.
List: Orders	S_ALR_87012995	You use this program to create a List of all Orders by Controlling Area for a Plan/Actual Comparison.
Orders: Actual/Plan/Variance	S_ALR_87012993	You use this program to create an overview of the actual and plan data on internal orders in the reporting time frame for each Cost element, Cost element group and Statistical key figure.
Order: Planning Overview	KABL	You use this program to create a planning overview by Order.
List_ Budget/Actual/Commitments	S_ALR_87013019	You use this program to create a List concerning Budget/Actual/Commitments for Internal Orders.

Profitability Analysis:
Execute Report	KE30	You use this program to create several profitability reports. · Execute Drilldown Report Plan/Actual Sales Detail List · Execute Drilldown Report Plan/Actual Sales Mat. Costs · Execute Drilldown Report Plan/Actual Sales OH Costs · Execute Drilldown Report Reconciliation

Information System:
Costs/Revenues/Expenditures/Receipts	S_ALR_87013531	You use this program to create a Cost/Revenues/Expenditures/Receipts report for projects.
Actual/Costs/Revenues	CJI3	You use this program to display Project Actual Cost Line Items.

Product Costing
Multilevel BOM: Value / Amount / Status	CK86_99	You use this transaction to create a List concerning costed BOMs.
Cost Component	CK80_99	You use this transaction to create a List concerning Cost Components of the Cost Estimate.
Itemization	CK84_99	You use this transaction to create a List concerning Itemization of the Cost Estimate.
Cost Elements	KKBC_MAT	You use this transaction to create a List concerning Cost Elements of the Cost Estimate.
Analyzing/Comparing Material Cost Estimates	S_P99_41000111	You use this transaction to create a List to compare Material Cost Estimate.
Analyzing Product Cost Collector	KKBC_PKO	You use this transaction to create a List to analyze Product Orders.
Analyzing Product Order	KKBC_HOE	You use this transaction to create a List to analyze Product Orders.

Why do we need to DEBUG : BREAK POINT : WATCH POINT

DEBUG

We write programs to achieve certain functionality and like other actions, we make mistakes while writing the code. If they are not trapped at the right time, problem becomes bigger, and bigger and bigger.

BREAK POINT

The BREAK POINT is a debugging aid. When we run a program normally, it is interrupted at the statement, and the system automatically starts the debugger, allowing you to display the contents of any fields in the program and check how the program continues. If the program is running in the background or in an update task, the system generates a system log message.

SAP - FI AR BK: Electronic Bank Reconciliation

The EBS is used to automatically assign incoming and outgoing payments to house bank accounts when they relate to items already posted in the system to customer/vendor/clearing accounts and, where appropriate, the clearing of them.
Each uploaded electronic bank statement will be assigned with a unique no. in SAP and can be printed retrospectively.

Steps in Electronic Bank Reconciliation:

1. Electronic Bank Statement file (in SWIFT MT940 format) is extracted from BANK
2. Data (SWIFT MT940 for BANK) is imported into a temporary dataset in SAP
3. Batch input sessions are generated (per bank statement: one session for G/L Accounting and one for Subledgers- AR/ AP). Bank accounting and subledger accounting batch session can be executed separately or jointly
4. Posting rules and account determination are defined in TR-CM customization
5. As an electronic bank statement is being imported, the system identifies the transactions in it and determines how they are posted.
6. The note-to-payee fields in the electronic bank statement contain various information relevant to open item clearing. Note to payee fields can be interpreted by document number or reference document number for the clearing transaction (example: standard algorithm). If the algorithms we deliver are not sufficient, it is possible to program a user exit tailored to your business (e.g. change the posting rule; influence account determination by means of account modification).
7. Post-processing for posting proposals(line items) which cannot be cleared

Note:
Electronic Bank Statement format SWIFT MT940 is compactable with SAP TR-CM. Standard algorithm for clearing documents is available in the predefined form in SAP. Customisation, as stated in point 6 above, will be needed to cope with AAA specific requirements on Bank Reconciliation. The review task will be performed on the Detail Design Phase, detail of which will be incorporated into the respective customisation functional specifications.

Reasons for adopting Costing-Based COPA

SAP CO-PA was intended for use with a cost-based approach that stores different currencies, quantities and values from SD, FI, MM and PP as PA value fields to manipulate for a variety of reports. This is the recommended path as it allows more variability in collecting data for PA reports (related to details of cost components for variances, etc.)

In case of High-Tech industry companies using SAP CO-PA, the majority of them utilitise Costing-Based COPA to enable more detail level of Cost of Sales analysis.

Costing-Based CO-PA sometimes does not match with legal book values. Such discrepancies can be explained mainly by 3 big factors:

Timing differences: When the Delivery step is performed in SAP SD, but Billing is not, nothing gets booked into COPA, but COGS is already booked in the FI legal book. During the SD Prototype, since Billing Due List (a batch program) will be executed each day, which perform the billing step for Sales Order with Delivery but not yet billed, the COGS and Revenue will be in syn in both FI and COPA for AAA.

Accruals: It is possible that accrued values are posted in COPA (might be triggered by program in Sales Order conditions), without any posting in FI legal book

Rounding differences from Foreign Currency Translations

Note:
Management using/ viewing these COPA reports need to be acknowledged the fact that due to the intended design of the Costing-Base COPA, values not necessarily always tie to FI legal book. Discrepancies to FI might occur, but explainable.s

SAP- CO : Some of the Product Cost Approaches

§ Finished Goods Inventory in Production Plant AAAA

Valuation at moving average price per batch (FIFO batch valuation)
A new batch number will be generated for each production order (work order) producing the finished product
Each batch will have a unique material cost
The material cost of a batch is calculated from semi-finished goods and raw materials that are directly constituting to the finished product according to the BOM

§ Semi-finished Goods Inventory in Production Plant AAAA

Valuation at standard price updated from standard cost estimates
All inventory of each semi-finished product will be valuated the same (at the defined standard cost)
The standard cost can be updated either: 1) manually, or 2) automatically from the cost roll-up (can be using weighted average) of the lower levels of the BOM and can be selectively updated only for certain semi-finished products.
Re-valuation of existing inventories for semi-finished product will happen whenever the standard cost is updated. The gain or loss will post to the P/L accounts

§ Raw Materials Inventory in Production Plant AAAA

Raw materials will be valuated for each batch of the receipts of purchase using the purchase order price.
The batches of raw materials will be issued to production orders at FIFO.
No re-valuation of raw materials will be required.

§ All Inventory in Branches

Inventory will be valuated for each batch of the receipts of STO using the STO price (transfer prices plus the landed costs).
The batches of goods will be delivered to customers at FIFO.
No re-valuation of inventory will happen.

SAP - CO : Period End Closing Process

Period end closing process is a monthly activity in CO and it refers to the following areas:

Execution of allocation cycles to apportion cost from common or shared cost centers to final cost centers
Generation of monthly reports

The following tasks have to be executed at every period end closing:

Ensure postings are completed from sub modules and sub modules have closed
Execute all the active allocation cycles
Check key figures to sub modules (i.e. total Cost Center Accounting figures to agree to total G/L expense accounts etc)
Generate monthly reports
Lock current posting period for controlling

SAP - CO : Statistical Key Figures

Statistical key figures serve as a basis for internal allocations and as references in the key figure analysis framework. Statistical key figures can be used for internal cost allocations, and can be defined as either fixed values or totals values. There are two major types of allocation in SAP:

Distribution
Assessment

Distribution is the process of cost allocation used to allocate primary costs of cost center using the original primary cost elements. In this method, the costs being allocated will be retained into the original cost elements. On the other hand allocation by assessment could be applied to both primary and secondary costs using a secondary assessment cost element which is different from the original cost elements. In this case, the costs being allocated will be posted to a secondary assessment cost element.

Statistical key figures are defined for assessment purpose:

The statistical key figures used are:

Employees
Man-hours
Floor space
Quantity by Finish Goods

Points for ECC 6.0 FI Certification - NEW GL

1. Possibilities with New GL:

· Legal and Management Reporting

· Extensibility (extended data structure by default - with customer fields)

· Account Balancing with Any characteristics

· Simple Mapping of Parallel Valuation (possible to manage multiple "books" (->ledgers)

· Reduction of TCO

· Transparency and Uniformity

· Segment Reporting (with online document split in real time)

· Real-Time Integration CO=>FI (time consuming recon activities omitted)

2. Above possibilities not available in Classic GL

3. Do I have to use the new GL

· Optional: for existing SAP customers – during upgrade Classic GL (GLT0) remains active at first

· For initial installations New GL Ledger is active by default in mySAP ERP

4. Activating the NGL Accounting:

· Automatic in initial installation

· It is at client level – applicable across all CC'

· TCODE: FAGL_ACTIVATION

· Result in system-wide changes to the easy access menu and screen and customizing paths

· Conventional Financial Accounting paths will initially remain available – can hide with program RFAGL_SWAP_IMG_OLD

5. Ledger Definition:

· SAP provides leading ledger "0L" and summary table – FAGLFLEXT with the standard system

· Leading ledger gets many of its control parameters from the CC – automatically comes to LL

· LL manages additional local currencies & FYV & PPV which are assigned to CC

· There is exactly only one leading ledger

· Only the values from LL are posted on to CO in standard system

· Addition to LL, you can define other non-leading ledger

· You can assign different alternate currencies &/ FYV, PPV to NLL

6. Summary / Total Table:

· Every reporting is from this table only

· It has extended database

· New GL Total Table (FAGLFLEXT) updates more char/data than the Classic GL Total Table (GLT0)

· New standard fields included:

i. CC

ii. PC

iii. Segment

· It can extended with additional fields – both predefine SAP fields and entirely new fields

· To add this – have to add to account assignment block

· Extending the block will lock out all other transactions

7. Scenarios – Definition and Assignment:

· Scenario defines which fields are updated in the ledgers (in GL view) during a posting (from other application component)

· Scenario provided by SAP:

i. Cost center update - FIN_CCA - sender & receiver CC

ii. Preparation for consolidation - FIN_CONS - consolidation transaction type & trading partner

iii. Business area - FIN_GSBER - sender & receiver BA

iv. Profit center update - FIN_PCA - PC & Partner PC

v. Segmentation - FIN_SEGM - segment, partner segment & PC fields

vi. COS accounting - FIN_UKV - sender & receiver FA

· Scenarios should be associated with the types of Ledgers (LL, NLL (N1), NLL (N2))

· Scenarios available in customizing - provided scenarios assigned to ledgers in customizing

· A ledger (LL) can be assigned one or more scenarios, or even all six at once

· Can not define your own scenarios

· Scenarios do not have to be assigned to non-leading ledgers

· You do not need one ledger for each scenario

· Multiple/non-leading ledgers are useful for modeling different accounting rules

· Values recorded in non-leading ledgers not record in CO module

· If you don't assign scenarios to a ledger (or to multiple ledgers) - segment B/S will not be possible

8. Entry View and GL View:

· When NGL active Financial accounting document always has two views

· You can also see the document in NLL in GL view

· Entry: view of how a document also appears in the sub ledger views / sub ledgers (AR/AP/AA/Taxes)

· General: view of how a document only appears in GL - only for GL and not for sub ledgers

9. S – A & F' I:

· In general, nothing has changed regarding the entry of the documents

· Dependencies have also remained:

i. Expense account is defined as primary cost element in CO and therefore requires a CO relevant account assignment during entry

ii. CO object is used to derive PC and FA

iii. Now new with ERP: A segment can now be derived from PC

10. S – A & F' II:

· If corresponding scenario not assigned – no entities are inherited to GL (neither LL / NLL)

· Effects of missing scenario will be like – if you call up B/S you can see the amount in exp account – but the same not allocated to scenarios – so segment B/S not possible

11. S – A & F' II:

· Scenario assignment is not capable of creating a "zero balance position" for any given entity – because all the terms not passed to all the line items so segment B/S not possible – this function can be possible using the document splitting with active inheritance

12. Use of segment entity:

· Segment field is one of the standard account assignment objects available in mySAP ERP to run analyses for "objects" below CC Level.

· Objective is to give a detail look at the various business activities- segment reporting - IAS14

· BA / PC can be used as alternatives – segment is in addition to BA & PC

13. Deriving a segment:

· Segment assigned in the PC Master record

· Segment posted automatically when PC posted

· There is no "dummy segment posting"

· If the PC does not have a segment, there is no segment account assignment either

· Default is derive segment from profit center – using BAdI , customer can develop their own derivation solutions

· BAdI : FAGL_DERIVE_SEGMENT

14. To post, analyze, and display document segments in NGL you have to perform below activities:

· Definition of the segment

· Derivation of the segment - from PC

· Maintain the FSV & FSG of corresponding FI doc - make 'segment' field to 'optional entry'

· Maintain the field status of the posting key - " "

· Display the segment field using layout in the document display

· Define the scenarios : scenarios has to be defined for LL - if not segment will only be visible in entry view

15. Document Splitting:

· Motivation: to create segment financial statements

· Assumption:

i. Operative process (of document entry) must not be disturbed (changed) by the online split

ii. When a vendor line item list is called, of course, there should still be only one open item for the invoice.

· Splitting doesn't happen in sub ledgers – happens only in GL account level

16. Steps involved in DS:

· Passive split

· Active (rule-based) split

· Clearing line/zero balance formation by document

17. Passive split:

· During clearing the account assignments of the items to clear are inherited to clearing line items

· Cannot be customized

18. Active split: (rule – based)

· System splits document due to splitting rules (provided or custom define)

· Can be configured

19. Clearing lines / zero balance formation by document:

· System creates new clearing line automatically to achieve a split

· Can control this process with the "zero balance flag"

20. Splitting procedure:

· Is the total of all splitting rules of all business transactions.

· Defines how and under which circumstances split will be performed

· Means, each procedure defines how each item category will be handled in the individual business transactions

i. Business transaction: is a general breakdown of actual business process that SAP provides and that is assigned a wide variety of item categories

ii. Business transaction variant: is a specific version of the predefined business transaction provided by SAP and (technical) modeling of a real business process for document splitting.

iii. Item category: is (technical) map of the posted line items – describes the items that appear within a document – derived from among other things, GL account categories – semantic description of document split.

iv. An individual splitting rule defines which item categories can be split and at the same time defines which foundation can be used

· Every GL has to be categorized into one of the item category

· GL account is associated with the item category

21. Splitting rule TCODE: GSP_RD

22. Splitting rules are not for CC – it is defined at client level

23. Document splitting characteristics:

· After defining how you want to split – now define which characteristics to use for splitting in GL accounting

· System proposes logical document splitting characteristics based on the assigned scenarios

· If you elect to use additional splitting chars, you should manage these chars in at least one Ledger

· Activate:

i. Zero balance flag – if you plan to use char to create FS. Balance of the involved entities is then always 0 for every posting, ensuring "entity balancing"

ii. Mandatory flag – has the two meanings:

1. It is an extension of the field status for accounts in which the char can not be entered during doc entry and for accounts that cannot be controlled through the field status.

2. It is a check as to whether a business process-equivalent business transaction variant was selected (which determines whether a splitting rule can be found)

24. Activating document splitting and inheritance:

· Splitting is first activated client-wide in customizing

· In a further step you can activate/deactivate splitting in each CC

· Inheritance: means when you create customer invoice from a revenue line – entities (such as BA / segment) are projected to the customer and tax lines in the GL View

· Default account assignment can be used to replace all account assignments that could not be derived from the posting with a constant "value"

25. Splitting procedure 0000000012 is the defaulted procedure provided by SAP

26. There is no reason why you shouldn't activate inheritance when splitting is active.

· If you didn't use inheritance, you'd have to define "rules" for the business processes to ensure that the account assignment are inherited – to achieve a zero balance in order to post the item

· Activation of inheritance is a first practical step to enable documents with active splitting, without any other customizing activities.

· Inheritance is performed online and at the line item level.