"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
In this document, we shall discuss best practices of reporting Integration Center issues to Cloud Product Support.
Integration Center enables HR business analysts to build, run, schedule, and monitor simple integrations. However, in the rare occasion that such integration issues should occur, the below information is crucial in investigating the root-cause and lowering the time-to-resolution.
The beneath outlined requirments are regarded as basic and fundemental when creating any Integration Center (LOD-SF-INT-INC) incident.
- SuccessFactors (SF)
- Integration Center
Reproducing the Issue
1. Navigate to Admin Center and enter 'Integration Center' via Tool Search.
2. Click 'My Integrations'.
3. Edit your Integration Center job that is resulting in an error/data issue
- You need to report an LOD-SF-INT-INC incident to resolve the problem.
To resolve Integration Center issues at maximum urgency, kindly provide the below information from Incident Creation:
1. Integration Center Job Title and Version Number:
Please highlight the job title and version number in full. This is to prevent CPS reviewing the incorrect job functionality.
Example: Integration Center - myIntegrationCenterJob - Version 4
2. The Starting Entity:
The starting entity is the entity in which the OData API Query (behind the Integration Center Job) is built on.
Some entities require certain Buiness Keys (fields) to be specified in order for the query/job to run correctly.
The Starting Entity can be found under 'Configure Fields' with the same label. Below example is the entity Email Information (PerEmail):
3. Integration Specification:
A file containing details of the integration in a human-readable CSV format.
4. Integration Definition:
A file containing the integration definition for import to another SuccessFactors tenant.
It excludes destination and scheduling settings.
NOTE: Both the Integration Specification and Definition can be found via the Save menu:
5. Event Log of Last Run:
On the landing page of the Integration Center, choose Monitor Integrations, which opens a new window on Execution Manager.
Click the > icon on the right of a process, to display the error, warning, and info messages generated by the executed job.
You can also use the arrow buttom icon on the top right to download the event log from the events view.
This log contains the detailed error messages which may be helpful to you for debugging purpose:
5.1. IMPORTANT EVENT LOG INFORMATION:
Please enable both 'Enable Server Side Pagination' and 'Enable diagnostics' when providing an Event Log to an Integration Center incident.
This is found in the 'Destination Settings' Tab under 'Advanced Settings'.
Server Side Pagination: helps to optimize query performance, prevent potential data loss, and eliminate duplicates in API query results.
Enable diagnostics: a JSON file output is created that displays the COAPI dump. Helpful for debugging purposes.
Server-Side Pagination Information:
2730132 - Integration Center Output file has Duplicate or Missing data
Enable Diagnostics and COAPI Dump File information:
2580564 - How to download JSON file or COAPI Data file from Integration Center
Integration Center, Basic Information, Integration Specification, Integration Definition, Event Log, COAPI , KBA , LOD-SF-INT-INC , Integration Center , LOD-SF-INT , Integrations , How To