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
2、 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 receivi
3、ng 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
4、 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
5、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
6、, 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 rec
7、eiving 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 th
8、at 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
9、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 take
10、n, 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
11、flexibility that purchased systems do not have. ?-Original Message-From: bounce-cpim-22316lists.apics.org mailto:bounce-cpim-22316lists.apics.orgOn Behalf Of Heimdal, JanSent: Wednesday, July 31, 2002 10:38 AMTo: Certified in Production and Inventory ManagementSubject: cpim Procedural questionFor th
12、ose 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 shippi
13、ng 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 c
14、hallenge 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
15、, 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
16、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 the
17、re 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?
18、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 http:/ redgrass太长了,而且又是英文,呵呵,所以懒得看妳的文字。SAP 提供了 third-party 的一整套的完整的
19、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 或是符合实
20、际需要的会计科目去).细节问题需要注意的是:我们对客户的 Billing 数量是根据对客户 SO 的数量开,还是根据供货商实际的送货数量开,是在对供货商 IV 之前 Billing,或是在 IV 之后才能 Billing,都可以在 IMG-中的 Billing document去设置.IV 也是.一般要求对客户的 AR 和对供货商的 AP 应该在同一个会计期间一起作(我们的做法).这就要要求采购的人跟销售的人在沟通上要做得很好.以上在 SD 和 MM 中的设置需要小心,否则将会出现帐目不能过到 CO 的情况,呵呵julianyangredgrass, 多交流！多交流！那一大串英文来源于 API
21、CS 的 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
22、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 som
23、etimes 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 th
24、e 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.
25、 逻辑接收后，系统自动作发出动作，其间为零时间差，同时系统要求在逻辑仓库做这类物料的接收，也不会对 MRP 运算造成影响。/quote对 1 这是 Billing 开立时点确认的问题: Third party 游戏规则要跟客户先谈好啊 ,Billing 的动作可以在(1)建立 SO 后立即作,(2) 供货商发货后通知我们 (楼上的兄弟说的,但我们可以不作逻辑接收),(3)我们对供货商 IV 后,(4) 客户收货后 EDI 给我们信息后 这四种情况开,根据输赢策略,3,4 我们太吃亏 ,呵呵,而 1 对方不肯,中肯一点的是 2 啦,实际上 Third party 之交易方式多为 EX Works,也符合此情况.对 2 楼上的兄弟说的观点在 SAP 的体现就是我们系统中作虚假的 GR 后立即触发对客户的PGI,这两个动作没有时间差:只是,需要问一句,有必要在系统做假进假出吗? em17cipher楼上，假进假出的目的仅仅是为了会计核算，因为在做采购订单时，做了 Dr 应计应付 Cr 采购接收（或在徒采购）销售发货时做了 Dr 销售成本 Cr 库存商品。 而在假进假出时做 Dr 采购接收 Cr 库存商品 来平帐。redgrass我的意思是沒有必要在系統中做假進假出
