Factivity Interface Load Scrap Reason Codes interface for JD Edwards
About the Factivity Interface Load Scrap Reason Codes interface
This interface is used to read the UDC table 42/RC scrap reason codes and format and write them to the FD3N0012 table.
Factivity is a shop floor application written by MDSS that controls/coordinates shop floor activities. The user interface is typically a touch screen PC that allows workers to see what is being processed on each machine. Factivity is a standalone system meaning it's not tied to any ERP package. The purpose of these dcLINK Factivity interfaces is to read information in JD Edwards, format that information and write it to the FD3N file listed below. Factivity then imports that information, giving it what it needs to process JD Edwards work orders.
Information is reported back to JD Edwards utilizing Advanced Inventory's existing shop floor interfaces (super backflush, completions, hours and quantities, issues, etc.).
Specifically, this interface will read the UDC table 42/RC which contains the scrap reason codes. Each code read will be formatted and written to the FD3N0012 table.
| Name | Function name | Description |
|---|---|---|
| DD3N0012 |
dcLINK Factivity Interface Load Scrap Reason Codes |
|
| FD3N0012 |
dcLINK Factivity Interface Load Scrap Reason Codes Table |
|
| ND3N0012 |
dcLINKFactInterfaceLoadScrapReas |
dcLINK Factivity Interface Load Scrap Reason Codes |
This interface guide applies to the following JDE versions.
-
EnterpriseOne Xe through 9.1
Corresponding EnterpriseOne application
This interface is completely unique to loading Factivity. There is no corresponding application in EnterpriseOne.
Processing Options
This NER does not use any processing options to perform its processing.
Common error messages
This interface does not generate any error messages.
Processing
This NER can be run to load reason codes.
If you are setting this up for the first time, the FD3N0012 table needs to be built in the correct environment. Use the table operations tab in OMW to first generate the table, and then generate the indexes. This should be a one time setup for each environment that is going to be running the dcLINK Factivity interfaces.
Factivity expects data to be imported in a flat text file that uses the pipe character “|” to separate fields. There is no selection criteria for this program. Every reason code found (with the exception of 06 which is reserved for JD Edwards) in the UDC table 42/RC will be formatted and written to the FD3N0012 table.
The first process this NER performs is to clear the work file FD3N0012 of any records that may have been left in it from the last run.
As a general rule Factivity does not want leading or trailing blanks on any field. Therefore part of the processing this NER performs is to trim blanks off of the beginning and ending of each field.
This is one of the simplest of the file loads. It only contains two fields: the reason code, and the reason code description.
This NER can be run at any time to load the reason codes. Typically, this is not a file that changes often, so the frequency of this could be monthly or bi monthly.
This NER has no user input, therefore it has no required fields. It does have the standard fields used in any dcLINK data structure, but processes regardless of any entry made in those fields.
Verify the processing
Use the Factivity Interface Load Scrap Reason Codes interface to load and verify reason codes.
To load reason codes using this NER, complete the following stepsTo verify that the processing completed successfully, complete the following steps..
-
Use UTB to browse the work file FD3N0012.
-
Call up the UDC entry program and inquire on the UDC 42/RC.
-
Other than ‘06', which is reserved for JD Edwards, each entry in the UDC table should show up in the FD3N0012 table.
Input data structure
Input data structure for DD3N0012.
| Name | Default value | R/O | Alias | Notes |
|---|---|---|---|---|
| cdcLINKActionCode_EV01 |
X |
EV01 |
Not used. |
|
| cActionCode_ACTION |
X |
ACTION |
Not used. |
|
| jdDateUpdated_UPMJ |
X |
UPMJ |
Not used. |
|
| mnTimeOfDay_TDAY |
X |
TDAY |
Not used. |
|
| szUserId_USER |
X |
USER |
Not used. |
|
| szWorkStationId_JOBN |
X |
JOBN |
Not used. |
|
| mnJobNumber_JOBS |
O |
JOBS |
||
| szProgramId_PID |
X |
PID |
Not used. |
|
| szVersion_VERS |
X |
VERS |
Not used. |
|
| cSuppressErrMsg_EV01 |
O |
EV01 |
||
| cErrorCode_ERRC |
Blanks |
X |
ERRC |
Defaulted in program. |
| szErrorMessageKey_EKEY |
Blanks |
X |
EKEY |
Defaulted in program. |
| iDebugLevel_INT01 |
O |
INT01 |
Displays M&D Debug statements if the value is greater than 0. |
|
| cMisc_EV01 |
R |
EV01 |
Not used. |
X = Required but will default in if not passed
O = Optional
Transaction test scenarios
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 | Load scrap reason code |
|---|---|
| cdcLINKActionCode_EV01 |
|
| cActionCode_ACTION |
|
| jdDateUpdated_UPMJ |
|
| mnTimeOfDay_TDAY |
|
| szUserId_USER |
|
| szWorkStationId_JOBN |
|
| mnJobNumber_JOBS |
|
| szProgramId_PID |
|
| szVersion_VERS |
|
| cSuppressErrMsg_EV01 |
|
| cErrorCode_ERRC |
|
| szErrorMessageKey_EKEY |
|
| iDebugLevel_INT01 |
|
| cMisc_EV01 |
Loading...
There was a problem loading this topic