Data Flow Control
Data Flow Control
Data Flow Control
SAP NW 2004s
Topics
Data
Transfer Process and Error Handling Process Chains Direct Access Real Time Data Acquisition
Data Transfer Process (DTP) is responsible for loading data within BI from one persistent layer to the other eg from Staging (PSA) layer to EDW Layer, or from EDW Layer to other Architected Data Marts layer.
TRANSFORMATION
DataSource (PSA)
InfoPackage
We can also define Transformation to other InfoProviders, loading data Via DTP from one InfoProvider To other InfoProvider. You Can also define an Open Hub destination, and Define Transformation Between the PSA and an Open Hub destination also scheduled Via DTP.
Source System 1
DTP
Once the transformation is defined, it is possible to create the DTP. Extraction tab
Mode Delta or Full Filter With filter it is possible to load a set of data to data target instead of complete volume.
Extraction
DTP
Update tab
Error handling Invalid records can be corrected in a error stack and updated into the data target. Semantic Grouping
Defines which data should be detained from the update after the erroneous data records. Semantic groups bundle records with the same semantic group key into the same request. Subset of the key of the target object Max 16 fields Example selecting company code as error stack key -> if one record of a particular company code is wrong, all records belonging to this company code will be written to the error stack.
DTP
Execute tab
Program Flow - In case the error handling is switched on and there are InfoObjects which have update mode overwrite in transformation, new records with the same key will be filtered out during the data loading. Setting of Temporary Data Storage traces the erroneous records, transformation by package/record. Deletion of temporary storage with request status green, if request is deleted, After X days. To display error stack click on PSA like Icon.
DTP.
Execute tab
Processing
Copying of process chain design Client dependency Flexible execution paths Parsing Output of System Commands Usability Repairing and repeating instances Synchronous execution Handling processes with errors Background user Display mode Check on batch process consumption Alerting with process chains
Business Scenario A new, season dependent product is sold in two different test markets. Depending on the system date, a decision must be made which source must be loaded into the InfoCube. New Process type Decision between multiple alternatives
Supports IF [condition1] THEN [event1] ELSEIF.. decision Up to 99 resulting events (plus an error event) can be defined Available in the General Services menu.
Event Logic: Formula Builder supports set-up of process type Decision between multiple alternatives. Event Logic: Formula Builder Special Functions
Allow decision based on current state of the runtime process chain. Process chain runtime parameters of the direct predecessor. Process chain runtime parameters of a process for the current chain Process of the chain has parameter value
Input help available for necessary parameters Tip: Use the Continue button for value help on the particular fields.
customizing the process type with its different conditions, the succeeding process types can be inserted. Each successor must be assigned as a resulting path to a possible condition. for custom-developed process types in table RSPROCESSTYPES.
System Command
Check for existence of a file before uploading it If file not available (result: , not found), try to upload it again every hour
Action can be defined by analyzing the result string with given search. Can be defined in transaction SM69.
Assignment of process chain to a particular client (path menu (Process Chain -> Attributes -> Editing Client). Scenario: Client-dependent applications that incorporate SAP NW BI (e.g. SAP SCM) -> process chain can only be seen in the specified client. Assignment of process chain to a particular client.
After the assignment, the process chain can only be monitored in this client. After the assignment, the process chain will be scheduled automatically. In transaction RSTPRFC a destination must be maintained in the client.
Note: Process Variants, which are used in a client-dependent process chain cannot be used in a process chain running in another client since the variant would be invisible.
Usability
Tree view
Navigation by cursor keys is possible In addition to network view (as available
prior to SAP
NW 2004s)
Context Menu
No drag & drop necessary Context menu displays the
variants grouped by type to which a process could be connected. It performs checks on the possible links that could be drawn from process one to another, so no superfluous target are offered.
Background User
Runs a process chain Scenarios 1. Special user for load balancing, 2. be able to see which user has scheduled a certain process chain and is in charge of it. Three option BWREMOTE User, User actually schedule the process, Manually specified user.
SAP BW 3x only repeat of single process type within (failed) process chain possible. Repeat = starting of a job with a new instance -> new request no. Former restart function Repairing resume the process within the same instance Some processes like the new data transfer process use this and offer features to repair broken instances.