SAP BLOG SAP Central Finance & Configuration Data Harmonization

SAP Blog

Kayıtlı Üye
Katılım
22 Ara 2017
Mesajlar
1,743
Tepki puanı
7
Puanları
6
2N.png


Wherever an organization thinks about SAP Central Finance first topic which pops up is data harmonization as SAP Central Finance given an opportunity to harmonize the data which is not done in legacy or due to the fact that legacy is based on M&A the data is segregated.

There are TWO components of Data Harmonization:

1N.png


In this blog the focus is on Configuration Data. Lets look at the list first which comprises of configuration data:

  • Company Codes
  • Controlling area
  • Credit Control Area
  • Ledger
  • Fiscal Year Variant
  • Country/Region
  • Plants
  • Sales Organization
  • Purchase Organization
  • Payment Method
  • Payment Terms
  • House Bank
  • Order Types
  • Business Area
  • Credit Segment
  • Unit of Measure
  • Exchange Rate Types
  • Tax Procedures
  • Functional Area
  • Company/Trading Partner
  • Document Types
  • Many more…

Now let’s see how these can be managed.

Please note that the information provided here is based on experience from CFIN projects. There is no right or wrong as the design decisions are organization/projects specific.



Object
Recommendation
Options
Potential Solution
Company CodesRecommended to keep 1:1 mapping.N:1 mapping can be doneCase by case study needed as N:1 mapping is not support by SAP in certain cases
Controlling AreaNADepends on Organizational DesignN:1 or 1:1 both choices are available
Credit Control AreaNADepends on Organizational DesignN:1 or 1:1 both choices are available
LedgerThis is mandatory in S/4HANA, even this is not in use in classic GL systemsDefine Ledgers based on the requirements – Leading/Non-LeadingConversion from Classic GL or Accounts based approach to ledger based is customization as SAP does not have any standard functionality
Fiscal Year VariantRecommended to keep same as in ECCChange can be done via customization. Extensive testing neededIf its same FY then standard SAP approach is sufficient
Country/RegionsKeep standardStandard or Custom countries (if custom exists in ECC)1:1 mapping recommended
PlantsNADepends on Organizational DesignN:1 or 1:1 both choices are available
Sales OrganizationIf needed as part of reporting design or future architecture then should be taken caseCFIN mandatorily does not need this field for accounting/CO document replicationN:1 or 1:1 mapping supported. If not needed as part of design, this can be ignored
Purchase OrganizationIf needed as part of reporting design or future architecture then should be taken caseCFIN mandatorily does not need this field for accounting/CO document replicationN:1 or 1:1 mapping supported. If not needed as part of design, this can be ignored
Order Types (Cost Objects)
Choose Cost Object Cardinality based on future design

(Cost Objects types and available mapping listed here — >>)

· Product Cost Collector :pCC

· Internal Order : IO

· Prod Order to PCC

· Quality Order :QM

· Process Order to IO

· Maintenance Order :MO

· MO : Internal Order

· WBS:WBS

· Project: Project
Based on order category N:1 & 1:1 are support
Business AreaDepends on usage
1:1 Mapping

N:1 Mapping or even ignore and clear the field
Segment/PC are better in terms of future design
Credit SegmentNot needed for CFIN purposesCustomer DesignCustomer Design leads
Exchange Rate TypesRecommended to HarmonizeMapping can be doneCustomer Design leads
Unit of MeasureRecommended to HarmonizeMapping can be doneCustomer Design leads
Functional AreaRecommended to harmonizeN:1 or 1:1 MappingMost of the cases it is a derived field
Tax ProceduresMostly based on countries1:1 mapping1:1 Mapping
House BankHarmonization RecommendedNot needed for CFIN purposes but needed for Central PaymentCustomer Design leads
Payment MethodHarmonization RecommendedNot needed for CFIN purposes but needed for Central PaymentCustomer Design leads
Payment TermsHarmonization RecommendedNot needed for CFIN purposes but needed for Central PaymentCustomer Design leads
Company/Trading Partnerbusiness Design and Intercompany processes leadsNACustomer Design leads
Document TypeRecommended to move to Standard document types1:1 or N:1 MappingMappings

Their are several more objects which are not immediately important to think about like:

  1. Order Groups
  2. Cost Element Groups
  3. Financial Statement Version
  4. Controlling Version
  5. Cost Center Attributes
  6. Project Type

In my next blogs i will talk about master data objects.

Keep reading and share your challenges related to CFIN Implementations…

Okumaya devam et...
 
Üst