SAP ABAP IMG Activity BWISUCS_MARKTNG_0002 (Extract Marketing-Relevant Data)
Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication
   IS-U (Application Component) SAP Utilities
     EE80 (Package) IS-U: Customizing
IMG Activity
ID BWISUCS_MARKTNG_0002 Extract Marketing-Relevant Data  
Transaction Code S_KK4_82000651   (empty) 
Created on 20010309    
Customizing Attributes BWISUCS_MARKTNG_0002   Extract Marketing-Relevant Data 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BWISUCS_MARKTNG_0002    

In this IMG activity you extract the marketing-relevant data from the SAP Utilities (IS-U) industry-specific component, to the SAP Business Information Warehouse (BW). A prerequisite is that you integrate the Marketing (IS-U-CS-MA) component. Only the special features of the extraction are described in this activity. The standard procedure is included in the documentation for BW.

You must perform all steps in BW. To avoid errors, a basic understanding of the interaction of the relevant OLTP DataSources is necessary.

These DataSources are divided up as follows:

  • Master data DataSources
    • 0UCCONTRACT_ATTR (IS-U: Contract, time-independent part)
    • 0UCCONTRACTH_ATTR (IS-U: Contract, time-dependent part)
    • 0UCINSTALLA_ATTR (IS-U: Installation, time-independent part)
    • 0UCINSTALLAH_ATTR (IS-U: Installation, time-dependent part)
    • 0UCPREMISE_ATTR (IS-U: Premise)
    • 0UC_CONNOBJ_ATTR (IS-U: Connection object, with service address)
    • 0CACONT_ACC_ATTR (FI-CA: Contract account, partner-independent part)
    • 0FC_ACCNTBP_ATTR (FI-CA: Contract account, partner-dependent part)
    • 0UC_ACCNTBP_ATTR (IS-U: Contract account, partner-dependent)
    • 0UCBU_PART_ATTR (IS-U: Business partner)
  • Transaction data DataSource

    0UC_ISU_CONSUMPTION (IS-U: Historical consumption values - mass activity)

The master data DataSources that are allocated to the InfoObject 0BPARTNER (business partner), and the DataSources of the CRM marketing project and ERP project system, play a considerable role, on the basis of IS-U data, for CRM target group selection in BW.

Provided that nothing else is specified, the following notes are equally valid for:

  • Full upload
  • Delta initialization
  • Delta transfer

For large installations, we recommend that you avoid a full upload and only use delta initialization and delta transfer.

Recommendations for data quality and performance

  • Upload the marketing-relevant data, in the following sequence:
    1. CRM attribute DataSource from the marketing plan (0CRM_MKTELM5_ATTR). This DataSource is allocate to InfoObject 0CRM_MKTELM.
    2. Master data DataSources from the ERP project system (in particular 0WBS_ELEMT_ATTR). These DataSources are allocated to InfoObject 0WBS_ELEMT.
    3. Master data DataSources from IS-U (as specified above)
    4. Master data DataSources from CRM for InfoObject 0BPARTNER
    5. Transaction data from IS-U (0UC_ISU_CONSUMPTION)
  • Do not permit any online changes before uploading the master data from IS-U, and before the IS-U extraction is complete.

    This is important, because within the update rules in BW for the consumption InfoCube, the master data is read and must have a status suitable for the consumption data. If the load on the IS-U System is too much that online changes cannot be locked during data extraction, see the notes for troubleshooting and error prevention.

  • During the extraction process, do not run any batch jobs that create master data or change allocations.

    You can, however, run the fundamental batch jobs (in particular order creation, billing, invoicing, payment run and dunning run).

  • Allocate the following master data DataSources in pairs to the same InfoObject and group the associated InfoPackages with a view to common scheduling in InfoPackageGroups:
    • 0UCCONTRACT_ATTR and 0UCCONTRACTH_ATTR
    • 0UCINSTALLA_ATTR and 0UCINSTALLAH_ATTR
    • 0FC_ACCNTBP_ATTR and 0UC_ACCNTBP_ATTR
  • For the extraction of transaction data, switch on the master data check in the scheduler.
  • With delta intitialization, you can process the respective master data fields within an InfoSource in parallel, according to number interval.

Notes for troubleshooting and error prevention

  • If additional master data is created during data extraction in the OLTP, the sequence of the master data uploads in step 3 (master data DataSources from IS-U) is of greater importance, in order to achieve high quality data. Follow the sequence for master data DataSources (contract, installation and so on).

    If the posting in the persistent staging area (PSA) or the update program for the InfoCube is canceled when uploading DataSource 0UC_ISU_CONSUMPTION, proceed as follows:

    1. Perform a further delta transfer, at least for the following DataSources:
    2. - 0FC_ACCNTBP_ATTR
      - 0UC_ACCNTBP_ATTR
      - 0UCBU_PART_ATTR
      - 0UCPREMISE_ATTR
      - 0UC_CONNOBJ_ATTR
    3. Restart the extraction of historical consumption values, or repeat the update in the InfoCube.
  • If, subsequently, you must add an attribute to a master data InfoObject,you must initialize the delta for the associated InfoPackage.
  • For maintenance of the transfer rules for InfoSources of historical consumption values, we recommend that from now on you copy all fields offered to the transfer structure. In this way you avoid subsequently adding attributes.

Example

Requirements

Standard settings

Recommendation

Activities

Further notes

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional 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 BWISUCS_MARKTNG_0002 0 I110004874 Marketing 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20010309 
SAP Release Created in 463