Media Object Long Text interface for JD Edwards
About the Media Object Long Text interface
The Media Object Long Text interface is used to write and retrieve media object text. The Media Object Text interface is not used at this time. The ND3N0011 interface was written in NER and calls a “C” business function BD3N0011 to actually write & retrieve the text.
The Media Object Long Text interface includes the following functions:
Name | Function name | Description |
---|---|---|
ND3N0011 | dcLINKMOLongText | dcLINK Media Object Long Text |
dcLINKMediaObjectText | dcLINK Media Object Text | |
DD3N0011C | dcLINK Media Object Long Text | |
DD3N0011 | dcLINK Media Object Text | |
DD3N0011B | dcLINK Media Object Text String | |
BD3N0011 | dcLINKRetrieveMOTextString | dcLINK Retrieve Media Object Text String |
dcLINKWriteMOTextString | dcLINK Write Media Object Text String |
This guide applies to the newest version of the ERP.
Processing options
This interface has no processing options.
[Body Empty]
Processing
Depending upon the cdcLINKActionCode used, the interface will either add up to 15,000 characters of text, or it will retrieve up to 15,000 characters of text. The text will be added or returned in five 3,000-character blocks.
Verifying the processing – retrieve text
Compare the text returned in the BF szText fields to what is on the actual media object for that particular application.
Verifying the processing - add text
Open the media object and make sure that the text that was passed in matches what is there.
Input data structure - DD3N00111C
Name | Default values | R/O | Alias | Notes |
---|---|---|---|---|
szObjectName_OBNM | R | This is required for both adding and retrieving text. This corresponds to the GDOBNM field in the F00165. | ||
iSequenceNumber_MOSEQN | R | This is required for retrieving text. This corresponds to the GDMOSEQN field in the F00165. | ||
szMediaType_MOTYPE | O | The system will default this to a zero. This corresponds to the GDGTMOTYPE field in the F00165. | ||
cErrorCode_ERRC | ||||
szGenericTextItemName_GTITNM | O | This will default to ‘Text' by the system. It corresponds to the GDGTITNM in the F00165. | ||
szUserId_USER | This is not used in this interface. | |||
jdDateUpdated_UPMJ | This is not used in this interface. | |||
mnTimeUpdated_TDAY | This is not used in this interface. | |||
cdcLINKActionCode_EV01 | R | ‘1' to Retrieve text, ‘2' to Write text | ||
szText1_LONGMSG | R | Required for adding text. This is for the first 3,000 characters of text to be added, or where the first 3,000 characters of text are returned. | ||
szText2_LONGMSG | O | This is for the second 3,000 characters of text to be added, or where the second 3,000 characters of text are returned. | ||
szText3_LONGMSG | O | This is for the third 3,000 characters of text to be added, or where the third 3,000 characters of text are returned. . | ||
szText4_LONGMSG | O | This is for the fourth 3,000 characters of text to be added, or where the fourth 3,000 characters of text are returned. | ||
szText5_LONGMSG | O | This is for the fifth 3,000 characters of text to be added, or where the fifth 3,000 characters of text are returned. | ||
iDebugLevel_INT01 | ||||
cDelimiterCharacter_EV01 | C | This is used if the szKey needs to contain a pipe ‘|' character. If the key needs pipe characters, use an alternate character in this field, and it will be replaced with the pipe within the code. A good alternate character to use is the ‘@' symbol. | ||
szMobileOrderNumber_DS50 | O | This is used for MOBILEApps processing. |
R = Required
O = Optional
X = Required, but will default if not passed
C = Conditional (see explanation for conditions)
Input data structure - DD3N0011B
The interface processes by calling BD3N0011, which uses JDE APIs to do the text. The following data structure is used.
Type | Description | Parameter |
---|---|---|
String | szObjectName | Input |
Integer | iSequenceNumber_MOSEQN | Input |
String | szMediaType_MOTYPE | Output |
String | szKey_MOTXKY | Input |
String | cErrorCode_ERRC | Output |
String | szGenericTextItemName_GTITNM | Input/Output |
String | szMediaObjectText_MOTEXT | Input/Output |
String | szUserId_USER | Output |
Date | jdDateUpdated_UPMJ | Output |
Notes
Notes on ND3N0011
-
The user will have to determine the media object data structure (the GTxxxx), which is entered into the GTObjectName field. The user will also have to determine the key for that record. In some instances, it will be a simple key (shipment number or short item number, for instance).
-
If a line number needs to be formatted in a particular way (if it is part of the key), it needs to be formatted prior to passing it into the Key field. For instance, the sales order detail line number needs to be passed in as 1.000 (as it does when done through JDE). If it is not passed in with the decimal formatting (ie, passing it in as 1), it will not appear on the application, but it will be in the F00165.
-
The delimiter field is needed if the Key field contains a pipe character If a pipe is needed, use a substitute character (such as @) in the place of the pipe in the Key field. Put the substitute character in the delimiter field.
-
The szText_ADDMSG field is limited to 1000 characters.
-
The mnSequenceNumber_MOSEQN field is for retrieving text. It is the GDMOSEQN field in the F00165. We do not provide it, nor do we look it up.
-
We do not validate any of the key data.
The following table provides valid action codes (cdcLINKActionCode_EV01) for this interface.
Action Code | Description |
---|---|
1 | Retrieve Text |
2 | Write Text |
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 | Retrieve Media Object Long Text | Write Media Object Long Text |
---|---|---|
szObjectName_OBNM | GT4301A | GT4301A |
iSequenceNumber_MOSEQN | 1 | |
szMediaType_MOTYPE | OP | |
szKey_MOTXKY | 5228 | 5228OP |
cErrorCode_ERRC | ||
szGenericTextItemName_GTITNM | ||
szUserId_USER | ||
jdDateUpdated_UPMJ | ||
mnTimeUpdated_TDAY | ||
cdcLINKActionCode_EV01 | 1 | 2 |
szText1_LONGMSG | 5228OPBP30 | |
szText2_LONGMSG | ||
szText3_LONGMSG | ||
szText4_LONGMSG | ||
szText5_LONGMSG | ||
iDebugLevel_INT01 | ||
cDelimiterCharacter_EV01 | @ | |
szMobileOrderNumber_DS50 |
Common error messages
The following table lists the common error messages that can be generated by this BF and what those error messages mean.
Error Message | Meaning |
---|---|
164F | Table Update or Insert Failed |
0002 | Record Invalid |
References
The following table provides the 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 |
BD3N0011 | dcLINK Retrieve MO Text String |
BD3N0011 | dcLINK Write MO Text String |
DD3N0011 | dcLINK Media Object Long Text |
Assumptions
Due to differences between JDE 8.9 and above and the ERP8 and below releases, the prior version of ND3N0011 - Media Objects will continue to be available. Limitations in JDE prohibit changes to be made to JDE ERP8 and below.
[Body Empty]
Loading...
There was a problem loading this topic