Application Load Status Program Documentation
The objective of this program is to provide the BW administrators, as well as internal users, a collective of BW process chain statuses displayed in a common table for simpler reviewing.
The table consists mostly of major or critical process chains existing in the BW environment and currently are being monitored on a daily basis. The chains are monitored by BW administrators and status reports are usually generated daily to inform the BW team and users. While status reports are useful for the BW team to review and resolve issues, internal users are not concerned with these issues and do not access to BW data systems.
This program serves as a quick status update to users regarding the process chains' health and completion progress. At the same time, it is an update based on estimation and is by no means an accurate representation of the process chains' operations.
Program Details
toc scope="LOCAL"/
ABAP source
To access or make changes to the ABAP source for this program, navigate to the ABAP Editor screen or transaction SE38. In the program field, input ZWBWD_APPLOADSTATUS and select * isplay*.
Program Variants
On the initial screen, if you select Variants instead of * ource Code* and select * isplay*, you will see another screen. This will show you the available program variants that have been created accordingly for the relevant process chains being monitored.
!Attachment Library^SE38ProgVariants.jpg|cleanup="null" kids="null" pendingsrc="null" !
To see all available variants, click on the list button beside the Variant field. You will see a popup dialog list containing all the variants.
For each relevant process chain, there are 4 program variants created. Where xxxx stands for the relevant process chain:
V_xxxx_E00* - The process chain has started successfully but encountered errors.
V_xxxx_E25* - The process chain at this point of time has completed/progressed at least 25% overall but encountered errors.
V_xxxx_S00* - The process chain has started successfully.
V_xxxx_S25* - The process at this point of time has completed/progressed at least 25% overall.
!Attachment Library^SE38ProgVariants2.jpg|cleanup="null" kids="null" pendingsrc="null" !
Variant Placement
To add a variant into a process chain, there are several things to take note before proceeding.
In the RSPC monitor screen, when a process chain has been selected to view, check that the chain is in planning view and change mode has been selected (in change mode, the background in the chain window is white instead of gray).
Right-click on the topmost subchain (usually indicated as Start , and select Maintain Variant
On the next screen, take note of the scheduling options selected. You will need to make sure that the schedule option is the same when you reschedule the process chain after you finish adding the variants. Once you have taken note, you may exit this screen for now.
Back on the prvious screen, with the Start subchain still selected, go to the menu bar at the top of the screen and select Execution From the dropdown menu, select Remove from Schedule IMPORTANT: Before removing from schedule, please ensure that the process chain is not currently still running * R* is scheduled to run anytime soon at the time of editing. This is to prevent any conflicts in the operations of the process chains. Please wait until the process chain is completed before making any changes.
Next select Process Types.
Next double-click on ABAP Program under * eneral Services*. You will see a popup dialog like in the screenshot below. In the * rogram* field, input RSV_ and click on the list button to the right of the field.
You will see another popup listing all the available variants. Depending on where you decide to place the variant, select a relevant variant to insert. You can only insert a variant one at time.
After inserting the variants, you need to link them to the correct subchains that are already present. Depending on the subchain that is supposed to be linked to the variant, there are different conditions for the variants to fulfill their role.
For example, the Started Successfully variant will be triggered regardless, therefore the link is black, indicating a direct link without status conditions. For the * 5% Completed* variant, the subchain that it is linked to has to be completed successfully in order for the variant to be triggered, therefore the link is represented in green. Vice versa, the * 5% Completed with errors* variant has a red link which will be triggered if the linked subchain encountered errors during its run.
The next step is important. Firstly, (1) you will need to save the changes made. After which, (2) you need to reschedule the process chain to ensure that the variants are activated and that the process chain will be triggered on schedule. Click on Execution on the top menu bar and select * chedule*. Alternatively, you may simply press * 8*.
You will see a popup like the following screenshot. You may leave the Host field empty and click on the green tick button or press * nter*.
On the next popup, select a suitable priority(usually Priority A and click on the green tick button or press Enter
The process chain is now saved and scheduled. This concludes the placement of the variants within a relevant process chain.
Program Variant Monitoring
Assuming that the relevant program variants have been placed accordingly, the next step is to monitor the status data collected by these variants. There are 2 different levels for monitoring. One is for adminstrators who have access to the warehousing workbench RSA1. You will be able to directly access and edit the master data table used for this program. You will be able to make corrections promptly in case of incorrect reporting of data so that to ensure the accuracy of the status update to the users.
The other monitoring level is for users accessing the status update report using BEx Analyzer. This is done by opening a workbook which extracts data from the master data and display the information in table and graph formats.
Monitoring from RSA1
In RSA1, navigate to the master data table. The master data table can be found in InfoObjects>>Rhodia>>Application status load>>Application load char>>BW Application Char Tech name is C_BWAPP). Right click on the infoobject and select Maintain master data
On the following screen, you do not need to fill in any of the selection fields as you will want to see all data collected. Just click on the Execute button or press * 8*.
You will see the table once it's fully loaded. The table will display all the information collected from the program variants when they are triggered within the process chains. Here you can make amendments to the data directly. Take note that you must remember to save and activate the master data again in order for any changes to take effect.
To edit any of the records, highlight the record and click on the pencil button on the toolbar or press F6 To save, click on the Save button near the top menu bar or press Ctrl+S
After saving, you need to activate the master data. To do this, go back to the RSA1 main screen and right-click on the infoobject again. This time, select Activate master data Upon successful activation, you will see a short notification message at the bottom statusbar. In some cases, you may receive a popup indicating that the master data is already active. This means that your amendments do not require reactivation but it is always recommended to perform this step to complete your changes.
Monitoring from BEx Analyzer 3.x
For users who want to know the latest status update of the process chains, a workbook has been created for this purpose. The workbook will display the same results as viewing from RSA1. Users will be able to filter the query results according to BW roles or simpy view all status updates.
In BEx Analyzer 3.x navigate to Add-Ins and click on the * pen* button. Select * orkbooks* and you will be prompted to log in. Enter your password and the file open dialog will appear.
Choose the Roles tab. Navigate to * ompetence Centre Role* folder. Under the subfolder * W App Load Status*, select * W App Load Status - Table & Chart (Core Workbook)* and click * K*. In this workbook, there are 2 sheets, namely * able* and * hart*. If users wish to see a graphical representation of the table, select the * hart* sheet.
Take note that even though the workbook is created in BEx 3.x it should also be able to open in the newer BEx 7.x Both sheets have been protected to prevent users from making or saving changes to the original workbook. For administrators who need to edit the workbook eg. changing query, the password to unlock both sheets is bwappload
|