Map Rule To Transaction

Activity overview

Unified glossary

Basics of using Ramco Enterprise series web page

Using online help

This page allows you to define how tax is calculated in a transaction. You can map the user-defined tax type, tax community, business function group, component and transaction type to a rule for, and rule Id. You can also view this mapping through a link in this page.

The “Map Rule To Transaction” page appears.

Tax Type

Use the drop-down list box to select the required tax type to map. On launch of the page the field is blank. The list is filled with all available tax types. Tax type is the type of tax for example, TDS, and VAT.

Tax Community

Use the drop-down list box to select the required tax community. On launch of the page the field is blank. The system fills the list box with applicable value on selecting the tax type. Tax community refers to the government authority that administers the tax laws.

Business Function Group

Use the drop-down list box to select the required BFG. On launch of the page the field is blank. The system fills the list box with the Business Function Group (BFG) and displays the first value of BFG. Business function groups (BFGs) are names assigned to a set of related functions of an enterprise, example, “Payables Management”.

Component

Use the drop-down list box to select the required component. On launch of the page the field is blank. On selecting the BFG, the applicable component is filled in the list and the first available component is displayed. Component is a code assigned to a specific function under the BFG.

Transaction Type

Use the drop-down list box to select the required transaction type. On launch of the page the field is blank. On selecting the component the applicable transaction types are listed in the list box and the first available value is displayed.

The type of transaction, which takes place under the component.

The system displays the following fields in the “Rule Details” multiline:

Sequence No

The system generated sequence number.

Rule For

The tax calculation logic is broken down into a set of predefined “Rule For’s”.

Each Rule for is associated to Rule ids for each transaction type. Rule for/Rule Id combinations are mapped to tax type/tax community combinations.

One Rule ID must not be mapped to more than one Rule for.

Rule ids for a predefined ‘rule for’, transaction type are defined for the tax type, tax communities applicable for the company.

Rule Id.

The pre defined Rule ID to identify the applicable tax parameters for a Tax Type & Tax Community.

Transaction Mode

Transaction mode refers to the mode of transaction, for example, create or edit. If Rule Id is entered mode must be entered. If tax type and tax community is predefined, transaction mode cannot be modified for any rule.

On clicking the “Map Details” pushbutton the system checks that the tax type/tax community combination is not pre-defined, and that there is no repetition in the mapping. The system also ensures that one “Rule Id” is not mapped to more than one “Rule For”. The mapping is saved, and the screen refreshes with the saved details.

The system also displays details in the following fields:

Created By

The login ID of the user who mapped the relationship.

Created Date

The date on which the mapping was done.

Last modified by

The login ID of the user who last modified the mapping.

Last modified date

The date on which the modification was done.

To proceed, carry out the following