Hierarchy
IS-OIL (Software Component) IS-OIL⤷
IS-OIL-PRA-REV (Application Component) Revenue⤷
OIU_HS (Package) PRA Hybrid Solition - Integration from/ to Razorfish & PRA
Basic Data
| Data Element | OIUHS_DEST_CD |
| Short Description | Destination code |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OIUHS_DEST_CD | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | OIUHS_JE_DPK |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Dest.Cd |
| Medium | 15 | Destination Cd |
| Long | 20 | Destination Code |
| Heading | 0 |
Documentation
Definition
The destination code defines where specifically an entry is to go in the system (to what table). For example, the entry might go straight into FI (the usual situation), or it might go to JVA (Joint Venture Accounting) in special situations.
The destination code is a system rule you set up that says, "Where should the system take this entry ?": straight to FI, or, is it a special situation in which you have carried owners or working interest owners and you are doing something special. For example, there might be special JVA situations, where you need special logic just for JVA.
The possible entries are:
- G/L - General ledger
- CW - Carried Working Interest
- NP - Net Profits
- AR - Accounts receivable
- AP - Accounts Payable
Note that G/L is used for 'everything', whereas CW and NP is for things that are netted.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
