Message type: E = Error
Message class: EK - IS-U Accounts Receivable and Payable
Message number: 311
Message text: No document type or main/subtransaction defined for charge category &
The charges determined in the dunning run could not be posted
automatically. Possibly, the
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
document typeEnter a document type for charge category &V1& that is permitted for
mass runs.
Assign the charge category a main and sub-transaction.
Error message extract from SAP system. Copyright SAP SE.
EK311
- No document type or main/subtransaction defined for charge category & ?The SAP error message EK311 indicates that there is an issue with the configuration of document types or main/subtransactions related to a specific charge category in the system. This error typically arises in the context of purchasing or procurement processes, particularly when dealing with conditions or charges that are not properly defined in the system.
Cause: Missing Configuration: The error usually occurs when the system cannot find a valid document type or main/subtransaction for the specified charge category. This can happen if: The charge category is not defined in the system. The document type associated with the charge category is not configured correctly. The main/subtransaction settings for the charge category are missing or incorrect. Incorrect Master Data: If the master data (like vendor or material master) is not set up correctly, it can lead to this error when trying to process a transaction. Customizations: If there have been custom developments or changes in the configuration that affect
Get instant SAP help. Sign up for our Free Essentials Plan.
EK310
Charges from category &, amount & & have been posted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EK309
Posting charges to business partner & is not possible
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EK312
Disconnection document & for contract account & already exists
What causes this issue? During a dunning run, a dunning level was reached at which a disconnection document is created. The disconnection document &a...
EK313
No charge schedule defined for dunning procedure &1, dunning level &2
What causes this issue? There are no dunning charges for dunning procedure &V1&, dunning level &V2& because no charge schema has been...
Click on this link to search all SAP messages.