The document outlines the agenda for Day 5 of an SAP FI bootcamp, which includes reviewing integration between FI and other SAP modules like MM, SD, and CO. It provides details on how purchasing and sales transactions are processed in MM and SD respectively, and how the accounting entries are automatically posted to FI during goods movement, invoice verification, billing, and payment. It also explains how cost and revenue data flows from FI to Controlling (CO) for internal reporting.
SAP FICO General Ledger EndUser Training | www.sapdocs.infosapdocs. info
You can download this material from http://sapdocs.info/sap/fico/download-sap-general-ledger-accounting-enduser-training-ppt-material/
Get more SAP Materials from http://sapdocs.info/sap/
Blogs on Document Splitting at www.veritysolutions.com.au
Document Splitting is a very powerful feature delivered by SAP ECC.
Previous to SAP ECC, if new fields were required to General Ledger SAP had to deliver these new fields in Special Purpose Ledger tables. Profit Centre Accounting in R3 was Special Purpose Ledger table 8*, Joint Venture Accounting was ledger 4*. This essentially meant that data had to be copied from General Ledger table GLT0 to special ledger tables so these could be reported upon. However, technical glitches in code and incorrect usage of functionalities caused imbalances between the main ledger GLT0 and the special purpose ledgers.
SAP customers who wanted to expand the functionality of General Ledger to cater to special business requirements (like reporting General Ledger with another fiscal year variant) had to create custom Special Purpose Ledger tables. For example, if a customer wanted to report by two fiscal year variants, they could report one variant using General Ledger and the other variant using Special Purpose Ledger.
All this disparate ledgers reported the same source information in different views. Customers had to execute several month end jobs to ensure synchronisation of data across all these ledgers. Differences in balances and information between ledgers led to delays in month end close and reporting.
With SAP ECC new GL, SAP Customers can add new fields (which SAP calls “scenarios”) into General Ledger. This allows customers to perform, for example, Profit Centre Accounting and Reporting within General Ledger.
With SAP ECC new GL, SAP Customers can add new ledgers (which SAP calls “parallel accounting”) into General Ledger. This allows customers to report, for example, the same General Ledger data in multiple fiscal year variants.
This replication of data happens in real-time. SAP customers no longer need to execute month end jobs to synchronise data between different ledgers.
This document provides instructions for configuring a company code in SAP FICO. It begins with an introduction to SAP FI and relevant terminology. It then outlines the steps to define a company, create a company code, assign the company code to a company and chart of accounts, define relevant organizational structures and assign them to the company code, and configure settings for the currency, fiscal year, posting periods, document numbers, and more. The goal is to fully configure company code 1100 for the fictional company ABC Ltd located in the US.
Sap fi integration with other modules in sap ficowhynet2005
This document discusses the integration between SAP FI (Financials) with other SAP modules like MM (Materials Management), CO (Controlling), and SD (Sales and Distribution). It provides examples of how transactions in these modules result in automatic accounting postings to the FI module. Key points covered include defining accounts and transaction keys to integrate overhead cost allocations from CO, inventory valuations from MM, and revenue/expense accounts from SD billing documents.
This document provides information about ERP (Enterprise Resource Planning) software and SAP modules. It discusses what ERP and SAP are, key SAP concepts like the system landscape and architecture, and SAP modules like FI, CO, SD. It also covers topics like data in SAP, roles in SAP implementations, and different types of data analysis tools in SAP like dashboards, reports, and OLAP. The document is intended to provide an overview of fundamental SAP concepts for trainees.
The document provides steps for configuring SAP FI including defining the enterprise structure, accounts, financial statement versions, and documents. The key steps include defining companies, company codes, business areas, and functional areas within the enterprise structure. Additional steps cover maintaining fiscal year variants, opening and closing posting periods, defining document types, and assigning number ranges for documents. The document is a guide for administrators to fully configure the necessary master data and settings for SAP FI.
This document provides an overview of key components and features of financial accounting in SAP, including the general ledger, accounts payable, accounts receivable, asset accounting, and bank accounting. It describes the organizational structure for accounting including company codes and charts of accounts. It also lists features such as real-time integration between modules, document control functions, multicurrency support, and automatic processes for payments, depreciation, and more.
example of SAP Cut over strategy FI CO MM PS moduleCitra Nudiasari
The document discusses the cutover strategy for migrating to a new SAP system, proposing an April 2016 go-live date with an initial balance from January 2016. It notes risks like difficulty recording backlog transactions from January to March before master data is finalized. It also outlines tasks like initial balance preparation ensuring correct currencies, values and depreciation data are migrated. A project timeline is provided listing milestones from key user training to go-live support.
SAP FICO General Ledger EndUser Training | www.sapdocs.infosapdocs. info
You can download this material from http://sapdocs.info/sap/fico/download-sap-general-ledger-accounting-enduser-training-ppt-material/
Get more SAP Materials from http://sapdocs.info/sap/
Blogs on Document Splitting at www.veritysolutions.com.au
Document Splitting is a very powerful feature delivered by SAP ECC.
Previous to SAP ECC, if new fields were required to General Ledger SAP had to deliver these new fields in Special Purpose Ledger tables. Profit Centre Accounting in R3 was Special Purpose Ledger table 8*, Joint Venture Accounting was ledger 4*. This essentially meant that data had to be copied from General Ledger table GLT0 to special ledger tables so these could be reported upon. However, technical glitches in code and incorrect usage of functionalities caused imbalances between the main ledger GLT0 and the special purpose ledgers.
SAP customers who wanted to expand the functionality of General Ledger to cater to special business requirements (like reporting General Ledger with another fiscal year variant) had to create custom Special Purpose Ledger tables. For example, if a customer wanted to report by two fiscal year variants, they could report one variant using General Ledger and the other variant using Special Purpose Ledger.
All this disparate ledgers reported the same source information in different views. Customers had to execute several month end jobs to ensure synchronisation of data across all these ledgers. Differences in balances and information between ledgers led to delays in month end close and reporting.
With SAP ECC new GL, SAP Customers can add new fields (which SAP calls “scenarios”) into General Ledger. This allows customers to perform, for example, Profit Centre Accounting and Reporting within General Ledger.
With SAP ECC new GL, SAP Customers can add new ledgers (which SAP calls “parallel accounting”) into General Ledger. This allows customers to report, for example, the same General Ledger data in multiple fiscal year variants.
This replication of data happens in real-time. SAP customers no longer need to execute month end jobs to synchronise data between different ledgers.
This document provides instructions for configuring a company code in SAP FICO. It begins with an introduction to SAP FI and relevant terminology. It then outlines the steps to define a company, create a company code, assign the company code to a company and chart of accounts, define relevant organizational structures and assign them to the company code, and configure settings for the currency, fiscal year, posting periods, document numbers, and more. The goal is to fully configure company code 1100 for the fictional company ABC Ltd located in the US.
Sap fi integration with other modules in sap ficowhynet2005
This document discusses the integration between SAP FI (Financials) with other SAP modules like MM (Materials Management), CO (Controlling), and SD (Sales and Distribution). It provides examples of how transactions in these modules result in automatic accounting postings to the FI module. Key points covered include defining accounts and transaction keys to integrate overhead cost allocations from CO, inventory valuations from MM, and revenue/expense accounts from SD billing documents.
This document provides information about ERP (Enterprise Resource Planning) software and SAP modules. It discusses what ERP and SAP are, key SAP concepts like the system landscape and architecture, and SAP modules like FI, CO, SD. It also covers topics like data in SAP, roles in SAP implementations, and different types of data analysis tools in SAP like dashboards, reports, and OLAP. The document is intended to provide an overview of fundamental SAP concepts for trainees.
The document provides steps for configuring SAP FI including defining the enterprise structure, accounts, financial statement versions, and documents. The key steps include defining companies, company codes, business areas, and functional areas within the enterprise structure. Additional steps cover maintaining fiscal year variants, opening and closing posting periods, defining document types, and assigning number ranges for documents. The document is a guide for administrators to fully configure the necessary master data and settings for SAP FI.
This document provides an overview of key components and features of financial accounting in SAP, including the general ledger, accounts payable, accounts receivable, asset accounting, and bank accounting. It describes the organizational structure for accounting including company codes and charts of accounts. It also lists features such as real-time integration between modules, document control functions, multicurrency support, and automatic processes for payments, depreciation, and more.
example of SAP Cut over strategy FI CO MM PS moduleCitra Nudiasari
The document discusses the cutover strategy for migrating to a new SAP system, proposing an April 2016 go-live date with an initial balance from January 2016. It notes risks like difficulty recording backlog transactions from January to March before master data is finalized. It also outlines tasks like initial balance preparation ensuring correct currencies, values and depreciation data are migrated. A project timeline is provided listing milestones from key user training to go-live support.
In sap we have two types of bank statement are there:
Manual Bank Statement
Electronic Bank Statement
If you receive an electronic statement then you just need to upload it to sap for the purpose of
preparation of bank reconciliation statement. If it is manual one then you need to enter the
statement manually into sap.
This document provides instructions for configuring automatic postings in an ERP system for inventory management and invoice verification transactions. Key steps include defining valuation levels, charts of accounts, valuation grouping codes, valuation classes, and account groupings. The system can then simulate postings to automatically determine the correct GL accounts based on these definitions and the transaction type. Definitions must be made for each chart of accounts and valuation grouping code combination.
This document summarizes key concepts and configuration related to purchasing and materials management in SAP S/4HANA. It covers areas like purchasing document types, material statuses, valuation, pricing procedures, and document flows. The document is structured with headings for key purchasing entities like material, vendor, plant, valuation area and provides details on attributes and relationships between these entities for purchasing, inventory valuation and related business processes in S/4HANA.
- Depreciation accounts reduce the value of assets over time by allocating costs to different periods. Accumulated depreciation accounts track total depreciation taken on an asset to date to calculate its current book value.
- When depreciation is posted, the depreciation account debits accumulated depreciation and credits the depreciation expense account. The depreciation expense is then posted to the profit and loss account to calculate net income.
- In the balance sheet, assets are reported at their historical acquisition cost less any accumulated depreciation to date to show their current value.
This presentation covers the basic modules of Financial accouting of SAP FICO module.This is for presentation purpose and doesn't serve as a full fledged presentation on SAP FI
Asset acquisitions can be posted in Asset Accounting integrated with accounts payable, without a purchase order link, through materials management for self-produced assets, or by capitalizing production costs through investment management. The asset value date determines the capitalization and depreciation start dates and affects planned depreciation amounts.
SAP Accounts Reveivable Functions | http://sapdocs.infosapdocs. info
This document provides an overview of key functions in the accounts receivable module in SAP, including:
1) Editing options and defaults that can be set for open item processing and credit management.
2) Customer line item management and open item management, including displaying line items and balances.
3) Processing open items by clearing customers, posting with clearing, or posting incoming payments manually.
4) Handling bank returned payments and resetting cleared items.
5) Posting transactions without clearing, for transfers or other receivables.
The document provides an overview of organizational structure options in SAP, including definitions of key elements like company code, sales organization, and purchasing organization. It discusses considerations for choosing between a simple or complex organizational structure, with a simple structure minimizing data maintenance and processing while a complex structure allows for more autonomous regional operations. Examples of each type of structure are presented to illustrate how the different elements can be configured.
S4 HANA Finance course contents
For more details & Online Training , mail me at pradeephota.sap@gmail.com
Watsup- 9437141137
Free Videos
https://www.youtube.com/channel/UCIuai9zASMANOi0netwDd7w?view_as=subscriber
The document provides an overview of new features and changes being introduced in New Asset Accounting in SAP S/4HANA. Key points include: depreciation is now posted per asset rather than in aggregate; reconciliation between FI and AA is integrated by design; a technical clearing account is used for asset acquisition postings; the migration process involves customizing, moving legacy data to the SAP Simple Finance add-on, and activating the new accounting functionality. Various transactions and programs from the previous asset accounting are no longer available.
Enterprise structures in SAP FICO include defining companies, company codes, business areas, and assigning them. This establishes the organizational units for accounting and reporting. Key steps include defining the chart of accounts, account groups, and creating general ledger master records at the central, company code, or individual level. Proper enterprise structuring in SAP FICO ensures complete and accurate accounting data across the organization.
1. The document describes a request for a functional specification (spec) for a new sales tax report. The spec would include business requirements, data needs, and processing logic to guide development.
2. A functional spec provides details on user inputs, outputs, and how the application should work. It streamlines development by informing programmers of the user experience design.
3. This spec example outlines sections for a report definition, functional requirements, processing logic, and output format. It describes needed fields, tables, and the report flow to retrieve the required data.
1. Company code 6600 for Universal Ltd. USA is created with currency as USD and country as US.
2. Fiscal year variant V3 (April to March) is used for company code 6600.
3. Posting period variant 6600 is created and assigned to company code 6600. Time intervals are defined to open and close posting periods for various account types like GL, AR, AP etc.
4. Preparations for defining field status variants and assigning them to company codes are explained. Standard SAP variant 0001 is used initially for new company codes.
This document discusses configuration steps for business partner setup in SAP S/4HANA. It explains that transaction codes for customer/vendor maintenance are obsolete and the BP transaction should be used instead. The steps include activating synchronization objects, defining business partner roles and categories, and configuring views and screen sequences to define which data is displayed for each role.
A presentation on Asset Management in SAP. It includes important definitions, types of assets, asset life cycle, month-end activities and year-end activities.
The document provides an overview of accounts receivable processes in SAP, including master data, credit management, invoice processing, cash receipting, and periodic processing. It describes setting up customer accounts, credit limits, and payment terms. The key processes covered are creating invoices, debit/credit memos, parked documents, and intercompany postings. Reports and periodic jobs are listed for managing accounts receivable.
The document provides an overview of the accounts payable process in SAP, including master data, invoice processing, payments, account analysis and reconciliation, and reporting. Key steps include maintaining vendor master records, entering invoices, processing payments, reconciling accounts, and generating reports. Special processes like foreign currency transactions, reversals, and intercompany billing are also summarized.
Understanding SAP Enterprise Structure in SAP FISAP XPERT
The document describes the company code and organizational structure of John Woolworths supermarket chain. It discusses that John Woolworths has four companies located in the US and Canada, and four business areas. It also provides steps to define the company code, company, business area, and segment in SAP using transaction codes.
Validation checks values entered by the user and substitutes incorrect values, while substitution removes incorrect values entered by the user. Validations can be applied at the document header, line item, and master data level to check for values like company code and business area. Substitutions can also be applied at various levels to replace values like profit centers or business areas. Both validations and substitutions use user exits and can be transported between systems after configuration.
The document provides an agenda and overview for a 5-day SAP Financial Accounting and Reporting bootcamp. Day 1 will cover an introduction to financial accounting, the general ledger including master data setup, enterprise structure, and basic transactions. Master data includes chart of accounts, account groups, field status groups, and configuration of general ledger accounts. Enterprise structure establishes the "where" of transactions using company codes.
This document provides an overview of how financial activities from other SAP modules are integrated with the SAP FI (Financials) module. It discusses the integration of FI with Materials Management (MM), Sales and Distribution (SD), and Controlling (CO). For MM, it describes the procure to pay process including master data, purchase orders, goods movement, and invoice verification. For SD, it discusses sales order processing, revenue account determination, and billing/invoicing. It also provides an overview of transaction types between FI and CO for accounting and cost allocation.
In sap we have two types of bank statement are there:
Manual Bank Statement
Electronic Bank Statement
If you receive an electronic statement then you just need to upload it to sap for the purpose of
preparation of bank reconciliation statement. If it is manual one then you need to enter the
statement manually into sap.
This document provides instructions for configuring automatic postings in an ERP system for inventory management and invoice verification transactions. Key steps include defining valuation levels, charts of accounts, valuation grouping codes, valuation classes, and account groupings. The system can then simulate postings to automatically determine the correct GL accounts based on these definitions and the transaction type. Definitions must be made for each chart of accounts and valuation grouping code combination.
This document summarizes key concepts and configuration related to purchasing and materials management in SAP S/4HANA. It covers areas like purchasing document types, material statuses, valuation, pricing procedures, and document flows. The document is structured with headings for key purchasing entities like material, vendor, plant, valuation area and provides details on attributes and relationships between these entities for purchasing, inventory valuation and related business processes in S/4HANA.
- Depreciation accounts reduce the value of assets over time by allocating costs to different periods. Accumulated depreciation accounts track total depreciation taken on an asset to date to calculate its current book value.
- When depreciation is posted, the depreciation account debits accumulated depreciation and credits the depreciation expense account. The depreciation expense is then posted to the profit and loss account to calculate net income.
- In the balance sheet, assets are reported at their historical acquisition cost less any accumulated depreciation to date to show their current value.
This presentation covers the basic modules of Financial accouting of SAP FICO module.This is for presentation purpose and doesn't serve as a full fledged presentation on SAP FI
Asset acquisitions can be posted in Asset Accounting integrated with accounts payable, without a purchase order link, through materials management for self-produced assets, or by capitalizing production costs through investment management. The asset value date determines the capitalization and depreciation start dates and affects planned depreciation amounts.
SAP Accounts Reveivable Functions | http://sapdocs.infosapdocs. info
This document provides an overview of key functions in the accounts receivable module in SAP, including:
1) Editing options and defaults that can be set for open item processing and credit management.
2) Customer line item management and open item management, including displaying line items and balances.
3) Processing open items by clearing customers, posting with clearing, or posting incoming payments manually.
4) Handling bank returned payments and resetting cleared items.
5) Posting transactions without clearing, for transfers or other receivables.
The document provides an overview of organizational structure options in SAP, including definitions of key elements like company code, sales organization, and purchasing organization. It discusses considerations for choosing between a simple or complex organizational structure, with a simple structure minimizing data maintenance and processing while a complex structure allows for more autonomous regional operations. Examples of each type of structure are presented to illustrate how the different elements can be configured.
S4 HANA Finance course contents
For more details & Online Training , mail me at pradeephota.sap@gmail.com
Watsup- 9437141137
Free Videos
https://www.youtube.com/channel/UCIuai9zASMANOi0netwDd7w?view_as=subscriber
The document provides an overview of new features and changes being introduced in New Asset Accounting in SAP S/4HANA. Key points include: depreciation is now posted per asset rather than in aggregate; reconciliation between FI and AA is integrated by design; a technical clearing account is used for asset acquisition postings; the migration process involves customizing, moving legacy data to the SAP Simple Finance add-on, and activating the new accounting functionality. Various transactions and programs from the previous asset accounting are no longer available.
Enterprise structures in SAP FICO include defining companies, company codes, business areas, and assigning them. This establishes the organizational units for accounting and reporting. Key steps include defining the chart of accounts, account groups, and creating general ledger master records at the central, company code, or individual level. Proper enterprise structuring in SAP FICO ensures complete and accurate accounting data across the organization.
1. The document describes a request for a functional specification (spec) for a new sales tax report. The spec would include business requirements, data needs, and processing logic to guide development.
2. A functional spec provides details on user inputs, outputs, and how the application should work. It streamlines development by informing programmers of the user experience design.
3. This spec example outlines sections for a report definition, functional requirements, processing logic, and output format. It describes needed fields, tables, and the report flow to retrieve the required data.
1. Company code 6600 for Universal Ltd. USA is created with currency as USD and country as US.
2. Fiscal year variant V3 (April to March) is used for company code 6600.
3. Posting period variant 6600 is created and assigned to company code 6600. Time intervals are defined to open and close posting periods for various account types like GL, AR, AP etc.
4. Preparations for defining field status variants and assigning them to company codes are explained. Standard SAP variant 0001 is used initially for new company codes.
This document discusses configuration steps for business partner setup in SAP S/4HANA. It explains that transaction codes for customer/vendor maintenance are obsolete and the BP transaction should be used instead. The steps include activating synchronization objects, defining business partner roles and categories, and configuring views and screen sequences to define which data is displayed for each role.
A presentation on Asset Management in SAP. It includes important definitions, types of assets, asset life cycle, month-end activities and year-end activities.
The document provides an overview of accounts receivable processes in SAP, including master data, credit management, invoice processing, cash receipting, and periodic processing. It describes setting up customer accounts, credit limits, and payment terms. The key processes covered are creating invoices, debit/credit memos, parked documents, and intercompany postings. Reports and periodic jobs are listed for managing accounts receivable.
The document provides an overview of the accounts payable process in SAP, including master data, invoice processing, payments, account analysis and reconciliation, and reporting. Key steps include maintaining vendor master records, entering invoices, processing payments, reconciling accounts, and generating reports. Special processes like foreign currency transactions, reversals, and intercompany billing are also summarized.
Understanding SAP Enterprise Structure in SAP FISAP XPERT
The document describes the company code and organizational structure of John Woolworths supermarket chain. It discusses that John Woolworths has four companies located in the US and Canada, and four business areas. It also provides steps to define the company code, company, business area, and segment in SAP using transaction codes.
Validation checks values entered by the user and substitutes incorrect values, while substitution removes incorrect values entered by the user. Validations can be applied at the document header, line item, and master data level to check for values like company code and business area. Substitutions can also be applied at various levels to replace values like profit centers or business areas. Both validations and substitutions use user exits and can be transported between systems after configuration.
The document provides an agenda and overview for a 5-day SAP Financial Accounting and Reporting bootcamp. Day 1 will cover an introduction to financial accounting, the general ledger including master data setup, enterprise structure, and basic transactions. Master data includes chart of accounts, account groups, field status groups, and configuration of general ledger accounts. Enterprise structure establishes the "where" of transactions using company codes.
This document provides an overview of how financial activities from other SAP modules are integrated with the SAP FI (Financials) module. It discusses the integration of FI with Materials Management (MM), Sales and Distribution (SD), and Controlling (CO). For MM, it describes the procure to pay process including master data, purchase orders, goods movement, and invoice verification. For SD, it discusses sales order processing, revenue account determination, and billing/invoicing. It also provides an overview of transaction types between FI and CO for accounting and cost allocation.
The document defines the organizational structures used in SAP's Materials Management (MM) module for procurement. Key structures include plants, storage locations, purchasing organizations, and purchasing groups. Plants represent physical or logical locations, storage locations subdivide plants for inventory management, and purchasing organizations and groups are responsible for procurement activities and reporting. The structures are hierarchical and integrated with the Finance module for procurement and accounting.
The document discusses Sales Order Management in SAP R/3. It describes the key organizational elements in SAP R/3 like client, company code, sales organization, etc. It then explains the sales order cycle from pre-sales activities to payment. Master data is critical for sales order processing. When an order is created, data is copied from customer, material, and pricing masters. Shipping point and route determine delivery dates. Stock availability is checked using backward or forward scheduling. Deliveries are created from sales orders and picking involves transfer orders. Billing can be split or collective.
This document provides an overview of SAP MM (Materials Management) including key concepts like the procurement process, inventory management, invoicing, valuation, materials requirements planning, and implementation milestones. It describes the basic functions of MM like master data setup, purchasing documents, goods movement, invoice verification, and price planning. It also gives examples of how procurement is different for stock and non-stock items, and how materials requirements are planned and replenished through purchase orders and requisitions.
The document provides an overview of business processes and transactions cycles. It discusses the key activities in each cycle, including acquiring capital, purchasing inventory, selling goods, collecting payment from customers, and paying employees and vendors. Each activity requires different types of information from internal and external sources. An effective accounting information system needs to integrate information from different sources. The main transaction cycles discussed are the revenue, expenditure, production, human resources/payroll, and financing cycles.
SAP_Inventory_Management_Overview_PPT v1.1Deb Martina
This document provides an overview of inventory management processes in SAP. It discusses how goods receipts, goods issues, and transfer postings are used to manage material movements both externally and internally. Material documents are generated during goods movements and serve as a record of transactions. Master data such as material, vendor, and purchasing info records must be accurate to ensure efficient transaction processing.
This document provides an overview of SAP MM (Materials Management). It discusses the key components and processes in SAP MM including master data, procurement, inventory management, invoicing, valuation, materials requirements planning, and implementation milestones. The procurement process involves activities from requisitioning to payment. Inventory management covers goods movements, stock updates, and document creation. Invoicing can be done based on purchase order or goods receipt. Valuation determines price and account updates. MRP generates planned orders to fulfill material requirements.
SAP_MM_ ERP System with explanationIntroduction.pptVilas97
This document provides an overview of SAP MM (Materials Management). It discusses the key components and processes in SAP MM including master data, procurement, inventory management, invoicing, valuation, materials requirements planning, and implementation milestones. The procurement process involves activities from requisitioning to payment. Inventory management covers goods movements, stock updates, and document creation. Invoicing can be done based on purchase order or goods receipt. Valuation determines price and account updates. MRP generates planned orders to fulfill material requirements.
Overcoming the Top 7 Intercompany Accounting Challenges in SAP ERP FinancialsSAPinsider Events
View this session from Financials 2015 in Las Vegas. Coming to Europe! www.Financials2015.com
Overcoming the Top 7 Intercompany Accounting Challenges in SAP ERP Financials by David Cohen, EY
This session will outline and provide resolutions for the seven most common intercompany accounting challenges that companies face within the areas of sale of products, charge of services, AP/AR reconciliation, profit elimination, assets transactions, and month-end closings. By attending you will receive:
- Practical examples on the most effective ways to use standard functionality of SAP ERP, SAP BusinessObjects BI, and SAP HANA to alleviate these issues
- Examples of overcoming difficulties in implementing asset transactions across borders, such as purchase and leasing
- Alternatives to performing inter-company profit elimination
- Lessons for configuring and running your month-end close
An enterprise is a group with common goals and resources to achieve those goals. Businesses have departments that communicate and exchange data. ERP systems integrate business functions like marketing, supply chain, accounting, and HR into a single system. This allows processes like order to cash to flow seamlessly across departments. ERP replaces legacy functional systems and centralized data to increase efficiency and provide real-time information. Challenges include the difficulty of implementation and requiring changes to business processes. ERP careers include functional, technical, and techno-functional consulting roles.
Sales and distribution is a core ERP module that automates the key processes involved in taking customer orders and delivering products. These include sales order processing, inventory sourcing, shipping, billing, payment collection, and analytics to improve marketing and sales strategies. ERP systems help by integrating these processes, proposing default data, tracking activities from inquiries to delivery, and automatically updating accounts.
This document provides an overview of SAP's Finance & Controlling (FICO) module. It describes the main components and objectives of the Finance (FI) and Controlling (CO) modules. In FI, the goals are to record financial transactions and generate standard financial reports. In CO, the goals are internal reporting and analysis to support decision making. Both modules use organizational objects like company code and cost centers. FI maps revenue accounts to revenue elements, while CO maps expense accounts to cost elements to classify costs. CO also performs cost allocations between cost objects using statistical key figures.
This document provides an agenda and overview for Day 3 of an SAP FI bootcamp. The day will include a review of the previous day's topics, as well as covering accounts payable master data, invoice processing, payment processing, and bank account reconciliation in SAP FI. Participants will work in teams to review a topic from the previous day and create a presentation and questions. Exercises are included to demonstrate creating and maintaining vendor master records, processing purchase order and non-purchase order based invoices, and resolving blocked invoices.
The document discusses the organizational structure in SAP R/3. It describes how the system is structured with clients, company codes, business areas, plants, sales organizations, and other units. It also provides an overview of the key modules in SAP R/3 including financial accounting, logistics, human resources, and their subcomponents. Financial accounting is linked to other modules and uses a double-entry accounting approach with documents, master records, and general ledger accounts.
Measuring Long-Run and Nonfinancial Organizational Performancenarman1402
This document discusses measuring organizational performance, both financial and non-financial, in the long-run. It covers the importance of vision and mission statements in guiding long-term objectives. Non-financial measures like throughput, quality, and lead time are important to consider alongside financial metrics. Activity-based management can help optimize processes. Measuring multinational performance is challenging due to differing business environments. The balanced scorecard approach integrates measures across key areas like customers, internal processes, innovation and financials. Sample manufacturing performance indicators are also provided.
The document describes IcSoft, a business software that provides ERP and manufacturing execution system capabilities. Key features include user-defined fields, barcode support, direct data entry from devices, document management, multi-currency accounting, customizability, paperless office functionality, statistical process control, plant maintenance, and integrated reporting. The software allows for rapid implementation between 3-6 months and supports lean manufacturing practices. It provides functionality across standard business areas like sales, purchasing, inventory, quality control, and finance.
Computer information systems project on real estate software - KiloBytes Real...Krupesh Shah
This document presents a proposal for a computer information system called KiloBytes' Realty Redefined from a group of 5 students. The proposed system aims to address problems faced by real estate developers like tracking marketing expenses, sales activities, payments, and inventory. It would be a web-based ERP system with modules for pre-sales, post-sales, engineering/purchasing, accounts. The system would allow for lead management, project setup, booking management, payment scheduling, procurement, and generate various reports. It promises benefits like being web-based, compatible with all devices, integrating with their website and accounts software, and being a powerful marketing and reporting tool.
Product lifecycle management (PLM) refers to managing data and processes across the entire lifecycle of a product, from design to retirement, including engineering, manufacturing, and supply chain. PLM software provides a centralized system to expedite product development and collaboration. It evolved from focusing only on internal engineering to including other departments like marketing, sales, and customers. Cloud-based PLM allows real-time collaboration regardless of user location. Supply chain management (SCM) aims to efficiently manage the flow of goods and services from raw materials to the customer. The five key elements are planning, sourcing, manufacturing, delivery, and returns. General ledger (GL) software tracks financial transactions and generates financial reports. It requires setting up
Improving the viability of probiotics by encapsulation methods for developmen...Open Access Research Paper
The popularity of functional foods among scientists and common people has been increasing day by day. Awareness and modernization make the consumer think better regarding food and nutrition. Now a day’s individual knows very well about the relation between food consumption and disease prevalence. Humans have a diversity of microbes in the gut that together form the gut microflora. Probiotics are the health-promoting live microbial cells improve host health through gut and brain connection and fighting against harmful bacteria. Bifidobacterium and Lactobacillus are the two bacterial genera which are considered to be probiotic. These good bacteria are facing challenges of viability. There are so many factors such as sensitivity to heat, pH, acidity, osmotic effect, mechanical shear, chemical components, freezing and storage time as well which affects the viability of probiotics in the dairy food matrix as well as in the gut. Multiple efforts have been done in the past and ongoing in present for these beneficial microbial population stability until their destination in the gut. One of a useful technique known as microencapsulation makes the probiotic effective in the diversified conditions and maintain these microbe’s community to the optimum level for achieving targeted benefits. Dairy products are found to be an ideal vehicle for probiotic incorporation. It has been seen that the encapsulated microbial cells show higher viability than the free cells in different processing and storage conditions as well as against bile salts in the gut. They make the food functional when incorporated, without affecting the product sensory characteristics.
Microbial characterisation and identification, and potability of River Kuywa ...Open Access Research Paper
Water contamination is one of the major causes of water borne diseases worldwide. In Kenya, approximately 43% of people lack access to potable water due to human contamination. River Kuywa water is currently experiencing contamination due to human activities. Its water is widely used for domestic, agricultural, industrial and recreational purposes. This study aimed at characterizing bacteria and fungi in river Kuywa water. Water samples were randomly collected from four sites of the river: site A (Matisi), site B (Ngwelo), site C (Nzoia water pump) and site D (Chalicha), during the dry season (January-March 2018) and wet season (April-July 2018) and were transported to Maseno University Microbiology and plant pathology laboratory for analysis. The characterization and identification of bacteria and fungi were carried out using standard microbiological techniques. Nine bacterial genera and three fungi were identified from Kuywa river water. Clostridium spp., Staphylococcus spp., Enterobacter spp., Streptococcus spp., E. coli, Klebsiella spp., Shigella spp., Proteus spp. and Salmonella spp. Fungi were Fusarium oxysporum, Aspergillus flavus complex and Penicillium species. Wet season recorded highest bacterial and fungal counts (6.61-7.66 and 3.83-6.75cfu/ml) respectively. The results indicated that the river Kuywa water is polluted and therefore unsafe for human consumption before treatment. It is therefore recommended that the communities to ensure that they boil water especially for drinking.
Optimizing Post Remediation Groundwater Performance with Enhanced Microbiolog...Joshua Orris
Results of geophysics and pneumatic injection pilot tests during 2003 – 2007 yielded significant positive results for injection delivery design and contaminant mass treatment, resulting in permanent shut-down of an existing groundwater Pump & Treat system.
Accessible source areas were subsequently removed (2011) by soil excavation and treated with the placement of Emulsified Vegetable Oil EVO and zero-valent iron ZVI to accelerate treatment of impacted groundwater in overburden and weathered fractured bedrock. Post pilot test and post remediation groundwater monitoring has included analyses of CVOCs, organic fatty acids, dissolved gases and QuantArray® -Chlor to quantify key microorganisms (e.g., Dehalococcoides, Dehalobacter, etc.) and functional genes (e.g., vinyl chloride reductase, methane monooxygenase, etc.) to assess potential for reductive dechlorination and aerobic cometabolism of CVOCs.
In 2022, the first commercial application of MetaArray™ was performed at the site. MetaArray™ utilizes statistical analysis, such as principal component analysis and multivariate analysis to provide evidence that reductive dechlorination is active or even that it is slowing. This creates actionable data allowing users to save money by making important site management decisions earlier.
The results of the MetaArray™ analysis’ support vector machine (SVM) identified groundwater monitoring wells with a 80% confidence that were characterized as either Limited for Reductive Decholorination or had a High Reductive Reduction Dechlorination potential. The results of MetaArray™ will be used to further optimize the site’s post remediation monitoring program for monitored natural attenuation.
Evolving Lifecycles with High Resolution Site Characterization (HRSC) and 3-D...Joshua Orris
The incorporation of a 3DCSM and completion of HRSC provided a tool for enhanced, data-driven, decisions to support a change in remediation closure strategies. Currently, an approved pilot study has been obtained to shut-down the remediation systems (ISCO, P&T) and conduct a hydraulic study under non-pumping conditions. A separate micro-biological bench scale treatability study was competed that yielded positive results for an emerging innovative technology. As a result, a field pilot study has commenced with results expected in nine-twelve months. With the results of the hydraulic study, field pilot studies and an updated risk assessment leading site monitoring optimization cost lifecycle savings upwards of $15MM towards an alternatively evolved best available technology remediation closure strategy.
Presented by The Global Peatlands Assessment: Mapping, Policy, and Action at GLF Peatlands 2024 - The Global Peatlands Assessment: Mapping, Policy, and Action
Epcon is One of the World's leading Manufacturing Companies.EpconLP
Epcon is One of the World's leading Manufacturing Companies. With over 4000 installations worldwide, EPCON has been pioneering new techniques since 1977 that have become industry standards now. Founded in 1977, Epcon has grown from a one-man operation to a global leader in developing and manufacturing innovative air pollution control technology and industrial heating equipment.
ENVIRONMENT~ Renewable Energy Sources and their future prospects.tiwarimanvi3129
This presentation is for us to know that how our Environment need Attention for protection of our natural resources which are depleted day by day that's why we need to take time and shift our attention to renewable energy sources instead of non-renewable sources which are better and Eco-friendly for our environment. these renewable energy sources are so helpful for our planet and for every living organism which depends on environment.
Climate Change All over the World .pptxsairaanwer024
Climate change refers to significant and lasting changes in the average weather patterns over periods ranging from decades to millions of years. It encompasses both global warming driven by human emissions of greenhouse gases and the resulting large-scale shifts in weather patterns. While climate change is a natural phenomenon, human activities, particularly since the Industrial Revolution, have accelerated its pace and intensity
2. 2
• Review of Day 4
• Integration with Other Modules
– Overview
– Integration with Material Management (MM)
– Integration with Sales and Distribution (SD)
– Integration with Controlling (CO)
• Case Studies
• Accenture Delivery Method (ADM)
• Course Closing
Agenda – Day 5
3. 3
• We covered the following topics on Day 4:
– Asset Accounting – Key Concepts & Organisation
Structure
– Asset Accounting – Master Data
– Asset Accounting – Business Transactions
– Asset Accounting – Period End Closing & Reporting
– New GL Online Document Splitting
Review of Day 4
4. 4
• Review of Day 4
• Integration with Other Modules
– Overview
– Integration with Material Management (MM)
– Integration with Sales and Distribution (SD)
– Integration with Controlling (CO)
• Case Studies
• Accenture Delivery Method (ADM)
• Course Closing
Agenda – Day 5
5. 5
R/3
Client / Server
ABAP/4
IS
Industry
Solutions
MM
Materials
Mgmt.
PDPersonnel
Development
SD
Sales &
Distribution
PP
Production
Planning
QM
Quality
Manage-
ment PM
Plant
Maintenance
FI
Financial
Accounting
CO
Controlling
TR
Treasury
PS
Project
System
WF
Workflow
EC
Enterprise
Controlling
IM
Investment
Management
PA
Personnel
Administration
Source: SAP AC010: Financial Accounting & Reporting
• Financial activities from other SAP modules are integrated
with FI Material Management (MM): manage
logistic processes such as purchasing
and warehouse/inventory management
Sales & Distribution (SD): manage
sales to billing processes
Plant Maintenance (PM): manage
maintenance and repair/refurbishment
processes
Project System (PS): manage
projects/WBS for both planning and
actual data
Controlling (CO): satisfy internal
reporting requirement
Not all FI integration is covered in this training session
Overview
6. 6
FI/General
Ledger
Controlling
& Reporting
Plan & Manage
Enterprise
(FI/CO)
MRP
Purchase
Order
Good
Receipt
Invoice
Verification
(A/P)
Outgoing
Payment
Vendor
Procure To
Pay
Order To
Cash
Billing
(A/R)
Credit Mgt Delivery Incoming
Payment
Sales Order Transport-
ation
Inventory
Management
Inventory
Management/
Warehouse
Management
Customer
Integration of MM, SD and FI/CO
Overview – Business Process
8. 8
• Review of Day 4
• Integration with Other Modules
– Overview
– Integration with Material Management (MM)
– Integration with Sales and Distribution (SD)
– Integration with Controlling (CO)
• Case Studies
• Accenture Delivery Method (ADM)
• Course Closing
Agenda – Day 5
9. 9
• Purchasing Master Data
– Vendor Master
– Material Master
• Procure to Pay – Purchase Order
– Account Assignment
• Procure to Pay – Goods Movement
– Automatic account determination
for goods movement (goods
receipt, goods issue, transfer)
• Procure to Pay – Invoice Verification
– Automatic account determination
for invoice verification
Good
Receipt
Invoice
Verification
(A/P)
Inventory
Management
Outgoing
Payment
FI/General
Ledger
Purchase
Order
Procure to Pay
12. 12
• Pricing control of
material: Standard
price or Moving
Average Price
• Valuation Class:
determine G/L
accounts which
needs to be updated
for goods movement
Purchasing Data – Material Master
13. 13
• Determine purchase order specification
– For example, what the purchase order is raised
for, e.g., asset, non-stock, services
– Only for non-material purchase orders
– Nature of the account assignment (cost object),
e.g., cost centre, sales order, project
– Indicates which account is used at goods receipt
and invoicing
Purchase Order – Account
Assignment
14. 14
• Determine purchase order specification
– FI posting will be created automatically based on
the account assignment and account
determination (for material purchase)
– Example:
Purchase Order – Account
Assignment (cont.)
Account Assignment = Blank (Material)
Goods Receipt
Dr. Material
Cr. GR/IR
Account Assignment = A (asset)
Goods Receipt
Dr. Asset
Cr. GR/IR
16. 16
• Determine purchase order specification
– For example, what the purchase order is raised
for, such as asset, non-stock, services
– Only for non-material purchase orders
– Nature of the account assignment, for example,
cost center, sales order, project
– Indicates which account is used at goods receipt
and invoicing
Goods Movement – Account
Determination (1 of 3)
17. 17
• Determine purchase order specification (cont.)
– FI posting will be created automatically based on
the account assignment and account
determination (for material purchase)
– Example:
Goods Movement – Account
Determination (2 of 3)
Account Assignment = Blank (Material)
Goods Receipt
Dr. Material
Cr. GR/IR
Account Assignment = A (asset)
Goods Receipt
Dr. Asset
Cr. GR/IR
18. 18
• Roadmap to Automatic Posting
– Valuation Class is maintained in Material Master –
Accounting View
• For example, Material 100-401 with Valuation class 7900
– Account determination has been configured for
movement type and valuation class
• For example, Movement Type 101 (goods receipt) for
valuation class 7900 is debited to stock account 304000
Goods Movement – Account
Determination (3 of 3)
21. 21
• When a vendor invoice is
entered through MM invoice
verification, automatic
posting is generated to FI
• If the Purchase Order is set
with goods receipt, invoice
verification is a 3-way
matching (e.g., quantity
from the goods receipt and
price/invoice amount from
the PO)
• Transaction code MIRO
Invoice Verification
22. 22
• Purchase Orders can
be drilled into from FI
invoice and vice versa
– Transaction code FB03
– Enter the FI document
number
– Go to Environment and
select Original
Document
– Click on Purchase
Order number to
display the PO
Purchase Order from FI Invoice
23. 23
• Transaction code ME23N
• Go to PO History
• Click on the Invoice
Receipt material
document
• Click on FI documents
button
• Double click on the FI
doc number to display
the accounting journal
FI Invoice from Purchase Order
26. 26
• Review of Day 4
• Integration with Other Modules
– Overview
– Integration with Material Management (MM)
– Integration with Sales and Distribution (SD)
– Integration with Controlling (CO)
• Case Studies
• Accenture Delivery Method (ADM)
• Course Closing
Agenda – Day 5
29. 29
• Credit limit is
assigned per
customer
• We can determine
when the checking
is done: order,
delivery, goods
issued, etc.
Customer Credit Management
31. 31
Condition Type determines items included in the Sales
Order, for example, material price, tax, discount, etc.
Sales Order – Revenue Account
Determination (1 of 3)
32. 32
Account key is assigned to condition type
Sales Order – Revenue Account
Determination (2 of 3)
33. 33
Account key and other parameters determine GL accounts
for automatic posting during A/R invoicing
Sales Order – Revenue Account
Determination (3 of 3)
Account key
Condition type Sales Org
34. 34
• Default profit
centre is
maintained in
Material Master
• This profit centre
will be taken to
Sales Order and
then to A/R
invoice
generated from
the Sales Order
Profit Center Assignment in
Material Master
35. 35
• When a billing document is created, the system automatically
creates all relevant accounting documents
Billing/Invoicing (1 of 3)
37. 37
• Display Billing
document from FI
Invoice:
– Transaction code
FB03
– Enter the FI
document number
– Go to Environment
and select Original
Document
Billing/Invoicing (3 of 3)
39. 39
• Review of Day 4
• Integration with Other Modules
– Overview
– Integration with Material Management (MM)
– Integration with Sales and Distribution (SD)
– Integration with Controlling (CO)
• Case Studies
• Accenture Delivery Method (ADM)
• Course Closing
Agenda – Day 5
40. 40
• Controlling (CO) and Financial Accounting (FI) are
independent components in the SAP system but
the data flow between the two components takes
place on a regular basis
• All data relevant to cost flows automatically to CO
from FI
Integration with Controlling
41. 41
• The system assigns the costs and revenues to
different CO account assignment objects like:
– Cost centres
– Business processes
– Projects or orders
• All relevant accounts in FI are managed in CO as
cost elements or revenue elements, which
enables one to compare and reconcile values
from CO and FI
Integration with Controlling (cont.)
42. 42
PROFIT & LOSS
Expense A 100
Expense B 200+300
Expense C 400
BALANCE SHEET
A/P
1000
Expense A 100 WBS Z1
Expense B 200 WBS Z1
Expense B 300 WBS Z2
Expense C 400 Cost Center Z3
Supplier X 1000
FI
CO
WBS Z2
Budget Actual Available
500 300 200
Expense A Expense B Expense C A/P
100 200
300
400 1000
Cost Center Z3
Budget Actual Available
800 400 400
WBS Z1
Budget Actual Available
1000 100+200 700
Transaction Type: Purchase
TRANSACTION TYPE: PURCHASE
43. 43
TRANSACTION TYPE: SETTLEMENT WBS Z1 to AUC WBS Z2 to CCZ3
Expense A 100 WBS Z1
Expense B 200 WBS Z1
Expense B 300 WBS Z2
Expense C 400 Cost Center Z3
Supplier X 1000
FI PROFIT & LOSS
Expense A 100
-100
Expense B 200+300
-200
Expense C 400
BALANCE SHEET
AUC 100+200
A/P 1000
Expense A Expense B Expense C A/P
100 200
300
400 1000
100 200
AUC
100+200
CO WBS Z1
Budget Actual Available
1000 100+200 700
(-100-200)
WBS Z2
Budget Actual Available
500 300 200
(-300)
Cost Center Z3
Budget Actual Available
800 400
300 100
Transaction Type: Settlement
44. 44
TRANSACTION TYPE: ALLOCATION Cost Center Z3 to WBS Z1
PROFIT & LOSS
Expense A 100
-100
Expense B 200+300
-200
Expense C 400
BALANCE SHEET
AUC 100+200
A/P 1000
Expense A 100 WBS Z1
Expense B 200 WBS Z1
Expense B 300 WBS Z2
Expense C 400 Cost Center Z3
Supplier X 1000
FI
Expense A Expense B Expense C A/P
100 200
300
400 1000
100 200
AUC
100+200
CO
WBS Z1
Budget Actual Available
1000 100+200
(-100-200)
700 0
WBS Z2
Budget Actual Available
500 300 200
(-300)
Cost Center Z3
Budget Actual Available
800 400
300
-700 800
No FI Posting
Transaction Type: Allocation
45. 45
• Display Billing
document from FI
invoice:
– Transaction code
FB03
– Enter the FI
document number
– Go to Environment
and select
Accounting
Documents
• Accounting documents consist of FI document,
Special Ledger document, Profit Centre document,
Profitability Analysis document, and CO document
Accounting Documents
46. 46
•List of Accounting
docs:
– FI document
– Profit centre
document
– Special Ledger
document
– CO document
Accounting Documents (cont.)
48. 48
• Review of Day 4
• Integration with Other Modules
– Overview
– Integration with Material Management (MM)
– Integration with Sales and Distribution (SD)
– Integration with Controlling (CO)
• Case Studies
• Accenture Delivery Method (ADM)
• Course Closing
Agenda – Day 5
49. 49
• Refer to Case Study 1 - Asset Procurement to
Payment in your Participant Workbook.
– Your task is to post the asset acquisition and the
payment.
Case Study 1 – Asset
Procurement to Payment
50. 50
• Refer to Case Study 2: Customer - Master, Invoice &
Payment in your Participant Workbook.
– Your task is to post an invoice and a correction and
post two customer payments.
Case Study 2 – Customer –
Master Invoice & Payment
52. 52
• Review of Day 4
• Integration with Other Modules
– Overview
– Integration with Material Management (MM)
– Integration with Sales and Distribution (SD)
– Integration with Controlling (CO)
• Case Studies
• Accenture Delivery Method (ADM)
• Course Closing
Agenda – Day 5
53. 53
Accenture Delivery Suite (1 of 3)
• The Accenture Delivery Suite
provides an integrated set of
methods, tools and architectures
to support systems delivery.
Accenture
Delivery Methods
Accenture
Delivery Tools
Accenture
Delivery Architecture
Accenture
Delivery Metrics
Accenture Delivery Suite
• The Accenture Delivery
Methods are proven processes,
deliverables and techniques that
enable global teams to define
what to do and how to do it.
Accenture Delivery Methods are
an integral part of the Accenture
Delivery Suite.
54. 54
Accenture Delivery Suite (2 of 3)
• The Accenture Delivery Tools
is a recommended toolset,
comprised of vendor-provided
tools and internally developed
Accenture tools, designed to
address key points across the
development life cycle and
support end-to-end solutions
delivery.
Accenture
Delivery Methods
Accenture
Delivery Tools
Accenture
Delivery Architecture
Accenture
Delivery Metrics
Accenture Delivery Suite
55. 55
Accenture Delivery Suite (3 of 3)
• The Accenture Delivery
Architectures are technical
architectures that provide proven
structured application frameworks
and reusable components to guide
developers on the most efficient
way to build a robust net centric
application.
• The Accenture Delivery Metrics
provide a core set of metrics to
measure key engagement delivery
processes.
Accenture
Delivery Methods
Accenture
Delivery Tools
Accenture
Delivery Architecture
Accenture
Delivery Metrics
Accenture Delivery Suite
56. 56
Accenture Delivery
Methods (ADM)
• A comprehensive library of
methods that supports multiple
types of work (for example,
custom development, package
implementations and
outsourcing)
• Focused on the fundamentals
and discipline, especially
around program and project
management
Accenture Delivery Methods
Accenture
Delivery Methods
Accenture
Delivery Tools
Accenture
Delivery Architecture
Accenture
Delivery Metrics
Accenture Delivery Suite
57. 57
Accenture Delivery
Methods (ADM) (cont.)
• Built on a common framework
to promote growth of
consistent skills
• Includes estimators for
estimating level of effort
• Includes repeatable, step-by-
step procedures to drive
consistency
• Defines standard language,
roles and deliverables
Accenture Delivery Methods
Accenture
Delivery Methods
Accenture
Delivery Tools
Accenture
Delivery Architecture
Accenture
Delivery Metrics
Accenture Delivery Suite
58. 58
Accenture Delivery
Methods: Benefits
• Strong methods, coupled with a sharp focus on process
improvement, will lead to the following benefits:
– Reduced cost
– Reduced risk
– Higher productivity
– Greater predictability & timeliness
– Higher quality
– Less rework
– Improved cross-group coordination
– More consistent skills
– High customer satisfaction
– Higher return on investment
– Meeting or exceeding expectations of management and users
59. 59
Accenture Delivery
Methods: Structure
– The vertical bars are
stages of work in a project.
• Plan, Analyze, Design,
Build, Test and Deploy
– The horizontal bars are
workstreams defined as
domain or area of work.
• Application, Technical
Architecture, Training &
Performance Support,
Service Introduction
• Structured as a matrix or stages of workstreams
60. 60
Accenture Delivery Methods
for SAP
– Complete lifecycle support
– SAP-specific terminology,
processes, roles, deliverable
templates, deliverable
samples and checklists
– Broader and more
comprehensive than SAP’s
Solution Manager
methodology by addressing
project management,
planning, deployment and
service introduction
– Proven project management
methods
• Provide support for the implementation of high-quality
SAP solutions
61. 61
Accenture Delivery Methods
for SAP (cont.)
– Includes top-down and
bottom-up estimators
– Support for process and
organisational elements of
the solution
– Supports transition of
application to maintenance/
support organisation
– Support for multi-site
development:
• Transition points
• Distributed work
guidelines
62. 62
Accenture Delivery Methods for
SAP: Usage and Scope
• When to use this method:
–You are managing a single project or one project
within a series of planned projects or releases
–You have identified the problems to solve for your
client
–You and the client agree on the key objectives of
the project
–You and the client have decided to deliver an SAP
application as the key element of the solution
63. 63
• The methodology does not cover the following:
Accenture Delivery Methods for
SAP: Usage and Scope (cont.)
– Selling the work to the client
– Strategic planning and business architecture
– Strategic change planning and management
– Program management
– Full business integration delivery, including organisational
design and development, full business process
redesign/reengineering, full content delivery and
management, full training and performance support, and
facilities and equipment concerns. Only those elements
directly related to the application are included.
– Specialised information for specific technologies or subject
matters such as J2EE, Oracle, and content management
64. 64
Accenture Delivery Methods
for SAP: Plan Stage
Plan stage
• Define Solution Blueprint
• Organise the project
(determine the business
goals, scope, and high-
level requirements of the
project)
65. 65
– PG091 Business Case
– PL081 Stakeholders Goal and Expectations
– PL101 Requirements
– PL123 Current Capability Assessment
– PL150 Solution Blueprint
– PL170 Delivery Strategy
– PL201 Requirements Traceability Matrix
– PM110 Project Plan
– PM246 Team Charter
– PM262 Roles and Responsibilities
– PM263 Project Orientation and Training Materials
– PM266 Training Needs Matrix
– PM289 Entry/Exit Criteria
• Primary deliverables for the Plan stage:
Accenture Delivery Methods
for SAP: Plan Stage (cont.)
66. 66
Accenture Delivery Methods for
SAP: Analyze Stage
Analyze stage:
• Gather, identify, analyse,
and manage the
requirements
• Evaluate packaged
software and select
technology infrastructure
components
• Determine environmental
and process needs to
support the new
capability
67. 67
• Primary deliverables for the Analyze stage:
– AP215 Fit/Gap Analysis
– AP250 RICEF Inventories
– AP260 Integration Conceptual Design
– BP310 Business Process Design
– PL101 Requirements
– PL103 Solution Metrics
– PL170 Delivery Strategy
– PL201 Requirements Traceability Matrix
– TE580 Test Plan
Accenture Delivery Methods for
SAP: Analyze Stage (cont.)
68. 68
Accenture Delivery Methods
for SAP: Design Stage
Design stage:
• Design the applications,
technical architecture,
technical infrastructure,
and application training
69. 69
– AP332 Configuration Design
– AP326 Configuration Rationale
– AP350 RICEF Functional Design
– AP360 Integration Functional Design
– AP370 Data Conversion Design
– AP481 Interface Agreement
– PL170 Delivery Strategy
– PL101 Requirements
– TE580 Test Plan
• Primary deliverables for the Design stage:
Accenture Delivery Methods
for SAP: Design Stage (cont.)
70. 70
Accenture Delivery Methods
for SAP: Build Stage
Build stage:
• Develop the applications,
technical architecture,
technical infrastructure,
and application training
71. 71
– AP332 Configuration Design
– AP370 Data Conversion Design
– AP450 RICEF Technical Design
– AP475 Integration Technical Design
– PL201 Requirements Traceability Matrix
– TE483 Common Test Data
– TE580 Test Plan
– TE598 Test Closure Memo
• Primary deliverables for Build stage:
Accenture Delivery Methods
for SAP: Build Stage (cont.)
72. 72
Accenture Delivery Methods
for SAP: Test Stage
Test stage:
• Test components built by
all workstreams
• Validate the solution with
the users
73. 73
– AP568 Mock Conversion Plan
– PL201 Requirements Traceability Matrix
– TE483 Common Test Data
– TE580 Test Plan
– TE598 Test Closure Memo
• Primary deliverables for the Test stage:
Accenture Delivery Methods
for SAP: Test Stage (cont.)
74. 74
Accenture Delivery Methods
for SAP: Deploy Stage
Deploy stage:
• Roll out the
application, technical
architecture, technical
infrastructure, and
training to the
organisation
75. 75
– DP211 Deployment Plan
– DP221 Deployment Work Plan
– DP424 Go Live Preparation Action Plan
– DP428 Go Live Support Plan
– DP679 Client Readiness Sign Off
– DP699 Handover Documents
• Primary deliverables for the Deploy stage:
Accenture Delivery Methods
for SAP: Deploy Stage (cont.)
76. 76
Business Operations Management Environment
Management
Quality Management
Service
Management
Service Provision
Manage
Contracted Work
Manage
Finance
Manage Client Relationships
Administer
Human
Resources
Manage and Report
Service
Performance
Manage
Continuous
Improvement
Manage Quality
Program
Maintain Customer
and Supplier
Relationships
Perform
Configuration
Management
Manage Facilities
and Equipment
Manage
Technology
Manage Domain Work
Execute
Problem
Resolution
Provide
Application
Support
Deliver Application Release
Manage Strategic Planning
Manage Delivery and Operations
Enable the
Organisation
Manage New
Business
Manage Work Entry
Perform
Contract
Mgmt
Execute
Service
Request
– Business Operations Management
Manage the unit, including monitoring delivery
of the service, handling finances, personnel
and client relationships
– Environment Management
Manage the facilities and the technical
infrastructure needed to run the entire unit
– Quality Management
Oversee quality audits, reviews and related
activities required of all personnel in the unit
– Service Management
Manage all service requests, new business
requests, metrics reporting and service level
agreements to ensure that the unit is meeting
its service commitments to the customer
– Service Provision
Perform the contracted service
• Provides a framework that addresses the five key business
areas needed to operate an Application Management unit
Accenture Delivery Methods for
Application Management
78. 78
1. When a purchase order is set with goods receipt,
what information is checked in the invoice
verification process?
2. What is the relevance of Condition Type in the
creation of a Sales Order?
3. How is FI-MM integrated in SAP for automatic
account posting?
4. How does the system determine the revenue
accounts for automatic posting during A/R
invoicing?
Knowledge Check
79. 79
5. Explain the difference between the Accenture
Delivery Suite (ADS) and the Accenture Delivery
Methods (ADM).
6. What are the six stages of work included in ADM?
Describe each stage.
7. Explain when it is appropriate to use ADM for SAP.
Knowledge Check
81. 81
End of Day 5 Lessons Learned
• Integration with MM - Purchasing Master Data
• Integration with MM - Purchase Order
• Integration with MM - Goods Movement
• Integration with MM - Invoice Verification
• Integration with SD - Sales Master Data
• Integration with SD - Sales Order
• Integration with SD - Billing
• Integration with CO
82. 82
• Review of Day 4
• Integration with Other Modules
– Overview
– Integration with Material Management (MM)
– Integration with Sales and Distribution (SD)
– Integration with Controlling (CO)
• Case Studies
• Accenture Delivery Method (ADM)
• Course Closing
Agenda – Day 5
83. 83
• .... A few remaining points we would like to share!
Closing Comments
84. 84
• Faculty to provide a hard copy list of key contacts
in the local region
– Key Contact Name
• Currently working at
• Previous FI experience
Key FI Contacts
85. 85
• Experts Network - https:experts.accenture.com
– Write directly to people – they will try to help as long as
the question is not too open-ended
• Experts Discussion Forums -
https:experts.accenture.com
– Post Questions in the Discussion forums
– People do help
Other FI Avenues for Assistance
86. 86
• Accenture’s SAP Home Page:
https://kx.accenture.com/Products/Pages/SAP.aspx
• The SAP homepage for the FI module is located at:
https://kx.accenture.com/Products/Pages/SAPFinan
cials-FinancialAccounting.aspx
• Search myLearning for related courses:
https:mylearning.accenture.com
Reference Materials
and Training (1 of 4)
87. 87
• SAP Internal Training
– For a list of upcoming SAP Internal Training go to:
https://kx.accenture.com/Products/Pages/SAP-
Training-InternalCourses.aspx
• SAP US IDES
– For self-study purposes, you can request access to a
self study client by completing a request form -
download form from:
https://kx.accenture.com/Products/Pages/SAP-
IDESAccess.aspx
Reference Materials
and Training (2 of 4)
88. 88
• SAP US IDES (cont.)
– Send the form to
mysap.cincinnati.request@accenture.com. The
accounts are valid for 2 months, and you can request
an extension by sending an email to the same email
address
– Please note: IDES clients are refreshed periodically;
therefore, the data you have created may be cleared.
Reference Materials
and Training (3 of 4)
89. 89
• SAP Online Help
• SAP Help Website: http://help.sap.com
• IDES Setup:
http://help.sap.com/saphelp_46c/helpdata/en/23/14b
3eafc5211d1a5760060087d1a6b/frameset.htm
Reference Materials
and Training (4 of 4)
92. 92
Lessons Learned – Course
• Overview of SAP Financial Accounting (FI)
functionalities and integration with other modules
• FI Organization structure, master data, business
transactions, and reporting
• Provide hands-on experience with basic FI business
transactions
• Provide hands-on experience with basic FI
configuration
• Share SAP project experience
Editor's Notes
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.
Z65402/Z65590 Copyright 2007 Accenture All Rights Reserved.