现象,克隆之后的环境,无法创建供应商,始终报以下错误
创建供应商时,无论输什么供应商名称,都 报错:
此供应商名称已经存在。 请重新输入。 程序包 AP_VENDOR_PUB_PKG 过程 Create_Vendor 中出现错误 ORA-20001:
This Supplier Number already exists. Re-enter. ORA-20001: in Package AP_VENDOR_PUB_PKG Procedure Create_Vendor
原因是因为供应商编号在自动模式下,系统生成的下一自动编号已存在。
设置路径
解决办法:查询当前系统中的最大供应商编号,然后重新设置该值。
CAUSE
The issue is caused by the following setup:
Supplier number is automatic and next available number is less than the number exists suppliers in system.
The following bug was also having the same issue where Oracle Development advised to get the value correctly:
Bug 11693139: UNABLE TO CREATE SUPPLIERS. ORA-20001: IN PACKAGE AP_VENDOR_PUB_PKG PROCEDURE CR
The following SQL identified the invalid / incorrect data:
SELECT supplier_numbering_method, supplier_num_type, next_auto_supplier_num,
MAX(LPAD(segment1, 30, '0')) PADMAX_SUP_NUM
FROM ap_product_setup, ap_suppliers
GROUP BY supplier_numbering_method, supplier_num_type, next_auto_supplier_num;
SOLUTION
To implement the solution, please execute the following steps:
1. Please navigate to Payable System Options set up
2. Change the setup under Supplier Number for Next Available Number to one greatre than PADMAX_SUP_NUM (sql result column)
3. Save the record.
4. Now retest the issue by creating a new supplier.
参考文档
【推荐】国内首个AI IDE,深度理解中文开发场景,立即下载体验Trae
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· go语言实现终端里的倒计时
· 如何编写易于单元测试的代码
· 10年+ .NET Coder 心语,封装的思维:从隐藏、稳定开始理解其本质意义
· .NET Core 中如何实现缓存的预热?
· 从 HTTP 原因短语缺失研究 HTTP/2 和 HTTP/3 的设计差异
· 分享一个免费、快速、无限量使用的满血 DeepSeek R1 模型,支持深度思考和联网搜索!
· 基于 Docker 搭建 FRP 内网穿透开源项目(很简单哒)
· ollama系列1:轻松3步本地部署deepseek,普通电脑可用
· 按钮权限的设计及实现
· Apache Tomcat RCE漏洞复现(CVE-2025-24813)