SK SKYVVA Documentation

How to custom error handling?

Introduction

It is a situation related to error response handling in an outbound processing system, where the user needs to map a table called "Imessage__c" for a fault interface on the inbound side. However, users are encountering an issue where this "sObject" is not visible in a picklist list in a previous, available on SKYVVA application version 2.50 and above.

Here's a breakdown of your description:

[su_box title="Note" box_color="#2a8af0" title_color="#000000"]"Include the sObject in the selection list to enable users to perform the mapping."[/su_box]

Display the skyvvasolutions__IMessage__c for the Interface’s source name

Create an integration and map fields from the "skyvvasolutions_IMessage__c" object in the SKYVVA application. Here are the steps you should follow:

Go to our SKYVVA application.

"Create New Inbound Interface."

In the process of creating the inbound interface, the user needs to specify the Source picklist.

Required step:

Result:

After selecting the source picklist, the user needs to map fields from this source side to the target destination.

Once the user mapped the necessary fields, make sure to save your mapping configuration. Look for a "Save"  button to save your mapping settings.

[su_box title="Expectation:" box_color="#2a8af0" title_color="#000000"]The user is expected to perform mapping for the skyvvasolutions_IMessage__c object within the Skyvva system. [/su_box]

Fault Message Error Handing with SAP CPI adapter

Creating an integration with an outbound adapter for SAP CPI involves several steps. Below are the steps user can follow to achieve this:

Log in to your SAP CPI (SAP Cloud Platform Integration) environment.

Within your integration project, create the Request and Response interfaces that define the structure of the data the user is sending to and receiving from SAP CPI. The user can do this using Data Types or Message Types, depending on business requirements.

Similarly, create a Fault Interface to handle error scenarios in case the integration fails. Define the structure of error messages the user needs to handle.

To connect to SAP CPI, the user needs to create an outbound adapter. In your integration project, select the outbound adapter, which should be the "SAP CPI" adapter ."

Configure the outbound adapter to use the Request Interface the user just created. This involves mapping the data from the integration flow to the structure defined in the Request Interface.

Create Message Types for REST Request, REST Response, and Fault messages. These message types define the format of data that will be exchanged between the SKYVVA application and the SAP CPI.

Within the integration flow, add a component that represents the SAP CPI adapter. Configure this adapter to connect the SAP CPI instance, providing the necessary connection details, such as the URL, credentials, and any other required entities.

In your integration flow, link the SAP CPI adapter with the outbound interface the user just created. This defines the data flow from the SKYVVA application to SAP CPI.

[su_box title="Expectation:" box_color="#2a8af0" title_color="#000000"]The message outbound will be updated in the event of an error occurring following the callout.[/su_box]

Required step:

[su_box title="Note:" box_color="#2a8af0" title_color="#000000"]Ensure that the inbound interface for the fault will perform an insert operation.[/su_box]

Here is the payload of the response fault interface in the mock service.

{ "gid": 500,

"status": "Application Error",

"information": "Invalid address"

}

Code for callout

String[] ids= new String[]{'0011j00001jHopOAAS'}; List result = skyvvasolutions.Iservices.invokeCalloutV3('Dahuy Fault handling','Request Interface',ids,'SYNC',null); String ResultString = result.toString();

Summary

In outbound processing, users can understand error response handling. Specifically, familiar with mapping a table called "Imessage__c" for a fault interface on the inbound side of the SKYVVA application. However, users have encountered an issue where this "sObject" is not visible in a picklist in a previous version of the SKYVVA application, now this picklist value is visible starting from version V2.50 and above.

Open this article in the interactive viewer →