Oracle EBS R12實用配置檔案列表
Profile Options in Oracle Application Object Library
This section lists each profile option in Oracle Application Object Library. These profile options are grouped into categories based on their functional area and are available to every product in Oracle Applications. For each profile option, we give a brief overview of how Oracle Application Object Library uses the profile’s setting.
Unless otherwise noted, a profile option uses the Security hierarchy type.
A table is provided for most profile options that lists the access levels for the profile option (at which levels the system administrator can set the profile option). For Security profile options, there are four possible levels at which system administrators can view and update a profile option value: site, application, responsibility, and user. This table lists whether the profile option’s value is visible at each of these levels, and whether it is updatable at each level.
Concurrent Processing Execution
The internal name for this profile category is FND_CP_EXECUTION.
Concurrent:Active Request Limit
You can limit the number of requests that may be run simultaneously by each user. or for every user at a site. If you do not specify a limit, no limit is imposed.
Users cannot see or update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | No | No |
| Responsibility | No | No |
| User | Yes | Yes |
The internal name for this profile option is CONC_REQUEST_LIMIT.
Concurrent:Attach URL
Setting this option to “Yes” causes a URL to be attached to request completion notifications. When a user submits a request, and specifies people to be notified in the Defining Completion Options region, everyone specified is sent a notification when the request completes. If this profile option is set to Yes, a URL is appended to the notification that enables them to view the request results online.
Only the System Administrator can update this profile option.
Users can see but not update this profile option.
This profile options is visible at all levels but can only updated at the Site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_ATTACH_URL.
Concurrent:Conflicts Domain
Specify a conflict domain for your data. A conflict domain identifies the data where two incompatible programs cannot run simultaneously.
Users can see but not update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_CD_ID.
Concurrent:Collect Request Statistics
Set this profile option to “Yes” to have statistics for your runtime concurrent processes collected.
To review the statistics you must run the Purge Concurrent Request and/or Manager Data program to process the raw data and have it write the computed statistics to the FND_CONC_STAT_SUMMARY table. You can then retrieve your data from this table using SQL*PLUS or on a report by report basis using the Diagnostics window from the Requests window.
Users cannot see nor change this profile option.
This profile option is visible at all levels but can only be updated at the Site level.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is CONC_REQUEST_STAT.
Concurrent:Date Parameter Increment Option
Use this profile to control how date parameters are automatically incremented for concurrent requests. In the Standard Request Submission window, the user can specify if to run a request periodically. The user can then specify that the interval be based on the start date of the requests, or specify the interval using a unit of time and number of units.
If this profile is set to “Start Date” then the date parameters for a given request will be incremented according to the difference between the requested start date of the request and the requested start date of the previous request. If this profile is set to “Resubmit” any date parameters are incremented according to the current request’s date parameter and the amount of time represented by the number of units (RESUBMIT_INTERVAL) and the unit of time (RESUBMIT_INTERVAL_UNIT_CODE).
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | No |
| Responsibility | Yes | No |
| User | Yes | No |
The internal name for this profile option is CONC_DATE_INCREMENT_OPTION.
Concurrent:Hold Requests
You can automatically place your concurrent requests on hold when you submit them.
The default is “No”. The concurrent managers run your requests according to the priority and start time specified for each.
Changing this value does not affect requests you have already submitted.
“Yes” means your concurrent requests and reports are automatically placed on hold. To take requests off hold, you:
- Navigate to the Requests window to select a request
- Select the Request Control tabbed region
- Uncheck the Hold check box
Users can see and update this profile option.
This profile option is visible and updatable at all four levels.
| Level | Visible | Allow Update |
| Site | Yes | Yes |
| Application | Yes | Yes |
| Responsibility | Yes | Yes |
| User | Yes | Yes |
The internal name for this profile option is CONC_HOLD.
Concurrent:Multiple Time Zones
“Yes” sets the default value to ‘Sysdate-1’ for the ‘Schedules Start Date’ used by request submissions. Sysdate-1 ensures that you request is scheduled immediately regardless of which time zone your client session is running in. You should use this profile option when the client’s session is running in a different time zone than the concurrent manager’s session.
Users cannot see nor change this profile option.
This profile option is visible at all four levels and updatable at the Site level.
| Level | Visible | Allow Update |
| Site |
相關推薦Oracle EBS R12實用配置檔案列表Profile Options in Oracle Application Object Library This section lists each profile option in Oracle Application Object Library. T Oracle ebs“發運方法”配置技術分享 服務 mode 擴展 ans com str http .com 一、WSH_MODE_OF_TRANSPORT運輸方式的設置 10_OM_訂單管理超級用戶>設置>發運>代碼 在ebs 12.1.3，WSH_MODE_OF_TRANSPORT的訪 0045-OpenCV2.4.9下載地址及連結器配置檔案列表因為OpenCV3.0的nonfree模組官方並沒有編譯，所以有時候我們使用OpenCV2.4.9進行影象處理的開發。 OpenCV2.4.9下載連結：https://pan.baidu.com/s/1o8FsD2i 密碼：n6ak 配置方法見帖子：https://blog.csdn.net Oracle EBS R12 WIP Component Issue Return Process分享一下我老師大神的人工智慧教程！零基礎，通俗易懂！http://blog.csdn.net/jiangjunshow 也歡迎大家轉載本篇文章。分享知識，造福人民，實現我們中華民族偉大復興！ Oracle EBS R12 - 如何更改SYSADMIN的密碼SQL> select * from v$version; BANNER -------------------------------------------------------------------------------- Oracle Database 11g Enterpris SpringBoot 樣例配置檔案列表在使用spring boot開發微服務程式的過程中，經常要加入一些元件或者說工具框架，這樣的話就需要知道該框架在繼承到SpringBoot當中的時候是如何配置的，配置項是如何定義的，每次都要到網上去翻找一番，真的是頭大，所以在這裡把官方給出的一個樣例配置檔案，放在這裡方便今 Oracle EBS R12 整合ADF環境： ADF version: 11.1.1.6.0 Oracle EBS version: R12.2.3 程式的目的在於取得 EBS 登入時的使用者相關資訊。整個程式架構如下圖： ADF 的程式面:Step 01: 在 ViewController 依序建立 Jav EOS SERVER配置檔案列表通用的配置檔案有4個： eosconfig.xml: eos產品的配置檔案。在config目錄下 prconfig.xml: eos自動機註冊檔案管理的配置檔案 log4j-config.properties log4j配置檔案 在con 處理Oracle EBS R12標準功能切換職責速度慢的問題最近使用者（用EBS系統的時候）普遍反饋一個問題： 切換職責的時候，很慢，基本要5秒左右。有時候甚至要等上7秒以上。 就是下圖，在點確定之後，切換到另外一個職責，經常要5秒左右。 這個問題如何處理？ 其實是這樣子的，如果以前使用系統的時候正常，現在突 ORACLE:例項化 EM 配置檔案時出錯解決方案今日安裝oracle 出現如題錯誤，原因是防毒軟體在oracle安裝時禁止了其中的一些操作。應對本錯誤解決方法如下： 大概可理解為刪除不成功配置，重新配置EM。當然，本次配置最好在防毒軟體允許或者關閉防毒軟體的情況下操作，否則會再次失敗。 G:\Documents an Oracle EBS R12 GL_IMPORT_REFERENCES 映射col eap pin oracle imp rac pps ppi .com 非原創。 轉自出處： http://alloracleapps.com/oracle_apps/gl_import_references-columns-mapping-11i-v Oracle EBS AR 更新客戶配置檔案DECLARE l_rec_profile_t hz_customer_profile_v2pub.customer_profile_rec_type; l_rec_profile hz_customer_profile_v2pub.cust_profile_amt_rec_ Oracle EBS避免長時間不登入失效的配置檔案介紹如何避免長時間不登入重新登入 （英文環境） 1、將配置檔案ICX:Session Timeout的值設為空 2、將ICX:Limit time設定稍大些，如8小時 Profile說明： ICX:Session Timeout（中文：ICX：會話超時） This Spring配置檔案中配置資料庫連線(mysql,sqlserver,oracle)xml配置檔案中配置如下： <bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource"> <property name="driverClassName" 目錄列表,配置檔案目標拒絕訪問。目錄列表,配置檔案目標拒絕訪問。 在conf/web.xml下: Java程式碼 <servlet> <servlet-name> default </servlet-name> <servlet-class> org.apa Metalink Note 中文文件列表 - Oracle EBS Enterprise Business Suite分享一下我老師大神的人工智慧教程！零基礎，通俗易懂！http://blog.csdn.net/jiangjunshow 也歡迎大家轉載本篇文章。分享知識，造福人民，實現我們中華民族偉大復興！ 根據登錄檔讀取應用程式配置檔案，根據XML文字動態生成樹狀列表，自定義SAP GUI登入頁面技術要點 1.根據SAPGUI應用程式名動態讀取登入配置檔案的絕對路徑，如果應用程式未安裝，則提示相應訊息。 2. 根據獲取的路徑得到配置檔案的XML文字字串,其中包含所有的登入資訊，呼叫上一篇日誌解析XML的類方法，得到登入介面結構的文件例項 3.通過文件例項利用控制 myBatis 配置檔案 批量操作（增、刪、改）操作（資料庫 oracle 11g）1、更新 <update id="batchUpdate" parameterType="java.util.List"> <foreach collection="list" item="item" index="index" open=" Nginx服務配置 （四） 檔案列表顯示配置當用戶訪問的站點或者目錄沒有index指令設定預設的索引檔案(比如index.html)的時候，就會報403錯誤。當開啟了目錄列表功能後，再出現找不到index索引檔案的情況就會以列表形式展示。 配置檔案查詢 EBSselect --pro.profile_option_name, pro.user_profile_option_name, lev.level_type type, –lev.level_code, lev.level_name, prv.profile_o |