F3430UpdateVendorScheduleQty

F3430 Update Vendor Schedule Quantity

Major Business Rule

Object Name: B3401160

Parent DLL: CMFG

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose

• The Business Function must be able to update the Vendor Schedule QuantityTtable (F3430) via the key
(DOCO, DCTO, KCOO, SFXO, LNID, STRT). Certain updateable columns have been specified in section 2.1
below. The updates will take place within the Business Function.

Note:For effeciency reasons not all columns have been specified for update to the F3430. If more
columns are required at a future date, then this business function will have to be modified to
accomodate the extra field(s).

1.2Setup Notes and Prerequisites
• In order for a successful update to the F3430 Vendor Schedule Quantity Table, the key fields (DOCO,
DCTO, KCOO, SFXO, LNID and STRT) need to be known at the time of calling this business function.

2.Technical Specifications
Using the key supplied (DOCO, DCTO, KCOO, SFXO, LNID, STRT) fetch the relevant row from
the Vendor Schedule Quantity Table (F3430).

Open F3430 Table
If Open table successful
Copy key list values into key
Fetch Record
If Fetch successful
Copy update values into data structure
Update Table
If Update unsuccessful
Set error 013H
Else fetch unsuccessful
Set error 2994
Else Open Table failed
Set error 3143
Close Table
Return
^

Data Structure

D3401160 - F3430 Update Vendor Schedule Quantity

Data Item Data Structure DescriptionI/ORequiredNotes
DOCO            Document/Order Number            IY      Key Field
DCTO             Document Type                  IY      Key Field
KCOO            Document Company                  IY      Key Field
SFXO            Suffix                        IY      Key Field
LNID            Line Id.                        IY      Key Field
STRT            Start Date                        IY      Key Field
DTAI            Error Code                        OY      If this field is blank on
return,
                                                                        then this implies no error
situations                                                                         arose in the business
function.
EV01            cSuppress Error Message            IN      Blank = Display Error Message

                                                                        '1'=  Suppress Error Message
MVPLQT      Planned Quantity                  IY      Passed to BF for update to
F3430
MVRLQT      Released Quantity                  IY      Passed to BF for update to
F3430

^

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnOrderNumber	DOCO	MATH_NUMERIC	NONE	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.
szOrderType	DCTO	char	NONE	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
szOrderCompany	KCOO	char	NONE	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.
szOrderSuffix	SFXO	char	NONE	NONE
In the A/R and A/P systems, a code that corresponds to the pay item. In the Sales Order and Procurement systems, this code identifies multiple transactions for an original order. For purchase orders, the code is always 000. For sales orders with multiple partial receipts against an order, the first receiver used to record receipt has a suffix of 000, the next has a suffix of 001, the next 002, and so on.
mnLineNumber	LNID	MATH_NUMERIC	NONE	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.
jdStartDate	STRT	JDEDATE	NONE	NONE
The start date for the order. You can enter this date manually, or have the system calculate it using a backscheduling routine. The routine starts with the required date and offsets the total leadtime to calculate the appropriate start date.
szErrorMessage	DTAI	char	NONE	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.
cSuppressErrorMessage	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
mnPlannedQuantity	PLQT	MATH_NUMERIC	NONE	NONE
The quantity of units planned for each period in the time series or plan.
mnReleaseQuantity	RLQT	MATH_NUMERIC	NONE	NONE
The quantity released against a blanket order. The total releases for a given date.

Related Functions

B9800100 Get Audit Information

Related Tables

F3430 Vendor Schedule Quantity File