0BPartner_Text Delta Load

Hi,
When I try to do a Delta Load on 0BPartner_Text, it is not picking up changed records where as I see the changed records in Full load. We are using standard function module "BUPA_CENTRAL_TEXT_EXTRACT_BW" with modifications for other Business Partners. Please suggest me if you had this issue earlier.
Thanks,
Ramana

Why you don't use the standard extractor 0BPARTNER_TEXT?
For it the delta run correctly.
Do you need some enhancement about it?
regards,
Sergio

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.....

Compare data in R/3 with data in a BW Cube after the daily delta loads

Hi Friends,
How can I compare data in R/3 with data in a BW Cube after the daily delta loads? Are there any standard procedures for checking them or matching the number of records?

Hi Sunil,
If you want to check the records daily instead of checking the data in R/3 manually ......
You can try this...
If you have staging DSO(level 1) that means whatever data is in source system load it to Staging DSO without any routines or any modifications.
Now load this DSO data to Cube or DSO(level 2) as per your requirement with routines etc.
Now Staging DSO contains Source system data.
Now the level 2 Cube or DSO contains BW data with some modifications.
Now create a Multiprovider based on level 1 and level 2 data targets.
Now create a report on which keyfigures you want to test the data.
In Multiprovider there is a field called 0infoprovider in data packet dimension.
you can drag this infoprovider to the columns and restict your keyfigures with level 1 and level 2 data targets.
In the first column you can see the level 1 DSO data ( source system data),in the 2nd column you can see the BW data.
Now create a formula which gives the diffrence b/n level 1 and level2.
that is R/3 data - BW data.
If the diffrence is zero both R/3 and BW data are same.
if the diffrence is not eqaul to zero check whether any routine is there or not.

What is the diffrence between full load and delta load in DTP

hI ,
I am trying to load the data into CUBE from another cube using DTP ..
There are 2 DTPS ..
1: DTP with full load
2: DTP with DELTA load ..
what is the diffrence betwen thse two in DTP ...
Please can somebody help me

1: DTP with full load - will update all the requests in PSA/source to the target,
2: DTP with DELTA load - will update only new requests to the datatarget
The system doesnt distinguish new records on the basis of changed records, rather by the request. Thats the reason you have datamart status to indicate if the request has been loaded to further datatargets.

Delta Loads are not working: 0FI_GL_10 With enhancement : HR Data in source

Hello Friends. Thanks for your answer on theory which I know, Please help me with this situation. I read all the sdn response to my message and have below for your suggestion
QUES1: Why the 0RECORDMODE is not coming in Standard DSO and hence it is not there in Transformation in between Infosource and DSO. What do I need to include 0RECORDMODE in standard DSO. What is the correct OSS to Implement on SP 10 to solve this.
Ques2. As suggested by you If I run the Delta loads after waiting for 1 hour of Init load. say init load was done at 11 am . i will do the delta at 12:10 am to psa via Infopack and then wait for an hour to run the DTP from PSA to DSO. Delta Records come in but it also bring in the records in DSO that are not changed from about 7 hours in ECC. and make our total Balance incorrect.
Ques3: We have this Cocatenation of Keys in DSO since we exceeded the total number of 13 key in DSO.
Cocatenation#1 GL ACCT and CHRT OF ACCTS
Cocatenation#1 SEGMENT AND CONT AREA
Cocatenation#1 Version, Value Typem, Valuation view, Currency Type.

Since business want to include HR Data in Keys Like Employee Number, Emp Code, EMPSPIMCODE. Payroll ID and I can not remove these fields from Key in DSO as per the business.
Also the above fields GL ACCT , CHRT OF ACCTS, SEGMENT, CONT AREA
exist in Data FIELDS OF DSO. so what are the steps to modify the design to fix this asap.
Please email me at [email protected] if you have any docs to resolve the above
Thanks
Soniya
null

Did the full load bring all records from sourcesystem to PSA?
Was this an issue with the first delta you have tested ?
Concatentaion of multiple keys into one should not be an issue here as that must have been happening in DSO and delta brings incorrect records to PSA itself.
Are you validating delta records against FAGLFLEXT inputing the timestamp value or RSA3 ..how ?
Check if this note helps
Note 1002272 - NewGL-DataSource 0FI_GL_10, 3FI_GL_*: Missing record.
Is delta bringing incorrect records to PSA or DTP brings incorrect records to DSO from PSA ?
May be you should revisit the logic behind for the enhancement of 0FI_GL_10.
I am facing a similar issue as well but here delta doesnot even bring a single record ( ODS has 20 keys )...will update if resolves and you do the same.
Message was edited by:
Jr Roberto

Error in delta loading from a planning cube

hi all,
I am using a delta load from one planning cube to another.When the changed records are of a magnitude of 100 then it is successful but when the records are of magnitude of 100000 then it stays yellow with no data records sent and eventually fails.the packet size is 20000.
any help is appreciated.

Hello Ajay,
Have you checked that your Request is closed in the planning cube? FM RSAPO_CLOSE_TRANS_REQUEST will do it
It is a customizing issue to tell the infopackage to end "green" when it has no data.
Transaction Spro ==> SAP Netweaver ==> SAP Business Information Warehouse ==> Automated Processes ==> Monitor Settings ==> Set Traffic Light Color. There you have to set the Traffic light on green if no data is available in the system.
Hope that helps
best regards
Yannick

No initial load of Customers, Material and delta load of Sales Orders.

Hi Experts,
I am facing a very troublesome issue. I am not able to setup the Middleware portion for initial and delta loads. I read a lot of documents and corrected a lot of things. finally, the connectivity is done with R/3 and CRM. Initial load of all objects is successful (as per Best PRactices guide). Customizing load is successful.
But after now I have these open issues for which I am unable to find any answers (am really exhausted!!):
- Customer_main load, it was succesful, but no BP's of R/3 are available.
- Material, it failed in SMW01, SMQ2, the errors are:
Mat. for Initial Download: Function table not supported
EAN xxxxxxxxxxxxxxxxxx does not correspond to the GTIN format and cannot be transferred
EAN yyyyyyyyyyyyyyyyyy does not correspond to the GTIN format and cannot be transferred
Plant xx is not assigned to a business partner
- Sales order, it shows green bdoc, but error segments says "No upload to R/3" and the order does not flow to R/3.
We had our system setup 3 years back for data transfer and Middleware. But few things changed and connectivity stopped. I did all that again now, but am not yet successful. Any inputs will be greatly appreciated.
Thanks,
-Pat

Hi Ashvin,
The error messages in SMW01 for MAterial initial load is :
     Mat. for Initial Download: Function table not supported
     EAN 123456789000562 does not correspond to the GTIN format and cannot be transferred
     EAN 900033056531434 does not correspond to the GTIN format and cannot be transferred
     Plant 21 is not assigned to a business partner
I have done the DNL_PLANT load successfully. Why then the plant error?
Some of the messages for BP:
Messages for business partner 1331:
No classification is assigned to business partner 1331
For another,
     Partner 00001872(469206A60E5F61C6E10000009F70045E): the following errors occurred
     City Atlanta does not exist in country US
     Time zone EST_NA does not exist
     You are not allowed to enter a tax jurisdiction code for country US
     Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
Now, the time zone EST is assigned by default in R/3. Where do I change that? I do not want to change time zones as this may have other impacts. Maybe CRM I cna change this, not for sure in R/3. City check has been deactivated in R/3 and CRM, still the error.
Till these 2 are not solved, I cannot go into the Sales order loads.
Any ideas will be greatly appreciated.
Thanks,
-Pat

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

Job terminated in source system - Request set to red during delta load

Hi All,
There is issue with the delta load where as full load works fine and it results in below job termination with below log.
Job started
Step 001 started (program SBIE0001, variant &0000000128086, user ID ALEREMOTE1)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_13_VDITM
RLOGSYS    = BWP_010
REQUNR     = REQU_DA9R6Y5VOREXMP21CICMLZUZU
UPDMODE    = R
LANGUAGES = *
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 17173577728                             *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 3000000                                 *
ztta/roll_extension........... 2000000000                              *
Object requested is currently locked by user ALEREMOTE1
Job cancelled after system exception ERROR_MESSAGE
Please help me to resolve this issue.
Thanks,
Madhu,

Hello,
As per the screen shot provided below, data soruce belongs to LO, so first check in RSA7, whether it has got mark in RSA7, for which you have entries in RSA7 against the data source. If you are not able to find the data source in RSA7, then you need to set-up the update methods, based on the requirement.
1) Direct Delta
2) Queued Delta
3) Unserialised V3 Update
Once it is done, Delete the Previous Initilisation, again perform the Re-Init With Out data and now schedule the Delta Data Loads
Hope this may Help you.
Thanks
PT

Delta loading and Process chain BI

Hi experts,
Two Issues.
1)As i am loading FI data into dso through a process chain which includes Start process>Delta infopackage(which gets data upto psa)>Delta dtp-->Datastore activation.
But infopackage is picking up deltas but DTP is picking up all the previous records plus deltas.
100 records -- 1st day throught Intialization of Delta with Data Transfer
2 delta records -- 2nd day
But DTP is picking up 102 Records on the 2nd Day, which means it is also picking the old records as well.
The DSO must have just 102 records but it is having 202 records.
2) A process chain in running daily as scheduled , but I rescheduled with new scheduling options without deactivating the Process chain.
My Question is
Will the Process chain run for the OLD and the New Schedule or
Is it going to run for new schedule or old one?
or
will I face any Problem because I did not deactivate and made changes to the Change.
Please help me in this matter.
Thanks in advance.
Bhadri.

First query:
I believe that u have used FUll update type DTP is instead of the Delta DTP.. Please cross check the Update mode of the DTP once.
To resolve this issue, delete the total content of the DSO as u have Init and delta loads in PSA. And then using the Delta DTP of the Process chain, load the data. It will extract the total cotent what ever is there in PSA, and later the same DTP will act as the Delta type and will pick the data from the New request of the PSA.
Second Query:
Its always suggested to deschedule the process chain before changing the schedule timings. When ever u do this type of scheduling, just check how many number of JObs available in Schedule mode, if u can see more than one, then delete the older one and keep the new one as it is.
But I always suggest you to deschedule the process chain and reschedule PC with the new timings and then activate the same.
Thanks
Assign points if this helps

Can we use both 0FI_AP_3 and 0FI_AP_4 for Delta Loads at the same time.....

Hi Gurus:
Currently my company uses 0FI_AP_3 for some A/P reporting. It has been heavily customized & uses Delta loading. However, SAP recommends the use of "0FI_AP_4" for A/P data fro delta loads. I was able to Activate 0FI_AP_4 as well & do some Full Loads in Dev/Test boxes. Question is whether I can use both the extractors for "Delta" loads at the same time......? If there are any issue, what is the issue and how ccan I resolve it? Is the use of only one extractor recommended......??
Please let me know as this impacts a lot of my development....! Thanks....
Best...... ShruMaa
PS: I had posted this in "BI Extractors" forum but there has been no response...... Hope to get some response.......! Thanks

Hi,
I would recommend you to use 0FI_AP_4 rather using both, particularly for many reasons -
1. DS: 0FI_AP_4 replaces DataSource 0FI_AP_3 and still uses the same extraction structure. For more details refer to the OSS note 410797.
2. You can run the 0FI_AP_4 independent of any other FI datasources like 0FI_AR_4 and 0FI_GL_4 or even 0FI_GL_14. For more details refer to the OSS note: 551044.
3. Map the 0FI_AP_4 to DSO: 0FIAP_O03 (or create a Z one as per your requirement).
4. Load the same to a InfoCube (0FIAP_C03).
Hope this helps.
Thanks.
Nazeer

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

Error while implementing Delta Load

Hello Experts,
I need your help.
I am trying to extract data from SAP R/3 to BI system.
The R/3 system contains data from 1999-2008 fiscal year. I extracted data for fiscal yr 2007,2006 and 2005 successfully and created a delta info package
In the delta info package I didn't specify any fiscal year limit under the Data selection tab.
I started a background job which needs to run daily. Now my issue is the load came up with an error stating time limit exceeded. I believe the number of data packets exceeded. The request showed a warning sign and it got stuck there. I tried to delete that request and consequently delete the whole delta info package and creating a delta package freshly.
But when I tried to start the process of extraction, the following message popped up. Please tell me what I need to next.
Init. select. for field name currently running in request REQU_464F7XQP5TZIEJPIS0MUV32IB
Message no. RSM1070
Diagnosis
Init. selection for field name with the 'From value' and the 'To-value' , is currently running in request REQU_464F7XQP5TZIEJPIS0MUV32IB.
Procedure
Wait until the init. selection is completed; check the load status in the Monitor.
Thank you. Appreciate your help.
Raj

Hello guys,
I tried to delete the delta request by right clicking on the infopack and hitting manage, and then selecting the particular request and hitting delete.
But when I tried to create a new infopack and initialize it it constantly gave me the same error saying that I need to delete the previous request.
There is another place where you need to delete the request from.
You need to double click on the delta infopackage and on the top menu click on
Scheduler > Initialization options for Source System > Now select the particular delta request and delete it.
This solves the problem and helps you to reintialize the delta load using the new delta infopackage

Error in delta load of 'Customer Group' from R/3 to CRM

Hi Experts,
I added new 'Customer Groups' in R/3. But this is not being updated in CRM. Do I have to trigger initial load again through R3AS or should I create new Customer Groups in CRM?
The BP delta load BDocs are stuck in SMW01 due to this change. Also, if I need to do the Initial load of Customer Group, which object do I need to do the load for? Is it dnl_cust_sales?
Please help as it is a Production issue.
-- Pat

Hi Pat,
Use object 'DNL_CUST_SALES' to download Customer Group from R/3 to CRM.
Use R3AS4 transaction to execute the same.
Best Regards,
Pratik Patel
Reward with Points!

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.

0BPartner_Text Delta Load

Similar Messages

Maybe you are looking for