/PF1/MSG_PO_E - Message class for messages related to entity layer for PO
The following messages are stored in message class /PF1/MSG_PO_E: Message class for messages related to entity layer for PO.
It is part of development package /PF1/PO_ENTITY_LAYER in software component FIN-FSCM-PF. This development package consists of objects that can be grouped under "PO Processing Entity Layer".
It is part of development package /PF1/PO_ENTITY_LAYER in software component FIN-FSCM-PF. This development package consists of objects that can be grouped under "PO Processing Entity Layer".
Message Nr ▲ | Message Text |
---|---|
001 | Technical error in method &1 of class &2 |
002 | Payment item was not found in payment order |
005 | Range object &1: number range &2 not maintained |
006 | Change is relevant for release; object submitted to release workflow |
007 | No data provided for order creation |
008 | Clearing area not provided |
009 | Order type not provided |
015 | Payment order date not provided |
016 | Payment order number not provided |
045 | Error when retrieving information of PO structure |
061 | Failure adding order to recall matching table |
070 | Valid-from-date is bigger than valid-to-date |
072 | Invalid service level agreement status |
073 | Invalid service level agreement type |
075 | Segment ID is missing in SLA type segment |
076 | There is already one SLA in clearing area &1 |
077 | Invalid SLA hierarchy; simultaneous definition of group and segment |
078 | Invalid segment name &1 |
079 | Invalid customer account field combination &1/&2 &3 &4 |
080 | Invalid customer ID; specify account or customer ID (BP) |
081 | Invalid rule set ID |
082 | SLA type cannot be changed |
108 | Error during status update at item of payment order &1 |
109 | Error during status update of payment order &1 |
114 | Matching recall &2/&1 found |
115 | Error during status update of item &1 |
127 | Update recall matching table for item &1 &2 &3 |
131 | Specified recall status is not valid |
144 | Payment order &1 could not be edited because it is in release process |
145 | Payment order &1 could not be removed from payment group |
146 | Payment orders were successfully removed from payment group |
150 | No object has been recalled so far |
152 | Recall status &1 was successfully reached |
161 | Recall &1 activated; matching items &2, processed items &3 |
162 | Incomplete activation of recall &1; reactivation necessary |
203 | Field &1 should be filled for SLA &2 |
204 | Bank key &1 does not exist for country/region &2 |
208 | BIC &1 is not valid; please replace with a valid value |
209 | Customer account with &1: &2 is already associated to SLA &3 |
211 | Cannot activate customer SLA &1 without assigned accounts |
224 | Invalid recall type |
226 | Recall type is missing |
230 | Recall &1 matches payment item &2 for clearing area &3 |
236 | Item &3/&4 was previously dismissed for recall &1/&2 |
252 | Company code &1 is already associated to segment &2 |
253 | Company code &1 is already associated to group &2 |
399 | Lock request has failed |
703 | Error occurred while reading data of order &1 / &2 / &3 |
744 | Status transition not allowed: recall state already legally active |
745 | Recall &1 is already processed and can only be legally deactivated |
746 | Recall matched with payment order |
748 | Payment matched by recall &1 but is locked by another process |
749 | Recall matched payment &2 but was locked by another process |
750 | Recall &1/&2/&3 activation will be retried |
751 | Recall &1/&2/&3 activation failed |
752 | Recall &1 with current status &2 cannot be activated |
753 | Recall activation failed because payment order &1 is locked |
754 | Recall &1 requires manual reactivation |
755 | Recall activation failed because batch &1 is locked |
756 | Object is locked; retry takes place in 2 seconds |
757 | Cannot update payment item &1 due to lock |
758 | Update failed; obsolete object version is presented |
760 | Multiple matches for recall with automatic processing option unique |
763 | Non-recallable matches found for recall |
764 | Incomplete recall matching of recall &1 with PI &2 due to status &3 |
767 | Recall conversion failed due to order status |
768 | Postprocessing reaction successfully executed for payment recall |
769 | Postprocessing reaction failed for payment recall |
770 | Finalization reaction successfully executed for payment recall |
771 | Finalization reaction failed for payment recall |
800 | Clearing area is missing |
896 | Duplicate accounts assigned to group SLA |
897 | Duplicate accounts assigned to segment SLA |
899 | Calendar for duplicate check not maintained |