A quantity contract (sales document type CQ) is basically an agreement stating that the customer will buy a certain quantity of a product in a certain time period. The contract contains general quantity and price information but no specifications of the delivery dates and quantities. The customer fulfills a contract by creating an order with reference to the contract. These sales orders are called contract release orders. When you create a release order, you refer to the relevant contract, and the system automatically updates the released quantities in the contract. Otherwise, processing a release order is just like processing a standard sales order. Quantity contracts in the apparel and footwear industry are often mapped as follows:
● Creation of a (requirement-relevant) quantity contract
● Procurement based on a quantity contract
● Contract release order
● Allocation run, delivery and billing of the contract release order.
Starting with Release 2.5B, you can also allocate against contracts.
AFS-specific data is also available for quantity contracts (entry at SKU level, several AFS order entry screens, VAS, and so on).
See also Sales Order Processing.
Normally a requirements type is assigned when creating a quantity contract (for example requirements type 011 – delivery requirement). As a result, the quantity contract is planned in the MRP accordingly. Depending on the settings in the material master record, if there is a stock shortage the MRP will create a purchase requisition, for example.
The customer fulfills a contract by issuing orders from the contract. If you have a contract with a customer, it is fulfilled when the customer creates sales orders with reference to the contract. These sales orders are called release orders. The system automatically updates the quantities called in the contract. The processing of a contract release order corresponds to the processing of a standard order. The usual process steps within the AFS sales processing are valid here. You cannot process items with account assignment (for example, in third-party orders, purchase-to-order procurement, make-to-order production) and the contract reduction at the same time. Usually the requirements that have been created by the contract with the created contract release order (sales order) are consumed by the reference of the order to the contract.
If you specify a material in a sales order, a list of all open contracts for that material is displayed if the sales order document date falls between Valid From and Valid To date of the contracts.
If you want to filter this list based on some business logic, implement the contract BadI in Customizing by choosing, Sales and Distribution ® Sales ® Sales Documents ® Contracts ® BAdI: Filtering Contracts for Display in Sales Order.
Simultaneous Release Orders
● If you select this field, both authorized partners can access the same contract at the same time and release the desired items.
● Several users can release against one contract at the same time.
● You cause different contract items for a single contract to be able to be processed at the same time in several contract release orders.
● When you change or create a contract release order, the referenced contracts will no longer be exclusively blocked, but rather only the corresponding contract items.
A contract contains 10 items, each with several schedule lines. If you have not selected this field and a partner authorized to release against the contract releases the item 100, the contract is then exclusively blocked. Another authorized partner, who wants to release item 300, must then wait until the first partner finishes the release, saves it and in so doing leaves the contract.
The save and continue function can be activated by order type. You use this option to save the sales order but it does not exit from that screen and stays in change mode. It is similar to saving the order and executing VA02. This enables you to save the order without leaving the order entry when you have finished some items. You can immediately continue to enter or change other items (of course only if these are not locked in the meantime).
If you choose the save and continue button after each item change, this contract item is only locked for a very short time, by when you must enter or change that particular item. This helps in creating release order for the same contract item nearly simultaneously.
Auto Save Interval
If you execute a contract release order with an activated item lock and enter a numerical value in this field, the document is automatically saved after this time period when you change an item. The point in time that is decisive for calculating the time period is when the first item lock was set.
The document is saved in the background. You therefore cannot interrupt the processing of the release order and restart it by calling the transaction again, but rather stay at the same point in the document while the process is running and can continue making changes there.
This field is only ready for input for sales document types that you can use for the contract release order. Functionally, it is used for the simultaneous contract release order.
A quantity contract is generally finished if it does not contain any items that must be delivered. However, the AFS-specific settings for each relevant schedule line category referring to the completion rule are important here.
You can allocate stock to the (requirements-relevant) contracts by using the allocation run. The grid values of an allocated contract are then displayed in the stock/requirements list in MRP status R (reserved by allocation run). When creating the contract release order of already allocated contracts, the system transfers the assigned stock to the order document together with the contract items and schedule lines. If an allocation type is transferred to the order type that is used for the contract release order, the MRP status is changed to F (fixed for delivery). Then you can create the delivery. If you have not stored an allocation type, the MRP status must be converted accordingly using the functions of the allocation run ( ARun Optimizer or Reorganization) so that the delivery can be created. The following graphic shows this process: