Scribd Logo
Upload

Welcome to Scribd!

  • PDF Document Management - Compress 1 55 27

    Uploaded by

    tzelatisdim
    7 views1 page
    Electronic Statement Agreement (ELECSTMT) is a required document type for Account Document Group 101. For this document, transactions are not processed. The document type ELECSTMT would be tracked whenever an account in Document Group 101 is input. DOCUMENT.STATUS stores status codes used to track documents. Statuses of "Received", "Not Received", and "Expired" are provided, with "Received" valid and the others invalid. However, users can modify the "Received" status to invalid for workflow reasons. If a mandatory document's status is set to invalid, a transaction will still be allowed on first input but stopped on subsequent inputs if the document remains invalid. Users can define additional custom statuses as

    Original Description:

    Original Title

    pdf-document-management_compress-1-55-27

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    Electronic Statement Agreement (ELECSTMT) is a required document type for Account Document Group 101. For this document, transactions are not processed. The document type ELECSTMT would be tracked whenever an account in Document Group 101 is input. DOCUMENT.STATUS stores status codes used to track documents. Statuses of "Received", "Not Received", and "Expired" are provided, with "Received" valid and the others invalid. However, users can modify the "Received" status to invalid for workflow reasons. If a mandatory document's status is set to invalid, a transaction will still be allowed on first input but stopped on subsequent inputs if the document remains invalid. Users can define additional custom statuses as

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    7 views1 page

    PDF Document Management - Compress 1 55 27

    Uploaded by

    tzelatisdim
    Electronic Statement Agreement (ELECSTMT) is a required document type for Account Document Group 101. For this document, transactions are not processed. The document type ELECSTMT would be tracked whenever an account in Document Group 101 is input. DOCUMENT.STATUS stores status codes used to track documents. Statuses of "Received", "Not Received", and "Expired" are provided, with "Received" valid and the others invalid. However, users can modify the "Received" status to invalid for workflow reasons. If a mandatory document's status is set to invalid, a transaction will still be allowed on first input but stopped on subsequent inputs if the document remains invalid. Users can define additional custom statuses as

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Document Management

    Example:
    Electronic Statement Agreement (ELESTMT) is a required Document Type for ACCOUNT Document
    Group 101 (In DOCUMENT.REQUIRED record with ID AC*101, ELESTMT is specified as a value of
    the field DOCUMENT.TYPE). For this document, the field TXN.PROCESSING is set to NO. The
    document type ELECSTMT would be tracked whenever an Account is input which belongs to the
    Account Document Group 101.

    In DOCUMENT.REQUIRED, for a LD loans Document Group, ACCOUNT is defined as a related


    application in the field: RELATED.APPLN; When a loan is input in the LD Application, the related
    Account belongs to Account Document Group 101. When the documents for the Account are tracked
    after LD input, since TXN.PROCESSING is set to NO for the document ELECSTMT in Account
    Document Group 101, it would not be tracked.

    DOCUMENT.STATUS
    This file stores the details of Status codes used in the document data files CUST.DOCUMENT and
    TRANS.DOCUMENT.

    Records with IDs 1 (“Received”), 2 (“Not Received”) and 3 (“Expired”) are supplied during installation
    and these Status ID values are used by T24 in processing. While Status 1 is a valid one (VALID=YES),
    both Status 2 and 3 are invalid (VALID=NO).

    However, for workflow reasons, an option is available to the Users to modify the Status 1 to an invalid
    one (VALID=NO).

    When the DOCUMENT.STATUS ID 1 is specified as an invalid one and when a Document is created
    by T24 with a Status of 1 (the document is tracked for the first time for the Customer/Transaction and
    user responds with YES to a T24 Confirmation Message), the stipulation of stopping a transaction
    when a mandatory document is invalid (STOP.TXN=YES in DOCUMENT.REQUIRED) would not be
    applicable.

    For example, VALID is set to NO in DOCUMENT.STATUS for the ID 1.

    The document IDCARD is mandatory for a transaction input and set with STOP.TXN=YES in
    DOCUMENT.REQUIRED. When IDCARD is tracked for the first time and the User responds with YES
    to the T24 Confirmation Message, the input would not be stopped and T24 would create the
    Document with the invalid Status 1. However, when the document IDCARD is again subsequently
    tracked and if the document IDCARD is still with Status 1 (an invalid status) in CUST.DOCUMENT or
    TRANS.DOCUMENT, the input would be stopped.

    Users could define their own Status codes in this application, which could be either Valid or Invalid
    (Field: VALID set to YES or NO).

    Records of this application could not be reversed.

    TEMENOS T24 User Guide Page 27 of 55

    You might also like