C1-HLD-DERIV

This algorithm reads the data in the BO_​DATA_​AREA column of the C1_​UPL_​REQUEST table and accordingly inserts the records in the C1_​UPLOAD_​REQ_​DTLS table. In addition, the status of each record in the C1_​UPLOAD_​REQ_​DTLS table is set to Pending.

It validates the following:

• Hold request type, hold request start date, hold request end date, hold reason, and hold entity are specified in the record.

• If the hold entity is ACCT, either the account ID or account identifier type and account identifier is specified in the record.

• If the hold entity is PERS, either the person ID or person identifier type and person identifier is specified in the record.

• If the hold entity is BILL, the bill ID is specified in the record.

If the hold entity is ACCT and the entity ID is not specified in the record, this algorithm derives the account ID using the respective account identifier type and account identifier combination. Similarly, if the hold entity is PERS and the entity ID is not specified in the record, it derives the person ID using the respective person identifier type and person identifier combination. Once the account ID or person ID is derived, the corresponding record is updated in the C1_​UPLOAD_​REQ_​DTLS table. If the system could not derive the account ID using the account identifier type and account identifier combination or if the system could not derive the person ID using the person identifier type and person identifier combination, the status of the record in the C1_​UPLOAD_​REQ_​DTLS table is changed to Invalid. In addition, if any of the above validations fail, the status of the record in the C1_​UPLOAD_​REQ_​DTLS table is changed to Invalid.

This algorithm also derives the fields which can be used as search filters based on the mapping defined in the respective upload request type.