SAP ABAP Data Element E_ORIGFUNC (Origin of Function Module)

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

Basic Data

Data Element	E_ORIGFUNC
Short Description	Origin of Function Module

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	E_ORIGFUNC
Data Type	CHAR	Character String
Length	10
Decimal Places	0
Output Length	10
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID	ORIGFUNC
Default Component name	ORIGIN OF FUNC.MOD
Change document	☑
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Origin FM
Medium	15	Origin of FM
Long	20	Origin iof FunctMod
Heading	10	Origin FM

Documentation

Definition

You can enter values for operands of a rate in the rate facts. This always involves a rate fact group. You can also maintain the operands in the rate facts for several rate fact groups. This allows you to use different billing procedures for customers with the same rate.

Example:

• Rate T100 contains a step that calculates a price for a register. The price operand is PREISOP1.
• You allocate the following rate codes to the PREISOP operand in the rate facts:
  Rate Fact Group Operand Operand Value (Rate Code)
  0001 PREISOP1 PA
  0002 PREISOP1 PB
  0003 PREISOP1 PC
• You create rate type TA and allocate rate T100 to rate type TA in the rate determination.
• During the billing-relevant installation of a device, you specify the rate type TA, in combination with a rate fact group, for the consumption register. This affects the billing in the following way:
• Consumption registers with rate type TA and rate fact group 0001 are calculated with price PA
• Consumption registers with rate type TA and rate fact group 0002 are calculated with price PB
• Consumption registers with rate type TA and rate fact group 0003 are calculated with price PC

Further Remarks:

• You can use the rate fact groups to allocate different values to all operands, not only price operands.
• The specification of a rate fact group is mandatory when maintaining rate facts. There is no operand value that covers all rate fact groups.
• When you enter a rate type for a register or device, or in the rate category facts or the installation facts, an internal rate determination is carried out. You must maintain a rate fact group parallel to the rate category. A check is carried out to ensure that rate facts exist for rate fact groups. For example: If you enter a rate category that is used to determine the aforementioned rate T100, only rate fact groups 0001, 0002, and 0003 are permitted.

  Exception: You are dealing with a rate without rate facts (all operand values come from the installation facts). In this case, the rate fact group must be left empty.

• In contract billing, the rate fact group must be the same for each rate. For example: The installation from a contract contains two consumption registers. Both registers contain the same rate category. The same rate fact group must then be used in both cases. If both registers are billed using different rates, then different rate fact groups may be used.

History

Last changed by/on	SAP	20050224
SAP Release Created in	464