摘要:直发(从供应商采购直接发到客户)的业务流程,不经过自己的物流,那位老大能说几句,在SAP或ORACLE中是如何处理的?

直发(从供应商采购直接发到客户)的业务流程

直发(从供应商采购直接发到客户)的业务流程,不经过自己的物流,那位老大能说几句,在SAP或ORACLE中是如何处理的

cipher

Drop Shipment, that is a process that you can receive orders for items that you do not stock or for which you

lack sufficient inventory, and have a supplier provide the items directly to your customer.

Drop Shipment order flow in :

A.EnteraDrop-shiporder->B.Releasetopuchasing->C.Confirmationofshipmentandreceipt->D.Invoicing

A.There is a field namely 'Source Type' to differentiate normal orders(internal source) and drop-ship orders(external source)

C.You need to do a logical receiving of drop-ship items even if they are not transactable. This creates inbound and outbound material transactions in your system for accounting purposes.

D.All the same as normal invoicing.

redgrass

it is third party business model, SAP have provide a standard solution for this model,maybe you can study it ^^

mingmei7784

ORACLE中可采用直入直出流程,先做销售合同-采购发放-导入申请-自动创建

mingmei7784

ORACLE中可采用直入直出流程,先做销售合同-采购发放-导入申请-自动创建

julianyang

First, redgrass, can you give us a detail example?

Secondary, Pls see the following to understand what the end-users are concerning with:

-------------------------------------------------

We have been presented with this situation for years and have dealt with, but not solved, the same issues.

We request notice of shipments from our vendors and receive them most of the time. In many cases this is an 'exceptional' circumstance for our vendors, and therefore they may not perform as well in this function as they normally do. We decided, however, that our customers should not have to do anything special, such as notify us of receipt, in these cases. It was better to live with the fallout of non-notification than place an added burden on our customers.

The puchase orders we create for these situations contain instructions to our receiving people to see that this material is for a particular sales order and is 'shipped' in our computer system when received at customer. These instructions do not print on the PO, so our vendors never see them. Sales orders and purchase orders are cross referenced in these circumstances. Ensuring that all relevant information is on all documents is a continuing challenge. Our receiving people notify our shipping people that Sales Order# ?????? needs to be 'shipped' . Any discrepencies between the sales order and the receipt at customer is then dealt with by the shipping people in whatever manner the shippers deem appropriate for the circumstance.

Our invoicing procedure automatically reduces our inventory, so it is imperative that this material be placed in inventory at some point. Also, our costing programs work with actual quantities received, freight charged, amounts invoiced, discounts taken, etc., as opposed to PO data. We would be manually making adjustments to numbers if we did not receive this material into inventory.

Our ERP system is home-grown and we have the ability to modify it to match our practices, rather than modify our practices to match the system. Perhaps this gives us flexibility that purchased systems do not have. ???

-----Original Message-----

From: bounce-cpim-22316@lists.apics.org [mailto:bounce-cpim-22316@lists.apics.org]On Behalf Of Heimdal, Jan

Sent: Wednesday, July 31, 2002 10:38 AM

To: Certified in Production and Inventory Management

Subject: [cpim] Procedural question

For those of you who implement/administer/support ERP systems, I have a procedural question regarding how to handle the direct shipment of a component from our supplier to our customer-i.e. we never touch the component, but we will bill our customer for it. It is no problem to specify the customer's shipping address on our PO to the supplier, but I'm wondering if there is a better way to account for customer receipt and billing.

I currently have our users receive the component on the PO and then dispatch and invoice the sales order for that component, so that it is only briefly in our system stock. A challenge occurs in two areas:

1. Performing the receipt in a timely manner. We don't really know when the customer takes receipt of the component, and we don't want our invoice to reach the customer before the component arrives from the supplier. The component may or may not be in stock at the supplier, or it may be a non-stocked custom manufacture item.

2. If the PO does get received, the component will sometimes linger in our system stock before someone notices that it should be allocated to the customer's sales order, then dispatched and invoiced. This is due to the fact that we have different personnel performing PO receipt and SO dispatch functions,. We have attempted to address this by cross-training a few users in different functional areas of the software so that they can create & receive the PO as well as allocate the component to a back-ordered sales order.

We're getting by, but there seems to be room for improvement. I guess we could request notification from the supplier once they ship the component to our customer-that would help. How are other list members handling this situation? Is there a way to by-pass receipt of the component into stock, and if so, is that desirable? Just curious.

Please state responses in generic terms-i.e. not specific to a particular software package. Thanks.

Jan Heimdal

TMI Systems Design Corp.

50 South Third Avenue W.

Dickinson, ND 58601

Phone: 701-456-6716

Fax: 701-456-6700

redgrass

太长了,而且又是英文,呵呵,所以懒得看妳的文字。

SAP提供了third-party的一整套的完整的Solution,当然,我们可以根据自己的需要在创建符合自身的解决方法(大致):

在IMG设置上,可以设置新的Sales order type,新的schedule line item(注意对PP run MRP的影响,在此可以设置让其自动产生PR等系统动作),新的PO type,新的PO Item category,新的accounting assignment category,然后把这些东西串联起来,当然还少不了在FI中设置新的General modification,并给它新的商品类的会计科目(或是中介科目-我们的做法-月底手工清到AR-other或是符合实际需要的会计科目去).

细节问题需要注意的是:

我们对客户的Billing数量是根据对客户SO的数量开,还是根据供货商实际的送货数量开,是在对供货商IV之前Billing,或是在IV之后才能Billing,都可以在IMG->中的Billing document去设置.IV也是.

一般要求对客户的AR和对供货商的AP应该在同一个会计期间一起作(我们的做法).这就要要求采购的人跟销售的人在沟通上要做得很好.

以上在SD和MM中的设置需要小心,否则将会出现帐目不能过到CO的情况,呵呵~~

julianyang

redgrass, 多交流!多交流!

那一大串英文来源于APICS的CPIM论坛,我今天早上刚收到这一则讨论drop shippment的邮件,里面特别谈到有2点:

1. we don't want our invoice to reach the customer before the component arrives from the supplier.

2. If the PO does get received, the component will sometimes linger in our system stock before someone notices that it should be allocated to the customer's sales order, then dispatched and invoiced.

Do u have any idea?

cipher

我前述的流程里可以很好的解决这两个问题

1. we don't want our invoice to reach the customer before the component arrives from the supplier.

仅当接到供

【责编:admin】

--------------------next---------------------

阅读(861) | 评论(0) | 转发(0) |

oracle采购业务流程,直发(从供应商采购直接发到客户)的业务流程相关推荐

  1. 塑化行业SRM供应商管理系统:缩短采购周期时间,改善供应商采购管理

    塑料行业是中国制造最具代表性的产业之一,近年来,我国的塑化产品产量庞大且价格波动剧烈,企业的生产经营面临不小的风险.然而,无论是上游石化公司,还是下游终端生产企业.实体产业客户,都缺少足够的议价能力和 ...

  2. 数字化采购管理系统开发:精细化采购业务流程管理,赋能企业实现“阳光采购”

    采购是保障企业正常运转所需物资稳定供应的核心环节,对于企业实现降本增效实践具有重要意义.近年来,随着数字化转型升级逐步渗透到企业生产经营的每一个环节,以新一代信息技术为驱动的数字化采购正在颠覆传统采购 ...

  3. “一个简单的问题”,采购是如何选择供应商的?

    供应商选择的影响因素 供应商隶属于供应链这一个开放的系统,因而供应商的选择也会受到各种经济.政治和其他因素的影响. 1 质量因素 质量是供应链的生存之本,产品的使用价值是以产品质量为基础的,它决定了最 ...

  4. 「SAP技术」SAP MM 不能向被分配了工厂代码的供应商采购服务?

    「SAP技术」SAP MM 不能向被分配了工厂代码的供应商采购服务? 近日收到A项目的业务团队报的错,说是试图创建一个服务采购订单,却失败了.报错如下, Procurement w/o materia ...

  5. 采购申请不固定供应商怎么破?

    系统有2个途径产生采购申请: 1.MRP物料需求计划产生采购申请,此时需要采购申请自动供应商,已实现: 2.第三方交货销售订单产生的采购申请,此时不需要采购申请自动固定供应商. 怎么破,去掉第三方交货 ...

  6. oracle 采购模块表信息,EBS采购(PO)模块常用表

     select * from po_requisition_headers_all 请求头 select * from po_requisition_lines_all 请求行 select * ...

  7. 企业电子采购管理系统解决方案:供应商内外协同,全程电子化采购系统管理

    传统企业的采购业务.流程.管理在电子商务的快速发展下转型电子化.网络化,更专业.快速的完成以前较为复杂的采购业务.与OA.ERP.MDM.合同系统等众多业务系统的集成.管理系统实现融合共用.正如[数 ...

  8. 付款申请单控制申请金额,1、每行记录不可高于采购订单金额减去已申请金额,2、申请时判断之前的已付款项,供应商采购发票有没有到齐。

    付款申请单控制申请金额,1.每行记录不可高于采购订单金额减去已申请金额,2.申请时判断之前的已付款项,供应商采购发票有没有到齐,第一次付款时无付款申请记录可直接通过,当有付款记录后,若已付款项的发票还 ...

  9. 瞄准物业采购痛难点,SRM供应商采购管理系统助力企业打造全数字化供应网络

    近年来物业行业规模快速增长.业态范围不断延伸.服务内涵不断丰富.服务品质越来越被重视,在行业高速发展.高质量发展的同时,企业间的竞争愈演愈烈,拼增长.拼服务.拼效率--,而这其中,数字化已经成为核心竞 ...

最新文章

  1. 底层实现_Redis有序集合zset的底层实现
  2. MySQL学习_计算用户支付方式占比_20161104
  3. 前端学习(3064):vue+element今日头条管理-状态处理
  4. HTML+CSS+JS实现React简单的计算器实例
  5. 【数理逻辑四】谓词逻辑及形式系统 【下】
  6. P1955 [NOI2015]程序自动分析 离散化学习 lower_bound学习
  7. 在InternetExplorer.Application中显示本地图片
  8. 【C语言】强迫症是不是病QAQ
  9. MicroShift - 一个超轻量级 OpenShift 环境
  10. 同步、异步、阻塞、非阻塞 简析
  11. 什么是服务的熔断降级
  12. IE6下PNG背景透明的七种方法
  13. Maven入门实战笔记-11节[7-11]
  14. 从机器学习谈起 (转)
  15. linux常用命令详解和用法_详解Linux shell用法中常用命令--read(传参)
  16. 华展云-让展览更高效 2017第6届中国国防信息化装备与技术博览会会刊(参展商名录)
  17. 英文词典 text 文本格式下载
  18. PIC单片机入门教程(四)—— 第一个工程
  19. Qt实现类似QQ头像
  20. 2021-2026年中国畜牧业发展环境分析及投资前景预测报告

热门文章

  1. iview button根据条件 disabled可用或者不可用
  2. 编程实战——电影管理器之界面UI及动画切换
  3. 阿里Java面试必问:java多线程实例
  4. 斐讯n1刷linux服务器,斐讯N1刷Ubuntu系统配置SMB
  5. 【王道考研】操作系统 笔记 第二章上 进程调度
  6. MCAFEE杀毒软件无法完全卸载的解决方案
  7. van访谈_谷歌业务分析师访谈
  8. debian 安装声卡驱动(Realtek alc887_vd)
  9. 第188天:extend拷贝创建对象的原理
  10. 博客2.0时代——读者的赞赏,才是原创的动力