This chapter provides an overview of customer data integration and discusses how to receive information from a billing system.
The PeopleSoft Receivables system relies on a family of tables that contain customer information that enable customer-related processing. This customer information usually resides in one or many systems that are maintained outside of the receivables processing area.
To transfer customer information from billing systems, order management systems, or customer databases, you must write an interface program or use a utility to populate the PeopleSoft customer tables with information.
You enter customer information only for the tablesets that you use. You do not need to add any information to customer tables that are keyed by business unit. The Receivable Update Application Engine process (ARUPDATE) creates or updates rows in these tables.
The tables listed below are keyed by setID. Of these tables. three are required, four are conditionally required, and the rest are optional. Required means that you must place a row in the table with correct default values, even if you will not use any of the fields in these tables. The system uses rows in the required tables to access information online and for background processing:
Table Name |
Required or Optional |
Information Type |
PS_CUSTOMER |
Required |
Customer header |
PS_CUST_VAT_REG |
Required for value-added tax (VAT) customers |
Customer VAT |
PS_CUST_ADDR_SEQ |
Required |
Customer address header |
PS_CUST_REGN_TYPE |
Optional |
Customer region code types |
PS_CUST_ADDRESS |
Required |
Customer address detail |
PS_CUST_CNTCT_SEQ |
Optional |
Customer contact header |
PS_CUST_CONTACT |
Optional |
Customer contact detail |
PS_CUST_CNTCT_TYPE |
Optional |
Contact type |
PS_CUST_CNTCT_DOC |
Optional |
Contact document |
PS_CUST_CNTCT_CARD |
Optional |
Contact credit card |
PS_CUST_CNTCT_PHN |
Optional |
Contact phone |
PS_CUST_CREDIT |
Optional |
Customer credit |
PS_CUST_OPTION |
Required for bill-to customers |
Bill-to customer options |
PS_CUST_SHIPTO_OPT |
Required for ship-to customers |
Ship-to customer options |
PS_CUST_SOLDTO_OPT |
Required for sold-to customers |
Sold-to customer options |
PS_CUST_BILLTO |
Optional |
Valid bill-to relationships |
PS_CUST_SHIPTO |
Optional |
Valid ship-to relationships |
PS_CUST_CRSPD |
Optional |
Customer correspondence |
Note. Use PeopleSoft Enterprise Application Designer to review the characteristics of each field in more detail.
See Also
PeopleSoft Enterprise PeopleTools PeopleBook: PeopleSoft Application Designer
This section provides overviews of PeopleSoft Receivables Pending Item tables, interface tables, and accounting entry creation and discusses how to:
Populate group control table fields.
Populate pending item table fields.
Populate user-defined fields.
Populate pending VAT table fields.
(IND) Populate pending tax table fields for India.
Prevent distribution of accounting entries for external groups.
Create accounting entries for external groups.
Troubleshoot missing accounting entries.
Troubleshoot Receivable Update error messages.
PeopleSoft Receivables accepts information from an unlimited number of billing systems. The relational structure of tables is flattened to contain posted data to simplify the interface process for converting existing items or bringing in billing information.
At a minimum, the interface program or utility must populate two tables:
PS_GROUP_CONTROL
PS_PENDING_ITEM
If you use the system for VAT processing, the system populates an additional table, PS_PENDING_VAT, with VAT data.
If you use the system for excise duty and sales taxes in India, the system populates additional tables: PS_PENDING_TAX and PS_PENDING_TAX_DTL.
If you create accounting entries during the Receivable Update process, the system creates rows in a sixth table, PS_PENDING_DST. Under certain circumstances and with certain limitations, you may also need to populate PS_PENDING_DST in your interface.
Because the PS/Import utility runs only on the client and has limited processing capability, write an interface program or use a tool such as Structured Query Report (SQR) to populate the interface tables. As another alternative, use the DC_PENDITEM_CI component interface to populate the pending item tables.
See Also
Performing Data Conversion Using the DC_PENDITEM_CI Component Interface
The Receivable Update process uses the information contained in the pending data tables to create and update rows in the tables that contain posted data:
Pending Data Tables Include: |
Posted Data Tables Include: |
PS_GROUP_CONTROL |
PS_CUST_DATA |
PS_PENDING_ITEM |
PS_CUST_HISTORY |
PS_PENDING_VAT |
PS_SUBCUST_DATA |
PS_PENDING_TAX |
PS_ITEM_ACTTAX |
PS_PENDING_TAX_DTL |
PS_ITEM_ACTTAX_DTL |
PS_PENDING_DST |
PS_SUBCUST_HISTORY |
|
PS_ITEM |
|
PS_ITEM_ACTIVITY |
|
PS_ITEM_ACT_VAT |
|
PS_ITEM_DST |
Use these tables to interface continuously with a billing system for the purposes of conversion and for online and background processing within PeopleSoft Receivables. They provide a single point of processing for the Receivable Update process.
Just as you populate PS_GROUP_CONTROL, PS_PENDING_ITEM, and possibly PS_PENDING_VAT, PS_PENDING_DST, PS_PENDING_TAX, or PS_PENDING_TAX_DTL, the PeopleSoft Receivables processes populate these tables as a result of group item entry, overdue charge processing, and activity from payments, maintenance, transfer worksheets, unpost processing, and draft processing; and direct debit processing, the Automatic Maintenance Application Engine process (AR_AUTOMNT), and the Payment Predictor Application Engine process (ARPREDCT).
We define the groups that you create for billing interface or conversion purposes as external groups, and they receive more extensive editing during the Receivable Update process. When you enter groups online during group item entry, the system performs online edits that reduce the editing that is needed during the Receivable Update process. The PeopleSoft application categorizes the third kind of group (created by the system through the worksheet, overdue charge, unpost, draft, direct debit, item splits, and the Automatic Maintenance and Payment Predictor processes) as system-defined groups with a required origin of PS_AR. These system-defined groups receive the least amount of editing during the Receivable Update process.
See Also
Setting Up Receivable Update and Pending Group Generator
This table lists and describes types of transactions for which you create accounting entries:
Transaction Type |
What the System Does |
Group item entry |
In the group item entry environment, the system enables the recording of an unlimited number of accounts receivable debit or credit entries and an unlimited number of offsetting entries of the opposite sign. The system also creates entries to VAT liability accounts if you use VAT processing. The system creates accounting entries for India taxes if you enter the items in PeopleSoft Receivables or if your billing system does not generate the accounting entries. |
Worksheets |
In the payment worksheet, in addition to cash and accounts receivable, the system creates entries to VAT liability accounts if you use VAT processing with a payment declaration point. The system also allows an unlimited number of debit entries for write-off activity. The system calculates realized gain or loss entries in a multicurrency application. It creates interunit and intraunit entries when needed. In the maintenance worksheet, the system records entries to accounts receivable and allows an unlimited number of debit entries for write-off activity. The system calculates realized gain or loss entries in a multicurrency application. It creates interunit and intraunit entries when needed. The system also creates entries to VAT liability accounts when appropriate if you use VAT processing with a payment declaration point. In the transfer worksheet, the system creates accounting entries when transferring items. It creates interunit and intraunit entries when needed. |
Unpost |
The unpost process reverses entries that are originally recorded. It does not require use of the Pending Group Generator Application Engine process (AR_PGG_SERV). |
You can create accounting entries in background processing. In the production environment, this is the normal way to create the entries. In addition, the Pending Group Generator process creates accounting entries for external groups (if the interface does not populate the Pending Distribution table (PS_PENDING_DST) and also creates the accounting entries that result from draft, direct debit, overdue charge, Automatic Maintenance, and Payment Predictor processing.
When the Pending Group Generator process creates accounting entries for external groups, it uses the Item Entry Type Accounting templates that you establish for entry types.
Note. The only way to create accounting entries that post without operator intervention—apart from populating PS_PENDING_DST directly in the interface—is to have only two lines on the accounting template, specified for use as a balanced entry.
Accounting Entry Approach
You need to make several decisions about how you will use the accounting entry capabilities of PeopleSoft Receivables. You should decide:
Whether your billing system and PeopleSoft Receivables will work together or separately to send accounting entries to your general ledger system.
Whether you will create accounting entries for pending items that are interfaced from your billing system directly in your billing interface program or you will enable PeopleSoft Receivables to create them for you.
How you will provide accounting entry information for items that you convert from your existing system.
Your decisions will also be influenced by whether you need to use more than one accounts receivable (AR) line for each pending item.
Background Processing Flow
If you use the Pending Group Generator process to create accounting entries for external groups, you must provide values in more fields on PS_PENDING_ITEM than if the interface populates PS_PENDING_DST directly. The process runs before the posting step of Receivable Update, so default values that the Receivable Update processes supply are not available when the process creates the accounting entries. The same is true for converting or interfacing in a multicurrency environment; you must populate additional multicurrency fields if you create accounting entries during the Receivable Update process.
The interface tables indicate which fields on PS_PENDING_ITEM must have values for the Pending Group Generator process to create accounting entries.
See Also
Your Accounting Entry Approach
The PS_GROUP_CONTROL table contains one row for each group that you enter into the system for billing interface or conversion purposes. We use the term group to mean a collection or batch of pending items that the billing system or conversion program produces and that PeopleSoft Receivables groups for control or processing purposes.
Some billing systems produce one group for each day. Other systems produce separate groups for debit memos, credit memos, or certain kinds of invoices. During conversion, you decide how many groups to create to bring in the activity that records open and closed items. PeopleSoft Receivables can receive an unlimited number of groups of various entry types and sizes.
Your interface or conversion program populates the group control table with external billing group information. The following table lists the appropriate values, along with the associated column name, for each field on PS_GROUP_CONTROL.
In the table, a field type is specified for each field; you use the field type to determine how to populate system-maintained fields and optional fields that you want to leave blank. To leave a field blank, enter a space for a character field, a null value or nothing for a date field, and a zero for a numeric field.
Note. Use Application Designer to review the characteristics of each field in more detail.
Column |
Field Name |
Field Type |
Optional/Conditional/Required |
Field Description |
1 |
GROUP_BU |
Character |
Required |
Associate each group with a PeopleSoft Receivables business unit. |
2 |
GROUP_ID |
Character |
Required |
Provide a group identifier for each group. |
3 |
OPRID |
Character |
Optional |
Enter the User ID of the person who entered the group. This value is used in group inquiry and processing pages. |
4 |
ASSN_OPRID |
Character |
Optional |
Enter the User ID of the person who is responsible for processing the group. This value is used in group inquiry and processing pages. |
5 |
BUSINESS_UNIT |
Character |
Optional |
Set the value to be the same as GROUP_BU. |
6 |
GROUP_TYPE |
Character |
Required |
Select the value that you established in the Group Type table for this type of group. Do not use D, F, M, P, T, or U. Draft, overdue charge, maintenance, payment, transfer, and unpost groups use these values. Also, do not use C or R, because the Claim Settlement Process for AR process (PO_CLMSTL_AR) uses these values for claim items entered in PeopleSoft Purchasing and PeopleSoft Order Management. |
7 |
BAL_STATUS |
Character |
Required |
The default value is N (out of balance). The Receivable Update process automatically balances all external groups and sets the value to I (in balance) during initial processing, provided that the entered amount and count that it calculates are equal to the control amount and count that you provide. |
8 |
EDIT_STATUS |
Character |
Required |
Indicates whether or not the group has been edited. Groups entered online, for example, are E because less editing occurs during the Receivable Update process for these groups. The default value is N (not edited) for external groups. |
9 |
POST_STATUS |
Character |
Required |
Indicates whether the group is fully posted, not posted, or has errors that prevented some items from the Receivable Update process. The default value is N (not posted). |
10 |
POST_ACTION |
Character |
Required |
Indicates if the group is automatically set to be processed by the Receivable Update process. The field is populated with A (no action) if you want to review the contents online before the Receivable Update process. A is the default for online processing. The field value is L (batch standard) to post during the next Receivable Update process run. |
11 |
CONTROL_AMT |
Number |
Optional |
Enter the control amount. The control amount is the total amount of all items that are in the group in the entry currency of each item. For mixed currencies, this becomes a hash total. If the group has two items, one at 10.00 EUR and one at 10.00 USD, then the CONTROL_ AMOUNT is 20.00. To require a single currency for each group, refer to the CONTROL_ CURRENCY. |
12 |
CONTROL_CNT |
Number |
Required |
Enter the number of items in the group. |
13 |
ENTERED_AMT |
Number |
Optional |
The system calculates this value for you, so enter 0. When the Receivable Update process balances the group, the system updates this field with the total monetary amount of all pending items. |
14 |
ENTERED_CNT |
Number |
Optional |
The system calculates this value for you, so enter 0. When the Receivable Update process balances the group, this field is updated with the count of all pending items. Online groups have a default of 1. |
15 |
POSTED_TOTAL |
Number |
Optional |
The system calculates this value for you, so enter 0. This field is updated by the Receivable Update process with the total entered amount of all pending items in the group that are posted. |
16 |
POSTED_COUNT |
Number |
Optional |
The system calculates this value for you, so enter 0. This field is updated by the Receivable Update process with the total count of all pending items in the group that are posted. |
17 |
GROUP_SEQ_NUM |
Number |
Optional |
The system calculates this value for you, so enter 0. The system uses this value to assign sequence numbers for certain kinds of groups. |
18 |
ORIGIN_ID |
Character |
Required |
Enter an origin ID to represent where the group came from. Select a value from the origin IDs that you define for use as external billing origins on the PS_ORIGIN_TBL. To qualify, the origin type must be Billing, and the origin method must be External. |
19 |
RECEIVED_DT |
Date |
Required |
Indicates the date on which PeopleSoft Receivables received the group. From an interface or conversion perspective, RECEIVED_DT and ENTRY_DT are probably the same. |
20 |
ENTRY_DT |
Date |
Required |
The date that you enter the group into PeopleSoft Receivables. From an interface or conversion perspective, RECEIVED_DT and ENTRY_DT are probably the same. |
21 |
POST_DT |
Date |
Optional |
The system calculates this value for you, so set the value to null. This value is updated by the Receivable Update process with the most recent date that the group was posted. |
22 |
ACCOUNTING_DT |
Date |
Required |
Enter the accounting date that applies to the group. The Receivable Update process uses this date to determine if the group falls within the date range that is on the Receivable Update process request. |
23 |
PROCESS_INSTANCE |
Number |
Optional |
The system calculates this value for you, so enter 0. This value is updated by the Receivable Update process with the process instance that is used for a given execution of the process. |
24 |
DST_BAL_STATUS |
Character |
Required |
Enter I (in balance) if you provide your own PS_PENDING_DST rows. Otherwise, enter O (out of balance). The Pending Group Generator uses and updates this value. |
25 |
GROUP_ID_ORIG |
Character |
Optional |
Enter a value when you unpost a group during online processing. |
26 |
DEPOSIT_BU |
Character |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
27 |
DEPOSIT_ID |
Character |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
28 |
PAYMENT_SEQ_NUM |
Number |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
29 |
PAYMENT_ID |
Character |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
30 |
PAYMENT_CURRENCY |
Character |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
31 |
PYMT_RT_TYPE |
Character |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
32 |
PYMT_RATE_MULT |
Number |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
33 |
PYMT_RATE_DIV |
Number |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
34 |
CONTROL_CURRENCY |
Character |
Optional |
If this field contains a value, all pending items in the group must have this currency as their entry currency. Select from the values on PS_CURRENCY_CD_TBL. If you enter a space, the pending items in the group may contain more than one entry currency. |
35 |
FORMAT CURRENCY |
Character |
Required |
Enter the currency code that controls the precision for this group's amount totals. Select from values on PS_CURRENCY_CD_TBL. If you provide a value for CONTROL_CURRENCY, use the same value here. |
36 |
PAYMENT_AMT |
Number |
Optional |
Enter a value when the group is created by a payment worksheet or by Payment Predictor. |
37 |
ALLOW_DST |
Character |
Required |
Tells the Pending Group Generator how to set the GL_DISTRIB_STATUS field for the PENDING_DST rows that it creates for this group. Set to Y to distribute the accounting entries to general ledger. This value sets GL_DISTRIB_STATUS = N. Set to N to prevent accounting entries from being distributed to the general ledger. This value sets GL_DISTRIB_STATUS = I. |
38 |
CREATE_DST_BATCH |
Character |
Optional |
This field is no longer used. |
39 |
CASH_CNTRL_USE |
Character |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
40 |
BANK_SETID |
Character |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
41 |
BANK_CD |
Character |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
42 |
BANK_ACCT_KEY |
Character |
Optional |
Enter a value when a payment worksheet or Payment Predictor creates the group. |
43 |
UNPOST_REASON |
Character |
Optional |
Enter the reason for unposting the group. Select one of the reason codes from the UNPOST_RSN_TBL table or enter a space. |
44 |
WS_REASON |
Character |
Optional |
Enter a reason that applies to all items in a maintenance group. Enter a value that you define in the PS_WS_REASON_TBL. |
45 |
OPRID_APPROVED_BY |
Character |
Optional |
Enter the User ID of the person who set the worksheet to post. |
The PS_PENDING_ITEM table is a child of the PS_GROUP_CONTROL table. It contains one record for each transaction that you add to the system. A pending item may represent any kind of invoice, debit memo, credit memo, or adjustment. During conversion, or in a specialized payment interface application, a pending item may also represent a payment.
The following table lists the appropriate values for each field in the PS_PENDING_ITEM table. Many of the fields are optional, and some are used only by the system processes.
The following table specifies a field type for each field in the PS_PENDING_ITEM_table. Use the field type to determine how to populate system-maintained fields and optional fields that you want to leave blank. Supply a space for a character field, a null value for a date field, and a zero for a numeric field.
Note. Use Application Designer to review the characteristics of each field in more detail.
Column |
Field Name |
Field Type |
Optional/ Conditional/ Required |
Field Description |
1 |
GROUP_BU |
Character |
Required |
Enter the same value as the GROUP_ BU on PS_GROUP_CONTROL. |
2 |
GROUP_ID |
Character |
Required |
Enter the same value as the GROUP_ID on PS_GROUP_CONTROL. |
3 |
BUSINESS_UNIT |
Character |
Required |
Enter the business unit that is associated with the customer account to which you post the pending item. It may be the same as, or different from, GROUP_BU. |
4 |
CUST_ID |
Character |
Required |
Enter the customer identifier. |
5 |
ITEM |
Character |
Required |
Enter the item identifier. |
6 |
ITEM_LINE |
Number |
Optional |
Enter PeopleSoft Receivables at a line-item level of detail. |
7 |
GROUP_SEQ_NUM |
Number |
Optional |
If you bring in more than one row for a single BUSINESS_UNIT, CUST_ID, ITEM, and ITEM_LINE combination, you must populate this field; otherwise, enter 0. An example of why you would bring in more than one row for a single item (BUSINESS_UNIT, CUST_ID, ITEM and ITEM_LINE combination) is that your billing system or conversion program is sending an invoice and credit memo for a single item that is in the same group. You have two options for populating this field:
|
8 |
ENTRY_TYPE |
Character |
Required |
Select the type of item that is being processed. Select from the entry types that you establish in the PS_ENTRY_ TYPE_TBL that are enabled for the IT-01 or IT-02 system functions. |
9 |
ENTRY_REASON |
Character |
Optional |
Enter an optional reason to further qualify the entry type. You can set up entry types in the system to require entry reasons. Select from the entry reasons that you establish in the PS_ENTRY_ REASN_TBL that are enabled for the IT-01 or IT-02 system functions. |
10 |
ENTRY_AMT |
Number |
Required |
Enter the amount of the entry in the entry currency. This amount cannot be 0. |
11 |
ENTRY_EVENT |
Character |
Optional |
Enter the code that the federal government uses to post pro-forma accounting information. The Entry Event Generator generates supplemental accounting lines if you enter this code. |
12 |
ACCOUNTING_DT |
Date |
Required |
Enter the date that determines the processing period for the Receivable Update process and accounting entries. |
13 |
ASOF_DT |
Date |
Required |
Enter an optional date for use in conversion or ongoing interface. Payment terms and aging calculations may be based on the value that is in this field. Use the same value as the ACCOUNTING_DT if you do not supply a separate value. |
14 |
POST_DT |
Date |
Optional |
The Receivable Update process updates this date. |
15 |
DUE_DT |
Date |
Optional |
Enter the due date of the item. Every pending item must have a due date or a payment terms code. For pending items that may represent subsequent activity against an original invoice, such as a credit memo, the due date field is not used in processing. However, it must contain a value. |
16 |
CR_ANALYST |
Character |
Optional |
Select an assignment of this pending item to a credit analyst. Select from the values that you establish in the PS_CR_ANALYST_ TBL or enter a space. If you enter a space, the Receivable Update process adds the default value from PS_CUSTOMER. |
17 |
SALES_PERSON |
Character |
Optional |
Select an assignment of this item to a team member. Select from the values that you establish in the PS_TEAM_MEMBERS, or enter a space. If you enter a space, the Receivable Update process adds the default value from PS_CUSTOMER. |
18 |
COLLECTOR |
Character |
Optional |
Select an assignment of this item to a collector. Select from the values that you establish in the PS_COLLECTOR_TBL or enter a space. If you enter a space, the Receivable Update process adds the default value from PS_CUSTOMER. |
19 |
DISPUTE_STATUS |
Character |
Optional |
Indicates if the item is in dispute. A possible use for this field is to carry over an existing dispute indication during conversion. Select from the values that you establish in the PS_DISPUTE_TBL. |
20 |
DISPUTE_DT |
Date |
Optional |
Enter the date associated with the dispute status indicator. |
21 |
DISPUTE_AMOUNT |
Sign |
Optional |
Enter the Amount associated with the dispute status indicator. |
22 |
PO_REF |
Character |
Optional |
Enter the purchase order associated with the item. |
23 |
PO_LINE |
Number |
Optional |
Enter the line number for the purchase order. |
24 |
DOCUMENT |
Character |
Optional |
Enter a reference number for the item. |
25 |
DOCUMENT_LINE |
Number |
Optional |
Enter a line number for the document reference. |
26 |
POSTED_FLAG |
Character |
Required |
Set to N (not posted). The Receivable Update process maintains this field. |
27 |
PYMNT_TERMS_CD |
Character |
Optional |
Enter a due date or payment terms code. Select from the values that you establish on PS_PAY_TRMS_TBL for accounts receivable. If you do not supply a value, enter a space. If you enter a space and do not provide a due date, the Receivable Update process uses the default that you establish for the customer or business unit options. |
28 |
DISC_AMT |
Number |
Optional |
Enter the first discount amount that is available if the payment accounting date is on or before the discount date. You may enter this or let the payment terms module calculate it. You cannot have a discount amount if you entered a payment terms code. Enter a value only if you are also entering the due date. A value is required if you have supplied the discount date. |
29 |
DISC_AMT1 |
Number |
Optional |
Enter the second discount amount that is available if payment accounting date is on or before the discount date. You may enter this or let the payment terms module calculate it. You cannot have a discount amount if you entered a payment terms code. Enter a value only if you are also entering the due date. A value is required if you have supplied the discount date. |
30 |
DISC_DT |
Date |
Optional |
Enter the date associated with DISC_AMT. |
31 |
DISC_DT1 |
Date |
Optional |
Enter the date associated with DISC_AMT1. |
32 |
DISC_DAYS |
Number |
Optional |
Enter the discount grace days that are associated with the item. If you do not supply a value, enter 0. If you enter 0, the Receivable Update process uses the default value from the customer or business unit level. |
33 |
DUE_DAYS |
Number |
Optional |
Enter the due grace days that are associated with the item. If you do not supply a value, enter a 0. If you enter 0, the Receivable Update process uses the default value from the customer or business unit level. |
34 |
ALLOW_DISC |
Character |
Required |
Set value to Y if you want the system to consider all discounts for this pending item as earned even if they are expired. Entering N enables normal discount processing. This field is useful for handling special invoice situations or, during conversion, to indicate that special instructions are already recorded. The Application Designer default for online processing is N. |
35 |
DST_ID_AR |
Character |
Optional |
If you populate PS_PENDING_DST in your billing interface, enter a space. If you plan to generate accounting entries during the Receivable Update process, you must supply a value. Select from the values that you defined for accounts receivable in the PS_DST_CODE_TBL. |
36 |
DUN_DT |
Date |
Optional |
The Dunning Application Engine process (AR_DUNNING) maintains this date. |
37 |
ST_DT |
Date |
Optional |
The Statements Application Engine process (AR_STMTS) maintains this date. |
38 |
FC_DT |
Date |
Optional |
The Overdue Charge Application Engine process (AR_OVRDUE) maintains this date. |
39 |
FC_AMT |
Sign |
Optional |
The Overdue Charge process maintains this amount. |
40 |
OC_ADMIN_DT |
Date |
Optional |
The Overdue Charge process maintains this date. |
41 |
OC_ADMIN_AMT |
Sign |
Optional |
The Overdue Charge process maintains this amount. |
42 |
OC_PNLTY_DT |
Date |
Optional |
The Overdue Charge process maintains this date. |
43 |
OC_PNLTY_AMT |
Sign |
Optional |
The Overdue Charge process maintains this amount. |
44 |
OVERDUE_CHG_LINE |
Character |
Options |
The Overdue Charge process maintains this value. |
45 |
AR_ERROR_CD |
Character |
Optional |
The Receivable Update process maintains the AR_ERROR_CD. |
46 |
ENTRY_USE_ID |
Character |
Optional |
Select the system-defined field that determines the type of processing that is associated with an entry type. Select IT-01 (Create an Invoice/Debit Memo) for a positive amount. Select IT-02 (Create a Credit Memo) for a negative amount. Make sure that you correctly match the entry types with the system function that represents the sign of the amount on the pending item. |
47 |
DST_BAL_ITEM |
Character |
Required |
Indicates if the accounting entries for the item are in balance. Enter O unless you provide your own PS_PENDING_ DST rows. If you provide your own rows, enter I. The Receivable Update process does not balance accounting entries that are supplied by an interface. |
48 |
COLLECTION_STATUS |
Character |
Optional |
Indicates if the item is in collection. Select from the values that you established in the PS_COLLECTION_TBL. This field may be used during conversion when the existing system marks items in this manner. |
49 |
COLLECTION_DT |
Date |
Optional |
Enter the date associated with the collection status. |
50 |
BILL_OF_LADING |
Character |
Optional |
Enter a bill of lading for the item. |
51 |
SUBCUST_QUAL1 |
Character |
Optional |
Enter a value for the first subcustomer field for the item (if required). Select from the values that you established in the PS_SUBCUST_ Q1_TBL. |
52 |
SUBCUST_QUAL2 |
Character |
Optional |
Enter a value for the second subcustomer field for the item (if required). Select from the values that you established in PS_SUBCUST_ Q2_TBL. |
53 |
ENTRY_CURRENCY |
Character |
Required |
Enter the currency code for the entry amount. Select from the values that you establish on PS_CURRENCY_CD_ TBL. If you provide a value for CONTROL_CURRENCY on PS_ GROUP_CONTROL, you must use the same value here. |
54 |
RT_TYPE |
Character |
Optional |
Enter the exchange rate type for the item. Required if the entry currency is different from the business unit base currency. Select from the values that are established on PS_CUR_RT_ TYPE_TBL or enter a space. |
55 |
RATE_MULT |
Number |
Optional |
Enter the ______________. This value is required if the entry currency is different from the business unit base currency. |
56 |
RATE_DIV |
Number |
Optional |
Enter the ______________. This value is required if the entry currency is different from the business unit base currency. |
57 |
PAYMENT_AMT |
Number |
Optional |
Enter 0. |
58 |
PAYMENT_CURRENCY |
Character |
Optional |
Enter a space. |
59 |
ENTRY_AMT_BASE |
Number |
Optional |
Enter the amount of the pending item that is denominated in the business unit base currency. If you populate this field, the assumption is that you have performed currency conversion. You should enter a value in the field that is equal to ENTRY_AMT multiplied by RATE_DIV and RATE_MULT. You must also enter values in the RATE_DIV and RATE_MULT fields. If you are populating PS_PENDING_DST in your interface, you may enter a 0 in this field. The Receivable Update computes ENTRY_AMT_BASE by using ENTRY_AMT, RATE_DIV, and RATE_MULT. If you create accounting entries during the Receivable Update process, you must supply a value for this field. In other words, you must perform currency conversion before or while populating PS_PENDING_ITEM to create accounting entries during the Receivable Update process. |
60 |
CURRENCY_CD |
Character |
Required |
Enter the base currency of the business unit that is associated with the item. Be sure that this value matches the value that you established for the PeopleSoft General Ledger business unit that corresponds to the Accounts Receivable business unit. |
61 |
REAL_GAIN_LOSS |
Number |
Optional |
Enter a realized gain or loss value that the system calculates during payment application or for a maintenance worksheet. |
62 |
DST_ID_REAL |
Character |
Optional |
Enter the distribution ID for the realized gain or loss value that the system calculates during payment application or for a maintenance worksheet. |
63 |
ITEM_ACCTG_DT |
Date |
Optional |
For multicurrency processing, enter the accounting date of the original item on certain subsequent entries. |
64 |
VAT_ENTITY |
Character |
Optional |
For VAT processing, enter a VAT entity for an accounts receivable business unit through a PeopleSoft General Ledger business unit. |
65 |
VAT_CALC_GROSS_NET |
Character |
Optional |
Select either the Gross or Net calculation type. |
66 |
VAT_EXCPTN_TYPE |
Character |
Optional |
Enter a VAT exception type, if applicable. |
67 |
VAT_EXCPTN_CERTIF |
Character |
Optional |
Enter a VAT exception certificate number, if applicable. |
68 |
VAT_DCLRTN_POINT |
Character |
Optional |
Enter a declaration point of either Payment or Invoice. |
69 |
VAT_RECALC_FLG |
Character |
Optional |
Select this option only if the VAT calculation type is Gross. If it is selected, the system recalculates the VAT discount amount at the payment time. |
70 |
VAT_BASIS_AMT |
Number |
Optional |
Enter the sales amount that the system uses to calculate the VAT amount. |
71 |
VAT_BASIS_AMT_BASE |
Number |
Optional |
Enter the VAT basis amount in the business unit base currency. |
72 |
VAT_AMT |
Number |
Optional |
If you convert or interface VAT information, provide the VAT amount for the item in the entry currency. Otherwise, enter 0. If you enter a value, the sum of the VAT_AMT in the PENDING_VAT rows for this item must equal this amount. |
73 |
VAT_AMT_BASE |
Number |
Optional |
The system calculates this amount by multiplying the VAT_AMT by the exchange rate that is used for the pending item. If you create accounting entries during the Receivable Update process, you must supply a value that is not 0. |
74 |
COUNTRY_VAT_BILLFR |
Character |
Optional |
If you convert or interface VAT information, provide the country code of the country where the invoice is generated. |
75 |
COUNTRY_VAT_BILLTO |
Character |
Optional |
If you convert or interface VAT information, provide the country code of the country where the invoice is sent. |
76 |
COUNTRY_SHIP_TO |
Character |
Optional |
If you convert or interface VAT information, provide the country code of the country where the invoice contents are shipped. |
77 |
COUNTRY_SHIP_FROM |
Character |
Optional |
If you convert or interface VAT information, provide the country code of the country from which the invoice contents are shipped. |
78 |
VAT_DISTRIB_FLG |
Character |
Optional |
Select or deselect the VAT distribution flag to indicate whether VAT information is distributed to the VAT Transaction Loader. The Receivable Update process updates this field. |
79 |
VAT_RGSTRN_BUYER |
Character |
Optional |
Enter the VAT registration ID of the buyer. |
80 |
VAT_DST_ACCT_TYPE |
Character |
Optional |
The system enters the VAT distribution account type. This field is populated by the system depending on the declaration point and transaction type (invoice, payment, write-off, and so on). |
81 |
VAT_ROUND_RULE |
Character |
Optional |
Indicates if the VAT amounts should be rounded up or down, or if it is regular rounding. |
82 |
ORDER_NO |
Character |
Optional |
Enter the order number that is associated with the item. |
83 |
CONTRACT_NUM |
Character |
Optional |
Enter the contract number that is associated with the item. |
84 |
BUSINESS_UNIT_BI |
Character |
Optional |
Enter the billing business unit for the item. |
85 |
BUSINESS_UNIT_OM |
Character |
Optional |
Enter the order management business unit for the item. |
86 |
ADDRESS_SEQ_NUM |
Number |
Optional |
The address location for the item. Select from the values on PS_ CUST_ADDRESS that are associated with the customer on the item. |
87 |
LETTER_CD |
Character |
Optional |
If you convert dunning letter information, enter the letter code of the most recent letter that contained the item. Otherwise, enter a space. |
88 |
CONSOL_BUS_UNIT |
Character |
Optional |
If you use PeopleSoft Billing, this field contains the business unit value that is associated with the consolidated bill. If you do not use PeopleSoft Billing, you may use the field for a similar purpose. |
89 |
CONSOL_INVOICE |
Character |
Optional |
If you use PeopleSoft Billing, this field contains the invoice identifier that is associated with the consolidated bill. If you do not use PeopleSoft Billing, you may use the field for a similar purpose. |
90 |
PAYMENT_METHOD |
Character |
Optional |
Enter CC for credit card, DR for draft, DD for direct debit, EFT for electronic funds transfer, GE for acceptgiro payments, or CHK for all other forms of payment. If you enter a space and do not provide a value, the Receivable Update process uses the default that you establish for the customer or business unit. |
91 |
DRAFT_BU |
Character |
Optional |
The draft creation process maintains this field. |
92 |
DRAFT_ID |
Character |
Optional |
The draft creation process maintains this field. |
93 |
DRAFT_APPROVAL |
Character |
Optional |
If the payment method is draft, enter P (preapproved) or R (approval required). If you enter a space and do not provide a value, the Receivable Update process uses the default that you establish for the customer or business unit. |
94 |
DRAFT_DOC |
Character |
Optional |
If the payment method is draft, enter C (create document) or N (do not create document). If you enter a space and do not provide a value, the Receivable Update process uses the default that you establish for the customer or business unit. |
95 |
DRAFT_CURRENCY |
Character |
Optional |
The draft creation process maintains this field. |
96 |
DRAFT_FORMAT |
Character |
Optional |
If the payment method is draft, enter M (multiple items per draft) or S to indicate that this item has its own draft. |
97 |
DRAFT_AMT |
Number |
Optional |
The draft creation process maintains this field. |
98 |
BANK_SETID |
Character |
Optional |
If you use the PeopleSoft Cash Management cash positioning options, enter the setID that is associated with the bank from which you expect payment for this receivable. PeopleSoft Receivables does not use this field in the Cash Forecast report. |
99 |
BANK_CD |
Character |
Optional |
If you use the PeopleSoft Cash Management cash positioning options, enter the bank code that is associated with the bank from which you expect payment for this receivable. PeopleSoft Receivables does not use this field in the Cash Forecast report. |
100 |
BANK_ACCT_KEY |
Character |
Optional |
If you use PeopleSoft Cash Management cash positioning options, enter the bank account key that is associated with the bank account from which you expect payment for this receivable. PeopleSoft Receivables does not use this field in the Cash Forecast report. |
101 |
DD_BU |
Character |
Optional |
The Create Direct Debits Application Engine process (AR_DIRDEBIT) maintains this field. |
102 |
DD_ID |
Character |
Optional |
The Create Direct Debits process maintains this field. |
103 |
DD_STATUS |
Character |
Optional |
The Create Direct Debits process maintains this field. |
104 |
DD_PROFILE_ID |
Character |
Optional |
Direct debit profile that is assigned to the item. The profile defines the direct debit processing rules for the item. |
105 |
DD_CURRENCY |
Character |
Optional |
The Create Direct Debits process maintains this field. |
106 |
DD_AMT |
Number |
Optional |
The Create Direct Debits process maintains this field. |
107 |
DD_AMT_BASE |
Number |
Optional |
The Create Direct Debits process maintains this field. |
108 |
DRAFT_TYPE |
Character |
Optional |
Select from the values that you establish in the PS_DRAFT_TYPE_TBL table. |
109 |
DRAFT_AMT_BASE |
Number |
Optional |
Draft amount in the business unit base currency. |
110 |
DOC_TYPE |
Character |
Optional |
Document type represents the business purpose of the financial transaction. It is assigned to only one journal code. Important! You must include a value in this field if you enable the Document Sequencing option for installation and the PeopleSoft General Ledger business unit is associated with the PeopleSoft Receivables business unit. |
111 |
DOC_SEQ_NBR |
Character |
Optional |
The document sequencing number is either automatically assigned or manually entered sequentially based on the PeopleSoft General Ledger business period at either the journal code level or the document type level within journal code. Important! You must include a value in this field if you turn on the Document Sequencing option for your installation and the PeopleSoft General Ledger business unit is associated with the PeopleSoft Receivables business unit. |
112 |
DOC_SEQ_DATE |
Date |
Required |
Date that the document sequencing number is assigned to a specific document or the date that the document was created. The system automatically populates this field for items that you enter online. However, you must include a value in this field if you turn on the Document Sequencing option for your installation and the PeopleSoft General Ledger business unit is associated with the PeopleSoft Receivables business unit. Important! The Receivable Update process requires a value in this field to post an item. |
113 |
DOC_SEQ_STATUS |
Character |
Optional |
The status that is used for posting a document with document sequencing. If blank, then the document is valid for posting. |
114 |
PROCESS_INSTANCE |
Number |
Optional |
Enter 0. The Receivable Update process uses this field. |
115 |
USER_AMT1 |
Number |
Optional |
This field is for your use. |
116 |
USER_AMT2 |
Number |
Optional |
This field is for your use. |
117 |
USER_AMT3 |
Number |
Optional |
This field is for your use. |
118 |
USER_AMT4 |
Number |
Optional |
This field is for your use. |
119 |
USER_AMT5 |
Number |
Optional |
This field is for your use. |
120 |
USER_AMT6 |
Number |
Optional |
This field is for your use. |
121 |
USER_AMT7 |
Number |
Optional |
This field is for your use. |
122 |
USER_AMT8 |
Number |
Optional |
This field is for your use. |
123 |
USER_DT1 |
Date |
Optional |
This field is for your use. |
124 |
USER_DT2 |
Date |
Optional |
This field is for your use. |
125 |
USER_DT3 |
Date |
Optional |
This field is for your use. |
126 |
USER_DT4 |
Date |
Optional |
This field is for your use. |
127 |
USER1 |
Character |
Optional |
This field is for your use. |
128 |
USER2 |
Character |
Optional |
This field is for your use. |
129 |
USER3 |
Character |
Optional |
This field is for your use. |
130 |
USER4 |
Character |
Optional |
This field is for your use. |
131 |
USER5 |
Character |
Optional |
This field is for your use. |
132 |
USER6 |
Character |
Optional |
This field is for your use. |
133 |
USER7 |
Character |
Optional |
This field is for your use. |
134 |
USER8 |
Character |
Optional |
This field is for your use. |
135 |
USER9 |
Character |
Optional |
This field is for your use. |
136 |
USER10 |
Character |
Optional |
This field is for your use. |
137 |
DOUBTFUL |
Character |
Optional |
Flag to indicate that an item is a doubtful receivable (one for which you do not expect to receive payment). The Receivable Update process updates this field. Enter a space. |
138 |
DRAFT_BUSN_EVENT |
Character |
Optional |
Action that is taken on an item during draft processing. The Receivable Update process updates this field. Enter a space. |
139 |
DRAFT_SUB_EVENT |
Character |
Optional |
Action that is taken on an item during draft processing. The Receivable Update process updates this field. Enter a space. |
140 |
SALES_PERSON2 |
Character |
Optional |
Second team member that is assigned to the item. Select from the values that are established on the PS_TEAM_MEMBERS or enter a space. |
141 |
REGION_CD |
Character |
Optional |
Region code for the team members that are assigned to the item. Enter a value from the PS_REGION_CD table or enter a space. |
142 |
REVALUE_FLAG |
Character |
Optional |
Flag to indicate whether to revalue the item if its currency is different from the base currency. Enter Y to revalue the item. Otherwise, enter N. |
143 |
PACKSLIP_NO |
Character |
Optional |
The packing slip number that is associated with the item. |
144 |
SBI_NUM |
Character |
Optional |
Self-billed invoice number. This field is currently not used by PeopleSoft Receivables. You can populate it if you want to use it for custom reports. |
145 |
PC_DISTRIB_STATUS |
Character |
Optional |
Flag that indicates the status for distributing the item to PeopleSoft Project Costing. Enter D to indicate the item is already in PeopleSoft Project Costing, H to hold the item, I to ignore the item, M to indicate that the item was changed, or N to integrate the item in a project. |
146 |
VAT_ADVPAY_FLG |
Character |
Optional |
Flag to indicate if VAT was paid when you entered the advance payment for the item. Enter Y to indicate that VAT is paid on the advance payment. Otherwise, enter N. |
147 |
LC_ID |
Character |
Optional |
The letter of credit number that is associated with the item. The bank includes this number with the payment. You use it to match the payment with the item. |
148 |
AR_SEQ_NUM |
Number |
Optional |
The Receivable Update process updates this field when you create a draft item for a pending item. Enter a space. |
149 |
DRAFT_POST_ACTION |
Character |
Optional |
The system maintains this value for draft processing. Enter a space. |
150 |
VAT_TRANS_AMT |
Sign |
Optional |
Total amount of the item on which VAT is calculated. |
151 |
RECEIVABLE_TYPE |
Character |
Optional |
Receivable type code that is used to categorize information on the Receivables Due From Public report. Select a value that is defined on the PS_REC_TYPE_TBL. |
152 |
ENTITY_CODE |
Character |
Optional |
Entity code identifying a government agency for the Receivables Due From Public report. Select a value that is defined on the PS_ENTITY_TBL. |
153 |
CONTROL_AMT |
Sign |
Optional |
Control amount for worksheets. Enter a space. |
154 |
CONTROL_AMT_BASE |
Sign |
Optional |
Control amount in the base currency for worksheets. Enter a space. |
155 |
ANCHOR_BU |
Character |
Optional |
Anchor business unit for maintenance worksheets. Enter a space. |
156 |
ITM_PAY_AMT_BASE |
Sign |
Optional |
Used by the system when the payment amount is in the base currency. Enter a space. |
157 |
PPRC_PROMO_CD |
Character |
Optional |
Promotion code that is assigned to the item. |
158 |
CLAIM_NO |
Character |
Optional |
Claim number for deductions. |
159 |
CONTROL_CURRENCY |
Character |
Optional |
Control currency for maintenance worksheets. Enter a space. |
160 |
CONTROL_CURR_BASE |
Character |
Optional |
Base control currency for maintenance worksheets. Enter a space. |
161 |
CONTROL_RATE_MULT |
Sign |
Optional |
Control rate at which the taxes are calculated. The value that appears here is determined by the value in the Calc Scheme (calculation scheme) field and is always a percentage. |
162 |
CONTROL_RATE_DIV |
Number |
Optional |
Control rate at which the taxes are calculated. The value that appears here is determined by the value in the Calc Scheme field and is always a percentage. |
163 |
CONTROL_RT_TYPE |
Character |
Optional |
Control rate type to use to calculate the exchange rate between the default reporting currency code and the override currency code. |
164 |
AR_SPECIALIST |
Character |
Optional |
An assignment of the pending item to an AR specialist. Select from the values that you establish in the PS_AR_SPECIALIST table. |
165 |
BROKER_ID |
Character |
Optional |
Identifier code for the individual who negotiated a promotion deal. Select from the values that you establish on the PS_CUSTOMER table where the Broker flag is checked. |
166 |
CARRIER_ID |
Character |
Optional |
Unique identifier for the shipping carrier. Select from the values that you establish on the PS_CARRIER_ID table. |
167 |
CLAIM_DT |
Date |
Optional |
Date of claim or debit memo. |
168 |
CLASS_OF_TRADE |
Character |
Optional |
Type of industry market, such as groceries, hardware, appliances. |
169 |
DEDUCTION_STATUS |
Character |
Optional |
Indicates the reason that an item is a deduction. Select from the values that you establish on the PS_DEDUCTION_TBL. |
170 |
DEDUCTION_DT |
Date |
Optional |
Date that the deduction was created. |
171 |
DIVISION |
Character |
Optional |
Geographic area within an organization. |
172 |
DT_INVOICED |
Date |
Optional |
The date that the associated invoice was created. The date is established when the invoice is created the billing system. This value cannot be changed. |
173 |
INV_PROD_FAM_CD |
Character |
Optional |
Identifier that defines inventory items at a high level. Examples might include computer items and office furniture. Select a value that is defined on the PS_INV_ITEM_FAM table. |
174 |
INVOICE |
Character |
Optional |
Original invoice that is associated with the item. |
175 |
INVOICE_BU |
Character |
Optional |
Code to identify the PeopleSoft business unit that is associated with an invoice. |
176 |
MAJOR_CLASS |
Character |
Optional |
Identifier for a group of customers in a trade, such as grocers or mass merchandisers. |
177 |
MEMO_STATUS_CD |
Character |
Optional |
(USF) Code that indicates the current status of a delinquent item. Enter a value that you defined on the MEMO_STATUS_TBL table. |
178 |
MERCH_TYPE |
Character |
Optional |
Use to track merchandising activity that is associated with promotions. |
179 |
PROOF_OF_DELIVERY |
Character |
Optional |
Proof of delivery slip number. |
180 |
SHIP_FROM_BU |
Character |
Optional |
Ship from business unit. |
181 |
SHIP_TO_ADDR_NUM |
Number |
Optional |
Address location for the ship to customer. Select from the values on the PS_CUST_ADDRESS table for the customer. |
182 |
SHIP_TO_CUST_ID |
Character |
Optional |
Customer ID of the ship to customer. |
183 |
SOLD_TO_ADDR_NUM |
Number |
Optional |
Address location for the sold to customer. Select from the values on the PS_CUST_ADDRESS table for the customer. |
184 |
SOLD_TO_CUST_ID |
Character |
Optional |
Customer ID for the sold to customer. |
185 |
SUB_GROUP_ID |
Number |
Optional |
Used by the Automatic Maintenance process and the maintenance worksheet to identify the match group in which items are matched. Enter 99999. |
186 |
VAT_TREATMENT_GRP |
Character |
Optional |
A set of VAT treatments that are permissible on a single VAT transaction. |
187 |
PHYSICAL_NATURE |
Character |
Optional |
Identifies the nature of a transaction for VAT calculation. Values are: G: physical good. S: intangible or service. |
188 |
COUNTRY_LOC_BUYER |
Character |
Optional |
Country where the buyer is physically located. |
189 |
STATE_LOC_BUYER |
Character |
Optional |
State where the buyer is physically located. |
190 |
COUNTRY_LOC_SELLER |
Character |
Optional |
Country where the seller is physically located. |
191 |
STATE_LOC_SELLER |
Character |
Optional |
State where the seller is physically located. |
192 |
VAT_SVC_SUPPLY_FLG |
Character |
Optional |
Flag to indicate if the buyer or supplier rendered the service and where the service was performed. Values are: 1: Supplier's Location. 2: Buyer's location. 3: Where the service is physically performed. |
193 |
VAT_SERVICE_TYPE |
Character |
Optional |
Flag to indicate whether the service is freight transport. This flag enables other types of services to be identified. Valid values are 1: Freight Transport, 2: Other. |
194 |
COUNTRY_VAT_PERFRM |
Character |
Optional |
The country where the VAT service was performed. |
195 |
STATE_VAT_PERFRM |
Character |
Optional |
The state where the VAT service was performed. |
196 |
COUNTRY_VAT_SUPPLY |
Character |
Optional |
Country where the service is physically performed. |
197 |
STATE_VAT_SUPPLY |
Character |
Optional |
State where the service is physically performed. |
198 |
STATE_SHIP_FROM |
Character |
Optional |
The state from which the items that are billed on this line are shipped. |
199 |
STATE_SHIP_TO |
Character |
Optional |
The state to which the items that are billed on this line are shipped. |
200 |
VAT_RPT_CNTRY_SRC |
Character |
Optional |
Source for the VAT reporting country. Enter one of these values: 1: Ship from country. 2: Ship to country. 3: Country in the VAT entity. 4: Service Performed in country. 5: Supplier location country. 6: Buyer location country. 7: Buyer registration country. |
201 |
STATE_VAT_DEFAULT |
Character |
Optional |
Enter the state or province that is used to determine the VAT defaults if the Track VAT by Province field (COUNTRY_VAT_SUBD_FLG) on the COUNTRY_VAT_TBL is set to Y. |
202 |
DISC_TAKEN |
Sign |
Optional |
Discount that is taken for the line in the entry currency. If there is no discount amount, enter zero. |
203 |
GL_LVL |
Character |
Optional |
The general ledger level flag that is carried from billing indicates whether PeopleSoft Billing is to create accounting entries for a receivables item. This controls the action that is available in external pending item entry. Levels are: A: PeopleSoft Receivables creates general ledger accounting entries. B: PeopleSoft Billing creates accounting entries. N: No general ledger accounting entries are created. |
204 |
ITEM_LINE_ORIG |
Number |
Optional |
The line number of the original item for new overdue charge item lines that were created when the option Create Charge by Item Line is selected on the overdue charge ID. It allows new items to point back to the item for overdue charges. |
205 |
TOT_TAX_AMT |
Sign |
Optional |
Total tax amount on the schedule. This amount is the sum of the excise tax amount and sales tax amount for India. |
206 |
TOT_TAX_AMT_BSE |
Sign |
Optional |
The base amount that the system uses when calculating taxes for India. |
207 |
TOT_EXD_AMT |
Sign |
Optional |
Total excise duty tax amount for India. Required if the excise tax is applicable. |
208 |
TOT_EXD_AMT_BSE |
Sign |
Optional |
The base amount that the system uses when calculating excise taxes for India. |
209 |
TOT_STX_AMT |
Sign |
Optional |
Total sales tax amount for India. Required if the sales tax is applicable. |
210 |
TOT_STX_AMT_BSE |
Sign |
Optional |
The base amount that the system uses when calculating sales taxes for India. |
211 |
AG_REF_NBR |
Number |
Optional |
(NLD) The payment reference number from the acceptgiro form attached to the invoice. |
212 |
AR_IU_REQ |
Character |
Optional |
Leave blank. The system enters Y in this field if you modify ChartField values online that are balancing ChartFields to enable the Inter/Intraunit processor to generate interunit accounting entries. |
213 |
CLAIM_SETID |
Character |
Optional |
Leave blank. PeopleSoft Purchasing and PeopleSoft Order Management populate this field with a claim SetID for vendor rebates or claim backs when you interface claims to PeopleSoft Receivables. |
PeopleSoft delivers customizable user fields in PS_PENDING_ITEM that are exclusively for your use. If the implementation uses any of the fields in this table, make sure that the interface populates them:
Amount Fields |
Date Fields |
Character Fields |
USER_AMT1 |
USER_DT1 |
USER1 |
USER_AMT2 |
USER_DT2 |
USER2 |
USER_AMT3 |
USER_DT3 |
USER3 |
USER_AMT4 |
USER_DT4 |
USER4 |
USER_AMT5 |
USER5 |
|
USER_AMT6 |
USER6 |
|
USER_AMT7 |
USER7 |
|
USER_AMT8 |
USER8 |
|
USER9 |
||
USER10 |
Types of User-Defined Fields
This tables describes the types of user-defined fields:
Type |
Description |
Amounts |
The USER_AMT fields have a cumulative effect on PS_ITEM. When the Receivable Update process finds a value in any of the user amount fields on PS_PENDING_ITEM, it places that value in the same field on the corresponding PS_ITEM_ACTIVITY row. It also updates the corresponding user amount field arithmetically on PS_ITEM. |
Dates |
The system places all USER_DT fields on the corresponding ITEM_ACTIVITY record. However, USER_DT1 and USER_DT2 update PS_ITEM only if the value on PS_ITEM is NULL. USER_DT3 and USER_DT4 update PS_ITEM whenever the value on PS_PENDING_ITEM is not NULL. |
Characters |
The USER1 through USER10 fields overlay an existing value if the PS_PENDING_ITEM value is not cleared, regardless of the update entry field. Only fields with values are moved. If USER1 is not cleared on the item, its value can remain and a pending item can affect USER2, leaving intact the value of USER1. |
Populate the PS_PENDING_VAT table only if you are bringing in VAT information from a billing system. For each item with VAT information, enter one or two rows for each unique combination of VAT applicability, VAT transaction type code, and tax code to the PS_PENDING_VAT table as needed. Each row should have a different VAT sequence number.
The following table specifies a field type for each field. Use the field type to determine how to populate system-maintained fields and optional fields that you want to leave blank. Supply a space for character fields, a null value for date fields, and a zero for numeric fields.
Note. Use Application Designer to review the characteristics of each field in more detail.
Column |
Field Name |
Field Type |
Option/ Condition/ Required |
Field Description |
1 |
GROUP_BU |
Character |
Required |
Use the same value as the GROUP_BU on PS_GROUP_ CONTROL. |
2 |
GROUP_ID |
Character |
Required |
Use the same value as the GROUP_ID on PS_GROUP_ CONTROL. |
3 |
BUSINESS_UNIT |
Character |
Required |
Use the same value as the BUSINESS_UNIT on PS_ PENDING_ITEM. |
4 |
CUST_ID |
Character |
Required |
Use the same value as the CUST_ID on PS_PENDING_ITEM. |
5 |
ITEM |
Character |
Required |
Use the same value as the ITEM on PS_PENDING_ITEM. |
6 |
ITEM_LINE |
Number |
Optional |
Use the same value as the ITEM_LINE on PS_PENDING_ITEM. |
7 |
GROUP_SEQ_NUM |
Number |
Optional |
Use the same value as the GROUP_SEQ_NUM on PS_PENDING_ITEM. |
8 |
VAT_APPLICABILITY |
Character |
Optional |
Enter the VAT applicability on the VAT line. |
9 |
VAT_TXN_TYPE_CD |
Character |
Optional |
Provide the transaction type code on the VAT line. |
10 |
TAX_CD_VAT |
Character |
Optional |
Provide the VAT code on the VAT item line. |
11 |
VAT_DST_ACCT_TYPE |
Character |
Optional |
If VAT_APPLICABILITY is T (taxable) or S (suspended) and VAT_DCLRTN_POINT is P (payment) (on PENDING_ITEM), then populate VAT_DST_ACCT_TYPE with VAT output intermediate VOI. If PENDING_ITEM.VAT_DCLRTN_POINT is invoice, then populate VAT_DST_ACCT_TYPE with VAT output VO. If VAT_APPLICABILITY is E (exempt) or O (out of scope), then populate VAT_DST_ACCT_TYPE with VONT. |
12 |
VAT_SEQ_NUM |
Number |
Optional |
Enter a sequence number if two VAT lines have the same combination of VAT applicability, VAT transaction type, and tax code. |
13 |
TAX_CD_VAT_PCT |
Sign |
Optional |
Provide the tax percentage corresponding to the VAT code. |
14 |
VAT_DCLRTN_DT |
Date |
Optional |
Provide the invoice date for declaration point of invoice; provide the ship date for declaration point of delivery; leave blank for a declaration point date of payment. |
15 |
VAT_BASIS_AMT |
Sign |
Optional |
Provide the VAT basis amount for the summarized information on this VAT line. |
16 |
VAT_TRANS_AMT |
Sign |
Required |
Provide the VAT basis transaction amount for the summarized information on this VAT line. This amount is the VAT basis (that is, sales) amount before the application of any prompt payment discounts. |
17 |
VAT_TRANS_AMT_BSE |
Number |
Optional |
Provide the VAT basis transaction amount for the summarized information on this VAT line. This amount is the VAT basis (that is, sales) amount in base currency before the application of any available prompt payment discounts. |
18 |
VAT_AMT |
Sign |
Optional |
Provide the VAT amount for the summarized information on this VAT line if the pending item has an invoice declaration point. |
19 |
VAT_AMT_I |
Sign |
Optional |
Provide the VAT amount for the summarized information on this VAT line if the pending item has a payment declaration point. |
20 |
VAT_ERROR_FLAG |
Character |
Required |
Set value to N. |
21 |
ENTRY_CURRENCY |
Character |
Required |
The currency code for the VAT amount. Select from the values that are established on PS_CURRENCY_ CD_TBL. |
22 |
VAT_AMT_BASE |
Sign |
Optional |
Provide VAT amount in business unit base currency. |
23 |
VAT_BASIS_AMT_BASE |
Sign |
Optional |
Provide VAT basis amount in base currency. |
24 |
VAT_AMT_BASE_I |
Sign |
Optional |
Holds intermediate VAT amount when VAT is declared at payment. |
25 |
VAT_TREATMENT |
Character |
Optional |
Determines which default values are applied. The system handles VAT treatment separately for transactions involving goods and services. |
26 |
PHYSICAL_NATURE |
Character |
Optional |
Indicates whether an object is a good or a service. |
27 |
COUNTRY_LOC_BUYER |
Character |
Optional |
Location country of the buyer. This determines VAT defaulting for a VAT service type of Other if it is performed at the ship to location. |
28 |
STATE_LOC_BUYER |
Character |
Optional |
Location state of the buyer. This determines VAT defaulting for a VAT service type of Other if it is performed at the ship to location. |
29 |
COUNTRY_LOC_SELLER |
Character |
Optional |
Location country of the seller. This determines VAT defaulting for a VAT service type of Other if it is performed at the ship from location. |
30 |
STATE_LOC_SELLER |
Character |
Optional |
Location state of the seller. This determines VAT defaulting for a VAT service type of Other if it is performed at the ship from location. |
31 |
VAT_SVC_SUPPLY_FLG |
Character |
Optional |
Indicates the default place of supply for VAT on services. This determines where VAT is liable. |
32 |
VAT_SERVICE_TYPE |
Character |
Optional |
For VAT services treatment, indicates whether the VAT service type is 1 (Freight Transport) or 2 (Other). This value determines whether the VAT treatment appears by default based on the ship to and ship from locations (freight), or the buyer's and sellers location (other). |
33 |
COUNTRY_VAT_PERFRM |
Character |
Optional |
For services, determines the country in which the services is performed. |
34 |
STATE_VAT_PERFRM |
Character |
Optional |
For services, determines the state in which the services is performed. |
35 |
COUNTRY_VAT_SUPPLY |
Character |
Optiona |
For VAT services treatment, indicates the country of the default place of supply. |
36 |
STATE_VAT_SUPPLY |
Character |
Optional |
For VAT services treatment, indicates the country of the default place of supply. |
37 |
STATE_SHIP_FROM |
Character |
Optional |
PeopleSoft Receivables business unit location state. In the case of transactions involving goods or freight service transactions, this is used to determine the VAT treatment. |
38 |
STATE_SHIP_TO |
Character |
Optional |
Ship to customer location country. In the case of transactions involving goods or freight service transactions, this is used to determine the VAT treatment. |
39 |
STATE_VAT_DEFAULT |
Character |
Optional |
Enter the state or province that is used to determine the VAT defaults if the Track VAT by Province field (COUNTRY_VAT_SUBD_FLG) on the COUNTRY_VAT_TBL is set to Y. |
40 |
VAT_DFLT_DONE_FLG |
Character |
Optional |
Leave this field blank. The system populates this field for VAT items that are entered online. |
41 |
VAT_ENTRD_AMT |
Sign |
Optional |
Entered VAT amount in base currency. This amount is calculated from the transaction currency entered VAT amount, based on the exchange rate that is applicable to the transaction. |
42 |
VAT_CALC_AMT |
Sign |
Optional |
Shows the calculated VAT amount in the transaction currency. |
43 |
PROCESS_INSTANCE |
Number |
Optional |
Enter 0. The Receivable Update process updates this value. |
Populate the PS_PENDING_TAX and PS_PENDING_TAX_DTL tables only if you are bringing in taxes for India information from a billing system.
PS_PENDING_TAX Table
The following table specifies a field type for each field. Use the field type to determine how to populate system-maintained fields and optional fields that you want to leave blank. Supply a space for character fields, a null value for date fields, and a zero for numeric fields.
Note. Use Application Designer to review the characteristics for each field in more detail.
Column |
Field Name |
Field Type |
Option/Condition /Required |
Field Description |
1 |
GROUP_BU |
Character |
Required |
Use the same value as the GROUP_BU on PS_GROUP_ CONTROL. |
2 |
GROUP_ID |
Character |
Required |
Use the same value as the GROUP_ID on PS_GROUP_ CONTROL. |
3 |
BUSINESS_UNIT |
Character |
Optional |
Use the same value as the BUSINESS_UNIT on PS_ PENDING_ITEM. |
4 |
CUST_ID |
Character |
Optional |
Use the same value as the CUST_ID on PS_PENDING_ITEM. |
5 |
ITEM |
Character |
Optional |
Use the same value as the ITEM on PS_PENDING_ITEM. |
6 |
ITEM_LINE |
Number |
Optional |
Use the same value as the ITEM_LINE on PS_PENDING_ITEM. |
7 |
GROUP_SEQ_NUM |
Number |
Optional |
Use the same value as the GROUP_SEQ_NUM on PS_PENDING_ITEM. |
8 |
TAX_RATE_SEQ |
Number |
Optional |
Indicates the order in which tax component codes in the tax rate code are calculated. This line number is system generated. |
9 |
EXD_APPL_FLG |
Character |
Optional |
Enter Y to indicate that the business unit is excise-duty applicable. Otherwise, leave it blank. |
10 |
STX_APPL_FLG |
Character |
Optional |
Enter Y to indicate that the business unit is sales tax applicable. Otherwise, leave it blank. |
11 |
EXS_TAX_TXN_TYPE |
Character |
Optional |
Tax transaction type for the transaction. Values are: DEB: Direct export with bond. DEWB: Direct export without bond. DIMP: Direct import. DOM: Domestic. LEB: Local export with bond. LEWB: Local export without bond. LIMP: Local import. |
12 |
STX_TAX_AUTH_RPT |
Character |
Optional |
Enter a sales tax reporting authority. Select from the values that you establish on the PS_STX_TAX_AUTH table. |
13 |
STATE_SHIP_TO |
Character |
Optional |
The state where the items that are billed on this line are shipped. |
14 |
STATE_SHIP_FROM |
Character |
Optional |
The state from which the items that are billed on this line are shipped. |
15 |
EXS_TXN_LINE_AMT |
Sign |
Optional |
The total amount of transactions for the line. Each line has its own transaction total. The system uses this amount to calculate the taxes. |
16 |
EXD_TAX_CATG_CD |
Character |
Optional |
Enter an excise tax category code for the item. Select from the values that you establish on the PS_EXS_TAX_CATG table. |
17 |
STX_TAX_CATG_CD |
Character |
Optional |
Enter an sales tax category code for the item. Select from the values that you establish on the PS_EXS_TAX_CATG table. |
18 |
EXD_TAX_AMT |
Sign |
Optional |
The total amount of excise duty tax for the line. Each line has its own excise duty tax amount. The sum of all the excise duty amounts should equal the control excise duty amount. The control excise duty amount is the amount at field PENDING_ITEM.TOT_EXD_AMT. |
19 |
EXD_TAX_RATE_CD |
Character |
Optional |
Enter the tax rate code that is used to calculate the excise duty for each line. Select from the values that you establish on the PS_EXS_TAX_RATE table. |
20 |
EXD_TAX_AMT_BSE |
Sign |
Optional |
Excise duty in the business unit base currency. |
21 |
EXD_TAX_AMT_RPT |
Sign |
Optional |
The excise duty tax amount in the reporting currency. |
22 |
STX_TAX_AMT |
Sign |
Optional |
The total amount of sales tax for the line. Each line has its own sales tax amount. The sum of all the sales tax amounts should equal the control sales tax amount. The control sales tax amount is the amount at field PENDING_ITEM.TOT_STX_AMT. |
23 |
STX_TAX_RATE_CD |
Character |
Optional |
Enter the tax rate code that is used to calculate the sales tax for each line. Select from the values that you establish in the PS_EXS_TAX_RATE table. |
24 |
STX_TAX_AMT_BSE |
Sign |
Optional |
Sales tax amount in the business unit base currency. |
25 |
STX_TAX_AMT_RPT |
Sign |
Optional |
Sales tax amount in reporting currency. |
26 |
EXS_CURRENCY_RPTG |
Character |
Optional |
Enter the excise reporting currency. Select the CURRENCY_CD for the tax location that you define on the PS_ORG_TAX_LOC table. |
27 |
STX_FORM_CD |
Character |
Optional |
Sales tax form codes are assigned to tax rate codes. The form code helps determine the applicable forms for the transaction for form tracking purposes. Select from the values that you establish on the PS_STX_FORM_CODE table. |
28 |
BU_APPL_FLG |
Character |
Optional |
Business unit applicable flag. Set this field to Y, if excise duty or sales tax are applicable to the business unit. |
29 |
EXS_DTL_LINK |
Character |
Optional |
Leave blank. |
30 |
SUM_TOT_EXD_AMT |
Sign |
Optional |
Summary total of the total excise duty tax amounts. |
31 |
SUM_TOT_EXD_BSE |
Sign |
Optional |
Summary total of excise duty tax amounts in base currency. |
32 |
SUM_TOT_STX_AMT |
Sign |
Optional |
Summary total of the total sales tax amounts. |
33 |
SUM_TOT_STX_BSE |
Sign |
Optional |
Summary total of sales tax amounts in base currency. |
34 |
SUM_TOT_TAX_AMT |
Sign |
Optional |
Summary total of excise duty and sales tax amounts. |
35 |
RATE_DIV_RPT |
Number |
Optional |
Used to convert the base currency into the tax location reporting currency. |
36 |
RATE_MULT_RPT |
Sign |
Optional |
Used to convert the base currency into the tax location reporting currency. |
37 |
RT_TYPE |
Character |
Optional |
Rate type used to calculate the exchange rate between the default reporting currency code and the override currency code. |
38 |
EXD_TAX_RATE_SRC |
Character |
Optional |
Source transaction for the excise tax rate. Enter 1 (system-defined) or 2 (manually entered). |
39 |
STX_TAX_RATE_SRC |
Character |
Optional |
Source transaction for the sales tax rate. Enter 1 (system-defined) or 2 (manually entered). |
40 |
ORG_SETID |
Character |
Optional |
SetID for an organization. |
41 |
ORG_CODE |
Character |
Optional |
Organization code for a tax location. Select from the values that are established on the PS_ORG_RGSTN_DTL table. |
42 |
ORG_TAX_LOC_CD |
Character |
Optional |
Organization that is associated with a tax location code. Select from the values that are established on the PS_ORG_TAX LOC table. |
43 |
EXS_TXC_LN_STATUS |
Character |
Optional |
Excise tax calculation line status. |
44 |
EXD_UOM |
Character |
Optional |
Excise unit of measure for the assessable value. |
45 |
RATE_MULT_EXS |
Sign |
Optional |
Currency rate multiplier that is used to convert the base currency into the tax location reporting currency. Enter 1. |
46 |
RATE_DIV_EXS |
Number |
Optional |
Currency rate divisor that is used to convert the base currency into the tax location reporting currency. Enter 1. |
47 |
COUNTRY_SHIP_FROM |
Character |
Optional |
Country from which items are shipped. |
48 |
COUNTRY_SHIP_TO |
Character |
Optional |
Ship to country for the line item. |
49 |
RATE_MULT |
Sign |
Optional |
Used to convert the transaction currency into base currency. |
50 |
RATE_DIV |
Number |
Optional |
Used to convert the transaction currency into base currency. |
51 |
ENTRY_CURRENCY |
Character |
Optional |
The currency code for the tax amount. Select from the values that are established on PS_CURRENCY_ CD_TBL. |
PS_PENDING_TAX_DTL
The following table specifies a field type for each field. Use the file type to determine how to populate system-maintained field and optional fields that you want to leave blank. Supply a space for character fields, a null value for date fields, and a zero for numeric fields.
Note. Use Application Designer to review the characteristics of each field in more detail.
Column |
Field Name |
Field Type |
Option/Condition/Required |
Field Description |
1 |
GROUP_BU |
Character |
Required |
Use the same value as the GROUP_BU on PS_GROUP_ CONTROL. |
2 |
GROUP_ID |
Character |
Required |
Use the same value as the GROUP_ID on PS_GROUP_ CONTROL. |
3 |
BUSINESS_UNIT |
Character |
Optional |
Use the same value as the BUSINESS_UNIT on PS_ PENDING_ITEM. |
4 |
CUST_ID |
Character |
Optional |
Use the same value as the CUST_ID on PS_PENDING_ITEM. |
5 |
ITEM |
Character |
Optional |
Use the same value as the ITEM on PS_PENDING_ITEM. |
6 |
ITEM_LINE |
Number |
Optional |
Use the same value as the ITEM_LINE on PS_PENDING_ITEM. |
7 |
GROUP_SEQ_NUM |
Number |
Optional |
Use the same value as the GROUP_SEQ_NUM on PS_PENDING_ITEM. |
8 |
TAX_RATE_SEQ |
Number |
Optional |
The sequence number for the tax rate. This entry is manual for most excise adjustment types. |
9 |
EXS_TAX_RATE_CD |
Character |
Optional |
If this line is related to excise duty, enter the same excise duty that is entered in the PENDING_TAX.EXD_TAX_RATE_CD field. If this line is related to sales tax, enter the same sales tax that is entered in the PENDING_TAX.STX_TAX_RATE_CD field. The field EXS_TAX_TYPE is the field that indicates if the line is an excise duty line or a sales tax line. Enter the tax rate code that is used to calculate the excise duty for each line. Select from the values that you establish on the PS_EXS_TAX_RATE table. Leave blank if excise duty and sales tax should not be calculated for the line. |
10 |
EXS_TAX_RATE_SEQ |
Number |
Optional |
Indicates the order that tax component codes in the tax rate code are calculated. |
11 |
EXS_TAX_TYPE |
Character |
Optional |
Enter the type of tax to calculate in the line. Enter E for excise duty and S for sales tax. |
12 |
EXS_TAX_CMPNT_CD |
Character |
Optional |
Enter the tax component code. Select from the values that you establish on the PS_EXS_TAX_CMPNT table. |
13 |
EXS_TAX_DEP_CD |
Character |
Optional |
Enter the tax dependency code that indicates the basis for calculating the tax, as well as the precedence of taxes of the same tax type that must be included. Select from the values that you establish on the PS_EXS_TAX_DPNDNCY table. |
14 |
EXS_CALC_SCHEME |
Character |
Optional |
Indicates how the taxes are calculated. Enter P (percentage), Q (quantity), or A (amount). In PeopleSoft Receivables, only the percentage lines are calculated, but the others should be populated to be consistent with the tax rate code. |
15 |
EXS_TAX_RATE_PCT |
Number |
Optional |
Enter the percent of taxation that is associated with the corresponding tax rate code if the EXS_CALC_SCHEME is P. |
16 |
EXS_TAXRT_AMT |
Sign |
Optional |
Leave blank. |
17 |
EXS_TAXRT_AMT_BSE |
Sign |
Optional |
Leave blank. |
18 |
EXS_TAXRT_AMT_RPT |
Sign |
Optional |
Leave blank. |
19 |
EXS_TAX_RATE_UOM |
Character |
Optional |
Leave blank. |
20 |
EXS_CURRENCY_RPTG |
Character |
Optional |
Enter the code for the reporting currency. |
21 |
EXS_TAX_AMT |
Sign |
Optional |
The total amount of excise tax for the line. The sum of all the excise tax amounts should equal the control excise tax amount. |
22 |
EXS_TAX_AMT_BSE |
Sign |
Optional |
Excise tax amount in the base currency. |
23 |
EXS_TAX_AMT_RPT |
Sign |
Optional |
The total amount of excise tax for each line expressed in the reporting currency. |
24 |
EXS_BASIS_AMT |
Sign |
Optional |
Base amount against which taxes are calculated. |
25 |
EXS_BASIS_AMT_BSE |
Sign |
Optional |
The base amount that the system uses when calculating excise or sales taxes. This amount is the excise basis amount in the base currency. |
26 |
EXS_BASIS_AMT_RPT |
Sign |
Optional |
The base amount that the system uses when calculating excise taxes expressed in the reporting currency. |
27 |
EXS_CURRENCY_TRC |
Character |
Optional |
Leave this field blank. |
28 |
CURRENCY_CD |
Character |
Optional |
Use the value in the CURRENCY_CD field currency code on the PS_PENDING_ITEM table if it's available. Otherwise, use the ENTRY_CURRENCY on the PS_PENDING_ITEM table. |
29 |
ENTRY_CURRENCY |
Character |
Optional |
The currency code for the tax amount. Use the same value as the ENTRY_CURRENCY on the PS_PENDING_ITEM table. |
PeopleSoft Receivables supports multiple AR lines for each pending item, so we base all subsequent accounting entries that affect the PeopleSoft Receivables accounts on the AR lines in the Item Distribution table (PS_ITEM_DST).
Although you may choose not to distribute accounting information for billing transactions from PeopleSoft Receivables to the general ledger system, you must have at least one row in PS_ITEM_DST that represents the AR line. If you indicate that you do not want transactions with this entry type distributed to PeopleSoft General Ledger, the system sets the GL_DISTRIB_ STATUS field on PS_PENDING_DST to I (ignore). This setting instructs the Journal Generator Application Engine process (FS_JGEN) to skip this row when it creates journal entries.
When you convert existing items or interface them from your billing system, you may want to prevent distribution of accounting entries for a specific entry type even though you want to enable distribution when you record the entry online. Use the ALLOW_DST flag on PS_GROUP_CONTROL for this purpose.
You may choose to populate the PS_PENDING_DST table directly through your interface program, even though this approach is considered an exception within the system's accounting entries architecture.
The following table describes the fields on PS_PENDING_DST. The table specifies a field type for each field. Use the field type to determine how to populate system-maintained fields and optional fields that you want to leave blank. Supply a space for character fields, a null value for date fields, and a zero for numeric fields.
Note. Use Application Designer to review the characteristics of each field in greater detail.
Column |
Field Name |
Field Type |
Option/ Condition/ Required |
Field Description |
1 |
GROUP_BU |
Character |
Required |
Use the same value as the GROUP_BU on PS_GROUP_ CONTROL. |
2 |
GROUP_ID |
Character |
Required |
Use the same value as the GROUP_ID on PS_GROUP_CONTROL. |
3 |
BUSINESS_UNIT |
Character |
Required |
Use the same value as the BUSINESS_UNIT on PS_PENDING_ ITEM. |
4 |
CUST_ID |
Character |
Required |
Use the same value as the CUST_ID on PS_PENDING_ITEM. |
5 |
ITEM |
Character |
Required |
Use the same value as the ITEM on PS_PENDING_ITEM. |
6 |
ITEM_LINE |
Number |
Optional |
Use the same value as the ITEM_LINE on PS_PENDING_ITEM. |
7 |
GROUP_SEQ_NUM |
Number |
Optional |
Use the same value as the GROUP_SEQ_NUM on PS_PENDING_ITEM. |
8 |
LEDGER_GROUP |
Character |
Optional |
Leave this field blank. |
9 |
LEDGER |
Character |
Optional |
Leave this field blank. |
10 |
DST_SEQ_NUM |
Number |
Required |
Provide a sequence number to make each accounting entry line unique. |
11 |
PRIMARY_LEDGER |
Character |
Required |
Default value: Y. |
12 |
BUSINESS_UNIT_GL |
Character |
Required |
Provide the value of the general ledger business unit to which you post this accounting entry. |
13 |
ACCOUNT |
Character |
Required |
Select from the values that you establish on PS_GL_ACCOUNT_TBL. |
14 |
ALTACCT |
Character |
Optional |
Select from the values that you establish on the PS_ALTACCT_TBL. |
15 |
DEPTID |
Character |
Optional |
Select from the values that you establish on PS_DEPARTMENT_TBL. |
16 |
CF16_AN_SBR |
Subrecord |
Optional |
ChartFields subrecord that contains these ChartFields:
Select from the ChartField values that you defined. |
17 |
PC_CF1_N_SBR |
Subrecord |
Optional |
ChartFields subrecord that contains these ChartFields used in PeopleSoft Project Costing:
Select from the values that you defined in PeopleSoft Project Costing. The subrecord also contains a field for the analysis type. This value is not used in PeopleSoft Receivables. |
18 |
STATISTICS_CODE |
Character |
Optional |
Select from the values that you establish on PS_STAT_TBL as long as you do not enter a statistical account in the ACCOUNT field. |
19 |
MONETARY_AMOUNT |
Number |
Optional |
Provide the amount of the debit or credit in the business unit base currency. Debit entries must be positive. Credit entries must be negative. As long as you do not enter a statistical account in the ACCOUNT field, this value must be something other than zero. If you enter a statistical account, this value must be zero. |
20 |
STATISTIC_AMOUNT |
Number |
Conditional |
If you enter a statistical account in the ACCOUNT field, enter the appropriate statistical amount. |
21 |
CF_EDIT_STATUS |
Character |
Required |
Indicates if ChartFields are editable or restricted for edit. |
22 |
JRNL_LN_REF |
Character |
Optional |
If you supply a value and do not summarize accounting entries into fewer journal lines, the system places the value in this field on the PS_JRNL_LN table when you create journals by using the Journal Generator process. |
23 |
LINE_DESCR |
Character |
Optional |
If you supply a value and do not summarize accounting entries into fewer journal lines, the system places the value in this field on the PS_JRNL_LN table when you create journals by using the Journal Generator process. |
24 |
SYSTEM_DEFINED |
Character |
Conditional |
Accounting entry line type. Enter A if this line represents the debit or credit to the AR account (or control account) or if this line represents the offsetting information. PeopleSoft Receivables supports using more than one AR line per pending item. |
25 |
ACCOUNTING_DT |
Date |
Required |
Use the same value as the ACCOUNTING_DT on PS_PENDING_ITEM. |
26 |
FOREIGN_CURRENCY |
Character |
Optional |
Use the same value as the ENTRY_CURRENCY on PS_PENDING_ITEM. |
27 |
FOREIGN_AMOUNT |
Number |
Optional |
The debit or credit amount for this line in the entry currency of the item. The sum of the FOREIGN_AMOUNT values on all AR lines in PENDING_DST should equal the ENTRY_AMT field on PENDING_ITEM. |
28 |
RT_TYPE |
Character |
Conditional |
The rate type for the item. Required if the entry currency is different from the business unit base currency. Select from the values that are established on PS_CUR_RT_ TYPE_TBL or enter a space. |
29 |
RATE_MULT |
Number |
Optional |
Required if the entry currency differs from the business unit base currency. |
30 |
RATE_DIV |
Number |
Optional |
Required if the entry currency differs from the business unit base currency. |
31 |
CURRENCY_CD |
Character |
Optional |
Code that identifies the type of currency for an amount, such as USD or EUR. |
32 |
GL_DISTRIB_STATUS |
Character |
Required |
If you want to distribute this accounting entry from PeopleSoft Receivables to the general ledger system (after the Receivable Update process posts it), provide an N. If you do not want to distribute this accounting entry, provide an I. |
33 |
DOC_TYPE |
Character |
Optional |
Document type represents the business purpose of the financial transaction. This value is assigned to one and only one journal code. Important! If you have turn on the Document Sequencing option for your installation and the PeopleSoft General Ledger business unit that is associated with the PeopleSoft Receivables business unit, you must include a value in this field. |
34 |
DOC_SEQ_NBR |
Character |
Required |
The document sequencing number is either automatically assigned or manually entered sequentially based on the PeopleSoft General Ledger business period at either the journal code level or the document type level within the journal code. Important! If you turn on the Document Sequencing option for your installation and the PeopleSoft General Ledger business unit that is associated with the PeopleSoft Receivables business unit, you must include a value in this field. |
35 |
DOC_SEQ_DATE |
Date |
Optional |
The date that the document sequencing number is assigned to a specific document or the date that the document is created. Important! The Receivable Update process requires a value in this field to post an item if you turn on the Document Sequencing option for your installation and the PeopleSoft General Ledger business unit is associated with the PeopleSoft Receivables business unit. |
36 |
DOC_SEQ_STATUS |
Character |
Optional |
The status that is used for posting a document with the Document Sequencing option. If it's blank, then the document is valid for posting. |
37 |
MOVEMENT_FLAG |
Character |
Optional |
Activate to pass document sequencing that is performed in PeopleSoft Receivables to PeopleSoft General Ledger. |
38 |
USER1 |
Character |
Optional |
This field is for your use, similar to the user fields on PS_PENDING_ITEM. |
39 |
USER2 |
Character |
Optional |
This field is for your use, similar to the user fields on PS_PENDING_ITEM. |
40 |
USER3 |
Character |
Optional |
This field is for your use, similar to the user fields on PS_PENDING_ITEM. |
41 |
USER4 |
Character |
Optional |
This field is for your use, similar to the user fields on PS_PENDING_ITEM. |
42 |
USER5 |
Character |
Optional |
This field is for your use, similar to the User fields on PS_PENDING_ITEM. |
43 |
VAT_APPLICABILITY |
Character |
Optional |
VAT applicability for the distribution line. Use the same value as on PS_PENDING_ITEM. |
44 |
VAT_TXN_TYPE_CD |
Character |
Optional |
VAT transaction type code for the item. Use the same value as on PS_PENDING_ITEM. |
45 |
TAX_CD_VAT |
Character |
Optional |
VAT tax code for the item. Use the same value as on PS_PENDING_ITEM. |
46 |
VAT_DST_ACCT_TYPE |
Character |
Optional |
VAT distribution account type. Use the same value as on PS_PENDING_ITEM. |
47 |
ENTRY_EVENT |
Character |
Optional |
Code that is used by the federal government to post pro-forma accounting information. The Entry Event Generator generates supplemental accounting lines if you enter this code. |
48 |
IU_ANCHOR_FLAG |
Character |
Optional |
Flag to indicate that this line is the anchor line for interunit and intraunit accounting entries and for inheritance. Enter Y or N. |
49 |
IU_SYS_TRAN_CD |
Character |
Optional |
System transaction code that is used to generate interunit and intraunit accounting entries. Enter ARIT. |
50 |
IU_TRAN_CD |
Character |
Optional |
Transaction code that is used to generate interunit and intraunit accounting entries. Enter GENERAL. |
51 |
OPEN_ITEM_KEY |
Character |
Optional |
If you selected OpenItem Account for the account in the distribution line during setup, enter a value for the prompt field and record that you specified for the account. Note. The interface from PeopleSoft Billing to PeopleSoft Receivables sets this value to NULL. |
52 |
PROCESS_INSTANCE |
Number |
Optional |
Updated by the Receivable Update process with the process instance that is used for a given execution of the process. Because the system calculates this value for you, enter 0. |
When the Receivable Update process finds errors, the process updates the AR_ERROR_CD field in the PENDING_ITEM table with an error code.
If you create accounting entries during the Receivable Update process, the process creates and balances the accounting entries before editing further. If the process does not create the accounting entries, or they are incorrect, the AR_ERROR_CD field contains a value of ACTOB.
If you receive this error code, follow these troubleshooting steps:
Attempt to create the accounting entries online by bringing up one of the pending items that is in error (Accounts Receivable, Receivables Updates, Correct Posting Errors, External Items).
Select a pending item with out-of-balance accounting entries.
On the Accounting Entry page, click the Create button.
If the accounting entries do not appear, the accounting entry setup is incomplete or in error, and you should receive an error message from the online system.
If the accounting entries appear, then your billing or conversion interface setup is incomplete or incorrect. Check the interface to verify that the following field values are correct before the group is posted:
PENDING_ITEM.DST_BAL_ITEM should be set to O.
Make sure that the following fields in PENDING_ITEM have values: RATE_DIV, RATE_MULT, ENTRY_AMT_BASE, DST_ID_AR.
Once accounting entries are correct and balanced, the Receivable Update process continues with two types of edits. The Receivable Update process edits the PS_PENDING_ITEM table through a series of editing updates and then through specific program logic.
See Also