CMM_CMDTY_PLAN - Planning Data Message Class
The following messages are stored in message class CMM_CMDTY_PLAN: Planning Data Message Class.
It is part of development package FIN_CMM_CMDTY_PLAN_EXPOSURE in software component FIN-FSCM-CMM-RSK. This development package consists of objects that can be grouped under "Commodity Hedge Plan Exposure".
It is part of development package FIN_CMM_CMDTY_PLAN_EXPOSURE in software component FIN-FSCM-CMM-RSK. This development package consists of objects that can be grouped under "Commodity Hedge Plan Exposure".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Upload structure must correspond to entity structure |
002 | File for upload is empty |
003 | Field &1 not in business object entity structure and therefore skipped |
004 | File parse partially complete for different reasons. See details |
005 | Error(s) occured while storing data in database |
006 | Entry for field '&1' is missing |
007 | Field '&1' not available for planning data |
008 | Planning data creation via API started |
009 | Planning data creation finished |
010 | Planning data creation by '&1' file upload started |
011 | Entry '&2' in field '&1' is not valid. Field will be cleared |
012 | The Field - '&1' is not assigned. |
013 | Semantic key contains the invaild value '&1' |
014 | A new version of the existing record will be created |
015 | A new record will be created |
016 | An error occured while creating the exposure |
017 | Status has been set to 'Created' |
018 | Authorization check failure |
019 | The same user cannot change status from 'To be Released' to 'Reject' |
020 | The same user cannot change status from 'To be Released' to 'Release' |
021 | Entry '&2' in field '&1' is not valid. Field will be set to -1 |
022 | Entry '&2' in field '&1' is not valid |
023 | Quantity entry '&1' is invalid. Enter a positive value. |
024 | Planning data are duplicated |
025 | Quantity has invalid value |
026 | File upload is not possible. Check the file for correctness. |
027 | Prior planning data with status 'Erroneous' were replaced by a new one |