Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Oracle may provide sample code in SuiteAnswers, the Help Center, User Guides, or elsewhere through
help links. All such sample code is provided "as is” and “as available”, for use only with an authorized
NetSuite Service account, and is made available as a SuiteCloud Technology subject to the SuiteCloud
Terms of Service at www.netsuite.com/tos.
Oracle may modify or remove sample code at any time without notice.
As the Service is a multi-tenant service offering on shared databases, Customer may not use the
Service in excess of limits or thresholds that Oracle considers commercially reasonable for the Service.
If Oracle reasonably concludes that a Customer’s use is excessive and/or will cause immediate or
ongoing performance issues for one or more of Oracle’s other customers, Oracle may slow down or
throttle Customer’s excess use until such time that Customer’s use stays within reasonable limits. If
Customer’s particular usage pattern requires a higher limit or threshold, then the Customer should
procure a subscription to the Service that accommodates a higher limit and/or threshold that more
effectively aligns with the Customer’s actual usage pattern.
Beta Features
Oracle may make available to Customer certain features that are labeled “beta” that are not yet
generally available. To use such features, Customer acknowledges and agrees that such beta features
are subject to the terms and conditions accepted by Customer upon activation of the feature, or in the
absence of such terms, subject to the limitations for the feature described in the User Guide and as
follows: The beta feature is a prototype or beta version only and is not error or bug free and Customer
agrees that it will use the beta feature carefully and will not use it in any way which might result in
any loss, corruption or unauthorized access of or to its or any third party’s property or information.
Customer must promptly report to Oracle any defects, errors or other problems in beta features
to support@netsuite.com or other designated contact for the specific beta feature. Oracle cannot
guarantee the continued availability of such beta features and may substantially modify or cease
providing such beta features without entitling Customer to any refund, credit, or other compensation.
Oracle makes no representations or warranties regarding functionality or use of beta features and
Oracle shall have no liability for any lost data, incomplete data, re-run time, inaccurate input, work
delay, lost profits or adverse effect on the performance of the Service resulting from the use of beta
features. Oracle’s standard service levels, warranties and related commitments regarding the Service
shall not apply to beta features and they may not be fully supported by Oracle’s customer support.
These limitations and exclusions shall apply until the date that Oracle at its sole option makes a beta
feature generally available to its customers and partners as part of the Service without a “beta” label.
Oracle may make available to Customer certain features designed to interoperate with third party
applications. To use such features, Customer may be required to obtain access to such third party
applications from their providers, and may be required to grant Oracle access to Customer’s account(s)
on such third party applications. Oracle cannot guarantee the continued availability of such Service
features or integration, and may cease providing them without entitling Customer to any refund, credit,
or other compensation, if for example and without limitation, the provider of a third party application
ceases to make such third party application generally available or available for interoperation with the
corresponding Service features or integration in a manner acceptable to Oracle.
Copyright
This document is the property of Oracle, and may not be reproduced in whole or in part without prior
written approval of Oracle. For Oracle trademark and service mark information for the Service, see
www.netsuite.com/portal/company/trademark.shtml.
Table of Contents
Oracle-NetSuite PBCS Sync ..................................................................................................... 1
Overview .......................................................................................................................... 1
Oracle-NetSuite PBCS Sync Administrator Guide .................................................................... 1
Prerequisites for Installing the Oracle-NetSuite PBCS Sync SuiteApp ..................................... 1
Installing the Oracle-NetSuite PBCS Sync SuiteApp ............................................................. 2
Setting Up Oracle-NetSuite PBCS Sync .............................................................................. 2
Setting Up Token-Based Authentication (TBA) .................................................................... 3
Creating Custom Saved Searches for PBCS ........................................................................ 4
Oracle-NetSuite PBCS Sync User Guide ................................................................................. 4
Oracle-NetSuite PBCS Sync RESTlets ................................................................................. 4
Error Codes and Messages ............................................................................................. 8
Oracle-NetSuite PBCS Sync 1
Overview
The Oracle-NetSuite PBCS Sync SuiteApp enables you to extract accounting reports from NetSuite
saved searches and use them in Oracle Planning and Budgeting Cloud Service (PBCS).
For information how to install and set up Oracle-NetSuite PBCS Sync in a NetSuite account, see Oracle-
NetSuite PBCS Sync Administrator Guide.
For information how a PBCS user can execute saved searches and extract data from NetSuite, see
Oracle-NetSuite PBCS Sync User Guide.
1. Enable the required features. See Prerequisites for Installing the Oracle-NetSuite PBCS Sync
SuiteApp.
2. Install the Oracle–NetSuite PBCS Sync SuiteApp. See Installing the Oracle-NetSuite PBCS Sync
SuiteApp.
3. Set up the Oracle-NetSuite PBCS Sync SuiteApp. This includes:
■ Setting up a password for file encryption.
■ Creating user records for PBCS users. These user records must have the PBCS Integration
role.
■ Customizing default saved searches that are created by the SuiteApp.
For more information, see Setting Up Oracle-NetSuite PBCS Sync.
4. Set up token-based authentication (TBA) for PBCS users. See Setting Up Token-Based
Authentication (TBA).
5. Create custom saved searches to be used by PBCS. Creating Custom Saved Searches for PBCS.
■ Custom Records
■ Server SuiteScript
■ Token-Based Authentication
■ Client SuiteScript
To enable these features, go to Setup > Company > Enable Features, and click the SuiteCloud subtab.
Important: The Oracle-NetSuite PBCS Sync SuiteApp is a shared bundle. To install this
SuiteApp, it must be provisioned in your account.
Note: The Oracle-NetSuite PBCS Sync SuiteApp is a managed SuiteApp. When improvements
or new features are added to the SuiteApp, it is automatically updated in your NetSuite account.
Set the file encryption password at Setup > Integration > PBCS File Encryption Password. This password
must have 16, 24, or 36 characters.
After installing the SuiteApp, you must update these saved searches to assign PBCS users as owners
and to add any custom segments you might need to have in these searches.
For information about custom segments, see the help topics Custom Segments and Custom Segments
in Record Searches.
To authenticate users using the OAuth protocol with RESTlets, you must set up TBA by doing the
following:
■ Enable the NetSuite Token-Based Authentication feature. See the help topic Enabling the Token-
based Authentication Feature.
■ Create an integration record representing PBCS at Setup > Integration > Manage Integrations.
On the integration record, you must check the Token-Based Authentication box. By enabling this
option, NetSuite generates the consumer key and consumer secret that represent PBCS.
For more information, see the help topic Creating an Integration Record.
■ Save the consumer key and consumer secret generated on the integration record. The consumer
key and secret show only one time. If you lose these credentials, you can regenerate new ones. For
more information, see the help topic Regenerating a Consumer Key and Secret.
■ Create a token and token secret for users who will call the RESTlets. For information, see the help
topic Managing TBA Tokens.
The token and token secret show only one time. If you lose these credentials, you must create a new
token.
Before calling these RESTlet URLs, you must dynamically generate the RESTlet domain. See Dynamically
Generating RESTlet Domains.
The following table lists RESTlets in the Oracle-NetSuite PBCS Sync SuiteApp.
The RESTlet domain is the first part of the URL. It appears as https://rest.netsuite.com, https://
rest.na1.netsuite.com, or a similar variant.
You must dynamically generate this portion of the URL. The domain for your account can change
because NetSuite hosts accounts in multiple data centers, and accounts are sometimes moved from
one data center to another.
To dynamically generate the domain, use NetSuite’s REST roles service. For more details, see the help
topics The REST roles Service and URLs for Accessing the REST roles Service.
Output Example
{
"searches": [
{
"id": "saved_search1",
"name": "My Saved Search"
},
{
"id": "saved_search2",
"name": "My Saved Search 2"
}
]
}
Response Sample
Output Example
{
"cols":[{id: "firstname", label: "First Name"},
{id: "lastname", label: "Last Name"}],
"filters":["status","age"]
}
Response Sample
{"cols":[{"id":"account","label":"Account"},{"id":"type","label":"Type"},{"id":"tranid","label"
:"Document Number"},{"id":"entity","label":"Name"},{"id":"amount","label":"Amount"},{"id":"debi
tamount","label":"Amount (Debit)"},{"id":"creditamount","label":"Amount (Credit)"},{"id":"posti
ngperiod","label":"Period"}],"filters":["postingperiod","posting","mainline","postingperiod"]}
Input Example
{
"searchid": <searchid>
"filters": [
{
"name": <filter_name>,
"value": <value>,
"operator": <operator>
},
{
"name": <filter_name>,
"value": <value>,
"operator": <operator>
}
]
}
Output Example
{
"requestid": "123",
"status": "QUEUED",
"errcode": "",
"exception": ""
}
Response Sample
{"requestid":2302,"status":"QUEUED","errcode":"","exception":""}
earch_request&requestid=2302'
Output Example
{
"status": "SUCCESS",
"files": [
305,
4472
],
"errcode": "",
"exception": ""
}
Response Sample
{"status":"SUCCESS","files":["6745"],"errcode":"","exception":""}
Output Example
Account, Type, Document Number, Name, Amount, Amount (Debit), Amount ( redit)
Sales,Sales Order,1,1 Mesto Prostejov,250.00,,250.00