Kontakt

Ansicht
Dokumentation

Moving the extractors into PI_BASIS ( RELNBW_310_BCT_CABP )

Moving the extractors into PI_BASIS ( RELNBW_310_BCT_CABP )

rdisp/max_wprun_time - Maximum work process run time   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Moving the extractors into PI_BASIS

Use

For Plug-In 2002.2, the extractors are no longer a component of the Plug-In for the SAP business partner for Basis release 6.20, but rather are a component of PI_BASIS. This does not affect usability. However, as of PI_BASIS 2003.1, the respective DataSources become obsolete with this in CRM and EBP.

Example

Until now, the DataSource 0CRM_BPART_ATTR has to be used in CRM for extracting the business partner master record, because the DataSource 0BPARTNER_ATTR contained in the Plug-In was not available in CRM systems. By moving it, it is possible to work in all SAP systems with DataSource 0BPARTNER_ATTR.
This is valid for Release PI 2003.1, R/3 4.70, and CRM 4.0.

New delta methods

The delta methods for some business partner extractors were changed from 'Delta Using ALE Change Pointer' to 'Delta Using Delta Queue'. This is valid for the following DataSources:

  • 0BPARTNER_TEXT: Business partner texts
  • 0BP_DEF_ADDRESS_ATTR: Business partner standard address
  • 0BP_RELATIONS_ATTR: Business partner relationships

In order not to lose any delta information, the following steps have to be executed for each DataSource before the activation, meaning before the transfer to the new version:

  1. Execute the delta upload for all connected BW systems. This is necessary, because after the Content activation, you can no longer access the old deta records, and these would be lost.
  2. Transfer the DataSource directly thereafter (transaction RSA5).
  3. Replicate the new version in all connected BW systems.
  4. Execute a delta initialization.
    In doing so, note the following:
    1. An initialization without transferring data is technically sufficient. If you should be concerned that delta information was lost during the conversion of the DataSource (by the business partner data changed in the meantime), you can also excute a delta initialization with a data transfer.
    2. The named DataSources are zero-downtime-capable in the new version. This means that directly after starting the delta initialization, the delta is logged in the source system. It does not initially begin with the completion of the initialization.

Zero-Downtime

A zero-downtime delta initialization was enabled for the following DataSources:

  • 0BP_ID_ATTR: External ID numbers for the business partner
  • 0BP_IS_ATTR: Business Partner Industries
  • 0BP_STATUS_ATTR: Business Partner Status

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information






BAL Application Log Documentation   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 3166 Date: 20240603 Time: 031438     sap01-206 ( 53 ms )