Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20_EBF (Package) IS-U Correction Workbench - Historical & Archived Doc. Lines
Basic Data
| Data Element | EEBFTAB |
| Short Description | Location for EBF Datapool |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AS4TAB | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | DD02L |
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 | Location |
| Medium | 15 | Location EBF |
| Long | 21 | Location for EBF |
| Heading | 30 | Location for EBF |
Documentation
Definition
Storage table for documents from migration with storage type "Table".
Use
The table structure is made up of different structures. The first structure 'EBFKEY' contains the key fields. The second structure 'EBFLIN' contains essential fields for the billing framework. You can use customer include CI_EBFLIN to add other fields, whereby you can only use fields from structure 'ERCHZ'. Fields in the customer namespace are used for information purposes only and have no effect on the billing framework as long as it was not defined using customer include CI_ERCHZ.
Dependencies
If the activation category is "Table", you must enter a table name in this field so that the individual line items from the migration documents can be saved.
Example
The table must have the following structure:
| Fields |Key |Init |Field type |
|.INCLUDE |X | X | EBFKEY |
|.INCLUDE | | X | EBFLIN |
|.INCLUDE | | | CI_EBFLIN |
History
| Last changed by/on | SAP | 20050615 |
| SAP Release Created in | 600 |
