Skip to main content
26.3
Search
Search ONESOURCE Global Trade Help and Support.

This article applies to:

  • Product: ONESOURCE Global Trade

ERP Integration - SAP

Material Sent to SAP Without a Detailed Description in Some Cases

Applies to
: SAP GTM Integration – Material interface
What was fixed?
 When a material didn't have a detailed description filled in, the interface was sending the field empty to SAP instead of using the material's summary description as a fallback, as it did before. This fix restores that fallback: whenever the detailed description is empty, the summary description is used in its place.
Technical Data
:
PL/SQL
  • Changed sap_bg_produto_descricao.sql
  • Restored the fallback rule for the P_DESCRICAO_DETALHADA field

I103X Not Updating Partner Status When Using Direct Processing (Process Type B)

Applies to
: SAP GTM Integration – I103X (Partner Status Update / /SFTCMX/RPS_PARTNERS_STATUS)
What was fixed?
 When partners were processed directly (Process Type B), the STATUS field on the source table was never updated — that step only ran as part of the separate batch (Process Type T) flow. This is now corrected: the status update runs immediately for direct processing too.
Technical Data
:
ABAP
  • Changed function module
    /SFTCMX/RPS_PARTNERS_STATUS
  • Changed include
    /SFTCMX/DO103FX_PROXY_RPS
  • Changed include
    /SFTCMX/DI103FX
  • Changed function module
    /SFTCMX/FI103X_PROC_DADOS

Syntax Error When Processing Long Material Text Descriptions

Applies to
: SAP GTM Integration – Material interface (
/SFTCMX/O101X
)
What was fixed?
 When a material's text description needed to be split across multiple lines because it was too long, the interface could crash with a syntax error instead of completing the split. This has been corrected so long descriptions are processed normally.
Technical Data
:
ABAP
  • Changed include
    /SFTCMX/DO101FX
  • Replaced the invalid inline comparison
    if vl_indice >= c_max_chars_per_line - 50 and vl_indice < c_max_chars_per_line.
     with a pre-calculated variable
    vl_limite_quebra
     and explicit parentheses:
    if ( vl_indice >= vl_limite_quebra ) and ( vl_indice < c_max_chars_per_line ).