SAP SD Third Party sales process with MIGO and Without MIGO complete class with Configuration
TLDRThis video tutorial explores the third-party sales process in SAP's Sales and Distribution module. It covers the setup for third-party materials, the creation of sales orders, purchase requisitions, and purchase orders. The instructor explains the invoicing process, including the use of MIGO for vendor payments and customer billing, highlighting the margin gained in third-party transactions. Two scenarios are discussed: with and without MIGO, emphasizing the importance of configuration settings for successful third-party sales.
Takeaways
- 😀 The video discusses the third-party sales process in SAP's Sales and Distribution module, where goods are procured from vendors instead of being manufactured by the company itself.
- 🛍️ In a third-party sale, a sales order is created along with a purchase requisition, which is a request to the vendor to send goods directly to the customer.
- 💼 The term 'MIRO' stands for material invoice verification, which is the process of paying the vendor after receiving goods.
- 📊 A margin is earned in third-party sales, where the company pays the vendor a certain amount and sells the goods to the customer at a higher price.
- 🔍 There are two scenarios for third-party sales in SAP: with MIGO (goods receipt and invoice verification) and without MIGO (only invoice verification without goods receipt).
- 📚 The script explains the process of configuring and creating materials, sales orders, purchase requisitions, and purchase orders in the context of third-party sales.
- 🔑 The importance of activating the purchasing tab in the material master and setting the item category group to 'BANS' for third-party items is highlighted.
- 📝 The script details the steps for creating a sales order, including entering the third-party material, setting the item category, and using specific document types.
- 🔄 The process of creating a purchase requisition based on a sales order and how it is automatically generated at the scheduling category level is described.
- 📑 The video outlines the steps to create a purchase order from a purchase requisition and the subsequent creation of a MIGO document for invoice verification.
- 💻 The script provides insights into the system's controls and configurations for third-party sales, such as the settings in the item category group and purchasing tab.
- 📈 The video concludes with the importance of proper configuration for successful third-party sales processes in SAP, emphasizing the need for correct settings to enable the creation of necessary documents.
Q & A
What is the third party sales process in SAP SD?
-The third party sales process in SAP SD involves creating a sales order for goods that the company does not manufacture but procures from vendors. This process includes creating a purchase requisition for the vendor to send goods directly to the customer, followed by creating a purchase order, and then processing vendor invoice (MIRO) and customer billing.
What is a purchase requisition in the context of third party sales?
-A purchase requisition in third party sales is a request to the vendor to send goods directly to the customer. It is created as part of the sales order process when the company does not have the goods in stock and needs to procure them from a vendor.
How does the margin work in third party sales?
-In third party sales, the margin is the difference between the price the company pays to the vendor and the price the company charges the customer. For example, if the company pays $20 to the vendor and charges the customer $120, the margin is $100.
What are the two scenarios of third party sales in SAP SD?
-The two scenarios of third party sales in SAP SD are with MIGO (Goods Receipt and Invoice Verification) and without MIGO. With MIGO, there is an actual goods receipt and invoice verification process, while without MIGO, it is a statistical process for invoice verification only.
What is the role of MIRO in the third party sales process?
-MIRO (Material Invoice) is used in the third party sales process to record the payment to the vendor for the goods received. It is an essential step after the goods have been delivered to the customer and the company needs to settle the payment with the vendor.
How is the material master configured for third party sales?
-For third party sales, the material master should be configured with the item category group set to 'BANS', indicating that it is a third party item. The purchasing tab should be activated, and the purchasing group should be maintained. Additionally, the material should be marked as a trading good.
What is the significance of the item category group 'BANS' in third party sales?
-The item category group 'BANS' signifies that the item is a third party item, meaning the company is selling it from a vendor rather than manufacturing it themselves. This setting is crucial for the system to recognize the item as part of the third party sales process.
How does the system know if a material is a third party material?
-The system identifies a material as a third party material based on the item category group set to 'BANS'. This setting in the material master helps the system to differentiate between items that the company manufactures and those that are procured from vendors.
What is the difference between a purchase requisition type 'NB' and 'ZNB' in third party sales?
-In third party sales, a purchase requisition type 'NB' indicates that it is a standard purchase requisition, while 'ZNB' is used for non-business purposes. The selection of the type depends on the specific requirements of the sales process.
Why is the Goods Receipt (MIGO) considered statistical in the third party sales process without MIGO?
-In the third party sales process without MIGO, the Goods Receipt (MIGO) is considered statistical because there is no actual goods receipt taking place. The company is not receiving the goods; instead, the goods are sent directly from the vendor to the customer, and MIGO is used for tracking and invoice verification purposes only.
What are the implications of not maintaining the GR (Goods Receipt) option in the sales order for third party sales?
-If the GR option is not maintained in the sales order for third party sales, the system will not create an actual Goods Receipt (MIGO) document. This means that the company will not track the physical receipt of goods, and the process will be limited to invoice verification only, which is a statistical process.
Outlines
🛒 Introduction to Third-Party Sales in SAP
This paragraph introduces the concept of third-party sales in SAP's Sales and Distribution module. It explains that in third-party sales, the company does not produce the goods but instead sends them from standard vendors to customers upon request. The process involves creating a sales order and a purchase requisition, which is a request to the vendor to send goods directly to the customer. The company then creates a purchase order and makes a payment to the vendor (Miro), followed by customer billing, where the customer pays the company. The company earns a margin on the transaction, which is the difference between what they pay the vendor and what they charge the customer. The paragraph also mentions two scenarios in third-party sales: with and without goods receipt (GR) and invoice verification (my go).
🔍 Understanding Third-Party Material Identification in SAP
The speaker discusses how the SAP system identifies third-party materials based on the item category group 'BANS'. When creating a sales order, the system recognizes the third-party nature of the material through the settings in the material master data, specifically in the purchasing tab where the item category group is set to 'BANS'. The paragraph also covers the creation of a sales order (VA01) and the importance of the schedule line category, which is set to 'CS' for third-party sales, indicating no delivery is involved. The system creates a purchase requisition based on the sales order, and the absence of a movement type in the procurement section signifies that no goods receipt is expected.
📋 Configuring Purchase Requisition and Order in Third-Party Sales
This section delves into the configuration settings for purchase requisitions and orders in third-party sales scenarios. It explains the importance of maintaining the correct vendor in the sales order, which will automatically appear in the purchase order if set as a fixed vendor. The paragraph also covers the options 'ZR' for creating a non-validated (statistical) GR and 'GR' for a validated GR, which is necessary for billing. The speaker mentions the process of creating a purchase requisition and order, emphasizing the system's ability to display the document flow and the importance of checking the configuration settings for proper document creation.
🚀 Creating Goods Receipt and Vendor Payment in SAP
The speaker describes the process of creating a goods receipt (GR) and vendor payment (Miro) in SAP for third-party sales. Although no actual goods receipt is expected in third-party scenarios, a statistical GR can be created for tracking purposes. The paragraph explains the steps to create a GR, emphasizing that the system will not show any stock in the unrestricted use list because no physical goods are received. Following the GR, the speaker discusses creating a vendor payment document, which is linked to the purchase order and is crucial for allowing customer billing in the system.
🔄 Completing the Sales Process Without Shipping Notification
This paragraph focuses on completing the sales process in third-party sales without a shipping notification (GR). The speaker explains that after creating a purchase order, a sales order can be created without a subsequent GR, as the system allows billing based on the invoice quantity from the vendor payment (Miro). The paragraph highlights the importance of the item category level settings for billing relevance and the process of creating a sales order after the completion of the vendor payment.
📝 Finalizing Billing and Configuration Settings in Third-Party Sales
The final paragraph discusses the final steps in the third-party sales process, including the creation of customer billing based on the completed vendor payment. The speaker emphasizes the importance of the configuration settings at the item category level, which determine the billing process. The paragraph also touches on the use of trading goods in third-party sales and the necessity of maintaining the correct item category group ('BANS') and settings in the purchasing tab for proper process execution. The speaker concludes by inviting viewers to subscribe to the channel and reach out with any questions or doubts.
📧 Viewer Engagement and Support
In the concluding remarks, the speaker encourages viewers to engage with the content by subscribing to the channel, liking the video, and sharing it with others. They also invite viewers to reach out with any questions or doubts they may have regarding the topic, offering a direct line of communication for further clarification and support.
Mindmap
Keywords
💡Third Party Sales
💡SAP SD
💡Sales Order
💡Purchase Requisition
💡Purchase Order
💡MIGO
💡Customer Billing
💡Margin
💡Item Category Group
💡Goods Receipt
💡Invoice Verification
Highlights
Introduction to the third party sales process in SAP SD (Sales and Distribution) module.
Explanation of the concept where goods are sent from standard vendors instead of being produced by the company.
Process of creating a sales order and purchase requisition in third party sales.
Understanding the role of purchase requisition as a request to the vendor to send goods directly to the customer.
Creation of a purchase order following the sales order in third party sales.
MIRO (Material Invoice Receipt) as a vendor payment process in third party sales.
Customer billing process and how to achieve margin in third party sales.
Two scenarios in third party sales: with MIGO (Invoice Verification) and without MIGO.
The difference between statistical MIGO and original MIGO in third party sales.
Explanation of the IPO (Item Procurement Order) process in contrast to third party sales.
How to configure material master for third party sales, including activating the purchasing tab.
Importance of item category group 'BANS' for identifying third party items.
Process of creating a sales order in transaction VA01 for third party sales.
How the system recognizes third party materials based on item category group 'BANS'.
The significance of 'Building Relevance FF' in sales order for third party sales.
Automatic creation of purchase requisition at schedule line category level in third party sales.
Configuration settings for creating purchase orders and the importance of the 'ZR' option for enabling MIGO.
Process of creating a MIGO document for invoice verification in third party sales.
Explanation of the conditions under which customer billing is allowed after MIGO in third party sales.
How to handle the process of third party sales without MIGO, focusing on statistical MIGO for tracking.
Configuration steps for third party sales at the material master level and their importance.
Conclusion and invitation for feedback on the third party sales process in SAP SD.