Ansicht
Dokumentation

_CRD_VC_CRD_RQTYP - Configure Requirement Types

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

In this activity, you can configure requirement types. This lets you determine the characteristics of a certain type of requirement.

• You define here whether the requirement type is a simple requirement or a combined requirement.

• You also define whether the requirement type requires you to store a combination algorithm for it.

• Finally you have the option of defining requirement types that deviate from those of the standard delivery.

Note that although the version management function from Incentive and Commission Management (ICM) also applies to the underlying table, table TCRD_RQTYP, the effective start and end dates cannot be changed. The system sets the dates to default values. New versions can be generated only by changing the attributes.
Since the requirement types are some of the fundamental configuration settings in the system, we recommend that you do not make any changes of this kind, especially if there are already requirements that depend on requirement types.
If none of the requirement types meets your needs, you should create a new requirement type instead of changing an existing one.

It may be advisable to create the same requirement type more than once, since the requirement type is a filter for BAdI CRD_REQ_FACTORY.

Note that if you create a filter in this way, you must then assign it to a BAdI implementation. Implementations are provided for all requirement types that are part of the standard delivery.

By copying the client-specific Customizing, the most important requirement types should be available to you.

If ICM is integrated with CRD, only those requirement types can be used that can be combined, or that you defined yourself. For those that you created yourself, you must make sure that their requirements return a check result when they are checked against a partner. If you use the associated requirements in combinations, you must define the requirement type as a combinable requirement type.

If you have implemented your own requirements, assign a suitable implementation of BAdI CRD_REQ_FACTORY to the filter that is defined by the requirement type.

General Material Data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 2587 Date: 20240523 Time: 165330     sap01-206 ( 49 ms )