xSuite Helix support
To support the xSuite Helix offering, some additional functionalities are now available.
Implicit training
After posting or parking an xSuite Interface document, data that has been changed in the validation can be reported back to the xSuite Helix system, allowing the Helix data extraction to learn these changes automatically.
Data is considered changed if the values transferred to the SAP document differ from the values originally transferred to the xSuite Interface table /WMD/IFIVH.
The training takes place automatically in the background. Any errors that may have occurred are written to the xSuite trace. No message will appear in the UI.
For such training to take place, the following parameters must be set for the relevant record type in record-type customizing (transaction /WMD/FP_RTYPE):
Parameter | Parameter value |
|---|---|
HELIX_SYSTEM | Fully qualified hostname of the Helix system |
HELIX_PORT | HTTP port of the Helix system |
HELIX_PROJECT | Name of the Helix data extraction project |
HELIX_SCENARIO | Name of the Helix data extraction scenario |
The following values are trained:
SAP field name | Helix field name |
|---|---|
BLDAT | DocumentDate |
XBLNR | InvoiceNumber |
CUST13 | Custom1 |
CUST14 | Custom2 |
CUST15 | Custom3 |
CUST16 | Custom4 |
CUST17 | Custom5 |
This function is implemented by class /WMD/CL_FP_HELIX. The actual call of the training takes place in the method UPDATE_TRAINING, which is called at the end of the method POST_DOC or PARK_DOC from the xSuite Interface model class.
SAP queries for data extraction
Some data from the SAP system is required to support Helix data extraction. It is called by the Helix system using function module /WMD/BC_EXECUTE_QUERY.
The following queries are available in the user group /WMD/QUERY for the Helix platform:
Query | Description |
|---|---|
MD_VENDOR_365 | Supplier data |
MD_PO_365 | Purchase order items |
MD_CCTR_365 | Cost center master data |
MD_CUST_365 | Customer data |
MD_GLAC_365 | G/L account master data |