FINS_MAP - Management Accounting Platform
The following messages are stored in message class FINS_MAP: Management Accounting Platform.
It is part of development package FINS_HCP_MAP in software component FI-GL-GL. This development package consists of objects that can be grouped under "Management Accounting Platform".
It is part of development package FINS_HCP_MAP in software component FI-GL-GL. This development package consists of objects that can be grouped under "Management Accounting Platform".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Expected Auth Field &1 of Auth Object &2 not specified. |
| 001 | During payload parsing field '&1' was not found. |
| 002 | For authorization object &1 you need to mention authorization field &2. |
| 003 | Payload could not be parsed, potentially syntax error. |
| 004 | Error during certificate parsing: &1. |
| 005 | No certificate was provided in HTTP request. |
| 006 | Queries modifying the database are not allowed. |
| 007 | No database connection specified in customizing table. |
| 008 | Request type not supported. |
| 009 | ERP release version could not be determined. |
| 010 | User not authorized to execute query. |
| 011 | Application Log: &1 |
| 012 | Execution rejected because certificate issuer &1 is not trustful. |
| 013 | Execution rejected because request was sent without certificate (IP &1). |
| 014 | Executed Query Template: |
| 015 | Utilized Query Parameter: Order &1; Type &2; Value &3 |
| 016 | Error auth check: &1 |
| 017 | No authorization check strategy found for authorization object &1. |
| 018 | No payload was sent via HTTP. |
| 019 | No value was specified for field '&1'. |
| 020 | RFC execution rejected because RFC calls from gateway are disabled. |
| 021 | Error during obtaining attributes of RFC context: &1. |
| 022 | RFC execution rejected because RFC call not trustful. Origin:&1, &2, &3 |
| 023 | Error Signature Verification: &1. |
| 024 | Error BAPI: &1. |
| 025 | Error Obtaining User Profile: &1. |
| 026 | Execution rejected because payload was not correctly signed. |
| 027 | Execution rejected becauase environment type could not be determined. |
| 028 | Execution of Remote Function Module &1 triggered. |
| 029 | Execution of Remote Function Module &1 rejected. |
| 030 | Execution rejected: HTTP method used is not allowed |
| 031 | Execution rejected: Request did not use X.509 Authentication Method |
| 032 | Execution rejected: Digital Signature has expired on &1 |