Configuring CHARM after solman migration

Hi,
We are going to migrate our existing Solman system to another system using system refresh, we have implemented CHARM which takes care of the Transport for our ECC and Portal Systems, my question is what needs to be done in the newly migrated system after the system refresh and what changes we need to make in our ECC System in order for CHARM to work in the newly migrated system.
Our landscape info
We have DEV,QA and Prod in our existing landscape with charm is configured in the Solman. Our Prod is the main domain controller and solman is the secondary domain controller, can some one explain me what needs to be done in the configuration after the system migration.
Sathish

Hi
Only hostname/ipaddress and SID name will be changed for solution manager. So for solution manager back RFC in ECC and EP systems you need to change hostname/ipaddress and instance number.
From SMSY try to update/read ECC and EP systems data. Check it is working fine or not.
Suman

Similar Messages

Reconfiguring CHARM after System Migration

Hi,
We are going to migrate our existing Solman system to another system using system refresh, we have implemented CHARM which takes care of the Transport for our ECC and Portal Systems, my question is what needs to be done in the newly migrated system after the system refresh and what changes we need to make in our ECC System in order for CHARM to work in the newly migrated system.
Our landscape info
We have DEV,QA and Prod in our existing landscape with charm is configured in the Solman. Our Prod is the main domain controller and solman is the secondary domain controller, can some one explain me what needs to be done in the configuration after the system migration.
Sathish

Hi,
Only hostname/ipaddress and SID name will be changed for solution manager. So for solution manager back RFC in ECC and EP systems you need to change hostname/ipaddress and instance number.
From SMSY try to update/read ECC and EP systems data. Check it is working fine or not.
Suman

Network adapter configuration error after quick migrate of stopped VM in 2012 r2 data-center edition 3 node cluster environment

We've got a couple of Windows 2012 r2 / Hyper-V 3 node clusters, and I have a problem with network adapters on them.
I have 3 node cluster all vm running fine on node 1 and 2 also quick and live migration very good between
node 1 and node 2, but no vm migrating on node 3. show "Network adapter configuration error".
If the VM is powered off, and I move it to 3rd
host (quick migration via Failover Cluster Manager), the network adapter loses its connection to the virtual switch - it turns to "Configuration Error"..if
manually change V switch of every VM then it worked only on 3rd node, and having same problem on node 1 and 2.
Quick migrate with the power off, and it fails to pick up the VSwitch on the3rd host.
Thanks
Shipon

Hi,
> I created a new VM via the Failover Cluster Manager (ie not via Hyper-V manager on one of the nodes).
Generally, this issue happens if a network adapter is added or removed on a highly available virtual machine using the Hyper-V manager console. Since the Hyper-V Manager console is not cluster aware, which means that configuration changes that are made to
virtual networks or virtual machines in the Hyper-V Manager console must be replicated to the other cluster nodes by using the “refresh virtual machine configuration” option in the Failover Cluster Manager console.
I know that “refresh virtual machine configuration” option is not needed if you change virtual machine settings using the Failover Cluster Manager console, but you may try to refresh the configuration of virtual machine to check the result.
In the Failover Cluster Manager console, expand Services and Applications, and then click the virtual machine for which you want to refresh the configuration.
In the Actions pane, scroll down, click More Actions and then click Refresh virtual machine configuration.
For more information please refer to following MS articles:
Refresh the Configuration of a Virtual Machine
http://technet.microsoft.com/en-us/library/dd759135.aspx
Highly Available Virtual Machines Lose Configuration Settings after Failover in Windows Server 2008 Failover Clusters
http://support.microsoft.com/kb/2000016
Hyper-V Live Migration fails on Windows Server 2008 R2 with Event ID 12080
http://support.microsoft.com/kb/2592237
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support

Role of old released transport after configuring charm

I want to configure charm 7.1 in solution manager 7.1 SP10 .how can i include released(old ) transports after charm configuration? please share your ideas about this.Thanks in advance

Hi
Only hostname/ipaddress and SID name will be changed for solution manager. So for solution manager back RFC in ECC and EP systems you need to change hostname/ipaddress and instance number.
From SMSY try to update/read ECC and EP systems data. Check it is working fine or not.
Suman

Application is throwing NSAPI and other errors after the migration

We started seeing NSAPI and other errors after the migration of new codes and recently make some changes
1) During the migration, all the 4 WLS cluster instances were bounced simultaneously. What is the best practice and recommendation from BEA Oracle? Do we need to bounce it one by one for any specific reason?
2) we recently introduced the 4th weblogic cluster instance on Solaris 10 zone. All other WLS instances are running on Solaris 8.
Is it okay to have two different OS versions( Solaris 8 and Solaris 10) and different hardware to host WLS cluster instances? Does BEA Oracle support this kind of configuration?
3) We are consistently seeing below errors in the iplanet web server error logs even though site is working fine
[11/Sep/2009:08:53:50] failure ( 4453): for host XX.XX.XX.XX trying to POST /servlet/FSO, wl-proxy reports: exception occurred for backend host 'YY.YY.YY.YY/23120/0': 'CONNECTION_REFUSED [os error=0, line 1732 of URL.cpp]: Error connecting to host YY.YY.YY.YY.YY:23120'
Do we need to upgrade our WLS proxy plugin? . Current version of WLS proxy plug-in is libproxy_61.so. Our Weblogic version is WLS 92 MP2
I'll really appreciate if some can anwsers those questions

OK booted in to Virtualbox, seems too be working fine this way, maybe it is the ATi drivers
any Help would be appreciated

Need help in configuring CHARM with R/3 System landscape with seven systems

Hi All,
we are planning to configure CHARM for our R/3 landscape.our current STMS includes seven systems.in the current STMS the transports flow as below.
D20->C20->C21->C22->C23->T20->P20
we require the transports to move in the same way as stated above even after CHARM is configured
1.please let me know if we can configure CHARM with seven systems.
2.if yes, how would the import happen( ie Action for import appears for all systems?).
Regards,
Anand Reddy

HI andy,
the transports will move in the following order.
D20(DEV)->C20(Consolidation)->C21(integ)->C22(reg)->C23(unit)->T20(final test)->P20(production)
transport will start in D20,then imported C20 followed by C21,C22,C23,T20 imports and finally reach P20
the systems are not in parallel they are one behind the other
Anand Reddy

CHARM in Solman

Hi
We are having the SOLMAN Version 4.0 SP13 system. As per my understanding the CHRAM can b eused for the following
1.Maintenance optimizer ( for downloading& implimenting support packages)
2, Maintnenance cycle(for enhancment or bug fix cycle)
3. TMS integration( Moving the transports to different systemsDEV-QAS-PRD)
4.Hot news ( to view and create OSS notes)
Asper the process we have to activate the ChaRM for the given Project (SOLAN_PROJECT_ADMIN) in the system landscape tab.
Query is
1.if i want to go for only Maint optimizer, still i need to activate this?
2. IfI want ot go for TMS & Hot news fucnitonality -do i need to activate CHARM ?
Thanks In Advance
Seeking your valuable inputs on this
Reagrds
Dinesh

Hello
As per my understanding from configuration point of view there is no dependency in customization of maintenance optimizer and charm. There is no need to activate charm for activating maintenance optimizer.
We have activated maintenance optimizer far before and never configured Charm for that reason.
But when you configure charm, you have the option to import support patches or notes through task list of charm.
Hope this will help;
Regards,
Sharmishtha

Handling Solution Manager changes with ChaRM (ChaRM on SolMan PRD)

Hi Experts,
Having deployed ChaRM to satellite system (three system landscape) we became interested in handling Solution Manager changes with ChaRM. We have operable ChaRM in SolMan 4.0 SP12.
We have DEV and PRD for SolMan so we are talking about two system landscape.
Has anyone of you done this? Does it go the same way as if SolMan was a real satellite system (rfc's=>tms=>ibase=>organization=>project=>MC=>CRs = order of configurations roughly).
I tried searching specific instructions for this deployment but it seems that configuration guides etc focus on satellite system handling. Our need is basically to document and control SolMan changes and with ChaRM we could.
Perhaps there is no magic to this and everything goes just like in satellite, but I would appreciate any experiences others may have had doing this.
Kind regards,
Auli

Hello,
We have implemented this with two systems landscape where in we have in place a Solution Manager Dev system and Solution manager Production system both are SOLMAN 4.0 with SP12. So the path for us to move the changes is from Development Systems to Production system.
We have ChaRM between the Dev and production. We reapplied the satellite system concept. For us the Solution manager Prod is a satellite systems all the changes that we move from Development system to Production systems is tracked with necessary documentation in the ChaRM process.
Yes, I agree with you that this is not any big magic. Working with two SOLMAN implementation, I strongly feel that SAP needs to have well rounded ChaRm processes. We have robust Change Management Process, but when we moved to ChaRM we were limited functionality of the ChaRM processes.
I had approached and did some research on how other companies are implementing the same process. Most of them have almost the same process for tracking SOLMAN changes. I am still look out for improved process to manage SOLMA changes.
Hope this helps!!! Thanks
Vish

Configuring ChaRM to unfinished pipeline (PRD yet missing)

Hi Experts,
We are working with SolMan 4.0 SP13 and have been succesfull in configuring ChaRM to 3 system pipelines. Now we are facing a situation where new pipeline is not yet finished but development and therefore transports need to be started.
I have a vaque memory of seing possibility to use a "placeholder" for systems that don't exist yet and then add them once they are available. Having searched notes and SDN I haven't been able to find a solution.
What we have now is DEV and QAS in the pipeline and we need to start trasnports between these two. PRD will be available later on in the spring and once it is, we would add it to ChaRM configuration. The request is to start using ChaRM for implementation and development.
Has anyone of you done this kind of ChaRM configuration? I'd be greatful for any hints you may give me.
Sincerelly,
Auli

Hi experts,
I found out that the "placeholder" is infact a virtual machine and that we should use before the pipeline is completed. I'm still worried that how can we replace the virtual machine in logical component, iBase and task lists and still be able to complete transport to production if we use the vm now.
Has anyone of you done a similar ChaRM configuration?
I would be very greatful for any advice you may give me on this matter!
Thank you in advance!
BR,
Auli

System performance degrades after server migration ???

Hi Friends,
System performance degrades after we migrate our BW 3.5 Server (Production) from UK to Germany.
for details :
1. Data is coming to Informatica server from Informatica its going to POSDM Server (Point of Sales Data Management) from POSDM we are running pipes and data is coming to BW (Delta Queqe)
so before Server Migration it was taking 2 Hrs to load 4 Million Records
After Server Migration it is taking 4 Hrs.
Please help out to find the reason for this.
Note : Server Ram , Hard Disk , Speed is same on both Servers
Thanks
Asim

Note : Server Ram , Hard Disk , Speed is same on both Servers
Are you cahnge any application or database parameter (the OS and all patch'es are the same?)
How you doing migration? Very low information... Are you check the network configuration are the same( for example check the network speed 1G or 100MB).
Are you trying to analyse the St03N and St04 t-codes?
Regards.

Pre-requisites and steps to configure ChaRM and SDA

HI ,
We are implementing the Solman EHP1 with configuration of ChaRm and SDA , I need pre-requisite to configure ChaRm and SDA . Request your help on this .
Thanks,
Om

hi,
best way to start charm using this forum
First steps to work with Change Request Management scenario in SAP Solution Manager 7.0
and other related links for charm scenarios are here on this wiki
http://wiki.sdn.sap.com/wiki/display/SM/WeblogsrelatedtoSolutionManager check out the below topics
Change Request Management scenario: Usual questions
Change Request Management scenario: Working examples
Change Request Management scenario: Working examples "Development without Release" phase
Change Request Management scenario: Working examples "Development with Release" phase
Change Request Management scenario: Working examples "Test" phase
Change Request Management scenario: Working examples "Emergency Correction" phase
Change Request Management scenario: Working examples "Go-Live" phase
Change Request Management scenario: Working examples "Being Completed" and "Completed" phase
Change Request Management scenario: Working examples Final Points and Appendix
Thanks
Jansi

Invalids Objects after DB Migration

Hi,
I got lot of invalid objects after DB migration, Before export i droped apps/edw db links in source, after import in new target system i can see lot of invalid objects
alter VIEW APPLSYS.AQ$WF_CONTROL compile;
alter VIEW APPLSYS.AQ$_WF_CONTROL_F compile;
alter VIEW APPS.EUL5_B080110101824Q8V1 compile;
alter VIEW APPS.EUL5_B080110140308Q1V1 compile;
alter VIEW APPS.EUL5_B080110101824Q1V1 compile;
alter VIEW APPS.EUL5_B080110142754Q5V1 compile;
alter VIEW APPS.EUL4_B050720090637Q1V1 compile;
alter VIEW APPS.EUL5_B080110101824Q5V1 compile;
alter VIEW APPS.EUL5_B080110101824Q7V1 compile;
alter VIEW APPS.EUL5_B080110105519Q8V1 compile;
alter VIEW APPS.EUL4_B050225111630Q1V1 compile;
alter VIEW APPS.EUL5_B080827104717Q2V1 compile;
alter VIEW APPS.EUL5_B080827104041Q1V1 compile;
alter VIEW APPS.EUL5_B080825171948Q1V1 compile;
alter VIEW APPS.EUL5_B080827104041Q3V1 compile;
alter VIEW APPS.EUL4_B070517133406Q3V1 compile;
alter VIEW APPS.EUL4_B060516094902Q1V1 compile;
alter VIEW APPS.EUL5_B080110101824Q2V1 compile;
alter VIEW APPS.EUL5_B080110105519Q7V1 compile;
alter VIEW APPS.EUL4_B040914132829Q1V1 compile;
alter PACKAGE APPS.ENG_CHANGE_TEXT_UTIL compile;
alter VIEW APPS.EUL5_B080110105519Q6V1 compile;
alter VIEW APPS.EUL4_B070517133406Q1V1 compile;
alter VIEW APPS.EUL4_B041230091230Q1V1 compile;
alter VIEW APPS.EUL5_B080110105519Q4V1 compile;
alter VIEW APPS.EUL4_B050720092221Q1V1 compile;
alter VIEW APPS.EUL4_B050225111545Q1V1 compile;
alter VIEW APPS.EUL5_B080110105519Q5V1 compile;
alter VIEW APPS.EUL4_B070108141912Q1V1 compile;
alter VIEW APPS.EUL5_B080110142754Q4V1 compile;
alter VIEW APPS.EUL5_B080110142754Q1V1 compile;
alter VIEW APPS.EUL5_B080110142754Q2V1 compile;
alter VIEW APPS.EUL5_B080110101824Q4V1 compile;
alter PACKAGE APPS.EGO_ITEM_TEXT_UTIL compile;
alter package APPS.CS_WF_ACTIVITIES_PKG compile body;
alter package APPS.CS_SR_ADDR_SYNC_INDEX_PKG compile body;
alter package APPS.BOMPKMUD compile body;
alter package APPS.ICX_POR_INTERMEDIA_INDEX compile body;
alter package APPS.CS_KB_CONC_PROG_PKG compile body;
alter package APPS.OF_PA_PKG compile body;
alter package APPS.AD_PARALLEL_UPDATES_PKG compile body;
alter package APPS.CE_BANK_PURGINGS compile body;
alter package APPS.OE_CREDIT_CARD_MIGRATE_UTIL compile body;
alter package APPS.OKS_CCENCRYPTION_PKG compile body;
alter package APPS.OKC_RISK_EVENTS_PKG compile body;
alter package APPS.OKC_REP_CONTACT_ROLES_PKG compile body;
alter package APPS.JTF_TASK_IDX_UTL compile body;
alter package APPS.ENI_DENORM_HRCHY compile body;
alter package APPS.EGO_ITEM_TEXT_PVT compile body;
alter package APPS.EGO_ITEM_TEXT_UTIL compile body;
alter package APPS.EDW_POA_LN_TYPE_M_C compile body;
alter package APPS.EDW_POA_SPLRITEM_M_C compile body;
alter package APPS.EDW_GEOGRAPHY_M_C compile body;
alter package APPS.RA_CUSTOMER_TEXT_PKG compile body;
alter package APPS.OPI_EDW_UOM_CONV_F_C compile body;
alter package APPS.EDW_OPI_PRDL_M_C compile body;
alter package APPS.EDW_OPI_LOT_M_C compile body;
alter package APPS.EDW_OPI_ACTV_M_C compile body;
alter package APPS.EDW_OPI_OPRN_M_C compile body;
alter package APPS.OPI_EDW_OPMINV_DAILY_STAT_F_C compile body;
alter package APPS.OPI_EDW_OPMCOGS_F_C compile body;
alter package APPS.OPI_EDW_OPM_JOB_DETAIL_F_C compile body;
alter package APPS.OPI_EDW_OPM_JOB_RSRC_F_C compile body;
alter package APPS.OPI_EDW_COGS_F_C compile body;
alter package APPS.EDW_MTL_INVENTORY_LOC_M_C compile body;
alter package APPS.ISC_EDW_BOOK_SUM1_F_C compile body;
alter package APPS.FND_OID_DIAG compile body;
alter VIEW APPS.EUL5_B090911130003Q2V1 compile;
alter VIEW APPS.EUL5_B090911130003Q1V1 compile;
alter VIEW APPS.EUL5_B090910161600Q2V1 compile;
alter VIEW APPS.EUL5_B090910161600Q1V1 compile;
alter VIEW APPS.EUL5_B090910090134Q2V1 compile;
alter VIEW APPS.EUL5_B090910090134Q1V1 compile;
alter VIEW APPS.EUL5_B090701170823Q3V1 compile;
alter VIEW APPS.EUL5_B090701170823Q2V1 compile;
alter VIEW APPS.EUL5_B090701170823Q1V1 compile;
alter VIEW APPS.EUL5_B090701170628Q3V1 compile;
alter VIEW APPS.EUL5_B090701170628Q2V1 compile;
alter VIEW APPS.EUL5_B090701170628Q1V1 compile;
alter VIEW APPS.EUL5_B090701162946Q3V1 compile;
alter VIEW APPS.EUL5_B090701162946Q2V1 compile;
alter VIEW APPS.EUL5_B090701162946Q1V1 compile;
alter VIEW APPS.EUL5_B090629085441Q1V1 compile;
alter VIEW APPS.EUL5_B080109163823Q5V1 compile;
alter VIEW APPS.EUL5_B081014161934Q1V1 compile;
alter VIEW APPS.EUL5_B080827104041Q2V1 compile;
alter VIEW APPS.EUL5_B080826171658Q1V1 compile;
alter VIEW APPS.EUL5_B080827104717Q1V1 compile;
alter VIEW APPS.EUL5_B080827091711Q1V1 compile;
alter VIEW APPS.EUL5_B081014085038Q1V1 compile;
alter VIEW APPS.EUL5_B080826171630Q1V1 compile;
alter VIEW APPS.EUL5_B080827091711Q2V1 compile;
alter VIEW APPS.EUL5_B080110101824Q6V1 compile;
alter VIEW APPS.EUL4_B040903135303Q1V1 compile;
alter VIEW APPS.EUL5_B080109163823Q4V1 compile;
alter VIEW APPS.EUL5_B080110105519Q1V1 compile;
alter VIEW APPS.EUL5_B080110105519Q2V1 compile;
alter VIEW APPS.EUL5_B080110142754Q6V1 compile;
alter package APPS.ICX_CAT_INTERMEDIA_INDEX_PVT compile body;
alter package APPS.ARP_STAX_88 compile body;
alter package APPS.ARP_STAX_82 compile body;
alter package APPS.ARP_STAX_86 compile body;
alter package APPS.ARP_STAX_85 compile body;
alter package APPS.ARP_STAX_84 compile body;
alter package APPS.ENG_CHANGE_LINE_UTIL compile body;
alter package APPS.ENG_CHANGE_ACTIONS_PKG compile body;
alter package APPS.ENG_LAUNCH_ECO_OI_PK compile body;
alter package APPS.EDW_MRP_PLAN_M_C compile body;
alter package APPS.EDW_MRP_FORECAST_M_C compile body;
alter package APPS.EDW_MRP_DM_CLS_M_C compile body;
alter package APPS.CS_SR_SYNC_INDEX_PKG compile body;
alter package APPS.OKE_DELIVERABLE_UTILS_PUB compile body;
alter package APPS.OKE_DELIVERABLE_UTILS_PKG compile body;
alter package APPS.EDW_ORGANIZATION_M_C compile body;
alter package APPS.EDW_HR_MVMNT_TYP_M_C compile body;
alter package APPS.HR_EDW_WRK_CMPSTN_F_C compile body;
alter package APPS.EDW_HR_RQN_VCNCY_M_C compile body;
alter package APPS.EDW_HR_REASON_M_C compile body;
alter package APPS.EDW_HR_REC_ACT_M_C compile body;
alter package APPS.EDW_HR_PRSN_TYP_M_C compile body;
alter package APPS.EDW_HR_POSITION_M_C compile body;
alter package APPS.EDW_HR_SERVICE_M_C compile body;
alter package APPS.EDW_HR_GRADE_M_C compile body;
alter package APPS.EDW_HR_JOBS_M_C compile body;
alter package APPS.EDW_HR_ASSGNMNT_M_C compile body;
alter package APPS.EDW_HR_AGE_BAND_M_C compile body;
alter package APPS.EDW_HR_ASG_CHNG_M_C compile body;
alter package APPS.FII_PA_BUDGET_F_C compile body;
alter package APPS.FII_PA_REVENUE_F_C compile body;
alter package APPS.FII_PA_UOM_CONV_F_C compile body;
alter package APPS.FII_PA_COST_F_C compile body;
alter package APPS.FII_AR_E_REVENUE_F_C compile body;
alter package APPS.FII_AR_TRX_DIST_F_C compile body;
alter package APPS.FII_AP_SCH_PAYMTS_F_C compile body;
alter package APPS.FII_AP_INV_LINES_F_C compile body;
alter package APPS.FII_AP_INV_PAYMTS_F_C compile body;
alter package APPS.FII_AP_INV_ON_HOLD_F_C compile body;
alter package APPS.FII_AP_HOLD_DATA_F_C compile body;
alter package APPS.HZ_PURGE compile body;
alter package APPS.AR_CMGT_DATA_POINTS_PKG compile body;
alter package APPS.AR_CMGT_AGING compile body;
alter package APPS.ENG_CHANGE_TEXT_PVT compile body;
alter package APPS.ENG_CHANGE_TEXT_UTIL compile body;
alter package APPS.AP_WEB_MANAGEMENT_REPORTS_PKG compile body;
alter package APPS.OKC_REP_RELATIONSHIPS_PKG compile body;
alter package APPS.AZ_R12_TRANSFORM_CASCADE compile body;
alter package APPS.AZ_COMP_REPORTER compile body;
alter package APPS.IRC_POSTING_CONTENT_API compile body;
alter package APPS.IRC_DOCUMENT_API compile body;
alter package APPS.HZ_PARTY_STAGE compile body;
alter package APPS.HZ_DQM_SYNC compile body;
alter package APPS.OKE_AGREEMENT_PVT compile body;
alter package APPS.OKC_TEMPLATE_KEYWORD_PVT compile body;
alter package APPS.OKC_DELIVERABLE_PROCESS_PVT compile body;
alter package APPS.OKC_ARTICLE_KEYWORD_PVT compile body;
alter package APPS.OKC_TERMS_COPY_GRP compile body;
alter package APPS.INVPOPIF compile body;
alter package APPS.IBC_IMT_PUB compile body;
alter package APPS.FND_IMUTL compile body;
alter package APPS.ENG_ECO_UTIL compile body;
alter VIEW CLM.CLM_CLMRMCM1_VIEW compile;
alter VIEW CLM.CLM_CLMRMMS1_VIEW compile;
alter VIEW CLM.CLM_CLMRMVS1_VIEW compile;
alter VIEW CLM.CLM_CLMRMUS1_VIEW compile;
alter VIEW CLM.CLM_CLMRMSG1_VIEW compile;
alter VIEW CLM.CLM_CLMRMRS1_VIEW compile;
alter VIEW CLM.CLM_CLMRMRP1_VIEW compile;
alter VIEW CLM.CLM_CLMRMRG1_VIEW compile;
alter VIEW CLM.CLM_CLMRMPT1_VIEW compile;
alter VIEW CLM.CLM_CLMRMPO1_VIEW compile;
alter VIEW CLM.CLM_CLMRMOW1_VIEW compile;

alter VIEW CLM.CLM_CLMRMGM1_VIEW compile;
alter VIEW CLM.CLM_CLMRMFS1_VIEW compile;
alter VIEW CLM.CLM_CLMRMFN1_VIEW compile;
alter VIEW CLM.CLM_CLMRMFD1_VIEW compile;
alter VIEW CLM.CLM_CLMRMDF1_VIEW compile;
alter VIEW CLM.CLM_CLMRMCP1_VIEW compile;
alter VIEW CLM.CLM_CLMRMCL1_VIEW compile;
alter VIEW CONV.TEST_1 compile;
alter VIEW DMUSER.GL_JE_LINES_V compile;
alter VIEW DMUSER.GL_JE_CATEGORIES_TL_V compile;
alter VIEW NOETIX.NOETIX_SEARCHBY_CANDIDATES compile;
alter package OBT_AA.PA_EXPENDITURE_INQUIRY compile body;
alter package OBT_AA.PO_CORE_S compile body;
alter package OBT_AA.OBTPA_AP_PO_FLEX_PURGEUTL_PVT compile body;
alter package OBT_AA.PO_INQ_SV compile body;
alter package OBT_AA.PA_PROJECT_PUB compile body;
alter package OBT_AA.PA_PROJECT_PVT compile body;
alter package OBT_AA.PA_CONTROL_API_PVT compile body;
alter package OBT_AA.PA_CONTROL_API_PUB compile body;
alter package OBT_AA.PA_PROJECT_CHECK_PVT compile body;
alter package OBT_AA.RCV_QUANTITIES_S compile body;
alter package OBT_AA.PA_RESOURCE_PUB compile body;
alter package OBT_AA.PO_VALIDATE_CAI compile body;
alter package OBT_AA.OF_PA_PKG compile body;
alter package OBT_AA.OBTPA_AP_PO_FLEX_PROCS compile body;
alter package OBT_AA.ARP_STAX_88 compile body;
alter package OBT_AA.ARP_STAX_86 compile body;
alter package OBT_AA.ARP_STAX_82 compile body;
alter package OBT_AA.ARP_STAX_84 compile body;
alter package OBT_AA.ARP_STAX_85 compile body;
alter package OBT_AA.EGO_ITEM_TEXT_UTIL compile body;
alter package OBT_AA.ENG_CHANGE_TEXT_UTIL compile body;
alter package OBT_AA.PA_EVENT_PVT compile body;
alter package OBT_AA.PA_EVENT_PUB compile body;
alter package OBT_AA.OBTPA_AP_PO_FLEX_AP_PURGE_PKG compile body;
alter package OBT_AA.PA_INTERFACE_UTILS_PUB compile body;
alter package OBT_AA.OF_ID_PKG compile body;
alter package OBT_AA.AP_INVOICES_PKG compile body;
alter package OBT_AA.OBTPA_AP_PO_FLEX_RCV_PURGE_PVT compile body;
alter package OBT_AA.AP_INVOICES_UTILITY_PKG compile body;
alter package OBT_AA.GBLWF_PO_AG compile body;
alter package OBT_AA.AP_INVOICE_PAYMENTS_PKG compile body;
alter package OBT_AA.FND_GFM compile body;
alter package OBT_AA.OBTPA_AP_PO_FLEX_PURGE_PVT compile body;
alter package OBT_AA.GL_CI_REMOTE_INVOKE_PKG compile body;
alter package OBT_AA.OBTPA_AP_PO_FLEX_PURGE_GRP compile body;
alter package OBT_AA.FND_ATTACHMENT_UTIL_PKG compile body;
alter package OBT_AA.POLOAD_CAI compile body;
alter package OBT_AA.POLOAD2_CAI compile body;
alter package OBT_AA.POLOAD1_CAI compile body;
alter package OBT_AA.OBTPA_CUSTOM_APPO_FLEX_PROCS compile body;
alter VIEW OBT_AA.PO_REQUISITION_HEADERS_REQ_V compile;
alter VIEW OBT_AA.RCV_VRC_TXS_VEND_V compile;
alter VIEW OBT_AA.ICX_POR_SES_REQS_V compile;
alter VIEW OBT_AA.ADI_WEB_FILES_VL compile;
alter VIEW OBT_AA.POR_ATTACHMENTS_SUMMARY_V compile;
alter VIEW OBT_AA.WIP_OPERATION_INSTRUCTIONS_V compile;
alter VIEW OBT_AA.WIP_ENTITY_COMMENTS_V compile;
alter VIEW OBT_AA.WIP_COMMENT_CODES_V compile;
alter VIEW OBT_AA.XLA_OKL_AEL_GL_TRX_V compile;
alter VIEW OBT_AA.XLA_OKL_AEL_GL_QTE_V compile;
alter VIEW OBT_AA.XLA_OKL_AEL_GL_CTR_V compile;
alter VIEW OBT_AA.OKL_AEL_GL_QTE_V compile;
alter VIEW OBT_AA.OKL_POOL_SRCH_V compile;
alter VIEW OBT_AA.CE_CP_DISC_V compile;
alter VIEW OBT_AA.OKL_POOL_SRCH_PAYFREQ_V compile;
alter VIEW OBT_AA.XLA_OKL_AEL_GL_AST_V compile;
alter VIEW OBT_AA.OKL_AM_ASSET_RETURNS_UV compile;
alter VIEW OBT_AA.IGI_EXP_DUS_V compile;
alter VIEW OBT_AA.OKL_AEL_GL_TRX_V compile;
alter VIEW OBT_AA.OKL_AEL_GL_CTR_V compile;
alter VIEW OBT_AA.CE_CP_DISC_SURPLUS_V compile;
alter VIEW OBT_AA.CUN_ITEM_NETWORK_UNITS_V compile;
alter VIEW OBT_AA.PA_FCST_PERIODIC_HDR_V compile;
alter VIEW OBT_AA.PA_FCST_PERIODIC_DTL_V compile;
alter VIEW OBT_AA.OTA_FINANCE_LINES_V compile;
alter VIEW OBT_AA.PA_ADW_LOWTSK_ACT_CMT_V compile;
alter VIEW OBT_AA.OKL_EBIZ_KHEADERS_V compile;
alter VIEW OBT_AA.OKL_CURE_RFND_VND_DTLS_UV compile;
alter VIEW OBT_AA.OKL_CURE_CONTRACT_UV compile;
alter VIEW OBT_AA.OKL_BPD_RECEIPT_ASSET_UV compile;
alter VIEW OBT_AA.OKL_BPD_RECEIPT_APPLIC_UV compile;
alter VIEW OBT_AA.CUN_ASSET_ADDITIONS_UNITS_V compile;
alter VIEW OBT_AA.ICX_PO_ACTION_HISTORY_PK_V compile;
alter VIEW OBT_AA.CST_PAC_WIP_TXN_V compile;
alter VIEW OBT_AA.PO_RELEASE_XML compile;
alter VIEW OBT_AA.PO_RELEASE_ARCHIVE_XML compile;
alter VIEW OBT_AA.PO_LINE_LOCATIONS_XML compile;
alter VIEW OBT_AA.PO_LINE_LOCATIONS_ARCHIVE_XML compile;
alter VIEW OBT_AA.PO_LINES_XML compile;
alter VIEW OBT_AA.PO_LINES_ARCHIVE_XML compile;
alter VIEW OBT_AA.PO_HEADERS_XML compile;
alter VIEW OBT_AA.OTFV_FINANCE_LINES compile;
alter VIEW OBT_AA.PO_HEADERS_ARCHIVE_XML compile;
alter VIEW OBT_AA.OKL_BPD_AP_DISB_DTL_LN_UV compile;
alter VIEW OBT_AA.OKL_BPD_AP_DISBURS_SMRY_UV compile;
alter VIEW OBT_AA.OKL_ACCOUNT_BALANCES_V compile;
alter VIEW OBT_AA.OKL_AEL_GL_AST_V compile;
alter VIEW OBT_AA.CUN_PROJECT_SHIPMENT_V compile;
alter VIEW OBT_AA.PO_POS_ALL_V compile;
alter VIEW OBT_AA.PA_PROJ_COMMITMENT_STATUS compile;
alter VIEW OBT_AA.OKL_VP_AGREEMENT_UV compile;
alter VIEW OBT_AA.OKL_TRX_HEADER_UV compile;
alter VIEW OBT_AA.OKL_FA_DIST_UV compile;
alter VIEW OBT_AA.PO_DOCUMENT_HEADERS_VIEW compile;
alter VIEW OBT_AA.PO_ACTION_HISTORY_V compile;
alter VIEW OBT_AA.OKL_BPD_AP_DISB_DTLS_UV compile;
alter VIEW OBT_AA.MRP_SR_VIEW_REC_V compile;
alter VIEW OBT_AA.CUN_TRANSACTION_HIST_V compile;
alter VIEW OBT_AA.CUN_ITEM_SUMMARY_V compile;
alter VIEW OBT_AA.CE_CP_DISC_CLOSE_V compile;
alter VIEW OBT_AA.PA_RPT_PRJ_SUMMARY compile;
alter VIEW OBT_AA.PA_RPT_CUST_SUMMARY compile;
alter VIEW OBT_AA.PA_PROJECT_LISTS_PORTLET_V compile;
alter VIEW OBT_AA.PA_FCST_PROJECT_HDR_V compile;
alter VIEW OBT_AA.PA_FCST_PROJECT_SUM_V compile;
alter VIEW OBT_AA.PA_FCST_PROJECT_DTL_V compile;
alter VIEW OBT_AA.PA_FCST_PERIODIC_SUM_V compile;
alter VIEW OBT_AA.PA_ADW_TOPTSK_ACT_CMT_V compile;
alter VIEW OBT_AA.OKL_CURE_REFUNDS_DTLS_UV compile;
alter VIEW OBT_AA.OKL_OUTSTANDING_CURE_UV compile;
alter VIEW OBT_AA.OKL_CURE_RULE_UV compile;
alter VIEW OBT_AA.OKL_AP_TRX_LINE_UV compile;
alter VIEW OBT_AA.OKL_AP_DIST_UV compile;
alter VIEW OBT_AA.CUN_ASSET_UNITS_V compile;
alter VIEW OBT_AA.GMS_COMMITMENT_TXNS_V compile;
alter VIEW OBT_AA.GMS_STATUS_PROJ_GENERIC_V compile;
alter VIEW OBT_AA.CE_CP_DISC_NET_V compile;
alter VIEW OBT_AA.XLA_WIP_AEL_SL_V compile;
alter VIEW OBT_AA.XLA_AP_AEL_SL_V compile;
alter VIEW OBT_AA.WIP_EAM_REQUIREMENTS_ALL_V compile;
alter VIEW OBT_AA.XLA_WIP_AEL_SL_PAC_V compile;
alter VIEW OBT_AA.XLA_PSA_PO_ENC_BC_GL_V compile;
alter VIEW OBT_AA.PA_STATUS_COMMITMENTS_V compile;
alter VIEW OBT_AA.XLA_WIP_AEL_GL_V compile;
alter VIEW OBT_AA.XLA_WIP_AEL_GL_PAC_V compile;
alter VIEW OBT_AA.XLA_REQ_ENC_AEL_GL_V compile;
alter VIEW OBT_AA.XLA_PSA_REQ_ENC_BC_GL_V compile;
alter VIEW OBT_AA.XLA_PO_ENC_AEL_GL_V compile;
alter VIEW OBT_AA.XLA_PO_AEL_SL_V compile;
alter VIEW OBT_AA.XLA_PO_AEL_SL_PAC_V compile;
alter VIEW OBT_AA.XLA_PO_AEL_SL_MRC_V compile;
alter VIEW OBT_AA.XLA_PO_AEL_GL_V compile;
alter VIEW OBT_AA.XLA_PO_AEL_GL_PAC_V compile;
alter VIEW OBT_AA.XLA_INV_AEL_SL_V compile;
alter VIEW OBT_AA.XLA_INV_AEL_SL_PAC_V compile;
alter VIEW OBT_AA.RCV_ENTER_RECEIPTS_V compile;
alter VIEW OBT_AA.RCV_ENTER_RECEIPTS_SUP_INT_V compile;
alter VIEW OBT_AA.PO_TAX_SHIPMENTS_DETAIL_V compile;
alter VIEW OBT_AA.PO_TAX_CODES_SUMMARY_V compile;
alter VIEW OBT_AA.RCV_ENTER_RECEIPTS_INTERNAL_V compile;
alter VIEW OBT_AA.PO_RFQS_VAL_V compile;
alter VIEW OBT_AA.PN_INDEX_EXCLUDE_TERM_V compile;
alter VIEW OBT_AA.PO_RFQS_ALL_V compile;
alter VIEW OBT_AA.PA_STATUS_PROJ_TOTALS_V compile;
alter VIEW OBT_AA.PA_SST_VIEW_PROJECTS_TASKS_V compile;
alter VIEW OBT_AA.PA_RPT_PRJ_SUMMARY_BASE_V compile;
alter VIEW OBT_AA.PA_RPT_CUST_SUMMARY_BASE_V compile;
alter VIEW OBT_AA.PA_REP_PROJ_SP_PA_V compile;
alter VIEW OBT_AA.PA_REP_PROJ_SP_GL_V compile;
alter VIEW OBT_AA.PA_INV_BURDEN_DETAILS_LM_V compile;
alter VIEW OBT_AA.PA_ADW_R_ST_ACT_CMT_V compile;
alter VIEW OBT_AA.PA_ADW_R_ACT_CMT_V compile;
alter VIEW OBT_AA.PA_ADW_ACT_CMT_V compile;
alter VIEW OBT_AA.OKL_REFUND_UV compile;
alter VIEW OBT_AA.OKL_K_VENDOR_PROGRAMS_UV compile;
alter VIEW OBT_AA.OKL_C_V_RULES_UV compile;
alter VIEW OBT_AA.OKL_CS_PARTIES_TAB_UV compile;
alter VIEW OBT_AA.OKL_CURE_VENDOR_PROGRAM_UV compile;
alter VIEW OBT_AA.OKL_CS_ALL_PARTIES_W_AMOUNT_UV compile;
alter VIEW OBT_AA.OKL_BPD_DISB_CONTRACT_LOV_UV compile;
alter VIEW OBT_AA.GMS_STATUS_COMMITMENTS_V compile;
alter VIEW OBT_AA.CUN_ITEMS_V compile;
alter VIEW OBT_AA.CSP_REQUIRED_PARTS_V compile;
alter VIEW OBT_AA.CSP_DC_PARTS_V compile;
alter VIEW OBT_AA.MRP_SR_RECEIPT_ORG_V compile;
alter VIEW OBT_AA.MRP_I2_RESCHED_PO_REQ_V compile;
alter VIEW OBT_AA.RCV_RECEIVERS_UNORDERED_V compile;
alter VIEW OBT_AA.JG_PO_REL_TAX_LINES_SUMMARY_V compile;
alter VIEW OBT_AA.PN_TERM_TEMPLATES_V compile;
alter VIEW OBT_AA.PJM_PROJECT_PROJ_SUMMARY_V compile;
alter VIEW OBT_AA.PA_REQUIREMENTS_AMG_V compile;
alter VIEW OBT_AA.PA_REP_RES_CAP_WKD_V compile;
alter VIEW OBT_AA.PA_REP_RES_AVL_WK_V compile;
alter VIEW OBT_AA.PA_PROJ_SUMMARY_AMOUNTS_V compile;
alter VIEW OBT_AA.PA_PROJ_COMMITMENT_BASE_VIEW compile;
alter VIEW OBT_AA.PA_REP_ASMT_DTS_V compile;
alter VIEW OBT_AA.PA_PROJ_ASSIGNMENTS_AMG_V compile;
alter VIEW OBT_AA.PA_PROJECT_OPEN_ASSNS_STAFF_V compile;
alter VIEW OBT_AA.PA_PROJECT_OPEN_ASSNS_V compile;
alter VIEW OBT_AA.PA_PROJECT_LISTS_USER_V compile;
alter VIEW OBT_AA.PA_PROJECT_ASSIGNMENTS_V compile;
alter VIEW OBT_AA.PA_FCST_PROJECT_LIST_V compile;
alter VIEW OBT_AA.PA_PROJECTS_CUST_360_V compile;
alter VIEW OBT_AA.PA_C_RES_DETAILS_V compile;
alter VIEW OBT_AA.OKL_FUND_REQ_HEADERS_UV compile;
alter VIEW OBT_AA.OKL_CURE_REFUNDS_SUMRY_UV compile;
alter VIEW OBT_AA.OKL_CURE_VENDOR_SUMRY_UV compile;
alter VIEW OBT_AA.OKL_BPD_DISB_LOV_UV compile;
alter VIEW OBT_AA.AP_EXPENSE_REPORT_HISTORY_V compile;
alter VIEW OBT_AA.OKC_K_ATE_V compile;
alter VIEW OBT_AA.AX_MTL_MATERIAL_TRANS_CONV_V2 compile;
alter VIEW OBT_AA.AHL_OSP_ORDER_LINES_V compile;
alter VIEW OBT_AA.OKC_KOL_ATTACHMENTS_V compile;
alter VIEW OBT_AA.AMW_EXPORT_PROCESS_V compile;
alter VIEW OBT_AA.OKI_K_CONTACTS_V compile;
alter VIEW OBT_AA.OKE_K_ALL_ACCESS_V compile;
alter VIEW OBT_AA.OKC_KOL_SEARCH_KHEADERS_V compile;
alter VIEW OBT_AA.ICX_REQ_SUPPLIERS_V compile;
alter VIEW OBT_AA.ICX_REQ_DIST_HEADER_V compile;
alter VIEW OBT_AA.ICX_PO_RFQ_LINE_LOC_V compile;
alter VIEW OBT_AA.ICX_PO_REQ_HEADERS_V compile;
alter VIEW OBT_AA.ICX_PO_REQS_BY_USERS_V compile;
alter VIEW OBT_AA.ICX_AP_EXPENSE_LINES_V compile;
alter VIEW OBT_AA.ICX_ENG_WEB_SCHEDULE_PO_V compile;
alter VIEW OBT_AA.ICX_PO_OPEN_REQS_BY_USERS_V compile;
alter VIEW OBT_AA.GMS_COMMITMENT_BURDEN_V compile;
alter VIEW OBT_AA.GMS_1034_REPORT_V compile;
alter VIEW OBT_AA.FV_ECS_PAYMENT_V compile;
alter VIEW OBT_AA.FII_AP_IVSR_INV_SOURCE_LCV compile;
alter VIEW OBT_AA.EAM_DIRECT_ITEM_RECS_V compile;
alter VIEW OBT_AA.ECE_PO_PROJECT_INFO_V compile;
alter VIEW OBT_AA.CST_PAC_AEL_SL_WIP_V compile;
alter VIEW OBT_AA.CST_AEL_SL_WIP_V compile;
alter VIEW OBT_AA.CE_REVERSAL_TRANSACTIONS_V compile;
alter VIEW OBT_AA.CHV_SCHEDULERS_VAL_V compile;
alter VIEW OBT_AA.CE_RECONCILED_TRANSACTIONS_V compile;
alter VIEW OBT_AA.CE_AVAILABLE_TRANSACTIONS_V compile;
alter VIEW OBT_AA.CE_FC_API_DISC_V compile;
alter VIEW OBT_AA.AMW_EXPORT_AUDIT_PROCEDURE_V compile;
alter VIEW OBT_AA.AP_AEL_SL_V compile;
alter VIEW OBT_AA.MRP_SCATP_SOURCES_V compile;
alter VIEW OBT_AA.MRP_I2_PROCUREMENT_V compile;
alter VIEW OBT_AA.MRP_I2_PART_SUPPLIER_V compile;
alter VIEW OBT_AA.IGI_CIS_PMT_VCH_V compile;
alter VIEW OBT_AA.XTR_AP_OPEN_TRX_V compile;
alter VIEW OBT_AA.WIP_OSP_REQS_POS_V compile;
alter VIEW OBT_AA.WIP_ICX_OSP_WORKBENCH_V compile;
alter VIEW OBT_AA.WIP_BIS_PROD_VAL_EMP_V compile;
alter VIEW OBT_AA.REQ_ENC_AEL_GL_V compile;
alter VIEW OBT_AA.RCV_VIEW_INTERFACE_V compile;
alter VIEW OBT_AA.RCV_MSH_V compile;
alter VIEW OBT_AA.RCV_AEL_SL_MRC_V compile;
alter VIEW OBT_AA.RCV_ENTER_RECEIPTS_INVENTORY_V compile;
alter VIEW OBT_AA.RCV_AEL_SL_V compile;
alter VIEW OBT_AA.RCV_ENTER_RECEIPTS_INT_REQ_V compile;
alter VIEW OBT_AA.RCV_AEL_GL_V compile;
alter VIEW OBT_AA.PSA_REQ_ENC_GL_BC_V compile;
alter VIEW OBT_AA.PO_REQEXPRESS_LINES_V compile;
alter VIEW OBT_AA.PO_RFQ_HEADERS_PRINT compile;
alter VIEW OBT_AA.PO_REQS_IN_TRANSIT_ALL_V compile;
alter VIEW OBT_AA.PO_NOTIFICATION_DETAILS_V compile;
alter VIEW OBT_AA.PO_HEADERS_PRINT compile;
alter VIEW OBT_AA.PO_HEADERS_CHANGE_PRINT compile;
alter VIEW OBT_AA.ITG_UPDEL_LINES_V compile;
alter VIEW OBT_AA.ITG_UPDEL_HEADERS_V compile;
alter VIEW OBT_AA.ITG_SP_REL_PART_SOLDTO_V compile;
alter VIEW OBT_AA.ITG_SP_REL_LINE_PART_SHIPTO_V compile;
alter VIEW OBT_AA.ITG_SP_REL_LINE_DIST_V compile;
alter VIEW OBT_AA.ITG_SP_PO_PART_SOLDTO_V compile;
alter VIEW OBT_AA.ITG_SP_PO_LINE_PART_SHIPTO_V compile;
alter VIEW OBT_AA.ITG_SP_PO_LINE_DIST_V compile;
alter VIEW OBT_AA.ITG_REQ_LINES_V compile;
alter VIEW OBT_AA.ITG_REQ_HEADERS_V compile;
alter VIEW OBT_AA.ITG_PO_LINE_LOC_ARCH_V compile;
alter VIEW OBT_AA.ITG_PO_HEADER_ARCH_V compile;
alter VIEW OBT_AA.ITG_PO_DISTRBN_ARCH_V compile;
alter VIEW OBT_AA.INVFV_MOVEMENT_STATISTICS compile;
alter VIEW OBT_AA.IGI_MPP_SELECTED_INVOICES_V compile;
alter VIEW OBT_AA.IGI_MPP_EXP_RECOGNITION compile;
alter VIEW OBT_AA.IGI_MPP_AP_DIST_MERGE_V compile;
alter VIEW OBT_AA.IGI_MPP_AP_INVOICES_MERGE_V compile;
alter VIEW OBT_AA.IGI_EXP_AVAILABLE_TRX_V compile;
alter VIEW OBT_AA.IGI_EXP_DU_LINES_V compile;
alter VIEW OBT_AA.IGC_CC_HEADERS_V compile;
alter VIEW OBT_AA.ICX_SHIP_SCHEDULE_HEADERS_V compile;
alter VIEW OBT_AA.ICX_RECEIPT_HEADERS_V compile;
alter VIEW OBT_AA.ICX_RCV_TRANSACTIONS_V compile;
alter VIEW OBT_AA.ICX_RCV_RETURNS_V compile;
alter VIEW OBT_AA.ICX_RCV_REJECTED_ITEMS_V compile;
alter VIEW OBT_AA.ICX_RCV_EARLY_LATE_RECEIPTS_V compile;
alter VIEW OBT_AA.ICX_RCV_ACCEPTED_ITEMS_V compile;
alter VIEW OBT_AA.POS_ACK_SELECT_V compile;
alter VIEW OBT_AA.POR_VIEW_REQS_BY_GROUP_V compile;
alter VIEW OBT_AA.POR_VIEW_REQS_BY_APPROVER_V compile;
alter VIEW OBT_AA.POR_RECEIVE_ORDERS_V compile;
alter VIEW OBT_AA.POR_RCV_RETURN_TO_VENDOR_V compile;
alter VIEW OBT_AA.POR_VIEW_LINE_DETAILS_V compile;
alter VIEW OBT_AA.POR_LINES_ALL_V compile;
alter VIEW OBT_AA.PN_PAYMENT_TERMS_V compile;
alter VIEW OBT_AA.PN_PAYMENT_TERMS_HISTORY_V compile;
alter VIEW OBT_AA.PN_EXP_PAYMENT_ITEMS_V compile;
alter VIEW OBT_AA.PA_TXN_ACCUM_V compile;
alter VIEW OBT_AA.PA_TEMPLATE_REQUIREMENTS_V compile;
alter VIEW OBT_AA.PA_STATUS_EI_V compile;
alter VIEW OBT_AA.PA_STATUS_PROJ_V compile;
alter VIEW OBT_AA.PA_STATUS_PROJ_GENERIC_V compile;
alter VIEW OBT_AA.PA_REV_BURDEN_DETAILS_V compile;
alter VIEW OBT_AA.PA_SECURED_PROJECTS_V compile;
alter VIEW OBT_AA.PA_REP_RES_SCHHRS_WKD_V compile;
alter VIEW OBT_AA.PA_REP_REQT_DTS_V compile;
alter VIEW OBT_AA.PA_REP_RES_SCHHRS_PAD_V compile;
alter VIEW OBT_AA.PA_REP_RES_SCHHRS_GLD_V compile;
alter VIEW OBT_AA.PA_REP_PROJ_REQHRS_WKD_V compile;
alter VIEW OBT_AA.PA_REP_PROJ_REQHRS_WK_V compile;
alter VIEW OBT_AA.PA_REP_PROJ_REQHRS_PA_V compile;
alter VIEW OBT_AA.PA_REP_PROJ_REQHRS_PAD_V compile;
alter VIEW OBT_AA.PA_REP_PROJ_REQHRS_GL_V compile;
alter VIEW OBT_AA.PA_REP_PROJ_REQHRS_GLD_V compile;
alter VIEW OBT_AA.PA_QUERY_RES_LIST_MEMBERS_V compile;
alter VIEW OBT_AA.PA_PRVDR_CC_ORG_REL_V compile;
alter VIEW OBT_AA.PA_PROJ_UNBILLED_EXPEND_VIEW compile;
alter VIEW OBT_AA.PA_PROJ_PARTIES_PROG_EV_V compile;

Sql Server 2014 showing no services in the configuration manager after install?

I'm using Windows 8. Recently I downloaded sql server management studio 2014 from the official website. But when I open the Sql server 2014 Configuration Manager there are
no services listed.
During installation, there were no any errors.
See pic from here -> http://stackoverflow.com/questions/26159248/sql-server-2014-showing-no-services-in-the-configuration-manager-after-install?noredirect=1#comment41009151_26159248
I did search everywhere but still I didn't find anything, please help me resolve this issue. I downloaded Sql server management studio 2014 from here-> http://msdn.microsoft.com/en-in/evalcenter/dn434042.aspx
Inside `win+r` as i type `services.msc` I'm unable to see any sql or service into it.

I downloaded sql server management studio 2014 from the official website. But when I open the Sql server 2014 Configuration Manager there are
no services listed.
Of course not, SSMS = SQL Server Management Studio is just a tool/frontend, not a Service. You have to install SQL Server database engine.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Shared folders not visible after the migration from 10.1.3.2.1 to 10.1.3.4

Hi All,
After the migration from 10.1.3.2.1 to 10.1.3.4., we are not able to view the shared folders after clicking on the answers link.
Can you please let me know how can i resolve the same.
Thanks in Advance
Siva.

Hi,
Please check the catalog folder that user privilege and manage permission.
Thanks
Deva

SM59 "Remote Logon" malfunctions after server migration

Hi all,
Originally our BW server is running under I386 platform. And the server seems not powerful enough, so we decided to migrate the server to IA64 platform.
After we migrated the server to the IA64 platform, we've performed some basic checking, including SM59 check. But problem occurs.
After I choose one of the RFC destination from SM59, I CAN execute the "Connection Test" and "Unicode Test" correctly. But when I press the button "Remote Logon", nothing happens.
I've also checked for the developer trace and nothing can be found. So I have also updated the Kernel to the latest version but the result is still the same ("Remote Logon" malfunctions).
Do you have any idea?
Many Many Thanks.
Best Regards,
Marco

> Originally our BW server is running under I386 platform. And the server seems not powerful enough, so we decided to migrate the server to IA64 platform.
Oh - IA64 - x86_64 would have been as powerful (or even more) and cheaper but neverless - to your problem:
> After I choose one of the RFC destination from SM59, I CAN execute the "Connection Test" and "Unicode Test" correctly. But when I press the button "Remote Logon", nothing happens.
Is the user provided a DIALOG user on the remote system? If not, then you can't logon.
Markus

Configuring CHARM after solman migration

Similar Messages

Maybe you are looking for