Child pages
  • Common Issues Related to Semantically Partitioned Obejcts - SPO
Skip to end of metadata
Go to start of metadata

This page covers Common issues related to SPO objects.

Error 1:

Transport of BADI BAdI IF_RSLPO_BADI_PARTITIONING & SPO doesnt work correctly.

Solution:

The BAdI IF_RSLPO_BADI_PARTITIONING is intended to be used only in DEV systems. It is currently not called in target systems during the after import phase. The advantage is that the any SPO has the same properties in any target system as compared to the DEV system where the SPO has been created. This is also the standard behaviour for all other BW TLOGO objects. If the requirment is to have SPOs that looks different in the target system as compared to the source system, manually SPOs need to be adjusted in target system. For this purpose,  implement the BAdI IF_RSLPO_BADI_PARTITIONING also in the target system and use this BAdI, for instance by running the program RSLPO_MASS_ACT in the target system.

However, there is a BADI: 'RSO_BADI_TRANSPORT' . See also:
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4a/780dfc3109731ee10000000a42189c/frameset.htm
By implementing the Business Add-Ins (BAdI) RSO_BADI_TRANSPORT, you can automatically trigger subsequent activities such as the execution or rescheduling of process chains after objects have been imported. Here,  the method AFTER_IMPORT of the interface IF_EX_RSO_TRANSPORT is  executed after the standard BW after-import methods are finished.
For more information, see Implementation of BAdls in the Enhancement Builder and in the method documentation for IF_EX_RSO_TRANSPORT AFTER_IMPORT.

Error 2:

Its not possible to create SPO based on virtual provider

Solution:

You can use a Semantically Partitioned Object (SPO) to create identical partitions, which are either based on a reference InfoCube or on a reference DataStore object. This concept works only for "real" objects, for which tables are to be created on the database. It does not work for any "virtual" objects like VirtualProviders. 

Error 3:

Delta functionality is not supported for SPO based on DSO

Solution:

Delta extraction from SPOs is only available for Infocube-based SPOs and not DSO-based SPOs. Therefore, since at the time of creation of the DTP template, it is not known if the source SPO is DSO-based or Cube-based, we do not allow the delta option while creating the DTP template. However, after the DTP has been generated (with FULL mode), you can change the extraction mode in the DTP maintenace if the SPO is Infocube based. You could also refer to the following link for more information:

http://help.sap.com/saphelp_nw73/helpdata/en/d6/0ea95ace6647968bdbba22ba8631ad/frameset.htm

Known Corrections: 

General

 

1860147

Technical enhancement for activation of 'RSLPO_MASS_ACT'

1847954

730SP10:Change of dataclass for active table/activation queue of DSO or SPO based on DSO does not work correctly

1821231

730SP10:SPO on write-optimized DSO: incorrect data aggregation

1798684

Termination when changing InfoProviders despite display auth

1789063

Error message "DataStore object x belongs to higher-level InfoProvider; display only"  

1725352

SP08: SPO extraction to DataStore object fails

1753406

Activatig SPO: Syntax error in GP_ERR_RSTRAN_MASTER_TMPL

1750896

DUMP in CL_RSLPO_VERS_CMPR_VIEW

1735328

Change to InfoArea is complete only after activation

1737763

Improved error handling in SPO context

1715267

RSLPO_GUI026 - Initialization of semantically partitioned object cancelled

1698063

Dump ASSERTION_FAILED in CL_RSLPO_LOCKS

1614501

Activating an InfoCube based SPO with Aggregates dumps

1665315

SP07: MultiProvider hint in the MultiProvider extractor

1639752

Master Data deletion for InfoObjects used in SPOs

1613780

Missing translation in transaction RSLPO_MASS_ACT

1562958

Error handling corrected in transformation context

Process chain

 

1610966

SPO Process Chain Generation : Write-Optimized DSO

1641630

Orange: SPO ProcessChain Generation - Index drop/recreate

DTP

 

1739116

SPO: DTP overview loses selection and positioning

1700148

DTPs cannot be changed or activated after SPO activation

1567365

DTP Generation for SPOs with 3.x Datasources not possible

Transformation

 

1844751

730SP10:SPO migration leads to transformation deactivation

1666890

730SP7:Copying transformations associated with SPO

1656648

Activate SPO: Runtime error OBJECTS_OBJREF_NOT_ASSIGNED

1649470

Expert routine w/ data target of the SPO type does not work

1652082

Termination ASSERTION_FAILED in class CL_RSTRAN_TRFN_VERS

1846983

730 SP10:Key Figure Assignment lost for inbound transformations of SPO based on cube

1788882

NW BW 7.30(SP09): Currency/unit conversion for SPO

1735254

730SP8:RSDG_TRFN_ACTIVATE doesnt activate TRF related to SPO

1581253

DTPs with inactive transformations cannot be changed

HANA DB

 

1785116

SPO: SAP HANA conversion for write-optimized DSO SPOs

1668468

SPO: Data conversion to "SAP HANA optimized" - Part 2

1651357

SPO: Data conversion to "SAP HANA optimized" - Part 1

1750721

SPO: Query on SAP HANA-optimized InfoCube SPO terminates

1685280

SPO: Data conversion for SAP HANA-optimized partitions

Partition

 

1683252

SPO: Termination when displaying partitions

1804868

Semanticaly partitioned objects

1771001

SPO activ. takes a very long time if many partitions exist

1634889

Activating SPOs with Partitions fails

1824272

SPO Semantic Partitions possess incorrect DB Partitioning

1684236

Activate SPO: Database partitioning and 0FISCVARNT

1794510

730SP9:Problem in Semantic Partition Selection Critieria in SPO

1590179

SPO: Limitation for maximum of 99 partition increased

1592879

SPO: Metadata sharing for DataStore-based partitions

1631635

SPO: Texts for InfoCube partitions are incorrect

1738982

SPO: Partitions deactivated after InfoObject is activated

1546207

SPO: Partition maintenance without existing BAdI terminates

1558562

Partition overview for semantically partitioned InfoProvider

Archiving

 

1745839

How to create an archiving request in a Semantically Partitioned Object

1642825

No archive overlap check when activating SPO DSO

Transport

 

1790597

ASSERTION Failed , transport runtime of SPO

1651932

Transport: Reimport of SPO but no activation

1784970

SPO: Activation in after-import mode

1578946

SPO transport: Change to SPO structure fails

1671108

Semantically Partitioned Object missing text after transport

 

Link to this page: http://wiki.sdn.sap.com/wiki/x/igFIF

1 Comment

  1. Former Member

    Hi, not sure how to add a relevant note:

    1934385 - Flatten scenario fails for SPO with navigation attributes switched on