Do you have any question about this error?
Message type: E = Error
Message class: ME - Purchasing: General Messages
Message number: 747
Message text: No default value found for the document type
During automatic purchasing document creation, the system requires a
default value for the document type, which could not be found.
Processing is canceled.
In Customizing for Purchasing under 'Define Default Values for Document
Type', enter a default value for transaction MB01 (regardless of whether
you work with transaction MB01 or MIGO).
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
ME747
- No default value found for the document type ?The SAP error message ME747 ("No default value found for the document type") typically occurs in the context of purchasing documents, such as purchase orders or purchase requisitions. This error indicates that the system is unable to determine a default document type for the transaction you are trying to execute.
Causes:
- Missing Configuration: The document type may not be configured in the system for the specific purchasing organization or company code.
- User Profile Settings: The user profile may not have a default document type assigned.
- Missing Master Data: The relevant master data (like vendor or material master) may not be set up correctly, leading to the inability to derive a document type.
- Authorization Issues: The user may not have the necessary authorizations to access the document type.
- Custom Development: If there are custom developments or enhancements in the system, they may interfere with the default document type determination.
Solutions:
Check Document Type Configuration:
- Go to the configuration settings in SPRO (SAP Reference IMG).
- Navigate to Materials Management > Purchasing > Purchase Order > Define Document Types.
- Ensure that the relevant document types are defined and assigned to the appropriate purchasing organization and company code.
User Profile Settings:
- Check the user profile settings in transaction SU01.
- Ensure that a default document type is assigned to the user.
Review Master Data:
- Verify that the vendor and material master records are correctly maintained.
- Ensure that the necessary data is available for the purchasing organization and company code.
Authorization Check:
- Use transaction SU53 to check for any authorization issues that may be preventing access to the document type.
- Consult with your SAP security team to ensure the user has the necessary authorizations.
Debugging Custom Code:
- If there are custom enhancements or user exits, review the code to ensure it does not interfere with the document type determination process.
Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
Related Information:
By following these steps, you should be able to identify the root cause of the ME747 error and implement the necessary solutions to resolve it.
Get instant SAP help. Start your 7-day free trial now.
ME746
Delivery costs already settled (Function not possible)
What causes this issue? You have attempted to delete a purchase order item for which settlement has not yet been effected for the relevant goods but ...
ME745
Purchase requisition & cannot be changed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ME748
Supplier is not unique
What causes this issue? During automatic generation of a purchase order, the system found several suppliers. The purchase order header only permits o...
ME749
Rejection of PO item & & with reason &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.