Property talk:P2139

From Wikidata
Jump to navigation Jump to search

Documentation

total revenue
income gained by an organization during a given time frame. Not to be confused with fiscal revenue
DescriptionAmount of revenue for a company/organization in one year
Representsrevenue (Q850210)
Data typeQuantity
Domain
According to this template: Entities
According to statements in the property:
organization (Q43229), business (Q4830453), company (Q783794), tax (Q8161), mixed martial arts event (Q18536800) or fictional company (Q5446565)
When possible, data should only be stored as statements
Allowed values
According to this template: Positive numbers
According to statements in the property:
0 ≤ 𝓧 ≤ 5E14
When possible, data should only be stored as statements
Allowed unitsInstances of: currency
United States dollar (Q4917), yen (Q8146), pound sterling (Q25224), Euro (Q4916), Czech koruna (Q131016), Canadian dollar (Q1104069), rupee (Q178843), Norwegian krone (Q132643), Swiss franc (Q25344), renminbi (Q39099), won (Q202040), Swedish krona (Q122922), Russian ruble (Q41044), Danish krone (Q25417), Brazilian real (Q173117), United Arab Emirates dirham (Q200294), forint (Q47190), naira (Q203567), Argentine convertible peso (Q199578), złoty (Q123213), New Taiwan dollar (Q208526), Australian dollar (Q259502), Indian rupee (Q80524), new shekel (Q131309), hryvnia (Q81893), Bulgarian lev (Q172540), West African CFA franc (Q861690), Central African CFA franc (Q847739), Saudi riyal (Q199857), Philippine peso (Q17193), Vietnamese đồng (Q192090), Malaysian ringgit (Q163712), Mexican peso (Q4730), Romanian Leu (Q131645), rupiah (Q41588), New Zealand dollar (Q1472704), French franc (Q184172), Belarusian ruble (Q21531507), Singapore dollar (Q190951), ruble (Q15788), Serbian dinar (Q172524), Hong Kong dollar (Q31015), Botswana pula (Q186794), Egyptian pound (Q199462), Namibian dollar (Q202462), Syrian pound (Q240468), Iraqi dinar (Q193094), Uzbekistani som (Q487888) or Georgian lari (Q4608)
ExampleSamsung Electronics (Q20718) → 2.58935494E14 won
Wikimedia Spain (Q14866877) → 18,601.52 Euro
Guillin Group (Q130387411) → 884,640,000 Euro
German Red Cross (Q694104) → 210,731,000 Euro
Robot and gadget jobsGlobal Economic Map Bot can do this
Tracking: usageCategory:Pages using Wikidata property P2139 (Q21606244)
See alsofiscal/tax revenue (P3087), total assets (P2403), net profit (P2295), operating income (P3362)
Lists
Proposal discussionProposal discussion
Current uses
Total101,438
Main statement100,92799.5% of uses
Qualifier5100.5% of uses
Reference1<0.1% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Required qualifier “point in time (P585): this property should be used with the listed qualifier. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2139#mandatory qualifier, SPARQL
Range from “0” to “5e+14”: values should be in the range from “0” to “5e+14”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2139#Range, hourly updated report
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2139#Single value, SPARQL
Citation needed: the property must have at least one reference (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2139#citation needed
Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2139#Scope, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2139#Entity types
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Currency

[edit]

I've added more currencies to allowed units. In many cases, the revenue can only be claimed as reported in a company's financial reports, using the same currency specified there. Danrok (talk) 11:02, 14 July 2016 (UTC)[reply]

Constraints / point in time vs. start time&endtime

[edit]

The constraint point in time is false. The value of total assets is at some point in time - usually 31.12.XXXX. Revenue is always the flow of some time period - for example start time 01.01.2017 - end time 31.12.2017. Any comments? Datawiki30 (talk) 11:48, 21 July 2018 (UTC)[reply]

@Datawiki30: I would say that "point in time: 2015" means "in the 2015 fiscal year" or something like that. − Pintoch (talk) 08:41, 14 January 2019 (UTC)[reply]
@Datawiki30: Agree with you here. Fiscal years often don't match the calendar year and it is not uncommon to have fiscal years that are more or less than 12 months. Some companies have 52 week fiscal years and other abnormalities. The only elegant way I can see to solve all these problems would be to specify the exact bounds of the fiscal year. Belteshassar (talk) 11:54, 8 September 2019 (UTC)[reply]
Some definition on this talk page doesn’t mean anything. I’m using valid in period (P1264) as the more appropriate qualifier for a periodic/cumulating value, which works fine for calendar years. Use start/end qualifiers for fiscal years that differ and don’t have their own item, I guess. Karl Oblique (talk) 13:09, 5 January 2024 (UTC)[reply]

Einsatzbereich / Range of use

[edit]

Don't we need geographical and/or administrative or subject-orientated dimensions, too? E.g. the market for pharmaceutical products in Germanys and its size. Polimorph (talk) 15:57, 29 October 2019 (UTC)[reply]

Range constraints

[edit]

The range constraints "Type “organization (Q43229), business (Q4830453), company (Q783794), tax (Q8161), mixed martial arts event (Q18536800)”" are strange. How could we define the total revenue for a video game, for example? The addition of Q18536800 suggests this is not just for organizations, but also events, products, etc. Why have an exception just for Q18536800?

Adding another currency

[edit]

Can someone add Syrian pound to the allowed currencies. Thanks 2620:6E:6000:3100:6528:F7F3:E690:A995 01:07, 12 December 2023 (UTC)[reply]

✓ Done. See Special:Diff/2028326501. Regards Kirilloparma (talk) 03:46, 12 December 2023 (UTC)[reply]