标签归档:EBS

Oracle EBS R12.2.6系统资产模块折旧账务未传总账问题处理

背景:

某客户在10月8号运行9月折旧后,创建会计发现请求报黄(但是能把9月的折旧数据正常传过去),于是看创建会计科目输出报表(或者看资产模块“子分类帐期间关闭例外报表”),可以发现里面有大量7月31号的数据,都是很明确的提示如下所示内容,无效期间:

原因探索:

此类问题原因很多,本人遇到过以下几种情况,以频率排序:
1、资产传总账时未正常传至GL模块(总账期间正常打开,此种情况可根据例外报表的提示处理,再次传总账即可);

2、资产传总账时未正常传至GL模块(总账期间关闭);

3、交叉验证规则导致生成账务问题(这种情况很少,一般在新机构建立时可能有)。

具体到本次问题,经过追溯,发现用户在7月31号晚上5点03分提交了运行折旧的请求,但是在请求未完成时,立即提交了创建会计科目到总账模块(默认会将资产相关账务处理传总账)。导致7月新增资产数据科目和中转科目都正常到了总账模块(用户检查时检查了中转科目为0,未再做深入核实,8月折旧也出问题,用户未察觉)。

方案1:打开7月期间正常传至7月总账模块,由于用户反馈7、8月份报表已经出具(金融行业),不同意再开7月期间。

方案2:后台修复数据至当期(9月),具体执行命令不再赘述,见以下脚本(根据自身情况限制条件)

–1、备份三个表的问题数据(具体条件根据自身问题限制)
select t.*
from xla_ae_headers t
where 1 = 1
and to_char(t.accounting_date, ‘yyyy-mm-dd’) = ‘2019-07-31’
and t.gl_transfer_status_code = ‘N’;

select *
from xla_ae_lines t
where 1 = 1
and to_char(t.accounting_date, ‘yyyy-mm-dd’) = ‘2019-07-31’
and t.ae_header_id in
(select t.ae_header_id
from xla_ae_headers t
where 1 = 1
and to_char(t.accounting_date, ‘yyyy-mm-dd’) = ‘2019-07-31’
and t.gl_transfer_status_code = ‘N’);

select *
from xla.xla_events# t
where t.event_type_code = ‘DEPRECIATION’
and to_char(t.event_date, ‘yyyy-mm-dd’) = ‘2019-07-31’
order by t.transaction_date desc;

–2、更新三张表,按顺序以免后续无法关联,更新的时候最好看一下条数是否正确
update xla_ae_lines t
set t.accounting_date = to_date(‘2019-09-30’, ‘yyyy-mm-dd’)
where 1 = 1
and to_char(t.accounting_date, ‘yyyy-mm-dd’) = ‘2019-07-31’
and t.ae_header_id in
(select t.ae_header_id
from xla_ae_headers t
where 1 = 1
AND to_char(t.accounting_date, ‘yyyy-mm-dd’) = ‘2019-07-31’
and t.gl_transfer_status_code = ‘N’);

update xla_ae_headers t
set t.accounting_date = to_date(‘2019-09-30’, ‘yyyy-mm-dd’),
t.period_name = ‘2019-09’
where 1 = 1
and to_char(t.accounting_date, ‘yyyy-mm-dd’) = ‘2019-07-31’
and t.gl_transfer_status_code = ‘N’;

update xla_events t
set t.transaction_date = to_date(‘2019-09-30’, ‘yyyy-mm-dd’),
t.event_date = to_date(‘2019-09-30’, ‘yyyy-mm-dd’),
t.event_status_code = ‘P’,
t.process_status_code = ‘P’
where t.event_type_code = ‘DEPRECIATION’
and to_char(t.event_date, ‘yyyy-mm-dd’) = ‘2019-07-31′;

扩展:

LOOKUP_TYPE LANGUAGE LOOKUP_CODE MEANING DESCRIPTION
XLA_EVENT_PROCESS_STATUS US D Draft Draft
XLA_EVENT_PROCESS_STATUS US E Error Error
XLA_EVENT_PROCESS_STATUS US I Invalid Invalid
XLA_EVENT_PROCESS_STATUS US P Processed Processed
XLA_EVENT_PROCESS_STATUS US R Related Event In Error Related Event In Error
XLA_EVENT_PROCESS_STATUS US U Unprocessed Unprocessed

LOOKUP_TYPE LANGUAGE LOOKUP_CODE MEANING DESCRIPTION
XLA_EVENT_STATUS US I Incomplete Incomplete
XLA_EVENT_STATUS US N No Action No Action
XLA_EVENT_STATUS US P Processed Processed
XLA_EVENT_STATUS US U Unprocessed Unprocessed

SELECT * FROM APPS.FND_LOOKUP_VALUES WHERE LOOKUP_TYPE =’XLA_EVENT_PROCESS_STATUS’ ;

SELECT * FROM APPS.FND_LOOKUP_VALUES WHERE LOOKUP_TYPE =’XLA_EVENT_STATUS’ ;

日期无论改到哪天都会在期间的最后一天。

Oracle S 由数据库端找到对应的前台URL地址

SELECT home_url FROM icx_parameters; 

SELECT profile_option_value  
  FROM fnd_profile_option_values  
WHERE profile_option_id=  
   (SELECT profile_option_id                              
      FROM fnd_profile_options WHERE profile_option_name = 'APPS_FRAMEWORK_AGENT')                               
   AND level_value = 0; 

Oracle EBS 取消“是否提交另一项请求”

配置文件

中文:并发:提交每个请求后显示请求摘要

英文:Concurrent: ShowRequests Summary After Each Request Submission

说明:设置为“是”以使 SRS 表单 (FNDRSRUN) 在每次提交新请求时显示当前提交请求的摘要。

使用场景:

    在使用EBS提交请求后,总要弹出“是否提交另一项请求”的提示,而我们往往选择“否”,这个提示就显得多余。  

    为了减轻这“多一步”的负担,取消“是否提交另一项请求”的提示,设置方法如下:默认:否(No),修改为是(Yes),可以在User Level上修改。

Oracle EBS R12启用HTTPS安全链接(SSL)

        E-Business Suite R12.1.1 provides Advanced Configuration wizards that make it easier to deploy features such as SSL and load-balancing.  Apps administrators can use these wizards to make configuration changes online through Oracle Applications Manager (OAM) and then run AutoConfig on the applications tier to make the changes effective.

       SSL (Secure Sockets Layer) is one of the most commonly used configurations in EBS. I'll walk through the SSL Advanced Configuration Wizard in this article.

Accessing the Advanced Configuration Wizards

Launch the Oracle Applications Manager Site Map using the System Administrator responsibility, then select the AutoConfig link from the Administration tab.

 

Click on Launch Wizards. It brings up the launch pad for five wizards:

  1. Forms Socket Mode
  2. SSL
  3. SSL Accelerator
  4. HTTP Load Balancing 
  5. OC4J Load Balancing

Start the SSL Configuration Wizard

The OAM General Collection Service must be activated before running any configuration wizards.  From the Administration tab of the Site Map, click on the 'Generic Services' link under the Application Services. Select 'OAM Generic Collect Services' and start it for the target instance. OAM submits a concurrent request for the same. Click on Verify to see if the service starts up fine. Once the service starts, you are ready to use the wizard.

From the Configuration Wizards launch pad, click on the 'Enable' button for SSL.

Select Nodes to be SSL-Enabled

Select the nodes on which you would like to enable SSL and click 'Next.'

2. Set Context variables for SSL

Notice the tip at the bottom of the Parameters screen:  you should make sure that your digital certificates are properly imported into the Wallet of your EBS instance. For details about importing SSL certificates, see:

 

The wizard sets the following context variables to 'https': 

  • URL protocol
  • Local URL protocol

It also sets values for the 'Web SSL directory' and the 'Active HTTP SSL port.' The subsequent screen gives the current and new values for these variables.

3. Validation

The wizard validates all settings when you click 'Next' after the user comparison of context values screen.  It checks that the Wallet and the required directory structures exist.

Make sure that the Status is 'Success.' Check the log file in the 'View' link for any errors.

4. Confirmation Page

Clicking 'Next' will take you to the Confirmation Page in the train cart. Click on the link below to check the confirmation page.

5. Submit the changes and run AutoConfig

Clicking the 'Submit' button on the Confirmation page displays the next action to be taken. You can review the context file on the applications tier for the changes that have been made. 

The next step is to run AutoConfig to propagate the changes. You need to restart all application services to make the changes effective.

Once the service have been restarted, the EBS instance is ready to be used in SSL mode.

转载自:http://blog.csdn.net/sunansheng/article/details/45848783

Oracle的单点登录解决方案(Single Sign-On Solution)

        Single Sign-On(SSO)即单点登录,在多个应用系统中,用户只需要登录一次就可以访问所有相互信任的应用系统。在此条件下,管理员无需修改或干涉用户登录就能方便的实施希望得到的安全控制。

        Oracle现有两套单点登录的解决方案:Oracle Access Manager,Oracle Single Sign-On Server (OSSO)。
Oracle官方推荐Access Manager作为SSO的解决方案,Oracle Single Sign-On Server的高级用户最终也会建议迁移到Oracle Access Manager解决方案上。

(来源:Note 1461465.2 – Information Center: Overview EBS Technology Stack OID and SSO and OAM)

OAM SSO实现方式有两种:一种是通过OAM Agent(WebGate),另外一种是使用OSSO Agents(mod_osso)

1.) 使用OAM Agent(WebGate代理),然后和Oracle E-Business Suite Access Gate集成(此处以EBS为例).

WebGate是Web服务器的一个插件,用于拦截HTTP请求,并把请求导向Oracle Access Manager (OAM)来获取用户认证。

OAM SSO登陆的过程描述:

When a user tries to access a protected application, the request is received by OAM which checks for the existence of the SSO cookie.

After authenticating the user and setting up the user context and token, OAM sets the SSO cookie and encrypts the cookie with the SSO Server key (which can be decrypted only by the SSO Engine).

Depending on the actions (responses in OAM 11g) specified for authentication success and authentication failure, the user may be redirected to a specific URL, or user information might be passed on to other applications through a header variable or a cookie value.

Based on the authorization policy and results of the check, the user is allowed or denied access to the requested content. If the user is denied access, she is redirected to another URL (specified by the administrator in Webgate registration).

可以看到,Oracle OAM通过Cookie存储用户的信息,进而通过Cookie来实现单点访问授信站点。

2.) 使用mod_osso代理,这种方法只适用于从Oracle Single Sign-On Server 10gR3升级上来的用户。

详细见:About SSO Log In Processing with OAM Agents中的“About SSO Login Log In Processing with OSSO Agents (mod_osso)”

关于Cookie

Cookies就是服务器暂存放在你的电脑里的资料( 用户ID,密码、浏览过的网页、停留的时间等信息),好让服务器用来辨认你的计算机。 当你在浏览网站的时候,Web服务器会先送一小小资料放在你的计算机上,Cookies 会帮你在网站上一些内容都记录下来。当下次你再访问同一个网站,Web服务器会先看看有没有它上次留下的Cookies资料,有的话,就会 依据Cookie里的内容来判断使用者,送出特定的网页内容给你。 一般来说,Cookie通过HTTP Headers从服务器端返回到浏览器上。IE Cookies 文件夹路径保存于注册表:HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Cookies

See Also:

Oracle LDAP解决方案 – Oracle Identity and Access Management Suite :http://blog.csdn.net/pan_tian/article/details/20927733

About SSO Log In Processing with OAM Agents

Overview of Single Sign-On Integration Options for Oracle E-Business Suite [ID 1388152.1]
Integrating Oracle E-Business Suite Release 11i with Oracle Access Manager 11gR2 (11.1.2) using Oracle E-Business Suite AccessGate [ID 1536941.1]

Oracle Access Manager 11.1.2 Certified with E-Business Suite 12 

Oracle Access Manager 11.1.2 Certified With E-Business Suite 11i
Introduction to Installing WebGates

转载自:http://blog.csdn.net/pan_tian/article/details/8691726