直发(从供应商采购直接发到客户)的业务流程.doc_第1页
直发(从供应商采购直接发到客户)的业务流程.doc_第2页
直发(从供应商采购直接发到客户)的业务流程.doc_第3页
直发(从供应商采购直接发到客户)的业务流程.doc_第4页
直发(从供应商采购直接发到客户)的业务流程.doc_第5页
已阅读5页,还剩1页未读 继续免费阅读

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

直发(从供应商采购直接发到客户)的业务流程risingsun直发(从供应商采购直接发到客户)的业务流程直发(从供应商采购直接发到客户)的业务流程,不经过自己的物流,那位老大能说几句,在SAP或ORACLE中是如何处理的cipherDrop Shipment, that is a process that you can receive orders for items that you do not stock or for which youlack sufficient inventory, and have a supplier provide the items directly to your customer. Drop Shipment order flow in Oracle:A.EnteraDrop-shiporder-B.Releasetopuchasing-C.ConfirmationofshipmentandreceiptD.InvoicingA.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.redgrassit is third party business model, SAP have provide a standard solution for this model,maybe you can study it mingmei7784ORACLE中可采用直入直出流程,先做销售合同-采购发放-导入申请-自动创建mingmei7784ORACLE中可采用直入直出流程,先做销售合同-采购发放-导入申请-自动创建julianyangFirst, 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: mailto:On Behalf Of Heimdal, JanSent: Wednesday, July 31, 2002 10:38 AMTo: Certified in Production and Inventory ManagementSubject: cpim Procedural questionFor 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 customers shipping address on our PO to the supplier, but Im 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 dont really know when the customer takes receipt of the component, and we dont 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 customers 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. Were 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的情况,呵呵julianyangredgrass, 多交流!多交流!那一大串英文来源于APICS的CPIM论坛,我今天早上刚收到这一则讨论drop shippment的邮件,里面特别谈到有2点:1. we dont 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 customers sales order, then dispatched and invoiced. Do u have any idea?cipher我前述的Oracle流程里可以很好的解决这两个问题1. we dont 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 customers sales order, then dispatched and invoiced. 逻辑接收后,系统自动作发出动作,其间为零时间差,同时系统要求在逻辑仓库做这类物料的接收,也不会对MRP运算造成影响。logi同意cipher的說法/做法。redgrass我前述的Oracle流程里可以很好的解决这两个问题1. we dont want our invoice to reach the customer before the component arrives fr

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

评论

0/150

提交评论