Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
OID (Package) MCOE Marketing, Contracts and Order Entry
IMG Activity
| ID | SIMG_MCOE_0004 | Define contract restrictions |
| Transaction Code | S_SO5_65000095 | IMG activity: SIMG_MCOE_0004 |
| Created on | 19990913 | |
| Customizing Attributes | SIMG_MCOE_0004 | Define contract restrictions |
| Customizing Activity | SIMG_MCOE_0004 | Define contract restrictions |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_MCOE_0004 |
Description
Table TVAK_DEF
This view controls the contract restrictions defaulting functionality. It will default a set of restrictions and messages for a specific contract type.
When using this functionality, the system can be set to default restrictions, for a given contract type, that are applied to the orders called off from it. This occurs every time a new contract of that type is created.
Example
SaTy Description Prd SH msg Qty Trm Dat UoM
-----------------------------------------------------
|ZCQR|Restricted Contract| E | E | E | W | E | I |
-----------------------------------------------------
For example, a new contract type can be set up for a customer that requires certain restrictions on the orders called off from its contracts. Instead of manually setting the restrictions in every new contract, these can be specified once for the contract type which is specific to that customer.
The above fields can be restricted on the call-off orders to the values specified on the referenced contract (where the restrictions themselves are set).
The possible values in the message field define what action the system will take upon detecting a restriction violation. If the field is blank, the restriction is deactivated. The other statuses apply different types of message if the attribute restrictions are violated.
Requirements
Please note that this functionality is only available for contracts in SD.
Standard settings
Refer to example above for an entry describing a heavily restricted contract and the relevant table entries.
Recommendation
The use of this functionality is recommended for speeding up the manual entry of contracts and their restrictions. In the example above, where a set of restrictions is specified for a given contract type, the restrictions will automatically default every time a new contract of the given type is created.
Activities
Further notes
If a particular restriction is an exception to the rule, the defaulted field can be changed manually by the user on the contract itself.
Should a particular restriction become obsolete, the restriction itself or the message that is related to it can be changed at any time on the contract itself.
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_MCOE_0004 | 0 | I270009308 | Marketing, Contract and Order Entry |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TVAK_DEF | V - View | SM30 | MCOE_00001 | View to default Contract Restrictions per Contract type |
History
| Last changed by/on | SAP | 20000118 |
| SAP Release Created in |
