Item Completions interface guide for JD Edwards
About the Item Completions interface
This interface is used to perform a "paperless" completion of an item.
There is no work order associated with the item being completed. All that is needed is the item being completed, the branch/plant, shift, the line the item was built, on and, of course, the quantity completed.
| Name | Function name | Description |
|---|---|---|
| DD3N1011A |
dcLINK Interface Item Completions |
|
| N3D3N1011 |
dcLINKInterfaceItemCompletions |
dcLINK Interface Item Completions |
The full name of this interface is ND3N1011 dcLINK Item Completions
This interface guide applies to the following JDE versions.
-
EnterpriseOne Xe through 9.1
Corresponding EnterpriseOne application
The corresponding E1 application is PF31011, Ad hoc Item Completions, which can be found on menu GF3112.
This interface doesn't require a work order to report completions, but it does expect a bill of materials to exist for that item and will throw a warning message if one is not found.
Processing options
The interactive version will default to ZJDE0001 if not otherwise specified in the parameter list on the call. The shift code, line identifier, and RF31011B version are all used by this interface. The lean check box value is passed into the UBE RF31011B.
Processing option data structure for DD3N3109
Our interface retrieves these parameters by calling BD3N3109 and is passed back in the following data structure.
| Type | Description | Parameter |
|---|---|---|
| String |
szPO_Version_VERS |
Input |
| Char |
cPO_ShiftCode_SHFT |
Output |
| Char |
cPO_LeanCheckBox_LCHBX |
Output |
| Char |
szPO_RF31011BVersion_VERS |
Output |
| String |
szPO_DFMLineIdentifier_DFMLINE |
Output |
| String |
cPO_AllowDupLotSerial_EV22 |
Output |
Processing
This is actually a pretty easy interface to run and doesn't require a lot of input. If the call is successful, you performed a work order completion, so validation of what happened is in all the usual places. Look in CARDEX and summary availability to make sure inventory went up by the number completed.
Required fields
The minimum required fields are the item number and branch plant. This assumes that the other needed fields will default from the processing options.
If you were not going to use any processing option fields, then you would need to pass the item number, the branch/plant, the shift, the line number, and either a quantity good or quantity bad.
Input data structure
Input data structure for DD3N4312C
| Name | Default value | R/O | Alias | Notes |
|---|---|---|---|---|
| cdcLINKActionCode_EV01 | Not used | o | EV01 | |
| cActionCode_ACTION | Not used | o | ACTION | |
| jdDateUpdated_UPMJ | Not used | o | UPMJ | |
| mnTimeUpdated_UPMT | Not used | o | UPMT | |
| szUserId_USER | Not used | o | USER | |
| szWorkStationId_JOBN | Not used | o | JOBN | |
| mnJobNumber_JOBS | Not used | o | JOBS | |
| szProgramId_PID | ND3N1011 | x | PID | |
| szVersion_VERS | ZJDE0001 | x | VERS | |
| cSuppressErrorMessage_EV01 | Not used | 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 | |
| szItemNumber_UITM | r | UITM | This is a required field, and the interface will return an error if nothing is passed in. | |
| szBranchPlant_MCU | r | MCU | This is a required field, and the interface will return an error if nothing is passed in. | |
| szLineCell_DFMLINE | r | DFMLINE | This is a required field, but may default in from the processing options, so it may not be necessary to pass in on the call. | |
| cShift_SHFT | r | SHFT | This is the shift the person was working that is reporting the completions. If left blank, the shift will default from the processing options. | |
| mnQuantityCompleted_SOQS | o | SOQS | The quantity good that is being reported complete. | |
| szUOM_UOM | o | UOM | If not entered, the unit of measure will default to the item's Production unit of measure. | |
| mnQuantityScrapped_SOCN | o | SOCN | The quantity bad that was is being reported. While it's not required that a quantity good be reported, or a quantity bad be reported, it is required that one of those two get reported. | |
| szLocation_LOCN | o | LOCN | Enter the location where the completed item(s) are being stored. If nothing is passed in, the default is the default location defined in the F41021 file. | |
| szLot_LOTN | o | LOTN | If this is a lot controlled item, enter the lot number of the completed item. | |
| szGuidUniqueID_GUID | Blanks | o | GUID | If generate GUIDs is turned on in the dcLINK configuration utility, this field will contain a GUID (guaranteed unique identifier). The GUID is used to tie database changes in PeopleSoft to the transactions that triggered those changes to occur. |
| szGuidApprover1_USR1 | Blanks | o | USR1 | An entry in this field or the Approver 2 field will cause a signature capture record to be written. Signature capture records are part of the GUID processing and should not be used unless a GUID is being created by dcLINK. The value of this field is a User ID, not an address book entry. There must be a value passed in to either this field or the approver 2 field, otherwise it is an error. |
| szGuidFullName1_FULLNAME1 | Blanks | o | FULLNAME1 | This field is the full name of the GUID Approver 1. |
| szGuidApprover2_USR2 | Blanks | o | USR2 | GUID processing supports up to two approvers. If two approvers are required, this is the user ID of the second approver. There must be a value passed in to either this field or the approver 1 field, otherwise it is an error. |
| szGuidFullName2_FULLNAME2 | Blanks | o | FULLNAME2 | This field is the full name of the GUID Approver 2. |
| mnGuidReasonCode1_REASON1 | Blanks | o | REASON1 | If either of the approver fields contains a value, but no value is entered into one of the reason code fields, then an error will be returned. Reason codes must match the valid reason codes setup for GUID processing, otherwise it is an error. |
| szGuidCommentField_COMMENTS | Blanks | o | COMMENTS | This is a free form entry field that is used to further explain the reason code entered into the previous field. |
| mnGuidReasonCode2_REASON2 | Blanks | o | REASON2 | If either of the approver fields contains a value, but no value is entered into one of the reason code fields, then an error will be returned. Reason codes must match the valid reason codes setup for GUID processing, otherwise it is an error. |
| szGuidCommentField2_2COMMENTS | Blanks | o | 2COMMENTS | This is a free form entry field that is used to further explain the reason code entered in the previous field. |
| szGuidScriptID_FMNMVERS | Blanks | o | FMNMVERS | In PeopleSoft, the screen ID where the change was made is captured. dcLINK captures the script ID. |
| szGuidTextMessage_TEXTMES | Blanks | o | TEXTMES | This is a free form entry field. |
| szCountryOfOrigin_ORIG | Blanks | o | ORIG | This is to pass Country Of Origin |
X = Required but will default in if not passed
O = Optional
Transaction test scenarios
The following test scenarios demonstrate a variety of ways 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.
Common error messages
The following are common error messages that can be generated by this BF and what those error messages mean.
| Error message | Meaning |
|---|---|
| 0002 |
Record Invalid. This error message can come from 3 different places in this interface.
|
| 0003 |
Blanks Invalid. If the item number passed in is equal to blanks or nulls, then this error message will be returned. The item number is a required field. |
Loading...
There was a problem loading this topic