Service Material Master Guidelines

Section 1 General Guidelines of GMD

ZSER: An SAP Sold service is a material type which is utilized to generate revenue for
services provided to our customers.
ZJOB: Discrete Service is the material type for a bill of materials (BOM). Bill of material
is used on all orders for services to determine job purpose.
ZSBM: Sales Blends are material compounds which may be created and used as either
configurable or non-configurable service materials.
Section 2 Approvals and Submittal of requests:

These are the steps to follow in order to request Service Materials. (ZSER,ZJOB,ZSBM)

First, identify your PSL and PSL price analyst for support and approval. See link
Price Book Approval List

Complete forms on the link below.

For 1-3 Material requests - Create New Service Material Form With Dropdowns
For more than 3 Material requests - Create Material Form WithOUT Dropdowns (All
Views)

The process flow is as follows:

The Requestor fill out what they can on the individual request form, it has drop
downs then it is forwarded to the PSL Analysts for review,
completion/correction if needed, and approval.

10/26/2016

The process is designed for the PSL Analyst who is approving the requests to
communicate with the requestor to understand what is needed and then
completing the form for submission to GMD.
GMD then reviews the forms when received from the Analyst, and if something is
still missing or unclear, then they should communicate with the Analysts.

Section 3 Other Non - Service Material types:

There are a few types of non-service material types that are handled through the price
book functional FDUNPRBK.
ZCUS: customer-owned Inventory: this type of material is used to get around the issue of
using non-valuated materials for customer-owned inventory while keeping the ZSFG
material type. Customer-owned material types are user-defined materials, meaning its
setup is not like the other material types in numeric sequence. Instead a specific naming
convention is utilized.
NEW!! Use this link for more information about new ZCUS creation process: This
process is currently used in Norway and US locations.
http://halhelp.corp.halliburton.com/gm/folder-1.11.20336?mode=EU
ZVAS: Virtual Assembly
ZSTS: Object Codes: The object code are solely used for reporting and only submitted
from Duncan, Ok, currently by Burt Hamm.
Section 4 Product Hierarchy:

The product hierarchy (PH) table is a grouping of product and reporting attributes that are
created and maintained by GMD Price Book. The product hierarchy is set per material

10/26/2016

and has a one-to-many relationship between the basic and sales views as guided in this
documentation. The main rule to follow is to setup the same product hierarchy across all
sales view the material may potentially be extended to.
Approval: All new Product Hierarchies and changes must be approved by the PSL
approver. See link Price Book Approval List
There is a specific naming and meaning in the creation and setup of a product hierarchy.
The illustration and explanation below will provide an example of the meaning and
implications of a product hierarchy and the Request process flow for new product
hierarchy on page 4.

Explanation of naming and meaning of product hierarchy per level:

Level 1 = The first two numeric digits represents the division/PSL. It can only be
numeric.

Level 2 = Digits 3-8 represent the sub-PSL.

10/26/2016

o The last five digits of a profit center should always equal the product
hierarchy sub-PSL for all service materials.

Level 3 = Digit 9 represents the product hierarchy type. It can only contain one
alpha character. It will be one of the following:
o S = Services
o M = Products
o J = Job BOMs
o X = For Landmark

Level 4 = First node group for reporting. It can contain 3 characters and can be
mixed with alpha and numeric characters. Three characters are required.

Level 5 = Second node group for reporting. It can also contain 3 characters with
mixed alpha and numeric characters. Three characters are required.

Level 6 = Last node for reporting. It can contain 4 characters with mixed alpha
and numeric characters. Three characters are required, but four can be entered.

10/26/2016

Request process flow for new product hierarchy:

Request documentation may consist of email text or spreadsheet detailing need, structure and name.

10/26/2016