There are sometimes doubts regarding how to set up processes within the process

chains. Process chain is structural and logical grouping of processes , jobs or

steps involved within loading of data into BW. Proper design of chain has effect
s on its performance and consequently on performance of whole BW system. Therefo
re kind of best practice I can recommend following sequence for designing proces
s chains:
a. Delete Index
b. Data Transfer Process / Execute InfoPackage optimally in parallel
c. Generate Index
d. Construct Database Statistics
e. Compress cube
f. Delete PSA (aged data requests)
g. Delete Change Log (aged data requests)
DataFlow of Process Chains in different SAP BW-BI
Steps for Process Chains in BI 7.0 for a Cube.
1. Start
2. Execute Infopackage
3. Delete Indexes for Cube
4.Execute DTP
5. Create Indexes for Cube
For DSO
1. Start
2. Execute Infopackage
3. Execute DTP
5. Activate DSO
For an IO
1. Start
2.Execute infopackage
3.Execute DTP
4.Attribute Change Run
Data to Cube thru a DSO
1. Start
2. Execute Infopackage ( loads till psa )
3.Execute DTP ( to load DSO from PSA )
4.Activate DSO
5.Further Processing
6.Delete Indexes for Cube
7.Execute DTP ( to load Cube from DSO )
8.Create Indexes for Cube
SAP BW 3.X
Question 1
Update records are written to the SM13, although you do not use the extractors f
rom the logistics cockpit (LBWE) at all.
Active datasources have been accidentally delivered in a PI patch.For that reaso
n, extract structures are set to active in the logistics cockpit. Select transac
tion LBWE and deactivate the active structures. From now on, no additional recor
ds are written into SM13.
If the system displays update records for application 05 (QM) in transaction SM1
3, even though the structure is not active, see note 393306 for a solution.
Question 2
How can I selectively delete update records from SM13?
Start the report RSM13005 for the respective module (z.B. MCEX_UPDATE_03).
Status COL_RUN INIT: without Delete_Flag but with VB_Flag (records are updated).
Status COL_RUN OK: with Delete_Flag (the records are deleted for all modules wit
h COL_RUN -- OK)
With the IN_VB flag, data are only deleted, if there is no delta initialization.
Otherwise, the records are updated. MAXFBS : The number of processed records wi
thout Commit.
ATTENTION: The delta records are deleted irrevocably after executing report RSM1
3005 (without flag IN_VB). You can reload the data into BW only with a new delta
-initialization!
Question 3
What can I do when the V3 update loops?
Refer to Note 0352389. If you need a fast solution, simply delete all entries fr
om SM13 (executed for V2), however, this does not solve the actual problem.
ATTENTION: THIS CAUSES DATA LOSS. See question 2 !
Question 4
Why has SM13 not been emptied even though I have started the V3 update?
The update record in SM13 contains several modules (for example, MCEX_UPDATE_11
and MCEX_UPDATE_12). If you start the V3 update only for one module, then the ot
her module still has INIT status in SM13 and is waiting for the corresponding co
llective run. In some cases, the entry might also not be deleted if the V3 updat
e has been started for the second module.In this case, schedule the request RSM1
3005 with the DELETE_FLAG (see question 2).
V3 updating no longer functions after the PI upgrade because you did not load al
l the delta records into the BW system prior to the upgrade.Proceed as described
in note 328181.
Question 5
The entries from SM13 have not been retrieved even though I followed note 032818
1!
Check whether all entries were actually deleted from SM13 for all clients. Look
for records within the last 25 years with user * .
Question 6
Can I schedule V3 update in parallel?
The V3 update already uses collective processing.You cannot do this in parallel.
Question 7
The Logistics Cockpit extractors deliver incorrect numbers. The update contains
errors !
Have you installed the most up-to-date PI in your OLTP system?
You should have at least PI 2000.1 patch 6 or PI 2000.2 patch 2.
Question 8
Why has no data been written into the delta queue even though the V3 update was
executed successfully?
You have probably not started a delta initialization. You have to start a delta
initialization for each DataSource from the BW system before you can load the de
lta.Check in RSA7 for an entry with a green status for the required DataSource.
Refer also to Note 0380078.
Question 9
Why does the system write data into the delta queue, even though the V3 update h
as not been started?
You are using the automatic goods receipt posting (transaction MRRS) and start t
his in the background.In this case the system writes the records for DataSources
of application 02 directly into the delta queue (RSA7).This does not cause doub
le data records.This does not result in any inconsistencies.
Question 10
Why am I not able to carry out a structural change in the Logistics Cockpit alth
ough SM13 is blank?
Inconsistencies occurred in your system. There are records in update table VBMOD
for which there are no entries in table VBHDR. Due to those missing records, th
ere are no entries in SM13. To remove the inconsistencies, follow the instructio
ns in the solution part of Note 67014. Please note that no postings must be made
in the system during reorganization in any case!
Question 11
Why is it impossible to plan a V3 job from the Logistics Cockpit?
The job always abends immediately. Due to missing authorizations, the update job
cannot be planned. For further information see Note 445620.
Master loading ( Attr, Text, Hierarchies )
Steps :
1.Start
2. Execute Infopackage (say if you are loading 2 IO's just have them all paralle
l )
3.You might want to load in seq - Attributes - Texts - Hierarchies
4.And ( Connecting all Infopackages )
5.Attribute Change Run ( add all relevant IO's ).
Start
\/
Infopackge1A(Attr)Infopackge2A(Attr)
\/
Infopackge1B(Txts)Infopackge2B(Txts)
/_____________________
Infopackge1C(Txts)______
\_____________________
_\____________________
__\___________________
___\__________________
_____\________________/
______ _And Processor__ ( Connect Infopackge1C & Infopackge2B )
____________________
Attribute Change Run ( Add InfoObject 1 & InfoObject 2 to this variant )
1. Start
2. Delete Indexes for Cube
3. Execute Infopackage
4.Create Indexes for Cube
For DSO
1. Start
2. Execute Infopackage
3. Activate DSO
For an IO
1.Start
2.Execute infopackage
3.Attribute Change Run
Data to Cube thru a DSO
1. Start
2. Execute Infopackage (Loads till PSA)
3.Activate DSO
5.Further Processing
6.Delete Indexes for Cube
7.Execute Infopackage
8.Create Indexes for Cube