1.Functional Description
Update all the records in F00092 for a specific individual with a new ending effective date.
1.2Setup Notes and Prerequisites
1.3Special Logic
2.Technical Specifications
2.1Parameters
Data Item Data Structure DescriptionI/OReqNotes
EFTEjdDateEndingEfectiveINEnding Date
2.2Related Tables
Table Table Description
F00092Supplemental Data
Address By Date
2.3 Related Business Functions
Table Table Description
N/A
Processing:
Loop through F00092 for all records with a matching partial key.
Update the ending date for each record.
D0800480 - Data Structure to Pass to Supplemental Data
Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
---|---|---|---|---|
szSupplementalDatabaseCode | SDB | char | OPT | NONE |
A user defined code (00/SD) that sets up databases for groups of related supplemental data types. This code differentiates the
| ||||
cActionCode2 | ACTN | char | OPT | NONE |
A code that specifies the action that is performed. Valid values are: A Add C Change | ||||
szTypeofData | TYDT | char | OPT | NONE |
A code that you assign to supplemental data so that you can group data by categories. Valid values include:
A
Approval steps
B
Requisition
| ||||
szSuppDataAlphaKey1 | SBA1 | char | OPT | NONE |
This field specifies one of the alphanumeric keys to the Generic Supplmental Database. The key may be selected from a list of supported
| ||||
szSuppDataAlphaKey2 | SBA2 | char | OPT | NONE |
This field specifies one of the alphanumeric keys to the Generic Supplmental Database. The key may be selected from a list of supported
| ||||
szCostCenter | MCU | char | OPT | NONE |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
| ||||
szCompanyKey | KCO | char | OPT | NONE |
A number that, with the document number, document type and G/L date, uniquely identifies an original document, such as invoice, voucher,
| ||||
mnSuppDataNumericKey1 | SBN1 | MATH_NUMERIC | OPT | NONE |
This field specifies one of the numeric keys to the Generic Supplemental Database. You can select the key from a list of supported data
| ||||
mnSuppDataNumericKey2 | SBN2 | MATH_NUMERIC | OPT | NONE |
This field specifies one of the numeric keys to the Generic Supplmental Database. The key may be selected from a list of supported data
| ||||
szNameRemark | RMK | char | OPT | NONE |
A generic field that you use for a remark, description, name, or address. | ||||
szNameRemarksLine2 | RMK2 | char | OPT | NONE |
A generic field that you use for a remark, description, name, or address. | ||||
jdUpdatedDate | UPDJ | JDEDATE | OPT | NONE |
A date that can be used with supplemental data information. For example, you can enter a verification date in this field to show when
| ||||
szUserId | USER | char | OPT | NONE |
The code that identifies a user profile. | ||||
mnAmountUserDefined | AMTU | MATH_NUMERIC | OPT | NONE |
A quantity that represents the statistical or measurable information related to the code that is defined for the data type. For example, if the
| ||||
mnAmountUserDefined2 | AMTV | MATH_NUMERIC | OPT | NONE |
The second Amount associated with the code defined for this Supplemental Data Type. For example, if you have a stock option plan, you
| ||||
mnAddressNumber | AN8 | MATH_NUMERIC | OPT | NONE |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
| ||||
mnDaysUserDefined | DYUD | MATH_NUMERIC | OPT | NONE |
The days associated with the code defined for this supplemental data type. For example, engineering change order leadtime days
| ||||
szUdcEquivalentWw | KYWW | char | OPT | NONE |
This fields holds the "UDC Equivalent" of the Profile Data Codes. It is to be used for obtaining descriptions when using World Writer for the
| ||||
jdDateUpdated | UPMJ | JDEDATE | OPT | NONE |
The date that specifies the last update to the file record. | ||||
szProgramId | PID | char | OPT | NONE |
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry
| ||||
mnTimeOfDay | TDAY | MATH_NUMERIC | OPT | NONE |
The computer clock in hours:minutes:seconds. | ||||
szWorkStationId | JOBN | char | OPT | NONE |
The code that identifies the work station ID that executed a particular job. | ||||
jdDateEffectiveRates | EFT | JDEDATE | OPT | NONE |
The date that identifies when a date is first valid. The effective date is used generically. It can be a lease effective date, a price or cost
| ||||
jdDateEndingEffective | EFTE | JDEDATE | OPT | NONE |
The date on which the item, transaction, or table becomes inactive, or through which you want transactions to appear. This field is used
| ||||
mnUniqueKeyIDInternal | UKID | MATH_NUMERIC | OPT | NONE |
This field is a unique number used to identify a record in a file. | ||||
szUserDefinedCode | KY | char | OPT | NONE |
A list of valid codes for a specific user defined code list. | ||||
szRelatedPoSoNumber | RORN | char | OPT | NONE |
A number that identifies a secondary purchase order, sales order, or work order that is associated with the original order. This number is for
| ||||
szRelatedOrderType | RCTO | char | OPT | NONE |
A user defined code (system 00, type DT) that indicates the document type of the secondary or related order. For example, a purchase
| ||||
mnUnitsTransactionQty | UORG | MATH_NUMERIC | OPT | NONE |
The quantity of units affected by this transaction. |
None |
None |