Summary
The following enhancement to STEP's data exchange functionality have been made as part of the 2024.3 update.
-
An optimization to hotfolder performance has been made, which should reduce the overhead of accessing and sorting files in a hotfolder.
These enhancements are also part of the update and are described further in the Details section that follows:
-
The new and improved SFTP delivery method, available for OIEPs and Export Manager, expands the type of cryptographic keys allowed and includes a connection timeout. The original SFTP delivery method, renamed as 'SFTP (Deprecated),' remains unchanged in this update.
-
New Stibo Systems guidelines simplify SAP integration by providing step-by-step instructions to reduce complexities and accelerate integrations with SAP and migrations from SAP R3/ECC to S/4HANA.
-
A new REST Direct receiver for IIEP configurations is available, which returns the ID of the import process so that progress may be tracked by the user.
-
Enhanced error logging in STEP now allows the optional inclusion of detailed HTTP error responses from OIEPs, enabling faster root cause identification.
-
AutoCare PIES Importer is enhanced to include product-controller referencing for improved data tracking.
Details
Improved SFTP delivery method
For outbound integration endpoints (OIEPs) and Export Manager, the new and improved SFTP delivery method allows the use of ED25519, ECDSA, RSA-SHA2-256, and RSA-SHA2-512 cryptographic keys. Also, both an OIEP and Export Manager using the new SFTP delivery method now include an automatic connection timeout that cancels the delivery attempt if processing is halted for more than 30 seconds. Proxy server functionality is not supported. For an OIEP, the timeout sets the process to a 'Failed' stated to alert the user that attention is needed to resume processing.
With these changes, the original SFTP delivery method is now renamed to 'SFTP (Deprecated),' but the functionality is unchanged. When using the deprecated delivery method, only RSA encryption is allowed, and there is no connection timeout. Without a timeout, a process that is halted goes to a 'Disabled' status. No change is required by customers who already use the 'SFTP (Deprecated)' delivery method. However, it is recommended to use the new SFTP delivery method to take advantage of the increased functionality.
For more information, refer to the Export Manager SFTP Delivery Method topic and the OIEP SFTP Delivery Method topic, both in the Data Exchange documentation.
New Product MDM SAP integration guidelines available
Customers now have access to comprehensive SAP integration guidelines for Product MDM that explain how STEP can reduce the complexities of SAP integration and accelerate migrations from R3/ECC to S/4HANA.
Integrating with SAP is often complex and time-consuming, posing challenges for customers seeking a seamless integration. The new step-by-step guidelines simplify the integration process by outlining recommended implementation approaches (along with their limitations) for the most common use cases and addressing associated challenges. The guidelines ensure simple, effective, and efficient implementations that meet market demands.
To access the guidelines, refer to the Accelerating SAP R3/ECC to S/4HANA Migrations and Reducing End-to-End Complexities topic in the Product MDM Solution Enablement documentation.
New REST Direct Receiver
A new Inbound Integration Endpoint (IIEP) Receiver called REST Direct is now available, offering users an easier method of importing files via REST calls. Unlike the existing REST Receiver, which requires that the files be uploaded to a hotfolder before import, the REST Direct receiver sends a REST call that immediately generates a new import process. As soon as the REST call is made, a background process ID is provided so that users can check on the progress of the import.
Previously, when working with REST Receiver, there was no way to identify the relevant background process as no ID was provided.
For more information, refer to the REST Direct Receiver topic in the Data Exchange documentation.
Improved error logging when HTTP errors occur in OIEPs using REST
When integrating with third-party systems using an outbound integration endpoint (OIEP) and the REST delivery method, the OIEP may respond with HTTP errors, where the error details are in the HTTP response body. To facilitate quick identification of the root cause of the error, it is now possible to include the HTTP response body in the BGP execution report in STEP.
Since some integrations may contain customer-sensitive information in the response body, the inclusion of the HTTP response body on error is an optional setting when configuring the REST and REST Direct delivery methods.
For more information, refer to the topics REST Delivery Method and REST Direct Delivery Method in the Outbound Integration Endpoints section of the Data Exchange documentation.
AutoCare PIES Importer now includes product-controller referencing
The PIES Importer can now be configured to create references between imported products and their corresponding import controllers. Users have to configure the import flow framework to establish multiple references, allowing each product to link with its associated controllers. This enhancement improves tracking and feedback on imported products, offering better statistical insights and streamlined data merging. This becomes more valuable for managing data within the golden record system. The system fully supports multiple controller references for each product.
For more information, refer to the Conversion State topic in the Solution Enablement: Product MDM for Automotive documentation.