6.9.0.1 Integration for SAP Documentation
Release summary
The 6.9.0.1 release introduces integration for customer down payments through SD Module, supports
MM
logistics invoice verification (LIV) accounting document with more than 999 line items, adds support of new OneSource Indirect Tax Determination fields in Nata Fiscal (Brazil) and CDS view for IDT Tax Data Table, updates the document currency field in tax data table, along with various bug fixes and minor enhancements.For SAP ECC, this release version is compatible with
SAP ECC EHP6 and above.
In this release, validated and tested Global Next release 6.9 to be compatible for the latest
S/4HANA 2023 FPS02.
ONESOURCE Determination Customer Down Payment Settlement (Milestone Billing Plan & Document Conditions) Integration with Global Next
The support for Customer Down Payment settlement solution with both Milestone Billing Plan and Document Conditions within the Sales & Distribution Module has been introduced to seamlessly integrate with ONESOURCE Determination's calculated tax, enabling a Customer Down Payment settlement.
Refer to section Customer Down Payment through SD Module in "Special Functions Configuration Guide" for list of features, instructions, and additional information.
Support for Logistics Invoice (LIV) Accounting Document with more than 999-line items using Document Split
In alignment with SAP's provided BADls and configuration options for posting LIV accounting documents with more 999-line items, developed an integration solution that seamlessly uses the document split functionality provided by SAP ensuring tax calculations and detailed tax information are accurately recorded and processed within the SAP system for large financial documents.This integration leverages SAP's capabilities to efficiently manage large transaction volumes while maintaining compliance and accuracy in tax reporting.
For more detailed guidance and limitations, Refer to Section 'More Than 999 Line Items support in Financial Accounting Document' in 'Special Functions Configuration Guide'.
Support for Two New Fields in Nota fiscal (Brazil)
With this latest release, Global Next Integration has been enhanced to support two new XML fields: CALC_BASIS_MODE (MODBC/MODBCST) and EXCLUDED_PIS_COFINS_AMOUNT, which arecalculated by ONESOURCE Indirect Tax Determination.
In response to recent changes in Brazilian tax legislation, these fields have been introduced to ensure that ICMS state taxes are excluded from the calculation base for social taxes (PIS/COFINS) in specific industries, such as pharmaceuticals. The integration of these fields into the Nata Fiscal SAP document enables companies to comply with the updated tax regulations and perform accurate tax calculations for affected industries. This enhancement ensures compliance with the updated tax regulations and facilitates accurate tax calculations for affected industries.
Support for Document Currency in Tax Data Table
New fields GROSS_AMOUNT _TC, GROSS_AMT _CUR_TC and
T
AX_AMOUNT _T
been introduced in/IDT/D_ TAX_DATA table to support document currency.CDS view for /IDT/D_ TAX_DATA table
A CDS view is now available for the /IDT/D_ TAX_DATA table, aligning with SAP standards. This enhancement allows customers to leverage its capabilities for reporting and other business needs.
FIORI APPS COMPATIBILITY
The Global Next 6.9.0.1 version is compatible with the following applications:
- Apps with the type SAPGUI forHTMLthat support external tax systems.
- Transactional apps supporting external tax systems.
Technical changes
Unable to update /IDT/D_STRUCTS from SM30
Issue:
Unable to update table /IDT/D_STRUCTS due the maintenance class of table.Solution:
Maintenance class of table /IDT/D_STRUCTS has been changed.Cost center data is missing in custom field mapping
Issue:
Custom mapping to pass cost center in PO creation is not working.Resolution:
Code modifications were implemented in the methods SET_COSTCENTER_DATA of class/IDT/JOURNEY_ITEM_REQUEST to populate cost center in PO processing.Shuttle is not deleted in PO creation process when using the same session for subsequent PO creation
Issue:
Global Next Integration shuttle is not getting deleted in PO creation process (ME21N), due to which an inconsistency in tax calculation may occur during subsequent PO creation using the same session.Solution:
Applied a code fix in include /IDT/PURCHASING_BADI_POST to delete the shuttle by identifying the transaction type.Call to determination is not triggering for unplanned Service Entry Sheets ( SES )
Issue:
The call to determination is not initially triggered when unplanned SES services are first entered in ML81N. However, if any changes are made to the unplanned SES line, such as updating the quantity, the tax call is subsequently triggered.Solution:
Modifications were made to the Class/lDT/JOURNEY_NG_ITEM_SERV_ENTR and the method SET_ITM_TRANSACTION_DATA was updated to incorporate unplanned line items into the item tra Discrepancy in Tax Data table during billing cancellation.
Issue:
Tax Data table and Audit entries are not in sync with the tax determined during a billing cancellation, when an exempt certificate was applied after the billing document had already been created.Solution:
A new field was added to the /IDT/D_TAX_DATA table to store the effective zone level, and a mapping was created to populate this field. Additionally, modifications were made to the Class/IDT/JOURNEY_AUDIT_CANCEL and the method BOARD_TRAIN to incorporate the override amount based on the effective zone level stored during billing creation.GN Code correction - WBS Element address issue
Issue:
The check was applied on an incorrect table field when generating addresses for WBS.Solution:
Modifications were made to the Class /IDT/SET_ADDRESS_WBS and the methods SET_ADDRESS_ITM_FI, SET_ADDRESS_ITM_LIV, SET_ADDRESS_ITM_PURCHAS, andSET_ADDRESS_ITM_SES to validate that the value of PRPS-FKSTL is not initial.Adjustment to fetch material data in S/4HANA
Issue:
Performance issue on using MARC in S/4HANA instance. SAP suggests using CDS view V_MARC_MD in S/4HANA.Solution:
Modifications were made to the Class /IDT/INFORMATION_DESK and the method GET_MATERIAL_PLANT_DATA to retrieve material details from the V_MARC_MD CDS view in S/4HANA instances and from the MARC table in ECC instances. Invoices made in batch have the last sale order information for all the items in the request.
Issue:
Invoices processed in batch using background job /foreground are missing accurate sales data in the corresponding item request when processing with multiple sales orders.Resolution:
Code modifications were implemented in the methods COLLECT_CONFIGURED_ADDRESS_ITM and COLLECT_ITM_TRANSACTION DATA of class/IDT/ROUTE_GROUP_BILLING to populate accurate sales information, including VBAK and VBKD details.Rounding off issue - Tax rate in the accounting document
.Issue:
When Global Next summarization is enabled, the rate is recalculated based on the summarizing fields, and if the rate is identical across all lines, a minor discrepancy in cents may occur.Solution:
Modifications were made to the Class /IDT/JOURNEY_STANDARD_RESPONSE and the methodSUMMARIZE_CONDITION_DATA, as well as a local method, to compare rates and update the actual rate if the rates are identical across all lines.Duplicate registration numbers in tax request call for Deferred taxes process in S/4HANA
.Issue:
A duplicate registration number was passed in request to determination, when the same registration number is present in both the Master data tables and the DFKKBPTAXNUM table.Solution: Code
modifications were implemented in the Class /IDT/JOURNEY_HEADER_REQUEST,/IDT/TRAIN_STATION, and the BOARD_TRAIN method, as well as the Class/IDT/JOURNEY_AUDIT_SAVE_FRM_GL and the RUN_GL_POST_BTE_PROCESSES method, to eliminate duplicate registration numbers.Error while processing Utility BAPI
.Issue:
The customer is utilizing the /IDT/BAPI_TAX_CALC_UTILITY to invoke tax call for tax calculation. When ONESOURCE Indirect Tax Determination returns severity 2 error messages, the error is not being captured in the BAPl's return parameters.Solution:
Updates were made to the Class /IDT/BAPI_TAX_CALC_UTILITY (specifically the COLLECT_ERROR_MESSAGE and START methods), the Class /IDT/ROUTE (HANDLE_ERROR_MESSAGEmethod), and the BAPI/IDT/TAX_CALC_UTILITY_BAPI to improve the handling of error messages and ensure more robust error processing.
Wrong tax amounts in Deferred tax process
.Issue:
Addresses are not copied from /IDT/ROUTE_NON_GROUP_DOC_AP and/IDT/ROUTE_NON_GROUP_DOC_AR request to /IDT/ROUTE_NON_GROUP_DOC_DT request while processing deferred tax.Solution:
Code modifications were implemented in the Class /IDT/JOURNEY_AUDIT_SAVE_FRM_GL, specifically in theADJ_DEF_TAX_REV_CHARGE_ADDRESS and RUN_GL_POST_BTE_PROCESSES methods, to ensure that the address is successfully passed from the AP and AR requests to the/IDT/ROUTE_NON_GROUP_DOC_DT request.ONESOURCE Indirect Tax Determination error message is not fully displayed back on SAP transactions
.Issue:
Error message coming back from determination is truncated which is not showing the entire message on SAP transaction during tax determination.Solution:
A fix applied in Method HANDLE_ERROR_MESSAGE from Class /IDT/ROUTE to pass whole message to SAP that displays the full error message to the user without truncating.Dump while running Archival report (/IDT/LOG_ARCHIVE) to extract huge data.
Issue:
A dump occurred while running Archival report (/IDT/LOG_ARCHIVE) due to extraction of huge data.Solution:
The code was refined in Method PROCESS_DATA from Class /IDT/LOG_ARCHIVE to insert the entries for archival.Accounting Balance error in WB2R_SC when driver and target tax codes are same.
Issue:
Accounting Balance error is observed in WB2R_SC when driver tax code and Final tax code is same, for example if both the tax codes are A1, then you see an accounting Balance error.Solution:
Removed the code which compares the tax codes for deleting the extra lines from ACCIT.Code refinement done for deleting the extra lines by checking the extra lines with sum of tax lines for the specific lines in ACCCR and deleting in both ACCCR and ACCIT. Bug notes
This section lists known bugs, workarounds (if applicable) and limitations within the overall Global Next integration.
Issue:
FB60 throws ABAP Dump Fl_
TAX_DISTRIBUTE_AMOUNT.Reason:
It is observed that the issue is happening because of the OSS note 3016863.The code from the note 3016863 would distribute the amounts among all the line items by comparing the tax codes between the
Fl
line item (BSEG) and the tax lines (BSET). At this point the tax codes for BSEG and BSET are different. So, it is not able to distribute the tax amounts correctly. Hence throwing the dump.Workaround:
There is already logic in place in Global Next where the tax code is updated in the Fl line item, but it happens after distributing the tax amounts successfully.Recommended using the same tax code for both driver and target tax codes to fix this issue.
Issue:
'Accounting Interface: Balance in Transaction Currency' while processing settlement processes in S/4HANA using wb2r _sc or wb2r _sv.Action:
If you come across this error, please reach out to customer support or Engineering team for the hotfix.