F3013UpdateEffectivityDates

F3013 Update Effectivity Dates

Master Business Function

Object Name: B3001540

Parent DLL: CMFGBASE

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
This business function will update the ECO Parts List in the table (F3013) for a given Document
Number, Primary Sequence and Related Sequence.

1.2Setup Notes and Prerequisites

• None.

1.3Special Logic
None.

2.Technical Specifications

2.4Processing

1. Read the ECO Parts List row from the F3013 table using Document Number (DOCO), Primary Sequence
(PSQ) and Related Sequence (RSQ) as the key.

2. If fetch is not successful, assign Error Message ID = '0002' - Record Not Found. If fetch not
successful and Suppress Error Message is not equal to '1', allow runtime message handling to occur.

3. Retrieve System Date, Time, Workstation ID, and User ID using call to B9800100
GetAuditInformation. Assign the current system time, date, workstation ID and User ID to the corresponding fields in
the F3013.

Update the ECO Parts List Record (F3013).
^

Data Structure

D3001540 - F3013 Update Effectivity Dates

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.
mnPrimarySequence	PSQ	MATH_NUMERIC	NONE	NONE

mnRelatedSequence	RSQ	MATH_NUMERIC	NONE	NONE

jdEffectiveFromDate	EFFF	JDEDATE	NONE	NONE
A date that indicates one of the following: o When a component part goes into effect on a bill of material o When a routing step goes into effect as a sequence on the routing for an item o When a rate schedule is in effect The default is the current system date. You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
jdEffectiveThruDate	EFFT	JDEDATE	NONE	NONE
A date that indicates one of the following: o When a component part is no longer in effect on a bill of material o When a routing step is no longer in effect as a sequence on the routing for an item o When a rate schedule is no longer active The default is December 31 of the default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
szProgramID	PID	char	NONE	NONE
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value. It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry program.
cSuppressErrorMessages	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
szErrorMessageID	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.

Related Functions

B9800100 Get Audit Information

Related Tables

F3013 ECO Parts List Detail