User manual BUSINESS OBJECTS ACCOUNTS RECEIVABLE RAPID MART 11.5.4.0

[. . . ] BusinessObjects Accounts Receivable Rapid Mart User's Guide Version 11. 5. 4. 0 Patents Business Objects owns the following U. S. patents, which may cover products that are offered and sold by Business Objects: 5, 555, 403, 6, 247, 008 B1, 6, 578, 027 B2, 6, 490, 593 and 6, 289, 352. Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. [. . . ] Make sure all joins for CUST_PER_TTL_FACT are in the CUST_PER_TTL_FACT context. Make sure all joins for CUST_PER_TTL_FACT_VR are in the CUST_PER_TTL_FACT_VR context. 3. 4. 6. View for DSO (Days Sales Outstanding) Calculation The universe contains a database view CUST_ITEMS_AR_BALANCE_VIEW (on CUST_ITEMS_FACT). It is joined to the CUST_PER_TTL_FACT_VR table and used in the calculation of DSO (Days Sales Outstanding). The view was created so that we can obtain the open Accounts Receivable balance for a customer. This is not available in the Customer Totals fact tables. The SQL to create this view is included with the target schema for the Rapid Mart in the SQL source file: AR_Create_Tables. sql For performance reasons, you may decide to create an aggregated fact table to replace the view. 100 BusinessObjects Accounts Receivable Rapid Mart User's Guide Universe Customizing the Universe 5 1. Create a fact table CUST_ITEMS_AR_BALANCE_FACT with the same columns included in the view. Make sure the columns have the same data types as their source columns in CUST_ITEMS_FACT table. In the Data Integrator job for the Rapid Mart, create a dataflow that runs immediately after the CUST_ITEMS_FACT table is populated. The new dataflow populates CUST_ITEMS_AR_BALANCE_FACT using the same logic used to create the view in SQL source file: AR_Create_Tables. sql In the Universe, replace CUST_ITEMS_AR_BALANCE_VIEW with CUST_ITEMS_AR_BALANCE_FACT, preserving the join to the CUST_PER_TTL_FACT_VR table. There are several objects in the Universe that need to be repointed from the view to the new fact table (highlighted below): 2. 3. 4. BusinessObjects Accounts Receivable Rapid Mart User's Guide 101 5 Universe Customizing the Universe 5. Save and export the universe. 102 BusinessObjects Accounts Receivable Rapid Mart User's Guide Universe Universe Validation 5 Universe Validation When validating the universe within the Universe Designer, some errors are expected and acceptable. They do not harm universe performance in any way. They are detailed below. Unlinked Tables There are 6 tables that are not joined to other tables. This is because we use only aliases of those tables in the universe. However, the original table must remain as a placeholder for the original table name. They are shown below. Object Parsing There are 39 objects that will fail validation. Most are in the Advanced Techniques section. They are all template objects that must be customized to your specific needs. BusinessObjects Accounts Receivable Rapid Mart User's Guide 103 5 Universe Universe Validation The remaining objects fail because they use the "@database" function, but will execute correctly in reports. Also, note that the error messages are specific to your database server. Thus Oracle, SQL-Server, and DB2 will have different messages for the same errors. The screen-shot below shows the object parsing failures in an Oracle environment. 104 BusinessObjects Accounts Receivable Rapid Mart User's Guide Universe Universe Validation 5 Cardinality There is one cardinality error in the join between CUST_PER_TTL_FACT_VR and CUST_ITEMS_AR_BALANCE_VIEW. Cardinality for this join is set to 1:1 in the universe. [. . . ] Add: For example, to customize the Rapid Mart, you might: · · · · · · · Columns from tables already sourced New columns from tables not extracted Aggregates Calculated or scrubbed data You change your Rapid Mart in exactly the same way you would change any Data Integrator application. For information about how to make such changes, see the Data Integrator product documentation. Note: In general, whenever you make a change, you need to perform impact analysis. Impacts to consider include: · · Initial load Incremental load BusinessObjects Accounts Receivable Rapid Mart User's Guide 149 8 Using the Rapid Mart Customizing the Rapid Mart · · · · · · Target tables Integrity of existing Rapid Mart data Integrity between batch extraction and real time jobs Downstream analysis and reporting and Web applications Variable settings used by imported components and sections Other Rapid Mart (in a multi-Rapid Mart environment) If you are implementing the Rapid Mart on Oracle 8i or Oracle 9i platforms, you can take advantage of pre-processing and post-processing performance tuning stored procedures described in "Fact table stored procedures" on page 133 and in the Rapid Mart Deployment Guide. 150 BusinessObjects Accounts Receivable Rapid Mart User's Guide Rapid Mart Data Schema appendix Appendix Table Summary A Rapid Mart Data Schema This appendix provides detailed information about the tables and views in the BusinessObjects Accounts Receivable Rapid Mart for SAP. [. . . ]