Purchase Requisition Mapping Group

Use the Purchase Requisition mapping group to map header information on the SuiteProjects Pro purchase request record with header information on the NetSuite purchase requiition transaction record. The mapping group supports filters.

For reference information and best practice guidelines, review the following topics:

References — Overview of record types in SuiteProjects Pro and NetSuite with links to the relevant reference material for information about fields available for mapping.
Default and Custom Filters — Overview of default filters and how to modify the default behavior, and custom filters. Custom filters are supported for this mapping group.
Default Field Mappings — Overview of default field mapping definitions including notes and best practice guidelines where relevant. Information exported by default includes NetSuite employee ID for the user who created the expense report, expense report date, expense report number, advance, notes, accounting and supervisor approval (with NetSuite user IDs of approvers), and multicurrency flag. Filters and pullbacks are supported.
Additional Field Mappings — There are no specific best practice guidelines for custom field mapping definitions. The mapping group supports custom pullback field mappings, retrieving information from the record created in NetSuite back into SuiteProjects Pro.

References

The following table gives reference information about the records and fields available for custom field mapping definition with links to the relevant reference material. See also Schema Reference Documentation.

NetSuite Record type [`SOAP object`]	SuiteProjects Pro Record Type [`table`]	Mapping Group [`Integration point`]
Purchase Requisition [`PurchaseRequisition`] Schema: PurchaseRequisition (2025.2)\|PurchaseRequisition (2023.1) XSD: tranPurch (2025.2)\|tranPurch (2023.1) XSD (pullback): `TransactionSearchRowBasic` — platformCommon (2025.2)\|platformCommon (2023.1)	Purchase Request [`purchaserequest`] Data Dictionary: purchaserequest	Purchase requisition [`PURCHASE_REQUEST_TO_PURCHASE_REQUISITION`]

NetSuite Record type [SOAP object]

SuiteProjects Pro Record Type [table]

Mapping Group [Integration point]

Purchase Requisition [PurchaseRequisition]

Schema: PurchaseRequisition (2025.2)|PurchaseRequisition (2023.1)

XSD: tranPurch (2025.2)|tranPurch (2023.1)

XSD (pullback): TransactionSearchRowBasic — platformCommon (2025.2)|platformCommon (2023.1)

Purchase Request [purchaserequest]

Data Dictionary: purchaserequest

Purchase requisition [PURCHASE_REQUEST_TO_PURCHASE_REQUISITION]

Default and Custom Filters

By default, purchase requests records are exported from SuiteProjects Pro to NetSuite if the following conditions are met:

The purchase request is approved in SuiteProjects Pro.
The purchase request was not already exported — purchaserequest.exported is empty.
The NetSuite ID [netsuite_purchaserequisition_id] custom field is empty OR the Allow objects with a NetSuite ID to be exported during integration run box is checked on the NetSuite Connector administration form. See Allow objects with a NetSuite ID to be exported during integration run.

Custom filters are supported for this mapping group. For more information about adding filter conditions, see Using Filters and Filter Definition.

Default Field Mappings

The following table describes the default field mapping definitions for the Purchase Requisition mapping group tab.

NetSuite Field	SuiteProjects Pro Field	Notes
`PurchaseRequisition.entity`	Looked up SuiteProjects Pro field value — `User.netsuite_user_id__c` for the employee with `User.id` equal to `Purchaserequest.user_id`	The internal ID for the NetSuite employee record corresponding to the employee who submitted the purchase request in SuiteProjects Pro.
`Transaction.internalId`	`Purchaserequest.netsuite_purchaserequisition_id__c`	Not visible on mapping definition table [Pullback] When you export a new purchase request record from SuiteProjects Pro to NetSuite, SuiteProjects Pro stores the internal ID of the NetSuite purchase requisition in the NetSuite ID [`netsuite_purchaserequisition_id`] custom field. This custom field is used to link the SuiteProjects Pro and NetSuite records for future updates and matching record associations.
—	`Purchaserequest.exported`	Not visible on mapping definition table SuiteProjects Pro adds a timestamp for the date and time the record was exported.

NetSuite Field

Direction

SuiteProjects Pro Field

Notes

PurchaseRequisition.entity

Looked up SuiteProjects Pro field value —

User.netsuite_user_id__c for the employee with User.id equal to Purchaserequest.user_id

The internal ID for the NetSuite employee record corresponding to the employee who submitted the purchase request in SuiteProjects Pro.

Transaction.internalId

Purchaserequest.netsuite_purchaserequisition_id__c

Not visible on mapping definition table

[Pullback] When you export a new purchase request record from SuiteProjects Pro to NetSuite, SuiteProjects Pro stores the internal ID of the NetSuite purchase requisition in the NetSuite ID [netsuite_purchaserequisition_id] custom field. This custom field is used to link the SuiteProjects Pro and NetSuite records for future updates and matching record associations.

—

Purchaserequest.exported

Not visible on mapping definition table

SuiteProjects Pro adds a timestamp for the date and time the record was exported.

Additional Field Mappings

Important:

Review the following guidelines

You should contact your SuiteProjects Pro Professional Services representative if you need to make changes to your integration configuration and field mapping definitions.
For advanced mapping usage and best practice guidelines, see Advanced Field Mapping Definition.
Familiarize yourself with the NetSuite and SuiteProjects Pro technical documentation before attempting to set field mapping definitions using the advanced notation — See Schema Reference Documentation.

The following table describes additional field mapping definitions for the Expense Report mapping group tab that may be required or useful in some cases.

NetSuite Field	Direction	SuiteProjects Pro Field	Notes
`Transaction.tranId`		`Purchaserequest.netsuite_transaction_id__c`	You can import transactional information –for example, the NetSuite transaction number– back into SuiteProjects Pro. To do so, add a pullback row to the field mapping definition table for the Purchase Requisition mapping group, mapping the NetSuite transaction field to a custom field associated with the purchase request record type in SuiteProjects Pro.

NetSuite Field

Direction

SuiteProjects Pro Field

Notes

Transaction.tranId

Purchaserequest.netsuite_transaction_id__c

You can import transactional information –for example, the NetSuite transaction number– back into SuiteProjects Pro. To do so, add a pullback row to the field mapping definition table for the Purchase Requisition mapping group, mapping the NetSuite transaction field to a custom field associated with the purchase request record type in SuiteProjects Pro.