Write View File interface for JD Edwards
About the Write View to File Interface
The PO Approval – Write View to File - interface is used to create a file to do PO Approvals.
Write View to File works with view VD3N4382. This interface was written in NER.
| Name | Function name | Description |
|---|---|---|
| DD3N4382 | dcLINK MBL – PO Approval – Write View to File | |
| ND3N4382 | dcLINKMBL_POAPPROVAL_VIEWTOFILE | dcLINK MBL – PO Approval – Write View to File Entry |
Processing
This API is used for MobileApps.
View VD3N4382 has three tables joined together. It processes data based on these three tables' joint condition. F4209 – Held Orders, F4301 - Purchase Order Header, and F0101 - Address Book Master. This interface deletes old records from table FD3N4382 and populates fresh records in table FD3N4382 for each time the API is executed. Table FD3N4382 gets populated based on Person Responsible, Status Approval, Release Date, and Transaction date.
Criteria for data selection
Selected columns for view - VD3N4382
Input data structure DD3N4382
The Input data structure for the Write View File.
| Name | Default value | Notes | ||||
|---|---|---|---|---|---|---|
| R/O | Alias | |||||
| mnPersonResponsible_RPER | R | RPER | ||||
| szStatusApproval_ASTS | R | ASTS | ||||
| jdDateTransactionJulian_TRDJ | R | TRDJ | ||||
| jdDateReleasedJulian_RDJ | R | RDJ | ||||
| cErrorCode_ERRC | ERRC | |||||
| szErrorMessageKey_EKEY | EKEY | |||||
| szAttachmentNameObject_OBNM | OBNM | |||||
O = Optional
R = Required
X = Required, but will default in if not passed
C = Conditional.
Required fields
Required fields for the Write View File.
Populate these records in table FD3N4382.
The following are Required fields.
-
BF mnPersonResponsible_RPER
-
BF jdDateReleasedJulian_RDJ
-
BF szStatusApproval_ASTS
-
BF jdTransactionJulian_TRDJ
Verify the process
In EnterpriseOne, the application has run, open the table to verify that all records are inserted to the table FD3N8342.
To verify that all records are inserted to the table FD3N8342, complete the following.
-
In EnterpriseOne,enter “databrowser”.
-
Select the table to view records.Example
Transaction test scenarios
Testing scenarios for the View File Transaction.
The following test scenarios demonstrate a variety of ways in which this interface could be used, and the fields that would be passed for each scenario. The data structure fields are in the left column, and the corresponding values for each scenario are listed by column.
| Field Name | Creates view for PO approval |
|---|---|
| mnPersonResponsible_RPER | 2207072 |
| szStatusApproval_ASTS | 2N |
| jdDateTransactionJulian_TRDJ | 1/1/2014 |
| jdDateReleasedJulian_RDJ | 10/31/2014 |
| cErrorCode_ERRC | |
| szErrorMessageKey_EKEY | |
| szAttachmentNameObject_OBNM |
Loading...
There was a problem loading this topic