PM Key Master File (PM00400)

Easily find this page again using the shortlink: http://gpt.azrcrv.co.uk/PM00400

Product: Microsoft Dynamics GP (0)
Series: Purchasing

Display Name: PM Key Master File
Physical Name: PM00400
Technical Name: PM_Key_MSTR

Group Display Name: Payables Key Master Logical File
Group Technical Name: PM_Key_Master_Logical_File

Click to show/hide table information

The PM_Key_MSTR table is used to validate the uniqueness of control numbers in the system. A combination of the control number and control type ensure uniqueness. The control numbers used with transaction entry are Voucher Number - Work, Cash Amount Payment Number, Check Amount Payment Number, and Credit Card Amount Payment Number. The PM_Key_MSTR table also is used to ensure uniqueness for the Document Number and Check Number. The PM_Key_MSTR table will contain a record for the numbers it is tracking, no matter if they reside in work, open or history tables. A record will remain in the PM_Key_MSTR table until all transaction data for the control number it is tracking has been deleted (i.e. the transaction record, all distributions, all taxes).

When a control number is initially entered, a PM_Key_MSTR table record is saved with the control number to prevent another user from using the same control number. This keys record will be given a Document Status of 0. This means the control number is reserved for use by an unsaved work record. When the transaction record is actually saved, this status will be changed to 1. As the transaction moves through the system, this status changes to reflect the current location. The other Document Status settings are 1 for work, 2 for open, and 3 for history.

In lieu of importing into the PM Key Master table, transactions can be imported into the Payables Transaction Work table, with an associated control number, and checklinks run on the Payables Transaction Logical table. This will create the corresponding record in the PM Key Master table.

A keys record for the Voucher Number - WORK should be created first. This record is also used to track Document Number uniqueness if Allow Duplicate Invoices of table PM_SETP is set to false.

Seq NoPhysical NameDisplay NameDexterity Data TypeSQL Data TypeSQL DB LengthKeyable Length
1CNTRLNUMControl NumberSTR20_LBAUString2220
2CNTRLTYPControl TypeINT1Integer21
The Control Type records the type of transaction.

Click to show/hide Control Types

0	Voucher types
1	Payment types
2	Printed alignment forms
3DCSTATUSDocument StatusDDL_Doc_StatusInteger20
Records status of the document - identifies which transaction table will contain the record.

Click to show/hide Document Statuses

0	Reserved key
1	Work
2	Open
3	History
4DOCTYPEDocument TypeDDL_Document_TypeInteger20
Document Type records the type of document.

Click to show/hide the Document Types

1	Invoice
2	Finance Charge
3	Miscellaneous Charges
4	Return
5	Credit Memo
6	Payment
5VENDORIDVendor IDSTR_15_Vendor_IDString1615
Key to the PM Vendor Master File (PM00200).

Click to show/hide example SQL

SELECT
       ['PM Key Master File'].VENDORID AS 'PM Key Master File-Vendor ID'
       ,['PM Vendor Master File'].VENDORID AS 'PM Vendor Master File-Vendor ID'
FROM
       PM00400 AS ['PM Key Master File']
INNER JOIN
       PM00200 AS ['PM Vendor Master File']
              ON
                     ['PM Key Master File'].VENDORID = ['PM Vendor Master File'].VENDORID
6DOCNUMBRDocument NumberSTR20_Document_NumberString2220
7TRXSORCETRX SourceSTR13String1413
8CHEKBKIDCheckbook IDSTR15_Checkbook_IDString1615
Key to the CM Checkbook Master (CM00100).

Click to show/hide example SQL

SELECT
       ['PM Key Master File'].CHEKBKID AS 'PM Key Master File-Checkbook ID'
       ,['CM Checkbook Master'].CHEKBKID AS 'CM Checkbook Master-Checkbook ID'
FROM
       PM00400 AS ['PM Key Master File']
INNER JOIN
       CM00100 AS ['CM Checkbook Master']
              ON
                     ['PM Key Master File'].CHEKBKID = ['CM Checkbook Master'].CHEKBKID
9DUEDATEDue DateDTDate48
10DISCDATEDiscount DateDTDate48
11BCHSOURCBatch SourceSTR15String1615
Records whether the transaction was entered in a batch or not.

Click to show/hide the Batch Sources

PM_Trxent	Batch
XXPM_Trxent	No batch (real-time)
12DOCDATEDocument DateDTDate48
13USERIDUser IDSTR15_User_IDString1615
Key to the Users Master (SY01400).

Click to show/hide example SQL

SELECT
       ['PM Key Master File'].USERID AS 'PM Key Master File-User ID'
       ,['Users Master'].USERID AS 'Users Master-User ID'
FROM
       PM00400 AS ['PM Key Master File']
INNER JOIN
       DYNAMICS..SY01400 AS ['Users Master']
              ON
                     ['PM Key Master File'].USERID = ['Users Master'].USERID
14DEX_ROW_IDintint1010

DEX_ROW_ID is an auto-numbered IDENTITY column used internally by Dexterity for lock management; it should not be used by developers to identify any particular piece of information.

Microsoft MVP Mariano Gomez has a good write up on the DEX_ROW_ID column.

1 thought on “PM Key Master File (PM00400)

Leave a Reply

Your email address will not be published. Required fields are marked *