尤尼佳01_bw12_Connecting_CO.docVIP

Connecting CO-PA to the SAP BW Contents Introduction The Metadata Maintenance Utility Creating New InfoSources Creating the Missing InfoObjects Realignment of Characteristic Values in CO-PA Displaying an InfoSource Maintaining Existing InfoSources Deleting InfoSources Splitting an InfoSource (SAP BW 1.2A only) Why Will You Need More Than One InfoSource Per Operating Concern? Example (1) Strategy Example (2) The Corresponding InfoCube The Transactional Data Interface Management of Change 1. Introduction In SAP BW releases 1.0 and 1.2 and R/3 releases 3.0D-3.1I, R/3 CO-PA data can be replicated to the SAP Business Information Warehouse. You can choose from the following options: replicate one or more summarization level replicate line items In each case you can run a full update from the data source specified for the initial load of the warehouse. You can then run delta updates (e.g. on a daily basis) from the line item tables to keep the replicated data in the warehouse current. Using the extractor software supplied and applying the techniques and procedures described in this document will guarantee the consistency of the replicated data (up to the replication gap). 2. The Metadata Maintenance Utility In contrast to other R/3 applications, which can deliver predefined InfoSources for SAP BW together with the extractor software, all CO-PA InfoSources must be generated (similar to the operating concerns itself). A CO-PA InfoSource can be defined on the level operating concern and client. The InfoSource itself consists of the following information: name of the operating concern client source of data for full update (summarization level, segment level, line items) subset of the set of characteristics to define the detail of replication subset of the set of value fields replication status (InfoSource defined, full update in progress, delta update in progress, update complete, invalidated) timestamp to define which data has already been replicated to