MOD - Final General Ledger Blueprint

AcceleratedSAP - Business Blueprint
ASAP Business Blueprint

General Ledger
Period-end Closing
Consolidations
•
•
PROJECT- BUSINESS BLUEPRINT...........................................................................................................................3

Document Flows.............................................................................................................................................................5
Legal Entity Structure..................................................................................................................................................10
QADB/CI Template......................................................................................................................................................11
Chart of Accounts.....................................................................................................................................................11
Master data............................................................................................................................................................11
G/L account master record processing ............................................................................................................11
Planning................................................................................................................................................................14
G/L planning ....................................................................................................................................................14
Posting to G/L.......................................................................................................................................................14
G/L account posting ........................................................................................................................................14
Manual foreign currency valuation .................................................................................................................16
Closing operations....................................................................................................................................................16
Period-end closing................................................................................................................................................16
Period Closing..................................................................................................................................................16
Foreign currency valuation balances ..............................................................................................................18
Foreign currency valuation open items ...........................................................................................................19
Periodic reporting ............................................................................................................................................19
Goods Received/Invoices Received (GR/IR) clearing accounts maintenance ..............................................20
Customer/vendor balance interest calculation processing...............................................................................20
Year end reports....................................................................................................................................................20
Year-end closing preparation ..........................................................................................................................20
Year-end closing ..............................................................................................................................................20
Archiving..............................................................................................................................................................22
Archiving (FI) ..................................................................................................................................................22
Archiving .........................................................................................................................................................22
Consolidation............................................................................................................................................................22
Master data............................................................................................................................................................22
Creation of consolidation guideline ................................................................................................................22
Company acquisition .......................................................................................................................................24
FS chart of accounts change ............................................................................................................................24
Company split ..................................................................................................................................................24
Preparations for Consolidation.............................................................................................................................25
Implementation of consolidation guideline ....................................................................................................25
Centralized Data Entry.........................................................................................................................................25
Data transfer ....................................................................................................................................................25
Currency translation.............................................................................................................................................25
Central currency conversion ............................................................................................................................25
Postings.................................................................................................................................................................25
Standardizing entries .......................................................................................................................................25
Intercompany Eliminations..................................................................................................................................26
Intercompany balance declaration ..................................................................................................................26
SAP Financial Close Sequence ...................................................................................................................................27
- End -.....................................................................................................................................................................27
2
• PROJECT- BUSINESS BLUEPRINT

Executive Summary - General Ledger/Consolidations Team
Financial Overview
Lam Research currently operates on a variety of financial systems merged at period-end to support external and
management reporting requirements. The processes include both manual and automated activities. The sources of
information are varied and non-integrated, thus requiring manual intervention and reconciliation to control totals
in the preparation of financial results. When the financial community has a firm knowledge that results are whole,
only then may they focus attention on the analysis of the result rather than in the preparation of those results. This
is the paradigm shift which SAP enables.
Business functions in the SAP Phase II implementation initiative include administration and management of the
general ledger (G/L) and the Company-wide financial consolidation process within SAP’s “FI” module. The SAP
G/L and Consol functions will replace the functionality of legacy systems enhancing the reporting and tracking
aspects of all related G/L and Consol activities.
To the extent that best practices are already incorporated in the SAP FI module, Lam will generally be
implementing the standard suite of G/L and Consol tools. Operationally, SAP applications will be far superior to
what is currently available. For instance, the integrated nature of SAP allows immediate posting of all
intercompany transactions resulting in balances between subsidiaries always remaining in balance. Additionally,
reporting from the FI module is far superior to what is currently available. Time consuming investigations of data
flow problems through dis-aggregated information and ad hoc routines will be replaced by basic SAP queries.
Key Functionality & Assumptions
Key Functionality of SAP’s General Ledger and Consolidations modules:

• One global chart of accounts will provide Lam with the flexibility to handle continued expansion and to
meet county-specific requirements. A global chart of accounts will provide real-time drill-down
access to worldwide financial data. The chart of accounts will allow for centralized control. The
number of accounts will be significantly reduced through the use of sub-ledgers (A/P, A/R) and
supporting product-line data managed separately in the SAP’s CO module.
• Period-end closing will be streamlined and result in a reduction of the closing cycle (Two Day Goal). A
number of enablers will aid this reduction including, but not limited to; automated journal entries,
balanced sub-ledgers, and a significant reduction in reconciliations.
• SAP will facilitate one close process for all company entities.
• Data is entered directly into the general ledger once and is available to all components and users of the
system. The quality of data can be ensured by monitoring information at the transaction source.
Customized data entry screens will enable rapid, efficient data input.
• The design will allow local and foreign currency transactions to occur in parallel. SAP will translate the
entry into local currency and store both transaction amounts. This results in the ability to view
balances in foreign currencies and facilitates the automation of foreign exchange gain and loss
recognition.
• Intercompany transactions will result in automatic postings to the G/L, eliminate out of balance situations,
and streamline the data entry process.
• Changing fiscal periods from one to the next, either monthly or yearly, is very simple, with controls to
easily open prior periods for posting when needed.
• Every account in the G/L has a large set of controls and rules that help manage and reconcile each account
based upon its own characteristics.
• Cost allocations will efficiently post using SAP automated functionality.
• SAP provides an improved audit trail though the use of the “document’ concept. Every transaction which
results in a financial impact to the general ledger (and even transactions which do not) receives a
3
document number. All transactions are stamped with a date, time, and user who entered the
transaction.
• The integrated nature of SAP’s financial applications will result in a reduction of reconciliation
processing. Closing and reporting from one central system will result in a shift of duty and
responsibility for the financial community at Lam from compiler/consolidator/reconciler to
business/financial analyst with the responsibility for monitoring, controlling, and reporting results.
Key Assumptions:
• Specific key resources are assigned full time to work in this process and are empowered to make
decisions.
• Business personnel take responsibility of the activities that belong to them, and participate actively on the
project.
• Legacy systems resources are assigned to work on interfaces and conversions.
• Development computer hardware environment is set up and ready after business blueprint workshops are
finished.
Key Benefits
• Information needed for decision making will be stored in one system only. As of this moment, several
systems contain necessary operational and reporting data (ASK, Excel, Sun Systems, Essbase, etc.).
• SAP system is year 2000 compliant.
• Business processes will be improved, according to Lam’s strategic vision.
• SAP FI system will have a much better audit trail, which will in turn simplify research and period-end
reconciliation.
• Close time will be significantly reduced.
Major Organizational Changes Anticipated
• The General Accounting department will be enabled to become pro-active problem solvers and decision
making drivers.
• International sites must truly act in concert with a centralized close process.
Key Risk
• With the high degree of visibility between legal entities, the open system will require sound business
policies to be in place to control intercompany charges and aid disputes.
Key Outstanding Issue

• Decision required on the use of local currency as the functional currency in all foreign sites. Initial
configuration requires that this issue be resolved. Corporate Controller and Treasury VP are working the
issue. For NextGen Team, resolving the issue before the end of November is crucial to successful
implementation.
4
• Document Flows
G e n e ra l L e d g e r A c c o u n t M a in te n a n c e
E nd
1 3 .2 . 4 9
N e e d fo r N e w
A c c o u n t E x is t s
N o
F I A c c o u n t M a in t e n a n c e F I F i n a n c ia l s
R e q u e s t fo r N e w
A c c o u n t C re a te d S y s t e m V a lid a t e s A ccount
A ccount R equest S y s t e m V a lid a t e s
in L a m C O A . A c c o u n t C o p ie d to A c c o u n t a p p e a rs N e e d s to b e A d d e d
C o m p le te d A p p ro v e d P ro p e r # S c h e m a E n t ity S p e c ific
(C o p y w it h A p p ro p ria te L e g a l o n F I F i n a n c ia ls to F in a n c i a ls ?
1 3 .2 .4 2 1 3 .2 .4 3 1 3 .2 .4 5 D a ta E n te re d
R e fe re n c e to E n t it i e s 1 3 .2 .4 7 1 3 .2 . 4 8
1 3 .2 .4 6
E x i s t in g S e t t in g s ) 1 3 .2 .4 5
1 3 .2 .4 4
Yes
A d d t o F i n a n c ia l
S ta t e m e n t
C O M a in t e n a n c e V e r s io n s 1 3 .2 . 5 0
R e v e n u e /C o s t A c c o u n t re q u ire d
E le m e n t R e q u ire d ? Yes V a lid a t e E le m e n t in C C A /P C A R e p o r ts ? Yes A d d to C C A /P C A
C opy A ccount E n t e r C O s p e c if i c
1 3 .2 .5 1 A p p e a rs o n C O 1 3 .2 .5 6 R e p o rts
fro m F I 1 3 .2 .5 2 d a ta 1 3 .2 .5 3
R e p o rts 1 3 .2 .5 5 1 3 .2 .5 8
N o No
E nd
E nd
1 3 .2 .5 7
1 3 .2 .5 4
C o n s o l id a t e d F S A c c o u n t R e q u ir e d
V a lid a te F S It e m End
it e m r e q u ir e d ? Yes C opy Account i n F in a n c i a l s ? Yes A d d to
A p p e a rs o n 1 3 .2 . 6 5
1 3 .2 .5 9 fro m F I 1 3 .2 .6 3 C o n s o lid a t e d
C o n s o lid a te d
1 3 .2 .6 1 R e p o rts 1 3 .2 .6 4
R e p o rts 1 3 . 2 .6 2
No
N o
E nd
End
1 3 .2 .6 0
P re -C lo s e C o lle c t a n d P ro c e s s D a ta
O n g o in g p r o c e s s in g t o t h e e n d o f a fis c a l p e r io d
M M SD SM
1 3 .3 .3 5 1 3 .4 .3 8 1 3 .5 .6 0 1 3 .1 2 .1 1
A ll I n v e n t o r y A ll S a le s A l l S a le s
A ll I n v o i c i n g , A ll C a s h A ll A s s e t S a l./W a g e s
M o v e m e n ts , O rd e rs , O rd e rs ,
C ash D is t r i b u t i o n s , T ra n s fe rs , A c t u a ls &
S h ip m e n t s , R e v e n u e /C O S , R e v e n u e /C O S ,
A p p lic a t io n s E xpenses R e t ir e m e n t s A c c ru a l
R e c e ip t s R e s e rv e s R e s e rv e s
1 3 .2 .4 1 3 .2 .5 1 3 .2 .6 1 3 .2 .7
1 3 .2 .1 1 3 .2 .2 1 3 .2 .3
G L
O n g o in g
A u t o R e c u r r in g A u t o m a tic I n t e g r a t e d
R e v ie w A u t o J E s V a li d a t i o n
J E s a n d A c c ru a l P o s t in g s
to C re a te , C h a n g e , o f P o s t in g s
R e v e r s a ls 1 3 .2 .1 0
o r D e le t e 1 3 .2 .1 1
1 3 .2 .8
1 3 .2 .9
G e n e r a l L e d g e r D e t a il e d
T r a n s a c t io n s
1 3 .2 .1 2
P o s s ib le b a c k - u p
d o c u m e n ta tio n P o s t E n t r ie s
1 3 .2 .1 3 1 3 .2 .1 4
J o u rn a l
E n try
N eeded?
1 3 .1 5 .2 2 A ll O t h e r
P e rio d ic In te rfa c e d
S e t tle m e n t s T ra n s a c tio n s
1 3 .2 .1 7 1 3 .2 .1 8
R e v ie w V a lid a te a n d R e c o n c ile
D a y O n e C lo s e
1 2 :0 1
AM
D ay
O ne
P r e lim in a r y R e v ie w ,
R e c o n c ile & A d ju s t /
R e -p o s t C o m p le t e S e c o n d
C o m p le t e F ir s t S e t o f 1 3 .2 .2 1 S e t o f P e rio d ic
F re e z e C o m p a n y
P e r io d ic P o s t in g s P o s tin g s
U p d a te C u rre n c y P o s t in g s
( D e p r , P / R A c c r u a l) ( A llo c a tio n s ,
T a b le 1 3 .2 .2 4
1 3 .2 .2 0 C o m p le te " R e g u la r " S e t tle m e n ts )
1 3 .2 .1 9
J o u rn a l E n trie s 1 3 .2 .2 3
1 3 .2 .2 2
No
P re p a re B a la n c e
R e m e a s u re m e n t a t S heet and P & L R e s u lts a s 1 3 .2 .2 8
F o r e ig n L e g a l E n t it y 1 3 .2 .2 6 E x p e c te d ? Y es C o n s o lid a te
1 3 .2 .2 5 1 3 .2 .2 7 1 3 .1 .1
C o n s o lid a te , R e v ie w a n d F in a liz e
D a y T w o C lo s e
1 3 .2 .2 8 C o n t r o lle r R e v ie w , In te rc o m p a n y
C u rre n c y
C lo s e d A d ju s t, E li m i n a t i o n A R & E l im in a t i o n o f I / C O
T ra n s la tio n
B ooks R e -p o s t A P , In v e s tm e n t in S a le s /C O S & T a x A c c ru a l E n try
1 3 .1 .2
1 3 .1 .1 1 3 .1 .3 S u b 1 3 .1 .4 P ro fit in In v e n to r y 1 3 .1 .6
1 3 .1 .5
In te rn a l F in a l P ro d u c e
C o n s o lid a te d M anagem ent F in a n c ia l s In te rfa c e to F a s t
R e v ie w & R e v ie w & F i n a l A d j u s t in g Tax
1 3 .1 .1 0
R e c o n c ilia t io n A d ju s tm e n t s E n t r ie s 1 3 .1 .1 1
1 3 .1 .7 1 3 .1 .8 1 3 .1 .9
Y e a r-E n d C lo s e P ro c e s se s in F I
The Y ear E nds
Yes
A N e w Y e a r B e g in s
F is c a l Y e a r N ew Y ear
V a r ia n t f o r N e w C r e a t e F is c a l Y e a r P o s t in g P e r io d s C r e a t e G lo b a l
No No
Y e a r E x is t s ? V a r i a n t a n d a s s ig n E x is t & O p e n e d ? P o s t in g P e r io d s
1 3 .2 .2 9 to C o m p a n y C o d e 1 3 .2 .3 1 a n d O p e n fo r
1 3 .2 .3 0 P o s tin g 1 3 .2 .3 2
Yes
C lo s e A /R C lo s e A /P C lo s e F A C lo s e G / L C l o s e C o n s o l id a t io n s
C h a n g e F is c a l
C a rry F o rw a rd o f C a rry F o rw a rd o f Y e a r ( n o e a r lie r C a rr y F o rw a rd G /L C a rry F o rw a r d F S
Y e a r- E n d C lo s e
A / R B a la n c e s A /P B a la n c e s th a n la s t m o n t h o f B a la n c e s Ite m B a la n c e s
1 3 .2 .4 1
1 3 .2 .3 3 1 3 .2 .3 4 p r e v io u s y e a r ) 1 3 .2 .3 6 1 3 .2 .3 7
1 3 .2 .3 5
F A P o s t in g s C lo s e F A
c o m p le t e f o r C a rry F o r w a rd
Yes
p re v io u s y e a r? B a la n c e s
1 3 .2 .3 8 1 3 .2 .4 0
No
C o m p le t e A s s e t
P r o c e s s in g
1 3 .2 .3 9
• Legal Entity Structure
L a m C o n s o lid a te d
L a m F re m o n t F o r e ig n S a le s C o r p o r a tio n
L a m S c o tla n d L td . L a m J a p a n L td .
(N o r th A m e r ic a ) (F S C )
C C 2000 C C 3000
C C 1000 C C 1100
L a m F ra n c e S A R L L a m T a iw a n L td .
C C 2100 C C 3100
L a m G e rm a n y G m b H L a m K o re a
C C 2200 C C 3200
L a m N e t h e r la n d s B .V . L a m S in g a p o r e P T E , L td .
C C 2300 C C 3300
L a m Ita ly S R L
C C 2400
L a m Is r a e l
C C 2400
• QADB/CI Template
Chart of Accounts
Master data
G/L account master record processing
1. Requirements/Expectations
Lam requires a chart that will meet our needs and minimize configuration time.
One Lam COA will be created for all legal entities.
The Lam chart may be enhanced per specific legal requirements for each legal entity.
The chart will be centrally maintained.
The chart will be designed to minimize the impact of additions and changes throughout the
system.
Text on the functionality of an account should appear on each individual account.
2.1 General Explanations

A complete review of the chart, accounts necessary and the settings per each is required.
• Comparison of Lam with Pre-configured chart required to arrive at decision regarding
proper mix.
2.2 Explanations of Functions and Events

• FS01 Create G/L Account Master Record.
2.3 Special Organizational Considerations

The COA will be maintained centrally in SAP as it is today, therefore there should be no impact
to the organization. International sites will have to route requests through this central location
which is a change in process only - not necessarily an organization structure change. Unique
skills in understanding SAP functionality is necessary though, since there are many rules that
can be assigned to one account. Training is a key to this successful implementation.
3. Changes to Existing Organization

Lam will need to learn the new chart of accounts and functionality of the various types of
accounts. Automatic postings will help reduce impact to the organization. The COA will be
maintained centrally in SAP as it is today, therefore there should be no impact to the
organization. International sites will have to route requests through this central location which is
a change in process only - not necessarily an organization structure change.
4.1 Description of Improvements

Due to the supporting functionality in SAP's Controlling module, the need to have specific
accounts for each; product line, sales tax state, and every legal entity intercompany activity, is
eliminated.
4.2 Description of Functional Deficits

None are apparent at this time.
4.3 Approaches to Covering Functional Deficits
6.1 System Configuration Considerations

A substantial amount of work is required in understanding and setting up Account Groups, Field
Status, Currency and Tax Settings for desired functionality and control.
6.2 File Conversion Considerations

Balance Sheet totals as of year-end 1999 will be loaded (income & expense will be zero).
Reconciliation (A/P, A/R, F/A) and actual inventory accounts will be loaded with detail of 6/30/99. Any
differences in inventory legacy historical cost versus new standard cost will be written off to the income
statement.
Other G/L accounts may be loaded as of 6/30 and subsequent adjustments made in SAP or these balances could be
posted as of final close of Lam's books as this will not interfere with daily processing going forward.
Legal entity historical loads of balances will be different from entity to entity. Consideration
must be given to these differences in each legal entity. While this historical load is not critical
to going live, a decision as to the detail, age and method of load (system vs. Business
warehouse) must be made.
6.3 Interface Considerations

None if Big Bang.
6.5 Authorization Considerations

Authorizations and rules can be configured to control the use of accounts and their impact on
CCA, PCA. Authorization to add or update the COA will be held centrally.
Business Process Questions
1: Business Process Requirements
What types of daily, weekly, periodic, and ad hoc transaction reports do you need for general ledger?
One report for each subsidiary ledger (AP, AM, AR, MM...) weekly or on request, this includes inventory reports
on quantity and fully absorbed overhead values.
Please provide your current Chart of Accounts.

Current chart is not in good order for use in SAP. Basic numbering structure can be used for most part, as it is
standard 1000=assets, 2000=liabilities... Many accounts will disappear as SAP accommodates reduction in
natural accounts required for financial reporting. See the "Draft of Proposed Chart of Accounts" - old accounts
have been mapped to new.
How do you change your chart of accounts?

Chart of Accounts will be maintained centrally - one point affects all down-stream systems and entities. All
requests for new or updated accounts will go through this central group. This group to reside most likely in
General Accounting Fremont.
4: Describe how the account number is set up (for example: department, natural account)
See complete draft of Chart of Accounts in the "Requirements" folder within the Finance directory on the
NextGen server.
5: Describe the numbering logic.

Follows standard SAP number logic including a six digit number. See complete draft of Chart of Accounts in the
"Requirements" folder within the Finance directory on the NextGen server.
6: How many natural account numbers will you have?

See complete draft of Chart of Accounts in the "Requirements" folder within the Finance directory on the
NextGen server.
7: What procedure do you use when you need to create new account numbers?
Chart of Accounts will be maintained centrally - one point affects all down-stream systems and entities. All
requests for new or updated accounts will go through this central group. This group to reside most likely in
General Accounting Fremont.
8: Can you define groups of general ledger accounts that require similar information in the master record?
Yes
9: How many retained earnings accounts do you maintain per company code?
One primary current year retained earnings account. Other equity accounts include; share capital/common stock,
retained earnings prior year, and possibly CTA.
10: For which general ledger accounts do you wish to retain line item detail?
Most accounts except; reconciliation accounts, sales revenue accounts, material stock accounts, and tax accounts.
11: Which accounts do you wish to have open item managed (for example: bank accounts)?
Bank clearing accounts, goods/invoice received clearing accounts, material in-transit, and any other accounts
where it's important to see the balance of an account represented by the items displayed.
12: Which accounts do you wish to maintain in foreign currency (for example: bank accounts)?
Some operating accounts within foreign entities will be maintained primarily in their local currency. Non-USD
accounts can basically exist throughout the balance sheet and P&L depending upon the legal entity and use of the
account. The answer to this question of course will depend upon resolution of the local functional currency issue.
Planning
G/L planning
1: What is the planning (budgeting) that you maintain in your General Ledger?
Currently, no budget data is kept in the general ledger, although account hierarchy for P&L is the same.
Requirement is to merge actual and budgeting data together in either a data warehouse environment, the SAP
general ledger, or a third party forecasting tool.
2: Do you plan on a monthly, quarterly, or annual basis?

Currently, forecasting is completed monthly, budgeting is completed bi-yearly.
3: How do you distribute planned amounts to individual planning periods (for example: equal distribution
among periods, seasonal distribution)?
Equal distribution among periods, or based upon relative actual number of days in a given period.
4: Does your planning take into consideration non-financial (statistical) data?

Yes, various statistical data such as headcount will be used in the planning process.
Posting to G/L
G/L account posting
Lam requires various forms of entry into the G/L.
Lam wants to reduce the time and effort required to post, validate and close the G/L.
Lam expects control over and the proper use of G/L accounts.

Standard G/L journal entries including accruals, reversals, recurring will be used.
Additional functionality of SAP account assignment models and posting with reference will also be used.
Many of the entries made into the G/L will be generated automatically from the various integrated systems within
SAP.
Sales & Distribution - Revenue Related & Receivable posting
Service Management - Revenue Related & Receivable posting
Materials Management - Inventory Movements, COS, Receipts(All)
Human Resources - P/R and Accrual entries
Internal Accounting applications - Cash, Currency, A/P invoices, A/R manual invoices...)
Fixed Assets - Depreciation, Retirements...
Controlling - Production costing and Expense allocations
Automatic Account Assignments are created in each application to point transactions to the proper G/L account.
Settings are also made on each G/L account to ensure all necessary information is captured on transactions
"hitting" the accounts where this information is shared/used in other modules (CO for example).
Since transactions are instantaneously posted to FI, Validations of the postings can occur throughout the month.
Because of the set-up of "Reconciliation Accounts" - A/P, A/R, F/A are always reconciled and
can be validated quickly.

Journal Entry Documents
G/L Document Posting F-02
With Reference FBR2
Recurring Entries F.14
Accruals F.81
Reversals FB08
Account Assignment & Field Status are configuration steps that will enable the integrated
processes.

Data entry time and errors will be reduced by the automatic postings to the general ledger.
Journal entry tools enable faster data entry.
• Auto-reconciliation of various sub-ledgers with quick validation routines.
6.1 System Configuration Considerations

All integrated processes resulting in a G/L transaction will be mapped to the required G/L account.
G/L accounts will be set with predetermined additional information requirements.
This definition and setting will occur during the realization phase.
Document numbering - Italy follows a chronological numbering requirement for:

· Purchase Orders - starting with number one at the beginning of the calendar year
· Sales Orders - starting with number one also at the beginning of the calendar year.
This is a requirement of the Italian IRS concerning VAT issues
6.4 Reporting Considerations

Standard SAP Deliverables for Documenting posting data including Compact Journal & Balance
Audit trail.
1: What types of general ledger transactions do you process?

[X] Journal entries
[X] Recurring documents
[X] Accruals/Deferrals
[X] Intercompany transactions
[X] Others
2: How does your current system assign document numbers (internally, externally)?
Internally
3: What is the numbering logic?

Manually assigned in a series.
4: Are the document numbers assigned on a yearly basis?

No
5: Describe any special requirements to posting to particular general ledger accounts (for example:
expense accounts require an associated cost center).
Expense entries definitely require a cost center. Other account requirements will be reviewed in detail during
realization, but there are no major blueprint issues at this point.
6: Is there certain information that you wish to be able to display when you view journal entries online?
Debit/credit accounts, cost centers, amounts, and descriptions of each line, journal entry number, plant code,
company code, period posting to, page number.
Manual foreign currency valuation
1: In which case do you post foreign currency revaluations manually?

None, all revaluations are system generated.
Closing operations
Period-end closing
Period Closing
The ultimate goal in Lam's utilization of SAP's General Ledger module will be to reach a two day Close
completion. So it follows that Lam's requirements of SAP's G/L module include:
- System processing time must be kept to a minimum just before and during the two day close cycle.
- Modules outside the G/L must integrate and automatically post to the G/L efficiently and in-balance not only
during the period-end cycle, but also when possible DURING the period using pre-determined schedules in order
to minimize the impact to processes near the end of the period and during Close.
- Reconciliations and adjustments must be made DURING the period when possible, minimizing the impact to the
Close. This includes inventory reconciliation, internal order settlements, reserve calculations, depreciation
expense, allocations and any other process that has potential to complete work before the Close.
- Worldwide control of all legal entities that effect a coordinated, centralized approach to managing postings and
closings of sub-ledgers and final books. SAP G/L management and control of entities' books must consider time
specific requirements, i.e. Japan will close at a very different time than Fremont yet some controls upon Japan are
managed in Fremont.
• - All subsidiaries will operate from the same Chart of Accounts (see Chart of Accounts
maintenance).

At Lam, the period-end closing will complete all sub-systems' and sub-ledgers' financial activities in order to
understand actual and planned financial results of Company operations for monthly, quarterly, and yearly time
periods. The basic deliverables include balance sheet and income statements for each legal entity based on actual
and planned activity. (Other report deliverables such as product line and regional P&Ls are covered in the CO
functions of SAP.) Please see the "Close Process" flow diagram and "Financial Close Sequence" Gantt chart
attached to this business process blueprint for a detailed scenario for Period-end Closing.
It is expected that virtually all modules within SAP have input into Period-end Closing with
regard to financial result information. Lam expects these interfaces to be extremely well
integrated and automated as advertised. Please see the aforementioned flow diagrams and Gantt
chart for details on the expected inputs from all sub-systems.

With the expectation that using SAP G/L functions and processes reduces the amount of time
and effort required to complete the Period-end Closing for the Company, there should be a
REDUCTION in the resource required to accomplish this. In Lam's situation this translates into
greater employee productivity and moral - a key requirement for the system in general.

With the expectation that G/L functions be centrally managed, it remains to be seen exactly who
in Lam's organization will have this responsibility and how it will be managed. Considerations,
as mentioned, must be given to local time requirements and to exactly which controls will be
utilized worldwide. For example, preventing posting to accounts payable allows the Company to
move on with the Period-end Closing - this control could be managed centrally with
considerations. But SHOULD it be managed centrally?. These specific situations will be
analyzed and set up in the Realization Phase of this SAP implementation.

On-line real-time integrated financial processing of most all SAP modules enables employees to become vastly
more efficient. From product costing to sales order processing and all related and supporting systems, the Period-
end Closing process will be the ultimate beneficiary of SAP's integrated systems. Please see the close process flow
diagram showing all module inputs to the general ledger keeping in mind that most modules input real-time to the
G/L. Consider the information available to act upon before the actual period-end arrives. Lam should see major
improvements in cycle times and data accuracy as long as these capabilities are utilized.
The Realization Phase of the project should detail out the specific process changes that allow
Lam to take advantage of real-time data. For example, intercompany receivables and payables
are recorded as they occur and may be analyzed throughout the month/quarter resulting in much
more time to verify postings before Close.

There are no deficits to SAP's Period-end Closing functionality perceived at this time.
5. Notes on Further Improvements

SAP's Project System (PS) will not be utilized in this phase of the project. The interim solution
for project accounting will utilize SAP's Internal Order functionality. Please see the CO module
description of this process.

It is expected that only ending balances will be brought into SAP without detail on go-live date. with the
exception of:
- AR balances
- Fixed asset balances
- AP balances (Ann MacDonald wants to freeze all AP activity prior to go-live and start over with zero balance.)
There will be no historical legacy system data converted.
6.3 Interface Considerations

Interface related considerations include:
- Vertex tax package for calculating tax books, plus foreign requirements of this package
- Travel Spending package (Necho) and foreign requirements of this module
- Third party software for Forecasting/Budgeting
Decision discussions relating to the above are in progress and expected to be resolved shortly.

Standard balance sheet and income statements and trial balances are required at period-end. SAP
supplies this and more using "account group" reporting functionality and "Report Painter"
functionality.

Top-level process control over sub-system posting and closing needs to have ownership assigned.
Lower level control over account postings needs to be assigned. Each account has rules that
allow only certain types of postings. Consideration needs to be given to who maintains these
controls.
Foreign currency valuation balances

One of the major steps of the closing process is the "remeasurement" of foreign currencies.
Lam must "remeasure" its books into the local currency.
Lam bases this remeasurement and the group consolidation upon the key rate entered at 12:01am on day 1 of the
close process.
This rate remains in effect as the current rate for the following monthly activity.
Only certain accounts are remeasured and this flag will be set on the G/L master record.

Upon the close of business for the month (12:01 AM) after the last day of month the period is blocked for posting
of normal daily activity (A/R, A/P, SD, MM...) and new period opened if not already performed.
The Currency tables are maintained for the new rate to be in effect as of the last day of the month (to remeasure as
of that day).
The rate is US based "Reuters" currency rates on the last day of the month.
An exchange rate difference key is created to point to this rate and to designate which accounts are to be
"remeasured".
Upon "close" of the legal entity books, two currency translations are performed.
One for open item accounts which valuates each individual transaction and one that revaluates balances.

The following details the chronology of events with the accompanying SAP transaction code:
The period is selectively blocked for posting new period opened (12:00 AM Day 1) OB52
The new currency rates are created (12:01 AM Day 1) OB08
Legal entity books are finalized
Foreign Currency remeasurement for open items executed/booked F.05
Foreign Currency remeasurement for balances executed/booked F.06
Legal entity books closed OB52

Control of the currency table maintenance function and the remeasurement process is an issue for Lam due to
timing issues.
The various Lam legal entities are spread over various time zones therefore the new period rate should be added
before the first entries are processed for the new period.
This is feasible since the rate could be changed on the weekends since every period closes on a weekend.
The year-end close does not follow that logic however since it ends on June 30 regardless of day.
Irregardless, any financial impact is negligible and would correct itself upon the next remeasurement.
Therefore, it would seem appropriate to maintain the currency tables and remeasurements
centrally.

Centralized Currency Table Maintenance and Remeasurement Execution.

Centralized authorization for the above mentioned functions
1: Describe your foreign currency revaluation process and which valuation methods and exchange rate
types you use?
Remeaurement of specific accounts at legal entity level.
Group consolidation translation at USD
All translations use same rate method as of same date. (Rate as of 12:01AM Day 1)
2: How do you currently maintain your exchange rates? Are they manually entered or uploaded from a
service?
Lam plans to manually update currencies.
3: Do your material movements consider LIFO or FIFO accounting strategies ?

All of Europe requires FIFO, or Standard Cost which is compares closely to FIFO.
Foreign currency valuation open items
1: How do you currently maintain your exchange rates? Are they manually entered or uploaded from a
service?
Lam plans to manually update currencies.
2: Describe your foreign currency revaluation process and which valuation methods and exchange rate
types you use?
Run currency valuation based on rate on last day of month, that rate is also the new rate for the next month until
the last day when it is updated again and valuations are run for that month.
Periodic reporting
1: Which internal and external evaluations belong to month-end closing? Please provide a sample of all
evaluations.
Reconciliation of Accounts - A/R, A/P, F/A, Inventory and other key accounts such as cash bank accounts.
2: Do you want to report daily or weekly balances? (If yes, you will need to use Special Ledger.)
No
3: How do you specifically handle reporting for taxes on sales and purchases?
By tax jurisdiction. In Europe, VAT return has to be provided on a monthly basis; comprehensive quarterly
reports might also be requested.
4: Do you create inventory lists using the SAP R/3 System, or using a non-SAP system?
Will use SAP system functionality.
5: What does your asset history sheet look like?

See Asset Management (Europe has differing requirements regarding useful depreciable asset life).
Goods Received/Invoices Received (GR/IR) clearing accounts
maintenance
See Invoice Verification process.

Load of open GR/IR receipts on go live date.
Possible scenario:
1) load open PO's
2) create amended line items for open receipts back on to PO with dummy G/L
account but original description.
3) Review these items or maintain spreadsheet of open GR items with AP
referencing as backup and charging dummy GR/IR account upon manual
invoice entry or maintain invoices in ASK for those open items and charge
dummy GR/IR account upon manual invoice entry.
1: What is your procedure for reporting goods receipts without invoice and invoices without goods
receipts separately in your balance sheet?
GR/IR account is GR without invoice receipt only.
IR without IR is a manual periodic accrual.
Customer/vendor balance interest calculation processing
1: For which customers/vendors do you calculate interest on balances? Please give a brief description.
Customer by Customer decision, pre-agreed in sale. No regular interest charges. For consignment stock, we are
required to charge interest on holding the inventory.
2: For which G/L accounts do you calculate interest on balances? Please give a brief description.
There is a note payable that resides on Lam Japan’s books that we calculate and record interest.
Year end reports

Year-end closing preparation
Year-end closing
Lam requires a clearly define process for closing a year and opening a new year.
Lam expects a smooth transition from year to year processing with no time delays.

The year-end process is a sequence of events for the rolling-forwarded of balances to the
new year.
There is no "hard" close of the FI module.
To begin a new year the following conditions need to be met -
The "Fiscal Year Variant" for the new year must be created. This is the creation of the
table of period dates for the new year.
The desired posting periods need to exist and be open in the open/close posting period
table.
The following processes can be performed at any time after the creation of the Fiscal Year
Variant -
The A/R & A/P balances are carried forward to the new year. This can be done even before
the year-end and any subsequent prior year posting will update the balance carried forward.
The following process needs to be performed at a certain time -

The Asset Management module requires the running of the "Change Fiscal Year" program.
This can be performed only in period 12 of the prior year going forward.
After the change fiscal year program has been run and all Asset postings are complete you
must carry forward the F/A balances. Unlike A/P & A/R subsequent prior year postings are
not carried forward. If additional asset postings are required, the above process needs to be
reversed and rerun.
The following process can be performed at anytime in the close process -

The G/L balance carry-forward program carries forward the profit & loss accounts into the
predetermined retained earnings account. Subsequent postings made to prior year will
automatically update the relevant carry-forward balance.
Consolidations
The balances in the consolidations module must be rolled forward to the current year once
the
final consolidation for the prior year has occurred.
1: Do you run the year-end closing process in asset accounting separate from general ledger?
Asset accounting is integral to and a subset of the general ledger close.
2: When do you close your fiscal year?

[X] Always on same date
[ ] When required
[X] On certain month
[X] Date for GL Accounting
[X] Date for AR Accounting
[X] Date for AP Accounting
3: Which operations are part of the year-end closing? E.g. Correction of depreciation, revaluation...
Same as quarterly close when ALL accounts are verified to be accurately representing the period's ending balance.
Goods in-transit to foreign entities are taken back by Corporate due to insurance rate calculation.
Commission accruals are brought up to date at year end from the one month lag calculation made during the year.
4: Please describe your year-end closing process

See the Year End Close Process flow diagram
Archiving
Archiving (FI)
This Scenario/Process Group best represents your requirements for this Business Process.
1: Business Process Requirement
How long do you want to keep the documents online in the database? Please specify by type of
transaction.
Archiving policy to be determined. In Europe, financials must be kept in archive up to ten years.
Archiving
Please refer to Master data handling (Quality Management)->Archiving (quality management)
for more detailed information.
Consolidation
Master data
Creation of consolidation guideline
Lam must consolidate the results of its operations globally.
Lam requires a single group consolidation for legal reporting, however a possible regional "step" consolidation
(Europe, Asia, US) may need to be performed for management reporting purposes.
Lam will update the consolidation module automatically from FI (system performance permitting).
The consolidation module will use the "Lam" chart of accounts and Financial Statement Version subtotals as a
basis for its Financial Statement Items (FSI).
Additional FSI's will be created as required for reporting purposes.
Lam maintains a group currency of USD, and consolidations will be maintained in such.
Lam will perform various consolidating and eliminating entries.

To perform the consolidation, the following steps will occur.
Carry-forward of Retained Earnings from FI.

Validation of the legal entities' balances.
Re-measurement of legal entities' balances to local currency
Translation of foreign currencies to USD
Elimination of Investment in Subsidiary.
Elimination of Intercompany Payables & Receivables.
Elimination of Profit in Inventory with Intercompany Sales & COS
Reclassification of Intercompany Sales & COS with COS.

The following details the chronology of events with the accompanying SAP transaction code:
The individual legal entity books are "closed"

A roll-forward of the retained earnings is performed OC55
A validation that the "books" are in balance is performed OC77
Currency translation is executed for all relevant entities OC91
Intercompany AP/AR accounts are eliminated. OC89
Investment in Subsidiary accounts are Eliminated/Reclassed OC69/OC90
Balance sheet evaluations are run on the inventories effected
by intercompany sales. MRN9
Inventory revaluations are posted in consolidations GC23
Remaining intercompany Sales/COS are reclassed OC90/GC23
Any other Reclasses/Adjustments are made. OC90/GC23
Data Selection is performed for reporting OC87
Reporting is executed SART

It is not feasible to track every piece of inventory in order to arrive at a specific elimination of profit in inventory
amount.
4.3 Approaches to Covering Functional Deficits

In order to best evaluate the profit in inventory the following enhancements will need to be performed.
The US standard cost will be maintained in the material master of every relevant foreign entity.
This will need to be updated as the standards change.
This will need to be maintained in USD and the valuations calculated based on USD.

The consolidation reports must be built.
All pre-delivered reports contain predefined FSI's that are not specific to Lam.
Various reports can be built in a short amount of time by copying the structures of the
predefined reports column and row layout structures.

SAP delivers preset rules for the control of the flow of events in the consolidation process.
These are by no means complete, and therefor one person should be responsible for the entire
consolidation process to ensure the complete and correct flow of events.
1: Do you have more than one legal company?

Yes
2: Are they all represented in the SAP system by an FI company code?

Yes
3: Are there transactions between these companies?

Yes
4: Does the effect of the transactions between the companies need to be eliminated when these
companies are combined?
Yes
I/CO Sales, COS, Profit in Inventory, Assets
5: List all legal entities that will be included in the consolidation process.
See Company Code List
6: What is the currency of each of these companies?

TBD -
Scenario 1 - All USD except Japan
2 - All Local Currency
Consideration must be given to the Euro currency in Europe.
7: Which of these companies are parent companies?

Lam US will represent the parent.
Group will be consolidated under group company 100. (or whatever desired)
8: How will data enter the consolidation database for each of these companies?
Auto update from FI, system performance permitting, otherwise in periodic loads.
9: Have you determined the structure of reporting on accounts for the consolidated entity? This will help
in determining the number of totals financial statement items that are needed.
Will be a copy of the FI GL account structure and FSV items.
Additional accounts for consolidating accounts as determined.
10: What are the posting attributes for each of the financial statement items that will be created? This will
determine the validation that will be done on each FSI that is posted to by the
consolidation system (trading partner, transaction type currency, etc.).
I/CO transactions are coded with trading partner identification.
Transaction type currencies will be the same as the FI transactions.
All consolidating transactions will be in USD group currency.
Company acquisition
1: Will your company make another company acquisition?

Yes, most likely.
FS chart of accounts change
1: Within your consolidation, do you need to convert your accounts to a different Chart of Accounts?
Not really. Additional accounts, sets and formatting are needed to assist consolidations.
The French COA will need to be converted once a year.
Company split
1: Will you convert a company to two or more separate legal entities?

Not in the short term, but there is a possibility that this will happen.
Preparations for Consolidation
Implementation of consolidation guideline
1: What types of validations need to be performed on the data at the original currency level?
Validation of balanced financials from FI.
Necessary currency translations performed.
2: What types of validations need to be performed on the data at the translated currency level?
Intercompanies balance.
Eliminations have been performed.
Centralized Data Entry

Data transfer
1: Do you want real-time access to consolidation data?

Yes, performance permitting
2: Do you want drilldown capability in reports from the consolidation database to the original entry?
Yes
4: Do you want to impact your Special Purpose Ledger with entries from non SAP systems (similar to
direct data entry, but as an interface.)
No, all data will come from SAP same client unless we do not have a big bang implementation.
Currency translation
Central currency conversion
1: Are any of the companies denominated in a foreign currency?

Yes
2: What is the translation method that this company uses (Temporal or Current Rate)?
Current rate updated at 12:01 AM of day 1 of close.
Postings
Standardizing entries
1: Will there be a need to enter transactions directly into the Consolidation database without impacting the
balances in any of the SAP applications?
Yes
These will be consolidating entries only.
2: What strategy will be used to make adjustments in consolidated results if the other SAP financial
applications are closed for the period?
In the case where an FI document needed to be posted, Lam will re-post to FI and rerun the consolidation
procedure if required.
Only foreign currency entries, I/CO entries in FI would force a re-consolidating.
Tax entry to Lam US would not effect consolidation process.
Intercompany Eliminations
Intercompany balance declaration
1: Identify the type of inter-company transactions that occur in the organization.
(E.g.: Inter-company payable/receivable, sales/COS, corporate interest charges)
I/CO payables and Receivables Trade - based on I/CO Sales and COS
I/CO payables and Receivables non-trade based on I/CO charges
2: Identify the accounts that will be involved in each of these inter-company postings.
I/CO AP & AR Trade
I/CO AP & AR - Other
I/CO Sales Revenue & COS
Inventory (or Inventory in Transit)
Various Expense Accounts
3: What companies are involved in each type of inter-company transaction?

All Companies
4: Will any of these elimination's be one-sided elimination entries?

No
5: Is there any profit in transferred inventory that needs to be eliminated?

Yes
6: Is there any profit in transferred assets that needs to be eliminated?

Yes
7: Are there any inter-company transactions that will be needed to eliminated manually?
Yes:
The elimination of Profit in Inventory with offsets to I/CO Sales & COS.
The elimination remaining I/CO Revenue & COS with difference to Trade COS.
8: Where should the differences in inter-company balances be posted?

There should not be any differences due to controls and rules established for I/CO charges.
Billed I/CO entries should automatically post to other legal entity.
In the case of billed inventory, amounts could be posted to an inventory in-transit account and moved to regular
inventory upon physical receipt.
• SAP Financial Close Sequence

C = Within Two Day Close
P = Precursor to Close
T = Transactions
X = Post Close (not gating)
C2 = Close but minimize impact to system processing Dependant upon Other Module
 = not needed in Soft Close Eliminate this task in Soft Close
Fiscal Day:
Tasks -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 1 1.1 1.2 1.3 1.4 2 2 2.1 2.2 2.3 2.4 2.5 3 4 5 6 7 8 9
X/T Inventory Reconciliation MM
P Reserve Calculations CO
T/P Variance Calculations CO
P Manufacturing Overhead Application CO
P Settle Internal Orders CO
P Asset Close, Depr/Amort posting (last before close) AM
C AP Vendor Close AP
C MM Period End Close/Open (Logistical Dependency) MM
C Update F/X Rate Table
C AR Customer Close - Complete Billing Docs/Recon AR 
C/T Revenue Recognition SD 
C/T Payroll Accruals (External Force) 
C FI Allocations
C2 Product Standard Cost Release: Bi-yearly CO
P/C Benefits (External Force)
C CO Allocations CO
C Work In Process Calculation (RA) CO 
C Accruals 
C Commissions (External Force) ? 
C Re-measurement of Foreign Entity to Local Currency
C Intercompany Receivable/Payable Eliminations
C Intercompany Transferred Asset Depreciation Elim
C Intercompany Profit Eliminations
C Translation of Foreign Entity Balances to USD
C/P Journal Entries (Opr. Exp Review/Adjust)
C Transfer Costs to PCA CO
C Taxes - Vertex (External Force) VER
C Reports (Deliverable)
C+1 Plan Updated (Deliverable)
X Reversals 
P Data Maintenance/Clean Up (Logistical Dependency)
P Open Next Period FI
T Actual Taxes (External Force) VER
X Product Costing Roll CO anytime
X Archiving
C Material Ledger? (Logistical Dependency)
• - End -

MOD - Final General Ledger Blueprint

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

MOD - Final General Ledger Blueprint

Caricato da

Copyright:

Formati disponibili

AcceleratedSAP - Business Blueprint

ASAP Business Blueprint

PROJECT- BUSINESS BLUEPRINT...........................................................................................................................3

• PROJECT- BUSINESS BLUEPRINT

Key Functionality & Assumptions

Key Functionality of SAP’s General Ledger and Consolidations modules:

Major Organizational Changes Anticipated

Key Outstanding Issue

The Y ear E nds

2.1 General Explanations

2.2 Explanations of Functions and Events

2.3 Special Organizational Considerations

3. Changes to Existing Organization

4.1 Description of Improvements

4.2 Description of Functional Deficits

4.3 Approaches to Covering Functional Deficits

6.1 System Configuration Considerations

6.2 File Conversion Considerations

6.3 Interface Considerations

6.5 Authorization Considerations

Business Process Questions

1: Business Process Requirements

2: Business Process Requirements

Please provide your current Chart of Accounts.

3: Business Process Requirements

How do you change your chart of accounts?

5: Describe the numbering logic.

6: How many natural account numbers will you have?

2: Do you plan on a monthly, quarterly, or annual basis?

4: Does your planning take into consideration non-financial (statistical) data?

2.1 General Explanations

2.2 Explanations of Functions and Events

4.1 Description of Improvements

6.1 System Configuration Considerations

Document numbering - Italy follows a chronological numbering requirement for:

6.4 Reporting Considerations

6.5 Authorization Considerations

Business Process Questions

1: What types of general ledger transactions do you process?

3: What is the numbering logic?

4: Are the document numbers assigned on a yearly basis?

Manual foreign currency valuation

Business Process Questions

1: In which case do you post foreign currency revaluations manually?

2.1 General Explanations

2.3 Special Organizational Considerations

3. Changes to Existing Organization

4.1 Description of Improvements

4.2 Description of Functional Deficits

5. Notes on Further Improvements

6.2 File Conversion Considerations

There will be no historical legacy system data converted.

6.3 Interface Considerations

6.4 Reporting Considerations

6.5 Authorization Considerations

Foreign currency valuation balances

2.1 General Explanations

2.2 Explanations of Functions and Events

2.3 Special Organizational Considerations

3. Changes to Existing Organization

6.5 Authorization Considerations

Business Process Questions