Setting Up History IDs
Page Name |
Definition Name |
Usage |
---|---|---|
CUST_HIST_S_TABLE |
Link system-defined history IDs to the SetIDs associated with customers for whom you want to track history. |
|
CUST_HIST_U_TABLE |
Create the customer history IDs used to summarize history about customer receivables activity. For each history ID that you create, the system maintains the total specified customer activity for each fiscal year and accounting period. |
To set up history IDs, use the System Defined History (SYSTEM_HIST_TABLE) and the User Defined History (CUST_HIST_TABLE) components.
Use these components to:
Review system-defined history IDs.
Define user-defined history IDs.
Note: You must define at least one user-defined history ID called SALES.
Use the System Defined History page (CUST_HIST_S_TABLE) to link system-defined history IDs to the SetIDs associated with customers for whom you want to track history.
Navigation:
This table lists the available system-defined history IDs:
History ID |
Description |
---|---|
AVGDAYS |
Average Days Late |
CURRENTDUE |
Current Due |
DSO30 |
30 Days Sales Outstanding |
DSO90 |
90 Days Sales Outstanding |
FUTUREDUE |
Future Due |
HI_BAL_AMT |
High Balance Amount |
HI_CURRENT |
High Current Balance |
HI_FUTURE |
High Future Due |
HI_OTHER |
High Other Due |
HI_PAST |
High Past Due |
OTHERDUE |
Other Due |
PASTDUE |
Past Due |
WTAVGDAYS |
Weighted Average Days Late |
WTAVGPAID |
Weighted Average Paid |
WTAVGTERMS |
Weighted Average Terms |
Use the User-Defined History page (CUST_HIST_U_TABLE) to create the customer history IDs used to summarize history about customer receivables activity.
For each history ID that you create, the system maintains the total specified customer activity for each fiscal year and accounting period.
Navigation:
Define as many history IDs as you need.
The system requires a minimum of one user-defined history ID called SALES. The Receivables Update process uses the SALES history ID to calculate DSO. If you cannot use the name SALES for this history ID, then you must change the Receivables Update process to ensure that calculations for DSO are correct.
Field or Control |
Description |
---|---|
Entry Type and Entry Reason |
Enter the combination that the system should use to compile customer history. If an entry type has more than one entry reason, you need to list the entry type with each entry reason. |
Note: If an entry type does not require an entry reason, you must list the entry type, but leave the entry reason blank. The history then includes those items with the entry reason that you indicated.