State of Louisiana
Upcoming SlideShare
Loading in...5
×
 

State of Louisiana

on

  • 1,540 views

 

Statistics

Views

Total Views
1,540
Views on SlideShare
1,540
Embed Views
0

Actions

Likes
1
Downloads
51
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

State of Louisiana State of Louisiana Document Transcript

  • LaGov ERP Project Business Blueprint Table of Contents – Section #3 C.  Business Intelligence Definitions ............................................................................................... 1076  1.  General Ledger ...................................................................................................................... 1083  2.  Controlling .............................................................................................................................. 1091  3.  Funds Management ............................................................................................................... 1114  4.  Accounts Payable .................................................................................................................. 1116  5.  Accounts Receivable ............................................................................................................. 1122  6.  Project Systems ..................................................................................................................... 1129  7.  Asset Accounting ................................................................................................................... 1134  8.  Grants Management .............................................................................................................. 1143  9.  Budget Preparation ................................................................................................................ 1150  10.  Grantor ................................................................................................................................... 1153  11.  Real Estate ............................................................................................................................ 1156  12.  Procurement / Contracts ........................................................................................................ 1184  13.  Stockroom / Warehouse / MRP ............................................................................................. 1205  State of Louisiana LaGov ERP Project Page 3 of 1338
  • LaGov ERP Project Business Blueprint C. Business Intelligence Definitions Introduction and Solution Architecture The Business Intelligence Summary provides a high-level summary of the purpose, function and overall structure of the analytical processes used to develop and implement the LaGov BI Release. It defines, in general terms, the functions and development approach of the proposed BI system and provides a boundary and architecture for the scope of the BI effort for the State of Louisiana LaGov project. As appropriate, the organization’s current and to-be business, and data environments were analyzed to obtain a proper context and perspective in planning and developing the LaGov BI system. The focus is to align the BI system development effort with the organization’s business objectives and other broader business, organization and IT initiatives. Background LaGov is implementing an SAP ERP that includes SAP Core Financials and Logistics modules. Functionality is comprised from several SAP major components (ECC, SRM, and CRM) plus the non-SAP system Agile Assets. In support of the analytical and reporting processes associated with these functions, the State is implementing SAP Business Intelligence (BI). The primary strategy is to leverage the SAP Standard Business Intelligence Content (described later) as well as the State’s current Business Objects infrastructure and abilities. The current Business Intelligence capability is mainly supported by the Lagniappe Data Warehouse. Lagniappe is a collection of reporting capabilities. In some cases, in particular the major mainframe applications, data is collected and loaded on a periodic basis to a client/server environment. This data is organized in a way that optimizes data retrieval for reporting purposes and is extensible. The data structure is broken into sub systems called Data Marts that group related data together. For the majority of other systems supported by Lagniappe, data is not moved to a separate reporting environment. The universe capability of Business Objects is used to report directly against the productive systems. Access to this data is controlled by the Business Objects Administrator. The Business Objects administrative tool is also used to create universes which are data maps that handle the complex relationships within the data model. The business users of this data can run standard or ad-hoc reports utilizing the Business Objects reporting tools (Web Intelligence and Crystal Reports) without having to understand the underlying architectural complexities. The present environment maintains licensing (and maintenance) for: • Business Objects Enterprise Premium XI R2 Windows CPU license - 4 CPUs • Crystal Reports Professional XI Windows Named User License - 5 (for OIS internal use only) Estimations with regard to the expanded use of Business Objects have been performed and there is indication that the State will have to work with its SAP/Business Objects vendor to ensure adequate licensing for the new system. State of Louisiana LaGov ERP Project Page 1076 of 1338
  • LaGov ERP Project Business Blueprint Recently, SAP purchased Business Objects and is in the process of incorporating much of the Business Objects functionality into its future BI releases. Current Business Intelligence Environment - Lagniappe Production Legacy Systems Legacy Universe LegacySystems Legacy Systems Systems •Web Intelligence • Iview Production Data Marts CFMS ETL AFS AGPS The systems that have been incorporated as Data Marts include • AFS Financial GL • AGPS Purchasing • CFMS Contracts All the other legacy systems are reported against by direct reads of the productive databases using the Business Objects front end. The basic strategy for dealing with the current environment is to maintain its capabilities relative to legacy systems. This will provide the State the ability to shut-down the front end of the systems that are being replaced while maintaining the ability to report against these databases for historical purposes. Usage will be monitored and when queries drop below an established threshold, the legacy system will be totally decommissioned and its data archived according to legislated and legal determinates. The current environment will also be used to access systems that are not being replaced. State of Louisiana LaGov ERP Project Page 1077 of 1338
  • LaGov ERP Project Business Blueprint With this strategy and the build out of the new SAP BI being implemented, there will be a period of co- existence until the current legacy systems run their course. LaGov To-Be Business Intelligence Architecture SAP SAP CRM SAP BI Common User ECC Front End SAP DSO BEx SRM Query Universe Infocube Directed as- Other required Lagniappe Universe Roadmap Product - TBD Remaining Non-SAP Retired Retired Marts Apps Data Extraction SAP BI provides strong support for SAP on-line transaction processing (OLTP) source data extraction by supplying pre-configured data extractors. This data is transferred to the data warehouse environment where it is summarized as needed. The Production Data Extractors (PDEs) create ABAP programs that are executed on the application server against the source OLTP system. A generic data extractor is also provided which allows for enhancements to the existing business content and customer defined ‘Z’ tables. As transaction events occur in the R/3 system, the extract source structure is updated with the new information. An extract source structure is essentially a transparent table that collects data. The data transfer is initiated by the scheduling tool to extract data from the extract source structure using Application Link Enabling (ALE) as the underlying transport mechanism. Data Staging The Staging Engine is the name given to the process of transforming, mapping and storing data from the various source systems to the Dimensional Data Model (InfoCubes) in the BI system. The staging engine allows for the transfer of transaction data, master data, and metadata and, to some degree, allows for a logical selection of delta (created or changed data) updates and refresh. The ability to capture and transfer deltas is dependent on the source system’s ability to provide a type of change log. The data from the source systems is stored in DSO objects. This allows data to be saved in a consolidated way in the technical format of BI. The transfer rules transform the data from the source system-dependent data format. The data is stored on the document level and constitutes the consolidated database for further processing in BI. Reporting is, therefore, not usually carried out on the DSOobjects at this level. However, an DSOcan be marked “reportable” to allow query development. It should be noted that this affects load performance. State of Louisiana LaGov ERP Project Page 1078 of 1338
  • LaGov ERP Project Business Blueprint Data Storage To support the multidimensional OLAP capabilities of the BI, a star schema data model is used to segregate facts and dimensions. Hierarchies and metadata also play a role in representing the data in various formats. The BI InfoCube is modeled on an extended star schema (large fact table surrounded by multiple independent dimension tables, i.e., customer, product and time to view the data). It is important to note that the dimension “master” data and descriptive texts reside externally from the base star schema so they can be shared between the InfoCubes. Data Presentation Traditionally, the Business Explorer (BEx) is the analysis and reporting tool for the SAP BI. The BEx Designer is the primary tool used to build queries based on a selection of Info Objects or predefined query templates for an InfoCube. It also provides On-line Analytical Processing (OLAP) functions to end- users (once the query is executed) to filter, drill-down, traverse hierarchies and further analyze the data. However, SAP is in the process of dramatically changing it Data Presentation Layer and is incorporating Business Objects front ends into its product. In anticipation of this as well as easing the transition from the end-users’ perspective, we will use the Business Objects suite of tools as the true data presentation layer (what the user sees). LaGov will build the queries that extract the data from the data warehouse InfoCubes and DSOs and expose that data to the Business Objects front-end where end users can continue to leverage their Business Objects knowledge. Organizational Considerations Efforts are underway to identify a comprehensive list of the end user BI community. While maintaining the Business Objects front end and ad-hoc reporting tools will reduce much of the impact of this implementation, there will still be impacts to the end user community. Change Integration As an organizational initiative, the rollout of the LaGov SAP BI effort must be carefully planned addressing various organizational issues such as stakeholder interest, knowledge transfer, training and technical support. LaGov has a Change Integration process in place and will incorporate BI processes change assessments such as: • Assessment of BI Effort Impact on Organization • Assessment of data warehouse impact on business processes • Assessment of data warehouse impact on organizational structure A critical component of a successful BI rollout is ensuring that those users of the tool are trained to the degree necessary. The following figure depicts within the pyramid, the level of BI functionality that is available. As the sophistication of use and desire for flexible reporting increases, so do the training requirements of the user. State of Louisiana LaGov ERP Project Page 1079 of 1338
  • LaGov ERP Project Business Blueprint SAP BW User Analysis Requirements High High Analytical functionality Authoring and flexibility and Ad-hoc Query 10 % Required training investment OLAP Analysis and Power Reporting and cost 20-30 % Information Consumption, Portal-based Deployment, Low and Executive Reporting Low 60-70 % Relationship of training requirements to degree of analysis Not only will end-users require tool knowledge, but many of the analysis processes themselves may change. This then has an impact on job roles and duties as well as the associated support processes. There is also an impact to the IT organization that is required to support the BI after its release. There may be a need to identify and fill new functions and positions to support the Business Intelligence environment and to protect data integrity. What is standard Business Content? SAP BI comes packaged with Standard Business Content (SBCT). Stated simplistically SBCT consists of source system extractions, transformation rules, information providers, reports, and security required to extract data from presumed sources and presented in a presumed manner to a presumed audience. Therefore, where the presumed conditions do not exist, variances are present SAP BI Business Content delivers predefined, role-based and task-oriented information models within BI. SAP BI Business Content‘s objective is to make relevant information available to specific roles within an enterprise so as to provide these users with the information they need to fulfill their daily tasks within their business. SAP Business Blueprint Summary The Business Intelligence Team met with each of the SAP Functional Area sub-teams to understand the nature and scope of each of the functional areas. Within the scope of these areas, the SAP BI Standard Business Content was reviewed to gain an understanding of how relevant the content was to LaGov. Relevant practices were further discussed in order to gain an understanding of the completeness of the best practice. Simply put, we asked, “Is the best practice relevant, and if so, are the supporting BI components adequate?” This Business Blueprint contains a Business Intelligence Definition Document (BDD) for each of the analytical and reporting processes identified as relevant. The BDD’s capture only the configurable standard content provided by SAP that is relevant to this implementation. Custom reports (RDD’s) and enhancements (EDD’s) that are necessary to fully support the reporting have been written and appear under their respective headings within this Blueprint. State of Louisiana LaGov ERP Project Page 1080 of 1338
  • LaGov ERP Project Business Blueprint General Ledger Five areas of analysis are provided including Profit and Loss Statements, Balance Sheet, and flexible Financial Statement queries. A real time remote Infocube is provided to support period end closings analysis. Substantial enhancements to the standard business content are necessary in order to support the unique reporting requirements of the State. There are six (6) specific custom reports identified. However, we have included a place marker for 218 reports used by OSRAP. These reports will need to be analyzed more during Realization to determine disposition and responsibility. Budget Preparation The standard content for dealing with Budget Preparation is provided however, this area will require a substantial number of enhancements to support the State of LA. Furthermore, there are Gaps associated with this area that will need to be resolved before a detail design can take place. In any event, support will be provided for budget development and inquiry. More than a dozen significant enhancements and query requirements have been identified. Grantor Three areas of analysis are provided including: Grantor Management Application, Agreement, and Claims. A Consolidated Data Mart (Multi-Cube) is provided that allows analysis of these areas within a single query session. Accounts Receivable The analysis of Accounts Receivable is supported from a summary and aggregate perspective as well as the provision of detailed lines items. Analysis of Payment History can be performed from a variety of perspectives. Eleven custom reports are required but at this time, no enhancements to support those custom queries have been determined. Accounts Payable The analysis of Accounts Payable is supported from a summary and aggregate perspective as well as the provision of detailed lines items. To support the five (5) custom reports in this area, two (2) enhancements will be necessary to add new fields to the existing InfoCubes. Project Systems Business Intelligence is provided for the analysis of dates and costs posted to Project Systems. Within BI, controlling functions are combined with WBS hierarchy analysis to provide flexible and comprehensive analysis of projects. Two significant enhancements have been identified to support new entities and attributes that will need to be added to the BI analysis area. An enhancement is required in the Budget and Planning analytical scenario as well. To-Date five (5) custom queries have been identified. Controlling Controlling analysis is supported by 12 Data Marts within BI including support Costs and Allocations, Activities, and Statistical Key figures in the areas of Cost Center Accounting, Overhead Orders, Activity Based Costing, and WBS costing. State of Louisiana LaGov ERP Project Page 1081 of 1338
  • LaGov ERP Project Business Blueprint Funds Management The Funds Management area of BI combines information from accounting, controlling, commitments, and budgeting to provide a comprehensive view of expenditures from various organizational, budgetary, time, and commitment perspectives. A custom report and enhancement to support revenue/expense versus budget analysis have been identified. Asset Accounting Support for analysis of Asset Accounting is comprised of collecting and reporting on asset related transactions and depreciation. Four custom reports are identified that drive an enhancement to include some Agile Asset master data in the BI so it can be analyzed in context to the financial aspects of the assets. An additional three reports are required to support retirement of assets. Grants Management The content implemented will support the analysis of Grants with respect to Networks and Status. Custom reports (4) are required to analyze funds, budget authority, and grants receipt. These custom reports require 2 enhancements to implement. Real Estate Thirteen Real Estate analysis scenarios are being implemented. Among them are evaluations of Leases, Cash Flow, Asset Valuation, Vacancies, and Contract measures. Custom reports for RE Master data have been identified. Significant enhancements will be required to support Real Estate Insurance requirements. Procurement and Contracts A good deal of BI support will be provided for the procurement function – particularly SRM. Analysis of Bids, Shopping Carts, Buyer Workloads, Spend Analysis, monitoring of the Approval Process, Accounting overviews, and Vendor Evaluation are among the analytical scenarios supported. Forty-five (45) custom or revised reports have been identified in the Procurement Area. Five (5) enhancements have been identified that are required to join data, add or enhance extractors, and create or modify InfoCubes. Inventory Management Several queries will be implemented that address Inventory Management in the area of Material and Stock movements and the analysis of slow moving items and turnover. Within the area of the MRP solution, a Multi-Cube enhancement is required to support the customized reporting. Performance Measurement and Reporting Within the GAP section of this Blueprint is a description of the options available for dealing with the State’s requirement to maintain and report performance measures. Prototype Dashboard Within the GAP section of this Blueprint is a description of the options available for dealing with the State’s requirement to build an executive dashboard. State of Louisiana LaGov ERP Project Page 1082 of 1338
  • LaGov ERP Project Business Blueprint 1. General Ledger Team: BI BDD Name: General Ledger (New) Balance Sheet Profit and Loss BIW-GL-BDD001-General Ledger (New) Balance Sheet Profit BDD Number: and Loss Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The central task of G/L accounting is to provide a comprehensive picture of external accounting and accounts. Recording all business transactions (primary postings as well as settlements from internal accounting) in a software system that is fully integrated with all the other operational areas of a company ensures that the accounting data is always complete and accurate. Scope/Detailed Definition This InfoProvider is a virtual cube based on the basic cube. No data is ever actually loaded into this cube. As long as the basic cube is being loaded then this cube will also be available for reporting. There is one datasource that loads the basic cube which is Transaction Details. Key Figure Requirements The Business Content key figures available are: 1. Total debt postings 2. Total credit postings 3. Cumulative balance 4. Flow value 5. Stock value The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a State of Louisiana LaGov ERP Project Page 1083 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Company code 2. Cost center 3. Controlling area 4. Profit center 5. Functional area 6. Segment for segmental reporting 7. Chart of accounts 8. G/L account 9. Financial statement item 10. Valuation view 11. Version 12. Value type for reporting 13. Currency type Security Requirements Currently we anticipate the use of no business content roles: Standard Queries There is 1 business content query available, 1. Financial Statement (New): Actual/Actual Comparison, Remote Data Flow Diagram None as it is a virtual cube coming off of the General Ledger (New) Transaction Figures basic cube. State of Louisiana LaGov ERP Project Page 1084 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: General Ledger (New) Transaction Figures BDD Number: BIW-GL-BDD003-General Ledger (New) Transaction Figures Functional Lead (State): Will Kelly Functional Lead (Consultant): Ronald Burke BACKGROUND AND SCOPE Introduction The central task of G/L accounting is to provide a comprehensive picture of external accounting and accounts. Recording all business transactions (primary postings as well as settlements from internal accounting) in a software system that is fully integrated with all the other operational areas of a company ensures that the accounting data is always complete and accurate. Scope/Detailed Definition This InfoCube contains all the transaction data (transactions figures) from the leading ledger in new General Ledger Accounting that was loaded from the integrated source system(s). Key Figure Requirements The Business Content key figures available are: 1. Sales for the period 2. Total debt postings 3. Total credit postings 4. Cumulative balance The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a Context / Dimensions Requirements The following analytical dimensions are required: 1. Company code 2. Cost center 3. Controlling area 4. Profit center 5. Functional area 6. Segment for segmental reporting 7. Chart of accounts 8. G/L account 9. Valuation view 10. Version 11. Currency type 12. Value type for reporting Security Requirements There are no business content roles. State of Louisiana LaGov ERP Project Page 1085 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries There are 2 business content queries available: 1. General Ledger (New): Balance Display 2. General Ledger (New): Balances – Cumulated, Comparison with Previous Year Data Flow Diagram State of Louisiana LaGov ERP Project Page 1086 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: General Ledger (New) Balance Sheet Profit and Loss, Remote BIW-GL-BDD004-General Ledger (New) Balance Sheet Profit BDD Number: and Loss, Remote Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The central task of G/L accounting is to provide a comprehensive picture of external accounting and accounts. Recording all business transactions (primary postings as well as settlements from internal accounting) in a software system that is fully integrated with all the other operational areas of a company ensures that the accounting data is always complete and accurate. Scope/Detailed Definition This InfoProvider is a virtual cube based on the basic cube. No data is ever actually loaded into this cube. As long as the basic cube is being loaded then this cube will also be available for reporting. There is one datasource that loads the basic cube which is Transaction Details. Key Figure Requirements The Business Content key figures available are: 1. Total debt postings 2. Total credit postings 3. Cumulative balance 4. Flow value 5. Stock value The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a State of Louisiana LaGov ERP Project Page 1087 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Company code 2. Cost center 3. Controlling area 4. Profit center 5. Functional area 6. Segment for segmental reporting 7. Chart of accounts 8. G/L account 9. Financial statement item 10. Valuation view 11. Version 12. Value type for reporting Security Requirements Currently we anticipate the use of no business content roles. Standard Queries There are 3 business content queries available, 1. Financial Statements (New): Actual/Actual Comparison 2. Financial Key Figures: Overview 3. Financial Key Figures: Details Data Flow Diagram None as it is a virtual cube coming off of the General Ledger (New) Transaction Figures Remote cube. State of Louisiana LaGov ERP Project Page 1088 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: General Ledger (New) – Transaction Figures, Remote BIW-GL-BDD002 - General Ledger (New) – Transaction BDD Number: Figures, Remote Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The central task of G/L accounting is to provide a comprehensive picture of external accounting and accounts. Recording all business transactions (primary postings as well as settlements from internal accounting) in a software system that is fully integrated with all the other operational areas of a company ensures that the accounting data is always complete and accurate. Scope/Detailed Definition This InfoCube contains all the transaction data (transactions figures) from the leading ledger in new General Ledger Accounting that was loaded from the integrated OLTP system(s). This RemoteCube can be used to select current data in real time. It is not necessary for the data to be replicated in InfoProviders. The data is read directly from the OLTP system by means of a BAPI. Key Figure Requirements The Business Content key figures available are: 1. Quantity 2. Sales for period 3. Total debit postings 4. Total credit postings 5. Cumulative balance The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a State of Louisiana LaGov ERP Project Page 1089 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Cost center 2. Controlling area 3. Company code 4. Profit center 5. Functional area 6. Segment for segmental reporting 7. Chart of accounts 8. G/L account 9. Valuation view 10. Version 11. Value type for reporting 12. Currency type Security Requirements There are no business content roles. Standard Queries There are 2 business content queries available: 1. General Ledger (New): Balances – Cumulated, Comparison with Previous Year, REMOTE 2. General Ledger (New): Balance Display, Remote Data Flow Diagram State of Louisiana LaGov ERP Project Page 1090 of 1338
  • LaGov ERP Project Business Blueprint 2. Controlling Team: BI BDD Name: Costs and Allocations BDD Number: BIW-CO-BDD001-Costs and Allocations Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of Costs and Allocations. It covers the required analysis of full costs on cost centers (plan, target, actual, etc.) as well as origin of the costs (allocation partner such as material number, cost center, and so on). Key Figure Requirements The Business Content key figures available are: 1. Amount 2. Consumption State of Louisiana LaGov ERP Project Page 1091 of 1338
  • LaGov ERP Project Business Blueprint The following additional key figures, restricted key figures, and calculated key figures are required: 1. Input price variance 2. Input quantity variance 3. Resource usage variance 4. Remaining input variance 5. input variance 6. price variance 7. Quantity variance 8. Cost variance 9. Remaining variance 10. Output variance 11. Variance 12. Actual costs 13. Planned costs 14. Target costs 15. Actual activity quantity 16. Plan activity quantity 17. Commitments 18. Actual consumption quantity 19. Plan consumption quantity 20. Target consumption quantity Context / Dimensions Requirements The following analytical dimensions are required: 1. Cost center 2. Cost element 3. Partner cost center 4. Partner order 5. Controlling area 6. Currency type 7. Partner object type 8. Partner object 9. Version 10. Customer number 11. Vendor number 12. G/L account Chart of accounts 13. FM area 14. Fund 15. Functional area 16. Grant 17. Partner fund 18. Partner functional area 19. Partner grant Security Requirements Currently we anticipate the use 2 business content roles, which are: 1. Cost Center Accounting 2. Management: Cost Centers (Regular Reports) State of Louisiana LaGov ERP Project Page 1092 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries There are 13 business content queries available: 1. Actual Costs – Periods / Quarterly / Situation 2. Plan/Actual - Periods / Quarterly / Situation 3. Target/Actual - Periods / Quarterly / Situation 4. Analysis - TOP N - Internal Activities 5. Analysis - TOP N - Vendors 6. Planning - Periods 7. Analysis - Plan/Actual - Costs and Quantities 8. Debit/Credit - Current Year/Previous Year 9. Actual Debit/Credit - Periods 10. Actual/Actual - Periods 11. Actual/Actual - Current Year/Previous Year 12. Actual/Plan - Periods / Quarterly / Situation 13. Actual/Plan - Periods / Quarterly / Situation Data Flow Diagram State of Louisiana LaGov ERP Project Page 1093 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Costs and Allocations (by Activity Type) BDD Number: BIW-CO-BDD002-Costs and Allocations (by Activity Type) Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of Costs and Allocations (by Activity Type). It covers all costs and quantities for marginal costing on cost centers that were transferred from the ECC Controlling module. The costs and quantities that are distributed via cost splitting to activity types are also included. Key Figure Requirements The Business Content key figures available are: 1. Amount 2. Fixed Amount 3. Variable Amount 4. Consumption 5. Fixed Consumption 6. Variable Consumption The following additional key figures, restricted key figures, and calculated key figres are required: 1. Actual credit 2. Plan credit 3. Actual costs 4. Actual costs (splitting) 5. Planned costs 6. Planned costs (splitting) 7. Target costs 8. Target costs (splitting) 9. Commitments 10. Actual revenues 11. Actual activity quantity 12. Planned activity quantity 13. Actual consumption quantity 14. Planned consumption quantity 15. Target consumption quantity State of Louisiana LaGov ERP Project Page 1094 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Cost Center 2. Cost Element 3. Controlling Area 4. Activity Type 5. Currency Type 6. Key Figure Type 7. Version 8. Details of Value Type 9. Value Type for reporting 10. Sender/receiver indicator 11. Valuation view 12. FM area 13. Fund 14. Functional Area 15. Grant 16. Partner Fund 17. Partner functional area 18. Partner Grant Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Cost Center Accounting 2. Management: Cost Centers (Regular Reports) Standard Queries There are 3 business content queries available: 1. Cost Center/Activity Type: Analysis – Target/Actual Variance 2. Cost Center/Activity Type: Analysis – Splitting Plan/Target 3. PSM: Cost Center/Activity Type: Analysis – Plan/Actual/Variance Data Flow Diagram State of Louisiana LaGov ERP Project Page 1095 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Activity Type Quantities and Prices BDD Number: BIW-CO-BDD003-Activity Type Quantities and Prices Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of Activity Type Quantities and Prices. IT contains all activity types that are entered in activity accounting. These are entered in plan and actual data based on quantity, and were transferred from the ECC Controlling module. Key Figure Requirements The Business Content key figures available are: 1. Output 2. Capacity 3. Activity 4. Scheduled Activity 5. Price, No Split (Total Cost) 6. Price, No Split (Fixed Cost) 7. Price, No Split (Variable Cost) 8. Price, Split (Total Cost) 9. Price, Split (Fixed Cost) 10. Price, Split (Variable Cost) 11. Price Based Quantity State of Louisiana LaGov ERP Project Page 1096 of 1338
  • LaGov ERP Project Business Blueprint The following additional key figures, restricted key figures, and calculated key figres are required: 1. Actual price 2. Actual price, fixed 3. Actual price, variable 4. Plan price 5. Plan price, fixed 6. Plan price, variable 7. Scheduled activity 8. Actual activity 9. Plan activity 10. Allocated activity 11. Capacity (Plan) 12. Plan output 13. Actual price – base quantity 14. Plan price – base quantity Context / Dimensions Requirements The following analytical dimensions are required: 1. Cost Center 2. Activity Type 3. Controlling Area 4. Key Figure Category 5. Version 6. Value Type for Reporting 7. Valuation View 8. Price Indicator 9. Currency Type 10. Cost Component 11. Cost Component Structure Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Cost Center Accounting 2. Management: Cost Centers (Regular Reports) Standard Queries There are 8 business content queries available: 1. Cost Center (Range): Analysis – Activity Quantity – Plan/Actual 2. Cost Center (Range): Analysis – Activity Type Price 3. Cost Center (Detail): Analysis – Activity Quantity – Plan/Actual 4. Cost Center (Detail): Analysis – Activity Type Price 5. Cost Center (Detail): Analysis – Activity Type Price – Split 6. Cost Center (Detail): Analysis – Activity Quantity – Plan/Actual – Periods 7. Cost Center (Detail): Planning Current Year/Comparison to Previous Year 8. Cost Center (Detail): Activity Type Price – Plan/Actual – Periods State of Louisiana LaGov ERP Project Page 1097 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1098 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Statistical Key Figures BDD Number: BIW-CO-BDD004-Statistical Key Figures Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of Statistical Key Figures. It contains all the quantities you posted to statistical key figures for cost center accounting which were loaded from the ECC Controlling module. Key Figure Requirements The Business Content key figures available are: 1. Quantity 2. Inventory quantity The following additional key figures, restricted key figures, and calculated key figures are required: 1. Actual Quantity 2. Actual Quantity (non-cumulative value) 3. Planned Quantity 4. Planned Quantity (non-cumulative value) Context / Dimensions Requirements The following analytical dimensions are required: 1. Cost Center 2. Controlling Area 3. Statistical key figure 4. Version 5. Value type for reporting Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Cost Center Accounting 2. Management: Cost Centers (Regular Reports) State of Louisiana LaGov ERP Project Page 1099 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries There are 2 business content queries available: 1. Cost Center (Range): Key Figures – Plan/Actual – Situation 2. Cost Center: Analysis – Statistical Key Figures Data Flow Diagram State of Louisiana LaGov ERP Project Page 1100 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: WBS: Statistical Key Figures BDD Number: BIW-CO-BDD005-WBS: Statistical Key Figures Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of WBS Statistical Key Figures. It contains all the statistical key figures posted to WBS elements that were retrieved from the ECC Controlling module. Key Figure Requirements The Business Content key figures available are: 1. Quantity 2. Inventory Quantity The following additional key figures, restricted key figures, and calculated key figures are required: 1. Actual Quantity 2. Actual Quantity (non-cumulative value) 3. Planned Quantity 4. Planned Quantity (non-cumulative value) Context / Dimensions Requirements The following analytical dimensions are required: 1. WBS Element 2. Controlling Area 3. Statistical key figure 4. Version 5. Value type for reporting Security Requirements There are no business content roles. Standard Queries There is 1 business content queries available: State of Louisiana LaGov ERP Project Page 1101 of 1338
  • LaGov ERP Project Business Blueprint 1. WBS Element: Statistical Key Figures – Plan/Actual/Variance Data Flow Diagram State of Louisiana LaGov ERP Project Page 1102 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: WBS Costs and Allocations BDD Number: BIW-CO-BDD006-WBS Costs and Allocations Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Specify and describe the business area that this HLA applies to. Describe the integration of this HLA as a solution i.e. how all the objects in this HLA integrates and work together to provide a solution. Describe how this HLA integrates with other HLA (if any) to provide a solution. Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of WBS Costs and Allocations. It contains all costs and quantities on WBS elements (plan and actual using delta extraction, commitment, budget, accruals) that were transferred from the ECC Controlling module. Key Figure Requirements The Business Content key figures available are: 1. Amount 2. Consumption quantity State of Louisiana LaGov ERP Project Page 1103 of 1338
  • LaGov ERP Project Business Blueprint The following additional key figures, restricted key figures, and calculated key figures are required: 1. Actual costs 2. Planned costs 3. Settled costs 4. Commitments 5. Budget (per fiscal year) 6. overall planning (per fiscal year) 7. Actual revenue 8. Planned revenue 9. Actual consumption quantity 10. Plan consumption quantity 11. Revenue in excess of billings 12. Work in process 13. Cannot be activated 14. Revenue affecting net income 15. Cost of sales 16. Cost of sales (cannot be capitalized) 17. Realized loss 18. Reserves for imminent losses 19. Reserves for imminent losses – inclusion cannot be capitalized 20. Loss 21. Reserve: unrealized costs 22. Reserve: unrealized costs, not capitalized Context / Dimensions Requirements The following analytical dimensions are required: 1. PSP element 2. Cost element 3. Controlling area 4. Currency type 5. Partner object type 6. Partner object 7. Key figure category 8. Version 9. Detail of value type 10. Value type for reporting 11. Sender/receiver indicator 12. Valuation view 13. Statistical indicator for value type 14. FM area 15. Fund 16. Functional area 17. Grant 18. Partner fund 19. Partner functional area 20. Partner grant Security Requirements There are no business content roles. State of Louisiana LaGov ERP Project Page 1104 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries There are 5 business content queries available: 1. WBS Element (Detail): Plan/Actual 2. WBS Elements (List): Budget/Actual/Commitment 3. WBS Elements (List): Overall Planning/Actual/Commitment 4. PSM: WBS Element (Detail): Plan/Actual 5. PSM: WBS Elements (List): Budget/Actual/Commitment Data Flow Diagram State of Louisiana LaGov ERP Project Page 1105 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: ABC Statistical Key Figures BDD Number: BIW-CO-BDD007-ABC Statistical Key Figures Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of ABC Statistical Key Figures. It contains all the quantities you posted to statistical key figures for the process that were loaded from the ECC Controlling module. Key Figure Requirements The Business Content key figures available are: 1. Quantity 2. Inventory quantity The following additional key figures, restricted key figures, and calculated key figures are required: 1. Actual Quantity 2. Planned Quantity 3. Actual Quantity (non-cumulative value) 4. Planned Quantity (non-cumulative value) Context / Dimensions Requirements The following analytical dimensions are required: 1. Controlling area 2. Business process number 3. Statistical Key Figure 4. Version 5. Key figure type 6. Statistics indicator for value type 7. Reporting value type Security Requirements Currently we anticipate the use of 1 business content role, which is: 1. Activity-Based Costing State of Louisiana LaGov ERP Project Page 1106 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries There are 5 business content queries available: 1. Process (Range): Key Figures – Plan/Actual – Situation 2. Process (Range): Key Figures – Plan/Actual – Quarterly 3. Process (Range): Key Figures – Plan/Actual – Periods 4. Process (Range): Analysis – Statistical Key Figures – Plan/Actual 5. Process (Range): Key Figure Planning – Current Year/Previous Year Data Flow Diagram State of Louisiana LaGov ERP Project Page 1107 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: ABC Business Process Quantites and Prices BDD Number: BIW-CO-BDD008-ABC Business Process Quantites and Prices Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of ABC Business Process Quantities and Prices. It contains all business processes for which planned and actual quantities have been entered and prices determined, and this data loaded from the ECC Controlling module. This InfoCube contains the associated quantity information on activities, scheduled activities, output, and capacity. It also contains the price information (with and without cost components) and the associated base quantities for the prices. The InfoCube contains two types of data records that differ in their key figures: business process quantities and business process prices. Key Figure Requirements The Business Content key figures available are: 1. Output 2. Capacity 3. Activity quantity 4. Fixed price, not split 5. Fixed price, split 6. Total price, not split 7. Total price, split 8. Variable price, not split 9. Variable price, split 10. Base quantity for price 11. Scheduled activity quantity State of Louisiana LaGov ERP Project Page 1108 of 1338
  • LaGov ERP Project Business Blueprint The following additional key figures, restricted key figures, and calculated key figures are required: 1. Plan price (key figure = total price) 2. Plan price, Fixed (key figure = price, fixed, with cost component split) 3. Plan price, Variable (key figure = price, variable, with cost component split) 4. Actual price (key figure = total price) 5. Actual price, Fixed (key figure = price, fixed, with cost component split) 6. Actual price, Variable (key figure = price, variable, with cost component split) 7. Planned activity quantity 8. Actual activity quantity 9. Scheduled activity (Plan) 10. Allocated activity (Actual) 11. Plan output 12. Actual output 13. Capacity (Plan) 14. Base quantity of plan price 15. Base quantity of actual price Context / Dimensions Requirements The following analytical dimensions are required: 1. Valuation view 2. Business process 3. Key figure type 4. Cost element 5. Controlling area 6. Price indicator: Calculate allocation price 7. Version 8. Reporting value type 9. Cost component 10. Cost component structure 11. Currency type Security Requirements Currently we anticipate the use of 1 business content role, which is: 1. Activity-Based Costing Standard Queries There are 8 business content queries available: 1. Process (Range) Analysis – Plan/Actual Business Process Quantity 2. Process (Range) Analysis – Business Process Price – Plan/Actual 3. Process (Range) Analysis – Plan/Actual Activity Quantity 4. Process (Detail) Analysis - Business Process Price – Plan/Actual 5. Process (Detail) Analysis - Business Process Price, Split, Plan/Actual 6. Process (Detail) Process Quantity – Plan/Actual – Periods 7. Process (Detail) Process Quantity Planning – Current Year/Previous Year 8. Process (Detail) Business Process Price – Plan/Actual – Periods State of Louisiana LaGov ERP Project Page 1109 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1110 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: ABC Costs and Allocations BDD Number: BIW-CO-BDD009-ABC Costs and Allocations Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of ABC Costs and Allocations. It contains all costs and allocated quantities for business processes (actual and plan) that were transferred from the source system or systems. In addition to complete information on variances, this InfoCube also contains the extended partner information (such as the partner business process with master data) for the allocation relationships. In allocations, the process can function as the sender or the receiver of activities (quantities) or costs. The processes are credited or debited accordingly. Key Figure Requirements The Business Content key figures available are: 1. Consumption Quantity 2. Amount State of Louisiana LaGov ERP Project Page 1111 of 1338
  • LaGov ERP Project Business Blueprint The following additional key figures, restricted key figures, and calculated key figures are required: 1. Input Price Variance 2. Input Quantity Variance 3. Resource – Usage Variance 4. Remaining Input Variance 5. Total Input Variance 6. Output Price Variance 7. Output Quantity Variance 8. Fixed-Cost Variance 9. Remaining Variance 10. Total Output Variance 11. Total Variance 12. Actual Credit: Internal Activity Allocation 13. Actual Credit: Allocation to Profitability Analysis 14. Actual Credit: Allocations 15. Actual Credit 16. Planned Credit 17. Actual Costs 18. Planned Costs 19. Target Costs 20. Actual Activity Quantity 21. Plan Activity Quantity 22. Actual Consumption Quantity 23. Plan Consumption Quantity 24. Target Consumption Quantity Context / Dimensions Requirements The following analytical dimensions are required: 1. Valuation View 2. Customer number 3. Details of value type 4. Business Process 5. Key Figure Type 6. Chart of accounts 7. Vendor Number 8. Cost element 9. Controlling area 10. Activity type of partner cost center 11. Partner order 12. Partner business process 13. Partner InfoObject 14. Partner Cost Center 15. Partner WBS element 16. Partner object 17. G/L account 18. Sender/receiver indicator 19. Statistics indicator for value type 20. Version 21. Reporting value type 22. Currency type State of Louisiana LaGov ERP Project Page 1112 of 1338
  • LaGov ERP Project Business Blueprint Security Requirements Currently we anticipate the use of 1 business content role, which is: 1. Activity-Based Costing Standard Queries There are 15 business content queries available: 1. Process (Range) Costs – Plan/Actual –Situation 2. Process (Range): Costs – Plan/Actual – Quarterly 3. Process (Range): Costs – Plan/Actual – Periods 4. Process (Range): Costs – Target/Actual – Situation 5. Process (Range): Costs – Target/Actual – Quarterly 6. Process (Range): Costs – Target/Actual – Periods 7. Process (Range): Actual Costs – Situation 8. Process (Range): Actual Costs – Quarterly 9. Process (Range): Actual Costs – Periods 10. Process (Range): Analysis – TOP N Vendors 11. Process (Range): Analysis – TOP N Internal Activities 12. Process (Range): Plan Costs – Current Year/Previous Year 13. Process (Range): Plan Costs – Quarterly – Year/Previous Year 14. Process (Range): Plan Costs – Periods – Current Year/Previous Year 15. Process (Detail): Costs – Plan/Actual – Situation 16. Process (Detail): Costs – Target/Actual – Situation Data Flow Diagram State of Louisiana LaGov ERP Project Page 1113 of 1338
  • LaGov ERP Project Business Blueprint 3. Funds Management Team: BI BDD Name: Funds Management – Commitments/Actuals and Budget BIW-FM-BDD001-Funds Management – Commitments/Actuals BDD Number: and Budget Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Provide general analysis capabilities necessary for controlling revenues and expenditures against existing budgets. Primary query capabilities include ad hoc analysis of dollar amounts viewed from various organizational, budgetary, time, and commitment perspectives. Seven predefined queries are included. Scope/Detailed Definition Since R/3 FM is using the Budget Control System (BCS) BW will focus only on BCS reporting. In Business Content one infocube, Commitments/Actual and Budget, exists that specifically addresses the BCS FM area. This cube sources data from seven areas, the datasources are: 1. Commitment Line Items in FM 2. FI Line Items in FM 3. CO Line Items in FM 4. Budget Totals Records 5. Budget Line Items 6. Budget Entry Documents 7. Consumable Budget and Consumed Amount Key Figure Requirements The Business Content key figures available are: 1. Amount FM Area Currency 2. Amount Transaction Currency The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a State of Louisiana LaGov ERP Project Page 1114 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. FM Area and Fund 2. Funds Centers 3. Commitment Items 4. Functional Area 5. FI Account Assignment 6. General Details 7. Budget Details 8. Details of Commitments and Actuals 9. Customers 10. Vendors 11. Funded Program 12. Grant 13. Cover Group and Year-End Closing 14. Time 15. Unit Security Requirements Security needs to be at the data level on Cost Center / Fund Center data item. Currently we anticipate the use of three roles, two business content roles, which are: 1. Budget Supervisor 2. Budget Planner Standard Queries There are 10 business content queries available, 1. Assigned Funds (Releases) 2. Assigned Funds 3. Budget 4. Assigned Funds (All Ledger) 5. Budget Version Comparison 6. Commitments and Actual 7. Payment Budget Overview 8. Budget Overview According to Year of Cash Effectivity 9. Released Objects 10. Budget Usage of Cover Groups State of Louisiana LaGov ERP Project Page 1115 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram 4. Accounts Payable Team: BI BDD Name: FI-Accounts Payable Line Items BDD Number: BIW-AP-BDD001- FI-Accounts Payable Line Items Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Accounts Payable is the money which a company owes to vendors for products and services purchased on credit. This item appears on the company's balance sheet as a current liability, since the expectation is that the liability will be fulfilled in less than a year. Scope/Detailed Definition This BDD implements analysis of Accounts Payable. It covers the required analysis of debit amounts, credit amounts and terms by vendor account number, company code, and currency type by Item level detail. This InfoCube contains all the Accounts Payable line items that were loaded from the integrated source State of Louisiana LaGov ERP Project Page 1116 of 1338
  • LaGov ERP Project Business Blueprint Key Figure Requirements The Business Content key figures available are: 1. Amount in foreign currency 2. Amount in local currency 3. Terms for net condition 4. Credit amount in foreign currency 5. Credit amount in local currency 6. Cash discount percentage 1 7. Cash discount days 1 8. Cash discount percentage 2 9. Cash discount days 2 10. Cash discount amount 11. Cash discount amount 12. Cash discount base 13. Debit amount in foreign currency 14. Debit amount in local currency Context / Dimensions Requirements The following analytical dimensions are required: 1. Reconciliation account 2. Clearing document number 3. Baseline date for due date calculation 4. Document type 5. Receipt date 6. Long text 7. Posting date in the document 8. Company code 9. Posting key 10. Date of last dunning 11. Clearing date 12. Date the record was created 13. Reason code 14. Indicator: Original document archived 15. Chart of accounts 16. Account type 17. Branch account number 18. Vendor 19. Credit control area 20. Country key 21. Dunning area 22. Dunning key 23. Dunning block 24. Dunning level 25. Due date for net payment 26. Item status 27. Invoice year 28. Invoice number 29. Invoice item 30. Reference document number 31. Reference key 1 State of Louisiana LaGov ERP Project Page 1117 of 1338
  • LaGov ERP Project Business Blueprint 32. Reference key 2 33. Reference key 3 34. Account number 35. Payment block key 36. Due date for cash discount 1 37. Due date for cash discount 2 38. Special G/L indicator 39. Sales Document 40. Terms of payment key 41. Payment method Security Requirements Currently we anticipate the use of one standard business content role, which is: Accounts Payable Accountant Standard Queries There are no standard business content queries available. Data Flow Diagram State of Louisiana LaGov ERP Project Page 1118 of 1338
  • LaGov ERP Project Business Blueprint State of Louisiana LaGov ERP Project Page 1119 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: FI-Accounts Payable – Transaction Data BDD Number: BIW-AP-BDD002- FI-Accounts Payable – Transaction Data Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Accounts Payable is the money which a company owes to vendors for products and services purchased on credit. This item appears on the company's balance sheet as a current liability, since the expectation is that the liability will be fulfilled in less than a year. Scope/Detailed Definition This BDD implements analysis of Accounts Payable. It covers the required analysis of debit amounts, credit amounts and terms by vendor account number, company code, and currency type by Item level detail. This InfoCube contains all accounts payable data (transaction figures) that was downloaded from the ECC FI module. Key Figure Requirements The Business Content key figures available are: 1. Sales of the period 2. Total debit postings 3. Accumulated balance 4. Total credit postings Context / Dimensions Requirements 1. Account number of the vendor or creditor 2. Currency type 3. Company code Security Requirements It is planned to mirror the ECC security role model. Currently we anticipate the use of 1 standard business content role, which is: 1. Accounts Payable Accountant State of Louisiana LaGov ERP Project Page 1120 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries There is 1 standard business content queries available: 1. Accounts Payable: Overview Data Flow Diagram State of Louisiana LaGov ERP Project Page 1121 of 1338
  • LaGov ERP Project Business Blueprint 5. Accounts Receivable Team: BI BDD Name: FI-Accounts Receivable BDD Number: BIW-AR-BDD001- FI-Accounts Receivable Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Accounts receivable (A/R) is one of a series of accounting transactions dealing with the billing of customers who owe money to a person, company or organization for goods and services that have been provided to the customer. In most business entities this is typically done by generating an invoice and mailing or electronically delivering it to the customer, who in turn must pay it within an established timeframe called credit or payment terms. The Accounts Receivable: MultiProvider provides for the reporting on AR (Accounts Receivables), Cash (including Down Payments: requested and received) and other related transactions, e.g. debt provisions and write-offs. A/R Ageing: MultiProvider provides for the reporting of open Accounts Receivables outstanding balances aged, based on Invoice Date, in predefined day range bands. Cash Reporting: MultiProvider provides for the reporting of cash received and other associated transactions. Scope/Detailed Definition This InfoCube contains all accounts receivable data (transaction figures) that was downloaded from the ECC FI System. It supports the analysis of sales postings by customer and organizational perspectives. Key Figure Requirements The Business Content key figures available are: 1. Sales of the period 2. Total debit postings 3. Accumulated balance 4. Total credit postings Context / Dimensions Requirements The following analytical dimensions are required: Characteristics 1. Customer number 2. Company code 3. Currency type State of Louisiana LaGov ERP Project Page 1122 of 1338
  • LaGov ERP Project Business Blueprint Security Requirements The security model in BI for Accounts receivable is going to be role based. Currently we anticipate the use of one standard business content role which is: 1. Accounts Receivable Accountant Standard Queries There are 2 standard business content queries available: 1. DSO Analysis, Current Period 2. Customers: DSO Analysis for a Period (Credit Management) Data Flow Diagram State of Louisiana LaGov ERP Project Page 1123 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: FI-Accounts Receivable Line Items BDD Number: BIW-AR-BDD002- FI-Accounts Receivable Line Items Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Accounts receivable (A/R) is one of a series of accounting transactions dealing with the billing of customers who owe money to a person, company or organization for goods and services that have been provided to the customer. In most business entities this is typically done by generating an invoice and mailing or electronically delivering it to the customer, who in turn must pay it within an established timeframe called credit or payment terms. Accounts Receivable provides analysis in various areas such as: The Accounts Receivable: MultiProvider provides for the reporting on AR (Accounts Receivables), Cash (including Down Payments: requested and received) and other related transactions, e.g. debt provisions and write-offs. A/R Ageing: MultiProvider provides for the reporting of open Accounts Receivables outstanding balances aged, based on Invoice Date, in predefined day range bands. Cash Reporting: MultiProvider provides for the reporting of cash received and other associated transactions. Scope/Detailed Definition This InfoCube contains all the Accounts Receivable line items that were loaded from the integrated ECC System. It provides analysis of credits, discounts and net dollars according to periods, documents and other accounting perspectives Key Figure Requirements The Business Content key figures available are: 1. Amount in foreign currency 2. Amount in local currency 3. Terms for net condition 4. Credit amount in foreign currency 5. Credit amount in local currency 6. Cash discount percentage 1 7. Cash discount days 1 8. Cash discount percentage 2 9. Cash discount days 2 10. Cash discount amount 11. Cash discount amount 12. Cash discount base 13. Debit amount in foreign currency 14. Debit amount in local currency Context / Dimensions Requirements The following analytical dimensions are required: State of Louisiana LaGov ERP Project Page 1124 of 1338
  • LaGov ERP Project Business Blueprint Characteristics 1. Reconciliation account 2. Clearing document number 3. Baseline date for due date calculation 4. Document type 5. Document date 6. Long text 7. Posting date in the document 8. Company code 9. Posting key 10. Last dunning date 11. Clearing date 12. Date the record was created 13. Reason code 14. Indicator: Original document archived 15. Chart of accounts 16. Account type 17. Branch account number 18. Customer 19. Credit control area 20. Country key 21. Dunning area 22. Dunning key 23. Dunning block 24. Dunning level 25. Due date for net payment 26. Item status 27. Invoice year 28. Invoice number 29. Invoice item 30. Reference document number 31. Reference key 1 32. Reference key 2 33. Reference key 3 34. Account number 35. Payment block key 36. Due date for cash discount 1 37. Due date for cash discount 2 38. Special G/L indicator 39. Sales document 40. Terms of payment key 41. Payment method State of Louisiana LaGov ERP Project Page 1125 of 1338
  • LaGov ERP Project Business Blueprint Security Requirements The Security model in BI for AR is role based. Currently we anticipate the use of one standard business content role, which is: 1. Accounts Receivable Accountant Standard Queries There are 3 standard business content queries available: 1. Accounts Receivable: Due Date for Net Payment Analysis 2. Accounts Receivable: Days Agreed / Days Taken 3. Accounts Receivable: Overdue Analysis Data Flow Diagram State of Louisiana LaGov ERP Project Page 1126 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: FI-Accounts Receivable Payment History BDD Number: BIW-AR-BDD003-FI-Accounts Receivable Payment History Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Accounts receivable (A/R) is one of a series of accounting transactions dealing with the billing of customers who owe money to a person, company or organization for goods and services that have been provided to the customer. In most business entities this is typically done by generating an invoice and mailing or electronically delivering it to the customer, who in turn must pay it within an established timeframe called credit or payment terms. Accounts Receivable provides analysis in various areas such as: The Accounts Receivable: MultiProvider provides for the reporting on AR (Accounts Receivables), Cash (including Down Payments: requested and received) and other related transactions, e.g. debt provisions and write-offs. A/R Ageing: MultiProvider provides for the reporting of open Accounts Receivables outstanding balances aged, based on Invoice Date, in predefined day range bands. Cash Reporting: MultiProvider provides for the reporting of cash received and other associated transactions. Scope/Detailed Definition This InfoCube contains the payment history (payment volume and days in arrears) of customers per company code and fiscal year period. The data comes from table KNB4 in the ECC source system. It supports the analysis of payment receipts relative to due date. Key Figure Requirements The Business Content key figures available are: 1. FI-AR: Payment volume without cash discount (currency) 2. FI-AR: Average delay for payment with cash discount 3. FI-AR: Average delay for payment without cash discount 4. Number of incoming payments in the period Context / Dimensions Requirements The following analytical dimensions are required: Characteristics 1. Customer number 2. Company code 3. Currency type Security Requirements Currently we anticipate the use of 1 standard business content role, which is: 1. Accounts Receivable Accountant State of Louisiana LaGov ERP Project Page 1127 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries There is one standard business content query available: 1. Accounts Receivable: Payment History Data Flow Diagram State of Louisiana LaGov ERP Project Page 1128 of 1338
  • LaGov ERP Project Business Blueprint 6. Project Systems Team: BI BDD Name: Project Systems BDD Number: BIW-PS-BDD001- Project Systems Business Process Owner: Christine Lee Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Project systems is the ability to be able to control all tasks in project execution. An organizational form is needed specific to the project and which is shared by all departments involved. Project systems provides a clear, unambiguous project structure that is the basis for successful project planning, monitoring, and control. Scope/Detailed Definition This BDD implements analysis of project management reporting in the controlling area. The project manager has the job of ensuring that the project is executed efficiently, on time, and within budget - which he or she achieves by ensuring that the required resources and funds are available as and when needed. This BDD is about resource management reporting for project systems. This BDD is specific about controlling data for project objects to enable corresponding reports. This cube has as a primary role of feeding the project systems dates / controlling MultiProvider: C051. Key Figure Requirements The business content key figures: 1. Costs: Overall Plan 2. Costs: Planned 3. Costs: Actual 4. Costs: Commitment 5. Residual Order Plan Context / Dimensions Requirements 1. Fiscal Year Variant 2. Network 3. Project Definition 4. Order number 5. Activity element 6. Network Activity 7. Work Breakdown Structure Element (WBS Element) 8. Fiscal Year State of Louisiana LaGov ERP Project Page 1129 of 1338
  • LaGov ERP Project Business Blueprint Security Requirements Currently we anticipate the use of 3 business content roles: 1. WBS element 2. Commercial Project Manager 3. Technical Project Manager Standard Queries This InfoCube contains transaction data related to PS Controlling. You can generate reports for various purposes based on this InfoCube. These include: 1. Hierarchical Project Overview/Residual. Ord. Plan (ID Using GUID) 2. Calculation of residual order plan 3. WBS Elements: Costs/Variances 4. Commercial Project Overview 5. Overview Report – Projects Data Flow Diagram State of Louisiana LaGov ERP Project Page 1130 of 1338
  • LaGov ERP Project Business Blueprint State of Louisiana LaGov ERP Project Page 1131 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Project Systems BDD Number: BIW-PS-BDD001- Project Systems Business Process Owner: Christine Lee Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Project systems is the ability to be able to control all tasks in project execution. An organizational form is needed specific to the project and which is shared by all departments involved. Project systems provides a clear, unambiguous project structure that is the basis for successful project planning, monitoring, and control. Scope/Detailed Definition This BDD implements analysis of project management reporting in the controlling area. The project manager has the job of ensuring that the project is executed efficiently, on time, and within budget - which he or she achieves by ensuring that the required resources and funds are available as and when needed. This BDD is about resource management reporting for project systems. This BDD is specific about project system dates data for project objects to enable corresponding reports. This cube has as a primary role of feeding the project systems dates / controlling MultiProvider: C051. Key Figure Requirements The business content key figures: 1. Duration: Actual 2. Duration: Plan Context / Dimensions Requirements 1. Object Type 2. Project Definition 3. Work Breakdown Structure Element (WBS Element) 4. Network 5. Network Activity 6. Dates: Basic Start Date 7. Dates: Basic Finish Dates 8. Dates: Actual Start Date 9. Dates: Actual Finish Date State of Louisiana LaGov ERP Project Page 1132 of 1338
  • LaGov ERP Project Business Blueprint Security Requirements Currently we anticipate the use of 3 business content roles: 1. WBS element 2. Commercial Project Manager 3. Technical Project Manager Standard Queries 1. Technical Project Overview (Identification Using GUID) Data Flow Diagram State of Louisiana LaGov ERP Project Page 1133 of 1338
  • LaGov ERP Project Business Blueprint 7. Asset Accounting Team: BI BDD Name: FI-AA Annual Values BDD Number: BIW-AA-BDD001-FI-AA Annual Values Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Asset Accounting is utilized for managing your company’s Fixed Assets. SAP allows you to categorize assets and to set values for depreciation calculations in each asset class. Scope/Detailed Definition This InfoCube contains all of the period values uploaded from the source system(s) for Asset Accounting on the basis of posted depreciation. InfoSource: Posted Depreciation Key Figure Requirements The Business Content key figures available are: 1. Acquisition value of asset at period start 2. Value of asset at period start 3. Period: Posted transferred reserves 4. Period start: Accumulated ordinary depreciation 5. Period start: Cumulative transferred reserves 6. Period start: Cumulative special depreciation 7. Period start: Cumulative unplanned depreciation 8. Period: Posted ordinary depreciation 9. Period: Posted special depreciation 10. Period: Posted unplanned depreciation 11. Value adjustment/write-up of transferred reserves 12. Value adjustment/write-up of ordinary depreciation 13. Value adjustment/write-up of special depreciation 14. Value adjustment/write-up of unplanned depreciation Context / Dimensions Requirements The following analytical dimensions are required: 1. Asset sub-number 2. Asset main number 3. Company code 4. Depreciation area real or derived 5. Depreciation area of asset State of Louisiana LaGov ERP Project Page 1134 of 1338
  • LaGov ERP Project Business Blueprint Time Characteristics: 1. Fiscal year/period 2. Fiscal year variant 3. Posting period 4. Fiscal year Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Fixed Asset Manager 2. Capital Investment Manager Standard Queries 1. Value Comparison Between Depreciation Areas Data Flow Diagram State of Louisiana LaGov ERP Project Page 1135 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: AA – Transactions BDD Number: BIW-AA-BDD002-AA – Transactions Business Process Owner: Rhoama Speights Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Asset Accounting is utilized for managing your company’s Fixed Assets. SAP allows you to categorize assets and to set values for depreciation calculations in each asset class. Scope/Detailed Definition This InfoCube contains all line items uploaded from the source system(s) from Asset Accounting InfoSources: 1. Transactions 2. Posted Depreciation (periodic values) Key Figure Requirements The Business Content key figures available are: 1. Acquisition value for transactions 2. Interest on transaction 3. Investment support on transaction 4. Ordinary depreciation on transaction 5. Transferred reserves on transaction 6. Revaluation on transaction 7. Revaluation of ordinary depreciation on transaction 8. Special depreciation on transaction 9. Unplanned depreciation on transaction 11. Transaction: Value adjustment/write-up on transferred reserves 12. Transaction: Value adjustment/write-up on ordinary depreciation 13. Transaction: Value adjustment/write-up on special depreciation 14. Transaction: Value adjustment/write-up on unplanned depreciation 15. Value adjustment on investment support 16. Value adjustment on revaluation of APC 17 Value adjustment on revaluation of ordinary depreciation State of Louisiana LaGov ERP Project Page 1136 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Asset sub-number 2. Asset main number 3. Company code 4. Depreciation area real or derived 5. Depreciation area of asset 6. Number of asset line item in fiscal year 7. Asset transaction type Time Characteristics: 1. Fiscal year/period 2. Fiscal year variant 3. Posting period 4. Fiscal year Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Fixed Asset Manager 2. Capital Investment Manager Standard Queries Relevant standard queries: 1. Asset Acquisitions 2. Asset Acquisitions on Quarterly Basis Data Flow Diagram State of Louisiana LaGov ERP Project Page 1137 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: AA – Annual Values BDD Number: BIW-AA-BDD003-AA – Annual Values Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Asset Accounting is utilized for managing your company’s Fixed Assets. SAP allows you to categorize assets and to set values for depreciation calculations in each asset class. Scope/Detailed Definition This InfoCube contains all of the annual values uploaded from the source system(s) for Asset Accounting on the basis of planned depreciation. Accounting InfoSources: 1. Revaluation/Year 2. Investment Support Key Figure Requirements The Business Content key figures available are: 1. Cumulative acquisition value at fiscal year start (w/o investment support) 2. Accumulated ordinary depreciation 3. Cumulative transferred reserves 4. Cumulative special depreciation 5. Cumulative unplanned depreciation 6. Planned annual transfer of reserves 7. Planned annual ordinary depreciation 8. Planned annual special depreciation 9. Transactions affecting acquis. value (w/o inv. support) 10. Unplanned depreciation for year 11. Value adjustment/write-up of transferred reserves for year 12. Value adjustment and write-up on ordinary depreciation 13. Value adjustment and write-up on special depreciation 14. Value adjustment and write-up on unplanned depreciation 15. Cumulative revaluation on ordinary depreciation 16. Cumulative revaluation on replacement value 17. Planned revaluation of cumulative ordinary depreciation 18. Planned revaluation of replacement value 19. Value adjustment on revaluation of APC 20. Value adjustment on revaluation of ordinary depreciation 21. Cumulative investment grants 22. Investment grants for year 23. Value adjustment on investment support State of Louisiana LaGov ERP Project Page 1138 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Asset sub-number 2. Asset main number 3. Company code 4. Depreciation area real or derived 5. Depreciation area of asset Time Characteristics: 1. Fiscal year 2. Fiscal year variant Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Fixed Asset Manager 2. Capital Investment Manager Standard Queries Relevant standard queries: 1. Asset List 2. Value Comparison Between Depreciation Areas Data Flow Diagram State of Louisiana LaGov ERP Project Page 1139 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Asset Accounting Annual Values and Transactions BIW-AA-BDD004-Asset Accounting Annual Values and BDD Number: Transactions Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Asset Accounting is utilized for managing your company’s Fixed Assets. SAP allows you to categorize assets and to set values for depreciation calculations in each asset class. Scope/Detailed Definition This InfoCube contains all of the annual values uploaded from the source system(s) on the basis of planned depreciation and line items. This InfoCube is designed for the asset history sheet. It includes the planned depreciation from InfoCube Annual Values and the line items from InfoCube Transactions. Key Figure Requirements The Business Content key figures available are: 1. Acquisition value at fiscal year start (w/o inv. support) 2. Accumulated ordinary depreciation 3. Cumulative transferred reserves 4. Cumulative special depreciation 5. Cumulative unplanned depreciation 6. Planned annual transfer of reserves 7. Planned annual ordinary depreciation 8. Planned annual special depreciation 9. Transactions affecting acquisition value (w/o inv. support) 10. Unplanned depreciation for year 11. Value adjustment/write-up of transferred reserves for year 12. Value adjustment and write-up on ordinary depreciation 13. Value adjustment and write-up on special depreciation 14. Value adjustment and write-up on unplanned depreciation 15. Cumulative revaluation on ordinary depreciation 16. Cumulative revaluation on replacement value 17. Planned revaluation of cumulative ordinary depreciation 18. Planned revaluation of replacement value 19. Value adjustment on revaluation of APC 20. Value adjustment on revaluation of ordinary depreciation 21. Cumulative investment grants 22. Investment grants for year 23. Value adjustment on investment support 24. Acquisition value for transactions 25. Interest on transaction State of Louisiana LaGov ERP Project Page 1140 of 1338
  • LaGov ERP Project Business Blueprint 26. Investment support on transaction 27. Ordinary depreciation on transaction 28. Transferred reserves on transaction 29. Revaluation on transaction 30. Revaluation of ordinary depreciation on transaction 31. Special depreciation on transaction 32. Unplanned depreciation on transaction 33. Transaction: Value adjustment/write-up on transferred reserves 34. Transaction: Value adjustment/write-up on ordinary depreciation 35. Transaction: Value adjustment/write-up on special depreciation 36. Transaction: Value adjustment/write-up on unplanned depreciation 37. Value adjustment on investment support 38. Value adjustment on revaluation of APC 39. Value adjustment on revaluation of ordinary depreciation Context / Dimensions Requirements The following analytical dimensions are required: 1. Asset sub-number 2. Asset main number 3. Company code 4. Depreciation area real or derived 5. Depreciation area of asset 6. Asset transaction type 7. Number of asset line item in fiscal year Security Requirements Currently we anticipate the use 2 business content roles, which are: 1. Fixed Asset Manager 2. Capital Investment Manager Standard Queries There are 3 business content queries available: 1. Asset History Sheet (for APC) 2. Asset History Sheet (for Depreciation) 3. Posted Depreciation State of Louisiana LaGov ERP Project Page 1141 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1142 of 1338
  • LaGov ERP Project Business Blueprint 8. Grants Management Team: BI BDD Name: Grants Management Detail Activity BDD Number: BIW-GM-BDD001-Grants Management Detail Activity Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The Grants Management application component is part of Public Sector Management. It is placed parallel to Funds Management (FM), with which it is closely linked. GM supports the budget and the actual line item ODS and four reporting infocubes. In addition to these transactional data providers, query-enabled master data infoobjects exist. One Query template is provided for each infocube. Scope/Detailed Definition The infocube contains the breakdown of the FI-SL table GMIA. Key Figure Requirements The Business Content key figures available are: 1. Amount 2. Quantity The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a Context / Dimensions Requirements The following analytical dimensions are required: 1. Budget Phase 2. Workflow State of a Record in the Budget 3. Budget Release Status 4. Billing Status for Item 5. Document’s Technical Origin 6. Budget Validity Number 7. Fiscal Year of Grantee Organization 8. Grant 9. Sponsored Class 10. Sponsored Program 11. GM Statistical Indicator 12. GM Value Type 13. Budget Version 14. Commitment Item 15. Functional Area 16. Financial Management Area State of Louisiana LaGov ERP Project Page 1143 of 1338
  • LaGov ERP Project Business Blueprint 17. Funds Center 18. Funded Program 19. Fund 20. Business Area 21. Chart of Accounts 22. G/L Account 23. Company Code 24. Main Asset Number 25. Asset Sub-number 26. Cost Center 27. Controlling Area 28. Network 29. Order Number 30. Profit Center 31. WBS 32. Currency Type 33. Source System ID 34. Business Process 35. Indicator: Document Item Completed 36. Indicator: Line Item Deleted 37. Business Transaction 38. Value Type for Reporting 39. Valuation View Security Requirements Security needs to be at the data level on Cost Center / Fund Center data item. Currently we anticipate the use of no business content roles. Standard Queries There is 1 business content queries available: 1. Activity Detail Data Flow Diagram State of Louisiana LaGov ERP Project Page 1144 of 1338
  • LaGov ERP Project Business Blueprint State of Louisiana LaGov ERP Project Page 1145 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Grants Management Budget Activity BDD Number: BIW-GM-BDD003-Grants Management Budget Activity Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The Grants Management application component is part of Public Sector Management. It is placed parallel to Funds Management (FM), with which it is closely linked. GM supports the budget and the actual line item ODS and four reporting infocubes. In addition to these transactional data providers, query-enabled master data infoobjects exist. One Query template is provided for each infocube. Key Figure Requirements The Business Content key figures available are: 1. Amount 2. Quantity The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a Context / Dimensions Requirements The following analytical dimensions are required: 1. Budget Phase 2. Workflow State of a Record in the Budget 3. Budget Release Status 4. Budget Validity Number 5. Fiscal Year of Grantee Organization 6. Grant 7. Sponsored Class 8. Sponsored Program 9. GM Statistical Indicator 10. GM Value Type 11. Budget Version 12. Financial Management Area 13. Fund 14. Company Code 15. Currency Type 16. Business Transaction 17. Value Type for Reporting 18. Valuation View 19. Source System ID 20. Business Process State of Louisiana LaGov ERP Project Page 1146 of 1338
  • LaGov ERP Project Business Blueprint Security Requirements Security needs to be at the data level on Cost Center / Fund Center data item. Currently we anticipate the use of no business content roles. Standard Queries There is 1 business content queries available: 1. Budget Detail Data Flow Diagram State of Louisiana LaGov ERP Project Page 1147 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Grants Management Aggregated Key Figures BIW-GM-BDD002-Grants Management Aggregated Key BDD Number: Figures Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The Grants Management application component is part of Public Sector Management. It is placed parallel to Funds Management (FM), with which it is closely linked. GM supports the budget and the actual line item ODS and four reporting infocubes. In addition to these transactional data providers, query-enabled master data infoobjects exist. One Query template is provided for each infocube. Scope/Detailed Definition The infocube contains the breakdown of the FI-SL table GMIT. Key Figure Requirements The Business Content key figures available are: 1. Amount 2. Quantity 3. Accumulated Balance The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a Context / Dimensions Requirements The following analytical dimensions are required: 1. Budget Phase 2. Workflow State of a Record in the Budget 3. Budget Release Status 4. Budget Validity Number 5. Fiscal Year of Grantee Organization 6. Grant 7. Sponsored Class 8. Sponsored Program 9. GM Statistical Indicator 10. GM Value Type 11. Budget Version 12. Financial Management Area 13. Fund 14. Chart of Accounts 15. Company Code 16. Currency Type State of Louisiana LaGov ERP Project Page 1148 of 1338
  • LaGov ERP Project Business Blueprint 17. Business Transaction 18. Value Type for Reporting 19. Valuation View 20. Source System ID Security Requirements Security needs to be at the data level on Cost Center / Fund Center data item. Currently we anticipate the use of no business content roles. Standard Queries There is 1 business content queries available: 1. Budget vs. Commitment/Actuals Data Flow Diagram State of Louisiana LaGov ERP Project Page 1149 of 1338
  • LaGov ERP Project Business Blueprint 9. Budget Preparation Team: BI BDD Name: Budget Prep Standard Design BDD Number: BIW-BP-BDD001-Budget Prep Standard Design John Davis (FPC-Capital), Barry Dusse (Operating), and Mike Business Process Owner: Schiro (DOTD) Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction ERP must support the annual budgeting process for the State of Louisiana for both operating budget as well as capital outlay. Both the operating and CO budgets are lengthy budget request documents with a large amount of data unique to Louisiana. This transactional cube will be used to store submitted budget data during the budget development cycle prior to retraction to FM. Adjustments subsequent to retraction (mid year adj’s/BA7s) will be made to FM. Scope/Detailed Definition Custom InfoCube: TBD - referred for HB1, HB2 and DOTD Hwy Budget These custom InfoCubes contain all values that are saved when creating the Operating and Capital budget entries. These InfoCubes are transactional in nature, in other words, these InfoCubes are "input- enabled" for data entry from user input screens.Planning / Budget Formulation process is expected to be a fully custom development solution leveraging the tools SAP provides for development. InfoCube: 0PU_C51 This standard delivered InfoCube will also be used for the Budget Preparation process. It is similar to the Reporting InfoCube 0PU_C02, with the essential difference that it is a transactional InfoCube. MultiProvider: 0PU_MP03 The MultiProvider displays actual, plan, and forecast data simultaneously for budget reporting. With the further Inclusion of the custom Planning / Budget Formulation Infocubes, this Multi-Provider is expected to support several reports, including the BI-based Budget versus Actual report. Key Figure Requirements The Business Content key figures available are: 1. Amount in FM area currency 2. Amount in transaction currency State of Louisiana LaGov ERP Project Page 1150 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements 1. Amount type 2. Number of year end closing transfers 3. Carryforward level 4. Change Run ID 5. Chart of accounts 6. Commitment item 7. Company code 8. Account number of supplier/vendor 9. Currency Key for Transaction Currency 10. Customer Number 11. Fiscal year / period 12. Posting period 13. Fiscal year variant 14. Fiscal year 15. Indicator: Original Document Archived 16. Detailing of Commitment and Actual in Funds Management 17. Financial Management Area 18. Budget category in Funds Management 19. Currency key for FM area currency 20. Funds Management statistical indicator 21. Transaction for Detailing Commitments and Actuals 22. Value type in Funds Management 23. Functional area 24. Fund 25. Funds Center 26. G/L Account 27. Grant 28. Budget Period 29. Budget Type 30. Year of Cash Effectivity for Budget (BCS) 31. Cover Group (BCS) 32. Ledger for Availability Control 33. Funded Program 34. Migration Indicator 35. Budgeting Process (Internal) 36. User dimension 37. Budgeting Value Type 38. Workflow Status of a Data Record in Budget Totals Table 39. Record type 40. Request ID 41. Version Security Requirements The standard roles in this area are: 1. Budget Planner 2. Budget Supervisor Other roles TBD. State of Louisiana LaGov ERP Project Page 1151 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries There are 5 business content queries available, 5 have been identified as being useful those being: Budget - Available budget below Threshold Query: 0PU_MP03_Q0004 The aim of the queries is to display all funds where the available budget is smaller than the predefined threshold value. YTD Budget Overrun Query: 0PU_MP03_Q0002 The aim of the query is to display the fund where the available YTD budget is smaller than 0. YTE Budget Overrun Forecast Query: 0PU_MP03_Q0003 The aim of the queries is to display all funds where the available YTE budget is smaller than 0. Budget Chart Query: 0PU_MP03_Q0001 This query is to get an overview of the budget situation. Business Rules and Assumptions See Gap Documents related to Budgeting Data Flow Diagram State of Louisiana LaGov ERP Project Page 1152 of 1338
  • LaGov ERP Project Business Blueprint 10. Grantor Team: BI BDD Name: Grantor Management BDD Number: BIW-GR-BDD001-Grantor Management Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke Background and Scope Introduction: Grants Management for Grantor The Grants Management for Grantor solution is intended to meet the requirements of all levels of public sector organizations that fund grant programs. Developed within a SAP NetWeaver framework, business processes include program definition, application, assessment, agreement, grant payment, claims processing and monitoring and analysis. The Grantor solution includes web-enabled grant application processing, workflow authorization and notification in addition to case, correspondence and records management functionality. It also delivers robust reporting capability and content through the mySAP Business Intelligence solution. Scope/Detailed Definition SAP Grants Management complements SAP's current public sector offering. The application meets the requirements of public sector organizations that fund grant programs. The grantor solution allows organizations to record and report performance measures, define service standards, and assess risk. It provides a comprehensive auditing functionality. This BDD implements analysis of functionality of organizations that fund, or the Grantor. The MultiCube: Grantor Management: Application, Agreement and Claim is the consolidation of 3 lower level cubes and 3 lower level DSOs with the same names: 1. Grantor Management Application 2. Grantor Management Agreement 3. Grantor Management Claim. This MultiCube contains all data (header level) from the application and agreement in Grantor Management in CRM. Key Figure Requirements 1. Rel. Holdback Amount 2. Authorized Amount 3. Number of Applications 4. Authorized Amount 5. Authorized Amount 6. Billing Request Amount 7. Eligible Amount 8. Number of Claims 9. Requested Amount 10. Eligible Amount State of Louisiana LaGov ERP Project Page 1153 of 1338
  • LaGov ERP Project Business Blueprint 11. Holdback Accumulated Amount 12. Requested Amount 13. Total Authorized Amount 14. Total Billing Request Amount 15. Total Eligible Amount 16. Total Requested Amount 17. Number of Document Headers 18. Number of Document Items 19. Billing Request Amount 20. Number of Agreements Context Dimensions Required 1. Grantee 2. Grantor Program Management Element GUID 3. Application ID 4. GUID of GTR Agreement 5. Payment Type 6. Agreement ID 7. Claim ID 8. Business Transaction Object Type 9. Calendar day 10. Calendar year/month 11. Calendar year / week 12. Fiscal year / period 13. Fiscal year variant 14. Fiscal year 15. Calendar year 16. Funded Program 17. Grantor Program Type 18. Grantor Program Category 19. Grantor Program External ID 20. Financial management area 21. Service Organization CRM Security Requirements Currently we anticipate the use of 3 business content roles: 1. Grantor Program 2. Grant 3. Grantor Standard Queries 1. Grantor Lifecyle: Current Overview – from MultiProvider 2. Grantor Applications: Current Overview – From Grant Applications - Cube and DSO 3. Grantor Agreements: Current Overview – From Grant Agreements - Cube and DSO 4. Grantor Claims: Current Overview – From Grant Claims - Cube and DSO From these base queries the users will develop their specific reports. State of Louisiana LaGov ERP Project Page 1154 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram BW Dataflow for Multi-Provider Grantor focuses on multi-provider reporting, there is the option to report off of each individual cube / ODS, but we expect the consolidated reporting from the multi-provider to be of greatest benefit. State of Louisiana LaGov ERP Project Page 1155 of 1338
  • LaGov ERP Project Business Blueprint 11. Real Estate Team: BI BDD Name: FI – Real Estate Occupancy BDD Number: BIW-RE-BDD001-FI – Real Estate Occupancy Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition The Occupancy InfoCube allows you to run reports for a key date on occupied or unoccupied spaces (including vacancies) of rental objects, by • Company code • Business entity • Building • Property • Measurement type Unlike the Measurements InfoCube, this InfoCube takes account of whether or not there is a contract for the measurements of the rental object. Key Figure Requirements The Business Content key figures available are: 1. Measurement: Occupied (Change) 2. Measurement: Vacant (Change) 3. Measurement: Occupied 4. Measurement: Vacant State of Louisiana LaGov ERP Project Page 1156 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Real estate object 2. Object type 3. Company code 4. Business entity 5. Building 6. Property 7. Rental object 8. Measurement type Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries There is 1 business content queries available: 1. Occupancy Data Flow Diagram State of Louisiana LaGov ERP Project Page 1157 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Real Estate Measurements BDD Number: BIW-RE-BDD002-Real Estate Measurements Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition You can run reports on the time-dependent data of measurements of business entities, buildings, properties and rental objects using the Measurements InfoCube. The InfoCube provides an overview of the progress and status of real estate portfolios (leased-in or owned), by measurements, locations and industry sector on a key date. Key Figure Requirements The Business Content key figures available are: 1. Measurement amount 2. Measurement amount (change) Context / Dimensions Requirements The following analytical dimensions are required: 1. Company code 2. Business entity 3. Building 4. Property 5. Rental object 6. Measurement type 7. Real estate object Security Requirements Currently we anticipate the use 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects State of Louisiana LaGov ERP Project Page 1158 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries 1. Lease-In by Regional Location 2. Portfolio by Industry 3. Portfolio by Regional Location 4. Portfolio Overview 5. Portfolio Overview (% Share) 6. Owned Real Estate by Regional Location 7. Vacancy by Usage Type 8. Usage of My Objects Data Flow Diagram State of Louisiana LaGov ERP Project Page 1159 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Real Estate Cash Flow BDD Number: BIW-RE-BDD003-Real Estate Cash Flow Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition The Cash Flow InfoCube enables you to run periodic reports on the cash flow of contracts and rental objects based on the following criteria: • Controlling areas • Cost centers • Order numbers • Flow types • Condition types • Business partners Key Figure Requirements The Business Content key figures available are: 1. Net amount of cash flow item 2. Gross amount of cash flow item State of Louisiana LaGov ERP Project Page 1160 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Real estate object 2. Company code 3. Business entity 4. Rental object 5. Contract 6. Business partner 7. Controlling area 8. Cost center 9. Order number 10. Work breakdown structure element (WBS element) 11. Condition type 12. Flow type 13. Building 14. Property 15. Object type Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Description of Queries to be developed by Project 1. Cash Flow 2. Cash Flow – Rental Objects Data Flow Diagram State of Louisiana LaGov ERP Project Page 1161 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Real Estate Management Asset Transactions BDD Number: BIW-RE-BDD004-Real Estate Management Asset Transactions Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition The Real Estate: Asset Transactions InfoCube makes periodic reporting possible on line items of assets related to real estate objects, using the following criteria: • Asset main number and asset subnumber • Asset class • Depreciation areas • Balance sheet account for acquisition and production costs • Building • Property Key Figure Requirements The Business Content key figures available are: 1. Acquisition value for transactions 2. Interest on transaction 3. Investment support on transaction 4. Ordinary depreciation on transaction 5. Transfer of reserves for the transaction 6. Appreciation (revaluation) on transaction 7. Revaluation of ordinary depreciation on transaction 8. Special depreciation on transaction 9. Unplanned depreciation on transaction 10. Costs from asset retirement 11. Revenue from asset sale 12. Gain from asset retirement 13. Loss from asset retirement State of Louisiana LaGov ERP Project Page 1162 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Company code 2. Main asset number 3. Asset subnumber 4. Real estate object 5. Business entity 6. Building 7. Rental object 8. Real or derived depreciation area 9. Asset transaction type 10. Asset class 11. Balance sheet account for acquisition and production costs 12. Chart of accounts 13. Cost center 14. Controlling area Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries 1. Real Estate: Asset Acquisitions Data Flow Diagram State of Louisiana LaGov ERP Project Page 1163 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Real Estate Management Annual Asset Values BIW-RE-BDD005-Real Estate Management Annual Asset BDD Number: Values Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition The Real Estate: Annual Asset Values InfoCube makes reporting possible on annual values of assets related to real estate objects, using the following criteria: • Asset main number and asset subnumber • Asset class • Depreciation areas • Balance sheet account for acquisition and production costs • Building • Property Key Figure Requirements The Business Content key figures available are: 1. Cumulative acquisition value at FY start (w/o inv.support) 2. Accumulated ordinary depreciation 3. Cumulative reserves transfer 4. Cumulative special depreciation 5. Cumulative unplanned depreciation 6. Planned transfer of reserves for the year 7. Planned ordinary depreciation for the year 8. Planned special depreciation for the year 9. Transactions affecting acquisition value (w/o inv. support) 10. Planned unplanned depreciation for the year 11. Cumulative revaluation of ordinary depreciation 12. Cumulative revaluation of the replacement value 13. Planned revaluation of accumulated ordinary depreciation 14. Planned revaluation of replacement values 15. Cumulative investment grants 16. Investment grant for the year Context / Dimensions Requirements The following analytical dimensions are required: State of Louisiana LaGov ERP Project Page 1164 of 1338
  • LaGov ERP Project Business Blueprint 1. Company code 2. Main asset number 3. Asset subnumber 4. Real estate object 5. Business entity 6. Building 7. Rental object 8. Real or derived depreciation area 9. Asset class 10. Balance sheet account for acquisition and production costs 11. Chart of accounts 12. Cost center 13. Controlling area 14. Property Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries 1. Fixed Assets: Asset Lists 2. Fixed Assets: Comparison of Asset Values Data Flow Diagram State of Louisiana LaGov ERP Project Page 1165 of 1338
  • LaGov ERP Project Business Blueprint State of Louisiana LaGov ERP Project Page 1166 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Real Estate Management BDD Number: BIW-RE-BDD006-Real Estate Management Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition The Real Estate: Periodic Asset Values InfoCube makes reporting possible on periodic values of assets related to real estate objects, using the following criteria: • Asset main number and asset subnumber • Asset class • Depreciation areas • Balance sheet account for acquisition and production costs • Order number • Building • Property Key Figure Requirements The Business Content key figures available are: 1. Acquisition value of asset 2. Asset value at start of period 3. Values for the period: posted transfer of reserves 4. Value at period start: cumulated ordinary depreciation 5. Values at period start: cumulated transfer of reserves 6. Values at period start: cumulated special depreciation 7. Values at period start: cum. unplanned depreciation 8. Values for the period: posted ordinary depreciation 9. Values for the period: posted special depreciation 10. Values for the period: posted unplanned depreciation 11. Investment support for asset at period start 12. Revaluation of acquisition and prod. costs at start of period 13. Revaluation of ordinary depreciation at period start 14. Interest at start of period 15. Asset investment support 16. Values of period: posted revaluation of APC 17. Revaluation of cumulative ord. depreciation 18. Interest on period State of Louisiana LaGov ERP Project Page 1167 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Company code 2. Main asset number 3. Asset subnumber 4. Real estate object 5. Business entity 6. Building 7. Rental object 8. Real or derived depreciation area 9. Asset transaction type 10. Asset class 11. Balance sheet account for acquisition and production costs 12. Chart of accounts 13. Cost center 14. Controlling area 15. Order number 16. Property 17. Posted/simulated values Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries 1. Fixed Assets: Posted Depreciation State of Louisiana LaGov ERP Project Page 1168 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1169 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: FI – RE Costs and Revenues BDD Number: BIW-RE-BDD007-FI – RE Costs and Revenues Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition You can use the Costs and Revenues InfoCube to run reports on costs and revenues (plan and actual values) for real estate objects and for contracts. Costs and revenues for real estate objects can also be evaluated in relation to partners. Key Figure Requirements The Business Content key figures available are: 1. Amount 2. Fixed amount 3. Variable amount 4. Quantity 5. Fixed quantity 6. Variable quantity 7. Measurement amount for CO Context / Dimensions Requirements The following analytical dimensions are required: 1. Activity type 2. Company code 3. Cost element 4. Controlling area 5. Currency type 6. Sender/receiver indicator 7. Key figure category 8. Partner object type 9. Partner object 10. Contract 11. Business entity 12. Rental object 13. Real estate object 14. Valuation view 15. Version State of Louisiana LaGov ERP Project Page 1170 of 1338
  • LaGov ERP Project Business Blueprint 16. Details of value type 17. Statistical indicator for value type 18. Value type for reporting 19. Exception indicator for measurements 20. Object type 21. Building 22. Property 23. Functional location 24. Order number Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Description of Queries to be developed by Project 1. Real Estate: Costs and Revenues 2. Real Estate: Costs and Revenues (Cost Group) 3. Real Estate: Costs and Revenues – Plan/Actual 4. Real Estate: Costs and Revenues (per Space) 5. Real Estate Costs per Space and Usage 6. Partner Performance – Lease-Out (by Measurement) 7. Contract Performance – Lease-In 8. Contract Performance – Lease-In – Bottom N 9. Contract Performance – Lease-In – Top N 10. Contract Performance – Internal 11. Contract Performance – Lease-Out 12. Contract Performance – Lease-Out – Bottom N 13. Contract Performance – Lease-Out – Top N Standard Queries None identified. Data Flow Diagram State of Louisiana LaGov ERP Project Page 1171 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: FI – Real Estate Conditions BDD Number: BIW-RE-BDD008-FI – Real Estate Conditions Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition You can use the Conditions InfoCube to run reports based on key dates for contract conditions and rental object conditions. Key Figure Requirements The Business Content key figures available are: 1. Condition amount 2. Change to condition amount Context / Dimensions Requirements The following analytical dimensions are required: 1. Real estate object 2. Company code 3. Business entity 4. Contract 5. Rental object 6. Condition purpose 7. Condition type Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries 1. Conditions 2. Conditions – Rental Objects State of Louisiana LaGov ERP Project Page 1172 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1173 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: FI – Real Estate Vacancy BDD Number: BIW-RE-BDD009-FI – Real Estate Vacancy Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition You can run the following reports using the Vacancy InfoCube: • Usage of the real estate portfolio (leased out internally and externally) • Current vacancies • Potential notice dates Key Figure Requirements The Business Content key figures available are: 1. Vacancy in Period Context / Dimensions Requirements The following analytical dimensions are required: 1. Real Estate Object 2. Company code 3. Business entity 4. Rental object Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries 1. Days Vacant in Period State of Louisiana LaGov ERP Project Page 1174 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1175 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Occupancy – View by Period BDD Number: BIW-RE-BDD010-Occupancy – View by Period Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition You can use this InfoCube to run reports on the occupancy of rental objects. Due to the availability of vacancy reasons in the InfoCube, the InfoCube can be used for reports on vacancies (length of vacancy and reason for vacancy). The reports provide a period-related overview. Key Figure Requirements The Business Content key figures available are: 1. Measurement: Occupied (Change) 2. Measurement: Vacant (Change) 3. Measurement: Occupied 4. Measurement: Vacant State of Louisiana LaGov ERP Project Page 1176 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Unit of Area 2. Business Entity 3. Calendar Year/Month 4. Change Run ID 5. Company code 6. Total Number of Days 7. Number of Days Occupied/Vacant 8. Proportional Occupied Areas 9. Contract 10. Record type 11. Reference Area 12. Rental Object 13. Real Estate Object 14. Object Type 15. Occupancy 16. Request ID 17. Vacancy Quota (Value) 18. Vacancy Ratio (Days) 19. Vacancy Reason (RE-FX) Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries There are no business content queries available for this InfoCube Data Flow Diagram Not Available State of Louisiana LaGov ERP Project Page 1177 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: RE – Measurements of Architectural Object BDD Number: BIW-RE-BDD011-RE – Measurements of Architectural Object Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition You can use this InfoCube to run reports on the measurements of architectural objects. The analyses provided by this InfoCube are based on key dates. Key Figure Requirements The Business Content key figures available are: 1. Capacity 2. Capacity (Change) 3. Measurement Amount (Change) 4. Measurement Amount Context / Dimensions Requirements The following analytical dimensions are required: 1. Architectural Object 2. Calendar Day 3. Change Run ID 4. Measurement Type 5. Record type 6. Real Estate Object 7. Object Type 8. Request ID 9. Unit of Measure State of Louisiana LaGov ERP Project Page 1178 of 1338
  • LaGov ERP Project Business Blueprint Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries There are no business content queries available for this InfoCube Data Flow Diagram Not yet available. State of Louisiana LaGov ERP Project Page 1179 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: RE – Contract Measurements BDD Number: BIW-RE-BDD012-RE – Contract Measurements Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition You can use this InfoCube to run reports on measurements that have been specified individually for each contract. The analyses provided by this InfoCube are based on key dates. Key Figure Requirements The Business Content key figures available are: 1. Capacity 2. Capacity (Change) 3. Measurement Amount (Change) 4. Measurement Amount Context / Dimensions Requirements The following analytical dimensions are required: 1. Business Entity 2. Calendar Day 3. Calendar Year/Month 4. Change Run ID 5. Company code 6. Measurement Type 7. Building 8. Contract 9. Record type 10. Rental Object 11. Real Estate Object 12. Object Type 13. Property 14. Request ID 15. Object Type of Assigned Object 16. Unit of Measure Security Requirements State of Louisiana LaGov ERP Project Page 1180 of 1338
  • LaGov ERP Project Business Blueprint Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries There are no business content queries available for this InfoCube Data Flow Diagram Not yet available State of Louisiana LaGov ERP Project Page 1181 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: RE – Assignment Between Architectural View and Usage View BIW-RE-BDD013-RE – Assignment Between Architectural BDD Number: View and Usage View Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction The SAP Real Estate module assists management of every stage of the real estate portfolio life cycle, including property acquisition and disposal, portfolio management, technical management of building operations and maintenance, and investment controlling and reporting. Scope/Detailed Definition You can use this InfoCube to run reports on the assignment of measurements from architectural objects to usage objects (business entities, buildings, land, and rental objects). The analyses provided by this InfoCube are based on key dates. Key Figure Requirements The Business Content key figures available are: 1. Measurement Type 2. Measurement Amount (Change) 3. Measurement Amount: Partial Assignment 4. Measurement Amount: Part.Assignment (Change) 5. Measurement Amount: Share 6. Measurement Amount: Share (Change) 7. Measurement Amount State of Louisiana LaGov ERP Project Page 1182 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Architectural Object 2. Architecture-Usage Relationship Type 3. Business Entity 4. Calendar Day 5. Change Run ID 6. Company code 7. Building 8. Contract 9. Record type 10. Rental Object 11. Real Estate Object 12. Object Type 13. Property 14. Request ID 15. Assigned Real Estate Object 16. Object Type of Assigned Object 17. Unit of Measure Security Requirements Currently we anticipate the use of 2 business content roles, which are: 1. Real Estate Manager 2. Real Estate Manager for Architectural Objects Standard Queries There are no business content queries available for this InfoCube Data Flow Diagram Not yet available State of Louisiana LaGov ERP Project Page 1183 of 1338
  • LaGov ERP Project Business Blueprint 12. Procurement / Contracts Team: BI BDD Name: LOG-Supplier Relationship Mgmt BDD Number: BIW-SRM-BDD001-LOG-Supplier Relationship Mgmt Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Supplier relationship management is a comprehensive approach to managing an enterprise's interactions with the organizations that supply the goods and services it uses. The goal of supplier relationship management (SRM) is to streamline and make more effective the processes between an enterprise and its suppliers. SRM includes both business practices and software and is part of the information flow component of supply chain management (SCM). SRM practices create a common frame of reference to enable effective communication between an enterprise and suppliers who may use quite different business practices and terminology. Scope/Detailed Definition This MultiProvider allows you to perform cross procurement system analysis of procurement data with regard to purchase orders, goods receipts and service confirmations, and incoming invoices, on aggregate level. You can use it to execute general strategic reports like Global Spend Analyses and to evaluate variations between invoice values and purchase order values. Key Figure Requirements The Business Content key figures available are: 1. Confirmed Quantity in Base Unit 2. Confirmed Quantity (BUoM) for Order Date 3. Net Confirmed Value in Default Currency 4. Net Confirmed Value in Default Currency for Order Date 5. Customer from Third-Party PO 6. Expected Net Order Value in Default Currency 7. Freight Costs in Invoice in Default Currency 8. Invoiced Quantity in Base Unit 9. Invoiced Quantity (BUoM) for Order Date 10. Net Invoiced Value in Default Currency 11. Net Invoiced Value in Default Currency for Order Date 12. Order Quantity in Base Unit 13. Purchase Order Tax Amount in Default Currency 14. Net Order Value in Default Currency State of Louisiana LaGov ERP Project Page 1184 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: Characteristics 1. Base Unit of Measure 2. Approver 3. Number of Invoice Items 4. Number of Invoices 5. Buyer ID 6. Catalog 7. Number of Confirmations 8. Delivery Time Variance 9. Number of Confirmed Items 10. Number of Purchase Orders 11. Number of Order Items 12. Number of Perfect Purchase Orders 13. Purchasing Group 14. Purchasing Organization 15. Goods Recipient From Business Partner Table 16. Requester from Business Partner Table 17. Number of Shopping Carts 18. Number of Shopping Cart Items 19. Shopping Cart Quantity in Shopping Cart Unit 20. Logical Procurement System 21. Flag Third-Party Order 22. Product Description Time Characteristics 1. Calendar Day 2. Calendar Year/Month 3. Calendar Year/Quarter 4. Calendar Year/Week 5. Calendar Year Security Requirements The security is maintained at catalog items and shopping cart level. There are no standard business content roles available. Standard Queries There are nine business content queries available: 1. Procurement Value Analysis 2. Vendor Information 3. Price Trend Analysis 4. Sales Values (for Vendor) 5. Sales Values per Contract 6. Key Performance Indicators 7. Number of Vendors per Country 8. ABC Vendors 9. Procurement Values per Service Agent State of Louisiana LaGov ERP Project Page 1185 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1186 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: LOG-Supplier Relation Mgmt BDD Number: BIW-SRM-BDD002-LOG-Supplier Relation Mgmt Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Supplier relationship management is a comprehensive approach to managing an enterprise's interactions with the organizations that supply the goods and services it uses. The goal of supplier relationship management (SRM) is to streamline and make more effective the processes between an enterprise and its suppliers. SRM includes both business practices and software and is part of the information flow component of supply chain management (SCM). SRM practices create a common frame of reference to enable effective communication between an enterprise and suppliers who may use quite different business practices and terminology. Scope/Detailed Definition This MultiProvider allows a cross procurement system analysis of procurement data in regard to individual purchase orders, goods receipts and service confirmations, and incoming invoices. You can use it to analyze procurement values up to document level. In this way, for example, you can compare ordered values with confirmed and invoiced values for individual purchase order items. Note: You should use the MultiProvider Procurement Overview (Aggregated) for aggregated analyses. Key Figure Requirements The Business Content key figures available are: 1. Confirmed Quantity in Base Unit 2. Confirmed Quantity (BUoM) for Order Date 3. Net Confirmed Value in Default Currency 4. Net Confirmed Value in Default Currency for Order Date 5. Customer from Third-Party PO 6. Expected Net Order Value in Default Currency 7. Freight Costs in Invoice in Default Currency 8. Invoiced Quantity in Base Unit 9. Invoiced Quantity (BUoM) for Order Date 10. Net Invoiced Value in Default Currency 11. Net Invoiced Value in Default Currency for Order Date 12. Order Quantity in Base Unit 13. Purchase Order Tax Amount in Default Currency 14. Net Order Value in Default Currency State of Louisiana LaGov ERP Project Page 1187 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: Characteristics 1. Base Unit of Measure 2. Approver 3. Number of Invoice Items 4. Number of Invoices 5. Buyer ID 6. Catalog 7. Number of Confirmations 8. Delivery Time Variance 9. Number of Confirmed Items 10. Number of Purchase Orders 11. Number of Order Items 12. Number of Perfect Purchase Orders 13. Purchasing Group 14. Purchasing Organization 15. Goods Recipient From Business Partner Table 16. Requester from Business Partner Table 17. Number of Shopping Carts 18. Number of Shopping Cart Items 19. Shopping Cart Quantity in Shopping Cart Unit 20. Logical Procurement System 21. Flag Third-Party Order 22. Product Description Time Characteristics 1. Calendar Day 2. Calendar Year/Month 3. Calendar Year/Quarter 4. Calendar Year/Week 5. Calendar Year Security Requirements There are no standard business content roles. Standard Queries Currently we anticipate use of four business content queries available; 1. Purchase Order Document Analysis 2. Utilization per Purchasing Group 3. Confirmation Document Overview 4. Open Items (Confirmations) State of Louisiana LaGov ERP Project Page 1188 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1189 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: LOG – Supplier Relation Mgmt BDD Number: BIW-SRM-BDD003-LOG – Supplier Relation Mgmt Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Supplier relationship management is a comprehensive approach to managing an enterprise's interactions with the organizations that supply the goods and services it uses. The goal of supplier relationship management (SRM) is to streamline and make more effective the processes between an enterprise and its suppliers. SRM includes both business practices and software and is part of the information flow component of supply chain management (SCM). SRM practices create a common frame of reference to enable effective communication between an enterprise and suppliers who may use quite different business practices and terminology. Scope/Detailed Definition Account Assignment Information in Procurement. This InfoCube allows you to analyze account assignment data for purchase orders, confirmations, and invoices. The InfoCube contains an aggregated view of the account assignment elements, cost centers, the CO order, assets, networks/network activities and the work breakdown structure elements. Additional information about accumulated values and quantities can be determined using the G/L account. When the InfoCube is updated, all values are translated into the standard currency 0DEF_CURRCY. In this way, you can carry out all your evaluations in a standard evaluation currency without losing performance. Key Figure Requirements The Business Content key figures available are: 1. Confirmed Quantity in Base Unit 2. Net Confirmed Value in Default Currency 3. Freight Costs in Invoice in Default Currency 4. Invoiced Quantity in Base Unit 5. Net Invoiced Value in Default Currency 6. Order Quantity in Base Unit 7. Purchase Order Tax Amount in Default Currency 8. Net Order Value in Default Currency 9. Approved Net Shopping Cart Value in Default Currency 10. Expected Shopping Cart Value in Default Currency 11. Shopping Cart Tax Amount in Default Currency 12. Net Shopping Cart Value in Default Currency 13. Tax Amount of Invoice in Default Currency State of Louisiana LaGov ERP Project Page 1190 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: Characteristics 1. Network Activity 2. Asset Sub-number 3. Main Asset Number 4. Base Unit of Measure 5. Approver 6. Buyer ID 7. Procurement Card Company 8. Procurement Card Number 9. Product 10. Purchasing Group 11. Purchasing Organization 12. Goods Recipient From Business Partner Table 13. Requester from Business Partner Table 14. Shopping Cart Quantity in Shopping Cart Unit 15. Document Characteristics 16. Logical Backend System 17. Logical Procurement System 18. Logical FI System 19. Tax Code 20. Product Description 21. Vendor from Business Partner Table 22. Change Run ID 23. Chart of accounts 24. Company code 25. Order Number 26. Cost Center 27. Controlling area 28. Default Currency 29. eCl@ss 30. Version-Independent Key of eCl@ss 31. Version of eCL@ss 32. Fiscal year / period 33. Fiscal year variant 34. G/L Account 35. Purchase Category 36. Location 37. Source System for R/3 Entity 38. Service Provider 39. Vendor 40. Logical Procurement System 41. Material 42. Material group 43. Network 44. Plant State of Louisiana LaGov ERP Project Page 1191 of 1338
  • LaGov ERP Project Business Blueprint 45. Product 46. Product Category 47. Product Category 48. Purchasing organization 49. Purchasing Group 50. Record type 51. Request ID 52. Shopping Cart Unit 53. Storage location 54. UNSPSC Code 55. Version-Independent Key of UNSPSC Code (SQID) 56. UNSPSC Code Version 57. Vendor 58. Value Type for Reporting 59. Work Breakdown Structure Element (WBS Element) Time Characteristics 1. Calendar Day 2. Calendar Year/Month 3. Calendar Year/Quarter 4. Calendar Year/Week 5. Calendar Year Security Requirements Security is maintained at catalog items level and shopping cart level. There are no standard business content roles available. Standard Queries Currently we anticipate use of five business content queries: 1. Overview - Purchase Order Value per Requester 2. Cost Center Overview 3. Purchase Values per Order 4. Purchase Order Status 5. Purchase Orders per Order Number with Items State of Louisiana LaGov ERP Project Page 1192 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1193 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: LOG Supplier Relationship Mgmt BDD Number: BIW-SRM-BDD004-LOG Supplier Relationship Mgmt Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Supplier relationship management is a comprehensive approach to managing an enterprise's interactions with the organizations that supply the goods and services it uses. The goal of supplier relationship management (SRM) is to streamline and make more effective the processes between an enterprise and its suppliers. SRM includes both business practices and software and is part of the information flow component of supply chain management (SCM). SRM practices create a common frame of reference to enable effective communication between an enterprise and suppliers who may use quite different business practices and terminology. Scope/Detailed Definition The InfoCube contains the total spending volume of a company or a group. On the basis of the InfoCube, you can analyze – by vendor, category or product – how much money the company has spent for which material group, or for which account, over a certain period of time. To determine the best price, you can analyze your spending according to the following parameters: • Purchase order reference • Contract reference You can set these parameters in reference to: • Consolidated vendors • Consolidated products • Assigned standard category The total spend can be displayed in three different currencies (transaction currency, company code currency, and group currency). When constructing queries based on this InfoCube, you should ensure that gross and net amounts are not added Key Figure Requirements The Business Content key figures available are: 1. Confirmed Quantity in Base Unit 2. Confirmed Quantity (BUoM) for Order Date 3. Net Confirmed Value in Default Currency 4. Net Confirmed Value in Default Currency for Order Date 5. Customer from Third-Party PO 6. Expected Net Order Value in Default Currency 7. Freight Costs in Invoice in Default Currency 8. Invoiced Quantity in Base Unit 9. Invoiced Quantity (BUoM) for Order Date State of Louisiana LaGov ERP Project Page 1194 of 1338
  • LaGov ERP Project Business Blueprint 10. Net Invoiced Value in Default Currency 11. Net Invoiced Value in Default Currency for Order Date 12. Order Quantity in Base Unit 13. Purchase Order Tax Amount in Default Currency 14. Net Order Value in Default Currency Context / Dimensions Requirements The following analytical dimensions are required: Characteristics 1. Network Activity 2. Asset Sub-number 3. Main Asset Number 4. Base Unit of Measure 5. Approver 6. Buyer ID 7. Procurement Card Company 8. Procurement Card Number 9. Product 10. Purchasing Group 11. Purchasing Organization 12. Goods Recipient From Business Partner Table 13. Requester from Business Partner Table 14. Shopping Cart Quantity in Shopping Cart Unit 15. Document Characteristics 16. Logical Backend System 17. Logical Procurement System 18. Logical FI System 19. Tax Code 20. Product Description 21. Vendor from Business Partner Table Time Characteristics 1. Calendar Day 2. Calendar Year/Month 3. Calendar Year/Quarter 4. Calendar Year/Week 5. Calendar Year Security Requirements Currently we anticipate the use of no standard business content roles State of Louisiana LaGov ERP Project Page 1195 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries Currently we anticipate use of 11 business content queries: 1. Net Invoice Volume with or without Purchase Order Reference 2. Number of Suppliers per Category 3. Splitting the Total Purchase Value over Time 4. Invoices per Account 5. Invoice Values with Purchase Order Ref. and Contract (cons.) 6. Invoice Values per Category 7. Top 15 Categories 8. Top 15 Suppliers 9. Invoice Value per Product Category (Hierarchy) 10. Invoice Value per Supplier (Hierarchy) 11. Number of Suppliers per Category Data Flow Diagram State of Louisiana LaGov ERP Project Page 1196 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Shopping Carts BI High Level Design BDD Number: BIW-SRM-BDD005-Shopping Carts BI High Level Design Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Supplier relationship management is a comprehensive approach to managing an enterprise's interactions with the organizations that supply the goods and services it uses. The goal of supplier relationship management (SRM) is to streamline and make more effective the processes between an enterprise and its suppliers. SRM includes both business practices and software and is part of the information flow component of supply chain management (SCM). SRM practices create a common frame of reference to enable effective communication between an enterprise and suppliers who may use quite different business practices and terminology. Scope/Detailed Definition This ODS object contains information on header, item, and account assignment data of local shopping carts within vendor, customer, regional and product category perspectives. Key Figure Requirements The Business Content key figures available are: 1. Account assignment GUID 2. GUID of shopping cart 3. GUID of shopping cart item 4. GUID of contract 5. GUID of contract item Context / Dimensions Requirements The following analytical dimensions are required: Characteristics 1. Local ID of generic partner 2. Local product ID 3. Local category ID 4. Country 5. Country 6. Region 7. Vendor 8. Reference to material 9. Product ID 10. Reference to service 11. Product category ID 12. Customer State of Louisiana LaGov ERP Project Page 1197 of 1338
  • LaGov ERP Project Business Blueprint 13. Region 14. Vendor 15. Country 16. Customer 17. Industry sector 18. Region 19. Vendor 20. Business partner 21. Country 22. Vendor SIC code 23. DUNS number 24. Industry sector 25. Postal code 26. Region 27. Minority status 28. Women-owned 29. Customer 30. Industry sector 31. Competitor 32. CRM product 33. Division 34. External material group 35. Industry sector 36. Material category 37. Material group 38. Material type 39. Product hierarchy 40. General configurable material 41. Price band 42. Source of supply rule 43. Season 44. Season year 45. Source of supply 46. Industry standard description 47. Type of certification requirement 48. Construction class 49. Function class 50. Product type 51. R/3 product hierarchy 52. Current UN/SPSC code 53. Current version of UN/SPSC code 54. Class of current UN/SPSC code 55. Commodity of current UN/SPSC code 56. Family of current UN/SPSC code 57. Segment of current UN/SPSC code 58. First segment of current eCl@ss 59. Second segment of current eCl@ss 60. Third segment of current eCl@ss 61. Current eCl@ss 62. Current eCl@ss version 63. Purchasing organization 64. Purchasing group State of Louisiana LaGov ERP Project Page 1198 of 1338
  • LaGov ERP Project Business Blueprint 65. Country of plant 66. Distribution channel 67. Plant category 68. Purchasing organization 69. Sales area 70. Plant customer number 71. Sales organization 72. Sales district 73. Indicator: Balance sheet account 74. Indicator: P&L account 75. Profit center 76. Asset class 77. Cost center 78. Controlling area 79. Plant 80. Profit center 81. Order type 82. Controlling area 83. Plant 84. Profit center 85. Responsible cost center 86. Status 87. Business area 88. Change date 89. Controlling area 90. CRM marketing element 91. Profit center 92. Project definition 93. Cost center 94. Commitment item category 95. Application of funds 96. Fund customer 97. Fund type 98. Country key 99. Local ID of partner 100. Plant 101. Region (state, province, county) Time Characteristics 1. Calendar Day 2. Calendar Year/Month 3. Calendar Year/Quarter 4. Calendar Year/Week 5. Calendar Year Security Requirements The security is maintained at catalog items and shopping cart level. There are no standard business content roles. State of Louisiana LaGov ERP Project Page 1199 of 1338
  • LaGov ERP Project Business Blueprint Standard Queries Currently we anticipate use of 11 business content queries: 1. Shopping Carts in C-Room 2. Shopping Carts per Requester 3. Shopping Carts per Order 4. Shopping Carts Per Purchasing Organization / Purchasing Group 5. Shopping Carts per Shopping Cart Number 6. Shopping Carts per Shopping Cart Number with Items 7. Shopping Carts per Catalog 8. Shopping Carts per Contract 9. Shopping Carts per Cost Center 10. Shopping Carts per Product/Product Category 11. Status of Shopping Cart Data Flow Diagram State of Louisiana LaGov ERP Project Page 1200 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: LOG-Supplier Relation Mgmt BDD Number: BIW-SRM-BDD006-LOG-Supplier Relation Mgmt Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Supplier relationship management is a comprehensive approach to managing an enterprise's interactions with the organizations that supply the goods and services it uses. The goal of supplier relationship management (SRM) is to streamline and make more effective the processes between an enterprise and its suppliers. SRM includes both business practices and software and is part of the information flow component of supply chain management (SCM). SRM practices create a common frame of reference to enable effective communication between an enterprise and suppliers who may use quite different business practices and terminology. Scope/Detailed Definition This ODS object contains all information on the approval process like approver, approval key figures, and approval time and date values. If a shopping cart is approved – release status of the shopping cart ‘I1129’ (approved) is active on header level of the shopping cart – all approvers are available. If a shopping cart is rejected – release status of the shopping cart ‘I1016’ (rejected) is active on header level of the shopping cart – only the last approver is available. Key Figure Requirements The Business Content key figures available are: 1. GUID of shopping cart 2. Approver Context / Dimensions Requirements The following analytical dimensions are required: Characteristics 1. Country of Buyer 2. Region of Buyer Security Requirements The security is maintained at catalog items and shopping cart level. There are no standard business content roles. Standard Queries Currently we anticipate use of 3 business content queries: State of Louisiana LaGov ERP Project Page 1201 of 1338
  • LaGov ERP Project Business Blueprint 1. Approval Times 2. Overview of Shopping Carts per Approver 3. Overview of Approved Shopping Carts Data Flow Diagram State of Louisiana LaGov ERP Project Page 1202 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Vendor Evaluation-BI BDD Number: BIW-SRM-BDD007-Vendor Evaluation-BI Business Process Owner: Belinda Rogers, Llewellyn DeFoe, Kenya Lipscomb Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Using the vendor evaluation system ensures more objective ratings. All vendors are evaluated based on predefined and uniform criteria. Defining the weightings and scales of the questions in the web survey document, enables the system to calculate scores for each supplier in the system. Therefore, subjective impressions and judgments of individuals can be removed. In SRM, buyers can use the Vendor Evaluation business process to evaluate suppliers using questionnaire-based surveys. In the Web Survey Cockpit, buyers can easily create web surveys and distribute them via e-mail. Buyer defines which suppliers should be evaluated, who should participate in the evaluation and which questionnaires (eg. DOTD Planning and Development web survey, DOTD Environmental web survey etc.) Need to be used. Buyer can also monitor incoming responses and send out reminders to those who have not responded. Vendor Evaluation can also be linked with the confirmation and invoice entry transactions to evaluate day-to-day activities. This is accomplished by SRM displaying a web survey to the end user at the time a confirmation and an invoice is entered in the SAP SRM system. This process will not be used in the LaGOV solution and one survey is requested to be completed on an as required basis. Scope/Detailed Definition The LaGOV project has decided to use only the offline evaluation process for the vendor evaluation. Key Figure Requirements The Business Content key figures available are: 1. Score 2. Counter 1 3. Counter 2 4. Counter 3 5. Total evaluation counter 6. Denominator 1 7. Denominator 2 8. Denominator 3 9. Total evaluation counter 10. Weighted evaluation level 1 11. Weighted evaluation level 2 12. Weighted evaluation level 3 13. Weighted total score 14. Number of criteria State of Louisiana LaGov ERP Project Page 1203 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Weighting Key 2. Grouping 3 3. Grouping 2 4. Grouping 1 5. Criterion Security Requirements Security roles will include: 1. SAP_BWC_SRM_VENDOR_EVAL Other roles will be determined in realization. Standard Queries 1. Purchasing volume Vendor Portfolio with PO Value and Overall Score Supplier Evaluation 2. Purchasing volume Total Eval. / Purch. Order Value of Vendor over Time Supplier Evaluation 3. Vendor Evaluation of Vendor by Product Category Supplier Evaluation 4. Vendor Evaluation of Vendor by Product Category and Product Supplier Evaluation 5. Vendor Submitted Evaluations (Vendors) Supplier Evaluation Data Flow Diagram State of Louisiana LaGov ERP Project Page 1204 of 1338
  • LaGov ERP Project Business Blueprint 13. Stockroom / Warehouse / MRP Team: BI BDD Name: OPA Costs and Allocations BDD Number: BIW-IM-BDD010-OPA Costs and Allocations Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of OPA Costs and Allocations. It contains all costs and quantities on internal orders (plan and actual using delta extraction, budget, commitment) that were transferred from the ECC Controlling module. The InfoCube also contains the extended partner information (such as partner cost center with master data) for the allocation relationships. Key Figure Requirements The Business Content key figures available are: 1. Amount 2. Consumption Quantity The following additional key figures, restricted key figures, and calculated key figures are required: 1. Actual costs 2. Planned costs 3. Settled costs 4. Commitments 5. Budget (per fiscal year) 6. Overall planning (per fiscal year) 7. Actual revenue 8. Planned revenue 9. Actual consumption quantity 10. Plan consumption quantity 11. WIP: Revenue in excess of billings 12. WIP: Work in process 13. Revenue affecting net income 14. Cost of sales 15. Cost of sales (cannot be activated) 16. Realized loss 17. Reserves for imminent losses State of Louisiana LaGov ERP Project Page 1205 of 1338
  • LaGov ERP Project Business Blueprint 18. Reserves for imminent losses – inclusion cannot be activated 19. Loss 20. Reserve: unrealized costs 21. Reserve: unrealized costs, not capitalized Context / Dimensions Requirements The following analytical dimensions are required: 1. Order number 2. Cost element 3. Controlling area 4. Currency type 5. Partner object type 6. Partner object 7. Key figure category 8. Version 9. Details of value type 10. Value type for reporting 11. Sender/receiver indicator 12. Valuation view 13. Statistics indicator for value type 14. FM area 15. Fund 16. Functional area 17. Grant 18. Partner fund 19. Partner functional area 20. Partner grant Security Requirements Currently we anticipate the use of 1 business content role, which is: 1. Internal Orders Standard Queries There are 10 business content queries available: 1. Internal Order (Detail): Plan/Actual 2. Internal Orders (Group): Budget/Actual/Commitment 3. Internal Orders (Group): Total Plan/Actual/Commitment 4. Internal Orders (Group): Plan/Actual 5. Internal Orders (List): Budget/Actual/Commitment 6. Internal Orders (List): Total Plan/Actual/Commitment 7. Internal Orders (List): Plan/Actual 8. PSM: Internal Order (Detail): Plan/Actual 9. PSM: Internal Orders (Group): Plan/Actual 10. PSM: Internal Orders (List): Plan/Actual State of Louisiana LaGov ERP Project Page 1206 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1207 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: OPA Statistical Key Figures BDD Number: BIW-IM-BDD011-OPA Statistical Key Figures Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction Controlling is focused on documenting actual amounts and planning. Variances are calculated by comparing actual and plan data. Variances are used in decision making in order to control costs within business processes. Income statements such as, contribution margin accounting, are used to control the cost efficiency of individual areas of an organization, as well as the entire organization. Scope/Detailed Definition This BDD implements analysis of OPA Statistical Key Figures. It contains all the statistical key figures posted to internal orders that were transferred from the ECC Controlling Module. Key Figure Requirements The Business Content key figures available are: 1. Quantity 2. Inventory quantity The following additional key figures, restricted key figures, and calculated key figures are required: 1. Actual quantity 2. Actual quantity (non-cumulative value) 3. Planned quantity 4. Planned quantity (non-cumulative value) Context / Dimensions Requirements The following analytical dimensions are required: 1. Order number 2. Controlling area 3. Statistical key figure 4. Version 5. Value type for reporting State of Louisiana LaGov ERP Project Page 1208 of 1338
  • LaGov ERP Project Business Blueprint Security Requirements Currently we anticipate the use of 1 business content role, which is: 1. Internal Orders Standard Queries There are 2 business content queries available: 1. Internal Orders (Group) Statistical Key Figures – Plan/Actual 2. Internal Orders (List) Statistical Key Figures – Plan/Actual Data Flow Diagram State of Louisiana LaGov ERP Project Page 1209 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Material Movements BI Detailed Definition Draft BIW-IM-BDD002-Material Movements BI Detailed Definition BDD Number: Draft Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction This component deals with the following tasks: • Management of material stocks on a quantity and value basis • Planning, Entry, and Documentation of all Goods Movements • Carrying out the Physical Inventory Scope/Detailed Definition This MultiProvider enables you to evaluate materials for which no movement has occurred. Key Figure Requirements The Business Content key figures available are: 1. Quantity of consignment stock 2. Issue quantity: blocked stock 3. Quantity Issued from Consignment Stock 4. Issue quantity: stock in quality inspection 5. Issue quantity: scrap 6. Issue Quantity Total Stock 7. Issue Quantity: Stock in Transit 8. Issue value: scrap 9. Value issued from valuated stock 10. Receipt Quantity: Blocked Stock 11. Quantity Received into Consignment Stock 12. Receipt Quantity: Stock in Quality Inspection 13. Receipt Quantity: Stock in Transit 14. Value Received into Valuated Stock 15. Quantity Total Stock 16. Value of valuated stock The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a State of Louisiana LaGov ERP Project Page 1210 of 1338
  • LaGov ERP Project Business Blueprint Context / Dimensions Requirements The following analytical dimensions are required: 1. Blocked stock 2. Calendar Day 3. Calendar Year/Month 4. Calendar Year/Week 5. Calendar Year 6. Change Run ID 7. Material Stocks/Movements (as of 3.0B) 8. Local currency 9. Material 10. Stock in quality inspection 11. Record type 12. Request ID 13. Stock in transit Security Requirements Security needs to be at the data level on Cost Center / Fund Center data item. Currently we anticipate the use of no business content roles. Standard Queries There is 1 business content queries available: 1. Slow-Moving Items Data Flow Diagram Full data flow is too big to fit here, so the first level is presented below: State of Louisiana LaGov ERP Project Page 1211 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Material Movements BI Detailed Definition Draft BDD Number: BIW-IM-BDD001-Material Movements BI Detailed Definition Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE This component deals with the following tasks: • Management of material stocks on a quantity and value basis • Planning, Entry, and Documentation of all Goods Movements • Carrying out the Physical Inventory Scope/Detailed Definition This InfoCube allows you to evaluate stocks from ERP. Key Figure Requirements The Business Content key figures available are: 1. Value Received - Valuated Stock 2. Value - Valuated Stock 3. Value Issued - Valuated Stock 4. Issue Quantity - Blocked Stock 5. Issue Quantity - Consignment Stock 6. Issue Quantity - Inspection Stock 7. Issue Quantity - Stock in Transit 8. Receipt Quantity - Blocked Stock 9. Receipt Quantity - Consignment Stock 10. Receipt Quantity - Inspection Stock 11. Receipt Quantity - Stock in Transit 12. Inspection Stock 13. Blocked Stock 14. Quantity - Consignment Stock 15. Stock in Transit 16. Issue Quantity - Scrap 17. Issue Value - Scrap 18. Receipt Quantity - Total Stock 19. Issue Quantity - Total Stock 20. Quantity - Total Stock 21. Issue Quantity - Valuated Stock 22. Receipt Quantity - Valuated Stock 23. Quantity - Valuated Stock 24. Consumption Value - Vendor Consignment Stock The following additional key figures, restricted key figures, and calculated key figures are required: State of Louisiana LaGov ERP Project Page 1212 of 1338
  • LaGov ERP Project Business Blueprint 1. n/a Context / Dimensions Requirements The following analytical dimensions are required: 1. Material 2. Plant 3. Storage Location 4. Batch Number 5. Stock Type 6. Stock Categories 7. Vendor Security Requirements Security needs to be at the data level on Cost Center / Fund Center data item. Currently we anticipate the use of no business content roles. Standard Queries There are 21 business content queries available: 1. Warehouse Stock Analytics - Obsolete Stock and Variance 2. Warehouse Stock Analytics - Inventory Turnover 3. Demand/Supply Match - Inventory Values 4. Stock Overview - Extended 5. Inventory Aging 6. Material Range of Coverage 7. Stock Overview 8. Valuated Stock 9. Blocked Stock 10. Consignment Stock at Customer 11. Inventory Turnover 12. Vendor Consignment Stock 13. Vendor Consignment Stock (SUS) 14. Inspection Stock 15. Scrap 16. Stock in Transit 17. Receipt and Issue Blocked Stock 18. Receipt and Issue Consignment Stock at Customer 19. Receipt and Issue Vendor Consignment Stock 20. Receipt and Issue Stock in Transit 21. Receipt and Issue Inspection Stock State of Louisiana LaGov ERP Project Page 1213 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1214 of 1338
  • LaGov ERP Project Business Blueprint Team: BI BDD Name: Material Movements BI Detailed Definition Draft BIW-IM-BDD003-Material Movements BI Detailed Definition BDD Number: Draft Functional Lead (State): Will Kelly Functional Lead (Consultant): Ron Burke BACKGROUND AND SCOPE Introduction This component deals with the following tasks: • Management of material stocks on a quantity and value basis • Planning, Entry, and Documentation of all Goods Movements • Carrying out the Physical Inventory Scope/Detailed Definition This MultiProvider enables you to evaluate stocks from SAP ERP Central Component (SAP ECC). It obtains its data from the InfoCube Material Movements Key Figure Requirements The Business Content key figures available are: 1. Quantity of consignment stock 2. Issue quantity: blocked stock 3. Quantity Issued from Consignment Stock 4. Issue quantity: stock in quality inspection 5. Issue quantity: scrap 6. Issue Quantity Total Stock 7. Issue Quantity: Stock in Transit 8. Issue value: scrap 9. Quantity Issued from Valuated Stock 10. Value issued from valuated stock 11. Receipt Quantity: Blocked Stock 12. Quantity Received into Consignment Stock 13. Receipt Quantity: Stock in Quality Inspection 14. Receipt Quantity Total Stock 15. Receipt Quantity: Stock in Transit 16. Quantity Received into Valuated Stock 17. Value Received into Valuated Stock 18. Quantity Total Stock 19. Quantity of valuated stock 20. Value of valuated stock 21. Vendor Consignment Stock Consumption Value State of Louisiana LaGov ERP Project Page 1215 of 1338
  • LaGov ERP Project Business Blueprint The following additional key figures, restricted key figures, and calculated key figures are required: 1. n/a Context / Dimensions Requirements The following analytical dimensions are required: 1. Batch number 2. Blocked stock 3. Calendar Day 4. Calendar Year/Month 5. Calendar Year/Week 6. Calendar Year 7. Change Run ID 8. Vendor 9. Material Stocks/Movements (as of 3.0B) 10. Local currency 11. Material 12. Plant 13. Stock in quality inspection 14. Record type 15. Request ID 16. Stock Categories 17. Stock type 18. Storage location 19. Stock in transit Security Requirements Security needs to be at the data level on Cost Center / Fund Center data item. Currently we anticipate the use of no business content roles Standard Queries There are 4 business content queries available: 1. Warehouse Stock Analytics - Obsolete Stock and Variance 2. Warehouse Stock Analytics - Inventory Turnover 3. Demand/Supply Match - Inventory Values 4. Stock Overview - Extended State of Louisiana LaGov ERP Project Page 1216 of 1338
  • LaGov ERP Project Business Blueprint Data Flow Diagram State of Louisiana LaGov ERP Project Page 1217 of 1338