Quick Bites - Partner Determination in Nutshell


Partner Determination in Nutshell

Partner Determination is used at various levels all over the SAP. From SD Point of view, Partner determination is used at the following levels:

  1. Customer Master Partner Determination
  2. Sales Document Header Level
  3. Sale Document Item Level
  4. Delivery Document
  5. Shipping Document
  6. Billing Document Header Level
  7. Billing Document Item Level
  8. Sales Activities (CAS)
Below is the high-level Overview of how Partner Determination works in SAP:




Comments

Post a Comment

Popular posts from this blog

MATERIAL YOU MUST STUDY FOR ESTABLISHING YOUR SAP CAREER !!

Image
Important Tips for Interview for SAP SD Let me share some important tips for interview for SAP SD : 1. Please be through with the projects you have mentioned in your resume.  2. Remember all the versions you have worked upon.  3. If your projects are in Indian scenario be thorough with CIN/Excise VAT and pricing procedure.  4  For offshore client specially in Europe and NASA prepare yourself for Warehouse/Lean warehouse  5. Third party billing / Intercompany / Make to order are important topics.  6. Cost booking that is accounting enteries after PGI and Billing should be known to you.  7. Mug up all the determinations.  8. Remember your last ticket.  9. Have general awareness about ALE/EDI/IDOC, as this provides added advantage. (not very tough)  10. Please be through with your basics, the process, the pricing and the master data.  11. People who are thorough with route, transportation, shipping always have an added advantage. The MOST IMPORTANT THING: Do not try to f
Read more

SAP Note 11162 - Invoice split criteria in billing document .

Symptom From a number of deliveries or sales orders more than one billing document is created. Cause and prerequisites The invoice split may have been carried out for the following reasons: a) Explicit setting in Customizing b) Different header partners c) Different header fields d) The billing date of all documents is equated in a data transfer routine (for example, by VBRK-FKDAT = SY-DATUM). This works when you are billing using VF01; a single billing document is generated. However, if you use VF04 or in case of a batch, several billing documents might be generated. Solution Please check the causes mentioned above: 1. Explicit setting in Customizing: On the detail screen of the document flow table (TVCPF) in the entry field 'DATEN VBRK/VBRP' (as of Rel.2.2..: 'Data transfer') the routine '003' (single invoice) was entered and thus an invoice split was created. 2. Different header partners The header partners in the billing documents created
Read more

TAX determination in SD

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 Ta
Read more