ECC 5.0 to ECC 6.0 upgrade - role of anABAper

Hi all,
Im an ABAper previously worked on SRM and R/3 modules MM and PP.Now i will be working on an upgrade project for ECC 5.0 to ECC 6.0.
As an ABAPER what should I know to work on an upgrade project?What are the different Technical things I should know.
I have previosuly worked on BADi's and reports.

Hi Ram,
Initially it is teh SPDD and SPAU phase.
SPDD contains the list of all modified standard Data Dictionary objects, like tables, search helps, dataelements, domains,view etc. You have to go to SPDD transaction, click on execute, you get teh following list :
With Modification Assistant
Without Modification Assistant
Deleted Objects
Expand them.
click on each object and press on 'Version' in the tool bar, and in the next screen select the current version and previous version. you can see few differences between the two versions. Now you have analyse and take a call on whethere you have to 'RESET TO ORIGINAL' or 'ADOPT MODIFICATIONS'
SPAU will contain the modified standard repository objects.
Go to SPAU transaction as repeat as mentioned above.
You have to analyse each oject well and then decide which of the two you would choose 'RESET TO ORIGINAL' or 'ADOPT MODIFICATIONS'
Here you can find more info :
http://wiki.sdn.sap.com/wiki/display/ERP6/SPAU+Corrections
You can search in Google or SDN for many links on the topic.
http://lmgtfy.com/?q=spdd+sdn
You can find few documents here
You might also find this helpful
http://www.sapdb.info/sap-ecc6-upgrade/

Similar Messages

Best Practice in Upgrade from ECC 5.0 to ECC 6.0

Dear All,
Can someone help in looking for Best practice in Upgrade from ECC 5.0 To ECC 6.0 Project from Functional FI and CO Side.
Thanks

Moved to a different forum.

ECC Upgrade from ECC 5.0 to ECC 6.0 EHP4 - impact on XI 3.0

Hi,
We are palnning for upgrade our ECC System from ECC 5.0 to ECC 6.0 EHP4. We do not have any plan of upgrade on XI, which is on XI 3.0.
After ECC upgrade please provide the impact on XI 3.0 ?
Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
Thanks.

>>Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
As far as I know, no change is required in XI configuration.
Regards,
Praveen Gujjeti.

Upgrade from ECC 5.00 to ECC 6.00

We are planning upgradation from ECC 5.00 to ECC 6.00. What will be the role of FICO consultant in detail.

check the customization setting after upgrade
run a Unit Test and Integration Test.
run the Report developed

UPGRADE STEPS FROM ECC 5.0 TO ECC 6.00

Hi,
Can anyone of you help me in the upgrade steps (Process) from ECC 5.0 to ECC 6.0.
Thanks in Advance.
Ram

Hello Ramesh ,
Apart from this also download and have a look on look the Upgrade guide .
URL to Download :
www.thespot4sap.com/upgrade_guide_v2.pdf
Regards ,
Santosh Karadkar

Right SAPup version for upgrade from ECC 5.0 to ECC 6.0

Dear Expert!
I am upgrading from ECC 5.0 to ECC 6.0 , but i have a erro, with SAPup tool, I don't know to select right SAPup version, please show me about that, thank you very much!
Tru Hang

Hi,
As anil you have to download the Upgrade guide, therer you could see the clear information -about SAPup.
they have mentioned the issues with SAPup and they have asked us to use new SAPup version due to the issues of Old SAPup version.
have a look at the below notes
821032 Corrections for SAPup release 7.00
1056649 Corrections for SAPup release 7.10
48184 Upgrade: Stopping a running R3up or SAPup
1070771 Do not use SAPup version 7.00/2, build 24.094 !
You can see lots of threads in SDN lot of threads talks about SAPup issues.
-Srini

Does for upgrade from ecc 5.0 to ecc 6.0 we have to pay money for that

Hi All
Does for upgrade from ecc 5.0 to ecc 6.0 we have to pay money to SAP for that.

hi,
asking or teling ?
I think you need not as long as you are with official support . However please contact sap official support in you region

UPGRADE FROM ECC 5.0 TO ECC 6.0 Ehp4

Hai,
Can any one tell me the upgrade strategy from ecc 5.0 to ecc 6.0 Ehp4,also before we upgrade to Ehp4 do we have to upgrade to ecc 6.0 ?If no plz provide me with the link for latest documentation on this .
-regards
Srinivas Bitra

Hi Srinivas,
You can upgrade both in single shot.
You can include EHP4 along with ECC6.0 version upgrade. in BIND_PATCH phase upgade will prompts you to include EHPs if you want. so there you can include your EHP with SAP version upgrade.
You can get all these details in Upgrade guide.
-Srini

US Payroll upgrading from Ecc 5.0 to Ecc 6.o

Hi Experts
My client want to upgrade from Ecc 5.0 to Ecc 6.0 for all modules including US payroll.
please advise me what are the tables in i need to take care? means i need to have copy for double check?
Is any tables which was there in Ecc 5.0 and not available in Ecc 6.0?
I know that we need to have the backup of table T512w and T5uj tables, Apart from these table what other tables i need to check and have backup for double check?
Thanks in advance
Regards

Use following...Good luck...
Tables:
T52D2     This table is used to store processing class values
T512W     In this table, we want to check if someone made changes to the wage types in the SAP name range. We will therefore compare the wage types (only for country code = 10) in the SAP name range (/, M, B*) between two systems.
T512T     In this table, we want to check if someone made changes to the wage types in the SAP name range. We will therefore compare the wage types (only for country code = 10) in the SAP name range (/, M, B*) between two systems
T77S0     For table T77S0, we want to compare the switches that were changed in the SAP name range between two systems.
T511K/P     For these tables, we want to check which constants in the SAP name range were changed that may be reset back to standard.
T591A     For table T591A, we want to check which time constraints and subtypes have been changed, created and deleted
T52EL/Z     For these tables we want to check if any posting attributes of wage types in the SAP name range have been altered.
T556U     This table has a delivery class of E which means that SAP and the customer shares this table but with separate name ranges.
T52D7     This table has a delivery class of E which means that SAP and the customer shares this table but with separate name ranges. Customers are supposed to use name range /9** and 1*** - 9***. This table is used to group wage types.
T54C3     This table has a delivery class of E which means that SAP and the customer shares this table but with separate name ranges. Customers are supposed to use name range /9** and 1*** - 9***. This table is used cumulate wage types.
T52OCR     This table is used to store off-cycle reasons.
Tax Reporter tables     Verify the tax reporter configuration tables to make sure that the standard entries were not changed and overwritten.
Programs:
RPUMKG00     Re-generate all features
RPUBTCU0     Validate BSI connectivity for tax calculation
RHTTCP77     Table configuration needed for process models
RHSOBJCH     Table configuration needed for process models
RPUCT700     Generate all payroll functions and operations
Arti

Upgradation from ECC 5.0 to ECC 6.0

Hi Friends,
As an SD Consultant what would be the roles and responsibilities in the upgradation projects(from 4.6C/4.7E/ECC 5.0 to ECC 6.0)
with regards

HELLO,
Search the form you will get few links.
Also many companies have gone technical upgradation , but not functional upgradation.
Thanks
RK

ECC 5.0 to ECC 6.0 EHP6 upgrade

Hi All,
We have planned to upgrade ecc 5.0 to ecc 6.0 ehp6 upgrade.
Can we upgrade direct ecc6.0 ehp6 using SUM tool ?
Any one have idea Please let me know.
Regards,
Arun.

Hi Arun,
You cannot Upgrade directly to ehp6 because your operating system & database will not support for ehp6 as per PAM.
your target release ERP EHP6 : OS -win 2008 : Oracle 11 g
find below steps
Phase 1
1. Apply latest patches to win 2003 server.
2. Apply latest oracle patches to your current release
3. Upgrade your SAP from ECC5 to EHP5
Phase 2
1. Upgrade your OS from WIN 2003 To 2008
2. Upgrade Oracle from 10 to 11 ( you can upgrade this first phase also)
3. Upgrade ehp5 to ehp6
Thanks
Siva

Changes in functional and technical level on upgrading from SAP ECC 5.0 to ECC 6

Hi Friends,
Need help with the below mentioned questions
What will be the changes in Functional level while upgrading for ecc 5.0 to ecc 6.0?
What will be the changes in Technical level both Abap and Basis?
What will be the changes in Server Hardware level in Upgrading of Servers (Solution Manger,IDES,Dev Server,Prod Server)?
What is change in SAP License level?
Total cost of Project development and Support .
please help me as I need to answer some body .
Thanks in Advance

It seems that you have a combined upgrade - ABAP + Java in your system - is that right? If yes, did you start the Java upgrade in parallel?
Markus

Upgrading ECC 5.0 to ECC 6.0

Dear Friends,
We are planning to upgrade our SAP version from ECC 5.0 to ECC 6.0.
I need some information from you all;
1. What are the advantages.
2. If we upgrade 32 - bit to 64 - bit what is the difference and why 64 - bit SAP is preferring, what would be the main advantages.
Please clear me in this, i need your support to enhance my knowledge before start the proposed.
Regards,
Praveen Merugu

Dear Praveen Kumar Merugu,
Since SAP Basis Release 4.0, the 64-bit SAP kernel has been available. The mySAP.com solutions which are based on Web Application Server 6.10 or higher are - with few exceptions - available as 64-bit versions only for operating systems based on 64-bit-capable hardware.
1. 64-bit mySAP.com, what's behind it?
In order to provide a R/3 system as 64-bit version the source code of the R/3 kernel was re-translated. However, the source code itself was not modified. The functions of the 64-bit and the 32-bit versions therefore do not differ.
Basically, 64-bit software differs from the 32-bit version only in the different manner of addressing the memory. 64-bit software uses a 64-bit address pointer which, in theory, can address 18 billion Gb of memory directly. Actually, a 64-bit application can address a lot less with the different operating systems and the hardware available, but still the addressing of several terabyte (that is several 1000 Gbyte) of memory is possible. This is considerably more than required by the components of the myAP.com software.
For a 32-bit address pointer, the address space is limited to about 4 Gbyte; in reality, even less is available to the application. There are examples where this 4 Gbyte limit prevents an efficient operation of a mySAP.com system.
2. Advantages of the 64-bit technology for mySAP.com
The administration of the SAP system is considerably facilitated.
The SAP software can scale the available hardware (RAM, CPU) to a much higher degree.
3. System requirements for 64-bit mySAP.com
a) 64-bit-capable hardware
A basic requirement for using 64-bit operating systems and 64-bit applications is a 64-bit-capable hardware. In particular the version of the used processors (CPU) determines the 64-bit capability of existing hardware. For information on the compatibility of the hardware with 64- bit operating systems you should contact the responsible person at your hardware partner.
b) 64-bit operating system
For using a 64-bit SAP software, an upgrade to a 64-bit operating system may be required. For releases, please refer to the release notes that are available for each database for each SAP kernel release.
c) 64-bit database
When using a 64-bit mySAP.com software, a combination with a 64-bit database version (RDBMS) is recommended by SAP. Databases of SAP, IBM, INFORMIX, and ORACLE have already been supported as 64-bit versions since SAP release 4.0.
4. Exceptions
a) Operating systems on servers with Intel Pentium processors.
The Intel Pentium processor is a 32-bit processor. For this reason, the SAP Software for Microsoft Server operating systems and Linux will still be available in the 32-bit version for the next years to come. In the long run, SAP will change over to the 64-bit version of the SAP software also on these platforms which requires 64-bit Itanium processors. When changing over to the 64-bit version, SAP will also take into account the investment security of their customers.
b) DB2 UDB for Unix and Windows (DB6):
Since the DB2 UDB database allows a mixed operation of 32-bit and 64-bit database client applications as of version 8 only, SAP will make available 32-bit SAP Software of Release 6.x for DB2 UDB systems until the end of 2003.
5. Availability of 64-bit mySAP.com solutions
The latest information on R/3 Release planning can be found on the SAP Website under http://sapnet.sap.com/platforms. Detailed information on the platform combinations released by SAP can be found in SAP release notes under the XX_SER-SWREL component.
All existing 32-bit 4.x releases are supported with 32-bit versions of the SAP kernel until futher notice.
6. Availability of the different 64-bit mySAP.com solutions
a) R/3
R/3 is available as of release R/3 4.0.
b) Business Information Warehouse (BW)
Business Information Warehouse is available with 64-bit SAP kernel as of version 2.0A.
c) Enterprise Buyer Professional (EBP), former BBP
EBP is available with 64-bit SAP kernel as of version 2.0A.
d) Customer Relationship Management (CRM)
Customer Relationship Management is available with 64-bit SAP kernel as of version 1.2.
e) Advanced Planner and Optimizer (APO)
APO is available with 64-bit SAP kernel as of version 3.0A.
7. Possible combinations of 32-bit and 64-bit
a) Possible combinations within a SAP system
For the SAP releases as of 4.0B, a mixed use of 32-bit and 64-bit instances within one SAP system is supported on application server level. 32-bit and 64-bit SAP instances must reside on separate servers, however. The mixed use of 32-bit and 64-bit SAP instances on the same server is not supported.
For the SAP releases as of 4.0, the combination of 32-bit SAP application servers with a 64-bit database server, and of a 32-bit database with 64-bit application servers is possible in principle. Releases for such combinations are granted in justified cases. In case of a mixed installation of a 32-bit SAP application server and a 64-bit database server or vice versa on a shared host, you need to make sure in particular that the SAP application server uses the correct database libraries. A subsequent manual configuration may be required. The database upgrade guide describes how to proceed (see also Ora Note 406140 or 539922, for example).
b) Possible combinations within a mySAP.com system landscape
Transports with 'tp' or 'R3trans' between 32-bit and 64-bit SAP systems are possible.
There are many differences between a 32-bit and a 64-bit SAP system, e.g. the parameter settings of the HP-UX operating system kernel and SAP kernel that do not take into account a combined configuration of test and production systems.
All features and functions that depend on the parameter settings cannot be sufficiently tested for a 64-bit production environment in a 32-bit test or development system. This includes in particular the effect of the parameter settings on the memory management and the performance of a SAP system.
For this reason, SAP recommends to have at least one other 64-bit system available for each 64-bit production system within the transport track where the availability of SAP kernel, operating system and database can be tested.
c) Interoperability with 32-bit add-on products
For software products of third-party suppliers used with SAP software it is not important whether a 32-bit or a 64-bit SAP R/3 kernel is used. The use of a 32-bit or 64-bit SAP R/3 kernel is completely transparent for add-on products of third party suppliers as long as these products use SAP certified interfaces.
32-bit and 64-bit applications that directly access shared memory segments cannot be combined. For add-on products of SAP with direct access to the shared memory you have to ensure the bit size corresponds to that of the SAP kernel. This is e.g. valid for the product 'saposcol'. With a 64-bit SAP kernel it is only possible to use a 64- bit saposcol.
8. Preparations for the installation of a 64-bit SAP kernel
In addition to the basic requirements, 64-bit hardware, 64-bit operating system and 64-bit database the following aspects are to be taken into account for preparing the installation of a 64-bit SAP kernel:
a) Shared memory
Since there is virtually no limit of the shared memories in the case of a 64-bit SAP you can set large sizes for all buffers. (Refer to the recommendation of SAP Note 103747 under III).
b) Swap space
Addressing a very large memory requires the configuration of a correspondingly large swap space. To use a 64-bit SAP kernel you must at least configure 20 GB swap space.
c) Operating system kernel parameters
Except for some cases the parameter settings of the operating system kernel for a 32-bit and a 64-bit R/3 are identical. he most important operating system kernel parameters and their values recommended by SAP can be found in Note 146289. For HP-UX please also refer to Note 172747.
INSTALLATION TIPS
The installation of the 64-bit SAP kernel for Release 4.0B and 4.5B is carried out manually. First the system requirements described above must be fulfilled . The installation of the 64-bit SAP kernel is then simply performed by replacing all existing 32-bit executables of the SAP kernel with the corresponding 64-bit executables.
Example:
Initial state:              SAP release       4.5B
             SAP kernel        4.5B 32-bit
             RDBMS             ORACLE 8.0.5 64-bit
             OS:               HP-UX 11.00   64-bit
Target:              SAP release       4.5B
             SAP kernel        4.5B 64-bit
             RDBMS             ORACLE 8.0.5 64-bit
             OS:               HP-UX 11.0   64-bit
Procedure:
The procedure is described in detail in the following SAP notes:
SAP note: 146248    Installation of SAP R/3 4.0B 64-bit kernel
SAP note: 155355    Installation of SAP R/3 4.5B 64-bit kernel
Installation of the 64-bit SAP kernel as of SAP Basis release 4.6B
As of SAP release 4.6B the installation tool R3SETUP is delivered and supported as 64-bit version on CD.
System copy with 64-bit SAP 4.5B (ORACLE)
While unloading an Oracle database with the R3SETUP (32-bit version) it cannot connect to the database if a 64-bit SAP kernel is used.
If you use the 64-bit SAP kernel for Oracle you automatically use a 64- bit Oracle client library as only a 64-bit library can be loaded for a 64-bit SAP kernel. However, since the R3SETUP is only available as 32- bit version up to Release 4.5B and since the 32-bit R3SETUP is not compatible with the 64-bit Oracle client library the error mentioned above occurs in the case of a system copy (in particular during the unload).
While loading the 32-bit SAP kernel is unpacked first so no problems should occur here.
In order to be able to perform a system copy (unload) with the 32-bit R3SETUP follow the instructions of Note 177724.
UPGRADE TIPS
Upgrade from a 32-bit to a 64-bit SAP system
The operating system upgrade and the SAP upgrade should be performed separately (if possible). The same applies to the change of the 32-bit SAP kernel to the 64-bit kernel to ensure that the phases can be tested and completed separately.
As of 4.6C the change to a 64-bit SAP kernel will be supported during an upgrade.
That means that the individual phases like operating system upgrade, database migration and kernel exchange should be included in the planning.
Database
For a database, you need to check whether the binaries have to be replaced during the operating system upgrade. The binaries for HP-UX 10.20 do not run on HP-UX 11, for example!! The corresponding Oracle software for HP-UX 11 must be installed. When upgrading to a 64-bit Oracle 8 version you have to migrate to a 32-bit Oracle 8 version fist. Only then, you can import the 64-bit RDBMS.
The SAP upgrade should always be carried out before the 32-bit SAP kernel is replaced by the 64-bit SAP kernel, since the latter includes an adjustment of the UNIX kernel and the instance parameters.
Sample scenario 1:
     Initial state:                          R/3 release 3.1I
                         SAP kernel 3.1I (32-bit)
                         RDBMS:      ORACLE 7.3.4 (32-bit)
                         OS:         HP-UX 10.20 (32-bit)
    Target:                         R/3 release 4.6B
                        SAP kernel   3.1I (32-bit)
                        RDBMS:       ORACLE 8.0.5 64-bit
                        OS:          HP-UX 11.0 64-bit
Procedure:
1st alternative:
9. Upgrading the operating system to HP-UX 11.0
10. Installation of the 7.3.4 RDBMS binaries for HP-UX 11.0
11. Migration to 8.0.5 32-bit RDBMS for HP-UX 11.0 (see the instructions guide). This step is required as the database migration from 7 to 8 must always be performed via Oracle 8 32-bit.
12. Subsequent exchange of the RDBMS 8.0.5 32-bit to 8.0.5 64-bit. This step can be performed after the upgrade as well (prior to the SAP kernel exchange).
13. Upgrade of the R/3 system to 4.6B with a 32-bit SAP kernel. The PREPARE unpacks the 32-bit tools automatically so that no manual intervention is necessary.
14. Exchange of the SAP R/3 kernel on 64-bit prior to the upgrade and adjustment of the R/3 kernel and instance parameters
2nd alternative:
15. Migration to 8.0.5 32-bit on HP-UX 10.20
16. Operating system upgrade to HP-UX 11.0
17. Exchange of RDBMS binaries on 8.0.5 64-bit for HP-UX 11.0
18. Upgrade of the R/3 system to 4.6B with 32-bit SAP kernel
19. Exchange of the SAP R/3 kernel on 64-bit
Or (if required)
3rd alternative:
20. Oracle migration to 8.0.5 32-bit (on HP-UX 10.20)
21. Upgrade of the R/3 system to 4.6B with 32-bit SAP kernel
22. Operating system upgrade to HP-UX 11 64-bit
23. Exchange of the Oracle binaries on 8.0.5 64-bit
24. Exchange of the SAP kernel on 4.6B 64-bit
Sample scenario 2:
Initial state:                R/3 release    3.1I
               SAP kernel     3.1I (32-bit)
               RDBMS          Oracle 7.3.4 (32-bit)
               OS             HP-UX 10.20 (32-bit)
Target:               R/3 release     4.5B
              SAP kernel      4.5B 64-bit
              RDBMS           Oracle 8.0.5 64-bit
              OS              HP-UX 11.0 64-bit
Procedure:
The procedure is similar to the one described in the 1. scenario. However, in this case it is not possible to already import the 64-bit SAP kernel in the upgrade phase KX_SWITCH as the 64-bit kernel for Release 4.5B will not be delivered on the upgrade CD. The import of the 64-bit SAP kernel must be manually performed after the SAP upgrade. Release 4.5B will not be delivered on the upgrade CD. The import of the 64-bit SAP kernel must be manually performed after the SAP upgrade.
Do let me know in case of any queries.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh

Upgrade from ECC 5.0 to ECC 6.0 FICO

Hi,
Can anyone provide me the configuration documents with regard toUpgrade from ECC 5.0 to ECC 6.0 in FICO or brief the steps to be done. Plz do reply me at the earliest.
my email ID: [email protected]
thanks
suresh arya

Hi suresh,
1.Activate the New General Ledger Accounting by a single click on the clock icon
2.You will reach to change view "activation of New GL A/cg" detail screen and tick the checkbox and save.
3. After activation of New General Ledger Accounting, you exit the IMG screen When you re-enter , you find that a new node is added Financial Accounting (New)
4.After activation of New General Ledger Accounting , a new sub node appears in the IMG structure.
This sub node is Define Segment
The menu path is:
SAP Customizing IMG ---> Enterprise Structure -
> Definition ---> Financial Accounting ---> Define Segment
In this IMG activity, you define your segments.
If you then define your profit centers, you can enter an associated segment in the master record of a profit center. The segment is then derived from the assigned profit center during posting.
5.Activation has created a new field in Profit Center Master Record : the SEGMENT
6.Leading and Non- Leading Ledgers
In General Ledger Accounting , you can use several Ledgers in parallel. This allows you to produce financial statements according to different accounting principles. A ledger uses several dimensions from the totals table it is based upon. When defining Ledgers , one must be defined as the Leading Ledger . The Leading Ledger is based on the same accounting principles as that of the consolidated financial statements. It is integrated with all subsidiary ledgers and is updated in all company codes. This means that it is automatically assigned to all company codes. In each company code, the Leading Ledger receives exactly the same settings that apply to that company code : the currencies, the fiscal year variant and posting period variant .
You must designate one of your ledgers as the Leading Ledger. It is not possible to designate more than one ledger as the leading ledger.
The menu path is :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
> Ledger -
> Define Ledgers for General Ledger Accounting
Clicking on the checkbox identifies one of your ledgers as the Leading Ledger.
7. Activation of Non Leading Ledgers
Non Leading Ledgers are parallel ledgers to the Leading Ledger . They can be based on local accounting principle, for example. You have to activate a non- Leading Ledger for individual company codes. Non- Leading Ledgers can have different fiscal year variants and posting period variants per company code to the Leading Ledger of this company code.
The menu path is :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
> Ledger -
> Define and Activate Non Leading Ledgers
8.Assign scenarios to ledgers
A Scenario combines Customizing settings from different business views. Each business view specifies which posting data is transferred from different application components in General Ledger Accounting, such as cost Center update or Profit Center update .You assign the desired scenarios to your ledgers. For each ledger, you define which fields are filled with posting data from other application components.
SAP delivers a number of scenarios in the standard system. It is not possible to create additional scenarios.
The menu path is:
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
>Fields -
> Display Scenarios for General Ledger Accounting.
9. Cost of sales accounting
Cost of sales accounting is a way to create a profit and loss statement (P&L) for a company by comparing the revenues to the costs or expenses incurred to obtain these revenues.
The expenses are mainly divided by functional area such as:
Manufacturing
Administration
Sales
Research and Development
We can activate Cost of Sales Accounting by the following menu path :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
>Ledger------> Activate Cost of Sales Accounting
I hope this helps you
Assign points if useful
Regards
Genie

Tips / Lesson Learn: Upgrading from ECC 5.0 to ECC 6.0 w/ Unicode

Hi
We are looking into moving from ECC 5.0 to ECC 6.0 w/ EP7 and doing the unicode path on as well.
What are some lesson learn you guys could share in potential issue may occur in the HCM realm?
We don't currently have inhouse payroll, using PU12 to interface that information out.
If you could share some past experiences on what could occur during this upgarde caused by going to ECC 6 or even by the unicode patch would greatly be appreciated.
Thanks,

THe guru of ECM on SDN
nice to see you around. came across your tips and tricks regarding SAP HCM.and also for ECM.
you have dne a good job . i am new in this field but soon would have skills like you
Regards
Waqas Anwar

ECC 5.0 to ECC 6.0 upgrade - role of anABAper

Similar Messages

Maybe you are looking for