Can You Upload a 2.2 Level on 2.1.1.1

1 Objective

The objective of this affiliate is to give a brief overview of the Umoja enterprise structure and the relevant main information elements used in the coding block structure inside the Umoja environment. It aims to provide high-level understanding of the assignment of master information elements and how it impacts the derivation of linked master data elements to ensure the business concern transaction is captured accurately in accordance with the United nations's nomenclature and reporting requirements.

2 Umoja Enterprise Structure

2.1 Introduction to Umoja Enterprise Structure

The Umoja enterprise structure is merely the organizational structure that represents the UN Secretariat in SAP environment. In the UN, the foundational enterprise structure starts with the Company Code, Controlling (CO) area, and Fund Management (FM) area. Grants Direction, from an enterprise structure perspective falls under FM area.

The Umoja enterprise structure design is a fundamental step in the UN transformation initiative. Its design is driven past how business scenarios are processed, how balances are aggregated, and how reports are generated for an enterprise. Additionally, the enterprise construction design is flexible enough to integrate the dissimilar enterprise structure elements into the overall construction of Un organization and scalable plenty to suit the United nations's current and future business concern requirements.

Below the foundational elements, it consists of specific elements from diverse modules which for legal reasons or other specific business organisation related purposes are grouped together for example Supply Chain Management (SCM) or Human being Capital letter Management (HCM). Together with the Foundations Elements, the composition of these Enterprise Structure Elements is illustrated below.

2.1.i Umoja Enterprise Structure Terminology

2.one.1.one Foundation Elements

• The Company Lawmaking is the highest enterprise construction element in the hierarchy where complete financial statements tin can exist generated. In SAP, it is typically synonymous to the legal entity or external view of an organization. All structures within a Visitor Code have similar financial processes and use the aforementioned chart of accounts. Similarly, every financial transaction relevant to the external view is assigned to a Visitor Lawmaking. In Umoja, but Visitor Code k is set up for both Peacekeeping missions (PK) and Non-Peacekeeping Operations.

• The CO (Controlling) area defines the context where price (management) accounting takes place; it'southward most revenue and costs, including appropriate internal resource allotment and distribution. All revenue and toll transactions which are posted in Financial Accounting (FI) are also posted in CO surface area. The CO area must be assigned to Company Lawmaking to ensure transactions from FI are forwarded to CO area.

• The FM Area represents the organizational unit which plans, controls and monitors funds and the associated budgets to ensure budgetary control is established for the organization. Once the FM is activated in the Company Code 1000, posting transactions from upstream modules similar FI and SCM are recorded as commitment and bodily data in FM.

2.1.1.2 Fiscal Accounting Elements

• Business Area is an enterprise structure element from FI that represents a separate area of operations for Peacekeeping (PK) and Non-Peacekeeping (NPK) entities in United nations. From a business area perspective, internal financial statements tin be generated per entity to provide United nations a tool to analyze each PK and NPK entity's surface area of responsibleness.

• Segment is another enterprise structure element from FI that represents a 'upkeep colonnade' based on the current structure used for 'volumes' of Financial Statements as required by IPSAS. In Umoja, the value of segment is derived from the functional area.

2.1.1.iii Supply Chain Management (SCM) Elements

• Purchasing Organization is an organizational level that negotiates weather of purchase with vendors for i or more plants or companies. Information technology assumes legal responsibleness for all external buy transactions.

• Plant is an organizational unit which serves to subdivide an organization according to production, procurement, maintenance, materials planning and materials valuation.

• Storage Location represents a physical segregation of inventory or materials.

• Warehouse is a systematic representation of the physical layout of a storage facility, a logical grouping of storage locations.

• Transportation Planning Point is for planning shipments with particular features. A shipment is assigned to ane transportation planning point eastward.one thousand. by train, by transport, or by air.

• Shipping Point is the physical location to which the inventory or materials are shipped.

• Loading Betoken is the subdivision of Shipping Bespeak.

2.1.ane.iv Homo Capital Management (HCM) Elements

• Personnel Area is a unit in personnel administration, which represents a Land in Umoja.

• Personnel Subarea is subdivisions of the Personnel Area, which represents a Duty Station in Umoja.

• Employee Group represents a defined grouping of work rules, for example, authorization checks, remuneration levels, or piece of work schedules. In Umoja, the employee type relates to employee group which can be International Staff or Local Staff.

• Employee Subgroup is a subdivision of the Employee Group where for example, International Staff can be further be grouped into Professional or Field Service.

two.1.1.5 Sales and Distribution (SD) Elements

• Sales System is the organizational unit responsible for distributing goods and services, negotiating conditions of sale and other sales related activities.

• Distribution Channel is a means through which saleable materials or services reach the client; the method of distribution.

• Division is a means of grouping materials or services, non just for sales and distribution purposes, only too for materials management i.e. product lines.

• Sales Part is a location for sales and distribution activities.

• Sales Group is assigned to Sales Office to differentiate different products or services existence offered in Sales Function. Information technology also creates different areas of responsibleness within the Sales Role.

2.one.2 Subset of 'Full' Umoja Enterprise Structure

The subset represents a electric current snap shot of what comprises the Umoja Enterprise Structure. In the future, equally more entities are added it will abound bigger with additional plants, distribution channels, and personnel areas.

Below is a graphical representation of subset of 'total' Umoja Enterprise Structure:

Back to top

iii Master Information

three.1 Introduction to Master Data

Every organization like United nations runs on data and a ready 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 system. Thus, it is extremely critical for the organization to create a centralized data source. In Umoja, this centralized data is chosen Master Data.

The Umoja arrangement structures information into different groups, depending on its function and purpose.

3.i.1 Umoja Terminology

Key Reference Information is fix up to configure the Umoja system for specific needs of the UN. Information technology defines the highest level boundaries in the Umoja system. Information technology tends to be static and generally does not change subsequently it has been added to the system. One example of key reference data is Business organisation Area.

Master Data is centralized information used to back up 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 information in various application areas. 1 example of chief data which is used beyond dissimilar modules is business concern partners (BP).

Transactional Information is output data derived from processing business concern transactions in Umoja. The accumulated transactional data are stored in Umoja with drill down functionality from one transactional data in one module to go to another transactional data in another module. For instance, a textile document created from appurtenances receipt tin can be displayed in Procurement but user tin can too brandish the related bookkeeping document created in Financial Bookkeeping module.

Reporting is the grouping of transactional information across different areas and different parameters. Standard reports as well every bit custom reports are bachelor in Umoja environment.

three.1.two Umoja Coding Cake Elements

In Umoja, a big set of master information has to exist maintained to process the business transactions from one functional module to the next. To illustrate, a Concern Partner (BP) with a Vendor Role volition only be entered in one case during the creation of purchase requisition (PR) or purchase order (PO), the same BP volition be retrieved based on PO during good receipts or service receipts, and also equally during logistics invoice processing (LIV) when the vendor'south billing invoice is received.

Similarly, to enable 'simultaneous posting' when a business concern user is posting a business transaction in Financial Accounting, the master data elements in each of the following modules must be linked together:

· Financial Accounting (FI)

· Controlling (CO)

· Funds Management (FM)

· Grants Management (GM)

The Master Information from each module, in addition to some Central Reference Information, brand up the Umoja Coding Block elements.

The respective coding block elements for each module and ledger are equally follows:

iii.one.two.1 Fiscal Accounting (FI)

Full general Ledger (GL) accounts are maintained in Umoja Chart of Accounts '1000' and take 8 characters using transaction lawmaking FS00. Transaction code FS00 is used to maintain individual GL accounts in chart of accounts 1000. GL accounts receive the debit and credit value postings for various transactions and rolls ups to support the account balances in the financial statements.

The chart of accounts on the General Ledger are as follows:

Fiscal Twelvemonth is a key reference information which is usually a menstruum of twelve months or more for which an Arrangement like United nations issues Financial Statements. A fiscal yr may stand for to a calendar year but it is not obligatory. In Umoja, Fiscal Year Variant K4 is assigned to Company Lawmaking 'chiliad' which ways the Financial Twelvemonth is divided into 12 posting periods plus 4 special periods.

Special periods are additional periods that can be used to record year-end adjustments such as late adjustments, audit adjustments, etc. Although the UN anticipates not being able to utilize the special periods every bit a result of the decision to keep the current Leading and Non-Leading ledger completely in sync, iv special periods, the maximum number, were included in the configuration of the Leading ledger to permit for an eventual usage if SAP provides a fix in a subsequent update.

Interaction of Visitor Lawmaking and Fiscal year:

· All UN programmes and funds inside the Umoja solution are defined within a single Visitor and Company Code g; this includes all Peacekeeping funds and all Non-Peacekeeping funds.

· The Company Code is divers with a fiscal year variant of K4 starting 1st January to 31st December, mapped to a calendar yr. Therefore, the Leading Ledger view '0L' of transactions for the Company Lawmaking thou will be on a 1st January to 31st December footing.

· For Non-Peacekeeping funds the fiscal year is the agenda year; the same equally the Company Lawmaking 1000. Therefore the Leading Ledger volition exist the source for Non-Peacekeeping reporting.

· For Peacekeeping funds the fiscal twelvemonth 'Z6' is 1st July to 30th June. To support the Peacekeeping reporting a Non-Leading Ledger 'NL' volition be defined for the Un Company Code, with a fiscal twelvemonth of 1st July to 30th June assigned.

· For calculation of average daily balance (ADB) used in allocation of investment income, the fiscal year 'AD' is created based on 366 calendar days or posting periods. To support the investment bookkeeping, a Non-Leading Ledger 'AD' is defined for the Visitor Lawmaking chiliad.

· The Non-Leading Ledgers receives all financial postings that are made to the Leading Ledger and it volition be the source for Peacekeeping funds reporting and ADB calculations in investment accounting.

For definition of Business Area and Segment, refer to section ii.one.one.two Financial Bookkeeping Elements.

Dorsum to superlative

3.i.ii.2 Controlling (CO)

Price Element is a cost or acquirement item that is linked one-for-i to an expense or acquirement GL account. The chief cost element is automatically created when the corresponding cost and revenue GL business relationship is too created.

Toll Center is cost object that collects costs and revenues which identifies the areas of ongoing cost responsibility within an system's overall organizational structure. In Umoja, every cost center links to a funds center. Cost center is created using transaction code KS01.

Internal Society is another cost object that collects costs and revenues of a specific event or simple project that has defined commencement and stop 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. Internal club is created using transaction lawmaking KO01.

Work Breakup Structure (WBS) Element is structural element in a project which divides the project into manageable units, defines specific dates, and collects costs. WBS Element is created using transaction lawmaking CJ91.

Profit Centers is an attribute of cost objects (Cost Center, Internal Order and WBSE) that allows reporting of costs by concern function (e.one thousand. finance, HR, It, etc.). In revenue-producing areas, it supports reporting on products and services. Profit center is created using transaction code KE51.

3.1.2.iii Funds Management (FM)

Delivery Item is a functional grouping of costs and revenues. Delivery items allocate upkeep transactions and business transactions affecting liquidity into acquirement, expenditure, and greenbacks balance items. In Umoja, typically there is one to ane human relationship between expense and acquirement GL accounts in FI, price elements in CO, and commitment items in FM. During transaction entry, the commitment item tin can exist derived from GL account and/or price element. Commitment item master tape is created using transaction code FMCIA.

Fund is the everyman level source of funding used for tracking, controlling and reporting on available financial resources. In Umoja, fund is one of the document split characteristics to enable all accounting documents posted to separate balanced postings per business area, segment, fund, and grant to written report on financial statements per fund. Fund master record is created using transaction code FM51.

Fund Middle is an organizational unit within FM assigned with area of responsibility such a department or a section unit of measurement within a department or project. A Fund Center controls budget and is time dependent. In Umoja, at that place is a one to i relationship between a fund middle to a price eye. Fund Center is created using transaction code FMSA.

Funded Program as defined in Umoja is the program operational purpose and with definite timeframe. It can range from simple activities to complex projects and can cross fiscal years, funding sources and organizational units. Every internal guild and every project WBSE will exist assigned to a Funded Program in FM every bit required for budget command using an attribute on the internal society and WBSE 'Upkeep Control IO/WBSE'. Funded Plan can be created using transaction code FMMEASURE.

Functional Area is used to classify revenues and expenditures of an organization past function. It provides a programmatic view of the United nations from a budgetary perspective. Functional area is created using transaction code FM_FUNCTION.

Upkeep Period is the period of available upkeep authority. It enables to record budget appropriation/execution items independently of the financial year or whatsoever other master data data. In Umoja, Budget Periods will be used to enable biennial budget periods for Regular Budget (RB), annual budgets for Peacekeeping (PK) and annual budgets for trust funds and voluntary contributions. The Fund Blazon in combination with the posting date will be used to derive the Budget Period. Budget Period is created using transaction code FMBPD.

3.one.ii.4 Grants Management (GM)

Sponsored Classes are used to provide monetary control and to support reporting to Donors based on their specific requirements. Sponsored classes summarize the sponsor'southward expense and acquirement categories and correspond an alternative view of Umoja's Nautical chart of Accounts. Each Sponsored Class represents a group of GL accounts. Sponsored Class can exist created using transaction code GMCLASS.

Grant is used to maintain the terms and conditions of the Grantor'southward contribution through its lifecycle from proposal to execution to final close of the grant. In cases where the UN is a Grantee, that is the Un receives contributions from Donors, the Grant represents the Donor'south 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. Grant main tape can be created using transaction code GMGRANT.

Sponsored Plan represents the view the sponsor wants the data reported back to them and to enforce sponsor restrictions and requirements which cross grants. In Umoja, if a contribution is earmarked for a specific activity and donor requires reports to link the contribution to activities, this contribution will be represented by a unmarried sponsored program. Contributions of donors without requirement for exact reporting or earmarking will be grouped in sponsored programs with like earmarks. Sponsored Program can be created using transaction code GMPROGRAM.

Grant Validity Period is assigned in Grant master record which determines the start and stop date of Grant.

iii.2 Business Partners

The SAP Business Partner functionality allows the cosmos and management of business partners centrally. The SAP Business Partner information object is designed to provide technical benefits such as data integrity and freedom from data redundancy. The information that is common to multiple roles does not have to be created each time, meaning that redundant information cosmos and retention is avoided, and that data inconsistencies are avoided.

A Business organization Partner (BP) is an important Master Data blazon. It defines the person, group or an organisation with whom UN has a business interest.

Fundamental components of the full general BP Main Information include:

To achieve ane Master Data record per entity, each Business organisation Partner is defined through two dimensions in Umoja: Groups and Roles. Each Concern Partner belongs to 1 grouping, merely tin be assigned one or more than different roles. The roles ultimately make up one's mind how a Business Partner tin exist used in Umoja.

3.2.1 Business Partner Groups

Concern Partner Grouping	Organizations/Description
Third party:
Member States (Permanent Mission)
Non-Fellow member Land (Holy Come across etc.)	· Vatican · Palestine
Government and Local Authority	· Ministries (e.one thousand. Ministry of Finance, Espana) · Governmental agencies (CIDA) · Municipalities (e.grand. City of New York)
Un Agency, Fund and Program
Inter Governmental and NGO	· All non-UN and international organizations · All Non-governmental organization (NGO) (legally constituted system created by natural or legal persons that operates independently from any class of government.) · Clubs · Schools · University Clubs · Associations
Commercial:
Commercial Vendor (UNGM)	UNGM is the procurement portal of the United nations Organisation. It acts as a single window, through which potential suppliers may register with the 20 UN Agencies using the UNGM equally their supplier roster. Vendors registered in UNGM are commercial entities which sell goods or services to the UN. Vendors that do regular business with the UN, or ane-fourth dimension vendors who are providing goods/services valued at over USD 4,000 must register in UNGM before a Contract or PO tin be signed. The UNGM and Umoja integration allows for information from UNGM to exist populated in ECC every bit a Business Partner. Commercial companies cannot be created in the Umoja system directly as BP with UN Vendor Function.
Commercial Customer	Companies that made payments to the Un has to be created as BP with 'United nations Customer' role in Umoja. Commercial customers may be UNGM registered vendors, in which instance 2 BP numbers have to be created and linked due to UNGM integration requirement. This does non apply to not-commercial entities (i.east. i BP number with both UN Vendor and UN Customer roles).
Vendor (Non-UNGM)	Vendors used for Low Value Acquisitions (purchases totaled beneath USD four,000) do non have to register in UNGM even though UNGM registration is encouraged. They can be created directly in the Umoja system equally BP with 'United nations Depression-value Vendor' role.
Individuals:
Individuals externals, Not-staff	· Legal Committee Members, Judges · Coming together Participants, Travellers · Candidates/Applicants · Eminent Persons (VIPs) · Diplomats · Staff of UN agencies · Consultants, Individual Contractors · TC Experts on NR Loan - experts on loan to the UN from Governments Intern · Scholars, Fellows · Gratis Personnel - Blazon two · United nations Volunteers (UNV) · Postal Workers
Staff Fellow member, Ex-Staff Member, Retirees, Survivors	· Un Staff Members · Ex-Staff Members · Survivors and Dependents · Retirees
Non-Staff War machine and Police
Treasury:
Treasury Partner	The Treasury Business organization Partners are the persons or legal entities with whom the UN Treasury enters into purchase/sale transactions of investment or FX instruments, and keeps bank balances. They take to be created in Umoja every bit new Business organisation Partners with Treasury-related roles due to security and confidentiality requirements associated with transactions engaged past the UN Treasury. · Financial Services BP · UN Counterparty (Heir-apparent or seller of the financial instruments) · United nations Issuers (Issuer of the financial instruments) · UN Depository banks (Bank where custodial account is maintained)

Dorsum to top

3.2.ii Summary Table of Business Partner Groups

Concern Partner Grouping	Group ID	BP Number Range	Source
3rd party:
Member States (Permanent Mission)	Z011	1111XXXXXX	OPPBA
Not-Fellow member State (Holy Encounter etc.)	Z012	12XXXXXXXX	OPPBA
Government and Local Authority	Z013	13XXXXXXXX	OPPBA
United nations Agency, Fund, Programme	Z014	14XXXXXXXX	OPPBA
Inter Governmental and NGO	Z015	15XXXXXXXX	OPPBA
Commercial:
Commercial Vendor (UNGM)	Z010	111XXXXXXX	UNGM (PD)
Commercial Customer	Z018	18XXXXXXXX	OPPBA & UNGM
Vendor (Non-UNGM)	Z019	19XXXXXXXX	OPPBA
Individuals:
Individuals externals, Independent Contractors, Consultants, etc.	Z016	20XXXXXXXX	FPD & OHRM (Alphabetize#)
Staff Fellow member, Ex-Staff Member, Retirees, Survivors	Z020	20XXXXXXXX	OHRM (Alphabetize#)
Non-Staff Military and Police	Z021	20XXXXXXXX	FPD (Index#)
Treasury:
Treasury Partner	Z017	17XXXXXXXX	OPPBA (Treasury)

iii.2.iii Business Partner Roles

Each Business Partner belongs to one group, but can be assigned one or more roles. The BP role data is module-specific, such as UN Vendor data for Purchasing and Supplier Relationship Management (SRM) related processes and United nations Customer data for the Sales and Distribution (SD) procedure. The roles ultimately determine how a Business Partner can exist used in Umoja. Examples of business organisation partner roles are as follows:

A vendor is a BP function to whom Un payments is made to. This role is needed earlier a BP can be used to procure goods and services, and ship payments.

A customer is a BP office from whom invoices can be issued to and payments received from. This office is needed earlier a BP can be used for the provision of goods and services by the United nations through the Umoja Sales & Distribution (SD) module, and billing and creating business relationship receivables in the organization.

A sponsor or donor, is a BP part that represents a government, institution or individual providing funding to UN. This role is needed before a BP can be used to tape, rails and report on grants-related transactions.

Multiple roles take been created for UN Treasury. These specialized roles need to be assigned to a BP earlier it tin exist used to execute treasury-related transactions and move funds.

· Un Fiscal Services BP

· Un Counter Political party

· United nations Issuer

· UN Depository Bank

Multiple roles have been created for Umoja Existent Estate (RE) module. These specialized roles need to be assigned to a BP before information technology tin be used to execute RE-related transactions. In that location are 2 distinct sets of Real Estate roles, one to be assigned to leases and the other to perform RE-related transactions within the arrangement.

three.2.4 BP - Asking for Creation or Update, Cosmos and Roles Assignment

A. Follow the process below to request for creation or an update to a BP:

A.ane. In one case the need to create or update a BP is identified, download the Primary Information asking grade(due south) from the Umoja iSeek homepage à Primary Data Maintenance

A.two. Open the course and consummate the required fields.

A.iii. Send the completed form to umoja-mdm@un.org à an automatic confirmation volition be sent to the Requestor with a link to track progress.

A.4. In one case the form has been received, the Reviewer will send an acknowledgement email to the Requestor.

A.5. A notification will be sent to the Requestor once the request is complete.

The following is an overview of the process to create a BP. Refer to the subsequent section for detailed steps:

1. Using the course that is submitted by the Requestor, the Principal Data Maintainer determines the BP Group.

2. Adjacent, based on the BP Grouping assigned, the Master Data Maintainer creates the BP as a general office. This is necessary for every BP record.

three. Using the tabular array below, the Master Data Maintainer determines the required roles needed for the BP.

Back to acme

Business Partner Grouping	Blazon of BP	Un Vendor	UN Low value vendor	United nations FI Vendor	Un Client	United nations Sponsor	Un Fiscal services BP
Tertiary political party:
Member States (Permanent Mission)	Arrangement	Ten			X	X
Not-Member State (Holy Encounter etc.)	Organization	X			X	X
Government and Local Authorization	System	10			X	X
Un Agency, Fund, Program	Organization	X			X	X
Inter Governmental and NGO	Organization	X			X	X
Commercial:
Commercial Vendor (UNGM)	Organisation	X
Commercial Customer	Organisation				X
Vendor (Not-UNGM)	Organization		Ten
Individuals:
Individuals externals, Independent Contractors, Consultants, etc.)	Person	Ten
Staff Member, Ex-Staff Member, Retirees, Survivors	Person			X
Non-Staff War machine and Police	Person			X
Treasury:
Treasury Partner	Arrangement						10

iv. Using the course that is submitted past the Requestor, the Master Data Maintainer extends the relevant BP to the required BP roles and input all the essential and provided information.

v. The information is verified and approved by the Primary Data Approver. If applicable, certain blocks are automatically or manually placed on the BP record until the information tin exist verified.

vi. In one case the data is verified, the BP record is unblocked and fully functional.

3.ii.5 Business Partner Reconciliation Accounts

A BP Type that further categorizes the type of BP needs to be populated. This determines the reconciliation account that is automatically linked to the BP (for financial transactions).

Business Partner Group	Group ID	BP Type	Recon Acct (Vendor)	Recon Acct (Customer)
Commercial Vendor - UNGM	Z010	Z900 - Other Types	0035101510
Commercial Vendor Non-UNGM	Z019	Z900 - Other Types	0035101510
Commercial Client	Z018	Z900 - Other Types		0015101510
Staff member, Ex-Staff Member, Survivors	Z020	Z001 - International Staff	0035101610
Staff member, Ex-Staff Fellow member, Survivors	Z020	Z002 - Local Staff	0035101610
Staff member, Ex-Staff Member, Survivors	Z020	Z020 - Retiree	0035101610
Non-Staff Military machine and Police	Z021	Z004 - Armed services Staff Officer	0035101710
Non-Staff Military and Police	Z021	Z005 - Military Observer	0035101710
Non-Staff Military and Police	Z021	Z006 - Un Law	0035101710
Individual External, Non-Staff - NO Payroll	Z016	Z003 - United nations Volunteer	0035101810
Individual External, Non-Staff - NO Payroll	Z016	Z100 - Private Contractor	0035101810
Individual External, Non-Staff - NO Payroll	Z016	Z101 - Consultant	0035101810
Fellow member State	Z011	Z900 - Other Types	0033201010	0015101010
Non-Fellow member Land	Z012	Z900 - Other Types	0033201110	0015101110
Government & Local Authority	Z013	Z900 - Other Types	0035101210	0015101210
UN Bureau, Fund, Program	Z014	Z900 - Other Types	0035101310	0015101310
NGO and Intergovernmental	Z015	Z900 - Other Types	0035101410	0015101410
Treasury Partner	Z017	Z900 - Other Types

Thus, once a BP is created in the organization and assigned a BP part e.thousand. Z018 Commercial Customer, the same BP number will be created automatically equally customer in principal record. The same attributes such every bit name, search term, address, contact number and other information in BP will exist replicated in client chief record.

3.two.6 Business organisation Partner Maintenance

The use of SAP Business organisation Partner functionality is core to Umoja solution when processing transactions in ECC likewise every bit SRM. Each module enables specific processes and requires the cosmos of Customer, Vendor and/ or BP.

BP Primary Data Maintenance is an integrated Umoja solution spanning core modules in FI, TR, RE, GM, MM, and SD.

The following explains sure processes relevant to BP maintenance.

3.2.6.1 Create a New BP

B. The steps to create a new BP for Individual (i.e. Staff Member) / Transaction Code: BP

B.1. Enter BP in the Control field.

B.2. Click the Person push at the height of the chief menu. -> the Create Person screen is displayed.

B.three. Select Business Partner (Gen.) from the Create in BP role drib-down list to create the generic profile for the BP

B.4. Select the corresponding group from the Grouping drop-downwardly list. Brand this option based on the inputs specified on the form. Please take note that the BP group selected will command the consignment of BP number.

Note: For BP for Individual, the BP number will not be automatically generated. The User needs to manually enter the BP number, which is a 10-digit number starting with 20 and followed by the viii-digit index number of the individual.

Back to pinnacle

B.v. Click the Address tab and populate the following fields:

• Title: Select Mr. or Ms.

• Beginning and Last proper noun: This is the name of the BP that is being created.

• Search Term one: Search Term is used as a method to acquit searching for a particular BP or group of BPs. This search term is the last proper noun of the BP.

• Search Term 2: This search term is the first name of the BP.

• Street/House number: This represents the address of the BP.

• Postal Code/Urban center: This represents the address of the BP.

• State: This represents the accost of the BP.

Note: All fields should be completed using Upper-case letter Letters

B.vi. Click on the Addit. Fields button to enter additional details on the BP.

B.7. Select an advisable language from the Language match code listing as the default language of communication with the BP in term of any arrangement generated forms à press Enter.

B.viii. If applicative, additional addresses can be added for the newly created BP:

B.8.1. Click the Address Overview tab à click the Create button.

B.8.two. Populate the data in the pop-upwards window (every bit instructed previously) à click the Keep button.

B.8.3. The boosted accost will appear every bit a 2d line à place the address in the correct Address Usage folder:

B.8.3.one. Double-click the appropriate folder, e.g. Address for Correspondence.

B.8.iii.two. In the popup window, select the appropriate line item à click the Proceed button.

The additional address will appear in the corresponding binder:

B.9. Click the Control tab to constitute the BP Type and security Authorization Group for this BP record.

B.10. Click the match lawmaking icon in the BP Type field.

B.11. Select the advisable BP Type lawmaking.

B.12. In the Authorization Group field, select the appropriate Authorization Group lawmaking (Z901). This will ensure that only authorized users for 'Individual' BP Group are immune maintenance and approval accesses.

Back to acme

B.13. Click the Payment Transactions tab to add together a new bank account.

B.14. Type the IBAN number in the IBAN field, if the BP has an IBAN number. The Switch Entry Type icon adjacent to the IBAN field allows the user to blazon in free form. Note: This step can be skipped if the BP is paid past cash or cheque.

B.xv. The banking concern account details are automatically populated in the Bank Details section.

B.16. Click the Generate Bank Details push button.

B.17. If the BP does not have an IBAN number, enter the required details in the post-obit fields:

• ID: a 4-digit field. The beginning ii digits identify the type of the bank account (international or local) followed past a sequential number. Example: 1001 indicates the first local bank account.

· Ctry

• Bank Primal

• Bank Account

Note: Make sure that relevant approving is received for any BP before following the next steps.

B.17.i. If the BP Name is different from Business relationship Holder Proper name, enter the respective information in the Business relationship Holder field.

B.17.2. Bank details should but exist deleted if the information entered is incorrect. If depository financial institution details are being replaced with updated information, the old banking company details should be set to expire by clicking the Validity button changing the Valid To date.

B.17.3. Salvage when complete.

3.2.6.2 Add a UN FI Vendor Function to BP for Individual

For BP's Staff Member and Not-Staff War machine and Constabulary, only United nations FI Vendor Role should be assigned. This role is required to enable payment to these BP'due south.

C. Steps to add a UN FI Vendor office to a BP private / Transaction Code: BP

C.1. Type BP in the Control field and click the Enter icon à the BP that was nearly recently processed will be displayed. If this is not the BP you desire to add together the Vendor role to, navigate to the advisable BP.

C.2. Click the Brandish -> Change icon to make additional changes to the BP à select UN FI Vendor from the Modify in BP role drib-down list.

C.3. Additional tabs associated specifically with the Un FI Vendor Role for BP for Individual will announced but in that location is no compulsory field that need to be maintained:

• Employment Data

• Vendor: General Information

• Vendor: Tax Data

C.four. Review the data available in all the tabs, primarily the Address and Payment Transactions tabs. Most of the information in these tabs volition exist pre-populated from the generic BP contour.

C.5. Click the Company Code view to add vendor-specific information à type 1000 in the Company Code field and click the Enter icon .

C.half dozen. Click the Vendor: Business relationship Direction tab à review and ensure that the Reconciliation acct number assigned matches the BP Grouping type.

C.7. Type Z01 in the Sort primal field and VI in the Planning grouping field à click the Enter icon.

Note: The Sort primal field indicates the layout rule for the Resource allotment field in the document line item and the Planning group field is used to make up one's mind the treasury cash period.

The BP Grouping automatically determines the reconciliation account that is linked to the BP (for financial transactions).

Back to top

C.8. Click the Vendor: Payment Transactions tab à in both the Terms of Payment and Credit memo pyt term fields, blazon Z001 (paid immediately). Note that this is simply a default value and the information updated during the PO creation process tin can replace this information.

C.9. Select the Check Double Invoice check box.

C.10. Type an appropriate payment method code in the Payment methods field and Z001 in the Del.tolerance grp field à press Enter .

C.eleven. For cash/cheque payments (people without a depository financial institution account), the Accounting Clerk (Acctg clerk) field needs to exist entered every bit an indicator as to which location this payment volition exist fabricated à click the Vendor: Correspondence tab.

C.12. Blazon code correspondence to the location where payment by cash/cheque is expected in the Acctg clerk field and click Relieve when completed.

iii.two.half dozen.three Change BP Group

BP Grouping can be changed for BP created for Individuals. This is because the BP Number ranges set for all 3 categories of the Individuals are ready to be 20XXXXXXXX. BP Number will be maintained even if BP Grouping is inverse. Withal, the Reconciliation Acct number will be changed automatically to match the new BP Group.

D. The steps to change the BP grouping for an existing BP (created for Individual) with United nations Vendor Office / Transaction Codes: XK07, FK02 and BP

D.one. Type XK07 in the Command field and click the Enter icon.

D.two. Type the BP number in the Vendor field à a pop-up window appears on the screen. Ensure that the BP is selected.

D.3. Click the Enter icon.

D.four. Enter the new account grouping for the selected BP in the New account group field --> click the Enter icon

D.5. If a BP group changes, the user also needs to alter the BP'due south Reconciliation Account using the following steps:

D.5.one. Type FK02 in the Command field and click the Enter Icon.

D.5.2. Enter the BP number and Visitor Code.

D.5.3. Select the Bookkeeping Info check box à click the Enter icon.

D.v.4. Update the Recon. account number.

Notation: The Recon. account number is the vendor account number. The Recon. account number for customers do not demand to be updated. This is very important in ensuring that FI postings are correctly captured in the correct business relationship.

Dorsum to top

D.6. It is important to verify that the BP Blazon has been updated. Change the BP Type using post-obit steps:

D.six.one. Type BP in the Command field and click the Enter icon à the BP that was most recently processed will be displayed. If this is non the BP yous want to change BP Type, navigate to the advisable BP.

D.6.2. Click the Display->Change icon to brand additional changes to the BP à click the Control tab and change the BP Type to the appropriate 1.

D.6.3. Save the BP when complete.

3.2.6.iv Add UN Vendor Office

BP for Private Externals needs to be assigned United nations Vendor Role and non UN FI Vendor Role. This is because payment to Individual Externals needs to be obligated through the Umoja SRM module using a special category of Buy Orders (POs). Past adding United nations Vendor Role to these BP's, relevant purchasing information can be added for utilize by transactions related to Umoja SRM.

E. The steps to add a BP office to BP for Individual - vendor / Transaction Code: BP

E.1. Blazon BP in the Command field and click the Enter icon à the BP that was almost recently candy will be displayed. If this is non the BP you want to add the Vendor Role to, navigate to the appropriate BP.

E.two. Click the Display->Change icon to make additional changes to the BP à select UN Vendor from the Change in BP role drib-down listing.

Due east.3. Review the information available in all the tabs, primarily the Accost and Payment Transactions tab. Most of the information in these tabs volition be prepopulated from the generic BP profile.

E.4. Boosted tabs associated specifically with the United nations Vendor Role volition appear only there is no compulsory field that demand to be maintained:

• Employment Data

• Vendor: Full general Information

• Vendor: Taxation Information

E.v. Click on the Company Code view to add vendor-specific information.

E.vi. Enter 1000 in the Company Code field à press Enter.

E.7. Click the Vendor: Account Management tab à review and ensure that the Reconciliation Account number assigned matches the BP Grouping type. (Notation: The data in the Reconciliation acct (account) field is automatically populated based on the account group.)

E.8. Enter Z01 in the Sort key field and VI in the Planning group field à click the Enter icon.

Note: The data in the Reconciliation acct field is automatically populated based on the business relationship group.

Eastward.ix. Click the Vendor: Payment Transactions tab à in both the Terms of Payment and Credit memo pyt term fields, type Z001 (paid immediately). Note that this is simply a default value and the information updated during the PO creation process can replace this data.

E.10. Select the Check Double Invoice cheque box.

E.xi. Type an advisable payment method code in the Payment methods field and Z001 in the Del.tolerance grp field à press Enter.

E.12. For greenbacks/check payments (people without a bank business relationship), the Accounting Clerk field (Acctg. clerk) needs to be entered as to which location this payment will be made à click the Vendor: Correspondence tab.

E.13. Code corresponding to the location where payment by cash/check is expected in the Acctg clerk field.

Note: Additional fields volition be added in the future.

E.14. Click the Purchasing view push à type 1000 in the Purch. Organization field.

East.15. Enter the default Purchase Guild (PO) currency in the Lodge currency field. Annotation that during the PO creation process, the information entered on the PO volition override this currency.

E.16. In the Terms of Payment, type Z001 (paid immediately). Note that this is just a default value and the information updated during the PO creation process can supersede this information.

Back to top

E.17. Roll down and select the post-obit check boxes:

· GR-Based Inv. Verif.: this ensures that a appurtenances receipt transaction is performed against the PO. It is a default selection that can be removed from the certificate side.

· AutoEvalGRSetmt Del.: this is the electronic receipt settlement process that automatically creates an invoice when the goods receipt transaction takes place, e.g. services received for an private contractor. This is used for the delivery of services.

· AutoEvalGRSetmt Ret: electronic receipt process used for the return of services (automatically reverse invoice).

· SRV-Based Inv. Ver.: this ensures that a service entry sail (for service receipts) is performed against the PO.

E.18. Click the Save button à a alarm box will appear with the bulletin: 'Changes for vendor xxxxxxxxxx accept non yet been confirmed. Display this message for this business partner once more?' Note that this warning message will ever appear prior to confirming a Vendor Role in the system.

E.19. Click the No button so that the message does not display again.

iii.2.6.5 Deactivate/Expire a BP Function of a BP

To remove a part from BP, User has to either:

1. Conciliate or expire the relevant role by changing the role Valid To appointment (see F), or

2. Create a new BP without that item function, block the old BP and link them together through 'Relationship' (come across section 3.2.6.6).

F. Steps to alter the role Valid To appointment / Transaction Code: BP

F.1. Type BP in the Command field and click the Enter icon à the BP that was most recently candy volition exist displayed. If this is not the BP you want to add the Vendor Part to, navigate to the advisable BP.

F.2. Refer to step C.2, click the Brandish -> Change icon to make additional changes to the BP à select BP office that need to exist deactivate/expire from the Change in BP role drop-downward list.

F.3. Click the Magnifying Drinking glass icon, enter the Valid To date and hit Enter à click Save when complete.

three.ii.6.6 Cake/Unblock a BP

There are several methods and ways to block (or unblock) a BP from being used in performing transaction in the Umoja organization:

· Fundamental Block (T-code: BP) is used when a BP should no longer be used for any transactions in Umoja.

· Block/Unblock Vendor (T-code: XK05) is used when posting against and/or purchasing from the BP should be blocked.

· Sales Block (T-code: BP) or Customer Block/Unblock (T-code: XD05) is used when all or certain Sales and Distribution (SD) related transactions should no longer exist performed against the BP.

Note: Before blocking a BP, the user needs to check for pending invoices.

M. The procedure to do a cardinal block / Transaction Code: BP

1000.one. Type BP in the Command field and click the Enter icon.

G.2. In the BP Number field, enter the relevant BP number that needs to be blocked.

G.iii. Click the Display -> Change icon to make additional changes to the BP.

G.4. Click the General Information push button.

1000.five. Click the Status tab.

Thou.6. Select or Unselect the Key Cake check box under the Lock department to lock the BP.

Thousand.7. Click the Relieve icon.

G.viii. It is not possible to include any annotation directly against the Primal Cake bank check box at the Status tab. Any note the user wants to add together to the BP shall exist entered in the Notes field at the Command tab.

Yard.9. Go to the appropriate notation field.

G.10. Click the Pencil icon and enter relevant information in the text field.

G.11. Click the Salvage icon when completed.

Back to top

H. The process to block / unblock Vendor / Transaction Code: XK05

H.1. Type XK05 in the Command field and click the Enter icon.

H.two. Type the advisable BP number in the Vendor field.

H.3. Type 1000 in the Company Code and the relevant Purch. Organization (if demand to be specified) in the provided fields à click the Enter icon.

H.4. Select or unselect the appropriate bank check boxes in the Posting Cake, Purchasing Cake and Block for quality reasons sections to block the vendor functions à click the Salvage icon.

I. The process to do sales block/unblock / Transaction Code: BP

To block (or unblock) a BP with Un Customer function from any Sales and Distribution (SD) related transactions.

I.i. Blazon BP in the Command field and click the Enter icon.

I.2. In the BP Number field, enter the relevant BP number that needs to be blocked.

I.iii. Click the Brandish -> Modify icon to brand additional changes to the BP.

I.4. Click the Sales and Distribution button à click the Status tab.

I.five. Select or unselect the appropriate Sales Cake cheque box à click the Relieve icon.

I.half dozen. Click the Company Code button à click the Customer : Status tab.

I.seven. Select or unselect the appropriate Posting Block check box à click the Save icon.

J. Alternatively, use T-code XD05 to block or unblock the Sales and Distribution (SD) related functions of the BP / Transaction Code: XD05

J.1. Blazon XD05 in the Command field and click the Enter icon.

J.2. Type the appropriate BP number in the Customer field.

J.3. Blazon 1000 in the Company Code and the relevant Sales Area (if demand to be specified) in the provided fields à click the Enter icon.

J.4. Select or unselect the appropriate Posting Cake and/or Sales and Distribution (SD) Blocks check boxes à click the Salvage icon.

three.two.6.7 Add Alternating Payee

Alternate Payees tin exist added to a Vendor Part, due east.1000. to receive invoice against 1 vendor and pay another vendor.

K. Steps to add together alternate payee / Transaction Code: FK02

Thou.1. Type FK02 in the Control field and click the Enter Icon.

K.2. Enter the BP number and Company Code.

K.3. Select Payment transactions --> click Enter.

Back to top

K.4. Cheque the Private spec. box

K.5. Click on the Permitted Payee button. Enter the BP number of the alternate payee.

1000.6. Relieve the record when completed.

50. Alternatively, use T-code BP to add alternate payee / Transaction Code: BP

Fifty.1. Blazon BP in the Control field and click the Enter icon.

Fifty.2. Enter the relevant BP number in the BP Number field.

L.3. Click the Display -> Alter icon to make additional changes to the BP à select the BP role (Un FI Vendor or United nations Vendor) from the Change in BP role drop-down list.

L.4. Click the Company Code option à select the Vendor: Payment Transactions tab.

L.5. Enter the BP number of the alternate payee in the Alternative payee field à click the Relieve icon.

3.2.6.8 Terminate a BP

If a BP is no longer agile or its relationship with the UN has concluded, the BP tin be terminated.

M. Steps to cease a BP / Transaction Code: BP

Thou.i. Type BP in the Command field and click the Enter icon.

M.2. Enter the relevant BP number in the BP Number field.

M.3. Click the Display -> Change icon to make boosted changes to the BP à click the General Data and going to the Status tab.

M.4. Populate the followings:

· Check the Archiving Flag

· Check the Primal Block

· Enter the End Date

· Enter the appointment in the Customer Last Contact field

Chiliad.v. Click Relieve.

3.2.6.nine Approve a BP (Vendor)

The T-codes used for approving a BP in Umoja are as follows:

Approve	T-code
Vendor BP	FK08
Multiple Vendor BP changes	FK09

N. The steps to approve a vendor / Transaction Code: FK08

N.1. Type FK08 in the Control field and click the Enter icon.

N.2. Blazon the vendor BP number in the Vendor field.

North.3. Type thou in the Company Code field à click the Enter icon.

N.four. BP Approver (no bank data): Click the Changes to Sensitive Fields button at the key level and company lawmaking level to review all changes, if the Electric current status field shows the status To exist Confirmed. If the Current condition field shows the status as Confirmed, and so there are no changes that need to be confirmed.

N.5. BP Approver (with bank data): Click the Changes to sensitive fields button at the company code level and review all changes, if the Current status field shows the condition To be Confirmed. If the Current status field shows the status equally Confirmed, then there are no changes that need to be confirmed.

Due north.vi. Click the Confirm or Refuse push after reviewing the changes at the primal or company lawmaking level à click the Save icon.

Back to peak

O. The steps to corroborate multiple vendor BP changes / Transaction Code: FK09

O.one. Type FK09 in the Command field and click the Enter icon.

O.2. Type the vendor range in the relevant Vendor fields à click the icon.

O.3. The following screen will appear, list BP's with vendor roles that crave confirmation.

O.4. Click on each active link to open the Confirm Change Vendor screen and confirm the status change of each tape.

four Umoja Coding Cake

4.1 Introduction to Coding Block

The Umoja Coding Block is a tool that provides the following:

· 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 fiscal views.

· Allows the user to populate simply required fields (that is, to 'derive' related fields).

In Umoja, each module maintains a ledger and generates documents that make utilise of the coding block elements. These ledgers work in sync then that when a user posts a transaction in one ledger, corresponding entries are created in the other three. The four main ledgers of Umoja are as follows:

· Full general Ledger (maintained in the FI module): The GL only records actual postings. Every financial transaction conducted in Umoja has a respective posting inside the GL.

· Controlling Ledger (maintained in the CO module): The Controlling Ledger records postings used for cost and management accounting.

· Funds Management Ledgers (maintained in the FM module): The FM Ledgers record upkeep-relevant transactions, such as budget, consumption, budgetary resources, etc. and provides budget availability.

· Grants Ledger (maintained in the GM module): The Grants Ledger records grant-relevant transactions.

Each of the finance-related module stores data differently. This provides flexibility to perform dissimilar analysis within modules. To ensure that data remains consistent across the organisation, 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; and

· This provides a control point and then that if a transaction does not post simultaneously in all modules, then the transaction will neglect and prompt the user with an mistake message.

In Umoja, a functionality called 'Derivation' is used to excerpt the linked account assignments with a minimal entry of coding cake elements during transaction entry. For example, Cost Center will e'er derive the Business Expanse, 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 the other fields are automatically populated.

Equally an analogy, using transaction code FB60 - create an AP invoice, the business user will enter the post-obit values:

Below is the graphical presentation of Umoja Coding Block derivation by highlighting what chief information elements are entered in FI, and derived across 4 ledgers based on business transactions posted in Umoja.

The Umoja Coding Block design including derivation is based on Un reporting and assay requirements to ensure the transactions processed are grouped and rolls up to the UN reporting construction. Below is the mapping of UN classification requirements to coding cake data elements.

Back to top

'In Umoja, there are a number of changes using the Umoja Coding Block and the simultaneous postings in General Ledger, Controlling Ledger, Funds Direction Ledger, and Grants Ledger:

· Accrual accounting is adopted for fiscal accounting purposes;

· Full general Ledger is used for IPSAS actuals merely;

· Controlling Ledger is used to back up managerial bookkeeping;

· Umoja has divers additional cost centers to back up results-based management in the long-term;

· Funds Management Ledgers are used for monetary control and are on greenbacks basis;

· Functional area is used for more detailed programmatic analysis;

· Grants Ledger is used to track individual donor contributions and is on cash basis;

· Data will be entered in Umoja environment only;

· Business organisation processes will exist more automated; and

· Information will be stored in one fundamental data repository across the UN Secretariat.

4.2 Umoja Coding and Naming for Individual Coding Cake Element

4.2.1 GL Account

· Code length: viii characters

· Code composition: numeric smart code

· Short text: max. is 20 characters

· Long text: max. is fifty characters

1	2	3	4	5	half-dozen	7	8
Type*	Group			sub-grouping		specific code
7	410			x		30

*Type:

1	Electric current Assets
2	Non-Current Avails
three	Current Liability
4	Non-Current Liability
5	Net Assets
6	Revenues
7	Expenses
viii	OFF Fiscal Statements / Memo

Instance of a GL business relationship

GL Acct	Short Text	Long exam
11011010	Csh HQ USD Nominal	Cash HQ New York JPMorgan USD Wire ACH Nominal

Example of GL accounts for accounts receivable

1	ii	3	4	5	vi	7	eight
Type	Group			sub-group		specific lawmaking
ane - Current	410 - Assessed 411 - Voluntary 510 - Commutation 520 - VAT			ten - Member State 11 - Non-Memb State 12 - Govt & Local Authority thirteen - United nations Family 14 - Intergovt & NGO 15 - Commercial sixteen - Staff, Retirees 17 - Armed services & Police force 18 - Individuals Extern		10 Control Acct 14 Manual Reclassificat. xvi Assart (AFDA) 19 Revaluation

4.two.two Sponsored Class

· Lawmaking length: twenty

· Code limerick: alpha-numeric

· Short Text / Description: max. is xxx characters

1	2	3	iv	5	6	..	..	..	19	20
serial			dash	description of sponsored class
AR1			-	TRAVEL
AR1			-	Contract Service
AR1			-	Vol Contr Greenbacks

4.ii.3 Fund

· Code length: v characters

· Code limerick: alpha-numeric code that includes the fund type

· Short Text / Description: max. is twenty characters; current fund names need to be shortened

1	two	3	4	5
numeric fund blazon number		alpha code
10		UNA

Instance:

Fund Code	Fund Description
10UNA	Un General Fund
10WCA	Working Majuscule Fund

4.2.4 Grant

• Code length: 15

• Code composition: alpha-numeric

• Grant Type alpha-numeric:

1	ii	3	4	5	6	vii	8	9	10	eleven	12	13	14	15
Grant type		-	Fund					-	Sequential number
S1		-	32FSA					-	0 0 0 0 0 one
R1		-	32CER					-	0 0 0 0 0 2

· Grant types will be created for major categories: S1 - Simple Grant, R1 - Resource Mobilization Grant, M1 - Main Implementation Grant, and P1 - Passthrough Grant

· Short Text / Description: max. is xx characters

4.two.five Business Area

• Code length: 4 characters

• Code composition: alpha-numeric smart lawmaking

• Description: max. 30 characters

1	2	3	4
	grouping, numeric		sub-group, numeric, (nil-fill)
Due south	10		1

Example:

Code	BA Description
S101	United Nations Headquarters
S201	UN Role at Geneva
F400	UNODC
S101	UN Treasury Pools

four.ii.6 Cost Eye

· Code length: 5

· Lawmaking limerick: sequential number* (starting with 10000)

· Brusk text/clarification: max. is 20/xl characters; current org. unit names demand to be shortened

i	2	three	4	5
sequential number
10029

Instance:

10029	UNON Chief HRMS
10030	UNON Staff Admin Sct

4.2.vii Fund Center

• Normal Fund Centers: see cost center code

• High-level Fund Centers: vi-fourteen characters, alpha-numeric, prefix to identify where budget is entered and spending is controlled

ane	two	3	4	5	six	7	8	9	ten	11	12	13
Prefix 'B' 'C' 'BC'		_	Toll/Fund Center Group Lawmaking
			Department/entity abbreviation							seq. number
B		_	UNOG							001

Example

10021	Central Accounts Sec
10022	PK Accounts Department
BC_UNON.001	UNON Adm of Justice
BC_UNON.003	UNON HRM Service

Dorsum to top

4.2.8 Internal Gild

· Lawmaking length: eight

· Code limerick: sequential number, considering the aspect Concern Expanse and Responsible Cost Center will link the Internal Guild to an Organizational Element

· Curt Text / Description: max. is xl characters

1	two	3	4	5	6	7	8
Gild Type		sequential number
11		0 0 0 0 0 1

Example

10000080	ZM09 - Service Order (internal client/ department)
6000016	CS02 - Billable Service Social club
12000000	1200 - PK assessed contribution in kind
19000024	1920 - GM passthrough orders

iv.2.9 Project/WBSE

· Code length: xviii

· Code composition: blastoff-numeric, the first 9 characters composing the project identifier, the residual is used for the project structure

· Description: max. is 40 characters

1	2	three	4	5	6	7	8	9	10	xi	12	13	14	15	16	17	18
project code		-	sequential number							seq no			seq no			seq no
AA		-	0 0 0 0 4 5							0 1			0 1			0 1

Example

AA-000005	Role Facility
AA-000005.01	Design
AA-000005.02	Construction
AA-000005.03	PMO

4.2.10 Funded Program

· Code length: 11-18 characters

· Code limerick: blastoff-numeric

· Short Text / Clarification: max. is 20 characters

1	2	3	4	5	..	..	..	..	16	17	xviii
project code or 'IO'		-	Internal Order code or Projection code
AA		-	0 0 0 0 iv five . 0 ane . 0 ane . 0 ane
IO		-	1 i 0 0 0 0 0 1

('IO' for Internal Orders)

Example

AA-000005	Office Facility
AA-000005.03	PMO

4.ii.11 Sponsored Program

· Code length: x

· Code limerick: blastoff-numeric

· Brusk Text / Description: max. is 30 characters

1	2	three	4	5	half dozen	7	8	9	10
Earmarking			-	sequential number
F 0 1			-	100001

Example

Sp Prgr Code	Description
F01-100123	Vaccination Africa

4.two.12 Profit Heart

• Lawmaking length: iv characters

• Lawmaking composition: sequential number, with a CO Profit Heart hierarchy to create service lines

• Short Text / Clarification: max. is 20 characters

Examples

Code	Short Text
1001	Inspect
1002	Legal
1003	Safety and Security

4.2.13 Functional Area

· Code length: 7, plus five for RBM

· Lawmaking composition: numeric

· Short Text: max. is 25 characters, current programme names accept to exist shortened

1	2	three	4	5	6	7	viii	9	10	11	12	13	14	15	xvi
program code		categ	group	sub-programme				sub-activeness			upkeep period (optional)			result (optional)
ane 1		A	A	1 2 three four				i two three			B one 3			0 ane

Case

Code	Clarification
12AZ0007	NB funct control
12AA0007	Exec Dir Mgmt NB
12AC0007001	SP PPBA Nairobi
12AC0007002	SP Hour Nairobi
12AC0007003	SP Supprt services NB
12AC0007004	SP ICT ops NB

four.ii.14 Budget Period

· Code length: 3-4

· Lawmaking composition: blastoff-numeric

· Clarification: max. is 35 characters

1	2	3	(4)
code	year		'E'
B	1 3

Code: B = biennium, A = annual, P = peace keeping, MYn = multi-twelvemonth

Character 4: E = peacekeeping extended

4.3 Document Posting

Document: An bookkeeping document consists of a header and line items. Header is the part of a document that contains information valid for the whole document, for case document date, posting engagement, certificate type and document number.

Document type is a key that is used to classify accounting documents and differentiate the nature of business transactions to be posted. The arrangement unremarkably defaults the advisable document type when a business organisation transaction is entered. The certificate type determines which account types such equally vendor, customer, materials, asset, and normal GL accounts can exist posted to. A separate number range is assigned to every document type. In Umoja, both standard and custom certificate types are used.

Attached is the listing of document types which are used in Umoja. Delight have annotation that the list is discipline to change based on business requirements identified by the UN.

Posting Keys are synonymous to debit and credit side of accounting entries however apart from this; it also determines the account type to be used at debit and credit lines.

Back to top

Dec, 2016

askewaund1965.blogspot.com

Source: https://www.un.org/ipsas/Chapter2.html

Share this post