BCP Configuration FAQs
Answers to common questions regarding configuring Bulk Calculations – Petroleum (BCP) on your systems
For our crude oil conversion group, the S&W % value increases the product mass and weight instead of decreasing it. How can this be?
Enter a transaction quantity of 10 000 m³ (SAP UoM M3):
Apparently, the gross ton value (UoM GT) is lager than expected, also the net ton (UoM TO) and the gross and net weights (UoM GTA and TOA) for a S&W fraction of 0.1 %. How can this be?
Answer: For S&W calculations, it is important to select the correct UoM for gross observed or gross standard volumes (GOV, GSV), which are typically the transaction quantities. By design, M3 is a NOV (Net Observed Volume) UoM. Thus, the calculation is performed “backwards”
Can we calculate masses and weights in parallel with QuantityWare BCP?
Yes.
All QuantityWare BCP MQCI conversion groups are configured such that masses and weights can be calculated in parallel. By default, UoM of SAP dimension MASS are calculated as masses, UoM of SAP dimension WGHTA are calculated as weights:
The LB value is the calculated mass, the LBA value the calculated weight of your product. Certified consultants can configure your conversion groups such that SAP dimension “MASS” UoM are calculated as weights and e.g. dimension “VMASS” UoM are calculated as masses.
SAP QCI conversion groups calculate either the mass (air buoyancy indicator not set) or the weight (air buoyancy indicator set);
How can I extend the density and temperature range for my product?
Issue:
You trade a product which has a base density beyond the supported measurement standard range; or, temperature values along your supply chain are beyond the measurement standard range limits.
Solution:
It is possible to extend the calculation range with one click in the conversion group configuration:
You simply extend the range for densities, pressures and temperatures by selecting the “Extend range of standard implementation” indicator in the conversion group details screen:
This is possible for QuantityWare BCP ASTM D1250-80 and ASTM D1250-04 implementations,
We have extended the ranges of our ASTM D1250-04 conversion group and receive a short dump - how can we prevent such a dump?
Answer: You need to define technical ranges for your conversion group observed density value.
Example: You have extended the ranges for conversion group Q210:
You perform a trial calculation with a density of 0 and a UoM (here KGV) and hit “Return”:
An ABAP short dump happens:
The zero density value leads to a division by zero error. In order to prevent this, you must define a technical range check for the observed density:
In the Petroleum Measurement Cockpit (PMC), you navigate to the range group customizing settings via “Goto ->
Our conversion group calculates the base density at 15 °C. We also need to report the base API gravity at 60 °F. Is this possible?
Yes.
API MPMS Chapter 11.5 2009 provides the calculation logic for such calculations. It replaces the historical table 3, table 21, and table 51 of ASTM D1250-80 Volume XI/XII.
This new logic has been implemented in an ABAP function for MQCI conversion groups, which requires a base temperature of either 15 °C or 60 °F. Template MQCI conversion group Q22A provides the configuration example:
Can we enter the density for one product in different density types (°API, relative density, absolute density)?
Yes.
All BCP MQCI conversion groups can be configured in such a manner.
Example: BCP Template Conversion Group Q210:
Absolute Density:
Relative Density:
API Gravity:
In order to enable this flexible density type data entry, you simply add MQCI function module
/QTYW/MQCI_CON_TDICH_VAC_DNTYP with FMTYP 7to the conversion group function module sequence:
Important Note:
For “Special applications” type conversion groups (Q3** template conversion groups),
We need to report our product density in absolute density, relative density and API gravity. Is this possible?
Yes.
All MQCI conversion groups support such calculations. BCP configuration template conversion group Q210 can be used as a reference:
To achieve this, you simply add the function
/QTYW/MQCI_CALC_BDICH_ALLto the MQCI function module sequence:
and add the six density result parameters to the reading group:
Note: If you require calculation of e.g. the API gravity at 60 °F for a conversion group with base temperature 15 °C (or vice versa), read this FAQ.
We directly want to enter the base density of our products, w/o having to enter a test temperature. Is this possible?
Yes.
All BCP MQCI conversion groups can be configured in such a manner.
Example: BCP Template Conversion Group Q2A1:
Here you only enter the observed product temperature and the base density as input parameters. Then, the VCF and all densities in air values are calculated, as well as all quantity values.
Technically, this is achieved by adding MQCI Function Module
/QTYW/MQCI_BCP_PROD_DEFAULT with FMTYP 9 or /QTYW/MQCI_BCP_CHEM_DEFAULT with FMTYP 9 (for linear DCF conversion groups)to the Function Module Sequence (FSQ) in the configuration settings:
Then you simply remove the test temperature parameter from the reading group,
What does "German rounding" mean?
The ASTM D1250-80 /API MPMS Chapter 11 – 1980 implementation guide specifies, that absolute density values must be rounded to the nearest 0.5 kg/m³ value.
Example:
An input value of 781.3 kg/m³ is internally rounded to 781.5 kg/m³ before it is utilized for the computation of the base density or the VCF and subsequently for the mass values; a value of 781.1 kg/m³ is rounded to 781.0 kg/m³.
This rounding specification leads to the peculiar effect, that a base density value of e.g. 780.3 kg/m³ at 15 °C is rounded to 780.5 kg/m³ (at 15 °C) and a value of 780.1 kg/m³ at 15 °C is rounded to 780.0 kg/m³ (at 15 °C):
To avoid this effect,
We do not require the hydrometer correction. Can we remove it from our conversion group configuration?
Yes.
The hydrometer correction may only be required, if you enter an observed density that is determined with a glass hydrometer. If you utilize an ASTM D1250-04 implementation, you may simply remove the hydrometer function (and also remove the hydrometer indicator from the reading group):
ASTM D1250-80 implementations contain a built-in (by measurement standard definition) hydrometer correction logic, which requires that you actively turn the correction off if it is not required – read note 000026 for all important details.
I have set my quantity value UoM L15 and KG to be rounded to zero decimals, but it is not working. What can I do?
The UoM real rounding settings are considered for all MQCI template conversion groups. Rounding function
/QTYW/MQCI_ROUND_ALT_QUANTITYis assigned to all such conversion groups. To define the real rounding for a UoM, go to the PMC or GMC and navigate to: ( More -> ) Goto -> UoM Rounding:
Maintain the number of decimals for each UoM that shall be rounded.
NOTE:
Via transaction CUNI, you define the number of display decimals for your UoM only –
My rounding settings for the density values for an MQCI conversion group are not considered for the calculation. How can I fix this?
You have copied e.g. template conversion group Q1A1 to Z1A1. For the density UoM PPG (pounds per gallon – lb/ugl) you have maintained a rounding to 4 decimals; business requires that the rounded value is utilized for the calculation of masses.
A simple test calculation with Q1A1 shows the issue: The expected value for UoM LB is 620 540.00 LB; however, the value is calculated using the non-rounded density (while the rounded value is displayed):
This is due to the fact, that the density rounding function /QTYW/MQCI_ROUND_DENSITIES_UOM is processed after the quantity conversion model function /QTYW/MPMS_OBS_TO_ALT_QUAN:
If you position the rounding function before the quantity conversion model function:
the calculation is happening as expected:
The Q*** template conversion groups are configured to round the density values for reporting purposes,
The system displays a volume correction factor (VCF) of 1 for any observed temperature. Why is that?
MQCI conversion groups can be configured to display the volume correction factor (VCF / CTL / CTPL) from observed temperature to base temperature. The observed temperature (also known as material temperature) is associated with the transaction quantity of the product.
If you enter a transaction quantity with a UoM that has a temperature value assigned (GSV or NSV), the VCF is always calculated taking that temperature as observed temperature. By design, you are allowed to enter such a transaction quantity UoM.
Example 1 – 100 000 L15 :
The 15 °C assigned to L15 “overwrite”
My customer requires ASTM Table 1 UoM conversion factors. What are the configuration steps?
For MQCI conversion groups, you simply activate the ASTM Table 1 conversion factors and ASTM Table 1 version in the conversion group detail settings:
With the QuantityWare BCS configuration templates, ASTM Table 1 conversion factors are delivered, which are accessible in your client 045 after activation of the relevant Business Configuration (BC) set. Read Note 000055 for all important additional configuration details.
My client wants to use MQCI conversion groups, where UoM KG, LB, TO, STO ... are calculated as weights - is this possible?
Yes.
The BCS configuration template provides example MQCI conversion groups that are configured such that UoM of SAP dimension ID MASS are calculated as weights (which is also the case for SAP QCI conversion groups if the air buoyancy indicator is set).
Example – BCP template conversion group Q214:
The LB value is the weight of the 10 000 gallons of product. The configuration to achieve this requires 2 (plus 1) steps:
Step 1:
You assign the SAP Dimension IDs for weight (and mass) DIMID:
Step 2:
You assign marker function /QTYW/MQCI_WEIGHT_MASS to the MQCI model function sequence:
Step 3:
Depending on the MQCI calculation model,
What is MQCI function /QTYW/MQCI_SYNC_EXT_VALUES good for?
All QuantityWare MQCI template conversion groups are configured such that the MQCI function module sequence contains function
- /QTYW/MQCI_SYNC_EXT_VALUES
as default.
This function detects quantity value data that is passed from external systems (e.g. TAS systems) and subsequently synchronizes dependent quantity values based on that data.
This synchronization – i.e., keeping related quantity values consistent – is an important part of the two main roles that QuantityWare BCS fulfills: The “Gatekeeper” and the “Enricher” role.
Synchronization example 1:
- Transaction quantity is 1001 Liters (L)
- Internally,
