Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBS (Package) G/L Accounts
Basic Data
| Data Element | BILA_EIS |
| Short Description | Extract to SAP-EIS |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 18 | Extract to SAP-EIS |
| Heading | 0 |
Documentation
Definition
If you select this parameter, the balances for the specified reporting period are transferred to SAP-EIS. If this happens, the balance sheet is not displayed on the screen.
By specifying a plan version, you can have planned values for the reporting period transferred to SAP-EIS instead of actual values.
Transfer structure:
- Balance sheet version
- Plan version (filled if plan version is specified)
- Financial statement item
- Account number
- Company code
- Business area
- Reporting year
- Reporting period from
- Reporting period to
- Local currency key
- Balance in local currency
Accounts are assigned to the financial statement items dependent on the balance. When grouping the items together into totals items in EIS, you can refer to the financial statement version from FI (as an external hierarchy). However, the master data hierarchies in EIS are not dependent on the transaction data. This means that the assignment of the accounts to the balance sheet items is committed when the data is transferred from FI. It is based on the balance for the period of the data transfer and on the totals values for each company code. This means that at business area level, a negative balance in a bank account can still be assigned to the credits side of the balance sheet.
Only totals values from the reporting period can be transferred.
The following alternatives exist in conjunction with the "Balance sheet type" parameter and the choice of period:
1. Balance sheet type '1'
Only the values at the key date for closing should be reported in EIS. In this instance, you should run RFBILA00 once for the whole reporting period (e.g. for year-end closing, periods 1-16), and then set the values accumulated over the course of the periods in the period in which closing takes place (e.g. in this case, period 16).
2. Balance sheet type '1' and '2'
You should also be able to report the values for each period during the fiscal year in EIS. In this case, the data transfer must be started individually for each month with RFBILA00. Select balance sheet type '1' (cumulative values) for the first period so that the balance carried forward is also transferred. You should then select balance sheet type '2' (flow of funds analysis) for the subsequent periods, so that only the changes are transferred for the balance sheet accounts.
3. Balance sheet type '4' and '2'
If you want to keep the balance carried forward separate from the flow of funds analysis in EIS, you can transfer the balance carried forward in a separate key figure in EIS by using balance sheet type '4'.
Caution!:
The result calculated by RFBILA00 is transferred to the EIS Toolbox under the account '*RESULT*', once as a balance sheet item and once as a profit and loss item. If you don't want posting to take place under this (non-existent) account, you should maintain the transfer rules accordingly (e.g. by assigning another account or the initial value).
History
| Last changed by/on | SAP | 19950401 |
| SAP Release Created in |
