Quary wiht restricted kf problem

Hi gurus,
in my row i have Product characteristic,
in my column i have Sales Quantity key figure.
i want to visualise this table for posting periods between 06.2006 and 12.2007.
i restricted my kf 2 times.
in first restriction
Fiscal Year :2006
Posting Period : [6-12]
in second restriction
Fiscal Period :2007
Posting periiods: [1-12]
the screen i got is like this ;
means i can't input, * means input-ready area.
...............2006..................................................2007......................................
prod./p.p..1..2..3..4..5..6..7..8..9..10..11.12.TOT.1..2..3..4..5..6..7..8..9..10..11..12
...X.........#..#..#..#..#..#.................. ...........................................
...Y........#..#..#..#..#..#.................. ...........................................
i don't need and i don't want to see first 6 months of 2006. And i also restricted posting period (6-12) for 2006.
Why it shows me first 6 month of 2006 ?
Is this a general problem?
i'll assign points for helpfull answers.
thanx

here i'm sending the screenshots.
thats the . you can see that i have 2 key figures. One for 2006 one for 2007: columns
here is restriction detail for[2006 | http://img520.imageshack.us/img520/5410/2006restrictionuc1.jpg]
here is restriction detail for[2007 | http://img174.imageshack.us/img174/1038/2007restrictionav4.jpg]
and that's what i got http://img174.imageshack.us/img174/6066/screen1kh7.jpg
"kayıt dönemi" means posting period
"mali yıl" means fiscal year
Message was edited by:
Hayrettin Ustabasi

Similar Messages

How do I fix this restrictions passcode problem?

It has been two days since I posted this discussion. I have gotten over 80 views but not a single reply. I am just wondering why. Is the discussion to long? Have I violated some rule? Some changes have been made to make things a little clearer. I am sincere about this and want to make what ever correction is necessary. Plus I really do need help.
I recently bought a iPhone 3gs from a friend. AT&T was the phones carrier so in order to use it on the carrier of my choice I had it unlocked and activated the phone with my carrier (actually straight talk) on a AT&T compatible SIM card. All of my friends settings and contents had been successfully erased and the phone was operating good. I have run into a problem though and I am hoping once again that someone can point me in the right direction towards a solution.
Here is the problem:
I attempted to sync my phone with iTunes on my computer and a screen came up asking me how i wanted my phone to be treated, like a new iPhone or to back up an existing one (not sure how it was worded). My reasoning was that it is not a new phone, so not understanding the consequences of these options I chose "back up an existing one." Well, the result is that although I can still make and receive calls and send texts, all of my settings and contents have been erased and replace with my friends old settings and contents. Now, I cannot and never could erase settings and contents from the phone because it is and was passcode protected and my friend has forgotten the restrictions passcode. When I had my phone set up after it had been unlocked and activated, I did it through itunes for that reason. But now I am back to having a restrictions passcode and I cannot erase anything. Now each time I try to restore my phone through iTunes, the only thing that happens is that it updates the iOS.
What I want to do is erase it and start fresh. Not sure how to do that now and would really appreciate the help.

ovation wrote:
I recently bought a iPhone 3gs from a friend. AT&T was the phones carrier so in order to use it on the carrier of my choice I had it unlocked and activated the phone with my carrier (actually straight talk) on a AT&T compatible SIM card.
Here is the problem:
I attempted to sync my phone with iTunes on my computer and a screen came up asking me how i wanted my phone to be treated, like a new iPhone or to back up an existing one (not sure how it was worded).
My reasoning was that it is not a new phone, so not understanding the consequences of these options I chose "back up an existing one." Well, the result is that although I can still make and receive calls and send texts, all of my settings and contents have been erased and replace with my friends old settings and contents.
Now, I cannot and never could erase settings and contents from the phone because it is and was passcode protected and my friend has forgotten the restrictions passcode.
When I had my phone set up after it had been unlocked and activated, I did it through itunes for that reason.
But now I am back to having a restrictions passcode and I cannot erase anything. Now each time I try to restore my phone through iTunes, the only thing that happens is that it updates the iOS.
What I want to do is erase it and start fresh. Not sure how to do that now and would really appreciate the help.
restore as new device. http://support.apple.com/kb/HT1414

OpenSSO wiht security-costraints : PROBLEM!!!

HI,
i'm developing a simple web application. I use openSSO for authentication and i need to use a security costraint for blocking page to any groups of users.
The problem is:
I log in with an authorizated user and i obtain a 403 forbidden error when i try to access to an url that is part of the web-resource-collection of the security costraint in the web xml.
But if I come back and refresh the page and i retry to access to these URL i obtain the page.
Can anyone help me?
Thanks

it seems you have not configured properly the policy agent + the user login form.
You should do the following tasks:
- Enable policy agent in ALL mode (URL+J2EE)
- Configure a login form in your webapp as if were a JSP
- The login form url should be configured in your policy agent.
If this is done, when you ask an URL will happen:
- You don't have app level session, so you're redirected to the login-form
- Policy catch the login form request, It POST a username/ssoTokenID to j_security_check
- Your container log in the user, using the agentRealm
- then an application level session is created
- You're redirected to the original URL requested
- The appserver will be able to evaluate properly security constraints.
Hope it helps

Restriction passcode problems

My ipad does not accept my restriction passcode and i am 100% sure that i remember the passcode. It must be a bug from your new i.o.s. Can i reset my restriction password without having to use "ibackupbot"?

Hi,
I'm afraid you have to restore it like new from a Windows or Mac PC, through iTunes. Sorry.
Hope this helps!

Is there a problem with itunes (11.1 latest version) on a windows 7 non-administrator (standard) account?

When I tried to update my dad's iphone 5 to iOS 7 on a windows 7 standard account an unknown error was encountered and he lost everything! It also doesn't recognise my mum's iphone 4s (already updated to iOS 7), it gets an error, but her phone works fine on my administrator account. Do non-administrator restrictions cause problems? Any support would be really valued. Thanks.

I think there is a problem. I dont get the noises on each song even though that happened to me on a previous update but rather than being a sporadic click it was a very loud hiss over every single track...
The latest problem with my copy is that the songs are only playing out of one speaker and its not even the centre speakers, its the left speaker.
The last time itunes didnt work properly it took apple around a week or so to correct so im not worried at the moment but i have to use windows media player in the mean time which I dont like to use.
HP Windows XP

Problem about roaming when using IP Phone 792X

Hi Guys,
My Customer is wiht the following problem: When the user is using the IP Phone 792X near the Access Point the call worked Ok. When the User to do the roaming to another Access Point He hear audio only one side. If He turn off the IP Phone and turn on the call came back work. I don´t sure, but, I don´t believe that the problem is the IP Phone Configuration. My question is: Can be any problem about Wireless Controller configuration?
Information about the equipament:
IP Phone 792X Firmware -
CP7921G-1.3.3.LOADS
CP7925G-1.4.1.LOADS
Access Point
Model: 1140
Wireless Lan Controller
Model: WS-SVC-WISM-1-K9
Product Version.................................. 6.0.188.0
Thank You,
Wilson

Hi Wilson,
The first thing I would check is that you have proper cell overlap.
See page 3-13 in the deployment guide:
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns279/c649/ccmigration_09186a00808d9330.pdf
Without seeing more info, we can't conclude that this is a controller code issue, but I'd upgrade the controller to 6.0.202 to be sure.
6.0.188 is deferred:
http://www.cisco.com/web/software/Wireless/Deferral/Software_Advisory_6_0_196_0.html
You may also want to run your controller's config through the config analyzer and enable 792x voice checks:
https://supportforums.cisco.com/docs/DOC-1373
hth
jeff

Why we will go for Queue delta instead of Unserialized and Direct delta ?

Hi Experts,
Why we will go for Queue delta instead of Unserialized and Direct delta ? specify any reasons for that ?
What happens internally when we use Queue delta , Direct delta ?
I will allocate points to those who help me in detail. My advance thanks who respond to my query.

Hi,
Direct Delta
With this update mode, extraction data is transferred directly to the BW delta queues every time a document is posted. In this way, each document posted with delta extraction is converted to exactly one LUW in the related BW delta queues. If you are using this method, there is no need to schedule a job at regular intervals to transfer the data to the BW delta queues. On the other hand, the number of LUWs per DataSource increases significantly in the BW delta queues because the deltas of many documents are not summarized into one LUW in the BW delta queues as was previously the case for the V3 update.
If you are using this update mode, note that you cannot post any documents during delta initialization in an application from the start of the recompilation run in the OLTP until all delta init requests have been successfully updated successfully in BW. Otherwise, data from documents posted in the meantime is irretrievably lost. The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) A maximum of 10,000 document changes (creating, changing or deleting documents) are accrued between two delta extractions for the application in question. A (considerably) larger number of LUWs in the BW delta queue can result in terminations during extraction.
b) With a future delta initialization, you can ensure that no documents are posted from the start of the recompilation run in R/3 until all delta-init requests have been successfully posted. This applies particularly if, for example, you want to include more organizational units such as another plant or sales organization in the extraction. Stopping the posting of documents always applies to the entire client.
Queued Delta
With this update mode, the extraction data for the affected application is compiled in an extraction queue (instead of in the update data) and can be transferred to the BW delta queues by an update collective run, as previously executed during the V3 update.
Up to 10,000 delta extractions of documents to an LUW in the BW delta queues are cumulated in this way per DataSource, depending on the application.
If you use this method, it is also necessary to schedule a job to regularly transfer the data to the BW delta queues ("update collective run"). However, you should note that reports delivered using the logistics extract structures Customizing cockpit are used during this scheduling. This scheduling is carried out with the same report which is used when you use the V3 updating (RMBWV311, RMBWV312 or RMBWV313).There is no point in scheduling with the RSM13005 report for this update method since this report only processes V3 update entries. The simplest way to perform scheduling is via the "Job control" function in the logistics extract structures Customizing Cockpit. We recommend that you schedule the job hourly during normal operation - that is, after successful delta initialization.
In the case of a delta initialization, the document postings of the affected application can be included again after successful execution of the recompilation run in the OLTP (e.g OLI7BW, OLI8BW or OLI9BW), provided that you make sure that the update collective run is not started before all delta Init requests have been successfully updated in the BW.
In the posting-free phase during the recompilation run in OLTP, you should execute the update collective run once (as before) to make sure that there are no old delta extraction data remaining in the extraction queues when you resume posting of documents.
Using transaction SMQ1 and the queue names MCEX11, MCEX12 or MCEX13 you can get an overview of the data in the extraction queues.
If you want to use the functions of the logistics extract structures Customizing cockpit to make changes to the extract structures of an application (for which you selected this update method), you should make absolutely sure that there is no data in the extraction queue before executing these changes in the affected systems. This applies in particular to the transfer of changes to a production system. You can perform a check when the V3 update is already in use in the respective target system using the RMCSBWCC check report.
In the following cases, the extraction queues should never contain any data:
- Importing an R/3 Support Package
- Performing an R/3 upgrade
For an overview of the data of all extraction queues of the logistics extract structures Customizing Cockpit, use transaction LBWQ. You may also obtain this overview via the "Log queue overview" function in the logistics extract structures Customizing cockpit. Only the extraction queues that currently contain extraction data are displayed in this case.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) More than 10,000 document changes (creating, changing or deleting a document) are performed each day for the application in question.
b) In future delta initializations, you must reduce the posting-free phase to executing the recompilation run in R/3. The document postings should be included again when the delta Init requests are posted in BW. Of course, the conditions described above for the update collective run must be taken into account.
Un-serialized V3 Update
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.
With this update mode, the extraction data of the application in question continues to be written to the update tables using a V3 update module and is retained there until the data is read and processed by a collective update run.
However, unlike the current default values (serialized V3 update); the data is read in the update collective run (without taking the sequence from the update tables into account) and then transferred to the BW delta queues.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method since serialized data transfer is never the aim of this update method. However, you should note the following limitation of this update method:
The extraction data of a document posting, where update terminations occurred in the V2 update, can only be processed by the V3 update when the V2 update has been successfully posted.
This update method is recommended for the following general criteria:
a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.
Thanks,
JituK

Proximity Sensor delay!

Dear all,
After updating my phone to 4.1 I found no issues with PS exept one. When I remove the phone from my ear at the end of the call or to see who is calling if there was another line or for any other reason there is always a delay of about one second or so. I did compare it with my 3GS sure there is a delay and some times I can not switch between calls quickly as it should.
Is this normal to everyone, can someone please compare between both phone. If this issue is happening to all the new iPhone 4 then I have no problem exept leaving with. But if it only on mine I will take it back to exchange it.
Kindly confirm please.
Thanks

Thank You for the replay, now I now that it's bug in the firmware. I'm constantly loosing my respect to Apple!... Considering the way they thread their customers! They offer too much restrictions, and problems!

Calculating Profit of COGS - different ways of calculating

I found that in SAP B1 the profit calculation varies and it depends on where you look and the different settings allowed. For instance:
I am talking about the calculation method of COGS:
1. In System Initialisation/Document Setting one can set the workings of Profit on say Last Calculated Price
2. In individual (say Item Code ABC) Item Master Data one can set the calculation method on FIFO
3. In another Item Master Data (say Item code FGH) can be set on Average Cost method
So now we have 3 ways of calculating COGS in the same system - so how can one achieve consitency?
My understanding is that setting 1 is not taken into account when the system charges COGS, so does anybody know what is the purpose of this setting?
Thank you
Robert
I am trying to debate this in order to confirm my understanding

Robert--
The basic rule to understand in B1 is that specific settings take precedence over general settings. The company-wide default settings that you find in the System Initialization screens set the general parameters for the system. But they may be overridden on specific records - like the Item Master or BP Master. On these, company policy may determine that certain items or business partners do not fit the general rules and should be treated differently in some regard. So an authorized user may change the default settings for these records, either during the initial entry of the record or afterwards (if changes to the specific fields are permitted). Similarly, users may change some settings on specific documents if they represent an exception situation that should not be forced to follow the usual rules.
The other consideration - which should make accountants happy - is that settings that affect journal postings generally cannot be changed once they have been used. So for example, a customer's AR control account number cannot be changed once there are any transactions for that customer. An item's valuation method cannot be changed while there are quantities in the warehouse or open documents that may have caused journal postings. These rules may not represent consistency, as you wish for, but they do enforce an integrity in the accounting process.
The place where these restrictions cause problems is if records are imported from a legacy system without regard to the system defaults. Since these records are brought in and saved in a single process, they can have whatever settings are specified in the import process, which may or may not be the same as the system defualts you wanted. Once these records are created and then used in transactions, it is very difficult to make them conform to what you wanted. Changing the system defaults will never cause retroactive changes to existing records.
If you are having continuing problems with settings on new records, I would consider restricting authorization for adding or editing new records to those people who understand what the ramifications are. Additional training for your personnel may also be helpful, now that you have a better understanding of how the system works.

Material Receipt

Hi all,
I want to receipt material against process order.
In MIGO screen I have entered
Goods receipt -> Order--> Proc.Order No. (Ex:1234567890).
Now system is allowing me to Receipt as well With draw also.
But system need not to allow 261 movement in this scenario (101).
How to restrict this problem.
Please, can anybody help me in this.
regards,
Anand.M (Hyderabad)

HI,
Instead of MIGO, use MB31, with movement type 101 against the order.
Regards
Merwyn

ActionEvent Vs FocusListener

Hi all,
and thx in advance.
My problem look like the Bug ID: 4224932
Environment Description :
-     I have some some JtextField.
-     each JtextField have an difference instance of FocusListener listener.
-     On focusLost I�m doing a validation (check) of JtextField content.
-     I have also OK Button.
Problem Description:
-     When I click on OK button first I receive the an ActionEvent and at the end we have focusLost Event.
Consequence:
-     last JtextField does�t have a validation.
Restriction:
- This problem append only on HPUX, on Windows I receive first the focusLost and then the ActionEvent.

Swing related questions should be posted in the Swing forum.
Use an InputVerifier, not a FocusListener.
If you need further help then you need to create a "Short, Self Contained, Compilable and Executable, Example Program (SSCCE)",
see http://homepage1.nifty.com/algafield/sscce.html,
that demonstrates the incorrect behaviour, because I can't guess exactly what you are doing based on the information provided.
Don't forget to use the "Code Formatting Tags",
see http://forum.java.sun.com/help.jspa?sec=formatting,
so the posted code retains its original formatting.

Disappearing downloaded items

I recently suffered a major drive crash. I sent Apple a message regarding recovering some of my downloaded items (specifically a season of a TV Show). It downloaded, but now I can't find it at all. It is not in its folder, and iTunes doesn't know where it is (the exclamation point comes up next to all the episodes). Now, I can't re-re-download it from iTunes because Apple restricts reporting problems/recovering downloaded items to one time.

Did you do a search of your HD using Spotlight?
MJ

Mysap ERP and BW in one instance

Hello,
in the mySAP ERP 2004, Master Guide", chapter "Technical Overview" it is said that "ERP und BW in the same system ... can only be supported on a project basis".
This is difficult to understand for customers who are told that with mySAP ERP they will have "lower TCO through integrated SAP BW 3.5"
Can somebody explain with respect to the installation of BW 3.5 and ECC 5.0 in one instance
- why there are restrictions
- which problems have to be expected.
Are there any experiences?
Thanks!
Peter

hi,
-->"This is difficult to understand for customers who are told that with mySAP ERP they will have "lower TCO through integrated SAP BW 3.5""
that means mySAP ERP has install BW3.5 with R3 installation.
and BW work as a unique client in mysap ERP.And you can specify the BW client in table.
RSADMINA-->BWMANDT
if you work as a sales man ,you just can say" There is BW in mySAP ERP."

Direct Delta, Queued and Unseralized V3

HI
FOR IM datasources, BF and UM, the guide mentions Direct Delta as the preferred selection. How do we decide this?
Also for LO cockpit DS in SD, what selection is chosen?
Thanks
Harie

hi Harie,
take a look oss note 505700 -LBWE: New update methods as of PI 2002.1 and 500426 - BW extraction SD: alternatives to V3 updating
hope this helps.
505700
Symptom
Up to and including PI 2001.2 or PI-A 2001.2, only the "Serialized V3 update" update method was used for all applications of the logistics extract structures Customizing Cockpit. As a result of the new plug-in, three new update methods are now also available for each application.
The "Serialized V3 update" update method is no longer offered as of PI 2003.1 or PI-A 2003.1. Between installing PI 2002.1 or PI-A 2002.1 and installing PI 2003.1 or PI-A 2003.1, you should therefore switch to one of these new methods in all applications offering alternative update methods.
Rather than describing an error, this note helps you make the right selection of update methods for the applications relating to the logistics extract structures Customizing Cockpit.
Read this note carefully and in particular, refer to the essential notes required for some applications when using the new update methods.
You will also find more detailed information on the SAP Service Marketplace at: http://service.sap.com/~sapidb/011000358700005772172002
Or:
http://service.sap.com/BW > SAP BW InfoIndex > Delta Handling > New Update Methods in Logistics Extraction with PI2002.1 2.0x/3.0x (ppt)
Other terms
V3 update, V3, serialization, TMCEXUPD
Reason and Prerequisites
New design
Solution
1. Why should I no longer use the "Serialized V3 update" as of PI 2002.1 or PI-A 2002.1?
The following restrictions and problems with the "serialized V3 update" resulted in alternative update methods being provided with the new plug-in and the "serialized V3 update" update method no longer being provided with an offset of 2 plug-in releases.
a) If, in an R/3 System, several users who are logged on in different languages enter documents in an application, the V3 collective run only ever processes the update entries for one language during a process call. Subsequently, a process call is automatically started for the update entries from the documents that were entered in the next language. During the serialized V3 update, only update entries that were generated in direct chronological order and with the same logon language can therefore be processed. If the language in the sequence of the update entries changes, the V3 collective update process is terminated and then restarted with the new language.
For every restart, the VBHDR update table is read sequentially on the database. If the update tables contain a very high number of entries, it may require so much time to process the update data that more new update records are simultaneously generated than the number of records being processed.
b) The serialized V3 update can only guarantee the correct sequence of extraction data in a document if the document has not been changed twice in one second.
c) Furthermore, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if the times have been synchronized exactly on all system instances, since the time of the update record (which is determined using the locale time of the application server) is used in sorting the update data.
d) In addition, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if an error did not occur beforehand in the U2 update, since the V3 update only processes update data, for which the U2 update is successfully processed.
2. New "direct delta" update method:
With this update mode, extraction data is transferred directly to the BW delta queues every time a document is posted. In this way, each document posted with delta extraction is converted to exactly one LUW in the related BW delta queues.
If you are using this method, there is no need to schedule a job at regular intervals to transfer the data to the BW delta queues. On the other hand, the number of LUWs per DataSource increases significantly in the BW delta queues because the deltas of many documents are not summarized into one LUW in the BW delta queues as was previously the case for the V3 update.
If you are using this update mode, note that you cannot post any documents during delta initialization in an application from the start of the recompilation run in the OLTP until all delta init requests have been successfully updated successfully in BW. Otherwise, data from documents posted in the meantime is irretrievably lost.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) A maximum of 10,000 document changes (creating, changing or deleting documents) are accrued between two delta extractions for the application in question. A (considerably) larger number of LUWs in the BW delta queue can result in terminations during extraction.
b) With a future delta initialization, you can ensure that no documents are posted from the start of the recompilation run in R/3 until all delta-init requests have been successfully posted. This applies particularly if, for example, you want to include more organizational units such as another plant or sales organization in the extraction. Stopping the posting of documents always applies to the entire client.
3. The new "queued delta" update method:
With this update mode, the extraction data for the affected application is compiled in an extraction queue (instead of in the update data) and can be transferred to the BW delta queues by an update collective run, as previously executed during the V3 update.
Up to 10,000 delta extractions of documents to an LUW in the BW delta queues are cumulated in this way per DataSource, depending on the application.
If you use this method, it is also necessary to schedule a job to regularly transfer the data to the BW delta queues ("update collective run"). However, you should note that reports delivered using the logistics extract structures Customizing cockpit are used during this scheduling. There is no point in scheduling with the RSM13005 report for this update method since this report only processes V3 update entries. The simplest way to perform scheduling is via the "Job control" function in the logistics extract structures Customizing Cockpit. We recommend that you schedule the job hourly during normal operation - that is, after successful delta initialization.
In the case of a delta initialization, the document postings of the affected application can be included again after successful execution of the recompilation run in the OLTP, provided that you make sure that the update collective run is not started before all delta Init requests have been successfully updated in the BW.
In the posting-free phase during the recompilation run in OLTP, you should execute the update collective run once (as before) to make sure that there are no old delta extraction data remaining in the extraction queues when you resume posting of documents.
If you want to use the functions of the logistics extract structures Customizing cockpit to make changes to the extract structures of an application (for which you selected this update method), you should make absolutely sure that there is no data in the extraction queue before executing these changes in the affected systems. This applies in particular to the transfer of changes to a production system. You can perform a check when the V3 update is already in use in the respective target system using the RMCSBWCC check report.
In the following cases, the extraction queues should never contain any data:
- Importing an R/3 Support Package
- Performing an R/3 upgrade
- Importing a plug-in Support Packages
- Executing a plug-in upgrade
For an overview of the data of all extraction queues of the logistics extract structures Customizing Cockpit, use transaction LBWQ. You may also obtain this overview via the "Log queue overview" function in the logistics extract structures Customizing cockpit. Only the extraction queues that currently contain extraction data are displayed in this case.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) More than 10,000 document changes (creating, changing or deleting a documents) are performed each day for the application in question.
b) In future delta initializations, you must reduce the posting-free phase to executing the recompilation run in R/3. The document postings should be included again when the delta Init requests are posted in BW. Of course, the conditions described above for the update collective run must be taken into account.
4. The new "unserialized V3 update" update method:
With this update mode, the extraction data of the application in question continues to be written to the update tables using a V3 update module and is retained there until the data is read and processed by a collective update run.
However, unlike the current default values (serialized V3 update), the data is read in the update collective run (without taking the sequence from the update tables into account) and then transferred to the BW delta queues.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method since serialized data transfer is never the aim of this update method. However, you should note the following limitation of this update method:
The extraction data of a document posting, where update terminations occurred in the V2 update, can only be processed by the V3 update when the V2 update has been successfully posted.
This update method is recommended for the following general criteria:
a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.
5. Other essential points to consider:
a) If you want to select a new update method in application 02 (Purchasing), it is IMPERATIVE that you implement note 500736. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBV302 report.
b) If you want to select a new update method in application 03 (Inventory Management), it is IMPERATIVE that you implement note 486784. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV303 report.
c) If you want to select a new update method in application 04 (Production Planning and Control), it is IMPERATIVE that you implement note 491382. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV304 report.
d) If you want to select a new update method in application 45 (Agency Business), it is IMPERATIVE that you implement note 507357. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV345 report.
e) If you want to change the update method of an application to "queued delta", we urgently recommended that you install the latest qRFC version. In this case, you must refer to note 438015.
f) If you use the new selection function in the logistics extract structures Customizing Cockpit in an application to change from the "Serialized V3" update method to the "direct delta" or "queued delta", you must make sure that there are no pending V3 updates for the applications concerned before importing the relevant correction in all affected systems. To check this, use transaction SA38 to run the RMCSBWCC report with one of the following extract structures in the relevant systems:
    Application 02:   MC02M_0HDR
    Application 03:   MC03BF0
    Application 04:   MC04PE0ARB
    Application 05:   MC05Q00ACT
    Application 08:   MC08TR0FKP
    Application 11:   MC11VA0HDR
    Application 12:   MC12VC0HDR
    Application 13:   MC13VD0HDR
    Application 17:   MC17I00ACT
    Application 18:   MC18I00ACT
    Application 40:   MC40RP0REV
    Application 43:   MC43RK0CAS
    Application 44:   MC44RB0REC
    Application 45:   MC45W_0HDR.
You can switch the update method if this report does return any information on open V3 updates. Of course, you must not post any documents in the affected application after checking with the report and until you import the relevant Customizing request. This procedure applies in particular to importing the relevant Customizing request into a production system.
Otherwise, the pending V3 updates are no longer processed. This processing is still feasible even after you import the Customizing request using the RSM13005 report. However, in this case, you can be sure that the serialization of data in the BW delta queues has not been preserved.
g) Early delta initialization in the logistics extraction:
As of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the delta initialization for selected DataSources.
Only the DataSources of applications 11, 12 and 13 support this procedure in the logistics extraction for PI 2002.1.
The early delta initialization is used to admit document postings in the OLTP system as early as possible during the initialization procedure. If an early delta initialization InfoPackage was started in BW, data may be written immediately to the delta queue of the central delta management.
When you use the "direct delta" update method in the logistics extraction, you do not have to wait for the successful conclusion of all delta Init requests in order to readmit document postings in the OLTP if you are using an early delta initialization.
When you use the "queued delta" update method, early delta initialization is essentially of no advantage because here, as with conventional initialization procedures, you can readmit document postings after successfully filling the setup tables, provided that you ensure that no data is transferred from the extraction queue to the delta queue, that is, an update collective run is not triggered until all of the delta init requests have been successfully posted.
Regardless of the initialization procedure or update method selected, it is nevertheless necessary to stop any document postings for the affected application during a recompilation run in the OLTP (filling the setup tables).
500426
Symptom
With the BW extraction with the structures of the logistics extract structures customizing cockpit there is only V3 updating as an update method up to plug-in release PI-2001.2.
To make every possible effort to ensure the transfer of document postings to BW in the correct sequence the parameter "SERIAL" was added to the V3 collective update (refer also to note 385099). If this parameter is set at the start of the V3 collective update, the update data is read and processed by the database in the sequence of its creation time.
However, this procedure gives rise to the following major performance problem:
If documents are entered in an application in an R/3 System by several users that are logged on in different languages, the V3 collective run will only ever process the update entries for one language in a process call. A process call is then started automatically for the update entries of the documents which were entered in the next language. Accordingly, during the serialized V3 update only update entries which were generated in direct chronological sequence and with the same logon language can ever be processed. If the language changes in the sequence of the update entries, the V3 collective update process is terminated and restarted with the new language.
During every restart, the update table VBHDR is read sequentially on the database. If there are very many entries in the update tables, this can cause the processing of the update data taking so much time that more new update records are generated simultaneously than are processed.
Furthermore, the serialization is not 100% guaranteed in all scenarios when the V3 update is used, as described also in note 384211.
From plug-in PI 2002.1 the option is offered for the most important applications of the logistics extract structures customizing cockpit of selecting between several alternative update methods.
The serialized V3 update is no longer provided from plug-in PI-2003.1.
The modification provided here enables you to use the new update methods for the applications 11, 12 and 13 as early as from patch 5 of PI 2001.2 or PI-A 2001.2.
The following update methods are offered:
direct delta (update mode A):
With this update mode the extraction data is transferred directly into the BW delta queues with every document posting. Every document posting with delta extraction becomes exactly one LUW in the corresponding BW delta queues.
If you use this method it is therefore no longer necessary to regularly schedule a job to transfer the data to the BW delta queues. Otherwise there will be a substantial increase in the number of LUWs per DataSource in the BW delta queues since, unlike previously, with V3 updating the deltas of many documents are grouped together to form an LUW in the BW delta queues.
Furthermore you should note when using this update mode that during delta initialization in an application, from the start of the recompilation run in the OLTP no document postings may be made until all delta Init requests have been updated successfully in BW. Otherwise data in documents posted in the interim will be irretrievably lost.
queued delta (Update mode B):
With this update mode the extraction data of the affected application is collected in an 'extraction queue' instead of in the update dataand can be transferred via an update collective run into the BW delta queues, as is already the case during V3 updating.
For each DataSource,1000 delta extractions are summarized by documents of the application to form an LUW in the BW delta queues.
If you are using this method it is thus also necessary to regularly schedule a job for transferring the data to the BW delta queues. This scheduling is carried out with the same report which is used when you use the V3 updating (RMBWV311, RMBWV312 or RMBWV313). You are recommended to schedule the job on an hourly basis in normal operation - that is following the successful delta initialization.
In the case of a delta initialization the document postings of the affected application can be included again after the successful execution of the recompilation run in the OLTP (OLI7BW, OLI8BW or OLI9BW) if you ensure that the update collective run is not started before all delta Init requests are updated successfully in BW.
In the posting-free phase during the recompilation run in the OLTP - as previously - the update collective run should be be run once successfully to ensure that there is no old delta extraction data in the extraction queues during the reinsertion of the document posting.
Using transaction SMQ1 and the queue names MCEX11, MCEX12 or MCEX13 you can get an overview of the data in the extraction queues.
unserialized V3 update (update mode C):
With this update mode the extraction data of the affected application is written to the update tables as before with the aid of a V3 update module and kept there until the data is read and processed by an update collective run.
However, unlike the current default values (serialized V3 update), in the update collective run the data is read and transferred to the BW delta queues without taking into account the sequence from the update tables. This is why the performance problem described above does not arise in this case.
This method should only be used if, due to the design of the cubes or ODS objects in the BW system, it does not matter whether the data is transferred to BW in exactly the same sequence in which it was generated in the OLTP System.
Other terms
V3 update
Reason and Prerequisites
Additional desired functions.
Solution
If you already want to use one of the above-described new update methods in the applications 11, 12 or 13 with PI 2001.2 or PI-A 2001.2, you can do this with the corrections given here. However, it is vital that you bear in mind the following points:
1. The corrections described here consist ofa modification which is not included in any PI Support Package. Check whether the described corrections are necessary. When you import a PI Support Package, parts of these corrections may be overwritten. When importing the PI Support Package ensure that you have got all of these corrections (SPAM/SPAU).
2. Only copy these modifications in consultation with SAP logistics extraction development.
3. The corrections presented here should only ever be regarded as an interim solution. The functions are only fully available with PI 2002.1 and PI-A 2002.1. You should also consider the option of upgrading soon to PI 2002.1 or PI-A 2002.1.
Note also that if the update methods of the applications 11, 12 and 13 are changed prematurely, other applications can still only offer the serialized V3 update. The performance problem described above continues to apply to these applications. It should, however, be significantly reduced by the absence of the modules of applications 11, 12 and 13.
4. The corrections described here necessitate the importing of Support Package 5 of PI 2001.2 or PI-A 2001.2. The corrections described here are not possible in a lower plug-in release or Support Package status since the functions of the new update methods are not available.
5. If you want to change the update method of an application to "queued delta", you are strongly recommended to first install the most current qRFC version. Refer to note 438015.
6. If you use the corrections below to change from the update method "Serialized V3" to "Direct delta" or "queued delta" in an application, you must ensure that before the corresponding corrections are imported there are no more open V3 updates for the corresponding applications in all affected systems. To check this, you can execute the report RMCSBWCC in the corresponding systems with transaction SA38 with one of the following extract structures:
    Application 11:   MC11VA0HDR
    Application 12:   MC12VC0HDR
    Application 13:   MC13VD0HDR.
The change is possible if you are not referred to open V3 updates. Of course, no document postings should be made in the affected application after the check with the report until the transfer of the corrections. This procedure applies in particular to the importing of the corrections into a production system.
7. If you are already using the update mode "queued delta" with one of the applications 11, 12 or 13 with the corrections stored here before PI 2002.1 and if you want to make changes to the extract structures in this phase via the cockpit, you should ensure that there is no data in the extraction queues before you execute these changes in the affected systems. In particular this applies to the transportation of changes into a production system. In this case it is not sufficient to execute the check report RMCSBWCC recommended in the cockpit and to eliminate the problem areas specified there.
Below we describe how you can check and ensure this condition.
8. When you import PI 2002.1 the changes made here will always be ineffective and you will get the update method "serialized V3" again as the preset update method.
If you have already changed to a different update method in advance in one of the applications 11, 12 or 13 via the corrections stored here, you must consider the following points during the plug-in upgrade to PI 2002.1 or PI-A 2002.1:
a) Before the upgrade you must ensure that there is no more data in the extraction queues MCEX11, MCEX12 and MCEX13. Otherwise it may no longer be possible to process the data, which may have to be deleted from the queues, due to an extract structure enhancement with the new plug-in. You can do this by starting the collective update report (RMBWV311, RMBWV312 or RMBWV313) and by subsequently checking the extraction queues using transaction SMQ1.
b) After the upgrade you must ensure that before the inclusion of new document postings, the update method of the corresponding application used in advance by the corrections specified here is also set in the cockpit of the logistics extraction (LBWE), and that this setting is transported into all clients of the affected systems.
Note in this context that the corrections specified here change the update method so that it is client-independent. The new functions in the cockpit of the logistics extraction from PI 2002.1 or PI-A 2002.1 then allow the client-specific selection of the update methods.
9. If you want to use the update method "direct delta" in application 11 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000373868" given below for the include MCEX11TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
10. If you want to use the update method "direct delta" in application 12 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000373868" given below for the include MCEX12TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
11. If you want to use the update method "direct delta" in application 13 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000373868" given below for the include MCEX13TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
12. If you want to use the update method "queued delta" in application 11 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380083" given below for the include MCEX11TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
13. If you want to use the update method "queued delta" in application 12 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380083" given below for the include MCEX12TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
14. If you want to use the update method "queued delta" in application 13 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380083" given below for the include MCEX13TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
15. If you want to use the update method "unserialized V3 update" in application 11 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380084" given below for the include MCEX11TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
16. If you want to use the update method "unserialized V3 update" in application 12 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380084" given below for the include MCEX12TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
17. If you want to use the update method "unserialized V3 update" in application 13 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380084" given below for the include MCEX13TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).

Queued Vs Unserialized V3 Update.

Hi BW experts,
I am not clear about the difference between Queued delta and Unserialized V3 Update.And what are the disadvantages of V3 Update.
Thanks in Advance.
Thanks,
Jelina.

Hi ,
The new "queued delta" update method:
With this update mode, the extraction data for the affected application is compiled in an extraction queue (instead of in the update data) and can be transferred to the BW delta queues by an update collective run, as previously executed during the V3 update. Up to 10,000 delta extractions of documents to an LUW in the BW delta queues are cumulated in this way per DataSource, depending on the application.
If you use this method, it is also necessary to schedule a job to regularly transfer the data to the BW delta queues ("update collective run"). However, you should note that reports delivered using the logistics extract structures Customizing cockpit are used during this scheduling. There is no point in scheduling with the RSM13005 report for this update method since this report only processes V3 update entries. The simplest way to perform scheduling is via the "Job control" function in the logistics extract structures Customizing Cockpit. We recommend that you schedule the job hourly during normal operation - that is, after successful delta initialization.
In the case of a delta initialization, the document postings of the affected application can be included again after successful execution of the recompilation run in the OLTP, provided that you make sure that the update collective run is not started before all delta Init requests have been successfully updated in the BW.
In the posting-free phase during the recompilation run in OLTP, you should execute the update collective run once (as before) to make sure that there are no old delta extraction data remaining in the extraction queues when you resume posting of documents.
If you want to use the functions of the logistics extract structures Customizing cockpit to make changes to the extract structures of an application (for which you selected this update method), you should make absolutely sure that there is no data in the extraction queue before executing these changes in the affected systems. This applies in particular to the transfer of changes to a production system. You can perform a check when the V3 update is already in use in the
respective target system using the RMCSBWCC check report.
The new "unserialized V3 update" update method:
With this update mode, the extraction data of the application in question continues to be written to the update tables using a V3 update module and is retained there until the data is read and processed by a collective update run.
However, unlike the current default values (serialized V3 update), he data is read in the update collective run (without taking the sequence from the update tables into account) and then transferred to the BW delta queues.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method since serialized data transfer is never the aim of this update method. However, you should note the following limitation of this update method:
The extraction data of a document posting, where update terminations occurred in the V2 update, can only be processed by the V3 update when the V2 update has been successfully posted.
This update method is recommended for the following general criteria:
a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.

Quary wiht restricted kf problem

Similar Messages

Maybe you are looking for