Overview
The Lyftron Provider for Oracle Sales Cloud offers the most natural way to access Oracle Sales Cloud data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing Oracle Sales Cloud data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Oracle Sales Cloud data provider and automatically build your data migration pipelines in minutes, not months.
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
Key Features
- Comprehensive Delta load mechanism.
- Real-time access to Oracle Sales Cloud.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
Prerequisites
The user must have credentials for Oracle Sales Cloud, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Establishing a Connection with Lyftron's Quickstart Steps
Create your Oracle Sales Cloud connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click Oracle Sales Cloud for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish Oracle Sales Cloud connection with Lyftron.
"HostURL=https://my.host.oraclecloud.com; Username=abc123; Password=abcdef;"Key | Value | Field |
Connection Name | Enter your connection details | Required |
HostURL | Enter HostURL | Required |
Username | Enter Username | Required |
Password | Enter Password | Required |
Logfile** | Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx | Optional |
Verbosity** | Choose verbosity 1-5 based on the severity of debugging | Optional |
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
Hurray! Now you have successfully connected with the Lyftron Oracle Sales Cloud connector and can utilize the connector to Extract, Warehouse, Analyze, Visualize and Share your data.
Data Model
The Lyftron Provider for Oracle Sales Cloud models entities in the Oracle Sales Cloud API as tables, views, and stored procedures. These are defined in schema files, which are simple, text-based configuration files.
API limitations and requirements are documented in this section; you can use the SupportEnhancedSQL feature, set by default, to circumvent most of these limitations.
Tables
The Lyftron Provider for Oracle Sales Cloud models Item Listings in tables so that they can be easily queried, updated, and deleted. You can list items on your Oracle Sales Cloud store by calling the AddItem stored procedure.
Views
Views are tables that cannot be modified. Typically, read-only data are shown as views.
Name | Type | Description |
AccountAddresses | Tables | The address resource is used to view, create, and update addresses of an account. An address represents the location information of an account. |
AccountAddressPurposes | Tables | The address purpose resource is used to view, create, or modify the address purpose. The address purpose describes the use of an address, such as shipping address or billing address. |
AccountNotes | Tables | The note resource is used to capture comments, information, or instructions for an account. |
AccountPrimaryAddresses | Tables | The primary address resource is used to view, create, and update primary address of an account. A primary address is the default communication address of an account. |
AccountRelationships | Tables | The relationship resource is used to view, create, and update account relationships. |
AccountResources | Tables | The sales team member resource represents a resource party and is assigned to a sales account team. A sales account team member has a defined access role for the sales account. |
Accounts | Tables | The sales team member resource represents a resource party and is assigned to a sales account team. A sales account team member has a defined access role for the sales account. |
Activities | Tables | Table to capture task and appointment information. |
ActivityAssignees | Tables | Table used to capture the assignees/resources associated to the activity. |
ActivityContacts | Tables | Table used to capture the contacts associated to the activity. |
ActivityNotes | Tables | Note data objects that capture comments, information or instructions for an Oracle Fusion Applications business object. |
ActivityObjectives | Tables | Table used to capture the objectives associated to the activity. |
ContactAddresses | Tables | Table that includes attributes used to store values while creating or updating an address. An address represents the location information of an account, contact or household. |
ContactAddressPurposes | Tables | The address purpose resource is used to view, create, or modify the address purpose. The address purpose describes the use of an address, such as shipping address or billing address. |
ContactNotes | Tables | The note resource is used to capture comments, information, or instructions for a contact. |
ContactPrimaryAddresses | Tables | The primary address resource is used to view, create, or modify a primary address of a contact. A primary address is the default communication address of an entity. |
ContactRelationships | Tables | The relationship resource includes attributes that are used to store values while viewing, creating, or updating a relationship. |
Contacts | Tables | Table resource items include attributes used to store values while creating or updating a contact. |
ContactSalesAccountResources | Tables | The sales team member resource represents a resource party and is assigned to a sales account team. A sales account team member has a defined access role for the sales account. |
EmployeeResourceAttachments | Tables | The contact picture attachment resource is used to view, create, and update the resource's picture.Get a resource's picture |
EmployeeResources | Tables | The resources resoure is used to view, create, and update a resource. A resource is a person within the deploying company who can be assigned work to accomplish business objectives, such as sales persons or partner members. |
Opportunities | Tables | The opportunity competitor resource is used to view, create, and update the competitors for an opportunity. The opportunity competitors is used to store information about the competitors associated with the opportunity. |
OpportunityCompetitors | Tables | The opportunity competitor resource is used to view, create, and update the competitors for an opportunity. The opportunity competitors is used to store information about the competitors associated with the opportunity. |
OpportunityContacts | Tables | The opportunity contact resource is used to view, create, and update the contacts of an opportunity.The contact associated with the opportunity. You can specify a contact's role, affinity, and influence level on an opportunity. A single contact can be marked as primary. |
OpportunityDeals | Tables | A deal associated with the opportunity. |
OpportunityLeads | Tables | The opportunity lead resource is used to view, create, and update the lead that resulted in an opportunity. |
OpportunityNotes | Tables | The note resource is used to capture comments, information, or instructions for an opportunity. |
OpportunityPartners | Tables | The opportunity partner resource is used to view, create, and update the partners associated with this opportunity.The opportunity partner is used to store information about partners who are contributing to the selling effort of the current opportunity. |
OpportunityRevenueItems | Tables | The revenue items resource is used to view, create, and update revenue items of an opportunity. The revenue items associated with opportunities are products, services, or other items a customer might be interested in purchasing. You add revenue items by selecting a product group or product to associate with an opportunity. |
OpportunityRevenueProductGroups | Tables | The product group resource is used to view, create, and update the product groups associated with an opportunity. The product group let you categorize products and services that you sell. |
OpportunityRevenueProducts | Tables | The following table describes the default response for this task. |
OpportunityRevenueTerritories | Tables | The opportunity revenue territories resource is used to view, create, and update the revenue territories of an opportunity. The territories assigned to an opportunity revenue line. The territories provide the rules for automatically assigning salespeople and other resources to customers, partners, leads, and opportunity line items. |
OpportunitySources | Tables | The opportunity source resource is used to view, create, and update the source of an opportunity.The opportunity source is used to capture the marketing or sales campaign that resulted in this opportunity. |
OpportunityTeamMembers | Tables | The opportunity team members resource is used to view, create, and update the team members associated with an opportunity. The opportunity team member of the deploying organization associated with the opportunity. |
Territories | Tables | The sales territories resource represents the list of sales territories that the logged-in user can view. A sales territory is an organizational domain with boundaries defined by attributes of customers, products, services, resources, and so on. Sales territories can be created based on multiple criteria including postal code, area code, country, vertical market, size of company, product expertise, and geographical location. Sales territories form the fundamental infrastructure of sales management as they define the jurisdiction that salespeople have over sales accounts, or the jurisdiction that channel sales managers have over partners and partner transactions. |
Advanced Settings
To view a detailed advanced settings options, go to Oracle Sales Cloud Advanced Settings. Complete list of the parameters you can configure in the connection string can be found by clicking Connection String Parameters.