Address book phone number maintenance interface for JD Edwards

About the Address Book Phone Number Maintenance interface

This interface allows a user to maintain phone numbers for an address book.

The address book phone number interface allows a user to maintain phone numbers for an address book. This specifically gives them the ability to maintain the area code and phone number, plus specify the kind of phone that is associated with the number. The dcLINK interface that allows this to be maintained is called ND3N0115.

Name	Function name	Description
DD3N0115		dcLINK Interface A/B Phone Numbers
ND3N0115	dcLINKABPhoneNo	dcLINK Interface A/B Phone Numbers

The full name of this interface is ND3N0115 Address Book Phone Number Maintenance

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 maintain address book phone numbers is P0115. To get to this program, go to menu G01 and select address book revisions. When the program loads, find the address book number to be maintained, highlight it, and select the row exit labeled Phones. This calls the program P0115.

Processing options

This business function does not retrieve or use any processing options.

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.

Field name	Add a phone number	Change a phone number	Delete a phone number
cdcLINKActionCode_EV01	0	0	0
cActionCode_ACTION	A	C	D
jdDateUpdated_UPMJ
mnTimeUpdated_UPMT
szUserId_USER
szWorkStationId_JOBN
szMachineKey_MKEY
mnJobNumber_JOBS
szProgramId_PID
szVersion_VERS
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
mnAddressNumber_AN8	527	527	527
szPhoneNumberType_PHTP	CAR	#&#
szPhoneAreaCode1_AR1	913
szPhoneNumber_PH1	322-2492
mnPhoneLineNo_RCK7		1	1
mnLineNumberID_IDLN	0	0	0

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. In the context of this BF, this error is returned when an error has been detected from one of these three business functions: dcLINK Set User ID, dcLINK Utility Set Audit Info, or dcLINK Utility Write Signature Capture Record.
0003	Blanks Invalid. This message is generated if the action code is equal to ‘C' or ‘D' and the field mnPhoneLineNo_RCK7 is equal to blank, null or zero.
018A	Not found in User Defined Code. The value passed in for the field szPhoneNumberType_PHTP is a valid value that is setup in the UDC table 01/PH.
043V	Phone Number Required. The phone number is required if the action code is equal to ‘A'.
138T	Action Code Invalid. The action code is not equal to ‘A', ‘C' or ‘D'.
341E	Address Book Master Record Not Found. For a change or delete, the Address Book Phone Number master record was not found. The key to this file is the address book number, the line number ID, and the phone line number.
3210	Invalid Change. This error is generated if the action code is equal to ‘C' but no value was passed in for the area code, phone number, or phone number type.
H00067	Invalid Address Book Number. The address book number must contain a value that is greater than zero.

Input data structure

Input data structure for DD3N0115.

Name	Default values	R/O	Alias	Notes
cdcLINKActionCode_EV01	0	X	EV01	Always defaults to a 0. No different action takes place based on this code.
cActionCode_ACTION	A	X	ACTION	A = add a phone number for the address book C = change an existing phone number D = delete an existing phone number
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.
szMachineKey_MKEY		X	MKEY
mnJobNumber_JOBS		O	JOBS
szProgramId_PID	ND3N4109	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	Automatically generated by dcLINK	O	CFRGUID	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		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 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		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 on which the change was made is captured. dcLINK captures the script ID.
szGuidTextMessage_TEXTMES		O	TEXTMES	This is a free form entry field.
mnAddressNumber_AN8		R	AN8	A valid address book number that already exists in the address book master.
szPhoneNumberType_PHTP		O	PHTP	This field identifies what type of phone associated with the phone number. Examples are: car, cell, home, work, fax, etc. The value in this field must be a valid value in the 01/PH UDC table.
szPhoneAreaCode1_AR1		O	AR1	The area code associated with the phone number.
szPhoneNumber_PH1		O	PH1	The phone number itself.
mnPhoneLineNo_RCK7		R	RCK7	Each phone number added under a who's who line has a unique line number.
mnLineNumberID_IDLN		R	IDLN	This is the who's who line number.

R = Required

X = Required but will default if not passed in

O = Optional

Processing

You can use this interface to maintain a phone number list for contacts in the address book master.

This interface maintains the phone number list for a who's who contact in the address book master. Different action codes are used to direct activity. The fields that can be changed are the area code, phone number, and phone type.

This interface supports three action codes (cActionCode_ACTION).

Action code	Description
A	Tells the interface to add a new line number to an existing who's who line. An example of this would be, referring to figure 1, entering a new value on the bottom grid row.
C	Tells the interface to change a specific line number that already exists for a who's who line. An example of this would be, referring to figure 1, changing the phone type on line 2 to ‘CAR'.
D	Tells the interface to delete a specific line number that already exists for a who's who line. Again referring to figure 1, it would be valid to delete line 1 or 2, but invalid to delete line 3 (it does not exist).

Required fields

As a script builder, do you let the NER default in values or do you map those values in the API call in the script? The answer to that question really cuts to the heart of the readability and maintainability of the scripts. It is very tempting to let the NER default as much as it needs to and keep the script “clean”. The only problem with that approach is it hides from the user items that may need to be changed. For example, some interfaces may require a different action code depending on what is being done. By allowing the NER to default the action code, it is not as observable to whoever has to edit the script, that the action code needs to be changed.

The address book number must be a valid existing address book number, regardless of the action code being used. The who's who line number (mnLineNumberID_IDLN) must be a valid existing number, regardless of the action code being used. The line number (mnPhoneLineNo_RCK7) must be a valid existing line number for changes or deletes. If passed in on an ‘add', it needs to be a number that does not already exist. If it does the ‘add' will fail. If line number is left off of an ‘add' transaction, this interface will determine what the next available line number is and use that value. The phone number (szPhoneNumber_PH1) is required for all ‘add' transactions. For a ‘change' transaction one of the three fields (area code, phone number, or phone type) must be supplied or an error will occur.

Special processing

The phone number must always be entered, but both the area code/prefix (szPhoneAreaCode1_AR1), and phone type (szPhoneNumberType_PHTP) are optional. If these fields already contain a value, but the user wants to blank them out, place the value #&# in field to be blanked out and then call this interface.

Remember the phone number is required and cannot be blanked out. This only works for the area code and phone type.

There was a problem loading this topic

Mobile Enterprise Platform