Escolar Documentos
Profissional Documentos
Cultura Documentos
Extraction and Data Transfer Data Load Monitoring, Reload and Repair ODS and Datamart Handling Process Chain Architecture & Functionality Process Chain Modelling Aspects Process Chain Monitoring & Error Handling Data Modelling from the technical point of view BW Transport Management System
Monitoring Changerun Load Balancing & Number Range Buffering BW Statistics and Query Tuning with Aggregates(RSRT) Usage of Basis Transactions (SM50, ) for applicational people
First steps & Basics Specific settings Background Processing & Load Distribution to different Servers Transporting Process Chains Tips & Tricks Implementing new Processes
Start
Drop Indices Roll up Aggregates
Build DB Statistics
Build Indices
Motivation
Automating the BW administration Graphical modelling and monitoring Central monitoring of all BW processes
Openness for all kinds of processes Moving responsibility into the individual processes
Different views to the the activities which are possible: Process chains Process types Data targets InfoSources Logs
working area
There are three main views in the icon bar with different views: Planning view (shows if the process chain is active) - Grey: unplanned processes (e.g. not activated process chain) - Green: planned processes (process chain is active and start process is released) - Yellow: planned but unknown processes - Red: multiple planned processes Checking view (consistency check like double used start variants, missing index deletion and recreation, wrong references in variants, ...) - Green: Error-free processes - Yellow: Process with warnings - Red: Process with errors Log view - Grey: Not yet run - Green: Finished without error - Yellow: running - Red: aborted or failed note that the log information is a usually mixture of - log information of maintenance activites (e.g. new process, change of design, activation) 5
can be displayed.
Display component
Process chain
Folders in the process chain are called display components. For mainentance of display components you have to use process chains display components. For reassignment of process chain to different display component For creation of new display component attributes
Application Processes
Application processes represent BW activities that are typically performed as part of BW operations. Examples include: Data load Attribute/Hierarchy Change run Aggregate rollup Reporting Agent Settings
Starter process that exists to initiate process chain execution ABAP program Another process chain Customer built process
Collector Processes
Collectors are used to manage multiple processes that feed into the same subsequent process. The collectors available for BW are:
AND: All of the processes that are direct predecessors must send an event in order for subsequent processes to be executed OR: A least one predecessor process must send an event The first predecessor process that sends an event triggers the subsequent process EXOR: Exclusive OR Similar to regular OR, but there is only ONE execution of the successor processes, even if several predecessor processes raise an event
Collector processes allow the designer of a process chain to trigger a subsequent process based on whether certain conditions are met by multiple predecessor processes. Application processes are the other type of processes these represent BW activities such as aggregate rollup, etc. Although the AND condition is implemented for process chains using the event chain functionality from 2.x, this event chain is internal and cannot be edited.
10
Start TR
Load Data
drop
TR Texts
3. Press Refresh
When you draw a line to connect processes, you are prompted to indicate whether the subsequent process should execute based on the success or the failure of the predecessor process. In other words, it is possible to schedule a process to run only if the predecessor process fails.
11
Start Process
Variant
Note: For each process chain the start process is mandatory. It is not possible to use the same variant more than once !!!
SAP AG 2005, BW System Administration / 12
The process variant could be used just by one process chain. Each process chain could be started manually or via RFC connection with the function module RSPC_API_CHAIN_START.
12
Variant Configuration
13
If standard process types can be changed depends on the changeability of name ranges (transaction SE03)
14
15
16
Maintain Message
Planning view context menu Write a message and fill in recipient and type. Info saved within process variant.
Bwadmin@sap.com BWADMIN@sap.com
Internet Mail Access has to be configured (with SAPCONNECT) for sending Emails from SAP-System to the Internet via SMTP.
17
First steps & Basics Specific settings Background Processing & Load Distribution to different Servers Transporting Process Chains Tips & Tricks Implementing new Processes
18
Example: Example You drag and drop a data load process to your process chain, the Index drop and the Index create process are automatically inserted. If you want no corresponding processes to be inserted automatically, flag the (user specific) setting in the menu under Settings Default Chains
19
Polling Flag
With setting the polling flag you can control the behavior of the main process when you have distributed processes (Process Chain Attributes Polling). The main job run all the time in parallel (flag is set) or is only triggered by a finished process of the process chain (flag is not set: default).
SAP AG 2005, BW System Administration / 20
With setting the polling flag you can control the behavior of the main process when you have distributed processes. Distributed processes, such as the loading process, are characterized as having different work processes involved in specific tasks. With the polling flag you determine whether the main process needs to be kept as long as the actual process has ended. Setting the indicator has the following advantages: A high level of process security is guaranteed External scheduling tools that react only to the SAP internal event 'Batch Process Complete', are also informed about the status of distributed processes. Setting the indicator also has the following disadvantages: Increased demand on resources. Although the CPU is not under pressure during the waiting time, it is during the status checks that run at two minute intervals. You require one more background process.
20
21
WAIT Process
Sometimes it is necessary to have some wait time before the subsequent process is started ...
22
Background Server
Note: This setting is just valid, if the process chain is not started directly, but as sub chain!
With this setting you can assign this process chain (especially the Process BI_PROCESS_TRIGGER to a specific background server. Due to the fact that the different processes of this chain are scheduled via event, they are usually started also on this server. Only if there are to less background processes they are distributed to other servers.
SAP AG 2005, BW System Administration / 23
For the case that you start the process chain with directly the the setting for background server is given as proposal, when you execute the process chain. But you can change the background server within this step. Please refer to notes: 604448 24092 519059 Collection note on job management Distribution of background jobs on application servers FAQ: Background processing system
23
First steps & Basics Specific settings Background Processing & Load Distribution to different Servers Transporting Process Chains Tips & Tricks Implementing new Processes
24
All processes except the BI_PROCESS_TRIGGER are event scheduled All other processes are event triggered
SAP AG 2005, BW System Administration / 25
Time scheduled
25
Result:
one instance is usually the favourite execution server
Recommendation:
Set rdisp/btctime on the different SAP Instances to different values, like 59, 60,61,.... With this setting there is no fixed relationship for the pickup times anymore
Recommendation is just useful for SAP Systems with more than one SAP Instance
26
Result:
If rdisp/btcname is the same on all Instances and there are sufficient BTC processes running on this Instance, this Instance will take almost all event triggered BTC Jobs (this means no load distribution for Process Chain Jobs!)
27
Disadvantage:
Delay times are occuring for event triggered jobs , but the more Instances the less delay times.
SAP AG 2005, BW System Administration / 28
28
Disadvantage:
Unflexible and getting optimal Job distribution on the different servers is more difficult.
29
RZ01:
30
Due to the fact that the other processes of the chain are
event triggered, they are usually running on the server which is determined with the SAP Parameter /rdisp/btc_name (instance specific!) (see note 24092)
SAP AG 2005, BW System Administration / 31
Collection note on job management Distribution of background jobs on application servers FAQ: Background processing system Load balancing of background jobs does not work Jobs remain in the 'Ready' status for a long time
31
If complex chains (also in parallel) are executed, you can improve the
overall runtime of the process chains, if there are sufficient BTC processes configured, in order to avoid unnecessary delay times. Sometimes it makes sense to configure more than 2 BTC processes per CPU.
rough calculation for the number of BTC processes in order to get best performance and avoid delay times in the batch queue: # BTC (optimal) = number of parallel processes at the widest part of the chain + number of parallel subchains at the widest part + 1
32
33
Note: BI_Process_Trigger for the second sub chain could not be started immediately, because there are just 5 BTC configured on the SAP Application Server
meaning of this slide there are 5 BTC work processes configured for the BW System (in this case just Central Instance exists) After execution of the process chain all BTC processes are allocated BI_Process_Trigger for the Process Chain itself. This process starts subsequent processes and finishes after the subsequent processes are sending status information back to BI_Process_Trigger PI_Process_Chain processes are starting subsequently the BI_Process_Trigger jobs of their assigned local process chains. Due to the fact that the there are just 5 BTC configured on the SAP Instance, there is one free BTC process missing for BI_Process_Trigger of the second subchain. This job is still waiting in the batch queue for free resources on this or further SAP Instances.
34
Subchains
If you have a complex structure of subchains which are running in parallel, you have to provide a minimum number of BTC processes: # BTC (minimum) = number of parallel subchains at the widest part of the chain + 1
35
36
I f subchains are used, a different background server can be assigned to the subchains with attribute background server in the maintenance view
Usually the processes within one process chain are running on the same server (because they are event-scheduled!)
rdisp/btctime: Start Interval for Background Scheduler Specifies the frequency in seconds with which the background processing job scheduler is to be started in a server which can run jobs in the background.
37
Result:
The jobs mostly run on the same server
Recommendation:
apply note 700479 in order to get a round robin procedure
38
First steps & Basics Specific settings Background Processing & Load Distribution to different Servers Transporting Process Chains Tips & Tricks Implementing new Processes
39
Process chains are transportable Button for writing to a change request when maintaining a process chain in RSPC Process chains available in the transport connection wizard (administrator workbench) Tlogo Object R3TR RSPC
40
41
Transport - Changeability
Note 337950 Queries (and other objects) cannot be edited
This option allows to deactivate the Change and Transport System for specific BW components
This setting is only intended for systems in production or test systems that are set to not changeable !
42
First steps & Basics Specific settings Background Processing & Load Distribution to different Servers Transporting Process Chains Tips & Tricks Implementing new Processes
43
The following loading process automatisms are ignored within process chains:
Flag for automatic ODS-activation in ODS-maintenance Flags for automatic deletion/creation of infocube indexes/statistics (Performance-Tabstrip in Infocube Manage) Flags for automatic Infocube Content Deletion or Deletion of overlapping requests in infopackage Flag in Infopackage: PSA + update subsequently in datatargets
There are differences between manual execution and execution in process chain For all these cases there are own process types to get the same functionality and to avoid interdependency / deadlock problems.
SAP AG 2005, BW System Administration / 44
44
Instead of this: Process Type Read PSA and Update Data Targets
Instead there is: Process Type Delete Overlapping Requests from InfoCube
Only the BW Quality flag is processed, but it is a prerequisite for Process Chains that this flag is set, otherwise unknown kinds of error messages can be displayed
45
Start Process
Direct scheduling:
Job BI_PROCESS_TRIGGER will be scheduled when the process chain is executed.
46
Sometimes you want to start a process chain immediately. You dont want to change the variant of the start process.
Each process chain could be started always manually or via RFC connection with the function module RSPC_API_CHAIN_START.
47
Display Component
Typical situation: Folder structure missing! Proposal: Apply your own display components
48
49
50
51
When collector processes are built into a process chain, there are actually several background jobs scheduled with events in order to construct the conditional nature of collector processes. The simple view displays the processing chain as it exists logically. The detail view displays the processing chain with the extra collector processes.
52
Often required in HR
53
01/2001
11/2001
2 records
1 record
54
blue green
1st upload
blue blue
Reorganization
blue blue
time
55
First steps & Basics Specific settings Background Processing & Load Distribution to different Servers Transporting Process Chains Tips & Tricks Implementing new Processes
56
...then you can use the process type ABAP to run your program in a chain. However if you...
...Want to ask predecessor processes of your program ...Write a log , which should be displayed in the process monitor ...Have implemented an own monitor ...Have a customizing screen, which is more difficult than the parameters of a program
57
58
Interfaces:
EXECUTE GET_INFO GET_LOG MAINTAIN GET_VARIANT
GET_DEFAULT_CHAIN
Maintainance
Runtime
Log View
X X X X X X X X X X X X X X
X X X X X X X X X X X
means: e.g.: Interface: IF_RSPC_EXECUTE is executed at runtime of the Process Chain. Usage of this Interface within your self defined process type is mandatory Process Type ABAP just uses IF_RSPC_EXECUTE and IF_RSPC_GET_Variant. No status is given back. e.g.: Interface: IF_RSPC_Get_Status is executed at runtime and when startig log view. It is not mandatory to use this interface within your own process type.
59
60