SAP Business suit

SAP Business suit categorized by Net weaver technology is based

1. Cross Industry 1. People
2. Industry 2. Information
3. Technology 3. Process
4. Services

Client: A self-contained unit in an SAP system with separate master records and its own set of tables.
Instance: Instances are the smallest elements for designing system landscapes. They group technically dependent software component versions
which have to be installed and operated on a single logical system/server.
Landscape components: server, databases, systems, system components
A project is a complex sequence of activities taken to reach a certain goal, with defined start and end dates. Reflecting the project goals,
Implementation projects cover initial implementations of new applications and functional enhancements of existing solutions.
Upgrade projects take care of both technical and functional upgrades.
Continuous improvement projects manage software maintenance, technical optimizations, and business process optimizations

Business Scenario: A business scenario is set of business processes that define a business task in a comprehensive way on macro level. A
business scenario is normally related to a company’s business unit, a central function, or a profit center, and it can also involve business partners
from other companies. A Business Scenario may consist of a number of variants, each of them describing an end-to-end business flow. Each end-to-
end business flow is represented by an ordered sequence of business processes. A Business Scenario requires one ore more SAP components or
non-SAP software.
Business Process: According to the definition of Davenport & Short (1990), a business process is “a set of logically related tasks performed to
achieve a defined business outcome”. Each process is composed of several process steps and can run across several SAP components and
possibly non-SAP software. A business process may occur in one or more Business Scenarios
Business Process Step: A business process step is an elementary activity performed to accomplish a process. It is carried out either by a user or
by a system. Each process step runs only in one software component. In many cases, it is represented by one transaction. This means, that the step
ends in the same software component in which it has been started (leading component). However, functions in other software components may be
invoked to provide information that is required to perform the process step but is not available in the leading component, e.g. availability check in a
warehouse management system during sales order processing in a CRM system. In such cases, the function invoked needs to be represented as
an additional business process step.
Business Side:
Program management office : communicates these requirements to the IT organization, decides on the financing of development and operations,
and ensures that the requirements are implemented.
Business process champions: define how business processes are to be executed.
End users: use the implemented functionality to run their daily business.
Key users: provide first-level support for their colleagues

Technical side:
Application management: team is in direct contact with the business units. It is responsible for implementing the business requirements and
providing support for end users.
Business process operations: Covers the monitoring and support of the business applications, their integration, and the automation of jobs.
Custom development: takes care of adjusting the solution to customer-specific requirements and developments.
SAP technical operations: is responsible for the general administration of systems and detailed system diagnostics.
IT infrastructure: organization provides the underlying IT infrastructure (network, databases,).

There are 16 standards for solution operations defined by SAP:

• Incident Management describes the process of incident resolution
• Exception Handling explains how to define a model and procedures to manage exceptions and error situations during daily business
operations
• Data Integrity avoids data inconsistencies in end-to-end solution landscapes
• Change Request Management enables efficient and punctual implementation of changes with minimal risks
• Upgrade guides customers and technology partners through upgrade projects
• eSOA Readiness covers both technical and organizational readiness for enterprise service-oriented architectures (eSOA)
• Root Cause Analysis defines how to perform root cause analysis end-to-end across different support levels and different technologies
• Change Control Management covers the deployment and the analysis of changes
• Minimum Documentation defines the required documentation and reporting regarding the customer solution
• Remote Supportability contains five basic requirements that have to be met to optimize the supportability of customer solutions
• Business Process and Interface Monitoring describes the monitoring and supervision of the mission critical business processes
• Data Volume Management defines how to manage data growth
• Job Scheduling Management explains how to manage the planning, scheduling, and monitoring of background jobs
Transactional Consistency safeguards data synchronization across applications in distributed system landscapes
• System Administration describes how to administer SAP technology in order to run a customer solution efficiently
• System Monitoring covers monitoring and reporting of the technical status of IT solutions
 Client
A commercially, organizationally, and technically self-contained unit within an SAP System. Clients have their own master records and set of
tables.
The client is the highest level in the SAP System hierarchy. Specifications that you make, or data that you enter at this level are valid for all company
codes and for all other organizational structures. You therefore only need to make these specifications, or enter this data once. This ensures that the
data is consistent
This means that you cannot include customer accounts from different clients in one dunning run.

Company
- The smallest organizational unit for which individual financial statements are created according to the relevant legal requirements.
- A company can include one or more company codes.
- A company’s financial statements also form the basis of consolidated financial statements
- All of the company codes within a company must use the same chart of accounts and fiscal year.
- However, each company code can have a different local currency.

Chart of Account
For each G/L account, the chart of accounts contains the account number, account name, and the information that controls how an account
functions and how a G/L account is created in a company code.
You have to assign a chart of accounts to each company code. This chart of accounts is the operating chart of accounts and is used for the daily
postings in this company code.
You have the following options when using multiple company codes:
 You can use the same chart of accounts for all company codes
If the company codes all have the same requirements for the chart of accounts set up, assign all of the individual company codes to the
same chart of accounts. This could be the case if all company codes are in the same country.
 In addition to the operating chart of accounts, you can use two additional charts of accounts
If the individual company codes need different charts of accounts, you can assign up to two charts of accounts in addition to the operating
chart of accounts. This could be the case if company codes lie in multiple countries.
Charts of accounts can have three different functions in the system:
 Operating chart of accounts
The operating chart of accounts contains the G/L accounts that you use for posting in your company code during daily activities. Financial
Accounting and Controlling both use this chart of accounts.
You have to assign an operating chart of accounts to a company code.
 Group chart of accounts
The group chart of accounts contains the G/L accounts that are used by the entire corporate group. This allows the company to provide
reports for the entire corporate group.
The assigning of an corporate group chart of accounts to a company code is optional.
 Country-specific chart of accounts
The country-specific chart of accounts contains the G/L accounts needed to meet the country's legal requirements. This allows you to
provide statements for the country's legal requirements.
The assigning of an country-specific chart of accounts to a company code is optional.

Company code
Characteristics
Legal entity and independent accounting unit org units can be assigned to a company code
o Have a Balance Sheet and Profit & loss Statement sales organization , Plant
o Represents a legal company or subsidiary
o A company code and business area represent a group from a financial perspective. Several companies can use the same chart of
accounts
o More than one sales org can be assigned to a company code. You can assign a sales organization to several plants within the same
company
o This includes the entry of all transactions that must be posted and the creation of all items for legal individual financial statements, such as
the balance sheet and the profit and loss statement.
Business area
o Business area represents an organizational unit for which you can carry out internal reporting.
o A company code may be divided into multiple business areas
o A business area may also be shared by several company codes. For this reason BA must have the same description in all company codes
o 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
o The relevant business area is determined for each order item according to defined rules
 Sales organization Org structure in SD
o Sales organization
Characteristics o Distribution channel
o Each sales organization has it’s own master data o Division
o Liable for products sold and for customers rights of recourse Optional
o Sales office
o Negotiate Sales conditions
o Sales group
o Distribute goods
SO an organization element that represents the company's S & D activities
A SO has an address and is a business unit that is responsible for product liability and rights of recourse Transaction Data
o Incoming invoices.
You must create at least one SO in your R/3 system and you can define your own master data in a SO
o Outbound deliveries
Sales organization is uniquely assigned to only one company code
All SD documents are assigned to a sales organization.

Distribution channel Division

 You can define your own sales documents types for a
distribution channel
 Provide the structure in which products/services are
distributed
 Is a means to ship goods to the customer e.g. (Whole
sale/Retail)
 All the items in a billing document belong to the a distribution
channel
 Represents strategies to distribute to customers
 Distribution chain consists of sales organization and D.C
 All the items in a billing document belong to the a distribution
channel
 Master data can be varied by distribution channel
Characteristics
o Division is used to group materials and services
o Division represents a broad product line
Several divisions can be assigned to a Sales Organization
A material always belong to only one division
Division have two main applications;
o It is a org unit of SD
o it is necessary for business area account determination for
logistics transactions in FI.

Sales Area Sales office

SA appear in all the Sales & Distribution documents More than one sales office can be assigned to a Sales Area, and a sales
office can be assigned to many sales areas
SA is used for updates in the Sales information System
A Sales Group is assigned to a Sales Office
SA is used to determine the sales price calculation in sales pricing
Sales Office, Sales Group and Sales Employee represent an internal
Customer master data contain data that is specific to the Sales Area structure
Sales documents are always assigned to a specific Sales Area A Sales Office can have more than one Sales Group assigned to it.
All sales, delivery and billing documents will always be assigned to a
sales area and therefore will you be able to carry out sales analysis
within a sales area

Plant
Characteristics Plant determined in sequence
o Can be a Stock keeping location - Customer material info record
o Can be a production facility - Customer master
o Can be a location from where SD can distribute stock - Material master
∙ Pant is uniquely assigned to one company code only
∙ Plant can be assigned to SO/ DC in relation of One to Many
∙ Plant can be assigned to SO/ DC in relation of Many to One
∙ plant is determined in a very specific Plant be assigned to a SO/DC of another company
∙ A plant can be assigned to many SO for a specific DC
∙ A plant can be linked to a SO of another company. (The result will be intercompany sales.)

Shipping point
∙ A Shipping point represents the highest-level organizational unit that control your shipping (delivery) activities
∙ Facilitates distribution and can be a group of people, a rail depot, a warehouse etc
∙ More than one plant can be assigned to one shipping point and more than one shipping point can be assigned to a plant
∙ A single delivery will be processed by just ONE shipping point
∙ The shipping point is determined by the shipping condition, loading group and the delivering plant.
∙ A shipping point can be divided into many loading points.
Default value of a shipping point can be changed manually in a sales document as long as the new shipping point has been added in the shipping
point determination in customizing

Functions
Sales Document
 Availability check
SD process Pre-sale activities, Sales order processing, Procurement, Shipping, Billing, Payment  Messages, Output and
Source of data texts
 Delivery schedule
o Master data (customers, materials, condition records)
 Pricing
o Other documents (quotations)
o Customizing tables (shipping point determination) Document types used in SD
o Sales document type
o Hard coded controls (ABAP programs) o Delivery document type
o Billing document type
 A Quotation can have many orders
Match codes for a sales order
 An order can have more than one ship to party but only one payer o Customer master
 Delivery data for shipping is located on the schedule lines. o Material master
 The Sales Order contains all the relevant info for completing the whole process
Input tools for the S.D
 An item is considered complete when the full quantity or value has been referenced. document
 Each item of the sales order has separate data and contains data about goods & products or  Customer master
services ordered by the customer like Material numbers, descriptions, prices, terms of delivery and  Material master
payment.  Customer material info
record

Order combination (many orders - one delivery) Data proposed from

Customer
o Shipping point, Delivery date, Ship to party, Route
∙ Partners
o Incoterms, Order combination indicator on customer master ∙ Plant
∙ Pricing
∙ Output
Document type determines the delivery date in a sales order Material
The required delivery date is proposed by entering the lead time in days in the sales document type in addition ∙ Plant
to collecting the 'propose delivery date ∙ Pricing

If the Sales unit of measure has been maintained in the material master, the Sales Unit of measure will be Customer material info record
displayed in sales order
∙ Plant
Delete ∙ Customer specific
You can only delete a complete sales document if there are no subsequent documents. material numbers and
You can delete individual items in a sales document if there are no subsequent documents descriptions
∙ Minimum delivery
Change the sold-to party, you need to redetermine the related data: quantity
∙ Partial delivery/item
 All business partners and data that arise from the sold-to party
∙ Maximum partial
 Texts deliveries
 Free goods Additional master data
 Prices - Output
- Incompletion log
 Output - Common master data
( DC / Division )
 Profitability segment
 Customer master data (including the fields for Brazil and Argentina)
MASS  SAPMMSDL
 Data from the sales information record (such as the customer material number)
Billing date from
 The system re determines the plant if the system reads info records according to the sales order Billing type
type, or the ship-to party changes SD document type
Sales organization
 The system re determines shipping points and routes if the shipping conditions change Distribution channel
The system does not redetermine the following data: Division
Shipping point
 Material number (info record, material determination, product selection) Sold to party
Destination country
 Sales office and sales group
 Product allocation (availability check can be triggered manually) Object type

 Batch determination (can be triggered manually) BUS2032 Sales orders

BUS3006 G/L accounts
 Reference data for the previous sold-to party (such as the purchase order number) remain the same KNA1 Customers
but can be changed manually if necessary LFA1 Vendors
In document processing, you can change the sales document type in the overview screen (Sales tab page)
simply by selecting the required document type. ( alternative document type)

SD integration Sold to party Edit  Fast changes Delivery blocks V.14

FI - Credit management  Pricing Reason for rejection
MM - Availability check Sales document types.
PS - Projects  Inco terms Delivery block schedule line category
 Shipping condtion
Billing block sales orders-Header data
SO creation w/r
Inquiry Payer Delivery data Sales order-Item data.
Quotation  Payment terms Delivery priority Plant
Order  credit limit checks
Contract Billing Blocks VD05
Schedule agreement Ship to party sales documents types
Billing Document  Delivery address Sales doc item categories.
 Tax
sales orders-headers data
 Good rcv hours
sales orders-item data

Schedule Line Category Control

Schedule line contains delivery date and quantities as well as the requirement transfer and inventory management

Two type to automatic determination

1. Item category and MRP type
2. Item category and No MRP type

The various schedule line categories are controlled in different ways:

 The schedule line AT in inquiries is used only for information.
 No requirements are transferred and no availability check is carried out for the schedule lines BN and CN.
 Requirements are transferred and the availability of the material is checked for the schedule lines BP and CP.
 No stocks are managed for the schedule line categories BT, CT and CX.
 No goods issue is posted for the categories BT and CT. However, goods issue is posted for CX.
 The schedule line categories BV and CV are controlled in the same manner as the categories BN and CN. However, requirements can be
passed on for analysis purposes.
 Goods receipt is posted for the schedule line DN in a returns document.
 The schedule line categories CN, CP, CT, and CV are relevant for delivery; the other schedule line categories are not.

First character Second character

A  Inquiry D  No inventory management
B  Quotation N  No MRP
C  Order V  Consumption based planning
D  Returns X  No inventory mgt with goods issues
P  MRP
 Sales order process
Inquires
Inquiries are non binding information
An inquiry will be closed once it has been referenced and a quotation will only be closed once the total
quantity has been referenced or rejected.
VA05  SAPMV75A
Quotation Sold to party
 Quotation are legally binding for the validity period of the quotation Material
Purchase orders
 You can have alternative products in a quotation Open sales order
 Using the selection list, you can copy the main item and any alternatives into the document All orders
My orders
 Using the selection list, you can only copy either the main item or the alternative item into the sales
order .An order can reference a quotation that has a valid to-date in the past
Cash sales
o When saving the order, a background delivery is created.
VBELN - sales document
o Cash sales generate order and delivery document numbers. VBELN - Delivery
o When saving the cash sale, the billing due list is updated because cash sale is order related
o Receivables do not occur for the customer as they do for rush or standard orders, because the AUART- sales document type
invoice amount is posted directly to a cash account. LFART - Delivery type
Rush order FKART - billing type

o In a rush order, the goods issue must still be performed. VBTYP - document category
o when you save this sales document type, a delivery is automatically created and billing is related to FKTYP - billing category
the delivery.
POSNR - sales doc item
o For rush order the system will print an invoice when the billing is created, to be send to the customer
Scheduling agreement

 An outline agreement with the customer containing delivery quantities and dates. You can either
create schedule lines when you create the S.A or you can create them later.
 You fulfill a scheduling agreement by creating the deliveries in the schedule as they become due. BOM
Can’t used in Free goods process
 After you have carried out the delivery, the system updates the Delivered quantity field in the
scheduling agreement item with the delivery quantity.
 If there are still outstanding items in the agreement but you nevertheless want to close it, you can
assign a reason for rejection to these items. The system then sets the status of the agreement as
complete and the outstanding items no longer appear in the delivery due list
Third party order
o A purchase requisition is generated automatically from the sales order.
o The item category controls third party processing.
o Purchase order changes are automatically updated in the sales order.
Return order
o A returns document have a billing block
o A returns document can be referenced to a sales document or a billing document.
o A returns document can be created without a reference to another document
Debit/Credit memo
o Debit and credit memos is used to correct value only and no stock is corrected
o Debit and credit memos are order related billing
o Debit and Credit memos can be reference to either a sales document or a billing document
o Debit and credit memos as well as returns will have a billing block TANN pricing B
Free goods
R100
o Free goods determination procedure will use the sales area, document pricing procedure Req 55 Check the indicator B
( document type) and the customer pricing procedure (customer master) to be able to determine in pricing
Free goods
NRAB
o Free goods determination use condition technique to determine calculation of free goods
Req 59 determine the discount
o The item category is assigned with usage FREE for free goods process from free goods factor
CBF 29
o Each access sequence for free goods determination contain condition table that form the key for the
checks whether free goods have
master data (condition records already been determined
 o You can activate analysis in the sales document for free goods determination. This will then display
condition category F
detailed information on how free goods were determined
o Discounts can be provided in the form of the free goods based on quantity of items ordered
calculation type
o Inclusive free goods will not be displayed on the billing documents
∙ proportional
o Exclusive free goods will not be displayed on the billing documents, but it will show i the sales ∙ unit-reference
document as free of charge ∙ whole unit
o The item category determines how the free goods will be handled in the process
Calculation type for determining free goods quantity

The calculation rule defines the manner in which the free goods amount is calculated from the free goods
quantity, additional quantity and the document quantity.

Example:Free goods quantity = 100 pieces

Additional quantity = 3 pieces
document quantity = 280 pieces:
Free goods for proportional = 8 pieces (= 280 / 100 * 3 rounded down)
for unit-reference = 6 pieces (= 200 / 100 * 3)
only 2 * free goods quantity considered
for whole unit: = 0 pieces 280 is not a multiple of 100
Invoice correction
Invoice correction
First  Credit entry
o Invoice correction is used to correct quantities and value on a billing document Second  Debit entry
o The invoice correction will create a debit and credit entry and you can only correct the debit entry.
The Credit entries will be listed first in the document and then the debit entries
Fast changes
o Fast change function enable you to simultaneously block all items that you have selected in a
document
o Fast change function let you change the pricing, plant, currency or materials in several documents
at the same time
o Fast change function let you change several items of a document at the same time
Backorder
o An order can be back-dated if the quantity of an order is not totally confirmed
Quantity contract
o An order can be back-dated if the delivery date for an order item cannot be kept Header  Contract data
o Back orders can be processed manually or automatically via rescheduling Item  Billing plan
Contracts
Quantity contract does not contain any schedule lines, delivery quantities, delivery dates
o Agree on special price agreements or delivery times
Value contract
o Customer fulfills the contract with individual releases o Special price
agreements
o Customer restriction
Value contract Customer agree to purchase a fixed dollar value (target amount ) of goods and services o Material restriction
during a defined period. The value contract is similar to a quantity contract in that the
subsequent function is the creation of a release order. Grouping Master contract
 The value contract can be billed directly or via the release orders.
∙ Quantity contracts
 The subsequent function is a release order. ∙ Value contracts
 They can be for a specified time period. ∙ Service contracts

 A master contract only contains header level information. Master contract contains
The lower level contracts must be assigned to the same sales organization as the master contract.
∙ Business data
You can define the sold-to party authorized to release against a contract in the partner screen of a contract. ∙ Partner data
This partner may only schedule orders with reference to this contract, even when he is not the sold-to party ∙ Contract data
authorized against a contract. ∙ Billing plan data

WK1  Diff material WKN VCTR( usage ) VCIT (Item category group )
WK1  General value contract
WK2  For single material WKC VCIT (usage ) WK2  Material related value cont
WK0001  Pricing procedure, WK00  Condition Y – document procedure QP  Rental contract
SC  service & materials
QC  Quantity contract
Partner authorized to release contract at header level only
AA  sold to party contract release PDP  KAB assigned to
AW  ship to party contract release
Item customizing
Value contract material WKM1
Contract release ctrl A (warning if target value is exceed ) GK  master contract document

VEDA  Contract data

Contract profile contains values for contract data that can be proposed when you create a contract.
 Date determination rule for contract start date FPLA  Billing plan header
 Date determination rule for contract end date
 Validity period category
 Cancellation procedure
 Follow-up action to be carried out before the contract expires
 Date determination rule that specifies when the follow-up action is to be carried out

 Master contract contains general conditions that are valid for all the lower level contracts
 Group contract only contain header data, therefore no items

Complaints Processing
Implementation Considerations You can process complaints in the following ways:
 Example 1: The customer returns the goods. You create a return to process the transaction.
If the customer wants a refund for the amount, enter a credit memo with reference to the return.
If the customer wants a replacement product, enter a free-of-charge subsequent delivery with reference to the return.
 Example 2: The customer does not send the goods back.
If the customer wants a refund, you enter a credit memo request with reference to the sales order or the invoice.
If the customer wants a replacement product, you create a free of charge subsequent delivery with reference to the sales
order.
 Example 3: The price is wrong.
For example, the discount was forgotten or the scaled prices were miscalculated. You then enter an invoice correction request with
reference to the invoice.
Example 1
You sent the customer 100 pieces. The customer sends 30 back because they were damaged during transport. You create a
return for 30 pieces and then either a credit memo or a free-of-charge delivery with reference to the return.
Example 2
The customer reports that a further 10 units were so damaged that they threw them away. You enter either a credit memo
request or a free of charge subsequent delivery with reference to the sales order or invoice.
Example 3
100 units were calculated at 10 USD per unit for the customer. However, due to a promotion they should have been calculated
at 9 USD per unit. You enter an invoice correction request with reference to the invoice and enter the price as 9 USD per unit.
Prerequisites
Process Flow
1. You decide which one of the above scenarios is most similar to the type of complaint you are processing.
Enter the appropriate sales document, with or without reference to an order or invoice.
2. You can change the settings in Customizing so that the sales document is automatically blocked for a delivery or billing. This means that
the system does not create a free-of-charge delivery or a credit memo until you have had the opportunity to check the goods or clarify the
complaint.
3. Once you have checked the goods or clarified the situation, you can:
Approve the complaint by releasing the sales document.
Reject the complaint by entering a reason for rejection in the sales document.
If you do not need any release procedures for credit memo requests, you can also create a credit memo with reference to an invoice. In
this case, you do not need either the credit memo request or its release.
Result Once you have released the sales document, you can create a delivery or a credit memo.
Free of Charge Deliveries FD
You can create free of charge deliveries for sending samples of your products to the customer. The system will then generate a delivery
based on the free-of-charge delivery.
For free of charge deliveries, you can do one of the following:
o Approve it by deleting the delivery block.
o Reject it by entering a reason for rejection.
When you create a free-of-charge delivery, you must enter a value in the Order reason field or the system informs you that the document is
incomplete.
Free-of-Charge Subsequent Delivery
You can create a free-of-charge subsequent delivery if, for example, a customer receives too few goods, or if the goods have been damaged in the
shipment. The system uses the free-of-charge subsequent delivery to create a delivery.
To create a free-of-charge subsequent delivery, you have to refer to an existing sales document, such as the:
 Sales orders , Contracts , Contract release orders

Delivery Delivery header

When a goods issue is posted it integrates with FI - Texts
 Integrate via MM to FI through table 30 of MM - Partner
- Output
o Delivery manually with/without reference to a particular order
o Delivery due list can be executed online or background job - Reference order
o Picking can be processed collectively - Route determination
- Storage location rule
The general data may include: - Delivery split WM
∙ Shipping point - Automatic packing
∙ Data about delivery scheduling and transportation scheduling (for example, the goods issue date - Gen pack material item
or the date of delivery to the ship-to party)
∙ Weights and volumes of the entire outbound delivery
Delivery Item
∙ Sold-to party and the ship-to party numbers Check for over delivery
∙ Route Picking location determination
Origin of data in the delivery Text
 Data from the customer master record of the ship-to party Availability check
 Data from the material master records of the delivery items Check minimum delivery quantity
Changing and adding to the outbound delivery Automatic batch determination
- Ship to party and shipping point will not change if delivery created Check quantity 0
- We can change or add to delivery documents after they have been saved Relevant for picking
- We can also add items to the outbound delivery without referring to an order
- You can delete individual items from the outbound delivery or add new items to it. Mandatory sub-process of delivery
o Delivery create
Prices in outbound delivery Shipping related condition at header level such freight costs o Goods Issue
Complete delivery
Splitting an existing delivery (one order - one delivery)
o We can split existing delivery into small deliveries
Partial delivery
o Split deliveries called ‘ Results ‘ and ‘ Remainders’ (one order - many deliveries)
o Split profile determine the type of split
VL04  RV50SBT1
o Split profile assigned to delivery types Shipping point
Delivery creation date
Delivery interface
Sales organization
- EDI messages are used for external communication Idoc DELVRY02 ( 4.6 A ) Distribution channel
- ALE messages are used for Internal communication DELVRY03 ( 4.6 B ) Division
Sales office
- DELVRY02 & 03 data structures that consist of segments and contain the fields for the delivery and Sold to party
other relevant for shipping such as route & Batch Ship to party
Material
Plant/storage location
Shipping point determination ( shipping point cannot be changed in delivery)
( Shipping point determined in item level) Delivery block OVLS , OVLX

 Delivery plant  CMR, SH from customer, material master record

 Shipping conditions  SD doc type, SP in customer
Delivery scheduling
 Loading group  Material master ( sales general plant )
Pick pack time & Loading time
Route determination
o From the shipping point
 Departure zone of shipping point ( country )
Transportation scheduling
 Shipping conditions
Transits time & TP lead time
 Transportation group assigned to the material (sales general plant )
o From route
  The country & transportation zone of SH
In order item, we can manually overwrite the route that is determined. We can redetermine route in A route schedules contain
outbound based on the weight (weight group ) route is redetermine depend on the configuration of the A route
delivery type
A weekday as the departure date,
System determines required material availability based on delivery date requested by customer. along with a departure time

- Transit Time  Time required to ship a delivery to the ship to party A list of ship to parties

- Loading time  Time required to load the goods An itenary ( optional )

- Pick/ pack time  Time required for picking, packing and son on
- Transport planning lead time  Time required to organize the shipment Route schedules used in
o Sales order
Precious scheduling o Stock transfer order
o Out bound delivery
- The system calculated and displays the results of scheduling down to the minute
- In daily, scheduling the system use days,hours,and minute for calculate but only display the
resulting date Goods issue
- If you maintained working times of shipping point , the system perform precise scheduling o Manually
- Shift sequence is define the shifts for each week day and define starting and finish work o Collective process
Route schedules o For TO confirmation
- To organize outbound deliveries from a particular shipping point to different Ship to parties o Delivery monitory
- Assigned to each shipping point order type, delivery type, purchasing document type, plant

Specific activities in shipping process

o Monitoring the deadlines of reference documents due for shipping
o Creation and processing of outbound delivery
o Monitoring of the capacity situation in the warehouse
o Support of picking
o Packing
o Printing and distribution of shipping document
o Process of goods issues
o Controlling
Loading point
- Loading point are stored manually to the delivery header
- Any number of Loading points are assigned to a shipping point
- Only one shipping point can be assigned to loading group
-

Picking
user exit VO2V002
- Delivery item category determines item relevant for picking
Warehouse structure
- Picking area can defined for WM number and storage type - Warehouse
- We can assign WM number to combination of plant & storage type - Storage type
- Storage section & picking area
Storage location Rule - Staging area
 MALA  Shipping point / plant / storage condition for material - Door
 RETA  plant / situation ( SETUA ) / storage condition
 MERE  MALA then RETA ( backup procedure ) traditional scenario Transfer order
- Material number
A transfer order is an instruction to move materials from a source storage bin to a destination bin with in - Quantity to moved
warehouse complex - Source and destination
o Lean warehouse means using a small part of the functions provided by the warehouse storage bin
management component. Creating TO
o In lean WM the picking quantity is initially same as the delivery quantity - Subsequent

o Lean WM does not have inventory management at the level of storage bin and therefore more - Explicitly
suitable for fixed bin warehouse - Automatic direct to
o Lean WM need at least one warehouse number and one storage type - Collective process
 o We can activate lean WM at the WM number level Lean WM not include functions
WM random storage material can be stored in different storage bins or even several storage bins at the - Storage sections
same time
- Reserve storage bins

WMTA output type at header level of the outbound delivery - Strategies for put away and picking

Prerequirements for this is that at least on item of the outbound delivery is relevant for WM - Replenishment
Combination delivery type / shipping point - Inventory at storage bin level
Time 1-3 ( processing later ) automatic transfer order creation
Direct transfer order creation Time 4 ( processing immediately ) Batch number are unique at
We have to define the confirmation requirement for each storage type o Plant level
Batches o Material level
If copied from SO to Delivery we cont change batch in delivery o Client level for material
We can enter batch number in Picking view in delivery Batch mgt indicator in MM03
Batch split o Purchasing screen
o Manually in the batch split screen of the delivery item o Storage1 screen
o Using automatic batch determination ( Control in delivery item category )
o Through manually triggered batch determination in the batch split screen SLED Self life expiration
o In where house management BBD Best before data

Serial Number
Serial no profile in MM03
o We can assign a unique serial number to each material
 Storage 2
o Serial number profile in the material master
o Serial number usually specified in the delivery item
o We can define them in sales order
Packing
VERP Pack material type - DLN
Packing material are materials use for packing or Transport goods
LEIH returnable package - TAL
Selected item from an outbound delivery can be packed in an individual package type is called a handling
unit Condition type ZPVA

Handling unit header contain information about the packing material used in packing AT  RE

Overview screen of the packing material displays the quantity of the delivery items or other handling units RPI

Packing is a process of assigning delivery item to packaging material. This produce handling units which handling unit  Packing type
can then turn packed in additional packaging materials
Packing control
We can also unpack items from handling units as well as entry and delete
- Packing allowed
Deleting item control relevant for packing
- Packing not allowed
Packing function is available Packing Instruction consists
- Packing mandatory
- In orders ( as packing proposals ) - Packing material
Packing output types 2
copied from order to delivery - Material to be packed
- Picking list (at delivery level) PL00
- In the outbound delivery - Text item
- Shipping label ( at HU level)
- In the inbound delivery - Subordinate packing instructions
- In the shipment document - Define of check profile
HU information
- Minimum quantity
- Content
Control in copy control header level if packing not allowed of credit block
- Weight/volume/measurements
Packing in outbound delivery is copied to shipment material grouping for packaging materials
- Status information
HU in shipping  physical combination of materials consist
- History
Packing material (E.g. pallets, cartoons )
Goods ( to be transported ,used, stored )
HU an included in
Each handling unit has a unique identification number - Inventory mgt
HU also nested so that higher level handling unit may certain several identification numbers - Production
Goods receipt process in HU must be exit before you create TO for put away - QM, SD, WM
Goods issue process after TO & picking is created

Goods Issue
∙ Update quantity in inventory
 ∙ Update the value in balance sheet accounts
∙ Sets status for billing due list and update the status for all other relevant sales documents
∙ Updates billing index and updates the status in all other sales documents
∙ Updates document flow
∙ Updates in controlling doc.

Header
Billing
- Identification number of the payer
- Billing date
The billing document is controlled via the billing type.
- Net value of the entire billing document
When a billing document is posted to accounting it generate - Document currency
o Profit centre accounting document - Terms of payment and Inco terms
- Partner numbers, such as the
o Profitability analysis document
identification number of the sold-to party
o Accounting document
- Pricing elements
o update status in all relevant sales, delivery and billing documents
o updates SIS Items
o updates the consumption of credit limit of a customer - Material number
o update the consumption of credit limits of a customer and update the status in all sales - Billing quantity
documents - Net value of the individual items
- Weight and volume
The business area can be equivalent to the: - Pricing elements relevant for the
 Sales area (if the accounts are to be posted according to sales) individual items

 Plant/division (if the accounts are to be posted according to products)

Complete billing  one billing document for one delivery when billing saved
Invoice split  several invoices are created for one delivery customer receivable a/c DR
TO revenue a/c
An order contains terms of payment at header as well as item level. These are stored only at header
level in the billing document, however. If there are different terms of payment in the reference When payment made by customer
documents, an invoice split will always be made.
Cash a/c Dr
To customer receivable a/c
Collective invoice  several deliveries are grouped together in one invoice
o Payer and Bill to parties are the same SDCHECKVOFA
Check the settings within billing types
o Payment terms are the same
o Destination country
Costs and revenue can posted to
Reference number and assignment number  Customer accounts receivable
For these purposes there are two special numbers in the billing document header which can be  General ledger
passed on to the accounting document as follows:  (for example, a cash clearing
account)
 the reference number in the accounting document header  Revenue
 the assignment number in the customer line item  Sales deductions
 Accruals (for rebate
The reference number can contain the number of the customer business transaction. This number agreements)
can be used as search criteria for changing or displaying the document. You can print the reference o Accrual account
number instead of the accounting document number in all business correspondence. o Accrual clearing
The assignment number provides additional information in the customer line item of the accounting account
document. The account line items are sorted and displayed according to the assignment number.
Negative posting Indicator that causes the transaction figures to be reset for a document item. VF04  SDBILLDL
If the indicator is set, then the transaction figure update is changed. A correspondingly set posting Billing date from
on the debit side reduces the credits side of the account. A credit posting reduces the debit side of the Billing type
account. SD document type
Sales organization
Use: The indicator can be entered in billing types for credit memos and cancellations. It only has the
Distribution channel
required effect in FI, if the company code permits negative postings.
 Division
Shipping point
Pro forma Invoice Sold to party
 Goods issue is not required before you create a delivery-related pro forma invoice. Destination country
 You can create as many pro forma invoices as you like for a sales order or a delivery
because the billing status in the sales order or delivery is not updated.
F2 invoice
 Data from the pro forma invoice is not passed on to financial accounting. F8 pro forma invoice
 Quantity/volu pos/neg field is not available for entry in order to avoid the possibility of profom G2 credit memo
L2 debit memo
Cancellation invoice RE return
A cancelled billing document will generate a new document and the postings will have the opposite S1 cancellation invoice
symbols. This cancelled document will update the status and document flow. S2 cancellation credit memo
LR invoice list
o Cancel a billing document , you must create cancellation document. The system copies data
LG credit memo list
from the reference document into cancellation and offsets the entry in accounting IV intercompany billing ( invoice )
o You do not need to make an entry in copying control for cancellation IG intercompany billing ( credit memo )
Create credit and debit memo either with reference to credit or debit requests.
Billing doc Reference document
o Without reference to a previous business transaction Invoice sales doc / delivery
o With reference to an order Credit memo Cr request / Billing
Debit memo Dr request / billing
o With reference to a billing document Return Cr Memo Return document
Credit memo Invoice correction
Invoice correction request
Pro form invoice Sales doc / delivery
o Invoice correction request represents a combination of credit and debit memo requests. Cancel invoice Billing document
o The invoice correction request must be created with reference to the corresponding billing Invoice list Billing document
document ( no reference to order or inquiry ) Bill extern trans External transaction
o When creating an invoice correction request the items are automatically duplicated (second Intercompany Delivery
Rebate cr memo Rebate request
item is created , the resulting item categories must have opposite + / - values
o First all credit memo items are listed, followed by all debit memo items.
o Credit memo items cannot be changed. The corresponding debit memo item can be updated Billing in background
according to new characteristic s ( new pricing, change in quantity. ) o Periodically
o At a specific time
o You can delete the credit and debit memos in pairs ( unchanged pairs of items can be
deleted all at once in this way
Cash sale
o Order related billing
o No output determination, as has already been carried out in the order
o Now new price determination, as the pricing should not differ from the printed invoice
o Posting in financial accounting is made to cash settlement account , not to the customer
o Billing type SV is used for cancellation in cash sales

Data flow Copy control

Header Header level
o Reference document : which documents may be used as reference for billing o Foreign trade data
o Allocation number
o Determination of foreign trade data, allocation numbers, reference numbers and item
o Reference number
numbers assign
o Item number assignment
Item Item level
o Billing quantity: which quantity should be invoiced the order or delivery quantity o Quantity
o Pricing and exchange rate o Pricing

o Should pricing for example be carried out again or should prices from the order be copied
over, and at what exchange rate?
o Updating the quantity and value in the reference document

 System can include bother order– related and delivery–related items in the same
billing document
 Additional split requirements in customizing for copy control header level
 Eg : separation based on material group or profit center VBRK-ZUKRI in header

Invoice list
 Invoice list contain various billing documents ( invoices, credit and debit memos ) and can LR for invoices
be sent to a payer on specified days or certain intervals LG for credit memos
 Maintain Factory discount RL00 as well as condition type MV15
 Each billing type to be included in an invoice list must be assigned an invoice list type
 Define a factory calendar , when specified when invoice list are to be created
  Maintain condition records for RL00 for the payer

 Create output condition records for the condition type LR00 and RD01

Billing plans
o 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 documents at item level
o You can also define a billing plan at header level , which is then valid for all items assigned Periodic Billing
to it.
o Rental contract
o These header billing plans are assigned to sales document types
o Fixed period
Periodic billing
Period billing is often used for rental and service agreements, in order to bill the full amount o Total amount
periodically at certain dates
The contract data stored in the system can then be used as basis for creating billing plan
The start and end dates define the duration of the billing plan.
You can create new date either directly in the billing plan , or using the report RVFPLA01
Mile stone billing
o Plan engineering and
Mile stone billing
construction
 Mile stone billing is often used in plant engineering and construction , in order to spread o Partial amounts
billing of the full amount over several dates within a billing plan
o Finial settlements
 During mile stone billing, the total value to be billed is distributed among the individual dates
according to certain rules
 Billing plan dates can be blocked for billing
 Changes that occur ( for example, top the amounts) after certain milestone billing document
have been created are distributed amount the remaining billing plan dates. The amount
remaining to be retro-billed for the billing documents already created is included in the final
invoice
 System creates an entry in the billing index for each billing date. This means that you will
find an entry in the billing index for this milestone billing at the time of the billing date
specified .In this case, billing is carried out as order–related.
 When you create a billing document , the system updated the status of the billing plan dates
 Dates that have already been billed can no longer be changed in the billing plan

Billing plan with link to milestone billing You can now control whether a billing date is
 fixed date
 Required to b updated with the actual date of the milestone
 Updated with the actual date of the milestone, if production is completed before the planned
billing date

Billing rule (Determine billing value )

Billing rule can be created for each billing plan date. This rule determine how the value to be billed on
a particular date is determined
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 ( when dealing with
rental costs for example) monthly prices can be defined.
The billing plan type is determined from the document item category
 Billing Relevance

Use In Customizing for the item category, you can determine the basis for billing using the indicator Billing relevance.
This allows you to carry out the following controls:
 A: Relevant for delivery-related billing documents
Outbound delivery is the basis for billing. The billing document status is only updated in the outbound delivery.
 B: Relevant for order-related billing documents
The sales document is the basis for billing. The billing status is defined by the required quantity.
In the standard system the item categories REN (returns) and BVN (cash sales) are set up in this way.
 C: Relevant for order-related billing documents
The sales document is the basis for billing. The billing status is defined by the target quantity.
In the standard system the item categories G2N (credit memo) and L2N (debit memo) are set up in this way.
 D: Relevant for pro forma
To create a pro forma invoice, the billing relevance indicator must be blank. In addition, indicator D for cross-company code business
processing should be used as follows: In the case of free-of-charge outbound deliveries, an internal allocation should be made to the
company code for the delivery. The indicator D allows you to make free-of-charge outbound deliveries.
 F: Relevant for order-related billing documents - Status according to the invoice receipt quantity
Relevant for order-related billing on the basis of the invoice receipt quantity (third party business transaction). The system only puts the
order into the billing due list, if in Purchasing the invoice has been received from the vendor and processed. After every invoice receipt,
a customer invoice is created in addition to the quantity given in the incoming invoice. The order applies until the next invoice comes in
from the vendor.
In the standard system, the item category TAS (third party business transaction) is set up in this way.
Alternatively this procedure can refer to the quantity of goods received.
You can control whether the invoice receipt quantity or the quantity of goods received is relevant for billing by carrying out copying
control for billing at item level in the billing quantity field.
G: Relevant for order-related billing of the delivery quantity
The order is relevant for billing, but the cumulated quantity already delivered. This means that you can bill a number of partial
deliveries in one transaction.
H: Relevant for delivery-related billing documents - no zero quantities
You can use this to prevent items with zero amount being included in the billing document.
 I: Relevant for order-related billing documents - billing plan
Billing is carried out using the billing plan and its status. The status of the order item is understood to be the total status of the billing
plan billing statistics.
In the standard system, the item categories WVN (Service), MVN (rent) and TAO (milestone billing) are set up in this way.
 J: Relevant for cross EC country deliveries. The outbound delivery is only relevant for billing if
 1. the switch ‘Plants abroad’ is active in Customizing
2. Country of departure (where plant is located) and destination country (country of ship-to party) are different EU countries.
In the standard system, the item categories KBN (consignment fill-up), KAN (consignment pick-up) and NLN (replenishment delivery)
are set up in this way.
 K: Relevant for delivery-related partial billing documents
You use these indicators if you would like to select items and partial quantities in Billing.

Rebates Pre requisites for rebate process

o The sales orgnisaion
A rebate is a special discount which is paid retroactively to a customer. This discount is based on the
customer's sales volume over a specified time period. o The payer maser
o The billing document type
This general data applies to all condition records that you create within the rebate agreement:
 Validity period
 Status (for example, whether the agreement is released for settlement)
 Rebate recipient (the party who receives the credit memo)
 Currency (default from the sales organization)
Rebate based on
 Method of payment (check, bank transfer, and so on)
 Material
In FI, the rebate accrual is posted to two accounts: a sales deduction account and an accrual account.  Customer
The accrual account is cleared when the rebate agreement is settled with a credit memo.  Customer hierarchy
 Group of materials
Req 24 used only in billing documents
Req 25 used in rebate-relevant billing documents

o Rebate accrual amount is calculated using the rebate basis Agr type condition
o System update the rebate basis and the accrual amount on the rebate agreement sales volume 001 customer/material % Bo01
screen
002 customer/material Q Bo02
When you save the rebate agreement, the system will automatically create a credit memo request. The 003 customer % Bo03
system uses this document to create a credit memo. When the credit memo is released, the accruals are 004 customer hierarc l % Bo04
posted to FI.
005 sales volume ind % Bo06
If you have posted accruals manually, but these have not been passed on to financial accounting, the
manual accruals and manual payments in the rebate agreement are blocked. Rebate accruals posted

You can carry out final settlement of rebate agreements  Sales deduction accounts
o automatically  Accruals accounts
o Manually
o as a background task (in batch programs RV15C001, RV15C002 SDCHECKBONUS
Report to checks for Rebate type
You can carry out settlement directly from within a rebate agreement.
Collectively process rebate settlements as a background task. SDBONT06
Condition Type Groups Update billing documents for payer
In this IMG activity you can define condition type groups that contain condition types and condition tables
for rebate processing and assign them to an agreement type.
Normally a condition type group comprises a rebate condition. However the following options are available
if your rebate processing require them:
 You can assign more than one condition type to a group.

 You can enter the same condition type several times in a group and use different condition tables
or key combinations for individual cases.
This makes it possible to split the rebate settlement up within a rebate agreement. If you are using more
than one condition type within a group, you can post part of the rebate settlement to an account for
marketing costs and part of it to an account for administration costs.

Partial rebate settlement can limited for each rebate agreement type
 o Up to the accumulated accrual amount
Rebates
o Up to the calculated payment amount for the current data
Rebate agreement VBO1
o Unlimited
 SAPMV13A
Accruals are cancelled automatically when a credit memo is created Rebate extend VB(D
 RV15C005
Retroactive rebate agreements
Rebate settlement VB(7
o Retroactive rebate agreement allow you to take into account billing documents created before the
 RV15C001
rebate agreement is created
o The rebate basis for the billing document create previously is accumulated and recorded in the Update billing doc VBOF
rebate agreement  SDBONT06
o The accrual amount is not automatically updated for billing document created previously. Rebate list VB(8
o This amount can be entered manually or can corrected by using report RV15B002  RV15C002
o Rebate relevant billing documents created after the rebate agreements is created update oth the
rebate basis and accrual fields automatically.

Partner Determination Partner type

The account group determines: ∙ Customer CU
∙ Vendor LI
∙ Which screens and fields are necessary for entering master data ∙ Contact person CP
∙ Whether you can or must make an entry in these fields ∙ Human resource
∙ Personal number PE
∙ How master record numbers are assigned (externally by you or internally by the system) and the
number range from which they are assigned Partner objects
∙ Which partner functions are valid o customer master record
∙ Whether the business partner is a one-time customer or one-time vendor o sales document
- header TA
- item N
As accounting data is always needed for processing a business transaction, sales and distribution data
is created for a business partner in a common master record. o delivery
- header LF
From an accounting view there are customers Customers and vendors Creditors.
o Shipment TR
Therefore, customer master data is managed in a customer master record and vendor master data is o billing document
managed in a creditor master record.
- header FK
Partner types let us distinguish between different business partners classified into certain groups. - item FP
Partner Functions represents the roles they play within a business transaction. Assigning Partner functions o sales activity CAS
in SAP system determines the functions of that partner in the sales process.
Sold to, Ship to, Bill to and Payer is all the same Partner type named "CUSTOMER". KNVP - Customer master
Customer account group control the field selections, number assignment, one time customer account and KNVH - Customer hierarchy
output. KNVK - Contract
We can maintain a customer master record for each partner T024P - Credit repetitive
If we enter SH only system determines SP from SH
VD05  SAPMF02D
Sold to party ship to party payers
Customer
Pricing Delivering address Payment terms Sales organization
Inco terms Goods receiving hours Credit limit check Distribution channel
Division
Shipping conditions Tax
All sales areas / selected sales
areas
General Data  Relevant for sales and accounting valid for all organizational units( with in client ). Order block
Delivery block
It is stored centrally(client specific ) in order to avoid data redundancy Billing block
Company code data  Relevant for accounts, valid for respective company code Block sales support
1.overall block
Sales area data  Relevant for SD, valid for specific sales area
2.All free of charge
3.No sales
Availability check

The availability check takes place on the material availability date. This means the material availability date must be determined in the sales order
before the availability check can be carried out. Material availability date determination use delivery scheduling.

Replenishment lead time can be used for availability check

Replenishment lead time is the time for material to become available either from external procurement or in-house production
Forward scheduling
The material availability date is in the past. On the proposed availability date, there is not enough stock.
Fixing Quantities and Dates in Sales Documents

If the availability check for an item determines that the item cannot be delivered fully on the requested delivery date, and, as a result one or more
schedule lines have to be created for later delivery dates, the customer can decide whether to accept these delivery dates and quantities.

You can record the customer's decision either by setting an indicator in the Fixed date and qty field or by leaving this field blank. The field is
displayed both on the schedule line overview screen and on the availability screen.

Customer Accepts the Schedule Line Proposal

If the customer accepts the schedule lines which are proposed by the system, mark the Fixed date and qty field. The system then transfers the
requirements for the schedule lines to material requirements planning.

Blocking Confirmation of Quantities in Sales Documents

In Customizing, using Block transfer of requirements by delivery block, you can specify that certain delivery blocks in the sales document header
also block the confirmation of order quantities.

If you enter such a delivery block in a sales order header, the system confirms the available quantity to show you the delivery options. If you save the
document, however, the confirmed quantities are not saved. Your company could block confirmation for a customer if this customer's credit
worthiness was questionable. The sales order in this case is not only classed as unconfirmed, it is also blocked for delivery.

Thus, no stock is reserved. The stock is still available for other customers. Although the order quantities are not confirmed, the system still transfers
the requirements to material requirements planning. It is assumed that the delivery block will be removed at some point. The automatic transfer of
requirements means that the order quantity can be confirmed at a later point in time.

Pricing Conditions can be grouped into

the following groups
∙ Prices
Price determination process makes use of the 5 step condition technique
∙ Discounts & Surcharges
∙ Taxes
Data about conditions is stored in condition records
Condition records are created using a specific key. These keys are set up in the condition tables. ∙ Freight

The new condition maintenance allow maintenance across all condition types and tables Kind of Prices
∙ Material price
Condition records must already exist in the system for each of the condition types that you want the system
to apply automatically ∙ Price list type
∙ Customer-specific price
Price list types
Table
Additional condition tables can be created for specific requirements. by customer groups
(wholesale, retail, and so on)
They are used to determine the key in the condition records by currency
You can add fields to the field catalog in order to create new condition records based on different criteria (price lists for each foreign country )
It is important to list the fields in a condition table in the proper order
Pre request ions of automatic pricing
Material
Access sequence ∙ Tax classification
This search strategy defines the sequence in which condition records for a condition type are found and
∙ Price material
read
a search strategy. ∙ Material group

made up one or more condition tables. ∙ Cash discount

Each access performed during the access sequence is made using a condition table
Customer
Assigned to a condition type
∙ Customer pricing
An access sequence must be set up from most specific to least specific
procedure
Which pricing element is used to control pricing so that you can specify a customer specific price rather
∙ Price list
then a general material price to be used during automatic price determination in a sales document
∙ Price group

Condition type ∙ Tax classification

Condition type determines the category of a condition and describes how it is used. The condition type
contain all the rules and controls
A condition type that must be captured manually, will not have an access sequence assigned to it.
Header conditions can be entered manually at header level and is valid for all items
The basis of the distribution of a condition that was entered at header level, can be changed in the pricing
procedure by selecting the appropriate routine. You can mark a condition type in
the pricing procedure as being
User Specific area menus can be created for price maintenance in the new condition maintenance function
- A mandatory condition
- A manually entered condition
Pricing procedure - For statistical purposes only
The primary job of a pricing procedure is to define a group of condition types in a particular sequence
The pricing procedure also determines: Pricing reports - 3 sections
∙ Which sub-totals appear during pricing
∙ Page Header
∙ To what extent pricing can be processed manually ∙ Group Header
∙ Items
∙ Which method the system uses to calculate percentage discounts and surcharges

∙ Which requirements for a particular condition type must be fulfilled before the system takes the
V/LA  SAPMV14A
condition into account
In pricing, what object stores the condition type and the sequence in which they are executed in the Sales
document during pricing
The Pricing procedure can have any number of subtotals (to be use for base calculations)
The Pricing procedure contains all the condition types necessary for the calculation of the price
In the pricing procedure you can mark the Condition Type as mandatory and if they can be entered
manually
Prices can be changed in the condition procedure of a sales document and these changes will be marked
as “changed manually”

Header conditions
Automatic pricing does not take header conditions into account.
You can not create condition records for them in the standard system.
Header conditions are entered manually in order processing

 Freight condition type KF00 applies to each item in a sales document. During automatic pricing, Both at header and item level
the system searches for valid condition records that apply to this freight condition.
 Freight condition type HD00 can only be applied to an entire document. You enter this freight ∙ Percent from gross RA01
manually during sales order processing. ∙ Absolute discount RB00
∙ Weight discount RD00
Information in the Pricing Analysis
The analysis screen is divided into three.
In the left-hand side of the screen, an overview tree shows the four levels of pricing. These are:
Header conditions
∙ the pricing procedure
∙ Percent discount HA00
∙ condition types
∙ Absolute discount HB00
∙ accesses
∙ Freight HD00
∙ any condition records found
∙ Order value HM00
In the upper right-hand side of the screen you receive more detailed information for the level of the
overview tree that you have selected.
Item conditions
 At condition type level you receive information on the number of accesses and why accesses ∙ Material discount K004
have not been implemented. If a requirement for a condition type in the pricing procedure has not ∙ Customer/Material K005
been met, you have the option to display routines by selecting Information.
∙ Customer discount K007
 At the access level you receive information on which fields work with an access. By selecting the ∙ Material price PR01
technical view you can see the field names for an access.
 At condition record level you can branch into the relevant condition record.
In the lower right-hand side of the screen you receive additional documentation for the access and Statistical conditions
condition levels. You can use this if the information in the detail screen is not enough.
VPRS SKTV Cash discount (before tax)
The condition type VPRS goes into the valuation segment in the material master and determines from this SKTO Cash discount (after tax)
the standard price or average price. PI01 Inter company
∙ The condition type VPRS is labeled as a statistical condition in the pricing procedure. RL00 Factoring discount
MW15 Factorial discount tax
∙ Using the condition category G, the condition type VPRS goes into the valuation segment of
GRWR Statistical value
the material master and determines from here the standard or average price.
VPRS Cost
 ∙ The condition category S always accesses the standard price whereas condition category EK02 Calculated costs
T always accesses the average price. EDI1 Cus t.expected price
∙ The profit margin is determined using the calculation formula 11 assigned in the pricing EDI2 Cust.expected value
procedure. In this calculation formula the cost price is subtracted from the subtotal of net
value 2.
Net price list
Net Price list provides the option to create price information for a customer on a selected number of
materials. The price list report will determine the prices by simulating a Billing document
After starting program SDNETPRO a billing document is simulated and the system issues the result.
HB00 Header discount distributed as percentage because it is marked as a header condition and as a
group condition
RB00 Assigns the header discount to every item, because it is only marked as a header condition

The Condition Exclusion Procedure

First of all, you create exclusion groups. An exclusion group is a list of condition types that is identified by a three-digit number. Exclusion groups are
defined in Customizing for Sales. You also assign exclusion groups to a pricing procedure and to determine how the condition exclusion is to be
carried out.
You then assign the exclusion groups to a pricing procedure, thus defining the condition exclusion.
Depending on how you configure exclusion groups in the pricing procedure, the system can use condition exclusion to select the best price or
discount in six different ways:
 Selecting the best condition record of a particular condition type from within one exclusion group

 Selecting the most unsuitable condition from within one exclusion group

 Selecting the best condition record for a condition type

 Selecting the most unsuitable condition record for a condition type

 Selecting the best conditions from different exclusion groups

 Excluding all condition types in the second exclusion group if a particular condition type in the first exclusion group exists in the document
Determining Best Price From Condition Types
During automatic pricing for a sales order item, the system may find a number of valid condition records that apply to the same item. If the competing
condition records belong to a variety of condition types, the system selects the record with the best price and excludes the other condition records.
Condition records that the system ignores are not deleted from the sales order but are simply deactivated. You can still see the excluded condition
records on the pricing screen in the sales order.

In condition exclusion in the standard system, a condition record with a zero value is not taken into consideration. It is treated as though it
doesn’t exist.
If you want to take a zero value into consideration, enter the standard calculation formula 038 in the pricing procedure for one of the conditions to
be compared.
The following is an example of a situation where a zero value should be taken into consideration:
A company has two condition types in the pricing procedure for surcharges. A condition exclusion group with these two condition types has been
defined and shows that the lower of the two should be applied. In some cases the surcharge could be zero. The reason for this may be a condition
record found or a manual entry. In order that the system takes zero into consideration as the lowest surcharge for the customer, the formula ‘38’
must be assigned to one of the condition types in the pricing procedure.

Determining Best Price Within One Condition Type

If the access sequence for a particular condition type does not specify exclusive accesses, it is possible for the competing condition records to exist
within the same condition type. For example, the system may find two valid condition records for a material discount (K004) - one a material
discount, the other a customer-specific material discount. The system determines the record with the most favorable discount for the customer.

If the Exclusive access indicator is set, the system looks no further after it finds the first valid condition record. In this case, the
system cannot determine a best price.
Determining Best Price from Different Exclusion Groups
This method allows the system to check between exclusion groups for the most favorable price or discount. In this case, the system totals the
condition values for each group, compares them, then selects the most advantageous group for the customer.
Excluding the Conditions in an Exclusion Group
In the fourth alternative when the system selects one particular condition type that exists in the first exclusion group, it excludes all the conditions in
the second exclusion group from pricing.
After you have defined the exclusion groups you want to use, you can enter them in the pricing procedure. The following example shows how
exclusion groups can be used in the pricing procedure. In this case, the exclusion procedure selected is the best condition type within one exclusion
group.

Pricing Copy
A: Copy pricing elements and update according to scale
 Copies the pricing elements from the sales document (that is, it does not determine any new condition types).
The system then uses these pricing elements to determine the valid prices, surcharges, and discounts based on the quantity to be
invoiced.
 Redetermines the scale prices for changed delivery quantities
If the delivery quantity differs from the order quantity, the system determines the price, surcharges and discounts on the basis of the
delivery quantity based on the scales that are valid at the time of order entry.
Invoice A. When an order was entered, the system used the January price list to determine a price of $9.00 per piece based on the rate for 20
pieces. At billing, the system uses the same price list, but uses the rate for 10 pieces (delivery quantity) to determine a price of $9.50 per piece.

B: Carry out new pricing

 redetermines pricing. The system determines valid pricing elements at the time of billing and uses those elements to determine the prices,
surcharges and discounts.
For instance, the customer may be entitled to a special price after the sales order has been created. The system would then determine the
relevant pricing element for this instance and find the valid price.
If the delivery quantity differs from the order quantity, the system determines the price, surcharges and discounts on the basis of the
delivery quantity, according to the scales valid at the time of billing.
 redetermines the taxes.
Invoice B. At the time of billing, there is a new price list and a new discount for March. The system uses this price list with the rate for 10
pieces to determine a material price of $10.50 per piece. It also determines a 2% discount. The system does not copy the manual
Surcharge or discount into the billing document since it is carrying out new pricing. The surcharge or discount entered manually in the
order is not copied to the billing document, since pricing is carried out again.

C: Copy manual pricing elements and redetermine the others :

 re determines pricing (as above)
 Copies manually entered pricing elements from the sales order
 Re determines the taxes
In the standard system, this pricing type is determined for items in an invoice using billing type F1.
 Invoice C. As in invoice B, the system determines the new scale price of $10.50 per piece and copies the manually entered
discount from the sales order into the invoice. Note: Customer loses quantity-based discount.

D: Copy pricing elements unchanged

 Copies the pricing elements and any automatically determined or manually entered surcharges and discounts from the sales order without
changing them
 Does not redetermine the tax
In the standard version of R/3, this pricing type is defined for items in credit and debit memos (billing document types G2 and L2).

Invoice D. This time the system does not use the delivery quantity as basis for pricing. It merely copies the price of $9.00 per
piece from the sales order. It also copies the manually entered discount. Note: Customer keeps quantity based discount.

E: Copy pricing elements and values unchanged

 Copies the pricing elements and values unchanged with automatically determined or manually entered surcharges and discounts from the
reference document
 Does not redetermine the tax

In invoice E, 20 units are invoiced, even if only 10 units are delivered.

In the standard system, this pricing type is determined for items in a cancellation.
F: Only used within the program
This pricing type is used within the program during processing of group conditions.

G: Copy pricing elements unchanged and redetermine taxes

 redefines the following condition types:
– Taxes (condition class D)
– Rebate (condition class C)
– Inter company billing conditions (condition category I)
– Invoice list conditions (condition category R)
– Condition types with condition category L
– Cost conditions (condition category G)
– Cash discount conditions (condition category E)
 All other condition types are treated as in pricing type D.
In the standard version of the SAP R/3 system, this pricing type is defined for invoices of billing type F2 as well as for pro forma invoices F5 and F8 .
H: Copy pricing elements and re determine freight
 redefines the following condition types:
– Freight conditions (condition category B, F)
– Condition types with condition category L
All other condition types are treated as in pricing type A.
 Shipment shipment types:
∙ Individual shipment
Transportation planning point consists of a group of employees responsible for organizing transportation
activities. ∙ Collective shipment
Each shipment is assigned to a specific transportation planning point for transportation planning and ∙ Transportation chain
shipment completion.
It is not necessary to assign the transportation planning point to a company code for transportation planning
purposes. However, company code assignment is necessary for shipment costing and settlement. An individual shipment includes
∙ One or more deliveries
You can use shipment documents to:
∙ One point of departure
Combine deliveries into one inbound or outbound shipment
∙ One destination
Specify shipment stages
∙ One mode of transport
Legs
border crossing points
A collective (or milk-run) includes
load transfer points
∙ One or more deliveries
Assign goods to handling units
∙ Several points of departure
Assign service agents
∙ Several destinations
Specify planned transportation deadlines
Record actual transportation deadlines ∙ One mode of transport

Specify output required for transportation (such as shipping papers or EDI messages)
Information in shipment document
Shipment can contain one or more delivery
∙ Means of transport
A shipment is normally created before goods issue and the deliveries is linked to a shipment before goods ∙ service agents
issue
Packing in shipment is carried out for a number of deliveries ∙ Deadlines
A shipment document control external delivery activities and a transfer order control internal material ∙ Status
movements
∙ Tendering status
Shipment outputs include: ALTR general shipment, bill of lading, shipping order, EDI in general (SEDI), ∙ Route
shipment notification, goods receipt/issue slip. ∙ Texts
Delivery outputs include: delivery note, mail (internal output), shipping notification, warehouse order, and ∙ Output
package labels. ∙ Dangerous goods

A traffic light icon indicates the overall status of the shipment document
 ∙ No traffic light: No planning activities have been performed
∙ Red light: Transportation planning is complete
∙ Yellow light: Loading at the plant has either started or is complete
∙ Green light: Shipment has been processed and is en route or has arrived

Shipment cost
Forwarding agents or railroads use freight codes (and sets of freight codes) to classify the goods they
transport.
A freight class is a group of freight codes used to calculate shipment costs. Functions
Create the accounting document for
Automatic freight code determination uses the following criteria: the shipping of goods.
 Country of origin Calculate the shipment costs.
 Shipping type (truck, rail, etc.)
 Forwarding agent (forwarding agent freight group in the vendor master) Settle the costs with the service
agent.

To carry out shipment costing for a shipment document, the following requirements must be met: Transfer the costs to FI and CO.
 The shipment must be marked as relevant for shipment costing.
 The shipment must have the required total status as set in the definition of the shipment cost
type.
 The shipment must have a transportation status of at least planned.
 The shipment must have a service agent.
 Customizing for shipment cost pricing must be set.

The system determines a pricing procedure for the shipment cost item (for example, a shipment stage)
using transportation planning point, service agent, shipment cost item category and shipping type as criteria

Logistic information system PURCHIS purchasing IS

INVCO Inventory IS
Aggregates and stores this data in the data ware house. The data can be aggregated with regard to quality TIS Transportation IS
and quantity. SFIS shop floor IS
LIS through out the entire logistic area in the system QMIS quality management IS
PMIS plant management IS
Sales Information system
SIS contains
The purpose of the SIS system is to compress data effectively. This will ensure that you can manage results o Standard analysis
effectively and quickly
o Flexible analysis

The Sales & Operations Planning (SOP) application is based on information structures Characteristics
An information structure is a statistics file containing operational data. Sales Organization
Customer
Material
Information structure used for data evaluation, projection, and analysis in all the logistics information
key figures
"Statistics group" indicator appears in the material master record and customer master record and allows Incoming orders Value
you to influence the statistics update with reference to your master data. Sales Volume

Sales Information System reports are info structures. Which of the following make up info structures Info structures
1: Characteristics Specify to collect data on a certain subject ( sales org, sales office, customer, material) ∙ S001 "Customer"
2: Key figures can be defined as the performance measurements: Quantity and Value. ∙ S002 "Sales office"
3: period unit ∙ S003 "Sales organization"
∙ S004 "Material"
Characteristics : A characteristic can be defined as which data is to be analyzed ∙ S005 "Shipping point"
E.g. material or customer. The characteristics form the header of an info structure. ∙ S006 "Sales employee "
∙ S009 “ sales support”
Update group  Sales area + Cust stat grp + Mat st grp + status group sale doc (OVRO)
∙ S066 “ credit management”
Update group  Sales area + Cust stat grp + Mat st grp + status group sale doc + status group sale item
(OVRP) ∙ S060 “ rebate processing”
∙
Update group: For customizing S501 to S599
01: Sales document, Delivery, Billing document
 02: Returns, Return delivery, Credit memo
MC18  Field catalog
Examples of SD data that updates info structures include: orders, returns, deliveries, and credit memos MC21  info structure
Currency amounts are always updated in the statistics currency which is assigned to the sales organization  Updating group
MC24  update rule
Early Warning System
o Exceptions can be used to help detect and rectify potential problems at an early stage. Maintain statistic groups for
o Customer
o The Early Warning System is based on the key figures of the Logistics Information System (LIS)
o Material
o Sales documents
Business warehouse
Assign Statistic groups for
o Business warehouse contains a staging engine and a databases
o Business warehouse store not only master data and transaction data but also meta data o Sales document type
o SD item type
o Info cubes, info objects and Queries are part of the business content of business warehouse
o Delivery type
o Delivery item type
Online lists provide data for documents and let you change and display documents. Determine the billing type relevant to
statistics
Work lists display activities that need to be processed
work lists in
sales
delivery due list
Picking
Billing due list

Online or standard lists

List of orders
List of quotations
List of incomplete items

Billing types
BillT Description DocCa CaBlT ILTyp ActDPr Out.pr Out. DoPr Stat Rel.rebate
B1 Rebate Credit Memo O S2 KOFI00 V10000 RD00 X X
B2 Rebate Correction O S2 KOFI00 V10000 RD00 X X
B3 Rebate Part Settlmnt O S2 KOFI00 V10000 RD00 X X
B4 Rebate Manual Accrls O S2 KOFI00 V10000 RD00 X X
BV Cash Sale M SV LR KOFI00 V10000 A X
F1 Invoice (F1) M S1 LR KOFI00 V10000 RD00 A X X
F2 Invoice (F2) M S1 LR KOFI00 V10000 RD00 X X
F2B Nota fiscal M S1 LR KOFI00 V10000 RD00 X X
F5 Pro Forma for Order U V10000 RD00
F8 Pro Forma Inv f Dlv U V10000 RD00
F9 Invoice (ALE) M S1 LR KOFI00 V10000 RD00 X X
Canc.down pymnt
FAS req. N LR KOFI00 V10000 RD00
Down payment
FAZ request M FAS LR KOFI00 V10000 RD00 A
FS Invoice Service/Rent M S1 LR KOFI00 V10000 RD00 V X X
FV Invoice Contract M S1 LR KOFI00 V10000 RD00 X X
G2 Credit Memo O S2 LG KOFI00 V10000 RD00 X X
IG Internal Credit Memo 6 KOFI00 V10000 RD00 X
IV Intercompany billing 5 IG LR KOFI00 V40000 RD04 I X
JEX Excise invoice India U V10000
L2 Debit Memo P S1 LR KOFI00 V10000 RD00 X X
LG Credit memo list 4 KOFI00 V30000 LR00 X
LR Invoice list 3 LRS KOFI00 V30000 LR00 X
LRS Cancel invoice list 4 KOFI00 V30000 LR00 X
RE Credit for Returns O S2 LG KOFI00 V10000 RD00 X X
REB Ret. credit memo BR O S2 LG KOFI00 V10000 RD00 X X
S1 Invoice Cancellation N LR KOFI00 V10000 RD00 X X
S2 Cancel Credit Memo S LG KOFI00 V10000 RD00 X X
S3 Cancel Training Adm N LR KOFI00 X X
SHR Cancel Cash Sale N LR KOFI00 V10000 RD00 X
SV Plants Abroad N KOFI00 V10000 X
WIA Invoice M S1 LR KOFI00 V10000 RD00 B X X

Item categories
ItCa Description BilRl Prcg. StructScpe Cost ComRl BD SchAl RelWgtVol InProc Ret
AFN Inquiry Item X X A X X X
AFNN Free of Charge Item X A X X X
AFTX Text Item A X
AGC VariantConfiguration X D X B X X X 20
AGN Standard Item X X B X X X 20
AGNN Free of Charge Item X B X X X 24
Reb.Credit Memo
B1E Req. C X X
B1N Rebate Cr Mem Req C X X 29
BI2 Indir.Returns Rebate B X X X X 20 X
BVN Cash Sales Item B X X X X X 20
Cash
BVNN Sales:FreeofCh. B X X X X 24
C2RP Ret.full Pr.EW A X X X X X 20 X
G2N Request C X X X X 21 X
KAN Consignment Pick-up X X X 33 X
KBN Consignment Fill-up X X X 33
KEN Consignment Issue A X X X X X 20
KLN Free of Charge Item X X X X 24
KMN Qty Contract Item X X C X X 23
KRN Consignment Returns B X X X X 20 X
L2N Request C X X X X 21
LAN Ret.Packaging Pickup X X X 33 X
LFN Request billing plan I X X X X 21
Sched.Agreement
LPN Item A X X X X X 22
MAK Dlv.-Pos. correction X X 20
MVN Lease Item I X X C X X 35
NLC InterCo stock tr.itm D X X
NLN StandStockTransItem D X X X X 20
PVN Item Proposal
REN Standard Item B X X X X 20 X
TAB Indiv.Purchase Order A X X X X X 28
TAC VariantConfiguration A X D X X X 20
TAD Service B X X X 28
TAE Explanation X
TAK Make-to-order Prod. A X X X X X 20
TAL Ret.Packag.Shipment X X X 33
TAM Assembly Item A D X X X X 20
TAN Standard Item A X X X X X 20
TANN Free of Charge Item A B X X X X 24
TAO Milestone billing I X X X X X 20
TAP Extent delivered A A X 26
TAPS Standard Item (PS) X 24
TAQ Extent delivered A X A X X X X 20
TAS Third Party Item F X X X X X 28
TASG 3rd pty credit memo F X X X X 28
TATX Text Item A
TAW Value Item A X X X 28
WAN Release Item ValCont X X X X X
WKM Config.at Comp.Level I X D E X
WKN Value Contract Item X E X
WVN Maint.Contract Item I X X C X X 35

Schedule line categories

SLCa Description MvT MvT AvC Rq Del.sched. InProc I A
AT Inquiry sched.line
BN No MRP 30
BP Deterministic MRP X X 30
BT No inventory mgmt
BV Consumption MRP 30
C0 ConsgtIssue/w/o AvCh 633 30
C1 ConsgtIssue/w. AvCh. 633 X X 30
C2 Repost retPck/w/o AC 623 30
C3 Repost retPck/w. AC 623 X X 30
CB Indiv.Purchase Order 601 X 31 0 E
CD Without delivery
CN No MRP 601 30
CP Deterministic MRP 601 X X 30
CS Leg 31 5 1
CT No inv.mgmt/no GdsIs
CV Consumption MRP 601 X X 30
CX No inventory mgmt 30
D0 Consignment Returns 634 30
DN Returns 651 30
E0 StoTranToCons.w/o AC 631 30
E1 StoTranToCons. w. AC 631 X X 30
E2 StoTranRetPck.w/o AC 621 30
E3 StoTranRetPck. w. AC 621 X X 30
E4 StoTranToCons. ExtAg 631 X 30
E5 MRP external agent X 30
EP Cust. requirements X
F0 ConsPickup w/o AvCh 632 30
F1 ConsPickup w. AvCh 632 X X 30
F2 RetPckPickup w/o AC 622 30
F3 RetPckPickup w. AvCh 622 X X 30
IA Repair Delivery 601 X X E
IR Return for Repairs 653
K0 TF consgmt lending 635
K1 TR consgmt ret. del. 636
L1 Deterministic MRP 601 X 30
L2 Deterministic MRP X 30
LB Dlv.to stock of mat. 541 30
LN No MRP 603 30
LP Delivery frm project 30
LR Return del.to vendor 122 30
NC Intercompany replen. 643 645
NN Replenishmnt w/o MRP 641 647
NR Replen. returns 671
NS Backlog CrossC Ret 673 675
RN Returns w/o planning 161

Pricing condition types

CTyp Name AcSq CalTy CdCat CCl ScBas Man. GrC CdUpd Head Item +/- C Del DeleteDB
Minimum
AMIW SalesOrdrVal K020 B A D X X
Minimum
AMIZ ValueSurchrg K020 B A C X X
Down
AZWR Pay./Settlement B e A X
BO01 Group Rebate BO01 A C B X X A
BO02 Material Rebate BO02 C C C X X A
BO03 Customer Rebate BO03 A C B X X A
BO04 Hierarchy Rebate BO04 A C B X X A
BO05 Hierarchy rebate/mat BO05 A C B X X A
Sales Indpndt
BO06 Rebate BO03 B C B X X A
DIFF Rounding Off B L A D X X
DUPL Cond.to be duplic. A A C X X
EDI1 Cust.expected price C J B X X X
EDI2 Cust.expected value B J B X X X
EK01 Costs C Q B X
EK02 Calculated costs C Q B X
EK03 Calculated ship.cost C Q B X
Cust.
FK00 shipment(IDES) B A
GRWR Statistical Value K033 A L B C X
HA00 Percentage Discount A A X X X
HB00 Discount (Value) B A X X X X
HD00 Freight D F A X X
HI01 Hierarchy HI01 A A B C X X X
HI02 Hierarchy/Material HI02 C A C C X X X
HM00 Order Value B B X X X
K004 Material K004 C A C X X X
K005 Customer/Material K005 C A C C X X X
K007 Customer Discount K007 A A B X X X
K020 Price Group K020 A A B X X X X
K029 Mat.Pricing Group K029 D A D X X X
K030 Customer/Mat.Pr.Grp K030 A A B X X X
K031 Price Grp/Mat.Pr.Grp K031 A A B X X X
K032 Price Group/Material K032 C A C X X X
K148 Product Hierarchy PRHI A A B X X B
KA00 Sales Promotion K005 A A B C X X X A X
KA02 Promo Discount % 1 A001 A A C C X X X X
KA03 Promo Discount % 2 A001 A A C C X X X X
Promo Discount MD
KA04 1 A001 C A C C X X X X
Promo Discount MD
KA05 2 A001 C A C C X X X X
KP00 Pallet Discount K007 C A C X X X
KP01 Incomp.Pallet Surch. K007 C A C X X
KP02 Mixed Pallet Disc. K007 B A C X X X A X
KP03 Mixed Pallet Surch. K007 B A C X X B X
KUMU Cumulation condition G A D X X
KV00 Sales Costs (ISR) VKWG A A C X X
KW00 Group price C b B D X
MS15 Tax 15% MSM1 H D D D X X
MW15 Fact.Discount Tax MWM1 A D D D X X
MWST Output Tax MWST A D D D X X
PBU Price book - determ. PBU G H D X
PBUD Price book - Basis PBUD A B X
PBUP Price book - GrossPr C B D X
PI01 Intercompany Price PI01 C I B C C X A A
PI02 Intercompany % PI02 A I B C X A
PMIN Minimum Price K004 C A C C X A
PN00 Net Price C B X X
PN10 Sales Price B H B X
PNET Net value G L A D X
PNTP Net price C L B D X
R100 100% discount A A D X X
RA00 % Discount from Net A A X X X
RA01 % Disc.from Gross A A B X X X
RB00 Discount (Value) B A X X X X
RC00 Quantity Discount C A X X X
RD00 Weight Discount D A X X X
RF00 Discount Formula
RH00 Percent in Hundreds H A X X X
RL00 Factoring Discount RL00 A R A D X X
SKTO Cash Discount A E A D X X
SKTV Cash Discount A E A D X X
UTXJ Tax Jurisdict.Code UTX1 A 1 D D X
VA00 Variants VA00 C O A C C X X
VA01 Variants % ZA00 A O A C C X X
VPRS Cost C G B D X

Incomplete procedure
Group Description InProc Group Description InProc Group Description

A Sales - Header 10 A Inquiry/Quotation 30 C Deliv-Rel.Sched.Line

B Sales - Item 11 A Sales Order 31 C Sched.Line w/PurReq.
 Sales - Sched.
C Line 12 A Outline Agreement
D Partner 13 A Order w/o charge
F Sales Activity 14 A Credit memo 6 D Contact persons
G Delivery header 15 A Debit Memo 7 D Customer
H Delivery item 16 A Product proposal 8 D Vendor
17 A Rebate Credit Memo 9 D Personnel Number
18 A Contract
1 F Direct Mailing
20 B Standard Item 2 F Sales activity
21 B Credit/Deb.Memo Item 3 F Dir.Mailing Campaign
22 B Sched.Agreement Item
23 B Qty Contract Item GT G GTS Incompletion
24 B Free of Charge Item K0 G Maximum delivery
25 B Service Item K1 G Minimum delivery
26 B Free of charge serv. K2 G Inbound Delivery 1
27 B Inquiry Item Text K3 G Inbound Delivery 2
28 B Value Item
29 B Rebate Credit Memo
32 B Requirements
33 B Consignment/RetPack.
34 B SchedAgrItm w.DlvScd
35 B Contract Item
36 B SchedAgr w.ExtAgent
38 B Product Selection
Description Output Output assigned PF Med- Program Form Access sequence
type procedur ium

Shipment ALTR V70001 Shipment FA 1 Print RV56TD00 shipment TPP +shipment type
type
Packing 0001 V00001 Packing SH 1 Print SDPACKDR SDPACKETIK Ship to party / packing
material material
Packing KEP6 V00001 Packing SH 1 Print RXSILABELPRINT Ship to party / packing
material material
Inquiry AF00 V05000 IN SP RVADOR01 RVORDER01 SO / DC / DIV /
customer
Quotation AN00 V06000 QT SP RVADOR01 RVORDER01

Order BA00 V10000 OR SP RVADOR01 RVORDER01

Contract KO00 V08000 QC SP RVADOR01 RVORDER01

Scheduling LP00 V07000 DS SP RVADOR01 RVORDER01

agreements
Credit KRML KB 7 S. RVADOR01 RVORDER01 CCA / C RG / Risk
Processing KM Mail category
Cash Sales RD03 V10001 CS RVADOR01 RVORDER01
Invoice
Internal Message MAIL MA
Invoice RD00 V10000 BP RLB_INVOICE RVINVOICE01 SO / Billing type
Single RD01 BP RVADIN01 RVINVOICE01 SO / Billing type
Invoice List
Invoice List LR00 V30000 BP RVADIL01 SD_INVOICE_LIST SO / Billing type

Condit Procedure Access

Description Assigned to
type sequence / Fields
Free goods NA00 NA001 Sales area + Doc pro + cust NA00
proce Customer /
Material
Material A001 A00001 Sales document type A001
determination Material entered
MATWA
Material listing A001 A00001 Sales document type A001
Material exclustio B001 B00001 Sales document type B001
KNVV text object 01 cust Customer account group
KONP pricig con Price,disc,freight Condition type

Credit management
Overview F.31  RFDKLI40
Missing data F.33  RFDKLI10
Brief over view F.33  SAPLKKBL
Update billing doc VBOF SDBONT06
Rebate list VB(8  RV15C002

Inco terms OVSG  SAPL080H

Terms of payment OBB8  SAPL0F30
 SOA - Service oriented architecture
Composite applications - act as a blueprint for complete services enabled ESA - Sap enhanced concept
SOA Business process platform business solutions
Existing system landscape

ESA : Improvement and reusability of the IT Infrastructure to generate value to the customer. ESA Environment – Design tools

ESA Environment – Design tools 1. Solution composer

2. Visual composer
1 Solution composer: 3. SAP NET weaver develop studio
4. ARIS Business architect
Is off line PC tool provided by SAP to help visualize, plan and implement integrated IT solution with
in a company
ERP products
It helps to integrate people, data and business process both with in enterprises and between organization
SAP R/3 from SAP
Uses: Create and change SAP solution maps My SAP from SAP
Create and change SAP Business scenarios maps
Oracle E-business suite from oracle
2. Visual composer People soft from oracle
Generates codes and acts as debugger, tester and document creator JD Edward enterprise from oracle
Minimize time and effort to create content
Lead to quicker go-live decision
Reduce total cost of ownership (TCO)

3. SAP Net weaver Develop studio

Its supports a variety of web-centric programming models including J2EE, web dynpro, web services
portal content
Most supply chain management process start and end with the customer
A typical value generation process in an organizational starts with sales personnel making the sale of
product.

SAP ERP sales

SAP ERP sales
o Sales order management
o After market sales and
Product development and manufacturing with SAPERP services
o Professional services
Entire life cycle of product related such as product structure, routes delivery
Production planning Material requirement planning, to create unconstrained production plans in
production order or planned order Product Dev & Manufacturing
Manufacturing execution Process of capturing actual production information from the shop floor to o Production planning
support production control and costing process o Manufacturing execution
Product Development Process of define a product, gathering requirements developing the product, o Product development
sourcing for suppliers involved and managing the ramp up

Procurement and logistics execution Procurement & LogisticsExecution

o Procurement
Procurement Requesting, purchase order management and invoice verification o Inventory management
Inventory management Recording and tracking of materials on quantity and value basis o Transport management
Planning, entry and documentation of stock movements such as good receipts,
goods issues, physical stock transfers
Transport Management Financials
Financial accounting
SAP ERP Financials Management accountancy
Financial Accounting Central tracking of all financial accounting data International framework of Financial supply chain management
multiple companies, languages, currencies And chart of accounts
Management Accountancy Enables availability of finance data for all cost and revenue related reporting Sarbanes Oxley Act ( SOX or SOA )
as desired by the management IAS  International Accounting
Financial supply chain management Standards
Perform credit management, cash management, Invoicing, collections, cash and liquidity management
US GAAP  General accepted
accounting principle
SAP ERP Human capital management(HCM)
Human capital Management
Work process management Employee transaction, management capability, administration, payroll, time Work process management
management and legal reports Work force deployment
Work force deployment Deploy the right people with right skills to the right positions at right time, Talent management

project resource planning, call centre Planning

Talent Management
ERP Corporate services
1.Real Estate Management
2.Enterprise asset management
3.Project & portfolio management Enables portfolio managers to better identify, select, prioritize and
4.Travel Management
Training, development, retention
Talent management capability enables human resources to manage the
entire life cycle of an employee in the organization
ERP corporate services
Optimize of assets with lease amount of costs and best possible asset Real Estate management
performance for those operating a plant Enterprise asset management
Project & portfolio management
manage a portfolio of projects. Travel management
Key performance metrics on budgets, schedules and staffing. Environment ,Health & safety mgt
Travel planning and online booking, travel expense reporting accounting, Quality management

settlement and travel policy Management Global trade services

5.Enviornment,health and safety compliance management

6.Quality management
7.Global trade services
SAP ERP Analytics
Support an organization throughout the life style and along the supply chain
Assuring and managing the quality of products and assets
Extensive support for world wide export/Import trades as well deliveries within
specific trade areas such as EU & NAFTA

Provides extensive reporting, analytics and forecasting tools enable organizations to make influenced SAP ERP Analytics
business decisions o Financial analytics
o Operational analytics
1.Financial analytics o Workforce analytics
Provide tools define financial targets and develop business plan, monitor cost and revenues
o Strategic enterprise mgt
Using FA organizations can perform financial planning, budgeting forecasting, sales, cost, profitability
planning, product cost services cost management, overhead cost management

2.Operational analytics
Detail operation reports through a typical value generation operating plans such as sales planning,
maintenance cost
Planning and also analyze and monitor all aspects of supply chain such as procurement I & W
management order fulfillment customer service and program & profit management

3.Workforce analytics
Enable data analyis on workforce performance
Headcount and personal cost planning and perform reporting and analytics as necessary and bench
mark salaries and cost against industry standards

4.Strategic enterprise management

Robust software solution that provide full suit of application to enable organizations to implement and
manage strategic successfully

ABAP  Advanced Business Application Programming

ABAP is fourth general language
Kernel is writing using C language
SAP NETWEAR
At the heart of SAPERP is SAPNETWEAR technology or the application platform on which SAPERP NETWEAR integrates
Based and by virtue of its technology, plays important role in integrating applications, process, information Process
and people with the support of self services Information
SAP Net weaver is not a concept but a technology people

ESA  Acronym for Enter praise service architect SAP solution map
Process Series of actions, changes or functions brings about a result that is integrated by sap net weaver Analytics
Financials
Sap Net weaver  The underlying technology of SAPERP Human capital management
Next generation technology from sap, A plot form for developing integrated solutions, Procurement and logistic execution
Product dev and manufacturing
Web services Sales and services
Accessible via internet
Hide behind it the technological intrics of sap ERP suit of applications Corporate services

How does work

Using widely accepted standards for applications to communicate via the internet
Enabling pre programmed components for integration with Micro soft, .net, sun micro systems, j2ee and
IBM web sphere technology

The web service

Receive the request from various applications
Process the received request
Respond with the requested feature or functionality

SAP Net wear benefits of an organization

By virtue of its technology , has the ability to integrate applications within or outside the SAP ERP suit

1. People Integration Brings the right functionality and right information to the right place
2. Process integration Enhances business process management (BPM)
Capabilities of an organization by providing tools to configure the process
3.Information Integration Provides an organization with both structured and unstructured information that
is consistent and accessible from different and multiple systems

Solution Manager

Solution manager is a stand alone system that communicate with the systems in your various landscapes

Purpose of SAP solution manager Benefits

o Faster Implementation
o Faster Issue resolution
o Optimal support for operations
o Optimal access to support
More reliable it industries
More leverage from it investments
Faster ROI
Reduce cost of implementation
Reduce cost of operation

Solution manager is the central application management plat form that customers can run in their solution
landscape to help them. Implement, operate , monitor and support their SAP solutions
It helps
o Optimize the management of your solution
o Ensure reliability of your sap solution
o Ensure efficient operations
o Ease implementations and upgrades
o Continuously adopt and improve your solution

Solution manager web application server installation connected to all systems in your solution
landscape(satellite system )

Why solution manager

o Faster implementation and more efficient operation of solutions
o All available implementation and upgrade content is included
o Optimal access to all support services
o Optimal support of all operations, maintenance and improvement activities
o Faster issues resolutions through collaboration with active global support

Benefits
Usage scenarios
1.More reliable IT solutions
o Implement SAP solutions
o Minimize risk during implementation
o Monitor sap solution
o Avoid inconsistencies
o Manage service desk
o Resolve issues quickly resulting in less down time
o Link to sap services
o More efficient implementations and change management project
o Upgrade sap solutions
o Manage change request
2.Reduce cost of implementation and continues improvement
o Reduce cost of process design technical setup, business setup and operations, testing and
knowledge transfer
o Centralized project handling blue printing, configuration and testing
o Reduce the cost of upgrades or continues improvement projects Usage scenarios ( Core Business
process)
1.Implementation
3.Faster return on investment (ROI )
- Implement solutions 1
o Accelerator implementation and continues improvement
- Upgrade solutions 6
o Availability of implementation roadmaps, best practice documents and SAP solution management
services speed learning and accelerate project
2.Operations
- Monitor SAP solutions 2
4.Reduce cost of operation
- Manage the support desk 3
o Provide central point of control for multi components environment
o Facilitate technical and application integration
3.Optimization
- Manage change requests 5
5.More leverage from IT investments
- Link to SAP services 4
o Integrates with IT landscapes that include both SAP and Non SAP applications
o Reduce their total cost of ownership without making major changes

The ASAP methodology is a proven, repeatable and success able approach to implement SAP solutions
across multiple industries and customers environments.
First introduced as a PC based tool set called value sap (1990 )
Successfully implement sap solution across multiple industries and customer environment
ASAP is to successfully implement SAP solution across multiple industries and customer environment

Types of Roadmaps
o Global Template roadmap - During implementation
o Implementation roadmap - Technical infrastructure and its operation
o Upgrade roadmap
o Solution management roadmap

Phases of implementations roadmap Project preparation

1.Project preparation Project planning
Project procedure
o Provide initial planning and preparation for sap projects
Technical requirement planning
o General project management requirement
o An Issue management plan Identification of end use and their
training needs
o Organizational change management plan
Conduct kick of meeting
o Establish of other policies and procedures for running the project
Project planning Quality check project preparation
phase
- Create project charter for defining purpose & measurement
 - Refine implementation strategy for objectives and scope
- Establish project team working environment
- Determine project organization including steering committee
- Prepare detail project plan for planning budget and resources
- Prepare project team training and logistic plan

Project procedures
- Determine required systems (DEV, QAS, PROD,IDES & BIW
- Determine client deployment strategy like development client and QA and production etc.
- Determine transport system strategy for managing change requests, development requests
etc

Technical requirement planning

- Initial hardware sizing separately for each system, such as the development system, the
quality assurance system and production system
- Determine the requirement for back up, recovery, and rest of the different systems

Project kick-off
- Kick of meeting
- Milestone activity for officially launching R/3 implementation
- Communication the detail project plan to entire project plan
- Communication the roles and responsibilities of project team members

Quality check project preparation phase

- Define business process documentation standards
- Create issue management plan
- Open issues database in Q & A db
- Create scope management plan- scope change procedures
- Define system land scope
- Project ream ,communication & schedules
- Project documentation procedures
- Development and authorization role standards
- Testing strategies Business Blue print
Conduct level II training program
2.Business blue print
Establish Dev system environment
o Document the business process requirements of the company Business organization structure
o Comprise activities for aligning the customer business and technical requirements to the sap workshop, define and sign off
standard software
Business process workshop,
o Conduct the Level II training program definition, documentation and sign off
o Establish dev system environment
o Business organization structure work shop ,define and sign off
o Business process work shop, definition, documentation and sign off
o Identify roles for authorization generate BPML and conduct quality check

Project management blue print

- Conduct project team status meeting to share information with teams and keep
implementation process unified

- Conduct steering committee, meetings in order to resolve issue according during progress of
various projects;

Development system environment – BASIS

- Create technical design where physical system layout, printing infrastructure, networking
environment
- Create development environment where installation of initial hardware, configuration of
development
 - client, and printing infrastructure maintain system administration procedure, backup
strategies
- Initialize project IMG where creation of project header and scope is defined in SAP R/3
Organization structure workshop
- Schedule organization structure workshop
- Access to key players and Top management is critical
- Organizational structure must be reviewed, presented and signed off
Business process workshop
- Determine general settings and enterprise standers. E.g. Calendar, currencies, unit of
measure, chart of accounts, number ranges etc
- Determine business process requirement and document in the CI template – Q&ADB
- Determine development and authorization requirement document in the CI temple - Q&ADB
- Identify gaps and resolve where ever applicable
- Complete business process analysis and sign off
Authorization roles
- Identify authorization roles in coordination with business process owners and business
process users Unit testing ( Developers )
- The authorization roles need to be mapped to SAP role during realization phase - Particular module of source code

3.Realisation Regression testing

o Implement the business and process requirements based on the business blue print - Version testing

o Comprise the building and testing of the solution as prescribed by the business blue print
Recovery testing
o Software enhancements, special programming, building & executing test plans and finally signoff - Backup
the configured system
o Conduct Level III training program(optional) Security testing
o Complete baseline configuration and final configuration - Avoid unauthorized
o Map roles to authorization roles and generate authorization matrix develop conversion,
enhancement application interfaces, custom reports etc. Stress testing

o Conduct unit, scenario, development and integration tests

Performance testing
o Identify end user training curriculum and documentation - size of software, memory
o Complete end use training logistics plan
Usability testing
o Complete and communicate cut over strategy

Alpha beta testing

Base line configuration - Actual end use, report bugs
- Develop plan for baseline configuration
- Configure General setting and organization structure Integration testing
- Configure and validate baseline
- Prepare and perform baseline confirmation User acceptance test

4.Final preparation
o Complete the preparation for go live
o Many crucial tasks remain ,such as acceptance testing of the production system hardware
o The completion of end use training’
o Plans for transfer to the production system

5.Golive & support

o SLA & help desk procedures are established and tested
o Hand over to the operations and monitoring staff

Types of Roadmaps
Elements of Implementation roadmap Implementation roadmap
Solution management roadmap
1.Roadmap structure Global Template roadmap
o Gives the project team a list of what to do and when to do it Upgrade roadmap
o Filtered by roles so that each member can forces only on those items requiring their attention
Other roadmap

2.Viewing text area

Project management futures
o Procedural guides ,pre requisite information
Issue management plan
Accelator Status Team
notice members
 o Deliverables Scope management plan
Organizational change management
3.Attachment area
o Accelerators ,issues and supplemental documentation Feature of the Business Blue print
o Assigning project team members, tracking the status of the highlighted item in roadmap structure 1.Blue print structure
2.Business scenarios
3.Business process groups
Feature of the Business Blue print 4.Associted Items
5.Blue print document
1.Blue print structure
o Developed through the business process workshops
o All requirements gathered are recorded and associated with a structure item Elements of Implementation
roadmap
Configuration transaction o Roadmap structure
o Is used to business blue print structure to configure IMG objects in development systems.
o Viewing / text area

Operation & support  BPR Business process repository o Attachments area

- Solution monitoring
o System monitoring
o Business process monitoring Roadmap viewing
structure text area
- Help desk

SAP SM Monitoring Attachment

area
o Business process monitoring (CCMS compute centre management system )
o System monitoring .central system Components in configuration
o Service level management ( Based on early watch alert ) 1. Project documentation
2. Transaction assignments
Service desk 3. Configuration of IMG objects
Offers a complete infrastructure for organizing and operating a solution wide support organization at your 4. Development items
site
5. Test cases
1.Message handling process 6. Graphics
End use can create messages that automatically collect system and context data. An interface for third 7. Training materials
party message tools is also included
2.Customer solution database Allows customer to build a history database for future trouble shooting

Provides all functionality to centrally analyses and monitor a

3.Diagnostics Based on solution configuration
complete SAP solution o Remote consulting
o self services
Solution Service desk Change Solution Delivery of Continues
o Best practice documents
monitoring management reports sap services improvement

Change request management Service desk Features

o Integrate service desk functionality for managing change requests Message handling process
o Support urgent corrections for implementations fast and direct changes in the productive Customer solution data base
environment Managing SAP notes
o Maintenances cycle activities Solution manager diagnostics

SM Diagnostics Change request management

o Ability to perform root cause analysis with speed and efficiently Solution manager diagnostics
o Centrally analyze and monitor a complete sap solution
o Reduces the time needed to train a support consultant in root cause analysis

Functional Specification
It is a document, that contains day to day tools Inputs and outputs client given inputs to the functional
consultant and functional consultant in turns to gives output
 Key Information create campaign
1. Channel
2. Target group
3. Campaign description
4. Beginning and ending date
Order to Cash 5. Campaign identification number

o Monitoring and campaign marketing Marketing cycle

o Sales processing - continuous view
o Sales person - how it is work Identify problem
o Logistic executive of customs sales
o Billing invoices
Determine course of action
Market segment
Is the process of dividing customer master data into different groups depending on the planned marketing
activity Identify potential customers
Data sources for target groups include SAP BW reports
SAPBW reports: user master data, profiles, or transactional data
Info set queries : Use general data from the customer master record Create target group

Marketing and campaign management

Marketing department to analysis the market, define strategies plan their activities and then using existing Create and launch campaign
data such as customer data and profiles start markets actions
Marketing analysis SAP CRM, SAP SEM, BW
Marketing campaign ABC classification
Customer request ERP CRM Based on revenue of customers
Logistic execution ERP,SEM,SCM
Billing SAP Financial, SEM
PAY
Marketing analysis
Marketing
Marketing is all about getting the right product, to the right customers, at the right time.
CRM marketing functions integrated with SAPBW, SAP SEM and SAP global supply chain management

Marketing (CRM ) benefits Marketing

campaign
o Plan clear objectives for business and coordinate resources in order to achieve goals
o Measure & monitor the relevant key performance indicators to asses the success of business
o Deploy analytical results to optimize it operational process and empower employees to make
informed decision Customer request
o Uncover hidden patterns and trends that impact business and apply these findings to predict
future shifts in customer be heavier
o Can capture all relevant customer information from different sources and integrate it into a
customer knowledge base Logistic execution
o Market segment are based on different attributes such as demographics, revenues, geography,
fortunately

Bill
Profile : Is a finite list of attributes, attribute values
Profile set : is a folder of related marketing profiles and /or target groups
Target group: List of customer who match the corresponding profile/sets.
Target group is must be assigned to a profile set Pay

Data sources for Target group

SAPBW reports: Use master data, profile or transaction date Eg: sales volume
Info set queries : Use general data from the customer master record e.g.: Zip code

Marketing attributes from the customer master data

Maintain own marketing attributes directly in the master record eg. Hobbies

Differences web shop SAP ERP

Customer places the order Limited access to transaction

Minimal amount of information required Flexible in entering additional detailed information
Includes pictures of product Role based responsibility for creating order

When web shop order is saved by customer

o Automatically saved in SAP CRM
o Order information / including document number always automatically replicated in SAP ECC

o Order confirmation has been transferred to SAP ECC by reviewing a distribution status field
Tcode: CRMD BUS2000115 transaction order no status tab  R/3 transfer and R/3 status

Check product availability

When customer places order using web shop ?
o SAP system performs several automotive validation on the order
o Scheduled line are populated with dates based upon information in order
o Save the uniq document number
o Billing information is saved for future invoices for the customers

Customer service representative

o Enter correct order type
o Add the appreciate sales area information
o Enter customer material number Business content
o Roles
Transactional data
o Work books
Is task related information that is created and saved in the SAP system. An order created using web shop
generates transaction data. Transactional data is different than master data, which is entered once and o Queries
used multiple times o Info cubes
o Extractors , Info sources
Business warehouse o Info objects

o Business warehouse contains a staging engine and a databases

o Business warehouse store not only master data and transaction data but also meta data
o Info cubes, info objects and Queries are part of the business content of business warehouse
o BW server contains a staging engine and database
o Staging area controls the loading and processing of data and prepare data for subsequent
process

Business explore reports tools

Allow you to carryout simulations Microsoft excel and web based analysis according to different dimensions
Business framework components
Sources systems communicates via BAPI business application programming in
Business information ware house Interface

SAP BW allows view both the

Transactional data ( OLTP ) Business strategy

Analysis data ( OLAP ) Knowledge at a same time
 CDM customer distribution model
RFC remote function call
ALE application link enable

IDOC types
- Basic Idoc
Cross Applications - Extension Idoc

ALE Establishing a link between two clients or servers Internal structure of IDOC
- Control record EDIDC table
ALE configuration Tcode: SALE
- Data record EDIDD table
Defining logical system ( DVOLS table ) - Status record EDIDS table
Assigning client to logical system
Define RFC destination SM59 IDoc creation
Create segment WE31
IDOC  Intermediate document  IDOC contains segments ID
Segments contains fields, fields contain data. Create IDOC type WE30
Release segment WE31
Message type stored in EDIMSG table Release IDoc type WE30
IDOC creation Create message type WE81
- Give the data name and data element Assign message IDoc WE82
- Create IDoc type  name it create, select IDOC & Create segment buttons & save it To check the IDoc WE60
- Release the segment  go to  edit  set release button
- Release IDOC BD10 - material
- Create message type WE81 BD11 - get mat
- Click on change –go to new entries name save BD12 - send case
- WE82 click on change go to new entries assign message to IDoc , we have to mention version BD13 - int
BD14 - send vender
2. CDM customer distribution model BD64 BD15 -
BD16 -
- Click on create model BD17 -
- View give name & give technical name
- Select the view and click on “ add message type “ & same
- Go to “ Environment “ “ general partner profiles “ give the partner sys name and execute EDI – electronic data interchange
- Come back two time & save
- Go to edit  model view  distribution  contain TIBCO , MACARATOR
- SM59  go to R/# connection same process for REC limit enable tracking partner to
communicate
EDI
EDI is the electronic exchange of business documents between computer system of business partners,
with a standard format components in EDI
- sender
Business document It is legal document that speaks about the transaction that is been conducted - Receiver
between two different parties
- Language
ANSI X12 American national standards Institute - Content
EDIFACT Electronic data interchange for administration , commerce and transport - Medium
Which supplying common language for format content

EDI process Program types

Outbound process  send document from the SAP system to business partner
Inbound Process  receive an IDOC form a business partner - Executable program
- Function group
- Include program
- Interface pool
- Class pool
- Module pool
- Subroutine pool