SAP SOLUTION MANAGER

É a plataforma central de suportes e serviços p/ a implementação e operação das soluções

SAP.

IMPLEMENTATION
Functional Implementation
Technical Implementation
Implementation of Operations

OPERATIONS

Services for Operations

Solution Monitoring
Support Desk

O SAP Solution Manager fornece ferramentas para o mapeamento dos requisitos técnicos
e funcionais, permitindo desenhar e documentar uma solução aderente aos negócios da
empresa, envolvendo soluções SAP e não SAP.

ETAPAS DE IMPLEMENTATION

1 - Project Preparation
- Planejamento
- Divulgação p/ Empresa
- Início Oficial

2 - Business Blueprint
- Conhecer a Organização
- Desenhar conceitualmente
- Emititr o Business BluePrint

3 - Realization
- Configurar testes
- Desenvolver os programas necessários
- Executar os testes
- Encerrar o material de treinamento

4 - Final Preparation
- Testes de Sistemas
- Treinamento de usuários finais
- Transportes, cargas de dados
- Fechamento de sistemas legados

5 - Go Live & Support

- Entrar em produção
- Manter o suporte p/ o sistema produtivo
- Encerrar oficialmente o projeto

OPERATIONS

- (SMR) Solution Manager Review Service

- Eally Watch Alert - Analisa os componentes de uma solução p/ determinar
como aumentar a performance
- Sistem Monitoring - Monitoração técnica da solução

- SAP Service Desk - Gerenciamento central de chamados / mensagem p/ todas

as soluções SAP e não SAP. Pode ser usado durante a implementação.

SAP GUI - GRAPHICAL USER INTERFACE (TELA DE APRESENTAÇÃO)

Pode conter ambiente produtivo, outro para testes, desenvolvimento ou treinamento.

Tecnicamente eles são totalmente independentes dos demais, mas podem quando
configuradas trocar informações entre si.

CLIENT - É uma unidade independente no sistema. Os mandantes possuem seus

próprios ambientes de dados e por isso possuem seus próprios dados mestres, dados
transacionais e parâmetros de customizing específicos.

SD - PROCESSO DE ORDEM DE VENDAS

É realizado através de documentos agrupados em 4 categorias:

- Doc. Pré - Vendas, Solicitações e Cotações

- Contratos Básicos, Como Contratos e Programas de Remessas
- Ordens de Vendas
- Reclamações, remessas gratuita, solicitações de notas de crédito/débito e
devoluções.

Estrutura do documento de vendas possui:

Cabeçalho, Item e Divisão de Remessa

Divisão de Remessa

Define para um item de venda as informações necessárias para as remessas, tais como
quantidade, data de remessa e quantidade confirmada.
FONTE DE DADOS DO DOCUMENTO DE VENDAS

Possíveis fontes são:

- Dados Mestres (Mestre de clientes, Materias, Condições)

- Dados existentes do documento (O centro fornecedor do nível de ítem como base para
determinar o local de expedição)
- Customizing - Ex. Tipo de doc. de venda, bloqueio do fornec. cond, de expedição -
Determinação de valores
- Controles efetuados - Exemplos : Avaliação das diferentes fontes de informação
durante a determinação do centro.

INFO SOBRE DOCUMENTOS DE VENDAS

Ao exibir ou modificar um documento de vendas é possível verificar algumas

informações importantes.

- Fluxo de documentos
- Síntese de Status
- Log de dados Incompletos
- Exibição de modificações

" O doc. contábil é um documento subsequente indireto do fornecimento pois ocorre após
o faturamento."

REGISTRO MESTRE DE CLIENTES (FI)

O registro mestre além de conter dados que controlam a maneira como as transações
contábeis são registradas e processadas pelo sistema, inclui todas as informações sobre
um cliente com o qual é necessário para manter relações de negócios.

É dividido em 3 Segmentos:

Dados Gerais (Nome do cliente, Endereço, tel, fax)

Dados da Área de Vendas (Relevantes à área de vendas)
Dados da Empresa (Relevantes à Área de Finanças)
Ex.: Dados de Adm. de Conta.
Dados de Cobrança
Dados de Correspondência

Uma transação comercial somente poderá ser faturada pela área de Vendas &
Distribuição depois que todos os segmentos de cadastro de clientes tenham sido criados.
PARCEIROS DE NEGÓCIOS "Específicos p/ fornecedores e clientes.

Todas as funções que uma pessoa física ou jurídica pode assumir, são apresentadas pelos
parceiros de negócios no sistema. Utilizados p/ definir os Direitos e as responsabilidades
de cada parceiro de negócio.

BLOQUEIO DE CONTA DO CLIENTE

Bloqueio de Ordem
Bloqueio de Fornecimento
Bloqueio de Faturamento

ELIMINAÇÃO DE UM REGISTRO MESTRE DE UM CLIENTE

- O cliente não pode conter movimentação no mês atual da eliminação

- Deve ser marcado para eliminação no Registro mestre
- É necessário bloquear um cliente antes de marcá-lo para eliminação.

COTAÇÕES PRÉ-VENDAS

As cotações podem ser exibidas em uma lista

Pode-se tirar uma lista de cotações dos últimos 6 meses.
Não é necessário identificar o código do material.

Estrutura do documento de cotação é igual a estrutura de uma ordem.

Pode ser criada com referência, como um documento inicial e a partir de um contato
comercial.

Uma cotação pode ser referenciada até o montante completo ou até que alcance a data
de validade.

ORDEM DE VENDA

É um acordo contratual entre org. de vendas (empresa) e um emissor da ordem (Cliente)

sobre o fornecimento de produtos ou prestação de serviços com preços, qtd e prazos
definidos.

Cada processo de venda possui um tipo de documento específico no Sistema.

Durante o processamento o Sistema executa algumas funções básicas.

- Verificação de disponibilidade do material

- Programação da Expedição
- Transf. de Necess. p/ o MRP
- Cálculo de Preços e impostos
 - Verificação de limites de crédito
- Criação de documentos impressos

É possível criar uma ordem de venda de uma cotação, contrato, uma ordem, um
programa de remessa, um documento de faturamento.

É possível modificar dado de itens individuais contidos na ordem ou efetuar

modificações rápidas.

É Possível bloquear as ordens de vendas para funções subseqüentes.

Nas ordens do cliente é possível bloquear transações que envolva os processos de

Expedição, Faturamento.

Você pode definir um bloqueio de faturamento no cabeçalho do doc. e relacioná-los

aos ítens.

Motivo de Recusa - Se o cliente desistir de comprar algum item, você pode atribuir um
motivo de recusa para cada um desses itens.

Ficha de clientes - Ajuda na criação do doc. ao exibir diversas informações relevantes

sobre o cliente.

Tipos de Ordens Especiais

Venda a vista
Venda Imediata
Processamento em Background

PROGRAMA DE REMESSAS

É um contrato básico realizado com o cliente que contém as quantidades previstas e

datas de fornecimento.

Estrutura do documento assemelha-se aos outros documentos de vendas.

É possível definir sugestão de embalagens p/ um programa de remessas (Itens).

Só estará concluído quando não existirem mais ítens a serem fornecidos.

CONTRATO

Os contratos básicos simplificam os processos empresarias para os parceiros de uma

transação comercial.
 Documentos.
Contratos em qtd
Contratos em valor
Contratos de serviços

Não contém uma programação de datas

O documento que ativa um contrato é chamado de solicitação de remessa. (Release

Order).

RELATÓRIOS DE ANÁLISES DE VENDAS E DISTRIBUIÇÃO

É um programa executável que lê o banco de dados, avalia-os e lança os resultados s/

efetuar quaisquer modificação.

SIS = Sistema de informação de vendas e Distribuição.

- Listas e Relatórios

SIS - É uma ferramenta flexível que permite coletar, consolidar e utilizar dados,
provenientes do processamento de vendas e distribuição.

Estruturas de Informação

São as tabelas de Estatísticas especiais contendo dados transacionais de diferentes

aplicações.
Contêm três tipos básicos de informação:

• Característica
• Unidade de período
• Índices

Todas as análises podem ser gravadas

O Sistema possui análise Standard e Análise Flexível, a fim de atender as necessidades

do usuário.

ADMINISTRAÇÃO DE VENDAS

Visão geral de determinação de preços

Os dados de condição de preço são transferidos para os registros que depois alimentarão
os documentos de faturamento.

A configuração da técnica de cond. é definida pelo Adm. do Sistema.

São elementos de preço no processamento de ordem:

Preços / Sobretaxas e deduções / Custo de Frete / Impostos

Registro de condições de preço

O esquema de cálculos de preços define os tipos de condição válidas para a determinação

de preços.

Elementos da técnica de condições:

• Esquema de cálculo
• Tipo de Condição
• Seqüência de Acesso
• Tabela de Condição
• Registro de Condições

O Objetivo do registro de condição é gravar e recuperar dados de determinação de

preços no sistema.

É possível fazer estipulações p/ definir ou provocar um plano geral de Marketing para

uma linha de produtos p/ um determinado período.

VENDAS E DISTR.

ORDENS EM ATRASO

Uma ordem não está totalmente confirmada se a data da remessa de um item não puder
ser mantida.

(ATP) - Através dele se atribui um estoque disponível para atendimento (Available to

promise) as quantidades pendentes da ordem.

O ATP serve para processar ordens em atraso e realocar ou distribuir novas

produções.

EXPEDIDOR DA MERCADORIA

Visão Geral da Expedição

No processamento da expedição você cria o documento de remessa para retirar o

material do depósito, vc faz o picking e qdo o material deixa o depósito, vc lança a saída
de mercadorias.
Documento de Entrega

Fala do documento de remessa.

Picking é o processo de separação de mercadorias p/ entrega ao cliente, com atenção
especial às datas e quantidades.

O documento de entrega é a base p/ o lançamento de saída de mercadorias.

O documento não pertence a vendas e distribuição embora seja uma atividade de

vendas, Pertence à MM e FI.

Assim que as mercadorias saem da empresa, a atividade empresarial de expedição é

considerada encerrada.

VISÃO GERAL DE FATURAMENTO

Das funções do faturamento uma muito importante é a integração com a contabilidade

financeira.

Quando o usuário cria o doc. de faturamento, os documentos de Contab.Financ. (FI) e

da Contabilidade de Custos (CO), são criados automaticamente.

A emissão da nota fiscal e o lançamento nos livros, também ocorrem automaticamente.

Solution Manager

É o ambiente de gestão de soluções SAP. Gerencia e auxilia na atualização, implantação

de versão.

Tem 6 conceitos importantes que um consultor de SD deve saber. São eles:

1. Organizational Structure
2. Document Type
3. Item Category
4. Schedule Line category
5. Copy Control
6. Condition Technique

Um documento de vendas sempre está atribuído a uma Sales Area.

Client - Is in organizational terms, an independent unit in the system - Instalação

completa do SAP

SAP recomends at least 3 environments:

Development QAS PRD
Ambiente de P&D Ambiente de teste Ambiente Produtivo

O client 100 e 110, estão na mesma instance. Automaticamente o client 100 atualiza o
110 ou vice-versa.

A unidade 220 é a unidade de teste p/ ir p/ o request.

As requests são liberadas pelo consultor p/ ser realizado o teste no QAS.

ESTRUTURA DE VENDAS E DISTRIBUIÇÃO

Uma Company Code pertence ao módulo de FI.

Uma Company Code pode ter várias org. de vendas, várias organizações de vendas
podem ter somente uma company code.

Um documento de vendas sempre está atribuido a uma sales area.

You need at least one sales organization to use sales and distribution functions in the
system.

Uma organização de vendas é como uma empresa se organiza p/ vender, se através de

produtos, região, mercados, Etc.

A Division is used to group materials and services.

SAP Netweaver é a plataforma de integração de todas as soluções SAP. Que possibilita

integração entre ambiente complexos e heterogeneos.

Um Mandante pode ter várias empresas.

Uma Division está associada a uma Sales Organization.

Deve-se emitir balanço somente através de uma company code.

O Storage Location está associado a só uma plant.

You must assign a sales organization and distribution channel to a plant.

Shipping Point - Local pelo qual eu organizo a delivery (Local de Expedição)

Não Necessariamente significa um local (Não cai na prova)

É a maneira que eu organizo a minha expedição.

Área de Picking é onde eu separo o produto.

Remessa, fornecimento, entrega = Outbound Delivery

Sales Office and sales group são estruturas opcionais, ou seja, não são obrigatórios.

Sales office are assigned to a sales area.

As informações do cliente variam e podem variar por sales area

PROCESS OVERVIEW
PRE-SALES ACTIVITY

Transação VC01 (Pode-se disparar um mailing)

Uma Inquiri é uma solicitação de cotação.

Uma Company Code é a responsável principal em emitir Balanços e resultados.

Uma Organização de vendas é como a empresa ou Company Code se organiza p/

vender. É a principal unidade da área de vendas.

Um Canal de Distribuição, são as formas que Org. Vendas distribui as vendas. Está
associado à Sales Organization.

Uma Plant ou Centro, pode ser uma fábrica, ou filial. Precisa ser associado a uma
combinação da Org. Vendas e Canal de Distribuição. E associado unicamente a uma
Company Code. É essencial para determinar um Shipping Point.

Um Storage Location ou Depósitos, São Locais de Estoque dentro de uma Plant.

Uma cotação pode gerar várias ordens e várias ordens podem ser gerados por várias
cotações.

Porém existem regras de negócio.

Não se pode fazer o Goods Issue antes do Picking.

Fazer o Picking é uma ação e o documento é a Transfer Order.

The available check is performed at Procurement (Abastecimento - Verifica se tem

estoque disponível) in Sales order processing? Yes

Item Category, define o comportamento da condição / Negociação p/ o item.

Schedule Line = Divisão de Remessa.

Todo documento de venda tem que ter um tipo.

Todo item tem que ter uma categoria.

Todo Schedule Line tem que ter um Schedule line Category

O que diz para o Sistema o comportamento que o item tem que ter?

Item Category.

Quais São os Sales Document?

Cotation, Inquiry, Order.

Delivery e Billing documents possuem 2 Partes. Header and Item.

Não se pode criar um Outbound Delivery p/ 2 Shipping Points diferentes.

Eu não posso ter dentro de um delivery itens de shipping points diferentes.

After you posting goods Issue the delivery document is available at the billing due list.

Um Sales Group é ligado ou associado a uma área de vendas.

Através do SAP pode-se fazer a gestão do Pré-Sales.

O pricipal documento da Delivery é o Shipping.

Despois do Posting Goods Issue ele atualiza:

Stocks
Transfer of requirement
Doc. Flow
Billing Due List
Account Doc.

DADOS MESTRE - MASTER DATA

No customer material você pode juntar o cliente e o material.

Condition master Data.

Possui configuração flexível

Data Origin in Sales Document

Source of data includes, for example:

Customer Master Data

Material Master Data
Condition Master Data
Outputs
Customer / Material Master Data

Quem cadastra dados mestre é o usuário.

The Customer Master Groups data into three categories:

General data, Sales area data and Company Code data.

Tudo que está no General data, serve para qualquer empresa.

O cadastro do cliente p/ a Company Code deve ser realizado no FD01, pela área de FI.

A criação da Área de vendas, força a criar o cliente p/ vender p/ aquela determinada

área de vendas.

Quando ocorre uma mudança no cadastro de cliente o único dado que muda na ordem, é
o endereço do cliente.

Division é um atributo do material.

Quando não se pode misturar o grupo de produtos, você deve escolher uma division
diferente. Não pode ser Cross Division.

SALES DOCUMENT TYPE

O tipo de documento de venda influencia na categoria do item e nos demais

documentos.

Todo documento tem um tipo.

DETERMINAÇÃO DE PLANT

1 - Customer / Material information

2 - Ship - to - party - Customer Master
3 - Material master Data

PROCESS OVERVIEW

PRÉ-SALES ACTIVITY INCLUDES

 • Entering and tracking customer contacts
• Mailing Campaigns
• Answering Customer telefone queries
• Quotations
• Inquiries

Standard Orders normally contain:

• Customer and Material information

• Price information for all financial statement items
• Information about delivery dates and delivery quantities
• Information about Shipping processing
• Information about Billing

You can enter a sales order with many items in a single screen.

Throughout a procurement process step in sales and distribution, you can check the
availabiltity of the ordered goods and Transfer the requirements to materials
planning.

Shipping

Shipping processing in Sales and Distribution begins when you create the delivery
document.

The Delivery document, controls, supports and monitors numerous sub process
for Shipping processing.

You can create one or more outbound deliveries from the order - you can also combine
items from more than one order in an outbound delivery. But the orders must correspond
with the characteristics that are essential for the shipping process. (Shipping Point,
Delivery Date, Ship to Address.)

- (optional) picking and confirming (T.Orders)

- (optional) packing
- (optional) planning and monitoring of transport (Shipment document)
- Posting the goods issue (goods issue documents)

You can not posting goods issue, without doing the picking.

The Goods issue Carrie Out five things in the system automatically.

• The quantity in Inventory management and the deliveries

requirements in material plan are updated.
 • The value change in the balance Sheet for inventory accounting is
posted
• The system creates further documents for financial accounts
• The Status in all relevants Sales Documents is updated.

BILLING DOCUMENT

Creating a billing document includes Copying information from the sales order and the
delivery document onto the billing document.

Functions of the Billing documents.

• Acts as the basis for creating invoices

• The billing document serves as a data source for financial accounting to
help you to monitor and process customer payments.
• The system can combine a member of outbound deliveries in one billing
document provided that they have the same characteristics, such as:

- Payer
- Billing Date
- Destination Country

SALES DOCUMENT STRUCTURE

A sales document Structure is divided in three levels:

Header, item and Schedule line.

Header - The data for the document header is valid for the entire document.

Items - Each item in the sales document has separate data. Each sales document can
contains several items.

Schedule Lines for line items - Schedule line contain delivery quantities and delivery
dates. They clearly belong to an item. The item can have several schedule line.

DELIVERY DOCUMENT STRUCTURE

A delivery document is grouped into two level: Header and Item

• Delivery doc. Header - The data for the document header is valid for the
entire document.
• Delivery doc. Item - Each item in the delivery document contains its own
data.
Picking

You create a transfer order for an outbound delivery. A Transfer order is generated
for a Warehouse number. And during this process, only the deliveries that are necessary
for picking are taken into account.

BILLING DOCUMENT STRUCTURE

A billing document is grouped into two levels:

Header and item

Is the same role of delivery document.

Effects of Billing document:

• The Status in all related sales, delivery and billing documents is
updated.
• The sales statiscs in the sales information system are updated
• The data regarding the consumption of the customers credit
limit is updated.

UNIT 4 - SUMMARY

Wich are the data Origin in Sales Document?

• Customer Master Data

• Material Master Data
• Customer / Material Master DAta
• Output Master Data
• Condition Master Data

CUSTOMER MASTER DATA

The customer master Groups data into 3 categories:

GENERAL DATA - Relevant for sales and accounting valid for all
organizational units

SALES AREA DATA - Relevant for Sales organization, Distrib. Channel and
Division.

COMPANY CODE DATA - Relevant for accounting valid for Company Code

The Cstomer master includes all data necessary for processing orders, deliveries,
invoices and customers payments.
Customer Master in General Data

The General data is maintained independently of the organizational units.

By changing the Customizing settings, you can hide certain fields on a tab page or make
them required entry fields.

TAB PAGES

• ADDRESS
• CONTROL DATA
• PAYMENT TRANSACTIONS
• MARKETING
• UNLOADING POINTS
• EXPORT DATA
• CONTACT PERSONAL

Customer Master
Sales Area Data

Sales, Shipping, Billing document, Partner functions:

You can maintain the sales area data in various ways, deppending on the sales area.
(Sales Org., Distrib. Channel., Division)

Wich are the mandatory partner functions in the Customer Master necessary for
processing a Sales Order?

• Sold to party
• Ship to party
• Payer
• Bill to Party

Customer Master
Company Code Data

The company code data in the Customer Master comprises the following tab pages:

Account Management, Payment transactions, Correspondence Insurance.

- Effects of changes in the Customer Master

When you change a master record after having used it to create documents (orders,
deliveries, billing documents and so on)

The Changes do not affect the documents already created.

The address in the customer master, however, is an exception.

MATERIAL MASTER DATA

The material master comprises the following areas:

1. Basic data 1 - Relevant, for all areas valid for all organizational units
2. Sales - Sales Organization - Relevant for Sales, valid for sales
organization and Distr. Channel
3. Sales General Plant: Relevant for Sales - Valid for Delivering Plant
4. Purchasing - Relevant for materials Management, valid for plant
5. Further - Relevant for construction requirements planning accounting,
and so on.

Division - Specific and Cross Division Sales

Cross Division Sales

You can use this kind of processing to enter multiple materials with various divisions in
a Sales order:

Na Sony os documentos de vendas em sua maioria são Cross Division, a área de vendas
do documento será selecionado com base no cliente e cada item terá sua division. Para
fins estatíticos eu posso decidir se será mantida a Division do Item ou a Division do
Documento.

You can control the following in Customizing, according to the sales document type.

• It is possible to enter multiple materials with various divisions for an order

• The way the system is to respond (with or without warning message)
• Wheter the divisions on item level is copied from material master record
or wheter the division in the document is also copied into the item.

Division: Specific Sales Area

You can not use this kind of processing to enter multiple materials with various divisions
in order.

This can be controlled in Customizing, according to the Sales Document Type

CUSTOMER - MATERIAL INFO RECORD

(VD51 ou VC51)
The Customer-Material Information record is used for storing Customer-specific material
data.
If a Customer-Material info record has been defined for a customer and a material, the
default values take priority over the values in the customer or material Master. When a
document is processed (Order, delivery, and so on).

You can also use to the following data:

• Cross-reference from your customer's material number to your material

number on the customer material description.
• Specific Shipping information for this customer and material.

CONDITION MASTER DATA FOR PRICING

The condition master data includes:

• Prices (Material Price, Price List, Customer Specific, Other)

• Surcharges and discounts (For the customer, material, price group,
material group
• Freights (Freight incoterms 1 + 2 other)
• taxes

In Customizing you can control the data on wich prices, surcharges and discounts,
freights or taxes can be dependent.

• Condition Master Records in Pricing

- You can have a percentage, a quantity-dependent, etc. depending
on the condition type.
- You can restrict a price agreement to a certain period.
- You can maintain values within a condition record (according to
a scale, There is no limit to the number of scale levels.

• Pricing in Sales Orders

- Prices, Surcharges, discounts, freights, and taxes conditions can
be found automatically using the automatic pricing function. You can also
change these conditions manually.

- Pricing is carried out using the condition tecniche.

ADDITIONAL MASTER DATA

• OUT PUT
- Output is information that is sent to the customer via various
media, such as mail, EDI, or fax. Ex. The Printout of a cotation or an order confirmation.
 - Output determination as with pricing takes place using the
condition technique.

In the Output Master Data, you define the transmission medium, the time, and
the partner function for an output type.
- Output types includes quotations, orders confirmations, and
invoices.

INCOMPLETENESS CHECK (OVA2 - Transação)

- Incompletion Log (Available in the sales order and in the

delivery)
Each sales and distribution document contains data required for the document and for
further processing.

The system determines which field will be displayed in the incompletion log. If the user
does not complete them during sales order processing.

* You receive the incompletion log either, automatically when the data is saved, or by
choosing edit Incompletion log.

* In Customizing you can define wich fields shoud be part of the incompletion log.

COMMOM MASTER DATA - DISTRIBUTION CHANNEL

If you do not need the master Data (Customer / Material and condition master data) to be
differentiated accourding to distribution channels, you have to set up a representative
distribution channel.

You do it in Customizing.

COMMOM MASTER DATA - DIVISIONS

I s the same of the Master Data for Distr. Channel, however it applies to a division.

UNIT 5 - FUNCTIONS OF THE SALES DOCUMENT TYPE

Sales Document Type

- Standart Order
- Contract (QTD or VALUE)
- Cash Sales (Quando uma ordem automaticamente já cria uma delivery e
emite um boleto)
- Rush Order (É a mesma coisa mas não emite boleto)

- Free of charge delivery (Doação)

 - Returns
- Consignment Order
- Credit / Debit memo request

* Different business process can be identified and controlled by means of the sales
document type.

* The sale document type controls the sales documents. Similarly the delivery type can
be used to control the shipping documents and the billing type can be used to control the
billing documents.

Function of sales documents.

Depending on the transaction, certain functions are carried out automatically.

These functions can be activated or deactivated directly via the sales document type.

PLANT, SHIPPING POINT, AND ROUTE DETERMINATION

Plant Determination - Determining the delivering Plant automatically

- When processing an item, the system automatically attempts to determine the associated
delivering plant from the master data. The entry can later be changed manually.

Serch Strategy:

- First it checks within a Customer - Material info record.

- Second, Customer Master Record using the Ship-to-party
- Third, it checks in the Material Master Records
Without a plant, an item cannot normally be processed further.

SHIPPING POINT DETERMINATION

Shipping Point

The System tries to determine a Shipping point for every item to be delivered.
Using three fields:

• Shipping condition from the Sold-to-party

• Loading Group - in the sales-specific material data
• Delivering plant

Can be changed manually too.

Route Determination
The system tries to determine a route for every item to be delivered, using 4 fields as
search keys for determine the route automatically.

Normally defined in Customizing and Master records.

• The departure zone (In customizing for the Shipping Point)

• Shipping Condition from the sold to party
• Transportation Group - in the specific material data.
• Transportation Zone - In the general data for the Ship-to-party

Shipment Scheduling

In shipment and transportation scheduling, you define the time at which the receipt of the
goods at the customer can be acknowledged (confirmed delivery date)

Different lead times are taken into account:

The Preparation time > Loading time > Transportation lead time > and transit time.

The following data is used in Shipment Scheduling:

• Order date
• Material availability date
• Loading date
• Goods issue date
• Delivery date

Bacward Scheduling

The goal of shipment and transportation scheduling is to confirm a delivery date for a
material requested by a customer.

If the system confirm that the material is available using the two dates.

Forward Scheduling

If one of the two dates is before the order date confirmation of, the requested delivery
date, can not take place. The system attempts to determine the next possible date (forward
scheduling).

Two scheduling lines are generated for the sales line item:

• The date of the first corresponds the requested delivery date has no confirmed
quantity
 • The date of the second shows the confirmed date and the confirmed amont.

COLLECTIVE PROCESSING IN SALES AND DISTRIBUTION

Delivery Creation

To make shipping faster and easier, you can use the delivery due list to create more than
one Outbound delivery Simultaneosly.

This function can be used as follows:

• Online processing of the delivering due list

• Creating a Background job to be executed during off peack
hours.

The system controls the creation of outbound deliveries via the Shipping Point, the
Selection data (picking date) and other criteria grouped on various tab.

There are fields in Master Data and in the sales document where you can store customer
defaults for processing deliveries.

• If the customer requires Complete deliveries, the order should be

delivered in one single delivery.
• If the customer does not requires complete deliveries, you can
define a partial delivery agreement with the customer.
• If the customers allows orders to be combined, the R/3 system
combines ordens when create the delivery Due List.

COLLECTIVE PROCESSING IN PICKING

You can also introduce picking via collective processing. To do this, you can select a
worklist from all the Outbound deliveries ready for picking and create several transfer
order at the same time.

The system controls, the creation of transfer order via the Shipping point, the selection
data and other criteria.

Collective Processing for Posting Goods Issue.

- The system controls the posting of the goods issue via Shipping Point, the
Selection Date and ither criteria.

Collective Processing in Billing.

You can use a Billing Due list to process more than one billing document to current
simultaneosly.

Options:

Depending on the system setting, these can either be order items or Outbound delivery
items.

Worklists:

1 - The delivery list is used to process many sales document for outbound deliveries.

2 - The picking worklist creates transfer orders for picking.

3 - The goods issue worklist, for outbound deliveries will post goods issue, for many
deliveries.

4 - The billing due list is used to create invoices for outbound deliveries and orders.

Não tem processamento coletivo de ordens.

UNIT 6

AVAILABILITY CHECK IN THE SALES ORDER

An availability check in the sales order is carried out during sales order processing if:

• The material requires an availability check

• The availability check is set in Customizing for this transaction
• Availability is checked on the material availability date, working
Backwards from the customers requested delivery date.
• The system calculates the time required for picking, packing,
loading and transportating the goods.
• The availability check is carried out for the (delivering) plant at
item level, if you set up. Following sequence:

1. Customer-Material Information
2. Ship-to-party Customer Master Record
3. Material Master Record

Transfer of Requirements

The communication between sales and distribution and procurement is carried out
via requirements.

COMPLETE AND PARTIAL DELIVERIES

Any agreements you made with the customer about deliveries also affect the result of the
availability check.

O número máximo de entregas provenientes de uma ordem não podem ser

superiores a 9.

* The indicator for controlling complete/partial deliveries is proposed from the

customer master record.

* The proposal for the item level comes from the Customer-material info.

CONFIRMATION ON REQUESTED DELIVERY DATE

The availability check includes:

- Current Stock
- Planned Inward movements (Such as purchase order, requisitions, planned
order).
- Forecast outward movements (Such as existing sales orders, deliveries)

* The system executes at first a backward scheduling trying to confirm the date taking
in consideration the requested delivery date and the material availability date and then
to confirm the deliveries scheduling.

* The system uses delivering scheduling (forward scheduling) to calculate the

confirmation date for the possible available date.

BACK ORDER PROCESSING

An order item is backdated if:

• The quantity of an order item is not totally confirmed

• The required delivery date for an order item can not be kept.

There are two types of backorder processing:

• Manual with backorder processing (manually via list)

• Via rescheduling (Delivery priority)

Quando não se confirma o pedido para a data do cliente vira backorder.

TRANSPORTATION PROCESSING

1 Shipment document gera 1 shipment cost document

O que são os itens do shipment documents?

São deliveries.

* The shipment function is optional.

* You can use it to combine deliveries with the same transportation requirements such as
forward agent, destination route, or means of transport.

Normally you create a shipment before you post goods issue.

Creating Shipment Documents

Utiliza os outbound deliveries, pegando os itens que possuem a mesma data, o mesmo
destino.

Loading and Packing Shipments

Packing itens are assigned to the required means of transport (Truck, for example).

Unlike packing in the delivering, packing in the shipment can be carried out for several
deliveries.

Billing Shipment Costs to the Customers.

You can invoice the customer for shipment costs, wich are based on effective shipments
cost.

It appear as an additional entry in the customer billing document.

Connection to Financial Accounting

There are connections with an Accounting document

UNIT 7
MAKE TO ORDER

Sales support tasks

You can implement the following activities in the sales support system.

• Prepare information about customers, prospective customers, contract people,

competitors, and their products.
• Manage Sales Activities
• Carry out direct Mailing Campaigns
• Direct Acces to the (SIS) Sales Information System

Pre-Sales Documents

Inquiries and Quotations

Document Flow in the Pre Sales Phase

Inquire Quotation Order

Qtd 4 Qtd 3 Qtd 2
1) 2) 3)

1) Any quantity gives completely referenced status to an Inquiry.

2) A quotation needs to be totally referenced to have a complete status. In this case The
quotation is partly referenced (3) to the order (2).

Item Categories

Classifica um item de um documento quanto ao seu comportamento.

By using an item category, the system can process a material differentely in each sales
document type.

The item category in the sales document is defined using the sales document type and
the material.

An item category can influence, for example:

• Whether the system runs automatically pricing

• Whether the item appears on an invoice
• Whether the item appears on a delivery
 • Which fields are recorded in the incompletion log, if they were not entered in the
order
• Which partner functions belong to the item
• Which text types belong to the item
• Whether you can create schedule lines for the item.

Make to order

Make to order production is chareacterized, by the fact materials are not stored in the
warehouse, but produced specially for a particular sales order.

Make to order - Production without Assembly Processing

Need to generate dependent requirements.

Make to order - Production with Assembly Processing

You just need a one level (bill of material explosive) and you do not need to generate
dependent requirements.

Cost Manager per item

In Sales order processing, the costs and sales revenue for a sales order are collected in a
controlling object for that item and setted in a profitability analysis.

Packing - During packing, delivery items can be assigned to packaging materials. The
handling units created by this can be packed in additional packaging materials.

Delivery from sales order stock

• Goods issue for delivery of an individually produced material reduces the sales
order stock.
• Sales order stock is a special stock which can be used only for the special sales
order

Complants Processing

* Para documentos de crédito não tem deliveries.

• Credit and debit memo requests can be created with reference to a billing
document or a sales order.
• Both contains a Billing Block
• When the billing documents are posted (credit / debit memo) the required
accounting documents are generated automatically.

O sistema entende que é um item de crédito devido ao Item Category + Document Type.
Approving a Credit Memo

• The return, credit memo request, debit memo request and invoice correction
request documents, contain a billing block.
• Credit memo request é um sales document type.
• Credit memo é um Billing Document.

Returns

• Siginifica que alguma coisa voltou fisicamente.

• Item Category plus document type determines wether the material will enter in
the stock.
• Pode se fazer antes ou depois de dar o crédito.
• Can be created with reference to a billing document or a sales order.
• For evaluation purposes, you must enter an order reason.
• Contains automatic billing block.

Processing Invoice Corrections - Não existe no Brasil.

The invoice correction is used to correct quantities or values for which the customer
has already been billed.

"Is always created with reference to the billing document only."

CANCELLING A BILLING DOCUMENT

O cancelamento é um novo documento de faturamento c/ valor e quantidades invertidos.

A billing document may have to be cancelled, for example if the payment terms or
address of the payer have changed.

• New accounting document are generated.

UNIT 9 - ANALYSES FOR SALES AND DISTRIBUTION PROCESS.

SOURCES OF SD INFORMATION

• The SIS belongs to Sales and Distribution

• With SIS you can compress data from sales documents to obtain information
which will help you make strategic business decisions.
• SAP provides list fuctions to create worklists in sales, delivery, picking, and
billing.
• With Standard and Flexible analysis.
LISTS AND REPORTS

Lists fall into two categories:

- Backorders and open quotations - Online lists

* Allow you to check and change documents

- Delivery Due List, Billing Due List - Worklists

* Display activities that need to be processed
* Allow you to organize tasks into efficient works units

DOCUMENT FLOW

The document flow is another online list function. It displays the history of related
documents.

It shows all documents associated with the sales order.

O SIS é uma parte dos LIS (Logistic Information System)

LIS - Is used to review and analyze key figures throughout the entire Logistics area in
the system.

The following information systems are available in Logistics:

• SIS (Sales Information System)

• Purchis (Purchasing Information System)
• INVCO (Inventory Controlling)
• TIS (Transportation Information System)
• SFIS (Shop Floor Inf. System)
• QMIS (Quality Management Inf. System)
• PMIS (Plant Maintenance Information System)

DATA WAREHOUSE CONCEPTS

Tudo que se faz no SAP, está armazenado no OLTP, it is an environment.

You can also update data from other systems in LIS.

LIS AGGREGATES and stores this data in the data warehouse. The data can be
aggregated with regard to quality or quantity:

- QUANTITATIVE reduction by aggregation at period level

- QUALITATIVE reduction by selection of the key figures.
COMPOSITION OF INFORMATION STRUCTURES

The SIS is based on information Structures that comprise three basic types of
information:

• Characteristics (SAles Org. / Customer)

• Period Unit (Week / month)
• Key Figures (Incoming Orders / Invoiced Sales / Delivery Quantities

STANDART ANALYSIS

The analysis is based on the information structures. First, select the required data scope
depending on the characteristics and period of the information structure.

• All analyses can be archived

The evaluation results, can also be:

• Printed
• Dowloaded as a file to your local PC
• Dowloaded to a spreadsheet program
• Sent to one or more employes

FLEXIBLE ANALYSES

Flexible analyses in LIS allow you to determine which data in which format is combined
to create an individual report.

SAP BW ARCHITECTURE

SAP Business Information Warehouse allows you to view the transaction oriented OLTP
and the analyses oriented OLAP environment together.

Allows you to integrate SAP and non SAP system as a source data.

ENTERPRISES STRUCTURES IN SALES AND DISTRIBUTION

Objectives of Org. Structures in the SAP System

• Achieve flexibility in representing complex corporate structure.

• Distinguish between views in Logistic (Sales and Distribution)
• Adapt to changes in the corporate structure.
• Process data across company codes.
INTEGRATION OF SALES IN FINANTIAL ACCOUNTING

• All Organizational units within a client are subject to one business control.
• You can use the company code and business area to represent a group from a
financial accounting perspective.
• Each company code represents an independent accounting unit. Several
company codes can use the same chart of accounts.

A Business Area is a separate business unit for wich cross-company code internal
reporting can be carried out. Using this Organizational unit is optional.

• You use Business area if you want to calculate profit and loss
statements independently of the company code.

SALES ORGANIZATION

• Each Sales Organization represents a selling unit as a legal entity.

• Each Sales Organization has its own Master data, for example, it's own
customer and material master data as well as condition records.

DISTRIBUTION CHANNEL

• Can be set up according to your company's market strategy or internal

organization.
• You can vary the master data relevant to sales for each sales
organization and distribution channel.

DIVISION

• A broad product range can be divided into divisions.

• You can make Customer-Specific agreements for each division. For example
regarding partial deliveries or pricing.
• Within a division, you can carry out statistical analyses or device your own
marketing strategics.

SALES AREA

Is a combination of sales organization Distribution channel and division.

• Sales document, delivery document and billing documents are always assigned
to a sales area. Every sales process always takes in a specific sales area.
• The relevant Master Data can usually be maintaned explicity for each sales
area, for example:
 • Sales Material Master Data (The division is a general field of the material
master; as a result a material can only be assigned to one division.)

SALES OFFICE - Can be assigned to multiple sales area.

SALES GROUP - Is assigned to a sales office.

SALES PERSON - Is assigned to a sales office and group in the sales employee
Master record.

PLANT - Each plant is assigned to a unique company code.

For a plant to delivery goods to customers, it must be configured appropriately

as a delivering plant in sales customizing.

DELIVERING PLANT - A Delivering Plant must be assigned to a sales organization

and a distribution channel (distribution chain) in Customizing.

* One plant can be assigned to several distribution chains as the delivering plant. It
also can be assigned to several sales organizations.
* It is also possible for the delivering plant of a distribution chain to belong to a different
independent company code in the corporate group. (That is, the plant belongs to a
different company code to the sales organization. This is know as cross company
sales.

UNIT 11

SOURCES FOR DOC. DATA

Possible source of information are:

• Master Data - The system reads the master data defined for a Customer, a
material or a pricing condition.
• Existing Document Data
• Customizing - Defalt values for creating documents can be defined in
customizing.
• Hard-coded controls - Different information sources can be weighted using
controls hard -codes.

SALES ORDER ENTRY

• Each sales ordered is assigned to a unique sales area

• When you enter a sales order, you don't need to specify the sales area
immediately.
• The system automatically derives the sales area from the sold-to-party.
Proposing Order Data from Master Data

You can enter different types of Master Data in the SAP System. Such as information on
business partners materials, customer material, item proposals. bills of material,
prices, discounts and rebates, taxes freight, output and texts so on.

The system will frequently access the data during order processing.

BUSINESS PARTNERS FROM THE CUSTOMER MASTER

The essential business partners for sales transaction are sold-to-party, ship-to-party,
payer and bill-to-party.

- These business partners play various roles (called partner functions) in the business
process.
- When you enter a sales document you can also enter the ship-to-party instead of the
sold-to-party.

The system then determines the sold-to-party from the ship-to-party.

- If a sold-to-party cannot be determined, the system issues an error message in the

status bar.

PROPOSING ORDER DATA FROM THE CUSTOMER MASTER

• The business data in a sales document is taken from the master data records for
the different Business partners.
• Delivery address and control information are taken from the ship-to-parties master
record.
• The bill-to-party contains the address to which the invoice should be sent. This
address may be different from that of the payer.

Business Data - You can define business data (such as payment conditions, incoterms)
at document header level or for each item.
• You can decide in customizing for the Item category, wheter business data at
item level should be able to differ from business data at header level. You define
this option separately for each item category.

PROPOSING PLANTS AUTOMATICALLY

During it search the system checks several Master Data Records:

 1. Customer-Material info record
2. Customer Master for the Ship-to-party
3. Material Master Record

If there isn't a plant in the material master record the system will be unable to determine a
valid plant and it cannot determine any other document data.

SALES SUMMARY

Sales summary helps to create documents by displaying a variety of relevant information

about the customer.

OVERVIEW: CHANGING OF SALES DOCUMENT

Different options are available for changing document data:

• Fast change function (by item)

Allows you to change several - or - all items of a document at the same time.
• Changing of several documents
You can use the documents list to change Plant, currency, materials, and pricing in
several documents at the same time
• The essential characteristics of an item category decide:

- Whether business data in the item can be different of that of the

document header.
- Whether pricing applies to the item
- Whether and how an item is billed
- Whether the item refers to a material or wheter it is just a text item
- Wich incompletion log is used to check the item data

• You can define new item categories. To do this , you should always copy existing
item categories that have already been created, then change these to meet your
requirements.
• The delivery relevance is only for items without schedule lines. You could
indicate that a text item was relevant to delivery, for example.

CONTROLLING THE ITEMS IN THE SALES DOCUMENT

Every item in a sales document is controlled by means of its item category. These enables
you to:

• Use different item categories in different sales document types.

• Realize different business process for each item in the sales document
• You can configure the function of the item category according to your
requirements.
SUB ITEMS: You can assign an item to higher-level item if, for example, a customer
receives free goods for ordering a certain quantity of your product.

Other example for using subitems include the explosion of BOMS of service items in
sales documents.

ASSIGNING ITEM CATEGORIES TO SALES DOCUMENT TYPES

- Item categories are assigned to sales document types.

This assignment is influenced by:

• The Item category group from the material master record

• The usage for the item, wich in some case is set internally in the program.
• The item category of a higher-level item (in the case of a sub item)

BOM - BILL OF MATERIALS FOR A COMPUTER

Example a
Computer - You can store this structure in the systems a bill of materials. All the items
in the systems in the bill of material (BOM) that you want to control in the sales
document must be flagged as relevant for sales. If you create a BOM material with BOM
usage 5 (sales and distribution), all the items in the Bill of material will be automatically
flagged as relevant to sales.
• By makking the appropriate settings in Customizing for the item categories in the
sales document, you only need to enter the material number of the BOM.
• The BOM appears in the sales document as a structure with main items and sub
items.
• The individual item categories control what a bill of material can do in a sales
document.
• In Customizing, you define and assign item categories for the main and sub-items
of the Bom in the sales document.
• In Customizing, for item category, you control wich items are relevant to pricing
and how you want to implement requirement transfer.

CONTROLLING SALES DOCUMENTS - SCHEDULE LINE CATEGORIES

É determinado por ITEM CATEGORY + MRP TYPE

• The schedule line category is defined with a two character key. The first indicates
the sales process in wich the Schedule Line category is used.
• The second indicates what happens to the schedule lines within logistics

D= No inventory Management N = No MRP X= No inventory Managment with Goods

Issue P = Material requirements Planning.
Dialog Flow

Create with reference:

You can create a sales document with reference to a preceding document

from both the initial screen and during document processing. The process is
controlled using a uniform dialog box.

The dialog box contains the six tab pages for Inquiry, Quotation, Order,
Contract, Scheduling agreement and Billing document.

- You can create sales documents with reference to documents that already
exist.

COMPLETION RULE AND REFERENCE STATUS.

If you want to restrict the reference to an item (for example, only until the full
quantity in the preceding document has been referenced), set the appropriate
Completion rule in the item category.

The status of each item in the preceding document is updated separately,

depending on the completion rule of the item category.

If you enter a reason for rejection, the item receives “Completed” status.

DOCUMENT FLOW

A sales process is made up of the sequence of individual process steps recorded

as documents. This process chain is stored in the document flow.

They are updated for the overall document and for individual items.

COPYING CONTROL

A 1.º função do copying control é dizer o que é permitido. É função do consultor

de SD controlar isto.

In copying control, you determine wich document types can be copied to

another document type.

You determine the details of the copying procedure in copying control.

 • You set up copying control for header, item and schedule line level to
match the structure of your sales document.

Regras no nível do documento – Document Type.

Regras no nível do Item – Item Category
Regras entre documentos – Copying Control.

To control the copying procedure, at each level you create:

- Routines for data transfer
These routines control transfer of fields in the preceding document
- Copying Requirements
Here you define requirements that are checked when you create a
document with reference.
- Switches
There are switches for setting specific controls for each transaction.

- Tem que ter copying control de todos os documentos.

- O copying control fica no spro em cada relacionamento de documentos.

RUSH ORDERS

Rush orders and cash sales are sales document types that are used in the
sales from plant process or for when the customer needs to pick up their goods
immediately from the warehouse.

When you create a rush order, the systems automatically and immediate creates
a delivery of type LF.

CASH SALES

When you save a cash sales the system automatically creates a delivery and
prints a document that can be given to the customer as an Invoice. (Porém ele
não faz o Goods issue) que deverá ser feito em BackGround por algum
programa)

No cash sales diferentemente do Ruch order tem um Output Type.

Cai na prova:
No processo de Cash Sales quando eu for fazer o Billing, vai emitir a Invoice?
Não!

The system does not print Invoices during Billing.

CONSIGNMENT PROCESSING

In consignment processing, goods are delivered to the customer but remain the
property of the company until they are actually used. An invoice is not created
until the customer withdraws goods from the consignment stock. Up until that
point, the customer has the right to return consignment goods.

When goods are issued, both the customer special stock at the customer and the
stock in the delivering plant are reduced. This transaction is relevant for billing.

DELIVERIES FREE OF CHARGE AND SUBSEQUENT DELIVERIES

You create a delivery free-of-charge document when you want to send your
customer a sample, for example.

Customizing for sales document type determines that this transactions requires a
preceding document.

You can also decide what happens to these item regard to pricing and billing
there.

INCOMPLETION LOG

An incompleteness log is a list of all data essential to your company in a

sales document that has not yet been entered in the system.

You can define these data fields in customizing for the incompleteness log.

INCOMPLETE SALES DOCUMENTS

In customizing for sales document types, the incompletion messages field allows
you to control whether incomplete sales documents can be saved or not.

The procedure controls what effects the incomplete data has on the process.
Example: If the terms of payment are missing, the order can be delivered
but it cannot be billed. At the same time, you will not be able to create a new
order with reference to an incomplete order.

CONTROLLING THE INCOMPLETION LOG

The incompletion log differentiates between the following levels:

Procedure Sales document header – Sales document Type

Procedure Sales document item – Item category
 Procedure Sales document schedule line – Schedule line category

In each procedure you determine which fields are checked for completion.

STATUS OF INCOMPLETE SALES DOCUMENTS

Incomplete document data affects further processing in different ways. A status

group is assigned to each field in the incompleteness procedure. When you
define the status groups, you decide which steps should be prevented if data is
missing.

FUNCTION AND SIGNIFICANCE OF PARTNER FUNCTIONS

Business Partner

Various business Partners exists within the market place, with various business
relationships to each other. Examples of business partners are:

Customer
Vendor
Employee
Contact person

Partner Functions

Assigning partner functions in the SAP system determines the functions of

particular partners in the sales process. One partner may take on several
functions.

The forward agent (agente de transporte) is an example of a vendor.

Partners in the Sales Process

Partner relationships are usually already defined in the customer master.

These are proposed automatically in the document header when you create
a sales document.

Partner Functions can be assigned to:

Partner Objects Assignment key

⇒ Customer Master > Account Group
⇒ Sales document header > Sales document type
⇒ Sales document item > Item category in sales
⇒ Free-of-charge > Delivery type
⇒ Shipment > Shipment type
 ⇒ Billing Header > Billing Type
⇒ Billing Item > Billing Type
⇒ Sales activities (CAS) > Sales activity type

In the sales document has been configured so that only one partner can be
assigned to each partner function. The only exception is for outline
agreements (partner function AA and AW).

You can define which partner functions have to be entered (mandatory

functions).
As funções mandatórias do Partner são: SOLD, SHIP, PAYER AND BILL.

You can also define partners at item level in the sales documents. Business
partners that are only defined in the header cannot be changed at item level
however.

You can prohibit anyone from changing a partner that has already been entered
(You can indicate that the sold-to party cannot be changed in the sales document
for example).

Partner Determination Procedure

Qual é a função de um Account Group?

R.: Ele define quais são as funções disponíveis do tipo de Partner.

A partner determination procedure is where you determine which partner

functions may or must appear. You determine areas of validity by assigning
procedures.

For example: You use the account group to assign the partner determination
procedure for the customer master.

Customer Master and Account Group

The account groups controls the amount of data and the response of customer
master records.

You can create additional account groups as necessary.

- When you define the account group, you determine:

For each data field, whether it is displayed or not whether maintenance is
mandatory, optional, or not possible.
- The number range
- A number of control elements, such as for partners and text of the
customer master.
OUTLINE AGREEMENTS

The two main outline agreements (acordos comerciais) are scheduling

agreements and contracts.

Contracts – Sales document Types

There are two types of contracts – value and quantity. Contracts can cover both
goods and services. Generally no restrictions apply to the different contract
forms.

A contract is an outline agreement between you and your customer that is valid
for a certain time period. The contract does not contain any schedule lines
delivery, quantities or delivery dates.

Rental and maintenance contracts are frequently used in the service industry.

Um contrato gera uma Release Order (que é a mesma coisa que uma ordem
standard, mas é referenciado a um contrato).

In copying control, you decide which types of sales documents can be used as
release orders from a contract.

Assortment modules (Módulo de sortimento) for value contracts are maintained

in the master data for products. When you create a release order, the system
checks the respective entry date against the validity period.

You can create release in any currency but the total value is updated in the
currency of the contract.

You can either bill the value contract directly or you can bill each release
order.
Pode ser feito pagamento de acordo com um programa de pagamento.

If a release exceeds the target value in a contract item, you can configure
how the system reacts: no response, two different warning messages or an
error message.

Partner authorized to Release in contract

Normally, both the sold-to party and other business partners are authorized
to release from a contract. They may also be several ship-to parties.

The partner determination procedure assigns the partners authorized to

release against the contract.
To enable the releasing partner to be different than the sold-to party for the
contract, copying control uses requirement.
Partners authorized to release are checked at header level only.

Contract Data in Sales Documents

In customizing for sales document types, you can activate the contracts data.

You can maintain contract data at both the header and the item level in the
sales document. Contract data at header level is valid for all items as long as the
data at item level is not different.

Determining Dates

When you create a contract the system proposes, for example, the start and
end dates of the contract. You define the date determination rules in
customizing. Its also have a duration category, Subsequent activities,
Cancellation procedure.

Scheduling Agreements

A scheduling agreement is an outline agreement between you and a sold-to-

party that is valid for a certain period of time. The scheduling agreement
contains fixed delivery dates and quantities.

O scheduling agreement tem como função subseqüente os deliveries

diferentemente de um contrato que precisa de Release Order

The system can provides you an overview of all the open quantities.

If the quantity in the schedule lines exceeds the target quantity, the system
issues a warning message.

MATERIAL DETERMINATION, LISTING AND EXCLUSION

Material determination (VB11)

Material determination provides you with a tool for automatically exchanging

materials in the sales document. The condition technique provides you with a
greater flexibility in material determination. When you process a document, the
system automatically searches for valid master records that you created
previously in material determination.
You can assign a substitution reason to every master record in material
determination that defines how the material should be determined. You define
the substitution rules in customizing.

You do not need a material master record for the material number that you
are replacing.

Selecting products manually

When you enter an order you can enter use different material numbers for the
same product.

We have extended the functions in manual and automatic product selection. In

manual product selection the system does not automatically replace the product.
Instead, it displays a list of all of the substitution materials and other information
in the master record.

Master Data

With the condition technique you can create data records depending only on
the material number or depending on the material and the customer number.

When you process master Record you can:

• Restrict the validity period of a record
• Maintain separate entries for each key combination
• Determine reasons for substitution
• Save one or more substitutes per master record

If there is more than one material defined in the master record for material
determination/product selection, the sequence in which they appear defines the
priority that they have.

Automatic Product Selection

In automatic product selection, the system replaces the entered material

automatically if it is not available.

When you enter an order, the system tries to fill the quantity of the order with the
first material in the material determination master record. If there is not enough of
this material, it fills the remaining quantity with the next material.

You can choose whether or not you want re-run material determination when
the delivered is created.

Automatic Product selection – Master Data

Usa-se a condition Techniche!

The sequence of the substitution material in the master data influences the result
of the automatic product selection in the order.

If you want the material that is first entered in the order to be included in the
substitution, then you must enter it in the substitution list.

Pode-se usar estratégia para substituir produto.

CONDITION TECHNIQUE - Material Determination

Os elementos da Condition Technique são:

• Procedure Determination
• Procedure
• Condition Type
• Access Sequence
• Access
• Condition Table
• Condition Record Master Data

The condition Techniche provides more flexibility in modeling material

determination and product selection

You can assign a material determination procedure to each sales

document type. The procedure contains all of the Customizing information
that the system needs for material determination. The procedure includes one
or more defined condition types.

- One access sequence is assigned to each condition type.

- Each access sequence consists of one or more access.

- Each access contains exactly one condition table. This represents

the search key that the system uses to search for a valid master
record.

You can activate an analysis of the material determination in the sales

document. The system then displays detailed information on how the materials
were determined.

Material Listing
You want to make sure that your customer receives only specific materials. You
enter these materials as a material listing. This listing is controlled by the
condition Technique.

You define in the sales document type whether the system checks the material
listing or not.

Material Exclusion

You want to ensure that the customer does not receive certain materials. You
enter these materials as a material exclusion. The material exclusion is also
controlled with the condition technique.

FREE GOODS

Free goods can be part of the order quantity not included in the invoice. This is
called an inclusive bonus quantity. The ordered goods and the free goods both
involve the same material. The quantity units of the free goods and ordered
goods must be the same.

Free goods can also take the form of extra goods that are free of charge. These
are called exclusive bonus quantities. In exclusive bonus quantities, the
extra goods are delivered free of charge and are not included in the invoice.

The exclusive free goods appear in the sales document as a separate, free-
of-charge item.

Free Goods in the sales Order

Both forms of free goods are handled in the same way in the order. The material
that has been ordered is entered as main item and the free goods material is
automatically displayed as a sub item.

The item category determines how the item is controlled later in the business
process.(for example, for delivering or pricing).

You can also enter free goods manually by entering data in the higher-level
item and item category fields (TANN). In this way however, the system does
not refers to the free goods master record.

If pricing is re-run in the sales order, it does not affect the free goods
determination.

Free Goods – Master Data

The condition technique is used for free goods. Free goods are generally
regarded as a supplement to the pricing agreement for a material.

You can define master records for one level in many different ways, for example,
material, customer/material, price list category / currency / material or customer
hierarchy / material.

You can restrict master record for one level in many different ways:

Validity period
Minimum quantity
Calculation rule
Scales

Free Goods – Calculation Rule

When you specify a calculation rule, you decide how the system determines
the free goods quantity from the additional and document quantities.

Tree Calculation rules are provided in the standart system. It can be:
Rule 1 – Pro Rata (Compre 100, ganhe 10, compre 136, ganhe 13)
Rule 2 – Unit Reference to Units (100 – ganhe 10, 136-ganhe 10, 200-
ganhe 20)
Rule 3 – Whole units (100-ganhe 10, 200-ganhe 20, 136-ganhe 0)

You can also define your own rules.

Free Goods – Analyses and Accounting

You can see detailed information about free goods in Accounting or analyses.
Revenues, sales deductions and costs of free goods can be transferred to
Accounting in different ways.

Free Goods – Condition Technique

The system uses the information about the sales area, document
determination procedure (from the sales document type) and customer
determination procedure (from customer master) to determine the free goods
procedure.

The conditions contains a list of the condition types for free goods.

One access sequence is assigned to each condition type. Each access

sequence consists of one or more access.
Each access contains exactly one condition table. This represent the search
key that the system uses to search for a valid master record.

If the search is successful, the system generates a sub item for the free goods in
the document.

Por tipo de documento você define qual price procedure pode utilizar.

Uma condition technique possui conditions types.

OVERVIEW OF THE DELIVERY PROCESS

Logistics Execution: Components and Sources

Logistics Execution is the application component for executing logistics in the

stricter sense. Its is connected with Production Planning and Control, Materials
Management, and Sales and Distribution.

Logistics Execution

Warehouse Mgmt Shipping Transport

Materials Sales and

Management Distribution

Warehouse Management was transferred from Materials Management, and

Shipping and Transportation Processing was transferred from Sales and
Distribution.

Logistics Execution

Logistics execution provides you with all necessary functions for mapping the
execution of logistical processes that are largely not industry-specific. It basically
involves more or less complex goods receipt and goods issue process.

Process Overview
In Logistics Execution there are two ways of modeling goods receipts and goods
issues: You can create either a delivery or an inventory management posting at
the beginning of the process.

• The transfer order is the document used to execute all goods

movements in the warehouse.

Structure of the delivery document

A delivery document consists of header and a number of items. The header

contains data that applies to the whole document. This means that the ship-to
party, shipping point, route, and so on, are unique for each outbound
delivery.

The Shipping Process

The terms “Shipping” or shipping process are often used in conjunction with
deliveries. These actually only describe outbound goods movements, the original
process that relates to an order. Shipping is also the name given to the
department responsible for the logistical process of the logistical process of
delivery handing (picking, packing, loading).

Criar um delivering significa que precisa de um picking.

Since the deliveries document can also be used in other areas, we refer to
deliveries related to sales document as Outbound deliveries.

Difference Between Outbound Delivery and Shipment

The outbound delivery in the SAP system supports the processing of shipping
activities in the warehouse and at the shipping point.

Basically, each outbound delivery starts at a shipping point, continues along a

route and has the ship-to party as the destination.

O delivery não é um documento de transporte.

A shipment document is generated if you have for example several outbound

deliveries to be loaded onto a truck and the truck is to deliver goods to several
shipping points and ship-to parties along a particular route.

BASIC CUSTOMIZING SETTINGS FOR THE DELIVERY PROCESS

A client is often synonymous with a corporate group, while a company code
represents an independent accounting unit.

1 Plant must have at least 1 storage location. A Plant is a production facility or

a location that handles material stock.

Stock is managed at level of the storage location.

Organizational Structure: Warehouse

In a Warehouse you can use the following structure:

Warehouse number: É a estrutura organizacional do mais alto nível. The

entire warehouse structure is managed under one warehouse number. This
number represents the warehouse complex.
Storage Type. The different warehouse areas, which differ with respect to
their organizational and technical features, are defined as storages types (for
example, high rack warehouse with random storage, picking warehouse with
fixed bind (endereço). Or shipping area. São os locais devidamente numerados
onde guardamos e estocamos materiais.
Storage section and picking area: Below the storage type level the
picking area groups together storage bins from a picking point of view. It is the
opposite of the storage section, which groups storage bins together from the
putaway viewpoint.
São áreas que sabemos temos coisas para guardar ou enviar.
Staging Area: Is a part of the warehouse where goods are store
immediately after unloading or shortly before loading. (Onde o material fica
quando acaba de chegar ou quando está pronto para sair).
Door: A door within a warehouse can be used for both the inbound and
outbound delivery of goods.

Connection Between Warehouse Number and Plant/Storage

The connection of the organizational units in the warehouse to MM Inventory

Management results from the assignment of the warehouse number to a
combination of plant and storage location.

Several storage locations within a plant can refer to the same warehouse
number.

Uma plant e um storage location aponta p/ um warehouse number.

Organizational Structure: Shipping

A Shipping Point is an independent organizational unit at fixed location that
process and monitors outbound deliveries and goods issue.

The responsible shipping point is determined in the order at item level.

An Outbound delivery is processed from a single shipping point.

The allowed combinations of shipping point and plant are defined in the
Customizing application of the enterprise structure.

A shipping point may also be set as a goods receipt point.

Any number of loading points can be assigned to a shipping point. Only one
shipping point can be assigned to a loading point. Ou seja, Um loading point
só pode ter um shipping point.

A shipping point can process the outbound deliveries of several plants. This
is only useful if the plants are located in the same general vicinity.

O Storage location não é determinado na ordem.

Delivery Type

Um delivery pode ser também de entrada.

Funções de um Delivery Type:

Number assignment
Partner (diferentes como um vendor)
Delivery split by warehouse number
Texts (específicos)
Reference to order (Criada ou não com referência a uma ordem ex.
pallets, não necessita de uma ordem)
Relevant for shipping
Route determination
Output

The delivery types controls the entire delivery.

Delivery Item categories define if?

Relevant for picking?
Packing control
Automatic batch determination
Check minimum delivery quantity
Availability check
Texts
 Picking location determination
Check for overdelivery

The delivery item category controls how delivery items are handled and
processed during the shipping process.

• When you copy an order item to a delivery, the system copies the
item category of the order item to the delivery item.

Copying Control

In the copying control table you specify:

• Which sales and distribution document types can be copied to which

delivery types
• Which item categories are copied from reference documents

You can also specify:

• Under what conditions data is copied from the order to the outbound
delivery
• Under what conditions several orders can be combined in an outbound
delivery
• Which data is to be transferred
• Whether the reference should be recorded in the document flow

Order items that are due for delivery that have the same shipping criteria are
shipped together. Required shipping criteria include the shipping point, the
route, and the ship-to party.

Determining Item categories in deliveries

An item category is not specified for order-independent items in the delivery, for
deliveries without reference to an order or for outbound deliveries.

In this case the system determines an item category for the delivery according to
the assignments specified in Customizing. For determine the item category, the
system takes into account the Delivery type and the item category group
(from the material master) Additional usages are set internally, for some
functions.

Shipping Relevant Customizing in Sales

You control order types by specifying:

- Which delivery type is proposed for the outbound delivery

 - Whether a requested delivery date is proposed in the order and how
far it is in the future
- Whether the outbound delivery is automatically created in the
background when the order is saved

Delivery relevance on the item category level is valid only for text or value items.

The goods issue movement type (or goods receipt movement type for
returns deliveries) is defined at the schedule line category level.

GOODS ISSUE PROCESS

The Shipping Process

The ECC systems supports the following functions within shipping processing:

- Monitoring of deadlines for reference documents due for shipping

- Creation and processing of outbound deliveries
- Monitoring of goods availability
- Monitoring of the capacity situation in the warehouse
- Support for picking
- Packing of the delivery
- Printing and distribution of shipping documents
- Processing of goods issue
- Controlling through overviews

Shipping Point Determination

The responsible shipping point is determined for each order item.

The Shipping Point depends on the following criteria:

The Shipping conditions from the ship-to party

The delivering plant (from the customer-material info record, the
ship-to-party or the material master record.
The required loading group, field in the material master.

The shipping condition is proposed from the sales document type if a shipping
condition has been assigned to it.

The Shipping point can not be changed in the outbound delivery.

Order items with different shipping points are therefore not copied into the
same outbound delivery.

Route Determination
Route determination is carried out in the order item and depends on:

The country and Departure zone of the shipping point

The shipping condition agreed in the sales document type
The transportation group assigned to the material
The country and Transportation zone of the ship-to party

In the order item you can manually overwrite the route that is determined.

Backward Scheduling

The earlier date to create the delivery is the earlier date between Pick/pack time
and transportation lead time?

Yes!

Scheduling takes into account the following times:

Transit time:
Loading Time
Pick/Pack time
Transportation planning lead time

The loading time and pick/pack time come from the shipping point; the
transit time and transportation planning time come from the route.

Forward scheduling

First the system performs backward scheduling in the order. If this results in a
date in the past, the system automatically perform forward scheduling, which
confirms a new delivery date. The same happens if the material is not available
at the material availability date.

When you create outbound delivery you can carry out forward scheduling
again.

Precise and daily Scheduling

In precise scheduling, the systems calculates and displays the results of

scheduling down to the minute. In daily scheduling, the systems uses days,
hours and minutes for calculation, but only displays the resulting date.

The working hours of a shipping point consist of a calendar and a shift

sequence.
In precise scheduling, pick/pack and loading times are specified in hours and
minutes.

The route is used to determine the transportation planning lead time.

Route Schedules

You can use a route schedule to organize outbound deliveries from a

particular shipping point to different ship-to parties that occur regularly in the
same sequence for a certain route.

The route schedule generally contains:

A route
A weekday as the departure date, along with a departure time
A list of ship-to parties
An itinerary (optional)

You can use schedules in sales orders, stock transfers orders, and outbound
deliveries. The system determines them automatically.

Options for creating Outbound deliveries

You can create an outbound delivery manually with or without reference to a

particular order. However, if you create a delivery manually, you cannot deliver
purchase orders or other requests.

If you use collective processing (delivery list), you can deliver goods for all
types of shipping documents. This can take place online or in the background
(overnight for instance).

Delivery due List

The delivery due list is a worklist of all operations requiring deliveries.

In the standart system, a user role is assigned to each delivery scenario. You can
maintain the user roles in Customizing.

Determining the Picking Location

If no storage location for picking is specified in the order item, the system
determines the storage location when it creates the outbound delivery and copies
it into the delivery item.

Na ordem de vendas não tem storage location.

The picking location is determined based on the shipping point, the
delivering plant, and the storage condition for the material.

MALA: The picking location is determined based on the shipping point,

the delivering plant, and the storage condition for the material as defined in the
material master.
RETA and MARE: These rules are mainly used in trade scenarios.
The picking location search is activated for each delivery item category.

Determination of Door and Stagin Area

Door or staging area determination can take place at the delivery header level,
depending on the goods recipient or the route schedule.

Staging area determination can also take place at the delivery item level if the
storage conditions (material master) are also taken into account.

Note that different staging area at the delivery item level lead to a transfer order
split because the staging area is a header field in the transfer order.

Changing and Adding to the Outbound Delivery

You can Change or add to delivery documents after they have been saved.
However, information such as ship-to parties and shipping points can no
longer be changed once you have created the outbound delivery.

You can also add items to the outbound delivery without referring to an
order.

Outbound Delivery Monitor

The outbound delivery monitor displays all deliveries that are still to be
processed or that have been processed.

This includes processing output types for shipping, such as the delivery note.

You can use the inbound delivery monitor to monitor and execute inbound
delivery activities in the same way.

Picking

Picking is the process of preparing goods for delivery to the customer with
special attention paid to dates, quantity, and quality.
Sap recommends that you use the Warehouse Management transfer order
functions. For this purpose you do not need to implement the complete WM
system; Lean WM is sufficient.

Using Lean WM, means using a small part of the functions provided bythe
Warehouse Management Component.

In the standart configuration of the system, the prerequisite for posting goods
issue is that picking-relevant items are completely picked. This means that the
delivery quantity and the pick quantity in the outbound delivery must be the
same.

Picking Process Using Warehouse Management/Lean Warehouse

Management

To use WM in picking (either full WM or Leans WM), you create a transfer

order(TO).

The transfer order is a document with which the goods movements within a
warehouse complex can be initiaded and monitored.

Instead of print out the transfer order as a picking list, you can transfer the data
in the transfer order to an external system using portable data capture or to a
warehouse control unit.

By confirming the TO, you verify the quantities removed from the warehouse.

Then, you can post the goods issue. This completes the shipping process.

The Transfer Order

A transfer order is an instruction to move materials from a source storage bin to

a destination storage bin within a warehouse complex.

Transport orders include the following information:

- Material number
- Quantity to be moved
- Source and destination storage bin

WM versus Lean Warehouse Management

If you have a warehouse with random storage, you need to use WM system
with full functionality. Since a material can be stored in different storage bins or
even several storage bins at the same time, precise inventory management at
the level of the storage bin is required.
Lean WM, does not have inventory management at the level of the storage bin
and is therefore more suitable for fixed bin warehouses.

Some of the WM functions note included in the Lean WM are:

- Storage sections
- Reserve storage bins
- Strategies for putaway and picking
- Replenishment
- Inventory at storage bin level

For Lean WM, you need at least one warehouse number and at least one
storage type from which picking takes place. You also need one storage type in
which goods are stored.

Picking areas can be defined for each warehouse number and storage type.

You can activate Lean WM in Customizing at the warehouse number level.

You assign a warehouse number to a combination of plant and storage type.

Creating and Printing Transfer Order

In WM, you have the following options for printing using a print code:

- Single print: One page for each two TO item

- Combined print: One list for the entire TO
- Pick list: One list for several TO that were created in collective
processing

In picking, differences may occur between the quantity actually removed and the
delivery quantity. However, you can only post a goods issue if the picking
quantity and delivery quantity are the same.

You must confirm the transfer order and therefore also picked quantities before
the goods issue is posted.

SPECIAL FUNCTIONS FOR PROCESSING DELIVERIES

Bathes

É um produto com características de produção em si.

You can specify a bath in the relevant detail screen for materials handled in
batches (Whether or not a material is handled in bathes is indicated in the
material master record in the “Storage 1” and “Purchasing” screens). When
delivering a sales order, this batch is copied to the outbound delivery. You can
not change it there.

If a batch has not been specified in the sales order, you can enter one in the
“picking overview” screen of the outbound delivery.

You must specify a batch before a goods are issued.

You can carry out batch splits as follows:

- Manually in the batch plit screen of the delivery item

- Using automatic batch determination when creating the outbound
delivery
(this function must first be activated in the delivery item category)
- Throught manually triggered batch determination in the batch split
screen
- In Warehouse Mangement

Serial Numbers

You can assign a unique serial number to each material. This allows you
monitor goods movement for individual materials.

You can also have serial number assigned automatically by the system.

You must specify all serial numbers before posting goods issue.

Pricing in the outbound delivery

The outbound delivery can contain shipping-related conditions at header level,

such as shipping or freight costs (if you are using the transportations
component).

You can enter the condition values manually or determine them using pricing
condition technique.

Splitting an Existing Delivery

You can split an existing delivery into several smaller deliveries, which is useful
if, for example, there is not enough room in your truck to hold the entire delivery.

When you split a delivery, you create one or more new deliveries, called
“results”, and the “remainder”.
Pode-se se fazer split fora do transportation.

Delivery Interface – Communication Scenarios

If business partners are involved in the shipping process, or some functions are
performed by non-SAP systems, you need to exchange information with these
other parties. Normally electronic data interchange (EDI) messages are used for
external communication, and Application Link Enabling (ALE) messages are
used for internal communication.

The delivery interface groups together all EDI and ALE messages that refer to
the delivery. They are all based on the same IDoc (É um txt que você recebe e
coloca dentro do sistema).

Log of Incomplete Items

When you call up the logo of incomplete items, the system checks if the data in
the outbound delivery is complete.

In the outbound delivery, the system can check completeness at both header and
item level.

In the Customizing, you can control which fields, if not entered, cause an
outbound delivery to incomplete and which effects this has on follow-on activities
such as picking, packing, goods issue, and billing.

More functions in the outbound delivery.

- Quantity checks
- Material substitution
- Credit and risk management
- Controllable error messages
- Delivery split by warehouse number
- Group of outbound deliveries
- Dangerous goods check
- Export control
- Texts

PACKING

Packing Materials

São materiais usados para embalar ou transportar produtos.

You must create material master records for the different packaging materials.
In the material master, you define special data such as packing weight and the
volume permitted for each shipping material.

Handling Unit

É quando eu pego algum produto e coloco dentro de uma caixa/embalagem.

The handling unit is assigned unique sequential number from a predefined

number range.

The handling unit header contains information about the packaging material
used in packing.

Packing Functions

Packing is the process of assigning delivery items to packaging material.

This creates new handling units. You can use as many levels as required
(multilevel packing).

In Customizing, you specify whether each delivery item category is relevant for
packing.

Packing in the Sales and Distribution Process

The packing function is available:

- In orders (as packing proposals)

- In the inbound delivery
- In the outbound delivery
- In the Shipment document

The packing proposal in the order can be copied to the outbound delivery. You
control this at the header level in the copy control table for deliveries.

Packing in the outbound delivery is copied to the shipment.

Pode-se fazer packing no outbound delivery ou no transportation.

Packaging Material Types and Material Grouping for Packaging Materials.

Similar packaging materials are grouped together in packaging material types.

The Material grouping for packaging materials is used to group together

materials that have similar packing requirements.
Packing Instructions

Packing Instructions consist of:

Packing materials
Materials to be packed
Text Items
Subordinate packing instructions
Rules concerning rounding, minimum quantities, an do on
Definition of a check profile

Packing Instructions (2)

Packing instructions can be used as packing proposals for online processing or

as packing rules for automatic packing.

Packing instruction determination is carried out using condition techninque, for

which you must define a corresponding procedure and condition types.

Packing Station

Deliveries and handling units can be packed using a packing station.

Each packing station can be controlled individually using the terminal ID, and can
therefore be used to carry out different processes.

Subsequent Processing for Packaging Materials

You may need to manage stock for packaging Materials. To enable you to do
this, the system can generate a separate item in the outbound delivery for
each packaging material.

You can bill the customer for the packaging materials, or you can use returnable
packaging materials that are not billed.

- In the former case, you must create the packaging materials in the
material master record with item category group VERP. The item
category determination procedure in the standart system determines
item category DLN. These items can be copied to the billing document
- If you use returnable packaging materials, you must create them in the
material master record with item category group LEIGH (item
category TAL is determined). These items will not be copied to the
billing document.

Handling Unit Management in Logistics

Handling units are involved in the entire logistics process and can be used in
Inventory Mangement, Production, Quality Management, Warehouse
Management, and Sales and Distribution.

Goods Receipt Process using Handling Units

If materials in a storage location administered using handling units are to be

posted as goods received, you must create an inbound delivery document.

Within the inbound delivery, you can create new handling units or adopt existing
ones.

Goods Issue

Posting goods issue for an outbound delivery completes shipping activities.

Posting goods issue requires that all mandatory shipping activities have been
performed.

Effect of goods Issue Posting

• Reduces inventory stock

• Post the value change to the stock accounts in inventory accounting
• Reduces delivery requirements
• Enter status information in the outbound delivery
• Is stored in the document flow
• Creates a work list for billing

Cancelling Goods Issue

If goods Issue for an outbound delivery is canceled, the goods issue posting is
reset.

On the selection screen, you can select one or more outbound deliveries for
which you want to cancel the goods issue posting.

QM in Shipping

The Quality Management (QM) component supports Sales and Distribution with
quality inspections for goods issues (for example, packing inspections).

You specify in the quality Management view of the material master if a quality
inspection is to be carried out for the material.
When the outbound delivery is created in the SD, QM auatomatically creates an
inspection lot for the delivery items that are relevant for inspection.

Proof of delivery (POD)

Proof of delivery (POD) is essential designed to support the process of creating

an invoice once the customer has confirmed the arrival of the goods.

After receiving the goods, the ship-to-party transfers the proof of delivery by IDoc
to SAP R/3 and thereby confirms the quantities for the entire delivery.

The system creates the billing document based on the correct (verified)
quantity. Creating the billing document via the billing due list is blocked until proof
of delivery has been confirmed.

Before you can use the proof of delivery function, you need to define which
delivery item categories are relevant for the POB (proof of billing) process. You
also need to define reasons for deviation, and in the customer master you are
using for the POB process, specify POB relevance.
PRICING FUNDAMENTALS

Groups of conditions

Data about conditions is stored in condition records.

You can determine conditions at any level you require

Condition Types:
• Prices
• Discounts/Surcharges
• Freight
• Taxes

Level on which the condition is defined

Conditions type
Sales Organization
Distribution Channel
Customer
Material

Condition Records

É um lugar onde o usuário cadastra a condição.

You can limit a pricing agreement to a certain period by specifying a validity
period.

The values in a condition record, such as price, surcharge and discount, can be
defined according to a scale. You can specify an unlimited number of levels in a
scale.

Eu posso ingressar um valor numa price normalmente sem estar numa condition
record?
Posso.

Condition Type

The condition type determines the category of a condition and describes how the
condition is used.

Possible scale base types: Possible calculation types

Value Percentage from a initial value / Fixed Amount
Quantity Amount per unit of measure
Weight Amount per unit of wheight
Volumes Amount per unit of volume
Time period Quantity per unit of time

Condition Maintenance

An additional maintenance interface is provided for condition maintenance.

This means that condition records can now be maintenance across all
condition types and condition tables. For example, you can display and
maintain the material prices and the discounts and surcharges for a customer in
one step.

Pricing procedure

All condition types permitted in pricing are available in the pricing procedure.

You need to determine how the system should use conditions by specifying the
requirements for each condition.

The sequence in which the system accesses the conditions in the business
document is also determined in the pricing procedure.

The reference level provides a method to specify a different basis to calculate

the condition type and to group conditions for subtotals.

The pricing procedure can contain any number of subtotals.

You can mark a condition type in the pricing procedure as being:
• a mandatory condition
• a manually entered condition
• for statistical purposes only

Access Sequence

An access sequence can be assigned to a condition type (except for condition

types configured as a header condition).

Cada condition type possui uma access sequence, dentro de uma access
sequence você encontra condition tables, que estão gravados pelos usuários
numa condition record.

A Condition table is a combination of fields, which form the key for a condition
record.

Pricing Overview

Um documento de vendas só aponta para um esquema de preço. (Price

Procedure).

Exemplo:

1 pedido de 120 peças de um material é criado. O sistema deve determinar o

preço automaticamente.

First, the relevant pricing procedure is determined based on the sales area,
customer, and sales document type.

The system reads the condition type of the first step and then determines the
assigned access sequence for this condition type.

The system reads the access sequence. The sequence of the condition
tables represents the search strategy to find the relevant condition record.

Each condition table represents one access, which can be made for a condition
record with specified key.

Eu consigo dizer dentro de uma Price procedure, qual condition é mandatória

ou não.

The system searches for valid condition records with the key specified by the
condition table.
If the first access does not find a valid condition record, then the system
searches for the next access using the next condition table.

After the system finds a valid condition record for an access, the system reads
the condition record and copies the value that corresponds to the scale into the
sales document.

The whole process is repeated for each condition type until the system has
finished the entire pricing procedure.

Desenhar uma price procedure:

Changing prices Manually in Documents

The prices surcharges and discounts determined automatically by the system

can be changed manually and are then marked as such.
In the condition records, you can specify limits which a manual change can be
made, for example, making a discount, which could only be changed between
the range 1% and 3%.

Conditions can be entered manually in the sales document.

You can change or create conditions on the conditions screen.

Conditions in the Document Header

Você pode ingressar com uma condition no cabeçalho?

Pode.

Conditions de cabeçalho só podem ser manuais.

Conditions can also be entered at the document header level. These are know as
header conditions and are valid for all items.

These header conditions are automatically distributed among the items based on
net value. The basis for distributing the header conditions can be changed in the
pricing procedure by selecting the appropriate routine.

New pricing and pricing types

You can configure the pricing behavior in the Pricing type.

You have two options to control the New pricing function in the sales document:

• Update prices on the condition screens is available at the header and

item levels.
• To use the new pricing document function for the sales document,
assign a pricing type to the pricing procedure in customizing. If you do not
maintain an entry, the system uses pricing type B (carry out new
pricing).

These functions are supported for both the sales and billing documents.

Pricing in the Billing Document

Copying control makes it possible to handle repricing of billing documents

based on several different scenarios.

OVERVIEW OF PRICING CONFIGURATION

Condition Table
Overview: Pricing configuration

The condition table contains the keys that can be used to create dependent
condition records.

You can add your own condition tables using tables from 501 through 999.

Condition Tables

Condition records are always created using a specific key.

Condition tables are used to define the structure of the keys of a condition
record.

The key fields of a condition table must appear at the start of the table.

In the condition table you can determine whether a field appears in the
header or in the item of the generated fast entry screen for the maintenance of
condition records.

Access Sequence

An access sequence consists of one or more condition tables

Creating an Access Sequence

You can define prices, discounts, and surcharges at various levels.

Each level is defined by a condition table.

The order of the entries in an access sequence defines the hierarchy of the
various levels.

The system determines the condition records in the sequence specified.

Determining Source Fields for Access Sequences

Within each access sequence, you can specify the document field or source field
with which an access is performed.

Examples:
- Material or pricing material?
- Document currency or local currency?
- Sold-to party or ship-to party?
Access requirements

You are able to make accesses dependent on requirements to avoid

unnecessary access. This reduces the system load.
Condition Type

After the access sequence is created, it is assigned to a condition type.

You can also creates your own condition types. You can determine the
characteristics of each condition type, for example, whether or not the
condition type represents surcharges or discounts and whether or not the
condition type should be dependent on values or quantities.

Pricing Procedure

The condition types are combined in the required sequence in the pricing
procedure.

Procedure Determination

Finally, you need to maintain the determination of the pricing procedure. The
pricing procedure is determined according to the following factors:

• Sales Area
• Customer pricing procedure field in the customer master
• Document pricing procedure field that is assigned to the sales
document type

Customizing Pricing Components

Adding New Fields for Pricing

The information required to add new pricing fields is available in the IMG
documentation. Search for create new fields using the condition technique.

To solve particular problems, you need to build and link all the pricing
components creatively.

- Condition table – Defines the key fields of the condition records.

- Access sequence – Contains the hierarchy for condition record
access.
- Condition Type – Represents the properties of the pricing conditions.
- Pricing procedure – Defines how the condition types are linked.
- Procedure determination – select the correct pricing procedure.

The following elements may be necessary to implement complex scenarios:

(CAI NA PROVA)
- Adding new fields for pricing – Creates new fields to meet customer
requirements
- Requirements – defines dependencies and improves performance.
- Formulae – Enables expanding the limits of standart configuration.

New fields may be added to the pricing field catalog. This allows you to use the
new field to define condition tables.

Requirement routines and formulae provide a method to modify the standart

pricing logic meet unique user requirements.
Pricing Reports – Customer-Specific Prices

To provide an overview of existing condition records, you can generate a list of

conditions for analysis. You might ask the following questions:

• What customer-specific price agreements are made within a certain

period?
• What Incoterm condition records are stored in the system?
• What price lists are created with scale prices?

The layout of the lists and the condition records reported is set in Customizing.

Pricing Reports – Tables

When creating a new program for pricing reports, you first decide the views in
which you want to analyze the condition records.

Depending on which fields are selected, the system generates a list of tables,
which contain at least one of the selected fields.

Maintaining Conditions Using Pricing Reports

Condition maintenance has two maintenance interfaces.

The newer interface allows mass maintenance of conditions based on

characteristics.
This means that condition records can now be maintained across all
condition types and condition tables.

You can also call up the classis maintenance transaction for conditions by
choosing Select using condition type.

Creating Condition Records with reference

 New condition records can be created with reference to existing condition
records.

During the process, changes can be made to the rate, validity period, and
additional sales data in the newly created records.

This function provides an efficient method to update condition records

simultaneously.

Change Condition Records

Individual condition records can be maintained manually.

The price change function allows you to maintain multiple condition records
simultaneously.

Copying Condition Records

Multiple condition records can be created by copying an existing condition

record.

Copying rules are maintained in Customizing and you may create your own
copying rules.

Long Texts in Condition Records

⇒ Can be maintained for condition records

⇒ Can be maintained for agreements

o Promotion
o Sales deal
o Rebate agreements

You can maintain long texts in the condition records for pricing and
agreements, such as rebates, sales deals, and promotions.

These provide information about:

• Creating condition records
• Approvals
• Invalidity

If required, long texts in the rebate agreement can be copied to the documents.
However, text control customizing offers no possibility to copy the text long
texts from condition records to the documents.

Text is not copied when you create condition records with reference.

Net Price List

The net price list provides an option to create price information for a
customer on a selected quantity of materials.

The net prices are determined by simulating a billing document.

(aqui)
Condition Indices

You can create and use condition indices to search for condition records
that were created for a variety of condition types and condition tables.

For example, you can view all the condition records that apply to a particular
customer or product.

Before you use the indices that are delivered in the standard version, you
must first activate the indices in Customizing for sales.

If you create your own indices, the system automatically activates each new
index when you generate it. In additional you must specify an update
requirement for each condition index.

You can configure for each condition type whether or not the system updates
the condition indices when you post the condition records for the
corresponding condition type.

Release Procedure (Procedimento de liberação) for Conditions

You can allow a release procedure to be used when a condition table is

created, by selecting the With release status checkbox. Thiis adds the following
fields to the condition table automatically:

KFRST: Release status as last key field

KBSTAT: Processing status as a field of the variable data part

The release status is predefined. At present the following status are defined:

• Released (Liberado)
• Blocked
 • Released for price simulation (net price list)
• Released for planning and price simulation (planning in CO-PA

The release status is set indirectly by defining a processing status in

Customizing for pricing and assigning a release status to the processing
status.

Calculation Type
Changeable calculation Types

The calculation type for acondition type is defined in Customizing. This calculation type
determines how prices or discounts and sucharges are calculated for a condition.

The calculation type can now be selected when creating a condition record for the first
time.

When creating new condition records, you can select a calculation type that differs from
the one set in Customizing.

SPECIAL FUNCTIONS

Group conditions

In customizing, you can set a condition type to be a group condition. The

condition base value, such as weight, is then calculated as the sum of the
individual items within a group.

Group Conditions with Varying Keys

For group conditions with varying keys, item quantities are accumulated for
scale point determination purposes but the rate for each item is calculated
from its individual condition record.

Excluding Conditions

Conditions can be linked to requirements in the pricing procedure.

A requirement can evaluate the condition exclusion indicator and ignore the
condition if the indicator is set.

The condition exclusion indicator can be set in either the condition type or
the condition record.

Comparing Condition Types

Determining the Best Price Using condition Exclusion
Condition types to be compared are first placed in an exclusion group.

During pricing, the conditions, which result in the best price (lowest charge or
highest discount) are selected from this group. All other conditions are
deactivated.

There are several comparison methods which may be used:

• A: All conditions found within the first exclusion group are

compared and the condition with the best price is chosen. All other
are deactivated.
• B: All condition records found for one condition are
compared. The best price is chosen. All other conditions are
deactivated. This method can be used with condition type PR00.
• C: The total of condition records found in the first exclusion
group is compared to the total of condition records found in the
second exclusion group. The group that calculates the best price is
chosen. The other is deactivated.
• D: If a condition record is determined for the condition types
of the first exclusion group, all the condition records for the second
exclusion group are deactivated.
• E: Similar to method B, except that the worst price is chosen
• F: Similar to method C, except that the group with the worst
overall price is chosen.

Condition Update

Updating Conditions – Tracking (rastreando) Cumulative Values

Values can be accumulated in condition records and tested against limits. In

this way, you can set a maximum condition value, condition base value, or
number of orders for a condition.

The cumulative values in the condition record can be displayed.

Condition Supplements

Condition supplements do not have their own access sequence. They are found
together with the underlying condition record.

Hierarchy Pricing

You want to grant a discount that depends on characteristics related in a

hierarchy.
Hierarchy Accesses

Hierarchy accesses optimize pricing for hierarchy data structures, such as

the product hierarchy.

Hierarchy Accesses (2)

To define the condition table key for hierarchies such as this, you need to
include partial quantities for a predefined quantity of characteristics.

Without hierarchy accesses, you need to create a condition table for each
combination and assign all the accesses to these tables in an access sequence.

Hierarchy Accesses (3)

The new solution, you need a single condition table (= one access).

The functions in hierarchy accesses enable you to solve problems using one
access to a condition table.

When you create the access sequence to use this condition table, you need to
define at the field whether or not each field is a fixed component of the key or
whether or not the field is optional.

Priorities are in the next step assigned to the optional fields.

Hierarchy accesses also provide clear and easy master maintenance because
the different condition records for a condition type can be created together in
the quick entry screen for maintaining conditions.

Data Determination in Access

For pricing you can determine and use data that is not contained in the
document.

This can be performed in two steps:

Data determination
Data use

Data Determination in Access – Price Book

The term price book refers to a price determination strategy.

This can be achieved using a two-step data determination process, as

shown:
 • Step1: A sales deal number is determined, depending on the customer
group.

• Step 2: Using the material group as a basis, special agreements are

determined, which take:

Pricing date
Scale quantity
Item price list
Into account (condition type PBUD).

• The special agreements that are determined are used in the condition
type, PBBS. As a result, the base prices are read.
• On the basis of these prices, the gross price is calculated in the condition
type, PBUP, using the percentage value from condition type, PBUD.

SPECIAL CONDITION TYPES

Manual Order Value HM00

The header condition type HM00 allows you to enter the order value manually.
The new order value is then distributed proportional between the items,
taking into account the previous net item value. Taxes are determined again
for each item.

Net Price PN00

The PN00 condition in the standard system allows you to specify the net
price for an item manually. The original conditions are deactivated.

Minimum Price Value

Minimum Order Values AMIW and AMIZ

You may create minimum value for each order using condition type AMIW, if
the value in the order header is less than this minimum order value during
pricing, the system uses a minimum as the net order value automatically. The
minimum order value is a statistical condition.

Condition type AMIW is a group condition and is divided among the different
item according to value.

Calculation formula 13 is assigned to condition type AMIZ in the pricing

procedure. This formula calculates the minimum value surcharge
(sobrecarga) by subtracting the net item value from the minimum order
value, AMIW.

Exemplo: O cliente coloca um pedido de 2 itens um item com o valor líquido de

100 o outro item com o valor líquido de 60. Que somado dá 160.

Você possui uma Price group numa condition record com a condition type AMIW
que está com o valor mínimo de 200.

O AMIZ é calculado automaticamente pela diferença do NET do AMIW com o

NET da somatória dos itens na ordem. Que dá 40.

O sistema automaticamente altera o NET desta ordem para 200. que é o AMIW
mínimo para aquele cliente.

Minimum Price PMIN

You can create a minimum price for a material using condition type PMIN. If
the minimum price is not met during pricing, the system determines the
difference using condition type PMIN.

Você possui uma condition record de material com a condition type PMIN com
um valor de 1.500 para um material. Na ordem o PR00 determinou um preço de
1600 – o desconto do K007 de 160 que seria cobrado o valor de 1440. O PMIN
define então o valor de 1500 pois é o preço mínimo daquele material..

Scale Pricing

Interval Price PR02 (Preço por intervalo)

You can maintain condition records with interval scales if the condition type
is set to scale type D in Customizing. Interval scales cannot be used for
group conditions.

Customer Hierarchy Pricing

Customer hierarchy is available in Sales Order Management so that you can

create flexible hierarchies to reflect the structure of customer organizations.
Use customers hierarchies during sales order processing and billing to
determine pricing and running statistics.

A customer hierarchy consists of nodes.

To create a customer hierarchy:

 1. Create master records for each node
2. Assign the nodes to each other
3. Assign the customer master records to the relevant
nodes.

Customer hierarchies are valid for a certain period of time.

Você cria um nó para uma Sales area.

Hierarchy Path

With customer hierarchies, you can assign price or rebate agreements to a

higher level node. The agreements are then valid for customer at all
subordinate levels of this node. You can create pricing condition records
for each node indicated as relevant for pricing.

If one or more nodes in the hierarchy path of sales order contain pricing
information, the system takes these nodes into account automatically
during pricing according to the underlying access sequence.
Hierarchy Discount H101

In the standard system, the access sequence is set in Customizing so that

the discount is initiated at lowest hierarchy level.

Discounts and Surcharges

Pallet Discount KP00

The pallet discount grants the customer a discount for whole units of measure
only, such as complete pallet.

Incomplete Pallet Surcharge KP01

In this case, the customer pays a surcharge for an incomplete pallet.

Mixed Pallet Discount KP02

The mixed pallet discount accumulates the quantities of the individual

items and calculates the discount for complete pallets only.

Surcharge for Incomplete Mixed Pallets KP03

The mixed pallet surcharge accumulates the quantities of the individual

items and calculates the surcharge on any fractional portion of the total
quantity.
Rounding Diff (Define-se regras de arredondamento)

You can maintain a rounding unit in Table T001R (SAP NetWeaver > General
Setting > Currencies > Define rounding rules for currencies) for each
company code and currency. If the final amount in the order header differs
from the rounding unit, the system rounds the amount up or down as
specified.

Statistical Condition Types

Cost VPRS

In the standard version, condition type VPRS is used to retrieve (recuperar) the
standard cost. The pricing procedure uses this condition type as a statistical
value.

Não afeta o preço.

VPRS is not determined using condition Record.

Cash Discount SKTO

É um desconto por adimplência.

In the standard system, condition type SKTO is used to retrieve the cash
discount rate. The pricing procedure uses this condition type as a statistical
value.

Customer Expected Prices – EDI1 and EDI2

You can either enter the customer expected price manually in the order or
retrieve the price from the incoming IDoc in an EDI environment.

You can use condition type EDI1 to compare the net price for each item. You
can use condition type EDI2 to compare the overall item value, which is
obtained by multiplying the net price and the quantity.

Calculation formula 9 is assigned to condition Type EDI1 in the pricing

procedure. This formula tests for a maximum deviation of 0.05 currency unit.

Calculation formula 8 is assigned to condition type EDI2 in the pricing

procedure. This formula tests for a maximum deviation of 1.0 currency unit.
You can processes lists of orders having differences in prices, allowing the
system to use or correct the price it determined.

Pode controlar por preço unitário ou por acumulado.

TAXES, PRICING AGREEMENTS, AND REBATES

Um material ou um cliente, possui nos cadastros mestre uma TAX

Classification formando um conjunto de informações que geram um código
IVA.

Um código IVA por sua vez, aponta para uma TAX PROCEDURE, que é
responsável em definir o que será calculado através das conditions Types.

A TAX PROCEDURE, por sua vez aponta para uma PRICING PROCEDURE, lá
as conditions types assinaladas ou marcadas na Tax Procedure definirá como
se calcula estes impostos na Ordem.

Na ordem são então calculados os impostos que foram encontrados para

aquela combinação Cliente/Material.

Criteria to determine TAx

⇒ Departure Country - (Country of the delivering plant)

⇒ Destination Country - (Country of the ship-to party)
⇒ Customer tax classification
⇒ Material tax classification - (access with departure country)

You can assign a rule, blank, A, B, at the Sales organization level to

determine the sales tax identification number in the order and billing
document (the tax classification determination is linked to this).

Pricing Procedures for Tax

Taxes may be calculated in Sales and Distribution using the normal

condition techniques.

The condition Type for TAX is entered into the pricing procedure.

The access sequence is used to find the appropriate condition record for the
current situation.

Tax Interfaces (Example – United States)

The tax procedure is assigned in the defaults for Financial Accounting
according to country.

For the United States, you have the following options:

• TAXUS (Taxes are calculated in Sales and Distribution)

• TXUSJ (Taxes are calculated in the central tax procedure using the tax
jurisdiction value stored in the master data for the ship-to party
• TAXUSX (Taxes are calculated through an RFC and a central tax
procedure)

Pricing Agreements

Use agreements to implement and evaluate marketing projects.

Promotion and Sales Deal (Acordo de Vendas)

Validity Period

You can define a promotion or general marketing plan for a product line for a
certain period of time.

You can then link promotion with specific sales deals, which are then linked to
special condition records used for promotional pricing or discounts.

Existe comunicação com o SIS que consegue monitorar estas campanhas.

Sales Deal and Promotions in the Billing

The sales deal number and promotion number are displayed in the detail
screen of the billing item. The Sales Information System can be used to
capture and report the statistics for the sales deals and promotions with a
user-defined information structure.

Release Status for Sales Deals

The release status of a sales deal controls where you can find the condition
records for a sales agreement.

Rebates (Bonificações)

A rebate is a discount, which is granted subsequently to a rebate recipient on the

basis of a defined sales volume within a certain period.
Rebate agreements are created to determine the values required for a rebate
settlement within the validity period of the rebate agreement.

Rebate Agreements Types

You may define rebates at as many levels as you require, similar to any other
pricing condition.

The standard system provides the following rebate agreement types:

• Material rebate
• Customer rebate
• Customer hierarchy rebate
• Material group rebate
• Independent of sales rebate volume

Creating Rabate Agreements

The rebate agreement is created with a specific rebate agreement type. The
features of each rebate agreement type are set in Customizing.

Condition records are linked to the rebate agreement specifying the rebate
rate and the accrual rate.

With the rebate agreement, you can specify:

• The condition types used with this rebate agreement type

• A Validity period proposal

Processing Rebates

Rebates are different from other discounts in that they are based on the sales
Volume generated by the customer within a specified period and are paid
retrospectively. The rebate details are defined in a rebate agreement.

A settlement run creates the required credit memo request automatically.

When the rebate-relevant billing documents are processed, accruals can be
determined and posted automatically. You can use the rebate memo to
reverse these accruals, if required.

Prerequisites for Rebate Processing

To function properly, rebate processing must be activated for:

 • The Sales Organization
• The Payer master
• The Billing document type

To improve performance, you should deactivate rebate processing if it is not

necessary.

Rebate Processing

Rebate processing begins by creating a rebate-relevant billing document.

The validity rebates are determined by the pricing procedure using the rebate
basis subtotal.

Each rebate condition type has an assigned access sequence.

The system uses the access sequence to search for the valid rebate condition
record. If valid condition records is found, the accrual rate is read.

Requirement 24 in the pricing procedure enforces that the rebate conditions

are used only in billing documents.

Requirement 25 in the pricing procedure enforces that the rebate conditions

are used only in rebate-relevant billing documents.

The rebate accrual amount is calculated using the rebate basis.

The system posts an accrual to financial accounting when the rebate-relevant

billing document is released to accounting.

Settling Rebates

Creating rebates settlements

The system uses the accumulated amounts in the rebate agreement to create a
rebate settlement. Status A refers to an open rebate agreement.

The system generates a rebate credit memo request for the rebate payment
amount specified.

You can display the sales volume and drill-down in the rebate agreement.

You can perform a final Settlement for the rebate agreement in the following
ways?

• Manually
 • Automatically
• In the background

Accruals are reversed as soon as the rebate agreement is settled by credit

memo.

Partial Rebate Settlement

Partial rebate settlement can be limited for each rebate agreement type, as
follows:

• Up to the accumulated accrual amount

• Up to the calculated payment amount for the current date
• Unlimited

Accruals are cancelled automatically when a credit memo is created, provided

that the rebate agreement type is set accordingly in Customizing.

Settlement Material (1)

You may have a Rebate that does not refer to a particular material but rather
to a group of materials or to a customer.

Settlement Material (2)

When creating a credit memo, the settlement material is the source for
important material master data, for example, account determination.

Retroactive Rebate Agreements

Retroactive rebate agreements allow you take into account billing documents
created before the rebate agreement is created.

The rebate basis for the billing documents created previously is accumulated
and recorded in the rebate agreement.

The accrual amount is not automatically updated for billing documents

created previously. This amount can be entered manually or can be
corrected by using report RV15B002.

Rebate-relevante billing documents created after rebate agreement is created

update both the rebate basis and accrual fields automatically.

INTEGRATION OF THE BILLING DOCUMENT IN THE SD

PROCESS CHAIN
 • Billing Orders and deliverires
• Updating the document flow
• Creating documents in Financial Accounting
• Updating billing status
• Updating the SIS (Sales Information System)
• Updating the Credit account
• Forwarding data to PA (Profitability Analysis)

An important part of billing is the interface to Financial Accounting. This allows

documents to be created automatically in Financial Accounting and Controlling
when you create billing documents.

Billing Document Structure

All billing documents have the same structure. They are made of the header
and any number of items.

The header contains the general data that is valid for the entire billing
documents. This includes:

• Customer number of the Payer

• Billing date
• Net value of the entire billing document

The items contain the data relevant for each individual item. This includes:

• Material number
• Billing Quantity
• Net Value of the individual items

Billing Document Screens (TELAS)

The data in the billing document can be displayed on different screens.

These screens are divided up as follows:

• Overview screens

o Overviews with header and item data

• Detail Screens
o Screens at header level with general data
o Screens at item level with specific data for items.
WORKING WITH ORGANIZATIONAL UNITS IN CUSTOMIZING

Customizing - How to proceed

In the first step, you define your own organizational structure in the relevant
data views.

In the next step, you assign the various organizational units to each other.

Assigning Sales Organizations and Plants

Sales organizations and plants are assigned uniquely to one company

code.

A Sales organization can sell goods from more than one plant.

A plant can also be assigned to several sales organizations.

In the sales order the system automatically creates a delivering plant on the
basis of a priority rule.

A sales organization can also sell products supplied by a plant that is

assigned to a different company code (inter-company sales processing).

Organization in Accounting

Each company code in the system uses general ledger accounts from exactly
one chart of accounts.

In Financial Accounting, the business transactions are created, saved

processed and posted at company code level. You can create several
company codes for each client, in order to carry out accounting for several
independent companies. There must always be at least one company code.

Because a unique assignment is made between sales organization and

company code, the company code is automatically determined when you
enter the relevant sales organization in the sales order.

The Business Area represents an organizational unit for which you can
carry out internal reporting. A company code may be divided into multiple
business areas.

Define a Business area is optional. They can be used to prepare balance

sheets and profit and loss statements not only for company codes, but also
for other internal areas (for example, division-related).
The relevant business area is determined for each order item according to
defined rules.

CONTROLLING THE BILLING PROCESS

Billing Types

The billing type controls the whole billing document.

• F2 Invoice
• F8 Pro forma Invoice
• G2 Credit memo
• L2 Debit Memo
• Re returns
• S1 Cancellation invoive
• S2 Cancellation Credit memo
• LR Invoice List
• LG Credit memo List
• IV Intercompany billing (invoice)
• IG Intercompany billing (credit memo)
• Cash Sale

Billing Type Controls

You can create new billing types or redefine existing ones in the standard
system to meet the requirements of your company installation.

Many of the control parameters in the billing type influence further processing in
Financial Accounting (posting block, account determination).

Are functions of the Billing type to control:

• Number assignment
• Partners
• Texts
• Output
• Rebates
• Posting Block
• Special features of the FI Interface
• Account determination
• Invoice list type
• Cancellation billing type Number assignment

Importance of the Item Category within Billing

Billing type Proposal

In Customizing for the item category, you can determine whether billing is to
be carried out with reference to a delivery or an order.

O item category diz qual o billing document type.

Delivery-Related Invoices

You can reference either an order or a delivery when creating an invoice.

If you want to ensure that goods have already been shipped before an invoice is
created, create an invoice with reference to a delivery.

You can create an invoice for goods (the carpet) and service (laying
(assentar) the carpet), as long as the corresponding requirements for combining
the two are met.

Order-Related Invoices

If you want to invoice a customer for services rendered, normally you create
an invoice with reference to the sales order because deliveries are not usually
created for services.

SPECIAL BILLING TYPES

Cancellation

To cancel a billing document, you must create a cancellation document. The

system copies data from the reference document into the cancellation and offsets
the entry in Accounting.

The reference document of the billing document (for example, the delivery for
the canceled invoice) can now be billed again.

Credit memos can be cancelled with billing document type S2 in the

standard system.

You also have the option of canceling individual items in a billing document.

Credit and Debit Memos

You can create credit and debit memos either with reference to credit or
debit memo request (sales document), or, if your company does not require
a release procedure in the case of complaints, directly with reference to a
billing document.

You can create credit and debit memo requests:

• Without reference to a previous business transaction

• With reference to an Order
• With reference to a Billing document

Releasing or Rejecting Credit Memo Requests

You can release a credit memo request or return by removing the billing block.

You can enter a reason for reject for each item.

The value of theses items will not be copied into the billing document.

Workflow for Credit Memo Requests

Credit memo requests are usually blocked for billing (that is, credit) upon
creation until the employee responsible releases this block.

If the value of the credit memo request is below a certain minimum limit, then it
can be released automatically by the system.

Invoice Correction Process Flow

The Invoice Correction request represents a combination of credit and debit

memo requests.

The invoice correction request must be created with reference to the

corresponding billing document (no reference to order or inquiry).

When creating an invoice correction request, the items are automatically

duplicated (this means that for every item in the billing document, a second
item is created). The resulting item categories must have opposite +/- values.

First all credit memo items are listed, followed by all debit memo items.

The credit memo item cannot be changed. The corresponding debit memo
item, however, can be updated according to new characteristics (new
pricing, change in quantity).
You can delete debit and credit memos in pairs.

You can create an invoice correct for quantity difference or Price difference.

Returns

You create a return for goods sent back from a dissatisfied customer.
Returns are processed in the same way as a credit memo requests.

The credit memo is billed with reference to the order, which means it refers to
the return request document, not to the return delivery.

Pro Forma Invoices

Billing Types for pro forma invoices are available for export transactions.

You can create pro forma invoices with reference to orders or deliveries. You
do not need to post the goods issue before creating a delivery-related pro
forma invoice.

You can create as many pro forma invoice as required, since the billing
status in the reference document is not updated.

Data from pro forma invoices is not transferred to Accounting.

Cash Sales

For cash sales, payment is made when goods are ordered. The invoice is
also printed at this time.

• The order and the delivery are created in one step.

• The goods issue is posted at a later time as a separate transaction so
the customer does not have to wait.

Order Type CS is used for Cash Sales.

The actual billing document can be created later after the goods issue has
been posted.

Type SC is configured as follows:

 • Order-related billing
• No output determination, as this already been carried out
in the order
• No new price determination, as the pricing should not differ
from the printed invoice
• Posting in Financial Account is made to a cash
settlement account, not to the customer
• Billing type SV is used for Cancellations in cash sales

DATA FLOW AND COPYING CONTROL

The Billing Process

Each billing document requires a reference document (exception: billing of

external transactions). This may be:

⇒ Sales document
⇒ Outbound delivery
⇒ Billing document

Reference Document

You must always refer to an existing document when creating a Billing

document.

The quantities can be taken from the delivery; the prices however are taken
from the underlying order.

Data Flow

You can, to a certain extent, influence data flow from reference documents to
billing documents. This is done using:

⇒ Billing Types
⇒ Copying control
o At header level:
• Foreign trade data
• Allocation number
• Reference number
• Item number assignment

o At Item Level
• Quantity
• Pricing
You can also use data transfer routines to influence the data flow to meet
your individual requirements. For example, Terms of payment can be copied
from the customer master instead of the preceding sales document.

Copying Control

The system administrator can define how data is transferred in the billing
process in the copying control table. Controls are determined for:

• The header
• The item

The following controls are found at header level:

• Reference document: Which documents may be used as

reference for billing?
• Determination of foreign trade data, allocation numbers,
reference numbers, and item numbers.

The following controls are found at item level:

• Billing quantity;
• Pricing and exchange rate
• Should price, be carried out again or should prices from the
order be copied over, and at what exchange rate?
• Updating the quantity and value in the reference document
• Where should the conditions in the billing document be carried
over from, copying over shipment costs from the shipment
cost document?

In copying control you can specify whether goods issue has to be posted
before billing can be carried out.

Billing Quantity

Deliveries and order quantities are referenced in billing. You can also take
into account, the quantity already billed (Depending on the area for which
the relevant billing type is used).
This makes it possible, to create an order-related billing document for quantities
already delivered. (Ex.: Quantity already delivered minus quantity already
billed).

Pricing Overview

The system determines a pricing procedure based on document information.

Individual condition types are stored in this pricing procedure in a

corresponding sequence.

An access sequence is stored for every condition type. This defines the
search strategy the system utilizes when searching for valid condition records.

For each access, the key fields are filled with document data so that the
system can search for available condition records in the condition file.

These condition records can be created using scales.

When determining a suitable, valid condition record, the scale is read with the
number of pieces or the value from the item, and the corresponding
price/discount is set in the document.

The procedure described above is carried out for every single condition type
contained in the pricing procedure.

Pricing in the Billing Document

At the time of billing, the following possible pricing types may be set for the
items:

A: The pricing elements are copied from the reference document and updated
according to a scale.
B: Pricing is carried out again.
C: The manual pricing elements are copied, and pricing is carried out again for
the others.
D: The pricing elements are copied unchanged from the reference document.
G: The pricing elements are copied unchanged from the reference document.
The tax conditions are determined again.
H: The pricing elements are copied unchanged from the reference document.

The system administrator can assign a pricing type or define new ones for
each type and item category combination.

The system administrator can also define how the rate is determined.
OPTIONS FOR CREATING BILLING DOCUMENTS

Todo processo coletivo gera um LOG.

The selection criteria for a Billing Due List is: Sold-to party, billing date, and
destination country.

After saving a Billing Due List, you can display the log to determine which billing
documents were created from a billing due list and whether any errors
occurred.

You can process the billing due list in simulation mode. The system displays
the billing documents without saving documents.

Further selection data (sales document number, distribution channel, division,

and shipping point) and new ways of processing are available when processing
the billing due list.

Creating Invoices on Specific Dates

You can process invoices periodically. All deliveries due for billing on a certain
date can be combined into one collective invoice.

To do this, you must first:

• Maintain individual billing dates in the factory calendar using

special rules
• Enter the factory calendar in the Customer Master Record of
the PAYER (Billing schedule screen)

When you create a document, the system copies the next invoice date from
the factory calendar to the appropriate document as the billing date.

The calendar is client-independent.

Billing in the Background

You may decide to create invoices using a background job because it is

practical and efficient. You can run the background job automatically in the
following ways:

• Periodically (for example, every Monday at 2 a.m.

• At a specific time

Cancellation of Collective Billing Run

You can cancel a collective billing run.

This cancels all the Billing documents in a collective run. The caneled billing
documents are combined under a collective processing number in collective
processing type S and can be displayed by choosing Billing document – Log.

You can then bill the preceding documents for the canceled billing document
again.

General Billing Interface

Using the general billing Interface, you can Invoice external documents in the
SAP system. (that is, orders and deliveries not created in the SAP system).

To do this, you must first:

• Prepare the data in a sequential file of specified format

• Specify a minimum number of required fields to be filled from the
data records
• Specify the remaining number of required for billing either through
the data records for the sequential file or through the system
(optional fields).

INVOICE COMBINATION AND INVOICE SPLIT

Collective Billing Document

As a rule, the system attepts to combine all compatible transactions in a single

billing document.

Automatic Invoice Split

If the header partners or data in the header fields are not identical, the
system will automatically perform an invoice split.

All header partner and header fields in the billing document can cause an
invoice split.

Item-Dependent Invoice Split

The system administrator can also define additional split requirements in

Customizing for copying control, to prevent the system from combining sales
documents in a billing document.
Individual Billing Documents

You can configure the SAP system to create one billing document for each sales
document.

Invoice List

Invoice List contains various billing documents (invoices, credit and debit
memos) and can be sent to a payer on specified days or at certain intervals.

Uma Invoice List é um Billing Document Type.

You can agree upon a factoring discount.

Each billing type to be Included in an invoice list must be assigned an

invoice list type.

You also need to maintain the following master data:

⇒ Define a factory calendar, which specifies when invoice lists are

to be created, Enter this factory calendar in the Payer Customer Master
Record
⇒ Maintain condition records for condition type, RL00, for the
payes
⇒ Create output condition records for the condition types, LR00
and RD01]
You can use communications technology to decide whether
invoice documents are sent to the customer when the invoice list is
created or whether they are not sent until the invoice list is created.

You can cancel invoice lists. In the case of factoring discounts, a

corresponding cancellation document is created for FI.

SPECIAL BUSINESS TRANSACTIONS

Billing Plans – Periodic Billing and Milestone Billing

Billing Plan

When processing an order, instead of storing a single billing date, you can
store a detailed billing plan with several billing dates in the sales document at
item level.
$
You can also define a billing plan at header level, which is then valid for all
items assigned to it. These header billing plans are assigned to sales
document types.

There are two types of Billing Plans:

Periodic billing is often used for rental and service agreements, in order to
bill the full amount periodically at certain dates.

Milestone billing is often used in plant engineering and construction, in order

to spread billing of the full amount over several dates within a billing plan.

Periodic Billing

The start and end dates define the duration of the billing plan. If possible
they are taken from the contract data. You may decide not to set an end
date (if the duration is unlimited).

You can create new dates either directly in the billing plan, or using the report
RVFPLA01. You should schedule the report to run at regular intervals, since
new dates are not compiled automatically when individual settlement periods
are billed.

Milestone Billing

During milestone billing, the total value to be billed is distributed among the
individual dates according to certain rules.

You can enter as many dates per billing plan as you require.

Billing plan dates can be blocked for billing.

The system creates an entry in the billing index for each billing date.

Dates that have already been billed can no longer be changed in the billing
plan.

Billing Plan with Link to Milestone Billing

Milestone area assigned to the billing plan dates and blocked for billing until the
milestone is confirmed as completed.

Billing Rule: Determining Billing Value

A billing rule can be created for each billing plan date. This rule determines how
the value to be billed on a particular date is determined.

This allows you to define, for example, whether a fixed amount or a

percentage of the total amount is to be billed.

The system can also determine whether the amount to be billed counts as a
final invoice for which as yet unbilled dates must also be taken into account.

Within pricing, condition records are created for special condition types, for
which monthly prices can be defined.

Customizing for Billing Plans

The billing plan type is determined from the document item category and
the relevance for billing.

Date descriptions represent the text description for the corresponding billing
dates in the billing plan.

The date categories defined have a control function at billing date level. For
example, they determine which billing rule is used to settle the date, whether the
billing date is a fixed date and whether a billing block is set for this date.

Date rules are needed in the billing plan, in order to define the start date and the
end date, as well as to determine the corresponding billing dates.

The foundation of every date determination rule is a basis date to which a

defined period is added.

Differentiation of periodic billing and milestone billing with the relevant

controlling parameters is carried out via the billing plan type.

The date proposal is used exclusively for milestone billing. It determines a

sequence of dates that are used as the reference for date determination
during order processing.

Down Payment Processing in Sales Distribution/Financial Accounting

Down payments are usually arranged with the customer when dealing with plant
engineering and construction or capital goods.

Down payments are already created in the sales order.

At the corresponding due date, a down payment request (billing document

in Sales and Distribution) is sent to the customer.
The down payment request in SD is automatically posted in Financial
Accounting (FI) as a down payment request. The item has a special General
Ledger (G/L) indicator, which ensures that posting is statistical.

When posting an incoming payment for a down payment, the incoming

payment is assigned to the down payment request.

When processing partial/final invoices, the down payments made are transferred
as down payment to be cleared. Within Financial accounting, the down
payments are deducted from the special reconciliation account and entered in
the standard reconciliation account. The down payments for clearing then
appear as open items for the customer and reduce the receivables total.

Down Payment Agreements in the Sales Order

Down payment processing is carried out with the billing plan function.

One or more down payment agreements can be stored as a date in a billing

plan.

The value of the agreed down payment can be entered either as a fixed amount
or as a percentage of the value of the item.

Control is carried out via the billing rule:

o Billing rule 4: Down payment for percentage milestone billing

o Billing rule 5: Down payment for value-based milestone billing

The down payment agreement can be assigned directly to an item, or it can

be defined as valid for all items in the order.

Down Payment Request

As soon as the billing date (in the billing plan) for the down payment has been
reached, the system creates a down payment invoice and sends it to the
customer.

Billing Type FAZ, is used to create the down payment request.

This down payment request can be created as follows:

⇒ Automatically via the billing due list processing in a collective

run
 ⇒ Explicitly by specifying the order number via the transaction
Create billing document

Tax is determined and displayed automatically when the down payment

request is created.

The down payment request in FI, is created automatically from the down
payment request in Sales and Distribution.

Incoming Payments for Down Payments

When a payment request is settled, the especial General Ledger (G/L) indicator
A displays the incoming payment in Financial Accounting as a down payment
by posting.

You can view the down payments in the open items of accounts receivable
under the special G/L indicator A.

The down payment request is correspondingly set to cleared in the document

flow of the sales order.

Partial Invoice – Full Settlement

For partial and final invoices, the down payments made are transferred to the
billing documents as down payments for clearing.

Partial Invoice – Proportional Settlements

During partial invoicing, the amount of the down payment to be cleared can
be changed.

In this case, the maximum amount for clearing is the amount received as down
payments minus the down payments already cleared.

During final invoicing, all uncleared down payments are taken into account.

Installment Payments (Parcelas)

Installment Plan

An installment plan allows the customer to pay in installments. Only one

billing document is created for all of the installment payments. The printed
invoice is created on the basis of this billing document and includes a list of
individual payment dates and exact amounts.
Each installment payment creates an account receivable line item posting
in Financial Accounting.

You must define installment payment terms in Customizing.

For installment payment terms, you must specify the number and amount
of the installment in percentage and payments terms for each installment
payment.

Account Determination Process and Areas

Using Account Determination

You will need to determine the accounts to be posted in several

different areas:

• G/L accounts for posting sales revenue, sales deductions, and

VAT are to be determined automatically when data is
transferred from the billing document to FI.
• When processing cash sales, a G/L account must be set in
the document for cash settlement (no posting to customer
account)
• In addition, the system can determine a reconciliation account
that is different from the account that is entered in the payer
master record.
• When using payment cards, you also need to post to
differing G/L accounts.

Account Assignment Criteria in Billing

The sales revenue accounts are created in FI, in order to receive certain
evaluations and to be able to carry out reconciliation with the Profitability
Analysis.

For this reason you can set different criteria for account determination of the
relevant accounts. The following criteria are defined in the standard system:
• Chart of accounts
• Sales organization
• Account assignment group for payer (Payer Master Record)
• Account assignment group for material (Material Master Record)
• Account key (Discounts and surcharges – Pricing Procedure)

Revenue Account Determination

Account determination is carried out using condition technique.

Depending upon the billing type, an account determination procedure is

assigned for G/L accounts.

This determination procedure contains one or more condition types to

which an access sequence is assigned.

This access sequence is composed of individual accesses in the form of

condition tables.

The condition tables contain the fields and field combinations upon which
revenue account determination depends.

The key fields are filled with document data, so that the system can search for a
corresponding G/L account for the relevant combination.

If an access determines a G/L account, then it is set in the accounting document

and search is determined.

The account for posting VAT is not determined in account determination in

Sales and Distribution. The relevant assignment is stored in Customizing
for Financial Accounting.

Account Assignment for Business Areas

Business Areas

A company code represents an independent accounting unit. The balance

sheet and the profit loss statement required by law are created at this level.

A business area can report financial information across several company codes
with regard to specif fields of activity.

Business area balance sheets and profit and loss statements can only be
used for internal reporting.

G/L accounts can be posted by business area.

The Business area has no fixed assignment in Customizing; it is determined

per order item according to certain rules.

Determining the Business Area

You can specify the rules you want to use for determining the business area
for each sales area.

These rules are available (this can not be extended):

• Business area assignment by plant and item division

• Business area assignment by sales area
• Business area assignment by sales organization, distribution
channel, and item division

This can lead to different business areas being determined for several items
within the same order.

SD/FI INTERFACE

Link to Financial Accounting

The system sends billing data in invoices, credit memos, and debit memos
to Financial Accounting and posts them to the correct accounts.

The following data can be changed before an accounting document is

created:

• Billing date
• Pricing
• Account determination
• Output determination data

Once the billing document, has been released to accounts, you can only
change output data.

Posting Block

Normally, the system automatically transfers accounting-related data to Financial

Accounting.

However, you might not want the data to be transferred automatically for certain
billing types. In that case you can set a posting block for the billing type
concerned.

The system will then generate the accounting documents only after you
have released the billing document.
This allows you to generate Sales and Distribution billing documents first, then
print out the billing documents and finally, transfer them to FI. In this way you
can improve system performance.

Reference Numbers and Allocation Numbers

You can automatically fill the Reference number and allocation number fields
in the accounting document with numbers from SD documents.

The reference number is in the header of the accounting document and is

used for clearing.

The allocation number, is in the customer line item and is used for sorting line
numbers.

In Customizing for copying control in billing, you can define which numbers
will be copied as reference or allocation numbers:

• A – Purchase order number

• B – Sales order number
• C – Delivery number
• D – External delivery number
• E – Billing document number
• F – External delivery number if available, otherwise delivery number

Reference Numbers in Invoice Lists

You must first create billing documents and post them to Financial
Accounting before you combine them in an invoice list. The number that was
saved as a reference number in copying control is then transferred to Financial
Accounting.

When the invoice list is created, the reference number from the invoice list
overwrites the reference numbers from the individual billing documents.

Ex.: 90000001 - 90000004

90000002 - 90000004
90000003 - 90000004

This enables you to post incoming payments with the invoice list number.

Transaction-Related Document Types

You can differentiate between document in Financial Accounting by using the
document type.

Up until now, the system has given all Sales and Distribution documents the FI
document type RV.

You can carry out differentiated number assignments, by using the

document type field within the billing document type configuration.

CAI NA PROVA

Head Office and Branches (filial)

When maintaining master data, you can represent the relationship between
the head office and its branches.

You can either represent this relationship with the partner functions in Sales and
Distribution, or with the Head office field in the accounting segment of the
customer master record.

You can use the Head office/branch field in the billing type to control which
partner functions in the billing document should be transferred do Financial
Accounting.

Negative Postings

In the SAP standard system, cancellations and credit memos are posted on
the opposite side of the account as compared to posting receivables to the
customer.

Customers requested that credit memos and cancellations could be posted

on the same side as receivables. This allows the account to have a zero
balance.

If you wish to do this, you must activate the Negative postings field for the
billing types for credit memos and cancellations.

The system transfers this information to Financial Accounting across the FI-
CO interface.

Value Dated Credit Memos

The period for the billing document baseline payment date can be used as
the basis for value dating the credit memo.
Controlling processing of credit memo value dating is carried out via the
value dated credit memo field in billing types.

If this indicator is blank, then the procedure continues as usual, that is, the credit
memo is due immediately on the billing date.

If the Value Credit Memo field is selected in the credit memo billing type, the
reference billing document is not cleared, and if the baseline date for payment
for the originating billing document is after the billing date in the credit memo,
the baseline payment from the originating billing document is entered in the
Value Date Field in the credit memo.

Copying Control

Document Flow

Data is copied from the preceding to the subsequent document in the

process. This process chain is captured in the document flow.

The document flow is updated at full document level. If the “Update

Document Flow” indicator is set in copying control, the document flow
is updated for individual items too.

Creating with reference

You can create sales document with reference to documents that were
created previously.

You can enter a different requested delivery date for all the items in the
new document.

In this way you can transfer individual items and partial quantities from the
reference document into the new document.

You cannot copy incomplete sales documents.

Copying control – Overview

There are Copying control tables for Sales Document, Deliveries and Billing
Document. They can control:
 • Copying Requirements
• Allowed source and target documents
• Data transfer routines
• Update document flow
• Transfer schedule lines?
• Influence the document status
• Quantity/Value Update
• Control of price determination

There are three levels for copying control for sales documents:

- Header
- Item
- Schedule line

Copying Requirements

Before data is copied from the reference document to the target document,
certain requirements must be met.

Significa atender alguns requisitos para passar adiante.

Once the copying requirements are satisfied, the specified data transfer routines
are executed.

Copying Control – Header Level

The detailed screen for a selected “Target document type/Source document

type” pair contains:
• Copying requirements
• Data transfer routines
• The agreement on whether or not item numbers are copied to the
target document
• The “full reference” agreement

Copying Control – Item Level

In copying control, the item level controls are defined for each item category for
every “Target document type / Source document type” pairing.

The details screen for an item category contains:

 • Copying requirements
• Data transfer routines

And includes the following important entries:

• Quantity/value pos/neg:
• Copy quantity
• Pricing type
• Update document flow

The item category determination rules also apply when you create sales
documents with reference.

TEXT CONTROL

Pode-se ter textos em Customer Master Record, Material Master Record,

Customer/Material Master records and in all Documents.

The Customer master records, contains central texts, texts specific to

Accounting and to Sales and Distribution as well as texts for contact
persons. You can define different text types for each of these areas.

Sales note, marketing note, shipping specification are example of text

types.

The material master record contains a purchase order text and a sales text.

Documents contains texts at header and item level

You can enter a text in several different languages.

Texts in Business Processes

Texts can also be copied from a reference document to another sales and
distribution document.

Texts can be copied in a specific language.

You can determine the conditions under which texts are to be copied, for
example, whether the text is copied from the customer master record, or from a
preceding document.

Text Control Overview

You can define different text determination procedures for each text object.
Example, the sales document header or the central text for a customer.

The text determination procedures contain all the text types that can be
maintained for a text object.

Each characteristic in a text object must be assigned to one of the defined

procedures.

You can define an access sequence for every text type in the text
determination procedure for documents.

You can also define specific controls for each text type, such as including a
text type in the incompleteness log.

Text Control – Text Type

A Text Type is created for a specific text object.

Text Control – Permitted Text Objects

Every access step contains a specified text object as the source for the
access.

Text Control – Text Determination Procedure

Text types are included in a text determination procedure. The text

determination procedures contain all text types that can be maintained for a text
object.

For document text determination procedures you can also specify whether:

• A text should be mandatory (Incompleteness log)

• The text should be determined automatically
• Whether the text should be displayed in a text window (popup)
when it is transferred to the document
Text Control – Procedure Assignment

Each attribute of a text object must then be assigned to one of the defined
text determination procedures.

This means that when you create a customer master record, the system uses
the text determination procedure that has been assigned to that customer’s
account group.

Using Texts as Reference

For each text type in a text determination procedure, you can determine
whether the text adopted is copied

Text Source “Preceding Document” in the Billing Document

The text source for text objects VBBK (Sales and distribution header texts) and
VBBP (Sales and distribution item texts) can be selected in the configuration for
the billing type.

If “Text Delivery” is switched off, the corresponding texts are taken from the
order.

If “Text Delivery” is switched on, the corresponding texts are taken from the
outbound delivery.

OUTPUT DETERMINATION

Output in the SAP system is for communication purposes (particularly with the
customer).

The information that influences output determination is stored as master data, in

the form of condition records.

Output Types in SD

Output is a means of communication for exchanging information between

partners and systems.

In the Sales document, Delivery document and Billing document, you have
the follows Output Types:

• Order confirmation (BA00/BA01)

• Delivery note (LD00)
• Invoice (RD00)
• Cash Sales invoice (RD03)
• Sales activity (KO00)
• Mail Credit processing (KRML)
• Scheduling agreement (LP00)
• Quotation confirmation (AN00)

You can make output determination dependent on different criteria. The

condition technique is used for this.

Todo output tem que ter uma Transmission media.

Transmission Media

The transmission medium determines how output is issued. For example, you
can agree with the customer that an order confirmation is sent by EDY or that
notification is given beforehand by way of the Internet.

A program with the relevant layout sets can be assigned to each output type
and transmission medium.

Communication Strategy

A communication strategy represents a sequence of communication types.

The communication strategy can be used for external transmission.

Timing of Output

You can determine when an output is to be issued.

The following times are available:

• You can run at regular intervals.

• Automatically
• Explicit

Overview of Output determination

Output is determined using the condition technique.

You determine the transmission medium, the time and the partner function in
the condition record.

It is also possible to create output that is not dependent on a particular partner.

Output Processing
Procuring and Preparing Data

The structure and data in the documents that are processed online are stored in
the database.

To transmit output, the system procures the data from the database and
prepares it for the required transmission medium.

Printing Data
The system procures and prepares data in two sparate steps when printing
documents.

The printing controls are defined in the SAPscript form, independent of the
print output program.

The output is then transmitted to a printer or other output device.

É assim que se cria a Nota Fiscal.

New Fields for Printing Documents

Simple changes that do not need preparation logic or new fields in the
communication structure can be processed directly in the form with
SAPscript.

A form modification is “pure” if the following prerequisites are met:

• The field exists in the communication structure

• The field is NOT contained in the form
• The field can be integrated into the form in an existing format

Integrating a New Output Type

New output types are normally based on existing document types.

This means that if you need to create any document, you can copy most of it
from an existing communication structure.

The real work starts when writing the processing program and its form definition.

Adapting the User Interface

Controlling the Customer Master Using the Account Group

Sales data constitutes the basic data for SD and Shipping.

Company code data constitutes the basic data for FI.

General Data is assigned directly to clients. It is then valid for both the various
company codes as well as the different sales areas.

Customer Master – Account Groups

An account group is a classification within the customer master records.

The account group specifies:

• Which entries in the master record are required or optional

• The number range for the customer account number
• Whether the number is assigned by the user or system
• Whether or not the account is a one-time account
• Which output determination procedure is used

You can add your own account groups to those that are predefined in the SAP
standard system.

Customer Master – Selecting Fields for Data Groups

You can use field selection for each account group to determine whether field
entries are option or required. Any fields that are not required can be hidden.

The field status information for the two influencing factors (account group
and transaction) are combined in pairs.

Table Control

Table control is a display element that enables you to configure the table view to
meet customer-specific requirements.

Transactions Variants / Screen Variants / GUIXT

Transactions processes can be simplified with screen variants. These can:

Alterar as telas e ocultar o que não interessa.

• Enter default values in fields
• Hide and change the ready for input status of fielsds
• Hide whole screens

A transaction variant is made up of screen variants.

A transaction variant is assigned to one transaction alone. Each transaction

can have several variants.

Transactions variants are only permitted for dialog transactions.

The supplementary tool GuiXT allows for flexible design of individual screens.