/PF1/MSG_MBC - MBC Connector Integration
The following messages are stored in message class /PF1/MSG_MBC: MBC Connector Integration.
It is part of development package /PF1/SIN_FSN in software component FIN-FSCM-PF. This development package consists of objects that can be grouped under "Service Inbound FSN".
It is part of development package /PF1/SIN_FSN in software component FIN-FSCM-PF. This development package consists of objects that can be grouped under "Service Inbound FSN".
Message Nr ▲ | Message Text |
|---|---|
| 001 | No MBC message type assignment found in configuration for schema &1 |
| 002 | No MBC message type assignment found for DMEE format tree &1 in config |
| 003 | Creating Multi-Bank Connectivity message |
| 004 | Message type &1 determined for MBC message &2 |
| 005 | Receiver ID &1 determined for MBC message &2 |
| 006 | Message ID for Multi-Bank Connectivity message: &1 |
| 007 | Sender ID &1 determined for Multi-Bank Connectivity message &2 |
| 008 | Sending of Multi-Bank Connectivity message &1 triggered |
| 009 | File name &1 determined for MBC message &2 |
| 010 | Receiver ID &1 of MBC message &2 adjusted to &3 |
| 011 | Object list &1 created in advanced payment management |
| 012 | Starting import with converter ID &1 |
| 013 | MBC message created for object list &1 |
| 014 | Clearing area of object list: &1 |
| 015 | No BAM ID found for payment order &1 |
| 016 | No receiver ID found at house bank &1 / &2 |
| 017 | No sender ID found at house bank &1 / &2 |
| 018 | Object of category &1 not expected for receiver ID determination |
| 019 | No converter ID assignment found for message type &1 |
| 020 | Import error in advanced payment management (MBC Message &1) |
| 021 | XSTRING to STRING format conversion |
| 022 | Message cannot be sent to MBC due to an error |
| 023 | Checking relevance of message &1 for Advanced Payment Management |
| 024 | Error during relevance check in Advanced Payment Management: &1 |
| 025 | Error during processing in Advanced Payment Management |
| 026 | Message &1 is relevant for Advanced Payment Management |
| 027 | Message &1 is not relevant for Advanced Payment Management |
| 028 | Scope item 4MT (Advanced Payment Management) is active |
| 029 | Starting import in Advanced Payment Management |
| 030 | Import in Advanced Payment Management finished |
| 031 | Starting input processing in Advanced Payment Management |
| 032 | Input processing in Advanced Payment Management finished |
| 033 | Synchronous processing activated via parameter /PF1/IH_PF_SYNC |
| 034 | Step status set to &1 because of object list status &2 (&3) |
| 035 | APM relation not found for message &1; no status update was made |
| 036 | Unexpected object category provided by Advanced Payment Management: &1 |
| 037 | Invalid XML error returned by Advanced Payment Management: &1 |
| 038 | Original message information added as navigation reference |
| 039 | No batch number found during creation of outgoing MBC message |
| 040 | No EBICS order type determined |
| 041 | Message &1 is locked. Waiting for it to be released. |
| 042 | Message &1 still locked. Processing is aborted. |
| 043 | Message &1 released. Continuing processing. |