What's Changing?
As a result of the Ascend 2.0 Initiative, we expect two major components of Emarkets to change.
Department code will become financial unit in the Transact system. Because Transact Emarkets use department codes, this data point needs to be mapped to the future state financial units.
Full Accounting Units (FAUs) will become Chart of Accounts (COAs). Because Transact Emarkets use FAUs this data point needs to be mapped to the future state COAs.
Below are examples of current state Emarket fields and how they are expected to be retrofitted to the new financial system.
|
Transact Field |
Current Example |
Max Character Count |
Current Format |
Future Format |
|---|---|---|---|---|
|
Item Code Name
|
43580MISC |
12 |
#####AAAAAAA #####=Department (5) AAAAAAA=Abbreviation (7) |
#######-1111 #######=Financial Unit (7) - = (1) 1111=Numeric Value in ascending order (4) Example: 1234567-0001 |
|
Location
|
41565C155 |
10 |
#####L&&& #####=Department (5) L= Location Type (1) [C=Cashiering, E=Emarket, W=Web, R=Refund, B=Batch) &&&=Location Number (up to 3) |
#######L&& #######=Financial Unit (7) L= Location Type (1) [C=Cashiering, E=Emarket, W=Web, R=Refund, B=Batch)
&&&=Location Number (up to 3) Example: Cashiering: 1234567C01 or 1234567155 (for locations >99) Emarket: 1234567E01
|
|
Merchant Code
|
40070CRESS |
10 |
#####AAAAA #####=Department (5) AAAAA=Abbreviation (5) |
#######AAA #######=Financial Unit (7) AAA=Abbreviation (3) Example:1234567E01
|
|
Station
|
41565155S1 43580C1S1 |
10 |
#####&&&S% (if location number is 100+) #####L&&S% (if location number is less than 100)
#####=Department (5) L=Location Type (1) [C=Cashiering, E=Emarket, W=Web, R=Refund, B=Batch) &&&=Location Number (up to 3) S= “S” for Station (1) %=Station Number (1) |
#######S%% #######=Financial Unit (7) S=“S” for Station (1) %%=Station Number (2) Example:1234567S01
|
SIT Timeline
All Emarket stakeholders will be required to participate in SIT 3 and UAT. Some stakeholders are participating in SIT 2 testing; optional system integration testing that will occur earlier.
Integration Timeline
| Testing stage | description | Start date* | End date* |
|---|---|---|---|
| System Integration Testing (SIT) 2 | Optional, early testing. | 5/17/24 | 6/28/24 |
| System Integration Testing (SIT) 3 | Required for all stakeholders | 7/18/24 | 8/27/24 |
| User Acceptance Testing (UAT) | Required for all stakeholders | 10/14/24 | 11/22/24 |
*Dates are subject to change.
Learn More
Access our new resources to learn more about the upcoming changes.
Questions?
Contact PSC on the MyUCLA Message Center.
