/BOBF/FRW_CONTRACT - Exception texts for contract violations (no UI texts)
The following messages are stored in message class /BOBF/FRW_CONTRACT: Exception texts for contract violations (no UI texts).
It is part of development package /BOBF/FRAMEWORK in software component BC-ESI-BOF. This development package consists of objects that can be grouped under "Business Object Processing Framework".
It is part of development package /BOBF/FRAMEWORK in software component BC-ESI-BOF. This development package consists of objects that can be grouped under "Business Object Processing Framework".
Message Nr ▲ | Message Text |
---|---|
000 | API contract violation. See prev. exception or "Application Information" |
001 | Illegal state transition from "&1" to "&2" |
002 | Mixed call with active and draft keys |
003 | Probably a determination "on SAVE" has returned a failed key |
004 | Not all dependent drafts are deleted during ACTIVATION |
005 | Principal not locked while creating dependent |
006 | Action was illegally called for active instances |
007 | Enqueue context of source not found while creating dependent |
008 | Calling action EDIT_DEPENDENT on an active instance of BO "&" twice |
009 | Inconsistent state in BOPF runtime after previous error |
010 | Using "Draft Scope" requires BO migration to "Smart Validations" |
011 | Class &1 is reserved for use by generated actions |
012 | Method parameter violates condition "&1&2&3&4" |
013 | Action &1 (model key &2) is not a standard action |
014 | Node &1 (model key &2) is not a normal node |
015 | Group &1 (model key &2) is not a check group |
016 | Alternative Key given in &1 does not belong to node given in &2 |
017 | Association &1 (model key &2) is internal and cannot be used here |
018 | Either both or none of the parameters &1 and &2 must be provided |
019 | BO &1 unexpectedly rejected saving in phase DO_SAVE |
020 | Source node, key, or association given when creating a root instance |
021 | Source node, key, or association missing when creating non-root instance |
022 | Use EML statements instead of Service Manager for BO &1 |
023 | Cannot create Service Manager for Dependent Object &1 |
024 | CDS Messages have to be of instance /BOBF/CL_FRW_DURABLE_MESSAGE |
025 | Missing data for update modification request |
026 | Missing node or instance key |
027 | Provided data for modification doesn't have a structure type |
028 | Key conflict in legacy DAC |
029 | This API is obsolete for RAP migrated BO &1 |
030 | Parameter &1 must have a component named &2 |
031 | RAP edit of unsaved instance with %PID is not supported |
032 | This API is relevant only for RAP migrated BOs |