This note describes how to use the status concept to extract status information for SAP BW.

Reason and Prerequisites

You are using BW Release 2.0B or higher.
If you are using BW 2.0A, also refer to Note 312927. This describes special cases that apply only to this release.

If you use a Basis Release 6.1 or higher, views 'V_BWCVSYST' and 'V_BWCVUSST' can be modified to a limited extent only, which terminates the call of transactions BWS1 and BWS2. You can prevent this by

  • calling transaction SE11 (ABAB Dictionary: Initial Screen)
  • choosing 'View' and entering the name 'V_BWCVSYST' or 'V_BWCVUSST',
  • choosing the 'Change' ****on,
  • and selecting the line 'Display/Maintenance Allowed' in the 'Data Browser/Table View Maintenance' on the last tab (maintenance status).

As an alternative, you can

  • call Transaction SM30,
  • enter 'V_BWCVSYST' (system status) or 'V_BWCVUSST' (user status) for Table/View,
  • choose the 'Customizing' ****on,
  • select a project or choose 'Continue w/o specifying project',
  • and then select the desired action in the Customizing.

Status concept for Business Information Warehouse

This note is divided as follows:
1.) The principles and functions of the concept
2.) Enhancement and specification of the concept in the customer system

1. The principles and functions of the concept

In R/3 master data, all statuses that are currently active for an object are usually displayed.
In this case, any amount of statuses may be active at the same time. However, there are groups of status values of which only one status may be active.

for example:

Technically completed

A BW status object may be defined in BW Customizing in the source system for one of a certain group of statuses. In this case, the statuses are grouped together under a 4-character abbreviation (indicated below by xxxx). A status number which internally represents the status value is assigned to each status in BW.
A BW status object can either represent a group of system statuses or a group of user statuses. Transactions BWS1 (system status) or BWS2 (user status) can be used for maintenance depending upon the desired type.

The example above corresponds to a large extent to the pre-defined BW status object SYS0 for the system status.

A number must be assigned to each combination of BW /R/3 statuses. For multiple assignments of R/3 statuses for a BW status, the numbers must be distributed sequentially beginning with 1. You may not distribute the value 0 for 'not set'.

The value for a BW status object is transferred into the BW System as an attribute of a master record DataSource. The master data DataSource contains a field for this with the name BWSTXXXX, where XXXX is the name of the BW status object defined in Customizing as a 4-character abbreviation of the name. You cannot currently make a selection for data extraction according to the value of a BW status object.

The field BWSTXXXX is automatically supplied by the extractor with the status number of the status BW status object XXXX active for the particular master data object. If several statuses of the BW status object are simultaneously active for the master data object, the status that has the highest number of status numbers in a group is transferred. If you include the fields BWS1XXXX for the date and BWS2XXXX for the time of the set status, this information may also be loaded into the BW System if required.

For example, the status object SYS0 is used by the DataSource 0PROJECT_ATTR, which can be displayed in the OLTP using transaction RSA6, application PS-IO.

In BW, the field BWSTXXXX of the master data DataSource is assigned to an InfoObject of the naming convention 0STATUSXXXX. The language dependent texts which belong to the statuses of the BW status object XXXX are assigned to this InfoObject. No InfoObjects of this naming convention can be created again in the customer system. Instead, use one with the name ZSTATXXXX.

These texts are transferred into the BW System by the DataSource 0STATUSXXXX_TEXT. The DataSource 0STATUSXXXX_TEXT can be generated in the R/3 System via BW Customizing.

The BW status concept was implemented in the standard system for the following InfoObjects:

  • 0PROJECT Project definition
  • 0WBS_ELEMT WBS element
  • 0NETWORK Network
  • 0ACTIVITY Network activity
  • 0ACTY_ELEMT Network activity element
  • 0COORDER CO order
  • 0PRODORDER Production order
  • 0APPR_REQU Appropriation request (IM))
  • 0PROG_POS Program position (IM)

2. Enhancement and specification of the concept in the customer system

The extractors delivered in the standard system for the objects mentioned above, allow you to add additional information to the transferring status information:

  • - additional statuses
  • - depiction of the date of the last status change
  • - depiction of time of last status change

To add additional status information to existing InfoSources, proceed as follows:

1.) To receive the SAP standard settings for the standard BW status objects, perform an import for the Customizing table BWCVSYSTAT from the delivery client to the customer Customizing client. This should generally take place before the production startup.
You can also use transactions BWS1 and BWS2 to manually implement the Customizing tables BWCVSYSTAT and BWCVUSSTAT.

2.) Use Transaction BWST (you can get there via the BW Customizing in the source system) to create a new BW status InfoObject. You assign a 4 character abbreviation as the name of the new object. The transaction generates a DataSource called 0STATUSXXXX_TEXT, which can be used to extract texts of a status into BW.

3.) Create a new InfoObject in BW. Use the InfoObject 0STATUSSYS0 as a template for the technical settings regarding data type/length and so on. In the customer system, you can only create InfoObjects in the name space Z that are 9-characters in length. Therefore, create an InfoObject in the form ZSTATXXXX. Then update the meta data from the source system to make the generated settings available in BW. Then connect the text DataSource to the InfoObject.

4.) Use the BW Customizing in the source system (transaction SBIW) to assign R/3 status to the created BW status object. In the transactions BWS1 (system status) or BWS2 (user status), assign the required R/3 status with corresponding status numbers for the transfer to BW to the BW status object. Refer to the information above about this topic.

5.) Add the new status attributes to the extract structure of the respective master data DataSource. This is then available in transaction RSA6 'Postprocess DataSources and Hierarchy' in the source system. You have to call this transaction to transfer the structure changes to the DataSource.
In order to add a status object, use the following as the field name: BWSTXXXX and the data type BWST.
To extract the change date of a status, enhance the structure with the field name BWS1XXXX and the data type CDDATUM.
To extract the change time of a status, enhance the structure with the field name BWS2XXXX and the data type CDUZEIT. Note that the date and time can be extracted only in connection with a BW status object that is extracted in the same InfoSource. A separate extraction is currently not possible for technical reasons.

6.) Check the changes in the maintenance for the DataSource of the changed InfoObjects (for example, 0WBS_ELEMT_ATTR). Ensure that these fields are flagged for the extraction. To ensure this, the flag directly behind the status object must not be set. (Fields 'Selection' and 'Hide field').

7.) IMPORTANT: To export the system status and user status correctly to BW, you must use transaction SE16 to set the field NOTEXREL to 'Y' in the table ROOSFIELD for all status fields of the affected master data DataSource.

8.) To make the new fields visible in the BW, perform a meta data upload for the DataSource enhanced in the source system. Assign the respective InfoObjects to the fields. No info was generated for the date and time fields. You may have to create new InfoObjects. For information about the technical appearance of the InfoObject, refer to the InfoObjects 0DATE and 0TIME and reference them.

CLICK HERE for Complete Details & More...

CLICK Here SAP Full Configuration 6000 Real-time Screen Shots

More HOT Jobs Here