Classic Delivery ARIC Foundry

Published on Slideshow
Static slideshow
Download PDF version
Download PDF version
Embed video
Share video
Ask about this video

Scene 1 (0s)

Classic Delivery ARIC Foundry.

Scene 2 (6s)

Invoking Confirmation. The communications service provider uses Amdocs Monitoring & Control to request confirmation for a cycle..

Scene 3 (16s)

Prerequisites for Undo. . The following conditions must be met in order for Undo to be performed on the charges of a Customer: 1. The customer entity must not yet have been confirmed. 2. The associated billing arrangements must not yet have been confirmed, and must be successfully marked for Undo. 3. If the customer’s charges are distributed to a different billing arrangement (whether in the same cycle or a different one), the status of that billing arrangement must be UC (Unified Charges) or earlier, meaning that the charges have not yet been billed to that billing arrangement..

Scene 4 (43s)

Undo Functions. The Undo process performs the following functions: 1. Deletes from the tables the data written after the rollback point 2. Resets entity and cycle statuses (to the rollback point) 3. Clears the Format Extract Date (date on which extract to Amdocs Document Designer was performed) 4. Re-invokes the undone processes (optional).

Scene 5 (1m 8s)

[Audio] In invoice undo, The following tables are deleted:  BL1_BILL_FINANCE_ACTIVITY  BL1_BILL_STATEMENT  BL1_INVOICING_STATEMENT  BL1_PREPAID_STATEMENT  BL1_DOCUMENT  BL1_TAX_ITEM  BL1_TAX  BL1_CHARGE (only those charges that originated in Invoice Creation)  BL1_INV_CHARGE_REL  BL1_CHARGE_ACC  BL1_INVOICE  BL1_CYC_QA_POP.

Scene 6 (2m 57s)

[Audio] Thank You !. Thank You !.