Delta ALE: Problem TCDOB

Hi Gurus,
I want to extract data from 0FUNCT_LOC_ATTR in delta ALE mode. But the object that I need (TPLNR) is not in table TCDOB (which I can't enter data) so i can't select this object when i'm trying to configure the ALE Delta for this DataSource.
Can anybody help me?
Thanks in advance!
Regards!
Edited by: Guillermo Melero on Jun 20, 2008 12:34 PM

Hello Lida,
Try to be assisted via this link :
[Re: How to Retrive data from IDOC]
Good Luck,
Boaz

Similar Messages

MOVED: MSI KT880 Delta-FSR - problem with multiplier

This topic has been moved to Overclockers & Modding Corner.
MSI KT880 Delta-FSR - problem with multiplier

http://www.rme-audio.com/english/techinfo/nforce2_tweaks_02.htm
wiretrick it so multipliers under 12.5 will work
assuming the cpu is an old unlocked one

Msi k7n2 delta ilsr problem

hi i have this configuration on my pc:
antec true control 550 watts
msi k7n2 delta ilsr
kingston hyper x pc3700 2x512 mb
athlon xp 3200+
seagate 120 gb sata 7200.7 hd
ati radeon 9800 pro excalibur ice q
i have 2 problems : the first one is that sometimes windows display me a blue screen with certain problem related to ati2dg.dll i think that problem is beacause the video card so i decided to update the bios , in the live update page from msi says that the bios 7.6 fix a bug with ati vga cards but after flashing and updating to bios v7.6 that blue screen with the same error still appearing so i dont know what else to do to solve the problem and the second one is that when i start any game or make the processor to work a little mostly related with video stuff the case speaker start to beep and the pc lags until he restarts with no reason i really dont know why if u can help me thank you

Foxtrotccs,
In the BIOS try setting the AGP to 4X and disable Sidebanding. Then set the AGP Apeture to 256. See if that helps.
Make sure you are running the lastest nVidia nForce Drivers and the latest ATI Catalyst Drivers
Take Care,
Richard
P.S. There is still a possibility that the Kingston RAM is the problem.

Scenarion of Delta Load problem in COPA Extraction

Please get me the solution for this particular scenario.
Let us suppose that i created the datasource some 1 year back and running the deltas successfully since then.
Let us number the requests from 1,2,3... and so on since 1st jan 2009. And let us suppose each request loads
some 1000 records everyday from ECC to BI.
Now on 10th august some change was made to ECC( such as change in the User Exit ) that caused the mismatch in number of data records ( loading only 950 records ) since the change was made on 10th August. But I identified the problem on 17th august with request number 160. Let us say those request numbers are 153(10th),154(11th),155(12th),156(13th),157(14th),158(15th),159(16th),160(17th). I fixed the program in ECC on 17th and further the requests from request number 160(17th) are fetching the correct number of data records. Now I need to delete the data in BI for request numbers 153 till 159 since they are not reconciling the data of ECC with BI. Now we reload the deltas for such requests from ECC to BI. So how do I reload the deltas now in this scenario since ECC system keeps track of the last delta ie.. on 17th august(Req no 160). But how do I Load the deltas from req number 153 to 159 from ECC to BI.
One proposed solution to this problem was setting the timestamp of COPA to 10th august. But it is not advised to set the timestamp for COPA datasources using the KEB5 transaction in a production system.
Now in this scenario how do I load the request numbers 153 to 159 from ECC to Bi to fetch the correct data records for that period. Please propose a solution for this problem ASAP. U can also call me back whenever u need.
Thanks in advance

As stated in a previous post...
How you choose to do this can be summed up by the question: Does the target for this data have cumulative or non-cumulative Key Figures?
If you are doing an overwrite to the Key Figures, you could just execute a Full Repair InfoPackage that extracts the data for the days that you found inconsistencies instead of attempting to change the timestamp in KEB5 on the source ECC environment.
However, if you're target has cumulative Key Figures you're left with very few options (a couple of them are time-consuming):
1) Changing the timestamp in KEB5, if your plug-in is PI 2003.1 or older. Newer versions of the plug-in do not allow the changing of the timestamp as was pointed out by Ferruccio earlier.
2) Deleting the keys in the target InfoProvider for those records that you extract in a Full Repair extract.
3) Delete all data in BW for COPA and start from the beginning. This may be your best bet for cleaning up the issues in this scenario.

ALE Problem inter SAP system

Dear Expert,
I am a fresher in ALE. I have configure ALE in my Development and Q/A system. Dev system as sender and Q/A as receiver.
When I try to send GL account master data from Dev to Q/A, I have problem. I cannot see my GL Account in Q/A system. In sender, I see the log and found that IDoc status is ok.
Regards,
MAL

Hello MAL,
Please ensure that the user id in TRFC LUW has proper authorizations.Additonally also ensure the user in target group has proper authorizations Please give them autorizations not only to create and process idocs (S_IDOC* authorization objects) Also authorizations to create and change GL accounts (F_SKA1_BUK,F_SKA1_KTP etc. authorization objects) should be given to the user involved in QA system (this user is same as in the RFC destination for QA) If this is a system or communication user then SAP_ALL can be given. Do that and then process the TRFC queue.
Regards.
Ruchit.

Generic delta has problem with delts pointer time stamp

Hi All,
We have generic delta data source with Delte pointer as Time stamp. We have not used any safety limits. We are loading the data to DSO and using Additive delta. But the problem is when delta flag is set, there might be a case where some records still being inserted to table with lower time stamp. These records are not being fetched in next delta.
We are planning to keep a safety upper limit of 5 min so that those records can not be missed. But we have a doubt as it is a Additive delta duplicate records will be loaded. If we make the delta to 'new status to changed records', it is going to work?? Any other things we have to check when we make this changes??
Thanks
Haaris

Hi
If you had selected additive delta then you can load data to DSo with addition mode only. No overwrite possible.
If you want to select new or changed status then you can load to DSO with overwrite mode only.
Additive or changed delta depends on your requirement because if you want to add data to the DSO then you can go ahead with additive otherwise you have to use DSO with overwrite mode only.
You can either give safety upper limit or lower limit but if you give safety lower limit then you can only load data to DSO with overwrite mode because there could be some duplicate records.
Hope it clarifies.
Regards
Sadeesh

Delta INIT problems in production system

hi!
How do you do, I hope all fine, well, I have a problem in production system, I execute the delta init and the data is in BW the problem is when I want to activate the data, the system give me a processing error, somebody can helpme please?
BR

Hi
Please check with your Basis team to confirm there are enough resources.
Also Check what is max work process time . Tcode RZ11 parameter rdisp/max_wprun_time
Check this thread which mentions a lot of related notes.
Link: [Re: DSO-data activation issue;
Regards
Sanjyot

Inventory delta load problem

Hi,
We are facing inventory data load getting below error, Main problem is they got below error in PSA level from 16th june still they changed red icon into green and loaded to incube and compressed. when running process chain they getting same error daily.
Error:
Caller 09 contain an error message
Problem:
-> Data flow PSA->IC, 20th request (it look like have 16th to 20th data) they have changed PSA red request into green and loaded to cube and compressed.
21th request (it look like have 16th to 21th data) they have changed PSA red request into green and loaded to cube and compressed.
Kindly guide me what solution we can give.
thanks

I suggest that you handle this with utmost care. Since it does not look like you have the DSO in the dataflow, recovering the data would be impossible if the cube data is corrupted.
Need to understand the details to be able to give a proper solution.
You can consider request reverse posting option which will post reverse images of the PSA requests under the scope and nullify the value from the cube. Please try this in Dev and quality system, before trying this in Production.
Else, you can create a custom datasource based on this PSA table and reverse the values in the transformation.
If you could identify the documents, created after this delta corruption, you could set them up in source and do a repair full upload.
Please let me know whether it helps.

Master Data Delta Extraction Problem

Hi,
I have this problem. When loading delta data from 0BPARTNER_ATTR infosource, BW informs me "Short dump in the Warehouse". When I go looking for it, there is none. Once I got to the infopackage->scheduler, the system reports "Request the repeat?", and I go "Continue", but the data load never begins. Does anybody knows what it's wrong?.
I'v been doing some work-arround: start a new init load, but this is good for two or thre days (delta loads), and then the delta stops working.
any ideas where to look for the problem?
thanks for the help.
Mauiricio

Hi Mauricio,
maybe it depends by the number of records in delta quque. If you have a daily lot of changes in a Master Data the system is no more able to extract the data in tables for change pointers. Also maybe that you have to cancel entries on the tables of changed data.
Check the quantity of delta records for every day, and then check also if it is possible to update this master data frequently.
Ciao.
Riccardo.

Zpca_c03, delta reset problem

Hi All,
I have a problem with the delta loads to ZPCA_C03.
We have done full loads till March, monthly wise and set the delta init flag during a system down time.
Again we happened to do December data re-load to the cube. As the cube is duplicated with the december data, in ambiguity we have done selective deletion to remove the double december data, which is wrong. Now the delta is not working.
How to resolve this issue, possibly without a down time!!!
We need to have december data again and on going delta to be reset.
Regards
Raveena

Hi,
I need a clarification on this.
Is that the uploaded data successfullly loaded to the external system or not?
Are you uploading data to the cube or some thing else?
Regards,
Srini

HRMD_A ALE Problems

A while back I set up HR Master Data distribution. Initially, the client was running HR on the same server as FI, MM, SD etc. They wanted to move to a new HR server for security reasons.
I set up the ALE in order to connect the HR system to the R/3 system. Among others, i used message type HRMD_A. A problem I have come across is that sometimes the ALE tries to send objects across in the incorrect order, and the IDocs fail.
For example, if I create a new position, and then make some changes to that position, or assign relationships etc - The ALE sometimes tries to send the changes or relationships before it sends the actual position - This of course causes an error on the receiving system because the object does not exist when the changes are being attempted...
What are the steps that I should make sure have been taken to ensure no errors in the ALE?
What are the background jobs that I should have scheduled etc?

Dear David/Manas,
Manas : Please refer to note 752194 and also the documentation in SE38 of report RHALEINI. Serialization can assure that IDOCs are processed with the correct order even if customer only use message type HRMD_A.
David :
2.1 Re-distribute all the data just to make sure that all is in sync. Is that correct?
- Yes you need to make sure your initial distribution has been done correctly.
2.2 Before I run transaction PFAL, I assume that I need to de-activate change pointers u2013 or not?
- No you do not need to deactivate the change pointers.
2.3 I then follow your steps 1-4
3.1 After that, I should set up the serialization for sending and receiving on the box:
3.2 Which system must I do this on u2013 R/3 or HR?
- You need to install the serialization in your source system (where PFAL will be running). please refer to the documentation of report RHALEINI for further info.
3.3 I assume that I will need to "Define New Serialization Groups" for HRMD_A?
- Refer to note 752194 and the documentation of report RHALEINI. It will guide you in this process.
3.4 The distribution model has already been maintained as mentioned in point 1.1. Do I need to add info-type 1028 to the filter?
- Unless you need this infotype
3.5 I will then need to u201CDefine Inbound Processingu201D.
For inbound:
-> go to transaction WE20 -> Select Partner
Select Inbound Message Type and change the processing method from
"Trigger Immediately" to "Trigger by background program".
3.6 Lastly I will need to create a variant for program RBDSER01 and schedule a background job u2013 How often should this job run? Which server should this job be run on? R/3 or HR?
This report is used when you are using different application servers and different message types. So in your scenario, you can use report RBDMIDOC to create your idoc from change pointers and then run report RSEOUT00 to send these idocs to the target system.
Hopefully I clarify your request,
Best Regards
Christine

K7 delta ISLR problems with visioneer 7700 scanner and startup

I am a computer tech at our store i ran into a problem with k7 delta board with a visioneer photoport 7700 usb scanner plugged in at bootup it sit there at bios init for 1 min before the machine boots.
The scanner works fine but i have never seen a machine that took so long to boot with scanner pluuged into the usb.
If i unplug the usb scanner it boot at its fast normal speed could it be because its also a card reader that part of it is slowing down the bootup process?.

Hi,
Wait for machine to boot, then switch on scanner - problem solved!!!
Axel

Delta Upload Problem For 0PM_CO1 Cube

Hi Friends,
I got a problem for Delta Upload.In RSA3 data is O.K and In RSA7 also data is O.k.but the problem is with Delta Upload new records are not comming,i did First initialization,thst is o.k,but why Delta Upload is not comming.
please give me help about this .
Thanks in Advance.

Hi Praksh,
this is chava,can you send your mobile no. to my mail id.
Mail:[email protected]
Message was edited by: CHAVA CHAVA

Delta load problem from ODS

Hello everyone here.........,
I have a problem loading frm ODS to another target with delta.
Actually to ODS i am loading from two datasources. Both are full loads. Full1 and Full2. When i am trying to load from ODS to another target with delta..., it takes only Full1 data not Full2. So for loading Full2 now i am loading manually.
so why this happend here. Please let me know how to do
for making full2 also automatically........,
swetha

yes u r correct. after full1 loaded into ODS, its activating the ODS. these two can done through process chain. For full2 load we are loading manually. and doing manual activation.
lets take small example here that for yesterdays full1 & activation has done successfully. and after that i am loading
full2 manually & activated. and again today process chain ran, it loads full1 & activated ODS. Now what i am thinking is does this further datamart load which is run in process chain picks only full1 load and it doesn't pick full2 load which is already loaded & activated successfully.
I think u will get what i suppose to ask you now...,
clear my confusion here please......
swetha

Delta Update Problem when loading to Cube

Dear all.
Scenario:
DataSources 2LIS_18_NOTIF and 2LIS_18_I0TASK are extracted to ODS Daily which is a Delta Update.Weekly once they are updated to cube which is also Delta Update.This is automated by a process chain.
DataSource 2LIS_18_NOTIF failed on 27.07.2005 which we did not notice.Datasource 2LIS_18_IOTASK is fine.I did a repeat delta for 2LIS_18_NOTIF which is successful.Data upto ODS is fine.
Now the problem is loading data from ODS to cube which is Delta Update to be loaded every week.There are some Update rules written in which <b>sy-datum</b> is used.
Proposed Solution:
Change sy-datum for every monday date and do the delta update for 7 2LIS_18_I0TASK requests and 1 2LIS_18_NOTIF request.Delete the request from Cube,to remove delta management for 2LIS_18_NOTIF request.Now load for second week with 7 2LIS_18_I0TASK requests and the same 2LIS_18_NOTIF.Do this for all weeks and finally reconstruct all the requests which are deleted from cube.
if i follow the above approach can there be any Data inconsistency?
please help me to resolve this issue.
Regards
Ravi.

Hi Ravi,
If you are going to make a code change, which it looks like you are going to do, then I would suggest the following:
- Create an InfoObject called ZMondayd. Define is a type date, and allow master data.
- Input in the date you want your update rules to use
- In the update rule, change the code to read the value from the InfoObject, not sy-datum.
- Load your data.
I would also set up a process to update the InfoObject on a weekly basis to hold the date that you want. By using this method, if for some reason or another this process fails, you do not have to make any code changes, just maintain the InfoObject with the correct date, and reload the data.
Cheers! Bill

Delta ALE: Problem TCDOB

Similar Messages

Maybe you are looking for