Dispute Case Delta load

Hi
I am working on Dispute Management area. My requirement is to get all Dispute case attributes from SCMG_T_CASE_ATTR and UDMCASEATTR00 tables in ECC. I found two BI content extractors 0CSM_CASE_ATTR and 0DPM_DCAS_ATTR. These are delta enabled.
Issue: If Dispute case is modified multiple times in a day I am getting single record in the delta i.e. last change during the day. But I want to capture all the deltas into BI i.e. time to time changes during that day.
Is there any way to get all the changes to BI?
Thanks for your help
Sree

hi,
is that your require ment that you would need all the changes that had happened for a particular dispute.
if yes then you need create a generic data source based on the tables involved.
normally if a dispute has been raised by a customer and we would only be intrested in the final closing of the sttaus at the end of the day whether its closed open etc...
sap has delivered the extractor based on this and you will standard busssiness contenet avialble under 0dpm in BI and standard queries.
Thanks
krishna.y

Similar Messages

About delta loading for master data attribute

Hi all,
We have a master data attribute loading failed which is a delta loading. I have to fix this problem but I have two questions:
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
2. Could you please let me know the detailed procedures to perform this delta loading again ?
Thanks a lot

Hi...
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
Look.....for master data.....no need to delete request from the target..........just make the status red.......and repeat the load.....But problem is that master data sometimes does'nt support Repeat delta..........if u repeat......then load will again fail with Update mode R.........in that case u hav to do re-init.......
1) delete the init flag.......(In the IP scheduler >> in the top Scheduler tab >> Initialization option for source system)
2) Init with data transfer(if failed load picks some records)..........otherwise .....init without data transfer.....if the last delta failed picking 0 records.......
3) then Delta.......
2. Could you please let me know the detailed procedures to perform this delta loading again ?
1) Make the QM status red.........to set back the init pointer.......
2) Repeat the load.....
After that.........if again load failed with Update mode R.....
1) delete the init flag.......
2) Init with data transfer(if failed load picks some records)..........otherwise init without data transfer.....
3) then Delta.......
Regards,
Debjani.....

How to set-up a Timestamp for BI Delta Load in 0CLM_INVOICE datasrc at R/3?

Hi Experts,
Kindly let me know How to set-up a Timestamp for BI delta load at R/3 for the Data source 0CLM_INVOICE ?
Since the Timestamp for Upload of BI Delta is " . . : : ", we are not getting any delta value to BW.
I would like to know in where we need to maintain the DATE & TIME to fix the above problem.
Thanks.
Regards,
Jayaprakash J

Dear Jayprakash,
Chech the below links, it may help you in your case :
Re: 0FI_AA_11 Delta load failure
http://wiki.sdn.sap.com/wiki/display/BI/GeneralErrorIn+BI
Actaully you need not have to maintain the timestamp. Just try to replicate your datasource and the try to load the delta again.
Hopefully it will work.
Regards,
Rahul
Edited by: Rahul on Dec 10, 2010 10:23 AM

Issue in the Delta load using RDA

Hi All,
I am facing an issue while trying to load delta using RDA from R/3 source system.
Following are the steps followed:
1. Created a realtime Generic Datasource with timestamp as delta specific field and replicated it to BI.
2. First I have created the Infopackage(Initialization with data transfer) and loaded upto PSA.
3. Created a standard DTP to load till DSO and activated the data.
4. Then created a realtime delta infopackage and assigned it to a Daemon.
5. Converted the standard DTP to realtime DTP and assigned the same to the Daemon.
6. Started the Daemon, giving an interval of 5 minutes.
In the first time, Initialization with data transfer is taking the records correctly. But when I run Daemon for taking delta records, its taking all the records again, i.e. both the previously uploaded historical data and the delta records).
Also after the first delta run, the request status in the Daemon monitor, for both Infopackage and DTP changes to red and Daemon stops automatically.
Can anyone please help me to solve these issues.
Thanks & Regards,
Salini.

Salini S wrote:
In the first time, Initialization with data transfer is taking the records correctly. But when I run Daemon for taking delta records, its taking all the records again, i.e. both the previously uploaded historical data and the delta records). .
If I understand you correctly you Initially did a full load. Yes? Well next you need to do intialise & after that delta.
The reason is that if you will select delta initialisation & initialisation without data transfer- it means delta queue is initialised now & next time when you will do delta load it will pick only changed records
If you will select delta initialisation & initialisation with data transfer- It means delta queue is initialised & it will pick records in the same load.
As you know your targets will receive the changed records from the delta queue.
Salini S wrote:
Also after the first delta run, the request status in the Daemon monitor, for both Infopackage and DTP changes to red and Daemon stops automatically.
I take it the infopackage has run successfully? Did you check? If it has and the error is on the DTP then i suggest the following.
At runtime, erroneous data records are written to an error stack if the error handling for the data transfer process is activated. You use the error stack to update the data to the target destination once the error is resolved.
To resolve the error, in the monitor for the data transfer process, you can navigate to the PSA maintenance by choosing Error Stack in the toolbar, and display and edit erroneous records in the
error stack.
I suggest you create an error DTP for an active data transfer process on the Update tab page (If key fields of the error stack for DataStore objects are overwrite On the Extraction tab page under Semantic Groups, define the key fields for the error stack.) The error DTP uses the full update mode to extract data from the error stack (in this case, the source of the DTP) and transfer
it to the target that you have already defined in the data transfer process. Once the data records have been successfully updated, they are deleted from the error stack. If there are any erroneous data records, they are written to the error stack again in a new error DTP request.
As I'm sure you know when a DTP request is deleted, the corresponding data records are also deleted from the error stack.
I hope the above helps you.

Repair request for Delta load? Orders missing in Billing line Items

Hi
I am using BW 3.5; Some Orders are missing in BW for Billing line item reports (2LIS_13_VDITM) according to the users.
The report is based on Cube directly, ODS is not used. I planned to do a repair full request for this month's data so as to get the missing orders.
Could you please advice me on correct procedure to do that? Delta loads runs every day and todays delta is completed.
Thanks and BR
P.B

While it's usually recommended to execute setups during "quiet time", it's not required. Especially in this case. Since you're going to be restricting the setup to only extract a range of Billing Documents that are representative of the dates of data missing (or purely the identified missing documents), there is no need to wait for "quiet time" because you'll pick up the data either in your Full Repair extract or in the delta extract. Depending on how the target InfoProvider for this data is setup (cumulative v. non-cumulative), you may have to look out for duplicate data.
My recommendation would be to run your setup for only those documents that have been identified as missing. That way, you're limiting the amount of data that's required to be extracted to the setup table and then into BW, but also will remove any risk of duplicate data in your target InfoProviders.

Delta Load on DSO and Infocube

Hi All,
I would like to know the procedure for the scenario mentioned below.
Example Scenario:
I have created a DSO with 10 characteristics and 3 keyfigure. i have got 10 Customers whose transactions are happening everyday. A full upload on the DSO was done on 7th October 09. How can i load their changing data's from 8th Oct to till date to DSO? and what will be the situation for the same in the case of Infocube??
Step by step guidance will be a great help
Thanks in advance
Liquid

Hi,
The key-fields take an important role at DSO level alone as you get the power of overwritting records. Once thats done at the DSO level you can simply carry on with a Delta load into the cube from your Change Log table and you don't have to worry about anything. Just to add, all the characteristics in the cube are key-fields so you will get a new records for each different value only the key-figures will sum up for a set of all the same characteristics.
Thanks,
Arminder

FSCM SAP 5.0 Dispute Management-record and case model-dispute cas model.xml

Hello,
I am using the W21: Dipsute Management Building Block Configuration Guide.doc
At the first step, creating a case record model, the configuration guide refers to a file:
6.     In the toolbar of the Modeler in the upper middle section select Model >> Load local file and open the file - dispute case model.xml -.
I do not have this file available, does anyone have any idea how to resolve this?
-     How can I obtain this file
-     Is this file necessary, to create a case record model
Thanks for your help.
Kind regards,
Santiago

Hi Santiago,
This was tricky for me too. Execute tran UDM_DISPUTE. Change your RMS ID (left side, middle box, icon with two overlapping squares) to UDM_DISPUTE. In the same box, expand Record and Case Record Models. Double click on Modeler for Case Records in Dispute Management. This brings up a search box. Click on execute Search. Double click on the Dispute Management entry in the lower box. This gives you the standard model. You can download this, using the Other Model Functions.
Then change to your custom RMS ID (ex. ZUDM_DISPUTE). Expand Record and Case Record Models. Right click on Modeler for Case Records in Dispute Management and select Create. Then upload the standard model into your RMS. Then you can customize the model as you wish. Hope that helps!
Beth

Problem with delta load urgent!!

Hi,
I have a problem with delta load
We have an IP, which loads data from R/3 system daily, its a delta load to the ODS and it updates to the cube with the selection on Company Codes and 0FISCPER
we are in 3.5 system
For a couple of company codes A & B, the init was done for the period 07.2010 to 12.2099 and after tht the deltas are loaded from 07.2010 till 12.2099 and there's no pblm with tht
Now, there was some updation in R/3 system and the data was maintained for the company codes in A& B for the FISCPER 001.2010 to 006.2010, for which init wasnt maintained...
now how shall we need to load the init in this case? dnt ask me how the postings was done in R/3, but my pblm is purely related to the loading data in BW from R/3, as its very imp for the customer to see the data from 01.2010 to 12.2010 in reports, but the data was only available in reports from 07.2010 onwards
do i need to create another IP and maintain the init for 01.2010 to 06.2010? so tht this selection will automatically appear in the ODS delta loading infopackage
pls throw ur inputs ASAP
thank you

Hi Prince,
No need to maintain any Init for this data, It will be enough if you can load the data from jan 2010 to jun 2010 into your Info Cube.
Follow the below steps:
1)create full load IP for this data source.
2) give the selection as A and B company codes and 0FISCPER as 001.2010 to 006.2010
3) in menu bar, click on scheduler --> select full repair request
4) In the next screen check the check box and save
5) Now execute the IP, it will the data with out disturbing your daily delta.
follow the same procedure to load data till to your Info Cube.
Please revert if you have any questions
Regards,
Venkatesh

Selection Criteria for Delta loads triggered using MDM_CLNT_EXTR

Hi ,
Currently we are required to load data only from two specific account groups . Therefore in the selection criteria in mdm_clnt_extr we maintian these two account groups and extract data.
However, when setting up the delta load there does not to be an option to restrcit the delta to a specify an criteria. Therefore, in our case several records from account groups which are not required are passed on to the MDM system.
Is there a way to address this requirement ?
1. There is an option to run the initial load variants at regular intervals, the problem with this is that in our case we have several variant creates as the R/3 system does not allows extraction on more that 999 records at a time. Therefore at point of time to capture the delta records , if we run all these jobs our network gets choked.
2. Run delta job, but without selection criteria it pulls out records which we don't require
Any suggestions on how this problem can be addressed are welcome ,
Thanks in advance,
Anita George

Thanks Michael !
Well, regarding hte ALE settings, we did take a look in bd64 the filters are based on objects which one of these is relevant for customer account groups ? Probably in the future we would require all data, and then is it enogh to remove the filter ?
Can a filter be maintained at the XI level , this would be good as only the required account groups are passed on to MDM . Is there any documentation on available on this ?
Regarding the Import Manager, will have to check this functionality, as it is now no matter how many times we update the map/rename /load/unload it automated imports keep failing.
Our R/3 system seems to have problem extracting more than 999 records, as we tried with different number of records and all those extraction jobs got cancelled. So, currently we are running multiple jobs for the initial load and even this is very time consuming.
Thanks & Regards,
Anita George

Delta load from r3 to bw ?

i have one question on the mechanism of data transfer from r3 to bi 7.0. the followings is my concerns:
scenario:
The total numer of data is 1000 rows and these rows are seperated into 10 data package , each package contains 100 rows.
Now bw is trying to recieve these 10 packages from r3 in sequence.
When 5 data packages have been transfer to bi psa. the network is broken and the tranfer is canceled at the 6th data package.
What i want to know is when the network is reconnected ,Does the transfer start from the 6th data package?
How to find out whether its a delta load or a full load if a transfer is scheduled from r3 to bw ? For both CUBE & ODS.
How to find out how many records have been transfered from r3 to bw while the transfer has ended in
the middle ? I mean how to check how many records have been successfully transfered from r3 to cube/ods .Please tell me for ods as well as cube.
Is the continuation of transfer process is same for both ODS & INFOCUBE, if it ends in the middle ?
What is the procedure for full load & Delta load in case of CUBE & ODS ? I mean how to reschedule the transfer.
And if the whole scenario is is in the support, SO I will be handling these issues on the live production server. Am I right ? So in this case my user id should have access to all the production r3 and production bw to do these change status to red and delete the request and reload the request etc., So I should be logging on to the production server and do all the manipulation, Am I right ?
Last doubt, what is repair request and so if the transfer stops in the middle we change the status to red and reload the request again , Is it called repair request ?
What is the difference between repeat delta & repair request & repair delta ? When do we choose these options, In which scenarios ?
How do we schedule a daily load job from r3 to bw without the use of process chains ? I mean daily it should fetch the records from r3 to bw from the SD datasources at 10.00 PM ,how do we do that ?
Please I am having all these doubts and I want you SAP experts to answer them please so that I can clear my doubts in production support . I really appreciate if someone explain me the scenarios here. It will be a really great help if someonce clears these doubts.

Hi......
What i want to know is when the network is reconnected ,Does the transfer start from the 6th data package?
If your connection is broken in between......inspite your load is through PSA...........you have to delete the request from the target(after making the QM status red)............then you have to reload it again............But before repeating the load check the connection is ok or not in SM59........
How to find out whether its a delta load or a full load if a transfer is scheduled from r3 to bw ? For both CUBE & ODS
This you can check in IP scheduler in the Update tab...........whether it is delta or full load.......
or you can also check in IP monitor(You can go here through RSMO..........IP monitor screen will open directly here............or you can also go through RSA1>> Find your IP >> Double click on it >> Click on the monitor icon in the top >> From the you will go to the IP monitor>> the under the Header Tab you can see whether it is a delta or Full update...........
Or you can check the datasource also..........
If it is a generic datasource go to RSO2..........and check...........If it is a standard datasource check it in RSA5...........
How to find out how many records have been transfered from r3 to bw while the transfer has ended in the middle ? I mean how to check how many records have been successfully transfered from r3 to cube/ods .Please tell me for ods as well as cube
Your load cannot be ebded in the middle.........it can failed.............if it fails then you have to delete the request from the target..........and then repeat the load.......
Is the continuation of transfer process is same for both ODS & INFOCUBE, if it ends in the middle
Yes.........
What is the procedure for full load & Delta load in case of CUBE & ODS ? I mean how to reschedule the transfer
If a full or delta load fails after extraction got completed due lock issue or SID issue.....etc..........and if you load is through PSA.............then just delete the request from the target without making the QM status red.......and reconstruct the request.........no need to repeat the whole load again........
But if you r load is not through PSA..........then make the QM status red........delete the request from the target........and repeat the load...........
And if the whole scenario is is in the support, SO I will be handling these issues on the live production server. Am I right ? So in this case my user id should have access to all the production r3 and production bw to do these change status to red and delete the request and reload the request etc., So I should be logging on to the production server and do all the manipulation, Am I right ?
Yes.......
What is repair request and so if the transfer stops in the middle we change the status to red and reload the request again , Is it called repair request or reload request?
Suppose you delta load has failed ............and you have deleted the request from the target without making the QM status red............In this case your data will be lost and your delta mechanism will get corrupted............In this situation.............
1) Delete the init flag........
2) You have to do Full repair..........(After filling the set up table)
3) Init without data transfer to set back the init flag
4) Then Delta upload.............
In case of an ODS............you cannot load Full update and delta upload parrallely..............Your ODS activation will fail...........suppose you want full upload in the ODS..............then you have to go for Full repair............
What is the difference between repeat delta & repair request & repair delta ? When do we choose these options, In which scenarios ?
I think Full repair concept is now clear............
Suppose your delta load fails...........After that you delete the request after making the QM status red............Then system will ask for a repeat delta when you will try to repeat the load...........which means it will pick the same delta records of the failed load..........
How do we schedule a daily load job from r3 to bw without the use of process chains ? I mean daily it should fetch the records from r3 to bw from the SD datasources at 10.00 PM ,how do we do that ?
This you can do via infopackage or infopackage group...........schedule it at the specific time.....
Check these links :
http://help.sap.com/saphelp_nw04/helpdata/en/20/ad673844a7114be10000009b38f842/frameset.htm
Re: Schedule Infopackage for last day of a fiscal period
Hope this helps you.........
Regards,
Debjani...........

Delta load of customer from R/3 (ECC5.0) to CRM5.0

We have done an initial load of customers from ECC to CRM (R3AS). A change is done on a customer in ECC. I expect the changes to be reflected in CRM as a delta load. I do not see the changes. What am I missing?
All responses are appreciated and will be rewarded.

Hi Mani,
Here are some clues on how to proceed with processing of incomplete or failed BP deltas:
First of all you have to note that during the initial download, no delta download can occur. In particular, no delta download of customers occurs if the initial download of materials occurs at the same time. This is because the material download depends on the customer download.
During the delta download, the CRM system uses the inbound queues R3AD_CUSTOME<nnnnnnnnnn> where <nnnnnnnnnn> corresponds to the customer number in the R/3 system. If an error occurs during the download, the inbound queue for this customer is stopped. You can see the error messages in the flow trace. For the delta download, you have the option to use Transaction CRMM_BUPA_MAP for the error analysis. If you enter the customer and press Enter here, you can display the business partner number for a customer and all open BDocs (that is, those which contain errors or are being processed). To do this, you only have to click the 'Queues and BDocs during download' pushbutton. The system issues an overview of the queue and the open BDocs for this customer and in particular, you can 'look into' the BDoc. As a result, you return to the flow trace and you can display the error messages which occured as described above. During the delta download, you have the option to send the same BDoc again. This is useful if you can simply solve the problem by correcting Customizing in the CRM system. To do this, you simply click the corresponding icon in the flow trace (currently, this is the second icon from the left).
If you have to correct the error in the R/3 system, you have to delete the existing BDoc since it cannot be processed further. As a result, the inbound queue in the CRM system is released again. In this case, you are recommended to delete all existing open BDocs and to make the changes in the R/3 system.
If inconsistencies occur between the R/3 system and the CRM system, you can start a request for the customer. To do this, click the 'Get customer from the R/3 system' pushbutton. This starts a request which uses the inbound queue R3AR_CUSTOMER. Process possible errors as during an initial download.
If you still have problems and don't know how to fix, please post more specific information from the BDoc queue, such as what error message you are getting. It helps us better identify the problem.
Regards,
Rahul
PS. Please award points if it helps!
PPS. For future reference: this info was found in note 362621: Error drng data exchange customer<->business partner

ODS to ODS delta load error

HI
Im loading data into a consolidated ODS from 5 based ODS's. Im doing a delta load from the base to the top level ODS.
recently i made change in the cons ODS.I added a key figure to the ODS(not a key field). Now when i try loading delta again, it gives an error.something which says 'ORA 14400 Inserted partition key does not map to any partition'
has anyone of you come across such an issue.
help will be appreciated
jpjp

HI JP
This is an error on oracle partitioning.. please check the note.
ORA-14400 means=
ORA-14400 occurs if you want to insert an entry in the table that does not match the value range of any partition. In such a case, you must compare the value of the entry with the definitions of the partitions to determine the cause of the error.
please look in to this note..
Note 722188 - FAQ: Oracle partitioning
Note :991181 search this tooo
Hope it helps little
Regards
AK

"Error occurred in the data selection" on init delta load ODS- InfoCube

Hi, gurus and experts!
I'm trying to do Init delta load from 0FIAR_O03 ODS into 0FIAR_C03 InfoCube in PRD env. by InfoPackage "Initialize with delta transfer (with data transfer)". Immediately after the load was started I got error
"Error occurred in the data selection"
with details
"Job terminated in source system --> Request set to red".
Where are no any short dumps. There are 1 activated init load in ODS - nearly 6 500 000 records.
Any ideas about error? And the way I can load data?

Hi Gediminas Berzanskis,
I faced the similar error when I tried to load data from an ODS which contained huge amount of data to a Cube. Even in your case the volume of data is more (around 6.5 million records). The error could be due to the table space issue, please contact your Basis team to check if enough table space exist for both the data targets.
Meanwhile you may also check the RFC connection of the Myself source system.
You can replicate the DSO datasource once and then reactivate the transfer rules using the program RS_TRANSTRU_ACTIVATE_ALL.
Try load with a small amount of data with a Full load option and then with a delta option..
Hope this Helps,
Prajeevan (XLNC)

0 records in master data delta loads.

We have activated delta on 0CUSTOMER_ATTR and verified the queue is active in RSA7. However the delta load is not fetching any records. A full load, however, does. I have deleted and reactivated the delta init multiple times with no success
The infopakage error monitoring status has the following messages
<i>No new data since the last delta update
Diagnosis
The data request was a delta update, meaning, the data basis in the
source system has not changed since the last update.
System response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.</i>
Thanks in advance.
D

hi ok first check what Ajay said the BD61 if it is activated in R3.
After that go to roosgen fill in the name of the DS 0custmer_attr select the line with the R3 from which you want to extract data.
Copy the message type.
Then after you have made the change (update or creation) go to table cdhdr and cdpos to get the change doc object, table name and field name.
After that go to bd 52 paste your message type and add the entry for in your case for the phone number in communication tab
chge doc ADRESSE table : ADR2 field name : TEL_NUMBER
Launch the delta it should work.
In fact when you go to bd52 you will see the fields that are entered for the fields to be taken into consideration when an update is made (they are mainly based on the chge doc obj DEBI) so if you need more fields add them in function of your needs and the info you get in cdhdr and cdpost when you do changes. You can do this only manually so take care of repeating these steps in QA and in prod.
Hope this could help you to solve your issue.
regards
Boujema

Invoice/payment delta loads

We have a web application that displays project/WBS related invoices and payments. We have found that different clearing document types, payment types, credit memos, etc. cause issues with delta loads to this application.
Has anyone addressed this topic before? In the web app, the user wants to see invoices (revenue) by WBS and the corresponding payment(s) - sounds easy but the way data is stored in BSEG, BSAD, BSID, etc., we have found that it is not so easy to do it by WBS.
Any help is appreciated.

Matt,
We are currently using a function module that the ABAPer wrote. This is not SAP BW but it is a case of sending data to an external system so if you think there is another forum that is more appropriate, please move it.
Thank you,
bak

Dispute Case Delta load

Similar Messages

Maybe you are looking for