Introduction
This blog post introduces a recent enhancement in SAP Document and Reporting Compliance for Türkiye in SAP S/4HANA Cloud Public Edition. It has been designed to improve the performance and user experience of retrieving registered user list for the eInvoice and eDelivery/eDespatch processes for customers whose service provider is SOVOS.
Background
In Türkiye, if your business exchanges electronic invoices and electronic delivery notes, you must maintain an up-to-date list of registered users. This list lets you check whether your trading partner is officially registered with the tax authority as an electronic user.
Traditionally, if you were using SAP Document and Reporting Compliance for Türkiye, you relied on two separate applications to retrieve this user list information:
Retrieve Delivery Note UsersRetrieve eInvoice Users
These applications populate the corresponding SSCUI configuration tables, which are consumed by the eInvoice and Delivery Note processes:
Default Partner Alias for eInvoicing (ID: 103088) Define Default Partner Alias for Delivery Notes (103104)
Limitations of the existing approach:
In the S/4 Public Cloud environment, unlike the Private Cloud, heap memory extension is not possible. Performance – As the number of registered users in Türkiye continues to grow, the existing solution is not optimized to efficiently process large user lists, which can result in longer execution times and reduced system performance.
What’s New?
To address the limitations above, SAP has introduced an alternative approach for SOVOS customers to retrieve user lists. User list retrieval is now integrated into the standard Process eDocument Inbound Messages application, the same application that you already use for processing incoming e-documents as part of business operations.
Key enhancements:
Improved performance — Large user lists are now processed in chunks, enabling efficient retrieval and persistence even for high volumes of registered users. Unified User Experience – User list retrieval is performed through the same Process eDocument Inbound Messages application used for other inbound e-document processes, providing a consistent and streamlined experience. Automatic Submission and Persistence – The system automatically requests, receives, processes and persists in the retrieved user list without requiring any additional user action. Full Traceability – Technical eDocuments are created in the Manage Electronic Documents application, providing complete traceability through detailed application logs and a history tab that displays information such as the request file, file name, and correlation ID.
Two new message types have been introduced to drive the user list pull through the Process eDocument Inbound Messages application:
ProcessMessage TypeDelivery NoteTR_DLN_USERLIST_PULL eInvoiceTR_INB_USERLIST_PULL
Prerequisites
This enhancement is available only for SAP S/4HANA Cloud Public Edition. As a customer, you must use SOVOS as the service provider for Türkiye Document and Reporting Compliance. Source type PULL needs to be activated for the company code in the relevant SSCUI. Customers should edit the respective communication arrangement of both eInvoice and eDespatch and deploy the same to get the new API changes.
New Process to Retrieve the User List
The user list retrieval process is now fully integrated into the Process eDocument Inbound Messages application. The following steps describe how to execute the process. Subsequent sections explain how to monitor the results using the Manage Electronic Documents, Application Log, and History tab.
Running the Inbound Message Handler
Open the Process eDocument Inbound Messages application.
Enter the Company Code. Enter the Country/Region as Türkiye (TR). Select one or both of the following actions:
Get Available Messages – Specify the Received-On date to retrieve new messages from SOVOS. Process Existing Messages – Specify the Received-On date to process messages that have already been retrieved.
You can execute either action independently, run them sequentially (first Get Available Messages, then Process Existing Messages), or execute both actions in a single run. Select the appropriate Message Type:
TR_DLN_USERLIST_PULL – Retrieves eDelivery Note users. TR_INB_USERLIST_PULL – Retrieves eInvoice users.
Click Execute to start the process.
The example below illustrates the configuration required to retrieve the eInvoice user list using the Process eDocument Inbound Messages application and the TR_INB_USERLIST_PULL message type. This is provided as an example only. The same configuration steps can be followed to retrieve the eDelivery Note user list by using the TR_DLN_USERLIST_PULL message type.
Once the process is executed, the system:
Creates technical eDocuments in the Manage Electronic Documents. Automatically updates the SSCUIs Default Partner Alias for eInvoicing (ID: 103088) and Default Partner Alias for Delivery Notes (103104) with the latest user list data. Handle auto-submission of technical eDocuments, you do not need to take any further action.
Scheduling the Job
To ensure that the user list remains up to date, SAP recommends scheduling the process at a frequency that meets your business requirements.
Create separate scheduled jobs for:
eInvoice user list retrieval using message type TR_INB_USERLIST_PULL eDelivery Note user list retrieval using message type TR_DLN_USERLIST_PULL
The scheduling frequency can be configured according to business needs.
Monitoring in the eDocument Cockpit
Once the message handler is executed, the corresponding eDocuments will be visible in the eDocument Cockpit. The two flows can be distinguished by the Type Description:
ProcessType DescriptionUser List Download Request (eInvoice) Türkiye Incoming Pull Req Inv User List Download Request (eDelivery Note) Türkiye Incoming Pull Req Deln
These are technical eDocuments only. No business documents (such as invoices or delivery notes) are created. The eDocuments serve as tracking records and for audit purposes for the user list retrieval process.
Process Statuses
The eDocument can have the following key process statuses:
User List Processed — The user list pull and persistence completed successfully. User List Unprocessed — Something went wrong during the flow. The exact error can be reviewed in the Application Log.
Application Log
The Application Log provides a detailed overview of each execution run. For each processed chunk, the log displays the following information:
Total number of users retrieved The number of users persisted (newly added). The number of users updated. Number of users deleted.
History – Request File
The history tab of the eDocument provides access to the request file associated with each retrieval run. The request file provides important technical metadata, including:
Correlation ID (only specific to SOVOS) — Enables end-to-end tracing of a specific chunk throughout the processing flow. File name — Identifies the file received from the SOVOS service.
Note: The file name is generated and provided by SOVOS. SAP does not control or modify the file name, the system stores the file name exactly as received from the service provider.
Summary
With this enhancement, the user list retrieval processes in SAP Document and Reporting Compliance for Türkiye have been integrated into the standard Process eDocument Inbound Messages application. As a result, customers using SOVOS as their service provider can use the Process eDocument Inbound Messages application as a primary process and keep the existing Retrieve eInvoice Users and Retrieve Delivery Note Users applications as an alternative.
Key takeaways:
Use TR_INB_USERLIST_PULL for eInvoice and TR_DLN_USERLIST_PULL for Delivery Note. SSCUIs Define Default Partner Alias for eInvoicing (ID: 103088) and Define Default Partner Alias for Delivery Notes (103104) are populated automatically when the application is run. Schedule the report once per process based on your business requirements. Monitor processing through the technical eDocuments generated in the Manage Electronic Documents, identified by their respective document type descriptions. Submission and processing are handled automatically by the system, eliminating the need for manual intervention.
This change provides a more performant, transparent, and unified experience for SOVOS users managing their Türkiye compliance flows.
IntroductionThis blog post introduces a recent enhancement in SAP Document and Reporting Compliance for Türkiye in SAP S/4HANA Cloud Public Edition. It has been designed to improve the performance and user experience of retrieving registered user list for the eInvoice and eDelivery/eDespatch processes for customers whose service provider is SOVOS.Background In Türkiye, if your business exchanges electronic invoices and electronic delivery notes, you must maintain an up-to-date list of registered users. This list lets you check whether your trading partner is officially registered with the tax authority as an electronic user. Traditionally, if you were using SAP Document and Reporting Compliance for Türkiye, you relied on two separate applications to retrieve this user list information: Retrieve Delivery Note UsersRetrieve eInvoice Users These applications populate the corresponding SSCUI configuration tables, which are consumed by the eInvoice and Delivery Note processes:Default Partner Alias for eInvoicing (ID: 103088) Define Default Partner Alias for Delivery Notes (103104) Limitations of the existing approach: In the S/4 Public Cloud environment, unlike the Private Cloud, heap memory extension is not possible. Performance – As the number of registered users in Türkiye continues to grow, the existing solution is not optimized to efficiently process large user lists, which can result in longer execution times and reduced system performance. What’s New? To address the limitations above, SAP has introduced an alternative approach for SOVOS customers to retrieve user lists. User list retrieval is now integrated into the standard Process eDocument Inbound Messages application, the same application that you already use for processing incoming e-documents as part of business operations. Key enhancements: Improved performance — Large user lists are now processed in chunks, enabling efficient retrieval and persistence even for high volumes of registered users. Unified User Experience – User list retrieval is performed through the same Process eDocument Inbound Messages application used for other inbound e-document processes, providing a consistent and streamlined experience. Automatic Submission and Persistence – The system automatically requests, receives, processes and persists in the retrieved user list without requiring any additional user action. Full Traceability – Technical eDocuments are created in the Manage Electronic Documents application, providing complete traceability through detailed application logs and a history tab that displays information such as the request file, file name, and correlation ID. Two new message types have been introduced to drive the user list pull through the Process eDocument Inbound Messages application: ProcessMessage TypeDelivery NoteTR_DLN_USERLIST_PULL eInvoiceTR_INB_USERLIST_PULL PrerequisitesThis enhancement is available only for SAP S/4HANA Cloud Public Edition. As a customer, you must use SOVOS as the service provider for Türkiye Document and Reporting Compliance. Source type PULL needs to be activated for the company code in the relevant SSCUI. Customers should edit the respective communication arrangement of both eInvoice and eDespatch and deploy the same to get the new API changes. New Process to Retrieve the User List The user list retrieval process is now fully integrated into the Process eDocument Inbound Messages application. The following steps describe how to execute the process. Subsequent sections explain how to monitor the results using the Manage Electronic Documents, Application Log, and History tab. Running the Inbound Message Handler Open the Process eDocument Inbound Messages application. Enter the Company Code. Enter the Country/Region as Türkiye (TR). Select one or both of the following actions: Get Available Messages – Specify the Received-On date to retrieve new messages from SOVOS. Process Existing Messages – Specify the Received-On date to process messages that have already been retrieved. You can execute either action independently, run them sequentially (first Get Available Messages, then Process Existing Messages), or execute both actions in a single run. Select the appropriate Message Type: TR_DLN_USERLIST_PULL – Retrieves eDelivery Note users. TR_INB_USERLIST_PULL – Retrieves eInvoice users. Click Execute to start the process. The example below illustrates the configuration required to retrieve the eInvoice user list using the Process eDocument Inbound Messages application and the TR_INB_USERLIST_PULL message type. This is provided as an example only. The same configuration steps can be followed to retrieve the eDelivery Note user list by using the TR_DLN_USERLIST_PULL message type. Once the process is executed, the system: Creates technical eDocuments in the Manage Electronic Documents. Automatically updates the SSCUIs Default Partner Alias for eInvoicing (ID: 103088) and Default Partner Alias for Delivery Notes (103104) with the latest user list data. Handle auto-submission of technical eDocuments, you do not need to take any further action. Scheduling the Job To ensure that the user list remains up to date, SAP recommends scheduling the process at a frequency that meets your business requirements. Create separate scheduled jobs for: eInvoice user list retrieval using message type TR_INB_USERLIST_PULL eDelivery Note user list retrieval using message type TR_DLN_USERLIST_PULL The scheduling frequency can be configured according to business needs. Monitoring in the eDocument Cockpit Once the message handler is executed, the corresponding eDocuments will be visible in the eDocument Cockpit. The two flows can be distinguished by the Type Description: ProcessType DescriptionUser List Download Request (eInvoice) Türkiye Incoming Pull Req Inv User List Download Request (eDelivery Note) Türkiye Incoming Pull Req Deln These are technical eDocuments only. No business documents (such as invoices or delivery notes) are created. The eDocuments serve as tracking records and for audit purposes for the user list retrieval process.Process Statuses The eDocument can have the following key process statuses: User List Processed — The user list pull and persistence completed successfully. User List Unprocessed — Something went wrong during the flow. The exact error can be reviewed in the Application Log. Application Log The Application Log provides a detailed overview of each execution run. For each processed chunk, the log displays the following information: Total number of users retrieved The number of users persisted (newly added). The number of users updated. Number of users deleted. History – Request File The history tab of the eDocument provides access to the request file associated with each retrieval run. The request file provides important technical metadata, including: Correlation ID (only specific to SOVOS) — Enables end-to-end tracing of a specific chunk throughout the processing flow. File name — Identifies the file received from the SOVOS service. Note: The file name is generated and provided by SOVOS. SAP does not control or modify the file name, the system stores the file name exactly as received from the service provider. SummaryWith this enhancement, the user list retrieval processes in SAP Document and Reporting Compliance for Türkiye have been integrated into the standard Process eDocument Inbound Messages application. As a result, customers using SOVOS as their service provider can use the Process eDocument Inbound Messages application as a primary process and keep the existing Retrieve eInvoice Users and Retrieve Delivery Note Users applications as an alternative. Key takeaways: Use TR_INB_USERLIST_PULL for eInvoice and TR_DLN_USERLIST_PULL for Delivery Note. SSCUIs Define Default Partner Alias for eInvoicing (ID: 103088) and Define Default Partner Alias for Delivery Notes (103104) are populated automatically when the application is run. Schedule the report once per process based on your business requirements. Monitor processing through the technical eDocuments generated in the Manage Electronic Documents, identified by their respective document type descriptions. Submission and processing are handled automatically by the system, eliminating the need for manual intervention. This change provides a more performant, transparent, and unified experience for SOVOS users managing their Türkiye compliance flows. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
