Hi everybody,
Recently, we delivered performance improvements for the views of CTR PARTICIPANTE and NF_IMPOSTO_RETIDO in notes 3462516 and 3520967 for SP18 and note 3538136 for SP19. The SAP TDF solution is already up to date to consume the enhancement delivered in the notes, but third-party implementations need to be adjusted to benefit from the performance changes. In this blog post we will describe the new parameters created and provide tips on how the improvements can be consumed.
Optimization of the PARTICIPANTE view
Some information on this view comes from invoices, so we have created the following parameters that can be used to decrease the volume of selected invoices:
P_DT_INI: Start date of the invoice, compared to the Document date (DOCDAT) field. P_DT_FIN: End date of the invoice, compared to the Document date (DOCDAT) field. P_DT_E_S_INI: Start date of the invoice, compared to the TMF Reporting Date (ITMF_REPDAT) field. P_DT_E_S_FIN: Start date of the invoice, compared to the TMF Reporting Date (ITMF_REPDAT) field. P_DO_NOT_USE_ONE_TIME_PARTNER: In case ‘X’ is informed, participants derived in the invoice aren’t considered in the query.
As the information coming from SAP ERP has no date field, the number of registers tends to grow. We recommend using the following PARTICIPANTE fields as filters:
Participant Code (COD_PART) Partner Type (Vendor or Customer) (TIPO_PART)
Using these filters significantly improves your queries involving the PARTICIPANTE view.
Optimization of view NF_IMPOSTO_RETIDO
The NF_IMPOSTO_RETIDO view consists of information coming from the PARTICIPANTE, taxes withheld from FI and invoices. The following parameters can be provided:
P_MANDT: Client filter, relevant for all cases. P_EMPRESA: Company code, relevant for filtering both data coming from invoice and from taxes withheld from FI. P_DT_INI: Invoice start date, compared to the Document date (DOCDAT) field. P_DT_FIN: End date of the invoice, compared to the Document date (DOCDAT) field. P_DT_E_S_INI: Start date of the invoice, compared to the TMF Reporting Date (ITMF_REPDAT) field. P_DT_E_S_FIN: Start date of the invoice, compared to the TMF Reporting Date (ITMF_REPDAT) field. P_DO_NOT_USE_ONE_TIME_PARTNER: In case ‘X’ is informed, participants derived in the invoice are not considered in the query.
Additionally, we recommend the following best practices when accessing the view:
Use the PARTICIPANTE filters mentioned above: COD_PART and TIPO_PART. Perform batch queries by passing multiple tax postings in each query.
We’d love to hear from you. Leave your comment below if you have any questions or suggestions for an upcoming post. And don’t forget to follow the SAP Tax Declaration Framework for Brazil tag here in the SAP Community to get updated about the latest news about the Tax Declaration Framework (TDF).
See you next time!
Rafael Galuschka
SAP TDF Development Team
Hi everybody, Recently, we delivered performance improvements for the views of CTR PARTICIPANTE and NF_IMPOSTO_RETIDO in notes 3462516 and 3520967 for SP18 and note 3538136 for SP19. The SAP TDF solution is already up to date to consume the enhancement delivered in the notes, but third-party implementations need to be adjusted to benefit from the performance changes. In this blog post we will describe the new parameters created and provide tips on how the improvements can be consumed. Optimization of the PARTICIPANTE view Some information on this view comes from invoices, so we have created the following parameters that can be used to decrease the volume of selected invoices: P_DT_INI: Start date of the invoice, compared to the Document date (DOCDAT) field. P_DT_FIN: End date of the invoice, compared to the Document date (DOCDAT) field. P_DT_E_S_INI: Start date of the invoice, compared to the TMF Reporting Date (ITMF_REPDAT) field. P_DT_E_S_FIN: Start date of the invoice, compared to the TMF Reporting Date (ITMF_REPDAT) field. P_DO_NOT_USE_ONE_TIME_PARTNER: In case ‘X’ is informed, participants derived in the invoice aren’t considered in the query. As the information coming from SAP ERP has no date field, the number of registers tends to grow. We recommend using the following PARTICIPANTE fields as filters: Participant Code (COD_PART) Partner Type (Vendor or Customer) (TIPO_PART) Using these filters significantly improves your queries involving the PARTICIPANTE view. Optimization of view NF_IMPOSTO_RETIDO The NF_IMPOSTO_RETIDO view consists of information coming from the PARTICIPANTE, taxes withheld from FI and invoices. The following parameters can be provided: P_MANDT: Client filter, relevant for all cases. P_EMPRESA: Company code, relevant for filtering both data coming from invoice and from taxes withheld from FI. P_DT_INI: Invoice start date, compared to the Document date (DOCDAT) field. P_DT_FIN: End date of the invoice, compared to the Document date (DOCDAT) field. P_DT_E_S_INI: Start date of the invoice, compared to the TMF Reporting Date (ITMF_REPDAT) field. P_DT_E_S_FIN: Start date of the invoice, compared to the TMF Reporting Date (ITMF_REPDAT) field. P_DO_NOT_USE_ONE_TIME_PARTNER: In case ‘X’ is informed, participants derived in the invoice are not considered in the query. Additionally, we recommend the following best practices when accessing the view: Use the PARTICIPANTE filters mentioned above: COD_PART and TIPO_PART. Perform batch queries by passing multiple tax postings in each query. We’d love to hear from you. Leave your comment below if you have any questions or suggestions for an upcoming post. And don’t forget to follow the SAP Tax Declaration Framework for Brazil tag here in the SAP Community to get updated about the latest news about the Tax Declaration Framework (TDF). See you next time! Rafael Galuschka SAP TDF Development Team Read More Technology Blogs by SAP articles
#SAP
#SAPTechnologyblog
