UNABLE TO CHANGE THE LOT NUMBER USING PICK RELEASE API FOR ATO
ONDEMAND: UNABLE TO CHANGE THE LOT NUMBER USING PICK RELEASE API FOR ATO
*** 02/16/06 09:51 am ***
Tar Number: SR:5059789.992
PROBLEM STATEMENT:
------------------
Unable to change the lot numbers using pick release API if it is ATO order.
By default take the lot generated after the completing of WIP job.
.
Is there an API within Inventory to change and pick a different lot number than the one that's assigned from the discrete job? Or Transact Move Orders API?
A particular sales order was created from a discrete job.
After that, the workers moved the finished goods into specific lots within
Inventory.
When performing a pick release with Autoallocate and Auto Pick Confirm set to
'No', the User goes to the Transact Move Orders screen where they can perform
allocations and change the lot number that was originally assigned by the
discrete job from the View Allocations screen.
Need to find out if there is an API within Inventory to change and pick a
different lot number than the one that's assigned from the discrete job.
Even though these actions can be performed from the Transact Move Orders
form, the requirement is to perform these tasks through an API due to the
number of occurrences that these actions take place.
.
Verified the issue and requirements during OWC with Customer where Customer
explained the process that they currently performed through the Transact Move
Orders form.
Customer wants to know whether the same process can be performed using an API
within Inventory.
查看全文BI与搜索技术融合趋势与技术问题分析
中国邮政国内给据邮件条码编码规则应用
EMS 校验规则
GET OE 销售员
更改销售订单的销售人员
UPDATE OE_ORDER_HEADERS_ALL OH SET OH.SALESREP_ID=100001140 WHERE OH.ORDER_NUMBER='60006445'
UPDATE OE_ORDER_LINES_ALL OL SET OL.SALESREP_ID=100001140 WHERE OL.HEADER_ID =18101
ship_confirm API of my test script
method 2 , exit delivery_id and change the line/orders to ship
method1: by pick realease API add a parameter:
lr_batch_rec. ship_confirm_rule_id:=1;
查看全文ship_confirm api of Oracle Example
This procedure can be used as an example on how to ship confirm a delivery
consisting of delivery details that have already been pick released and assigned
to a delivery.
Call WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes API to update the
corresponding delivery details to ship all quantities in the first delivery
detail; to back order all in the second; to stage all in the third delivery
detail.
Call WSH_FREIGHT_COSTS_PUB.Create_Update_Freight_Costs API to create freight
costs for the delivery that the details have been assigned to.
Call WSH_CONTAINER_PUB.Auto_Pack to pack the delivery lines into a container.
Call WSH_DELIVERIES_PUB.Delivery_Action API to ship confirm the delivery. 查看全文
SHIP CONFIRM API
picked ->shipped 中间的ship confirm 如何通过API实现 研究过程
查看全文订单 carrier_name 预付
Batch Pick Release 客制化完成
2.产生批次挑库请求(一个VIEW, 两个table ),过程见DEMO PICK RELEASE ,比较复杂的请求
3.批次挑库处理FORM
4. 通过API 进行结果导入 查看全文
查看订单预留信息
前几天忙得忘记了,已经找过,今天又多于找3个小时(研究ORACLE 订单FORM),真浪费时间
查看全文Demo Pick Release (模拟挑库)ver 1.0 已经完成,信息对称
通过ITEM查找 批号和所在库位
两种方法 :
mtl_onhand_quantities_detail
mtl_material_transactions
我只要找到批号相关的库位即可.
批次控制是在物料属性那里设置的。
对一个物料要么启用批次要么不启用批次。不可能一部分用批次,一部分不用批次吧
销售订单单行状态不对订单不关闭的处理
获得某个ID 默认的成本中心
前提: 采购订单信息中的默认费用账户必须设置
查看全文PO 编号产生规则
EBS :PO-setup->organization->purchasing option ->
查看全文发运行的寄销设置与 ASL 中的寄销属性不匹配
Error: Line # 1 Shipment # 1: The consigned setting on the shipment line does not match the consigned attribute on the ASL.
The shipment line must be deleted and re-entered.
行 # 1 发货 # 1: 发运行的寄销设置与 ASL 中的寄销属性不匹配
Import Standard Purchase Order (标准PO订单导入接口)BUG集合(1)
[心血原创,转载注明]
Import Standard Purchase Order (标准PO订单导入接口)BUG集合(1)
this week , I was puzzled by this PO interface program .Up to now , I find two big bugs in this program . 希望不再发现任何bug in this program .也希望不再有Import Standard Purchase Order (标准PO订单导入接口)BUG集合(2)
Oracle , 原来你的代码也这样地烂......
bug 1:Import Standard Purchase Order , Find 'REJECTED' in po_headers_interface table , But couldn't find records in PO_interface_errors
bug2:ORA-1403 ORA-6512
DECLARE*ERROR at line 1:ORA-01403: no data foundORA-06512: at line 55 查看全文
Reading notes of Integrating Oracle Order management using order import
notes of Oracle Order Management Open Interfaces, API, & Electronic Messaging Guide
Integrating Oracle Order management using order import
l prerequisites and set-up
l transaction sources
l import types
l data values and options
l validations
l order import satistic concurrent program
l request submission
l processing results
查看全文料号转换程序终于开发完成
ENG05_Update 06 Item Attributes
写了一个form , 2个package ,代码量5000左右,小程序,呵呵,但是该用的都用了,五脏俱全
通过这次开发,熟悉了以下:
1. 简单Form 二次开发(应用template 模版进行二次开发, 写常见的触发,调用自己/系统的request 等)
2. ERP接口开发能力
3. 熟练运用Cursor ,写package 等PL/SQL 编程能力,应该说是有一个大的飞跃。(写了两个package ,其中一个后台copy mtl_system_items_b 表里的数据,另外一个是并发程序,通过form 来调用,以报表的形式显示更新结果)
4. 对ERP里的form, function, menu , responsibility 设置的熟悉
5.熟练SecureCRT , FTP(form server)的上传编译form
一些代码具有可重复使用的特性,以后可重用!
尽管开发过程很艰难,压力很大,但是现在很高兴。
查看全文业务分析究竟是做什么的呢
欢迎具有技术底蕴的业务顾问过来现身说法
。。。
目前在写一个料号更新程序 ,因为以前开发经验不够,通过这次炼狱,增长了很多东西。
这个程序开始需要一个form , 用于输入1 个或多个料号和描述,放到临时表里面。 然后点击按钮,后台 copy 类似的料号属性,把这些属性放到临时表里, 再插入 mtl_system_items_interface 接口,然后再调用EBS 的import items request . 最后还要统计出用户输入更新的料号哪些成功哪些不成功。
查看全文Import items 总结
Update item :
1.1. Insert a item in Oracle EBS manual .such as : 000-00600-06
2.2.Find the segment’s info
select msi.inventory_item_id , msi.organization_id, msi.* --, msi.transaction_type
from mtl_system_items_b msi
where msi.segment1='000-00600-06'
查看全文Oracle ERP集成问题(items导入)
导入项目测试
第一步:确定常用模板
1. 创建模板 在应用层执行:库存-设置-项目-模板 可以创建模板。
2. 查找常用模板 :在 sql工具进入 APPS 用户 执行sql “ select mit.template_id, mit.template_name, mit.description from MTL_ITEM_TEMPLATES mit ” 列出模板的ID,和名称。 请确定现在我们常用的是那些模板。例如选择常用的模板:TEMPLATE_ID:149.
Resource for Import items -1
Use the item import process to import items from your legacy system or PDM system. You can import items from any source into Oracle Inventory and Oracle Engineering. When you import items through the Item Interface, you create new items in your Item Master organization or assign existing items to additional organizations. You can specify values for all the item attributes, or you can specify just a few attributes and let the remainder default or remain Null. You can also specify an item template for each item and inherit attribute values from the template. The Item Interface also lets you import revision details, including past and future revisions and effectivity dates. Validation of imported items is done using the same rules as the item definition forms, so you are insured of valid items.
查看全文mtl_system_items_interface 料号导入问题
脚本如下:
INSERT INTO mtl_system_items_interface
(inventory_item_id, segment1, organization_id,process_flag,
transaction_type, item_type, revision_qty_control_code,
must_use_approved_vendor_flag, inventory_planning_code,
planner_code, planning_make_buy_code, fixed_days_supply,
mrp_planning_code, planning_exception_set, shrinkage_rate,
preprocessing_lead_time, fixed_lead_time, attribute2,
attribute4, attribute1, postprocessing_lead_time, buyer_id, attribute15
)
VALUES (17534,'12230006B36', 117, 1, 'INSERT',
'FG', NULL, 'N',
6, 'B-1AN2K',
1, 12, 3,
NULL, NULL, 1,
3, 'F0030', 'F0030',
NULL, 0, NULL, NULL
)
--提示插入成功
接着commit;
查看全文
item 中的bom_item_type 的描述
from mfg_lookups
where looKUP_type='BOM_ITEM_TYPE'
当报表限制条件为OU =106, 111,110的时候不能选取交易类型为‘External Sales’的订单
当报表限制条件为OU =106, 111,110的时候不能选取交易类型为‘External Sales’的订单,在网上问了一下,自己也写出来了:
and (((ct.org_id=106 and ot.attribute8 <>'External Sales') or (ct.org_id=106 and ot.attribute8 is null))or (ct.org_id<>106))
and (((ct.org_id=110 and ot.attribute8 <>'External Sales') or (ct.org_id=110 and ot.attribute8 is null))or (ct.org_id<>110))
and (((ct.org_id=111 and ot.attribute8 <>'External Sales') or (ct.org_id=111 and ot.attribute8 is null))or (ct.org_id<>111))
为什么要写的这样麻烦,原因就是 ot.attribute 可能有null的值,但是这样的记录还不能丢弃!
但是同事帮我调试的时候优化了一代码:
查看全文通过订单 number 找到邮寄号码
select wda.delivery_id,ol.shipment_number , ol.unit_cost,ol.*-- delivery_id 邮寄号码 :80514
from
oe_order_headers_all oh,
oe_order_lines_all ol,
wsh_delivery_assignments wda,
wsh_delivery_details wdd
where
oh.header_id=ol.header_id
and
ol.line_id=wdd.source_line_id
and wdd.delivery_detail_id=wda.delivery_detail_id
and oh.order_number=1206400049
po line cancel 后不能退货
PO 状态的closed 代表什么啊?
比如一个 line : order qty 500 due 40 accept 460 bill 420 这样就closed 会怎么样?
更新PO行属性的时候出现错误:FRM-40654
AP 立帐的时候不能match之:app-sqlap-10655
OM 中通过发票找Order headers和lines 等相关信息
单证系统里发票和核销单的对应
查看全文
OM 资料
采购模块设置
1.
设置键弹性域
2.
设置日历,货币和帐簿
3.
设置组织
4.
设置计量单位
5.
设置物品
6.
设置人员
7.
如何使用帐户生成器
8.
定义预置文件
9.
打开库存和采购会计期
10.
定义子库存
11.
设置交叉参考类型,税名和位置关系
12.
设置审批信息
13.
设置查看代码
14.
定义标准附件
15.
定义采购选项
16.
定义采购员
17.
定义物品
18.
定义文档控制
19.
设置财务选项
20.
设置接收选项
21.
定义供应商
22.
启动"Send Notifications for Purchasing
Documents" Process
23.
设置文档建立选项(必需 with
defaults)
24.
设置审批等待时间(可选)
25.
启动工作流后台进程(可选)
26.
修改定单改变工作流选项(可选)
Error APP-PER-06697
采购设置里面有个3维匹配和4维匹配什么意思
po/receipt 的选项是不同的!
The Invoice Match Option in the purchase order Shipments window and the Match Approval Level here are independent options.
点击setup , personal , position 时候出现APP-PER-06697: position keyflex must be complied and dynumic inserts set to yes. 错误,不知道如何解决,上metalink 又上不了!!!
查看全文采购流程学习
(1)采购what,向who采购,采购的price,when采购,采购的quality
(2)采购活动,寻找供应商、收料、进料品检、拒收与发料;供应商评估、采购运输管理、采购品质管理、采购合同管理、付款条件管理、采购零组件的规则制定
(3)采购目标 查看全文
如何理解“一揽子采购协议”?
一揽子采购:与供应商就购买某物品时签订价格折扣协议,需要采购时,发放该采购协议。
查看全文三角贸易 PR 对应着 I/O
通过发票号码找PO号:
/* Formatted on 2006/05/08 16:21 (Formatter Plus v
SELECT rt.quantity, poh.segment1
FROM po_headers_all poh,
po_lines_all pol,
po_line_locations_all poll,
rcv_shipment_lines rcvl,
rcv_transactions rt
WHERE poh.po_header_id = pol.po_header_id
AND pol.po_line_id = poll.po_line_id
AND poll.line_location_id = rcvl.po_line_location_id
AND rcvl.shipment_line_id = rt.shipment_line_id
AND rt.attribute1 = '01260731'
-- rcv_transactions. attribute1 is invoice.NO
通过PO, 找点收单号:
select rsh.receipt_num
from po_headers_all poh,
rcv_shipment_headers rsh,
rcv_shipment_lines rsl,
po_lines_all pol,
po_line_locations_all poll
where
poh.segment1='20600021'
and