Differences between 4.7 and ecc6

hi all,
help me regarding the differece between 4.7 and ecc 6( only FI/CO) and if possible any documentation on this.
pls send me
thanks
sandeep.ch

Hi Sandeep,
I'm listing out a few differences.
1. Audit Information Support-Offers new roles that support two different business audit approaches
2. Collections Management-It is now possible to create and monitor promises to pay, to create dispute cases, and to display a detailed invoice history.
3. Credit Management: Credit Decision Support-evaluations for analyzing the credit history for a customer, and for analyzing payment or purchase behavior.
Visit this link: http://solutionbrowser.erp.sap.fmpmedia.com/
Visit this thread: SAP ERP Financials
Kindly reply for further clarifications. Award points if the answer was helpful.
Regards,
Siva

Similar Messages

Difference between 4.7 and ECC6

Hi
Could any one explain me the difference between 4.7 and ECC6
Regards
Uday

Hi,
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Regards,
Rakesh

Technical difference between ECC5.0 and ECC6.0

Hi everyone,
Can anybody tell me whats is the Technical difference between ECC5.0 and ECC6.0.
I am doing upgrade from ECC5.0 to ECC6.0 in Retail.
Regards,
Divya

Dear Divya,
When it is a technical upgrade from a lower version to ECC6.0, many objects like includes, Function modules, reports, OSS notes, DDIC objects, BDC/Print programs, SAP scripts, screens will get affected due to the upgradation. So we need to check with all these objects.
u2022 We will encounter short dumps while executing certain programs. This may be due to the usage of obsolete function modules or Unicode errors.
u2022 The BDCs in the upgraded version will become defective as many of its screen field names will be changed during version change.
u2022 Program texts of many programs will be lost. They have to be restored.
u2022 In case of tables, enhancement category has to be provided.
u2022 There is a possibility of losing the variants during upgradation. So care should be taken to retain them before upgradation.
u2022 ECC6.0 is case sensitive, so many of the interface programs will fail to transfer (FTP) files between systems. These objects have to be changed so that the commands passed to the external system be UPPERCASE.
So a developer should be aware of the following:
u2022Unicode programming is followed in ECC6.0. So we need to be aware of it to rectify certain Unicode errors which are likely to occur.
u2022You have to run the transactions SPAU & SPDD to check for list of standard & custom objects that needs modification in the upgraded version.
Check the below link to find more details on usage of SPAU & SPDD transactions
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
u2022Should be aware of the objects that have become obsolete in ECC6.0. They have to be replaced by appropriate ones.For eg.:
--> The WS_* function modules have been replaced by GUI_* FMs in ECC6.0 as WS_* FMs have become obsolete from 4.7
-->Tables like TVARV & TTREX have been replaced by TVARVC & TTREXN respectively in ECC6.0.
u2022In case of tables, we need to specify the Enhancement category.
u2022Due to upgradation, we will lose out some variants. So we should take a back-up before proceeding with the upgradation.
u2022In case of BDC programs, some field names will be changed. So they have to be named appropriately.
Please check with the below links for more details:
SAP Upgrade guide:
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
From ABAP's perspective, the following link helps you:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
For technical upgrade inputs:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
Hope this helps you.
Regards,
Rakesh

Differences Between ECC5.0 and ECC6.0 in Controlling

Sir.
can you Explain?
Differences Between ECC5.0 and ECC6.0 in Controlling
Regards

Hi There,
Check the below link:-
[http://solutionbrowser.erp.sap.fmpmedia.com/Search.aspx]
here enter your source system and target system and the differences will be listed.
Regards,
Gaurav

Screen difference between 4.5B and ECC6

Hi,
Could you kindly provide me with some documnet or link , where i can actually see the screen changes for the standard SAP transactions between the 4.5B and the ECC6 version?
Regards,
Ruchika

main diffeences between SAP 4.7 and ECC 6.0 versions ?
diff between 4.6c to 4.7 abap
difference between SAP 4.6C and SAP ECC6.0
For functional differences please check out the following link:
http://solutionbrowser.erp.sap.fmpmedia.com/
Regards

What is the difference between 4.7c and ECC6

Hi
What are the major differences or the best features in ECC 6.0 for our ABAP
Regards
laxman

hi Laxman,
you can check this for some info
chk this
Difference b/t ABAP4.7 and ECC6.0.
Message was edited by:
Chandrasekhar Jagarlamudi

Difference between ECC5.0 and ECC6.0

Hi All,
I am currently working on ECC5.0. But we now want to upgrade to ECC6.0 from ECC5.0.
Could anybody please let me know what are the technical differences between both the versions.
Also, how can we accomplish the upgrade activity.
Thanks a lot.
Points will be surely rewarded.
Regards,
Himanshu

Hi,
Check this links,
https://forums.sdn.sap.com/click.jspa?searchID=3241668&messageID=3605560
https://forums.sdn.sap.com/click.jspa?searchID=3241668&messageID=3606238
https://forums.sdn.sap.com/click.jspa?searchID=3241668&messageID=3525628
Thanks,
Reward If Helpful.

Differences in 4.7 and ECC6.0.

Hi,
What are the major differences between 4.7 and ECC6.0 for HR module from technical side. How many HR related Enterprise Services are exposed. Do we have any other services for ESS and MSS packages.?
Thanks,
Uma....

Dear Uma,
Please check the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Please award points if found useful.
Regards,
Rakesh

SAP SD--Difference of upgrade between SAP4.7 and ECC6.0

Hi friends,
Somebody can pls tell --Difference of upgrade between SAP4.7 and ECC6.0 in terms of sap SD module or any links for this.
Rahul

Hi Rahul,
Your question is a little general...Maybe you could go to sap help portal to search for the documentation for upgrading to 600.
As I know, we have some new functionality in release 600. For example, shipping point determination with storage location, automaticly outbound delivery creation after saving stock transfer order...
Also the screen is different for most list transactions like VA05.
Regards,
Smile

What are the differences between ECC5.0 and 6.0 new GL functionality

Hi Experts,
What are the differences between ECC5.0 and 6.0 new GL functionality.
If we want to implement IFRS, I think New GL functionality is very helpful, but why sap is recommending only for ECC6.0 new GL functionality, Eventhough this functionality is available in ECC5.0.
Best Regards,
Dharani

Dear,
ECC 5.0 vs. ECC 6.0/SAP ERP 6.0
Functionality not available in the new G/L with mySAP ERP 2004 and ERP Central Component (ECC) 5.0:
Transfer prices
Statistical key figures
Euro translation
Audit Information System (AIS)
Archiving
Data retention tool
Regards,
Chintan Joshi.

Difference between NetWeaver 2004 and NetWeaver 7.0 or 7.1

I am little confused and curious to know the recent changes happening in SAP.
Can you please tell me the differences between NetWeaver 2004 and NetWeaver 7.0 or 7.1
NetWeaver 2004 is named because SAP has released it in 2004
and then we have XI 3.0, XI.7.0(that is PI right) , EP6.0 etc as individual components have different versions released in NewtWeaver suite.
But what is this NetWeaver 7.0.
We have EE5 or ECC6 and WebAs 6.4 or GUI 6.4 or recently GUI 7.o or WebAs 7.0.
How does all these differe, is individual component of NetWeaver upgraded with higher versions or total NetWever is upgraded with a higher version.
Can any one please tell me the exact difference between versions.
If some one has ECC6 installed in their environment does it mean that they have Netwaver components like XI, EP, MDM.. etc are installed or its only R/3, BI etc...
How it works exactly?
Thanks,
Kiran.

Pretty much everything is explained in here:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/706005a3-3bd6-2910-91ae-a2016239bdcf">SAP NetWeaver Process Integration 7.1 Overview of New Capabilities</a>
I think there's a weblog with a concise list somewhere, but I dont have the link saved.
Hope that helps.
James.

Diff between ECC5.0 and ECC6.0

Hi,
This is Ramakrishna,can any one give proper explanation diff between ECC5.0 and ECC6.0
Regards
Ramakrishna

Hi,
Refer following link;
[SAP ERP Solution Browser|http://solutionbrowser.erp.sap.fmpmedia.com/]
Following are the basic differences as far as MM Module is concerned;
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
- Goods receipt
- Goods issue
- Transfer posting
- Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
- To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
- Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
- Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
- Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
- 107: Goods receipt to valuated goods receipt blocked stock
- 109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location

Difference between 4.6 and 4.7 , 4.7 and Ecc

Hi,
Pls help me what is the difference between 4.6c and 4.7 .....
4.7 and Ecc6.0 in MM point of view.

Read the release notes
matt

Difference between customer exit and user exit?

hi experts
difference between customer exit and user exit?

These r the main differences between user exits and customer exits
1) user exits r subroutines where as customer exits r function modules
2) user exits r not upgraded where as customer exits r will upgrade
3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
4) customer exits r reusable where as user exits r not reusable.
Also:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
1. Previously there were only user-exits.
2. Then came the concept of customer-exits.
3. user exits were nothing but subroutines
FORM/PERFORM
called from standard programs.
4. The FORM defintion was placed inside
an empty include file.
5. So It was called EVERYTIME.
and we need to MODIFY/REPAIR the
standard include .
6. Then it came with concept of customer-exit
7. It consists of calling a FUNCTION MODULE,
which is called only if
the user-exit is ACTIVATED (other wise not called)
In this case, the code in put inside
a pre-defined Z include.
8. Functionality of both is same, howerver
we can note the following important differences
a) Customer exit is called only if activated.
(hence, it does not waste resources)
b) in customer exit, REPAIR does not happen
to the standard include.
Exits are basically the hooks whcih SAP has provided to add your own code.
User Exits: These are provided only SD module .
They are Empty subroutines with naming like USEREXIT_.
We need to have Access key to implement them.
Customer Exits: These are enhancement techniques.
There are defined in SMOD and implemented in CMOD.
Types of Customer exits: Function exit, Screen Exit, Menu exit.
User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
Customer Exit,
Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
User Exits: allow you to add additional functions to the SAP standard.
Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
reward points if found useful
regards
palak

Difference between Leading ledger and Non-Leading ledger

Dear friends,
what is the main difference between Leading ledger and Non-leading ledger in New G/L.
Thanks in advance,
Babu.

This concept is introduced in SAP Ecc6.0
Many companies have to maintain books for more than two fiscal years (For example 31st December as per companies act & 31st March as per income tax Act).
So leading ledger & non leading concept helps in maintianing same.
Leading Ledger is the ledger in which all the entries are posted originally. From Leading ledger all entries flow into non keading ledger. You need not pass entries seprately in leading or non leading ledger.
In case your leading ledger is Jan to December, January will be the 1st period & so on.
In case your non leading ledger is April to March, April will be 1st period.
Also, The leading ledger is based on the same accounting principle as that of the consolidated financial statement.
The non-leading ledgers are parallel ledgers to the leading ledger. They can be based for example on local accounting principles
Leading ledger 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 currencies, FYV and posting periods. You can define a second and third parallel currency for your leading ledger for each company code.
Non-leading ledgers are parallel ledgers to the leading ledger. They can be based on a local accounting principle of a country, ex: You have to activate a non-leading ledger for the individual company codes.
Regards

Differences between 4.7 and ecc6

Similar Messages

Maybe you are looking for