Sterling B2B Integrator - EBICS Reporting Service
The EBICS Reporting service generates a PSR report with every FUL request.
EBICS Reporting Service
Graphical Process Modeler (GPM) categories
This service composes Payment Status Report (PSR).
Use this service to generate a PSR report with every FUL request. The PSR report is in an XML format and follows the ‘pain.002.001.02′ schema. After the PSR report is generated successfully, it is placed in the EBICS subscriber’s download mailbox.
Use this service for a business process that needs to generate a PSR report.
This service is preconfigured as part of the system installation.
Requires third-party files?
All supported Sterling B2B Integrator platforms.
Initiates business processes?
This service is invoked from a business process.
Business process context considerations
You must be familiar with the internal service (workflow and business process parameters) that invoked this service. Workflow parameters are the values that were passed into the internal service. Business process parameters are the values specified in the BPML code.
Returned status values
Fatal – Nonrecoverable error
Transient – Recoverable error
Logic – Recoverable error
Set the user token in the BPML code before invoking this service. Setting the user token in the BPML code ensures that the workflow executor has the right to insert the report into a mailbox.
Debugging information for this service is located in Sterling B2B Integrator. Navigate to and .
Output from Business Process to EBICS Reporting Service
The following table contains the parameters passed from the business process to the EBICS Reporting service:
|Required. Specify the EBICS transaction ID.|
Output from EBICS Reporting Service to Business Process
The following table contains the parameter passed from the EBICS Reporting service to the business process:
|Required. The status code of the result of the service. Valid values are OK and Error.|
Business Process Examples
PSR Reports – Examples
The following example is of a PSR report when ‘GrpSts’ is set to ‘RJCT’:
463353943D942C7E840110DA9D0494E5 2009-07-07T03:29:37Z HOSTIDAA O001 pain.xxx.cfonb160.ict RJCT NARR EBICS_INVALID_SIGNATURE_FILE_FORMAT
The following example is of a PSR report when ‘GrpSts’ is set to ‘RCVD’:
33F60D9949576D6AE926CF3BD6BFF0BB 2009-07-07T03:29:39Z HOSTIDAA O008 pain.xxx.cfonb160.ict RCVD
Share Blog Post