AP Encountered Error while creating accounting for AP Invoice [intangible assets-1]

本文档记录了处理AP发票在线会计创建失败的问题过程。主要症状为无法为无形资产类别的AP发票创建会计条目。通过提交应付账款会计流程、应用补丁5253656和5474676以及执行特定的SQL脚本来解决数据损坏问题。

Doc ID: AG1043

Subject: PQ AP Encountered Error while creating accounting for AP Invoice [intangible assets-1]

Type: Problem

Creation Date: 08-DEC-08

Last Revision Date: 12-JAN-09

Status: Closed

Owner: Kevin

 

Symptom

PQ AP Encountered Error while creating accounting for AP Invoice [intangible assets-1], the error is APP-SQLAP-10710: Online accounting could not be created. Please submit the Payables Accounting Process instead to create accounting entries for this transaction.Refer to AG0516 AG0526

 

 

Cause

 

 

Solutions

1. [04-DEC-08] PQ AP Encountered Error while creating accounting for AP Invoice [intangible assets-1]. (Refer to AG1043_01 AG1043_02)

2. [08-DEC-08] According to the cue, Kevin submitted the request “Payables Accounting Process”, but he encountered a error. (Log file refers to AG1043_03)

3. [08-DEC-08] The error: ORA-00001: unique constraint (AP.AP_AE_HEADERS_U2) violated occurred in

AP_ACCOUNTING_MAIN_PKG.Insert_AE_HeaderAP_PREPAY_UN_EVENT_CORE_PKG.Derive_Accounting_Ent

ry<-AP_PREPAY_UN_EVENT_CORE_PKG.Execute<-AP_ACCOUNTING_MAIN_PKG.Create_Accountin

g_Entry<-AP_ACCOUNTING_ENGINE_PKG.do_accounting<-APXAEREPwith parameters (&PARAMETERS)

4. [08-DEC-08] Refer to AG0516, Kevin used the following sql statement and found out there was one record error.

·         select distinct aea.accounting_event_id
, aea.source_id
, aea.source_table
, aea.event_status_code
, aea.event_type_code
from ap_accounting_events_all aea
, ap_ae_headers_all aeh
where aeh.accounting_event_id = aea.accounting_event_id
and aea.event_status_code =
'CREATED'

5. [08-DEC-08] Kevin applied the solution on TEST server first,

·         Use tool SQL Plus to run undoatgh.sql (Refer to AG0516_04)

·         Run UndoAtgh.sql

§         Enter Org ID: 109

§         Enter option 1 for Display Selected Event Details

§         Enter option 1 for Display AP Accounting Data

§         Enter option 1 for a Single Event

§         Enter Event #: 196983

§         Undo the Events Now: Y

§         Enter N to Sweep to Currently Open Period

§         Enter N to not delete events IDs (You will only get this prompt on 11i.AP.K and above)

§         COMMIT; <<< the script does not self-commit

·         Run the request Payables Accounting Process

 

6. [08-DEC-08] End of the request Payables Accounting Process, Kevin encountered other error: ORA-01403: no data found occurred in P_PREPAY_UN_EVENT_CORE_PKG.Populate_AE_Line_Elements<-AP_PREPAY_UN_EVENT_CORE_PKG.Derive_Accounting_Entry<-AP_PREPAY_UN_EVENT_CORE_PKG.Execute<-AP_ACCOUNTING_MAIN_PKG.Create_Accounting_Entry<-AP_ACCOUNTING_ENGINE_PKG.do_accounting<-APXAEREP With parameters (&PARAMETERS) (Refer to AG1043_04)

7. [08-DEC-08] From Metalink, Note:564973.1 mentions the same symptom with our problem. (Refer to AG1043_05)

8. [08-DEC-08] Kevin asked Ren to help to apply Patch 5253656 in ERPDB (TEST Server).

9. [09-DEC-08] After applied Patch 5253656 in ERPDB, Kevin ran undoatgh.sql and the problem solved.

10. [10-DEC-08] PQ accounting confirmed that the problem was ok in ERPDB. (Refer to AG1043_06)

11. [11-DEC-08] Jack applied Patch 5253656 in ERPAPP successfully. (Refer to AG1043_07)

12. [11-DEC-08] PQ accounting found new problems those invoices [PO#14421] [0498] [532258-1] can’t be accounted. (Refer to AG1043_08 AG1043_09)

13. [12-DEC-08] For invoice [PO#14421] which can’t be accounted, because it’s held and the cause is “Insufficient funds exist for this invoice”. Kevin asked them to add budget and then try to create accounting again.

14. [16-DEC-08] Kevin found a sql script from Metalink to determine the exact cause. (Refer to AG1043_10)         Kevin ran the sql script as follow and found four records:

select invoice_id 
from ap_invoice_distributions_all aid
where aid.line_type_lookup_code = 'TAX'
and aid.accounting_event_id is null
and aid. match_status_flag = 'A'
and aid.posted_flag = 'N' 
and exists (
select 1
from ap_invoice_distributions_all d
where d.line_type_lookup_Code = 'PREPAY'
and d.invoice_id = aid.invoice_id);

Note: If this returns rows then there is a tax line without an associated event id. This indicates a data corruption that is most likely caused by following bug::
Bug 5330439 - Unaccounted Tax Distribution After Prepayment Unapplication

15. [16-DEC-08] Patch 5474676 - 1Off:5330439:FP.G:11.5.10.2: Unaccounted Tax Distribution After Prepayment
This patch includes the fix for
Bug 5330439
 
16. [19-DEC-08] After applied Patch 5474676 in ERPDB, the problem still existed.
17. [22-DEC-08] Kevin found another solution, the sql script as follows:
update ap_invoice_distributions_all aid
set aid.accrual_posted_flag='Y',
   aid.posted_flag='Y'
where aid.invoice_id=110855
and aid.org_id=109 and aid.last_update_login=6059048
 
update ap_invoice_distributions_all aid
set aid.accrual_posted_flag='Y',
    aid.posted_flag='Y'
where aid.invoice_id=118685
and aid.last_update_login=6057973 and request_id is null
 
18. [22-DEC-08] Kevin applied the solution in ERPDB and asked user to check them. (Refer to AG1043_11)
19. [06-JAN-09] Kevin applied the solution in ERPDB and asked user to check them again. (Refer to AG1043_12)
20. [06-JAN-09] PQ accounting confirmed that the problem was normal. 
21. [06-JAN-09] Kevin applied the solution in ERPAPP and PQ accounting confirmed that the problem was normal. (Refer to AG1043_13)
当遇到 `pip subprocess to install build dependencies exited with error and metadata-generation-failed` 问题时,可以尝试以下解决方案: #### 更新 pip 和 setuptools 确保 `pip` 和 `setuptools` 是最新版本,以避免兼容性问题。 ```bash pip install --upgrade pip setuptools ``` #### 检查依赖项 某些包可能依赖于系统级的库或工具。例如,编译 C 扩展时可能需要安装 `gcc` 等编译器。以 Ubuntu 为例,可以使用以下命令安装常见的编译工具: ```bash sudo apt-get install build-essential ``` 若使用 pip 安装 Python 包时出现 `subprocess-exited-with-error` 错误,且提示 `Could not find "cmake" executable!`,通常是由于系统缺少 cmake 工具或环境变量配置问题导致,需要安装 CMake。 #### 清理缓存 清除 `pip` 的缓存,有时缓存文件可能损坏,导致安装失败。 ```bash pip cache purge ``` #### 使用虚拟环境 创建一个新的虚拟环境,并在其中尝试安装包,避免全局环境中的冲突。 ```bash python -m venv myenv source myenv/bin/activate # 在 Windows 上使用 `myenv\Scripts\activate` pip install package_name ``` #### 降低 setuptools 版本 这一问题通常是由于 setuptools 版本不兼容引起的,通过降低 setuptools 版本,可以有效解决问题 [^2]。 ```bash pip install setuptools==<specific_version> ``` 将 `<specific_version>` 替换为合适的版本号。 #### 指定 Python 版本 如果系统中安装了多个 Python 版本,确保使用的是正确的版本。 ```bash python3 -m pip install package_name ``` #### 查看详细错误信息 根据详细的错误输出定位问题。例如,错误信息中可能会提示缺少某个依赖库或文件。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值