User manual BUSINESS OBJECTS PROFITABILITY AND COST MANAGEMENT 7.0 FOR WINDOWS DATABASE GUIDE FOR MS SQL SERVER

[. . . ] Profitability and Cost Management Database Guide for Microsoft SQL Server BusinessObjects Profitability and Cost Management 7. 0 windows Copyright © 2009 SAP® BusinessObjectsTM. SAP BusinessObjects and its logos, BusinessObjects, Crystal Reports®, SAP BusinessObjects Rapid MartTM, SAP BusinessObjects Data InsightTM, SAP BusinessObjects Desktop IntelligenceTM, SAP BusinessObjects Rapid Marts®, SAP BusinessObjects Watchlist SecurityTM, SAP BusinessObjects Web Intelligence®, and Xcelsius® are trademarks or registered trademarks of Business Objects, an SAP company and/or affiliated companies in the United States and/or other countries. SAP® is a registered trademark of SAP AG in Germany and/or other countries. All other names mentioned herein may be trademarks of their respective owners. [. . . ] Update the Loadstatus for processed items. Property Load Pre-validation Steps: 1. Validate Load identifier supplied is valid. Profitability and Cost Management Database Guide for Microsoft SQL Server 85 4 Data Loader for Microsoft SQL Server Procedure Logic 3. Flag any property items in the load dataset that are duplicates, and leave just the one copy. Identify records with matching keys then remove matching records from the schema where Loadstatus is 70. Flag any property names which do not exist where Loadstatus is 1 for later use. Update the load status for processed items (apart from status 70). Property Item Value Load Pre-validation Steps: 1. Flag any property items in the load dataset that are duplicates, and leave just the one copy. Identify records with matching keys then remove matching records from the schema where Loadstatus is 70. Flag any dimension item names which do not exist where Loadstatus is 1. Add all new property item values that have passed validation at the root level. Update the Loadstatus for processed items, apart from status 70. 86 Profitability and Cost Management Database Guide for Microsoft SQL Server Data Loader for Microsoft SQL Server Procedure Logic 4 Value Load These are data only related procedures and in the main, validation will center on ensuring that the names supplied exist in the model being loaded. Cases exist where one loading table can supply more than one database table. An example of this is the Line Item Value procedure, where one record can potentially create two rows in the Profitability and Cost Management schema, one in PP_LINEITEMVALUE and the other in PP_LINEITEMDELTA, assuming of course the VALUE and the DELTAVALUE fields in the staging table are non-zero. The following sections detail the validation steps taken for the value procedures. Initially the model, load and user details are validated, and then each dimension making up the value key will be checked to ensure that the item exists in the relevant model dimension. If an item is found that does not exist, the record will be flagged with the relevant Loadstatus code and the procedure will move on to the next record in the staging table. Flag any records in the load dataset that are duplicates, and leave just the one copy. Identify records with matching keys then remove matching records from the schema where Loadstatus is 70. The relevant dimension checks will be carried out. Activity Driver Value (PP_ACTIVITYDRIVERVAL UE_LOADMAIN ) Data is written to the following tables: · PP_ACTIVITYDRIVERVALUE · PP_ACTIVITYDRIVERDELTA · PP_ACTIVITYDRIVERTARGET Profitability and Cost Management Database Guide for Microsoft SQL Server 87 4 Data Loader for Microsoft SQL Server Procedure Logic Write Steps: 1. Add data into the delta table if the @INLOADACTIVITYDRIVERDELTA parameter value is set to true. Add data into the target table if the @INLOADACTIVITYDRIVERTARGET parameter value is set to true. Update Loadstatus for processed records. Activity Driver Volume (PP_HVACTIVITYDRIVER VOLUME_LOADMAIN) Data is written to the following table: PP_HVACTIVITYDRIVERVOLUME Restriction: This package must only be initiated by the EPMConsole command: loadvol umedata, because it can only be executed as part of the PPHV_LOADSTAGE procedure. [. . . ] udfSERVICENAMENO TEXIST 21 22 23 24 Profitability and Cost Management Database Guide for Microsoft SQL Server 335 7 Appendices LOADSTATUS Field Values and Constant Names LOADSTATUS Field Val- Description ue 25 The Spread name does not exist (Values). The Worksheet2 name does not exist (Values). Constant Name udfSPREADNAMENO TEXIST udfWORKSHEET1NA MENOTEXIST udfWORKSHEET2NA MENOTEXIST 26 27 28 The Capacity name does not exist udfCAPACITYRULENA (Values). MENOTEXIST The User Rule name does not exist udfUSERRULENAMENO (Values). TEXIST The Line Item Detail name does not udfLINEITEMDETAILNA exist (Values). [. . . ]