Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-GL (Application Component) General Ledger Accounting⤷
FAGL_LEDGER_CUST (Package) New General Ledger: Scenarios, Ledgers
Basic Data
| Data Element | FAGL_RAND_FIELD |
| Short Description | FI-GL: Field Name for Randomization |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FDNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | DD03L |
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 | Field Name |
| Medium | 20 | Fld Name (Randomiz.) |
| Long | 30 | Field Name for Randomization |
| Heading | 10 | Field Name |
Documentation
Definition
The field entered here is applied in the randomization.
When posting a line item with the condition fulfilled (see table FAGL_RAND_RANGE), the system issues random numbers and saves these numbers in this field for the affected totals table and actual line items table.
In this way, the system creates totals records artificially, thereby eliminating or reducing the performance problems related to database locks when the totals records are updated.
Use
Only use fields that you do not need and when you are certain that they will not be required in the future.
After entering the ledger, you can use input help to display the possible fields.
Caution: Using input help does not replace the need to check thoroughly whether a field can actually be used.
For more information, see SAP Note 1682250.
Dependencies
Example
You have encountered performance problems related to database locks when updating totals records of the leading ledger of table FAGLFLEXT for the customer reconciliation account, and it is not possible to resolve these problems by changing Customizing settings or by making changes to the data provided by feeder systems.
In tables FAGLFLEXT and FAGLFLEXA, mass data has already been posted, and there are no relevant, non-required ZZ fields. It would be critical to performance to add the customer field ZZRANDOM_NUMBER (specially intended for this purpose) because this would involve a time-consuming table conversion.
Since the leading ledger does not the business area scenario assigned to it, you can use the non-required field SBUSA (partner business area) as a randomization field.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
