Factivity Interface Load Employees Table interface for JD Edwards
About the Factivity Interface Load Employees Table interface
This interface is used to obtain a list of employees.
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 Address Book file (F0101) to obtain a list of employees. Each branch/plant read will be formatted and written to the FD3N0014 table.
| Name | Function name | Description |
|---|---|---|
| DD3N0014 |
dcLINK Factivity Interface Load Employees Table |
|
| FD3N0014 |
dcLINK Factivity Interface Load Employees Table |
|
| ND3N0014 |
dcLINKFactInterfaceLoadEmplyee |
dcLINK Factivity Interface Load Employees 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 obtain a list of employees.
If you are setting this up for the first time, the FD3N0014 table needs to be built in the correct environment. Use the table operations tab in OMW to first generate the table, 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. Users have two fields that can be used to define the scope of employees that will be loaded into Factivity. First there is a Branch/Plant field. If this is left blank, all employees regardless of their branch/plant will be loaded. However, if a value is provided in this field, only the employees setup in that branch/plant will be selected. The other field that can be used is the Pay Type field. If a value is entered into this field, then only employees with a pay type that matches what was entered will be selected. Every selected employee will be written to the FD3N0014 table.
Unlike other Factivity interfaces that automatically clear this work file as a first step, the clear must be expressly called in this interface by passing a ‘9' in the dcLINKActionCode field. This was adopted because the employee file can be loaded by branch/plant. Each branch/plant can then control when they want their employees cleared and reloaded. If a branch/plant is passed into this business function, then only records for that branch/plant will be cleared.
As a general rule, Factivity does not want leading or trailing blanks on any field. Therefore part of the processing performed by this NER is to trim blanks off of the beginning and ending of each field.
This business function will only process address book entries that are defined as employees, address type equal to ‘E'. Once records have been selected from the Address Book Master, the Employee Master (F060116) is read to get the employee's pay status, pay type, and shift code. If the employee's pay status is not equal to ‘0' then the employee will not be selected. If the employee's pay type does not equal the pay type passed into the business function, then the employee will not be selected. Factivity only recognizes shifts that are 1 through 9. If an employee is setup on a shift outside of that range, then his shift will be changed to ‘1'. The final information that is retrieved is the employee's address, city, state, and zip. That information is retrieved by reading the Address by Date (F0116) file.
This NER can be run at any time to load the employees. It really depends on each client's workforce to know how often this needs to be run. A client with a stable workforce may only need to run this every couple of weeks. Clients that have lots of changes in their workforce may to have run this daily or weekly.
Troubleshooting Tip: If you were expecting lots of employees, but actually downloaded very few, double check that a value was entered for the employee's pay type.
The branch/plant is not required. If it is not entered, this business function will assume all branch/plants are to be processed. However, the pay type must be entered. The program makes a comparison between the employee's pay type and what was entered. If they are not equal, the employee is not selected.
Verify the processing
Use the Factivity Interface Load Employees Table to obtain a list of employees.
To obtain a list of employees using this NER, complete the following steps in JDE.
-
Use UTB to browse the work file FD3N0014. This interface is harder to verify because data really comes from a couple of different files.
-
Run UTB over the F0101 file to get a list of all employees with the correct branch/plant and employee type.
-
The final list of employees loaded could be less than this, as the pay type from the employee master might eliminate some from this list.
Input data structure
Input Data Structure for DD3N0014.
| Name | Default value | R/O | Alias | Notes |
|---|---|---|---|---|
| cdcLINKActionCode_EV01 |
X |
EV01 |
0 = Load FD3N0014 9 = Clear FD3N0014 |
|
| 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. |
|
| cPayTypeHSP_SALY |
R |
SALY |
This field must be entered. Only employees whose Employee Master file pay type matches what is entered here will be selected. |
|
| szBranchPlant_MCU |
O |
MCU |
If a value is entered into this field, then only employee's that are setup in the same branch/plant will be downloaded into the FD3N0014 file. The file purge is also conditioned on this value. If a branch/plant is entered then only employees for that branch/plant will be removed from the FD3N0014 file. |
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 all employees | Load only one branch/plant | Clear one branch/plant | Clear the entire file |
|---|---|---|---|---|
| cdcLINKActionCode_EV01 |
0 |
0 |
9 |
9 |
| 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 |
||||
| cPayTypeHSP_SALY |
S |
S |
||
| szBranchPlant_MCU |
30 |
30 |
Loading...
There was a problem loading this topic