F17111GetWarrantyDefaults

F17111 Insert Warranty Defaults

Minor Business Rule

Object Name: N1700480

Parent DLL: CCRIN

Location: Client/Server

Language: NER

1.1Purpose
This NER is used to write base warranty records for new equipment records.

1.2Setup Notes and Prerequisites
Processing Options for P1720 are retrieved in this NER.  Accordingly the processing options for P1720
need to be set up for this NER to work properly.

Warranty rules sequence also need to be set up so the correct hierarchy of events can take place.

1.3Special Logic
Check the warranty rules sequence table (F1750) for hierarchy of warranty information.  For each rule
sequence record, check for an exact match on incoming parameters in the warranty defaults table
(F17111).  If warranty default records are found, write a contract header, if required, and contract detail
record.

NOTE: For required parameters:  If the value for a parameter is unknown, pass either a blank or zero,
according to the data type of the parameter.

Data Structure

D1700480 - F17111 Insert Warranty Defaults

Parameter Name Data Item Data Type Req/Opt I/O/Both

szCountry CTR char REQ INPUT

A user defined code (00/CN) that identifies a country. The country code has no effect on currency conversion. The Address Book system
uses the country code for data selection and address formatting.

szProductFamily PRODF char REQ INPUT

A code that classifies an inventory item into a group for customer service. Some examples include: Laser Printer, Inkjet, or Fax.

szProductModel PRODM char REQ INPUT

A code that classifies an inventory item into a model for customer service. Some examples include: Laser Printer, Inkjet or Fax.

mnInvItemNumber ITM MATH_NUMERIC REQ INPUT

An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:   o Item Number (short) - An eight-digit, computer-assigned item number     o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number     o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number

mnCustomerNumber AN8 MATH_NUMERIC REQ INPUT

A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.

szBranchPlant MMCU char REQ INPUT

A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which
represent lower-level business units, subordinate to it. For example:     o Branch/Plant (MMCU)     o Dept A (MCU)     o Dept B (MCU)     o Job 123
(MCU) Business unit security is based on the higher-level business unit.

cInformationType1 ITYPE char REQ INPUT

A code that indicates specific record types when records of different types are stored within the same table. For internal use only.

mnBillToAddress ANOB MATH_NUMERIC OPT NONE

The address number of an alternate location to which the owner wants the invoice (application) sent.

mnSite LANO MATH_NUMERIC OPT NONE

The address book number for the lessor, renter, or lending institution.

szDescription DL01 char OPT NONE

A user defined name or remark.

szP1720Version VERS char OPT NONE

A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined
processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a
menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version.

mnAssetItemNumber NUMB MATH_NUMERIC OPT NONE

An 8-digit number that uniquely identifies an asset.

cSuppressErrorMessages EV01 char OPT NONE

An option that specifies the type of processing for an event.

szErrorMsgID DTAI char OPT NONE

A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or
special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.

mnContractNumber DOCO MATH_NUMERIC OPT NONE

A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on.

szContractType DCTO char OPT NONE

A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has
reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post
program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and
should not be changed: P Accounts Payable documents   R Accounts Receivable documents   T Payroll documents   I Inventory documents
O Purchase Order Processing documents   J General Accounting/Joint Interest Billing documents   S Sales Order Processing documents

szCompanyKeyContractNo KCOO char OPT NONE

A number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a
sales order, and so on). If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (X0010) uses the
order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order
type, the order company lets you locate the desired document. If you use the regular Next Numbers facility, the order company is not used to
assign a next number. In this case, you probably would not use the order company to locate the document.

szContractChangeNum COCH char OPT NONE

The change number of the contract. The change order number of the base contract is always initialized to 000. Each time you enter a
change order for a contract, the system automatically increases the change order number by one. For example, the base contract is the change
order number 000, the first change order is 001, the second is 002, and so on.

mnSalesOrderNumber DOC1 MATH_NUMERIC OPT NONE

The document number associated with a given document type.

szSalesDocType DCT1 char OPT NONE

Used to record the Closing journal entry's document type in the Lot Proceed files.

szSalesCompany SKCO char OPT NONE

Document Company (Sales Order)

szSalesSuffix OSFX char OPT NONE

The number that identifies a specific pay item associated with the document.

mnSalesLineNumber LNID MATH_NUMERIC OPT NONE

A number that identifies multiple occurrences, such as line numbers on a purchase order or other document. Generally, the system assigns
this number,but in some cases you can override it.

szBusinessUnit_MCU MCU char REQ INPUT

An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units
for which you have no authority.

jdContractStartDate_CSDT CSDT JDEDATE REQ INPUT

The date you actually start work on the contract.

cAddWarrantyFloat_EV01 EV01 char REQ INPUT

An option that specifies the type of processing for an event.

mnQuantity_AROQ AROQ MATH_NUMERIC REQ INPUT

The original number of units for an asset. If assets are purchased and accounted for in quantities (more than one), you can specify the
original quantity purchased. For example, if you purchase 100 office chairs, you would set up one asset item with an original quantity of 100. Then,
as you disposed of office chairs, you would adjust the current quantity to reflect the current balance. This adjustment allows you to track
assets purchased in bulk quantity on one master record.

cNonSerializedProduct_EV01 EV01 char REQ INPUT

An option that specifies the type of processing for an event.

szLineType LNTY char OPT NONE

A code that controls how the system processes lines on a transaction. It controls the systems with which the transaction interfaces, such as
General Ledger, Job Cost, Accounts Payable, Accounts Receivable, and Inventory Management. It also specifies the conditions under
which a line prints on reports, and it is included in calculations. Codes include the following: S Stock item   J Job cost   N Nonstock item   F Freight
T Text information   M Miscellaneous charges and credits   W Work order

szShipToCountry SHPCTR char OPT NONE

A user defined code (00/CN) that identifies a country. The country code has no effect on currency conversion. The Address Book system
uses the country code for data selection and address formatting.

szDocumentType DCT char OPT NONE

A user defined code (00/DT) that identifies the origin and purpose of the transaction.  PeopleSoft reserves several prefixes for document
types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are: P Accounts payable
documents R Accounts receivable documents T Time and Pay documents I Inventory documents O Purchase order documents S Sales order
documents

szGroupCustomerPriceGp CPGP char OPT NONE

A user defined code (40/PC) that identifies a customer group. You can group customers with similar characteristics, such as comparable
pricing.

szPricingCategory PRGR char OPT NONE

A user defined code (system 40/type PI) that identifies an inventory price group for an item. Inventory price groups have unique pricing
structures that direct the system to incorporate discounts or markups on items on sales and purchase orders. The discounts or markups are
based on the quantity, dollar amount, or weight of the item ordered. When you assign a price group to an item, the item takes on the same pricing
structure defined for the inventory price group. You must assign an inventory price group to the supplier or customer, as well as to the item, for
the system to interactively calculate discounts and markups on sales orders and purchase orders.

Related Functions

None

Related Tables

None

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szCountry	CTR	char	REQ	INPUT
A user defined code (00/CN) that identifies a country. The country code has no effect on currency conversion. The Address Book system uses the country code for data selection and address formatting.
szProductFamily	PRODF	char	REQ	INPUT
A code that classifies an inventory item into a group for customer service. Some examples include: Laser Printer, Inkjet, or Fax.
szProductModel	PRODM	char	REQ	INPUT
A code that classifies an inventory item into a model for customer service. Some examples include: Laser Printer, Inkjet or Fax.
mnInvItemNumber	ITM	MATH_NUMERIC	REQ	INPUT
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and so forth. The item numbers are as follows: o Item Number (short) - An eight-digit, computer-assigned item number o 2nd Item Number - The 25-digit, free-form, user defined alphanumeric item number o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item number
mnCustomerNumber	AN8	MATH_NUMERIC	REQ	INPUT
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or location.
szBranchPlant	MMCU	char	REQ	INPUT
A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which represent lower-level business units, subordinate to it. For example: o Branch/Plant (MMCU) o Dept A (MCU) o Dept B (MCU) o Job 123 (MCU) Business unit security is based on the higher-level business unit.
cInformationType1	ITYPE	char	REQ	INPUT
A code that indicates specific record types when records of different types are stored within the same table. For internal use only.
mnBillToAddress	ANOB	MATH_NUMERIC	OPT	NONE
The address number of an alternate location to which the owner wants the invoice (application) sent.
mnSite	LANO	MATH_NUMERIC	OPT	NONE
The address book number for the lessor, renter, or lending institution.
szDescription	DL01	char	OPT	NONE
A user defined name or remark.
szP1720Version	VERS	char	OPT	NONE
A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version.
mnAssetItemNumber	NUMB	MATH_NUMERIC	OPT	NONE
An 8-digit number that uniquely identifies an asset.
cSuppressErrorMessages	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
szErrorMsgID	DTAI	char	OPT	NONE
A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.
mnContractNumber	DOCO	MATH_NUMERIC	OPT	NONE
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry, and so on.
szContractType	DCTO	char	OPT	NONE
A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and should not be changed: P Accounts Payable documents R Accounts Receivable documents T Payroll documents I Inventory documents O Purchase Order Processing documents J General Accounting/Joint Interest Billing documents S Sales Order Processing documents
szCompanyKeyContractNo	KCOO	char	OPT	NONE
A number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a sales order, and so on). If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (X0010) uses the order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order type, the order company lets you locate the desired document. If you use the regular Next Numbers facility, the order company is not used to assign a next number. In this case, you probably would not use the order company to locate the document.
szContractChangeNum	COCH	char	OPT	NONE
The change number of the contract. The change order number of the base contract is always initialized to 000. Each time you enter a change order for a contract, the system automatically increases the change order number by one. For example, the base contract is the change order number 000, the first change order is 001, the second is 002, and so on.
mnSalesOrderNumber	DOC1	MATH_NUMERIC	OPT	NONE
The document number associated with a given document type.
szSalesDocType	DCT1	char	OPT	NONE
Used to record the Closing journal entry's document type in the Lot Proceed files.
szSalesCompany	SKCO	char	OPT	NONE
Document Company (Sales Order)
szSalesSuffix	OSFX	char	OPT	NONE
The number that identifies a specific pay item associated with the document.
mnSalesLineNumber	LNID	MATH_NUMERIC	OPT	NONE
A number that identifies multiple occurrences, such as line numbers on a purchase order or other document. Generally, the system assigns this number,but in some cases you can override it.
szBusinessUnit_MCU	MCU	char	REQ	INPUT
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units for which you have no authority.
jdContractStartDate_CSDT	CSDT	JDEDATE	REQ	INPUT
The date you actually start work on the contract.
cAddWarrantyFloat_EV01	EV01	char	REQ	INPUT
An option that specifies the type of processing for an event.
mnQuantity_AROQ	AROQ	MATH_NUMERIC	REQ	INPUT
The original number of units for an asset. If assets are purchased and accounted for in quantities (more than one), you can specify the original quantity purchased. For example, if you purchase 100 office chairs, you would set up one asset item with an original quantity of 100. Then, as you disposed of office chairs, you would adjust the current quantity to reflect the current balance. This adjustment allows you to track assets purchased in bulk quantity on one master record.
cNonSerializedProduct_EV01	EV01	char	REQ	INPUT
An option that specifies the type of processing for an event.
szLineType	LNTY	char	OPT	NONE
A code that controls how the system processes lines on a transaction. It controls the systems with which the transaction interfaces, such as General Ledger, Job Cost, Accounts Payable, Accounts Receivable, and Inventory Management. It also specifies the conditions under which a line prints on reports, and it is included in calculations. Codes include the following: S Stock item J Job cost N Nonstock item F Freight T Text information M Miscellaneous charges and credits W Work order
szShipToCountry	SHPCTR	char	OPT	NONE
A user defined code (00/CN) that identifies a country. The country code has no effect on currency conversion. The Address Book system uses the country code for data selection and address formatting.
szDocumentType	DCT	char	OPT	NONE
A user defined code (00/DT) that identifies the origin and purpose of the transaction. PeopleSoft reserves several prefixes for document types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are: P Accounts payable documents R Accounts receivable documents T Time and Pay documents I Inventory documents O Purchase order documents S Sales order documents
szGroupCustomerPriceGp	CPGP	char	OPT	NONE
A user defined code (40/PC) that identifies a customer group. You can group customers with similar characteristics, such as comparable pricing.
szPricingCategory	PRGR	char	OPT	NONE
A user defined code (system 40/type PI) that identifies an inventory price group for an item. Inventory price groups have unique pricing structures that direct the system to incorporate discounts or markups on items on sales and purchase orders. The discounts or markups are based on the quantity, dollar amount, or weight of the item ordered. When you assign a price group to an item, the item takes on the same pricing structure defined for the inventory price group. You must assign an inventory price group to the supplier or customer, as well as to the item, for the system to interactively calculate discounts and markups on sales orders and purchase orders.