Data entities - Public sector

This article provides a list of the data entities that are available for Public sector.

Available data entities

The setup for a public sector company uses the same data packages as the setup for a commercial company. However, it also uses additional packages that contain the data entities for public sector–specific features. The sequence in the following table refers to the packages that are described in other related data entity articles, and also contains details for the public sector–specific data entities. Additionally, the heading for each subsection contains a hyperlink to the corresponding related article. Note that, unless otherwise stated, any warnings and notes in the linked articles also pertain to Public sector.

System administration and Global address book

Suggested sequence Package
1 01.1.001 SYS – Currencies
2 01.1.002.SYS – System parameters
3 01.1.003 SYS – Address basic setup for legal entities
4 01.1.004 SYS – Address prerequisites for legal entities
5 01.1.005 SYS – Address setup Note: The issue that is related to failing records in the Cities entity won’t occur for public sector data.
6 01.1.006 SYS – Legal entities
7 01.1.007 SYS – Operating units
8 01.1.008 SYS – Organization hierarchies Note: Export is Organization Hierarchy – Published, and import is Organization Hierarchy. Each hierarchy must be published manually. To manually publish a hierarchy, click Organization administration > Organizations > Organization hierarchies, and select Budget planning. On the Action Pane, click View > Edit > Keep working on this draft, and then click OK. Verify that the hierarchy is accurate, and then click Publish. Enter the current date, and then click Publish.
9 01.1.009 SYS – Units
10 01.1.010 SYS – Number sequences Note: Some number sequence record files will fail. These records are linked to the companies other than PSUS.
11 01.1.011 SYS – Organizational calendar
12 01.1.012 SYS – System users
13 01.1.013 SYS – Document types
14 02.1.001 GAB – Teams
15 02.1.002 GAB – Post address setup

Workflow

Suggested sequence Package
16 02.1.003 WF – Workflow

General ledger and Bank 06.1.001 PubSect – Funds

Suggested sequence Entity name Area Entity type Dependency Comments
17 Fund types General ledger Setup None Categorization of funds. Categorization is typically completed by function.
18 Fund General ledger Setup Fund types
Suggested sequence Package
19 03.1.001 GL – Chart of accounts – Shared. Note: Activate financial dimensions, and then import the Financial dimension sets data entity again. To activate financial dimensions, click General ledger > Chart of accounts > Dimensions > Financial dimensions, and select Close on pop up. On the Action Pane, click Activate, and then, on the Activate financial dimensions page, click Activate. The posting type must be added to the Sales tax payable and Use tax payable main accounts. Click General ledger > Chart of accounts > Accounts > Main accounts, and open account 24800. On the Posting validation FastTab, in the Posting type field, select Sales tax. Repeat for this procedure for main account 24801.
20 03.1.002 GL – Account structures – Shared. There is a known issue on export in PSUS for the Advanced rule structure allowed values and Account structure allowed values data entities. No values are exported for these two data entities. The package on Microsoft Dynamics Lifecycle Services (LCS) has been modified.
21 03.1.003 GL – Fiscal calendar – Shared
22 03.1.004 GL – Ledger setup. If you’re using demo data, records will fail in the Ledger fiscal calendar period data entity because of closed periods that can’t be reopened.
23 03.1.005 GL – Ledger journals. Records will fail in the Journal names data entity until the Bank accounts data entity is imported. After the bank accounts are imported, import the Journal names data entity again.

06.1.002 PubSect – Posting definition setup If you’re using demo data, some records will fail in the Posting definition entry data entity because of a known issue.

Suggested sequence Entity name Area Entity type Dependency Comments
24 Posting definition General ledger Setup None
25 Posting definition entry General ledger Setup Posting definition The lines that are associated with each posting definition
26 Transaction posting definition Bank General ledger Setup Posting definition The association of the posting definition with the Bank module
27 Transaction posting definition General ledger General ledger Setup Posting definition The association of the posting definition with the General ledger module
28 Transaction posting definition Payable General ledger Setup Posting definition The association of the posting definition with the Payable module
29 Transaction posting definition Purchasing General ledger Setup Posting definition The association of the posting definition with the Purchasing module
30 Transaction posting definition Receivable General ledger Setup Posting definition The association of the posting definition with the Receivable module
31 Transaction posting definition Budget General ledger Setup Posting definition, Budget Setup The association of the posting definition with the Budget module. Note: Budget setup is a dependency for the Transactional posting definition budget. Therefore, this data entity is included with the Budget setup package.
Suggested sequence Package
32 03.1.006 GL – Allocations
33 03.1.007 BANK – Bank setup
34 03.1.008 BANK – Bank accounts. Note: If you’re using demo data, remove NSFJournalName from the Bank accounts data entity import file, and re-import Journal names. Then, on the Payment management tab, in the NSF payment journal field for bank accounts PSUS Oper and PSUS Payrol, select CustPay. NSFJournalName has been removed from the Bank accounts data entity in the package on LCS.
35 Re-import 03.1.005 – Ledger journals

06.8.001 PubSect – Advanced ledger entry lines If you’re using demo data, many records will fail because of dependencies on Project. After the Project master data entity is imported, import the Advanced ledger entry lines data entity again.

Because of a known issue with demo data, the posting definition isn’t attached to many lines. The package on LCS has been modified.

Suggested sequence Entity name Area Entity type Dependency Comments
36 Advanced ledger entry lines General ledger Transaction General ledger setup, Posting definitions The general ledger entry that is source document–enabled and uses posting definitions

Human resources

Suggested sequence Package
37 05.1.001 HR – Foundation setup
38 05.1.002 HR – Competencies
39 05.1.003 HR – Jobs
40 05.1.004 – Pay
41 05.1.005 HR – Employees
42 05.1.006 HR – Contractor
43 05.1.011 HR – Benefits. Pay cycle and Pay period are dependencies for this entity, but payroll DEs aren’t available. Manually generate the pay periods for the pay cycle, and then re-import Calculation frequency pay period.
44 05.1.007 HR – Positions
45 05.1.008 HR – Worker details
46 05.1.009 HR – Compensation
47 05.1.010 HR – Absence
48 05.1.012 HR – Performance
49 05.1.013 HR – Courses. If you receive a record that has Fail in the Courses data entity, import this data entity after you import vendors. Note: There is a known demo data issue with the Course types data entity. The package on LCS has been modified.
50 05.1.014 HR – Recruitment. You must manually start the recruitment projects. Click Human resources > Recruitment > Recruitment projects > Recruitment projects, and select the Bookkeeper project. Then, on the Action Pane, click Recruitment project status. Repeat this procedure for each project, and then import Applications again. Note: Records will fail in the Applicants data entity because of a known issue that is related to effective and expiration dates. Records will also fail in the Applications data entity because of dependency on the Applicants data entity.
51 05.1.015 HR – Employee related associations. Note: See the comment for the Employee fixed compensation data entity in the Data entities: Human resources article. If you’re using demo data, the Injury and illness incidents data entity will fail. The package on LCS has been modified.
52 05.1.016 HR – Human resources parameters. Note: If you’re using demo data, the Human resources parameters data entity will fail. The package on LCS has been modified.
53 05.1.017 HR – Shared human resources parameters. Note: If you’re using demo data, the Shared human resources parameters data entity will fail. The package on LCS has been modified.

Accounts payable and taxes

Suggested sequence Package
54 10.1.001 AP – AP and AR shared setup
55 10.1.002 AP – Vendor payment setup
56 10.1.003 AP – Vendor attributes
57 10.1.006 Tax – Sales tax setup. Note: Some records in Sales tax authorities and Sales tax period setup will fail because of dependencies on Vendors. You should re-import this package after the Vendors package has been imported.
58 10.1.007 Tax – Sales tax code groups. Note: Some records in this package will fail because of dependencies on Vendors. You should re-import this package after the Vendors package has been imported.
59 10.1.004 AP – Vendors
60 06.1.003 PubSect – Vendor certification types
Suggested sequence Entity name Area Entity type Dependency Comments
61 Vendor certification types Accounts payable Setup None Vendor attribute that are related to specific functions that are performed or certifications that are held
Suggested sequence Package
62 Re-import 10.1.006 Tax – Sales tax setup
63 Re-import 10.1.007 Tax – Sales tax code groups
64 Re-import 05.1.013 HR – Courses
65 10.1.005 AP – AP Parameters
66 10.1.008 Tax – Sales tax parameters

Accounts receivable

If you’re implementing Accounts receivable but aren't using Accounts payable, you should use the 10.1.001 AP and AR shared setup package. For details about that package, see Data entities: Accounts payable and taxes.

Suggested sequence Package
67 11.1.001 AR – Customer payment setup
68 11.1.002 AR – Customer attributes
69 11.1.003 AR – Customers
70 11.1.004 AR – Accounts receivable parameters
71 06.1.004 PubSect – Billing classification and codes. Note: Records will fail because of dependencies on Interest codes and Collection. The package on LCS has not been modified.
Suggested sequence Entity name Area Entity type Dependency Comments
72 Billing classification Accounts Receivable Setup Interest codes US and Collection letters Setup data for classifying details such as the main account, to make it easier to create a group and, in turn, vendor invoices
73 Billing code with billing code version Accounts Receivable Setup Billing classification, Interest codes US and Collection letters The component details that make up the billing classification
74 Billing classification with billing code Accounts Receivable Setup Billing classification, Billing code
75 Billing code custom field Accounts Receivable Setup Billing code
76 Billing code with accounting distribution Accounts Receivable Setup Billing code
77 Billing codes with billing code customer field Accounts Receivable Setup Billing code
78 Billing code with billing code rate Accounts Receivable Setup Billing code

Budgeting All General ledger data entities and the setup are a prerequisite for importing Budgeting data entities. For more information about General ledger data entities, and to confirm that the setup is completed, see Data entities: General ledger.

Suggested sequence Package
79 12.1.001 BUD – Ledger budget setup
80 12.1.002 BUD – Budget control setup
81 12.8.001 BUD – Budget account entries

Budget planning

Suggested sequence Package
82 12.1.003 BUD – Budget planning setup. A demo data issue will cause records to fail in the Budget plan stage rule data entity. The package on LCS has been modified.
83 12.01.004 BUD – Forecast position

Costing

Suggested sequence Package
84 15.1.001 COS – Costing setup

Inventory management

Suggested sequence Package
85 19.1.001 INV – Site setup
86 19.1.002 INV – Warehouse setup
87 19.1.003 INV – Group setup
88 19.1.004 INV – Journal setup
89 19.1.005 INV – Packing setup
90 19.1.006 INV – Posting definitions
91 19.1.008 INV – Inventory parameters
92 19.1.007 INV – Price discount setup
93 19.4.001 INV – Charge groups

Fixed assets

Suggested sequence Package
94 16.01.001 FA – Fixed assets attributes
95 16.01.002 FA – Fixed assets setup. Note: On the Fixed asset parameters data entity, unmap DefaultValueModelID. If you’re using demo data, records in the Fixed asset value model data entity will fail because of missing depreciation profiles. The package on LCS has been modified for import.
96 16.01.003 FA – Fixed assets. Note: If you’re using demo data, records in the Fixed asset value model data entity will fail because of missing depreciation profiles. The package on LCS has been modified for import.

Product information management

Suggested sequence Package
97 24.1.001 PIM – Dimension groups
98 24.1.002 PIM – Product variant groups
99 24.1.003 PIM – Size assignments
100 24.1.004 PIM – Color assignments
101 24.1.005 PIM – Style assignments
102 24.1.006 PIM – Category setup. Note: Before you proceed, confirm that product categories are accurately set up.
103 24.1.007 PIM – Attribute types
104 24.1.008 PIM – Product attributes. Note: If you’re using demo data, records in the Product attributes data entity will fail because of missing depreciation profiles. The package on LCS has been modified for import.
105 24.4.001 PIM – Attribute groups
106 24.4.002 PIM – Products – Shared
107 24.4.003 PIM – Product UOM conversion
108 24.4.004 PIM – Product variants
109 24.4.005 PIM – Released product creation. Note: This is used if Products fails.
110 24.4.006 PIM – Released products
111 24.4.007 PIM – Released product variants
112 24.4.008 PIM – Category attributes
113 24.4.009 PIM – Attribute values

Procurement and sourcing

Suggested sequence Package
114 23.1.001 PRO – Summary parameters
115 23.1.002 PRO – Purchase order setup
116 23.1.003 PRO – Distribution setup
117 23.1.004 PRO – Form setup
118 23.1.005 PRO – Prices discounts setup
119 23.1.006 PRO – External item setup
120 23.1.007 PRO – Vendor setup
121 23.1.008 PRO – Supp item setup
122 23.1.009 PRO – Rebate setup
123 23.1.010 PRO – Price tol setup
124 23.1.011 PRO – Discount groups setup
125 23.1.012 PRO – Policies setup. Note: The Procurement type document default values data entity will fail because a dependent data entity, Return actions, is missing. The package on LCS has been modified to make import easier.
126 23.1.013 PRO – Purchase agreement classification

06.1.005 PubSect – PO commitment

Suggested sequence Entity name Area Entity type Dependency Comments
127 Confirming PO Procurement Setup None Description of the types of PO confirmations
128 Commitment lines Procurement Setup None
Suggested sequence Package
129 23.4.001 PRO – Charges setup
130 23.4.002 PRO – Purchase agreements. Note: Before you import the package, reset the number sequence for Purchase agreement ID to 1, and then unmap PurchaseAgreementID.
131 23.4.003 PRO – Purchase agreement lines
132 23.8.001 PRO – Purchase orders. Note: Before you import the package, reset the number sequence for the Purchase order ID to 1, and unmap ReasonCode. Some records will fail because of a Project dependency. Re-import this package after you import the Project master data entity dependency.
133 23.8.002 PRO – Purchase order lines. Note: If you’re using demo data, records will fail due to Project and Fixed assets dependencies. Re-import this package after you import Project master and all Fixed asset packages.

Project accounting

Suggested sequence Package
134 26.1.001 PA – Projects setup
135 26.1.002 PA – Journals setup
136 26.1.003 PA – Estimates setup
137 26.1.004 PA – Forms setup
138 26.1.005 PA – Resourcing setup. Note: Review the warnings in the “Resourcing setup” section in the Data entities: Project accounting article.
139 26.1.006 PA – Project periods
140 26.1.007 PA – Categories, posting, and line property. Note: If you’re using demo data, records will fail in the Line property setup because of a dependency on Projects. Re-import this package after you’ve imported the Project master data entity.
141 26.1.008 PA – Forecasts setup
142 26.1.009 PA – Retention setup
Important: Before you proceed with additional data import, you must manually set up Project management and accounting parameters, because that information is required in order to complete the remaining steps.
143 26.1.010 PA – Grants setup
144 26.1.011 PA – Project contracts. Note: Records will fail in Project funding source data entity because of a dependency on Grants. You must manually set up Grants from demo data by using the components that were imported in 26.1.010 PA – Grants setup. Records will fail in Project funding rule because of a dependency on Project funding sources.
145 26.1.012 PA – Inventory project consumption setup
146 26.1.013 PA – Projects master. Review the warnings in the section for the Project master data entity in the Data entities: Project accounting article.
147 Re-import 26.1.007 PA – Categories, posting, and line property
148 26.1.014 PA – Validation setup. Review the warnings in the section for the Validation setup data entity in the Data entities: Project accounting article.
149 26.1.015 PA – Pricing setup
150 26.1.016 PA – Indirect costs setup
151 26.8.001 – Project beginning balance. Review the warnings in the section for the Project beginning balance data entity in the Data entities: Project accounting article.
152 26.8.002 – Project hour and fee journal transactions. Review the warnings in the section for the Project hour and fee journal transactions data entity in the Data entities: Project accounting article.
153 Re-import 06.8.001 PubSect – Advanced ledger entry lines
154 Re-import 23.8.001 PRO – Purchase orders
155 Re-import 23.8.002 PRO – Purchase order lines

See also

Data entities and packages framework

Data entities