Transport a ztable from 4.7 to ecc 6.0

hi,
i'v a prob to create a same z-table in ECC 6.0. that is already created in my 4.7 version
my ECC 6.0 and 4.7 as diff. servers.
i only want to create structure. i'dont want to recreate it in ECC 6.0 is their any short cut so it can create without any manual creation
mukesh

That's not true!!!!
All transports transports from 47 can be imported in ECC6.0...
Just ask basis guy to import transports. If the transport doesn't exists in ECC6.0 there should be downloaded cofiles and data files and then put them on the application server ecc6.0 et finally stms to import them!

Similar Messages

SPAU / SPDD Transport During Upgrade from 4.6C to ECC 6.0

We are currently upgrading R/3 4.6C to ECC 6.0 SR2. During the DEV upgrade, we performed Dictionary Objects adjustments before ACT 7.00 and SPAU adjustments at the end of the upgrade. All the adjustments are collected in a transport.
I read in another thread that we will have to choose 'SELECT FOR TRANSPORT' button in SPAU and not release it. Then, continue with the upgrade. And in the same thread, it is also mentioned that DDIC object modifications should not be handled through transports.
Now, my question is, if I have collected the SPAU adjustments in a transport and continued with the upgrade without choosing the 'SELECT FOR TRANSPORT' button, can I do it after I complete the upgrade before I continue with QAS upgrade? Will the upgrade still automatically detect the transports and move them? And, my other question is, if DDIC modifications are not supposed to be dealt through transports, how else should they be worked upon?
Your response ASAP will be rewarded properly.
Thank you.

Nick, thank you for the reference. Even though I had gone through this note before, I couldn't apply this note because, this note was refering to "R3up" which, I guess, is no more used. "SAPup" is the program currently in use. Also the location mentioned in the note to execute "R3up" is "//usr/sap/put/exe" but, "SAPup" is located under "//usr/sap/put/bin/". So, I am not sure if there is any new notes refering to this. One other question I have with regards to this note is, one of the arguments for the command R3up is, "REL". For SPDD, the note suggests to use target release. And for SPAU, the note suggest to use the release mentioned in the DDIC activation phase.
In my case, I am upgrading from 4.6D (kernel) to 700 (kernel). The DDIC activation shows ACT_700. So, I am sure I would use "700" as value for "REL" for SPDD. But, am I supposed to use "46D" for SPAU? or should I use "700"?
Thank you.

Transport the ztable

Hi,
How to transport the ztable from DEV TO QUALITY??
HELP ME. ITS URGENT.
REGARDS,

Hi Vijay,
When you create a ZTABLE it might ask you for reqest. Create the request number and then go to SE09 and you will see the request number there expand the request number you will see the task number. first you have to transport the task and then transport your request number. For transporting click on the request number in se09 you will see the small bus in the top just click it and it will transport your request number . but remember first you have to transport you task and then transport your request number.
Thanks
Vikranth Khimavath

How to maintain a Factory Calendar from 4.6C to ECC 6.0 ?

Hi,
Any idea how to maintain a Factory Calendar of 4.6C
in ECC 6.0 ?
Edited by: Murtaza Dharsi on Feb 18, 2008 5:28 PM

Hello Wolfgang,
Thank you for your response.
I am aware of the transaction SCAL.
Could you please share your experience that transporting Calendar entries from 4.6C to ECC 6.0 is quite risky ?
Is the least effort in keying in the entries into ECC 6.0 manually ?
Thanks & Regards
Murtaza

SmartForm transportation From 4.6C to ECC 5.0..

hi,
we have requirement to transoport all Smarforms form 4.6 C to ECC 5.0 ..need help on that..how to initiate the process..
thanx in advance
Regards,
Dinesh

hi,
Try these links:
Upgrade from 4.6c to ECC 5.0
sap.ittoolbox.com/groups/strategy-planning/sap-projectmanagement/ecc-60-upgrade-plan-986625
Hope this helps.
Regards,
Vivek.
(-->Reward points if helps

Transfer data in the Ztable from one client to another client in a same ser

Hi all,
How can i transfer or move data in the Ztable from one client to another client in a same server .
Thanks
Ajay

hi,
create a transport request (Workbench type) and add the following line into the transport request:
R3TR TABU name_of_table
save and doubleclick this line and enter the table keys for the required entries (if you need all antries: client and an asterisk will do).
When it is done save again, release the transport and ask basis to import into target client (or you can do on your own in SCC1 transaction)
hope this helps
ec

Technical upgrade from 4.7 to ECC 6.0

Experts,
1.We need to make Technical upgrade in HR from 4.7 to ECC 6.0 with OM,PA, -ve Time,Payroll, Recruitment (other Modules also upgraded).Kindly let us know what will haeepen for the following .
A.Configrations in SPRO
B.Previous database (Cluster table for previous Time and payroll run)
C.Master data of employees which is stored in Infotypes
2.Also Kindly let us know is there anything we need to take care after moving from 4.7 to 6.0

Hi Kumar,
Basically there needs to be a Transport established between 4.7 and ECC6.00 Version . You can create Transport request for those tables whose value remain same in 4.7 nad ECC6.00 But for tables having changes you need to create the Configuration.
1 more method applied by organization is a client copy of tables.
My suggestion would be like this :
1. Compare and Update Tables (from Configuration Handbook)
Pay Frequency
Define Period Modifiers
V_T549R
Define Date Modifiers
V_T549L
Check Payroll Accounting Area
V_T549A
Pay Scale Structure
Define EE Subgroup Grouping for PCR and Collective Agreement Provision (CAP)
V_503_B
Check Pay Scale Type
V_T510A
Check Pay Scale Area
V_T510G
Check Assignment of Payscale Structure to Enterprise Structure
V_001P_C
Define Default for Pay Scale Data
Feature - TARIF
Setup payroll period for Collective Agreement Provision
V_T510W
Revise Pay Scale Groups and Levels
V_T510
Enterprise Structure for Wage Type Model
T539A
Feature - LGMST
Revise Default Wage Types
V_T539A - already tested
Define Valuation of Base Wage Types
V_T539J
Legacy Data Transfer
T558B
T558D
Define Periods for import
T558B - already tested
Rates of Pay
T512W
Pay Scale Allowance Group
V_T7INA1
Assign Pay Scale Groupings for Allowances
V_T7INA3
Define Basic Codes
V_T7INB4
Statutory
Define Trust Details for Provident Fund
V_T7INF1
Assign Company Rates for Provident Fund
V_T7INF5
Define PF Trust Validity Period
V_T7INF7
Maintain Contribution Details for Provident Fund
Feature: 40EPF
V_T7INF3
Define Contribution Type for Statutory rates for Provident Fund
V_T7INF3 - already tested
Employees' State Insurance
V_511P_B
V_T511P
Maintain Number of Working Days in a Month
V_511K_B
V_T511K
Define Personnel Area and Subarea Groupings for ESI
V_T7INE1
Assign ESI Groupings for Personnel Area and Subarea
V_7IN0P_ESI
Maintain Contribution Rates for ESI
V_T7INE3
Assign Universal Contribution Groupings for Universal Contribution Type
V_T7INOP_ALL
Assign slab code for Universal Contribution Grouping
V_T7INU1
Assign Slab code and other parameters for each state of a universal type
V_T7INU3
Assign contribution Value for each slab
V_T7INU5
Maintain Eligibility Details for Superannuation
Feature - 40SAN
Tax and Professional Tax
Define Professional Tax Grouping Details
V_T7INP1
Maintain Method and Form Layout for Ptax Groupings
T596F
Maintain Re-Computation Behaviour of Tax related
Feature - 40MWT
Maintain Schema for Exemption on Medical Reimbursement / Insurance
V_T7INT9
Maintain Schema for Exemption of Child education and hostel allowance
V_T511K - already tested
V_T7INT9 - already tested
Bonus Act
T511K - already tested
T511P - already tested
One Time Bonus Tax
Copy Wage Types
V_T7INT9 - already tested
V_T7INA9
Define Compensation Area Feature
Feature - CAREA
Assign organizational assignment to Compensation Groups
Feature - CMGRP
Maintain Variant for Payroll Simulation
Feature - 16CVA
Maintain Payslip Variant
Feature - 16EVA
HRA/CLA/LTA
Define Accomodation Types
V_T7INT7
Company Loans
Maintain Loans Grouping
Feature - 40LGR
Mantain Loans Eligibility Checks and Limits
Feature - 40 LGR - already tested
Banking
Setup House Banks
V_T012
Bank Account
V_T012K
Define Sending Banks
Feature - DTAKT
Check Text Keys for Payment Transactions
V_T520S
General Ledger
Define Employee Grouping Account Determination
Feature - PPMOD
Define Symbolic Accounts
V_T52EK
V_T52EZ
2. Compare and Update Genaral Tables
1     T512W
2     T511K
3     T511P
4     TCURR
5     T030
2a. Compare and Update Additioanl PY-IN Tables
1     T7INTN TAN Number Maintainence
2     T7INA1 Pay scale grouping for allowances
3     T7INA3 Associating pay parameters to pay scale grouping
4     T7INA5 Wage type model for pay scale grouping for allowances
5     T7INA7 Reimbursements Allowances and Perks - base slabs
6     T7INA9 Reimbursement allowances perks - eligibility and calculation
7     T7INAA Salary year for pay scale grouping for allowances
8     T7INB1 Basic Wages
9     T7INB4 Basic Codes
10     T7INB5 Basic Codes for Allowance Groups
11     T7INB7 Basic slabs
12     T7INB8 Appraisal Criteria
13     T7INB9 Increment criteria
14     T7INC1 Car types master
15     T7INC3 Type and age eligibility for car schemes(COCS/OYCS)
16     T7INC5 Perk valuation for cars
17     T7INC7 Amount and number eligibility for car schemes(COCS/OYCS)
18     T7INC9 Conveyance allowance eligibilty
19     T7INCA Codes for Conveyance types
20     T7IND1 Dearness allowance consumer price index master
21     T7IND3 Dearness allowance consumer price index value
22     T7IND5 Dearness allowance basic slab details
23     T7IND7 Dearness allowance calculation rules
24     T7IND9 Dearness allowance consumer price index slabs
25     T7INE1 Personnel area / subarea grouping for employees' state ins.
26     T7INE3 Employees' state insurance contribution rates
27     T7INF1 Trust Master
28     T7INF3 Statutory rates for Provident fund
29     T7INF5 Company rates for Provident Fund
30     T7INF7 Trust details
31     T7ING1 Gratuity Details Maintenance
32     T7ING3 Gratuity ID Maintenance
33     T7ING5 Gratuity ID and Related Wage Types
34     T7INI0 Investment category limits
35     T7INI2 Investment technical description and text
36     T7INI4 Investment details
37     T7INI5 Sub section description
38     T7INI7 Sub section limit
39     T7INI8 Sub division description
40     T7INI9 Sub division details
41     T7INIA Deduction wage type for Sec 88
42     T7INIC Deduction wage type for Sec 80
43     T7INJ1 Section 24 Deduction Details Maintenance
44     T7INJ3 HR-IN: Loans Eligibility checks and limits
45     T7INJ5 HR-IN: Loans Dusbursement Schedule
46     T7INJ6 HR-IN : Loan Tranche Disbursement: Text for Events Code
47     T7INL1 Leave validation for LTA
48     T7INO1 One day salary deduction
49     T7INP1 Professional tax grouping details
50     T7INP3 Method and form layout for states
51     T7INP4 Professional tax slab amounts
52     T7INR1 Housing code for taxation
53     T7INR3 Percentage/amount for housing related constant
54     T7INR5 Housing related statutory constants for taxation
55     T7INR7 Codes for Housing Types
56     T7INR9 City category for housing type
57     T7INS1 Superannuation Details Maintenance
58     T7INS3 Superannuation ID
59     T7INS5 Superannuation-Wagetype Details
60     T7INT1 Slab codes for taxation
61     T7INT3 Taxation slabs
62     T7INT5 Personnel subarea grouping for Tax
63     T7INT7 Tax codes for tax exemptions
64     T7INT9 Taxability of wage types
65     T7INU1 State for Universal Grouping
66     T7INU3 Slab Codes for States
67     T7INU5 Contribution Value for Each Slab
68     T7INW1 Personnel area/subarea grouping for LWF
69     T7INW3 Labour welfare fund rates
70     T7INY1 Recovery of rounding off amounts
71     T7INZ1 Factor for retiral benefits
72     T7INZ3 Period of notice codes
3. Compare Payroll Schemas
1     Compare ECC5- to ECC6 standard schemas
2     Compare ECC5- to ECC6 customised schemas
4. Compare Personnel Calculation Rules (PCR)
1     Compare ECC5- to ECC6 standard PCR's
2     Compare ECC5- to ECC6 customised PCR's
B. Payroll Process
1     Generic Payroll Process
1.1     Simulate Payroll
1.2     Release Payroll
1.3     Start Payroll
1.4     Check result
1.5     Corrections
1.6     Remuneration statement
1.7     Simulate and test FI/CO postings
1.8     Simulate and Test Preliminary DME
1.9     Run Preliminary DME Program
2     Create a live posting run and create FI documents
C. Regression Testing (Variance Monitor)
1     Compare Payroll Results
Create a Excel with these contents and fill them up by saying the percentage of similarity and completetion.
Please let me know if this is usefull
Regards,
Prabha

How can i copy ztable from development server to ides server?

how can i copy ztable from development server to ides server?

Hello Suresh
The simplest way is to use a transport request.
Another possibility is to check for SAPLINK plugins which allow to download table definitions (including data elements and domains) into a flat file. Upload on IDES again via [SAPLINK|https://wiki.sdn.sap.com/wiki/display/ABAP/SAPlink].
Regards
Uwe

What is the impact of R/3 upgradation from 4.7 to ECC 6 on BI

Dear all,
Can any one tell me what will be the impact of R/3 Upgradation on BI... as we are shortly going to upgrade our R/3 from 4.7 to ECC 6.
Do we need to take any precautions in R/3 and aswell as BI
Please give the information...points will be given
Regards
venu

Hi
Please Refer this as this vll give u the Pros and Cons for upgrade.
Refer
http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B
This Wiki contains Rob Moore's ( BW Manager, Edwards Limited) teams experiences in upgrading Business Warehouse System from 3.0B to BW 7.0.
Contents
1 Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
2 Introduction
3 Overview & Scope
4 Drivers
5 Environment
6 Resource & Timescales
7 High Level Plan
8 Summary Task List
8.1 #Support Pack Hike
8.2 #Plug-in installation
8.3 #PREPARE process
8.4 #Dbase upgrades
8.5 #System Upgrade
9 Lessons Learnt
10 Issues & Fixes
10.1 Unfixed Issues
10.2 Fixed Issues
11 Regression Testing Process
11.1 Introduction
11.2 Set up
11.3 Actions
11.4 Security
12 Transport Freeze
13 Web Applications
13.1 Dashboards
13.2 Internet Graphics Server (IGS)
14 Detailed Task Lists
14.1 Support Pack Hike (detail)
14.2 Plug-in installation (detail)
14.3 Dbase upgrades (detail)
14.4 PREPARE Process (detail)
14.5 System Upgrade (detail)
Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
Introduction
This Wiki contains my teams experiences in upgrading our Business Warehouse System from 3.0B to BW 7.0.
Hopefully it will be useful to anyone else who's about to embark on this. If there's anything I've missed or got wrong, then please feel free to edit it or contact me and I'll try to explain.
Rob Moore - BW Manager, Edwards Limited.
Overview & Scope
This was to be a technical upgrade of BW only. The new BW 7.0 web functionality & tool suite which requires the Java stack rather than the ABAP stack was out of scope. We had heard that the latter was where most of the problems with the upgrade lay. Our plan is to wait for this part of BW 7.0 to become more stable. Also it has a big front end change and the business didn't have sufficient resource to cope with that much change management.
Drivers
3.0B at the end of its maintenance
Opportunities to do better reporting
Options to utilise BI Accelerator
Environment
Our R/3 system was at 4.6C and was not going to be upgraded. We have APO at version SCM4.0.
Our BW system is approximately 300 GB, with 125 global users. It was at version 3.0B SP 18
We have Development, Acceptance and Production environments.
Resource & Timescales
The Project ran for 3.5 months from Feb to May 2007. We used the following resources. The percentages are the approx. amount of their time spent on the project.
Project Manager * 1 70%
BW technical team * 3 50%
ABAP coder * 1 10%
SAP Systems Development expert * 1 20%
Basis * 1 25%
High Level Plan
These are the basic areas. We planned to complete this process for each environment in turn, learning our lessons at each stage and incorporating into revised plans for the next environment. However we did the Support Packs and Plug-Ins in quick succession on all environments to keep our full transport path open as long as possible.
Upgrade BW to the minimum support pack.
Install R/3 Plug-ins PI 2004.1
Run PREPARE on BW
Dbase upgrades (Database & SAP Kernel upgrade)
System Upgrade
Summary Task List
This list contains all the basic tasks that we performed. A more detailed check list is shown below for each of the headings.
#Support Pack Hike
We moved only to the minimum acceptable SP as this seemed most likely to avoid any problems with the 3.0B system prior to the upgrade.
Apply OSS 780710 & 485741
Run Baseline for Regression tests
Full Backup
Apply SP's (we were at SP18, going to SP20)
SPAU list review
Regression testing
#Plug-in installation
Apply SAP note 684844
Import and patch Basis plugin PI 2004.1
SPAU list review
#PREPARE process
BW Pre-Prepare tasks
BW - Inconsistent Data fix
Run PREPARE
Review of results
Any showstoppers from PREPARE?
#Dbase upgrades
Database Upgrade (FixPak)
SAP Kernel Upgrade
#System Upgrade
Reverse Transport of Queries
Reconnect DAB & SAB to AAE
Run Baseline for Regression tests
Full Backup
Run the Upgrade
SPAU list review
Regression testing
Lessons Learnt
Testing is all! We picked up on a lot of issues, but would have picked up more if we'd had a full copy of our production environment to test over.
Our approach of doing a full upgrade on each environment before moving to the next one paid dividends in giving us experience of issues and timescales.
Write everything down as you go, so that by the time you get to upgrading production you've got a complete list of what to do.
We succeeded because we had people on our team who had enough experience in Basis and BW to be able to troubleshoot issues and not just read the manual.
The SAP upgrade guide is pretty good, if you can understand what they're on about...
Remember the users! The fact that the loads have been successful doesn't count for anything unless the users can see the data in Excel! There's a tendency to get caught up in the technology and forget that it's all just a means to an end.
Issues & Fixes
I've listed the main issues that we encountered. I have not listed the various issues where Transfer rules became Inactive, DataSources needed replication or we had to reinstall some minor Business Content.
Unfixed Issues
We could not fix these issues, seems like SP 13 will help.
Cant delete individual request from ODS
After PREPARE had been run, if we had a load failure and needed to set an ODS request to Red and delete it, we found that we could not. We raised an OSS with SAP but although they tried hard we couldn't get round it. We reset the PREPARE and still the issue persisted. Ultimately we just lived with the problem for a week until we upgraded production.
Error when trying to save query to itself
Any query with a re-usable structure cannot be saved (more thsan once!)
OSS 975510 fixed the issue in Dev and Acc, but NOT in Production! SP 13 may solve this once it's released.
Warning message when running some queries post-upgrade
Time of calculation Before Aggregation is obsolete. Not a big issue so we haven't fixed this one yet!
Process Chain Scheduling Timing error
Process chains get scheduled for the NEXT day sometimes and has to be manually reset.
See OSS 1016317. Implement SP13 to fix this. We will live with it for now .
Fixed Issues
Duplicate Fiscal Period values in Query
If you open up a drop down box ("Select Filter Value") for Fiscal Year/Period to filter your query, you are presented with duplicate entries for Month & Year.
Due to Fiscal Year Period InfoObject taking data from Master Data not InfoProvider. Thus it picks up all available periods not just Z2.
Auto-Emails being delayed
Emails coming from BW from process chains are delayed 2 hours on BW before being released
Due to userids that send these emails (e.g. ALEREMOTE) being registered on a diffferent timeazone (i.e. CET) from the BW system (i.e. GMT)
Pgm_Not_Found short dump
Whenever a query is run via RRMX or RSRT
Call transaction RS_PERS_ACTIVATE to Activate History and Personalisation
Characteristics not found
When running a query the warning message Characteristic does not exist is displayed for the following: 0TCAACTVT, 0TCAIPROV, 0TCAVALID
We activated the three characteristics listed and the warnings stopped. NO need to make them authorisation-relevant at this stage.(also did 0TCAKYFNM)
System generated Z pgms have disappeared
Post-upgrade the system Z-pgms ceased to exist
Discovered in Development so we compared with pre-upgraded Production and then recreated them or copying them from production.
Conversion issues with some Infoobjects
Data fails to Activate in the ODS targets
For the InfoObjects in question, set the flag so as not to convert the Internal values for these infoobjects
InfoObject has Conversion routine that fails, causing load to fail
The routine prefixes numeric PO Numbers with 0s. SD loads were failing as it was not able to convert the numbers. Presumably the cause of the failure was the running of the Pre-Prepare RSMCNVEXIT pgm.
Check the Tick box in the Update rule to do the conversion prior to loading rather than the other way round.
Requests fail to Activate on numeric data
Request loads OK (different from above issue) but fails to Activate
Forced conversion within the update rules using Alpha routine. Deleted Request and reloaded from PSA.
Database views missing after pre-PREPARE work
Views got deleted from database, although not from data dictionary
Recreated the views in the database using SE14.
Workbook role assignations lost
We lost a few thousand workbook assignments when we transported the role they were attached to into Production
The workbooks did not exist in Development, thus they all went AWOL. We wrote an ABAP program to re-assign them in production
Regression Testing Process
Introduction
We were limited to what we could do here. We didn't have a sandbox environment available. Nor did we have the opportunity to have a replica of our production data to test with, due to lack of disk space in Acceptance and lack of sufficient Basis resource.
Set up
We manually replicated our production process chains into test. We didn't have any legacy InfoPackages to worry about. We asked our super-users for a list of their "Top 10" most important queries and did a reverse transport of the queries from Production back into test (as we do not generally have a dev/acc/prodn process for managing queries, and they are mostly created solely in prodn). We made sure every application was represented. In retrospect we should have done some Workbooks as well, although that didn't give us any problems.
Actions
Prior to the various changes we loaded data via the Process chains and ran the example queries to give ourselves a baseline of data to test against. After the change we ran the same queries again and compared the results against the baseline. We tried to keep R/3 test environments as static as possible during this, although it wasn't always the case & we often had to explain away small changes in the results. After upgrading BW Development we connected it to Acceptance R/3, so that we had pre-upgrade (BW Acceptance) and post-upgrade (BW Development) both taking data from the same place so we could compare and contrast results on both BW systems. We did the same thing once BW Acceptance had been upgrading by connecting it (carefully!) to Production R/3. To get round the lack of disk space we tested by Application and deleted the data once that Application had been signed off. Once we got to System test we involved super-users to sign off some of the testing.
Security
We chose to implement the new security schema rather than choosing the option to stick with old. For us, with a relatively small number of users we felt we could get away with this & if it all went wrong, just temporarily give users a higher level role than they needed. Our security roles are not complex: we have end user, power-user and InfoProvider roles for each BW application, together with some common default roles for all. In the event we simply modified the default "Reports" role that all our users are assigned, transported it and it all went smoothly. Apart from the fact that everyone's workbooks are assigned to this role and so we "lost" them all !
Transport Freeze
Once you've upgraded Development you've lost your transport path. We planned around this as best we could and when absolutely necessary, developed directly in Acceptance or Production, applying those changes back to Development once the project was complete. Depending on what other BW projects you have running this may or may not cause you pain!
Web Applications
Dashboards
We had various dashboards designed via Web Application Designer. All these continued to function on the upgraded system. However there were various formatting changes that occurred e.g. Bar graphs were changed to line graphs, text formats on axes changed etc. SAP provides an upgrade path for moving your Web applications by running various functions. However we took the view that we would simply re-format our dashboards manually, as we didn't have very many to do. Plus the external IGS (see below) powered all our environments and needs upgrading separately as part of the SAP method. Thus we couldn't have tested the SAP path in Development without risking Production. Sticking with manual mods was a lower risk approach for us. We did find we had to re-activate some templates from BC to get some of the reports to continue to work.
Internet Graphics Server (IGS)
We had an external IGS server with v3.0B. Post-upgrade the IGS becomes part of the internal architecture of BW and thge external server is redundant. We found no issues with this; after the upgrade BW simply stops using the external IGS and no separate config was needed.
Detailed Task Lists
Support Pack Hike (detail)
Apply OSS 780710 & 485741
Communicate outage to users
Warning msg on screen
Stop the jobs which extract data into delta queues
Clear the delta queues by loading into BW
Check RSA7 in PAE that delta queues are now empty
Run Baseline for Regression tests
Stop Delta queues
Lock Out users
Full Backup
Apply SP's
Upgrade the SAP kernel from 620 to 640
SPAU list review
Apply OSS Notes 768007 & 861890
Unlock Test users (inc. RFC id's on R/3)
Regression testing
Regression sign-off
Remove warning msg
Unlock users
User communication
Plug-in installation (detail)
Communicate outage to users
Warning msg on screen
Apply SAP note 684844
Lock out users
Full Backup
Empty CRM queues
Import and patch Basis plugin PI 2004.1
SPAU list review
Apply OSS 853130
Switch back on flag in TBE11 (app. BC-MID)
Remove warning msg
Unlock users
User communication
Dbase upgrades
Dbase upgrades (detail)
Communicate outage to users
Warning msg on screen
Run Baseline for Regression tests
Stop the Data extract jobs
Full Backup
Lock Out users
Apply FixPak13SAP to DB2 database
Upgrade the SAP kernel from 620 to 640
Apply OSS 725746 - prevents RSRV short dump
Unlock Test users (inc. RFC id's on R/3)
Regression testing
Regression sign-off
Remove warning msg
Unlock users
User communication
PREPARE Process (detail)
Pre-PREPARE Process
RSDG_ODSO_ACTIVATE
Repair Info objects and recreate the views
Communicate outage to users
Warning msg on screen
Run Baseline for Regression tests
Stop the Data extract jobs
Lock Out users
Full Backup
Run RSMDCNVEXIT Using BSSUPPORT ID
If there conversion process runs longer delay the regular backup
Re-run Baselines and sign off
If there conversion process Fails repeat the steps on Sunday after the regular backup
BW work
Back up customer-specific entries in EDIFCT (note 865142)
Activate all ODS objects
Execute report RSUPGRCHECK with flag "ODS objects" (note 861890)
Check Inconsistent InfoObjects - Upgr Guide 4.4; OSS 46272; Convert Data Classes of InfoCubes - Upgr Guide 4.3
Execute report SAP_FACTVIEWS_RECREATE (note 563201)
Make sure Delta queues are empty (RSA7)
Basis Work
Full Backup of BW
Lock users
Unlock id's RFC id's and designated test users
Confirm backup complete OK
Apply OSS 447341 Convert Inconsistent Characteristic Values - Upgr Guide 4.5
Confirm OK to PREPARE
Run PREPARE
Review of results
System Upgrade (detail)
Communicate outage to users
Process errors from PREPARE
Check disk space availability for PAB
Warning msg on screen
Reverse Transport Queries from PAB to SAB & DAB
Change BW to R/3 connection
Get backup put on hold, for Ops to release later
Ensure Saturday night backup is cancelled
Final run of PREPARE
Run Baseline for Regression tests
Clear Delta Queues
Delete Local Transports
Remove process chains from schedule
Lock Out users (with some exceptions)
Confirm to Ops and Angie that we're ready
Full Backup
Incremental backup of Unix files
UPGRADE "START"
Back up kernel
Unpack latest 700 kernel to upgrade directory
Check ids required for upgrade are unlocked
Check no outstanding updates
Turn off DB2 archiving
Open up the client for changes
Stop saposcol, & delete from exe directory
Run the Upgrade
Execute the saproot.sh script
Perform the database-specific actions
Perform follow-up activities for the SAP kernel
Reimport additional programs
Import Support Packages
Call transaction SGEN to generate ABAP loads
Transport Management System (TMS)
Handover to BW Team
SPAU list review
Apply OSS Notes from SPAU
Process Function Module XXL_FULL_API (part of SPAU)
Restore table EDIFCT (if required)
Transport Fixes from our BW Issue list
Convert the chart settings - manually
Perform activities in the Authorization Area
Activate hierarchy versions
Update the where-used list
Execute the conversion program for the product master
Transport New roles to PAB
Unlock selected users
Regression testing
Regression sign-off
Go / No Go decision
Restore if required
Remove warning msg
Tell Ops that the CR is now complete
Lock down PAB
Unlock users
User communication
Perform the follow-up activities for SAP Solution Manager
Reschedule background jobs
Reschedule weekly backup on Ctrl-M
Drinks all round.
Vendors mentioned: dBase
Hope this helps.

Steps to follow in Upgrade from 4.7 to ECC 6.0

Hi ,
As part of Upgrade from 4.7 to ECC 6.0 , Basis team completed Prepare module.
Now Prepare module report says there are some modifications need to be done .
Do i need to make the changes to the adjustments populated in SPDD/ SPAU transaction code before basis team goes for Upgrade ?
If changes are applied to the modifications populated in SPDD / SPAU. How i need to transport these objects ?
Please let me know the steps need to take in transport of these objects .
Cheers,
Reddy

Dear,
Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade, the upgrade will stop at the begin of ACT_700 phase, so you can logon to shadow instance and perform the adjustments in SPDD.
About transaction SPAU that allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.
You have the option to include the SPDD request from previous upgrade,
The PREPARE includes the ADJUSTPRP phase for this purpose. In this
phase, the system searches the global transport directory for comparison
requests from previous upgrades and offers these for inclusion in the
upgrade. If you do not have this request, you may go ahead with the upgrade
and the proceed with the SPDD / SPAU adjustments during the upgrade.
Please refer to the following SAP Notes for more details:
68678 Exporting modification adjustment for 2nd upgrade
610311 Importing a modification adjustment in 2nd upgrade
124522 Importing a modification adjustment in 2nd upgrade
I hope this helps.
Lucio Rodrigues

LONGPOST.LOG Errors during Upgrade from 4.6C to ECC 6.0

Dear all,
We have received the below errors during our upgrade from 4.6C to ECC 6.0.
Basically we have received three types of errors:
1.
4PETG065 RSUPGDEC: Table/structure "BAPE_VBAK" (component "SD-SLS" ) enhanced illegally: Error "2"
2.
A2PESEEF_BADI 103 BAdI implementation "/IRM/BADI_SDDOCFLOW" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZZ_MG_MASS_NEWSEG" must still be migrated A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
3.
3PETG447 Table and runtime object "/SSF/DHEAD" exist without DDIC reference ("Transp. table")
3PETG447 Table and runtime object "/SSF/DTAB" exist without DDIC reference ("Transp. table")
3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
Can anyone help us how to solve this issues.
Thanks & Regards
Senthil

Hi,
Senthil following are ans to ur questions
1. After the SPAU remediation is completed, should I manually release the transport or should I start the upgrade and the upgrade will release that transport?
Ans : Once your SPAU remediation is completed you should release the requests and then start the upgrade of the DEV system.
2. How do we import this SPDD & SPAU transport in the QA and PRD, I mean at what stage of the upgrade we need to specify/ include this transport?
Ans : Now when you start the QA or PRD upgrade at that time you come across a phase during PREPARE called ADJUSTPRP.
Refer following note for further information --
SAPNote 124522 - Importing a modification adjustment in 2nd upgrade
3. Suppose the QA & PRD has more objects to adjust than our Dev box, and this transport will not take care of the delta objects, so in that case how should we remediate, we need to create an other transport request in QA and then it will become two transports?
Ans : First of all this should not be the scenario where you have more modified objects than that in DEV. As all the modfications should take place in DEV first and then should be transported to QA and then PRD. But in such case what you can do is complete the upgrade of QA system and then you are still having 14 days to complete the SPAU objects. So you can make another request which can be transported as a post upgrade activity once the upgrade is completed in production. For SPDD you will have to take care of the SPDD objects if there are different than those in DEV during the ACT_700 phase only or else you might risk data.
This is the reason why SAP always asks you to follow a proper transport path.
4. If our dev box has more objects for remediation than our QA & PRD, then will these objects be also imported into the QA & PRD box?
Ans : Yes, thats why you should be very sure about the SPAU objects that you have found in DEV. You need to compare the objects with QA and PRD and then only make the modifications.
I hope i have answered all your queries.
Regards,
Suhas

Wrong Delivery date determined in Stock transport delivery NLCC from PO

Hi Everyone,
Since we upgraded R/3 from 4.6C to ECC 6.0 we are facing problems in the Stock transport process.
We are using purchase order type NB for moving material from plant X from company 1 to plant Y from company 2. In the stock transport order we enter a delivery date which is the goods receipt date from the receiving plant. In tab "Delivery Schedule" we find the Material Staging date which is 25 days earlier because of the transportation time overseas.
When the materials are available in the supplying plant X we make a delivery. Before the upgrade the MBDAT (material availability date) was copied from the purchase order into the delivery date of the Delivery.
After the upgrade not the MBDAT is copied but the goods receipt date, which is 25 days in the future.
Does anybody know if we can influence this date determination in e.g. customizing.
Thanks in advance for your Help.

Hi,
the whole scheduling in stock transport orders are actually controlled by two settings:
- the sheduling in the purchase order is controlled by the set-up for the stock transfer order (topic "Assign delivery type and checking rule" in IMG). Here you need to flag the "Shipment scheduling" for your purchase order / supplying plant combination. This is important, as otherwise the creation date of your delivery can not be calculated.
- Then, as mentioned before, you need to have DL as default order type for your delivery type NLCC. Even you have no sales order, the sales order type is necessary, because the system always uses the copying routines to fill the necessary data. Now in this case the structure xkomdlgn is used to temporary store the data from the source document (in this case the stock transport order) and to pass it on to the delivery.
--- actually I believe you do not even need to assign DL as default order type in the delivery type setting. If I remember right, at least for the delivery type NL this is hardwired (if no default order type is entered, then DL is used...), I guess it is the same for NLCC...
- But now comes the trick: actually the delivery dates are not copied over from the copying routine (don't ask me why), but they are controlled by the sheduling in the default order type, in this case DL. If you check the sheduling for the sales order type DL("Define scheduling by sales document type"), you should find out that is is not activated - there you go. Activate delivery and transportation scheduling for your default order type, that should do the trick.
Best regards
Juergen

Query from 4.6c to ecc 6

HI
We are upgrading query from 4.6c to ecc 6. We are using Export/Import. When I am exporting query via RSAQR3TR. I am getting error
F Transport dataset AD1D910286 does not exist.
Pls help with solution.
Regards
Ajith

Hi,
you can try to read OSS note 352617 .
Ivan

Error while deploying a PAR file from NWDS into an ECC.

Hi all,
I am getting this error while deploying a PAR file from NWDS into an ECC.
Operation Failed: Please make sure the server is running or check the log (sap-plugin.log) for
more detail.
My server is running properly
1 - Where is sap-plugin.log file? I don´t find it.
2 - Could there be another file with another name with information about the error?
3 - Is there another way to deploy the file directly from the ECC?
Regards,

Hi,
Just make sure you have maintained correct server setting to check the same open the NWDS and follow this path
Windows/ Prefereces / SAP Enterprise Portal
Check the following enteries
Alias
Host
Port
Login etc.
Regards,

Error while RRI from BW reports to ECC CJI3 transaction

Hi All,
When we try to set up RRI from BW reports to ECC CJI3 transaction, we get an error message (Stop message):
You cannot use the report-report interface to call up report RKREP000
Diagnosis
Line Item report RKPEP000 is not suitable for the report/report interface
Procedure
Always enter RKPEP000 as the receiver report for project line items in the report/report interface. This program uses the transfer parameters to determine which line item reports can be accessed.
<b>As per the other reply tried the ABAP Report RKPEP000/3 also ..no use ..
can you please suggest , how to go about this CJI3 issue for RRI , what settings need to be done in the RSBBS ...</b>
We have attemped to use "S_ALR_87013543" as well but the parameters don't go through properly which means when a user jumps from a BW report, they end up at the ECC selection screen of S_ALR_87013543.
Drill through is working for our Cost Center reports. Just not this one in particular.
Any advice would be greatly appreciated.
prasad

Hi,
I'm facing the same problem so please If you have found some solution please tell me what should I do to use RRI from BEX query to CJI3 transaction.
Regards,
Ana

Transport a ztable from 4.7 to ecc 6.0

Similar Messages

Maybe you are looking for