Regular Element with Costing Type of Distributed Examples
These examples are of regular elements with a distributed costing type.
At Least One Segment Defined at Distributed Element Eligibility Level
In this costing example, the flexfield that contains 4 segments, such as company, cost center, expenditure type, and project has a costing type of Distributed, has at least one segment defined at the distributed element eligibility level and has these costing entries:
|
Distributed Element Eligibility |
Payroll |
Element Eligibility of a Set Member |
Department |
Job |
Element Entry |
---|---|---|---|---|---|---|
Company |
01 |
|||||
Cost Center |
100 |
|||||
Expenditure Type |
70001 |
60001 |
||||
Project |
000000 |
123456 |
Based on the above entries, the costing process determines these costing levels to build the cost account 01.100.70001.000000:
-
Company is costed at Payroll level.
-
Cost Center is costed at the Department level.
-
Expenditure Type is costed at the Distributed Element Eligibility.
-
Project is costed at the Payroll level.
Here, 000000 is considered for the Project segment from the Payroll level because element eligibility of set member will be ignored if at least one segment is populated at distributed element eligibility level
The priority account isn't actually part of the hierarchy. The distributed element eligibility takes highest priority in the above hierarchy. And, when the same segment is populated at higher level in the costing hierarchy with distributed element eligibility, then it's used in the costing process. For example,
-
Account Number 70001 is defined at distributed element eligibility level.
-
Account Number 60001 is defined at Person Costing for the account segment.
-
The costing process uses 60001 for the account number.
No Segment Defined at Distributed Element Eligibility Level
In this costing example, the flexfield that contains 4 segments, such as company, cost center, expenditure type, and project has a costing type of Distributed, has no segment defined at the distributed element eligibility level and has these costing entries:
|
Distributed Element Eligibility |
Payroll |
Element Eligibility of a Set Member |
Department |
Job |
Element Entry |
---|---|---|---|---|---|---|
Company |
01 |
|||||
Cost Center |
I |
100 |
||||
Expenditure Type |
60001 |
|||||
Project |
000000 |
123456 |
Based on the above entries, the costing process determines these costing levels to build the cost account 01.100.60001.123456:
-
Company is costed at Payroll level.
-
Cost Center is costed at the Department level.
-
Expenditure Type is costed at the Element Eligibility of a Set Member level.
-
Project is costed at the Element Eligibility of a Set Member level.
Here, 123456 is considered for Project segment from set member element eligibility because no segment is populated at distributed element eligibility level.
The priority account isn't actually part of the hierarchy. The distributed element eligibility takes highest priority over the above hierarchy. And, when the same segment is populated at higher level in the costing hierarchy with distributed element eligibility, then it's used in the costing process. For example,
-
Account Number 60001 is defined at Person Costing for the account segment.
-
The costing process uses 60001 for the account number.