Table of Contents

1. FI and MM integration (MM modules means procure to pay process)........1

2. FI and SD integration (MM modules means procure to pay process)..........3
3. Closing And Reporting activities.........................................................................................4
4. Cut Over Strategy.........................................................................................................................8
5. New General Ledger Accounting...............................................................................................10
6. Automatic Payment Programme.......................................................................................15
7. House Bannks...............................................................................................................................16
 From the initial page of the SAP Service Marketplace, you access the IBU
information as
follows:
www.service.sap.com => Choose the portal Education, Consulting, Solution Areas and more
=>
Choose the Solution Details tab page.
In the hierarchy tree displayed on the top left, navigate as follows:
Business Solutions and Applications -> mySAP Business Suite -> mySAP ERP -> mySAP ERP
Financials -> mySAP ERP Financials in Detail -> Financial Accounting -> Financial
Accounting in
Detail -> General Ledger -> Media Library -> PDF file New General Ledger Accounting and
SAP Industry Solutions

In the Media Library, you can also find other sources of interesting information
relating to New
General Ledger Accounting, as well as some recorded system demos that you can view
(using the
SAP Tutor Player).
1.
2. FI and MM integration (MM MODULES MEANS PROCURE TO PAY PROCESS)
Please follow the following steps for FI and MM integration:

Integration of SAP FI with MM is done with T-code: OBYC.

 
In MM you purchase goods and to which you pay, the purchasing process has the following
steps:
 
Step1: First you send a Purchase Order to the Vendor.
Here there won't be any accounting entry as this is simply like telling the Vendor what
goods you want, its quantity and the date of delivery etc.,
 
Step 2: You will receive the Goods to the Purchase Order (MIGO entry).
Path: Sap easy access → Logistics → Material managements → Inventory managements →
Goods movements → Goods receipts → For purchase order → Purchase order number
known

When you receive Goods you CAN NOT make the following entry
Inventory A/c Dr
To Vendor A/c
Because, some of the goods you have received may be damaged or may not be up to the
mark or for any other reason goods may reject, so before posting it to Vendor A/c we keep
it in separate place till we verify the goods. And the actual entry will be:
 
Inventory A/c Dr (Transaction Key BSX @ OBYC)
To GR/IR A/c (Transaction Key WRX @ OBYC)
 
Here the goods received is Debited to inventory and Credited to a temporary A/c i.e., GR/IR
a/c
 
Step 3: You will post an Invoice to the Goods receive (MIRO entry).
Here you will post the invoice after you are satisfied with the goods received, the entry will
be
Path: Sap easy access → Logistics → Material managements → Logistics invoice verification
→ Documents entry → Enter invoice (MIRO)

GR/IR A/c Dr
To Vendor A/c

Step 4: And make Payment to Vendor.

Vendor A/c Dr
To Bank Clearing A/c
 
Step 5: At the time of Bank Statement upload:
Bank Clearing A/c Dr
   To Bank Main A/c

Confidential Page 1 of 263

Note: Valuation class and Movement type is used for the G/L determination.

Valuation class: Valuation classes is nothing but sub-classify of the material

Valuation class is used to group together several materials with their same
attributes, so that we can carry the same account determination for various materials.
Every material has a valuation class; many materials can contain same valuation class. As
we know the valuation class is link with material type via account category reference.

The valuation class will be for Raw material, Semi-finished, finished goods. We can
differentiate valuation class as per our business requirement.

Valuation Area

Valuation area is nothing but Plant

Movement type: Movement type is used for all types of material movement. Suppose if
you receive a material from a vendor, a movement is happens for the movement. If we
transfer a material from one location to another, a movement type is happens for the
movement. It means, whenever we do an off-setting entry, a movement type will be
created for that. For various movement types SAP defines a G/L account for the material
movement.

Standard movement types

101 – Material receive against the purchase order / production

102 – Reverse of 101 or Purchase order
201 – Issue to cost centre
202 – Reversal of 201
261 – Issue to orders
262 – Reversal of 261
521 – Material received without production order
522 – Reversal of 521
561 – When posting opening stock
562 – Reversal of 561
601 – When goods delivered
602 – Reversal of 601

Transaction keys

These transaction keys are used to determine accounts or posting key for line items which
are created automatically by the screen. These transaction keys are defined in this system
and cannot be changed by the user.

BSX – Inventory postings (every inventory accounts we assign BSX key)

WRX – For GR / IR Accounts
PRD – Price difference accounts / production order differences
GBB – Offsetting entries for inventory posting

Confidential Page 2 of 263

Material Master > Valuation Class > Movement Type > Transaction Event Key

3. FI and SD integration (MM MODULES MEANS PROCURE TO PAY PROCESS)

Whenever we sale a finish material to customer, then the customer have to pay for that. We
send a bill to customer. In that position all billing document which is happens to sales and
distribution module will be posted into FI module.

AS per SD module, the customer account will be picked from customer master data, which
is maintained from SD module. We just need to configure the revenue account and if there
any discount and surcharges account.

SAP provides 5 ways to determine G/L account in SD modules.

These are
1    Cust.Grp/MaterialGrp/AcctKey
2    Cust.Grp/Account Key
3    Material Grp/Acct Key
4    General
5    Acct Key

Path: IMG >Sales and Distribution >Basic Functions >Account Assignment/Costing

>Revenue Account Determination >Assign G/L Accounts or Via Transaction Code: VKOA

Accounting Entries:
1. Sales Order created.

No entry

2. PGI Done (Goods Issue)

Cost of Goods Account Dr (Configured in OBYC GBB T-Key)
To Inventory Account

3. Billing document released to accounting

Customer Account Dr
To Sales Revenue Account (ERL T-Key in Pricing Procedure)

Note: The GL account is assigned to this ERL in VKOA

4. Payment Received
Bank Account Dr
To Customer Account

Confidential Page 3 of 263

4. Closing And Reporting activities
The closing operations can be subdivided into: Day-end closing, month-end closing, and
year-end closing.

The closing operations include:

 Periodic accrual and deferral of expenditures and revenues

 Recording and valuating payables and receivables
 Creating the financial statements
 Documenting the posting data

1. Process Day-End Closing

a. Update Exchange Rates: Exchange rates for foreign currencies are updated
each day or each month.
T-code: S_BCE_68000174
Path: Accounting ® Financial Accounting ® General Ledger ® Environment ®
Current Settings ® Enter Translation Rates

b. Gaps in Document Number Assignment : Checklist to find gaps in the

document number assignment across several ledgers
T-code: S_ALR_87012342
Path: Accounting ® Financial Accounting ® General Ledger ® Information
System ® General Ledger Reports (New) ® Document ® General ® Gaps in
Document Number Assignment

c. Invoice Numbers Allocated Twice: Checklist of documents assigned more

than once.
T-code: S_ALR_87012341
Path: Accounting ® Financial Accounting ® General Ledger ® Information
System ® General Ledger Reports (New) ® Document ® General ®
S_ALR_87012341 - Invoice Numbers Allocated Twice
d. Display the compact document journal: Checklist of the most important data
from the posted documents
Use: The compact document journal displays the most important data from the
document headers and items in the form of a table for the documents selected.
The list can be used as a compact journal and for reconciliation with the account
balances (accounting reconciliation
T-code: S_ALR_87012289
Path: Accounting  Financial Accounting  General Ledger  Information
System  General Ledger Reports (New)  Document  General  Compact
Document Journal

2. Process Month-End Closing

a. Update Exchange Rates: Exchange rates for foreign currencies are updated
each day or each month.
T-code: S_BCE_68000174
Path: Accounting ® Financial Accounting ® General Ledger ® Environment ®
Current Settings ® Enter Translation Rates

Confidential Page 4 of 263

 b. Gaps in Document Number Assign-ment: Checklist to find gaps in the
document number assignment across several ledgers

T-code: S_ALR_87012342

c. Invoice Numbers Allocated Twice: Checklist of documents assigned more

than once

T-code: S_ALR_87012341

d. Open and Close Posting Periods: Close Accounts Receivable, Accounts Payable
and Asset sub-systems from posting into prior period; New accounting period is
starting.
T-code: S_ALR_87003642 (OB52)
Path: Accounting ® Financial Accounting ® General Ledger ® Environment ®
Current Settings ® Open and Close Posting Periods

e. Enter Recurring Entries: Recurring documents for the period that were entered
into system need to be processed.
T-code: FBD1
Path: Accounting ® Financial Accounting ® General Ledger ® Posting ®
Reference Documents ® Recurring Document

f. Post Recurring Entries: Recurring documents for the period that were entered
into system need to be processed.
T-code: F.14
Path: Accounting ® Financial Accounting ® General Ledger ® Periodic
Processing ® Recurring Entries ® Execute

g. Run Batch Input Session: Post the recurring documents processed in prior
step.
T-code: SM35
Path: System ® Services ® Batch Input ® Sessions

h. Automatic Clearing of GR/IR Account special process: GR/IR clearing

accounts
Use: This activity handles the automatic clearing of the GR/IR accounts. The
purchase order number and item is used to compare documents
T-code: F.13
Path: Accounting ® Financial Accounting ® General Ledger ® Periodic
Processing ® Automatic Clearing ® Without Specification of Clearing Currency

i. Analyze GR/IR Clearing Accounts: Analyze GR/IR Clearing Accounts and

Display Acquisition Tax.
Use: This activity analyzes GR/IR Clearing Accounts and Display Acquisition Tax.
The program analyzes goods receipt/invoice receipt (GR/IR) clearing accounts at
a specified key date, and generates adjustment postings if necessary. These are
needed to display the following business transactions correctly in the balance
sheet
 Goods delivered, but not invoiced

Confidential Page 5 of 263

  Goods invoiced, but not delivered
T-code: F.19
Path: Accounting ® Financial Accounting ® General Ledger ® Periodic
Processing ® Closing ® Reclassify ® GR/IR Clearing

j. Manual Clearing: If documents cannot be cleared automatically. They can be

cleared manually.
T-code: F-44
Path: Accounting  Financial Accounting  Accounts Payable  Account  Clear

k. Post Adjustment Entries: Post adjustments to current financial data, like

accruals, to better represented the current financial situation.
T-code: FB50
Path: Accounting ® Financial Accounting ® General Ledger ® Posting ® Enter
G/L Account Document

l. Foreign Currency Reva-luation: Foreign currency transactions need to be

valuated at the current exchange rate.
T-code: FAGL_FC_VAL
Path: Accounting ® Financial Accounting ® General Ledger ® Periodic
Processing ® Closing ® Valuate ® Foreign Currency Valuation (New)

m. Post Tax Payable: Finance reporting.

T-code: FB41

Path: Accounting  Financial Accounting  General Ledger  Periodic

Processing  Closing  Report  Post Tax Payable

n. Advance Return for Tax on Sales/ Purchases: Finance reporting.

T-code: S_ALR_87012357

Path: Accounting ® Financial Accounting ® General Ledger ® Reporting ® Tax

Reports ® General ® Advance Return for Tax on Sales/Purchases ® Advance
Return for Tax on Sales/Purchases

o. Display the document journal: List of the posted documents in the period

T-code: S_ALR_87012287

p. Financial Statement : Finance reporting

T-code: S_ALR_87012284 or
Path: Accounting ® Financial Accounting ® General Ledger ® Information
System ® General Ledger Reports (NEW) ® Financial Statement / Cash Flow ®
General ® Actual/Actual Comparisons ® Financial Statement

T-code: S_PL0_86000028
Path: Accounting ® Financial Accounting ® General Ledger ® Information
System ® General Ledger Reports (NEW) ® Financial Statement / Cash Flow ®

Confidential Page 6 of 263

 General ® Actual/Actual Comparisons ® Financial Statement: Actual/Actual
Comparison

3. Process year-end closing:

a. Carry Forward AP/AR Balances: Carry the A/P balances into the new fiscal
year.
T-code: F.07
Path: Accounting  Financial Accounting  Accounts Receivable or Accounts
Payable  Periodic Processing  Closing  Carry Forward  Balances

b. Carry Forward GL Balances: Balance sheet accounts have balances for the
new year and P/L account balances have been posted into retained earnings.
T-code: FAGLGVTR
Path: Accounting  Financial Accounting  General Ledger  Periodic
Processing  Closing  Carrying Forward  Balance Carry Forward (New)

c. Re-grouping Receivables/Payables:
Use: You have to carry out adjustment postings in the following cases.
 Sorted list according to remaining terms
 Vendors with a debit balance and customers with a credit balance
 Modified reconciliation accounts or partners (VBUND)
T-code: FAGLF101
Path: Accounting  Financial Accounting  Accounts Receivable (or Accounts
Payable)  Periodic Processing  Closing  Reclassify  Sorting / Reclassify
(New)

d. Balance Confirmation Receivable:

Use: You can use balance confirmations to check that receivables and payables
vis-à-vis your business partners are correct. There may be discrepancies that
have to be clarified with the business partner, or individual value adjustments
that have to be posted.
T-code: F.17
Path: Accounting  Financial Accounting  Accounts Receivable  Periodic
Processing  Closing  Check/Count  Balance Confirmation: Print

e. Balance confirmation Payable:

Use: You can use balance confirmations to check that receivables and payables
vis-à-vis your business partners are correct. There may be discrepancies that
have to be clarified with the business partner, or individual value adjustments
that have to be posted.
T-code: F.18
Path: Accounting  Financial Accounting  Accounts Payable  Periodic
Processing  Closing  Check/Count  Balance Confirmation: Print

f. Final Close and Release Financial Reporting: The company’s financial

results need to be reported.

Confidential Page 7 of 263

 Use: The report creates 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
T-code: S_ALR_87012284

g. Close Previous Accounting Period: Do not allow any more financial postings
in the previous period because the results have been released.
T-code: S_ALR_87003642 (OB52)

h. Display the Document Journal:

T-code: S_ALR_87012287
Path: Accounting  Financial Accounting  General Ledger  Information
System  General Ledger Reports (New)  Document  General  Document
Journal

5. Cut Over Strategy

The Go Live strategy comprises of the following:-
1) Cut off procedure
2) Pre- Go live checks.

What is meant by cutoff date?

SAP system is configured as per the requirement of the client. The system is ready for the
client to use. Now client’s needs to migrate data from the Old system (Legacy system) to
the new SAP system. The migration from the old system to the SAP system is known as
cutoff date.
The old system is switched off and the new SAP system is switched on. The data will be
migrated from the old system to SAP. The data will henceforth be entered in the new SAP
system. To have a smooth switch over from the Legacy system to the new SAP systems are
devised the cut off procedure.

What is meant by Pre u2013 Go live check?

It is ensuring that SAP Production system is ready to go live smoothly.
Letu2019s proceed then.
Scenario:
A Ltd. is a company implementing SAP system. The company follows a January - December
period for preparing financial accounts.
Therefore the go live data decided for A Ltd is 2nd January 2006. The Trial balance
will be uploaded with date as on 31st December 2005. The Trial balance will consist only of
balance sheet items since all the expense items are already transferred to the retained
earnings account in the old system.

The activities are divided as follows:-

1) Pre Go live activities
A Ltd will upload the GL codes, cost elements in the production system on 1 st December
2005.

Confidential Page 8 of 263

A Ltd will complete upload of all the material masters with all the views in the production
system by 2nd December 2005.
All Bill of Material, Routings will be uploaded in the production system by 4th December
2005.
The material masters for raw and packing material will be uploaded with the moving
average prices on 4th December 2005.
The cost center Plan will be uploaded, allocation cycles and activity price calculation will be
done by 6th December 2005.
Product cost calculation will be conducted from 7th Dec 2005 to 20th December 2005 to get
the correct cost calculation from system.
All other masters will be uploaded into the production system from 5th December
2005 and completed by 18th December 2005

2) Cut off activities

The company closes it sales on 26th December 2005.
The company stops all its stock movement on 26th December 2005 up to 1st January 2006.
All open purchase orders will be uploaded on 28th December 2005.
The provision for stock received and invoice not received will be accounted in a separate GL
code (different than the GR/IR)
The stocks will be finalized by 29th December 2005.
The company closes its old (legacy) system on 30th December 2005.
The stocks will be uploaded on 31st December 2005 and 1st Jan 2006.
The standard cost estimate will be marked and released on 2nd January 2006.
The system is available for data entry and operation to the users from 2nd January 2006.
Accounts Receivable open items will be uploaded from 1st January 2006 to 3 rd January
2006.
Thus Accounts Receivable is available from 4th January 2006 to account for customer
incoming payment.
Accounts Payable open items will be uploaded from 3rd January 2006 to 4th January 2006.
Accounts Payable is available for payment from 5th January 2006.
Fixed assets are uploaded on 5th January 2006.
The Remaining GL Balances are uploaded on 7th January 2006.
Thus entire data take over activities are to be completed by 7th January 2006

We will divide the activities as follows:-

A) Pre u2013 Go Live activities
B) Pre u2013 Go Live checks
C) Upload transaction data into the system

A) Pre u2013 Go Live activities

1. Master data Load into Production system
Ensure all the master data is loaded into the production system.
We will broadly cover the master data which needs to be loaded and the module
responsible.
Material Master u2013 Basic responsibility MM: All the respective views of the material
masters the other modules responsible. Ensure that all the required views are uploaded
GL codes - FI

Confidential Page 9 of 263

Customer Master - FI (accounting view) and SD (sales view)
Vendor Master - FI (accounting view) and MM (purchasing view)
Cost elements - CO
Secondary cost elements - CO
Profit centers - CO
Cost center - CO
Activity type u2013 CO
Bill of Material u2013 PP
Work Center/ Resource u2013 PP
Routing / Master Recipe u2013 PP
Purchasing Info Record u2013 MM
Service Master - MM
Bank Master - FI
Quality Info Record u2013 QM
Quality Inspection plan
2. Upload Cost center plan
Cost center plan must be updated through transaction code KP06 or using excel upload.
3. Execute the allocation cycles within cost center accounting
The plan allocation cycles (distribution, assessment) must be executed within the cost
center accounting module. This will allocate the costs from the service cost center to the
receiver cost center.
4. Update planned activity
After executing of the plan allocation cycles, the production cost centers are now ready with
the planned costs.
You can now calculate the activity prices through the system or manually update the
planned prices by calculating it outside.
The planned activity must be updated through transaction code KP26.
5. Calculate Activity prices Calculate the activity prices using transaction code KSPI.

6. NEW GENERAL LEDGER ACCOUNTING

Introduction:
Possibilities with New General Ledger Accounting
 Real-Time Integration CO => FI
 Segment Reporting
 Transparency and Consistency
 Accelerated Period-End Closing
 Simple Representation of Parallel Accounting
 Financial Reporting Using Any Characteristics (document splitting)
 Standard Enhancement and Extensibility (with custom fields)
 Legal and Management Reporting

New General Ledger Accounting in mySAP ERP has the following advantages
compared to classic General Ledger Accounting (such as in R/3 Enterprise):

 New General Ledger Accounting has an extended data structure in the standard
delivery. Customer fields can also be added to the general ledger.

Confidential Page 10 of 263

  With (real-time) document splitting, balance sheets can be created for entities, such
as "Segment".
 You can run a real-time reconciliation of Management Accounting (CO) and Financial
Accounting (FI) - there is the real-time integration with Controlling. This renders
time-consuming reconciliation tasks obsolete.
 New General Ledger Accounting makes it possible to manage multiple ledgers within
General Ledger Accounting. This is one of the possible ways of portraying parallel
accounting in the SAP system.

“SAP Note 756146 also provides an overview of the benefits of New General Ledger
Accounting”

New General Ledger Accounting can be explained briefly as follows: New General Ledger
Accounting contains functions that combine classic General Ledger Accounting with the
Special Purpose Ledger component

Important: Despite all the new features, the "interfaces" for entering the data and making
the postings are virtually identical to the interfaces in the previous release.

Crucial question: Do companies have to use New General Ledger Accounting?

 It will be optional for existing customers. You will not be obliged to activate New
General Ledger Accounting. During a release upgrade (to mySAP ERP), classic
General Ledger Accounting (using totals table GLT0) remains active at first.
Of course, New General Ledger Accounting has many advantages!

 For new installations, New General Ledger Accounting is active by default in mySAP
ERP.

 If existing customers want to use New General Ledger Accounting, they first need to
activate it using a Customizing transaction (=> FAGL_ACTIVATION).
Caution: This transaction is performed at the start of the course to enable you to
explore the new functions. In practice, executing this transaction (for existing
customers) is one of the last activities performed during the migration project
leading up to the implementation of New General Ledger Accounting.

Note: Accounting, you can run program RFAGL_SWAP_IMG_OLD to hide the classic
Financial Accounting paths.

Ledger Definition:
SAP provides the leading ledger 0L and totals table FAGLFLEXT with the standard system.
The leading ledger gets many of its "control parameters" (as before) from the company
code.
 The leading ledger manages the (additional) local currency (currencies) that is (are)
assigned to the company code.
 The leading ledger uses the fiscal year variant that is assigned to the company code.
 The leading ledger uses the posting period variant that is assigned to the company
code.

Special features of the leading ledger:

 There is exactly one leading ledger!
 Only the values from the leading ledger are posted to CO in the standard system

Confidential Page 11 of 263

  In addition to the leading ledger, you can also define other, non-leading ledgers (=>
also see the unit Parallel Accounting).
 The non-leading ledgers can then be assigned currencies and/or fiscal year variants
that differ from the leading ledger.

Scenarios – Definition and Assignment

What is a scenario definition?

A scenario defines which fields are updated in the ledgers (in the general ledger
view) during a posting (from other application components).

Scenarios provided by SAP:

 Cost center update (FIN_CCA)
Update of the sender cost center and receiver cost center fields
 Preparation for consolidation (FIN_CONS)
Update of consolidation transaction type and trading partner fields
 Business area (FIN_GSBER)
Update of the sender business area and receiver business area fields
 Profit center update (FIN_PCA)
Update of profit center and partner PC fields
 Segmentation (FIN_SEGM)
Update of the segment, partner segment, and PC fields
 Cost-of-sales accounting (FIN_UKV)
Update of the sender functional area and receiver functional area fields

 To display the available scenarios Financial Accounting (New), and choose Financial
Accounting Global Settings (New) -> Ledgers -> Fields -> Display Scenarios for
General Ledger Accounting
 The fields that are updated by the scenarios can be used to model certain business
circumstances – such as segment reporting.
 You cannot define your own scenarios.
 The delivered scenarios are assigned to the ledgers in Financial Accounting
Global Settings (New) -> Ledgers -> Ledger -> Assign Scenarios and Customer
Fields to Ledgers
 Important note: A ledger (=> the leading ledger in all cases) can be assigned
one or more scenarios, or even all six at once!
The decision as to how many scenarios to assign depends solely on which
"facts" / "business aspects" you want to model in the General Ledger Accounting.
 You do not necessarily have to define non-leading ledgers, which means scenarios do
not have to be assigned to non-leading ledgers either. Important: You do not
need a ledger for each scenario!
 Multiple/non-leading ledgers are useful for portraying accounting in accordance with
different accounting principles.

Entry View and General Ledger View:

When New General Ledger Accounting is active, a Financial Accounting document always
has two views: The entry view and the general ledger view.
Besides the leading ledger, you may also see the document in other, non-
leading ledgers in the general ledger view.

Confidential Page 12 of 263

Definition:
Entry View: View of how a document also appears in the subledger views / subledgers
(AP / AR / AA / taxes)!
General ledger view: View of how a document appears (only) in the general ledger!

Use of the Entity Segment:

The Segment field is one of the standard account assignment objects available in mySAP
ERP for running analyses for "objects" below the company code level.

 Segments can be used to meet the requirements of international accounting principles

(=> IAS / IFRS / U.S. GAAP) regarding "segment reporting".
 The segment is provided in addition because the business area and/or profit center
were frequently used for other purposes in the past and thereby to meet other
requirements.
 The ERP system enables you to assign a segment in the master data of a profit center.
 Postings are automatically made to the segment when the profit center is posted:
There is no "dummy segment posting", as in the profit center logic; if the
profit center does not have a segment, there is no segment account assignment
either.
 The default setting involves deriving the segment from the profit center, but customers
can develop their own derivation solutions through a user exit (BAdI).
The definition name of the BAdI is: FAGL_DERIVE_SEGMENT

Document Splitting – Motivation

Steps Involved in Document Splitting:

Simplified, you can divide the document splitting process into three steps:
1. Passive split: During clearing (during a payment, for example), the account
assignments of the items to clear are inherited to the clearing line item[s]
(=> such as payables line item[s]). This step cannot be customized.
The passive split not only ensures that the account itself is balanced, but also the
additional dimensions. The passive split not only ensures that the account itself is
balanced, but also the additional dimensions.

2. Active (rule-based) split:

 The system splits documents on the basis of (delivered or custom ) document splitting
rules
 Document splitting rules can be configured.

3. Clearing lines/zero balance formation by balancing char. (and document):

 The system creates clearing lines automatically to achieve a split
 You can control this process with the "zero balance indicator"

Note: Between steps two and three, document splitting is supported by two things:
inheritance and default account assignment.

Document Splitting Characteristics (from FI):

You first have to define for which (FI) characteristics document splitting is performed.

Typical document splitting characteristics:

• Business area

Confidential Page 13 of 263

• Profit center
• Segment
Important: User-defined entities can also be split

 The system proposes logical document splitting characteristics based on the assigned
scenarios.
 If you elect to use additional document splitting characteristics, you should use these
characteristics in at least one ledger.
 You should always set the Zero Balance indicator if you plan to use the
characteristics to create financial statements. The balance of the involved entities is
then always 0 for every posting, ensuring "entity balancing".
 The Mandatory field has two meanings:
1. Firstly, it is an extension of the field status for accounts in which the
characteristics cannot be "entered" during document entry, and/or for accounts that
cannot be controlled using the field status. Example: Vendor lines should always
include a profit center or a segment.
2. Secondly, 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).

Activating Document Splitting and Inheritance:

Document splitting is first activated client-wide in Customizing
 In a further step (in the dialog structure), you can use this transaction to
activate/deactivate document splitting for each company code
 Inheritance means that, when you create a customer invoice from a revenue line, for
example, the entities (such as business area or segment) are projected (inherited) to
the customer and tax lines in the general ledger view.
 There is no reason why you should not activate inheritance when document splitting
is active.
If you were not to use inheritance, you would have to define "rules" for the
business processes to ensure that the account assignments are projected, for
example, to achieve a zero balance in order to post the document.
Activation of inheritance is practically the first step to enable documents to be
posted when document splitting is active, without any other Customizing activities.
Inheritance is performed online and at the line item level.

Note: The expert mode provides information on all essential document splitting parameters
(such as splitting method or business transaction) and describes how the split amounts are
achieved.

New General Ledger Accounting – Integration

a. Real time Integration CO – FI

Trace / Log: Transaction FAGLCOFITRACEADMIN
If necessary, the CO=>FI real-time integration can be logged with a trace.
 If the trace was active during a CO posting, you can analyze the real-time integration
data again at any time – including the following data:
 The document number of the original CO document
 Whether it was a transfer or a test run
 The document number of the follow-up document in FI if a transfer to FI took place
 The reason for transfer, but also the reason for a failed transfer

Confidential Page 14 of 263

  The posting mode: online posting or subsequent transfer (subsequent posting /
follow-up)
 Posting date, posting time, and user
 Line item data for the documents: All posted to objects and partner objects

Real-Time Integration CO -> FI – Document Flow

Display CO Document:
From CO reporting line item:
• Menu path: Environment -> Accounting Documents
From originally used CO transaction (e.g. GB13N):
• Menu path: Goto -> Accounting Documents

7. Automatic Payment Programme

Automatic Payment Program serves the purpose of posting accounts payable (say, payment
to a vendor) based on vendor invoices automatically, shortly termed as APP.

Steps for Configuring APP:

1. All company: Maintain Paying company code, Maintaining Sp. G/L transactions to be
paid for vendor & customers.
2. Paying company codes: Minimum amount for incoming & outstanding payment,
maintain Form for the Payment Advice and sender details.
3. Payment methods in country: Payment methods classification:
a. Bank b.Check c. Bills of Exchange D. Check/Bill/ Exchange
Maintaining Posting details:
Document type for payment –ZP
Clearing document type –ZV
4. Payment method in Company code:
Maintain Amount Limit: a. Minimum amount b. Maximum amount

Group of Items:
a. Select Single Payment for Marked Items
b. Payment Per due day
5. Bank Determination: Ranking Order, Bank Accounts, Available Amount

Blocking All Items of a Payment

If you want to block all items of a payment, you can do this by choosing Block all.
When making changes to a lot of open items, you should save your data frequently. By
choosing Environment _ Line item changes, you can display the change history and also see
which changes are not saved yet.

Blocking Open Items

Use
You block the items that, regardless of their due date, you do not want to pay. To do this,
you enter a blocking key in the item, which represents the reason for blocking. If you want
to block the account of a customer or vendor from payment, you enter the blocking key in
their master record.
The standard system contains several blocking keys for blocking, which you can add
to or change.

Confidential Page 15 of 263

The payment program creates a payment proposal during the payment run. The payment is
made on the basis of this payment proposal list. The blocked items are displayed separately
on the list. You can process the payment proposal, and, for example, set or cancel the
payment block on an item.
It is also possible to determine that a blocking key cannot be changed from the
payment proposal transaction.

8. House Banks
The banks with which your company (company code) maintains a bank account are referred
to as house banks.

You define these banks in the system under a house bank key (bank ID). You store
the accounts that you maintain at these banks under an account ID. For each bank account,
you create a G/L account in the SAP system.

Bank master data is stored centrally in the SAP system. This includes address data
and other control data, such as the SWIFT code. You require bank master data for your
house banks and for your customer or vendor's banks. By specifying the country and a
country-specific key, such as the bank number or the SWIFT code, you establish the
connection between your house banks and the bank master data (see the figure below). The
bank details are required for printing the payment forms.

9. FOREIGN CURRENCY VALUATION

FC Valuation – FAGL_FC_VALUATION

 A valuation run requires the entry of a valuation area (from FI).

 This area must be defined in Customizing and be assigned a valuation method – You can't do it
during the run itself!
The valuation method defines as before "how“ valuation is run and with which valuation
approach (such as the maximum value principle for payables)
 Only for balance valuation / not line item valuation: In a further Customizing step, you combine the
valuation area with an accounting principle (AP).

9.1 MODIFY RECONCILIATION ACCOUNT OF CUSTOMER MASTER DATA

Modify Reconciliation Account of Customer Master Data

When we make changes of existing reconciliation account form another one what all the things will get affect and
how it happens.
Is it possible to make two depreciation %age for operating chart of account and Local chart of account. Ex. 8% for
Operating and 10% for Local.
Once APP completed what happens . And what will be the Idoc status.
What all the process happens while posting MIGO entry.

Confidential Page 16 of 263