Sales Foundation Implementation Guidance
Purpose
Provides CX Sales implementation guidance for the Sales Foundation functional area.
When to Use
Use this functional-area skill after Sales scope is confirmed and the project needs sales foundation setup planning, baseline export, import sequencing, or validation checkpoints.
Catalog Metadata
- Pillar:
CX
- Offering:
Sales (ORA_MIDSIZE_SALES)
- Functional area / Setup Object:
Sales Foundation (ORA_ZBS_SALES_FOUNDATION)
Setup Tasks
- Manage Activity Type and Subtype (
ORA_ZMM_MANAGE_ACTIVITY_TYPE_SUBTYPE)
- Manage Activity Profile Options (
ORA_ZMM_MANAGE_ACTIVITY_PROFILE_OPTIONS)
- Manage Sales Note Type (
ZBS_MANAGE_SALES_NOTE_TYPE)
- Manage Sales Note Type Mapping (
ZBS_MANAGE_SALES_NOTE_TYPE_MAPPING)
- Manage Activity Standard Lookups (
ORA_ZMM_MANAGE_ACTIVITY_LOOKUPS)
- Configure Adaptive Search (
ORA_CONFIGURE_ELASTIC_SEARCHES)
- Manage Audit Policies (
FND_MANAGE_AUDIT_POLICIES)
Inputs
implementation_objective
project_context
sales_foundation_scope
sales_foundation_requirements
Outputs
functional_area_setup_plan
configuration_guidance
validation_checkpoints
skill_run_record
token_usage_record
Implementation Notes
Use the generated nested setup-task skills for task-level planning, sequencing, setup-data routing, and validation. Track token usage for any generated project artifact or skill-run record using the manifest policy.
Execution Route Selection
Select an execution route from the requester’s explicit instruction; do not infer a browser-driven UI action from a create or update request.
- For
Manage Activity Profile Options, route Inventory and Review through its export-reconciliation plus Apps Common read contract, and route every configured-value Create, Update, Delete, Set, Remove, or BulkSet through core.fusion-api.apps-common. The task's FSM/CSV catalog flags do not authorize a profile-value mutation package.
- For
Manage Activity Standard Lookups, route Review through exact Apps Common reads and route lookup-code Create, Update, Deactivate, or safe Delete through core.fusion-api.apps-common. The task's FSM/CSV catalog flags do not make Data Loader the default lookup-code CRUD route; use its package workflow only for an explicit Export, Import, or supported translation request.
- For
Manage Audit Policies, route Account, Contact, Household, and their live-resolved child-object audit checks or approved mutations through manage-audit-policies/SKILL.md, which delegates all Fusion operations to core.fusion-api.audit-setup. Do not substitute the task's wider FSM/CSV route for these audit-policy operations.
- For other tasks, an explicit CSV, FSM, Data Loader, import, or bulk-maintenance request uses the task-specific current package and routes through
shared.setup-export.task-level-export, both shared validators, and core.data-loader.
- For other tasks, an explicit manual or guided-UI request uses the documented setup-task procedure. Browser control is not an alternate import adapter and must not replace the selected Data Loader route.
- If a requested mutation for another task does not name a route, prepare the validated plan and request a route selection before attempting a live action.
Manage Sales Note Type (ZBS_MANAGE_SALES_NOTE_TYPE) uses FSM as its Data Loader import mode.
1---2skill_id: "cx.sales.sales-foundation"3name: sales-foundation-implementation-guidance4description: "Provides CX Sales implementation guidance for the Sales Foundation functional area."5layer: "pillar"6pillar: "CX"7offering: "Sales"8functional_area: "Sales Foundation"9functional_area_code: "ORA_ZBS_SALES_FOUNDATION"10type: "planning"11execution_mode: "assisted"12owner_team: "CX sales pillar team"13version: "0.1.0"14inputs:15 - "implementation_objective"16 - "project_context"17 - "sales_foundation_scope"18 - "sales_foundation_requirements"19outputs:20 - "functional_area_setup_plan"21 - "configuration_guidance"22 - "validation_checkpoints"23 - "skill_run_record"24 - "token_usage_record"25depends_on:26 - "shared.implementation-planning.offering-task-map-builder"27 - "shared.implementation-planning.task-dependency-resolver"28 - "shared.setup-export.functional-area-export"29uses_core:30 - "core.project-mgmt.artifact-version-manager"31 - "core.project-mgmt.artifact-registry-manager"32 - "core.project-mgmt.project-state-manager"33 - "core.diagnostics.role-access-check"34persists_project_state: true35token_usage_tracking:36 enabled: true37 granularity: "per_skill_run"38 artifact_type: "token_usage_record"39 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"40 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"41 required_fields:42 - "activity_start_time"43 - "skill_id"44 - "task"45 - "trigger"46 - "artifacts_written"47 - "files_read"48 - "estimated_input_tokens"49 - "estimated_output_tokens"50 - "estimated_total_tokens"51 - "estimation_method"52 - "notes"53state_updates:54 - "setup_task_sequence"55 - "design_decisions"56 - "configuration_blueprints"57 - "validation_results"58 - "token_usage_records"59workspace_outputs:60 - artifact_type: "setup_task_sequence"61 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-foundation/current/"62 versioning_policy: "major-new-version-minor-confirm-update"63 - artifact_type: "configuration_blueprint"64 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-foundation/current/"65 versioning_policy: "major-new-version-minor-confirm-update"66 - artifact_type: "design_decision"67 default_location: "project/{project_id}/decisions/"68 versioning_policy: "append-only"69 - artifact_type: "validation_result"70 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-foundation/current/"71 versioning_policy: "major-new-version-minor-confirm-update"72 - artifact_type: "skill_run"73 default_location: "project/{project_id}/state/runs/"74 versioning_policy: "append-only"75 - artifact_type: "token_usage_record"76 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"77 versioning_policy: "append-only"78required_setup_tasks:79 - "ORA_ZMM_MANAGE_ACTIVITY_TYPE_SUBTYPE"80 - "ORA_ZMM_MANAGE_ACTIVITY_PROFILE_OPTIONS"81 - "ZBS_MANAGE_SALES_NOTE_TYPE"82 - "ZBS_MANAGE_SALES_NOTE_TYPE_MAPPING"83 - "ORA_ZMM_MANAGE_ACTIVITY_LOOKUPS"84 - "ORA_CONFIGURE_ELASTIC_SEARCHES"85 - "FND_MANAGE_AUDIT_POLICIES"86applicability:87 industries:88 - "All"89 countries:90 - "All"91 fusion_releases:92 - "Current Oracle Fusion Cloud release"93side_effects: []94required_privileges: []95metadata:96 source: https://skillmd.com/skills/oracle/sales-foundation-implementation-guidance97---9899# Sales Foundation Implementation Guidance100101## Purpose102103Provides CX Sales implementation guidance for the Sales Foundation functional area.104105## When to Use106107Use this functional-area skill after Sales scope is confirmed and the project needs sales foundation setup planning, baseline export, import sequencing, or validation checkpoints.108109## Catalog Metadata110111- Pillar: `CX`112- Offering: `Sales` (`ORA_MIDSIZE_SALES`)113- Functional area / Setup Object: `Sales Foundation` (`ORA_ZBS_SALES_FOUNDATION`)114115## Setup Tasks1161171. [Manage Activity Type and Subtype](manage-activity-type-and-subtype/SKILL.md) (`ORA_ZMM_MANAGE_ACTIVITY_TYPE_SUBTYPE`)1182. [Manage Activity Profile Options](manage-activity-profile-options/SKILL.md) (`ORA_ZMM_MANAGE_ACTIVITY_PROFILE_OPTIONS`)1193. [Manage Sales Note Type](manage-sales-note-type/SKILL.md) (`ZBS_MANAGE_SALES_NOTE_TYPE`)1204. [Manage Sales Note Type Mapping](manage-sales-note-type-mapping/SKILL.md) (`ZBS_MANAGE_SALES_NOTE_TYPE_MAPPING`)1215. [Manage Activity Standard Lookups](manage-activity-standard-lookups/SKILL.md) (`ORA_ZMM_MANAGE_ACTIVITY_LOOKUPS`)1226. [Configure Adaptive Search](configure-adaptive-search/SKILL.md) (`ORA_CONFIGURE_ELASTIC_SEARCHES`)1237. [Manage Audit Policies](manage-audit-policies/SKILL.md) (`FND_MANAGE_AUDIT_POLICIES`)124125## Inputs126127- `implementation_objective`128- `project_context`129- `sales_foundation_scope`130- `sales_foundation_requirements`131132## Outputs133134- `functional_area_setup_plan`135- `configuration_guidance`136- `validation_checkpoints`137- `skill_run_record`138- `token_usage_record`139140## Implementation Notes141142Use the generated nested setup-task skills for task-level planning, sequencing, setup-data routing, and validation. Track token usage for any generated project artifact or skill-run record using the manifest policy.143144## Execution Route Selection145146Select an execution route from the requester’s explicit instruction; do not infer a browser-driven UI action from a create or update request.147148- For `Manage Activity Profile Options`, route Inventory and Review through its export-reconciliation plus Apps Common read contract, and route every configured-value Create, Update, Delete, Set, Remove, or BulkSet through `core.fusion-api.apps-common`. The task's FSM/CSV catalog flags do not authorize a profile-value mutation package.149- For `Manage Activity Standard Lookups`, route Review through exact Apps Common reads and route lookup-code Create, Update, Deactivate, or safe Delete through `core.fusion-api.apps-common`. The task's FSM/CSV catalog flags do not make Data Loader the default lookup-code CRUD route; use its package workflow only for an explicit Export, Import, or supported translation request.150- For `Manage Audit Policies`, route Account, Contact, Household, and their live-resolved child-object audit checks or approved mutations through `manage-audit-policies/SKILL.md`, which delegates all Fusion operations to `core.fusion-api.audit-setup`. Do not substitute the task's wider FSM/CSV route for these audit-policy operations.151- For other tasks, an explicit CSV, FSM, Data Loader, import, or bulk-maintenance request uses the task-specific current package and routes through `shared.setup-export.task-level-export`, both shared validators, and `core.data-loader`.152- For other tasks, an explicit manual or guided-UI request uses the documented setup-task procedure. Browser control is not an alternate import adapter and must not replace the selected Data Loader route.153- If a requested mutation for another task does not name a route, prepare the validated plan and request a route selection before attempting a live action.154- `Manage Sales Note Type` (`ZBS_MANAGE_SALES_NOTE_TYPE`) uses FSM as its Data Loader import mode.