Registering the custom master data
The custom master data is set of reference data that can be used in creating journal entries when there is no business document available for the same. IGFC will allow you to define the structure of the custom master data table, and subsequently populate it with values. This facility allows you to quickly define the mappings of various input data to come up with a specific output value to populate journal entry attributes.
This object can also be used for Account Number and journal type assignment. Data from the source transactions as well as the master data references are mapped to define the logical relationships that will determine the account number for a particular transaction.
One search template for custom master data must be defined, with "account number" as return value. Another must also be defined with "journal type" as the return value.
This table shows the structure of the custom master data:
| Attribute | Attribute name | Description |
|---|---|---|
| Sender | accEnt | Indicates the accounting entity of the source enterprise application. In a custom master data setup, the value of this field shall be the same for all records. |
| BOD | bod | The transactional business document. |
| Transaction Type | tranType | Detailed classification of a transaction. Example, PO receipt may be classified into PO receipt and Non-PO receipt. |
| Transaction Set | tranSet | Defines the set of debit and credit accounts for a given mapping. This also defines the sequence of accounting entries for a given event. |
| Tracking Method | trackMethod | Identifies whether the item is tracked in the item master as stocked-type or non-stocked. |
| PO Item Type | itemType | Identifies whether the purchased item is stocked type or direct type. |
| Costing Method | costMethod | Standard or moving average. |
| Receiver | recAccEnt | Indicates the accounting entity of the general ledger system. In a custom master data setup, the value of this field shall be the same for all records. |
| Account Number | account | The Account Number to be used in a journal entry. This should refer to a ChartofAccounts business document. |
| Account Description | accDesc | Name of the ledger account. |
| Journal Type | journalType | The journal type of the custom master data. |
| DrCr Flag | drCr | Indicates whether the account is debited or credited in a journal entry. |
| Effective Date | effDate | Date when the record is effective. |
This is the populated table:
| BOD | Transaction Type | Transaction Set | Tracking Method | PO Item Type | Costing Method | DrCr Flag | Account Number | Account Description | Journal Type | |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | PurchaseOrder | true | PS | DR | 102500 | Commitment PO On Order | POPS | |||
| 2 | PurchaseOrder | true | PS | CR | 142000 | Commitment Payable | POPS | |||
| 3 | PurchaseOrder | true | PD | DR | 102509 | Commitment PO On Order - COGS | POPD | |||
| 4 | PurchaseOrder | true | PD | CR | 142000 | Commitment Payable | POPD | |||
| 5 | ReceiveDelivery | PO Receipt | Set 1 | true | PS | DR | 142000 | Commitment Payable | RDSS | |
| 6 | ReceiveDelivery | PO Receipt | Set 1 | true | PS | CR | 102500 | Commitment PO On Order | RDSS | |
| 7 | ReceiveDelivery | PO Receipt | Set 2 | true | PS | DR | 110001 | Inventory | RDSS | |
| 8 | ReceiveDelivery | PO Receipt | Set 2 | true | PS | CR | 252000 | Accrual GRNI | RDSS |
Set 1 records of ReceiveDelivery (5 and 6) refer to the reversal of commitment entries, while Set 2 records (7 and 8) refer to the recognition of Inventory.