SAP ABAP Data Element IDENTBRE (Identifier for BRE Runs)
Hierarchy
☛
IS-UT (Software Component) SAP Utilities/Telecommunication
⤷ IS-U-BI (Application Component) Contract Billing
⤷ EE20_BRE (Package) IS-U Processing of Backlogs in Billing
⤷ IS-U-BI (Application Component) Contract Billing
⤷ EE20_BRE (Package) IS-U Processing of Backlogs in Billing
Basic Data
Data Element | IDENTBRE |
Short Description | Identifier for BRE Runs |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR12 | |
Data Type | CHAR | Character String |
Length | 12 | |
Decimal Places | 0 | |
Output Length | 12 | |
Value Table |
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 | Ident. BRE |
Medium | 15 | Ident. BRE |
Long | 20 | Ident. BRE |
Heading | 12 | Ident. BRE |
Documentation
Definition
You are free to specify an ID, which can be used identify BRE runs. This makes it easier to evaluate the data in the BLOG orFLEXLOG transactions.
If you do not use this option, the system generates a proposal that you are free to overwrite.
The proposal is a time stamp with an ID stipulating from which transaction the call originated.
For example: xYMMDDHHMMSS
- x = W BRE called via WAR
- x= S BRE called via BREE
- x = F BRE called via FLEXBRE
- x = O BRE called via FLEXFIN
Example: O20218145322 means that BRE was called from transaction FLEXFIN on18.02.2002 at14:53:22.
Achtung:
FLEXBRE andFLEXFIN can start several independent BRE runs of the BREE category in parallel.
Note that the system gives these parallel runs the same ID, which
is specified on the initial screen.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 464 |