Content
What is provided by SAP?
Standard BAdIs
SAP provides several standard BAdIs that allow customers to modify or enhance standard functionalities in the eDocument Cockpit. Below is a brief summary of the most commonly used ones.
- EDOC_ADAPTOR
Anyone who has ever worked with eDocuments has probably used this BAdI before. It’s the go-to option when you need to modify or add values to the XML (SET_OUTPUT_DATA). But that’s not all it can do
- The BAdI also lets you control whether an eDocument is created at all, independently of the document type (IS_RELEVANT) e.g. Domestic – Foreign.
- You can change the eDocument type (CHANGE_EDOCUMENT_TYPE) e.g. differentiate invoice or credit note with the same accounting document type.
- Or dynamically select a different PDF form (CHANGE_FORM) depending on your custom logic.
- EDOC_PARTNER_CONNECTOR
This BAdI allows you to implement a customer-specific solution for sending eDocuments to your customers via e-mail. It gives you full flexibility in how the delivery is handled and lets you freely design and control the email settings according to your requirements.
- EDOC_INTERFACE_CONNECTOR
Nowadays, these country specific interfaces are usually delivered by SAP, as they are most often used together with SAP Integration Suite or DRC Cloud Edition. That said, this does not change the fact that you can still build a custom connection to any third-party system or even connect directly to your government authority.
- EDOC_CUSTOM_FIELDS
Want to extend the cockpit with additional fields? This is where you can add the logic to populate them.
- EDOC_INCOMING
If you are using a vendor invoice automation, you can forward the received XML or PDF in the way that best fits your process. The documents can be sent via email, SFTP, API, or even directly into the system using add-ons.
On top of the standard BAdIs, here are a few others you’ll probably want to know about:
bgRFC Extended actions
A newer technology that can extend an existing process by plugging in your own custom process. You implement your logic in a function module and get it called once a specific process step has finished.
This makes it easy to add custom behavior, such as validations, data enrichment, or follow-up actions, without changing the standard flow.
Country specific
Some countries come with special requirements, and SAP also provides solutions to support these scenarios. For example, in Italy, eDocuments must be archived with a third-party provider (EDOC_IT_ARCHIVING) or In Mexico, you can add customer-specific addenda directly to the XML.
Custom Extensions for the eDocument Cockpit
Besides building a complete custom solution, there are still other ways to tweak and extend the eDocument Cockpit.
Extra Buttons
Since the eDocument Cockpit uses customizing tables to add buttons to the cockpit, you can take advantage of this mechanism to introduce your own custom buttons. These buttons can then be used to trigger additional functionality or to enrich the XML with extra data, basically whatever your scenario requires.
Custom PDF or SD/FI PDFs in the cockpit
Not a fan of the standard PDF? No problem, SAP let you switch to a custom PDF that fits your needs perfectly. And if you want to go even further, with a bit of tweaking, you can reuse the original SD or FI PDF output, giving you full control over formatting, layout, and the information that gets delivered.
Statuses – processes
Sometimes you need extra statuses or processes, like when a document needs approval before it can be processed. SAP’s Process Manager gives you a flexible framework, handling standard scenarios easily. But the real power comes when you extend it: you can define your own statuses, create custom process steps, and even trigger additional actions based on your business rules. This makes it easy to adapt the cockpit to fit exactly how your organization works.
Conclusion
The eDocument Cockpit keeps improving to keep up with ever-changing compliance requirements. Of course, there are still moments when something seems missing—but that’s where the fun begins. As a developer, I don’t see limitations, I see opportunities. Every requirement, no matter how tricky, can be addressed. Coding is limitless…
How PIKON can help you
With our Competence Center for Legal Requirements, we are a strategic partner who ensures that your SAP system and business processes meet different country-specific legal requirements all over the world in the long run. We have a team of experts that combine SAP expertise and in-depth knowledge of the end-to-end legal process and technical requirements of the Spanish and many other eInvoicing and eAccounting regulations. We have gathered this experience through our many SAP Document & Reporting Compliance and local implementation projects all around the world. Some examples are SDI in Italy, SII in Spain, CFDI and Complemento de Pago in Mexico, RTIR and EKAER in Hungary, XRechnung in Germany, the different legal requirements in Turkey, etc. We have also developed our own compliance SAP Add-Ons e.g. MTD VAT in the UK and the VAT Whitelist in Poland. Furthermore, we always keep an eye on new and changing legal requirements and inform our customers when action is needed. This ensures that your company doesn’t need to follow up on all the legal requirements yourselves, and you can concentrate on your daily business.
Schedule a web meeting
Do you have any further questions about the functionalities of the eDocument Cockpit?
Simply fill out the contact form or leave us a comment at the end of the article.
You are currently viewing a placeholder content from Active Campaign. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information
