send feedback

❮ Previous Next ❯

Rate Based Completions interface for JD Edwards

About the Rate Based Completions interface

The Rate Based Completions interface is used to report completions in a repetitive manufacturing environment.

Rate based completions is the transaction used for reporting completions in a repetitive manufacturing environment. Repetitive manufacturing is when you are making the same item and (usually) completing it to stock, rather than a specific work order. An example of this would be manufacturing batteries. Battery manufacturers typically make a fixed number of ‘AAA', ‘AA', ‘C', and ‘D' batteries, week in and week out, to keep up with the demand. Their manufacturing lines are setup specifically for the type of battery being made. The ‘D' size battery gets made on the ‘D' line. If ‘AA' is the most popular batter, there may be two or three lines that make nothing but ‘AA' batteries.

The dcLINK version is called ND3N3119. This interface was written in NER and calls ‘C' business function, BD3N3106, to retrieve the processing options.

Name	Function name	Description
DD3N3119		dcLINK Interface Rate Based Completions – Data Structure
ND3N3119	RateBasedCompletions	dcLINK Interface Rate Based Completions
DD3N3106		PO Retrieval Rate Based Completions
BD3N3106	PORetrievalRateBasedCompletion	PO Retrieval Rate Based Completions – Business Function

The full name of this interface is ND3N3119 Rate Based Completions

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 perform a work order completion is P3119 and can be accessed from the menu G3115.

Processing options

Processing options for the Rate Based Completions interface.

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

Defaults tab

trust_set_element_id="18">Enter the Schedule Type. Default value is ‘SC'. if no value is entered into this field then it defaults to SC. This field always overlays any value in the passed in order type (szOrderType_DCTO).
Enter the Employee Number (Optional). In theory, this value would be used if nothing was passed into this NER, but that functionality is not working.
Enter the Production Line (Optional). In theory, this value would be used if nothing was passed into this NER, but that functionality is not working.
Enter the Number of Days to Add to the From Date for the Thru Date (optional). If the “from/thru” dates passed into this NER are blank, then the value in this field is added to the “from” date to calculate the “thru” date.

Versions tab

Super Backflush (P31123): If the selection exit is equal to ‘0' (run super backflush), then this version is passed into the call to the dcLINK Super Backflush NER.
Work Order Completions (P31114): If the selection exit is equal to ‘1' (run WO Completions), then this version is passed into the call to the dcLINK Work Order Completion NER.
Hours and Quantities Update (R31422): If the processing option under the Process Tab is equal to a ‘1', then this is the version that will be used to call R31422.

Process tab

Enter a ‘1' to automatically process hours. A ‘1' in this field will cause the R31422 to process the hours and quantities. If left blank, R31422 will have to be submitted manually.

Processing option data structure for DD3N3106

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

Type	Description	Parameter
String	szPO_ScheduleType_DCTO	Output
Numeric	mnPO_EmployeeNumber_AN8	Output
String	szPO_ProductionLine_LINE	Output
Numeric	mnPO_NumberOfDays_MATH01	Output
String	szPO_FromStatus_FSTRE1	Output
String	szPO_ThruStatus_TSTRE1	Output
String	szPO_StatusCode_SRST	Output
String	szPO_VersionP31123_VERS	Output
String	szPO_VersionP311221_VERS	Output
String	szPO_VersionP31113_VERS	Output
String	szPO_VersionP3109_VERS	Output
String	szPO_VersionP4111_VERS	Output
Char	cPO_EverestEventPoint01_EV01	Output
String	szPO_VersionP3152_VERS	Output
String	szPO_VersionP31226_VERS	Output
String	szPO_VersionP31114_VERS	Output
String	szPO_VersionP4108_VERS	Output
String	szPO_VersionP31422_VERS	Output
String	szPO_VersionP0101_VERS	Output
String	szPO_VersionP3711_VERS	Output
String	sz_PO_Version_VERS	Input

Processing setup

The hardest part of running this transaction is the setup. This is a quick step guide to setting up a rate schedule.

To set up processing, complete the following steps.

Go to the Inventory Master and set up the parent item.

Step Information
In the Additional Info tab, for the Order Policy Code (order type), enter 5 for the Rate Scheduled.

Step Information
Set up the Bill of Materials.

Step Information
Set up up a Routing Location.

Step Information
A line/item relationship must be set up. The line number must be a business unit.

Step Information
Go to the Work Center Master and set it up.

Step Information
Enter a line/cell relationship in the menu G3141 Line/Item Relationship.

Step Information
Enter the Rate Schedule.
Step Information
Set the Shop Floor Control Daily Processing to Repetitive.

Enter the Change Rate Schedule.
Select OK to create the work order.

Step Information

Processing

Rate Based completion processing is simple as most of the work is done in setup.

At a minimum, all that is required is to find the schedule that you want to report against, and enter your quantity.

The dcLINK interface has two run time options that are invoked by the selection exit field (cOPSelectionExit_EV01). The options are ‘0', which uses Super Backflush to process the completion, or ‘1', which uses Work Order Completions to process the completion.

Required fields

The minimum required fields to perform a rate based completion are the item number, the cost center, the line identifier, and quantity shipped/canceled. The rest depends on your specific circumstances. If you are using Super Backflush to process your transaction, then you need to supply a shift code and an address book number – both required for hours and quantities. The dates (transaction date, effective date from, and effective date to) are not required, but if you are reporting against a schedule that can't be found using the current date, then they must be supplied in order for the interface to find the correct schedule. The version will default to ZJDE0001 for both Rate Based completions and Super Backflush, but they may not work for either. It is important that the Super Backflush version be setup to run “blind” for dcLINK. That's not necessarily the case for the interactive version, so it may be necessary for dcLINK to have its own version.

Verify the processing

Steps to verify the Rate Based Completions processing.

Since Super Backflush and Work Order Completions are the two interfaces that are doing the processing work for Rate Based Completions, everything that is affected by those two interfaces is going to be true for Rate Based Completions as well.

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

The processing can be verified in the following places.
Step Information
Work Order

Super Backflush

Work Order Issues

Work Order Completions

Hours & Quantities

Summary Availability

CARDEX

G/L Journal Entries

Receipt Routing

License Plates
In the Super Backflush application, the Total Qty Completed column should reflect the quantity reported so far.

Step Information
In the Work Order Completions application, the Qty Completed to Date field should reflect the completions.

Step Information
Any time there are completions to inventory, or issues from inventory, the CARDEX will have an entry. Depending on processing options, Rate Based Completions should display issues and completions.

Step Information

Input data structure

Input data structure for DD3N3119.

Name	Default value	R/O	Alias	Notes
mnUnitsQuantityShipped_SOQS		O, R	SOQS	The entire point of this transaction is to record either a quantity shipped, or a quantity canceled. Both these fields are optional fields, but there is no point in running the transaction if neither field has a value.
mnUnitsQuantityCanceled_SOCN		O, R	SOCN	The entire point of this transaction is to record either a quantity shipped, or a quantity canceled. Both these fields are optional fields, but there is no point in running the transaction if neither field has a value.
szUnitOfMeasure_UM		O	UM
jdDateTransactionJulian_TRDJ	Today's Date	O	TRDJ	The transaction date has to be greater than, or equal to, the effective from date, and less than, or equal to, the effective through date. In addition, in order for a schedule to be selected, this date must be greater than, or equal t,o the work order start date.
cShiftCode_SHFT	Spaces	O	SHFT	This field is used to help identify the correct schedule to be used to report against. It is compared to the shift from the work order tag file. If no value is passed in, this field defaults to spaces. This value is passed into the super backflush call.
mnAddressNumber_AN8		O	AN8	This field is passed into the call to super backflush. Super backflush requires a value to be entered into this field in order for it to create labor hours records.
szStatusCodeWo_SRST	If no value is passed the status defaults to the existing work order status.	O	SRST	This status is used to update the work order.
szItemNoUnkownFormat_UITM		R	UITM	Item number is used to find the correct rate schedule.
szLineIdentifier_LINE		O	LINE	If a value is passed in this field, it is used to help identify the correct schedule to use. It is possible to be making the exact same item on two different manufacturing lines. This field identifies the manufacturing line.
szCostCenterAlt_MMCU		R	MMCU	This field is used to read the manufacturing constants.
szOrderType_DCTO		R	DCTO	This field, along with the document number, is used to read the KANBAN master file. This field is always overridden from the processing options. The value will either be what is entered in the processing options, or defaults to “SC”.
cdcLINKActionCode_EV01	0	X	EV01	This value is passed into the call to work order completions.
cActionCode_ACTION		X	ACTION	This value is passed into the work order completions call.
jdDateUpdated_UPMJ	Current Date	X	UPMJ	Retrieved from GetAuditInfo.
mnTimeUpdated_TDAY	Current Time	X	TDAY	Retrieved from GetAuditInfo
szUserId_USER	Current User	X	USER	Retrieved from GetAuditInfo. If a value is passed into this field, it will be used to update CARDEX and any “last updated by” fields in tables.
szWorkStationId_JOBN	Current Workstation	X	JOBN	Retrieved from GetAuditInfo
mnJobNumber_JOBS		O	JOBS
szProgramId_PID	ND3N1116	X	PID	Defaulted in program if not passed in.
szVersion_VERS	ZJDE0001	X	VERS	Defaulted in program if not passed in.
cSuppressErrMsg_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.
jdEffectiveFromDate_EFFF	Today's Date	O	EFFF	This field is used to help select the schedule used for reporting. The from effective date has to be greater than, or equal to, the work order start date.
jdEffectiveThruDate_EFFT	The effective from date + the processing option number of days	O	EFFT
szFromStatus_FSTRE1	Processing options	O	FSTRE1	Not used by this NER.
szThruStatus_TSTRE1	Processing options	O	TSTRE1	Not used by this NER.
cOPSelectionExit_EV01	0	O	EV01	Possible values are: 0 = Super Backflush is called 1 = Work Order Completions is called
mnOrderNumber_DOCO		R	DOCO	This field, along with the document type, is used to read the KANBAN master file.
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 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.
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. dcLINK captures the script ID.
szGuidTextMessage_TEXTMES		O	TEXTMES	This is a free form entry field.
mnSecondaryQty_SQOR		O, R	SQOR	If the item is a DUAL unit of measure item, this is the secondary quantity. This field is passed in on the Work Order Completions call.
szSecondaryUoM_UOM2		O, R	UOM2	If this item is a DUAL unit of measure item, this is the secondary unit of measure.This field is passed in on the Work Order Completions call.

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	Using WO completions	Using Super Backflush
mnUnitsQuantityShipped_SOQS	5	10
mnUnitsQuantityCanceled_SOCN
szUnitOfMeasure_UM
jdDateTransactionJulian_TRDJ	08/14/2006	08/14/2006
cShiftCode_SHFT		1
mnAddressNumber_AN8		6002
szStatusCodeWo_SRST
szItemNoUnkownFormat_UITM	2032	2032
szLineIdentifier_LINE	R-A1	R-A1
szCostCenterAlt_MMCU	M30	M30
szOrderType_DCTO
cdcLINKActionCode_EV01
cActionCode_ACTION
jdDateUpdated_UPMJ
mnTimeUpdated_TDAY
szUserId_USER
szWorkStationId_JOBN
mnJobNumber_JOBS
szProgramId_PID
szVersion_VERS	ZDBK0001	ZDBK0001
cSuppressErrMsg_EV01
cErrorCode_ERRC
szErrorMessageKey_EKEY
iDebugLevel_INT01
jdEffectiveFromDate_EFFF	08/14/2006	08/14/2006
jdEffectiveThruDate_EFFT	08/18/2006	08/18/2006
szFromStatus_FSTRE1
szThruStatus_TSTRE1
cOPSelectionExit_EV01	1	0
mnOrderNumber_DOCO
szGuidUniqueID_GUID
szGuidApprover1_USR1
szGuidFullName1_FULLNAME1
szGuidApprover2_USR2
szGuidFullName2_FULLNAME2
mnGuidReasonCode1_REASON1
szGuidCommentField_COMMENTS
mnGuidReasonCode2_REASON2
szGuidCommentField2_2COMMENTS
szGuidScriptID_FMNMVERS
szGuidTextMessage_TEXTMES
mnSecondaryQty_SQOR
szSecondaryUoM_UOM2

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. This message is also generated if the item number on the work order isn't found in the item master file. This message can also be generated if the read against the Kanban master file (F3016) using the order number (mnOrderNumber_DOCO) and order type (szOrderType_DCTO) fails.
006B	Business Unit Must be Specified. The required business unit (szCostCenterAlt_MMCU) passed into this NER was blank.
009E	Model Work Order not found in F4801. When rate schedules are set up they are given a date range of when they are effective. For example, if the rate schedules are weekly, then each new week a new schedule is in effect. This NER loops the work order file trying to find the rate schedule that is in effect (it compares the transaction date (jdDateTransactionJulian_TRDJ) to the “from/to” effective dates). This error is returned if no record is found to be in effect for the transaction date.
014O	Quantity Creates Overcompletion. If the quantity shipped to date is greater than the quantity ordered, this message is displayed.
041K	Item number missing or invalid on ticket. Item number (szItemNoUnknownFormat_UITM) is a required field, but no value was passed into this NER.
051E	Shift Code Is Not Defined. If the shift code (cShiftCode_SHFT) passed into this NER does not equal any of the shift values returned from the Manufacturing Constants, or the shift hours in the Manufacturing Constants is equal to blanks, this error is returned.
443I	Manufacturing Constants are not set up. No record was found when the manufacturing constants file (F3009) was read using the cost center (szCostCenterALT_MMCU) passed in as the key.
2739	Transaction date outside active schedule. This error is returned if the transaction date (jdDateTransactionJulian_TRDJ) is less than the work order start date, or greater than the work order effective through date.
3326	Invalid Selection Exit. The selection exit (cOPSelectionExit_EV01) passed into this NER is equal to ‘2'.

There was a problem loading this topic

Mobile Enterprise Platform