create_item

 inv_item_grp.create_item(p_commit        => fnd_api.g_true, --
p_item_rec => l_item_rec,
x_item_rec => x_item_rec,
x_return_status => x_return_status,
x_error_tbl => l_error_tbl,
p_template_id => l_record.template_id);

update_item

inv_item_grp.update_item(p_commit        => fnd_api.g_true,
p_item_rec => l_item_rec,
x_item_rec => x_item_rec,
x_return_status => x_return_status,
x_error_tbl => l_error_tbl,
p_template_id => l_record.template_id);

默认接收子库存

 inv_item_sub_default_pkg.insert_upd_item_sub_defaults(x_return_status     => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_organization_id => x_item_rec.organization_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_subinventory_code => l_record.default_receiving_subinv,
p_default_type => '2',
p_creation_date => SYSDATE,
p_created_by => fnd_global.user_id,
p_last_update_date => SYSDATE,
p_last_updated_by => fnd_global.user_id,
p_process_code => l_process_code,
p_commit => fnd_api.g_true);

CREATE item INV CATEGORY

 inv_item_category_pub.create_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_category_id => l_record.inv_category_id,
p_category_set_id => 1,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

UPDATE item INV CATEGORY

inv_item_category_pub.update_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_old_category_id => l_old_category_id,
p_category_id => l_record.inv_category_id,
p_category_set_id => 1,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

DELETE item INV CATEGORY

inv_item_category_pub.delete_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_category_id => l_old_category_id,
p_category_set_id => 1,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

CREATE item SALE CATEGORY

 inv_item_category_pub.create_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_category_id => l_record.sale_category_id,
p_category_set_id => l_category_set_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

UPDATE item SALE CATEGORY

inv_item_category_pub.update_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_old_category_id => l_old_category_id,
p_category_id => l_record.sale_category_id,
p_category_set_id => l_category_set_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

DELETE item SALE CATEGORY

inv_item_category_pub.delete_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_category_id => l_old_category_id,
p_category_set_id => l_category_set_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

CREATE item COST CATEGORY

 inv_item_category_pub.create_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_category_id => l_record.cost_category_id,
p_category_set_id => l_category_set_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

UPDATE item COST CATEGORY

inv_item_category_pub.update_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_old_category_id => l_old_category_id,
p_category_id => l_record.cost_category_id,
p_category_set_id => l_category_set_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

DELETE item INV CATEGORY

inv_item_category_pub.delete_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_category_id => l_old_category_id,
p_category_set_id => l_category_set_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

CREATE item PO CATEGORY

 inv_item_category_pub.create_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_category_id => l_record.po_category_id,
p_category_set_id => l_category_set_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

UPDATE item PO CATEGORY

inv_item_category_pub.update_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_old_category_id => l_old_category_id,
p_category_id => l_record.po_category_id,
p_category_set_id => l_category_set_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

DELETE item INV CATEGORY

inv_item_category_pub.delete_category_assignment(p_api_version       => '1.0',
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_errorcode => l_errorcode,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_category_id => l_old_category_id,
p_category_set_id => l_category_set_id,
p_inventory_item_id => x_item_rec.inventory_item_id,
p_organization_id => x_item_rec.organization_id);

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

  1. 详解EBS接口开发之物料导入API

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

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

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

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

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

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

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

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

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

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

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

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

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

  8. 具体解释ebs接口之客户配置文件导入(二)

    ------------------------------------ -- 1a. Setup the Org_id ------------------------------------ ex ...

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

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

随机推荐

  1. 打印log 保存log

    using UnityEngine; using System.Collections; using System.IO; using System; using System.Text; names ...

  2. Git 笔记一 Git简介

    git 笔记一 什么是版本控制 所谓版本控制就是记录对文件的修改记录,这样以后就能回退到需要的 版本.比如你对一段代码进行了几次修改,有几次修改不想要了,如果 使用了版本控制,就可以回退到未做这些修改 ...

  3. Linux 下提高make的编译效率

    Linux下安装程序,一般都通过包管理器安装,但是包管理器或软件商店里的软件往往不是最新版本的,安装最新版软件时通常是下载源代码进行编译. 编译安装源代码时就离不开make了,但是make是单线程的, ...

  4. c#中的表达式

    // 把变量和字面值(在使用运算符时,将它们统称为操作数)与运算符组合起来 // 就可以创建表达式,表达式是计算的基本构件 // 操作数可以是数值也可以是变量 + ; ; int num3 = num ...

  5. jQuery 双击事件(dblclick)时,不触发单击事件(click)

    我这是转载的文字 原文地址:http://www.cnblogs.com/wyblog/archive/2011/12/15/2289219.html 万恶的双击事件啊!! 在jQuery的事件绑定中 ...

  6. Nohttp网络请求数据,Post以及Get的简单实用以及设置缓存文字的的请求

    开局声明:这是基于nohttp1.0.4-include-source.jar版本写的教程 由于nohttp功能强悍,因此需要多种权限,仅仅一个联网的权限是不够的,如果只给了Internet的权限,去 ...

  7. llinux之sudo配置

    1.使用visudo来配置,因为visudo在配置完毕后,会检查是否有语法错误. 2.配置格式: 授权账号    授权账号所在hostname=(可切换的账号)    可执行的命令command(如果 ...

  8. 刺猬大作战(游戏引擎用Free Pascal写成,GUI用C++写成,使用SDL和Qt4)

    游戏特性[编辑] 游戏引擎用Free Pascal写成,GUI用C++写成,使用SDL和Qt4[2]. 0.9.12开始支持实时动态缩放游戏画面. 个性化[编辑] 刺猬大作战有着高度定制性 游戏模式: ...

  9. HttpContext请求上下文对象

    一.HttpContext概述 HttpContext基于HttpApplication的处理管道,由于HttpContext对象贯穿整个处理过程,所以,可以从HttpApplication处理管道的 ...

  10. Linux命令之xargs的分析及隐患

    写一个main.c: #include <stdio.h> int main(){ printf("foo"); printf("bar"); re ...