Area: Customer Master/Sales and Distribution
Description
Block reason is a factor that blocks document processing of documents. You can define suitable blocking reasons to satisfy your business needs. Then these blocking reasons can be assigned to corresponding document types and used in the SD document processing.
You can also block a customer directly in the customer master. The specification in the customer master record and therefore also the the sales document block is valid either for all or only for individual sales areas.
For the blocked customers in the relevant sales area you cannot create sales document with the sales document type for which this blocking reason is valid. For example, you can block the creation of sales order for a customer but allow inquiry creation.
Read more…
Area: Customer Master
Description
The account group is a classifying feature within customer master records. The account group determines:
- in which number range the customer account number should be
- whether the number is assigned by the user or by the system
- which specifications are necessary or possible in the master record
For example, group of one-time customers, groups of ship-to-parties. You can find the account group of a specified customer record by choose menu Extras –> Administrative Data
Read more…
Area: Logistics Execution – Shipping
Description
Shipping conditions are the general shipping strategy for the delivery of goods from the vendor to the customer. You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master. You can also determine a shipping condition for each sales document type.
Example, a particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.
Read more…
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.
This article tries to analyze how the tax is calculated from a step-by-step example.
Read more…
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.
Some material is the component of the BOM and some material is the final product and is linked to a BOM. Below is logic to check whether a material is a component or is linked to a BOM.
First, check table STPO (BOM item). If the material name is in field STPO-IDNRK(BOM component), it means the material is part of the BOM.
Second, check table MAST(Material to BOM Link). If the material is in MAST table, it means this material is linked to a BOM.
Tables:
MARA – General Material Data
MAST – Material to BOM Link
STKO – BOM Header
STPO – BOM item
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.
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
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…
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…