CKO2 reporting feedbacks description for A2A channel
using SOAP protocol – Release notes
The purpose of this document is to provide a quick overview of the main modifications added in the
new version of the document “CKO2 reporting feedback description for A2A channel using SOAP
In general, problems with big files will be avoided and automation of feedbacks will be made more
o the 4 feedback steps use the same XML structure
o mayor report fields are reported for every step in the same way, in the message body
and in the feedback reports in notes at report level:
• FEEDBACK_TYPE or STEP: identifies 1 of the 4 feedback steps
o for all errors, error codes will be used
o notes with errors and information will be more structured using attributes.
As requested the 4 steps of the validation process are explained in detail, and many XML
examples are given.
The description of the "CKO2 reporting feedbacks description for the A2A channel using https
requests" (https requests instead of SOAP) will follow soon.
The body of the XML returned by the RequestFeedback webservice contains url’s to
feedback reports instead of feedback reports. With this url’s one can retrieve the
corresponding feedback report(s) XML file using simple http-request(s) (example
provided). This design change will make it possible to process bigger feedback report
Big files zipping
Big feedback reports will be zipped. Participants which don’t want to implement the
zipping can keep their report files small (small report files lead to small feedback
attachments). This was also done to avoid problems with big files. Unzip can be done
by Winzip or gzip.
Gzip can now also be used to zip the declaration reports before sending.
Note “code” attribute
All messages (“Note” element) have now an additional attribute: this was necessary to
be able to automate more completely the processing of the feedbacks.
CKO2 XML schema validation feedback
Validation step 1 now generates a feedback only in case of error.
“OneGate only” elements
OneGate adds some additional elements in the feedbacks which are not usefull for the
participant: these elements will now be invisible (e.g. “SECTION_ID”) in the feedbacks.
Reported debtor identification number
In the feedback attachments with valid actions now is indicated which debtor identifier
the participants used in the declaration report.
Report and items identification
The participants can now use the following reference elements to identify their data at
different levels, to match the feedback with the participants' data and to enable fast
REPORT_REFERENCE_TEXT: to identify a report (not new). This
identifier can remain unchanged when, after correcting errors, the report is
resent (the ticketId is always new for each upload).
PARTICIPANT_FREE_REFERENCE_TEXT: to identify an action (new).
PARTICIPANT_DEBTOR_CODE: to identify a debtor when no official
identifier (KBO, RRN) is available (not new).
PARTICIPANT_DEBTOR_COMMENT_TEXT can be used by the
participant to store e.g. a unique identifier of the reported debtor. Optional.
RISK_COMMENT_TEXT can be used by the participant to store e.g. a
unique identifier of the reported risk or credit data. Optional.
ITEM_LINE_NUMBER: indicates the location of errors and warnings in the
participant declaration report (before conversion to OneGate format) (not