CRD_REQBUILD - Credentialing: Generate Requirements
The following messages are stored in message class CRD_REQBUILD: Credentialing: Generate Requirements.
It is part of development package CRDRUN in software component ICM. This development package consists of objects that can be grouped under "Credentialing: Runtime".
It is part of development package CRDRUN in software component ICM. This development package consists of objects that can be grouped under "Credentialing: Runtime".
Message Nr ▲ | Message Text |
|---|---|
| 100 | **** Exceptions when Generating Requirements **** |
| 101 | No implementation found for BAdI &1 |
| 102 | Inconsistent status of class &1: Reference &2 does not exist |
| 103 | Nesting depth of requirements too large; maximum depth &1, requirement &2 |
| 104 | Requirement &1 is inconsistent |
| 105 | BAdI &1 has multiple implementations |
| 106 | Requirement &1 (ID &2): Internal error during generation |
| 107 | No role created for requirement &1 |
| 110 | No parameters have been defined for assignment algorithm &1 |
| 111 | Assignment algorithm is not implemented |
| 112 | First assignment condition is initial; second is not (in requirement &1) |
| 113 | Assignment parameters in requirement &1 do not match |
| 114 | No partner available for reference in requirement &1 (ID &2) |
| 115 | Assignment rule &1 is invalid for requirement &2 |
| 116 | Cannot generate root requirement |
| 120 | Filter for application assignment cannot be generated (requirement &1) |
| 130 | Requirement &1 |
| 131 | Requirement &1(ID &2) of partner &3 was fulfilled |
| 132 | Requirement &1(ID &2) of partner &3 was not fulfilled |
| 133 | Check of requirement &1(ID &2) for partner &3 is canceled |
| 134 | Check of requirement &1(ID &2) for partner &3 is skipped |
| 135 | Requirement &1 is assigned identification &2 |
| 136 | Requirement &1(requirements list &2, item &3) is incorrect |
| 137 | Item &2 of requirements list &1 has errors |
| 138 | Requirements list &1(ID &2) contains items with errors |
| 139 | Requirement &1(ID &2) was assigned to list &3 (ID &4) |
| 140 | Invalid access of an item list |
| 150 | **** Exceptions for Determination of Requirements **** |
| 151 | Invalid call sequence in method &1 of requirements determination |
| 152 | No combination defined for object type &1, event type &2, context &3 |
| 153 | Incorrect Customizing of requirements determination; see long text |
| 154 | Cannot determine name of transport structure for application &1 |
| 155 | Cannot generate transport structure |
| 156 | Root requirement in determination is not supported |
| 160 | No access to event structure possible during determination process |
| 161 | No access to header data possible during determination process |
| 162 | No access to determination structure possible during determin. process |
| 170 | Reading of single results in the determination failed |
| 171 | Requirement has no triggering event |
| 172 | Exception in determination of requirements |
| 180 | BAdI to define determination algorithm was not implemented |
| 181 | BAdI to define determination algorithm was implemented more than once |
| 200 | **** List Administration **** |
| 201 | Invalid insertion into list of requirements for requirement &1 |
| 202 | Invalid insertion into list of requirements |
| 203 | Reading of internal table failed; index &1 |
| 204 | Invalid reference to encapsulated requirements list |
| 205 | Generation of iterator failed |
| 206 | Invalid insertion into list of partners |
| 207 | Exception while reading from list |
| 208 | Generation of filtering iterator failed |
| 209 | Partner list in requirement &1 (ID &2) was not correctly processed |
| 210 | Combination of results of requirement &1(ID &2) was canceled |
| 300 | **** Messages on Input Data **** |
| 301 | Technical access time-spot is unknown |
| 302 | Effective access time-spot is unknown |
| 399 | **** Check of Requirements List/Combinations **** |
| 400 | Error while checking requirements list &1(ID &2) |
| 401 | No check is possible; requirement of list &1 is not yet generated |
| 402 | Combined requirement expects a result from requirements &1 |
| 403 | Combined requirement &1(ID &2) for partner &3 is fulfilled |
| 404 | Combined requirement &1(ID &2) for partner &3 is not fulfilled |
| 405 | Requirement &1(ID &2) will be checked against partner list |
| 406 | ...Partner &3: Check of requirement &1(ID &2) will be skipped |
| 407 | ...Partner &3: Check of partner list &1(ID &2) is canceled |
| 408 | ...Partner &3: Requirement &1(ID &2) is fulfilled |
| 409 | ...Partner &3: Requirement &1(ID &2) is not fulfilled |
| 410 | Requirement &1(ID &2) is fulfilled for partner list |
| 411 | Requirement &1(ID &2) is not fulfilled for partner list |
| 412 | Partner list for check of requirement &1(ID &2) is missing |
| 413 | Combination &1(Id &2) contains a list &3(ID &4) |
| 414 | Requirement &1(ID &2) (OR) is not fulfilled, empty list; see long text |
| 415 | Requirement &1(ID &2) (OR) is not fulfilled; see long text |
| 416 | Requirement &1(ID &2) (OR operat.) is fulfilled; fulfilled by partner &3 |
| 417 | Requirement &1(ID &2) (AND) is fulfilled, list is empty; see long text |
| 418 | Requirement &1(ID &2) (AND) is not fulfilled; not fulfilled by partner &3 |
| 419 | Requirement &1(ID &2) (AND) is fulfilled; fulfilled by all partners |
| 420 | Error while checking requirement combination &1(ID &2) |
| 500 | **** Simple Requirement ***** |
| 501 | Requirement &1 was not generated due to inconsistent transaction data |
| 502 | Requirement &1 was not generated due to inconsistent Customizing |
| 503 | Check of simple requirement &1 failed |
| 504 | No check possible; simple requirement &1 is not yet generated |
| 505 | More than one implementation of BAdI CRD_SIMPLERQMNT was found |
| 506 | Cannot determine read object for assignments |