RRN 06725 LOCAL NPA

KGKKRU03

Message Triggering Condition

Response in case of successful / unsuccessful result of the'execution on operator request, of one of the following'MMC-commands:'CRN 23379 DIS_LOCNPA'CRN 23381 CREATE_LOCNPA'CRN 23382 REMOVE_NPA

Report Layout

 SWA-SUBSEC PATED
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        OPERATOR INPUT
        -------------(1)
             COMMAND = (2).....
             LOCNPA     = (3)
        --------------------------------------------------------------(4)
        DISPLAY EXECUTED
        -----------------
             LOCNPA
             ------(5)
             (6)
        --------------------------------------------------------------(7)
        CREATE EXECUTED
        ---------------
            LOCNPA
            ------(8)
            (9)
        --------------------------------------------------------------(10)
        REMOVE EXECUTED
        ---------------
            LOCNPA
            ------(11)
            (12)
        --------------------------------------------------------------(13)
                ERROR : (14)....
  REPORT REFERENCE NUMBER = 6725

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(C) Result part type
(D) Result part number
(E) Continuation indicator
(1) INPUT
(2) COMMAND
(3) LOCNPA
(4) PRINT INPUT'
(5) DISPLAY INFO
(6) LOCNPA
(7) PRINT DISPLAY
(8) CREATE INFO
(9) LOCNPA_CREATE
(10) PRINT CREATE
(11) REMOVE INFO
(12) LOCNPA_REMOVE
(13) PRINT REMOVE
(14) ERROR

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(14) INPUT LOCNPA NOT FOUND IN R_LOCNPA-CANNOT REMOVE LOCNPA A
(14) NO LOCNPA FOUND- CANNOT DISPLAY LOCNPA . . . . . . A
(14) TUPLE ALREADY EXISTS - CANNOT CREATE LOCNPA . . . B

Action Description

Action Meaning
A This is caused when the input digits of LOCNPA is a value different from 0 to 9.

input each digits with values from 0 to 9

B This is caused because tuple already exists in R_NPA