...
Table of Contents
| Table of Contents | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Overview
There could be instances where the default saved searches used by the JPK file structures as sources of information do not fully meet company-specific requirements. For example, you may want to use certain fields instead of the default source field or include other transaction types that are not originally supported. In these scenarios, the Poland Localization SuiteApp is flexible enough to allow customized saved searches. These searches can be tailored to your business use case and assigned to the Poland Localization Settings as a source of information.
General Saved Search Guidelines
It is always a best practice to create a copy of the default saved searches provided in the SuiteApp and then save it as a separate search. Afterward, an administrator can make the necessary changes to the search depending on the business's needs.
In the Poland Localization Settings record for the subsidiary, different saved searches may be assigned as the JPK reports data source.
The user can change the fields used in the saved search columns to align with their business process (e.g., change the source of the customer tax number being reported from the native NetSuite VAT registration number field to a custom field developed for their business process).
The saved search column labels and summary labels are used as the basis for correctly generating the JPK reports. Do NOT change these when making copies of the saved searches.
Applying User-Defined Saved Searches
JPK_V7 File Structure
To select a different saved search source for JPK_V7:
...