Special Processing interface for JD Edwards

About Special Processing Interface

The guide provides additional information on entry options for selected groups of fields common to several interfaces.

The groups of fields described in this guide are as follows.

Lot and Serial Control fields
Dual Unit of Measure parameters
Globally Unique Identifier (GUID) fields

Lost/Serial control

Lot/serial control is determined at the item/branch level.

Lot process type

The Lot Process Type “SRCE” determines if a lot or serial number is required and how it is assigned.

The following are valid values.

Value	Description
Blank
0	Lots are optional.
1	Lots are assigned using the date (the API populates the lot number).
2	Lots are assigned with next number (the API populates the lot number).
3	Lots must be assigned manually.
4	Serial number is optional.
5	Serial number assigned using date.
6	Serial number assigned manually.

Serial number required

The Serial Number Required “NR” works in conjunction with the Lot Process Type to determine whether a serial number is required or if additional lot fields are required.

The following are valid values.

Value	Description
Blank	Serial number not required.
3*	Supplier lot required.
4*	Supplier lot, memo lot 1 required.
5*	Supplier lot, memo lot 1, and memo lot 2 required.
6	CSMS Non-serialized item.
N	Serial number not required.
Y	Serial number required dependent upon the lot process type flag having a value of “5,” “6,” or “7”; if the item is serialized, the quantity must be “1”.

Note: Entry of these fields is not supported by the Inventory Adjustment interface or by the enterprise system. The user must maintain the lot master after the record is added.

Because you are issuing inventory, the lot must already exist for lot-controlled items. The only information needed is the combination of item/location, lot number, and quantity.

The Shelf Life Days “SLD” determines if the expiration date can be assigned automatically based on the transaction date.

The Lot Status Code “LOTS” defaults from the item/branch record. If you are passing a value into this field, the processing options must be set to allow for processing lots on hold. The lot status code is validated against the UDC 41/L.

The Lot Grade “LOTG” determines whether grade is used for this item. The item can be either grade or potency controlled, but not both. If the item is grade controlled, the value is validated against the UDC 40/LG.

Globally unique identifier (GUID)

Several GUID options are available for the Special Processing interface.

Globally unique identifier (GUID) processing applies to organizations that are subject to Food and Drug Administration (FDA) electronic record and signature requirements, as defined in Part 11 of Title 21 of the Code of Federal Regulations (CFR). If your organization is not subject to FDA 21 CFR Part 11, all GUID values are optional.

To create an audit trail, Mobile Enterprise Platform generates a 32-character unique identifier value for the szGuidUniqueID_GUID field and passes it to JD Edwards EnterpriseOne. The following table outlines the other GUID fields and the data they contain.

To enable GUID options, you must also select the Use Advanced Inventory tracking ID for GUID parameter check box for the EnterpriseOne XML Connector in Advanced Inventory Platform Manager (Admin > Configuration > Connector Settings > EnterpriseOne XML Connector).

GUID Fields

R = Required (shaded in blue for quick reference)

O = Optional

X = Required, but will default in if not passed

C - Conditional (see explanation for conditions)

Name	Default values	Notes
Name	Default values	R/O	Alias
szGuidUniqueID_GUID	Value generated by function caller program		CFRGUID	Generates a 32-character unique identifier value, creating an audit trail. The generated value is passed to JD Edwards.
szGuidApprover1_USR1		C	USR1	User names are also approver names. There can be up to two, but only this one is required. If the value entered here matches a user name set up in the enterprise system, the name from the Address Book is populated into FullName1.
szGuidFullName1_FULLNAME1		O	FULLNAME1	If the value entered in USR1 does not match a user name set up in the enterprise system, and therefore FULLNAME1 is not automatically populated, you can enter a full name.
szGuidApprover1_USR2		C	USR2	User names are also approver names. There can be up to two. If the value entered here matches a user name set up in the enterprise system, the name from the Address Book is populated into FullName2.
szGuidFullName1_FULLNAME2		O	FULLNAME2	If the value entered in USR2 does not match a user name set up in the enterprise system, and therefore FULLNAME2 is not automatically populated, you can enter a full name.
mnGuideReasonCode1_REASON1		C	REASON1	Reasons 1 & 2 correspond with approvers (Users) 1 & 2. The value must be a valid reason code already set up in the enterprise system.
szGuidCommentField_COMMENTS		O	COMMENTS	Comments 1 & 2 correspond with approvers (Users) 1 & 2. The value is user defined.
mnGuideReasonCode2_REASON2		C	REASON2	Reasons 1 & 2 correspond with approvers (Users) 1 & 2. The value must be a valid reason code already set up in the enterprise system.
szGuidCommentField2_2COMMENTS		O	2COMMENT	Comments 1 & 2 correspond with approvers (Users) 1 & 2. The value is user defined.
szGuidScriptID_FMNMVERS		O	FMNMVERS	From Version—this is the ID of the dcLINK script that is using the GUID values.
szGUIDTextMessage_TEXTMES		O	TEXTMES	This is a text message associated with the GUID value. If used, it only needs to be entered once.

There was a problem loading this topic