MD102 Umoja Master Data and Coding Block Overview. Umoja Master Data and Coding Block Overview Version 16 1

Transcription

1 MD102 Umoja Master Data and Coding Block Overview Umoja Master Data and Coding Block Overview Version 16 Last Copyright Modified: United 14-August-13 Nations 1

2 Agenda Course Introduction Umoja Master Data Overview Umoja Coding Block Overview Course Summary Course Assessment Course Survey 2

3 Course Overview The purpose of the Umoja Master Data and Coding Block Overview course is to explain the concept of Master Data and Coding Block in Umoja. Prerequisite Review You should have completed the following prerequisite courses: Umoja Overview Course Duration: 1 hour and 30 minutes 3

4 Course Objectives After completing this course, you will be able to: Describe the Umoja Enterprise Structure Explain the concept of Reference Data, Master Data and Transactional Data Explain how Reference Data is used in Umoja Explain the use of Master Data based on the UN operating model Describe the benefits of Master Data Explain how Master Data is used in the Umoja Coding Block 4

5 Agenda Course Introduction Umoja Master Data Overview Umoja Coding Block Overview Course Summary Course Assessment Course Survey 5

6 Module 1 Objectives After completing this module, you will be able to: Describe the Umoja Enterprise Structure Describe the classification of data into Key Reference Data, Master Data, Transactional Data and Reporting Data Explain the concept of Key Reference Data and Master Data Describe the benefits of Master Data Describe the Key Reference Data and common types of Master Data used at UN Explain Master Data Management at global and local level 6

7 Key Terminology Key Term Key Reference Data Master Data Coding Block Description It is the data that is set up to configure the Umoja system for specific needs of UN. It defines the highest level boundaries in the Umoja system. It tends to be static and generally does not change after it has been added to the system. It is centralized data used to support business processes across the organization. It drives all business transactions, applications, reports and decisions and creates a single source of recording and reporting for an organization. It is shared or linked across modules avoiding the need to enter data in various application areas. It is a tool that: Describes the data structure for recording financial transactions Is used for revenue and expense financial transactions Is comprised of Coding Block elements that provide different financial views Allows the user to populate only required fields (that is, to derive related fields) 7

8 Umoja Enterprise Structure The Umoja Enterprise Structure defines the operational and organizational functions of the Umoja system. It impacts how: Transactions are processed Balances are aggregated Reporting is generated The Umoja Enterprise Structure meets the compliance needs of the UN (IPSAS/financial statement, reporting, auditing and controls) while supporting efficient and flexible processes for operations. 8

9 Umoja Enterprise Structure The foundation elements of the Enterprise Structure are: Company Code (1000) Controlling Area (1000) Funds Management Area (1000) In accordance with UN financial regulations and rules, the currency for each foundation element is USD. On all applicable Umoja screens, these foundation element numbers will be defaulted. With the Umoja Enterprise Structure in place, let s now see how data becomes a crucial part of each Umoja transaction. 9

10 Introduction to Data Every organization runs on data and a set of processes. As the level of information increases over time, data becomes complex and difficult to manage. If data is not stored and maintained properly, it leads to significant losses in productivity across the organization. Thus, it is extremely critical for the organization to create a centralized data source. In Umoja, this centralized data is called Master Data. In order to understand how Master Data is used, we first introduce the way Umoja classifies different types of data. 10

11 Data Classification The Umoja system structures data into different groups, depending on its function and purpose. Day-to-day data, which depends on accurate master data Example: Purchase Orders, Financial Postings Created from Umoja Ecc for operational or regulatory purposes Example: Material Document List, Cost Center Line Items Defines system bounds Example: Business Area, Plant Key data that serves as a basis for transactions Example: Materials, Funds Note: Transactional Data and Reporting for each process is covered in the corresponding overview and Level 3 courses. 11

12 Data Classification: Key Reference Data Definition Key Reference Data is set up to configure the Umoja system for specific needs of the UN. It defines the highest level boundaries in the Umoja system. It tends to be static and generally does not change after it has been added to the system. Key Points There is one set of Key Reference Data used across Umoja. This set is: Segment Segments are IPSAS required thematic areas achieved in the system using Functional Area Master Data. Segments are used for financial statement reporting and include PK segments, non PK segments and Unallocated segments (discussed in the next slide) Business Area A classification of UN entities operating in Umoja that is recorded on every financial transaction for example, OAH, PKM, SPM, region of commissions, agencies of funds and programs, etc. Plant A location where materials are produced, purchased, stored, inventoried, shipped, received and valuated, or from which services are provided (Mission/Support Center in Peacekeeping, Country for HQ and OAHs). 12

13 Data Classification: Key Reference Data Segments Definition Segments are Key Reference Data elements used for financial statement reporting, and are divided into PK segments, Non PK Segments and Unallocated segments. PK segments represent PK thematic areas. PK missions usually contribute to at least one substantive thematic area. The non PK segments represent the current budget sections of the Secretariat. "Unallocated" segments are for all those postings that are not directly attributable to a segment. Key Points These are examples of the three types of segments used across Umoja: PK Segments 201PEACEKE Peacekeeping Operations 202PEACONS Peace Consol, Cap Build, and Extension State Auth 206PKSUPMG Peacekeeping Support and Management Non-PK Segments 101PLCYMAK Overall policy-making, direction and coordination 106HUMANRI Human rights and humanitarian affairs 112SECSAFE Safety and security Unallocated Segments 199UNALLOC Unallocated RB 299UNALLOC Unallocated PK 13

14 Data Classification: Master Data Definition Master Data is centralized data used to support business processes across the organization. It drives all business transactions, applications, reports and decisions and creates a single source of records and reports for an organization. It is shared or linked across modules avoiding the need to enter data in various application areas. Key Points The characteristics of Master Data are: It is the key non-transactional data that defines the way UN classifies transactions moving forward. It is required to process system transactions. It tends to be stable and generally does not change after it has been added to the system. It allows data to be categorized based on hierarchy (classification of relationships of data) and/or group (for reporting purposes). 14

15 Data Types: Business Partner (BP) An important Master Data is the Business Partner (BP). It defines the person, group or an organization with whom the UN has a business interest. A BP can be assigned one or more different roles, which determines how the BP can be used in Umoja. Examples of BP roles are as follows: Business Partner Vendor A vendor is a Business Partner role from whom goods or services can be procured. Customer A customer is a Business Partner role to whom goods or services are provided. Sponsor A sponsor, or donor, is a Business Partner role that represents a government, institution or individual providing funding to the UN. 15

16 Business Partner Groups in Umoja Each existing entity at the UN is assigned to a BP Group. The BP Group then defines the role of a BP in the system. The BP Groups are as follows: Member States Non-member States Other Governmental Entities UN Agencies, Funds and Programs Individuals (Staff Members, Retirees, Survivors) Individual Consultants and Contractors NGO s Commercial Vendors 16

17 Business Partner Example All entities in the Commercial Vendors group are entered in Umoja with the following roles: Vendor, Customer and Sponsor. Since Company ABC is a Commercial Vendor, it is a BP with three roles. It is available to use for any transactions that involve a Vendor, Customer or Sponsor. BP Group Commercial Vendors Vendor Customer Sponsor 17

18 Business Partner Master Data Components Key components of the general BP Master Data include: Unique ID number BP Number Address, telephone number, etc. Contact Information Business Partner Banking details Banking Information Currency, payment terms and payment method Payment Condition 18

19 Data Types: Material/Service The common types of Master Data used at UN include: The Material Master Data contains all information about the products procured, stored and shipped by the UN. Material The Service Master Data is equivalent to the Material Master for all services procured by the UN. Service 19

20 Material and Service Master Data Components Key components of the Material/Service Master include: Unique ID of a material/service Product ID Example: (Projector: Dig) Type of product or service. Matches the equivalent UNSPSC classification. Characteristics to enable material management Product Category Example: (Projectors, Supplies) Material Characteristics Example: Unit of Measure = Each Master Data Objects Short and long description, G/L Account Code derived from product category Other Physical or Financial Characteristics 20

21 Data Types In addition, there is a large set of finance-related Master Data and Key Reference Data maintained in four modules: Financial Accounting (FI), Controlling (CO), Funds Management (FM) and Grants Management (GM). The data elements are: Financial Accounting Controlling (Cost Accounting) Funds Management Grants Management Segment Business Area G/L Account Fiscal Year Profit Center Cost Center Internal Order WBSE (Project Systems) Cost Element Functional Area Funds Center Funded Program Commitment Item Budget Period Fund Grant Sponsored Program Sponsored Class Grant Validity Period* Later in this course, we will demonstrate how the Umoja Coding Block is used to keep track of all these elements. Note: While the Grant Validity Period is part of the Coding Block, it is not a Master Data or Key Reference Data. 21

22 Master Data Benefits Umoja Master Data establishes one common language as the UN carries out its day-to-day business transactions. The benefits of Master Data are: It creates a single version of data and establishes boundaries to change Master Data. The UN can avoid data duplication and maximize data consistency across geographical locations Instead of maintaining separate instances of one data element, Master Data characteristics allow each piece of data to be used in multiple ways Allows the UN to have controlled use of data through methods such as workflows It allows the data to be readily available. Users have the ability to verify that entries exist and select existing Master Data via look-ups when processing transactions It provides consistent financial reporting in accordance to the UN Financial Rules and Regulations that support IPSAS requirements Note: The various attributes of each Master Data are covered in the corresponding Level 3 courses. 22

23 UN Operating Environment: Before and After Master Data The implementation of Master Data will synchronize data across the UN with one centralized data source, thereby avoiding data duplication. Before Master Data Implementation Data Source UNIFIL Data Source UNSCOL Data Source UNAMID Data Source IMIS-UNHQ After Master Data Implementation UNIFIL UNSCOL UNAMID Master Data (Centralized Data Source) IMIS-UNHQ 23

24 Master Data from Other Systems It is important to note that Umoja will coexist with several systems during the Umoja implementation. In order for Master Data in Umoja to be synced across all systems, Master Data is either automatically converted or manually entered into both systems. IMIS SUN Galileo Progen Local Projects Real Estate Procurement Commercial 24

25 Central Master Data Team Manages Master Data elements Interacts with the Transactional User Central Master Data Team In order to establish a consistent system of record, Master Data needs to be properly created, maintained and distributed. UNHQ has identified one Central Master Data Team to govern this process and centralize business control and compliance. Responsibilities of the Central Master Data Team include: Creating, modifying or deleting Master Data records based on requests submitted by the Transactional User Overseeing the data conversion process between Umoja and legacy systems Note: Within Umoja, Transactional Users can only display Master Data (with a few exceptions). Users will reference the data governance processes and forms to update each Master Data element. 25

26 Learning Checkpoint 1 Which of the following is NOT an example of Master Data? Select the correct option. A. Service Master B. Business Partner C. Controlling Area D. Material Master 26

27 Learning Checkpoint 1 Which of the following is NOT an example of Master Data? Select the correct option. A. Service Master B. Business Partner C. Controlling Area D. Material Master Option C is the correct answer. Controlling Area is not an example of Master Data. 27

28 Learning Checkpoint 2 With a few exceptions, can only display Master Data records. Fill in the blank with the correct option. A. Transactional Users B. Master Data Management Team C. Business Users and Master Data Management Team D. Vendors 28

29 Learning Checkpoint 2 With a few exceptions, can only display Master Data records. Fill in the blank with the correct option. A. Transactional Users B. Master Data Management Team C. Business Users and Master Data Management Team D. Vendors Option A is the correct answer. With a few exceptions, Transactional Users can only display Master Data records. 29

30 Module 1 Summary The key points covered in this module are listed below: The Umoja Enterprise Structure defines the operational and organizational system foundation for each major component (finance, logistics, etc.), including the currency The Umoja system classifies data as Key Reference Data, Master Data, Transactional Data and Reporting Data Key Reference Data is set up to configure the Umoja system for specific needs of the UN Master Data is centralized data used to support business processes across the organization The Master Data Management team will create, maintain and distribute Master Data along with centralizing business control and compliance 30

31 Agenda Course Introduction Umoja Master Data Overview Umoja Coding Block Overview Course Summary Course Assessment Course Survey 31

32 Module 2 Objectives After completing this module, you will be able to: Describe Simultaneous Posting Explain the concept of the Umoja Coding Block Identify the modules containing elements of the Umoja Coding Block Explain Derivation Describe how the UN Classification Requirement is captured in the Umoja Coding Block 32

33 Umoja Coding Block Umoja Modules As you recall, there is a large set of finance-related data maintained in four modules: Financial Accounting (FI) Controlling (CO) Funds Management (FM) Grants Management (GM) The Master Data from each module, in addition to some Key Reference Data, make up the Umoja Coding Block. In this module, we demonstrate how the Umoja Coding Block is used to keep track of all these elements. Definition The Umoja Coding Block is a tool that: Describes the data structure for recording financial transactions Is used for revenue and expense financial transactions Is comprised of coding block elements that provide different financial views Allows the user to populate only required fields (that is, to derive related fields) 33

34 Umoja Main Ledgers Each module also maintains a ledger and generates documents that make use of the coding block elements. These ledgers work in sync so that when a user posts a transaction in one ledger, corresponding entries are created in the other three. These are the four main ledgers of Umoja: General Ledger (maintained in the FI module) Controlling Ledger (maintained in the CO module) Funds Management Ledgers (maintained in the FM module) Grants Ledger (maintained in the GM module) General Ledger (G/L) Controlling Ledger FM Ledgers Grants Ledger The G/L only records actual postings. Every financial transaction conducted in Umoja has a corresponding posting within the G/L. The Controlling Ledger records postings used for cost and management accounting. The FM Ledgers records budgetrelevant transactions, such as budget, consumption, budgetary resources, etc. and provides budget availability. The Grants Ledger records grant-relevant transactions. 34

35 Chart of Accounts The chart of accounts on the General Ledger are as follows: G/L Accounts in FI Balance Sheet Accounts 1xxxxxxx Current Assets 2xxxxxxx Non Cur Assets 3xxxxxxx Cur Liabilities 4xxxxxxx Non Cur Liab. 5xxxxxxx Net Assets Revenue and Expense Accounts 6xxxxxxx Revenue 7xxxxxxx Expense Expense Accounts, Internal Only 75xxxxxx Internal 86xxxxxx Internal (Statistical) 88xxxxxx Memo 35

36 Simultaneous Posting Each finance-related module names and stores data differently. This provides flexibility to perform different analysis within modules. To ensure that data remains consistent across the organization, Umoja automatically links data elements across modules: Umoja uses the concept of Simultaneous Posting for transactions in one module to be automatically posted in all other corresponding ones This provides a control point: if a transaction does not post simultaneously in all modules, then the transaction will fail and prompt the user with an error message FI CO FM Centralized Master Data User enters transaction into one module GM Simultaneous Posting allows same transaction to be posted in all corresponding modules Data is stored in each module for different analysis 36

37 Umoja Coding Block Elements Definition The corresponding coding block elements for each module and ledger are as follows: Financial Accounting Controlling Funds Management Grants Management G/L Account Business Area Segment Fiscal Year Cost Element Cost Center Internal Order WBSE (Project Systems) Profit Center Commitment Item Fund Funds Center Funded Program Functional Area Budget Period Sponsored Class Grant Sponsored Program Grant Validity Period 37

38 Coding Block: Financial Accounting Elements The Financial Accounting Coding Block elements are defined below: G/L Account: The central accounting record for Umoja. It contains the balances of all offsetting credit and debit accounts. Every financial transaction conducted in Umoja has a corresponding posting within the G/L Business Area: This represents a classification of the UN entities operating in Umoja, recorded on every financial transaction for example, Peacekeeping Missions, Special Political Missions, OAHs, Region of Commission and Agencies of Funds and Programs Segment: This is established as a result of IPSAS requirements (used for financial statement reporting). It is achieved by using the Functional Area Fiscal Year: It is the year by which transactions are recorded in Umoja to comply with IPSAS requirements. A user transaction processing equates to the calendar year The General Ledger is covered in detail in the Umoja General Ledger Process course. 38

39 Coding Block: Controlling Elements The Controlling Coding Block elements are defined below: Cost Element: A cost or revenue item that is linked one-for-one to an expense or revenue General Ledger account Cost Center: A cost object that identifies the areas of ongoing cost responsibility within an organization s overall organizational structure. Every cost center links to a Funds Center Internal Order: A cost object that collects costs and revenues of a specific event or simple project that has defined start and end dates, is usually temporary (unique) in nature and where costs should be segregated from other events or on-going operations to enable more detailed monitoring WBSE (Work Breakdown Structure Element): Represents a project with its structure Profit Center: It is an attribute of cost objects (Cost Center, Internal Order and WBSE) that allows reporting of costs by business function (e.g. finance, HR, IT, etc.). In revenue-producing areas, it supports reporting on products and services The Controlling Ledger is covered in detail in the Umoja Cost and Management Accounting Overview course. 39

40 Coding Block: Funds Management Elements The Funds Management Coding Block elements are defined below: Commitment Item: The functional grouping of expenditures and revenues Fund: The lowest level source of funding used for tracking, controlling and reporting on available financial resources Funds Center: An organizational unit that controls a budget. It is time dependent and has the valid from and to dates. Every Funds Center links to a cost center Funded Program: A program operational purpose and defined timeframe. It can range from simple activities to complex projects and can cross fiscal years, funding sources and organizational units Functional Area: Used to classify revenues and expenditures of an organization by function. It provides a programmatic view of the UN from a budgetary perspective Budget Period: The validity for which the budget is approved The FM Ledgers is covered in detail in the Umoja Funds Management Overview course. 40

41 Coding Block: Grants Management Elements The Grants Management Coding Block elements are defined below: Sponsored Class: Used to provide budgetary control and to support reporting to Donors based on their specific requirements. Sponsored classes summarize the sponsor's expense and revenue categories Grant: Used to maintain the terms and conditions of the Grantor s contribution. In cases where the UN is a Grantee, that is the UN receives contributions from Donors, the Grant represents the Donor s Agreement. In cases where the UN is a Grantor, that is the UN gives money to an Implementing Partner, the Grant represents the Funding Agreement Sponsored Program: Used to identify a program of the Sponsor. It identifies the purpose of the Sponsor s contribution Grant Validity Period: Defined within Grant Master Data to be used in unreleased and released budgets The Grants Ledger is covered in detail in the Umoja Grants Management Overview course. 41

42 Balance Sheet Account Entries For balance sheet account entries, e.g. entering a receivable in Umoja, the following elements are always required to be entered (if not pre-populated from another module): Business Area G/L Account Fund Grant (GMNR or the applicable grant) 42

43 Derivation Related to Revenue and Expense Postings To manage this large number of data elements, Umoja uses a functionality called Derivation to link Coding Block elements to each other. While a transaction may require multiple pieces of information, the user only has to satisfy the minimum entry requirement. All dependent fields will be automatically populated from the source field. For example, the Cost Center will always derive the Business Area, Functional Area, Funds Center and Profit Center. When a user conducts a transaction requiring all such fields, only the Cost Center has to be entered. These other fields are automatically populated The documents generated from each module are also interlinked to reflect the above. Enter Cost Center Cost Center Business Area Automatically Derived Dependent Fields Functional Area Funds Center Profit Center Derivation 43

44 Umoja Coding Block: Requirements In order to satisfy the UN s reporting and analysis requirements, certain classifications for financial transactions have been identified. UN Classification Requirement G/L account/ type of expense Funding source Organisational & activity related Programmatic Financial period 44

45 Umoja Coding Block: Requirements In the legacy system, this classification mapped to IMIS/SUN Budgetary Account Classification (UN BAC). UN BAC G/L account Object code/class UN Classification Requirement G/L account/ type of expense Fund Funding source Org.Unit/Cost Ctr Project/Mission Activity Organisational & activity related Programme Fiscal Year (part of Fund code) Programmatic Financial period 45

46 Umoja Coding Block: General Ledger With Umoja, these classification are mapped to General Ledger (G/L) as follows: UN BAC G/L account Object code/class UN Classification Requirement G/L account/ type of expense General Ledger G/L Account The Umoja chart of accounts combines the as-is G/L accounts and object codes into new G/L accounts. Fund Funding source Fund /Grant Grant is used to track voluntary contribution. Org.Unit/Cost Ctr Project/Mission Activity Organisational & activity related Business Area This represents a classification of UN Entities operating in Umoja recorded on every financial transaction. Programme Programmatic Segment Functional Area Functional area is more detailed than as-is Programmes and provides detailed programmatic analysis. Fiscal Year (part of Fund code) Financial period Fiscal Year Budget Period Annual fiscal year; budget periods define budget validity. 46

47 Umoja Coding Block: Controlling Ledger These classification are also mapped to Controlling Ledger as follows: UN BAC UN Classification Requirement General Ledger Controlling Ledger G/L account Object code/class G/L account/ type of expense G/L Account Cost Element Fund Funding source Fund /Grant Fund /Grant Org.Unit/Cost Ctr Project/Mission Activity Organisational & activity related Business Area Cost Center Internal Order WBSE Programme Programmatic Segment Functional Area Functional Area Fiscal Year (part of Fund code) Financial period Fiscal Year Budget Period Fiscal Year Budget Period 47

48 Umoja Coding Block: FM Ledgers These classification are also mapped to Funds Management Ledgers as follows: UN BAC G/L account Object code/class Fund UN Classification Requirement G/L account/ type of expense Funding source FM Ledgers Commitment Item Fund/Grant Org.Unit/Cost Ctr Project/Mission Activity Organisational & activity related Funds Center Funded Program Programme Fiscal Year (part of Fund code) Programmatic Financial period Functional Area Budget Period 48

49 Umoja Coding Block: GM Ledger These classification are also mapped to Grants Management Ledger as follows: UN BAC UN Classification Requirement FM Ledgers GM Ledger G/L account Object code/class G/L account/ type of expense Commitment Item Sponsored Class Fund Funding source Fund/Grant Fund/Grant Org.Unit/Cost Ctr Project/Mission Activity Organisational & activity related Funds Center Funded Program Funds Center Sponsored Program Programme Programmatic Functional Area Functional Area Fiscal Year (part of Fund code) Financial period Budget Period Grant Validity Period 49

50 Coding Block Elements Umoja Coding Block A detailed view of the classification, four ledgers and the corresponding coding block elements and derivation rules is as follows: Module FI Financial Acct CO Controlling FM Funds Mgmt GM Grants Mgmt ENTERPRISE STRUCTURE CODE COMPANY CODE CO AREA FM AREA G/L acc related G/L Account Cost Element Commitment Item Sponsored Class Funding Source Related Organizational & activity related Programmatic Fund Fund Fund Fund Grant Grant Grant Grant Business Area Segment Cost Center (org structure: Department, Division, Unit) Internal Order Work Breakdown Structure Profit Center Funds Center Funded Program Funds Center Sponsored Program Functional Area Functional Area Functional Area Functional Area Financial Period Related Fiscal Year Fiscal Year Fiscal Year Grant Validity Period Budget Period Budget Period Budget Period Budget Period Legend: FI Entry Derived Derived or entered Underlined items are owned by corresponding module 50

51 Umoja Coding Block: Major Changes What are the Major Changes Resulting from the Umoja Coding Block? Here is an overview of the major changes: Financial Accounting: Accrual accounting is adopted for financial accounting purposes General Ledger is used for IPSAS actuals only Controlling: Controlling Ledger is used to support managerial accounting Umoja has defined additional cost centers to support results-based management in the long-term Funds Management: FM Ledgers are used for budgetary control and budgetary performance reporting Functional area is used for more detailed programmatic analysis Grants Management: Grants Ledger is used to track individual donor contributions 51

52 Umoja Coding Block for UN Staff Members What does the Umoja Coding Block mean for you as a UN Staff Member? It means that: You will typically have to enter information into fewer systems than you do today Processes will generally be more automated and will require fewer manual steps, thus saving you time. This also minimizes chances of manual-entry error Departments across the organization will have access to the same source of data 52

53 Learning Checkpoint 1 In Umoja, allows posting in one module to be automatically posted in all other corresponding ones. Fill in the blank with the correct option. A. Simultaneous posting B. Derivation C. Master Data Management D. All of the above 53

54 Learning Checkpoint 1 In Umoja, allows posting in one module to be automatically posted in all other corresponding ones. Fill in the blank with the correct option. A. Simultaneous posting B. Derivation C. Master Data Management D. All of the above Option A is the correct option. In Umoja, simultaneous posting allows posting in one module to be automatically posted in all other corresponding ones. 54

55 Learning Checkpoint 2 Which of the following ledger is used for IPSAS actuals only? Select the correct option. A. Controlling Ledger B. General Ledger C. FM Ledger D. Grants Ledger 55

56 Learning Checkpoint 2 Which of the following ledger is used for IPSAS actuals only? Select the correct option. A. Controlling Ledger B. General Ledger C. FM Ledger D. Grants Ledger Option B is the correct option. General Ledger is used for IPSAS actuals only. 56

57 Module 2 Summary The key points covered in this module are listed below: The Umoja Coding Block is a tool that describes the data structure for recording financial transactions The Umoja Coding block is comprised of elements from finance-related modules: FI, CO, FM and GM The Umoja Coding Block elements are linked to each other to allow simultaneous posting Umoja uses a functionality called derivation in which some Coding Block elements are linked to each other allowing the dependent fields to be automatically populated from the source field The UN Classification Requirement is captured in the Umoja Coding Block 57

58 Agenda Course Introduction Umoja Master Data Overview Umoja Coding Block Overview Course Summary Course Assessment Course Survey 58

59 Course Summary The key points covered in this course are listed below: The Umoja Enterprise Structure defines the operational and organizational system foundation for each major component (finance, logistics, etc.), including the currency Master Data is centralized data used to support business processes across the organization A central Master Data Management team will create, maintain and distribute Master Data along with centralizing business control and compliance The Umoja Coding Block is a tool that describes the data structure for recording financial transactions. It is comprised of elements from finance-related modules: FI, CO, FM and GM The Umoja Coding Block elements are linked to each other to allow simultaneous posting Some Coding Block elements are linked to each other allowing the dependent fields to be automatically populated, or derived, from the source field The UN Classification Requirement is captured in the Umoja Coding Block 59

60 Agenda Course Introduction Umoja Master Data Overview Umoja Coding Block Overview Course Summary Course Assessment Course Survey 60

61 Course Assessment Now that you have completed all the modules in this course, you can test your knowledge by completing the Course Assessment. To receive credit for completing this course, you must pass this assessment with a minimum score of 90%. To complete the assessment you must return to the Learning Management System: 1. Log into Inspira 2. Navigate to Main Menu -> Self-Service -> Learning -> My Learning 3. Search for the name of the course under the My Learning Activities section 4. Click the Start link of the course assessment 5. Click the Submit button once you have completed the assessment 61

62 Agenda Course Introduction Umoja Master Data Overview Umoja Coding Block Overview Course Summary Course Assessment Course Survey 62

63 Course Survey Your feedback is important to the continuous improvement of our training program. Please complete the evaluation for this course using the following steps: 1. Log into Inspira 2. Navigate to Main Menu -> Self-Service -> Learning -> My Learning 3. Search for the name of the course under the My Learning Activities section 4. Click the Start link of the course survey 5. Click the Submit button once you have completed the course survey 63

64 Congratulations! You have successfully completed the Umoja Master Data and Coding Block Overview course. 64