Message type: E = Error
Message class: FQ - Payment Requests and Payment Program
Message number: 847
Message text: Document &1 &2 &3 (lot number &4) not parked
FI document &V1& (company code &V2&, fiscal year &V3&) which contains
the request with lot number &V4& is not a parked document.
The requested processing cannot be carried out.
Check the document key.
Error message extract from SAP system. Copyright SAP SE.
FQ847
- Document &1 &2 &3 (lot number &4) not parked ?The SAP error message FQ847 indicates that a document (such as an invoice or a financial document) related to a specific lot number is not parked. This error typically arises in the context of financial accounting and inventory management within SAP, particularly when dealing with materials that are tracked by lot numbers.
Cause: Document Not Parked: The primary cause of this error is that the document in question has not been parked. In SAP, parking a document means that it is saved in a temporary state and can be edited or posted later. Lot Number Issues: The lot number specified may not be valid, or there may be issues with the lot number's status (e.g., it may be blocked or not available for posting). Authorization Issues: The user may not have the necessary authorizations to park or post documents related to the specified lot number.
Configuration Issues: There may be configuration settings in the system
Get instant SAP help. Sign up for our Free Essentials Plan.
FQ846
Requested function not (yet) supported
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FQ845
Posting request & & not permitted
What causes this issue? Request &V1& (company code &V2&) has not yet been approved.System Response It is therefore not possible to p...
FQ848
Changing request & & not permitted
What causes this issue? You are not allowed to change request &V1& &V2& because it has already been approved.System Response Making ...
FQ849
Create with reference: Request category &1 does not match category &2
What causes this issue? You have tried to create a request with request category &V2& and used request category &V1& as a reference...
Click on this link to search all SAP messages.