cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

No edocument created in ecockpit (SAP Public Cloud)

Janarthanan
Participant
0 Likes
377

Dear Everyone,

No eDocuments available in edocumetn cockpit, in SAP Public cloud.

I have posted the billing docuemnt XXXX for company Belgium company and Customer has Belgium VAT number in identification and all the neccary configuration has been created inthe system, but still no edocument genreated. Do any face this problem?

SAP Document and Reporting Compliance SAP S/4HANA Cloud Public Edition 

Regards

Janarthanan

Accepted Solutions (0)

Answers (1)

Answers (1)

Andrew
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Janarthan,

I don't have personal experience with this but did some research (Joule for Consultants) and sharing it on - alot seems rooted around the guidance from this blog as a starting point t validate proper setup:
https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/electronic-invoicing-in-...

and I would guess you've already browsed the Belguin HELP documentation? https://help.sap.com/docs/SAP_S4HANA_CLOUD/fba518519f834ed99011786d831ee504/2f9ab027fadc4a52bd2316d3...

These were the joule recommendations though:

Primary Diagnostic Steps

1. Check eDocument Cockpit Status Since you cannot access tables directly in Public Cloud, use the eDocument Cockpit or Manage Electronic Documents app to check the document processing status. Look for any error messages in both the application log (content issues) and interface log (integration issues) - Tobias' blog: https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/electronic-invoicing-in-...

2. Verify Belgium-Specific Configuration The Belgium eDocument implementation requires multiple configuration steps that must be properly implemented [2]. Key areas to verify include:

  • Scope Item Activation: Ensure scope item 5XU (SAP Document and Reporting Compliance) is activated in your system [1]
  • Feature Activation: Activate Document and Reporting Compliance Features through Central Business Configuration (CBC) or Solution Builder [1]
  • Party ID Type Assignment: Confirm your Belgium company code is properly assigned to the BE:VAT party ID type
  • Business Partner Configuration: Verify the customer's Belgium VAT number is correctly assigned as a party ID type [1]
  • eDocument Type Mapping: Check that your billing document type is properly mapped to the Belgium eDocument type (BE_INV for invoices, BE_CRE for credit memos)

3. Configuration Activities Review Navigate through the following configuration sections [1]:

  • General Settings for eDocument: Review all general eDocument configuration activities
  • Belgium-Specific Configuration: Check country-specific settings for Belgium electronic documents

Common Root Causes in Public Cloud

1. Value Mappings Issues Most eDocument submission errors in Public Cloud relate to missing value mappings [1]. Use the Configure Value Mapping app to verify:

  • Navigate to the Belgium namespace
  • Check all required value mapping tables are properly maintained
  • Note that value mappings are not transported and must be maintained separately in each system [1]

2. Master Data Requirements Verify required master data attributes on :

  • Business Partner: Belgium VAT number properly maintained in identification tab
  • Product Master: Required classification codes for Belgium

3. Integration Setup For Belgium, you typically integrate with SAP Document and Reporting Compliance, Cloud Edition or a third-party provider. Verify:

  • Communication arrangements are properly configured
  • Integration flows are active and functioning
  • Service connectivity is established

Troubleshooting Process

  1. Review eDocument Cockpit: Check for any processing errors or status indicators
  2. Validate Configuration: Use the configuration activities to verify all Belgium-specific settings
  3. Check Value Mappings: Ensure all required mappings are maintained for Belgium
  4. Verify Master Data: Confirm VAT numbers and other required data are properly maintained
  5. Test Integration: Verify the connection to your eDocument service provider

If you've reviewed those sources and it's sitll not resolved, I'd recommend a ticket on component FI-LOC-CA-BE

Janarthanan
Participant
Thanks for the help, I found there is activity wrongly created inthe configuration
Andrew
Product and Topic Expert
Product and Topic Expert
0 Likes
Thanks for sharing! If you don't mind please share what needed to be updated and select a solution so we can close this query. Cheers!