Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20_JBP (Package) IS-U: Japanese Billing Preriod
Basic Data
| Data Element | BP |
| Short Description | Selection of Billing Period: Standard or JBP |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BP | |
| 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 | BillPeriod |
| Medium | 15 | Billing Period |
| Long | 20 | Billing Period |
| Heading | 5 | BillP |
Documentation
Definition
The billing period is normally determined by the distance between two periodic meter reading results from a billing-relevant register.
There are two kinds of periods:
- Standard billing period (SBP). This billing period is defined in the following way:
SBP = [meter reading date of the last periodic result +1, meter reading date of current periodic result] - Billing period for Japanese energy provider (electricity) (JBP):
JBP = [meter reading date of last periodic result, meter reading date of current periodic result - 1 day]
Use
Note:
- You can define the billing period you want to use at division category level.
- We recommend that you use the same procedure for all division categories. If you do not make any selection, the SBP procedure is always used.
- Customizing settings cannot be changed afterwards.
Dependencies
Example
The last periodic result was entered on March 31, 2002 at 16:45 with 100kWh. The current periodic result was entered on April 30, 2002 at 11.15 with 220kWh. The following applies:
SBP = [04.01.2002, 04.30.2002]
JBP = [03.31.2002, 04.29.2002]
Make sure that the number of days in both cases is the same (here = 30 days). The consumption difference stays the same (here = 120 kWh)
Amounts from bills that were created before the SBP or JBP can be slightly different if there are prorations during a non-linear weighting procedure. This is due to possible differences that can occur in the weighting total.
It is not important which procedure is use from a business point of view.
Note:
SAP recommends that you always use the standard procedure (SBP) since this produces fewer problems in extreme situations. For example, a device removal and a meter reading that triggers billing on the same day is a problem in JBP, not in SBP.
Supplementary Documentation - BPETSBEL 0001
Use
With this parameter, you can influence the data printed in the open item list of the reply letter.
Supplementary Documentation - BPETSBEL 0002
Use
With this parameter, you can influence the data printed in the account statement or in the open item list.
Supplementary Documentation - BPMNG 0001
Use
If an order price unit that differs from the order unit has been defined in the purchase order, the goods receipt is recorded .
Recording the GR quantity in both units of measure is important for the following reasons:
- Goods receipts are valuated on the basis of the incoming quantities in order price unit.
- Invoice verification is also carried out on the basis of the GR quantity in order price unit.
- You can give notification of variances in the order price quantity immediately on receipt of deliveries.
Change the order price quantity if this differs from the proposed quantity. The variance must lie within predetermined tolerances.
In the event of partial (i.e. less than full) delivery, you must first change the quantity in the order unit. The order price quantity will be adjusted accordingly.
Supplementary Documentation - BPREI 0001
Procedure
- If a purchasing info record exists for the material, the net price will be taken from it. If you have entered a price, it will be overwritten. However, you can change the price on the detail screen.
- If the item is created with reference to a reference document, the price is taken from the reference item. That is to say, the price from the info record is not taken into account.
- If no reference price exists, enter the vendor's gross unit price. The system will calculate the net price automatically.
You can enter the following:
- The net price (that is the price including the vendor's discounts or surcharges).
- The gross price (that is the price excluding discounts or surcharges).
You maintain the conditions for the item. The net price is then calculated by the system.
Dependencies
During creation, you can only maintain the net price if you have not yet maintained the info record conditions. You must then maintain the price on the conditions screen.
Supplementary Documentation - BPREI 0002
Procedure
- If a purchasing info record exists for the material, the net price will be taken from it. You can change the price.
- If the item is created with reference to a reference document, the price is taken from the reference item. That is to say, the price from the info record is not taken into account.
- If no reference price exists, enter the vendor's gross unit price. The system will calculate the net price automatically.
You can enter the following:
- The net price (that is the price including the vendor's discounts or surcharges).
- The gross price (that is the price excluding discounts or surcharges).
You maintain the conditions for the item. The net price is then calculated by the system.
Dependencies
During creation, you can only maintain the net price if you have not yet maintained the info record conditions. You must then maintain the price on the conditions screen.
Supplementary Documentation - BPREI 0003
Procedure
You can enter the following:
- The net price, i.e. the price including the vendor's discounts or surcharges, or
- The gross price, i.e. the price excluding discounts or surcharges.
You maintain the conditions for the item. The net price will then be determined by the system.
If a purchasing info record exists for the material, enter the number of the info record in the field "Info record". The price will be adopted from this field.
Supplementary Documentation - BP_ADR_REF0010
Use
The address ID you define here is used as the default ID when a business partner is created in the selected role. The address you enter is registered under this ID.
You can change the default address ID when you create a partner. You can also define additional addresses under other IDs.
Procedure
Examples
Dependencies
Supplementary Documentation - BP_AVA_ALL0001
Use
In the project budget profile, the "Overall" indicator, used in conjunction with the "Releases" indicator, has the following effect:
Ind. 'Overall' Ind. 'Releases' Avail. control against ...
X - Overall budget
- - Annual budget
X X Overall budget released
- X Annual budget released
X = Indicator is set, in other words, checkbox was checked.
Procedure
Examples
Dependencies
If you carry out budgeting and then change the availability control settings, you should have the system recalculate the assigned values.
To do this, start availability control background activation in your application and choose the indicator "Recalculate all funds commitments".
Supplementary Documentation - BP_AVA_ALL0002
Use
If the indicator is set, availability control conducts checks against the overall budget.
Procedure
Examples
Dependencies
Supplementary Documentation - BP_CHAR1 0001
Use
Original language indicator
Supplementary Documentation - BP_CHAR1 0002
Use
Original language indicator
Supplementary Documentation - BP_CHAR1 7001
Use
Occupied/free/all rooms indicator
This field is an internal field, and is of no relevance for the user.
Procedure
Examples
Dependencies
Supplementary Documentation - BP_CP_M1 0001
Definition
Indicator which controls how the data already in the target version is to be treated
Use
You can opt to either keep existing plan data in the target version, or to overwrite it.
- Retain (i.e. just add new data)
The SAP System checks whether the target version for the project includes plan data in the relevant degree of planning detail. This data is not overwritten.
Example 1:
If version 000 contains structure plan values for 1994 and 1995, and version 001 contains structure plan avlues for 1994, only the new data - that is, the values for 1995 - are copied.Example 2:
There are two plan versions, with the following cost element plan values:
Version 000:
Cost element 400000/1995: $1000 and 415000/1995: $1500
Version 001:
Cost element 400000/1995: $2000
The system copies the plan value for cost element 415000 to version 001.
If the target version ever contained plan data, but you have since reset the value to 0, the database still includes a planning data record, with value 0. The SAP System recognizes this data record and does not overwrite it.
- reset and overwrite
The SAP System resets all the data in the target version relating to the relevant planning activity, and overwrites it with the plan data from the reference version.
Supplementary Documentation - BP_CP_M1 0002
Use
If you set this indicator, only budget values from the reference version are copied to the target version when no budget values exist in the given Budget Structure Elements. No changes are made to any existing values in the target version.
Examples
Some original budget already exists in the target version for BS elements A,B,C. You are copying original budget from the reference version to the target version:
Reference version:
A: $100 B: $10 C: $0
Target version before copy process:
A: $3 B: $0 C: $300
Target version after the copy process:
A: $3 B: $10 C: $300
Supplementary Documentation - BP_CP_M2 0001
Definition
Indicator which controls how the data already in the target version is to be treated
Use
You can opt either to retain the existing data in the target version, or to overwrite it
- reset and overwrite
The SAP System resets all the data in the target version relating to the relevant planning activity, and overwrites it with the plan data from the reference version.You can opt to either keep existing plan data in the target version, or to overwrite it.
- Retain (i.e. just add new data)
The SAP System checks whether the target version for the project includes plan data in the relevant degree of planning detail. This data is not overwritten.
Example 1:
If version 000 contains structure plan values for 1994 and 1995, and version 001 contains structure plan avlues for 1994, only the new data - that is, the values for 1995 - are copied.Example 2:
There are two plan versions, with the following cost element plan values:
Version 000:
Cost element 400000/1995: $1000 and 415000/1995: $1500
Version 001:
Cost element 400000/1995: $2000
The system copies the plan value for cost element 415000 to version 001.
If the target version ever contained plan data, but you have since reset the value to 0, the database still includes a planning data record, with value 0. The SAP System recognizes this data record and does not overwrite it.
Supplementary Documentation - BP_CP_M2 0002
Use
If you set this indicator, the existing budget values in the target version are reset and you can overwrite them with budget values from the reference version.
Procedure
Examples
Original budget already exists in the target version for Budget Structure Elements A,B,C and you are copying original budget from the reference version to the target version.
Reference version:
A: $100 B: $10 C: $0
Target version before copy process:
A: $3 B: $0 C: $300
Target version after the copy process:
A: $100 B: $10 C: $0
Supplementary Documentation - BP_CP_M3 0002
Use
If you set this indicator, new budget values in the reference version are added to the existing budget values in the target version.
Examples
Original budget already exists for Budget Structure Elements A,B,C in the target version and you are copying original budget from the reference version to the target version:
Reference version:
A: $100 B: $10 C: $0
Target version before copy process:
A: $3 B: $0 C: $300
Target version after the copy process:
A: $103 B: $10 C: $300
Supplementary Documentation - BP_FNPAI_EXIT0001
Use
The function module can contain the check routines for the Differentiation Type. You must execute these after you have input the values for the individual Differentiation Type Elements
Examples
If a differentiation type comprises several elements, you can check whether the values for the differentiation type elements produce a meaningful combination.
Supplementary Documentation - BP_FNPAI_EXIT0002
Use
The function module can contain the check routines for a Differentiation Type Element. You must execute these after you have input the value.
Supplementary Documentation - BP_GEBER 0001
Use
When payroll is transfer to accounting, postings are made to the fund entered in the cost distribution.
Exception: If the integration between HR and Funds Management is being processed using position management when settlement is carried out, the system uses the fund from the source of funds in Position Management.
Dependencies
Example
Supplementary Documentation - BP_GEBER2 0001
Use
The fund that was entered during the cost distribution is posted at the time of the transfer from payroll to accounting.
Exception: If the integration between HR and Funds Management is managed by HR Funds and Position Management, then the fund is determined from the financing in HR Funds and Position Management. Then any funds entered here do not have any significance.
Dependencies
Example
Supplementary Documentation - BP_GRP_ID_CTL0000
Use
Enter a business partner grouping for the Treasury Business Partner that refers to a number range with internal number assignment. If you have activated parallel maintenance and the System is unable to determine a Treasury Business Partner grouping when you create a Treasury Business Partner from an SAP Business Partner, the number is drawn from the number range assigned to this grouping.
Supplementary Documentation - BP_PARTNR 0001
Use
You must specify a business partner for variable transactions with value maintenance "with daily balances" or "with turnovers". The business partner is optional with value maintenance "without any of its own flow data". There is no business partner for variable transactions with value maintenance "with flows from FI G/L accounts".
Dependencies
Example
Supplementary Documentation - BP_PPROFIL0002
Use
You can control planning using the following parameters:
- Time frame
- Time period, which can be planned in the past
- Time period, which can be planned in the future
- Start year for cost planning
- Planning of overall-/annual period values
- Presentation
- View besides planned value at initial entry in the function
- Decimal places and display factor as default values
- Detailed planning (internal orders, project system)
Cost element group
- Primary costs
- Revenues
Plan parameters
- Costs
- Revenues
Sender cost center group
Sender activity type group
Statistical key figure group
Costing variants
- Planning elements (Project system)
- Planning on all WBS elements or only on planning elements
Dependencies
This description is only valid with certain limitations for the planning profile in cash budget management. You can find a description of the settings you can make in the planning profile in cash budget management, in the Implementation Guide for Cash Budget Management under "Set Planning Profile".
Supplementary Documentation - BP_PROFIL 0001
Use
You can use the following parameters to control budget planning in cost center accounting:
- Fix the past or future periods for which budgeting is possible
- Define the start year, in which budgeting is to start
- Define the scaling and decimal places for the value display in budget planning
- Fix period or year planning
- Define default values for the distribution key
Procedure
Enter a valid profile (use function "Input help" to display all the profiles) or enter a profile in cost center accounting customizing, under -> Planning -> Planning help -> Budget planning profile, and branch from there to -> Detail input -> Cost centers, to define your parameters.
Examples
Dependencies
If you carried out your initial budget planning with the "annual values" parameter activated, and later activate the "Period values" parameter in the profile, the system continues to display the annual values. Similarly, if you carried out your initial planning with parameter "Period values" activated, the system continues to display the period values if you later activate the annual values parameter.
Supplementary Documentation - BP_RELEASE0001
Definition
Indicator which determines whether availability control is carried out when the overall or the annual budget released.
Use
In the project budget profile, the "Overall" indicator, used in conjunction with the "Releases" indicator, has the following effect:
Ind. 'Overall' Ind. 'Releases' Avail. Control against ...
X X Overall budget released
- X Annual budget released
X - Overall budget
- - Annual budget
X = Indicator is set, in other words, checkbox was checked.
Procedure
Examples
Dependencies
Project System
If you change the availability control settings after carrying out budgeting, you should have the system recalculate the assigned values.
To do this, start background activation of availability control in your application, and choose "Recalculate all funds commitments".
Funds Management
If you change the settings for availability control (for example, Release/Budget), you must reconstruct the assigned values. You can start the program for this in the application menu or in the Funds Management implementation guide.
Supplementary Documentation - BP_RELEASE0002
Definition
Indicator, which controls whether availability control conducts checks against the commitment budget or funds released from it.
Use
If you set the indicator, availability control conducts checks against funds released from the commitment budget.
Procedure
Examples
Dependencies
Supplementary Documentation - BP_ROLETYP0001
Use
You must define a role category for accounting clerk here, if, as was previously the case, the accounting clerk is to be managed as a partner for this transaction type. If you have not assigned a role category to the accounting clerk, you must manage the accounting clerk via the entries defined in Customizing (Loans Management -> Functions -> Process Management -> Define Clerks).
Dependencies
Example
Supplementary Documentation - BP_ROLETYP_OLD0001
Use
You define the role category of the main contract partner here for the general contract.
You create a customer role category for a customer contract and a vendor role category for a vendor contract.
Dependencies
Example
Supplementary Documentation - BP_SUBVO 0001
Use
You can use the budget subtype that you enter here to identify the budget values that will be changed by this program.
Dependencies
Example
Supplementary Documentation - BP_VERSION0001
Use
Procedure
Enter an existing budget version in the original FM area in which you would like to import the budget data.
Examples
Dependencies
Supplementary Documentation - BP_VERSION0002
Use
Procedure
Enter the budget version of the euro FM area from which you would like to export budget data.
Examples
Dependencies
Supplementary Documentation - BP_VERS_V 0001
Definition
Version, from which the selected plan data is copied into the target version.
Use
Procedure
Examples
Dependencies
Supplementary Documentation - BP_VERS_V 0002
Definition
Version, from which the chosen budget data is copied into the target version.
Use
Procedure
Examples
Dependencies
Supplementary Documentation - BP_VERS_Z 0001
Definition
Version, into which the chosen plan data is copied from the reference version.
Use
Procedure
Examples
Dependencies
Supplementary Documentation - BP_VERS_Z 0002
Use
Version, into which the chosen budget data is copied from the reference version.
Procedure
Examples
Dependencies
Supplementary Documentation - BP_V_ACT_S0001
Definition
Indicator which controls that only data from individual planning activities is copied.
Use
If you select this indicator, the system copies only selected planning actvities from the reference version into the target version.
Use the "Select" pushbutton to select the planning areas required.
Supplementary Documentation - BP_V_ACT_S0002
Definition
Indicator which controls that only data from individual budget transactions is to be copied.
Use
If you activate this indicator, the system copies only selected budget activities from the reference version into the target version.
Use the "Select" pushbutton to select the budgets required.
Use
Procedure
Examples
Dependencies
Supplementary Documentation - BP_V_ADD 0002
Definition
Indicator, which controls how existing data in the target version is to be treated.
Use
You have the option of keeping existing budget data in the target version, or of overwriting it.
- keeping the data
The system checks, whether the project in the target version already contains budget data for the relevant budget activity. If it does, the data is not overwritten.
If budget data ever existed in the target version, but you have reset the value to zero, the data base still has a budget data record for thisproject, with value 0. The system recognizes this data record and does not overwrite it.
- resetting and overwriting
The system resets all the data in the target version for the relevant budget activity and overwrites it with the budget data from the reference version.
- adding
The system adds the data from the selected budget activities in the reference version to the data in the target version.
Procedure
Examples
Dependencies
Supplementary Documentation - BP_V_N_CHG0001
Definition
Indicator, which controls how existing data in the target version is treated.
You have the option of keeping existing planning data in the target version, or of overwriting it.
- keeping the data
The system checks, whether the project in the target version already contains planning data for the relevant degree of detail. If it does, the data is not overwritten.
Example 1:
If version 000 contains rough plan values for 1995 and 1996 and version 001 contains structure plan values for 1995, only the new data - that is, the values for 1996 - is copied.Example 2
There are two plan versions with the following cost element plan values:
Version 000
Cost element 400000/1995: $1000 and 415000/1995: $1500
Version 001:
Cost element 400000/1995: $2000
The system copies the plan value for cost element 415000 to version 001.If planning data ever existed in the target version, but you have reset the value to zero, the database still has a planning data record for this project, with value 0. The system recognizes this data record and does not overwrite it.
- resetting and overwriting
The system resets all the data in the target version for the relevant planning activity and overwrites it with the planning data from the reference version.
Supplementary Documentation - BP_V_N_CHG0002
Definition
Indicator, which controls how existing data in the target version is treated.
Use
You have the option of keeping existing budget data in the target version, or of overwriting it.
- keeping the data
The system checks, whether the project in the target version already contains budget data for the relevant budget activity. If it does, the data is not overwritten.
If budget data ever existed in the target version, but you have reset the value to zero, the database still has a budget data record for this project, with value 0. The system recognizes this data record and does not overwrite it.
- resetting and overwriting
The system resets all the data in the target version for the relevant budget activity and overwrites it with the budget data from the reference version.
- adding
The system adds the data from the selected budget activities in the reference version to the data in the target version.
Supplementary Documentation - BP_V_UPD 0001
Definition
Indicator, which controls how existing data in the target version is treated.
Use
You have the option of keeping existing planning data in the target version, or of overwriting it.
- Resetting and overwriting
The system resets all the data in the target version for the relevant planning details and overwrites it with the planning data from the reference version.
- Keeping the data - that is, adding only new data
The system checks whether the order in the target version already contains planning data for the relevant planning details. If it does, the data is not overwritten.
Example 1:
If version 000 contains rough plan values for 1996 and 1997 and version 001 contains structure plan values for 1996, only the new data - that is, the values for 1997 - is copied.Example 2
There are two plan versions with the following cost element plan values:
Version 000
Cost element 400000/1997: $1000 and 415000/1997: $1500
Version 001:
Cost element 400000/1997: $2000
The system copies the plan value for cost element 415000 to version 001.If planning data ever existed in the target version, which you have reset to zero, the database still has a planning data record in the database with value 0. The system recognizes this data record and does not overwrite it.
Supplementary Documentation - BP_V_UPD 0002
Definition
Indicator, which controls how existing data in the target version is treated.
Use
You have the option of keeping existing budget data in the target version, or of overwriting it.
- keeping the data
The system checks, whether the project in the target version already contains budget data for the relevant budget activity. If it does, the data is not overwritten.
If budget data ever existed in the target version, but you have reset the value to zero, the database still has a budget data record for this project, with value 0. The system recognizes this data record and does not overwrite it.
- resetting and overwriting
The system resets all the data in the target version for the relevant budget activity and overwrites it with the budget data from the reference version.
- adding
The system adds the data from the selected budget activities in the reference version to the data in the target version.
Supplementary Documentation - BP_WERT1 1964
Only relevant to investment programs:
Based on the corresponding maintenance transactions, the system displays the following values in this field:
- Original budget (without supplements or returns)
- Supplements
- Returns
The current budget is not displayed (original budget + supplements - returns). The current budget can be displayed in the second column (depending on how you set the view).
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 471 |
