Quantcast
Channel: SCN : All Content - SAP ERP 6.0 Upgrade
Viewing all 870 articles
Browse latest View live

Error in phase PREP_INPUT/DETMAINMODE (Upgrade from 620 to ERP 6.0 EHP 4)

$
0
0

Hi,

 

We want to do an upgrade for our customer from release R/3 Enterprise 47x110 (620) (Linux, MaxDB) to ERP 6.0 EHP4 (Linux, MaxDB) but we suffer from an error in "Extraction"-Phase.

 

The following Error-Message is displayed in SUM-Log-Directory:

 

2WETQ399 Could not map kit ID 'd74d9fa0-ec11-11dc-c003-0030058415aa' to known/supported media set!

1EETQ399 Last error code set is: Unsuppported DVD kit ID 'd74d9fa0-ec11-11dc-c003-0030058415aa' found in '/export_T11/SMSDXML_T11_20141105140130.957.xml'

1EETQ204 Upgrade phase "DETMAINMODE" aborted with severe errors ("20141106175706")

 

 

In the generated XML-File there is only one line which shows, that we need the following DVD:

 

-<dvd type="upgrade" id="d74d9fa0-ec11-11dc-c003-0030058415aa" caption="SAP Business Suite 2008 # Upgrade DVD">

 

These are only components from release 600, SP Level 13 (SAP_APPL 600, ECC-DIMP 600, etc.) which were stored in this DVD.

The other files from release 600 SP Level 14 have been already downloaded with Download Manager.

 

Could you please assist us, were we can find this DVD on SMP or if this DVD is no longer stored on Marketplace and must be ordered from SAP by the customer explicitly?

 

Thanks & Regards,

Manuel


How to upgrade HADR

$
0
0

Dear All,

 

   We are upgrading our ERP landscape from ECC6 to EHP6, OS is windows and DB is DB2. We have upgraded test system and development server every thing is went well, now we want to upgrade our production server. We have HADR in place for our production with automatic log syncing facility, We can upgrade our production server without any issue but how to do for our DR server?.

 

Regards,

Rakesh

Post amount greater than 9,999,999,999 in a single line item of document

$
0
0

Hello Experts,

 

Currently in SAP system we can post a maximum amount of 9,999,999,999 per line item.

 

But user wants to post amount more than 9,999,999,999.

For E.g.: 16,999,999,999.

 

Is this possible in SAP. If yes, How & where do we have to make the necessary changes.

 

Please reply.

 

Thanks in Advance,

 

Pratham

SAP Upgradation Issue

$
0
0

Hello Gurus,

 

I am new to ABAP and facing trouble in a upgradation project from ecc4 to ecc6  in SPAU phase.

 

I am not able to understand what has to be done with the  Note Correction phase with GREY and Question mark traffic light.Please reply its urgent,

 

 

Thanks in advance.

URL call was terminated because the corresponding service is not available

$
0
0


Hi Experts,

 

Post Ehp7 Upgrade we are facing an issue where we are trying to hit a URL it is not working and shows the attached error.

 

But, when we try to test the same service in SICF it is working fine with all the instance (we have 4 instance for this system).

 

Maintained all the instances FQDN in the profile parameter, maintained the setting change in SE80.

Capture.PNG

Please do suggest any solution for this ASAP.

 

 

Thanks,

Preetha Balan

SAP Upgradation Issue

$
0
0

Hello Gurus


how to find request created in spdd phase??


Thanks in advance


SAP Upgradation Issue

$
0
0

While upgrading from ecc4 to ecc6 I am facing trouble in SPAU phase in note correction note number 921165.When I am downloading note from SAP market place and implementing with SNOTE t-code  it shows error DATA FILE of SAP NOTE is incomplete .

 

Another issue is-

 

In sap note 0001361644 version does not exit shows in SPAU. How to resolve this issue

 

Thanks in advance.

SAP Paging overflow when storing data in the ABAP memory

$
0
0

Hi Experts,

 

Post Ehp7 Upgrade we are getting the below dump, found the given SAP Notes to match

 

133909 - Maximum value for PG_MAXFS, PG_SHM, ROLL_MAXFS, ROLL_SHM

 

1563748 - MEMORY_NO_MORE_PAGING" dump occurs

 

The current value of rdisp/PG_MAXFS parameter is 32768, is it okay to increase this parameter or any other possible solutions are available for this.

 

Thanks in advance!!!

 

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

 

Category               Resource Shortage

Runtime Errors         MEMORY_NO_MORE_PAGING

 

Short Text

    SAP Paging overflow when storing data in the ABAP memory

 

What happened?

    In the current program, memory has been requested from SAP Paging. This

    request could not be complied with.

 

What can you do?
    Note which actions and entries caused the error to occur.

    Consult your SAP administrator.

    Using transaction ST22 for ABAP dump analysis, you can view, manage,
    and retain termination messages for longer periods.

 

Error analysis
    The ABAP runtime system and the ABAP Compiler store different types of
    data using a common interface in various parts of SAP Paging. These
    types of data include the ABAP memory (EXPORT TO MEMORY), the
    parameters for SUBMIT REPORT, CALL DIALOG and CALL TRANSACTION USING
    aswell as internally defined macros (DEFINE).

    To store further data in SAP Paging, a new SAP Paging block needs to be
    allocated. No more blocks were available in SAP Paging however.

    When the SAP Paging overflow occurred, the ABAP memory contained
    entries for 39 different IDs.

    Note:
    The ABAP memory has been deleted to allow error handling.

 

How to correct the error
    The amount of memory (in bytes) used at termination time was:

    Roll area...................... 0
    Extended memory (EM) 779879376
    Assigned memory (HEAP) 0
    Short area.....................
    Paging area.................... 40960
    Maximum address space.......... 4294967295
    You can use transaction SM04 and then choose Goto -> Memory to display
    an overview of roll memory usage and paging memory usage by the active
    users and their transactions. Clarify whether either this program or
    another one is using too much memory.

    The system log shows you more information about the current
    termination. Check whether an unexpected recursion has occurred.
    Determine whether the error also occurs when the data volume is low.
    Check the profile (parameter "rdisp/PG_MAXFS", -> Installation Guide).
    Is the disk or file system where the paging file is located too full to
    be extended, even if the size specified in the profile has not been
    reached? Is the operating system configured so that files can actually
    be this large?

    The ABAP processor saves various types of data in SAP Paging memory:

    (1) Datencluster (EXPORT ... TO MEMORY ...)
    (2) Parameters when calling programs (SUBMIT REPORT ...), dialog
    modules (CALL DIALOG ...) and transactions (CALL TRANSACTION USING

...)
(3) Macros defined internally in programs (DEFINE ...)

Wherever programs cause an overflow in SAP Paging, the relevant
statements should therefore be checked.

The EXPORT statement is particularly critical, especially if many large
internal tables are written to internal memory, possibly using
different IDs.
If the error occurs in a non-modfied SAP program, you might be able to
find a solution in the SAP Notes system. If you have access to the SAP
Notes system, check there first using the following keywords:

"MEMORY_NO_MORE_PAGING"
"CL_IM_FI_ITEMS_PT_CBR=========CP" bzw. CL_IM_FI_ITEMS_PT_CBR=========CM001
"IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS"
If you cannot solve the problem yourself, please send the following
information to SAP:

1. This description of the problem (short dump)
To do this, choose  System -> List -> Save -> Local File (unconverted)
on the screen you are in now.

2. A suitable system log
To do this, call the system log in transaction SM21. Restrict the time
interval to ten minutes before the short dump and five minutes after
it. In the display, choose System -> List -> Save -> Local File
(unconverted).

    3. If these are programs of your own, or modified SAP programs: Source
    code of these programs
    To do this, choose  More Utilities -> Upload/Download -> Download in
    the Editor.

    4. Details regarding the conditions under which the error occurred or
    which actions and input caused the error.

 

System environment
    SAP Release..... 740
    SAP Basis level 0004

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////


ERP 6.0/MS Windows Server 2008/SQL Server 2008 Upgrade..........

$
0
0

Hi all

I am working with a client who wishes to do an SAP upgrade from ECC 6.0 to EHP7.  They also wish to upgrade the Op System from Windows Server 2008 R2 to Windows Server 2012; and the database from MS SQL 2008 to MS SQL 2012.

 

My proposal is to Upgrade OS , then the DB and then SAP upgrade.

Can anyone guide me what steps should i follow to complete my activity.

Does windows server 2012 supports sql server 2008? or i have to do DB upgrade first.

Please guide me with brief steps for each three of the main activities.

 

Thanks in advance.

Prasad

sap erp upgrade 6

$
0
0

Hello,

 

I am doing upgradation for first time and in SPAU transaction there is red traffic light in with modification assistant showing and I am not able to find any document or help .When I click on version management there are changes in PROGRAMS AS WELL AS FUNCTION GROUPS.

 

Please help as by today I have tocomplete my SPAU transaction.

 

Thanks in advance.Answers will be rewarded.

user-exit issue in spau

$
0
0

Hello,

 

I am beginner and doing up-gradation from ecc 4.7 to ecc 6.In SPAU transaction in WITH MODIFICTION ASSISTANT phase in function groups there are user-exits in include program having STOP traffic light and there has been modification done in older version.

 

While going through various discussion I have concluded two options

 

1- user-exit is upgraded with customer changes  done in newer version while doing SPAU but it has not been done in my case.

 

2- there is a SAP note 607893 which says

 

 

Header
Version / Date5 / 2003-03-25
PriorityCorrection with medium priority
CategoryUpgrade information
Primary ComponentBC-DWB-CEX Customer Extensions
Secondary Components

 


Summary

 

 

Symptom

User exits are provided for adjustment in transaction SPAU although this is an enhancement method.

 

 

Solution

In the case of user exits, (not to be confused with those exits created using transactions SMOD and CMOD) this is an obsolete enhancement method. Previously, user exits were delivered only once and were never overwritten by an upgrade.
Due to the changes in the upgrade procedure for Basis Release 6.x (as of R/3 Enterprise 4.70), all SAP sources are now replaced (for information on the changes in the upgrade procedure, see the upgrade guide). As a result, transaction SPAU displays all user exits changed by the customer.
It is therefore important that you adjust the user exits by selecting the traffic light if you want to retain your customer enhancements.

If a red traffic light is provided for the object, it makes sense to convert the modification to a modification "With Modification Assistant. To do this, proceed as follows:

    1. Make a note of the user exit name.
    2. Select "Reset to original".
    3. Call the object in the editor (transaction SE38 or SE80).
    4. Use the Modification Assistant to implement the enhancements again. Using the version management, you can copy and paste your source code from the old version.


Although transaction SPAU still displays the object for future upgrades, you can easily adjust the object by selecting the green traffic light.

 

 

 

PLEASE HELP ME.

 

THANKS IN ADVANCE. SUGGESTIONS WILL BE REWARDED.

TP error 16 but transport ok

$
0
0

Hi, we have SAP on Iseries and kernel to level 711 (THE LAST for 720 unicode). Now in STMS we have sometimes error 16 unknow step but the transport is ok.

 

and this is the detail.  Where is the problems?  Have Someone a solution?   Thanks

Detailed steps in ECC 6.0 EHP7 upgrade

$
0
0

Hi Experts,

 

I would need to do ECC 6.0 EHP7 upgrade from EHP4 with SUM tool.

 

Please let me know in short what steps will happen in each stages and how the import, SPDD and SPAU will happen in detail.

 

want to understand the happening process in extaction,config ,check , pre-processing and downtime phases clearly

 

Thanks in advance

 

 

 


NZDT in upgrades

$
0
0

Hi,

 

How the normal ECC/EHP upgrade differs from NeroZero downtime(NZDT).

 

what is process wise different and special features of NZDT.

 

Please help.

 

Thanks in advance

SAP EHP Upgrade Basis process Step

$
0
0

EHP UPGRADE

 

 

PLANNING OF EHP UPGRADE(ASAP ROAD MAP)

 

The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP System. ASAP Methodology for Implementation is the SAP roadmap for implementing SAP solutions in a cost-effective, speedy manner.

Standard ASAP 8 Methodology Phases-The Standard ASAP 8 Methodology is structured into the following phases.

 

1.Project preparation - During this phase the team goes through initial planning and preparation for SAP project.
2.Business blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to run SAP to support their business. In Standard ASAP 8 Methodology the result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops
3.Realization - The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration in Standard ASAP 8 Methodology is done in two work packages: Baseline configuration (major scope); and Final configuration (remaining scope). During this phase the solution is also tested.
4.Final preparation - The purpose of this phase is to complete the final preparation (including technical testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.
5.Go-live support - The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.
6.Operate - During this phase the system is operated with the help of the central operation platform, SAP Solution Manager, with the documented solution based on the transferred project documentation.
Need of phases
These phases are the main milestones for your SAP System implementation project. Each phase has:

•Work packages, which consist of activities, for which project teams are responsible.

•Activities, which consist of tasks, which are processed by one or more team members.

•Tasks, which are carried out by a project team member. You can also access the How-to sections and accelerators at this level.

What is an SAP EHP Upgrade?

It's the installation of a new SAP ERP software version, together with the accumulation of all the relevant fixes in the form of a Support Package Stack.

Upgrade Tools
  •PANAYA
  •SUM
  •solution browser
  •SAPUp – SAP Upgrade
  •SAPEhpi - SAP enhancement package installer
  •SUM – Software Update Manager
SUM
Traditionally for applying SPS we use SPAM for ABAP & JSPM for Java
Some of the benefits of using SUM tool over these tools among others are
  •Two different tools are not required to apply SPS. One SUM tool is used.
  •No need to uncar the SAR files.
  •Minimum downtime (Single downtime for both ABAP & Java combined).
  •Simultaneously the SPS are applied to both the stacks.
Note:
  Before you start the SUM tool do ensure that
  •Latest Kernel is applied to the Source System
  •Latest SPAM patch is applied.
Clone Mode: The Software Update Manager checks the tables in the database which will be cloned to the shadow system later on during the update. Here a shadow instance will be created with tables copied from source system.
  Next input screens will ask for SPAM update.the SPAM was already updated, we choose to ignore the SPAM update.As in case of other tools such as SAPup & EHPI tool, SUM tool will also prompt for any missing notes that should be applied
SUM STEPS:
  0.Administrator user and pass
  1.Welcome:
  2.Specify credential:
  3.Select target:
  4.Conform target:
  5.Execute process
    5.1 Initialization
    5.2 Extraction
    5.3 Configuration
    5.4 Check
    5.5 Preprocessing
    5.6 Execution
    5.7 Post processing
    5.8 Finalization
  6.Summery: 
-------------------------------------------------------------------------------------------
PRE STEPS:
-------------------------------------------------------------------------------------------
1. Install maintenance license
2. Prepare stack.xml and download software.
3. Install SUM as <sid>adm
  STEPS:
  1.cd /sapcd/XXX702SPS08
  2.SAPCAR –xvf <download directory>/<path>/<Archive>.SAR -R /usr/sap/<sapsid>
  3.SAPCAR -xvf SUM10SP08_1-20006543.SAR -R /usr/sap/xxx
  4.Change ownership to sidadm: sapsys on /usr/sap/XXX/SUM
  5.Change permission to 777 on /usr/sap/XXX/SUM
4. create and/or give Basis user in 000 and 300 client, assign SAP_ALL and SAP_NEW in system being upgrade.
5. Recommendation for Oracle 11.2: Apply latest Patch Set
6. Turn off backup
6. Database Passwords
  Do not use the '@' character in your database passwords, as the Software Update  Manager cannot handle the passwords then.
7. Increase the OPEN_CURSORS Parameter
  alter system set open_cursors = 20000 scope=both;
8. UPDATE STATS
  brconnect -u / -c -f stats -t oradict_stats
  brconnect -u / -c -f stats -t system_stats
  brconnect -c -u / -f stats -t all -f collect -p 4
Note:
oradict_stats: Collects statistics for Oracle dictionary objects using DBMS_STATS package. For more information, see SAP Note 863811.
system_stats: Collects system (CPU, I/O) statistics using the DBMS_STATS package. For more information, see SAP Note 601395
9. Calculate Space Statistics Before the Upgrade/Update
  brconnect -u / -c -f stats -t all -m +I -s P1 -f allsel,collect,method,precision -p 4
10. Make copy of profiles.
11. SAPSR3 Tablespace free space should be more than 75GB free
12. Make sure there’s no lock objects – release all transports
13. Turn off archive mode (If you can’t, you’ll have a chance to do so before downtime)
14. Check disk space in the file systems, SUM and current SAP mounts need to have at least 200GB free or larger
15. Check DIR_TRANS, clean up /EPS/in directory
16. Add more data files to tablespaces
17. Check path and empty /usr/sap/trans/EPS/in
-------------------------------------------------------------------------------------------
START UPGRADE:
-------------------------------------------------------------------------------------------
1. Start SUM as <sidadm>
  STEPS:
  1. cd /usr/sap/XXX/SUM
  2. ./STARTUP &
  3. Run SUM GUI
  4. http://<host name>:4239
2. Start phases
   SUM STEPS:
  0.It will ask for Administrator user and pass we can give any user name and pass but this person will be responsible fro whole upgrade.
  1.Welcome: In this phase we generally get the information of Detected SAP Netweaver System.Like Syystem technology: ABAP SYSTEM System id: KUN, System Directory: /usr/sap/KUN It also recomended to Read note 1790828
  2.Specify credential: this Part Used to ask about SIDADM Password so Provide KUNADM as user and password as *******
  3.Select target: This part having two option one for Stack.xml file and manually prepaired directory. we choose the location of Stack.XML File with XML name. EX-/usr/sap/KUN/ECCEHP6/SMSDXML_KUN_20130816212838.269.xml
  4.Conform target: target release is confirmed here it will show current version and ehp of system and the target version of the system where we are going also it will say to enter a keyword from a snote mention in the screen.
  5.Execute process
    5.1 Initialization:
    5.2 Extraction: Once you click next to go to Extraction Phase, it will ask for DDIC user Password and also Database user SYSTEM password. The Extraction phase will extract the relevant files from the download directory. Next input screens will ask for SPAM update.the SPAM was already updated, we choose to ignore the SPAM update.As in case of other tools such as SAPup & EHPI tool, SUM tool will also prompt for any missing notes that should be applied. Copy tp and R3trans to /usr/sap/XXX/SUM/abap/exe STEPS:
  /sapcd/sapcd/XXXUpgrade2013/KernelDuringSRMUpgrade***cp R3trans tp /usr/sap/XXX/SUM/abap/exe .Restart SUM step. In next step of Extraction it will ask to apply some snote.
    5.3 Configuration: Here we mainly choose standard option and dnt check the check boxes about archiving and expert mode. Here it will ask number of Processes during up time and during down time like Batch, DDL, R3Trans etc. Usually we keep default Value. After 2 Hours we will get another screen which will ask for add ons. The Java configuration steps also starts. With SUM tool you can choose to automatically update the additional dialog instances if any. In older times we had to manually uninstall and install dialog instances
    5.4 Check: It will check fro the Spaces in database. if space is not available then create tebalspace fro space.
  Steps:
  create tablespace PSAPSR3731 extent management local autoallocate segment space management auto datafile '/oracle/XXX/sapdata2/xx3731_1/xx3731.data1' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_2/xx3731.data2' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_3/xx3731.data3' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_4/xx3731.data4' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_5/xx3731.data5' size 10000M autoextend off
    5.5 Preprocessing: In this phase SUM prepare the system for Upgrade.
  Possible Error:Batch job RSVBCHCK Failed with error code 8
  SM13: Repeat or Delete all update records
  1873772 - Last error code set: Single errors (code <= 8) found in logfile 'PSVBCHCK.ELG'
  transaction LBWQ; Delete all queues;
  Transaciton LBWG; Delete 06/13

   5.6 Execution: In this phase SUM perform actual update in the system and downtime begin this phase take a long time.
  Possible Error: Calling usr/sap/XXX/DVEBMG/tp failed with return code 8.
  Solutioin: Note 912369 - FINB_TR_DEST, after import failures, transport errors
  Transaction: /nFINB_TR_DEST at client 000
  Create RFC FINBTR@XXXCLNT001 and FINBTR@XXCLNT300; Under RFC, input client with DDIC user/pwd.
  1 .In the next Screen it will ask u to take Backup of ur databae if you already done click action completed and hit Next.
  2. End of downtime notification
    5.7 Post processing: In this phase system will unlock and downtime finished.In this phase some manual action required some of them are
  1. we can reschedule the periodic job which has been deschedule during downtime.to reschedule these job we can run a report BTSTRNS2 using DDIC user in transaction SE38.
  2. Application specific post upgrade activity. Start ASU toolbox using transaction /ASU/UPGRADE
  3. see the log of SUM from usr/sap/XXX/SUM/ABAP/log/LONGPOST.LOG and from message class and message number we and applied the relevant Snotes.
    5.8 Finalization
  6.Summery: This phase will give the target version which completed and total time and system downtime.
-------------------------------------------------------------------------------------------
POST UPGRADE
-------------------------------------------------------------------------------------------
1.Implement note 1720495 before you start transaction SPAU  (Note 1790828); Manual step is not needed.
  Make sure to implement SAP note 1720495 immediately after a Support Package import, an enhancement package installation, or an upgrade and before making any adjustments in transaction SPAU
2.If you have SAP Kernel 7.10 or higher:
  Execute the following commands:
  cd <update directory>/abap/exe
  ./oraroot.sh <SAPSID>
  If you have an MCOD system and/or the database name does not correspond to the SAP system name, use the following command to run oraroot.sh:
  ./oraroot.sh <SAPSID> <DBSID>
  If you have one kernel directory: cd /usr/sap/<SAPSID>/SYS/exe/run
  If you have two kernel directories: cd /sapmnt/<sapsid>/exe/(n)uc/<platform>
  cp -p ./icmbnd.new ./icmbnd
  chown root:sapsys icmbnd
  chmod 4750 icmbnd
  exit
  cd $ORACLE_HOME/dbs
  cp /usr/sap/<SAPSID>/SYS/exe/run/sapdba_role.sql sapdba_role.sql
  sqlplus /nolog @sapdba_role.sql SR3
3.Call transaction STMS and choose OverviewSystems.
  Double-click the system that has been upgraded and switch to the Change mode.
  Do not change anything unless another action requires changes, and choose Save. Go back to the system overview.
4.Checking for Unused Indexes
  Call transaction DB02.
  Choose Missing Tables/Indexes.
  Choose Unknown objects in ABAP Dictionary.
  Check if there are unused indexes in the database. If this is the case, delete them manually.
  For more information, see SAP Note 1227270
5.Oracle: Deleting Tablespaces 
  select table_name, tablespace_name from dba_tables where TABLESPACE_NAME='PSAPSR3702';
  select index_name from dba_indexes where tablespace_name='PSAPSR3702';
  Note 1819182 - Tables (TTREE*) remain in old exchange tablespace
  In transaction SE13 or SE11, change the data type SSEXC to APPL0 for the tables and activate your data. After you do this, you can use
  a) SE14
  b) ICNV
  c) DB tools
  to move the table to a different tablespace (for TABART APPL0).
  SE11-> Technical Setting -> change data class from SSEXC to APPL0
  Check TAORA for APP0
  1. Call transaction ICNV and read the online documentation ("I" button"). Converting a table using ICNV is a complex procedure during which, for example, changes to the table contents are made using a database trigger. It is important that you have a basic understanding of how the transaction works.
  2. Call transaction SE14, enter the name of the table that you want to move and select "Edit" and then "Storage Parameters".
  3. Select "For new creation" and use the "current database parameters" as a template (if required). Switch to "Change" mode.
  4. After "TABLESPACE" and "INDEXSPACE", enter the new tablespaces required for the tables or index data.(Change PSAPSR3702 to PSAPSR3)
  5. Save your entries.
  6. Call transaction ICNV.
  7. Select "Edit->Add table" and enter the name of the table that you want to move. Do not change the proposed scenario.
  8. Follow the steps proposed by the wizard (choose "Assistant" or perform the following steps manually using the "Control" menu).
     a) Initialization
     b) Data transfer
     c) Transfer
     d) Delete entry
  Shutdown Oracle;
  brspace –f tsdrop
  brspace -c force -o process,time -u / -f tbreorg -a reorg -tablespace PSAPSR3702 -t "*" -parallel 3 -degree 3 -newts PSAPSR3
  Problem:
  ZPPSFIF004
  But when I was trying to upload a file from application server to table using a z program found the below error.
  Solution:
  Fix RFC WEBMETHOD.
  #1859173 - Taking into account of external services in SU25, improved display in step 2b
  #1850378 - Handling of (historically created) defective modification flags in SU24 data by SU25
  #1878702 - Optimizing the navigation in step 2b and the transport connection
6.Make sure client 000 is locked in SCC4
7.Set SE06>System Change Option back to original
8.Shutdown SAP
  As root, run ./saproot.sh SID in /sapmnt/SID/exe
  Rename folder /oracle/netbackup_script.bak to netbackup_script
  Create link for netbackup

SAP object cannot be assigned to package Z***t

$
0
0

Hello Experts,         

         we are try to implement SAP Note 1561545

we are received the following message:-

SAP object FUGR ADWP_SERVICES cannot be assigned to package Z001 as the following:-

01Error.PNG

Kindly aid us, How we can fix this issue?

Thanks

Said Shepl

SAP Upgradation Issue

$
0
0

Hello Gurus,

 

I m facing the issue in spau phase in badi while with modification assistant.the traffic light is green but if i am adjusting the following information occurred

please go through the the screen shot.please reply

 

 

 

thanks in advance.

Add New folder in SAP Menu

$
0
0

Dear all

I have requirement in our org they need all the Z Development to be keep in separate folder we have sap Standard menu in that in the below i need add folder called ABAP  development    i tried that with se43 didn't succeeded give me some helpful document to solve that issue

sap_easy.png

 

 

Regards

How to upgrade HADR

$
0
0

Dear All,

 

   We are upgrading our ERP landscape from ECC6 to EHP6, OS is windows and DB is DB2. We have upgraded test system and development server every thing is went well, now we want to upgrade our production server. We have HADR in place for our production with automatic log syncing facility, We can upgrade our production server without any issue but how to do for our DR server?.

 

Regards,

Rakesh

phase MAIN_NEWBAS/PARCONV_UPG running for ages

$
0
0

Hi,

 

my upgrade from 4.6C to ERP 6.0 EHP4 SP06 is now at phase MAIN_NEWBAS/PARCONV_UPG; database is MaxDB 7.7.7.18, OS is Solaris 10.

 

This phase is now running for at least 31 hours. There is no tp or R3trans running. Looking at SM50 there is only 1 single process running working on different tables (currently QCMVBAP, QCM8VBAP).

 

Any idea what's wrong or how to speed up this phase ?

 

The upgrade guide (page 35) says that this phase converts application tables and that it can be done during production time using "external conversion". Unfortunately there are no more details about how to do.

 

Its also said that when using ICNV this can be done during production time which i would prefer for this long running step. But looking at TA ICNV there are no tables to convert. The work space is empty ?

 

Any idea ?

 

Regards

  Wolfgang

Viewing all 870 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>