ProjectTemplatesProjectTransactionControls
The Project Transaction Control resource is used to view and create a project transaction control. Project transaction controls are a set of criteria that control whether a transaction can be charged to a project.
Columns
| Name | Type | Description |
| ProjectTemplatesProjectTemplateId [KEY] | Long | Unique identifier of the project template. |
| TransactionControlId [KEY] | Long | Identifier of the transaction control. |
| RuleNumber | Long | Identifier of the transaction control within a project or task. Default value is the successor of the maximum existing rule number. |
| StartDateActive | Date | The date from which the transaction control is effective. Default value is the project start date. |
| EndDateActive | Date | The date after which the transaction control is no longer effective. |
| BillableHint | String | Indicates that transactions charged to the project can be billed to customers. This attribute is applicable for billable projects. A list of accepted values - No and Task - is defined in the lookup type PJC_BILLABLE_INDICATOR. You can enter either this attribute or Billable Code or both of them. Default value is Task. |
| Billable | String | Indicates that transactions charged to the project can be billed to customers. This attribute is applicable for billable projects. A list of accepted values - N and T - is defined in the lookup type PJC_BILLABLE_INDICATOR. You can enter either this attribute or Billable or both of them. Default value is T. |
| ChargeableHint | String | Indicates that something is eligible to be charged to the project. A list of accepted values - Yes and No - is defined in the lookup type PJC_YES_NO. You can enter either this attribute or Chargeable Code or both of them. Default value is No. |
| Chargeable | String | Indicates that something is eligible to be charged to the project. A list of accepted values - Y and N - is defined in the lookup type PJC_YES_NO. You can enter either this attribute or Chargeable or both of them. Default value is N. |
| CapitalizableHint | String | Indicates the capitalizable status of the transaction. This attribute is applicable for capital projects. A list of accepted values - No and Task - is defined in the lookup type PJC_BILLABLE_INDICATOR. You can enter either this attribute or Capitalizable Code or both of them. Default value is Task. |
| Capitalizable | String | Indicates the code for the capitalizable status of the transaction. This attribute is applicable for capital projects. A list of accepted values - N and T - is defined in the lookup type PJC_BILLABLE_INDICATOR. You can enter either this attribute or Capitalizable or both of them. Default value is T. |
| ExpenditureCategoryId | Long | Identifier of the expenditure category. You can enter either this attribute or Expenditure Category or both of them. |
| ExpenditureCategoryName | String | A grouping of expenditure types by type of cost. For example, an expenditure category with a name such as Labor refers to the cost of labor. You can enter either this attribute or Expenditure Category ID or both of them. |
| ExpenditureTypeId | Long | Identifier of the expenditure type. You can enter either this attribute or Expenditure Type or both of them. |
| ExpenditureTypeName | String | A classification of cost that is assigned to each project cost transaction. Expenditure types are grouped into cost groups (expenditure categories) and revenue groups (revenue categories). You can enter either this attribute or Expenditure Type ID or both of them. |
| NonLaborResourceId | Long | Identifier of the nonlabor resource. You can enter either this attribute or Nonlabor Resource or both of them. |
| NonLaborResourceName | String | An implementation defined asset or pool of assets. These assets may represent actual pieces of equipment whose time is consumed, or an asset whose output is consumed. For example, you can define a nonlabor resource with a name of Training Room to track the usage of a physical room and the associated costs. The actual usage of the room is tracked in hours. You can enter either this attribute or Nonlabor Resource ID or both of them. |
| PersonName | String | The name of an individual human team member. You can enter either this attribute, Person ID, Person Number, or Email or a combination of these attributes. |
| PersonId | Long | Identifier of the person. You can enter either this attribute, Person Name, Person Number, or Email, or a combination of these attributes. |
| PersonNumber | String | Number that uniquely identifies a person. This number refers to the Fusion HCM specific identifier that uniquely identifies a person in the application, regardless of their relationship to the enterprise. It does not have any relation to any national identifier component. You can enter either this attribute, Person ID, Person Name, or Email, or a combination of these attributes. |
| EmailAddress | String | Email address of the person. You can enter either this attribute, Person ID, Person Number, or Person Name, or a combination of these attributes. |
| JobId | Long | Identifier of the job. You can enter either this attribute or Job or both of them. You must enter at least one from among the Person Name, Person ID, Person Number, and Email attributes if you enter a value for this attribute. |
| Job | String | The job that is being performed by the person that incurred the cost that was charged to the task. You can enter either this attribute or Job ID or both of them. You must enter at least one from among the Person Name, Person ID, Person Number, and Email attributes if you enter a value for this attribute. |
| PersonTypeHint | String | The type used to classify the person in human resources. For example, the person type can be either employee or contingent worker. A list of accepted values - Employee and Contingent Worker - is defined in the lookup type PJF_PERSON_TYPE You can enter either this attribute or Person Type Code or both of them. |
| PersonType | String | Indicates the code of the type used to classify the person in human resources. For example, the person type can be either employee or contingent worker. A list of accepted values - EMP and CWK - is defined in the lookup type PJF_PERSON_TYPE You can enter either this attribute or Person Type or both of them. |
| OrganizationId | Long | Identifier of the organization to which the person job belongs. You can enter either this attribute or Organization or both of them. You must enter the person and job attributes if you enter a value for this attribute. |
| Organization | String | The name of the organization to which the person job belongs. You can enter either this attribute or Organization ID or both of them. You must enter the person and job attributes if you enter a value for this attribute. |
| CreatedBy | String | The user who created the record. |
| CreationDate | Datetime | The date when the record was created. |
| LastUpdateDate | Datetime | The user who last updated the record. |
| LastUpdatedBy | String | The date when the record was last updated. |
| Finder | String | finder |
| ProjectTemplateId | Long | projecttemplateid |