BCG Configuration FAQs
Answers to common questions regarding configuring Bulk Calculations – Gas (BCG) on your systems
Which conversion group should I use for my high pressure pipeline natural gas project?
For high pressure natural gas projects, an MQCI conversion group should be selected. A certified BCG consultant can access the Gas Measurement Cockpit (GMC) and will follow the PAIG Methodology in order to create a selection of template conversion groups. The correct choice then depends on the detailed calculation scenario requirements which you will discuss with the certified consultant.
Template selection of high pressure conversion groups for AGA Report No. 8 / ISO 6976 calculations:
Does QuantityWare BCG support hydrogen quantity conversions?
Due to strong industry demand, QuantityWare has defined a development strategy for 100% hydrogen quantity conversions, which is published in note 000106. See the BCS Supported Products Manual for this new product support.
Read the FAQ for natural gas / hydrogen mixtures for support of natural gas – hydrogen mixtures.
The first release of a 100% high pressure hydrogen quantity conversion solution – as part of QuantityWare BCG 3.0 – has been delivered as an Advanced Development (AD) with note 000100 in July 2022,
We are processing natural gas with a high hydrogen fraction, but not 100% hydrogen. What conversion groups can we use for such a gas?
As stated in the research paper from the DVGW: “Calculation of Compression Factors and Gas Law Deviation Factors Using the Modified SGERG-Equation SGERG-mod-H2”
“The AGA8 equation and the GERG-2008 equation generally agree better than ± 0.1% for the measured values for all data sets in the entire pressure range. It can thus be expected that these equations of state can be used for any desired H2 fractions without significantly affecting the underlying 0.1% uncertainty of the equations.”
Thus, BCG conversion groups that are configured to utilize AGA8 compression factor calculations may be utilized for natural gas / hydrogen mixtures of any ratio.
I require UoM gigawatt hours for my natural gas calculations, how do I define it?
Gigawatt hour is an energy UoM. Within the QuantityWare template, 30 energy UoM are delivered:
Gigawatt hour and terawatt hour are not defined in the template. However, these UoM can be added easily to the template and then distributed through your system landscape. Simply copy e.g. UoM MWH (megawatt hour):
to GWH and TWH, and adjust the exponent in the details from 6 to 9 (GWH) / 12 (TWH). Check with business experts if a combustion condition set is required – typically natural gas quantity conversions do require specification of a combustion reference temperature:
With the next BCS CSP,
Which conversion group should I use for my LNG project?
For LNG projects, an MQCI conversion group should be selected. A certified BCG consultant can access the Gas Measurement Cockpit (GMC) and will follow the PAIG Methodology in order to create a selection of template conversion groups. The correct choice then depends on the detailed calculation scenario requirements which you will discuss with the certified consultant.
Template selection of LNG conversion groups for detailed ISO 6578 LNG calculations:
What options do we have for ISO 6578 LNG density calculations from composition?
QuantityWare BCG supports the ISO 6578 (Version 1991 and 2017) density calculations for LNG. As described in Note 000076, the main difference between these two versions is the definition of configuration data, i.e. the k1 and k2 factors and orthobaric molar volumes. Customers may wish to utilize their own, contractually defined, calculation data sets.
NOTE: This is a critical task for any LNG implementation, thus a certified BCG consultant is required to support this task.
You have three options to define the density calculations:
- Utilize ISO 6578:1991 data –
My LNG volumes in SAP Tank Management are way to large, how can this be?
The tank master data in SAP Tank Management (transaction O4NA) only allows the definition of a UoM of dimension VOLUME as capacity UoM. Thus, you define e.g. M3 (cubic meter, m³) as capacity UoM.
If you now perform a tank dip, utilizing your strapping data values in M3, the mass and energy values calculated are too small when compare to the apparent liquid LNG M3 value calculated from strapping – or the volume value in M3 (or any other UoM of dimension VOLUME) appears to large in relation to the masses and energies.
Reason: For all LNG template conversion groups,
Why are there no chemical components for i-butane and i-pentane defined in the gas component analysis?
i-butane and i-pentane are synonyms for the components 2-methylpropane and 2-methylbutane (the preferred IUPAC name), i.e. i-butane is 2-methylpropane and i-pentane is 2-methylbutane.
Some template conversion groups contain this mapping in the reading group parameter description, e.g. QVK0:
We enter pressure values for gas calculations. Are these values absolute or gauge pressure values?
QuantityWare BCS implementations for LPG/NGL, LNG and natural gas support both the data entry of absolute and gauge pressure values. The conversion group configuration can be made to support entry of either gauge or absolute pressure values – by adding or removing dedicated MQCI pressure calculation functions to the conversion group function module sequence.
If you execute the Conversion Group Check, a message is issued that informs if pressure values (input data) are considered as absolute or gauge values.
Example 1: Template Conversion Group Q741:
Example 2: Template Conversion Group Q154:
Read Note 000078 for additional details.
We receive error message /QTYW/BCG 114 - Heating value class is initial. How can we resolve this issue?
You perform quantity conversion calculations utilizing MQCI natural gas or LNG conversion groups. You receive error message /QTYW/BCG 114 – Heating value class is initial, enter a valid heating value class.
This message does not explain why the calculation is not completing. It actually appears, if the transaction UoM or any target UoM is not of an allowed SAP dimension ID – Energy, Volume, Mass (or Volume(Liquid, LNG)) for LNG and natural gas.
Example: Test Calculation for high pressure natural gas:
The calculation is executed successfully. Now we change the transaction UoM to M3L,
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 conversion groups (where rounding function/QTYW/MQCI_ROUND_ALT_QUANTITY
and maintain the number of decimals for each UoM that shall be rounded.
NOTE: In the main UoM transaction CUNI, you define the number of display decimals for your UoM only – Read FAQ Display UoM for additional details.
How can I extend the density and temperature range for my product?
I have a product which has a base density beyond the supported measurement standard range, is it possible to extend the calculation range?
If the algorithm defined in the measurement standards allows so, 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:
Read Annex D: Standard Range Limit Extensions in the BCP Supported Standards Manual for additional information.
Important: If you decide to set the “extend range of standard implementation” indicator,
What is MQCI function /QTYW/MQCI_SYNC_EXT_VALUES good for?
BCS contains function /QTYW/MQCI_SYNC_EXT_VALUES, which you can decide to add to your MQCI conversion group configuration. This function detects quantity value data passed from external systems (via the “manual entry indicator”) to the SAP system. It then 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.
All QuantityWare MQCI template conversion groups are configured such that the MQCI function module sequence contains function /QTYW/MQCI_SYNC_EXT_VALUES as default.