/AWS1/CL_ERNNAMESPACERLBASED00¶
The rule-based properties of an ID namespace. These properties define how the ID namespace can be used in an ID mapping workflow.
CONSTRUCTOR¶
IMPORTING¶
Optional arguments:¶
it_rules TYPE /AWS1/CL_ERNRULE=>TT_RULELIST TT_RULELIST¶
The rules for the ID namespace.
it_ruledefinitiontypes TYPE /AWS1/CL_ERNIDMAPWORKFLOWRLD00=>TT_IDMAPWORKFLOWRLDEFNTYPELST TT_IDMAPWORKFLOWRLDEFNTYPELST¶
The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and target must be compatible.
iv_attributematchingmodel TYPE /AWS1/ERNATTRMATCHINGMODEL /AWS1/ERNATTRMATCHINGMODEL¶
The comparison type. You can either choose
ONE_TO_ONEorMANY_TO_MANYas theattributeMatchingModel.If you choose
ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for theIf you choose
MANY_TO_MANY, the system can match attributes across the sub-types of an attribute type. For example, if the value of theBusinessEmailfield of Profile B, the two profiles are matched on the
it_recordmatchingmodels TYPE /AWS1/CL_ERNRCMATCHINGMDELLS00=>TT_RECORDMATCHINGMODELLIST TT_RECORDMATCHINGMODELLIST¶
The type of matching record that is allowed to be used in an ID mapping workflow.
If the value is set to
ONE_SOURCE_TO_ONE_TARGET, only one record in the source is matched to one record in the target.If the value is set to
MANY_SOURCE_TO_ONE_TARGET, all matching records in the source are matched to one record in the target.
Queryable Attributes¶
rules¶
The rules for the ID namespace.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_RULES() |
Getter for RULES, with configurable default |
ASK_RULES() |
Getter for RULES w/ exceptions if field has no value |
HAS_RULES() |
Determine if RULES has a value |
ruleDefinitionTypes¶
The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and target must be compatible.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_RULEDEFINITIONTYPES() |
Getter for RULEDEFINITIONTYPES, with configurable default |
ASK_RULEDEFINITIONTYPES() |
Getter for RULEDEFINITIONTYPES w/ exceptions if field has no |
HAS_RULEDEFINITIONTYPES() |
Determine if RULEDEFINITIONTYPES has a value |
attributeMatchingModel¶
The comparison type. You can either choose
ONE_TO_ONEorMANY_TO_MANYas theattributeMatchingModel.If you choose
ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for theIf you choose
MANY_TO_MANY, the system can match attributes across the sub-types of an attribute type. For example, if the value of theBusinessEmailfield of Profile B, the two profiles are matched on the
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_ATTRIBUTEMATCHINGMODEL() |
Getter for ATTRIBUTEMATCHINGMODEL, with configurable default |
ASK_ATTRIBUTEMATCHINGMODEL() |
Getter for ATTRIBUTEMATCHINGMODEL w/ exceptions if field has |
HAS_ATTRIBUTEMATCHINGMODEL() |
Determine if ATTRIBUTEMATCHINGMODEL has a value |
recordMatchingModels¶
The type of matching record that is allowed to be used in an ID mapping workflow.
If the value is set to
ONE_SOURCE_TO_ONE_TARGET, only one record in the source is matched to one record in the target.If the value is set to
MANY_SOURCE_TO_ONE_TARGET, all matching records in the source are matched to one record in the target.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_RECORDMATCHINGMODELS() |
Getter for RECORDMATCHINGMODELS, with configurable default |
ASK_RECORDMATCHINGMODELS() |
Getter for RECORDMATCHINGMODELS w/ exceptions if field has n |
HAS_RECORDMATCHINGMODELS() |
Determine if RECORDMATCHINGMODELS has a value |