Showing posts with label infopackage. Show all posts
Showing posts with label infopackage. Show all posts

Monday, March 7, 2016

A little about InfoPackage / DTP prefixes and BW data request's prefixes

In this post I try to sum up brief information on topic of different InfoPackage and DTPs prefixes. In addition I’m also providing information on BW’s data request numbers prefixes.

InfoPack prefixes:
ZPAK_* - custom developed InfoPack
0PAK_* - InfoPackage activated from BI Content
0GRU_* - BI Content InfoPackage groups, assignment of InfoPacks into Group is in table RSPAKPOS
0GRU_* - custom InfoPackage groups
PRNR_* - automatic update from the PSA into the data targets
INFO_* - InfoPackage for BW-WHM runtime statistics, used on old BW systems(below version 3.x)

DTP prefixes:
DTP_* - regular DTP, has corresponding DTP request ID with naming convention: DTPR_*     
D* - in general any the DTP ID can start with just D prefix
DTPR_SIMULATION    - not real the DTP run, only debug run of the DTP = debugging DTP


Request numbers prefixes:

- General prefixes:
REQU_* - generic request ID created by run of InfoPackage, any request that can be displayed in tcode RSRQ
DTPR_* - generic request ID created by run of the DTP
REBU_* - rebuilding request, it is not real (independent) request, it is the request that has not yet written any RSSELDONE entry, it cannot be displayed in monitor, because it is only number under which an additional rebuilding monitor log for normal load requests is stored.
APO_R* or APO_* - request for APO Demand Planning data, InfoProvider is switched to transactional behavior

- DSO/ODS relevant prefixes:
ODSR_* - ODS activation request or the request loaded from change log of an upstream ODS object using a "Reconstruction" function
ODSA_* - change log activation prefix
ODSU_* - change log update prefix

- Other request prefixes: 
STOR_* - reversal of a request
ARCH_* - requests generated by Data Archiving Processes (tcode RSDAP)

- Request prefixes not more used anymore (as of BW version 3.0B) prefixes:
MDMT_* - generated by master data maintenance functions of BW
R3RD_* - similar as above
RNDI_* - load of master data or text for characteristic using 'RSNDI API' functions

SPOK_* - looks like it was related to InfoSpoke functions

Sunday, March 6, 2016

Shadow InfoPackage

There are a special InfoPackages in the system. They are called Shadow InfoPackages. The shadow infopack is created when BW DataSource objects are activated from the Business Content (BCT). BW system reads the shadow InfoPackages from the table RSLDPIOSH for each DataSource that is to being activated.

Similarly in case of BW is used as a BW content development system, inconsistencies may occur between the A and D versions of the InfoPackage means between the shadow version and version of InfoPackage in cross-reference table RSSHIPDVERS.


All these situations are caused by inconsistencies between the tables RSLDPIOSH, RSLDPIO and RSSHIPDVERS. To remove the inconsistencies there is a SAP standard report which can be used to fix these issues. The report is called RSSM_SHIPDVERS_CLEANUP. It can recognize and corrects these inconsistencies.


When using the report a checkbox "Check Shadow Infopackages' needs to be activated on its selection screen. The report then lists out all Shadow Infopackages along no of records in tables RSLDPIOSH, RSLDPIO and RSSHIPDVERS. By using Repair functionality inconsistencies can be removed.


More information:

Sunday, July 8, 2012

Inconsistency in delta administration


Recently I encountered following error related to delta mechanism:

Inconsistency in delta administration RSM1363


 


Message appeared in my case when I attempted to browse an InfoPackage. If you get this error message InfoPackage is not accessible at all. I research on this message. I came across interesting site which pointed me into way how to resolve this error.
Basically root cause seem to be in tables on ECC and on BW sides storing information on delta initialization requests. It might be that in BW table RSSDLINIT contains entry for initialization for specific data source. On other hand table ROOSPRMSC in ECC does not contain entries for the same.

According note 852443 - Dump in include LRSSMU36/RSSM_OLTPSOURCE_SELECTIONS there are five scenarios that could happened. Two of them are mentioning ABAP report RSSM_OLTP_INIT_DELTA_UPDATE. This tool can be used to delete init selections in the 'Scheduler/Init selections in the source system' menu in the InfoPackage.

Notice that before you do any changes into the BW system you need to study above mentioned note and also other listed below: