Assigning dimension codes

A prerequisite in performing this step is that the relevant master data business documents must be sent to IGFC:
  • AccountingChart – contains the dimension types to be used within an organization.
  • ChartofAccounts – provides information regarding GL Account Number and name.
  • CodeDefinition – defines dimension codes for a particular dimension type.
Specify the account number, the corresponding dimension type by which to analyze the account, and how the dimension code value is retrieved. A dimension code value can be expressed as:
  • an attribute of master data (also referred to as an expression)
  • an attribute of transactional data, or
  • fixed, with a dimension code defined in CodeDefinition business document.

A dimension can also be assigned to multiple account numbers, and an account number can also be used to apply to different dimension types.

When the nature of a transaction can be classified into different types, assignment of dimension types should be made for each transaction type.
Note: In specifying transaction types, it is necessary that names accurately correspond to the transaction types used in other modules within IGFC.

See table below for a purchase order receipt where dimensions were assigned specifically for transaction types "PO receipt" and "NonPO receipt". These text strings should exactly match the transaction types specified in expressions or other relevant module in IGFC.

Dimensions with type "expression" must be included in the rule script and assigned to a dimension code variable. This is further illustrated in the rule script section.

Following our use case example, analyzing a particular purchase transaction in terms of its item class, would require you to determine which document contains information regarding the item’s classification code. In this case, an item master business document is used as the reference to retrieve the corresponding value. When the dimension type looks up to a master data to obtain information, a search template type expression should be used.

When a dimension type uses a transactional document as reference, attributes are used to define how the corresponding value is retrieved. Using the dimension type buyer as an example to get a buyer ID, the particular mapping from a purchase order BOD that contains this information was identified and used as the source, which is PurchaseOrder/PurchaseOrderHeader/CustomerParty/BuyerContact/ID.

This table shows the assignments that can be set up in IGFC:

Account Number Account Description Dimension Type Source Value Source
102500 Commitment PO on Order Item Class Expression PoItemClass
Buyer Attribute PoHdrBuy.poHdrBuyId
102500 Commitment PO on Order Item Class Expression RdItemClass
Buyer Attribute PoHdrBuy.poHdrBuyId
110001 Inventory Account Part Class Expression RdPartClass

Alternatively, a fixed code can also be assigned:

Account Number Account Description Dimension Type Source Value Source
110001 Inventory Account Item Class Code ‘001 – Rawmaterials’