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

流程管理

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

risingsun

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

直发（从供应商采购直接发到客户）的业务流程，不经过自己的物流，那位老大能说几句，在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 Oracle:

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:

[]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

流程管理…… 此处隐藏：6017字，全部文档内容请下载后查看。喜欢就下载吧 ……