This free book provides an introduction to SAP Business One Release 2005 A SP01.
SAP Business One …To Go is aimed at a U.S. audience, but all users of SAP Business One will find the book useful.
It includes business examples, annotated screenshots, and process diagrams, as well as tips, checklists, reminders, and definitions, and thus quickly prepares you to make the most out of the application for the benefit of your organization. Cross-references to the product documentation and the SAP Business One Customer Portal guide you to more in-depth information. The book is intended to complement, not replace, existing learning resources.
Continue Reading …
SAP- Sales & Distribution (SD) Notes
Module Functions:
(SD) Sales and Distribution: the module where order taking, pricing, invoicing, route selection and other customer billing activities take place
I. Organizational Elements (structures) for SD Customer Order Mgmt
1. Company Code
2. Plant:
A manufacturing facility, distribution center or office that stores inventory or renders services.
3. Sales Organization:
Area responsible for distribution of goods and services, negotiating conditions or a sale. The level of reporting for sales figures and analysis
4. Distribution Channel:
The channel to the customer i.e. retail, wholesale and direct sales
5. Division:
Used for customer specific agreements i.e. partial deliveries, pricing agreements, special payment terms
6. Shipping Point:
The shipping location. Each delivery is specific to a single point
7. Warehouse Number:
Physical location within a plant that has inventory.
II. Main Documents (transactions)
1. Presale – quotation or inquiry document
2. Sales Order Document
3. Inventory Sourcing Document
4. Delivery Document
5. Invoice Document
6. Remittance advice
III. Master Data
1. Material Master:
Contains and defines all data to manage materials, sued as a source of purchasing information and valuation of inventory.
2. Customer Master:
All customer related data for processing orders, deliveries, invoices & customer pmts. The customer master is broken into general data, company code data and sales and distribution data
3. Condition (pricing records) – Predefined prices, discounts, surcharges, freight rates and taxes
By Rajagopalan M
SAP- Finance (FI) Notes
Module Functions:
The module that performs most of the traditional legal entity accounting functions, reporting by company, income statements and balance sheets. This is the module where you will find the A/R and A/P sub-ledgers and their open items along with the Asset Accounting Ledger.
Organizational Elements (Structures):
• Chart of Accounts – contains all account numbers and some general control data.
• Company Code – an independent balancing / legal accounting entity. each company code is assigned to one Chart of Accounts
• Functional Area – Classify operating expenses according to of cost-of-sales accounting by production, admin, S&D marketing, R&D, etc. By breaking costs into functional areas cost- of-sales accounting shows why costs accrue and indicates the economic purpose of the expense.
• Trading Partner
• Operating concern – the central organizational element in profitability analysis. It represents the environment within which a market or (customer defined) segment of the business can be monitored and profitability analyzed. 1:n relation to controlling.
• Controlling area – identifies a self-contained unit for which the management of costs and profits can be performed. Only one chart of accounts is allowed within a controlling area. However,
• (FI-AA) Asset Accounting – Depreciation (both book and tax), net book values, transfers and retirements
Document Posting Principles:
Each posting is in the form of a complete document. It must contain:
• Basic account assignment data (i.e. document date, posting date, document type, posting key, account number and amount.
• Entries must be made in all required fields.
• Debit and credit balances must be equal.
Every document contains a document header and at least two or more line items.
• The header contains information valid for the whole document (i.e. document date and type).
• Line items contain transaction specific data (i.e. posting key, account number and amount).
Document header:
• Document Date is the date that the transaction took place. (Must be on or before the Posting date ?) Posting Date determines the posting period (the system will enter this date if not provided?)
• Document Number is normally assigned b the system from a range predefined for each document type. (Not an input for g/l doc types {S}
• Reference and Document Header Text is descriptive data
• Period is the accounting period. Normally numeric (1 to 16?)
• Document type, a two character alphanumeric field. This field determines the document number range and the valid account types which may be used.
• A df Fixed Assets
• D df Accounts Receivable
• K df Accounts Payable
• R df Logistics (MM & SD)
• S df G/L
• T df Treasury
• W df Material Management
• Z df Sp0ecial purpose
Line Items:
• Posting Key is a two character numeric
• Together with the account number controls posting at item level
• Controls valid account type (D,K,M,A)
• Defines a Debit or credit entry
• Controls fields required optional or suppressed
• Valid FI posting keys
o 01-09 DR Customer
o 11-19 CR Customer
o 21-29 DR Vendor
o 31-39 CR Vendor
o 40 DR G/L
o 50 CR G/L
By Rajagopalan M
SAP- Enterprise Controlling (EC) Notes
Module Functions:
EC-CS Enterprise controlling – Consolidations: The module where consolidations and elimination occur for both a legal entity (Company Code) and a management area (Profit Center). Consolidation gives you a reconciled view of your groups financial data and lets you create the reports required by corporate law (by group, company or business areas) as well as reports which reflect your company’s internal management structure (by profit center or region). This is possible due to powerful consolidation functions built on top of flexible structures. The raw data can be transferred via interfaces with FI-GL (General Ledger), FI-AA (asset accounting), MM (Materials Management, SD (Sales and Distribution) and EC-PCA. You can also analyze the results of the consolidation immediately in EC-EIS. DATA TYPES – i.e. CS Breakdown categories
• Company & Trading Partner controlled by FI are required to generate eliminations. Note: FI-GL/AR/AP line items always have Company in Document Header. Trading partner is in document line item where relevant
• Profit Centers & Partner Profit Centers controlled by PCA are needed to generate eliminations for Management Consolidation by line of business
• Consolidation Units and Partner Units controlled by CS are used to generate eliminations for various consolidations. Transaction data from CS-PCA updates Consolidation units and if appropriate stores the data by partner Unit.
• Transaction types controlled by FI are used for reporting of consolidated balance sheet flows in CS. Transaction Types are used by the Fixed Asset module to distinguish between beginning balance, additions, transfers, disposals and ending balances. Separate types are usefull to distinguish movements in equity holdings for financial investments.
• Functional Areas controlled by CO are used for reporting consolidated P&L Statements. Functional Areas combine accounts but distinguish balances by function (e.g. selling expenses, research & development costs etc.)
o FI-AA Assets Module is the primary user of Transaction Types. Transactions made in FI-AA are stored with a Transaction Type which identifies whether it is an addition or disposal, etc. These Asset Transaction Types can be mapped into consolidation transaction types.
o Data passing from PCA to CS populates a single field with either a Transaction type for selected Balance Sheet accounts or a Functional Area for selected P&L accounts.
o Transaction types and Functional Areas are for Reporting.
EC-PCA Profit Center Accounting – Profit center accounting forms an interface between the operative controlling (CO) applications and the Enterprise Controlling (EC) module It reflects the actual and plan postings from operative controlling and settlements components with which it is in targeted in real-time. It then summarizes this data according to profit centers, which reflect the internal structure of areas of responsibility within the company code
• Each profit center is assigned to one controlling area
• Reason for Profit Centers
1. to analyze areas of responsibility
2. to delegate responsibility to different decentralized units
• Profit Centers can be set up
1. Product (product lines, divisions)
2. Geographical factors (regions, sites)
3. Function (production, sales)
• Profit Centers are organized into an organizational hierarchy in which responsibility and incentive structures can be defined. Profit Center Hierarchy:
o Node one
(a) Profit Center one
o Node two
• Profit Center two
(a). Revenue
(b). Costs
• Profit Center three
• Planning can be done on a PCA
• In EC-PCA, the profit center is the lowest level at which you measure financial results
• Since CS-PCA is only complete at the end of the month, CS-PCA data in only rolled up to CS via FI-SL (Special Ledger) monthly.
Accounting Data Flows:
1. Real time data flows
2. Periodic data flows
EC-CS – Enterprise Controlling Consolidations
• Manual Entries
• EC-PCA – Enterprise Controlling Profit center accounting
o FI Balance Sheet Items
(1). SD, MM, PP, FI Journal Entries
FI Period End Update – Balance Sheet Sub Ledgers
- SD, MM, PP, FI Journal Entries
CO-OH
o FI P&L
- SD, MM, PP, FI Journal Entries
CO-Allocations
CO-PA
o FI P&L External Revenue and Cost of Sales
- SD, MM, PP, FI Journal Entries
By Rajagopalan M
