Contracts and Special Processes Flashcards
Contracts
- Quantity Contracts
- Value Contracts
- Service Contracts
- Group Master Contracts
Contract info
Use a different number range for contracts. Ensures an easier time searching for documents and referencing contracts later.
Contract info 2
- Contract configuration is the same as standard sales document types unless specifically states otherwise
- Order from a contract is a release order
- Open contract quantity only decreases if you have set the update document flow checkbox as enabled on the item category in the copy control rules
Quantity Contracts
- Happens after quotation but before an order
- Used mainly to limit the quanitity the customer can buy and to offer special pricing
- Generally used when demand for a material is greater than the available supply and business has to implement measures to limit the supplied quantity between its customer base
- Document type CQ
- Does not transfer requirements
- Does not create a requirement for stock within the plant and subsequently there is no confirmation of stock within the plant for the contract
- Does not require production to make the stock to satisfy the contract
- Does not require material management to purchase the stock to satisfy the contract
- Contract has no schedule lines nor specific delivery dates
- The requirement is placed on the plant when the release order is created with reference to the quantity contract
- Allows the customer to have a special price per material for a limited quanitity
- Quantity decrease each time an order is made
- Contract expires when the validity date expires or the customer has purchased the full quota of the stock
- Quantity contracts have their own pricing procedures, texts, partners, etc and item categories
- Quantity available is the “Target quantity”, quantity consumed is “order quantity”
Contract Configuration Field: PriceProcCondHeadr and PriceProcCondItem
Pricing procedures and are configured as pricing procedures.
They do not replace the price procedure used in the contract. These values are used for supplemental price agreements.
Contract Configuration Field: Contract profile
*discussed in next section*
Contract Configuration Field: Billing request
Used for service contracts, to bill the customer for a servie that was not agreed to in the original service agreement.
Standard SAP sales document type to perform this billing is LV, which is a debit memo request for service contracts
Contract Configuration Field: Group Ref. Procedure
Used for master contracts to determine which data is to be copied, or proposed, into lower level contracts. Referencing procedures are configured with master contracts later in this chapter.
Contract Configuration Field: Contract data allwd.
Indicates to the system what to do when data differs between the header and item levels.
X, system will not copy any changes you make in the header level into the item levels. This is also true even if the data at header and line item were identical prior to the header data being changed.
Y, the system automatically copies all header data into the item in the contract (only if the header and item contract data were identical prior to the changes)
Contract Configuration Field: FollUpActivityType
Used to speed up the creation of follow-up activites. For example, the follow-up sales activity type 0002 (telephone call) is specified for sales document type WV (service contract).
Contract Configuration Field: Subseq.order type
If the follow up action in “FollUpActivityType” would have been “create quotation,” you would need to enter a quotation document type, in this field.
Contract Configuration Field: Check partner auth.
checks that the partner either is the Sold-to Party of the contract or has a partner function of AA ( which indicates an authorized relesase partner). This is the standard hcecking rule A.
In the standard checking rule B, the system then checks if the partner wishing to release from the contract is a lower level customer in the customer hierarchy, to the Sold to Party in the contract.
Contract Configuration Field: Update low.lev.cont. check box
Used by the system to update lower-level contracts, should the data you are changing be the master contract. These changes are then passed down to the lower-level contracts via workflow.
Contract info
You may also create multiple Ship-to Parties for the specific contract.
There are two ship-to [arty partner functions, standard and the one for multiple ship-to parties
Contract Profiles
Have general info on a contract such as start date, and end date. They’re their own configuration objects ala sales document types, etc