Page Comparison

SAP CC does not support rollback on operations that has already been executed. In order to achieve transaction safety,  the agent will utilize a database to keep track of which record that has been processed. In a scenario where the workflow aborts, the agent will be able to refer to the database to determine which records were processed before the abort and prevent duplicated records from being processed.

We support Oracle 9 and above and PostgreSQL 9 and above.

To create the schema in Oracle, follow the command below:

CREATE TABLE MZ_SAP_CC_BATCH_STATE
(
  WF_NAME VARCHAR2(128) NOT NULL
, NODE_NAME VARCHAR2(128) NOT NULL
, POSITION NUMBER NOT NULL
, ANSWER_UDR BLOB NOT NULL
, CONSTRAINT MZ_SAP_CC_BATCH_STATE_PK PRIMARY KEY
  (
    WF_NAME
  , NODE_NAME
  , POSITION
  )
  ENABLE
);

To create the schema in PostgreSQL, follow the command below:

CREATE TABLE mz_sap_cc_batch_state (
wf_name        VARCHAR(128) NOT NULL,
node_name       VARCHAR(128)        NOT NULL,
position       NUMERIC(19)      NOT NULL,
answer_udr      bytea      NOT NULL,
PRIMARY KEY(wf_name, node_name, position)
);

Charging API Authentication is only available for SAP CC version 4.1 SP2 and later.

In terms of backwards compatibility, enabling this option prevents any compatibility issues with workflows that support the configurations from before the BigDecimal data type was introduced in version 8.0.5.0.