跳至主要內容
文件
文件
Adaptive Planning
Create Custom SQL Tuple Columns

Create Custom SQL Tuple Columns

  • Data Designer
     and
    Integration Operator
     permissions in Workday Adaptive Planning.
  • Set up a Workday data source.
  • Set up a Workday external system.
If your model brings together more than one Workday Core object into a single Adaptive Planning object, you must create a combined object known as a tuple. Tuples look like:
  • Ledger Account + Spend Category.
  • Company + Cost Center.
You concatenate the objects with a defined delimiter preferably an underscore
_
 or dash
-
. Make this concatenation consistent across all of the metadata and data loaders in Adaptive Planning. Define the concatenation in the external system to enable drilling and publishing.
Drilling into metadata and publishing plans both require the WID. The WID helps construct the URL that bridges Adaptive Planning to Workday objects and journal lines.
Concatenate the WIDs into a single ID column, and the Labels into a single Name column.
Create custom tuple SQL columns for any many-to-1 mappings that require ID columns and Label columns. Example:
Company-Cost Center ID
 and
Company-Cost Center Label
.
Configure the many-to-one column mappings in your Workday external system. You can drag and drop multiple selected items that shift to the top of the list within:
  • Dimension Mapping.
  • Report parameter mapping.
  • Publish Plans account mapping.
Place them in the same order as your concatenation.
  1. Drag a
    SQL Column
     from the
    Custom Column
     folder in the
    Data components
     pane into
    Tables to Import
    .
  2. Enter a name that describes the use of the concatenated columns and select
    Text
     for data type.
    Example: Company and Cost Center.
  3. Select
    SQL Expression
     to pick the (Id) columns in
    Available Columns
     to combine them. Concatenate them using vertical pipes and a single quoted text delimiter. Example:
    "Company (Id)" || '_' || "Cost Center (Id)"
    Use the same delimiter character for all of your data sources. Underscores work well because Adaptive Planning Account Codes accept them.
  4. Repeat Steps 1-3 but for the (Label) columns. Example:
    "Company (Label)" || '_' || "Cost Center (Label)"
  5. (Optional) You can also concatenate Ledger Account ID and Spend Category as Worktag ID. Example:
    "Ledger Account (Id)" || '_' || "Spend Category as Worktag (Id)"
  6. Apply
     and
    Save
     the data source to view how the columns concatenate.
The tuple SQL columns appear in the data source and become available in Adaptive Planning Loaders.
Review your Workday external system to verify you concatenated for the same many-to-1 mappings correctly.