Navigation:  Requirement >

Requirement mappings

Previous  Top  Next

Overview

This command will list the requirement mappings and the scopes associated with the applicability and implementation results. It allows an analytical vision of the requirement mapping.

 

Related tables

TABLE

Description

Primary key (PK)

Connection tables

RQMAPPINGREVISION

Table that stores the requirement mapping revision data

CDMAPPING

CDREVISION

 

GNREVISION

ADALLUSERS

ADTEAM

RQMAPPINGCONFIG

GNTYPEROLE

ADDEPARTMENT

GNASSOC

OBOBJECT

GNSUPPLIER

RQMAPPINGREQM

Association table between the requirement mapping and the requirement

CDMAPPING

CDMAPPINGREVISION

CDREQUIREMENT

CDREQUIREMENTREV

RQMAPPINGREVISION

RQREVISION

RQREQUIREMENT

Requirement record table

CDREQUIREMENT

CDREVISION

GNREVISION

GNASSOC

DCDOCUMENT

RQMAPCOVERAGE

Stores the requirement mapping coverage level

CDMAPCOVERAGE

RQREQUIREMENT

RQMAPPINGREVISION

ADDEPARTMENT

GNEVALRESULTUSED

RQMAPPINGDEPT

Table of the association of departments with the requirement mapping

CDMAPPING

CDMAPPINGREVISION

CDDEPARTMENT

RQMAPPINGREVISION

ADDEPARTMENT

GNREVISION

Revisions

CDREVISION

GNASSOC

GNACTIONASSOC

GNREVCONFIG

GNREASON

GNREVISIONSTATUS

ADALLUSERS

GNSUPPLIER

Table for the generic supplier record

CDSUPPLIER

CDCOMPANY

CDASSOC

CDSUPPLIERTYPE

CDCOMPLEXFILECONT

ADCOMPANY

Customer/Supplier companies

CDCOMPANY

ADCOMPANYTYPE

ADDEPARTMENT

Business unit and department record

CDDEPARTMENT

GNFAVORITE

ADALLUSERS

COWORKSPACE

ADTEAM

ADDEPARTMENT

GNASSOC

GNMAPPING

OBOBJECT

Base object table

CDOBJECT

CDREVISION

OBSUBREASON

GNASSOC

GNREVISION

OBOBJECTGROUP

ADTEAM

 

Oracle/Postgres/SQL Server

SELECT
        RQMAPPINGREVISION.FGOBJECTMAP,
        RQMAPPINGREVISION.IDMAPPING,
        RQMAPPINGREVISION.NMMAPPING,
        RQREQUIREMENT.IDREQUIREMENT,
        RQREQUIREMENT.NMREQUIREMENT,
        RQMAPCOVERAGE.QTAPPLY,
        RQMAPCOVERAGE.QTAPPLYTOTAL - RQMAPCOVERAGE.QTAPPLY AS QTNOTAPPLY,
        RQMAPCOVERAGE.VLIMPLEMENTED,
        ADDEPARTMENT.IDDEPARTMENT AS IDBUSINESSUNIT,
        ADDEPARTMENT.NMDEPARTMENT AS NMBUSINESSUNIT,
        ADAREA.IDDEPARTMENT AS IDAREA,
        ADAREA.NMDEPARTMENT AS NMAREA,
        OBOBJECT.IDOBJECT,
        OBOBJECT.NMOBJECT,
        ADCOMPANY.IDCOMMERCIAL,
        ADCOMPANY.NMCOMPANY,
        GNREVISION.IDREVISION
FROM RQMAPPINGREVISION
    INNER JOIN GNREVISION ON GNREVISION.CDREVISION = RQMAPPINGREVISION.CDREVISION
    INNER JOIN RQMAPPINGREQM ON RQMAPPINGREQM.CDMAPPING = RQMAPPINGREVISION.CDMAPPING
        AND RQMAPPINGREQM.CDMAPPINGREVISION = RQMAPPINGREVISION.CDREVISION
    INNER JOIN RQREQUIREMENT ON RQREQUIREMENT.CDREQUIREMENT = RQMAPPINGREQM.CDREQUIREMENT
        AND RQREQUIREMENT.CDREVISION = RQMAPPINGREQM.CDREQUIREMENTREV
    INNER JOIN RQMAPCOVERAGE ON RQMAPCOVERAGE.CDREQUIREMENT = RQMAPPINGREQM.CDREQUIREMENT
        AND RQMAPCOVERAGE.CDREQUIREMENTREV = RQMAPPINGREQM.CDREQUIREMENTREV
        AND RQMAPCOVERAGE.CDMAPPING = RQMAPPINGREQM.CDMAPPING
        AND RQMAPCOVERAGE.CDMAPPINGREVISION = RQMAPPINGREQM.CDMAPPINGREVISION
    INNER JOIN ADDEPARTMENT ON ADDEPARTMENT.CDDEPARTMENT = RQMAPPINGREVISION.CDBUSINESSUNIT
    LEFT OUTER JOIN RQMAPPINGDEPT ON RQMAPPINGDEPT.CDMAPPING=RQMAPPINGREVISION.CDMAPPING
        AND RQMAPPINGDEPT.CDMAPPINGREVISION=RQMAPPINGREVISION.CDREVISION
    LEFT OUTER JOIN ADDEPARTMENT ADAREA ON ADAREA.CDDEPARTMENT = RQMAPPINGDEPT.CDDEPARTMENT
    LEFT OUTER JOIN OBOBJECT ON OBOBJECT.CDOBJECT = RQMAPPINGREVISION.CDOBJECT
        AND OBOBJECT.CDREVISION = RQMAPPINGREVISION.CDOBJECTREV
    LEFT OUTER JOIN GNSUPPLIER ON GNSUPPLIER.CDSUPPLIER = RQMAPPINGREVISION.CDSUPPLIER
    LEFT OUTER JOIN ADCOMPANY ON ADCOMPANY.CDCOMPANY = GNSUPPLIER.CDSUPPLIER
WHERE RQMAPPINGREVISION.FGCURRENT = 1 /* NOTE1*/
  AND GNREVISION.FGSTATUS = 6 /* NOTE2*/

 

Notes

1: The FGCURRENT field of the RQMAPPINGREVISION table is used to search for the current revision that is not obsolete.

2: The FGSTATUS field of the GNREVISION table indicates the revision status, defined as: 1 = Draft; 2 = Review; 3 = Approval; 4 = Release; 5 = Released; 6 = Closed.

 

Fields used on the view screen

 

requirement-03

 

requirement-04

 

#

Field ID

Type

Description

1

FGOBJECTMAP

NUMERIC(2)

Mapping scope:

1 – Business unit;

2 – Business unit and department;

3 – Business unit and item;

4 – Business unit and supplier;

5 – Business unit and supply;

6 – Business unit and asset;

7 – Business unit and waste.

2

IDMAPPING

VARCHAR(50)

Requirement mapping ID #

3

NMMAPPING

VARCHAR(255)

Requirement mapping name

4

IDREQUIREMENT

VARCHAR(50)

Requirement ID #

5

NMREQUIREMENT

VARCHAR(255)

Requirement name

6

QTAPPLY

NUMERIC(10)

Number of requirements mapped as applicable

7

QTNOTAPPLY

NUMERIC(10)

Number of requirements mapped as not applicable

8

VLIMPLEMENTED

NUMERIC(28,12)

Percentage of the requirement applicable to the organization

9

IDBUSINESSUNIT

VARCHAR(50)

Business unit ID #

10

NMBUSINESSUNIT

VARCHAR(255)

Business unit name

11

IDAREA

VARCHAR(50)

Department ID #

12

NMAREA

VARCHAR(255)

Department name

13

IDOBJECT

VARCHAR(50)

Object ID #, which can be an asset, a supply, an item, or a waste

14

NMOBJECT

VARCHAR(255)

Object name, which can be an asset, a supply, an item, or a waste

15

IDCOMMERCIAL

VARCHAR(50)

Supplier ID #

16

NMCOMPANY

VARCHAR(255)

Supplier name

17

IDREVISION

VARCHAR(50)

Requirement revision