Delivery Processing

There are various functions in delivery processing like −

• Quantity Management and adjustment
• Text Management
• Printing
• Validation

You can post quantity difference in the inbound delivery for outbound delivery to post change in delivery. Using text management, you can make the following changes to the delivery document like −

• Display
• Change
• Delete
• Save

If you want to create and save new texts for a particular delivery, this can also be done.

Printing is done in EWM to print delivery notes. You can create an outbound delivery order or an outbound delivery. Validation in EWM is used to verify the delivery document, if it is complete and can be further processed in the system.

Structure

A document comprises a document header and any number of document items. The following figure shows the structure of a delivery document.

SAP SD - Picking, Packing & Post Good Issue

Picking of goods is done in SAP warehouse management system. It is done via a transfer order, which is used for picking list and to withdraw the goods from the stock.

There are three types of Picking −

• Picking of goods individually
• Picking as per defined intervals
• Automatic Picking in SAP SD module

Packing of goods is done with the packing material and to be created as material type − VERP. This can be done in two ways −

• Manual
• Automatic

The Post Good Issue (PGI) is the last step in delivery processing and in this goods ownership is moved to the customer and stock is updated as per delivery.

These functions can be performed in the system using the following steps −

• Creating an Outbound delivery
• Creating Picking Request
• Create Packaging
• Creating Post Goods Issue

SAP Sales And Distribution

SD: Free Goods

Purpose:

1. This is common practice to provide free goods to the customers. Free goods can be inclusive or exclusive.

Process:

1. Sales order is created as usual.
2. Inclusive free goods: e.g. 1 unit out of 10 units is free.  So, if a customer is ordering for 10 units, 1 unit will be given free and customer will pay only for 9 units.
3. Exclusive free goods: e.g. if a customer is buying 10 units, he will get additional 1 unit free. So, if a customer is ordering for 10 units, 1 unit (additional) will be given free and customer will pay only for 10 units. Exclusive free product can be either same as ordered product or can be a different product.
4. In the sales order, free goods (item category TANN) are displayed as a sub item of the original item.

Configuration/Master data:

1. Free good procedure is assigned to combination of sales area, document pricing procedure and customer pricing procedure.
2. Free goods procedure is created in the same way as we create pricing procedure, listing/exclusion procedure etc using condition technique.
3. Free goods – condition records are created using tcode VBN1.
4. In condition records we can control, if free goods are delivered alone or with main item.
5. Calculation type for determining free goods quantity. E.g. company is offering 3 units of free goods for 100 units ordered. Customer orders 212 units.
1. Pro rata: free goods quantity is rounded. Free goods quantity = 212*3/100 = 6.36 = 6 (after rounding)
2. Unit reference: Ordered quantity is rounded down as per condition record quantity. Free goods quantity = 200 (rounded down)*3/100 = 6
3. Whole units: checks if ordered quantity is multiple of condition record quantity. Free goods quantity = 0 as 212 is not multiple of 100.
4. We can create our own calculation rules using VOFM tcode.
6. For item category TANN, if
1. Pricing field (in item category configuration VOV7) is maintained as blank (no pricing): there will be no pricing (zero) for free goods.
2. Pricing field (in item category configuration VOV7) is maintained as ‘B’ (Pricing for free goods (100% discount)): and maintain condition type R100 with requirement 55 (free goods) in the pricing procedure, then sales order will have 100% discount for free item.

Sap SD

Material Determination, Listing, Exclusion, and Proposal
Material Listing and Exclusion

Material listing/exclusion is functionality in SAP SD that controls what materials a customer can buy. When you maintain a material listing for a customer, the customer can only buy those goods contained in the material listing assigned to the customer. Conversely, material exclusions allow you to set up a list of materials that a customer cannot buy.

Examples for material listing/exclusion

The first example shows how a material listing record maintained for a customer restricts a customer order to be processed only for listed materials, whereas the second example shows how material exclusion helps you exclude a particular material in customer order processing. The end results from both the approaches are same.

You can maintain a material listing at a sold-to level and also at a payer level. In the event the sold-to and payer are different and the material listing is maintained at both levels, the sold-to material listing takes precedence over the payer material listing. If the listing is only maintained at either the sold-to level or the payer level, SAP picks that level. If there is no listing maintained at either level, the customer is allowed to purchase any material without any restrictions. If your business scenario demands a new configuration setup for material listing/ exclusion, you can configure that by setting up the condition technique for material listing/exclusion.

Incompletion logs

In general

Incompletion Log ensures that all required fields in a document are populated. Incompletion procedures can be configured to (1) raise no messages, (2) raise a warning message, or (3) raise an error message.

If configured with no warning message, the system will indicate the sales document is incomplete and offer an option to complete missing data upon save. The incompletion procedure determines to what extent further processing of the document is allowed and if subsequent documents can be created. If a document is incomplete, it cannot be referenced.

Incompletion procedure

An incompletion procedure groups the fields together that must be checked for completion. If any of the fields are blank, the document is incomplete. Incompletion procedures can be assigned and maintained at various levels and for various document types:

• Sales header (different procedures can be assigned to different document types)
• Sales item (item categories can contain different procedures)
• Schedule line (each can contain different procedures)
• Partners (can maintain different procedures for each partner function)
• Sales activity
• Delivery header
• Delivery item

To display the procedures run transaction OVA2 or use the IMG path > Sales & Distribution > Basic Functions > Log of Incomplete Items > Define Incompletion Procedures.

Incompletion procedures are assigned to each document type via transaction VUA2 or use IMG path > Sales & Distribution > Basic Functions > Log of Incomplete Items > Assign Incompletion Procedures > Assign Procedures to Sales Document Type. The incompletion procedure can be viewed in document configuration (VOV8) but can only be changed here. To prevent the document from being saved if any fields are incomplete, check the box IC-dialog. In example below document type CR (Credit Memo Request) cannot be saved if any fields in incompletion procedure 14 are not populated.

How to customize the Partner Determination Procedure?

We can determine partner determination procedure by using the transaction code VOPA.
In the business different people interacts to make a transaction with the business while making transactions with the business every partner performs certain roles those are called as a partner functions.

Depending on the partner type every partner fulfill certain mandatory partner functions.  SAP determines relevant partner functions automatically to relevant partner object type.

Flow: Customer master, Sales, Delivery, Billing, Document header and items.

A) Partner Types.
1) Customer(KU)
He performs partner functions like Sp, Sh, Bp, Py.
2) Vendor(LI)
Partner Functions (FA- Forward Agent).
3) Contact Person (AP)
Partner Functions-CP.
4) Sales Employee(PE)
Partner Funcitons-SE

Authorized Partner to release the order

Contracts are release by raising sales orders. 

In the business one specifies partner is authorized to enter and to release contracts. 

At Header level( sales document) there is a control by which system carries out checks against partner whether he is authorized to release the contract.
Partner type(KU) and Partner Functions( AA- Sold T party) to release the contracts.
Aw- ship to party to release the contracts and this partner functions assigned to partner determination procedure (kab).
Partners to check credit limits:
We define partner functions
Km-credit Manager.
kb- credit representations  both belongs to partner  type pe(personal)
Configurations settings:
1) Define Account Group( OBD2)
2) Assign Number range key to Account Group (OBAR)
3) Define partner determination procedure for customer master.
a) Define partner functions
Path: Img -> sd -> basic functions -> partner determination -> set up partner determination -> set up partner determination for customer master.

Click on partner function control button under dialog structure

Partner Function Name         Partner type error
sp             sold to party  ku            07
sh             ship to party  ku            07
bp            bill to party    ku            07
py            payer             ku           07
partner type Pe
Km          credit manager  pe           09
kb            credit represent  pe           09
 
b) Define partner determination procedure.
c) Assign partner functions to partner determination procedure.
d) Assign partner determination determination procedure to account group.
e) Assign partner functions to account group.

For sales document. 

a) Define Partner functions to sales document header 
1) Define partner functions 

img -> sd -> basic functions -> partner determination -> setup partner determination -> set up partner determination for sales document header
2) Define partner determination procedure.
3) Assign partner functions to partner determination procedure 
4) Partner Determination procedure assignment.

Determination of Schedule Line Category in SAP SD

Determination of Schedule Line Category in SAP SD

Schedule line category:

In SAP SD process, schedule line category in sales order decides whether or how the system passes on requirements to materials requirements planning (MRP).

Determination:

Schedule line category is determined based on Item Category and MRP type

• Item category is determined(sales document type + item category group + item usage + higher level item category) in sales order(screen 1.0)
• MRP type is defined in material master - MRP 1(screen 1.1)

Screen 1.0

Screen 1.1

Determination Rule:

1. Item Category + MRP type
2. Item Category (if there is no MRP type defined), refer screen 1.2 for detail

This assignment is maintained in t-code VOV6(screen 1.2)

Screen 1.2

Stay Updated
Enter your email address:


Delivered by FeedBurner

Item categories in sales order

Item Categories

Item categories are defined to provide additional control functions for the sales documents and thus meet the demands resulting from different business transactions. A separate control is defined for each of these item categories. For example, the functions of a standard item are completely different from those of a free-of-charge item or a text item.

The following graphic shows some of the item categories which are defined in the standard system. For instance, the first example displays the item categories for a standard item in the inquiry, in the quotation, and in the sales order.

Item Category Control

The system uses an item category to process a material differently in each sales document type. For example, you can define a different control for a material in an inquiry and a material in an order.

The following graphic shows an example of how a material is controlled in an inquiry and how it is controlled in an order.

In the inquiry, the standard item is priced but is not relevant for delivery. For the free-of-charge item, however, which is subordinate to the standard item, no pricing is carried out and it is not relevant for delivery.

In the sales order, the situation is different. Both items are relevant for delivery but pricing is carried out only for the standard item.

Control Elements in Item Categories

Depending on the sales document type, different item categories are allowed. The item categories can also be adapted using control elements to meet the special requirements of your installation. You can modify the existing item categories or you can create your own. Your system administrator is responsible for maintaining the control elements.

The answers to the following questions form the basis for deciding how to define a particular item category:

General data

• Should pricing be carried out for the item?

• When should an item be regarded as completed? A quotation item, for example, can only be regarded as completed if the entire quantity has been copied into a sales order.

• Does the item refer to a material or is it a text item?

• Are schedule lines allowed for the item?

• May general business data, for example, the terms of payment at item level, deviate from those at header level?

• Should a system message appear if the item cannot be fully delivered?

• Which fields are relevant for the incompletion log?

• Which partner functions are allowed at the item level and which are mandatory?

• Which output (for example, an order confirmation) is allowed for the business transaction and which output determination procedure is used?

Shipping data

• Is the item relevant for delivery?

• Should the weight and the volume of an item be determined?

Billing data

• Is an item relevant for billing?

• Should the cost of the item be determined?

• Is it a statistical item? The system prices statistical items, but they are not added to the value of the order. In other words, the customer is not charged for them.

• Should a billing block be set automatically for an item? For example, this may be important for items whose prices have to be clarified before billing.

• Is it a returns item?

Determining the Item Category

The item category in the sales document depends on the sales document type and the material. An item category group is defined in the material master record. For example, in the standard SAP System, the item category group NORM is defined for materials kept in stock and the group DIEN for services and non-stock material.

The following graphic shows how the system determines the item category. For a material with item category group NORM, the system determines the item category AFN for an inquiry (sales document type IN) and the item category TAN for a standard order (sales document type OR).

Determining the Item Category for Sub-Items

Services and free goods can be entered as separate items or can be allocated to other items. An item which is allocated to another one is called a sub-item. Determining the item category for sub-items depends on the higher-level item.

If a free goods item is allocated to a standard item in a standard order (item category TAN), the item category TANN is used for the sub-item in the standard version of the SAP System, and the sub-item is processed as a free-of-charge item.