Ansicht
Dokumentation

CRMVC_DBA_MDL_RL - Define Decision Basis Model Behavior

BAL_S_LOG - Application Log: Log header data   General Data in Customer Master  
This documentation is copyright by SAP AG.

In this Customizing activity, you define features of a decision basis (DBA) model and the entity types used within the model.

Model Details

In this activity, you assign a standard completeness check strategy for each DBA model. For more information, see Completeness Check.

Entity Type Details

In this activity, you define a prefix for each entity type used for the unique DBA entity ID generated at runtime. The DBA entity ID is a key that identifies the specific entity within a decision basis. The entity ID consists of a prefix and sequential numbering combinations, separated by a dot. The entity ID is displayed in the WebClient UI and describes the path to the particular data for a decision basis.

The following is an example of a generated DBA entity ID based on the following settings:

Entity Type	Prefix
Working Relationship	WR
Income	INC

The generated entity ID of the first income at the first employer is WR1.INC1.

In the following subactivities, you define the DBA processing steps executed for each entity type:

• Initial Data Collection

In this activity, you implement your Business Add-In, BAdI: Define Processing Steps for Decision Basis, method LOAD_ENTITY_TREE, or your BRFplus function for initial data collection to each top entity type.

You cannot assign a rule to an entity type that is not a top entity type.

The BRFplus function requires you to use the DBA context (see BRFplus for Decision Basis).

• Consistency Check

In this activity, you create your Business Add-In, BAdI: Define Processing Steps for Decision Basis, method CONSISTENCY_CHECK, or your BRFplus function for consistency check collection for each entity type.

If no rule is maintained, set the entity status to Consistent.

The BRFplus function requires you to use the DBA context (see BRFplus for Decision Basis).

• Verification Check

In this activity, you create your Business Add-In, BAdI: Define Processing Steps for Decision Basis, method VERIFICATION_CHECK, or your BRFplus function for verification check data collection for each entity type (see BRFplus for Decision Basis).

If the Not Relevant indicator is selected, the entity status is set to Not relevant automatically.

If the Not Automaticindicator is selected, rules can be executed manually using the Single Verification function.

If no rules are maintained, the entity status is set to Manually verified.

• Completeness Check

The completeness check in the WebClient UI indicates whether a selection of DBA data fulfills the prerequisites for each of the decision-making subprocesses eligibility determination, entitlement determination, andentitlement calculation.

In the activity Completeness Check, you define each entity type for the relevant decision-making subprocess. In these Customizing settings, you have options to influence the completeness check status:

Usage	Completeness Check Status	Icon	Definition
Subprocess not chosen	Complete for [subprocess]	Green	Entity data have no impact on the status and are indicated as complete
Subprocess optional chosen	Complete with warning	Yellow	Entity data are filled but not activated*
Subprocess optional chosen	Complete for [subprocess]	Green	Entity data are activated* or are not filled
Subpocess mandatory chosen	Not complete for [subprocess]	Red	Entity data are not activated*
Subpocess mandatory chosen	Complete for [subprocess]	Green	Entity data are activated*

In the activity Model Details, you assign one completeness check strategy for each DBA model. SAP delivers the strategy AND. In accordance with the AND strategy, the completeness is fulfilled only if all entity data are activated* for each mandatory entity type. Alternatively, you can define your own strategy in the Customizing activity, Define Completeness Check Strategy.

*Entity data are filled, consistent, and verified.

Note:
For more information integrating the DBA data with the decision-making sub processes, see the class documentation CL_CRM_PS_DBA_API.

Green

Green

Green

Green

ROGBILLS - Synchronize billing plans   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 7751 Date: 20240523 Time: 161353     sap01-206 ( 83 ms )