Re: Info set and query transport under same request number

Hi,
I would like to know the details about info set and query transport from development to quality using SAP Query: Trnasport tool.my quesion is,
Can i create all info sets and related queries under same request number or will it be created in diffrent request numbers?Please respond any body to my question.
Regards,
Suresh Kumar.

No it is possible as per SAP.
Please read follwoing help-
http://help.sap.com/saphelp_nw70/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
It is talking abou the Special Features of InfoCubes in InfoSets.
For queries based on an InfoSet with an InfoCube, the system decides at runtime whether aggregates can be used for the InfoCube. This is the case if all the required InfoObjects of the InfoCube exist in an aggregate. The following InfoObjects are required:
The key figures of the InfoCube selected in the query
The characteristics of the InfoCube selected in the query
The characteristics required for a join with other InfoProviders in the InfoSet.
Furthermore, as a prerequisite for using aggregates, all the data required by an InfoCube must be readable using logical access. For an InfoCube within an InfoSet with InfoCubes, it is no longer possible to read part of the data from one aggregate and part of the data from another aggregate or the InfoCube itself.

Similar Messages

Re:User group,info set and Query combination table

Hi,
I would like to know the combination table of User group,info set and Query.
Can any body please respond to my question?
Regards,
Suresh Kumar.

Hi,
Check the tables starting with AQG*.
Reward points if useful.
Regards,
Atish

Info set and multiprovider

hi friends
i know what is info set and multiprovieder but can any one give me a good senerio for each one . how you have used the info set and multi provider in you project with good example?
thanks in advance .

Hi Sridhar,
Multiproviders help you to do UNION between two infoproviders, while Infosets do INTERSECTION.
Supose that you have two infoproviders with the same (or almost the same) structure and you want to show all in the same report.
InfoProvider A
Material; Quantity
0001; 9.00
0002; 8.50
InfoProvider B
Material; Amount;
0001; 230,000.00
0002; 350,130.00
Now, the union (Multiprovider) of A and B.
Material; Quantity; Amount
0001; 9.00; 00.00
0002; 8.50; 00.00
0001; 0.00; 230,000.00
0002; 0.00; 350,130.00
And the intersection (InfoSet) of A and B.
Material; Quantity; Amount
0001; 9.00; 230,000.00
0002; 8.50; 350,130.00
In this last one, you have to define the key field (or fields) that will make the relationship, in this case is the material number.
In this example, we can get almost the same results with the Multiprovider and the Infoset, if you put the first example (union) in a report by material number, you will get the totals like the second one (intersection), but that is because the simplicity of this example and the fact that fields that are not provided (Amount in A, and Quantity in B) are set to 0. There will be cases in which you'll need to go with one or the other.
Hope it helps.
Daniel

I have an I phone and I pad under same Apple ID, I want to stop exchange of data between both how?

I have an I phone and I pad under same Apple ID, I want to stop exchange of data between both how?

And in settings/iTunes & App Store you need to turn off auto download

Error message when checking Aggregates on Info-set based Query

Hi All,
I have an Info-set (Inner-join between Info-cube and DSO) based Query. When I checking whethere it is picking up the aggregates (which is created on Info-cube) or not in RSRT, it is giving me following message -
I>> Row: 23 Inc: SHOW_AGGR_COMPARISON Prog: CL_RSDDK_AGGREGATE_COLLECTION
RS_EXCEPTION
301CL_RSDDK_AGGREGATE_COLLECTION
SHOW_AGGR_COMPARISON
I have checked fully that whatever fields I am using in my Query are available in Info-cube's Aggregate.
Even when I am running same query (which I have created on same Info-cube direclty) in RSRT, it is picking up the aggregates.
I have put the Request status 'Rolled up data (Rollup)' in Info-cube in Info-set as well.
Please guide me what I need to do for picking up the aggregates.
Regards,
Dheeraj Kumar Garg

No it is possible as per SAP.
Please read follwoing help-
http://help.sap.com/saphelp_nw70/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
It is talking abou the Special Features of InfoCubes in InfoSets.
For queries based on an InfoSet with an InfoCube, the system decides at runtime whether aggregates can be used for the InfoCube. This is the case if all the required InfoObjects of the InfoCube exist in an aggregate. The following InfoObjects are required:
The key figures of the InfoCube selected in the query
The characteristics of the InfoCube selected in the query
The characteristics required for a join with other InfoProviders in the InfoSet.
Furthermore, as a prerequisite for using aggregates, all the data required by an InfoCube must be readable using logical access. For an InfoCube within an InfoSet with InfoCubes, it is no longer possible to read part of the data from one aggregate and part of the data from another aggregate or the InfoCube itself.

How can we access the cookie set by cfheader in the same request?

I've set a cookie in my application.cfm using cfheader and in the same request i need to access the cookie. How can i do this?

Unless you know the values you're setting in the cookie explicitly then I don't know if you can - not sure if it's one of those things whereby a cookie doesn't exist until it's hit their browser, and if you page hasn't finished rendering then it hasn't hit their browser.
I'd suspect you'll try it and either it'll work or it won't.
If you're setting the cookie explicitly with you own UUID's or similar you will of course know what you'll be setting it to.
If that made any sense.
Which I'm pretty sure it didn't.
O.

Automotive diagnostic command set and periodic messages on same can port - CVI

Hello everybody,
Is it possible, using Labwindows / CVI, to use NI AutomotiveDiagnostic Command Set to communicate with a MCU with KWP2000 protocol and simultaneously send periodic CAN messages on the SAME CAN interface (CAN0 or else ) and also using this port port to do some CCP communication ?
Thank for your support.

Hi,
I find myself also in this position. My current project only has LabVIEW 2009 and the ADCS from a few years back available to use.
We want to be able to:
- read in a CANDB file (.dbc) into the Channel API, to send general CAN messages (note you cannot use the Frame API to read in the dbc files unfortunately)
- using the same CAN interface, use the ADCS to perform diagnostics activities
Can you please elaborate on some of the hoops, and how long it might take? If its too much of a hack, a third CAN port might be the easier option.
Any light shed would be appreciated.
Christopher Farmer
Certified LabVIEW Architect
Certified TestStand Developer
http://wiredinsoftware.com.au

I have two iPhones and an iPad under same Apple ID. How can I change one of the iPhones to a separate id?

I have 2 iPhones & an iPad under 1 Apple ID. How can I change 1 of the iPhones to a separate account?

Sign out of the Apple ID on the device in question, making sure to disable the Find My iDevice feature.
Sign in with the new Apple ID.
If the intent is to sell the device, simply restore as new after disabling the Find My iDevice and signing out.

Is it possible to change an IDOC and save on the same IDOC number..?

Hi all,
I have an IDOC. When I processed the IDOC, it ended up with error status '51'. There was some problem with the data. So, I changed the data and reprocessed using the T-Code 'WE19' and it was processed successfully. When we reprocess the IDOC using 'WE19', it generates another IDOC number. But, the client is asking that, it should not generate another IDOC number. When we change the IDOC number, it should be saved under the same(ORIGINAL) IDOC number. Is it possible to change an IDOC and save under the same number..? Is there any transaction code to do so. Please give your valuable inputs.
Thanks in advance.
Thanks & regards,
Paddu.

Hi,
You can use the transaction WE09..to edit the IDOC data...
Then use the transaction BD87 to post the IDOC..
Thanks
Naren

Info set , info provider and info spoke

Hi gurus plz give me the difference in between info set and info provider and info spoke. and give me what are the prerequisites are needed to process infoset, infoprovider and info spoke?
Regards
Vidhu

InfoProvider
An InfoProvider is an object for which queries can be created or executed in BEx
Check this for more,
http://help.sap.com/saphelp_nw04/helpdata/en/4d/c3cd3a9ac2cc6ce10000000a114084/content.htm
Infoset:
An InfoSet is a special view of a dataset, such as logical database, table join, table, and sequential file, and is used by SAP Query as a source data. InfoSets determine the tables or fields in these tables that can be referenced by a report. In most cases, InfoSets are based on logical databases.
SAP Query includes a component for maintaining InfoSets. When you create an InfoSet, a DataSource in an application system is selected.
Navigating in a BW to an InfoSet Query, using one or more ODS objects or InfoObjects.You can also drill-through to BEx queries and InfoSet Queries from a second BW system, that isConnected as a data mart.
The InfoSet Query functions allow you to report using flat data tables (master data reporting).Choose InfoObjects or ODS objects as data sources. These can be connected using joins.You define the data sources in an InfoSet. An InfoSet can contain data from one or more tables that are connected to one another by key fields.The data sources specified in the InfoSet form the basis of the InfoSet Query.
Check the link for more,
http://help.sap.com/saphelp_nw2004s/helpdata/en/ad/2225391d4f000be10000000a114084/frameset.htm
InfoSpoke:
Info spoke is an open hub destination defines to which target the data is to be relayed.
Check this link for more,
http://help.sap.com/saphelp_nw2004s/helpdata/en/ad/2225391d4f000be10000000a114084/frameset.htm
Check this doc also,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/eb462104-0701-0010-07ae-d866630e0989
Hope this gives you a good idea...

My wife and I have both Iphone 5 and 5c. We have currently one icloud account and the bill is under one account number for both phones. We are not set up right. We want to be able to share only contacts, calendars, pictures, music. How do we do this.

My wife and I have iphone 5 and 5c. We want to only share contacts, calendar, music and photos. We currently have one iclud account and are billed under one customer number. How can we accomplish this?

Read http://macmost.com/setting-up-multiple-ios-devices-for-messages-and-facetime.htm l
If you wish to share an Apple ID with family members then read: http://www.macstories.net/stories/ios-5-icloud-tips-sharing-an-apple-id-with-you r-family/

ABAP Query Transport request related

Hi,
I have created a Abap query,
1) User group
2)Infoset
3) Query
But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the
Development
Please suggest, is this std behaviour or is anything missed
Rgds,
Jai

Thanks to all,
I just created TR with new package for user group and included ifoset and query in the same TR
and imported, issue is resolved
But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion
Short text
SAP Query: Transport tool
Description
The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.
General information
Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either
·     from a client (source client) of an SAP system to another client (target client) in the same SAP system or
·     from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).
In both cases, you have to perform similar actions.
The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.
If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.
If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.
The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).
This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.
As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).
Transport action EXPO (exports)
If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.
With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.
In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.
The import options, each of which has an abbreviated syntax,
are as follows:
REPLACE or R
MERGE    or M
GROUP=ug or G=ug    (ug = name of a user group)
UNASSIGN or U
If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.
If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.
If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.
This transport type allows you to transport a modified InfoSet and all the associated queries.
For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.
The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.
Transporting a user group
Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.
The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.
The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.
Entering a new member in a user group in the target client is possible only if a user master record exists.
In the target client, the assignment of InfoSets to this user group remains.
Transporting an InfoSet
Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.
Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.
The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.
The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.
The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.
The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.
Transporting a query
Transporting a query means only the query itself is transported.
Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.
The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.
The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.
Transport action IMPO (imports)
If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.
All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.
If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.
Transport action SHOW (display)
All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.
Transport action DELE (delete)
All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.
Transport of ABAP Query
I am involved in this upgrade project to 4.7
The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.
I remember a similar problem upgrading to 4.6C from 4.5B ......
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Just wanted to share my experience of transporting queries:
I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.
Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to 'new' system.
(This results in the entries being populated in transport table AQTDB in 'new' system).
Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.
(RSAQR3TR gives the message that stuff has been imported OK).
Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'.
(Now my queries etc were available in new system).
Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.
regards,
Jai

Can I use the same serial number for mac and pc?

My problem is that my mac is falling apart and I don't know how long it's still working - can be hours or can be months. I'm not sure if my next computer is mac or PC, so I'd like to know if the same serial number can be used with both mac and PC? I have understod that I can delete the program from my old computer and then use the same serial number in my next computer (Is it working that way?). So if I now buy a lisence for mac, can I use the same lisence later with PC?

Riisar for retail copies of the software you would need to complete the process detailed in Order an Adobe product platform swap or language swap.

Request number and Task number

Every Request number have hirerachy with Task Numbers,
Why SAP provdided 2 numbers like request number and task number...
Why we are not saving all the tasks under one Request number only...?why sap provided task number seperately..?
Please clear my doubt ,i am unable to find any forum related to this query in SDN..

You can refer :
http://help.sap.com/saphelp_nw70/helpdata/EN/7e/75ac89a9f811d2850d0000e8a57770/frameset.htm
Still copying the portion that gives your answer :
"The Transport Organizer helps you when you organize development projects by allowing you to distribute project work for individual developers or teams between different change requests. These change requests record all changes made to development objects and Customizing settings. Objects from the areas of Customizing and the ABAP Workbench are managed and recorded in separate requests. Special checks have been implemented for each of these applications.
Developments, corrections, and repairs are recorded in tasks and transported using change requests.
The target system and type of transport are assigned automatically and no longer need to be maintained by the user.
Several users can work together on a project by organizing their development work in tasks. These tasks belong to a common change request."
Thanks,
Amurta

Same Batch Number with different characteristics value

Dear Gurus,
I have the following scenerio:
The finished goods should be maintain in batch with external number and at the time of confirming the finished goods in co11n the client want to capture the finished goods value like length, width and diameter.
So we propose the batch characteristics with class type of 022 for finished good and we maintain the character as length, width and diameter under the batch class 022 and assign the batch class in finished good classification view.
Now the requirement is we want to capture the batch characteristics value length width and diameter with same batch number for multiple confirmation.
Example:
Confirmation      Batch number               batch Class               Length     width     Diameter
1                        1000                              022                              100        50             20
2                        1000                              022                              120        25             10
3                        1000                              022                              150        70             30
Now at present we are trying to capture the batch characteristics with same batch number but our standard system will not allow to maintain the different batch characteristics value under same batch number. If we overrite the batch characteristics in msc2n transaction the last value maintained be copied to all batch number. but we want same batch number with different batch characteristics value.
Please share your idea and try to solve..
Regards,
Vimal

Dear Vimal,
It is not possible to maintain multiple batch characteristics in one batch.
Work around is to create original batches and assign to your production order. During CO11N, generate one batch per confirmation. There is a report in batch information cockpit to link between original batch and batch per confirmation.
Rgrds,

Re: Info set and query transport under same request number

Similar Messages

Maybe you are looking for