Alternate Account Mapping and SetID Sharing

You map a corporate chart of accounts to one or many statutory charts of accounts. For example, you could have one chart of accounts for each country or local office that requires statutory accounting and reporting. When you couple this with the ability to share SetIDs, you have a very efficient solution.

One account value identified by a SetID can be mapped to 1 or many alternate account values. In turn, 1 alternate account value identified by a SetID can be mapped to 1 or many account values. However, any given account or alternate account can be a part of only 1 such mapping.

The following rules govern mapping:

• Within the same SetID, an account can only be mapped once to an alternate account in the same SetID. In turn, within the same SetID an alternate account can only be mapped once to an account in the same SetID.

• If you attempt to map a given account to an alternate account or map an alternate account to an account that is already mapped within the same SetID, you receive an error message indicating that the account or alternate account is already mapped.

• Within a given SetID, you can map an account to multiple alternate accounts as long as each alternate account is in a different SetID; an alternate account that is within a given SetID can be mapped to multiple accounts as long as each account is in a different SetID.

Consider the following examples:

Example 1 - Account>AltAcct Mappings (Same SetID for Account and Alternate Account):

Mapping #3 is not valid because ALTACCT 101000 is already mapped in Mapping #1 within the same SetID to ACCOUNT 100100.

Mapping #5 is not valid because ACCOUNT 140100 is already mapped in Mapping #4 within the same SetID to ALTACCT 140000.

Mapping #	ACCOUNT SetID	ACCOUNT	ALTACCT SetID	ALTACCT	Is Mapping Valid?
#1	MFG	100100	MFG	101000	Yes
#1	MFG	100100	MFG	101002	Yes
#2	MFG	109000	MFG	101003	Yes
#3	MFG	109100	MFG	101000	No
#4	FS	140100	FS	140000	Yes
#4	FS	140101	FS	140000	Yes
#5	FS	140100	FS	140500	No

Example 2 - Account>AltAcct Mappings (Different SetIDs for Account and Alternate Account):

In Example 2, Mappings #1 and #2 have an ACCOUNT value mapped to several ALTACCT values having different SetIDs.

Mapping #3a is not valid because the same ACCOUNT value in the same SetID (101000 in CORP) is already a part of the one account to many alternate account mappings in Mapping #1.

Mapping #3b is not valid because the same ALTACCT value in the same SetID (101003 in FRNC) is mapped to the same SetID (CORP) for the account values.

Likewise, mapping #4 is not valid because the same ALTACCT value in the same SetID (106001 in SPAN) is mapped to the same SetID (CORP) for the account values.

Mapping #	ACCOUNT SetID	ACCOUNT	ALTACCT SetID	ALTACCT	Is Mapping Valid?
#1	CORP	101000	FRNC	101001	Yes
#1	CORP	101000	FRNC	101002	Yes
#1	CORP	101000	SPAN	102001	Yes
#1	CORP	101000	SPAN	101002	Yes
#1	CORP	101000	GMNY	103001	Yes
#1	CORP	101000	GMNY	103002	Yes
#2	CORP	105000	FRNC	105001	Yes
#2	CORP	105000	SPAN	106001	Yes
#2	CORP	105000	GMNY	107001	Yes
#3a	CORP	101000	FRNC	101003	No
#3b	CORP	100000	FRNC	101003	No
#4	CORP	110000	SPAN	106001	No

Prompting for Account and Alternate Account and TableSet Sharing

To enable prompting for ACCOUNT and ALTACCT for a specific business unit, you must set up the appropriate SetIDs for these prompts by creating tableset sharing definitions.

The following are examples of tableset sharing definitions for ACCOUNT and ALTACCT:

Set Control Value	Business Unit	TableSet Record Group	ACCOUNT SetID	ALTACCT SetID
M60	M60	FS_05	CORP
		FS_40		FRNC
M61	M61	FS_05	CORP
		FS_40		SPAN
M62	M62	FS_05	CORP
				GMNY

In the above table, each business unit that is defined by the set control value has access only to the designated SetIDs for the specific business unit. For example, when you create a journal for Business Unit M60, the prompting on ACCOUNT and ALTACCT appears as CORP and FRNC, respectively. Business Unit M60 does not have access to any ACCOUNTS or ALTACCTS under any other SetIDs.