【正文】 ? Posting key/account field status custom fields, upon generation bee part of field status configuration, but initial setting is “hidden” 10 New General Ledger Setup/Lessons Learned – Custom Fields – Lessons Learned: ? Add check tables to COBL for dropdown functionality ? BAPI extensions on G/L postings ? Custom fields working well 11 Agenda ? Overview – Project Overview/Scope – Key Client Requirements ? New General Ledger Setup/Lessons Learned – Custom Fields – Segment vs. Business Area – Ledger Definition/Scenarios – Profit Centers in New G/L – Splitting – Allocations/Statistical Key Figures – FI/CO Realtime Integration – Technical Structures ? Conclusions 12 New General Ledger Setup/Lessons Learned – Segment vs. Business Area Key Business Requirements: – Fully balanced balance sheet and P/L by operating unit (major division of the business) – Partial balance sheet (Working Capital) and full P/L by branch ? The Segment is included with New G/L ? Segment is derived by Profit Center (Profit Centers defined for Branch reporting) ? Balanced financial statements can be generated by Segment using Splitting functionality ? All posting line items must identify a profit center in order to ensure full set of financial statements by Segment 13 New General Ledger Setup/Lessons Learned – Segment vs. Business Area Business Area vs. Segment – Both provide balanced financial statements (balance sheet and P/L) by reporting entity other than Company Code – Segment offers SAPdelivered derivation from Profit Center master record (validated “business” definition) – Business Area not used due to derivation。 Segment viewed as “cleaner” solution 14 New General Ledger Setup/Lessons Learned – Segment vs. Business Area – Configuration Step: Assign Segment Scenario to Ledger ? Activating the Segment scenario allows for population of Segment in New G/L 15 New General Ledger Setup/Lessons Learned – Segment vs. Business Area – Configuration Step: Define Segments ? Define the list of Segments to be used 16 New General Ledger Setup/Lessons Learned – Segment vs. Business Area – Master Data Step: Specify Segments on Profit Center master records ? Profit Center specified on posting line will derive Segment from master record 17 New General Ledger Setup/Lessons Learned – Segment vs. Business Area – Configuration Step: Define Splitting Characteristics (Segment set to zerobalance) ? Splitting functionality drives balanced Segment reporting 18 New General Ledger Setup/Lessons Learned – Segment vs. Business Area – Lesson Learned ? Partner Segment derivation functioning mostly correctly except for interpany transactions – Resolution ? Custom program or user exit for Partner Segment derivation under investigation as potential solution – Lesson Learned ? Segment not available on all standard SAP reports – Resolution ? Currently contacting SAP about this issue 19 Agenda ? Overview – Project Overview/Scope – Key Client Requirements ? New General Ledger Setup/Lessons Learned – Custom Fields – Segment vs. Business Area – Ledger Definition/Scenarios – Profit Centers in New G/L – Splitting – Allocations/Statistical Key Figures – FI/CO Realtime Integration – Technical Structures ? Conclusions 20 New General Ledger Setup/Lessons Learned – Ledger Definition/Scenarios Key Business Requirement: – FI/CO to always be in balance ? Client very sensitive to any potential outofbalance points with reporting in FI/CO and Profit Centers ? Profit Center absorption in New G/L (and scope) resulting in client leaning towards New G/L for most reporting ? Cost Center Accounting submodule “dangling” – most cost center reporting performed within New G/L ? Most scenarios activated for Ledger 21 New General Ledger Setup/Lessons Learned – Ledger Definition/Scenarios Ledger Definition: – Leading Ledger delivered by SAP and used in New G/L – Other Ledgers can be defined if needed – Scenarios activated in ledger to capture updates in New G/L 22 New General Ledger Setup/Lessons Learned – Ledger Definition/Scenarios – Configuration Step: Assign Scenarios to Ledger ? All scenarios applicable assigned so as to upd