Do you have any question about this error?
Message type: E = Error
Message class: FAGL_CONF - Configuration of Document Splitting
Message number: 006
Message text: Document type &1 has not been classified
Document type &V1& has not yet been classified with regard to a business
transaction variant.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Classify the document type in Customizing for <LS>document types</>
under <DS:SIMG.FAGL_OBA7_DC>Define Document Types for Entry View</>.
<ZH>Achtung:</>
INCLUDE FAGL_WZ_WARNING OBJECT DOKU ID TX
Error message extract from SAP system. Copyright SAP SE.
FAGL_CONF006
- Document type &1 has not been classified ?The SAP error message FAGL_CONF006 indicates that a specific document type has not been classified in the system. This classification is necessary for the system to process financial documents correctly, particularly in the context of the New General Ledger (New GL) functionality.
Cause:
The error typically arises due to one of the following reasons:
- Missing Classification: The document type specified in the error message has not been assigned a classification in the configuration settings.
- Configuration Issues: The New GL settings may not be properly configured to recognize the document type.
- Custom Document Types: If a custom document type is being used, it may not have been included in the classification settings.
Solution:
To resolve the FAGL_CONF006 error, follow these steps:
Check Document Type Configuration:
- Go to the SAP transaction code OBY6 (for document type configuration).
- Verify if the document type mentioned in the error message is listed and properly configured.
Classify the Document Type:
- Use transaction code OBY6 to classify the document type.
- Ensure that the document type is assigned to the appropriate classification (e.g., "G/L Account Document").
New GL Configuration:
- Navigate to the New GL configuration settings using transaction code SPRO.
- Follow the path: Financial Accounting (New) -> General Ledger Accounting (New) -> Master Data -> Document Types.
- Ensure that the document type is included in the classification settings.
Check for Custom Document Types:
- If you are using custom document types, ensure that they are also classified correctly in the system.
Transport Requests:
- If changes were made in a development environment, ensure that the transport requests are moved to the production environment.
Testing:
- After making the necessary changes, test the document posting again to ensure that the error is resolved.
Related Information:
Transaction Codes:
Documentation: Refer to SAP Help documentation for detailed steps on configuring document types and classifications in the New GL.
Support: If the issue persists after following the above steps, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
By following these steps, you should be able to resolve the FAGL_CONF006 error and ensure that the document type is properly classified in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
FAGL_CONF005
Account key is missing on document splitting rule header &1/&2/&3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAGL_CONF004
Item category &1 is not possible in business transaction &2/&3
What causes this issue? Item category &V1& is already used in business transaction &V2&/&V3& as an item for splitting. Howeve...
FAGL_CONF007
No account was assigned to account key &2 in chart of accounts &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAGL_CONF008
Check Tax Code indicator was not set
What causes this issue? The check run on the splitting rule has found that item category &V4& (which is to be split) is used. However, the &l...
Click on this link to search all SAP messages.