Please enable JavaScript to view this site.

Made in EU
Visma.net Financials Forums

Navigation: Catalog: VismaNet > Schemas > Schema: Project > Tables

Projects: Visma.net Financials Projects

Get a range of Projects - ScreenId=PM301000The requested page size must be lower or equal to the allowed max page size which is returned as part of the metadata information.If requested page size is greater than allowed max page size, request will be limited to max page size

Catalog: VismaNet

Schema: Project

Primary Keys: projectId

Label: Projects

Retrieve: true

Insert: true

Update: true

Delete: false

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function Projects. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name

Data Type

Required

Default Value

Documentation

attributes

 

☐

 

Identifies the attributes

branch

 

☐

 

The branch name.

createdDateTime

 

☐

 

This value, generated by the system, indicates the creation date and time. Use it to retrieve all records that have been created since that time, up to the present.Accepted format:* ```yyyy-MM-dd```* ```yyyy-MM-dd HH:mm:ss```* ```yyyy-MM-dd HH:mm:ss.FFF```* ```yyyy-MM-ddTHH:mm:ss```* ```yyyy-MM-ddTHH:mm:ss.FFF```_Note:_ __CreatedDateTime__ and __CreatedDateTimeCondition__ are __mutually inclusive__.

createdDateTimeCondition

 

☐

 

This value represents the condition to be applied when retrieving records.Accepted values (without the single quotes):* '>' for greater than* '<' for less than* '>=' for greater than or equal* '<=' for less than or equal_Note:_ __CreatedDateTime__ and __CreatedDateTimeCondition__ are __mutually inclusive__.

expandAttribute

 

☐

 

Expands project atributes

lastModifiedDateTime

 

☐

 

This value, generated by the system, indicates the last time the record was modified. Use it to retrieve all records that have been modified since that time, up to the present.Accepted format:* ```yyyy-MM-dd```* ```yyyy-MM-dd HH:mm:ss```* ```yyyy-MM-dd HH:mm:ss.FFF```* ```yyyy-MM-ddTHH:mm:ss```* ```yyyy-MM-ddTHH:mm:ss.FFF```_Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__.

lastModifiedDateTimeCondition

 

☐

 

This value represents the condition to be applied when retrieving records.Accepted values (without the single quotes):* '>' for greater than* '<' for less than* '>=' for greater than or equal* '<=' for less than or equal_Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__.

nonProject

 

☐

 

Set to true to return the non-project.

onHold

 

☐

 

If the project is on hold

publicId

 

☐

 

Identifies the Project by its publicId

restrictedEmployee

 

☐

 

ID of the employee where access restrictions apply

restrictedUser

 

☐

 

Id of the odp user where access restrictions apply

startDate

 

☐

 

Project’s start date

status

 

☐

 

Use drop down and select Status. (Values: Planned, Active, Completed, Cancelled, OnHold, PendingApproval)

systemTemplate

 

☐

 

If the project is a template

taskStatus

 

☐

 

Use drop down and select Status. (Values: Planned, Active, Cancelled, Canceled, Completed)

taskVisibleInAp

 

☐

 

If the project task is visible in the Supplier ledger

taskVisibleInAr

 

☐

 

If the project task is visible in the Customer ledger

taskVisibleInCa

 

☐

 

If the project task is visible in the Cash management workspace

taskVisibleInCr

 

☐

 

If the project task is visible in the CRM workspace

taskVisibleInEa

 

☐

 

If the project task is visible in the Expense workspace

taskVisibleInGl

 

☐

 

If the project task is visible in the General ledger workspace

taskVisibleInIn

 

☐

 

If the project task is visible in the Inventory workspace

taskVisibleInPo

 

☐

 

If the project task is visible in the Purchases workspace

taskVisibleInSo

 

☐

 

If the project task is visible in the Sales workspace

taskVisibleInTa

 

☐

 

If the project task is visible in the Time entities workspace

visibleInAP

 

☐

 

If the project is visible in AP

 

Columns of Table Function

The columns of the table function Projects are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

Name

Data Type

Label

Required

Documentation

allocationRule_active

char

Allocation Rule Active

☐

 

allocationRule_description

varchar2

Allocation Rule Description

☐

Click on the magnifier. > The description.

allocationRule_id

varchar2

Allocation Rule ID

☐

Click on the magnifier. > The identifier.

assets

double

Assets

☐

The top part > Assest > The actual assets for the project.

autoAllocate

char

Auto Allocate

☐

Summary tab > Invoicing and allocation settings section > Run allocation when you release project transactions > A check box that indicates (if selected) that allocation is run automatically during the release of the documents associated with this project.

automaticReleaseAr

char

Automatic Release AR

☐

Summary tab > Invoicing and allocation settings section > Automatically release customer documents > A check box that indicates (if selected) that invoice documents are released automatically after the project invoicing is completed.

billingPeriod

varchar2

Billing Period

☐

Summary tab > Invoicing and allocation settings section > Invoicing period > The frequency of invoicing, which can be one of the following options: Week, Month, Quarter, Year, On demand.

billingRule_active

char

Billing Rule Active

☐

 

billingRule_description

varchar2

Billing Rule Description

☐

Click on the magnifier. > The description.

billingRule_id

varchar2

Billing Rule ID

☐

Click on the magnifier. > The identifier.

branch_name

varchar2

Branch Name

☐

Click the magnifier. > The name.

branch_number

varchar2

Branch Number

☐

Click the magnifier. > The identifier.

COMPANY_CODE

varchar2(30)

Company Code

☑

Partition code, segmenting the data.

COMPANY_NAME

varchar2(240)

Company Name

☑

Name of the partition.

customer_name

varchar2

Customer Name

☐

Click the magnifier. > The name.

customer_number

varchar2

Customer Number

☐

 

customerLocation_id

int32

Customer Location ID

☐

Click the magnifier > The identifier

customerLocation_name

varchar2

Customer Location Name

☐

Click the magnifier > The displayed name

defAccount_description

varchar2

Default Account Description

☐

Name of item/description

defAccount_number

varchar2

Default Account Number

☐

Number of item

defAccount_type

varchar2

Default Account Type

☐

 

defAccrualAccount_description

varchar2

Default Accrual Account Description

☐

Name of item/description

defAccrualAccount_number

varchar2

Default Accrual Account Number

☐

Number of item

defAccrualAccount_type

varchar2

Default Accrual Account Type

☐

 

defAccrualSub_active

char

Default Accrual Account Sub Active

☐

 

defAccrualSub_description

varchar2

Default Accrual Account Sub Description

☐

Click on the magnifier. > The description.

defAccrualSub_id

varchar2

Default Accrual Account Sub ID

☐

Click on the magnifier. > The identifier.

defSub_active

char

Default Sub Active

☐

 

defSub_description

varchar2

Default Sub Description

☐

Click on the magnifier. > The description.

defSub_id

varchar2

Default Sub ID

☐

Click on the magnifier. > The identifier.

description

varchar2

Description

☐

Mandatory field: The top part > Description* > The description of the project.

endDate

datetime

End Date

☐

Summary tab > Project properties section > End date > The date when the project is expected to end.

errorInfo

varchar2

Error Message

☐

 

expenses

double

Expenses

☐

The top part > Expenses > The total of the current expenses incurred by the project.

hold

char

Hold

☐

The top part > Hold > A check box that you select to indicate that the project should have the In planning status.

income

double

Income

☐

The top part > Income > The income expected from the project.

internalID

int32

Internal ID

☐

 

lastBillingDate

datetime

Last Billing Date

☐

Summary tab > Invoicing and allocation settings section > Last invoicing date > The date when the latest invoicing was performed for the project.

lastModifiedDateTime

datetime

Last Modified

☐

System generated information

liability

double

Liability

☐

The top part > Liabilities > The actual liabilities for the project.

metadata_maxPageSize

int64

Metadata Max Pagesize

☐

 

metadata_totalCount

int64

Total Count

☐

 

nextBillingDate

datetime

Next Billing Date

☐

Summary tab > Invoicing and allocation settings section > Next invoicing date > The date for which the next invoicing is scheduled for the project.

note

varchar2

Note

☐

The note on the project.

projectID

varchar2

Project ID

☐

Mandatory field: The top part > Project ID* > The unique ID for the project.

projectManager_address_addressId

int32

 

☐

 

projectManager_address_addressLine1

varchar2

 

☐

Address 1 > The first line of the customer's/supplier's/company's/employee's contact address.

projectManager_address_addressLine2

varchar2

 

☐

Address 2 > The second line of the address.

projectManager_address_addressLine3

varchar2

 

☐

Address 3 > The third line of the address.

projectManager_address_city

varchar2

 

☐

City > The city.

projectManager_address_country_errorInfo

varchar2

 

☐

 

projectManager_address_country_id

varchar2

 

☐

Mandatory field: Country ID* > The unique two-letter country ID according to international standard ISO 3166.

projectManager_address_country_metadata_maxPageSize

int64

 

☐

 

projectManager_address_country_metadata_totalCount

int64

 

☐

 

projectManager_address_country_name

varchar2

 

☐

Mandatory field: Country name* > The complete name of the country.

projectManager_address_county_id

varchar2

 

☐

Click the magnifier > The identifier

projectManager_address_county_name

varchar2

 

☐

Click the magnifier > The displayed name

projectManager_address_postalCode

varchar2

 

☐

Postcode > The postcode.

projectManager_branch_name

varchar2

 

☐

Click the magnifier. > The name.

projectManager_branch_number

varchar2

 

☐

Click the magnifier. > The identifier.

projectManager_calendarID

varchar2

 

☐

 

projectManager_contact_attention

varchar2

 

☐

Attention > The attention line as it is used in your customer's/supplier's/company's business letters. The intention of this line is to direct the letter to the right person if the letter is not addressed to any specific person.

projectManager_contact_contactId

int32

 

☐

 

projectManager_contact_email

varchar2

 

☐

Email > The email address of the customer/supplier/company as a business entity.

projectManager_contact_employeeContact

varchar2

 

☐

Employee contact > The link to the contact record associated with the employee.

projectManager_contact_fax

varchar2

 

☐

Fax > The fax number.

projectManager_contact_firstName

varchar2

 

☐

First name > The first name of the employee.

projectManager_contact_lastName

varchar2

 

☐

Mandatory field: Last name* > The last name of the employee.

projectManager_contact_midName

varchar2

 

☐

Middle name > The middle name of the employee.

projectManager_contact_name

varchar2

 

☐

Name > The legal name of to appear on the documents.

projectManager_contact_phone1

varchar2

 

☐

Phone 1 > The default phone number.

projectManager_contact_phone2

varchar2

 

☐

Phone 2 > An additional phone number.

projectManager_contact_phone3

varchar2

 

☐

Phone 3 > An additional phone number of the employee.

projectManager_contact_title

varchar2

 

☐

Title > The courtesy title to be used for the employee.

projectManager_contact_web

varchar2

 

☐

Web > The website of the company, if one exists.

projectManager_department

varchar2

Project Manager Department

☐

Mandatory field: General information tab > Employee section > Department* > The department the employee works for.

projectManager_employeeClass_description

varchar2

 

☐

Click on the magnifier. > The description.

projectManager_employeeClass_id

varchar2

 

☐

Click on the magnifier. > The identifier.

projectManager_employeeId

int32

Project Manager Employee ID

☐

Mandatory field: The top part > Employee ID* > The unique identifier, which is assigned to the employee in accordance with the configuration of the EMPLOYEE segmented key.

projectManager_employeeLogin

varchar2

 

☐

 

projectManager_employeeName

varchar2

Project Manager Employee Name

☐

The top part > Employee name > The name of this employee.

projectManager_employeeNumber

varchar2

Project Manager Employee Number

☐

General information tab > Employee settings section > Employee ref. no. > A reference number for the employee.

projectManager_employeeUserId

guid

 

☐

Employee internal user ID. This is the ID of the user linked to the employee

projectManager_errorInfo

varchar2

 

☐

 

projectManager_lastModifiedDateTime

datetime

 

☐

 

projectManager_metadata_maxPageSize

int64

 

☐

 

projectManager_metadata_totalCount

int64

 

☐

 

projectManager_status

varchar2

Project Manager Status

☐

Mandatory field: The top part > Status > The status of the employee. The following options are available: Active, On hold, Hold payments, Inactive, One-time.

projectManager_timeStamp

blob

 

☐

Identifier that represents a specific version of the resource.It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers)

publicId

guid

Public ID

☐

 

rateTable_description

varchar2

Rate Table Description

☐

Click on the magnifier. > The description.

rateTable_id

varchar2

Rate Table ID

☐

Click on the magnifier. > The identifier.

restrictEmployees

char

Restrict Employees

☐

Summary tab > Project properties section > Restrict employees > A check box that indicates (if selected) that only the employees listed on the Employees tab of this window can create activities and documents associated with the current project.

restrictEquipment

char

Restrict Equipment

☐

 

startDate

datetime

Start Date

☐

Mandatory field: Summary tab > Project properties section > Start date* > The date when the project starts.

status

varchar2

Status

☐

The top part > Status > The status of the project, which can be one of the following options: In planning, Active, Completed, Suspended, Cancelled.

systemTemplate

char

System Template

☐

 

template_description

varchar2

Template Description

☐

Name of item/description

template_number

varchar2

Template Number

☐

Number of item

template_status

varchar2

Template Status

☐

 

timeStamp

blob

Timestamp

☐

Identifier that represents a specific version of the resource.It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers)

visibility_visibleInAp

char

 

☐

Supplier ledger

visibility_visibleInAr

char

 

☐

Customer ledger

visibility_visibleInCa

char

 

☐

Cash management

visibility_visibleInCr

char

 

☐

 

visibility_visibleInEa

char

 

☐

Expenses

visibility_visibleInGl

char

 

☐

General ledger

visibility_visibleInIn

char

 

☐

Inventory

visibility_visibleInPo

char

 

☐

Purchases

visibility_visibleInSo

char

 

☐

Sales

visibility_visibleInTa

char

 

☐

Time entries

 

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

  
Disclaimer