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.
Customer
XD01 Create Customer (Centrally)
XD02 Change Customer (Centrally)
XD03 Display Customer (Centrally)
XD04 Customer Changes (Centrally)
XD05 Block customer (centrally)
XD06 Mark customer for deletion (centr.)
XD07 Change Customer Account Group
XD99 Customer master mass maintenance
XDN1 Maintain Number Ranges (Customer)
Vendor
XEIP Number range maintenance: EXPIMP
XK01 Create vendor (centrally)
XK02 Change vendor (centrally)
XK03 Display vendor (centrally)
XK04 Vendor Changes (Centrally)
XK05 Block Vendor (Centrally)
XK06 Mark vendor for deletion (centrally)
XK07 Change vendor account group
Read more…
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
I want to let you know about a manufacturing & ERP software industry timeline on below website: http://www.softwareadvice.com/manufacturing/#timeline
The timeline includes 17 key events that have shaped the ERP software industry over the last 50 years. It’s a quick way to understand the context of current enterprise software events.
“We want to grow this to 35+ events and dates with the help of industry professionals (like yourself). Think of it as a ‘wiki-timeline.’ “, the author said. It gives you lots of information about ERP history.
When using MM01,MM02,MM03, you will find different views for each material. Material with different material type may have different views. For example, material with type finish goods do not have the purchase view as it is produced internally.
This can be defined in below path:
Logistics – General
Material Master
Basic Settings
Material Types
Define Attributes of Material Types
Read more…
All the condition records are stored in table KONH(Conditions Header),KONP(Conditions Item),KONM(Conditions 1-Dimensional Quantity Scale). Condition table like A017(A***) has a field named KNUMH which is the primary key of above condition record table.
Table KONV is used to store the condition transaction data. Field named KNUMV is used to connect table VBAK and KONV.
When define the condition table, we can mark one or serval fields with tool icon. Like pic below:
Read more…
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…
Lots of SAP new comers are confused by the version of SAP ERP(R/3). This post will clarify this question.
The first version of SAP’s flagship enterprise software was a financial Accounting system named R/1. This product is launched in 1973.
SAP R/2 was in a mainframe based business application software suite that was very successful in the 1980s and early 1990s.
SAP R/3 was released in 1992. SAP R/3 is SAP’s integrated software solution for client/server and distributed open systems. SAP’s R/3 is the world’s most-used standard business software for client/server computing. R/3 meets the needs of a customer from the small grocer with 3 users to the multi-billion dollar companies The software is highly customizable using SAP’s proprietary programming language, ABAP/4.
SAP R/3 is supported up to 4.6c. After that the product was renamed to SAP R/3 Enterprise and the platform was change from SAP Basis to SAP Web Application Server 6.20.
In 2004, SAP provide renamed its product name to mySAP ERP 2004 with application set name SAP ECC 5.0. At the same time the technical platform has changed from web AS to SAP Netweaver 2004. Netweaver 2004 support both Java and ABAP environment.
Read more…