You are on page 1of 109

TITAN SAP CONFIGURATION DOCUMENTS <SALES AND DISTRIBUTION>

AUTHOR(S) : Dhanbalan / Thitipan Singhapreecha


DOCUMENT NUMBER : SD-Configuration documents
VERSION : 0.1
SOURCE : Atos Origin
STATUS : Draft
DOCUMENT DATE : 01st of November 2007
NUMBER OF PAGES : 101
RELEASED FOR TRAINING :
RELEASED FOR OPERATIONS :

OWNER : Atos Origin

INITIALS :
Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Role Name / Function Signature Date

Author Dhanbalan / Thitipan


Singhapreecha

Mark Ma

Wong Fei Mun

Quality Assurance Function

Document Owner Atos Origin

Senior Manager Atos Origin

© Copyright 2007, Atos Origin All rights reserved. Reproduction in whole or in parts is prohibited without the written consent of the
copyright owner. For any questions or remarks on this document, please contact Atos Origin,

Atos Origin 30 janvier 2010 2 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Contents

1 ENTERPRISE STRUCTURE ....................................5


1.1 DEFINING THE STRUCTURE ...................................... 5
1.1.1 Define Sales Organization ....................................5
1.1.2 Define Distribution Channel ..................................8
1.1.3 Define Division ..............................................9
1.1.4 Maintain Sales Office .......................................10
1.2 ASSIGNMENT OF STRUCTURE .................................... 12
1.2.1 Assign sales organization to company code ...................12
1.2.2 Assign distribution channel to sales organization ...........14
1.2.3 Assign division to sales organization .......................16
1.2.4 Set up sales area ...........................................18
1.2.5 Assign sales office to sales area ...........................20
1.2.6 Assign sales organization- distribution channel- plant ......23
2 Sales and Distribution .................................27
2.1 Define Condition Types ..................................... 27
2.2 Maintain pricing procedure ................................. 31
2.3 Define Pricing Procedure Determination ..................... 32
2.4 Define Tax Relevancy of Master Records (Customer Taxes) .... 34
2.5 Define Account Key ......................................... 35
2.6 Assign G/L Accounts ........................................ 37
2.7 Maintain Output Types ...................................... 40
2.8 Maintain Output Determination Procedure .................... 43
2.9 Assign Output Determination Procedure ...................... 44
2.10 Define Text Types .......................................... 46
2.11 Define and Assign Text Determination Procedures ............ 48
2.12 Define Incompleteness Procedures ........................... 55
2.13 Assign procedures to the sales document types .............. 60
2.14 Assign procedures to item categories ....................... 62
2.15 Define Sales Document Types ................................ 63
2.16 Define Number Ranges For Sales Documents ................... 67
2.17 Define Order Reasons ....................................... 70
2.18 Define Item Categories ..................................... 71
2.19 Assign Item Categories ..................................... 75
2.20 Define Reasons For Rejection ............................... 76
2.21 Copy Control: Billing Document to Sales Document ........... 77
2.22 Define Billing Types ....................................... 84
2.23 Maintain Copying Control For Billing Documents ............. 98
3 LOGISTICS GENERAL .....................................107
3.1 Assign Update Group at Item Level ......................... 107
3.2 Assign Update Group at Header Level ....................... 108

Atos Origin 30 January 2010 3 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

List of changes
VERSION DATE DESCRIPTION AUTHOR
0.1 01 Initial configuration specification Thitipan
November Singhapreech
2007 a

Atos Origin 30 janvier 2010 4 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

1 ENTERPRISE STRUCTURE
Enterprises are economic units whose structure has often developed in an evolutionary way, An enterprise
can consist of several legally independent companies, for which you need to create individual financial
statements at the end of the year. Organization units represent the structure of an enterprise organization,
the legal and organizational views of an enterprise.
Sales and Distribution module uses some organization units that can represent sales and distribution
processes such as;

Sales Organization
Distribution Channels

Divisions

Sales Office

Other organization units, such as company code or plant, are used in Sales and Distribution and in other

modules in SAP system

1.1 DEFINING THE STRUCTURE

1.1.1 Define Sales Organization

The sales organization is an organizational unit in Logistics that groups the enterprise according to the
requirements of sales and distribution. A sales organization is responsible for distributing goods and services.
Therefore, it is also liable for the sold products and responsible for a customer‘s rights of recourse.
A sales organization is uniquely assigned to a company code. More than one sales organization can be
assigned to a company code. In Sales and Distribution module, you need at least one sales organization.
From SD Business Blueprint, each Company Code of Titan has one Sales Organization as below.

Menu Path IMG Enterprise Structure Definition Sales and Distribution Define,
copy, delete, check sales organization
Transaction Code: SPRO

Atos Origin 30 janvier 2010 5 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 6 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Enter Sales Organization and description accordingly.

Sales
Organization Description
SS01 Titan Virgo Sls Orgn
SS02 Titan Aries Sls Orgn
SS03 Estonia Capital SO
SS04 Titan Leo SO
SS05 Titan Mercury
SS06 Titan Pisces
SS07 Sino Venus SO
SS08 Titan Chios SO
SS09 Titan Gemini SO
SS10 Titan Libra
SS11 Titan Mars SO
SS12 Titan Neptune SO
SS13 Sino Ocean SO
SS18 Wendelstar Intl SO
SS19 Titan Ocean SO
SS20 NAS Mgmt SO
SS21 Neptune Assoc SO
SS22 Far East Bnkrng SO
SS23 Sino Mercury SO

Atos Origin 30 January 2010 7 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

1.1.2 Define Distribution Channel

A distribution channel is a mean through which salable materials or services reach the customer. Distribution
channel will be assigned to a sales organization
From SD Business Blueprint, one distribution channel is defined as below.

Menu Path IMG Enterprise Structure Definition Sales and Distribution Define,
copy, delete, check distribution channel
Transaction Code: SPRO

Atos Origin 30 January 2010 8 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Distribution
Channel Description
10 Sales

1.1.3 Define Division

A division is used to group materials and services. Division will be assigned to a sales organization
From SD Business Blueprint, one division is defined as below.

Menu Path IMG Enterprise Structure Definition Logistic General Define, copy,
delete, check division
Transaction Code: SPRO

Atos Origin 30 January 2010 9 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Division Description
S1 Singapore Shipping

1.1.4 Maintain Sales Office

Sales office is an organization unit in a geographical area of a sales organization

Menu Path IMG Enterprise Structure Definition Sales and Distribution Maintain
sales office
Transaction Code: SPRO

Atos Origin 30 January 2010 10 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales Office Description


1000 Singapore

Atos Origin 30 January 2010 11 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

1.2 ASSIGNMENT OF STRUCTURE

1.2.1 Assign sales organization to company code

Menu Path IMG Enterprise Structure Assignment Sales and Distribution Assign
sales organization to company code
Transaction Code: OVX3

Sales
Company Code Description Organization Description
SS01 Titan Virgo Pte Ltd SS01 Titan Virgo Sls Orgn
SS02 Titan Aries Pte Ltd SS02 Titan Aries Sls Orgn
SS03 Estonia Capital Ltd SS03 Estonia Capital SO
SS04 Titan Leo Pte Ltd SS04 Titan Leo SO
Titan Mercury
SS05 SS05 Titan Mercury
Shipping Pt
SS06 Titan Pisces Pte Ltd SS06 Titan Pisces
SS07 Sino Venus Pte Ltd SS07 Sino Venus SO
SS08 Titan Chios Pte Ltd SS08 Titan Chios SO

Atos Origin 30 January 2010 12 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales
Company Code Description Organization Description
SS09 Titan Gemini Pte Ltd SS09 Titan Gemini SO
SS10 Titan Libra Pte Ltd SS10 Titan Libra
SS11 Titan Mars Limited SS11 Titan Mars SO
Titan Neptune
SS12 SS12 Titan Neptune SO
Shipping Pt
Sino Ocean
SS13 SS13 Sino Ocean SO
Development Li
Wendelstar
SS18 SS18 Wendelstar Intl SO
International
SS19 Titan Ocean Pte Ltd SS19 Titan Ocean SO
NAS Management Pte
SS20 SS20 NAS Mgmt SO
Ltd
Neptune Associated
SS21 SS21 Neptune Assoc SO
Shippi
Far East Bunkering
SS22 SS22 Far East Bnkrng SO
Servic
SS23 Sino Mercury Pte Ltd SS23 Sino Mercury SO

Atos Origin 30 January 2010 13 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

1.2.2 Assign distribution channel to sales organization

Menu Path IMG Enterprise Structure Assignment Sales and Distribution Assign
distribution channel to sales organization
Transaction Code: OVXK

Atos Origin 30 January 2010 14 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales Distribution
Organization Description Channel Description
SS01 Titan Virgo Sls Orgn 10 Sales
SS02 Titan Aries Sls Orgn 10 Sales
SS03 Estonia Capital SO 10 Sales
SS04 Titan Leo SO 10 Sales
SS05 Titan Mercury 10 Sales
SS06 Titan Pisces 10 Sales
SS07 Sino Venus SO 10 Sales
SS08 Titan Chios SO 10 Sales
SS09 Titan Gemini SO 10 Sales
SS10 Titan Libra 10 Sales
SS11 Titan Mars SO 10 Sales
SS12 Titan Neptune SO 10 Sales
SS13 Sino Ocean SO 10 Sales
SS18 Wendelstar Intl SO 10 Sales
SS19 Titan Ocean SO 10 Sales
SS20 NAS Mgmt SO 10 Sales
SS21 Neptune Assoc SO 10 Sales

Atos Origin 30 January 2010 15 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales Distribution
Organization Description Channel Description
SS22 Far East Bnkrng SO 10 Sales
SS23 Sino Mercury SO 10 Sales

1.2.3 Assign division to sales organization

Menu Path IMG Enterprise Structure Assignment Sales and Distribution Assign
division to sales organization
Transaction Code: OVXA

Atos Origin 30 January 2010 16 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales
Organization Description Division Description
SS01 Titan Virgo Sls Orgn S1 Singapore shipping
SS02 Titan Aries Sls Orgn S1 Singapore shipping
SS03 Estonia Capital SO S1 Singapore shipping
SS04 Titan Leo SO S1 Singapore shipping
SS05 Titan Mercury S1 Singapore shipping
SS06 Titan Pisces S1 Singapore shipping
SS07 Sino Venus SO S1 Singapore shipping
SS08 Titan Chios SO S1 Singapore shipping
SS09 Titan Gemini SO S1 Singapore shipping
SS10 Titan Libra S1 Singapore shipping
SS11 Titan Mars SO S1 Singapore shipping
SS12 Titan Neptune SO S1 Singapore shipping
SS13 Sino Ocean SO S1 Singapore shipping
SS18 Wendelstar Intl SO S1 Singapore shipping
SS19 Titan Ocean SO S1 Singapore shipping
SS20 NAS Mgmt SO S1 Singapore shipping
SS21 Neptune Assoc SO S1 Singapore shipping

Atos Origin 30 January 2010 17 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales
Organization Description Division Description
SS22 Far East Bnkrng SO S1 Singapore shipping
SS23 Sino Mercury SO S1 Singapore shipping

1.2.4 Set up sales area

A sales area is a combination of the sales organization, distribution channel and division. It defines the
distribution channel a sales organization uses to sell products from a certain division

IMG Enterprise Structure Assignment Sales and Distribution Set up


Menu Path
sales area

Atos Origin 30 January 2010 18 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Transaction Code: OVXG

Sales Distribution
Organization Description Channel Division
SS01 Titan Virgo Sls Orgn 10: Sales S1: Singapore shipping
SS02 Titan Aries Sls Orgn 10: Sales S1: Singapore shipping
SS03 Estonia Capital SO 10: Sales S1: Singapore shipping
SS04 Titan Leo SO 10: Sales S1: Singapore shipping
SS05 Titan Mercury 10: Sales S1: Singapore shipping
SS06 Titan Pisces 10: Sales S1: Singapore shipping
SS07 Sino Venus SO 10: Sales S1: Singapore shipping
SS08 Titan Chios SO 10: Sales S1: Singapore shipping
SS09 Titan Gemini SO 10: Sales S1: Singapore shipping
SS10 Titan Libra 10: Sales S1: Singapore shipping
SS11 Titan Mars SO 10: Sales S1: Singapore shipping
SS12 Titan Neptune SO 10: Sales S1: Singapore shipping

Atos Origin 30 January 2010 19 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales Distribution
Organization Description Channel Division
SS13 Sino Ocean SO 10: Sales S1: Singapore shipping
SS18 Wendelstar Intl SO 10: Sales S1: Singapore shipping
SS19 Titan Ocean SO 10: Sales S1: Singapore shipping
SS20 NAS Mgmt SO 10: Sales S1: Singapore shipping
SS21 Neptune Assoc SO 10: Sales S1: Singapore shipping
SS22 Far East Bnkrng SO 10: Sales S1: Singapore shipping
SS23 Sino Mercury SO 10: Sales S1: Singapore shipping

1.2.5 Assign sales office to sales area

Menu Path IMG Enterprise Structure Assignment Sales and Distribution Assign
sales office to sales area
Transaction Code: OVXM

Atos Origin 30 January 2010 20 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales Distribution
Organization Description Channel Division Sales office
S1: Singapore 1000: Singapore
SS01 Titan Virgo Sls Orgn 10: Sales
shipping
S1: Singapore 1000: Singapore
SS02 Titan Aries Sls Orgn 10: Sales
shipping
S1: Singapore 1000: Singapore
SS03 Estonia Capital SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS04 Titan Leo SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS05 Titan Mercury 10: Sales
shipping
S1: Singapore 1000: Singapore
SS06 Titan Pisces 10: Sales
shipping
S1: Singapore 1000: Singapore
SS07 Sino Venus SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS08 Titan Chios SO 10: Sales
shipping
SS09 Titan Gemini SO 10: Sales S1: Singapore 1000: Singapore

Atos Origin 30 January 2010 21 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales Distribution
Organization Description Channel Division Sales office
shipping
S1: Singapore 1000: Singapore
SS10 Titan Libra 10: Sales
shipping
S1: Singapore 1000: Singapore
SS11 Titan Mars SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS12 Titan Neptune SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS13 Sino Ocean SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS18 Wendelstar Intl SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS19 Titan Ocean SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS20 NAS Mgmt SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS21 Neptune Assoc SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS22 Far East Bnkrng SO 10: Sales
shipping
S1: Singapore 1000: Singapore
SS23 Sino Mercury SO 10: Sales
shipping

Atos Origin 30 January 2010 22 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

1.2.6 Assign sales organization- distribution channel- plant

Menu Path IMG Enterprise Structure Assignment Sales and Distribution Assign
sales organization- distribution channel- plant
Transaction Code: OVX6

Atos Origin 30 January 2010 23 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales Distribution
Organization Description Channel Plant
SS01 Titan Virgo Sls Orgn 10: Sales 1001: Titan Virgo
SS02 Titan Aries Sls Orgn 10: Sales 1005: Titan Aries
1201: Front Lady
SS03 Estonia Capital SO 10: Sales
1202 Front Highness
SS04 Titan Leo SO 10: Sales 1006: Titan Leo
SS05 Titan Mercury 10: Sales 1003: Titan Mercury
SS06 Titan Pisces 10: Sales 1002: Titan Pisces
SS07 Sino Venus SO 10: Sales 1008: Titan Venus
SS08 Titan Chios SO 10: Sales 1010: Titan Chios (Shipping)
SS09 Titan Gemini SO 10: Sales 1007: Titan Gemini (Shipping)
SS10 Titan Libra 10: Sales 1009: Titan Scorpio (Shipping)
SS11 Titan Mars SO 10: Sales 2001: Titan Mars
SS12 Titan Neptune SO 10: Sales 1004: Titan Neptune (Shipping)
SS13 Sino Ocean SO 10: Sales 1101: Titan Taurus
3901: Four Spring
SS18 Wendelstar Intl SO 10: Sales
3902: Scorpius
1901: K Cosmos
SS19 Titan Ocean SO 10: Sales
6901: Titan Honour

Atos Origin 30 January 2010 24 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Sales Distribution
Organization Description Channel Plant
6902: Titan Spirit
SS20 NAS Mgmt SO 10: Sales
4001: Eagle Aries
5001: Alpha Power
5002: Jurong Krapu
5003: Alpha Prestige
5004: Jurong Herring
SS21 Neptune Assoc SO 10: Sales
5005: Alpha Prosperity
5006: Mimosa
5007: Lantana
5008: Neptra Premier
5101: Orchid
6002: Capricorn
6003: Neptank VII
SS22 Far East Bnkrng SO 10: Sales 6001: Neptank VIII
SS23 Sino Mercury SO 10: Sales

Atos Origin 30 January 2010 25 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 26 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

2 Sales and Distribution

2.1 Define Condition Types

Price elements are represented in the SAP system by condition types.


For Titan, price condition (PR00) can be Voyage freight, lumpsum freight, charter hire, bareboat hire,
demurrage, war risk, port charges, shipmanagement fee, shipmanagement costs and voyage miscellaneous
Another condition types for example, Add comm. (ZADD), Brokeragecom (ZBRK) etc. are defined as below

Menu Path IMG Sales & Distribution Basic Functions Pricing Pricing Control
Define condition types
Transaction Code: SPRO

Atos Origin 30 January 2010 27 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 28 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Cond. Description Access Control data Group Changes Scales


Type Seq. condition
PR00 Price PR00 Cond. Class = B Manual entry = C Scale basis =
Cal. Type = C Item condition= X C
Invoice cycle = 9 Amount/ Percent = Check value
X =A
MWST Output Tax MWST Cond. Class = D Group cond. Manual entry = D
Cal. Type = A Item condition= X

Atos Origin 30 January 2010 29 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

   Cond. Category = D
Invoice cycle = 9
SKTO Cash Discount Cond. Class = A Manual entry = D
Cal. Type = A Item condition= X
Cond. Category = D
Invoice cycle = 9

ZAD2 Add Comm Value Cond. Class = A Manual entry = ‘ ‘


Cal. Type = C Delete = X
Plus/Minus = ‘X’ Amount/ Percent =
Invoice cycle = 9 X
Item condition= X

ZADD Add Comm % Cond. Class = A Manual entry = ‘ ‘


Cal. Type = A Delete = X
Plus/Minus = ‘X’ Amount/ Percent =
Invoice cycle = 9 X
Item condition= X

ZBR2 Brokeragecom Cond. Class = A Manual entry = ‘ ‘


Value Cal. Type = C Delete = X
Plus/Minus = ‘X’ Amount/ Percent =
Invoice cycle = 9 X
Item condition= X

ZBRK Brokeragecom % Cond. Class = A Manual entry = ‘ ‘


Cal. Type = A Delete = X
Plus/Minus = ‘X’ Amount/ Percent =
Invoice cycle = 9 X
Item condition= X

ZFIX Fixed Differential Cond. Class = A Manual entry = ‘ ‘


Cal. Type = C Delete = X
Plus/Minus = ‘A’ Amount/ Percent =
Invoice cycle = 9 X
Item condition= X

ZOFF Offhire Cond. Class = A Manual entry = ‘ ‘


Cal. Type = C Delete = X
Plus/Minus = ‘X’ Amount/ Percent =
Invoice cycle = 9 X
Item condition= X

ZOVR Overage Cond. Class = A Manual entry = ‘ ‘


Cal. Type = C Delete = X
Plus/Minus = ‘A’ Amount/ Percent =
Invoice cycle = 9 X
Item condition= X

ZSPC Special Comm Cond. Class = A Manual entry = ‘ ‘

Atos Origin 30 January 2010 30 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

   Cal. Type = C Delete = X


Plus/Minus = ‘X’ Amount/ Percent =
Invoice cycle = 9 X
Item condition= X

ZVAR Variable Cond. Class = A Manual entry = ‘ ‘


Differential Cal. Type = C Delete = X
Plus/Minus = ‘A’ Amount/ Percent =
Invoice cycle = 9 X
Item condition= X

2.2 Maintain pricing procedure

The pricing procedure defines the conditions permitted for a document and the sequence in which the
system takes these conditions into account during pricing.
A standard pricing procedure is defined in the standard SAP system. It contains conditions most commonly
used. These include material prices, discounts, and surcharges, such as freight, or tax.
Titan standard pricing procedure (ZVAA02) is defined for calculating all pricing conditions

Menu Path IMG Sales & Distribution Basic Functions Pricing Pricing Control
Define and Assign Pricing Procedure Maintain pricing procedures
Transaction Code: SPRO

Atos Origin 30 January 2010 31 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

2.3 Define Pricing Procedure Determination

The determination of the pricing procedure depends on the following factors:

Atos Origin 30 January 2010 32 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

1. Customer determination procedure


You specify the customer determination procedure in the customer master record for each sales area.
2. Document pricing procedure
You specify the document pricing procedure for each sales document type and billing type.
To determine the procedure, you allocate the customer determination procedure and the document pricing
procedure to a pricing procedure within a sales area.

Menu Path IMG Sales & Distribution Basic Functions Pricing Pricing Control
Define and Assign Pricing Procedure Define Pricing Procedure Determination
Transaction Code: OVKK

Atos Origin 30 January 2010 33 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

2.4 Define Tax Relevancy of Master Records (Customer Taxes)

Define the tax relevance for customers for each tax category. User has to define tax relevance with the tax
classification indicator in the customer master data

Menu Path IMG Sales & Distribution Basic Functions Taxes Define Tax
Relevancy of Master Records (Customer Taxes)
Transaction Code: OVK3

Atos Origin 30 January 2010 34 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

For the combination of Customer and Material Tax classifications, Tax Codes are assigned. You can see the
assignments by:
Tcode VK11. Condition type: choose MWST and press Enter. In Key Combination window choose Domestic
Taxes radio button. In Display Output Tax screen choose SG in Country field and press Execute icon.

2.5 Define Account Key

Account Key is used for assign G/L accounts in revenue account determination

Atos Origin 30 January 2010 35 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

With the account keys, you group together similar accounts in financial accounting. This way you can
allocate a separate account key to each condition type within a pricing procedure to implement detailed
revenue account determination.

IMG Sales & Distribution Basic Functions Account Assignment/Costing


Menu Path
 Revenue Account Determination Define and Assign Account Keys
Define account key
Transaction Code: SPRO

The following account keys are predefined in the standard SAP R/3 System and used for Titan also
ERF freight revenues
ERL revenues
ERS sales deductions

Atos Origin 30 January 2010 36 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

2.6 Assign G/L Accounts

Allocate G/L accounts for revenue account determination.


The table used for allocation is 001 : Cust Grp/Material Grp/AcctKey

Menu Path IMG Sales & Distribution Basic Functions Account Assignment/Costing
 Revenue Account Determination Assign G/L Accounts
Transaction Code: VKOA

The table used for allocation is 001 : Cust Grp/Material Grp/AcctKey as below

Atos Origin 30 January 2010 37 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 38 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 39 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Assign the same G/L account as above to Sales Organization SS02-SS13, SS18-SS23 also.

IMP: Remember that in the Customer master and Material Master you need to specify entries in the Account
Assignment Group field.

2.7 Maintain Output Types

Outputs are an important media for communicating with Business Partner in sales processing.
Sales and distribution output can be sent both electronically and by mail.

IMG Sales & Distribution Basic Functions Output Control Output


Menu Path Determination Output Determination Using the Condition Technique
Maintain Output Determination for Billing Documents Maintain Output
Types
Transaction Code: V/40

Atos Origin 30 January 2010 40 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

There are two output types for Titan:


ZRD0 Titan Invoice/CN DN used for printing output
ZRD1 Titan Inv/CN DN PDF used for sending PDF file by E-mail

Atos Origin 30 January 2010 41 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 42 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

2.8 Maintain Output Determination Procedure

Output determination in sales and distribution allows you to control proposal using assignments and
groupings in such a way that the system selects the output allowed in each sales transaction and carries out
output processing according to predefined criteria.

IMG Sales & Distribution Basic Functions Output Control Output


Menu Path Determination Output Determination Using the Condition Technique
Maintain Output Determination for Billing Documents Maintain Output
Determination Procedure
Transaction Code: SPRO

Atos Origin 30 January 2010 43 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Titan project has two output types (ZRD0, ZRD1) as below and these output types are assigned to procedure
V10000

2.9 Assign Output Determination Procedure

This step is assign output determination procedure V10000 to billing documents.

IMG Sales & Distribution Basic Functions Output Control Output


Menu Path Determination Output Determination Using the Condition Technique
Maintain Output Determination for Billing Documents Assign Output
Determination Procedure
Transaction Code: V/25

Atos Origin 30 January 2010 44 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 45 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

The output type ZRD0 will be assigned to all billing types of Titan as below
SS01-SS13, SS18-SS23
CS01-CS13, CS18-CS23
DS01-DS13, DS18-DS23

2.10 Define Text Types

Classification for the texts that the user can define in master records or documents

Menu Path IMG Sales & Distribution Basic Functions Text Control Define Text
Types
Transaction Code: VOTXN

Atos Origin 30 January 2010 46 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 47 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

There are two text types as below


Z001 Contact person for enter contact name in Sales Order header
Z002 Freight information for copying freight information from Additional data B of header data

2.11 Define and Assign Text Determination Procedures

The text types of a text object from 2.10 are grouped together in text determination procedures. A text
determination procedure was assigned using certain keys, for example, account group customer or sales
document type.
The SAP System offers the text types of the corresponding text determination procedure for maintenance,
for example, when you are editing a customer master record of the assigned account group customer or a
sales document of the assigned sales document type.
In this step you set the following defaults:
Define access sequence for text types.
Define the text determination procedure.
Define text types and access sequence into text determination procedure.
Assign the text determination procedure for automatic text determination.

Menu Path IMG Sales & Distribution Basic Functions Text Control Define and
Assign Text Determination Procedures
Transaction Code: VOTXN

Atos Origin 30 January 2010 48 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define text determination for Sales Document Header

Atos Origin 30 January 2010 49 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define access sequences of text determination procedure

Atos Origin 30 January 2010 50 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Assign text types and access sequence into text determination procedure

Atos Origin 30 January 2010 51 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Assign text determination procedure 01 to sales order type ZCR, ZDR and ZOR

Atos Origin 30 January 2010 52 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define text determination for Billing Document Header

Assign text types and access sequence into text determination procedure

Atos Origin 30 January 2010 53 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 54 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Assign text determination procedure 03 to the following billing types


SS01-SS13, SS18-SS23
CS01-CS13, CS18-CS23
DS01-DS13, DS18-DS23

2.12 Define Incompleteness Procedures

Define an incompleteness procedure when a sales document or sales activity should be regarded as
incomplete and how the system should respond when you create a document.

IMG Sales & Distribution Basic Functions Log of Incomplete Items


Menu Path
Define Incompleteness Procedures

Atos Origin 30 January 2010 55 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Transaction Code: OVA2

Define an incompleteness procedure ZS Titan Standard Order

Atos Origin 30 January 2010 56 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define fields for checking incompleteness in Sales Order

Define an incompleteness procedure ZD Titan Debit Memo

Atos Origin 30 January 2010 57 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define fields for checking incompleteness in Debit Memo

Define an incompleteness procedure ZR Titan Credit Memo

Atos Origin 30 January 2010 58 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define fields for checking incompleteness in Credit Memo

Define an incompleteness procedure in Sales-Item

Atos Origin 30 January 2010 59 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define an incompleteness procedure ZV Titan Value Item

Define fields for checking incompleteness in Sales-Item

2.13 Assign procedures to the sales document types

IMG Sales & Distribution Basic Functions Log of Incomplete Items


Menu Path
Assign Incompleteness Procedures Assign procedures to the sales document
types
Transaction Code: VUA2

Atos Origin 30 January 2010 60 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 61 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Assign incompleteness procedures from 2.13 to sales document types

2.14 Assign procedures to item categories

Menu Path IMG Sales & Distribution Basic Functions Log of Incomplete Items
Assign Incompleteness Procedures Assign procedures to item categories
Transaction Code: VUP2

Atos Origin 30 January 2010 62 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Assign incompleteness procedures from 2.13 to item categories

2.15 Define Sales Document Types

The sales document types represent the different business transactions in sales, such as inquiry processing,
quotation processing, sales order processing and claim processing.

Menu Path IMG Sales & Distribution Sales Sales Documents Sales Document
Header Define Sales Document Types
Transaction Code: VOV8

Atos Origin 30 January 2010 63 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

There are 3 Sales Order Types used for Titan (ZCR, ZDR, ZOR) as below

Atos Origin 30 January 2010 64 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

The detail information of ZCR: Titan Credit Memo Request

Atos Origin 30 January 2010 65 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

The detail information of ZDR: Titan Debit Memo Request

Atos Origin 30 January 2010 66 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

The detail information of ZOR: Titan Standard Order

2.16 Define Number Ranges For Sales Documents

In this step, define the number intervals of the number ranges for sales documents.

Atos Origin 30 January 2010 67 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

When creating a sales document, a unique number is assigned which identifies the sales document. The
number comes from the number range which is provided for the document type.
There are two possible types of number assignment:
Internal number assignment
The SAP System automatically assigns a consecutive number from the defined number range.
External number assignment
You specify a number from the external number range.

Menu Path IMG Sales & Distribution Sales Sales Documents Sales Document
Header Define Number Ranges For Sales Documents
Transaction Code: VN01

Atos Origin 30 January 2010 68 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Number ranges of sales documents

Sales Order Types Description No. Number range from Number range to
ZOR Standard Order A0 411000000 411999999
ZCR Credit Memo Request A1 412000000 412999999
ZDR Debit Memo Request A2 413000000 413999999

Number ranges of billing documents (Invoice)

Billing Types Description No. Number range from Number range to


SS01 Titan Virgo Invoice A3 511000000 511999999
SS02 Titan Aries Invoice A4 512000000 512999999
SS03 Estonia Capital Inv A5 513000000 513999999
SS04 Titan Leo Invoice A6 514000000 514999999
SS05 Titan Mercury Inv A7 515000000 515999999
SS06 Titan Pisces Inv A8 516000000 516999999
SS07 Sino Venus Inv A9 517000000 517999999
SS08 Titan Chios Inv B0 518000000 518999999
SS09 Titan Gemini Inv B1 519000000 519999999
SS10 Titan Libra Inv B2 520000000 520999999
SS11 Titan Mars Inv B3 521000000 521999999
SS12 Titan Neptune Inv B4 522000000 522999999
SS13 Sino Ocean Inv B5 523000000 523999999
SS18 Wendelstar Intl Inv C0 528000000 528999999
SS19 Titan Ocean Inv C1 529000000 529999999
SS20 NAS Mgmt Inv C2 530000000 530999999
SS21 Neptune Assoc Inv C3 531000000 531999999
SS22 Far East Bnkrng Inv C4 532000000 532999999
SS23 Sino Mercury Inv C5 533000000 533999999

Number ranges of billing documents (Credit Note)

Billing Types Description No. Number range from Number range to


CS01 Titan Virgo CN C6 541000000 541999999
CS02 Titan Aries CN C7 542000000 542999999
CS03 Estonia Capital CN C8 543000000 543999999
CS04 Titan Leo CN C9 544000000 544999999
CS05 Titan Mercury CN D0 545000000 545999999
CS06 Titan Pisces CN D1 546000000 546999999
CS07 Sino Venus CN D2 547000000 547999999
CS08 Titan Chios CN D3 548000000 548999999
CS09 Titan Gemini CN D4 549000000 549999999
CS10 Titan Libra CN D5 550000000 550999999
CS11 Titan Mars CN D6 551000000 551999999
CS12 Titan Neptune CN D7 552000000 552999999
CS13 Sino Ocean CN D8 553000000 553999999
CS18 Wendelstar Intl CN E3 558000000 558999999
CS19 Titan Ocean CN E4 559000000 559999999
CS20 NAS Mgmt CN E5 560000000 560999999
CS21 Neptune Assoc CN E6 561000000 561999999
CS22 Far East Bnkrng CN E7 562000000 562999999
CS23 Sino Mercury CN E8 563000000 563999999

Atos Origin 30 January 2010 69 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Number ranges of billing documents (Debit Note)

Billing Types Description No. Number range from Number range to


DS01 Titan Virgo DN E9 571000000 571999999
DS02 Titan Aries DN F0 572000000 572999999
DS03 Estonia Capital DN F1 573000000 573999999
DS04 Titan Leo DN F2 574000000 574999999
DS05 Titan Mercury DN F3 575000000 575999999
DS06 Titan Pisces DN F4 576000000 576999999
DS07 Sino Venus DN F5 577000000 577999999
DS08 Titan Chios DN F6 578000000 578999999
DS09 Titan Gemini DN F7 579000000 579999999
DS10 Titan Libra DN F8 580000000 580999999
DS11 Titan Mars DN F9 581000000 581999999
DS12 Titan Neptune DN G0 582000000 582999999
DS13 Sino Ocean DN G1 583000000 583999999
DS18 Wendelstar Intl DN G6 588000000 588999999
DS19 Titan Ocean DN G7 589000000 589999999
DS20 NAS Mgmt DN G8 590000000 590999999
DS21 Neptune Assoc DN G9 591000000 591999999
DS22 Far East Bnkrng DN H0 592000000 592999999
DS23 Sino Mercury DN H1 593000000 593999999

Number ranges of billing documents (Cancellation)

Billing Types Description No. Number range from Number range to


ZS1 Cancel Inv./Debit Memo H2 601000000 601999999
ZS2 Cancel Credit Memo H3 602000000 602999999

2.17 Define Order Reasons

Order reasons describe the reasons which led to an inquiry, quotation or order.
When processing a sales document, you can specify the order reason in the overview at header level. It then
applies to all the items.

Menu Path IMG Sales & Distribution Sales Sales Documents Sales Document
Header Define Order Reasons
Transaction Code: SPRO

Atos Origin 30 January 2010 70 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

2.18 Define Item Categories

Item Category is characteristic that defines sales-relevant features of document items. The item categories
that are contained in the standard SAP R/3 System together with the sales document types represent the
usual business transactions.

Menu Path IMG Sales & Distribution Sales Sales Documents Sales Document
Item Define Item Categories
Transaction Code: SPRO

Atos Origin 30 January 2010 71 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

There are 3 item categories for Titan (ZG2W, ZL2W, ZSER) as below

Atos Origin 30 January 2010 72 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

The detail information of item category ZG2W

Atos Origin 30 January 2010 73 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

The detail information of item category ZL2W

Atos Origin 30 January 2010 74 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

The detail information of item category ZSER

2.19 Assign Item Categories

To specify which item categories the system proposes during document processing for each sales document
type and item category group

Menu Path IMG Sales & Distribution Sales Sales Documents Sales Document

Atos Origin 30 January 2010 75 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

 Item Assign Item Categories

Transaction Code: SPRO

Assign item categories from 2.18 to sales order types and item category group as below

2.20 Define Reasons For Rejection

Reason for rejection describes why an item in a sales document was rejected.
When processing a sales document, you can enter the reason for rejection by item in the overview for the
reason for rejection.

Menu Path IMG Sales & Distribution Sales Sales Documents Sales Document
Item Define Reasons For Rejection
Transaction Code: SPRO

Atos Origin 30 January 2010 76 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

2.21 Copy Control: Billing Document to Sales Document

Copy Control is a method to specify for a particular sales document type, which document type is to be
assigned to copied reference documents, and which item categories or schedule line categories are to be
copied.

Menu Path IMG Sales & Distribution Sales Maintain Copy Control for Sales
Documents Copy Control: Billing Document to Sales Document
Transaction Code: VTAA

Atos Origin 30 January 2010 77 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

When creating Credit Memo Request or Debit Memo Request, user can copy data from reference Billing
Document (Invoice)
The configuration of copying control: Billing Document to Sales Document need to be maintained as below

Billing types (SS01-SS13, SS18-SS23) can be copied to sales order type ZCR as below

Atos Origin 30 January 2010 78 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 79 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 80 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Billing types (SS01-SS13, SS18-SS23) can be copied to sales order type ZDR as below

Atos Origin 30 January 2010 81 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 82 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 83 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

2.22 Define Billing Types

Billing Type is a control for the processing of invoices, credit memos, debit memos and cancellation
documents.

Menu Path IMG Sales & Distribution Billing Billing Documents Define Billing
Types
Transaction Code: VOFA

Atos Origin 30 January 2010 84 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define Billing type CS01:Titan Virgo CN

Atos Origin 30 January 2010 85 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Detail information of CS01: Titan Virgo CN

Atos Origin 30 January 2010 86 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 87 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Do the same method for Billing type CS02-CS13 and CS18-CS23

Atos Origin 30 January 2010 88 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define Billing type DS01:Titan Virgo DN

Atos Origin 30 January 2010 89 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Detail information of Billing type DS01:Titan Virgo DN

Atos Origin 30 January 2010 90 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Do the same method for Billing type DS02-DS13 and DS18-DS23

Atos Origin 30 January 2010 91 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define Billing type SS01:Titan Virgo Invoice

Atos Origin 30 January 2010 92 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Detail information of Billing type SS01: Titan Virgo Invoice

Atos Origin 30 January 2010 93 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Do the same method for Billing type SS02-SS13 and SS18-SS23

Define Billing types ZS1 Cancel. Inv/Debit Memo, ZS2 Cancel of Cred. Memo

Atos Origin 30 January 2010 94 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Detail information of Billing type ZS1 Cancel. Inv/Debit Memo

Atos Origin 30 January 2010 95 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 96 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Detail information of Billing type ZS2 Cancel of Cred Memo

Atos Origin 30 January 2010 97 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

2.23 Maintain Copying Control For Billing Documents

Specify for a particular billing type which document type is to be assigned to copied reference documents
and which item categories are to be copied.

Menu Path IMG Sales & Distribution Billing Billing Documents Maintain Copying
Control For Billing Documents
Transaction Code: VTFA

Atos Origin 30 January 2010 98 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 99 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Define copying control: Sales document (ZOR) to billing document (SS01)

Atos Origin 30 January 2010 100 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 101 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Maintain the same method for copying control: Sales document (ZOR) to billing document (SS02-SS13) and
(SS18-SS23) also

Define copying control: Sales document (ZCR) to billing document (CS01)

Atos Origin 30 January 2010 102 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 103 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Maintain the same method for copying control: Sales document (ZCR) to billing document (CS02-CS13) and
(CS18-CS23) also
Define copying control: Sales document (ZDR) to billing document (DS01)

Atos Origin 30 January 2010 104 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Atos Origin 30 January 2010 105 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Maintain the same method for copying control: Sales document (ZDR) to billing document (DS02-DS13) and
(DS18-DS23) also

Atos Origin 30 January 2010 106 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

3 LOGISTICS GENERAL

3.1 Assign Update Group at Item Level

Assign the business events of an update group on item level.

Requirements
Sales areas have to be created.
Statistics groups have to be defined and allocated.

IMG Logistics General Logistics Information System Logistics Data


Menu Path
Warehouse Updating Updating Control Setting Sales and Distribution
 Update Group Assign Update Group at Item Level
Transaction Code: OVRP

Atos Origin 30 January 2010 107 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Assign Update Group at Item Level for sales organization SS01-SS13, SS18-SS23 as below

3.2 Assign Update Group at Header Level

Assign the business events of an update group on header level.

Requirements
Sales areas have to be created.
Statistics groups have to be defined and allocated.

IMG Logistics General Logistics Information System Logistics Data


Menu Path
Warehouse Updating Updating Control Setting Sales and Distribution
 Update Group Assign Update Group at Header Level
Transaction Code: OVRO

Atos Origin 30 January 2010 108 of 109


Titan Business Blueprint - <Module>
Version: < Draft > Doc. No.: < document number > SD-Configuration document

Assign Update Group at Header Level for sales organization SS01-SS13, SS18-SS23 as below

Atos Origin 30 January 2010 109 of 109