We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
Version 9.32304 of the ASAPIO Integration Addon contains the following changes:
Changes to ASAPIO Integration Add-on core framework:
New BAdI added to the events trigger FM. Allows clients to adjust keys, perform additional checks, add custom logic, etc.
see Event Trigger BAdI Documentation
It is now possible to have separate jobs (and therefore settings) per interface (Instance / Object)
see also: Active Alerting Documentation
The way the existing formatting options are configured has changed with the addition of the new options. A conversion program exists to convert existing configurations to the new style.
see Formatting Options Documentation
Export an AsyncAPI specification for outbound interfaces
Works with DB-view and PayloadDesign based extractions
see also https://asapio.com/docs/asyncapi/
In the configuration it is checked if the RFC destination exists.
New action in the ACI Monitor to release the lock from the integration run.
Changes to ASAPIO Connector for Confluent / Kafka:
Documentation on necessary settings
Changes to ASAPIO Connector for SAP Event Mesh:
Settings see SAP Help
Changes to ASAPIO Connector for SAP Fieldglass Integration:
When configuring the full load object as a reference to an incremental load object, the incremental interface checks the last run of the full load interface and removes all change pointers that have been created before that time.
With the new Feature Pack the Add-on utilizes the Invoice Response Upload Connector from Fieldglass to send responses to the invoice. Approved when invoice in SAP ERP was created successfully and Rejected when invoice couldn’t be posted.
As per SAP documentation the range 1-1000 for package numbers are reserved in the system that they can be used temporaly by BAPI’s (ie. Creation of Purchase Requisition). Nevertheless, there’re cases where those numbers are already on the DB (tables ESUH and ESLL) of the customer’s system.
The Add-On checks the numbers existing on the DB and recalculates the numbers that are temporaly added during the mapping of the structures and tables for the various BAPI’s.
When the cost center has a responsible user maintained, the user is validated by the Add-On if applicable for Fieldglass. In prior FP’s the extraction raised an error message when user wasn’t valid. Now the extraction looks up for the configured default user, replaces it and adds the cost center to the extract.
The Add-On has been extended to support Buyer Code lengths up to 6 characters.
Service Receipts pulled from Assignment Management module can contain entries with zero rates or zero billable amounts. This is causing errors posting Service Entry Sheets.
A new filter function has been implemented to remove such entries from the Service Receipt and post only such values to the SES which are submitted with real values.
A new interface has been added to the solution. If customer uses ERS (Evaluated Receipt Settlement) instead of FG invoicing, the Add-On sends the ERS invoice to Fg utilizing the ERS Invoice XML Upload Connector.
A new customizing table has been added to support customers that are not using SAP standard account assignment categories (ie. K, F, P, N). Custom AAC’s can be mapped to the standard AAC’s and Add-Ons converts the values.
A new interface has been added to upload contracts/outline agreements with its services into the contract lookup of Fieldglass.
The System ID which is typically only added in a multi-backend landscape was now added as default to all master data interfaces. This also helps in landscapes where several backend systems are connected to the FG test tenant.
0 Votes
0 Comments