Upload Item Quantity To interface for JD Edwards
About the Upload Item Qty To interface
This NER will update the FD3N4121 – Item details from F41021 and F4101 based on selection criteria. This function was created to speed up loading process to work file compare to use SQL statement.
| Name | Function name | Description |
|---|---|---|
| DD3N41021 | dsi Upload Item Qty to FD3N41021 | |
| ND3N4121 | dsiUploadItemQtyToWorkFile | dsi Upload Item Qty to FD3N41021 |
This guide applies to the newest version of the ERP.
Processing options
This interface has no processing options.
[Body Empty]
Processing
This business function udpates the FD3N4121 table with serialized or non-serilized item. NER fetch data from F41021 and F4101 based on user input data ( Item, Description / Item, Location / Item Lot Number). When Item is serialized its accumulate quantity total based on Item, Cost Center and Location.
Required fields
The item number, Description / Item number, Location / Item number and Lot number, then a best practice would be to also include cost center for this transaction.
Verifying the processing
All records has been uploaded to work file FD3N4121. Open the table in data browser and verify records has been added into the table.
| dcLINK Action cod | Description |
|---|---|
| 0 | Always defaults to a 0. No different action takes place based on this code. |
Input data structure - DD3N41021
| Name | Default value | R/O | Alias | Notes |
|---|---|---|---|---|
| dcLINKActionCode_EV01 | 0 | X | EV01 | Always defaults to a 0. No different action takes place based on this code. |
| cdcLINKReplaceCounts_EV01 | O | EV01 |
Blank – accumulate the count ‘1' – replace the count |
|
| jdDateUpdated_UPMJ | Current Date | X | UPMJ | Retrieved from GetAuditInfo |
| mnTimeOfDay_TDAY | Current Time | X | UPMT | Retrieved from GetAuditInfo |
| szUserId_USER | Current User | X | USER | Retrieved from GetAuditInfo |
| szWorkStationId_JOBN | Current Workstation | X | JOBN | Retrieved from GetAuditInfo |
| szProgramId_PID | ND3N4121 | X | PID | Defaulted in program if not passed in |
| szVersion_VERS | X | VERS | NA | |
| cSuppressErrMsg_EV01 | O | EV01 | ||
| cErrorCode_ERRC | Blanks | X | ERRC | Defaulted in program |
| szErrorMessageKey_EKEY | X | EKEY | Defaulted in program | |
| iDebugLevel_INT01 | O | INT01 | Displays M&D Debug statements if the value is greater than 0 | |
| szGuidUniqueID_GUID | Automatically generated by MEP | O | CFRGUID | If generate GUIDs is turned on in the MEP 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 | O, R | 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 MEP. 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 | O | FULLNAME1 | This field is the full name of the GUID Approver 1. | |
| szGuidApprover2_USR2 | O, R | 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 | O | FULLNAME2 | This field is the full name of the GUID Approver 2. | |
| mnGuidReasonCode1_REASON1 | O, R | 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 | 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 | O, R | 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 | 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 | O | FMNMVERS | In PeopleSoft the screen ID where the change was made is captured. MEP captures the script ID. | |
| szGuidTextMessage_TEXTMES | O | TEXTMES | This is a free form entry field. | |
| szIdentifiers2ShortItem_LITM | R | LITM | User need to enter item number. | |
| cSerialNumberRequired_SRNR | Y | O | SRNR | Always value is ‘Y' and defaulted |
| szDescriptionLine1_DSC1 | O, R | DSC1 | If required, please enter to match F4101 | |
| szCostCenter_MCU | O | MCU | Optional | |
| szLocation_LOCN | O, R | LOCN | If required, please enter | |
| mnIdentifierShortItem_ITM | O | ITM | Optional | |
| szLot_LOTN | O, R | LOTN | If required, please enter | |
| mnQtyOnHandPrimaryUn_PQOH | O | PQOH | Optional |
R = Required
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 | Serialized upload | Non-serialized upload |
|---|---|---|
| szIdentifiers2ShortItem_LITM | 220 | 220 |
| szDescriptionLine1_DSC1 | Bike | |
| szCostCenter_MCU | M30 | M30 |
| szLocation_LOCN | 1 A 1 | |
| szLot_LOTN | 123A |
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 overused error message can be received if any of the following situations are true:
|
References
Any related D3N objects used to support this NER.
| Object name | Description |
|---|---|
| BD3N0009 | dcLINK Utility – Turn Debug On and Off |
| DD3N0009 | dcLINK Utility – Turn Debug On and Off |
| BD3NSETU | dcLINK Set User ID |
| DD3NSETUSR | dcLINK Set User ID |
| BD3NSETA | dcLINK Utility Set Audit Info |
| DD3NSETA | dcLINK Utility Set Audit Info |
Loading...
There was a problem loading this topic