BW Object Status - OBJSTAT

Many BW objects use so called concept of Object Status. It indicates whether the object is active and is usable (e.g. executable) in the system. Let’s take an example of a DTP object. In addition to Object Version information and Indicator of Saved/Not Saved and there is the Object Status for each of the DTP in the system.

There are following values that the Object Status information can consist of:

ACT = active, executable. An object with this status can be executed or used.

PRO = productive. This status is a one step further from ACT, but is currently not yet implemented in the BW systems.

INA = inactive. The object is not executable/useable. This is the case, for example, if

·        object has been created and saved for the first time, but has not yet been activated,

·        object firstly has to be revised after changing one of the others.

OFF = switched off. The object is not useable. It was deliberately switched off so as not to appear, for example, in the list of useable objects.

DEL = logical deleted

<blank> =  DTP doesn't exist

 

Statuses ACT and PRO are the ones that indicate that the object is executable/useable.

 

Technically the BW tables contain column OBJSTAT that refers to ABAP DDIC domain RSOBJSTAT that is type of CHAR 3. In case of the DTP object the table that stores Object Status information is RSBKDTPSTAT (Status Information on Data Transfer Process).

Some other BW objects that use concept of the Object Status are BW query components, InfoSources, BW Formulas, Application components, ABAP routines, Open Hub Destinations, BPC model, BPC environment, Remodeling Rules, HANA Analysis Processes, Directory of InfoAreas, InfoObject catalogs, Directory of all InfoObjects, Open ODS View, Process Chains, Planning Sequence, Transformations, Workspaces, info cubes, etc.

 

More information:

Object Version

What is TLOGO in SAP BW terms?

I mentioned the TLOGO term in my previous post. I just add short explanation of what it means. The TLOGO just represents different BW object types. TLOGO most likely refers to Transportable Object Type. To dig deeper to that, there are always two logical transport objects that represents the BW objects. There are the objects:

·        customer

·        delivery TLOGO object

The BW writes the TLOGO object as per the system settings to the transport request when transporting the particular object.

For more details see domain RSTLOGO in data dictionary.

The different TLOGOs can be also spotted in t-code RSA1 in Metadata Repository.

As of version BW 74 there are following different BW object types present:

CTRT   Currency Translation Type

UOMT  Quantity Conversion Type

AREA   InfoArea

APCO  Application

ROUT  Routine

RSFO  BW Formula

IOBJ    InfoObject

IOBC   InfoObject Catalog

ODSO  DataStore Object (classic)

ADSO  DataStore Object (advanced)

CUBE   InfoCube

AGGR  Aggregate

HYBR   HybridProvider

LPOA   Semantically Partitioned Object

ISET    InfoSet

COPR  Local CompositeProvider

ODPE  Operational Data Provider (ESH-Based)

FBPA   Open ODS View

MPRO  MultiProvider

HCPR   CompositeProvider

ALVL   Aggregation Level

DAPA  Data Archiving Process

ISTD   3.x InfoSource

ISCS   Communication Structure

TRCS   InfoSource

UPDR  Update Rules

LSYS   Source System

ISFS   3.x DataSource

RSDS  DataSource

INSP   Inspection Plan

ISMP   Transfer Rules

ISTS   Transfer Structure

DEST   Open Hub Destination

ELEM   Query Element

HAAP   SAP HANA Analysis Process

TRFN   Transformation

ISIP    InfoPackage

ISIG    InfoPackage Group

RASE   Reporting Agent Setting

RAPA   Reporting Agent Scheduling Package

RRCA  RRI InfoCube Receiver

RRQA  RRI Query Receiver

XLWB  Workbook

SPOK  InfoSpoke

EVEN   Event Processing Chain

DDAS  Data Access Service

RSPT   Process Chain Starter

RSPI   Interrupt Process

WWPA Web Design Time Parameter Metadata

WWIB  Web Design Time Item Metadata

QVIW  Query View

EREL   Enterprise Report: Reusable Element

ERPT   Enterprise Report

ITEM   Web Item (Format SAP BW 3.x)

BITM   BEx Web Item

TMPL   Web Template (Format SAP BW 3.x)

BTMP  BEx Web Template

KPDF   KPI Definition

KPCE   KPI Catalog Entry

BRSE   Broadcast Setting

ANMO  Mining Model

ANSO  Model Source

DMMO Data Model (currently not used)

ANPR  Analysis Process

ACGR  Role

CRWB  Crystal Report

AQBG  InfoSet Query User Group

AQSG  InfoSet

AQQU  InfoSet Query

DTPA   Data Transfer Process

PLST   Planning Function Type

PLSE   Planning Function

PLSQ   Planning Sequence

THEM  Theme

PLCR   Characteristic Relationships

THJT   Key Date of Type Derivation

DMOD Data Flow

RSPV   Process Variants

RSPC   Process Chain

PLDS   Data Slices

ENHO  Enhancement/Append

ASOB  Analytics Security Object (BI Analysis Authorization)

RRUL   Remodeling Rule

RDAC  Configuration for Real-Time Data Acqusition

APPS   Appplication Set (BPC - Transport)

BIXP   Conversion Object

XCLS   Xcelsius Dashboard

AAOE  Analysis Office Excel Workbook

AAOP  Analysis Office PowerPoint

TRPR   Operational Data Provider

AZAP   Analysis Application

ENVM  BPC Unified Environment

MODL  BPC Model

TEAM  BPC Team

WKSP  BPC Workspace

BBPF   BPC BPF

BDAP  BPC Data Access Profile

AZEX   Design Studio Extension

AINX   Local Provider

AABC  AVA Global Setting

AADT  AVA Global Setting

AAPP   Model

AAPS   Environment

ABPC   Business Unit

ABPF   BPF

ABRU  Business Rule

ACGA  Configuration

ACGP  Configuration

ACGS  BPC System Configuration

ACLB   Library

ACTR   Control

ADAF  Data Access Profile

ADEE   BPC Deletion Enttiy

ADEI   Deletion Item

ADEL   BPC Deletion

ADIM   Dimension

ADMC  Data Manager Data File

ADMD  Data Manager File Folder

ADMF  Data Manager File

ADML  Data Manager Package Link

ADMP  Data Manager Package

ADTG  Drill Through

AFLD   File Folder

AFLE   Files

AFLG   Business Unit

AFLC   Category

AJUT   Journal Template

AKPI   AVA KPI Setting

AMBR  Dimension member

AMPF  ToBeDeleted

ARTP   Templates

ASPD  Script Folder

ASPF   Script File

ASPR   Script Logic

ATEM  Team

ATPF   Task Profile

AWSS  Workstatus

Different versions and statuses of BW objects

While working with BW objects one may encounter with different versions and statuses they may have.

Version of BW object (domain OBJVERS) is used to differentiate last active version and the modified version. E.g. if some settings within the BW object has changed from X to Z then before the object is activated then value of X is presented within record having OBJVERS 'A' and the value of Z will be in the 'M' record of the BW object. Once the object is activated then Z will be present in 'A' version.

To track changes within the BW object following customizing can be enabled: SPRO –>SAP Reference IMG –>SAP Net Weaver –>Business Warehouse –>General Settings –> Create Historical TLOGO Versions Automatically. Enabling this; the system may store historical versions of the specific BW object type (so called TLOGO – domain RSTLOGO) in case whether is created before the object of the relevant type is exported, imported or activated. The historical version enables you to monitor changes made to an object over time. Historical version can be generated in event of:

- Automatic version creation of export

- Automatic version creation after import

- Automatic version creation before activation

 

Objects versions of rest of BW objects (e.g. cubes, variables, etc) as defined in domain RSOBJVERS:

A        Active

M        Revised

N        New

D        Content

H        Historic

T        Transport

R        Retrofit (for some object types like BW transformations)

 

Object version for BI Metadata Search as domain RSOSOBJVERS:

A        Active

D        Content

 

Object versions of query elements - Usually query elements might be presented in the database tables in several objects versions:

A - Active version used by the BEx Query Designer and OLAP

B - Backup version represents 3.x definition in 7.x system

D - Delivery version. The objects created and delivered as SAP Business Content

M - Modifiable version. Used in transport. Query elements are imported into a target system in 'M' object version.

S - A backup object version created by the report SAP_GLOBV_CHECK.

 

Status of BW object describes whether the object is currently active or not. If it is active the value in is set to 'ACT', otherwise it will be 'INA'. The same value will be present in the 'A' and 'M' records for this field.

Object Status of BW object (DTP, LPO, TRFN, OpenHub, etc.) as per domain RSOBJSTAT:

ACT    Active, executable

INA     Inactive, not executable

OFF     Switched off

PRO    Productive

 

More information:

SDN wiki on Query Elements