Errors in BW

Deltas Not Working for Installation Master Data I am having trouble with the deltas for master data object "installation". The changes are clearly recorded in the time dependent and time independent tables, EANL/EANLH. The delta update mode is using ALE pointers, does anyone know of a table where I can go check where these deltas/changes are temporarily stored, or what's the process behind this type of delta?

The following steps must be executed: 1. Check, whether the ALE changepointer are active in your source system (Transaction BD61) and whether the number range is maintained (Transaction BDCP). 2. In addition, check in the ALE Customizing, whether all message types you need are active (Transaction SALE -> Model and implement business processes -> Configure the distribution of master data -> Set the replication of ch anged data -> Activate the change pointer for each message type ). 3. Check, whether the number range for the message type BI_MSTYPE is maintained (Transaction SNUM -> Entry 'BI_MSTYPE' -> Number range -> Intervals). The entry for 'No.' must be exactly '01'. In addition, the interval must start with 0000000001, and the upper limit must be set to 0000009999. 4. Go to your BW system and restart the Admin. workbench. All of the following activities occur in the InfoSource tree of the Admin. Workbench. Workbench. 5. Carry out the function "Replicate DataSource" on the affected attached source system for the InfoObject carrying the master data and texts. 4. Activate the X'fer structure All changes, all initial data creations and deletions of records from now on are recorded in the source system. 5. Create an InfoPackage for the source system. In the tabstrip 'update parameter', there are three alternative extraction modes: Full update Delta update Initialization of delta procedure First, initialize the delta procedure and then carry out the delta update. An update on this issue: In the EMIGALL process, SAP decided to bypass all the standard proces to upd ate the delta queues on IS-U, because it would cause too much overhead during the migration. It is still possible to modify the standard programs, but it is not recommended, except if you want to crash you system. The other options are as follows : - Extract MD with full extractions using intervalls.. - modify the standard to put data in a custom table on which you are going to create a generic delta; - modify the standard to put the ALE pointers in a custom table and then use a copy co py of the

Trusted by over 1 million members

Try Scribd FREE for 30 days to access over 125 million titles without ads or interruptions! Start Free Trial Cancel Anytime.



standard functions to extract these data.... - Extract the data you want in a flat file and load it in BW... BW... By the way, if you want to extract the data from IS-U, forget to do it during migration, find another solution to extract after. PS: Well if you have generic extractor and huge volume data then you can do it with multiple INITS with RANGES as selection criteria and then a single DELTA(which DELTA(which is summation of all INITS) in order to improve performance with GENERIC DELTA. DELTA.

Error in transport After creating a query in BEX, you try and save the query, it gives you the following popup message: "The query could not be saved due to a problem in transport". Steps to correct the problem: 1. Within Within Adminstrator Workbench click on the Transport Connection tab in the Navigation Window on the left hand side. 2. Select the Request BEx button on the toolbar. toolbar. 3. Create a transport. 4. Try to change the query again.

SAP BW ERROR : replicate data from f rom source system BW 2.1C OS WINT4 The RFC is working fine and you are trying to replicate data from source system (4.0B), while doing this you got an error an ABAP dump, in this dump the Exception Condition are "CNTL_ERROR" raised Take a look at OSS notes 158985 and 316243.



Transport Process Chains to Test System What is the best way to transport process chains to test system? I got many other additional and unwanted objects got collected when I tried for collection of process chains from transport connection.

To transport a process chain the best is to transport only objects created for the process chain. On my system I created specific obejcts for PC : Infopackages, jobs, variant. those objects are only use for PC. By B y this way I avoid errors when users restart load or job manually. So when I want to transport a process chain I go in the monitor and select the PC make a grouping on only necessary objects, and I go through the tree generated to select only what I need. Then I go in SE10 to check if the transport contains not other objects which can impact my target system. You can avoid some uncessary un cessary objects by clicking in Grouping > Data flow before & Data Flow After . For example you already have infopackages infopackage s in your target system but not process chains & you only onl y want to transport only process chain without any other objects like transfer structure or infopackages . You can choose before or after option .

You can also choose hierachries or display option from the Display tab too if you have objects in bulk but make sure all object are selected ( in case when different-2 process chain having different kind of object then better use Hierarchy, Hierarchy, not list ) While Creating these TR some objects may be in use or locked in other TR so first release them by b y Tcode Tcode Se03 ,using unclock object ( Expert Tool ). These options can reduce your effort while collecting your objects , even after so much effort you get some warning or Error like :- objects are already a lready in system then ask basis to use overwrite mode.

Transport a specific infoobject How to transport a specific info object? I tried to change it and then save but the transport request won't appear. How to manually transport that object?

1. Administrator Workbench Workbench (RSA1), then Transport Connection 2. Object Types, Types, then from the list of objects put the requested one on the right side of the screen (drag & drop)



5. Move the transport up to the another system.

If you change and reactivate the infoobject, but get no transport request, this means that your infoobject is still in $tmp class. go in to the maintenance of the infoobject, menu extras, object directory entry and change the development class. at this point you should have a pop-up requesting a transport request

If you're not getting a transport request when you change and activate, it could also be that the InfoObject is already on an open transport. When you collect the object in the transport connection as described above, you will see in the right hand pane an entry called Transport Request. If there is an entry here, the object is already on a transport and this gives you the transport number. You can then use SE01 S E01 or SE10 to delete the object from the existing transport if that is what you want to do then, when you change and activate the object again, you should be prompted for a transport request. Alternatively, Alternatively, you can use the existing transport depending on what else is on it.

How To Do Transports in BW? Step by step procedure for transporting in BW: 1. In RSA1 go to Transport Connection 2. Select Object Types Your Your Object that you want to transfer. transfer. 3. Choose grouping method (in data flow before and after) 4. Drag and drop your object. 5. Click the Truck button to transfer 6. In Source System (e.g Dev SE09). a. Expand to choose your child request b. Click on the release button (truck) c. Choose the parent request and click the Truck button release. 7. In Target System (e.g QA) go to STMS a. Click on Truck button (Import Overview) b. Dbl click on your QA system queue c. Clck on Refresh d. Clk on adjust import queue e. Select ur request and click on F11. *-- David Kazi



In RSPC, double click the process chain so that you can see it in the left hand pane. In the box where you type in the transaction code, type COPY and hit Enter.

Errors in BW

Recommend Documents