Notes on Repairing and Avoiding Errors 

For the extraction of marketing-relevant data, note the following information:

·        Transaction data can only be transferred for contracts that are either billable or were billed using the QUANTI23 variant program. If the transaction data for your contracts is partially missing, use a billing simulation to verify that the contracts can be billed. To do this, go to the SAP Easy Access menu and choose Utilities Industry ® Billing ® Billing Execution ® Individual Processing ® Billing Analysis. Start a simulation that covers the period from the move-in date of the contract to the extraction date minus one day, and display the log.

·        If additional master data is created in the OLTP during data extraction, the sequence of the master data upload in step 3 (master data DataSources from IS-U) becomes important for securing the quality of the data. The 0UCMA_PC01 process chain optimizes this sequence. You must also observe this sequence in the process chains that you created yourself.
If missing master data causes the update to the Persistent Staging Area (PSA) or the update program for the InfoCube to terminate during the upload to the 0UC_ISU_CONSUMPTION DataSource or the 0UC_ISU_CONSUMPT_02 DataSource, proceed as follows:

...

                            a.      Perform an additional Delta update, at least for the following master data DataSources:

§         0FC_ACCNTBP_ATTR

§         0UC_ACCNTBP_ATTR

§         0UCBU_PART_ATTR

§         0UCPREMISE_ATTR

§         0UC_CONNOBJ_ATTR

                            b.      Restart the extraction for historical consumption or repeat the update to the InfoCube.

·        If you want to add an attribute to an existing master data InfoObject, you must initialize the delta for the corresponding InfoPackage.

·        When you maintain the transfer rules for the historical consumption InfoSource, we recommend you adopt all the fields available in the transfer structure. This ensures you do not have to subsequently add any fields.

·        When master data is updated, the system uses the master data tables to verify the existence of the attribute values that themselves contain master data (for example 0CITY_CODE, 0STREET_COD, 0POSTCD_GIS, 0COMP_CODE, 0DIVISION, 0CRM_MKTELM, 0CRM_PROD). Additional consistency checks are based on the permissibility of plus/minus signs in the key fields (during external number assignment in the OLTP) and on master data with time-dependent attributes (time slices must not overlap). We therefore recommend that you first load the master data to the PSA only, where you can re-process incorrect records, and then start the update to the master data tables manually.

·        During the transaction data update for historical consumption (DataSource 0UC_ISU_CONSUMPTION or 0UC_ISU_CONSUMPT_02), we recommend you choose the Do not update data if no master data exists for a characteristic option. Also see the information below on repairing errors.

·        Only applicable when using the 0UC_ISU_CONSUMPTION DataSource: If, during the staging process, you cannot avoid parallel online changes in the OLTP then individual master data records may be missing when you load the consumption history. This is because the master data records are created in the OLTP shortly before loading. In this case, we recommend that you configure error handling in the scheduler as described below. The incorrect data records are loaded back to the PSA and can be imported in a new delta upload.

Note the following information on avoiding errors:

·        After a delta upload for master data DataSource the master data must be activated. If you are using a process chain based on the template of 0UCMA_PC01, this takes place automatically within the attribute change runs for the various master data characteristics.

·        If a PSA request has been assigned the status Incorrect, the status in the Manage Data Targets must be set to green before the data of subsequent successful requests can be evaluated.

Special Features of the Extraction of Marketing-Relevant Data

Note the following points:

¡        The business partner attributes should always be loaded from the CRM system

¡        The industry texts must be loaded from the CRM system (with the 0IND_SECTOR_TEXT DataSource)

¡        City and street codes should be loaded from the IS-U system (with the 0CAM_CITYCODE_TEXT and 0CAM_STREETCODE_TEXT DataSources)