SShortSingh.
Back to feed

How the Oil and Gas Downstream Business Moves From Crude Oil to Customer

0
·1 views

The downstream segment of the oil and gas industry covers refining, processing, distribution, marketing and sales of petroleum products to end customers. The process begins with procuring crude oil from internal or external suppliers, with activities such as contract management and quality monitoring. Refined products like petrol, diesel, aviation fuel, LPG and naphtha are then held in storage, where inventory tracking and stock reconciliation take place. Finished goods are moved to depots and retail outlets by pipeline, tanker, rail or road, and sold to retail, industrial and commercial buyers. The article also notes that SAP software modules such as MM, SD and FI are used to manage these stages, from inventory and logistics through to billing and financial reporting.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Entwickler baut iOS-App für Clash-of-Clans-Layouts mit Fokus auf Spielerfilter

A developer has created a free, unofficial iOS app for finding Clash of Clans base layouts, not affiliated with Supercell. The app lets players filter bases by Town Hall level so that lower-level layouts are excluded for higher-level accounts. It separates layouts into modes for war, farming, and Clan War League, and allows a single tap to copy a layout directly into the game. According to the developer, usage data suggests players favor bases with fewer copies, since those are harder for opponents to prepare for.

0
ProgrammingDEV Community ·

Record a short repro for coding agents instead of describing bugs in Slack

The author argues that vague bug descriptions in Slack threads give coding agents too little to work with, leading to patches that miss the actual problem. Instead, they recommend a brief, replayable repro such as numbered steps, a failing URL, a minimal network snippet, a short recording, or the relevant console stack trace. The piece stresses keeping the effort proportionate, so the repro is cheaper than guessing. It also offers a reusable template that captures surface, environment, steps, expected and actual results, and artifacts, along with rules for keeping recordings useful. Slack is positioned for routing and triage, while the agent chat or pull request serves as the artifact layer.

0
ProgrammingDEV Community ·

Friday app shares corrections across coding agents so fixes carry over between tools

Friday is a free, MIT-licensed desktop app that runs coding agents such as Claude Code, Codex and Cursor side by side on a user's computer. After each run, the coding tool reads the session locally and records lessons like decisions, pitfalls, and conventions for that repository. When a user corrects an agent, that correction is passed to every agent that later works in the same repository, regardless of tool. If a mistake recurs, Friday can run a user-approved read-only or test command after changes and returns failures to the agent, and lessons unused for 60 days are retired. All lessons are viewable and editable in Settings under Memory, stored locally per repository, and the author notes the feature is new with no data yet on its effectiveness.