Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NPAS (Package) Application development patient accounting system
Basic Data
| Data Element | ISH_REVASGN |
| Short Description | IS-H: Service Performance Date Determines Revenue Period |
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 | 10 | Rev.Asgmt |
| Medium | 14 | Revenue Asgmt |
| Long | 20 | Revenue Assignment |
| Heading | 1 | A |
Documentation
Definition
Certain hospital services should always be posted as revenue in Financial Accounting in the fiscal year in which they are performed.
Billing automates this revenue assignment when invoices are created.
Example:
A patient is hospitalized from 12/20/2000 through 12/27/2000. Billing is carried out on 01/15/2001. The corresponding posting period of the previous year is open. In this case, the system should post the revenue in the fiscal year 2000.
Select this option if you want services to be posted as revenue in the fiscal year in which they are performed.
If you select this option, you also have to select Period Split since extended services may have to be split between two fiscal years when a patient's case involves a stay bridging a fiscal year change. For these cases, a separate invoice will be created for each fiscal year.
Country Version Germany:
For flat rate per case charges, the criterion for revenue assignment is the date when the maximum length of stay is reached rather than the service performance date.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 463 |
