Data source table information
The following information can help you with the FTP import and export data.
Data source types
Data sources are used to create an import set so that data can be processed, if necessary,
prior to being mapped onto a production table.
| Label | Name |
|---|---|
| File | Data is in a recognized file format, accessible locally or remotely through several file retrieval methods. |
| JDBC | Data is in a database, accessible using JDBC. ServiceNow Technical Support supports Oracle, MySQL, Sybase, DB2 Universal, and MS SQL Server drivers. |
| LDAP | Data is in an LDAP server, accessible through the LDAP or LDAPS ports, 389 and 636 respectively. |
| OIDC | Data is accessible via OIDC. |
| REST (IntegrationHub) | Data is in a REST API, accessible through IntegrationHub. |
| Data Stream IntegrationHub | Data is loaded from a Data Stream Action, accessible through IntegrationHub. |
| Custom (Load by Script) | Data is obtained using a custom script. |
Folder structure
See the following folder structure. You can use the
<type>.request for
taking the data and <type>.response for posting the data back to the FTP
server:catalog.request
catalog.response
invoice.request
invoice.response
orders.request
orders.response
shipment.request
shipment.responseAssociated Table Transform Map
To import data, define a data source and transform map, and schedule or run an import at some regular interval.
Table transform map is associated with the table to transform the
File Based Catalog
Import [sn_spend_ftp_intg_catalog_stage] data into Catalog Import
[sn_spend_intg_imp_catalog]. See the following table transform labels and associated
table information.| Label | Name |
|---|---|
| Invoice Import | sn_spend_intg_imp_invoice |
| Catalog Import | sn_spend_intg_imp_catalog |
| Availability Import | sn_spend_intg_imp_availability |
| Shipment Import | sn_spend_intg_imp_shipment |
| Order Acknowledgment | sn_spend_intg_imp_purchase_order_ack |
| Price Import | sn_spend_intg_imp_price |