Report variant not transport to ECC 6.0

hi all,
after migration from SAP 4.6 to ECC6, i cant see the SAP transaction report variant not transaport over....is there any SAP table store the user variant not transported ?
Thanks .

Pls. check manual:
Phase SAVE_VAR_CHK
After the upgrade, many of your variants can no longer be used because the relevant selection screens
have changed. If your Basis Source Release is 4.5B or higher, the SAP system offers two reports to
save the variants:
n RASUVAR1 saves your variants on the source system.
n RASUVAR2 restores the variants in the target system.
During phase SAVE_VAR_CHK you can decide whether you want the upgrade tool to run report
RASUVAR1. The report is started in phase JOB_RASUVAR1. If you have decided to run report
RASUVAR1, phase JOB_RASUVAR2 automatically starts report RASUVAR2 towards the end of the
upgrade.
For more information about the reports, see SAP Note 712297.

Similar Messages

Report Variant Not Found During Transport

A user has requested a routine change (adding a purchase group) to a report variant.
According to our procedures, I have gone into our Development system and changed the report variant to include the new purchasing group. I have then created a transport referencing this report and variant.
However, when I release the transport I get a warning that...
LIMU VARX REPORTNAME VARIANTNAME not found, object also deleted in target system
Application help states that it is a Message no. TW 330
The transport goes through to our production system, but no changes are made. It is essentially an empty transport.
I have done this type of change before to numerous report variants without any issues, and other request of this nature continue to go through without problems. Any idea why this might be happening, and how it can be resolved?
Thanks - points will be rewarded.

Same problem once I face.
I transported one variant name and after that name changed and again transported.
It is not showing new variant name so we executed program and
Goto->variant and overwrite the previous one.
Reward if useful...
Minal

"Delete PSA" variant not transported

I have a process chain which involves a 'Delete PSA request' process. When this is transported into our Test environment the variants do not appear so the deletion does not happen. The process still exists but the variant defining which PSA to delete is blank and so no deletion occurs.
Does anyone know what the problem could be and how we can resolve it?

Hi, the table names are different in Dev and QA (/BIC/B0000628 in QA and /BIC/B0000302 in Dev). So if we reactivate the datasource in Dev, then re-transport the datasources and then retransport the process chains should this resolve the issue? Would the psa tables be re-created with the correct table names in QA if we do this?
Nothing in QA has been activated manually after transport so not sure how that would happen.
We are using NW 2004s, SP 8 at the moment.
Thanks for you help
Message was edited by: Katherine Huggins

Variant is not transported

Hello SAP gurus,
Immediate requirement your help is required.
I have created a variant and a TR number in VT04 but when the TR has been moved to quality system I could not find the variant there. The TR number is correctly imported from development to quality but variant is not there.
So my doubt is if we need to create the variant manually in each system.
Thanks
Sha

variants can be transported, please see OSS Note 128908 - Transporting report variants
for details.
This note has related notes which fix as well some problems, maybe you have one of these bugs in your system

Transporting reports are not overwritten

Hi,
Problem related to Transportation:
I transported some reports from DEV to QA. After that I made some changes on the transported reports and again I transported with another request, but those reports are not overwritten.
can you please post some points how can I solve this..
Regards
Rajesh

Hi rajesh,
Have you released the early transport request.
After doing changes in reports have you activated all and saved in request.check it.
Try to collect all in Transport connection in one request once again and transport the same to QA.
Let us know status....
Reg
Pra

Report does not work in 2nd instance after transported

My SAP Script report does not come out correctly after its transport into a 2nd instance. The fonts displayed in the report don't look the same like what we have in instance #1.
The report originally created in the instance #1 is good, but after the transport, the fonts in instance #2 are larger and some of the contents are not properly aligned. Some part of the boxes are also missing. I would appreciate any suggestions of how to fix them. Thanks, Sam

Hi,
There might be a possiblity that the necessary style used in the SapScript is not transported to the New Instance and hence the Cosmetic issues...
Check whether all the associated objects like Style are transported to nre Instance or not?

Changes not reflecting in Report designer after Transports

Hi,
I have made some changes to a Report in the report designer and transported it to Quality and Acceptance systems. But the changes are reflecting in Quality system not in Acceptance server. In Acceptance sever the changes are seen in the report physically but when i execute the report i still see the old format. I tried transporting the request again to the system but no luck.
Cleared the Cache in Acceptance still no luck. Also regenerated the base query in RSRT and no effect on the report. Any idea?
Thanks,
Praveen

Hi Praveen,
Make sure you have collected all the objects of the report.
You may check this in (development) RSA1->Transport Connection. Select that report and see if any objects are still not under $TMP or under any other Package and not got collected in your previous TR.
Regards,
Pratap Sone

MULTI LEVEL REPORT FOR STOCK TRANSPORT PURCHASE ORDER

Hi,
I will have lot of stock transport purchase orders,like md4c transaction where we get multilevel report for sale order/production order,is there any report for stock transport purchase orders.its urgent kindly help

goto purchase order history tab
you can see all the details of PO-deluvery-GI, GR, imvoice. Click on delivery, you can see the billing document throughdocument flow button.
This function is not availilable for production order, hence we have MD4c.

Transaction variant not working in quality

Hi,
I have created a transaction varient in SHD0 and activated it in develpoment and then
it is working fine in development system.Then variant transported to quality and there also
it is activated but somehow it is not working in qulaity sytem.
I checked in the respctive transaction with following path
SYSTEM>>>>>STATUS>>>>>SAP REPOSITORY DATA and i can find it is transaction variant name
below screen program.
Pl suggest the resolution.
Regards,
Rushikesh

Hi,
Check the variant is transported properly in QA. If present then check the transaction for the same.
If you make this transaction for a table the check the table delivery and maintenance allowed or not. It should be maintenance allowed.
Thanks
Subhankar

G_G_IDOC_REC_ZZINCOT function module not found in ECC 5.0

i am getting the dump.
the fuction module is not presend in ECC 5.0
Runtime Errors         CALL_FUNCTION_NOT_FOUND
Exceptn                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          04/05/2007 07:13:25
ShrtText
Function module "G_G_IDOC_REC_ZZINCOT" not found.
What happened?
The function module "G_G_IDOC_REC_ZZINCOT" was called, but cannot be
    found in the Function Library.
Error in ABAP application program.
The current ABAP program "SAPLGUIF" had to be terminated because one of the
    statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
     termination messages, especially those beyond their normal deletion
    date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',
     was neither
caught nor passed along using a RAISING clause, in the procedure
     "IDOC_INPUT_GLROLL" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    The program "SAPLGUIF" contains a CALL FUNCTION statement. The name
    of the function module to be called is "G_G_IDOC_REC_ZZINCOT".
No function module exists with the name "G_G_IDOC_REC_ZZINCOT".
    All function modules are stored in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
       to upper/lower case and underscores ("_")
    b) Transport error
c) If an enqueue/dequeue module has been used, the lock object
       may not have been activated (ABAP Dictionary)
       may not have been activated (ABAP Dictionary).
How to correct the error
Check the last transports to the R/3 System.
    Is the program "SAPLGUIF" currently being changed?
    If an enqueue/dequeue module is involved, is the activation
    of the lock object missing in the ABAP/4 Dictionary?
You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
"CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC
    "SAPLGUIF" or "LGUIFU05"
    "IDOC_INPUT_GLROLL"
Function modules with names similar to "G_G_IDOC_REC_ZZINCOT":
G_G_IDOC_REC_COFIT
G_G_IDOC_REC_FILCT
G_G_IDOC_REC_ECMCT
G_G_IDOC_REC_GLPCT
G_G_IDOC_REC_GLT0
G_G_IDOC_REC_SECURE
G_POSTING_ZZINCOT
G_G_IDOC_SEND_COFIT
G_G_IDOC_SEND_ECMCT
G_G_IDOC_SEND_SECURE
If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".
2. A suitable printout of the system log
       To obtain this, call the system log through transaction SM21.
       Limit the time interval to 10 minutes before and 5 minutes
       after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, select the Editor function "Further Utilities->
       Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    The exception must either be prevented, caught within the procedure
     "IDOC_INPUT_GLROLL"
"(FUNCTION)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "d48ix100"
    Network address.......... "151.162.153.62"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C65EFD4C00"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 2
    Short dump setting....... "full"
Database server.......... "d48ix100"
    Database type............ "ORACLE"
    Database name............ "D48"
    Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
    Created on............... "Nov 5 2006 20:46:58"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
Patch level.............. "156"
    Patch text............... " "
Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
     10.2.0.."
SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
    Roll..................... 16128
    EM....................... 8379856
    Heap..................... 0
    Page..................... 16384
    MM Used.................. 2530176
    MM Free.................. 1657232
    SAP Release.............. "640"
User and Transaction
Client.............. 010
    User................ "OS0730"
    Language key........ "E"
    Transaction......... "YICUPLD "
    Program............. "SAPLGUIF"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    The termination occurred in the ABAP program "SAPLGUIF" in "IDOC_INPUT_GLROLL".
    The main program was "Y21091IRECON ".
The termination occurred in line 65 of the source code of the (Include)
     program "LGUIFU05"
of the source code of program "LGUIFU05" (when calling the editor 650).
    Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"
     occurred in the
procedure "IDOC_INPUT_GLROLL" "(FUNCTION)" but was not handled locally, not
     declared in the
RAISING clause of the procedure.
    The procedure is in the program "SAPLGUIF ". Its source code starts in line 5
    of the (Include) program "LGUIF$05 ".
Source Code Extract
Line SourceCde
35
36 *Prüfen, ob Customizing richtig eingestellt ist
   37     CHECK EXIT IS INITIAL.
   38     PERFORM CHECK_CUSTOMIZING USING IDOC_NUMBER.
   39
40 *Für Einzelposten neue Belegnummern vergeben
   41     CHECK EXIT IS INITIAL.
   42     PERFORM NEW_DOCUMENT_NUMBER USING IDOC_NUMBER
   43                                       IDOC_CONTRL-MESTYP.
   44
45 *Füllen der Segmentdaten
   46     CHECK EXIT IS INITIAL.
   47     CLEAR IDOC_SEGMENT. REFRESH IDOC_SEGMENT.
   48
49     LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_NUMBER.
   50       IDOC_SEGMENT = IDOC_DATA.
   51       APPEND IDOC_SEGMENT.
   52     ENDLOOP.
53
54 *Name des zu rufenden Funktionsbausteines ermitteln
   55     ROL_FUNCNAME = 'G_G_IDOC_REC_$'.
   56     PERFORM BUILD_ROL_FUNCNAME USING IDOC_NUMBER ROL_FUNCNAME.
   57
58 *Funktionsbaustein zum Empfangen des IDOC's aufrufen
   59 *Wenn Sender 4.0 System -> Nimm' TAB30, sonst altes TAB
   60     IF NOT E1GLTTF-TAB30 IS INITIAL.
   61       L_TAB30 = E1GLTTF-TAB30.
   62     ELSE.
63       L_TAB30 = E1GLTTF-TAB.
   64     ENDIF.
>>>>>     CALL FUNCTION ROL_FUNCNAME
   66          EXPORTING
   67               MESTYP             = IDOC_CONTRL-MESTYP
   68               DOCNUM             = IDOC_NUMBER
   69               TAB                = L_TAB30
   70          TABLES
71               IDOC_SEGMENT       = IDOC_SEGMENT
   72               IDOC_STATUS        = IDOC_STATUS
   73               RETURN_VARIABLES   = RETURN_VARIABLES.
   74
75   ENDLOOP.
76
77 *Keine IDOC's empfangen
   78   IF SY-SUBRC NE 0.
   79     RAISE WF_ERROR_PROCESS.
   80   ELSE.
81 *Prüfen, ob Fehler bei der Verarbeitung der IDOCs aufgetreten sind
   82     LOOP AT IDOC_STATUS WHERE MSGTY = 'A'
   83                            OR MSGTY = 'E'.
   84       EXIT.
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 2
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY                                                                           &

I think that the FM is a customized one. Correct me if I am wrong. It is quite possible that certain FM's might have been missed out while the new system is built. Here I am assuming that the you are doing an upgrade.
If whatever, I've mentioned above is correct, you can copy the FM and its other components from the old system into the new one, to rectify the error

How to define a specific report variant execution in Area Menu

For report REP01, for exemple, with a selection screen, I defined a variant with specific options, named VAR_SPEC1, to be used by a certain group of persons.
Now I created the Area Menu ZMSPEC1, and I need to associate to it an entry to execute program REP01 via variant VAR_SPEC01. How can I do it?
I saw that the program REP01 already has already defined a report transaction (ZEXREP01, for ex.), but if I use this transaction in the Area Menu, I will not use my variant...
I was looking to the different types of transactions that can be defined, but I am a bit lost.
Thanks in advance.
Davide

Hello,
I am still a bit lost about the easier (or better) way to associate to the new Area Menu the execution of a non-local program with selection-screen, using some predefined options (hidding some fields, predefining others...).
Can someone be more specific?
I guess the necessary elements are:
1) non-local program REP01;
2) core report variant VAR_DEFAULT, for program above.
3) new local variant VAR_SPEC1, for program in 1)
4) ...
5) ... some solution to link both parts...
6) ...
7) Area Menu ZMSPEC1, with a new item to call the execution of REP01 with variant VAR_SPEC1.
Any ideas? many thanks!

Dynamic seleciton in report variant FBL1N

Hi,
Problem Description
I am trying use dyanamic selection in report variant of FBL1N but its not working.
My working
I am using dyanamic date variant.
In the selection screen of FBL1N, we have posting date in dynamic selections.
While creating a variant for the selection screen of FBL1N, I am selecting Posting Date of dyanamic selection and choosing selection variant as "D" (D: Dynamic date calculation) along with Current Date as variable.
However system is not accepting this and the current date is not coming up while choosing this variant.
Solution required
Can anyone please help me out with dyanamic date calculation in dates from dynamic selection in report FBL1N.
Thanks,
Nitish

Dear
You did not specify in which version you are working. If you are in new GL instead of using FBL1N you can as well use T.Code S_AC0_52000888 and here you can make dynamic selections.
Regds

Error in Dialog Module - INCLUDE report "%_HR9066" not found

Hi,
After upgrade from 4.6B to ECC 6.0.When i display/create/change Custom Infotype 9072 in transaction PA30. i encounter a dump stating
INCLUDE report "%_HR9066" not found. It occurs when the program goes for CALL DIALOG... in the SAP standard program.
Do advice on how to resolve this issue

Hi Chayan,
9066 is the custom infotype .
After upgrading check for the following things which are related to infotype :
1) Go to se51 and check for Program MP906600 and screen 2000 exist .If not there is a problem in calling the screen
2)Go to se11 and check whether the table PA9066 and structure P9066 exist
3)Check whether the infotype is assigned to the Infotypes in spro .(Optional)
If everthing is suceessful , the infotype exist in the system . If not one of the objects might miss from the above list .
Regards,
Gajalkshmi

Report painter execution error - KH014 "Report does not exist".

Hi All,
I customized one report in FSI3 and used SE43 to create a t code for this report. In the development system, report will be executable from this t code.
Transport requests are successfully transported from development to production without any error. But on production when I tried to execute the report, I am getting the error KH014 - "Report does not exist".
While checking in production I found that the report was missing from report tree in FSI3 and as a result the customized report cannot be executed. As per basis guys there was not a issue in request transportation.
Has anyone encountered similar problem? How was it resolved?
Thanks.
Prashant

Hi Mikko,
Thanks for your reply but your solution is not working.
Hi Stacy,
I can execute the report from t codes like FSI3 & FSI0 in development.
I used SE43 for t code creation. At the time of t code creation there is a option called "Drilldown" under Report type heading, In drilldown option I selected my report from report type 002 (Financial Statement Key Figure) and created the t code. After this I transported both the request to production server.
Please let me know if this is wrong method or there is any other option to transport this report in Production.
Thanks & Regards,
Prashant

Function Download not support in ECC 6.0

Dear All ,
Now i faced the problem when upgrade my coding to ECC6.0 , my current program is using Call funtion "Download" to export the report data to Excel, but this "Download" function is not support in ECC 6.0 , they suggest me to use call function "GUI_dowload", but this function cannot give me the features like "Donwload" funtion . Any others function which can use in ECC 6.0 and same features like "Download" .
Thanks

Those functions are obsolete, ([Note 594356 - Function modules ws_upload and ws_download are obsolete|https://service.sap.com/sap/support/notes/594356])
Use news FM GUI_DOWNLOAD or class CL_GUI_FRONTEND_SERVICES method GUI_DOWNLOAD.
Regards,
Raymond

Report variant not transport to ECC 6.0

Similar Messages

Maybe you are looking for