DeleteProfitRecognitionRecord
Delete Profit Recognition Record
Minor Business Rule
Object Name: B5100060
Parent DLL: CAEC
Location: Client/Server
Language: C
Delete Profit Recognition Master (F5144) records based on Version, Job Number, Subledger, Subledger
Type, Effective Date and Record Type. Delete Profit Recognition Balance record (F5145) based on Next
Number from F5144.
Data Structure
D5100060 - Delete Profit Recognition Record
Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szVersionCurrent | 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. |
szJobNumber | 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
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.
|
szSubledger | SBL | char | OPT | NONE |
A code that identifies a detailed, auxiliary account within a general ledger account. A subledger can be an equipment item number or an
address book number. If you enter a subledger, you must also specify the subledger type. |
cSubledgerType | SBLT | char | OPT | NONE |
A user defined code (00/ST) that is used with the Subledger field to identify the subledger type and how the system performs subledger
editing. On the User Defined Codes form, the second line of the description controls how the system performs editing. This is either hard-coded
or user defined. Valid values include:
A
Alphanumeric field, do not edit
N
Numeric field, right justify and zero fill
C
Alphanumeric field, right
justify and blank fill
|
jdDateEffective | DEF | JDEDATE | OPT | NONE |
The date on which this transaction takes effect. The effective date is used generically. It can be the date of the next raise, a lease effective
date, a price or cost effective date, a currency effective date, a tax rate effective date, a change in well status, or any other date that is
appropriate. |
cRecordType | TYRE | char | OPT | NONE |
A code that indicates how a record was generated when the Profit Recognition Build program (R51800) was run. Valid values are:
0
Generated through Generation by Project in R51800. The Business Unit belongs to a project, but this record contains no real Profit Recognition
data.
1
Generated through Generation by Project in R51800. The business unit itself is a project, and it contains the summarized profit recognition
information of all business units that belong to this project.
2
Generated through Generation by Business Unit in R51800.
3
Generated through
Generation by Subledger and Subledger type in R51800.
|
mnNextNumberValue | NNBR | MATH_NUMERIC | OPT | NONE |
The number that the system will use next for automatically assigning numbers. Next numbers can be used for many types of documents;
they include voucher numbers, invoice numbers, journal entry numbers, employee numbers, address numbers, and so on. You must adhere to
the next numbers that have been pre-established unless custom programming is provided. |