 where I want to go through the new features and functions of the latest release that we released last month. My name is Martin Schöfler, I'm global manager of the SAP integration add-on, and so we have muted everyone, so please if you have questions write them in the chat. There are other colleagues that will see them and if you have time in the end we can answer them on here. If not we will come back to you after the webinar. So we have quite a few things to talk about, so we will first talk about the more general features that we added to the framework that are available for all connectors basically, and then we go into more details on the connector specific features and also on the features for the FITCLAS integration. But we're going to start with the core or framework features that were added that are basically of interest to everyone using the V2. So the first feature I want to talk about is the async API support, so you can now export async API specifications for your outbound interface configurations. So async API is an emerging standard for how to describe where events go, how they look like, what is the schema of the event payload and things like that are part of the async API specification and in a lot of API management tools you can already import them so that you get a better overview or in your typical API management tools also have the event integrations that are available in your environment. So currently this is supported for outbound interfaces you configured using our low code or no code interfaces using database views or the new payload design for extractions. For custom extractors it's not available yet, but we are working with different customers doing custom extractors to see if we could enable it somehow and make the schema available as well. So the next feature is a new enhancement support in our event trigger function module where you can now do things where you previously would need a custom event trigger function module like translating the key from one set of key fields to a different set of key fields like typical scenarios for example the available to promise quantity integrations we have with a few customers where there are various business objects that are triggering that interface, but in the actual interface for the data extraction you typically need a certain set of key fields for the data extraction and to get that you can now implement just a body instead of replacing the whole ACI trigger function module and of course this also opens various other use cases where you want to store additional info on the events and some kind of custom table or do additional things like that when the event is triggered. Then of course there have been quite a few other more minor improvement in fixes but one I wanted to focus on also is the improved formatting options so these are all for our generic database view based extractions in formatting but you have now improved ways to do table and field renaming for example there's a new camel casing options so that you if you have existing database views or have views that use the typical ABAP naming scheme with all uppercase and the words basically separated by underscores you now have an automatic switch to camel casing using the typical rules that are available there for basically uppercasing the letters after the underscore and then or basically everything else is over cased so this is a new option that you that you can activate to get a better readable JSON for the consuming site there's also a new option to skip fields so it was often the case that you had some some database fields that you needed for the joins if you use database views but they were not relevant in your JSON output so you can now skip those so that they are not even put into the JSON and most important you now have an option to influence the nesting of the JSON that is created by the formatter so if you have multiple tables joined together it was always a little bit unclear to the system what should be nested into each other table and there was a really brute force way of doing it but now you can influence what should be basically the parent of each sub table so you get a better hierarchy control on the on the created JSON so these features have been added to all the database view formatters we have so there are a lot of connector specific ones and they all have these new features they should also work the same now besides the connector specific parts of it because we basically consolidated the coding around those but we also while introducing the new payload designer we will talk about in a minute we introduced a new formatter that can handle all these things in one format function module so this can be used for all the connector specific formats as well as for a normal generic database view formatting and can also be used for the new payload designer based extractions so this is the new new format that you should basically use first or try first before you choose some other more specific format and all the new formatting options are also available in that formatting function module yeah I think I already talked a lot about the the body in the trigger so test recap it's mainly used or main use case was for key translation so several use cases we had it required these key translations and now they can be done inside a body implementation and you don't have to rely on or don't have to replace the existing trigger but there are also other use cases to store additional info on the events that was used by some other use cases we saw in the field so this now shouldn't allow you to be closer to standard by using just the body and now coming to the new payload designer so this is a new core highlight feature that is available in the frame right which is a new codeless way to define your extraction and your payload and it just relies on configuration tables on the on the framework side so you don't have to create any database view or any other development objects so no no need for that and you get a new UI that also integrates the formatting options and stuff like that and this also allows us to offer reconfigured payload packages so currently they are in the works they are not ready yet but they will be made available for download through our support portal and they will come just as transport requests with these configurations in them so it is basically an isolated transport for the configuration of the payload designer and instead of showing just a slide I want to quickly show you the payload designer in the SAP system I'm just trying to find my SAP systems open there it is so the the new payload designer it's got a new standalone transaction um where you can call it as a dev design and you so initially you have to basically create your first one or if you have imported ours so you see there are a lot of this as up you slash as up you slash in front um so these are the standard ones we are working on and the way these look like you you always have a payload design that's just a high level information what what is it about what what is the application area and then um so what we designed now for the prepackage context is typically a a division into how big the payload is what what tables are included so we can for example check the medium where we have three tables and you will have a join builder where you can um where you can add the tables and create the joins in a more user friendly way to just drag and drop the fields on each other and what is also new with the payload designer what was always an issue with the database views you can now have outer joins as well um so it is a more flexible approach um to that and when you when you receive the the preconfigured content it will be like that that you can't you can't edit it here because it it should stay as it is as preconfigured content but you can make a copy of it and I already did that for the sales order so that you have you don't lose time here doing that but um if you have made a copy you can totally edit it and um do whatever you you like to it so add new fields because typically when we deliver it only the key fields are added so the preconfigured content basically only has the the join conditions which tables are used how they should be joined together so that you don't have to think about it but which fields already you can um easily add new fields just by choosing them from the from the tables so like if you want to like know some some additional info you can just add them and they will then appear down here in the field list and you can easily change um the the names to some JSON readable format like that you can use the skip field you can reorder them with the sequence and um as before via the field mapping there's also the option to have some conversion class and method to determine the name you can also add basically append fields to it that will be only filled when doing the formatting so these typically get the data that that the formator gets and you can give them the value for that field um okay and same goes also if you have custom fields that you want to add but should have a default value you can add them as well good and then once you once you have that you can also if you if you already use it somewhere um you yeah I used the name multiple times now but as I'm important now um you can also check where you use it in your configuration so this one is already used in some up and up check um and you can jump directly into the up and up check from the from the payload designer and also the other way around you have the payload view name and version here and you can of course jump back from here to the to the to the payload design great so this is a new codeless way to define your extraction and your your your payload design so um looking forward to what you all do with that option because it should cover a lot of use cases where previously the database views were not enough and um yeah offer a very quick way to define a new interface so just yesterday for a new demo we we designed an interface from scratch in about half an hour and of course that is we knowing the framework and the tooling but it shows that you can very quickly get up to speed and have a first payload the design up and running uh linked to some events and testable in your environment good now um going into the more um connector specific features so um there are a few mostly I will focus on the only fee class integration but also there are some some one for confluent and Kafka connector there's a big new feature of supporting the schema registry if you know confluent or Kafka you know there is the option to have a schema registry where you define how the events how the payload looks like of your events what is the schema for them and with the new support for schema registry you can now provide a schema ID from the schema registry and then when you load the data into the Kafka confluent environment it will be validated against that configured schema or the schema that you that you say that you want to adhere to and then if it also matches the one from the topic you sent data to so this is a good new addition for everybody using the schema registry and another option that you have in confluent Kafka is that besides the payload you always have a key field that basically identifies what object is that payload about and previously you only could have one field basically designated as a key field and this of course there is shortcomings because some some data objects are do have more than one key field so now you can also specify multiple and it will then produce a a JSON object as a key so you can use that as well in your Kafka environment to there are various use cases like compacting the topics and stuff like that are is using the key and it can be now more detailed than it was before then another new feature we are now already switching to the to the SAP OEM versions so the event enablement add-on for connecting the SAP event machine BTP and the C-class integration add-on to do the process integration to fee class but starting out with event enablement add-on the event mesh added last year sometime they added the option to have certificate based authentication when when doing your authentication and we now also support that certificate based authentication and our add-on yeah please please check the the documentation for details because you will have to download the certificates from the from event mesh instance and stuff like that but so if you need that feature or wanted to use it now it's available with the add-on as well then coming to the fee class integration so there are quite a few uh topics there as well um for those that don't know the fee class integration it is different than the event-based connectors that are more technical in nature where you define your own interfaces with the fee class integration there of course is a process integration where a lot of the interfaces are basically coming from fee class so what can be integrated what should be integrated so there's a lot more going on with actual content as well for the interfaces and the the headline feature for for the more functional users is a new integration dashboard which will complement our existing more technical monitoring that the administrators use um by having a view on the on the actual integrated document types perhaps quickly switching to a short view so that the functional people in your team can now review okay what was integrated what was what is the status was it successful did it fail what was the error messages and stuff like that and you can search by your by your business object basically so by the purchase order or by the time sheets that you have received and to quickly get a more a better overview from the functional side to see what has happened in the integration yeah the the new integration dashboard is also called by a new transaction but please review documentation on it then we added an option to to upload your contracts from from the scp site or galvan agreement services into the event hierarchy lookup into inside fee class so that you now get that pre-populated automatically with data from your from your scp contracts and next feature support for evaluated receipt settlement so if you if you use that process inside scp where if you get a service entry sheet you automatically create an invoice for it so you don't wait for the supplier sending the invoice but you use a process where you automatically create an invoice for these for these time sheets you get then this can be now achieved so the invoice is then created on the scp site and integrated into fee class instead of the normal process that would download the invoice from fee class and add them in the in the scp system with this with this process it works the other way around yeah jumping over the screen for the integration dashboard we also also as part of that improved the invoice status integration to get an additional back channel into fee class about the the status of the invoices we also added now more general support for custom account assignment categories so previously a lot of customers used custom account assignment categories but so far it was always necessary to have some body implementation to have some custom coding to deal with that and to map for the right categories for for fee class and now this is more a configuration option and the standard integration handles then the mapping already no custom code needed anymore so that's an improvement if you use these custom account assignment categories and the new release also adds support for the longer biocodes in fee class so fee class changed it from four characters to six characters and as it's used in a lot of places inside the integration and in the different integrated business objects it took some time to integrate it also into the integration add-on but now it's there so there's no need anymore to limit the customers to the four character biocode anymore and then more some more more more improvements to how you do your projects and have more more smoothness in the integration is one option typically when you do a project with fee class integration you have a one point in time where the coding goes into production and then a second point in time when the actual functional go live happens and in between the system will already record a lot of changes that are typically configured to not send them to fee class yet so all these recorded changes are basically obsolete previously there was a manual step to delete all those when you do the the initial full loads for the real functional go live and now this can be automated via configuration so that when you do the full load it will automatically delete previous or older change pointers that would be used for the incremental loads that are not necessary then anymore and yeah for the cost-send integration it was previously always an issue if the responsible user that is contained on the cost center is not an integrated user with fee class so the user does not exist on fee class side now there is an option where you can configure a default user for these cost centers that will be put into the responsible user field when sending to fee class so you can make sure that all the cost centers go over without having to care of the if all the users that are on the cost centers as responsible user are actually integrated to fee class analogies so this was a very quick rundown on the new features there is more documentation around that of course there are also features we did not mention so please check our release notes as well in the different places so for the SAP branded versions like the event enablement add-on and the fee class integration those are on the help.sub.com pages for these components and of course we for the other connectors all the documentation is on our documentation website so please please check that out and also release information is also in our support portal so direct customers from us will have access to the support portal and there you can also download the new releases and also all the corrections that we might have already made so there are quite a few for the integration dashboard and also a few for the payload designer already so you might want to check the download section in our support portal or if you're using the SAP branded components and please check for notes and you will find the new downloads in the SAP download center and for the event enablement add-on it's just sp7 so service pack 7 for fee class as it is a process integration it also has a the feature pack tags on it because of some initial service pack that we had to do that were technically in nature the feature pack is on level 6 but the service pack is on level 7 but you will encounter both both names when downloading the fee class integration so i think that's a wrap for the presentation if you have any questions or want to book a demo or know about the additional new features you can contact us i think today we don't have time for q&a so we used our time today in yesterday's meeting i did pay attention to the wrong clocks we were ready early i think the recording will be available to everybody in the call i assume and the these slides will be shared yes i see that as a question already so i would like to thank again everybody for attending today um so chat will be open for a little longer but presentation is over now and i want everybody in the european time so obviously a good day if you have somebody from the asian time zones good afternoon or good evening and talk to you soon bye everyone thank you all bye-bye