create_item

  1. inv_item_grp.create_item(p_commit => fnd_api.g_true, --
  2. p_item_rec => l_item_rec,
  3. x_item_rec => x_item_rec,
  4. x_return_status => x_return_status,
  5. x_error_tbl => l_error_tbl,
  6. p_template_id => l_record.template_id);

update_item

  1. inv_item_grp.update_item(p_commit => fnd_api.g_true,
  2. p_item_rec => l_item_rec,
  3. x_item_rec => x_item_rec,
  4. x_return_status => x_return_status,
  5. x_error_tbl => l_error_tbl,
  6. p_template_id => l_record.template_id);

默认接收子库存

  1. inv_item_sub_default_pkg.insert_upd_item_sub_defaults(x_return_status => x_return_status,
  2. x_msg_count => x_msg_count,
  3. x_msg_data => x_msg_data,
  4. p_organization_id => x_item_rec.organization_id,
  5. p_inventory_item_id => x_item_rec.inventory_item_id,
  6. p_subinventory_code => l_record.default_receiving_subinv,
  7. p_default_type => '2',
  8. p_creation_date => SYSDATE,
  9. p_created_by => fnd_global.user_id,
  10. p_last_update_date => SYSDATE,
  11. p_last_updated_by => fnd_global.user_id,
  12. p_process_code => l_process_code,
  13. p_commit => fnd_api.g_true);

CREATE item INV CATEGORY

  1. inv_item_category_pub.create_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_category_id => l_record.inv_category_id,
  9. p_category_set_id => 1,
  10. p_inventory_item_id => x_item_rec.inventory_item_id,
  11. p_organization_id => x_item_rec.organization_id);

UPDATE item INV CATEGORY

  1. inv_item_category_pub.update_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_old_category_id => l_old_category_id,
  9. p_category_id => l_record.inv_category_id,
  10. p_category_set_id => 1,
  11. p_inventory_item_id => x_item_rec.inventory_item_id,
  12. p_organization_id => x_item_rec.organization_id);

DELETE item INV CATEGORY

  1. inv_item_category_pub.delete_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_category_id => l_old_category_id,
  9. p_category_set_id => 1,
  10. p_inventory_item_id => x_item_rec.inventory_item_id,
  11. p_organization_id => x_item_rec.organization_id);

CREATE item SALE CATEGORY

  1. inv_item_category_pub.create_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_category_id => l_record.sale_category_id,
  9. p_category_set_id => l_category_set_id,
  10. p_inventory_item_id => x_item_rec.inventory_item_id,
  11. p_organization_id => x_item_rec.organization_id);

UPDATE item SALE CATEGORY

  1. inv_item_category_pub.update_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_old_category_id => l_old_category_id,
  9. p_category_id => l_record.sale_category_id,
  10. p_category_set_id => l_category_set_id,
  11. p_inventory_item_id => x_item_rec.inventory_item_id,
  12. p_organization_id => x_item_rec.organization_id);

DELETE item SALE CATEGORY

  1. inv_item_category_pub.delete_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_category_id => l_old_category_id,
  9. p_category_set_id => l_category_set_id,
  10. p_inventory_item_id => x_item_rec.inventory_item_id,
  11. p_organization_id => x_item_rec.organization_id);

CREATE item COST CATEGORY

  1. inv_item_category_pub.create_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_category_id => l_record.cost_category_id,
  9. p_category_set_id => l_category_set_id,
  10. p_inventory_item_id => x_item_rec.inventory_item_id,
  11. p_organization_id => x_item_rec.organization_id);

UPDATE item COST CATEGORY

  1. inv_item_category_pub.update_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_old_category_id => l_old_category_id,
  9. p_category_id => l_record.cost_category_id,
  10. p_category_set_id => l_category_set_id,
  11. p_inventory_item_id => x_item_rec.inventory_item_id,
  12. p_organization_id => x_item_rec.organization_id);

DELETE item INV CATEGORY

  1. inv_item_category_pub.delete_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_category_id => l_old_category_id,
  9. p_category_set_id => l_category_set_id,
  10. p_inventory_item_id => x_item_rec.inventory_item_id,
  11. p_organization_id => x_item_rec.organization_id);

CREATE item PO CATEGORY

  1. inv_item_category_pub.create_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_category_id => l_record.po_category_id,
  9. p_category_set_id => l_category_set_id,
  10. p_inventory_item_id => x_item_rec.inventory_item_id,
  11. p_organization_id => x_item_rec.organization_id);

UPDATE item PO CATEGORY

  1. inv_item_category_pub.update_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_old_category_id => l_old_category_id,
  9. p_category_id => l_record.po_category_id,
  10. p_category_set_id => l_category_set_id,
  11. p_inventory_item_id => x_item_rec.inventory_item_id,
  12. p_organization_id => x_item_rec.organization_id);

DELETE item INV CATEGORY

  1. inv_item_category_pub.delete_category_assignment(p_api_version => '1.0',
  2. p_init_msg_list => p_init_msg_list,
  3. p_commit => p_commit,
  4. x_return_status => x_return_status,
  5. x_errorcode => l_errorcode,
  6. x_msg_count => x_msg_count,
  7. x_msg_data => x_msg_data,
  8. p_category_id => l_old_category_id,
  9. p_category_set_id => l_category_set_id,
  10. p_inventory_item_id => x_item_rec.inventory_item_id,
  11. p_organization_id => x_item_rec.organization_id);

详解EBS接口开发之物料导入API的更多相关文章

  1. 供应商API补充(详解EBS接口开发之供应商导入)(转)

    原文地址  供应商导入的API补充(详解EBS接口开发之供应商导入) --供应商 --创建 AP_VENDOR_PUB_PKG.Create_Vendor ( p_api_version IN NUM ...

  2. 详解EBS接口开发之供应商导入

    (一)供应商常用标准表简介 1.1   常用标准表 如下表中列出了与供应商相关的表和说明: 表名 说明 其他信息 ap_suppliers 供应商头表 供应商的头信息如:供应商名.供应商编码.税号等 ...

  3. 供应商导入的API补充(详解EBS接口开发之供应商导入)

    --供应商 --创建 AP_VENDOR_PUB_PKG.Create_Vendor ( p_api_version IN NUMBER, p_init_msg_list IN VARCHAR2 := ...

  4. 详解EBS接口开发之供应商导入(补充)--错误信息处理

    check reject details on records of AP_SUPPLIER_INT SELECT s.parent_table,s.reject_lookup_code,S.LAST ...

  5. 详解EBS接口开发之供应商导入补充-供应商地点增加实例

    DECLARE --v_org_id number; v_vendor_interface_id NUMBER; v_vendor_site_interface_id NUMBER; --接口表的id ...

  6. 详解EBS接口开发之供应商导入(补充)--供应商银行账户更新

    CREATE OR REPLACE PACKAGE BODY update_vendor_account IS PROCEDURE main(errbuf OUT VARCHAR2, retcode ...

  7. 具体解释EBS接口开发之物料导入API

    create_item inv_item_grp.create_item(p_commit => fnd_api.g_true, -- p_item_rec => l_item_rec, ...

  8. 详解EBS接口开发之采购申请导入

    更多内容可以参考我的博客  详解EBS接口开发之采购订单导入 http://blog.csdn.net/cai_xingyun/article/details/17114697 /*+++++++ ...

  9. 详解EBS接口开发之库存事务处理批次更新

    库存事务处理批次有时候出现导入错误需要更新可使用次程序更新,批次导入可参考博客 详解EBS接口开发之库存事务处理-物料批次导入 http://blog.csdn.net/cai_xingyun/art ...

随机推荐

  1. RHEL Linux常用指令

    查询已安装软件包 rpm -qa|grep * 安装软件 rpm -ivh * 查询Linux版本 uname -a lsb_release -a cat /etc/redhat-release ca ...

  2. Go 语言教程

    Go 语言教程 Go 是一个开源的编程语言,它能让构造简单.可靠且高效的软件变得容易. Go是从2007年末由Robert Griesemer, Rob Pike, Ken Thompson主持开发, ...

  3. Tomcat中的c3p0数据库连接池的释放

    一个项目通过c3p0获得连接池,相关代码如下: public class JdbcUtil { // 连接池的核心类 private static ComboPooledDataSource data ...

  4. ZooKeeper之(六)应用实例

    6.1 Java API 客户端要连接 Zookeeper服务器可以通过创建 org.apache.zookeeper.ZooKeeper 的一个实例对象,然后调用这个类提供的接口来和服务器交互. Z ...

  5. move_uploaded_file的failed to open stream错误处理

    PHP的基本语法学习的差不多了,现在开始学习PHP的文件上传功能实现了.功能中使用到了move_uploaded_file方法,运行时报错: failed to open stream. 经过查资料, ...

  6. proc文件系统探索 之 以数字命名的目录

    在proc根目录下,以数字命名的目录表示当前一个运行的进程,目录名即为进程的pid.其内的目录和文件给出了一些关于该进程的信息. niutao@niutao-desktop:/proc/6584$ l ...

  7. OSTC 2015

    上周六去北京参加了OSTC 2015开源技术大会,并分享了<Spark技术内幕>,主要涵盖了Spark Core的核心实现.我主要以WordCount为例,讲解了任务调度的具体实现,资源分 ...

  8. SMON功能-SMON_SCN_TIME字典基表

    SMON后台进程的作用还包括维护SMON_SCN_TIME基表. SMON_SCN_TIME基表用于记录过去时间段中SCN(system change number)与具体的时间戳(timestamp ...

  9. Swift下多个Storyboard的项目结构

    我是个比较喜欢用storyboard和xib的人.我个人的习惯就是,能用storyboard的一定不用代码手工撸.当然自己业余个人写的项目,基本上一个storyboard就搞定了.但涉及到多人合作下时 ...

  10. Hexo 简明教程

    概述 对于个人独立博客的搭建,或者一些产品网站的介绍我个人比较推崇直接用静态网站生成器来完成这个事情,对于,静态网页部署方便,浏览速度快. 以下为部分静态网站生成器简要列表: Ruby Jekyll ...