Hi Redyy,
Go through the explanation given below with test cases.
INTERCOMPANY SALES
Business case: -
Customer orders goods to company code/Sales organization A (Eg.4211/4211).Sales org 4211 will accept and punch the order in the system with sold to party as end customer code in the system. Company code/sales org B (Eg.4436) will deliver the goods to end customer and raise an intercom any billing on 4211 with reference to delivery. This can happen only after 4211 raises invoice to his end customer to whom the material has been delivered by 4436.
SPRO Customization required:-
1. Assign plant of delivering company code (Eg.SI81) to sales org/distribution channel combination of ordering company code (Eg.4211/RT)
2. Maintain intercom any billing type as IV for sales document type OR
3. Assign Organizational Units By Plant (Eg.SI81/4211/RT/11)
4.Define Internal Customer Number By Sales Organization (Eg.4436 will create customer master for 4211 company code and that number will be maintained in this relationship:-4211/231)
5. Automatic posting to vendor account (Optional)
6. Maintain pricing procedure determination for 4211/RT/A/1/RVAA01-For customer sales and billing
Maintain pricing procedure determination for 4436/RT/A/1/ICAA01-For intercompony billing
Master data to be maintained:-
1. Create end customer master in company code/sales org 4211/RT/11
2. Create customer master for 4211 company code/sales org in 4436/RT/11
3. Maintain PR00 as price for end customer-Active in RVAA01
4. Maintain PI01 as price which has to be paid to 4436-Statistical in RVAA01
5. Maintain IV01 as inter-company Price-Active in ICAA01
Process:-
1. Create OR with sold to party as end customer.
2. Plant to be selected is delivering plant belonging to different company code. With this selection system will treat this order as intercomany sales.
3. Pricing procedure is RVAA01
4. With reference to this order delivery will be created from the delivering plant and post the goods issue for this delivery.
5. Ordering sales org will create billing document F2 with reference to delivery for end customer.
6. Delivering sales org will create intercompany billing IV with reference to delivery document.
STO
Whenever you need to transfer the materials from one plant to another plant belonging to one company or belonging to two company code stock transfer order is raised by the delivering company.
STO:
Transfer of goods from one location to another location,it may be between plants within the same company code or in different company code's plants.
within the company code,bet plants, receiving plant will raise the STO in Supplying/issuing plant-ME21n,
Supplying plant will deliver the goods to receiving plants , then we need to pick n post the Goods Issue-VL02n, nw when we can observe that the STO qtty will be added into receiving plant and reduced in Delievering plant.
Configure Intercompany Stock Transport Order
Material should exist in both the plants (Delivering & Ordering),
Internal customer should be assaigned to the ordering plant ( MM -> Purchasing -> Purchase Order -> Setup stock transport order -> assign the internal customer to the ordering plant and assign the Sales area of the internal customer.
Assign its Sales area to the delivering plant
Assign the document type and Delivery type NB and NLCC
Assign the Supplying plant --> Receiving Plant --> NB
Take the delivering plant and assign the sales area.
Vendor master has to be created and assaign the supply source ( Delivering Plant).
Create a puchase order ME21N ---> Save
Delivery VL10 G ---> Calculation rule (appropriate) --> Assaign the purchase order number here and execute.
Select the Delivery creation line and do the back ground process.
Start the log display and see the delivery document number by the documents button
Goto VL02N --> do picking and PGI --> Then do the MIGO with respect to the delivery document.
Billing (Intercompany pricing conditions should be set).
TAX DETERMINATION
Define Tax Determination Rules
You specify the valid tax types in transaction OVK1. More than one tax type can be defined for a country by defining the sequence.
The SAP System determines the taxes automatically within pricing.
In the standard SAP R/3 System, the elements of tax calculation are predefined (for example, tax condition type "MWST" for taxes on sales and purchases).
Assign the plant for Tax Determination in OX10, using the country key, the SAP System recognizes which tax type is valid for a plant and thus which taxes are relevant when creating an SD document.
Define the Customer Taxes in OVK3, you will maintain the tax code in Customer Master.
Define the Material Taxes in OVK4, which will then be maintain in Material Master.
For example :-
MWST GST 0 Tax Exempt
MWST GST 1 Liable for Taxes
Now, you define the Tax Determination in VK12.
VK12 - Domestic Taxes/Export Taxes
Condition Type MWST
Customer Taxes Material Taxes Rate Taxes
0 0 0 %
0 1 0 %
1 0 0 %
1 1 9 %
In this example, if both the Customer Master and Material Master Tax code is 1, Tax will be included when you create the Sales Order.
Tax Code in Customer Master / Sales Order
How can we maintain the Tax Code (Tax code - which we maintain in MWST Condtion Records) in Customer Master or in Sales Order?
There are few points which I would like to remind you:
1) MWST is a tax condition which is applied to customer to whom we are selling. The rate of tax is depend on various parameteres, whether is fully liable for tax or expemted (in case of Defence Customer)
2) There are few parameteres which we apply tax condition. Whether customer is tax liable? Whether material is tax exempted?
For example, if you are selling a goods which are free for tax to any customer, put the Tax Indicator (at MMR as '0'). If your
material is tax liable pur the Tax Indicator (at MMR as 1). If your customer is not liable for tax at all (like the case of Indian
Defence organisations) put the Tax Indicator (at CMR as 0) or 1 in case fully tax liable.
3) Now, at VK11 you need to mainatain your pricning conditions with all the combinations like:
1 0
1 1
0 1
0 0
4) While maintaining your Material Master Records or Cusotmer Master Records, you must identify, which are tax liable and which are tax exempeted.
5) In anycase, as a SAP standard Best Practises, while processing a sales order, you must retrieve a Tax condition record from SAP database only and not entered Manually. Accordingly, at V/06, the MWST condition Defintions, the field for 'Manual Entries', it would be marked as - D (Not possible to process Manually).
Due to this setting, normally, you cannot maintain Condition tax code during sales order processing. And in Cusotmer Master, you can only maintain Tax Indicator and not Tax Code.
6) In case your client insists for Manual entry of Tax code during Sales Order processing, you can change the field at point 5) above to C-Manual entry is priority instead of D.
For Taxation with an example just click this link:
http://www.sap-img.com/sap-sd/taxation-explain-with-an-example.htm
Reward if helpful.
I hope this helps you.Reward points if solution is useful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.