Skip to Content
Personal Insights
Author's profile photo Madhu Gowda

Handling of Oil & Gas secondary costs through SAP Global Trade Management

Overview

This blog post provides a sneak peek into how SAP Global Trade Management – with a few key enhancements – can be used together with Trader’s and Scheduler’s Workbench to provide an alternative solution for handling secondary costs in SAP S/4HANA for Oil & Gas industry customers.

What is Secondary Cost?

Secondary cost in general refers to cost incurred in moving a product from one location to another. It is important to tag the cost to the movement for many different reasons. Some of the most common use cases are to calculate the profitability of a trade, provide transparency to the costs involved and blend the costs into the moving average / standard price of the product.

Relevance of Secondary Cost in Oil & Gas Industry.

With vessel Demurrage charges ranging from 50,000 to 80,000 USD per day depending on the size of the vessel, secondary costs garner considerable attention from the stake holders of Oil & Gas companies. The industry seeks a solution through which they can effectively manage these costs, reduce freight spend and evaluate risk. Also, it is very important to track the secondary cost to understand if a trade is profitable or not.

Why SAP Global Trade Management?

The Trader’s and Scheduler’s Workbench sub module within SAP’s IS-OIL solution is where schedulers, and movement capture analysts perform the planning, scheduling, and actualization of all planned Bulk movements. The scheduler creates a nomination to schedule a movement,  (Nomination is Planning and scheduling document). When a nomination is actualized, it produces a logistics document called Bulk Shipment (also known as Transportation and Distribution shipment) which is later used for creating a shipment cost document. The reason for using the bulk shipment cost document where possible is that it is fully integrated with SAP Trader’s and Scheduler’s Workbench and an out-of-the-box solution for many standard scenarios. However, there are a number of special business scenarios that the traditional shipment cost solution cannot fulfill.

Examples include:

  1. Rail freight may need to be paid to the transportation company as soon as the rail cars are loaded. Since there is just one bulk shipment for the whole movement, typically you will have to wait until the discharge is complete to create the shipment cost document.
  2. Most marine and rail movements have an inspection fee. This fee is paid to the inspector who  checks the volume and quality of the product loaded into the equipment resource. These fees are some times required to be paid as soon as the inspection is completed. However, they cannot be paid through the shipment cost document as the movement has not yet occurred.
  3. If there are multiple service vendors involved in a movement, there is no standard way to  determine these vendors and assign them to the bulk shipment as partners. Without Partners it is not possible to generate shipment cost document.
  4. Finally, the bulk shipment document and its corresponding shipment cost documents are being replaced in SAP S/4HANA by Transportation Management (TM) and its corresponding Freight Settlement Documents (FSD). However, there is currently no out-of-the-box integration between SAP Trader’s and Scheduler’s Workbench and SAP TM.

Integrated SAP Global Trade Management & SAP Trader’s and Scheduler’s Workbench Solution for Secondary Cost.

Conceptual Flow Chart & Design

SAP Global Trade Management / SAP Trader’s and Scheduler’s Workbench end to end process flow.

Solution Highlights

The key activities required to implement this solution are:

  1. To integrate the SAP Global Trade Management Trading contract with SAP Trader’s and Scheduler’s Workbench, a trading contract has to be created for every nomination document. Commodity pricing in the trading contract needs to be replaced with generic dollar value condition type.
  2. Determine the relevant secondary cost condition types for the nomination and capture them in a custom table. This provides the freight estimate to the scheduler, feeds the estimated secondary cost to the SAP Treasury and Risk Management module and captures them as planned expenses in the trading contract.
  3. When the actual movements happens the movement capture analyst creates and actualizes a ticket against the nomination line item, The actualization of ticket will result in posting the goods movement and the material document posted has to be captured in staging table.
  4. Finally, schedule a batch program to create accrual Vendor Billing Documents against the movement document, based upon the planned expenses stored in the trading contract for the corresponding nomination line item.

Note that the trading contract generated here is only used for creating expenses and not to execute the trade itself. A separate module, Deal Capture, captures the trade, and SAP Trader’s and Scheduler’s Workbench module is used executing the subsequent process.

Advantages of Integrated SAP Global Trade Management & SAP Trader’s and Scheduler’s Workbench Solution

The key value drivers of this solution vs. other potential solution alternatives for capturing secondary  costs include:

  1. Flexibility to create accrual Vendor Billing Documents (VBDs) at the nomination line item level, even before the movement documents are posted.
  2. Accrual Vendor Billing Document at the cost type level provides flexibility to reverse just the affected cost type.
  3. Accrual Vendor Billing Document can be created at any point in time once the nomination is created. They are not dependent on the status of the movement.
  4. Ability to post the secondary cost into the inventory account of the corresponding commodity  and plant.

 

Conclusion

If your SAP Trader’s and Scheduler’s Workbench implementation includes SAP Global Trade Management in the target architecture and you need to capture secondary cost for the SAP Trader’s and Scheduler’s Workbench movements or other non-standard business scenarios, SAP Global Trade Management provides an excellent foundation for providing this key capability.

Assigned tags

      4 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Swapnil Wavhal
      Swapnil Wavhal

      Hello Madhu,

      Thanks for the above article I have one below question can you let me know how we can solution this approach?

       

      As a contract administrator I need to be able to define secondary cost type/names and the calculation for all secondary costings as part of the final settlement value.  This setup/configuration would drive the automatic default of secondary costings allowing for less manual intervention.

      --

      Eg:

      • Agri. Company has a flat price purchase contract with Counterparty A for Northern Spring Wheat 12.5% protein
      • Inco terms is Ex-Works, MOT is Truck
      • Contract location is Tulare, SD
      • Based on the criteria above, the following secondary costs would automatically default:
      • Freight - $00.20 USD
      • Blending - $00.05 USD

       

      How can we do this defaulting of Condition types and a specific cost on a GTM contract based on a particular combination or criteria?

      Author's profile photo Madhu Gowda
      Madhu Gowda
      Blog Post Author

      Hi Swapnil,

      Apologies for getting back late, Am very busy with my current project and I was unable take any time out sooner. Your question is more consulting related, However I have attempted to provide some pointers based on my experience. Hope this helps.

      If I understand correctly your question is related to automation of condition record determination on the trading contract. I Am for the moment assuming that you are not using TSW and just dealing with GTM, Based on this assumption I have put down my thoughts below, Please discuss with your local GTM consultant on how this can be implemented.

      1. Setup MM condition records for Freight and Blending fee based on Plant and material key combination.
      2. Include the above condition types in your commodity pricing procedures which gets determined at the time of creating the purchase contract. You can make them statistical if you do not want to include these charges in the commodity invoice.
      3. You will have to then implement a BADI or have some sort of custom development to read the freight and blending fee determined on the pricing procedure and then create the condition record associated with the expense class.
      4. The condition type you create for Freight and blending would each be associated with an expense class and condition type group, and each condition type group is associated with a condition table.
      5. Your custom development or BADI implementation should aim at creating the condition record under this condition table.
      6. Once the condition records are created under this condition table, the expenses would then automatically appear in the trading contract. These expense would then facilitate creation of VBDs.

      Thanks

      Madhu.

      Author's profile photo Swapnil Wavhal
      Swapnil Wavhal

      Thanks Madhu, we are already thought of this above condition tech. approach also we are going to use TSW integration in our project. As expense being a new area for me, so I am here to ask for a better approach for same 🙂

      The reason for asking is as TSW location would come in picture you will have a market and a port zone differentiation and based on those combinations we have to identify expense conditions and appropriate prices for same.

      Regards,

      Swapnil Wavhal

      Author's profile photo Madhu Gowda
      Madhu Gowda
      Blog Post Author

      Then this requirement will partly fit into the design methodology explained in my blog, where in you will be creating a separate custom tab under TSW nomination item screen to determine those secondary cost relevant condition records. The rest of the process would remain the same.