透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Oracle EBS 適用的 Looker Block
本頁說明如何透過 Cortex Looker Block 取得 Oracle EBS (E-Business Suite) 資料的洞察資訊。使用這個 Oracle EBS 適用的 Looker Block,您就能以快速且經濟實惠的方式,在 BigQuery 上開始製作「訂單到現金」(O2C 或 OTC) 作業報表。使用或自訂這個 Looker Block,即可:
- 找出資料中的趨勢和模式。
- 及早發現潛在問題。
- 更快做出更明智的決策。
可用的深入分析資訊
Cortex Framework 中的 Oracle EBS Looker 模塊提供下列預先定義的資訊主頁:
- 訂單狀態:訂單相關指標總覽,包括訂單量、從預訂到帳單的訂單流程狀態明細,以及訂單狀態分析。
- 銷售業績:深入瞭解銷售業績最佳的項目,包括商品、類別、顧客、業務單位和訂單來源。
- 訂單履行:追蹤一段時間內的履行成效,並醒目顯示平均訂單週期時間最長的項目,以及遇到履行問題的項目。
- 訂單明細:查看符合一組篩選條件的部分銷售訂單明細。舉例來說,您可以查看特定時間範圍內所有遭封鎖的訂單詳細資料。
- 帳單和月結單:月結單數量和金額總覽,包括每月趨勢。並醒目顯示享有最高折扣的顧客。
- 應收帳款:分析目前和逾期應收帳款,找出未付款金額最高和逾期付款時間最長的顧客。
- 月結單明細:查看符合一組篩選條件的部分月結單詳細資料。例如,查看特定時間範圍內所有未結月結單的詳細資料。
存放區
如要存取 Oracle EBS 適用的 Cortex Looker Block,請前往官方 GitHub 存放區:block-cortex-oracle-ebs。這個存放區包含必要的檢視區塊、探索和資訊主頁,可讓您將 Oracle EBS 資料順暢整合至 Looker 環境。這個存放區提供穩固的基礎,可供您建立符合特定需求的自訂報表、視覺化效果和資訊主頁。
部署作業
如需如何部署 Oracle EBS 適用的 Cortex Looker Block,請參閱「部署 Cortex Framework 適用的 Looker Block」。
完成這些指示後,請參閱下一節的「部署的其他規格」。
部署作業的其他規格
視資料來源而定,部分 Looker Blocks 需要一些規格才能正常運作。本節說明 Oracle EBS 適用的 Cortex Looker Block 特殊設定。
需要永久衍生資料表
用於這個區塊的 BigQuery 連線必須啟用永久衍生資料表。詳情請參閱「在連線上啟用 PDT」。
必要使用者屬性
部分資訊主頁需要多個 Looker 使用者屬性才能正常運作。使用者屬性可為每位 Looker 使用者提供個人化體驗。Looker 管理員會定義使用者屬性,然後將使用者屬性值套用至使用者群組或個別使用者。詳情請參閱「管理員設定 - 使用者屬性」。
針對這個 Oracle EBS 適用的 Looker Block,Looker 管理員應建立下列使用者屬性,並完全按照下列方式設定值:
必要使用者屬性名稱
|
標籤
|
資料類型
|
使用者存取權
|
隱藏值
|
預設值
|
cortex_oracle_ebs_category_set_name
|
Cortex Oracle EBS:類別集名稱
|
String
|
編輯
|
否 |
EBS 系統中使用的主要類別集名稱。如果使用 Cortex 測試資料,預設值等於 BE_INV_ITEM_CATEGORY_SET 。
詳情請參閱「測試資料」一節。
|
cortex_oracle_ebs_default_language
|
Cortex Oracle EBS:預設語言
|
String
|
編輯
|
否 |
US (或 EBS 系統中使用的主要語言代碼)。如果使用 Cortex 測試資料,可用的值為 US (英文) 和 ES (西班牙文)。詳情請參閱「測試資料」一節。 |
cortex_oracle_ebs_default_currency
|
Cortex Oracle EBS:預設目標幣別
|
String
|
編輯
|
否 |
USD 或所選貨幣,例如
EUR, CAD or JPY 。
|
cortex_oracle_ebs_use_test_data
|
Cortex Oracle EBS:使用測試資料
(Yes 或 No )
|
String
|
編輯
|
否 |
如果使用 Cortex Framework 測試資料,請輸入 Yes 。否則請輸入 No 。詳情請參閱「測試資料」一節。 |
每個資訊主頁使用者都可以按照「個人化使用者帳戶設定」一文中的操作說明,自訂可編輯的使用者屬性值。
測試資料
使用這個方塊的選用測試資料時,請注意下列重點:
其他注意事項
如要提升 Oracle EBS Looker Block 的效能和功能,請考慮下列事項:
- BI Engine 最佳化:在 BigQuery 中啟用 BI Engine 最佳化,可提升部分計算作業的效能。
- Liquid 範本語言:部分常數、檢視區塊、Explore 和資訊主頁會使用 Liquid 範本語言。詳情請參閱 Looker 的 Liquid 變數參考資料說明文件。
- 取消隱藏其他維度和指標:為簡化畫面,許多維度和指標都會隱藏。如果發現缺少任何有價值的項目,請在相關檢視畫面中,將欄位的
hidden
參數值設為 No
。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-09-04 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThe Cortex Looker Block for Oracle EBS provides pre-built dashboards for Order-to-Cash (O2C) operational reporting on BigQuery, enabling rapid and cost-effective insights into order status, sales performance, order fulfillment, billing, and accounts receivables.\u003c/p\u003e\n"],["\u003cp\u003eThe Looker Block offers predefined dashboards such as order status, sales performance, billing and invoicing, and account receivables, which are available within the Cortex Framework, that can be used immediately or customized for your needs.\u003c/p\u003e\n"],["\u003cp\u003eDeployment of the Looker Block requires enabling Persistent Derived Tables in the BigQuery connection and configuring specific user attributes like category set name, default language, and currency, along with an option for using test data.\u003c/p\u003e\n"],["\u003cp\u003eThe block is accessible via a GitHub repository, which includes essential views, Explores, and dashboards for integrating Oracle EBS data into Looker, and it also offers customization options for reports and dashboards.\u003c/p\u003e\n"],["\u003cp\u003eThe optional test data available has a defined timeframe, uses a specific date for calculations, and includes limited options for category sets, business units, as well as a predefined set of supported languages and currencies.\u003c/p\u003e\n"]]],[],null,["# Looker Block for Oracle EBS\n===========================\n\nThis page describes the insights you can get from the Cortex Looker\nBlock for Oracle EBS (E-Business Suite) data. Using this Looker Block\nfor Oracle EBS, you can jumpstart your Order-to-Cash (O2C or OTC) operational\nreports journey on BigQuery in a rapid and cost-effective manner.\nUse or customize this Looker Block to:\n\n- Identify trends and patterns in your data.\n- Spot potential problems early on.\n- Make better decisions faster.\n\nAvailable insights\n------------------\n\nThe Looker Block for Oracle EBS in Cortex Framework\noffers the following predefined dashboards:\n\n- **Order status**: Overview of order-related metrics, including order volume, a breakdown of the order flow status from booking to billing, and an analysis of order status.\n- **Sales performance**: Insights into top sales performers including items, categories, customers, business units, and order sources.\n- **Order fulfillment**: Tracks fulfillment performance over time, highlighting items with the longest average order cycle time and those experiencing fulfillment challenges.\n- **Order line details**: View details of a subset of sales orders satisfying a set of filter criteria. For example, see details of all blocked orders in a given timeframe.\n- **Billing and invoicing**: Overview of invoice volume and amounts including monthly trends. Also highlights customers with highest discounts.\n- **Accounts receivables**: Analyzes current and overdue receivables, identifying customers with highest outstanding amounts and duration of overdue payments.\n- **Invoice line details**: View details of a subset of invoices satisfying a set of filter criteria. For example, see details of all open invoices in a given timeframe.\n\nRepository\n----------\n\nTo access the Cortex Looker Block for Oracle EBS, visit its official\nGitHub repository: [**block-cortex-oracle-ebs**](https://github.com/looker-open-source/block-cortex-oracle-ebs).\nThis repository contains essential views, Explores, and dashboards that enable\nyou to seamlessly integrate Oracle EBS data into your Looker\nenvironment. This repository provides a solid foundation for creating custom\nreports, visualizations, and dashboards tailored to your specific needs.\n\nDeployment\n----------\n\nFor instructions about how to deploy the Cortex Looker Block for\nOracle EBS, see\n[Deploy Looker Blocks for Cortex Framework](/cortex/docs/looker-block-deployment).\n\nAfter completing these instructions, see\n[Additional specifications for deployment](/cortex/docs/looker-block-sap#additional_specifications_for_deployment)\nin the following section.\n\nAdditional specifications for deployment\n----------------------------------------\n\nDepending the data source, some Looker Blocks need some\nspecifications to work properly. This section describes special settings\nfor the Cortex Looker Block for Oracle EBS.\n\n### Persistent Derived Tables required\n\nThe BigQuery connection used for this block must have\n[Persistent Derived Tables](/looker/docs/derived-tables#persistent_derived_tables)\nenabled. For more information, see\n[Enabling PDTs on a Connection](/looker/docs/db-config-google-bigquery#creating_a_temporary_dataset_for_persistent_derived_tables).\n\n### Required user attributes\n\nSome dashboards require several Looker\n[user attributes](/looker/docs/admin-panel-users-user-attributes)\nto work properly. User attributes provide a customized experience for each\nLooker user. A Looker administrator defines a\nuser attribute and then applies a user attribute value to a user group or\nto individual users. For more information, see [Admin settings - User attributes](/looker/docs/admin-panel-users-user-attributes).\n\nFor this Looker Block for Oracle EBS, a Looker Admin\nshould create the following user attributes and\nset the values **exactly** as follows:\n\nEach dashboard user can personalize the values of the editable user attributes\nby following the instructions in [Personalizing user account settings](/looker/docs/user-account).\n\n### Test data\n\nWhen utilizing the **optional** Test data with this block, consider the\nfollowing key points:\n\n- **Timeframe**: The test data covers Sales Orders from January 1, 2021 to April 4, 2024 and Invoices \\& Payments from January 2, 2021 to March 31, 2024.\n- **Date Adjustment** : When using test data (user attribute `cortex_oracle_ebs_use_test_data` is set to `Yes`), the current date is replaced with March 31, 2024 for calculations. This ensures accurate calculations for dimensions like age of receivables.\n- **Category Set** : The only available `Category Set ID`/`Category Set Name` is `1100000425`/`BE_INV_ITEM_CATEGORY_SET`. The user attribute `cortex_oracle_ebs_category_set_name` should be set to `BE_INV_ITEM_CATEGORY_SET`.\n- **Business Unit** : Test data includes only one Business Unit named `BE1 operating unit`.\n- **Tax amount**: In Sales Invoices and Sales Invoices Daily Agg, the tax amount is 0 for all records.\n- **Intercompany** : For all records `Is_Intercompany` is set to `No`.\n- **Multiple languages and currencies** : To demonstrate different languages and\n currencies in the test data, during the [deployment of the Cortex Framework](/cortex/docs/deployment-step-five)\n for Oracle EBS, include `USD` and `EUR` as currency conversion targets, and\n `US` and `ES` as languages. The following is a sample snippet from the\n `config.json` file used in a deployment:\n\n \"OracleEBS\": {\n \"itemCategorySetIds\": [1100000425],\n \"currencyConversionType\": \"Corporate\",\n \"currencyConversionTargets\": [\"USD\",\"EUR\"],\n \"languages\": [\"US\",\"ES\"],\n \"datasets\": {\n \"cdc\": \"CORTEX_ORACLE_EBS_CDC\",\n \"reporting\": \"CORTEX_ORACLE_EBS_REPORTING\"\n }\n }\n\n### Other Considerations\n\nFor optimizing the performance and functionality of your\nLooker Block for Oracle EBS consider the following:\n\n- **BI Engine Optimization:** Some calculations perform better with [BI Engine Optimization](/bigquery/docs/bi-engine-query) enabled in BigQuery.\n- **Liquid Templating Language** : Some constants, views, Explores and dashboards use liquid templating language. For more information, see Looker's [Liquid Variable Reference](/looker/docs/liquid-variable-reference) documentation.\n- **Unhide additional dimensions and measures** : Many dimensions and measures are hidden for simplicity. If you find anything valuable missing, set field's `hidden` parameter value to `No` in the relevant views."]]