DR_ACTIVITY_VW(SQL View) |
Index Back |
---|---|
Latest Draft Activity View |
SELECT %subrec(DR_ACTIVITY_SBR, A) FROM PS_DRAFT_ACTIVITY A WHERE A.DTTM_CREATED = ( SELECT MAX(DTTM_CREATED) FROM PS_DRAFT_ACTIVITY A2 WHERE A.DRAFT_BU = A2.DRAFT_BU AND A.DRAFT_ID = A2.DRAFT_ID AND A.DRAFT_BUSN_EVENT = A2.DRAFT_BUSN_EVENT AND A.DRAFT_POST_ACTION = A2.DRAFT_POST_ACTION AND A.UNPOST_FLG = A2.UNPOST_FLG ) |
# | PeopleSoft Field Name | PeopleSoft Field Type | Database Column Type | Description |
---|---|---|---|---|
1 | DRAFT_BU | Character(5) | VARCHAR2(5) NOT NULL |
Identifies the Receivables business unit associated with a draft. This field is maintained by the Draft Creation process.
Prompt Table: DRAFT_CONTROL |
2 | DRAFT_ID | Character(15) | VARCHAR2(15) NOT NULL |
Uniquely identifies a payment draft. The Draft ID is system-generated during the Draft Creation process or manually entered.
Prompt Table: DRAFT_CONTROL |
3 | DTTM_CREATED | DateTime(26) | TIMESTAMP NOT NULL |
Datetime Created
Default Value: %Date |
4 | DRAFT_BUSN_EVENT | Character(2) | VARCHAR2(2) NOT NULL |
Defines the Draft life cycle event. It represents one of the actions that the PeopleSoft system has provided for Draft processing. Examples are: Approving a Draft Remitting a Draft to the Bank Voiding the Draft.
Prompt Table: DR_BUS_EVNT_TBL |
5 | DRAFT_POST_ACTION | Character(1) | VARCHAR2(1) NOT NULL |
Draft Post Action
A=Actual D=Dishonor |
6 | UNPOST_FLG | Character(1) | VARCHAR2(1) NOT NULL |
Unpost Flag
Y/N Table Edit Default Value: N |
7 | EVENT_DT | Date(10) | DATE |
The date upon which an accounting event is scheduled to be processed and converted into corresponding accounting
Default Value: %Date |
8 | POST_DT | Date(10) | DATE | The Date a transaction was Posted. |
9 | GROUP_BU | Character(5) | VARCHAR2(5) NOT NULL | Represents the high level grouping of multiple general ledger business units. |
10 | GROUP_ID | Character(15) | VARCHAR2(15) NOT NULL | Uniquely identifies a collection of pending items that are to be posted to accounts receivable. The identifier is manually entered or automatically generated by the system. |
11 | OPRID | Character(30) | VARCHAR2(30) NOT NULL | A user's ID (see PSOPRDEFN). |
12 | DOC_TYPE | Character(8) | VARCHAR2(8) NOT NULL | Specifies the business purpose of a financial transaction in countries that require all financial transactions to be tracked as "documents". A Document Type is associated with one and only one Journal Code. |
13 | DOC_SEQ_NBR | Character(12) | VARCHAR2(12) NOT NULL | Specifies the sequence number assigned to each financial transaction (a document). The sequence number may be manually entered or system-generated. |
14 | DOC_SEQ_DATE | Date(10) | DATE | Specifies the date that a document sequence number is assigned to a document or the date the document was created. |
15 | DOC_SEQ_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
A flag that indicates a document sequencing error. If there is no error the field is blank and document is considered valid for posting.
1=Document Sequencing Disabled A=GL BU Undefined B=GL BU Blank C=Accounting Date blank D=Doc Type Blank E=Jrnl Type, Code, Doc Undefine F=Sequence Range Undefine G=Max. Sequence Number Reached H=Manual Nbr for Auto Doc Type I=No Manual Number Entered J=Duplicate Manual Number K=Invalid Ledger L=Invalid Ledger Group N=No Status |
16 | ACTIVE_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
Transfer Template Status
A=Active I=Inactive Default Value: A |