Sales
Purpose
Coordinates CX Sales implementation guidance across functional areas, setup tasks, and standard implementation activities.
When to Use
Use this offering-level skill after Sales is in scope and before routing to a specific functional-area skill.
Catalog Identity
- Pillar:
CX - Pillar slug:
cx - Offering code:
ORA_MIDSIZE_SALES - Offering slug:
sales - Offering folder:
pillars/cx/sales - Offering mapping source:
knowledge/setup-task-catalog/effective/pillars-offerings-mapping.json - Setup task catalog source:
knowledge/setup-task-catalog/effective/offering-functional-area-task-catalog.json
Routing Responsibility
This skill routes control to functional-area skills created by developers under this folder. Developers should create functional-area skills with core.fusion-dev.pillar-skill-gen using the catalog-backed path pattern:
pillars/cx/sales/{functional-area-slug}/
Route any question or implementation request about Sales Orchestration, Sales Motions, Sales Plays and Content, Data Capture Rules, or Sales Orchestration Pre-requisites to Sales Orchestration. Let that functional-area skill classify the request and route task-specific questions to its nested skills; do not duplicate or bypass its task-routing rules here.
Route any question or implementation request about Sales Leads, Lead qualification templates, Sales Lead profile options or their current/configured values, or Sales Lead standard lookups to Leads. Treat phrases such as "list all Sales Lead profile options and their values", "current value", "configured value", and an exact Sales Lead profile-option code as task-routing signals, not as documentation-only questions. Let the Leads skill select the nested setup-task skill and complete its environment workflow before returning an environment-specific answer.
Route any question or implementation request about Sales Foundation, Activity profile options, Activity standard lookups, Activity types or subtypes, Sales note types, or Sales note type mappings to Sales Foundation. Let that functional-area skill select the nested setup-task skill and apply its task-specific execution route; do not duplicate or bypass its task-routing rules here.
When a requested functional area is not yet present under this offering, use the setup catalog below to identify the matching functional area and invoke core.fusion-dev.pillar-skill-gen to generate the child skill before adding functional-area-specific guidance.
Inputs
implementation_objectiveproject_contextcx_scopesales_requirements
Outputs
sales_scopefunctional_area_skill_plansales_work_productstoken_usage_record
Functional Areas From Effective Catalog
Source: knowledge/setup-task-catalog/effective/offering-functional-area-task-catalog.json
Offering code: ORA_MIDSIZE_SALES
Functional area count: 21
Setup task count: 365
ORA_SVC_COMPANY_PROFILE: Company ProfileORA_ASK_USERS_AND_SECURITY: Users and SecurityORA_ZBS_SALES_FOUNDATION: Sales FoundationORA_QSC_DEFINE_SALES_CATALOG_AND_PRODUCTS: Sales Catalog and ProductsORA_SVC_ACCOUNTS_AND_CONTACTS: Accounts and ContactsORA_MKT_CONFIGURE_SALES_CAMPAIGNS: Sales CampaignsORA_LDS_LEADS: LeadsORA_MOO_OPPORTUNITIES: OpportunitiesORA_TRT_TERRITORIES: TerritoriesZBS_FORECAST_DEPLOYED: Sales ForecastingZBS_QUOTAS_DEPLOYED: QuotasORA_ZCA_SALES_BUSINESS_PLAN: Business PlansORA_ZPM_MANAGE_PARTNERS: Partner Relationship ManagementORA_OKC_SALES_CONTRACTS: Sales ContractsORA_OSS_SUBSCRIPTIONS: SubscriptionsORA_CN_INCENTIVES: IncentivesORA_ZCA_SALES_ADAPTIVE_INTELLIGENCE: Intelligence in SalesORA_ZCA_INTEGRATIONS: IntegrationsORA_ASK_APPLICATION_EXTENSIONS: Application ExtensionsORA_DATA_QUALITY_VERIFICATION_SERVICES: Data Quality Verification ServicesCUSTOM_SALES_ORCHESTRATION: Sales Orchestration
Implementation Notes
- Keep offering-level planning, scope decisions, sequencing, and cross-functional-area handoffs in this skill.
- Put functional-area-specific implementation guidance in generated child skills under this offering folder.
- Use
core.fusion-dev.pillar-skill-genfor child functional-area skill creation so generated skills follow the repository contract. - Use
core.fusion-dev.fusionapps-resource-authoringafter child skill creation when Oracle FusionAppsora-resource/guidance is needed. - Do not create setup-task-specific skills directly under this offering folder unless the user explicitly requests nested task-level skill generation through the pillar skill generator.