HI
<b>What is the difference b/w contracts and Scheduling Agreements </b>
Both of them contains schedule line, price, quantity.
There are a couple major differences:
(1) - Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-ABART). Standard SAP you should have two sets of tabs - of schedule lines. One Forecast & the other JIT. Forecast forwards the schedule lines to planning (seen in MD04) and JIT passes them to shipping (VL10). They can be identical or different. Typically these are used for component supplier customers (namely Automotive). The customer will provide you 4-10 weekly buckets (usually a
Monday date) of future forecast qtys. Also send you 1-2 weeks of individual FIRM ship dates - which are entered on the JIT. It comes down to the customer not knowing exactly what they need next week, but they don't want to suprise you with a large order qty, where your lead times are 5+ days. The forecasted qtys they sent last week should account for this.
(2) Cumulative Quantities are tracked and influence how the schedule agreement passes requirements to both forecasting and shipping. These qtys are sometimes requested by the customer on ASNs. Cumulative qtys reset at year end unless you've got a customer calendar or you've modified standard SAP userexits to not reset.
Schedule agreements are very nice when the customer sends EDI data (830s = forecast or 862s = JITs). Outside of that they can really cause trouble regarding daily maintenance, missing requirements, cum qty corrections, year end processing, etc.
One alternative would be to use customer independent requirements - entering the weekly, monthly forecasting qtys and entering standard sales orders (with or without multiple schedule lines) to represent the true firm qtys.
<b> stock for the consignment sales</b>
To have an overview of the consignment stock at customer use MB58.From there you can have the details of the material movements that generate this stock, and the go back to the delivery (and the to the order by doc. flow)
Consignment Stock Processing
Purpose
Consignment goods are goods which are stored at the customer location but which are owned by the company. The customer is not obliged to pay for these goods until they remove them from consignment stock. Otherwise, the customer can usually return consignment goods that are not required.
Consignment Fill-Up: Consignment fill-up replenishes the stock at the customer site. Since the goods remain the property of the company, this process is not relevant for pricing and consequently not for invoicing either.
Create a sales order using order type KB.
Enter the required data on the customer, the consignment goods and the delivering plant.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The underlying goods movement type is a stock transfer. This ensures that when goods issue is posted, consignment special stock is created for the customer concerned. If special stock of this kind already exists in the delivering plant for this customer, the goods are posted to this special stock.
Order type: KB (document category C: sales order)
Std. Delivery type: LF
Item category: KBN (not relevant for pricing and billing)
Schedule line category: E1 (relevant for deliveries, uses availability check, 631 (GI consignment: lending) to post the stock into a special consignment category in the delivering plants stock for that particular customer and material)
Copy control rules for the sales doc, item category, and schedule line category.
Use trans MB58 or MMBE to check the stock.
In this case, Accounting document is required to be generated only for taxes, as the stock is still the ownership of the company. In the pricing procedure all condition type except for Taxes should be statistical.
Consignment Issue: The Consignment issue enables the customer to withdraw consignment goods from the special stock that are to be used or sold.
Create a sales order using order type KE.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The goods are then reduced by the relevant quantity in the special stock assigned to the customer. This goods issue also reduces your total stock.
Invoice the delivery which issues the consignment goods.
Order type: KE (document category C: sales order)
Std. Delivery type: LF
Invoice: F2
Item category: KEN (relevant for pricing and deliver related billing, special stock indicator W, should determine cost too)
Schedule line category: C1 (relevant for deliveries, uses availability check, 633 (GI issue: customer consignment)
In this case, Accounting document is required to be generated only for most of the condition type, as it is being invoiced to end customer.
Consignment returns: proceed as follows: Consignment returns enable your customer to return goods to the consignment stock that has already been issued from it.
Create a sales order using sales order type CR.
Enter the required data on the customer and the consignment goods.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The goods issue posting cancels the goods issue posting which was carried out when the consignment goods were issued. This posting records the return of the goods to the plant where goods receipt was carried out.
Create a credit memo for the consignment return you created in Step 1.
Order type: KR (document category H: returns)
Delivery type: LR
Credit for Returns Order type: RE (delivery or order related billing)
Item category: KRN (relevant for pricing and deliver related billing, special stock indicator W
Schedule line category: D0 (relevant for deliveries, no availability check, 634
In this case, Accounting document is required to be generated only for most of the condition type, as it is being returned by the customer & invoicing already done to customer..
Consignment Pick-Up: The company uses consignment pick-up to take back consignment goods that are faulty or excess materials that the customer does not need. This process is not relevant for billing since the goods remain the property of the company.
It may be beneficial to have a mandatory reference such as the consignment fill-up. In addition to it copy control rules can be used to further control it. In the copy control rules indicate the document flow. As the stock is coming back into the warehouse or plant, you can specify a returns shipping point to be automatically determined. No invoice is necessary, as the goods are not changing ownership.
Create a sales order using order type KA.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The transaction is completed by the goods issue posting which initiates a transfer posting from the customer's special stock to your plant stock.
Order type: KA (document category C: sales order)
Delivery type: LR
No invoice
Item category: KAN
Schedule line category: F1 (relevant for deliveries, availability check against the stock on the customer’s consignment, 632 (Consignment pickup)
In this case, Accounting document is required to be generated only for taxes, as the stock is still the ownership of the company. In the pricing procedure all condition type except for Taxes should be statistical, as the stock is being returned from consignment site to plant.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.