AXT_CRM_GEN - CRM Generation framework
The following messages are stored in message class AXT_CRM_GEN: CRM Generation framework.
It is part of development package AXT_CRM_GENERATION_FRAMEWORK in software component CRM-BF-EEW. This development package consists of objects that can be grouped under "Extensibility Generation".
It is part of development package AXT_CRM_GENERATION_FRAMEWORK in software component CRM-BF-EEW. This development package consists of objects that can be grouped under "Extensibility Generation".
Message Nr ▲ | Message Text |
---|---|
000 | *****001 - 019: BDOC checks ************************** |
001 | Provide at least one BDoc field |
002 | &1 is a mandatory parameter |
003 | Enter a name and assign a data element for provided BDoc fields |
004 | BDoc field generation failed |
005 | CDB table for BDoc &1 and segment &2 cannot be determined |
006 | BDoc not found in any transport request |
007 | BDoc &1 is ignored because its package (&2) is transportable |
008 | BDoc generation raised a dynpro |
009 | Only Z is supported as the namespace for BDocs, but &1 was used |
010 | Segment &1 exists in BDoc &2; choose another name for the segment |
011 | &1 is a messaging BDoc, but a synchronous BDoc was requested |
012 | Provide a parent segment for a segment extension |
013 | Software component &1 must be changable to enhance the middleware (BDocs) |
014 | Namespace &1 must be changable to enhance the middleware (BDocs) |
020 | *****021 - 030: BDOC cluster************************** |
021 | BDoc &1 activation failed |
040 | *****041 - 050: BWA fields ************************** |
041 | BWA DataSource field &1 generation failed |
042 | BWA DataSource field generation raised a dynpro |
043 | BWA DataSource not found |
060 | *****061 - 069: BDOC field elements checks************************** |
061 | BDoc & not found |
062 | Segment &1 not found for BDoc &2 |
070 | CDB table for &1 |
100 | *****100 - 199: OLTP Reporting ************************** |
101 | No BI client specified in system customizing |
102 | Error in OLTP reporting generation |
103 | RFC error: &1&2 |