Archive

Archive for the ‘SD’ Category

SAP SD-Consignment Process

July 12th, 2011 No comments

What is this turtorial about?

basic knowledge about sd consignment process.

 

Turtorial

Consignment is very regular in daily commercial life.It usually happens when our customer’s customers want to save the cost.

They will require to handle the goods according to consignment process.They only pay the money when the goods have been sold out.

 

The key point in consignment is the value of the stock.

There is a stock type named consignment in SAP MM module.This is the way that sap differ the value of the stock.

 

There are four stage in sales consignment process.

  • Consignment Fill-up.

Read more…

SD – Condition Type Upper and Lower Limits

May 27th, 2011 No comments

Sometimes,user have the requirements to set a range for specific condition type.

There are two ways to control this.

First way,control price in VK11,VK12.Just click Go to->Detail

image

you can set the limits on the screen.

Read more…

SD-Item Category

May 27th, 2011 No comments

Item Category is basic knowledge about SAP SD Processing.It’s a sub element of sales order,which controls behavior of sales order Item,

such like pricing revelant,billing revelant.

6[}WQG]PHWTE%[A3HSFJ13D

There are many bussiness scenario need item category supports.

Such like consignment processing,sales bom processing,they have their own special item category.

Sales order determine sales order item category by,sales order type,item usage and item category group.

Read more…

SD&PP Integration – Link between sales order and production order.

May 23rd, 2011 No comments

PP is one core module of sap erp software.There is a lot of factors that influence requirements element of PP module.Sales order is one type of data source of requirements element.Plan order can be generated by sales order requirements,and then generate production order.

The relationship between sales order and production order is

sales order(VA01)->requirement(MD04,MD02)->Plan Order->Production Order(CO02)

In MTO scenario,we can define if one sales order to one production order and control whether the operation on sales order influence production order.For example, one production order is the result of  so requirements,when we delete the sales order,we want there is a alerting message that tells us because there is one production order exits for the so,the deletion of so is not allowed.

How to achieve the effect?

Read more…

How SAP SD determines Tax Code

April 19th, 2010 1 comment

In sales order processing procedure, the output tax amount is calculated automatically according to the configuration. Below screenshot shows the tax rate is 4% and total tax amount is 28.00 USD based on sales price 700.00 USD.

clip_image002

This article tries to analyze how the tax is calculated from a step-by-step example.

Read more…

SD Return Order Process

February 26th, 2010 4 comments

Return process is a common process in SD. Customer may be not satified with the deliveried goods or the deliverable is not what customer exactly want. In these case, customer want to initiate the return process. SAP has provided standard steps for return process.

Create Return Order

Sales department creates return order using transaction VA01. Standard return order type is RE. It can be copied out and adapted according to custom requirement. The return order can be created with reference to sales order or billing document.

Create Return Delivery Document

Sales department creates return delivery document using transaction VL01N. The standard return delivery document has delivery type LR. This delivey type is configured in return order type RE. Below pic shows their relationship.

After the return delivery document has been created. Logistics department can post the document and receive the return goods to the warehouse.

Create Credit Memo

Finance department creates credit memo using transction VF01. The money can be refunded to the customer. The returned goods need to inspected and moved to corresponding area using different movement type(such as 453, 459). Transaction MB1B can be used for this purpose.

Subsequent Activities

After the goods has been returned to plant. The customer may request good replacement or refund. For the first option, the subsequent activity is create another standard sales order and follow the standard sales process: sale – delivery – billing – payment. If customer choose refund, the money can be refunded to the customer using credit memo.

Serial Number Function Module in SD

September 24th, 2009 1 comment

You can use serial number component to identify and differentiate between individual items of material.All the function modules related to serial number in SD module is located in function group IPW1(Serial Number Management in Documents).

Below are the most useful function module to add serial number to an SD document like sales order,delivery document and so on. It also contains a sample code to show you how to use these function module.
SERNR_ADD_TO_AU
SERNR_ADD_TO_HU
SERIAL_LISTE_POST_AU

* save the serial no
  LOOP AT it_sernr[] INTO it_sernr.
 
    CALL FUNCTION 'SERNR_ADD_TO_AU'
      EXPORTING
        sernr                       = it_sernr-sernr
        profile                     = lv_sernp
        material                    = i_matnr
        quantity                    = lv_qty
        document                    = i_vbeln
        item                        = i_posnr
        debitor                     = i_kunnr
        vbtyp                       = i_vbtyp
        sd_auart                    = i_auart
        sd_postyp                   = i_pstyv
     EXCEPTIONS
       konfigurations_error        = 1
       serialnumber_errors         = 2
       serialnumber_warnings       = 3
       no_profile_operation        = 4
       OTHERS                      = 5.
 
  ENDLOOP.
 
* save the serial number to the database
 
  CALL FUNCTION 'SERIAL_LISTE_POST_AU'.

The profile is the serial no profile which defined in material master.

SAP Intercompany Business Processing

September 23rd, 2009 1 comment

Intercompany business processing describes business transactions which take place between two companies (company codes) belonging to one organization. The ordering company orders goods from a plant which is assigned to another company code.

The following intercompany business transactions are possible:

Intercompany sales processing

A sales organization which is assigned to the ordering company code creates a sales order ordering goods from a plant assigned to another company code.

The plant in the delivering company code delivers the goods to the customer for whom the sales organization placed the order.

Intercompany stock transfer

A purchasing organization which is assigned to the ordering company code creates a purchase order ordering goods from a plant assigned to another company code.

The plant in the delivering company code delivers the goods to the plant for which the purchasing organization ordered the goods.

Because the two companies balance their accounts independently, the delivering company must bill the ordering company for the goods. This internal billing transaction is carried out by means of an intercompany billing document. The delivering company bills the ordering company at a price that allows the delivering company to cover its costs.

Read more…

SD Process Flow and tables

September 23rd, 2009 2 comments

SD Process Flow

1. Inquiry (VA11)

2. Quotation / Contracts / Scheduling Agreements (VA21)

3. Sales Order (VA01)

4. Delivery

a) Create Delivery (VL01N)

b) Picking (LT03)

c) Picking Confirmation (LT12)

d) Packing (Optional in VL02N)

e) Post Goods issue (VL02N)

5. Billing(=Invoice) (VF01)

6. Post Incoming Payment (F-28)

Read more…

SAP ERP SD Pricing – Technical Perspective

September 17th, 2009 No comments

This post will only focus on the technical perspective of SD pricing. Condition technique has many uses in SAP, the most import part is in pricing. I will post a new blog about how to add custom condition type to pricing procedure.

Program:

SAPMV45A. This is the entry point of sales document process like tcode VA01,VA02 and so on. The two userexit in this program for pricing is:

USEREXIT_PRICING_PREPARE_TKOMK This userexit is used to fill custom field of pricing communication structure in header level.

USEREXIT_PRICING_PREPARE_TKOMP This userexit is used to fill custom field of pricing communication structure in item level.

Read more…