Fixed Assets Location Transfer interface for JD Edwards

About the Fixed Asset Location Transfer interface

This interface allows users to move a fixed asset from one location to another.

Each time a transfer is made a history record captures where it has been. The dcLINK version is called ND3N1215. This interface was written in NER and calls a ‘C' business function, BD3N1205, to retrieve the processing options from the interactive program P12115.

Name	Function name	Description
DD3N1215		dcLINK Interface Fixed Asset Location Transfer
ND3N1215	dcLINKInterfaceReleaseOrder	dcLINK Interface Fixed Asset Location Transfer
DD3N1205		PO Retrieval Fixed Asset Location Transfer
BD3N1205	PORetrievalFALocationTransfer	PO Retrieval Fixed Asset Location Transfer

The full name of this interface is ND3N1215 Fixed Assets Location Transfer

This interface guide applies to the following JDE versions.

EnterpriseOne Xe through 9.1

Corresponding EnterpriseOne application

In EnterpriseOne, the application you would run to release orders is P12115. This application can be found on menu G1211. Select the Location Inquiry app and from there the form exit Transfers.

Processing options

Processing options for ND3N1215.

The dream writer version will default to ZJDE0001 if not otherwise specified in the parameter list on the call.

Only three of these processing options are being used in this NER. The cUpdateChildRateCode_EV02 and cUpdateChildBillingAmount_EV03 are passed into the MBF F1204 Transfer Children. The other processing option that is used is cBillingInformation_EV01, which tells the interface if the billing information (business unit, object account, and subsidiary) that had been entered on a previous transfer should copy over when the asset is transferred to a new location. A value of ‘1' tells the system to not clear the billing information; a value of blank clears it.

Processing option data structure for DD3N1205

Our interface retrieves these parameters by calling BD3N1205 and is passed back in the following data structure.

Type	Description	Parameter
String	szVersion_VERS	Input
Char	cDisplayMeters_EV01	Output
Char	cUpdateChildRateCode_EV02	Output
Char	cUpdateChildBillingAmount_EV03	Output
String	szLocationCode_AL	Output
String	szLocation_LOC	Output
Char	cBillingInformation_EV01	Output
String	szP12215Version_VERS	Output
String	szP12120Version_VERS	Output

Processing

Processing information for performing a fixed asset location transfer.

At a minimum, what needs to be supplied to perform a transfer is the asset number, the location to which the asset is being moved, and the time when the transfer is to take place. The “when” can simply be the effective date of the transfer, assuming you are only moving the asset once a day. If the asset could be moved multiple times during the day, then you must also supply the beginning time.

Action codes

Technically this interface has two values for the dcLINKActionCode: a 1 and a 2. The ‘1' tells the interface to perform an asset transfer. The ‘2' tells the interface to do an asset inquiry. The inquiry does not return a list of the locations to which the asset has been transferred, so there is no practical reason to perform an inquiry.

Required fields

In order to perform a transfer, the asset number (mnAssetNumber_NUMB), and the location (szToLocation_MCU) to which the asset is being transferred must be passed in. The effective date (jdEffectiveDate_EFT) may be supplied, but will default to today's date if a value is not supplied.

Verify the processing

Verify the processing of the transfer.

To verify the processing, complete the following steps in JDE.

Open menu G1211.
Go to the location inquiry application and check the following fields.
Step Information
The Location to which the asset was just transferred will be marked as the current (C) location.

The Begin Date will be the effective date entered on the transfer.

The Previous Location will be a history (H) record.

The Ending Date will be the effective date entered.

Input data structure

Input data structure for DD3N0111.

Name	Default value	R/O	Alias	Notes
cdcLINKActionCode_EV01	1	X	EV01	1 = Fixed Asset Transfer. 2 = Inquiry only.
cActionCode_ACTION	Not used	X	ACTION
jdDateUpdated_UPMJ	Current Date	X	UPMJ	Retrieved from GetAuditInfo.
mnTimeUpdated_UPMT	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.
mnJobNumber_JOBS		O	JOBS
szProgramId_PID	ND3N1215	X	PID	Defaulted in program if not passed in.
szVersion_VERS	ZJDE0001	X	VERS	Defaulted in program if not passed in.
cSuppressErrorMessage_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.
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 contain 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.
mnAssetNumber_NUMB		R	NUMB	If a value is not passed in an error will be returned.
szSerialNumber_ASID		O	ASID
szToLocation_MCU		O	MCU	This is a required field if the dcLINKActionCode is equal to a “1” = Transfer.
szFromLocation_MCU	Current Location	O	MCU	When you make a transfer ,the from location will default to be the location where the asset is currently located.
jdEffectiveDate_EFT	Today's date	O	EFT	If this parameter is left blank it will default to today's date.
szBeginningTime_FTIME		O	FTIME	Enter a beginning time if you are planning on making multiple transfers on a single day.
szTransferNumber_TRNN		O	TRNN	This will be assigned by JDE when a transfer is made.
jdDateEnding_END		O	END
szEndTime_FTIME		O	FTIME
mnQuantity_QTY		O	QTY	If this is a transfer, this quantity is checked against the current quantity in F1201. If this quantity is greater than what's in the file, an error message is created.
szRemark_RMK	Blanks	O	RMK	Any value entered into the remark shows up on the transfer log. When I transferred an asset into the SHOP I used the remark to indicate what was wrong with the asset.
szEquipmentStatus_EQST		O	EQST	Any value entered will be validated against the UDC table 12/ES.
mnBillingAmount_AMTB		O	AMTB
szBusinessUnit_MCU	Blanks	O	MCU	Together with object account and subsidiary, this is used to identify where the billing should go.
szObjectAccount_OBJ	Blanks	O	OBJ	Together with business unit and subsidiary, this is used to identify where the billing should go.
szSubsidiary_SUB	Blanks	O	SUB	Together with business unit and object account, this is used to identify where the billing should go.
cSubledgerType_SBLT	Blanks	O	SBLT
szSubledger_SBL	Blanks	O	SBL
cTransferActionCode_ROS	Blanks	O	ROS	Blanks are valid 1 = Rented to Job 2 = Sold to Job 3 = Bought back from the job 4 = Future Use
szColumn_AISL		O	AISL
szRow_BIN		O	BIN
mnMeterReadingCurrent_MTRC		O	MTRC
mnMeterReadingOriginal_MTRO		O	MTRO

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	Transfer with just a date	Transfer using time	Transfer with account
cdcLINKActionCode_EV01		1
cActionCode_ACTION
jdDateUpdated_UPMJ
mnTimeUpdated_UPMT
szUserId_USER	Elvis	Elvis	Elvis
szWorkStationId_JOBN
mnJobNumber_JOBS
szProgramId_PID
szVersion_VERS	ZJDE0001	ZJDE0001	ZJDE0001
cSuppressErrorMessage_EV01
cErrorCode_ERRC
szErrorMessageKey_EKEY
iDebugLevel_INT01
szGuidUniqueID_GUID
szGuidApprover1_USR1
szGuidFullName1_FULLNAME1
szGuidApprover2_USR2
szGuidFullName2_FULLNAME2
mnGuidReasonCode1_REASON1
szGuidCommentField_COMMENTS
mnGuidReasonCode2_REASON2
szGuidCommentField2_2COMMENTS
szGuidScriptID_FMNMVERS
szGuidTextMessage_TEXTMES
mnAssetNumber_NUMB	2277	2277	2277
szSerialNumber_ASID
szToLocation_MCU	5100	SHOP	5100
szFromLocation_MCU
jdEffectiveDate_EFT	01/01/2013	01/10/2013	01/12/2013
szBeginningTime_FTIME		10:00:00
szTransferNumber_TRNN
jdDateEnding_END
szEndTime_FTIME
mnQuantity_QTY
szRemark_RMK		Bent Shaft
szEquipmentStatus_EQST
mnBillingAmount_AMTB
szBusinessUnit_MCU			5100
szObjectAccount_OBJ			1355
szSubsidiary_SUB			02800
cSubledgerType_SBLT
szSubledger_SBL
cTransferActionCode_ROS			1
szColumn_AISL
szRow_BIN
mnMeterReadingCurrent_MTRC
mnMeterReadingOriginal_MTRO

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. One way this error can be returned is if GUIDs are being used, and an error is returned from the business function dcLINK Utility Set Audit Info, or the utility dcLINK Utility Write Signature Capture Record. This error can also be returned if you are trying to do a transfer but transfer quantity is being split.
0626	Asset Number Invalid Input. The field mnAssetNumber_NUMB cannot be blank or null.
069D	Invalid Location. If dcLINKActionCode_EV01 is equal to a “1” (transfer), then the location filed szToLocation_MCU cannot be blank or null.
0769	Range Invalid. You can transfer an asset on the same date (effective date entered equals effective date in the file), but then the transfer times are compared. If the effective time passed in (mnTimeBeginning_DDTS) is less than the beginning time in the F1204 file, then it's an error.
078F	Insert to table failed. Either the insert to the F1204 or the insert to the F1210 failed.
078H	Update to table failed An error occurred updating either the F1204, the F1201, or the F1307 table. No update occurred.
078I	Fetch from table failed No record was found when we tried to return the current record in the F1204 file for the asset being processed (mnAssetNumber_NUMB).
2761	Quantity Invalid. This error is returned if the quantity passed in (mnQuantity_QTY) is greater than the current quantity in the asset master.
2776	Effective Date Invalid. This error is returned if the effective date passed in (jdEffectiveDate_EFT) is less than the effective date already entered in the F1204 file.
2867	Transfer Invalid. This error is returned if the disposal date (jdDateEnding_END) is less than the effective date (jdEffectiveDate_EFT).
3090	Business Unit Number Invalid as Entered. This error is generated if either the “from location” (szFromLocation_MCU), or the “to location” (szToLocation_MCU), fails the validation done by Get Cost Center Master Information business function. This error can also be raised if the business unit (szBusinessUnit_MCU) is passed in but fails the edit in Get Cost Center Master Information.

There was a problem loading this topic

Mobile Enterprise Platform