This webservice operation decreases the size of the SICS Server System Pool.

Each request needs a system for being processed, therefore decreasing the size of the pool results into decreasing the maximum number of requests being processed at the same time.

This webservice operation increases the size of the SICS Server System Pool.

Each request needs a system for being processed, therefore increasing the size of the pool results into increasing the maximum number of requests being processed at the same time.

This webservice operation is Obsolete and cannot be used.

SICS Server must be shut down / stopped using the appropriate command of the JEE container (e.g. the stop command in Tomcat).

This webservice operation is as of version 4.0 obsolete and cannot be used.

Provides options for writing Api Support Files.

This webservice operation initiate the activation of a job that is defined in the SICS Job Scheduler module.

The job has one parameter (identifier), which identifies the job in the SICS Job Scheduler.

The calling application must call the service with a Job Identifier as parameter. The effect of calling this service is that SICS Server will activate the job immediately. The job can then be processed by a running SICS Batch Server (Scheduler) instance.

This service will take Identifier as the input and will perform the following:

Look for an actual job with activation ‘OnCallOnly’ and identifier matching the specified id.

If found, change the job status to ‘Active’ and desired start time to ‘Current Time’.

Else look for matching ‘OnCallOnly’ template in Job Template and if found, create a job from the template, change the job status to active and desired start time to ‘Current time’.

Else (no matching OnCallOnly job and no matching OnCallOnly template) look for matching actual job with activation ‘Requested’ and identifier matching the specified id. If found, changed the job status to ‘Active’ and desired start time to ‘Current Time’.

Although SICS allows more than one Template or Actual Job to have the same identifier, the intention is that externally scheduled jobs should have unique identifiers. It is up to the user who creates the Job Template or Actual Job to ensure this. If SICS Server is asked to activate a job and more than one Actual Job or Template matches the job identifier, then a random Job/Template will be activated.

When SICS Server is finished activating the selected job, it will reset itself and wait for a new service request. Even if more than one Actual Job or Template matches the requested identifier, SICS Server will only activate one job, using the selection criteria described above.

SOAP library - SicsWsBatchProcessEntryPoint - createAccountingOrder

SOAP library - SicsWsBatchProcessEntryPoint - createJob

SOAP library - SicsWsBatchProcessEntryPoint - createOrder

SOAP library - SicsWsBusinessEntryPoint - addRealiseNonPropFacOccProtection

SOAP library - SicsWsBusinessEntryPoint - addRealizeNonPropFacOccProtectionToLightPolicy

This webservice operation Amend a classification.

This will create a copy of the classifications and let the copy be owned by a specific amendment (SicsAmendment).

Before you can amend a classification, the amendment object (amendment number) you specify in the input message must already exist on the target business.

The behavior of the service is similar to the process of amending a classification on the SICS Workstation.

The amendClassification service does not allow you to specify new classification data.

This must be done using the updateScopeOfCover service.

SOAP library - SicsWsBusinessEntryPoint - amendClassification

This webservice operation is used to create business groups.

In addition to the creation of a group with its details the WS supports the assigning of one or several businesses to the group in same message.

SOAP library - SicsWsBusinessEntryPoint - createBusinessWithSections

This webservice operation creates multiple sections and section hierarchy.

MINIMUM input is Business ID, Insured period, Life cycle Status and amendment.

This webservice operation is used for deleting existing business or existing insured period.

MINIMUM INPUT: Business ID and Insured Period Start Date.

This webservice operation is used to delete business groups.

It covers deletion of the group, regardless of Type of group.

This webservice operation delete a scope of cover classification that is linked to the Scope of Cover and Amendment number indicated by the SOAP input.

This Web Service is only intended for deleting a Scope of Cover Classification that has been amended i.e. where Classification is linked to an Amendment that has Amendment number greater than 0.

If an attempt is made to delete Scope of Cover classification for Amendment 0, the Web Service will fail with a validation error message.

This webservice operation is used to automatically generate protection assignment for an Assumed Business, Policy Ceded using a Fac Protection Program.

The calculated protection assignment will be stored to the database and the new protection assignment of the business will be returned to the caller.

This webservice operation is used to ‘Generate Auto Protection (Commit)’ for the direct and fac businesses.

When function ‘Generate Auto Protection’ to be performed for given policy and insured period and life cycle phase.

The system will trigger the same functionality available on direct and fac businesses ‘Generate Auto Protection’.

The calculated PA will be stored to the database and the captured protection assignments will be returned to the caller.

This webservice operation is used to ‘Generate Auto Protection (Proposal)’ for the direct and fac businesses.

When function ‘Generate Auto Protection’ is performed for given policy and insured period and life cycle phase.

The system will trigger the same functionality available on direct and fac businesses ‘Generate Auto Protection’.

The calculated result will be returned to the caller as a proposal.

This webservice operation is used to automatically generate protection assignment for a Policy Light Business using a Fac Protection Program.

The calculated protection assignment will be stored to the database and the new protection assignment of the policy will be returned to the caller.

This webservice operation is used to ‘Generate Auto Protection (Proposal)’ for the Policy Light businesses.

When function ‘Generate Auto Protection’ is performed for given policy Light and insured period.

The system will trigger the same functionality available on Policy light businesses ‘Generate Auto Protection’.

The calculated result will be returned to the caller as a proposal.

This webservice operation is used to inactivate amendments on business.

Minimum input is: Business identifier, Begin date/time, Amendment number.

SOAP library - SicsWsBusinessEntryPoint - retrieveAllAssumedBusinessesLinkedToPlacement

This webservice operation is used to retrieve a list of valid life cycle statuses for a specific life cycle phase of a business(re-)using the rules and logic in SICS.

It can also be used to retrieve all possible valid life cycle statuses for a new assumed business.

This webservice operation revoke provisional cancellation for an insured period on a business.

Minimum input: Business identifier and Begin date/time.

This webservice operation Update business attributes.

This service does not support the update of business condition attributes.

This webservice operation is used to update business groups.

In addition to editing group details the Update WS covers assigning and/or removal of one or several businesses to the group.

SOAP library - SicsWsBusinessEntryPoint - updateContractCertaintyCheckList

This webservice operation is used for Creation of Insurable objects.

Minimum input for Create Service: Insurable Object type and name.

This webservice operation covers creation and update of existing Insured Peril Cessions for a business.

Minimum input for this Service: Business ID, SOC name and Insured period start date.

This webservice operation is used for Updating Insurable objects.

Minimum input for Update Service: Insurable object Name or Identifier (both Unique ID and Other ID can be used as reference).

This webservice operation Create and Approve a Bank Account for an existing business partner.

Minimum Input for Create and Approve a Bank Account: PartyReference : Identifier, Bank Account Number, Bank Identifier, Currency, Account Task.

This webservice operation supports all fields on the Main bank window, Addresses, Electronic Addresses, Identifiers and User Defined Fields.

Minimum Input for Create Bank: Name and Country.

This webservice operation creates Business Partner or Insured(Third Party).

In order to create an Insured(Third Party) the isInsured element must be set to true.

Minimum Input for Create Business Partner/Insured: Name and Country.

This webservice operation takes place when a user creates Business Partner Group or a Third Party Group.

Minimum Input: Business Partner (Third Party) Group CODE.

Business Partner (Third Party) Group NAME.

A Boolean to indicate if this is a Business Partner or Third Party Group.

This webservice operation create or update Collateral Information(Letter Of Credit, Trusts, Funds Held) for an existing business partner.

Minimum Input for Create or Update Collateral : Business Partner Identifier.

SOAP library - SicsWsBusinessPartnerEntryPoint - createOrUpdateCollateral

This webservice operation create or update Collateral details(Increase, Decrease, Withdrawal)Information for an existing business partner.

Minimum Input for Create or Update Collateral Details : Business Partner Identifier.

This webservice operation delete an existing Business Partner, Insured(Third Party), Bank or a Person.

If links exist e.g. partner is linked to a business, system will reject deletion.

Minimum input: Identifier.

This webservice operation supports all fields on the Main bank window, Addresses, Electronic Addresses, Identifiers and User Defined Fields.

Minimum Input for Update Bank: Identifier.

This webservice operation update a Bank Account for an existing business partner.

Minimum Input for Update a Bank Account: Bank Account Number, Bank Identifier.

This webservice operation Updates Business Partner or Insured(Third Party).

Minimum Input for Update Business Partner/Insured: Identifier.

This webservice operation takes place when a user updates a Business Partner Group or a Third Party Group.

Minimum Input: Identifier.

This webservice operation update person, support all relevant fields on the Main person window, Addresses, Electronic Addresses, Identifiers, and User Defined Fields.

Minimum input: Identifier.

This webservice operation allowed to annul the balance pairing.

Minimum input for annulBalancePairing : Object ID of the Balance Pairing ID.

This webservice operation change status of received/paid remittance balance.

The service does not support create new or edit existing Remittance Balance.

This webservice operation Close a worksheet.

Minimum input for closeWorksheet : Worksheet ID and Balance Amount.

This webservice operation Close a worksheet.

Minimum input for closeWorksheet : Worksheet ID and Balance Amount.

This webservice operation is to link(pair) balances together.

Balance Pairing can be created between Remittance Balance and Technical Balance (Technical-, Claim- or Cession Balance), Remittance Balance and Remittance Balance, Technical Balances and Technical Balance.