Hierarchy
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JAS (Package) Application development R/3 Publishing Advertising System***
IMG Activity
| ID | ISPAM_GP_VV_BA_PFL | Maintain Requirement Types |
| Transaction Code | S_KK4_74001822 | IMG Activity: ISPAM_GP_VV_BA_PFL |
| Created on | 19990816 | |
| Customizing Attributes | ISPAM_GP_VV_BA_PFL | Maintain Requirement Types |
| Customizing Activity | ISPAM_GP_VV_BA_PFL | Maintain Requirement Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISPAM_GP_VV_BA_PFL |
In this step you maintain requirement types for sales agent contracts.
The system starts sales agent determination automatically during order entry. This determines the sales agents who are to receive payment for services performed in connection with an order.
These services are defined in the sales agent contracts which contain a description of the requirements that must be fulfilled for a sales agent to receive payment. The type of payment (commission, bonus1, bonus2) is also defined for each contract requirement.
The individual elements of a requirement describe when this requirement has been fulfilled. An element could for example stipulate that the sales agent is only to receive payment for orders from a specific industry sector.
You can create various sample contract requirements and thus avoid having to define requirements and elements for each sales agent contract individually.
You must specify which type of requirement you are defining for each sample, such as a requirement for contracts and should state the number and type of elements that this requirement contains. This sample is known as a requirement type.
The system uses the requirement types that you have defined to search for sales agent contract requirements during sales agent determination. Requirement types are used in the sequence you have defined to find contract requirements that correspond to the data recorded in the order. You can determine whether the system is to terminate the agent search if contract requirements are found for payment using the current requirement type or one used previously. You can make this setting for each requirement and payment type.
The complexity of contract requirements as defined by the number of requirement elements influences the number of contract requirements found subsequently.
The number of requirement types and the cancellation criteria you specify allow you to control the length of time required for sales agent determination.
The validity of a requirement type applies to a sales area.
In addition to unique indicators and the short text for each requirement type, you can also define the following:
- Requirement type content
By selecting an attribute you determine the type of requirement, such as a requirement type for the contract or industry sector etc.
- Sequence
In this step you can determine the order in which requirement types are used in sales agent determination.
- Automatic assignment
If you select a particular indicator (commission, bonus1, bonus2) a sales agent will automatically receive the appropriate payment if a contract requirement is found using this search strategy.
This entry also controls whether in each case a search is only made for contract requirements during order maintenance, or whether a subsequent search is performed during billing.
- Cancel search once target has been found
If you select a particular indicator (commission, bonus1 bonus2) the system terminates the search for sales agent contract requirements for the particular payment if a contract requirement is found using the current requirement type or a previous one (see sequence).
- Sales activity type
Within the contract requirements, you can stipulate that a report regarding a sales activity for a customer is required in order for the contract requirement to be found during sales agent determination.
In this step you can determine in what form the sales activity for a customer is to occur if the report indicator has been selected for a requirement in the sales agent contract.
In the field catalog you can determine,
- Which components (fields) make up a contract requirement
- How a contract requirement can be structured
- How a component can be used in sales agent determination
- Selection of components
By determining the requirement type, you will already have determined a component. By marking additional components as required, optional fields, or a display field, you can specify the requirement type more precisely.
Please note that the addition of each subsequent field further limits the number of contract requirements which can be found using the search strategy.
- Structure of a contract requirement
By assigning component features, you determine the framework for the structure of contract requirements.
- Required field
In required fields, a value should be entered when determining a contract requirement.
Each required field is used in the search.
- Optional field
You can enter a value in an optional field when determining contact elements, but this can also be left blank.
Optional fields are used during the search.
- Display field
Display fields are only displayed later when determining contract elements. They can no longer be changed.
Display fields correspond to optional fields and are used in the search.
You can define a field as a display field:
- When creating a new requirement type, if you want to view the field and do not actually want to use it.
- When changing a requirement type, either if contract elements still exist which use this field, or when creating new contract elements which no longer use this field.
- Inactive field
When determining contract elements, it is no longer possible to enter values in inactive fields.
Inactive fields are not used in the search.
- Effect on sales agent determination
You can indicate whether a contract element has an inclusive or exclusive character later when determining the contract using the assign function field. This determines what effect the feature and content of the field has on sales agent determination.
- Inclusive contract elements
An inclusive contract element is fulfilled if the requirements of all required and optional fields are met.
- Exclusive contract elements
An exclusive contract element is fulfilled and this excludes the contract requirement from sales agent determination if the requirements of all required and optional fields have been met.
The features of these fields have the following effects:
- Required field
- A required field is used in the search.
- A requirement for a required field has been met, if the content of the required field corresponds to that of the relevant order field.
- Optional field
- An optional field is used in the search.
- A requirement for an optional field is met if the content of the optional field corresponds to that of the relevant order field. If the optional field is blank, then the requirement has definately been met for this field.
- Display field
- A display field is treated like an optional field.
- Inactive field
- An inactive field is not used in the search.
Recommendation
It can be advisable to create several requirement types with a limited number of optional fields for exclusive contract requirements so that the exclusive effect of blank optional fields does not become too comprehensive.
Leave gaps between the individual sequences. It is then easier to make changes to the sequence.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | 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 | ISPAM_GP_VV_BA_PFL | 0 | I170007108 | Business Partner in Advertising Management |
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 |
| JJVTJJ73 | V - View | SM30 | 0000000000 | Generated Table Maintenance: JJVTJJ73 |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
