SCM600--Sales and Distribution Processes-Data Determination and Collective Processing

Sales and Distribution Processes-Data Determination and Collective Processing[@more@]

1.Function of the Sales Document Type
In Sales, a wide range of different activities are carried out. Different business processes can be dentified and controlled by means of the sales document type.

2.Plant, Shipping Point, and Route Determination
*The system uses the following search strategy to delivering plant determination:
.First, it checks whether a specification exists in a customer-material info record.
.Second, it checks whether a specification exists in a customer master record of the ship-to party.
.Third, it checks whether a specification exists in the material master record.

*The route is the path a delivery follows from the delivering plant to the ship-to party.

*The system uses three fields as search keys for determining the shipping point automatically. This data is normally defined in the following master records:
.Shipping condition from the sold-to party (view: Shipping)
.Loading group in the sales-specific material data (view: Sales: General/Plant Data)
.Delivering plant -see:Determining Delivering Plant Automatically

*The system uses four fields as search keys for determining the route automatically.
This data is normally defined in master records and in Customizing:
.The departure zone in Customizing for the shipping point
.Shipping condition from the sold-to party (view: Shipping)
.Transportation group in the sales-specific material data (view: Sales:General/Plant Data)
.Transportation zone in the general data for the ship-to party

3.Shipment Scheduling
*The following data is used in shipment scheduling:
.Order date: date on which the order is placed
.Material availability date: date by which a sufficient quantity of goods must be available for picking and packing
.Loading date: date on which the goods picking and packing process is completed(and the mode of transport is available) so that loading can begin on time
.Goods issue date: the date on which the goods must leave the delivering plant so that they reach the customer on the agreed date
.Delivery date: date on which the goods arrive at the customer. A differentiation is made between:
--Requested delivery date: date on which the customer would like the goods to arrive
--Confirmed delivery date: date on which the goods receipt is confirmed for the customer.

*The total time includes:
.The transit time:The time required for transporting the goods to the customer
.Transportation lead time:The time required for preparing the goods for transportation

*For backwards scheduling, the customer's requested delivery date is used to calculate the material availability date and the transportation lead time. The delivery must be created on the earliest of the two dates (selection date for outbound delivery).
.If both dates are after the order date and the material is available on the material availability date, the customer's requested delivery date can be confirmed.
.If one of the two dates is before the order date, confirmation of the requested delivery date cannot take place. Therefore, the system attempts to determine the next possible date (forward scheduling).

*If the result of backward scheduling means that the delivery date required by the customer cannot be confirmed, the system executes forward scheduling.
.Forward scheduling takes into consideration the time parallels of the work flows for transportation planning and picking/packing of materials. The longer of the two periods is relevant for scheduling. The selection date of the outbound delivery is the earlier of the material availability or the transportation planning date.
.The earliest date at which the material is available in the warehouse is the new material availability date. This is the outgoing point for new delivery scheduling.

4.Collective Processing in Sales and Distribution
*The system controls the creation of outbound deliveries via the shipping point, the selection data (picking date) and other criteria grouped on various tab pages.
*There are fields in master data and in the sales document where you can store customer defaults for processing deliveries.
.If the customer requires complete delivery, the order should be delivered in one single delivery. All items should be delivered at the same time. When creating an outbound delivery, if all of the order items cannot be shipped with the full order quantity, you receive a warning that the customer requires complete delivery.
.If the customer does not require complete delivery, you can define a partial delivery agreement with the customer.
.If the customer allows orders to be combined, the R/3 System combines orders when creating the Delivery Due List. Combining items from different sales orders is only possible if the items have several common characteristics, for example:
--Shipping point (goods issue from the same place in your enterprise)
--Date that delivery is due (date on which shipping processing should begin, either materials availability date or transportation planning date) must be within the selection dates on the delivery list initial screen.
--Ship-to party (outbound deliveries have the same destination)
--Route (same method of transport and route)
--Incoterms (.International Chamber of Commerce. terms of liability for freight in-transit)

*Picking can be confirmed automatically or in a separate processing step.

*The goods issue can also be posted via collective processing.

*The system contains a range of options for creating billing documents. You can choose the option that best suits your requirements. Here are a few of the most common options:
.Invoice split:
You have a sales order for which one outbound delivery has been processed.Two billing documents are created from the outbound delivery, based on key differences between the line items, for example, different material groups.
.Separate billing document for each outbound delivery:
You have a sales order for which two outbound deliveries have been processed.Two billing documents are created from the outbound delivery. You would choose this option if your customers typically verify the invoice against a bill of loading, for example.
.Collective invoice:
You have two sales orders for which three outbound deliveries have been processed (for example, different ship-to party or partial delivery). A single billing document is created from the outbound deliveries.

*This slide gives an overview of the options that are available for collective processing to support the sales and distribution process.
1. The delivery list is used to process many sales documents for outbound deliveries.
2. The picking worklist creates transfer orders for picking.
3. The goods issue worklist for outbound deliveries will post goods issue for many deliveries.
Transactions which require picking are only taken into consideration in this list after picking has been successfully carried out.
4. The billing due list is used to create invoices for outbound deliveries and orders. Outbound deliveries are only taken into consideration in the billing due list if the goods issue has already been successfully carried out.

Exercise
Logistics → Sales and Distribution → Sales → Order → Change → Select item 10 → Schedule lines for item → Shipping
You can display a detailed list of the shipping dates for the confirmed schedule line of a sales document item.
Delivery date,Goods issue date,Loading date,Material availability date,Transportation planning date

Process the delivery due list for your shipping point.
Logistics → Sales and Distribution → Shipping and Transportation →Outbound Delivery → Create → Collective Processing of Documents Due for Delivery → Sales Orders

Choose Log for delivery creation display the collective processing log. Record the group number under which the system log is managed.

Process your billing due list.
Choose Logistics → Sales and Distribution → Billing → Billing Document → Process Billing Due List.

Select two documents and choose Split analysis.
Compare two documents to see why the items from these outbound deliveries cannot be put together into one billing document.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/149809/viewspace-1025072/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/149809/viewspace-1025072/