Tenneco SD BBP v1.1

SALES & DISTRIBUTION BUSINESS BLUEPRINT
Submitted to
TENNECO
By
WIPRO LIMITED VERSION 1.0
Business Blueprint Sales & Distribution
DOCUMENT APPROVAL
Abhaya Shankar Executive Sponsor P.S.Narayan Business Manager Anish Kumar Wipro Technical Manager Srinivas M Tenneco Project Manager Vijayamadhavan Wipro Project Manager Michael Joseph MJP Wipro Consultant Selvam Tenneco Core Team Member
Date
Date
Date
Date
Date
Date
Date
Wipro Ltd.
Page 2 of 44
Wipro Limited, 2007, All Rights Reserved. This document is proprietary to Wipro Infotech, a division of Wipro Limited. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute any material from this document, in any form or by any means, nor may you modify or create derivative works based on the text of any file, or any part thereof for public, private or commercial use, without prior written permission from Wipro Limited.
DOCUMENT INFORMATION
Project Name Go Everest Document Name SD Business Blueprint V1.0 Document Location Z:\03- DESIGN DEVELOP & TEST\BUSINESS BLUEPRINT\SD
DOCUMENT HISTORY
Version 1.0 1.1 Document Name SD Business Blueprint SD Business Blueprint Date
05.10.2007 09.10.2007
Author Michael Joseph Michael Joseph
Reviewed BY
Change Control Draft DraftDraft
TABLE OF CONTENTS
Wipro Ltd.
Page 3 of 44
1 EXECUTIVE SUMMARY......................................................................6 1.1 BACKGROUND ...............................................................................6 2 THE PROJECT SCOPE .......................................................................6 2.1 Geographic and Organizational Scope:...............................................6 2.2 Functional Scope:...........................................................................7 2.3 Technical Scope............................................................................8 2.4 BUSINESS BLUEPRINT OVERVIEW..................................................10 2.5 SALES & DISTRIBUTION.................................................................11 2.6 IMPLEMENTATION SCOPE...............................................................11
6.1.1 Oraganization Structure.........................................................................11 1.4.2 Business process scope ......................................................................12 1.4.3 Standard sales processing in sap.........................................................12 7.1.1 MM - Materials Management...................................................................16 1.5.2 FI - Financials ......................................................................................16 1.5.3 PP - Production Planning........................................................................16
2.7
MODULE INTEGRATION..................................................................16
2 ORGANISATION STRUCTURE..........................................................17 2.1 ORGANISATION ELEMENTS...........................................................17

2.1.1 Company Code..................................................................................17 2.1.2 Credit Control Area............................................................................17 2.1.3 Sales Organization ............................................................................18 2.1.4 Distribution Channel .........................................................................19 2.1.5 Division ...........................................................................................19 2.1.6 Sales Area .........................................................................................20 2.1.8 Plant ..............................................................................................20 2.1.9 Storage Location ................................................................................21 2.1.10 Shipping Point ................................................................................22 2.1.10 Transportation Planning Point ..........................................................22
2.2 OVERALL ORGANISATION STRUCTURE ........................................22 3 MASTER DATA................................................................................23 3.1 CUSTOMER MASTER ..................................................................24
3.1.1 Customer Account Groups ................................................................25 3.1.2 General Data .....................................................................................26 3.1.3 Company Code Data .........................................................................26 3.1.4 Sales and Distribution Data................................................................26 3.2.1 General Data .....................................................................................27 3.2.2 Sales and Distribution Data ................................................................27
3.2
MATERIAL MASTER ....................................................................26
3.3 PRICING MASTER........................................................................28 3.4 CLASSIFICATIONS FOR SALES MASTERS .....................................32 ..................................................................................................32
3.4.1 Customer Group...................................................................................32 3.6.1 Terms of Payment..............................................................................32 3.6.2 Incoterms..........................................................................................32 3.6.3 Shipping Conditions............................................................................33 3.6.5 Account Assignment............................................................................33
4 BUSINESS PROCESSES...................................................................33
Wipro Ltd. Page 4 of 44

4.1 Sales Contract Handling ..............................................................33
4.3
A quantity contract is an agreement to supply a fixed quantity over a period of time. Since the customer promises to buy the fixed quantity of goods/services, they will get a discounted price..............................................................................34 When Quantity is Limited - When the production quantities are limited in numbers, then customers are allocated a specific quantity by time -period ( say a month, or a quarter ) . And customers cannot place ad-hoc orders, but have to first sign a contract for a fixed quantity and always order via release orders that specifically refer to the contract. ....................................................................................34 When Vendors want to Lock-in Customer quantities - Some times to give deep discounts, sales folks require that customers commit to buying a fixed quantity over a time-period. This satisfies the sales figures ...................................................34 4.1.2 Master Data.......................................................................................34 4.1.3 Features for SASREF..........................................................................34 4.1.4 Business Process...............................................................................35
Sales Order...............................................................................35
4.5
4.3.1 Purpose..............................................................................................35 4.3. 2 Master Data......................................................................................35 4.3.3 Features for SASREF...........................................................................36 4.5.1 4.5.2 4.5.3 4.5.4 Purpose.............................................................................................37 Master Data.......................................................................................37 Features for SASREF...........................................................................37 Business Process.................................................................................37 Billing Process ...................................................................................38 Purpose.............................................................................................38 Master Data.......................................................................................38 Features for SASREF...........................................................................38
Delivery...................................................................................36
4.7
5 SASREF SALES SCENARIOS............................................................39
4.8.1 4.8.2 4.8.3 4.8.4
Billing ......................................................................................38
STANDARD INFORMATION SYSTEM............................................42 5.1 Purpose......................................................................................42 5.2 Features.....................................................................................42

5.3 Standard analyses..............................................................................43
5.1.1 Sales of Sulphur /LPG to Saudi Aramco via pipeline ................................39 5.1.1 Sales of Kerosene to Farabi / Wash Oil to Petrokemya / Benzene and Wash Oil to SADAF ................................................................................................40 5.1.1 Sales of Finished Product to Saudi Aramco Trading and Shell Trading via Ship 41
7 SD: LAYOUTS AND REPORTS........................................................44
Wipro Ltd.
Page 5 of 44
1
1.1
EXECUTIVE SUMMARY
BACKGROUND
Brief Description about the company SASREF is a joint venture between Saudi Aramco and Shell Refinery Company. It is located at the very heart of Saudi Arabias petrochemical-industry; Jubail Industrial City and is acknowledged as an industry pacesetter and was specifically designed as an export refinery. SASREF is now looking at implementing SAP solution for addressing their Hydrocarbon Supply Chan and Oil Accounting. As part of this process SASREF had evaluated the Shell Global SAP system and its fitment to their needs. The Shell GSAP template will be the base for the implementation, However the country / SASREF specific processes needs to be built on that and as well as leverage the standard SAP IS-Oil functionality. The HCM system has to be integrated with the existing SAP modules. Integration with external application for Daily Price Quotes, LIMS, EDI for invoicing and Operation Data System needs to be established, using SAP PI (XI) as the middleware. In essence SASREF is looking at one integrated ERP platform addressing the Operational, Planning, Supply Chain and Oil Accounting needs. SASREF runs on mySAP ERP ECC 6.0.
2 THE PROJECT SCOPE

Project scope is divided into three categories
Geographic and Organizational Scope: defined by the locations within SASREF into which it is planned to implement IS Oil Hydro Carbon Management Project.. Functional Scope: defined by the business functions proposed for implementation. Technical Scope: defined by the technical requirement proposed for implementation.
2.1
Geographic and Organizational Scope:
The scope of this project is limited to the implementation of the functionality of SAP ECC 6 IS Oil Hydrocarbon Management.
Wipro Ltd.
Page 6 of 44

Wipro consultants will be based out of Kochi Development Center for Project Preparation and Business Blue Print Phase. Later, the implementation team shall work from SASREF project office located at Jubail Saudi Arabia. The implementation will span only the following Legal Entities: Saudi Aramco Shell Refinery plant located at Jubail - Saudi Araiba ( SASREF) The SAP solution Implementation services at SASREF will include the following services from Wipro:
Refining and defining the to-be processes in line with GSAP template. Implement ERP ECC 6.0 with IS Oil for modules described in functional scope. Training on ECC 6.0 Senior Management & Core Users. Active Assistance in Organization Change Management Strategy implementation Assistance in Upload/Migration of data from current legacy to ERP system Basis Support during the engagement i.e. Installation of Server, Assistance in User Authorization etc. Develop Objects in ECC 6.0 to meet the New Functional Requirements to an extent of 99 FRICE Objects. 99 FRICE object shall include reports as detailed below
Business Process Area Product Delivery Oil Accounting Master Data Reports Detailed list of development object enclosed
Report Reference PD_R010 to PD_R250 OA_R010 to OA_R270
No. of Reports 25 27 14 Query based reports

SASREF report list.xlsx
Please note Data upload programs are not part of FRICE objects There shall be a Post-implementation support for a period of Three Month.
2.2
Functional Scope:
The following ERP ECC 6.0 modules will be implemented as part of this engagement: The scope of SASREF SAP IS-Oil Implementation project is mainly to provide an integrated and comprehensive solution for SASREF company to operate and support its main business functions in ERP including all supporting modules Materials Management

Quality Management To explore during project preparation phase and during blue print phase Sales & Distribution IS-Oil downstream Finance and Controlling Production Planning The main SASREF functions covered within the ERP scope are organized as scenarios:
1. Procurement and Inventory (MM):

IS Oil specific extensions and related functionalities to integrate with existing systems. Material Masters for Finished Products and feedstock and related functionalities to integrate with existing systems. Real time inventory maintenance.
2. Production Planning (PP-PI): Includes refined products, managing raw and feedstock
procurement, inventory management of the final products, production of the final finished products.
3. Sales and Distribution (SD, TSW & Exchanges): Covers execution of the nominations, lifting
amendments, production stock projection, berthing, vessels events management, and lay-time & demurrage. SAP IS-Oil solution will be applied for refined products. All the sales process such as order processing, credit management, billing using formula pricing and price quotes etc. will be covered by standard SAP. The Oil pricing will be based on SAP IS-Oil specific Marketing, Accounting & Pricing (MAP) module.
4. Quality Management (QM): Quality management covers quality inspection, quality checks, quality
assurance and sampling of products. QM will be used for receiving, in-process inspection, sampling and for shipments processes etc. In SASREF since Lab Ware (LIMS package) is being used the role of QM module will be limited. SAP will be interfaced with LIMS.
5. Finance: Covers Financial and Management Accounting processes comprising of Cash

Management and Liquidity forecast, Accounts Receivables, integration with Materials Management Module and Sales and Distribution Module etc., General Ledger and other related masters will be modified to the extent to suit current implementation.
6. Controlling: Covers product costing for refined products and profitability Analysis. Cost Centers
and related master data would be modified to the extent to suit the current implementation.
2.3
Hardware
Technical Scope
Wipro Ltd.
Page 8 of 44

Existing ECC 6.0 hardware is adequate for current implementation. However Wipro shall analysis and share their findings during the initial phase of the project to enable SASREF to make further investment on need basis Technical support Ten (10) Forms related to this implementation. Custom Reports as stated in the below table Report Reference PD_R010 to PD_R250 OA_R010 to OA_R270 No. of Reports 25 27 14 Query based reports
Business Process Area Product Delivery Oil Accounting Master Data Reports
Fifteen (15) custom developed programs which includes enhancements to standard SAP, development of module pool programs and custom workflows. 7. Conversion: Scope of work includes Upload of finished stock and other material relevant to this implementation. Quality module related data such as inspection characteristics and related data.
Technical Assumptions: A. Wipro will do Interface work related to SAP only. Any third party related work needs to be done by SASREF Interfaces: The following interfaces (are in scope) to be configured / developed ODS Both inbound and outbound interfaces limited to handling of production declarations of finished products, terminal ticket quantities, and receipt of feedstock in SAP through SAP XI. LIMS Both inbound and outbound interfaces for material inspection. Standard SAP QMIDI would be enabled for this implementation. PRICE Quotes: Interface with service provider for getting daily quotes for refined finished products and freight quotes through SAP XI. Standard SAP provided QCI interfaces would be enabled to perform quantity conversions required for this implementation. Note on XI
Wipro Ltd.
Page 9 of 44

ERP ECC 6.0 Functional Module XI Sub-Module Integration to ECC 6.0.
XI component shall be used to integrate SAP Instance and other Non SAP developments, Going forward SOA enabled architecture gives us the required flexibility in scaling and integrating any platform that can come into our landscape with relative ease.
2.4
BUSINESS BLUEPRINT OVERVIEW
This document summarizes the findings of the Wipro consulting team and SASREF Core team / Shell GSAP Team with respects to SAP processes to be implemented in SASREF. Following activities were carried out during different phases of the project. Knowledge Transfer To understand SASREF processes Current State of Business Process Understand SASREF Business Process FSBP-Future State Business Process Mapping GAP Analysis
The information was gathered through above activities carried out during different phases of projects i.e. reviews of business processes, business procedures, template documentation and relevant reports The purpose of Business Blueprint document is to prepare to move forward with the implementation of SASREF SAP R/3 system. At the conclusion of the blueprint, the Wipro consultants will determine the SAP functionality required to run SASREF business successfully in SAP R/3 The Blueprint and its associated appendices present a summarized perspective of all functional business processes that will be implemented. As such, the Blueprint document will serve - from this point forward the dual role of both official project scope as well as system acceptance criteria. The contents of this document describes the
1. Sales and Distribution Organizational structure 2. Master Data and 3. R/3 functional process flows to be implemented in SASREF.
Wipro Ltd.
Page 10 of 44

Requirements that can be met using standard R/3 functionality through routine configuration tasks are not explicitly documented. However, certain key requirements are explicitly identified and summarized to highlight their importance to SASREF and to document the approach proposed to meet the requirement. One section of the document summarizes identified gaps between requirement and availability.
2.5 SALES & DISTRIBUTION

The Sales and Distribution module in SAP contains all of the software functionality included in managing pre-sales activities, receiving & managing sales orders, and schedules, delivering products to customers, handling transportation and billing customers for products sold. A major focus for SASREF implementation will be to successfully match SASREF business requirements with the Sales and Distribution Module in SAP R/3. This section provides an overview of Wipro understands of the various Order Fulfillment, Customer Management, and Sales processes followed at SASREF vis-vis SAP functionality. These have been arrived at after close interaction with core teams & process owners by conducting business process understanding workshops and study of existing information systems. The activity resulted in the formulation of Current State Business Process (CSBP), which in turn formed the basis for arriving at Future State Business Process (FSBP). These would form basis of configuring the final system. The following gives an overview and scope of business processes to be covered in SAP.
2.6 IMPLEMENTATION SCOPE

6.1.1 ORAGANIZATION STRUCTURE
Organizational units in Sales and Distribution are: Company Code: Its a legal entity and independent accounting unit in SAP. The balance sheets required by law and profit and loss statement are carried out at company code level.
Wipro Ltd.
Page 11 of 44
Sales Organization: It is an organizational unit in logistics which groups the enterprise according to the requirements of sales and distribution. Sales Organization responsible for product revenue and liability; therefore it is liable for the sold products and responsible for customers rights of recourse. Distribution channel: It is a means through which saleable materials or services reach the customers. It represents strategies to distribute goods and/or services to customers. Division: It represents a product line. A division is used to group materials and services. Sales Area: A sales area is a combination of Sales Organization, distribution channel and division. It defines the distribution channel a sales organization uses to sell products from a certain division.
1.4.2
BUSINESS PROCESS SCOPE
Master Data Customer Material Condition Output Order Fulfillment Sales Contract Sales Order Logistics Execution Outbound Delivery Post Goods Issue Billing Billing Document Output Pricing
1.4.3
STANDARD SALES PROCESSING IN SAP
The SD module allows executing different business transactions based on sales documents defined in the system During sales order processing, the system carries out basic functions such as: Monitoring sales transactions Checking for availability
Page 12 of 44
Wipro Ltd.

Delivery scheduling Calculating pricing
Depending on how the system is configured, these functions may be completely automated or may also require some manual processing. There is a document flow function in the system. The document flow shows the entire chain of documents inquiry, quotation, sales order, delivery, invoice and accounting document. It is nothing but the flow of data from one document to another document. When a sales document is created, the system proposes much of the data from master records, preceding documents and automatically determined by the system. The following graphic shows how the various types of sales documents are interrelated and how data subsequently flows into shipping and billing documents.
PP
2.6.1.1 MASTER DATA It comprises Material, customer, condition and other master data. The master Data in an integrated SAP environment is used by all components in the SAP Logistics System. The integration of all master data in a single database object eliminates redundant data storage.
Wipro Ltd.
Page 13 of 44

1.4.2.1 PRICING The term pricing is used broadly to describe the calculation of prices (for external use by customers) and costs (for internal purposes, such as cost accounting). Conditions represent a set of circumstances that apply when a price is calculated. For example, a particular customer orders a certain quantity of a particular product on a certain day. The variable factors here - the customer, the product, the order quantity, and the date - determine the final price the customer gets. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records. 2.6.1.2 SALES CONTRACTS HANDLING Contract is an outline sales agreement that contains special conditions negotiated between the vendor and a customer, for example, price, target value or target quantity. A sales contract is valid for a specified period. A customer submits a sales order to release products from the amount agreed in the contract. Types of sales contract include value contracts and quantity contracts.
2.6.1.3
ORDER FULLFILMENT
This covers the process of Order, and Outline Agreements Entry that contain committed quantities at special prices and payment terms and customermaterial information for certain customers with the standard functions such as the following Pricing defined for various customer/material, material pricing group conditions.
Delivery Scheduling to determine the time material is available in the warehouse and ready for further processing Shipping point determination (from where the goods dispatched)
The pricing conditions are dependent on characteristic values and maintained centrally as master data.
Wipro Ltd.
Page 14 of 44
2.6.1.4
DELIVERY PROCESSING
This covers the functions of dispatch of goods at the finished goods plants and depots involving Creation and processing of Outbound Deliveries Picking Processing Goods Issue Controlling using overviews of deliveries currently in process, activities that are still to be carried out. 2.6.1.5 BILLING
The covers the functions of: Creation of Invoices based on deliveries Issue credit and debit memos Pro forma invoices Transfer billing data to Financial Accounting (FI) 1.4.4 GENERAL SETTINGS
2.6.1.6
The General settings in SAP consist of the following: 2.6.1.7 COUNTRY The country specific checks such as date format, decimal format, bank data, postal data and control data needs to be maintained for a country. All the country codes are already defined in SAP. At SASREF: Enter the required date format, the decimal format, bank data, postal data and control data in the country for KSA.
2.6.1.8
UNIT OF MEASURE (UOM)
This is the unit in which material is purchased, stocked, sold and moved. SAP has standard unit of measures already defined. At SASREF: The UOM such as Each, Piece, Barrel and MT will be defined in SAP.
Wipro Ltd.
Page 15 of 44
2.7
MODULE INTEGRATION
Master and transaction data in Sales and Distribution are closely integrated with other modules within Logistics and Finance. Business Transactions handled as part of SD module have tight linkages with other modules especially in Finance and Production Planning. The integration touch points of the Sales and Distribution with various modules are detailed below.
7.1.1
MM - Materials Management
Assignment of organizational elements like distribution chain (sales organization / distribution channel) to plants. These allow customers to be serviced from desired plants for a particular sales organization, through the distribution channel. Definition of Material Types and Material Master records for finished and other products. Stock Transport Order Processing for transfer of goods between plants. Inventory management part of Materials management is completely integrated in the entire logistics system. For example, on entering a sales order, a dynamic availability check can be initiated of stocks on hand. When the delivery is created, the quantity to be delivered is marked as "Scheduled for delivery". It is deducted from the total stock when the goods issue is posted. Customer master is maintained for the Logistic service provider. 1.5.2 FI - Financials
Creating linkages between Sales organization, highest entity in sales and company code in Finance. Customer payment processing including advances payments. Billing and posting the data to accounting Debit/Credit note creation for returns processing and wrong shipments etc., 1.5.3 PP - Production Planning
The production-planning module serves as an important link between sales and production. This allows the customer requirements to be translated into production planning parameters using the functionality availability check. The requirements are determined from customer requirements, which are represented by sales orders in the system; the result of demand management is been Manually given by the Marketing Department
ORGANISATION STRUCTURE
2.1 ORGANISATION ELEMENTS
The first steps in the implementation of the SAP System involve mapping the enterprise structure of SASREF. Onto the organizational units of R/3. This structure mapping must ensure that There is transparency at Operational level All business processes can run smoothly, using resources as efficiently as possible The requirements for internal and external reporting are met Segregation of various functions as Logistics / Marketing / Sales There is flexibility to add new entities to meet future growth
2.1.1 Company Code

The company code is the smallest organizational unit of Financial Accounting for which a complete self-contained set of accounts can be drawn up for purposes of external reporting. The process of external reporting involves recording all relevant transactions and generating all supporting documents required for financial statements such as balance sheets and profit and loss statements. At SASREF: One company code has been defined under FI module.
2.1.2 Credit Control Area

Credit control area is an organizational unit that represents an area responsible for granting and monitoring credit of customers. It specifies and checks a credit limit for customers. This organizational unit is either a single company code or, if credit control is performed across several company codes, multiple company codes. Credit information can be made available per customer within a credit control area. A credit control area can include one or more company codes. It is not possible to assign a company code to more than one credit control area. Within a credit control area, the credit limits for customers must be specified in the same currency.
Wipro Ltd.
Page 17 of 44
At SASREF: There will be one credit control area; the same would be a part of FI module.
2.1.3 Sales Organization

A Sales Organization is an organizational unit within Logistics that structures the company according to its sales requirements. A sales organization is responsible for selling materials and services. A sales organization has the following attributes: Legally, a sales organization is included in exactly one company code. One or more plants can be assigned to one sales organization. A sales organization can have its own customer and material master data as well as its own conditions and pricing. Sales employees can be assigned to a sales organization. All items in a sales & distribution document (sales order, delivery or a billing document) belong to a sales organization. A sales organization is the highest summation level for sales statistics with its own statistics currency. The sales organization is used as a selection criterion for the lists of sales documents, delivery and billing due list and standard reports. A sales organization cannot share any master data with other sales organizations. The master data must be created separately, by extending the customer to one sales organization to the other. The data for a distribution channel or a division can however be created for several distribution channels or divisions. SR01 sales organizations
At SASREF: SR01 Company Code will have responsible for all sales activities for finished goods
Sales Organization
SR01
Sales Organization Description SASREF Sales Organization
Location Jubail
Wipro Ltd.
Page 18 of 44
2.1.4
Distribution Channel
A distribution channel is the channel through which saleable materials or services reach customers. It includes Global Supply. A distribution channel has the following attributes: Can allocate distribution channel to one or more sales organizations. Can define own master data for customers or materials as well as conditions and pricing within a distribution channel. The distribution channel can be used as a selection criterion in lists and standard reports. Can define common distribution channels for master data such as customers, materials and conditions.
At SASREF: Sales Organizations would share one distribution channels. SASREF will have only one distribution channels Global Supply, representing the channel through which goods are sold to customers. Distribution Channel
06
Description Global Supply
2.1.5 Division
An organizational unit based on responsibility for sales or profits from saleable materials or services. It basically represents various product lines. Material division would be identified clearly at the time of defining material master records for finished products. A division has the following attributes: Allocate a division to one or more sales organizations. Allocate a division to one or more distribution channels. A material is always assigned to one division only. Can define own master data within a division for customers as well as conditions and pricing. Can define common divisions for master data such as customers and conditions. The division is used as a selection criterion for lists and standard reports.
At SASREF: One division has been identified, representing the SASREF products.
Wipro Ltd.
Page 19 of 44
Division
02
Description Fuel
2.1.6 Sales Area

Sales area is defined as a unique combination of sales organization/distribution channel/division for which all transactions are entered in SAP. All such valid combinations will be used as sales areas. A sales area can be used as a selection criterion for lists and standard reports. AT SASREF: There would be separate and unique sales area in SASREF The following Sales Area is identified .
Sales Organization Distribution Channel Division SR01 06 02
Sales Area SR01-06-02
2.1.8
Plant
A plant is an organizational unit within Logistics, serving to subdivide an enterprise according to production, procurement, maintenance, and materials planning. A plant is a part of SASREF where either material is produced, or goods and services are provided. The plant is an operating area or branch within a company. The plant is embedded in the organizational structure as follows: The plant is assigned to a single company code. A company code can have several plants. Several storage locations in which material stocks are managed can belong to a plant. A plant can be assigned to several combinations of sales organization and distribution channel.
Page 20 of 44
Wipro Ltd.

A plant can have several shipping points. A shipping point can be assigned to several plants. A plant has its own material master data.
The plant plays an important role in the following areas: Material valuation: When the valuation level is plant, the material prices are defined for each plant. Each plant can have its own account determination. Inventory Management: The material stocks are managed within a plant. MRP: Material requirements are planned for each plant. Each plant has its own MRP data. Analysis for materials planning can be made across plants. Production Costing: In costing, valuation prices are defined only within a plant.
At SASREF: Plant definition would be a part of MM Module, Under company code 1000 . Material valuation will be at plant level. These will be assigned to company code 1000 Plant will be assigned to Sales Organization and Distribution combination for carrying out sales activity from that location. Company code :- SR01
Plant 1000 Plant description
Channel
Renowned Auto Products Mfrs Ltd
Location Jubail
2.1.9 Storage Location

Storage location in SAP allows differentiation between various stocks of materials in a plant. These are the smallest unit in an organization hierarchy. These storage locations can also correspond to physical storage points within Tenneco. A storage location has the following attributes: There may be one or more storage locations within a plant. It is possible to store material data specific to a storage location. Stocks are managed only on a quantity basis and not on a value basis at storage location level. Physical inventory is carried out at storage location level. Storage locations are always created for a plant.
They are assigned to plants and are relevant for sales functions. At Tenneco: Storage Location definition would be a part of MM Module.
2.1.10
Shipping Point
The shipping point is an organizational unit in Logistics that carries out shipping processing. The shipping point is the part of the company responsible for the type of shipping, the necessary shipping materials and the means of transport. The shipping point has the following attributes: A shipping point can be allocated to several plants. A delivery is always initiated from exactly one shipping point. The shipping point is used as a selection criterion for lists of deliveries, the work list deliveries, picking and goods issue.
At SASREF: Shipping Point is assigned to Plants

Shipping Point in Plant 1000
Shipping Points 1000
Shipping Points description
Location Jubail
2.1.10
Transportation Planning Point
A Transportation Planning Point Represents a group of people responsible for handling transportation activities such as organizing shipments , such as Ship, Truck, Pipe line etc..A Company code is assigned to every transportation Planning point . Transportation Planning Point is mandatory input when creating shipments. Every shipment has exactly one transportation Planning Point. Transportation Planning Point can be assigned to Company code. Transportation Planning point is independent of other organization units.
At SASREF: One Transportation Point is assigned to Company Code

Shipping Point in Plant 1000
Transportation Planning Points 1000
Description
Location Jubail
2.2
OVERALL ORGANISATION STRUCTURE
The overall organization structure can be summarized in the figure below. The various organizational elements are described with the code to be used in configuration
Wipro Ltd.
Page 22 of 44
SASREF will have One Sales Organisations We will have One Distribution Channel For Global Supply and a Division for Fuels
MASTER DATA
In sales and distribution, products are sold or sent to business partners or services are performed for them. Data about the products and services as well as about the business partners is the basis for sales processing. Sales processing with the SAP R/3 System require that the master data has been stored in the system. In addition to sales and distribution, other departments of the company such as accounting or materials management access the master data. The material
Wipro Ltd.
Page 23 of 44

master data is stored in a specific structure in order to allow access from these different views. The processing of business transactions in sales and distribution is based on the master data. In the SAP R/3 System, business transactions are stored in the form of documents. These sales and distribution documents are structured according to certain criteria so that all necessary information in the document is stored in a systematic way. Master data is maintained for customer, Customer , Pricing and finished goods. This is created and maintained by responsible personnel in relevant sales function.
3.1
CUSTOMER MASTER
Customers are business partners whom the organization does sales related transactions. It is the central unit in the overall order fulfillment cycle and can denote internal users, external customers or direct end consumers. It is advisable to maintain data centrally in order to avoid duplicates and exercise effective control over master records. The various data elements for customer master records pertain to general information like name, address, contact persons; accounting information pertaining payment terms, shipping terms, G/L reconciliation account, customer classification towards tax determination and relevant partner functions for the same. Business related information on customer master is stored in the following structure as a part of customer master and depicted below. In Tenneco: Internal numbering is used in line with European System. Since we will work in the same client environment as the Walker implementations and since some customers are common we will have to keep the existing set-up as much as possible. Typical Tenneco business includes that the ordering party can be different from the delivering address and from the invoiced company. A ship-to address can have different unloading points.
Logistics Basic Data: Business Partners Here Parameters are set for business transactions to be done in Sales & Distribution Module.
Wipro Ltd.
Page 24 of 44

3.1.1 Customer Account Groups
Customer records are created for specific account groups (Sold to party, Goods Recipient, Payer and Bill to Party). These groups control: Required fields for entering master data. Number Range assignment, internal or external for master records Valid partner functions Customer Information required to process Customer related transactions is maintained. Control The following aspects form the basis of master data management for Customers (creditors): definition of account groups definition of number ranges for Customer master records definition of match codes for Customer master records Define account groups and field selection Account groups are defined for Customers in order to group together Customers of similar type. It is also used to define the following: Field statuses for Customer master records. Whether the account is a one-time account.
Slno 1 2 3 4 0001 0002 0003 0003
Acct Group
Description Sold to party Ship to Party Payer Bill to party
Type of Number range Internal Number Range Internal Number Range Internal Number Range Internal Number Range
Number Range The existing Account group will be used with same number Ranges In the standard R/3 System, the account groups for the following customer partner functions are in the same number range so the numbers for these customer master records are assigned consecutively:
Sold-to party
Wipro Ltd.
Page 25 of 44

Ship-to party Bill-to party Payer
Define number ranges for Customer master records
In this step, type of number assignment and the number range intervals for Customer master records are defined. When creating a Customer master record a unique number is assigned. This can be defined to be internal number assignment or external number assignment. No range assignment 3.1.2 General Data Defined at the client level and independent of any financial or sales functions; it includes company name, address, telephone number ,Email, region, unloading point etc. 3.1.3 Company Code Data
Data relevant to one company code and includes account management data and insurance data. The Reconciliation Account is being assigned at the Company Code data Level.
3.1.4
Sales and Distribution Data
This data is defined for a specific sales area, combination of sales organization, distribution channel and division. It includes shipping terms, pricing data, shipping conditions, delivery priority and partner functions relevant for shipping and billing. In SASREF: we will have all the data in line with GSAP like sales data, Shipping , Payment terms and Billing Reconciliation account with respect to Customer to be assigned to Sold-To-Party. Since only one account group will be there, reconciliation account involved also will be one.
3.2 MATERIAL MASTER
Wipro Ltd.
Page 26 of 44

Different company areas and SAP modules access the material master records, which therefore must meet a wide variety of requirements. During sales processing, the system repeatedly accesses the material master records. It is one of the basic sources of data for sales processing. Data in the material master record is of great importance for shipping and billing. However, the data required for shipping, for example, is not the same as that required for sales or billing. Material master records form the basic source of data for sales processing. The information relevant to general data, sales, plant, planning and storage related is maintained through views in the material master. This data is used during order entry, shipping and billing processes. The sales and distribution data for a material is managed at the organizational levels client, plant, sales organization and distribution channel. Therefore, the plant, the sales organization and the distribution channel have to be entered for which a material master record needs to be changed. All data and information entered for a material is stored in the data structure of the material master record. For sales and distribution, general data and sales and distribution data in the material master record are relevant.
3.2.1 General Data

General data in a material master record is identical for every sales organization, plant and storage location. General data, which is of importance for all departments, is always entered by the department, which creates the first part or view of the master record. General data contains, for example, the material number that identifies it, the material description, and units of measure, value, weight, volume and division.
3.2.2 Sales and Distribution Data

Sales and distribution data in a material master record is defined for a specific sales organization and distribution channel. The delivering plant, the assignment to the sales group, grouping terms for price agreements and sales texts, for example, are included in sales and distribution data. The fact that a material is linked to a distribution channel allows the material to be sold with different conditions through the various distribution channels. In SASREF: Sales and distribution data is divided into data that depends on the sales organization and data that depends on the plant: Sales organization/distribution channel data
Wipro Ltd.
Page 27 of 44

This data includes the delivering plant, the sales unit, the minimum order quantity and the minimum delivery quantity. Plant data This data applies to a plant and all its storage locations. Examples of plant data are safety stock quantity, the reorder level, or the shipping processing time.
3.3 PRICING MASTER

The term pricing is used broadly to describe the calculation of prices (for external use by customers or Customers) and costs (for internal purposes, such as cost accounting). Conditions represent a set of circumstances that apply when a price is calculated. For example, a particular customer orders a certain quantity of a particular product on a certain day. The variable factors here - the customer, the product, the order quantity, and the date determine the final price the customer gets. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records. The standard R/3 System includes predefined elements for routine pricing activities. For example, the standard system includes condition types for basic pricing elements, such as material prices, customer and material discounts, and surcharges such as freight and sales taxes. During pricing, the system calculates amounts based on a combination of automatic procedures and manually entered data. The system automatically transfers pricing data - for example, information about prices, surcharges, and discounts - from the condition records into sales and billing documents. Depending on the pricing policies, one can change prices manually during sales order processing. Pricing data will be maintained using condition records. These will be administered centrally and controlled by centrally. The following indicative price components would be setup using condition technique Condition records for base price can be maintained with various combinations such as Customer/Material., Various trade discounts and Premiums based on various factors. Freight, Handling fee, additional premium etc can be mapped in the system.
At SASREF: Depending on the requirement, different condition records will be maintained for different condition types such as, Basic price, Premium discounts

,Handling charges, Processing fee, freight, etc. Pricing Procedure Will be followed in line with GSAP process . SAP IS Oil pricing supports the Formula based pricing. While creating the Contracts system can pick the market prices from the quotations to calculate the final pricing Sales Pricing, Formula and Average Pricing engine of IS-Oil ( Industrial Specific OIL ) MAP is proposed to be used for real time pricing functionalities of F & A Pricing proposed to be used as follows . External Quotation Masters Maintenance: Quotation Master Maintenance would contain the following fields like Quotation source, Name, Pricing unit and absolute unit of measure like USD per 1 bbl. And the data for these fields would be fetching from OTIS daily basis. Formula ID: Formula ID will be created and stored in formula repository. The formulas will be created based on various options like Customer, Customer/Material, Customer/Material/Plant, Plant/Material level. Each formula ID will have the external quotations with pre-defined surcharges or premium. Following rules will be available in the formula : Base line date: Base line date is the date of applicability of pricing like pricing date, planned delivery date, goods issue date. It is proposed to use Goods Issue date as the base line date for sales. In Purchasing it is based on bill of lading date. Base Line Date Offset: Various offset rules are available in standard SAP like 1st day of the current month, 1st day of the week, Last day of the last month etc are available which can be used for negotiation with customers. The base line date will be shifted based on the offset rules eg. if a customer invoicing is based on MOPS average of previous month, then the offset rule applicable will be beginning of previous month. Time Unit of Measure Rules: Period of averaging rules like daily, weekly, fortnightly and monthly are available. It is proposed to use daily except for LPG where external quotations are available on monthly basis. Before and After Time units: The number of days/weeks/months before and after the base line date will be entered. In Exports Time units before and after will be used (eg. 2 days before and 2 days after B/L date including supply date) while for other business time units before is proposed. Week end Rule: Standard international rule and in line with best practice Sat-Fri / SunMon will be used. In trading for exports standard week end rule is used. No external quotation posting: In case external quotation is not available on a day standard rules available are to use last working day, previous day. It is proposed to use previous day functionality since working day may vary depending on customer specific holiday calendar. Currency Averaging: For billing in USD the currency conversion rules like Daily Currency rule or Period Average Currency rules are available. It is proposed to use daily currency conversion rule for billing in USD. Currency rates will be accessed from the data available in Treasury. Currency fluctuations within the time period are taken into account. Provisional and Final Invoicing: The provisional invoice will be issued based on price available at the time of goods issue date. The final invoice will be used once final price is available. The final invoice will be a debit/credit note w.r.t the provisional invoice. This functionality is available in SD transactions. For MM transactions with Formula Pricing
Wipro Ltd.
Page 29 of 44

Invoice Verification will be carried out only once. There is no provision in system to calculate provisional and final billing in purchase side. In SASREF, Prices calculated in three decimals The Pricing Procedure for SASREF Hydrocarbon Sales .
Pricing procedure- ZSASRE

Count er
Conditi on Type ZA00 (Formul a)
Description Basic Price (formula PriceQuotation+Freight+Pre mium)
Pricing Table PriceQuotation PremiumManual Entry FreightQuotation PriceManual Entry Manual Entry Manual Entry Manual Entry Manual Entry
Category Price from OTIS/ Third party+ Formula Surcharge Third Party Quotations+For mula Fixed Amount Discount Discount Surcharge Surcharge
Conditi on Type Behavio r

+
10
ZA01
20
Basic Price (fixed) Handling Fee Discount Processing Fee Additional Premium
ZHAN
30
+ +
ZDIS
40
ZPRO
50
ZAPR
60
SASREF PRICE CALCULATION
Wipro Ltd.
Page 30 of 44

S. No Pricing Scenario 1 Hydrocarbon Products Sales- Fuel Oil,-The Price calculation is based on the formula. System updated the quotation prices from the OTIS. Created Provisional Invoices Bases on the daily average/previous months average price. Differential Invoices created after getting the monthly average price. Freight is part of the basic price formula. 2 Hydrocarbon Products Sales- Kerosene,-The Price calculation is based on the formula. System updated the quotation prices from the OTIS. Created Provisional Invoices Bases on the daily average/previous months average price. Differential Invoices created after getting the monthly average price. Freight is part of the basic price formula .Prices are on Barrels. Freight cost has to convert from per MT to per BBL Hydrocarbon Products Sales- Naphtha,-The Price calculation is based on the formula. System updated the quotation prices from the OTIS. Created Provisional Invoices Bases on the daily average/previous months average price. Differential Invoices created after getting the monthly average price. Freight is part of the basic price formula. Hydrocarbon Products Sales- Gas Oil,-The Price calculation is based on the formula. System updated the quotation prices from the OTIS. Created Provisional Invoices Bases on the daily average/previous months average price. Differential Invoices created after getting the monthly average price. Freight is part of the basic price formula .Prices are on Barrels .Freight cost has to convert from per MT to per BBL Hydrocarbon Products Sales(Tender Products)- Long Residue and Mogas,-The Price calculation is based on the Tender. To calculate the tender price, 10 days price has to monitor from the B/L date and from the 10th day calculate backward and take 5 days average price .Premium is part of the pricing and for Mogas additional premium is there based on the RON Factor. Hydrocarbon Products Sales- Benzene, The price calculation is based on the third party quotations. Hydrocarbon Products Sales- Wash Oil, The price calculation is calculated on average quotation price of the November and December Months. Average density is one of the factor to calculate the pricing. Hydrocarbon Products Sales- LPG/ Sulphur- Price is on Fixed price given by ARAMCO, ARAMCO charges Handling fee from SASREF Pricing Document
FuelOil.xlsx
Kerosene.xlsx
Naphtha.xlsx
Gas Oil.xlsx
LR and Mogas.xlsx
Benzene.xlsx
Wash Oil.xlsx
Wipro Ltd.
Page 31 of 44

Freight Calculation- Frieght cost calculation is on per MT. Third part quotations are being used to calculate the freight. There are Yearly components and Monthly variable components.
Freight.xlsx
3.4 CLASSIFICATIONS FOR SALES MASTERS

The Sales Master Data Classifications in SAP consists of the following:
3.4.1 Customer Group

There are five fields in the customer master for classifying the customer. These fields are Customer group 1, Customer group 2 , Customer group 3 and Customer Group 4 At SASREF: Customer groups are Causeway pricing and reporting purpose. and Pipeline would be used for
3.6.1 Terms of Payment

The terms of payment are defined for the customers. Aspects of accounting such as due date for net payment in the invoice is defined and managed in FI module. The short texts for the terms of payment can be stored for SD. At SASREF: Payment Terms is 35 Days from the date of Goods Issue date it depends on the customer this will be a part of FI Module
3.6.2 Incoterms
International Commercial Terms Codification of international rules for the interpretation of the most commonly used terms in international trade. The Incoterms are specified for customers. It defines the terms of sale and the passing of risks for sales.
Wipro Ltd.
Page 32 of 44

At SASREF: As per GASP ,the Incoterms can be such as Ex Works (EXW), Free on Board (FOB). it will be defined in SAP.
3.6.3 Shipping Conditions

Shipping points are independent organizational entities within which processing and monitoring of the deliveries as well as goods issue is carried out. A delivery is processed by one shipping point only At SASREF: As per GASP the shipping conditions can be such as Vessels and Pipe line
3.6.5 Account Assignment

The account assignment is used to determine revenue accounts at the time of billing. An accounting document gets generated automatically when a billing document is created in SAP. The revenue accounts are automatically determined based on account assignment. Master Data Relevant for Account Assignment The account relevance for customers and materials can be defined to determine the revenue accounts at the time of billing. There are separate account assignment groups for customers and account assignment groups for materials. The respective account assignment group is assigned in the customer and material master. At SASREF: Depending on the revenue account determination at the time of billing, the customer and material account assignment group will be defined.
BUSINESS PROCESSES
4.1 Sales Contract Handling
Wipro Ltd.
Page 33 of 44
Business Blueprint Sales & Distribution 2.8

A quantity contract is an agreement to supply a fixed quantity over a period of time. Since the customer promises to buy the fixed quantity of goods/services, they will get a discounted price. When Quantity is Limited - When the production quantities are limited in numbers, then customers are allocated a specific quantity by time -period ( say a month, or a quarter ) . And customers cannot place ad-hoc orders, but have to first sign a contract for a fixed quantity and always order via release orders that specifically refer to the contract. When Vendors want to Lock-in Customer quantities - Some times to give deep discounts, sales folks require that customers commit to buying a fixed quantity over a time-period. This satisfies the sales figures .
4.1.2 Master Data

Customer Master, Material master Incoterms, Payment terms:
4.1.3 Features for SASREF

The contacts which you enter and store all the important, sales-related information you use during Nomination, Ticketing and Invoicing processing. The business user has to create monthly one quantity contract to supply the Hydrocarbon products to the customers. The use has to select the contact document type, As per the GSAP , In SASREF the contract type will be ZCQ., Fill the mandatory fields like Sales organization, distribution Channel and the division. Enter the Customer Code and the Material code and the quantity to be delivered in the month. Maintain the Validity period of the contract. In SASREF the contract validity is for one month. Check the Incoterm and the payment term, these fields will get copied from the customer master and the user an change the data in the contract. Check the pricing screen in the Contract. In SASREF most of the sales scenarios work based on the formula based pricing. As per the contract, select the pricing formula and maintain the same formula in the contract pricing. Maintain other pricing data like Processing fee, premium, freight, handling fee etc in the pricing. The pricing formula can be created separately in the repository and the same pricing formula can be used for different contacts. This is SAP standard functionality. Next step is to maintain the rule for the provisional and differential invoice creation .Provisional invoice will be created based on the average daily quotation price getting from the OTIS, the revenue will be posting to the accounts. The

differential invoice will be create based on the monthly average price of the quotation. After creating the differential Invoice, the system will post the differential amount to the account.
4.1.4
Business Process
All the Hydrocarbon sales transaction to be handled though the contracts Contract Document type:
Contract Type ZCQ
Description Global Standard Contract
Type of Number range Internal Number Range
Monthly created one contract for a customer to deliver the products. Pricing in the contract will be as per the agreed formula, A contract, can have one ore more than one line items Validity Period, Rule for invoicing-Provisional and Differential can be maintained in the Contracts Customer , Material, Payment Term, Incoterm etc.. will be copied from the Master data .
4.3 Sales Order

This business process in order to create and process a sales order and trigger subsequent logistics processing in SAP R/3. A sales order is a customers binding request to an enterprise to deliver a specific quantity of products, or to provide a service at a specific time. A sales organization accepts the sales order, and thus becomes responsible for fulfilling the contract.
4.3.1 Purpose
Sales Order is a pre-requisite for processing a customer order. It is the starting point where in the customers requirements in their purchase order is captured and taken for further processing.
4.3. 2 Master Data
Wipro Ltd.
Page 35 of 44

Customer Master, Material Master, Pricing Conditions, Incoterms, Payment terms.

We use documents from the components of Sales and Distribution (SD) in Traders and Schedulers Workbench (TSW). The system uses these documents for many processes and functions in TSW, such as to calculate inventory quantities in the Stock Projection Worksheet (SPW) or to calculate demand and supply quantities . In SASREF we assign these documents to nominations and to movement scenarios to determine how the system is to process and post the quantities during ticketing. To use these documents in TSW processes, we make these documents relevant to TSW applications. by assigning TSW relevance and/or SPW relevance. As per GSAP Process, In SASREF, when the user post the Ticket, the sales Order Creation will trigger in Background. Sales Document type: Sales Order Type ZOR Description SASREF Standard Order Type of Number range Internal Number Range
4.5
Delivery
Outbound delivery in its role as central object of the goods issue process, supports all shipping activities including picking, packing, transportation and goods issue. During the outbound delivery process, shipping-planning information is recorded, status of shipping activities is monitored and data accumulated during shipping processing is documented. When the outbound delivery is created, the shipping activities, such as picking or delivery scheduling, are initiated, and data that is generated during shipping processing is included in the delivery. Shipping plays an important role in the Logistics chain and is a subsequent activity of the Sales component. Some of the indicative functions supported by the shipping component are listed below: Deadline monitoring for reference documents due for shipment (sales orders Creating and processing outbound deliveries Monitoring material availability and processing outstanding orders Processing goods issue
4.5.1 Purpose
A delivery is processed through one shipping point. Which shipping point carries out the processing for a delivery can be determined automatically during order processing or you can specify it manually in the order. As soon as the material availability date or the transportation scheduling date for a schedule line is reached, the schedule line becomes due for shipping. When you create an outbound delivery, you initiate shipping activities such as picking and transportation scheduling.
4.5.2 Master Data

Customer Master, Material Master, Incoterms and Route.

As per the GSAP process, when the user posts the Ticket, System will create the Delivery document and the Goods Issue in the background. The payment term calculates based on the Goods Issue date
4.5.4 Business Process

While creating Delivery , automatically executing the delivery due list, Goods Issue, generate material document and the stocks reduces. Goods Issue generates accounting documents- Cost of Goods Sold-Debit and the Inventory account Credits.
. Delivery Document type: Delivery Type ZLF Description SASREF Standard Delivery Type of Number range Internal Number Range
Wipro Ltd.
Page 37 of 44
Business Blueprint Sales & Distribution 4.7 Billing

4.8.1 Billing Process
Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.
4.8.2 Purpose
Billing is the final document based on which the customer is to make payment for the products/services provided by the selling organization. The following options are available for billing document creation:
Automatic processing of the billing due list in the background This can also be carried out periodically (e.g. every day at 10 PM, or on 15th day of the month) and automatically by the system.
Manual processing of the billing due list Enter the selection criteria. The system then selects all the documents fulfilling this criteria and enters them in a billing due list which can be process
4.8.3 Master Data

Customer Master, Material Master, Pricing Conditions, Output

Invoices based on deliveries only Billing document will have Payer Pricing can be updated in the billing documents Provisional invoices will be created based on the daily average quotation prices Differential invoice will be created, after getting the monthly average quotation prices. Account posting will happen in the provisional and differential invoices. Accounting entries after billing, Customer account Debit and Sales revenue credit
Wipro Ltd.
Page 38 of 44

Background program will be activated to create the billing document, System will check the Goods issue completed documents and will create the billing document automatically in the background The background billing document will be generated in the 15th day of the month(Provisional) and the differential invoice in the beginning of the next month(After getting the monthly average price from the quotations) Billing Document types: Billing Type ZF2 ZDF Description SASREF Provisional Billing SASREF Differential Billing Type of Number range Internal Number Range Internal Number Range
SASREF SALES SCENARIOS

In SASREF we have identified Three Sales Scenarios,
5.1.1 Sales of Sulphur /LPG to Saudi Aramco via pipeline

On behalf of SASREF Aramco sells the Sulphur / LPG to the customers and Aramco charges handling fee from SASREF. SASREF sends the material to Aramco Via Pipeline or via Truck. The pricing is on Fixed amount given By Aramco. There wont be any provisional billing in this scenario
Wipro Ltd.
Page 39 of 44
5.1.1 Sales of Kerosene to Farabi / Wash Oil to Petrokemya / Benzene and Wash Oil to SADAF
SASREF sells Kerosene to Farabi, Wash Oil to Pertokemya , Benzene and Wash oil to SADAF. for pricing the calculation for Benzene, Kerosene is Monthly Average Price and for Wash oil, Nov-Dec Average Price. Provisional Invoice based on the Daily Average price and Actual Billing After Getting the Monthly Average price
Wipro Ltd.
Page 40 of 44
5.1.1 Sales of Finished Product to Saudi Aramco Trading and Shell Trading via Ship
SASREF sells the main products to Shell and Aramco in 50:50 basis. For Pricing Provisional Invoice based on the Daily Average price and Actual Billing After Getting the Monthly Average price
Wipro Ltd.
Page 41 of 44
STANDARD INFORMATION SYSTEM

5.1 Purpose
The Sales Information System is a flexible tool which allows you to collect, consolidates, and utilizes data from Sales and Distribution processing. It can be used at different levels in the decision-making process as a control and planning instrument, enabling you to recognize market developments and economic trends early on and to take appropriate measures.
5.2 Features
From the mass of data (Master data and Transactional data) which exists in the SD System, one can use the aggregation function to filter out the most important information, tailored to ones needs. It is up to the user to determine the depth of information he receive.
Wipro Ltd.
Page 42 of 44

The Sales Information System is a component of the Logistic Information System (LIS), which contains a range of other information systems including those for Purchasing and the Shop Floor. Some of the standard Information tools available are:
5.3
Standard analyses
MCTA Customer MCTC Material MCTE - Sales organization Conditions MCV5 - Price list Document information VA15 - Inquiries list VA25 - Quotations list MCV9 - Incomplete billing documents Orders VA05 - Orders list Deliveries VL06F - Deliveries list Billing documents VF05 - Billing docs list VF04 - Billing due list Customer MC(A - SIS: Customer, Inc.Orders Selection MC+A - SIS: Customer Returns, Selection MC+I - SIS: Customer Credit Memos - Selection MCTA - SIS: Customer Analysis Selection Sales organization MC(I - SIS: SalesOrg. Inc.Orders Selection MCTE - SIS: Sales Org. Analysis Selection ..
Wipro Ltd.
Page 43 of 44
7 SD: LAYOUTS AND REPORTS

SASREF needs the following layout to be printed from SAP SD Module: 1. Invoice Layout to be developed and the same need to convert into PDF to send to the customers. SD Report Requirement S.NO 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Name of the Report Product delivery ledger (OA_R010) Product Invoice ledger (OA_R020) Sales Summary By Product (OA_R180) Monthly Delivery listing (OA_R130) Sales Summary (OA_R070) Sulphur Sales Summary Sales Summary By Country (OA_R190) Invoice Summary (OA_R210) Monthly Freight Data listing ( OA_R030) Yearly Freight Data listing ( OA_R040) Freight Calculation Report (OA_R050) Quotation Price Listing (OA_R060) Calculation Sheet (OA_R100) Price Calculation (OA_R110) Sulphur Statement of Calculation Production (OA_R140)
Wipro Ltd.
Page 44 of 44

Tenneco SD BBP v1.1

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Tenneco SD BBP v1.1

Transféré par

Droits d'auteur :

Formats disponibles

SALES & DISTRIBUTION BUSINESS BLUEPRINT

WIPRO LIMITED VERSION 1.0

Business Blueprint Sales & Distribution

Business Blueprint Sales & Distribution

Author Michael Joseph Michael Joseph

Change Control Draft DraftDraft

Business Blueprint Sales & Distribution

2 ORGANISATION STRUCTURE..........................................................17 2.1 ORGANISATION ELEMENTS...........................................................17

MATERIAL MASTER ....................................................................26

Business Blueprint Sales & Distribution

5 SASREF SALES SCENARIOS............................................................39

4.8.1 4.8.2 4.8.3 4.8.4

STANDARD INFORMATION SYSTEM............................................42 5.1 Purpose......................................................................................42 5.2 Features.....................................................................................42

7 SD: LAYOUTS AND REPORTS........................................................44

Business Blueprint Sales & Distribution

2 THE PROJECT SCOPE

Geographic and Organizational Scope:

Business Blueprint Sales & Distribution

Report Reference PD_R010 to PD_R250 OA_R010 to OA_R270

No. of Reports 25 27 14 Query based reports

Business Blueprint Sales & Distribution

1. Procurement and Inventory (MM):

5. Finance: Covers Financial and Management Accounting processes comprising of Cash

Business Blueprint Sales & Distribution

Business Blueprint Sales & Distribution

BUSINESS BLUEPRINT OVERVIEW

Business Blueprint Sales & Distribution

2.5 SALES & DISTRIBUTION

2.6 IMPLEMENTATION SCOPE

Business Blueprint Sales & Distribution

BUSINESS PROCESS SCOPE

STANDARD SALES PROCESSING IN SAP

Business Blueprint Sales & Distribution

Business Blueprint Sales & Distribution

Business Blueprint Sales & Distribution

UNIT OF MEASURE (UOM)

Business Blueprint Sales & Distribution

Business Blueprint Sales & Distribution

2.1.1 Company Code

2.1.2 Credit Control Area

Business Blueprint Sales & Distribution

2.1.3 Sales Organization

Sales Organization Description SASREF Sales Organization

Business Blueprint Sales & Distribution

Description Global Supply

Business Blueprint Sales & Distribution

2.1.6 Sales Area

Sales Organization Distribution Channel Division SR01 06 02

Sales Area SR01-06-02

Business Blueprint Sales & Distribution

Renowned Auto Products Mfrs Ltd

2.1.9 Storage Location

Business Blueprint Sales & Distribution

At SASREF: Shipping Point is assigned to Plants

Shipping Points 1000

Shipping Points description

Renowned Auto Products Mfrs Ltd

Transportation Planning Point

At SASREF: One Transportation Point is assigned to Company Code

Transportation Planning Points 1000

Renowned Auto Products Mfrs Ltd

OVERALL ORGANISATION STRUCTURE