SAP ABAP IMG Activity BWCOPA_KEB0 (Create Transaction Data DataSource)
Hierarchy
SAP_FIN (Software Component) SAP_FIN
   CO (Application Component) Controlling
     RS_IMG_CO (Package) OLTP-IMG CO (Controlling)
IMG Activity
ID BWCOPA_KEB0 Create Transaction Data DataSource  
Transaction Code S_AX6_42000006   IMG Activity: BWCOPA_KEB0 
Created on 19990930    
Customizing Attributes BWCOPA_KEB0   Create DataSource 
Customizing Activity BWCOPA_KEB0   Create DataSource 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BWCOPA_KEB0    

In this activity, you can create or delete a DataSource for analyzing data from Profitability Analysis (CO-PA) as well as display its structure.

Create:

You define a DataSource on the basis of an existing operating concern. You can include in your DataSource all or just some of the characteristic and value fields of this operating concern.

A DataSource is defined by the following elements:

  • Operating concern
  • Amount of characteristics
  • Amount of value fields
  • Amount of calculated key figures

Up to and including Plug-In Release PI2003.1, a DataSource is only defined in the current client of the source system. This means that a DataSource can only be extracted from this client. The DataSource has a timestamp for the delta method, and this timestamp is only valid for the current client. This timestamp is managed by Profitability Analysis.

With Plug-In Release PI2004.1, timestamp management was converted to a new method, called generic delta. This method works in combination with a BW system with Release 2.0 and higher. With this method, timestamp management is no longer performed by Profitability Analysis, but instead by the Service API (interface between Profitability Analysis and SAP BW).

Compared to timestamp management in Profitability Analysis, the generic delta allows for several enhancements:

  • You can apply the delta method simultaneously using the same DataSource from more than one client of the source system because a separate timestamp is saved for each logical system.
  • You can apply the delta method for the same client of the source system simultaneously using the same DataSource from several BW systems.
  • You can perform several initializations of the delta method with different selections using the same DataSource from a given BW system for the same client of the source system.
  • The DataSource commands the "Delta Init Simulation" mode. With timestamp management in Profitability Analysis, this mode had to be implemented using the Simulate Delta Method Initialization transaction (see SAP Note 408366).

For more information on the generic delta, see section Delta Transfer, whereby the steps of the "Specify Generic Delta for a DataSource" section are performed automatically for Profitability Analysis when a DataSource is created. For this, the field determining the delta is taken as the timestamp for Profitability Analysis (TIMESTMP), and the timestamp is stored for summarization levels and line item tables. However, in contrast to generic DataSources, the TIMESTMP field is not generated in the extraction structure because this is not necessary for DataSources in Profitability Analysis. As with timestamp management in Profitability Analysis, an upper limit of 30 minutes is set as the safety interval.

You find the timestamp of a DataSource for the delta method in the current logical system either on the "Last Data Transfer" tab page or using the IMG activity Check Delta Queue. The timestamp is shown here when you choose the selection button in the Status column for the combination of DataSource and BW system.

DataSources created after implementing PI2004.1 automatically apply the new method. DataSources that were created in Plug-In releases prior to PI2004.1 still continue to use timestamp management in Profitability Analysis but can be converted to the generic delta in transaction Create CO-PA DataSource. For this, an additional selection option Convert to Generic Delta appears in the selection screen when a DataSource with timestamp management in Profitability Analysis is entered. Conversion from the generic delta to timestamp management in Profitability Analysis is not supported.

Conversion is only possible for DataSources that are defined in the current client of the source system and for which the delta method has already been successfully initialized or for which a delta update has successfully been performed. This is the case once the DataSource has the replication status "Update successful". Furthermore, no realignments should have been performed since the last delta update.

For the conversion, the timestamp for the current source system client is transferred from Profitability Analysis into the timestamp of the generic delta. In this way, the transition is seamless, enabling you to continue to perform delta updates after the conversion. If delta updates are to be performed from different clients of the source system for this DataSource, you first need to initialize the delta method for these clients.

The conversion must be performed separately in each source system because the timestamp information is always dependent on the current R/3 System and is reset during the transport. If, however, a converted DataSource is inadvertently transported into a system in which it has not yet been converted, delta extraction will no longer work in the target system because the timestamp information is deleted during the import into the target system and is not converted to the timestamp information of the generic delta. If in this instance no new delta initialization is going to be performed in the target system for the DataSource, you can execute program ZZUPD_ROOSGENDLM_FROM_TKEBWTS from SAP Note 776151 for the DataSource. This program reconstructs the current time stamp information from the information for the data packages transported thus far and enters this time stamp information into the time stamp information for the generic delta. Once this program has been applied, delta extraction should work again. Normally, however, you should ensure during the transport that the DataSource uses the same logic in the source system and the target system.

After the conversion, the DataSource must be replicated again from the BW system.

A successful conversion is recorded in the notes on the DataSource.

Since the generic delta does not offer any other log functions apart from the timestamp information (status: Plug-In Release PI2004.1), Profitability Analysis still logs the delta initialization requests or delta requests. However, the information logged, in particular the timestamps, only has a statistical character because the actual timestamp management occurs in the generic delta. Since the delta method can be performed simultaneously for the same source system client using the generic delta from several BW systems, the information logged is stored for each logical system (source system) and BW system. When a delta initialization is simulated, only the timestamp of the generic delta is set; Profitability Analysis is not called. Consequently, no information can be logged in this case. Messages concerning a DataSource are only saved for each logical system (on the source system side). You can use the IMG activity Display Detailed Information on DataSource to view the information logged.

Another enhancement from Plug-In Release PI2004.1 means that you can no longer exclusively perform full updates (that is, update mode "F") for DataSources of the Extractor Checker of the Service API that have recently been created or converted to the generic delta. The following update modes are possible:

  • "F" - Full update: Transfer of all requested data
  • "D" - Delta: Transfer of the delta since the last request
  • "R" - Repeat transfer of a data package
  • "C" - Initialization of the delta transfer
  • "S" - Simulation of the initialization of the delta transfer

In the case of all update modes other than "F", you have to specify an BW system as the target system so that the corresponding timestamp and/or selection information for reading the data is found. The "Read only" parameter is set automatically and indicates that no timestamp information is changed and that Profitability Analysis does not log the request.

Update mode "I" (transfer of an opening balance for non-cumulative values) is an exception: Although you can still select this mode, the system issues an error message because Profitability Analysis does not support this mode.

Delete:

You can delete a DataSource that you no longer require.

Example

Requirements

Standard settings

Recommendation

Activities

Create:

  1. Give the DataSource a unique technical name. As a default setting, this name starts with the prefix "1_CO_PA". This prefix is mandatory and cannot be changed.
  2. To create the DataSource, choose DataSource -> Create.
  3. Select the characteristics that are to be included in the DataSource. The DataSource must contain some of these characteristics. These are already selected for you and cannot be deactivated.

    It is also useful to include characteristics that are contained in the segment table and are hence used to create the profitability segments. These characteristics are already selected but you can deactivate them if necessary.

    When selecting the characteristics, ensure that they are formally indepen

Business Attributes
ASAP Roadmap ID 207   Establish Reporting 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BWCOPA_KEB0 0 HLA0009438 Information System 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object KEB0N COPA_KEB0 Dummy Object for Transaction Call from IMG 
History
Last changed by/on SAP  20031209 
SAP Release Created in