Do you have any question about this error?
Message type: E = Error
Message class: G6 - EDI messages in JV
Message number: 073
Message text: No transaction posted for 810 transaction set, see 819 transaction set(s)
This message is informational only. There was no 810 IT1 segments
without corresponding 819 segments, thus no FB01 was posted for this
specific 810.
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.
G6073
- No transaction posted for 810 transaction set, see 819 transaction set(s) ?The SAP error message G6073 indicates that there is an issue with the processing of an 810 transaction set (which typically represents an invoice) because no corresponding transaction has been posted. This error often arises in the context of Electronic Data Interchange (EDI) processes, where transactions are exchanged between business partners.
Cause:
- Missing or Incorrect Data: The 810 transaction set may not have the necessary data or may contain incorrect data that prevents it from being processed.
- No Corresponding 819 Transaction: The error suggests that there is no corresponding 819 transaction set (which typically represents a response or acknowledgment) that confirms the receipt or processing of the 810 transaction.
- Configuration Issues: There may be issues with the EDI configuration in SAP, such as mapping errors or incorrect settings in the partner profiles.
- Processing Sequence: The 810 transaction may have been sent before the necessary preceding transactions were processed, leading to a lack of context for the system to post the transaction.
Solution:
- Check Transaction Data: Review the data in the 810 transaction set for completeness and correctness. Ensure that all required fields are populated and that the data adheres to the expected format.
- Verify 819 Transaction: Check if the corresponding 819 transaction set has been received and processed. If it has not been received, you may need to contact the trading partner to resend it.
- Review EDI Configuration: Ensure that the EDI configuration in SAP is set up correctly. This includes checking the partner profiles, message types, and mapping settings.
- Transaction Processing Sequence: Ensure that the transactions are being processed in the correct order. If necessary, adjust the sequence of transactions to ensure that prerequisites are met before processing the 810 transaction.
- Consult SAP Documentation: Refer to SAP documentation or support resources for specific guidance on handling EDI errors and troubleshooting steps.
Related Information:
If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or a consultant who specializes in EDI processes within SAP.
Get instant SAP help. Start your 7-day free trial now.
G6072
Vendor Function & and Function Item & does not exist.
What causes this issue? Function `CCNP`, Item `AB` not found for Cash Call OR Function `NBIL`, Item `VE` not found for Asset or G/L posting.System Re...
G6071
JIBE/PASC &, Invoice &, Op Month & already processed.
What causes this issue? Only one 810 for a specific JIBE/PASC number, Invoice number and Operations month can be processed. JIBE/PASC number <...
G6074
Withhold Code & for &: &
What causes this issue? This message is informational only. This indicates the withhold code &V1& causing the FB01 to be parked instead of po...
G6075
BDC session & was created.
What causes this issue? An error occurred during the posting of the FB01 transaction. All the EDI mappings were maintained, but an error still occurr...
Click on this link to search all SAP messages.