Boundary of request IDs

Hello!
At the moment I have a special scenario in which we have to load data from one cube to another cube via DTP and a special selection option. In order to have only some small loading windows it is the need that we using a special date to split the data into different time slices. The problem ist that we need only data until a special request number. It is not possible to have request ID in the DTP. So my question is, if it is possible to exclude request IDs via ABAP routine in the DTP? I guess that ist should be possible to access the request ID, but at the moment I don't know how it works.
Example for scenario: Load all data with posting date 15.04.2014 but consider only request IDs until 20.04.2014. If there is any request who has a data record with posting date 15.04.2014 after 20.04.2014 then this recoord should exlcude from the loading procedure.
Is there anybody who has some expiriences with such a special scenario?
Thanx
Jens

Hello Jens
I could not understood your problem completely. What is this special request number? Is it the request ID of the source cube?
Are you looking for the option in the DTP to choose the Request ID ( Managescreen of the cube - 1st column)? In this case, it is possible to use this in the DTP Filter - DTP Request (SID).
Thanks and Regards,
Ningaraju

Similar Messages

Delete request Ids from Cube

Hello Experts,
We have 2 cubes (ZC_CB1, ZC_CB2). We are loading delta load to ZC_CB1. I need to move the specified period data from ZC_CB1 cube to ZC_CB2 cube and delete the specified period data from ZC_CB1 after finish the load. They don't want to use SELECTIVE DELETE to delete the data from ZC_CB1. Please let me know options to achieve the same.
Thank you
Regards,
Prasad

Selective deletion and deleting by request is the only way of deleting the data from the cube.
May I ask why they don't want to use a selective deletion?
You can also try to create a flatfile source system for this cube and load a reversal document to the cube.
thanks.
Wond

Request for Reverse Posting

Hi,
Request for Reverse Posting - can anyone explain me this in detail with example.
Regards,RAMU.

Hi Ramu,
In an Infocube we can delete data in three ways,
1) Entire Data deletion
2) Selective data deletion
3) Deletion based on request ID.
After compression of Infocube, request ids become zero and data gets aggregated and moves from F fact table to E fact table, so we can delete data only in two ways
1) Entire Data deletion
2) Selective data deletion.
But if it is required to delete data in Infocube after compression based on Request Id, we can go for Reverse Posting. We can reverse post the data only when we process the data through PSA.
If u reverse post the data for a compressed request, the data for the compressed request is taken from PSA multiplying with
-1 for the key figure values and loaded into the data target. Now the data in the data target is available in F table with negative key figure values. By Compression of Info Cube, data moves from F table to E table and nullifies the data in Infocube for the request ID.
Note: Since records with zero key fig values are of no use, to delete these records while compression check mark zero elimination option in collapse tab.
Hope It helps u
Cheers....
Sk Babu

Deletion of compressed request

Hi
I have two compressed in InfoCube
Req A - 200 records Timestamp 2008
Req B - 300 records Timestamp 2007
Now I want to delete the request "B" from the Cube which is beneath req A in the Cube.
I have already deleted the data for the Req B via selective delete, now the only thing I have been asked is to delete the request.
Can I delete the same via RSICCONT table and if so what is the Impact of the same.

Hi DPN,
Once u do the compression then the request idds will be deleted and the data will move from F table to E table, If u want to delete the compressed data then u have to do Request reverse posting for this you should have the data in PSA. If u do this all the in that request will be multiply with -1 and send to cube with new request, after that u have to do the compression so that + and - values will be cancelled.
I have already deleted the data for the Req B via selective delete, now the only thing I have been asked is to delete the request.
I dint understand this. Remember request ids will be deleted once u do compression.
Khaja

SharePoint system generated IDs are not synchronous

Hi,
We've published InfoPath forms in document library 'A' and used default "ID" field of SharePoint to generate Request IDs for tickets.
As we add consequent documents(items) in library 'A', 'ID' is getting incremented properly i.e. 801, 802, 803. But sometimes, consequetive IDs generated as 815, 820, 824 even if the items/documents between them are not deleted.
Can anyone help me for the reason behind this.
Thanks,
Kunal

Hello Kunal,
I am just thinking if this issue is related to multiple instances of form. Just try to add one more text field in form and populate item id on form load in that field. Then use this field in your rule instead of "max(i@d)+1".
Just try this and see the result
Hemendra:Yesterday is just a memory,Tomorrow we may never see Please remember to mark the replies as answers if they help and unmark them if they provide no help

Deleting Requests from ODS

I have a request REQU_42Y54WN5641WI37ZC04U19PS9 in ODS.
How to delete this request? how can I find that.
Thanks
SP

Hi
Go to Adminworkbench (RSA1)-> Infoproviders-> Right click on your ODS and click Manage. In the requests tab, you will find all the requests loaded into ODS with their request IDs. Find the request with request ID as REQU_42Y54WN5641WI37ZC04U19PS9 and delete it. But note that the requests which are activated after this particular request will also be deleted.Anyway when you delete this request, you will receive a message stating that the latest requests loaded after this particular request will also be deleted.
Hope this helps...let me know
Regards,
R.Ravi

I have request in the report level but the same is missing in the infocube

Dear Experts,
I have request in the report level but the same is missing in the compressed infocube level. What could be the cause? does the compressed infocube deletes the request ? if so, I could able to view other requests under infocube manage level.
Kindly provide with enough information.
Thanks.............

Hi
Compressing InfoCubes
Use
When you load data into the InfoCube, entire requests can be inserted at the same time. Each of these requests has its own request ID, which is included in the fact table in the packet dimension. This makes it possible to pay particular attention to individual requests. One advantage of the request ID concept is that you can subsequently delete complete requests from the InfoCube.
However, the request ID concept can also cause the same data record (all characteristics agree, with the exception of the request ID) to appear more than once in the fact table. This unnecessarily increases the volume of data, and reduces performance in reporting, as the system has to perform aggregation using the request ID every time you execute a query.
Using compressing, you can eliminate these disadvantages, and bring data from different requests together into one single request (request ID 0).
This function is critical, as the compressed data can no longer be deleted from the InfoCube using its request ID. You must be absolutely certain that the data loaded into the InfoCube is correct.
Features
You can choose request IDs and release them to be compressed. You can schedule the function immediately or in the background, and can schedule it with a process chain.
Compressing one request takes approx. 2.5 ms per data record.
With non-cumulative InfoCubes, compression has an additional effect on query performance. Also, the marker for non-cumulatives in non-cumulative InfoCubes is updated. This means that, on the whole, less data is read for a non-cumulative query, and the reply time is therefore reduced. See also Modeling of Non-Cumulatives with Non-Cumulative Key Figures.
If you run the compression for a non-cumulative InfoCube, the summarization time (including the time to update the markers) will be about 5 ms per data record.
If you are using an Oracle database as your BW database, you can also carry out a report using the relevant InfoCube in reporting while the compression is running. With other manufacturers databases, you will see a warning if you try to execute a query on an InfoCube while the compression is running. In this case you can execute the query once the compression has finished executing.
If you want to avoid the InfoCube containing entries whose key figures are zero values (in reverse posting for example) you can run a zero-elimination at the same time as the compression. In this case, the entries where all key figures are equal to 0 are deleted from the fact table.
Zero-elimination is permitted only for InfoCubes, where key figures with the aggregation behavior SUM appear exclusively. In particular, you are not permitted to run zero-elimination with non-cumulative values.
For non-cumulative InfoCubes, you can ensure that the non-cumulative marker is not updated by setting the indicator No Marker Updating. You have to use this option if you are loading historic non-cumulative value changes into an InfoCube after an initialization has already taken place with the current non-cumulative. Otherwise the results produced in the query will not be correct. For performance reasons, you should compress subsequent delta requests.
Edited by: Allu on Dec 20, 2007 3:26 PM

Load single Requests form a Infocube in antoher infocube

Hi all,
is there a possibility to load a selection of Request IDs from a infocube in another infocube?
Situation:
Cube X1 has requests 4711, 4712, 4713
Now i want to load request 4713 into infocube x2. How can i do this??
Thank you very much for your help, best regards
Frank

Go through this link
Restructuring InfoCubes :
http://help.sap.com/saphelp_bw31/helpdata/en/f2/99223803926e39e10000009b38f8cf/content.htm
Regards

Oracle in the Manager IDs

Concurrent > Manager > Administer > Standerd Manager > Processes
Under Concureent Processes
there are Manager IDs and Request IDs
What is Oracle in the Manager IDs? Is the database session id? but I am not able to find it. What's it?

Hi,
Concurrent Manager ID is CONCURRENT_PROCESS_ID (Concurrent process identifier) column in FND_CONCURRENT_PROCESSES table. This column is used to identify which concurrent manager processed a concurrent request (join it with FND_CONCURRENT_REQUESTS.CONTROLLING_MANAGER).
Oracle Process ID can be found in the same window (under Oracle column), and OS Process ID is the one under the System column.
Please refer to eTRM page for details.
Regards,
Hussein

Check infocube and verify that all request in there are reportable

hi all,
How can i verify that infocube that request are available in for reporting,,Is there any SAP or Z program/FM to find the solution.

hi Sajoy,
IF you go to the manage of cube, you will find an available for reporting sign in the infocube - whichever request has this is available for reporting.
Tables:
RSMDATASTATE SIDs are the same as the request no that you see (in request tab in 'manage'). Request IDs in the target can be checked in RSICCONT table.
The value in RSMDATASTATE tells the max value for which QM is ok, or, tech status is ok (as I understand it). This with RSICCONT table should tell us which all requests are there in the cube (that are available for reporting).
Hope this helps!
Sheen

Delta request compression twice

hi sdn,
can we double compress the same request i already compressed the requst but i'm not able to find out tik mark against that reqst but job is completed successfully can we compress it again
regards
rubane

All your job log says that compression finished. And you also checked that data has been successfully moved out of F table to E table.
I am assuming that you have refreshed your session properly.
Could you also try out the following things.
Go to Manage -> Environment -> Complete Check of request ID -> Click on 'Complete availability check of all request IDs in the info-cube'.
Go to transaction RSRV -> Perform few checks for Info-Cube
Let me know the findings.
Soumya

It is possible to delete the request after compression

Hi,
It is possible to delete the request after compression,if it yes,how can delete the request.

Hi,
You cannot delete the request individually but you can one of the following:
1. Do a selective deletion from the cube. RSA1 -> Cube -> Contents -> selective deletion.
2. Delete all the data in the cube and then reconstruct only the required request ids. This would work only if you have the PSA available for all the requests.
3. Reverse posting is another possibility.
Bye
Dinesh

What are the minimum and maximum numbers of a Concurrent Request ID

Hi,
Just wondering where the concurrent request IDs start e.g. 0,1, or 10000 and where they "tick over". E.g. is it at 9999999, 99999999 or higher.
I've got a feeling they start with four or five digits perhaps at 1000, but I haven't been able to uncover a direct reference in the manuals or on the Support site. I don't think the maximum size in the table FND_CONCURRENT_REQUESTS is the whole story but may be wrong.
Oh, I'm talking about an 11.5.10.2 instance in my case, but would be interested in the case for 12 too.
Regards,
John

jtowns wrote:
Hi,
Just wondering where the concurrent request IDs start e.g. 0,1, or 10000 and where they "tick over". E.g. is it at 9999999, 99999999 or higher.
I've got a feeling they start with four or five digits perhaps at 1000, but I haven't been able to uncover a direct reference in the manuals or on the Support site. I don't think the maximum size in the table FND_CONCURRENT_REQUESTS is the whole story but may be wrong.
Oh, I'm talking about an 11.5.10.2 instance in my case, but would be interested in the case for 12 too.
Regards,
JohnCheck the max value of FND_CONCURRENT_REQUESTS_S sequence -- In 11i/R12, it is 2000000000
Thanks,
Hussein

HELP: Customizing ESS Leave Request for multiple entries in one submission

Hi experts,
I appreciate help on this urgent problem. We're on ECC6 with EP7. My customization requirements are below:
1) Allow multiple leave entries to be submitted at one go. Standard ESS only allows one date range entry per submission. We've customized the Webdynpro Leave request form to allow multiple entries in table form.
Assuming there's 3 requests:
R1 ~ 01-Oct-2007
R2 ~ 03-Oct-2007
R3 ~ 05-Oct-2007
Whenever user clicks 'New Entry' button, Webdynpro will call bapi PT_ARQ_REQUEST_PREPARE to generate a new request ID.
When user clicks on 'Review' button, I will loop at the requests internal table and check each of the entries, which is an individual request, via BAPI PT_ARQ_REQUEST_CHECK. Am I doing correctly so far?
The checks return no error. Next comes the problem. When I click the 'Send' button, I will loop at the request IDs (in ascending order) into BAPI PT_ARQ_REQUEST_EXECUTE. I will get a dump, saying that the object cannot be found. Debugging shows that it cannot find the first request ID (R1) in the memory. I found that if I sort the request IDs in descending order, it will be able to find the last request (R3) and could process it. However, when it comes to the 2nd last request (R2), it will give me the same dump saying that object can't not found. Both R1 and R2 cannot be found whereas only R3 can be found.
In overview, the logic we adopted is like this:
1) PT_ARQ_REQUEST_PREPARE-CREATE (R1)
2) PT_ARQ_REQUEST_CHECK (R1) upon clicking 'New Entry' Button
3) PT_ARQ_REQUEST_PREPARE-CREATE (R2)
4) PT_ARQ_REQUEST_CHECK (R2) upon clicking 'New Entry' Button
5) PT_ARQ_REQUEST_PREPARE-CREATE (R3)
6) PT_ARQ_REQUEST_CHECK (R1, R2, R3) upon clicking 'Review' Button
7) Loop PT_ARQ_REQUEST_EXECUTE ( R3 - Returns OK, R2 - Returns object not found and terminates, R1 - not processed because execution terminated by R2).
Can anyone please advise me how I should go about changing the BAPIs? Or are the CLASSes/BADIs to be changed?
Points will be rewarded for helping with this urgent requirement. Thank you.
Regards,
Damien

Hi Kiran,
Thanks for replying. My guess initially was also that the requests are overwritten.
I heard of another company's implementation who did the same concept and was able to do it. Unfortunately, I'm unable to get any information from them.
Initially, my frontend programmer and I thought of adopting the 'dummy checks' methodology. i.e. Do dummy checks when clicking 'New entry' or 'Review' button. This is to ensure that the entries were entered correctly at front end. Only when the user clicks on the 'Send' button, my BAPIs take in a table of request entries and perform the Request_Prepare&Request_Check&Request_Execute one at a time.
This may be expensive as there will be double the processing needed. One set for dummy checks and one set for the actual backend processing.
Is there any way that I can create multiple requests in 'transcient' state so that it won't be overwritten and I can still find it when I call the BAPI PT_ARQ_PREPARE_EXECUTE? PT_ARQ_PREPARE_EXECUTE only takes in request IDs instead of request structures.
Thanks again, Kiran, for replying. Have a good weekend.
Regards,
Damien

Cube compression and request's id

Can we decompress compressed cube using the request id's?
What happens to the request id's when the cube gets compressed?
rgds

Hi Nitin,
when you load data into the InfoCube, entire requests can be inserted at the same time.
Each of these requests has its own request ID, which is included in the fact table in the packet dimension. This makes it possible to pay particular attention to individual requests. One advantage of the request ID concept is that you can subsequently delete complete requests from the InfoCube.
However, the request ID concept can also cause the same data record (all characteristics agree, with the exception of the request ID) to appear more than once in the fact table. This unnecessarily increases the volume of data, and reduces performance in Reporting, as the system has to aggregate using the request ID every time you execute a query.
Using compressing, you can eliminate these disadvantages, and bring data from different requests together into one single request (request ID 0).
This function is critical, as the compressed data can no longer be deleted from the InfoCube using its request IDs.
Hope now is clearer (and don't forget to assign some points by clickin'on the star to the contributors that helped you !!!)
Bye,
Roberto

Boundary of request IDs

Similar Messages

Maybe you are looking for