FUNCTION_IMPORT_INTERFACE Changed by SAP Upgrade
Dear Experts,
recently we had some new surpport package installed in our system,
since then some transaction need more authority
MR21 VL10D for example
TCODEs runs a function FUNCTION_IMPORT_INTERFACE
in which a new peice of code was added:
68 call function 'RS_ACCESS_PERMISSION'
69 exporting
70 * AUTHORITY_CHECK = 'X'
71 * GLOBAL_LOCK = ' '
72 * MASTER_LANGUAGE = ' '
73 mode = 'SHOW'
74 object = funcname
75 object_class = 'FUNC'
76 exceptions
77 no_modify_permission = 6
78 no_show_permission = 7
79 permission_failure = 8
80 request_language_denied = 9
81 others = 10.
82 if sy-subrc <> 0.
83 message id sy-msgid type 'E' number sy-msgno
84 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4 rai
85 endif.
this code will check display authority for function group MCEX
i wanna know why......
thanks a million
Hello Prashad,
Its standard that once the object is changed the corresponding entry is recorded in different tables.Even if you roll back now system will treat as the modifications because corresponding change entries are present in the tables. You can try to activate the older versions but i don't think this will help you.
This is not a point of worry as in SPDD adn SPAU you can choose reset to original for all those objects.
Even if you can get those objects to move back to the source version they will get back to the standard in the new release.So my advise will be to let your upgrade run and then reset these objects to original.
Regards
Niraj
Similar Messages
-
Standard Objects changed in SAP upgrade
Hi
Is there any kind of database available that describes what standard components (like tables, includes, FMs, programs etc) have changed in the new release.
For e.g. I am upgrading my system from 4.6C to ECC6, and table XYZ has changed in the new release, I need to fix Z program using table XYZ.
Is any such data available?
Thanks
JaydeepHi Narin, Sumit
Thanks for the inputs but I think there's small confusion. SPDD & SPAU will give be changed objects during upgrade only if they are modified by customer.
Let me try to clarify my question. I am trying to find out all the standard SAP objects that have undergone some change from old release to new.
For e.g. some table in 4.7 had 25 fields and in ECC5 (next release) SAP added 2 more fields.
Now this table may not be modified by customer, hence the change would be transparent to customer. This won't be stuck up in SPDD either during upgrade.
Same for ay standard program / include / function module.
Hope I am clear in explaining my requirement.
Thanks
Jaydeep -
SAP parameters need to be changed after memory upgrade
HI,
Recently we had the memory in few systems increased by 2-4 GB. Do we need to change any SAP/DB parameters due to this change?If yes, what are they? Info: Platform is AIX/Oracle, ECC6 and BI 7.0
Regards,
ArindamThanks for your reply.
No, I mean the memory has been increased by 2 - 4 GB. For e.g. in one system memory was 16 GB, it was increased to 20GB. In another system the memory was 12 GB, it was increased to 14GB. What I want to know is, because of this increased memory space are there any parameters in SAP/DB that also need to be adjusted according to the amount of memory space(hardware) added?
Regards,
Arindam -
What are the roles & responsibilites of consultant in SAP upgradation or mi
Hello ,
Would you please any dody help me to provide the role & responsibilities of consultant in SAP upgradation or migration project.Thanks.
Regards,
SampallyHello,
If the project is of technical up gradation then with no functionality changed, Then the job of abap consultant is critical, right from creating spdd and spau, interfaces, debug the new programs and fix the bugs if exists in the new programs. The functional consultant has to test the new system from functions point of view; functional consultant is responsible for taking user acceptance test before going on live to the new system.
Regards,
Vivek -
Put Together A Data Archiving Strategy And Execute It Before Embarking On Sap Upgrade
A significant amount is invested by organizations in a SAP upgrade project. However few really know that data archiving before embarking on SAP upgrade yields significant benefits not only from a cost standpoint but also due to reduction in complexity during an upgrade. This article not only describes why this is a best practice but also details what benefits accrue to organizations as a result of data archiving before SAP upgrade. Avaali is a specialist in the area of Enterprise Information Management. Our consultants come with significant global experience implementing projects for the worlds largest corporations.
Archiving before Upgrade
It is recommended to undertake archiving before upgrading your SAP system in order to reduce the volume of transaction data that is migrated to the new system. This results in shorter upgrade projects and therefore less upgrade effort and costs. More importantly production downtime and the risks associated with the upgrade will be significantly reduced. Storage cost is another important consideration: database size typically increases by 5% to 10% with each new SAP software release – and by as much as 30% if a Unicode conversion is required. Archiving reduces the overall database size, so typically no additional storage costs are incurred when upgrading.
It is also important to ensure that data in the SAP system is cleaned before your embark on an upgrade. Most organizations tend to accumulate messy and unwanted data such as old material codes, technical data and subsequent posting data. Cleaning your data beforehand smoothens the upgrade process, ensure you only have what you need in the new version and helps reduce project duration. Consider archiving or even purging if needed to achieve this. Make full use of the upgrade and enjoy a new, more powerful and leaner system with enhanced functionality that can take your business to the next level.
Archiving also yields Long-term Cost Savings
By implementing SAP Data Archiving before your upgrade project you will also put in place a long term Archiving Strategy and Policy that will help you generate on-going cost savings for your organization. In addition to moving data from the production SAP database to less costly storage devices, archived data is also compressed by a factor of five relative to the space it would take up in the production database. Compression dramatically reduces space consumption on the archive storage media and based on average customer experience, can reduce hardware requirements by as much as 80% or 90%. In addition, backup time, administration time and associated costs are cut in half. Storing data on less costly long-term storage media reduces total cost of ownership while providing users with full, transparent access to archived information.Maybe this article can help; it uses XML for structural change flexiblity: http://www.oracle.com/technetwork/oramag/2006/06-jul/o46xml-097640.html
-
Role of Time Mgmt functional consultant during SAP Upgrade from 4.7 to ECC6
Hi,
Could anyone explain the role of a time management functional consultant during SAP upgrade from R/3 4.7 to ECC6.0. Please provide me if you got any documentation.
Thanks,
Sunny"After you upgrade to SAP ERP 6.0, you can enhance the functionality of your application without performing a further
upgrade thanks to a new deployment technology u2013 the SAP enhancement package for SAP ERP. The enhancement
packages simplify the way you manage and deploy new software functions for SAP ERP." - that is the real benefit of ECC 6.0
There aren't any major changes to PTM functionalities from 4.7 to 6.0. I hope your system is already using IT 2006 instead of IT 0005. Under functional role, you are required to configure/test any functional upgrade and manage data.
Regards
Yash -
Need knowledge on sap upgrade 4.7 to ecc 6.0 in abap reports and sap query
please give me some ideas and useful links on sap upgrade 4.7 to ecc 6.0 in abap reports and sap query
Hi Jaya,
Not very clear with your question.
Are you looking for changes in areas od ABAP reports & SAP query when we upgrade SAP from 4.7 to ECC 6.0 ??
If the response is YES, then please refer to SAP solution browser www.sapsolutionbrowser.com
Define source release and target release .
You will get module wise details on new features for target release.
Hope this helps.
Regards,
Deepak Kori -
SAP Upgrade issue ABAP-PI Proxy error
Hi Guys,
We have an issue in SAP R3 system after the recent SAP upgrade.
The proxy programs in R3 were using SAP Standard structure in their development.
Standard structure : SAPPLCO_LOG_ITEM_CODE (TYPE SAPPLCO_LOG)
And so after the upgrade, There seems to be a new field added in the above standard structure and hence causing mismatch between the proxy program developed internal structure to the SAP standard structure.
We come to understand that this Standard structure is being used from SAP PI, Software component SAP APPL.
So SAP PI has old SAP standard structure and SAP R3 has new standard structure with additional field.
Can you please suggest how to overcome this issue. We have also raised an OSS ticket to SAP.
Kind Regards
Rajesh.SHi Harald,
Thank You for the information. I was able to download SAP_APPL 6.06 content from SAP service market place. Here We have a doubt before importing the new SAP APPL content. In market place downloads under SAP_APPL 6.06 we were able to see few many database downloads with last changed at 3.04.2014.
Our EHP upgrade for SAP_APPL is 6.06 , SP level 0007. So we should download / import the highlighted content version (SAPAPPL60607) in the screenshot from market place or download / import the latest change under SAP_APPL 6.06 download patch ? Kindly let us know.
Best Regards,
Rajesh.S -
SAP Upgrade - Standard function modules & modifications
Hello everybody,
we are doing a SAP Upgrade to SAP ERP 6.0 and I need your help
Some SAP standard funcion modules were modified in the last years and some weeks ago the changes were undone. The last version of the function modules are the same than the original function modules, but the version manager shows that the last version belongs to the user FGZ583 (and not SAP).
The Problem is, that SAP deals with that function modules as a modification (because the last change was done by FGZ583?), but they are identical to the original SAP function modules.
When the Upgrade is done, the SPAU/SPDD/se95 show that function modules as "modifications", although they are the same that the original ones.
What could I do to avoid that SAP deals with that function modules as modifications?
Cheers
PrashadHello Prashad,
Its standard that once the object is changed the corresponding entry is recorded in different tables.Even if you roll back now system will treat as the modifications because corresponding change entries are present in the tables. You can try to activate the older versions but i don't think this will help you.
This is not a point of worry as in SPDD adn SPAU you can choose reset to original for all those objects.
Even if you can get those objects to move back to the source version they will get back to the standard in the new release.So my advise will be to let your upgrade run and then reset these objects to original.
Regards
Niraj -
# signs instead of polish letters ą, ę etc. after SAP upgrade.
I am not sure that it is connected with SAP upgrade see my another topic on SCN Rabax during sap gui login
Do you know what could be the reason and is it reversible? Maybe there are some settings in SAP editor?
It is nonunicode ECC 6.0 EHP6 (after upgrade). Before upgrade it was ECC 5.0.
Thanks in advance.
QASHi,
Looking at the thread:
Rabax during sap gui login
it seems you have changed entries in TCPDB from 1401 to 1100.
This would explain your problem.
I would recommend to do a proper setup via report rscpinst.
Therefore you need to know how the system was setup before the upgrade.
If it was single code page with 1401, you need to maintain the used languages and the country field according to SAP note 43205 (the country setting can be found in table TCP0D in the old system).
Best regards,
Nils -
Hi,
We are working in a sap upgrade project ECC 5.0 to ECC6.0. We have found a issue in the features ( PE03) after the upgrade of the dev system. The modifications done to the features has now been overwritten by sap.
eg: The dates maintained in the Feature GBCHG - decision tree nodes are not the same before and after upgrade.
1. Are changes to features captured in SPAU/SPDD or what is the way to find out which/what features need to be adjusted again ?
2. Are there any other sap hr objects configurations which needs to be taken care similar to features?
Thanks
Jagruthi@ Jagruthi:
Hmmm, have you checked the overall structure of the Feature in QA using PE03. A lot of implementations change the way a structure is used to assist their configuration.
When you are in PE03 click on Attributes to look at the author of the changes for the Feature. This is seen on the Administrative Data box (bottom of the page). Notice if Last Changed is a User Name of a company user instead of SAP.
Also when you're in this view, review the actual structure to determine if the same Structure and fields match what you have in DEV.
I really doubt SAP has changed the Feature from ECC 5 to ECC 6. It is much more likely someone has reconfigured the Feautre a long time back.
Cheers, Al -
Going live check for SAP upgrade projects
Hello,
I am interested in "going live check" service and procedures for my upgrade projects. May I find any documentation? Do I have to pay for it?..
Thanking you in advance and a happy new years!
Kind regards
Nilüfer ÇalışkanHi Nilufer,
The following Input as follows :
Source : http://www.thespot4sap.com/upgrade_guide_v2.pdf
This service is included as part of your annual maintenance fee.
The underlying concept of the SAP GoingLive Functional Upgrade Check is
to ensure smooth operation of your mySAP.com solution by taking action
proactively, before severe technical problems occur.
The GoingLive Functional Upgrade Check is made up of three sessions
(Planning, Analysis and Verification)two sessions (Planning and Analysis)
before the upgrade and the other (Verification) after the upgrade.
Planning Session: This session should be performed as much in advance as
possible when the upgrade is first being considered.
Analyses compatibility for the target release with regards to connected
systems in the Solution Landscape, OS version, DB version, installed Add-
Ons, Plug-ins, Country Versions, and so on.
Analysis Session: It is generally performed two months before the
production upgrade (consider lead time for hardware procurement).
The focus is on resource planning and system configuration.
There is a high-level hardware plausibility check (this is not a hardware
sizing exercise).
Potential resource bottlenecks are identified.
Necessary changes will be recommended to prepare the system for the
productive use of the new release.
38 SAP Upgrade Guide | Simplifying Your Upgrade
Verification Session: Generally performed four to six weeks after the
production upgrade, and the recommendation from the analysis session
implemented.
Comparison of performance with results prior to upgrade
Recommendations on configuration and optimization
More information and ordering . For more information, see the GoingLive
Functional Upgrade Check web page at:
<b>http://service.sap.com/goinglive-fu</b>
To order a GoingLive Functional Upgrade Check, contact SAP Customer Care
Center at least eight weeks prior to the planned upgrade of your production
system.
For customers of value-added resellers (VARs) such as CBS customers in the
US, special conditions apply. Contact your VAR.
Remote Upgrade Service
Remote Upgrade Service is a technical upgrade that is performed by SAP
remote consultants. Pricing is based on the complexity of the customers
environment.
SAP performs the technical upgrade of your system, allowing you to focus on
the functional and training side of the upgrade. You are still responsible for
resolving object conflicts.
See SAP Notes 106447 and 84044.
The Remote Upgrade Service is an attractive option for CBS sized customers
with small or non-existent mySAP Technology group.
For more information see the Remote Upgrade Service web page at:
http://service.sap.com/remoteupgrade
Resources
The following list shows some of the resources you can use as you prepare for
your upgrade of SAP. These resources include:
Your installation partner
Customers and others you have networked with at customer functions and
conferences such as:
ASUG
Hope this Info helps you.
<i>Advanced New Year wishes.</i>
Br,
Sri
Award points for helpful answers -
SAP Upgrade ORA-00905: missing keyword
Dear experts,
we have a very urgent SAP upgrade case,
From SAP R/3 470 SR1 110 to ECC 6 EHP4 SPS09
source system have three languages ZH EN DE,it's a
non-unicode system,before SAP upgrade,From rscpinst, i delete language
German and change contry code to CN,
(China). Then there is only code page 8400,T-code: I18N check ok,now we have
a error during upgrade,i was already replace the kernel to 385 version(640_Rel Non-unicode,TP and R3trans alreay the latest version) repeat the SHADOW_IMPORT_UPG1 step but still fail,log result as follow,the SAPKLZHSR1EHP4ERP6F8.GS1 has incomplete conversion
but the previous log file I.E SAPKLZHSR1EHP4ERP6F7.GS1 also have incomplete conversion but no ORA-00905,we only have codepage 8400 and Non-unicode but why the log mention 4103 it's a Unicode code page,thanks a lot!
SHDUPGIMP1.ELG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPKLZHSR1EHP4ERP6F8.GS1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
1 ETP111 exit code : "8"
SAPKLZHSR1EHP4ERP6F8.GS1
4 ETW000 22 entries for RSMPTEXTS~ imported (SAPLMCB2 1*).
4 ETW000 1 entry for TLIBT~ updated (1MCB2).
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from FUNCT~ (1ANALYSE_DURCHF#HREN %) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from FUNCT~ (1ANALYSE_DURCHF#HREN %) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from FUNCT~ (1ANALYSE_DURCHF#HREN %) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from TFTIT~ (1ANALYSE_DURCHF#HREN ) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from TFTIT~ (1ANALYSE_DURCHF#HREN ) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from TFTIT~ (1ANALYSE_DURCHF#HREN ) deleted.
4 ETW000 [ dev trc,00000] Wed Sep 7 10:41:04 2011 815387003 1338.120210
4 ETW000 [ dev trc,00000] OCIStmtExecute() failed with -1=OCI_ERROR 10 1338.120220
4 ETW000 [ dev trc,00000] SQL error 905: 6 1338.120226
4 ETW000 [ dbsloci.,00000] *** ERROR => Error 905 in stmt_fetch() from oci_execute_stmt(), orpc=0
4 ETW000 12 1338.120238
4 ETW000 [ dbsloci.,00000] *** ERROR => ORA-905 occurred when executing SQL stmt (parse error offset=110)
4 ETW000 9 1338.120247
4 ETW000 [ dev trc,00000] sc_p=0x140f618,no=67,idc_p=(nil),con=0,act=1,slen=149,smax=256,#vars=4,stmt=0x1783c10,table=
4 ETW000 17 1338.120264
4 ETW000 [ dev trc,00000] SELECT ID,OBJECT,LANGU,TYP,VERSION FROM "DOKIL~" WHERE (LANGU IN ( :A0 )) AND ID = :A1 AND OBJECT BE\
4 ETW000 9 1338.120273
4 ETW000 [ dev trc,00000] TWEEN :A2 ANALYSE#_DURCHF#REN % :A3 #?; 5 1338.120278
4 ETW000 [ dev trc,00000] sc_p=0x140f618,no=67,idc_p=(nil),con=0,act=1,slen=149,smax=256,#vars=4,stmt=0x1783c10,table=
4 ETW000 11 1338.120289
4 ETW000 [ dev trc,00000] Dumping DBSL stmt. cache: 5 1338.120294
4 ETW000 [ dev trc,00000] prep=0,lit=0,nsql=1,lobret=0,xop=1,dbcnt=0,upsh=(nil),stmtp=0x1784758,rtc=0
4 ETW000 29 1338.120323
4 ETW000 [ dev trc,00000] IN : cols=4,rmax=1,xcnt=0,rpc=0,rowi=0,rtot=0,upto=4294967295,rsize=28,vmax=32,bound=1,iobuf_p=0x1493510,vda_p=0x1784db0
4 ETW000 10 1338.120333
4 ETW000 [ dev trc,00000] lobs=0,lmax=0,lpcnt=0,larr=(nil),lcurr_p=(nil),rret=0 6 1338.120339
4 ETW000 [ dev trc,00000] SELECT ID,OBJECT,LANGU,TYP,VERSION FROM "DOKIL~" WHERE (LANGU IN ( :A0 )) AND ID = :A1 AND OBJECT BE\
4 ETW000 7 1338.120346
4 ETW000 [ dev trc,00000] TWEEN :A2 ANALYSE#_DURCHF#REN % :A3 #?; 5 1338.120351
4 ETW000 [ dbds ,00596] ***LOG BY2=>sql error 905 performing FET [dbds#2 @ 596]
4 ETW000 14 1338.120365
4 ETW000 [ dbds ,00596] ***LOG BY0=>ORA-00905: missing keyword [dbds#2 @ 596] 6 1338.120371
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
4 ETW000 0 entries from FUNCT~ (1MCB_GRAPHIC_DAILY %) deleted.
4 ETW000 0 entries from FUNCT~ (%MCB_GRAPHIC_DAILY %) deleted.
4 ETW000 0 entries from TFTIT~ (1MCB_GRAPHIC_DAILY ) deleted.
4 ETW000 0 entries from TFTIT~ (%MCB_GRAPHIC_DAILY ) deleted.
SAPKLZHSR1EHP4ERP6F7.GS1
4 ETW000 1 entry for LDBNT~ imported (1FTI_TR_PL_CF *).
4 ETW000 0 d / 1 i / 0 u / 0 = 0% ucf LDBT~
4 ETW000 1 entry for LDBT~ imported (1FTI_TR_PL_CF).
4 ETW000 1 entry for TRDIRT~ inserted (SAPDBFTI_TR_POSITIONS 1*).
3WETW000 some text was mutilated during conversion from unicode to ascii in language '1'. This is the result: 'SP_JOTC ###############'
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '530050005f004a004f005400430020002000200020002000200020002000200020003a571659a44e13664d881f75a74ec1542000200020002000200020002000' -> 'SP_JOTC ###############'
4 ETW000 REPOT1SAPDBFTI_TR_POSITIONS A replaced.
4 ETW000 0 entries from D020T~ (SAPDBFTI_TR_POSITIONS %) deleted.
4 ETW000 0 entries from D021T~ (SAPDBFTI_TR_POSITIONS %) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSFXXX 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSNXXX 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSN001 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSSEL 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSSXXX 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSTOP 1%) deleted.
SAPup.ECO
Phase SHADOW_IMPORT_UPG1:
BLOCKED SIGNALS: ''
SAPup> Starting subprocess 2865 at 20110907101845
ENV: DIR_LIBRARY=/usr/sap/upgrade/upg_dir/abap/exenew
ENV: LD_LIBRARY_PATH=/usr/sap/upgrade/upg_dir/abap/exenew:/usr/sap/upgrade/upg_dir/jvm/jre/lib/amd64/server:/usr/sap/upgrade/upg_dir/jvm/jre/lib/amd64:/usr/sap/upgrade/upg_dir/jvm/jre/../lib/amd64:/usr/sap/GS1/SYS/exe/run:/oracle/GS1/102_64/lib
ENV: NLS_LANG=AMERICAN_AMERICA.WE8DEC
ENV: ORACLE_BASE=/oracle
ENV: ORACLE_HOME=/oracle/GS1/102_64
ENV: ORACLE_PSRV=GS1
ENV: ORACLE_SID=GS1
ENV: ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data
ENV: PATH=/usr/sap/upgrade/upg_dir/abap/exenew:/oracle/GS1/102_64/bin:.:/home/gs1adm:/usr/sap/GS1/SYS/exe/run:/opt/gcc295/bin:/opt/gnome/bin:/usr/games:/usr/bin/X11:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/global_lx/bin:/usr/global/bin
ENV: SAPSYSTEMNAME=GS1
ENV: auth_shadow_upgrade=0
ENV: dbms_type=ORA
ENV: dbs_ora_schema=SAPDAT
ENV: dbs_ora_tnsname=GS1
EXECUTING /usr/sap/upgrade/upg_dir/abap/exenew/tp (/usr/sap/upgrade/upg_dir/abap/exenew/tp) pf=/usr/sap/upgrade/upg_dir/abap/bin/SHDUPGIMP1.TPP put GS1
This is /usr/sap/upgrade/upg_dir/abap/exenew/tp version 376.03.38 (release 701)
This is /usr/sap/upgrade/upg_dir/abap/exenew/R3trans version 6.14 (release 701 - 03.06.11 - 17:57:00).
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
/usr/sap/upgrade/upg_dir/abap/exenew/R3trans finished (0008).
ERROR: stopping on error 8 during SHADOW IMPORT
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
stopping on error 8 during SHADOW IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 8
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 8
meaning:
A tool used by tp produced errors
Process with ID 2865 terminated with status 8
B.R
Lance.
Edited by: Yen on Sep 7, 2011 8:11 AMHello,
Following upg master was used -
51036889_1 BS 7 SR1 Upgrade Master 1/2
51036889_2 BS 7 SR1 Upgrade Master 2/2
And the kernel dvd used was NUC -
51036767_4 BS 7 SR1 Kernel 7.01
After successful upgrade to ecc6 EhP4, Unicode conversion was done later with UC kernel DVD (during IMPORT)
Thanks -
Hi All,
Iam getting this error while trying to change "com.sap.portal.navigation.masthead.par" within portal. I have updated the HeaderiView.jsp and then saved the PAR file and uploaded the file. It was successful upload from Administration console. But after I logged into portal again, I got this error and even though I tried to revert back the changes, it still gives the same error. Has any one faced similar issue? We faced this during the IE8 (Internet explorer 8) upgrade to SP 27 in sap portal.
Thanks.
#1.#0003BA4D72F200540000000300003DEA00049C4FAA821F4E#1297765883836#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#O000001496#192##n/a##bbf9eef438ee11e08722000035d6a152#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error##Java###10:31_15/02/11_903258450
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component :
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.pb.PageBuilder.createIviewProfile(PageBuilder.java:418)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:372)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:706)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.navigation.PortalLauncher.doOnNodeReady(PortalLauncher.java:218)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:547)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.sap.portal.navigation.Gateway.service(Gateway.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getDeploymentDescriptor(PortalApplicationItem.java:1622)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getConfiguration(PortalComponentItem.java:1022)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.refresh(PortalComponentItem.java:274)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:729)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 42 moreThanks Raghu.
I have tried that option as well. But, when I uploaded the PAR file from DEV to Sandbox environment, the header did not work, but I identified that the "portalapp.xml" file is only partially deployed (even though the PAR that is used for Upload (using Admin Console) contained all parameters. I could not understand why the portalapp.xml is only partially deployed.
After deployment the portalapp.xml has only 3 properties within it : ClassLoadingPolicy, value 5.0, DeploymentPolicy, value 5.0 and AuthenticationPolicy, value 5.0,
and all other attributes that are part of the uploaded par file are not present after deployment within "PAR directory within portalapps directory".
Edited by: jakk on Feb 16, 2011 5:17 PM
Edited by: jakk on Feb 16, 2011 5:19 PM -
Hi Experts,
I need some inputs to do SAP upgrade from 4.& to ECC 6.0.
Generally the steps involved in the Upgrade project?
What is the role of ABAPer in Upgrade project?
What us the role og Functional consultant in project?
How the configuration kind of stuff take care?
Can anyone send me the best document to understand the process..?
Regards,
Sekhar.JHi,
Upgrade Overview
The objective on SAP Technical version upgrade would be to bring in enhanced SAP functionality while retaining the custom development in the original system. The enhanced functionality is not necessarily implemented during the upgrade. The upgraded system is tested for all the functional scenarios existing in the original system and the custom objects are tested for its functioning as in the original system.
Upgrade project consists of 5 phases:
1. Project Preparation
2. Blueprinting
3. Realization
4. Production Preparation
5. Go Live & Support
ABAPer Role
a) Syntax Correction
b) Upgrade Correction (Replacement of obsolete statement)
c) BDC Program correction
d) BDC to BAPI conversion
e) Unicode testing using UCCHECK transaction
Functional consultant role
Unit Testing
Test Scripts preparations for Changes
Regards
Praneeth
Maybe you are looking for
-
Can't sync my ipad2, itunes quits, what's up?
I'm using windows 7 x 64 and all had been working until today I tried to sync my ipad2 and itunes through and error and shutdown. I then tried to work with itunes on my account (using windows 7) and even after verification of my account itunes would
-
Procedure to move highlighted files en masse to new folder
This procedure should be quite simple, but it escapes me! How can I move an entire group of highlighted files into a new folder?
-
Forms Builder 10g Crashes after opening R12 .fmb
Hi, I'm trying to open Oracle apps R12 .fmb from Oracle forms 10g(Forms [32 Bit] Version 10.1.2.0.2 ). It errors out with the following error : "Oracle forms Designer has stopped working". I checked metalink for this error no luck. Thanks, Kiran
-
Optical character recognition--how do I scan a document to text I can edit.
Optical character recognition--how do I scan a document to text I can edit?
-
Learn how to Cut the Grep, and win an Amazon gift card!
Hey SpiceHeads! We made it to Tuesday! That means you have officially survived the start of the week and have nearly made it to Wednesday! Congrats! But tell me are you tired of grepping through your logs to troubleshoot issues? Are you juggling vari