Problem in Query Transportation

Dear All,
We are transporting the query from 3.0B to BI 7. The BI 7 analyser is working fine with all the variables but in the fiscal year period it is giving the error. When we remove it from the query designer BI 7 and including the optional variable it is working fine, but when we include the compulsary variable it is giving the same error.
Program error in class SAPMSSY1 UNCAUGHT_ERROR
Variable contains invalid value
Specify a value for variable fiscal yer period(Interval, required)
We have checked this compulsary variables by creating the new query but still it is not working. We are suspecting that there is the problem with this variable only.
Pls give us some suggestion
Points will be rewarded.
Thanks
Sathya

Hi,
Please check if there is no hard filter on 0FISCVARNT. 0FISCPER and 0FISCYEAR are connected to 0FISCVARNT, these two are only clearly defined when a value has been set for 0FISCVARNT.Read note 141842.
Rgds
Manoj Kumar

Similar Messages

Problems with query transport (missing object)

Hello,
I've a problem while transporting a query with the transport connection. I choose the option "necessary objects" but the import in the productive system fails due to a missing object.
How can I find the missing object? In the transport log only the ID is given (e.g. " Element 67ZP0WYO09DFA52PLG2SREVBT is missing in version M")
Thanks in advance,
Markus

Hi Markus,
Check data base tables RSZELTXREF & RSZELTTXT for the missing element in the transport.
Try to include all the missing elements of a Query in a new transport and try again.
Hope this will help.
Praveen

Query Transportation Problem?

Hi Guru's,
We are working in Bw 3.5 Version
Query: We have observed that there was a problem with Query in Dev & Quality Server?
as per the regular activities we have modeled the entire process in Dev
from data Source to Data target
then we have developed a report on this data target.
all this was saved under one Request and transported to Quality.
then there was some modifications in update rules & and also in Bex report
for this also we have sent under one request to Quality
there we have observed that the modifications in update rules have been applied
& in report this modifications did nnot apply in Quality server
Can any one help in this ............
advance thanks ,very very urgent..
Points will be rewarded >
Hari

Hi,
I have the same problem. I have a query in production and I need to change it. I changed it in dev, transported the query with no error, but I don't see the changes in prod.
There is any configuration error? Normal transports work fine.
Thanks

Problems with query while transporting

Dear all,
I have transported some queries from the development system to the production system. The transportation ended with the following warnings:
Execute reports for change/transport request: DBWK900095
on the application server: kblbw
There are no reports to execute
Execution of programs after import (XPRA)
End date and time : 20060716141213
Ended with return code: ===> 4 <===
I can see the queries in the BW PRD system but when I run them, they ask for login to DEV system and fetch the data from DEV system itself. Even though the query is physically inside PRD system it is running on the DEV system. I'll be very grateful if someone can give me some inputs in solving this problem. Thanks a lot.
Regards,
Sumit

Dear Sumit,
Kindly check this link. will help you a lot..
Query Transportation
assign points if useful ***
Thanks,
Raj

Problem in query help me

hi
i m having problem in query please help me
here data is not coming
SELECT HBKID FROM PAYR INTO CORRESPONDING FIELDS OF TABLE INT_PAYR WHERE
ZBUKR = P_BUKRS
AND UBHKT IN (P_OHKONT).
loop at int_payr.
OUT_HBKID = int_payr-W_hbkid .
MODIFY INT_PAYR.
endloop.
give me advice.
thanks .

This example will help you ...
data: begin of i_mara occurs 0,
            matnr like mara-matnr,
            maktx like makt-maktx,
      end of i_mara.
data: wa_maktx type maktx.
select matnr into table i_mara from mara where matnr =
'000000000000000001'.
   select maktx into wa_maktx from makt
   for all entries in i_mara where matnr = i_mara-matnr.
   endselect.
   loop at i_mara.
      i_mara-maktx = wa_maktx.
      modify i_mara transporting maktx .
   endloop.
Regards,
Jayant
Please award if helpful

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

ABAP Query Transport

Dear All,
we want transport ABAP Queries from one SAP instance to another..these ABAP Queries under Global area (cross client).
please suggest me how to create a transport request to transport these old queries , one more thing is all standard area (client specific) queries are copied .
Regards,
Gopala.S

Check this link:
ABAP Query Transport request related
ABAP Query transport problem
Creating t.code for ABAP query and Transport it TO Production and run it .
Edited by: Afshad Irani on Jul 20, 2010 12:30 PM

Ugent issuedata erased in othe query due to some other query transportation

hi all,
today i transported some queries,the end user is reporting that data is erased in other queries,is it due to the problem of todays transported queries or that individual queries.how data is lossed in transported queries.urgent issue kindly reply asap.iam waiting for your reply
thanksin adavance

first make sure did you transport the query that the user is complaining? if so make sure what are the additional changes you have done for that particular queries ...
try to cross check them with the queries that are there in the production with your queries in the dev..

Problem loading Query Designer Add-in

Hi All,
Can anyone please help me on my below issue.
Whenever user is trying to start a new query in Essbase , he is getting below error message. It will not allow user to build a fresh Essbase pull
Problem loading Query Designer Add-in. Workbook Activate,open & close operations may not be fully propogated
Thanks in advance.
Regards
Vishal

Hi Vishal,
1) Try to remove the addin and then add again.(Before doing this close all the excel process from the task Manager)
2) Check weather essexcln.xll and essxleqd.xla are corrupted.

View with columns based on function - problem with query

Hi,
I'm using Oracle 9i;
I've created a view which has columns based on a table columns (multiple columns from 1 table) and funtion (multiple columns based on 1 function).
The function takes ID as the first argument and name of the column to determine which value to return as the second one.
Here is a sample of such function (simplified):
FUNCTION my_function
(in_id IN NUMBER, in_col_name IN VARCHAR2)
RETURN VARCHAR2
IS
c_name VARCHAR2(100);
c_last_name VARCHAR2(100);
BEGIN
SELECT T.NAME, T.LAST_NAME
INTO c_name, c_last_name
FROM TABLE_1 T, TABLE_2 Z
WHERE T.PK = Z.FK
AND Z.ID = in_id;
IF in_col_name = 'NAME' THEN
RETURN c_name;
ELSIF in_col_name = 'LAST_NAME' THEN
RETURN c_last_name;
END IF;
END;
For simplicty I've restricted the number of columns.
CREATE OR REPLACE VIEW my_view
(ID, NAME, LAST_NAME)
AS
SELECT
T.ID ID
,CAST(my_function(T.ID,'NAME') AS VARCHAR2(100)) NAME
,CAST(my_function(T.ID,'LAST_NAME') AS VARCHAR2(100)) LAST_NAME
FROM TABLE T;
There is no problem with query:
SELECT * FROM my_view;
The problem arises when I query the view (regardles of '=' or 'LIKE'):
SELECT * FROM my_view
WHERE name LIKE '%some_part_of_name%'
The query returns rows for same names, for same it doesn't. If I put '=' and the whole name the query returns nothing, but when I put 'LIKE' and the first letter it returns rows in some cases.
I've tried to debug this situation and I've discovered that the function recives ID not in the proper order and not the same amount of times - in explicit:
for each ID in (1, 2, 3, 4, 5, 6, ... , 100) the function should be called twice for each ID and in the same order, but it does not.
I get 1, 1, 2, 3, 3, 6, 20, 20 and so on.
Help needed.
Greetings.

The problem is more complicated than the solutions provided here.
The reason why I'm using the function is this:
the original view was constructed using multiple union all selects and the speed was terrible. I've created the index on the base table to obtain a proper sort. For retriving all records at once the view works perfectly, but if one wants to query by columns based on function the results are suprisng - sometimes there are, some times there are none, or if you serch with "like" and only a part of string there are results, but with "=" there are no results.
Here are real DDLs:
View:
CREATE OR REPLACE VIEW V_DOK_ARCH
(ID_ZDAR, TYP, STAN, DATE_CREATED, CREATED_BY,
DATE_MODIFIED, MODIFIED_BY, SPRA_ID_SPRA, PODM_ID_PODM, PODM_UMOW_ID_UMOW,
NR_WFS, WFS_NR_INTER, UWAGI_OPER, FUNDUSZ, NUMER,
DATA_PODPISANIA, RODZAJ, TYP_PRZY, TYP_UBEZ, NAZWISKO,
IMIE, IMIE_OJCA, NAZWA_FIRMY, NAZWA_FIRMY_SKR, DANE_KLIE)
AS
SELECT /*+ INDEX(Z ZDAR_DATE_CREATED_DESC_I) */
Z.ID_ZDAR ID_ZDAR
, Z.TYP TYP
, Z.STAN STAN
, Z.DATE_CREATED DATE_CREATED
, Z.CREATED_BY CREATED_BY
, Z.DATE_MODIFIED DATE_MODIFIED
, Z.MODIFIED_BY MODIFIED_BY
, Z.SPRA_ID_SPRA SPRA_ID_SPRA
, Z.PODM_ID_PODM PODM_ID_PODM
, Z.PODM_UMOW_ID_UMOW PODM_UMOW_ID_UMOW
, Z.NR_WFS NR_WFS
, Z.WFS_NR_INTER WFS_NR_INTER
, Z.UWAGI_OPER UWAGI_OPER
, Z.FUNDUSZ FUNDUSZ
, CAST(F_Rej_Zdar_Char(Z.ID_ZDAR, 'NUMER') AS VARCHAR2(30)) NUMER
, F_Rej_Zdar_Date(Z.ID_ZDAR, 'DATA_PODPISANIA') DATA_PODPISANIA
, CAST(F_Rej_Zdar_Char(Z.ID_ZDAR, 'RODZAJ') AS VARCHAR2(4)) RODZAJ
, CAST(F_Rej_Zdar_Char(Z.ID_ZDAR, 'TYP_PRZY') AS VARCHAR2(4)) TYP_PRZY
, CAST(F_Rej_Zdar_Char(Z.ID_ZDAR, 'TYP_UBEZ') AS VARCHAR2(3)) TYP_UBEZ
, CAST(F_Rej_Zdar_Char(Z.ID_ZDAR, 'NAZWISKO') AS VARCHAR2(30)) NAZWISKO
, CAST(F_Rej_Zdar_Char(Z.ID_ZDAR, 'IMIE') AS VARCHAR2(30)) IMIE
, CAST(F_Rej_Zdar_Char(Z.ID_ZDAR, 'IMIE_OJCA') AS VARCHAR2(30)) IMIE_OJCA
, CAST(F_Rej_Zdar_Char(Z.ID_ZDAR, 'NAZWA_FIRMY') AS VARCHAR2(300)) NAZWA_FIRMY
, CAST(F_Rej_Zdar_Char(Z.ID_ZDAR, 'NAZWA_FIRMY_SKR') AS VARCHAR2(100)) NAZWA_FIRMY_SKR
, CAST(LTRIM(F_Rej_Zdar_Char(Z.ID_ZDAR, 'NAZWISKO')||' '||F_Rej_Zdar_Char(Z.ID_ZDAR, 'IMIE')||' '||F_Rej_Zdar_Char(Z.ID_ZDAR, 'IMIE_OJCA')||F_Rej_Zdar_Char(Z.ID_ZDAR, 'NAZWA_FIRMY')||DECODE(F_Rej_Zdar_Char(Z.ID_ZDAR, 'NAZWA_FIRMY'),NULL,F_Rej_Zdar_Char(Z.ID_ZDAR, 'NAZWA_FIRMY_SKR'),NULL)) AS VARCHAR2(492)) DANE_KLIE
FROM T_ZDARZENIA Z
WHERE F_Rej_Zdar_Char(Z.ID_ZDAR, 'JEST') = 'T';
and functions:
CREATE OR REPLACE FUNCTION F_Rej_Zdar_Char
(WE_ID_ZDAR IN NUMBER
,WE_KOLUMNA IN VARCHAR2
RETURN VARCHAR2
IS
c_numer           T_PRZYSTAPIENIA.NUMER%TYPE;--VARCHAR2(30);
c_rodzaj           T_KLIENCI.RODZAJ%TYPE;--VARCHAR2(1);
c_typ_przy           T_PRZYSTAPIENIA.TYP_PRZY%TYPE;--VARCHAR2(1);
c_typ_ubez           T_PRZYSTAPIENIA.TYP_UBEZ%TYPE;--VARCHAR2(3);
c_nazwisko           T_KLIENCI.NAZWISKO%TYPE;--VARCHAR2(30);
c_imie                T_KLIENCI.IMIE%TYPE;--VARCHAR2(30);
c_imie_ojca      T_KLIENCI.IMIE_OJCA%TYPE;--VARCHAR2(30);
c_nazwa_firmy      T_KLIENCI.NAZWA_FIRMY%TYPE;--VARCHAR2(300);
c_nazwa_firmy_skr T_KLIENCI.NAZWA_FIRMY%TYPE;--VARCHAR2(100);
c_jest                VARCHAR2(1) := 'T';
c EXCEPTION;
BEGIN
--dbms_output.put_line('id zdar wykonania '||WE_ID_ZDAR);
BEGIN
SELECT p.NUMER, k.RODZAJ,p.TYP_PRZY,p.TYP_UBEZ,k.nazwisko, k.imie, k.imie_ojca, k.nazwa_firmy, k.nazwa_firmy_skr
INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
FROM T_KLIENCI k, T_PRZYSTAPIENIA p, T_ZDARZENIA z, T_PODMIOTY D1, T_PODMIOTY D2
WHERE p.KLIE_ID_KLIE = k.ID_KLIE
AND z.PODM_ID_PODM = D1.ID_PODM
AND D1.KLIE_ID_KLIE = p.KLIE_ID_KLIE
AND Z.PODM_UMOW_ID_UMOW = D2.ID_PODM
AND D2.PRZY_ID_PRZY = P.ID_PRZY
AND z.ID_ZDAR = WE_ID_ZDAR;
EXCEPTION
     WHEN NO_DATA_FOUND THEN
     BEGIN
     SELECT p.NUMER, k.RODZAJ,p.TYP_PRZY,p.TYP_UBEZ,k.nazwisko, k.imie, k.imie_ojca, k.nazwa_firmy, k.nazwa_firmy_skr
     INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
     FROM T_KLIENCI k, T_PRZYSTAPIENIA p, T_ZDARZENIA z, T_PODMIOTY D
     WHERE z.PODM_UMOW_ID_UMOW IS NULL
     AND z.PODM_ID_PODM = D.ID_PODM
     AND D.KLIE_ID_KLIE = k.ID_KLIE
     AND p.KLIE_ID_KLIE = k.ID_KLIE
     AND z.ID_ZDAR = WE_ID_ZDAR;
     EXCEPTION
          WHEN NO_DATA_FOUND THEN
          BEGIN
          SELECT NULL NUMER, NULL RODZAJ,NULL TYP_PRZY,NULL TYP_UBEZ, I.nazwisko, I.imie, I.imie_ojca, I.NAZWA NAZWA_FIRMY, I.NAZWA_SKR nazwa_firmy_skr
          INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
          FROM T_ZDARZENIA z, T_INSTYTUCJE I
          WHERE Z.TYP IN ('WFS526','WFS542','WFS553','WFS609','WFS611','WYP_KS','WYP_PO','WYP_SB','DI_ZAT')
          AND z.PODM_UMOW_ID_UMOW IS NULL
          AND Z.PODM_ID_PODM = I.ID_INST
          AND z.ID_ZDAR = WE_ID_ZDAR;
          EXCEPTION
               WHEN NO_DATA_FOUND THEN
               BEGIN
               SELECT p.NUMER NUMER, DECODE(a.TYP_AGENTA,'A','F','P') RODZAJ, DECODE(a.TYP_AGENTA,'P','R',a.TYP_AGENTA) TYP_PRZY,NULL TYP_UBEZ,a.nazwisko, a.imie, a.imie_ojca, a.nazwa_firmy, a.nazwa_firmy_skr
               INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
               FROM T_AG_AGENCI a, T_AG_UMOWY p, T_ZDARZENIA z
               WHERE a.ID_AGAG = p.AGAG_ID_AGAG
               AND z.PODM_UMOW_ID_UMOW = p.ID_AGUM
               AND z.ID_ZDAR = WE_ID_ZDAR;
               EXCEPTION
                    WHEN NO_DATA_FOUND THEN
                    BEGIN
                    SELECT p.NUMER NUMER, DECODE(a.TYP_AGENTA,'A','F','P') RODZAJ, DECODE(a.TYP_AGENTA,'P','R',a.TYP_AGENTA) TYP_PRZY,NULL TYP_UBEZ,a.nazwisko, a.imie, a.imie_ojca, a.nazwa_firmy, a.nazwa_firmy_skr
                    INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
                    FROM T_AG_AGENCI a, T_AG_UMOWY p, T_ZDARZENIA z
                    WHERE a.ID_AGAG = p.AGAG_ID_AGAG
                    AND z.PODM_ID_PODM = a.ID_AGAG
                    AND z.PODM_UMOW_ID_UMOW IS NULL
                    AND z.ID_ZDAR = WE_ID_ZDAR;
                    EXCEPTION
                         WHEN NO_DATA_FOUND THEN
                         BEGIN
                         SELECT p.NUMER_UMOWY NUMER, DECODE(p.TYP_AGENTA,'A','F','P') RODZAJ, DECODE(p.TYP_AGENTA,'P','R',p.TYP_AGENTA) TYP_PRZY,NULL TYP_UBEZ,p.nazwisko, p.imie_pierwsze, p.imie_ojca, p.nazwa_firmy, p.nazwa_firmy_skr
                         INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
                         FROM T_AG_KANDYDACI a, T_AG_UMOWY_TAB p, T_ZDARZENIA z
                         WHERE a.ID_AGKAN = p.TECH_PODM_ID_PODM
                         AND z.PODM_UMOW_ID_UMOW = p.TECH_ID_AGUMT
                         AND z.ID_ZDAR = WE_ID_ZDAR;
                         EXCEPTION
                              WHEN NO_DATA_FOUND THEN
                              BEGIN
                              SELECT p.NUMER_UMOWY NUMER, DECODE(p.TYP_AGENTA,'A','F','P') RODZAJ, DECODE(p.TYP_AGENTA,'P','R',p.TYP_AGENTA) TYP_PRZY,NULL TYP_UBEZ,p.nazwisko, p.imie_pierwsze, p.imie_ojca, p.nazwa_firmy, p.nazwa_firmy_skr
                              INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
                              FROM T_AG_KANDYDACI a, T_AG_UMOWY_TAB p, T_ZDARZENIA z
                              WHERE a.ID_AGKAN = p.TECH_PODM_ID_PODM
                              AND z.PODM_ID_PODM = a.ID_AGKAN
                              AND z.PODM_UMOW_ID_UMOW IS NULL
                              AND z.ID_ZDAR = WE_ID_ZDAR;
                              EXCEPTION
                                   WHEN NO_DATA_FOUND THEN
                                   BEGIN
                                   SELECT k.NUMER_UMOWY NUMER, DECODE(k.TYP_PRZYSTAPIENIA,'P','F','P') RODZAJ,k.TYP_PRZYSTAPIENIA TYP_PRZY,'NPO' TYP_UBEZ, k.nazwisko, k.imie_pierwsze, k.imie_ojca, k.nazwa_firmy nazwa_firmy, k.nazwa_firmy_skr nazwa_firmy_skr
                                   INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
                                   FROM T_WE_UM_NPO_TAB k, T_ZDARZENIA z
                                   WHERE z.ID_ZDAR = k.TECH_ZDAR_ID_ZDAR
                                   AND k.TYP_PRZYSTAPIENIA IN ('P','W')
                                   AND z.PODM_ID_PODM IS NULL
                                   AND z.PODM_UMOW_ID_UMOW IS NULL
                                   AND z.ID_ZDAR = WE_ID_ZDAR;
                                   EXCEPTION
                                        WHEN NO_DATA_FOUND THEN
                                        BEGIN
                                        SELECT k.NUMER_UMOWY NUMER, 'F' RODZAJ,'-' TYP_PRZY,'OPS' TYP_UBEZ, k.nazwisko, k.imie_pierwsze, k.imie_ojca, NULL nazwa_firmy, NULL nazwa_firmy_skr
                                        INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
                                        FROM T_WE_UM_OPS_TAB k,T_ZDARZENIA z
                                        WHERE z.ID_ZDAR = k.TECH_ZDAR_ID_ZDAR
                                        AND z.PODM_ID_PODM IS NULL
                                        AND z.PODM_UMOW_ID_UMOW IS NULL
                                        AND z.ID_ZDAR = WE_ID_ZDAR;
                                        EXCEPTION
                                             WHEN NO_DATA_FOUND THEN
                                             BEGIN
                                             SELECT NULL NUMER, NULL RODZAJ,NULL TYP_PRZY,NULL TYP_UBEZ, NULL nazwisko, NULL imie_pierwsze, NULL imie_ojca, NULL nazwa_firmy, NULL nazwa_firmy_skr
                                             INTO c_numer, c_rodzaj, c_typ_przy, c_typ_ubez, c_nazwisko, c_imie, c_imie_ojca, c_nazwa_firmy, c_nazwa_firmy_skr
                                             FROM T_ZDARZENIA z
                                             WHERE z.TYP NOT IN ('UM_OPS','UM_NPO','NPO_OP','UZUP_U')
                                             AND z.PODM_ID_PODM IS NULL
                                             AND z.PODM_UMOW_ID_UMOW IS NULL
                                             AND z.ID_ZDAR = WE_ID_ZDAR;
                                             EXCEPTION
                                                  WHEN NO_DATA_FOUND THEN
                                                       --dbms_output.put_line('id zdar wykonania '||WE_ID_ZDAR||' ostatni wyjatek');
                                                       NULL;
                                             END;
                                        END;
                                   END;
                              END;
                         END;
                    END;
               END;
          END;
     END;
END;
--raise c;
IF WE_KOLUMNA = 'NUMER' THEN
RETURN c_numer;
ELSIF WE_KOLUMNA = 'RODZAJ' THEN
RETURN c_rodzaj;
ELSIF WE_KOLUMNA = 'TYP_PRZY' THEN
RETURN c_typ_przy;
ELSIF WE_KOLUMNA = 'TYP_UBEZ' THEN
RETURN c_typ_ubez;
ELSIF WE_KOLUMNA = 'NAZWISKO' THEN
RETURN c_nazwisko;
ELSIF WE_KOLUMNA = 'IMIE' THEN
RETURN c_imie;
ELSIF WE_KOLUMNA = 'IMIE_OJCA' THEN
RETURN c_imie_ojca;
ELSIF WE_KOLUMNA = 'NAZWA_FIRMY' THEN
RETURN c_nazwa_firmy;
ELSIF WE_KOLUMNA = 'NAZWA_FIRMY_SKR' THEN
RETURN c_nazwa_firmy_skr;
ELSIF WE_KOLUMNA = 'JEST' THEN
RETURN c_jest;
END IF;
END;
CREATE OR REPLACE FUNCTION F_Rej_Zdar_Date
(WE_ID_ZDAR IN NUMBER
,WE_KOLUMNA IN VARCHAR2
RETURN DATE
IS
d_data DATE;
BEGIN
BEGIN
SELECT p.DATA_PODPISANIA
INTO d_data
FROM T_KLIENCI k, T_PRZYSTAPIENIA p, T_ZDARZENIA z, T_PODMIOTY D1, T_PODMIOTY D2
WHERE p.KLIE_ID_KLIE = k.ID_KLIE
AND z.PODM_ID_PODM = D1.ID_PODM
AND D1.KLIE_ID_KLIE = p.KLIE_ID_KLIE
AND Z.PODM_UMOW_ID_UMOW = D2.ID_PODM
AND D2.PRZY_ID_PRZY = P.ID_PRZY
AND z.ID_ZDAR = WE_ID_ZDAR;
EXCEPTION
     WHEN NO_DATA_FOUND THEN
     BEGIN
     SELECT p.DATA_PODPISANIA
     INTO d_data
     FROM T_KLIENCI k, T_PRZYSTAPIENIA p, T_ZDARZENIA z, T_PODMIOTY D
     WHERE z.PODM_UMOW_ID_UMOW IS NULL
     AND z.PODM_ID_PODM = D.ID_PODM
     AND D.KLIE_ID_KLIE = k.ID_KLIE
     AND p.KLIE_ID_KLIE = k.ID_KLIE
     AND z.ID_ZDAR = WE_ID_ZDAR;
     EXCEPTION
          WHEN NO_DATA_FOUND THEN
          BEGIN
          SELECT NULL DATA_PODPISANIA
          INTO d_data
          FROM T_ZDARZENIA z, T_INSTYTUCJE I
          WHERE Z.TYP IN ('WFS526','WFS542','WFS553','WFS609','WFS611','WYP_KS','WYP_PO','WYP_SB','DI_ZAT')
          AND z.PODM_UMOW_ID_UMOW IS NULL
          AND Z.PODM_ID_PODM = I.ID_INST
          AND z.ID_ZDAR = WE_ID_ZDAR;
          EXCEPTION
               WHEN NO_DATA_FOUND THEN
               BEGIN
               SELECT p.DATA_PODPISANIA DATA_PODPISANIA
               INTO d_data
               FROM T_AG_AGENCI a, T_AG_UMOWY p, T_ZDARZENIA z
               WHERE a.ID_AGAG = p.AGAG_ID_AGAG
               AND z.PODM_UMOW_ID_UMOW = p.ID_AGUM
               AND z.ID_ZDAR = WE_ID_ZDAR;
               EXCEPTION
                    WHEN NO_DATA_FOUND THEN
                    BEGIN
                    SELECT p.DATA_PODPISANIA DATA_PODPISANIA
                    INTO d_data
                    FROM T_AG_AGENCI a, T_AG_UMOWY p, T_ZDARZENIA z
                    WHERE a.ID_AGAG = p.AGAG_ID_AGAG
                    AND z.PODM_ID_PODM = a.ID_AGAG
                    AND z.PODM_UMOW_ID_UMOW IS NULL
                    AND z.ID_ZDAR = WE_ID_ZDAR;
                    EXCEPTION
                         WHEN NO_DATA_FOUND THEN
                         BEGIN
                         SELECT p.DATA_PODPISU_AGENTA DATA_PODPISANIA
                         INTO d_data
                         FROM T_AG_KANDYDACI a, T_AG_UMOWY_TAB p, T_ZDARZENIA z
                         WHERE a.ID_AGKAN = p.TECH_PODM_ID_PODM
                         AND z.PODM_UMOW_ID_UMOW = p.TECH_ID_AGUMT
                         AND z.ID_ZDAR = WE_ID_ZDAR;
                         EXCEPTION
                              WHEN NO_DATA_FOUND THEN
                              BEGIN
                              SELECT p.DATA_PODPISU_AGENTA DATA_PODPISANIA
                              INTO d_data
                              FROM T_AG_KANDYDACI a, T_AG_UMOWY_TAB p, T_ZDARZENIA z
                              WHERE a.ID_AGKAN = p.TECH_PODM_ID_PODM
                              AND z.PODM_ID_PODM = a.ID_AGKAN
                              AND z.PODM_UMOW_ID_UMOW IS NULL
                              AND z.ID_ZDAR = WE_ID_ZDAR;
                              EXCEPTION
                                   WHEN NO_DATA_FOUND THEN
                                   BEGIN
                                   SELECT k.DATA_PODPISANIA_UM DATA_PODPISANIA
                                   INTO d_data
                                   FROM T_WE_UM_NPO_TAB k, T_ZDARZENIA z
                                   WHERE z.ID_ZDAR = k.TECH_ZDAR_ID_ZDAR
                                   AND k.TYP_PRZYSTAPIENIA IN ('P','W')
                                   AND z.PODM_ID_PODM IS NULL
                                   AND z.PODM_UMOW_ID_UMOW IS NULL
                                   AND z.ID_ZDAR = WE_ID_ZDAR;
                                   EXCEPTION
                                        WHEN NO_DATA_FOUND THEN
                                        BEGIN
                                        SELECT k.DATA_PODPISANIA_UM DATA_PODPISANIA
                                        INTO d_data
                                        FROM T_WE_UM_OPS_TAB k,T_ZDARZENIA z
                                        WHERE z.ID_ZDAR = k.TECH_ZDAR_ID_ZDAR
                                        AND z.PODM_ID_PODM IS NULL
                                        AND z.PODM_UMOW_ID_UMOW IS NULL
                                        AND z.ID_ZDAR = WE_ID_ZDAR;
                                        EXCEPTION
                                             WHEN NO_DATA_FOUND THEN
                                             BEGIN
                                             SELECT NULL DATA_PODPISANIA
                                             INTO d_data
                                             FROM T_ZDARZENIA z
                                             WHERE z.TYP NOT IN ('UM_OPS','UM_NPO','NPO_OP','UZUP_U')
                                             AND z.PODM_ID_PODM IS NULL
                                             AND z.PODM_UMOW_ID_UMOW IS NULL
                                             AND z.ID_ZDAR = WE_ID_ZDAR;
                                             EXCEPTION
                                                  WHEN NO_DATA_FOUND THEN
                                                       d_data := NULL;
                                             END;
                                        END;
                                   END;
                              END;
                         END;
                    END;
               END;
          END;
     END;
END;
IF WE_KOLUMNA = 'DATA_PODPISANIA' THEN
RETURN d_data;
END IF;
END;

Problem in query with the u0091Document numberu0092

Hi,
I got problem in query with the Document number
There are three columns in the cube 1) Document number 2) Country 3) Count
In the cube there are multiple entries for same document number as below.
      Document number           country          Count
     10000               US          1
     10001               US          1
     10002               US          1
     10002               US          1
     10002               US          1
     10003               UK          1
     10004               IN          1
     10004               IN          1
When I ran the query on this cube for country US it shows count as 5 but I want count as 3 (i.e. it has to take count only once for the same document nos)
Similarly for country IN I want count as 1

Hi,
You have to create a counter based on the document number (exception aggregation). There is a How-to paper available for this. It is called: How-to...count the occurences of a characteristic.
Regards,
P.

Query transport-normal transport or BEx transport?

I could able to transport the backend objects but not sure about query transport. I would like to know difference between normal TRUCK transport and TRUCK-BEx transport in transport connection for queries. Can I use any or there are specific rules when to use what.

HI,
Bex transport truck mean you can create a global transport for you queries, when you transport your queries from dev to qa those queries wont be editable in development system unless you define this global transport. Everytime you make the changes in those queries these changes will be automatically gets updated in this global transport. Finally you dont have to retransport these changed queries, you have to simply release this global transport and the changes gets updated into quality server. The second transport truck is normal transport, and can be used to transport reports from dev to quality.
So bex transport is useful and you dont need to create a request after every change in report.
Hope this will help
regards,
ray

SAP Query: Transport tool(program: RSAQR3TR)

Does the SAP Query: Transport tool(program: RSAQR3TR) transport addtional fields and code in Extras of an InfoSet from one system to another?
TKS in advance.

Hello,
Yes the ABAP query transports the whole Infoset.
Goto Transaction SQ02
Goto Environment -> Query areas -> Select teh Standard area.
Select Environment -> Transports -> Import radio Button
Check the Overwriting allowedand teh remove the check for Test Run
Select the Transport Infosets and queries radiobutton
Fill in the Infoset and teh Query with the corresponding names and the Import option with Transport Request Number
Execute
Regards

ABAP Query transports not handled by CHARM

Hi,
How should ABAP query transports be handled in CHARM??
The ABAP query transport tool doesn't allow picking a transport that is already created (Own transport), it creates a new transports which is outside of CHARM. I had to assign the objects in the transport manually to the appropriate CHARM transport.
Any ideas???
ABAP query don't seem to be using the standard transport tool.
Thanks
Stephane

Hi
Instead of assigning the objects you can directly assign the trasnports to the charm task list of the project
check q22 (registerting transport created outside of charm)
Change Request Management scenario: Usual questions and known errors
hope it clarifies
regards
prakhar

ABAP Query Transports

How to do ABAP Query Transports?

Hi,
Use the SAP std report - RSAQR3TR.
Reward points if helps.
Regards,
JLN

Problem in Query Transportation

Similar Messages

Maybe you are looking for