Factivity Interface Load Plants and Locations Table interface for JD Edwards
About the Factivity Interface Load Plants and Locations Table interface
This interface is used to obtain a list of branch/plants and locations.
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 Edwards utilizing Advanced Inventory's existing shop floor interfaces (super backflush, completions, hours and quantities, issues, etc.).
Specifically, this interface will read the Location Master file (F4100) to obtain a list of branch/plants and locations. Each branch/plant/location combination read will be formatted and written to the FD3N0015 table.
| Name | Function name | Description |
|---|---|---|
| DD3N0015 |
dcLINK Factivity Interface Load Plant and Locations Table |
|
| FD3N0015 |
dcLINK Factivity Interface Load Plant and Locations Table |
|
| ND3N0015 |
dcLINKFactInterfaceLoadLocs |
dcLINK Factivity Interface Load Plant and Locations Table |
The full name of this interface is ND33N0015 Factivity Interface Load Plants and Locations Table
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 it's processing.
Common error messages
This interface does not generate any error messages.
Processing
This NER can be run to load the branch/plants and locations.
If you are setting this up for the first time, the FD3N0015 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. If the user passes in a branch/plant, then only the locations for that one branch/plant will be written to the work file. Otherwise all locations for all branch plants will be written to the FD3N0015 table.
The first process this NER performs is to clear the work file ND3N0015 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 branch/plant, and the location. Each branch/plant read from the F4100 will be used to read the inventory constants file (F41001). If there is no entry, that branch/plant isn't being used to hold any inventory. Therefore it will be skipped in the download.
This NER can be run at any time to load the branch/plants/locations. Typically, that's not a file that changes often, so the frequency of this could be monthly or bi monthly.
This NER has no required fields, but entering a value in the branch/plant is one way in which you can control what is loaded. 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 Work with Location Master application to obtain a list of all branch/plants and locations.
To view a list of the branch/plants and locations, complete the following stepsTo verify that the processing completed successfully, complete the following steps..
-
Use UTB to browse the work file FD3N0015.
-
Use the Work with Location Master application (P4100) to see all the branch/plants.
-
Each branch/plant shown, that also has an entry in the inventory constants, should show up in the FD3N0015 table.
Input data structure
Input Data Structure for DD3N0015.
| 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. |
|
| bsBranchPlant_MCU |
O |
MCU |
If a value is entered into this field, then only the locations for the branch plant entered will be downloaded. |
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 plants |
|---|---|
| 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 |
|
| bsBranchPlant_MCU |
Loading...
There was a problem loading this topic