Showing posts with label Extraction. Show all posts
Showing posts with label Extraction. Show all posts
Saturday, August 25, 2012
Inventory Management
Inventory Management (0IC_C03) Part - 1
Inventory Management (0IC_C03) Part - 2
Inventory Management (0IC_C03) Part - 3
Friday, August 24, 2012
Setup Monitoring Job to control client opening (T000)
Setup Monitoring Job to control client opening (T000)
It is normally wise to keep the production clients closed. One way of monitoring this is the following. Prerequisite is that you have table logging enabled on table T000. This process will setup a background job that will send you an email every time the T000 table is changed. This would normally be because the client is opened. You can use your imagination and use this same method to setup many other nice security controls. if you can run it in background with a variant...you can do it like this. Below the steps:
Run Transaction : SE16
Select the following fields for output in the report from menu
Thursday, August 23, 2012
How to retain deltas when you change LO extractor in Production system
Requirement may come up to add new fields to LO cockpit extractor which is up & running in production environment. This means the extractor is delivering daily deltas from SAP R/3 to BW system .Since this change is to be done in R/3 Production system, there is always a risk that daily deltas of LO cockpit extractor would get disturbed. If the delta mechanism is disturbed (delta queue is broken) then there no another way than doing re-initialization for that extractor. However this re-init is not easy in terms of time & resource. Moreover no organization would be willing to provide that much downtime for live reporting based on that extractor.
How to... Reverse Transport(Production to Quality)
1.Create request in Source System (Eg: BWP) say A.
· Collect required objects into request A.
2.Goto TCode : SE09/SE10 --> create a transport of Copies request B
· Goto Tcode : SE09/SE10. You can see following screen.
· Collect required objects into request A.
2.Goto TCode : SE09/SE10 --> create a transport of Copies request B
· Goto Tcode : SE09/SE10. You can see following screen.
What are the Setup Tables?
What are the Setup Tables?
The Setup Tables are the objects from which the Business Warehouse system is going to extract data for Full loads and Initialization on LO Cockpit DataSources. Not just "LO DataSources" because there are some that don't use this feature.
When a Full extraction or a Delta Initialization is going to be performed, the Setup Tables need to be filled with all the historical data to be loaded to the Business Warehouse system.
Their content can be deleted any time, without affecting the R/3 transaction data. In fact, after the full/Init load has been performed, it is highly likely that the information contained in the Setup Tables is already not up-to-date anymore. Therefore, it would be no harm at all to delete their content. You may think of it as a "PSA" on the R/3 side.
If the load performed was an Initialization, the next records to be extracted will be sent to the Delta Queues.
The Setup Tables are the objects from which the Business Warehouse system is going to extract data for Full loads and Initialization on LO Cockpit DataSources. Not just "LO DataSources" because there are some that don't use this feature.
When a Full extraction or a Delta Initialization is going to be performed, the Setup Tables need to be filled with all the historical data to be loaded to the Business Warehouse system.
Their content can be deleted any time, without affecting the R/3 transaction data. In fact, after the full/Init load has been performed, it is highly likely that the information contained in the Setup Tables is already not up-to-date anymore. Therefore, it would be no harm at all to delete their content. You may think of it as a "PSA" on the R/3 side.
If the load performed was an Initialization, the next records to be extracted will be sent to the Delta Queues.
Subscribe to:
Posts (Atom)

