Updating but000- Augrp when delta queue is created

Hi All,
         my requirement is i need to fill the augrp field in but000 when a account group is changed in R/3
i have tried using FM below in badi BUPA_FRG0040_UPDATE and in GENERAL update but it throws an error <b>NESTED_PERFORM_ON_COMMIT caller: SAPLB
GNERAL_BADI_CALL</b> CALL FUNCTION 'BAPI_BUPA_CENTRAL_CHANGE'
              EXPORTING
                BUSINESSPARTNER = L_BUT000-PARTNER
                CENTRALDATA     = GET_CENTRAL
                CENTRALDATA_X   = CENTRAL_X.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
Can any one help me out with this .....
Thanks.

The reason that the delta for the changes you made to the material showed up in the delta queue for 2LIS_03_BF, instead of 2LIS_03_UM, is due to the difference sources for that data.
The MKPF and MSEG (Material Movements) tables, along with MBEW (Material Valuations) table, are the source for the 2LIS_03_BF DataSource and not for the 2LIS_03_UM DataSource. The 2LIS_03_UM DataSource is sourced by the BKPF and BSEG (Accounting Documents) tables.
Since you changed the material price and added new material prices, there were no accounting transactions that took place and that is why no delta went to the 2LIS_03_UM DataSource delta queue. Once you have an accouting transaction take place, with an associated material movement, then you will have a delta generated for the 2LIS_03_UM DataSource.

Similar Messages

How to recover when Delta Queues have been emptied by error ?

Hi All,
Here is our problem : the ECC Delta Qs have been emptied by error some days ago, and for the moment we have frozen every BW updates from ECC, but the Delta Queues have been being filled in ECC since that.
We have so smart ideas so far...
Thx 2 all in advance

Hello ThoLei ,
In case your normal delta is running file in BW and the only thing you are concerned about is the data missed during the day when the queue got deleted, then yes you can go ahead with Repair Full option. If you refresh the missing data and no need to worry about delta.
Regards,
Pratap Sone

Problem Updating partner details when the confirmation is created.

I want to update the partner details when the confirmation is created
In SRM (non -sus ), Confirmation is created using the function module : bbp_pd_conf_create .
While creating confirmation, only item wise confirmation details are updated.
But the partner details of that confirmation is not updated.
bbp_pd_po_Getdetail is used to get the purchaser order details .
the same partner details are used in the confirmation create function module .
the following are the fm used for the above purpose ,
BBP_pd_conf_create
bbp_pd_conf_update
bbp_pd_conf_save
What are the details i should change in partner details to get updated. like guid information..
Please provide some suggestions ...
Thanks,
Uma

In BBP_PD messages
i can see the header , item and Stats details .
What ever value i retreive from PO getdetail fm , i pass it to the partner details while creating confirmation. only item details get updated but not partner details ,
I think its missing with the p_guid details. i dont know how to pass value consistently the p_guid value in hte partner when the item details are confirmed.

Any user exit for updating VBRK-XBLNR when the billing is created?

Hi all,
I understand that in VTFL, there are 4 options for Reference number.
But if i want it has a special value, how i can achieve it?
Thanks,
James

Hi,
See Note 301077 - User exits for the interface to accounting. I think that EXIT_SAPLV60B_001 is the right option.
Regards
Eduardo
PD: althought perhaps USEREXIT_FILL_VBRK_VBRP in RV60AFZC fits better for your requirement.
Edited by: E_Hinojosa on Jan 25, 2011 9:08 AM

Red Traffic Light for Datasources Delta Queues

Hi all,
Our R/3 source system is connected to our BW system.
Between the two systems we operated standard logistics datasources delta queues, by filling the setup tables and performing an initial update.
The datasources delta queues were created and used over a month (according to the RSA7 they all marked with green traffic light).
Now, we copied the R/3 source system to a new one.
After doing so, all the delta queues traffic light turned to be red.
Does anyone can provide a technical explanation/reason to this problem?
Also, is there something we could do to "save" this delta queue, without needed to delete it and create it all over again?
Thanks ahead,
Shani Bashkin

Hi Eddo,
Thanks for your help.
Yes, I'm using the same system name and system id. The new copied system has the same name and id like the productive system.
Also, it seems like the RFC connection to the BW is lost.
The question is why?
Thanks,
Shani Bashkin

Direct Delta, queued , Non-serialized V3 Update

could someone out here help me in understanding the Direct Delta, queued , Non-serialized V3 Update...
i mean a detailed level explanation.... or just in case u have any document then kindly pass it on.... to [email protected]

Hi,
Update Methods,
a.1: (Serialized) V3 Update
b. Direct Delta
c. Queued Delta
d. Un-serialized V3 Update
Direct Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues.
Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 delta extractions of documents for an LUW are compressed for each DataSource into the BW delta queue, depending on the application.
Non-serialized V3 Update:With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
Note: Before PI Release 2002.1 the only update method available was V3 Update. As of PI 2002.1 three new update methods are available because the V3 update could lead to inconsistencies under certain circumstances. As of PI 2003.1 the old V3 update will not be supported anymore.
(serialized) V3
Transaction data is collected in the R/3 update tables
Data in the update tables is transferred through a periodic update process to BW Delta queue
Delta loads from BW retrieve the data from this BW Delta queue
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Issues:
Even though it says serialized , Correct sequence of extraction data cannot be guaranteed
V2 Update errors can lead to V3 updates never to be processed
direct delta
Each document posting is directly transferred into the BW delta queue
Each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Less monitoring overhead of update data or extraction queue
Cons:
Not suitable for environments with high number of document changes
Setup and delta initialization have to be executed successfully before document postings are resumed
V1 is more heavily burdened
queued delta
Extraction data is collected for the affected application in an extraction queue
Collective run as usual for transferring data into the BW delta queue
Transaction postings lead to:
1. Records in transaction tables and in extraction queue
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Suitable for environments with high number of document changes
Writing to extraction queue is within V1-update: this ensures correct serialization
Downtime is reduced to running the setup
Cons:
V1 is more heavily burdened compared to V3
Administrative overhead of extraction queue
Un-serialized V3
Extraction data for written as before into the update tables with a V3 update module
V3 collective run transfers the data to BW Delta queue
In contrast to serialized V3, the data in the updating collective run is without regard to sequence from the update tables
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3.This BW Delta queue is read when a delta load is executed.
Issues:
Only suitable for data target design for which correct sequence of changes is not important e.g. Material Movements
V2 update has to be successful
Hope this helps
regards
CSM Reddy

Problem to initialize delta queue of datasource from CRM 7.0.

Hi all,
I've some problem to initialize delta queue of datasource from CRM 7.0. After initialize the Init in BW, the delta queue was created but after the user changed data, this changed didn't populated into delta queue.
I tried the steps below but without any success. Anybody know how can I correct this issue?
Suggestion 3: Please check the following.
Please Check if the services have been generated in transaction GNRWB.
If they are not active(not marked 'X' before their names) then activate
the services following the steps here.
Go to transaction GNRWB
Select BUS_TRANS_MSG
Select (on the right, the services) : BWA_DELTA3, BWA_FILL, BWA_queue
Press Generate.
Also check for the following:
1. The delta should have been initialized successfully.
2. Confirm that all Bdocs of type BUS_TRANS_MSG
are processed with success in SMW01.
3. If there are queues in SMQ1 with erroneous status then activate
these queues.
In Transaction SMQ1 if there are Queues existing with
names beginning with CRM_BWAn (n is number) then
activate these queues in the same transaction.
4.a)If required activate the datasource
Go to transaction BWA5 > select the required datasource and
activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
selecting the name of the datsource and pressing the candle icon for
'activate delta'.
5. In BW system
Go to transaction RSA1 > modeling > infosources > select the
infosource > right mouse click on the selected
infosource > choose option replicate datasource
Activate the infosource.
6. Go to the scheduler for the infosource > select delta in the
update >choose the option PSA only (in the Processing tab)

Hi Peter,
Thank you for your answer.
But we need to find out what the reason for this import error is.
Our customer will not be very pleased to see that all IDocs from CRM system cannot be found in the IDOC folder.
IDX2 import of metadata is no issue.
We were successful for standard and customer Idocs here.
Additional information:
We are already importing Idocs from a SAP ECC 6.0 system into PI in another SWCV
successfully. So this is a CRM system specific issue in our environment.
Regards
Dirk
Edited by: Meinhard Dirk on Aug 27, 2010 10:30 AM

How to delete the data in update queue and delta queue for Queued delta?

Dear BWers,
How do i delete the delta queue and update queue data before i fill the setup tables for a extraction based on Queued delta. Please help.
Thanks
Raj

Hi Raj,
I think you need some ground work for the LO extraction same as others here. Please read the 3 blogs expliciltly created for LIS by Robert Negro.
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
As well, the OSS 380078 would clear your doubts reagrding the the BW QUEUE mainatinance.
Please let me know if these material has been suffecient enough.
regarda,
raj

Difference between delta queue and unserialized v3 update - lo cockpit

Hi guys,
What is the difference between delta queue and unserialized v3 update.
How does sm13 come into picture. During system outages, how is setup table affected.
Edited by: zsl05 on Apr 22, 2009 11:29 PM

Hi,
In BW there are basically 3 types of delta queue mechanisms
1) Direct Delta: In this, as soon as the data is posted in the application tables, it is transfered to the RSA7 delta queue.
2) Queued delta: In this, as soon as the data is posted, it is first transferred to the Extractor Queue(LBWQ) and then via V3 Collective job to the delta queue periodically. The transfer sequence is the same as the sequence in which the data was created
3) Unserialized V3 : In this,when data is posted to the application table, it is posted into the Update queue first(SM13). It is then transferred to the Extractor queue (LBWQ) and then via V3 jobs to the Delta queue (RSA7). The difference lies in the fact that the sequence in which data was posted in the application table does not matter.
Hope this helps.
Regards.

Sequence of operations - Direct Delta, Queued Delta, Unserialized V3 Update

Is the below understanding about each update method correct?
a) Direct Delta
- The user selects a process (e.g. creating, updating or deleting a purchase order), fills the fields in the screen, presses SAVE.
- A module makes inserts, updates and deletes on the Application Tables.
- This or another module inserts delta relevant information (e.g.: before and after image, the key for deletion, reverse image, etc) about this PO in the Communication Structures.
- Another module reads the Comm Structures and inserts this information in the Delta Queue.
- COMMIT the operations in the App Tables and in the Delta Queue.
- The user receives a success message.
b) Queued Delta
- The user selects a process, fills the fields in the screen, presses SAVE.
- A module makes inserts, updates and deletes on the App Tables.
- This or another module inserts delta relevant information about this PO in the Comm Structures.
- Another module reads the Comm Structures and inserts this information in the Extraction Queue.
- COMMIT the operations in the App Tables and in the Extraction Queue.
- The user receives a success message.
- Periodically, a Collective Run inserts this information in the Delta Queue and deletes it from the Extraction Queue.
c) Unserialized V3 Update
- The user selects a process, fills the fields in the screen, presses SAVE.
- A module makes inserts, updates and deletes on the App Tables.
- COMMIT the operations in the App Tables.
- The user receives a success message.
- This or another module inserts delta relevant information about this PO in the Comm Structures.
- Another module reads the Comm Structures and inserts this information in the Information Structures (also known as Statistical Tables), as part of the LIS data flow u2013 as I understand it has nothing to do with LO data extraction, but it is coded this way.
- If the inserts into the Information Structures work well, another module reads the Comm Structures and inserts this information in the Update Table.
- Periodically, a Collective Run inserts this information in the Delta Queue and deletes it from the Update Table.
Thanks
César Menezes

Krishna
Thanks for your attention, but I've already read:
- Roberto Negrou2019s blogs,
- OSS Note 505700,
- Power point u201CNew Update Methods for Logistics Extraction with PI 2003.1u201D (quoted in the OSS Note, link u201Chttp://service.sap.com/~sapidb/011000358700005772172002u201D),
- many threads wich provided very useful information.
I need now more detailed information, step by step operation on each update method, like I posted in the thread.
Actually I want to cross this information with another thread I posted (), about Figure 6 (Comparison among call function hierarchies involved in different update methods).
This Figure is showed in Negrou2019s Episode Three and in the power point. I believe that this figure is wrong or at least is missing something.
Do you know about these two points, or can you please forward to someone who can help us ???
Thanks
César Menezes

At what point is delta queue updated?

Hi everbody,
I want to know at what point delta queue is updated? Is it updated after a successful init load in BW or is it updated when the set up tables are filled? If i delete the delta queue do i need to run init load again?
Thanks
Raj

The delta queue is a data store in the source system into which data records are automatically written using an update process in the source system (such as with FI documents) or using extraction using a function module after a data request from the BW
Please cgeck this for more details
Checking the Delta Queue
http://help.sap.com/saphelp_nw04/helpdata/en/6f/66bca6ae43744283d74f1e456ff6c0/content.htm
Update Process
http://help.sap.com/saphelp_nw04/helpdata/en/84/81eb588fc211d4b2c90050da4c74dc/frameset.htm
2 Deleting data from the delta queue does not require the delta method to be reinitialized to write DataSource data records into the delta queue.
Note that data that has yet to be read from the delta queue is also deleted. As a result, any existing delta update is invalidated. So, only use this function when you know what you are doing!
Hope this helps
Thnaks
sat
Message was edited by: Sat

Diff between update queue and delta queue

hi all
can anyone tell me wats is the diff between update queue and delta queue? wats is delta queue and update queue?
wats are the possible system generated errors and custom generated errors?
Thanks,
Shreya

Hi Shreya,
Update queue(LBWQ) comes into the picture when you choose Queued Delta for the Datasource. the data first comes to the Update queue and than goes to the Delta queue, however if you have choosen Direct Delta than the posted record will directly go to the Delta queue(RSA7).
Here is the URLS for Roberto's weblog to understand the whole LO-Extraction process.
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
Hope it helps you!!!!
Regards,
Amit
Pls do not forget to assign points, if helpful.

Difference Between Update Queue and Delta Queue

Hi Experts ,
Could u brief out the difference between Extraction Queue , Update Queue and Delta Queue ?

Hi
a) Serialized V3 Update(If you set this as your delta mode then data will populated into extraction queue tables)
This is the conventional update method in which the document data is collected in the sequence of attachment and transferred to BW by batch job.The sequence of the transfer does not always match the sequence in which the data was created.
b) Queued Delta(If you set this as your delta mode then data will be populated into update queue tables)
In this mode, extraction data is collected from document postings in an extraction queue from which the data is transferred into the BW delta queue using a periodic collective run. The transfer sequence is the same as the sequence in which the data was created
Delta queue is a table which collects data from extraction queue/update queue tables based on the frequency you have set(daily/hourly etc)..from these tables we will get delta records to bw with infopackage delta run..
Hope it helps
Thanks
Teja

When trying to update Apps in iTunes on my computer my old Apple ID appears, which is no longer in use and has no password; even when I try to create a password for this Old ID, Apple won't let me. When I go into see my Account settings My new Apple ID /

When trying to update Apps in iTunes on my computer my old Apple ID appears, which is no longer in use and has no password; even when I try to create a password for this Old ID, Apple won't let me. When I go into see my Account settings My new Apple ID / iTunes ID are listed and the passwords are correct obviously so why can't I update my Apps? Why does my Old apple ID keep appearing and how can I get Apple to change this?

I have the same problem - it is maddening. I rely on this iPad for work so this is not just an annoyance! The above solutions of changing the appleid on the device or on the website do not work.
The old email address no longer exists - I haven't used it in a year probably and I no longer have the account. I logged into the appleid website and there is no trace of the old email address so there is nothing that can be deleted or changed there. On the iPad there is no trace of the old email address so nothing can be deleted there either. I have updated the iPad software and the same problem comes right back. Every 2 seconds I am asked to log in using the old non-existent email. The device is currently useless.
The only recent change to anything was the addition of an Apple TV device, which was set up using the correct login and password.
Does anyone have any ideas? The iPad has been backed up to the iCloud so presumably it now won't recognize the current iCloud account? So restoring may notbe an option?

Can't update master table when creating a materialized view log.

Hi all,
I am facing a very strange issue when trying to update a table on which I have created a materialized view log (to enable downstream fast refresh of MV's). The database I am working on is 10.2.0.4. Here is my issue:
1. I can successfully update (via merge) a dimension table, call it TABLEA, with 100k updates. However when I create a materialized view log on TABLEA the merge statement hangs (I killed the query after leaving it to run for 8 hrs!). TABLEA has 11m records and has a number of indexes (bitmaps and btree) and constraints on it.
2. I then create a copy of TABLEA, call it TABLEB and re-created all the indexes and constraints that exist on TABLEA. I created a materialzied view log on TABLEB and ran the same update....the merge completed in under 5min!
The only difference between TABLEA and TABLEB is that the dimension TABLEA is referenced by a number of FACT tables (by FKs on the FACTS) however this surely should not cause a problem. I don't understand why the merge on TABLEA is not completing...even though it works fine on its copy TABLEB? I have tried rebuilding the indexes on TABLEA but this did not work.
Any help or ideas on this would be most appreciated.
Kind Regards
Mitesh
email: [email protected]

Thats what I thought, the MVL will only read data that has changed since it was created and wont have the option to load in all the data as though it was made before the table was created.
From what I have read, the MVL is quicker than a Trigger and I have some free code that prooved to work from a MVL using it as a reference to know what records to update. There is not that much to a MVL, a record ID and type of update, New, Update or Delete.
I think what I will have to do is work on a the same principle for the MVL but use a Trigger as this way we can do a full reload if required at any point.
Many thanks for your help.

Updating but000- Augrp when delta queue is created

Similar Messages

Maybe you are looking for