Showing posts with label SAP-SD. Show all posts
Showing posts with label SAP-SD. Show all posts

Labels:

Get The Net Price Of Main Item From KUMU Condition Type:- If you want to create a new CBV routine for a new condition type to capture the net price of the main item from KUMU condition type. You have to do the following...

Note: KUMU condion type cumulates the net price of main item and it's sub-items.

Create the new routine in transaction VOFM, and if you want to capture the net price of main item from KUMU amount and write a select query on komv table where kschl = 'KUMU'.
Sidhika is a computer technology professional, educator with experience in the information technology. She works in a multi-disciplinary role that combines IT Infrastructure, SAP Functional and Network Management. If you like this post, Please leave a comment.

Labels: ,

How To Avoid Condition Type VPRS From Being Captured In Pricing whenever we are creating a Credit Memo with reference to the billing document.

Solution:
  • Option 1: This can be avoided by having a different pricing procedure to your credit memo where you dont maintain VPRS. If you dont want then it comes in development it may be in copy controls from billing document to sales document where you have to stop copying if it is for document category is K. Note: Document category K -> Documents from CO. Reference: http://help.sap.com
  • Option 2: You can remove the VPRS condition type from Pricing procedure and do the changes (if any other values r dependent on VPRS)
Or as suggested by others creat new pricing procedure and do the required setting for determination. Only difference is DOC PRICING PROCEDURE.
Sidhika is a computer technology professional, educator with experience in the information technology. She works in a multi-disciplinary role that combines IT Infrastructure, SAP Functional and Network Management. If you like this post, Please leave a comment.

Labels: ,

Plant specific Tax GL accounts : TAXINN procedure : when you want to acheive plant wise seperate GL accounts for sales taxes (VAT & CST). There are two ways of get it done.
  1. Creating separate plant wise tax codes and assigning them in appropriate tax condition records VK11 and maintaining General Ledger (GLs) in OB40.
  2. Creating a dummy Tax code for all tax condition types and maintaining separate GLs through VKOA for the key combination of Sales org/*plant*/account key by creating a new table.
From the above two, First Option seems to be feasible and best way to solve the issue . In fact, you can even add Plant as one of those combinations to your tax condition type and in VK11, you can assign different tax codes accordingly.
Sidhika is a computer technology professional, educator with experience in the information technology. She works in a multi-disciplinary role that combines IT Infrastructure, SAP Functional and Network Management. If you like this post, Please leave a comment.

Labels:

What is the exact transaction or table where we can check the required partners for a customer account?

You can go to spro as described below...
In SPRO -> Sales and Distribution -> Basic Functions -> Partner Determination
  • Identify the partner procedure using the customer account group, (table: TKUPA)
  • Using the partner procedure, you can identify the mandatory partner functions. (table: TPAER)
Sidhika is a computer technology professional, educator with experience in the information technology. She works in a multi-disciplinary role that combines IT Infrastructure, SAP Functional and Network Management. If you like this post, Please leave a comment.

Labels:

If you want the sample materials are sent to the sales office and that it should be taken back once the exhibition is over. Better you go with consignment fillup process where, you treat the sales office as a sold to party and the exhibition venue as ship to party. Of course, you will have to take care of ED and VAT part.

With this settings, the inventory will only get reduced from manufacturing plant and will be in sales office account as "Cust.consignment".

Once the exhibition is over, you can create a consignment pick up and take back the exhibition materials to the manufacturing plant.

VLMOVE will not meet this requirement. VLMOVE - will be useful for goods movements for handling units and materials with 23 options inside it.

Purpose Of VLMOVE Transaction Code:
For material there are 17 options and none of the options suits your requirement.
This TCode will not be useful If you want to use this transaction for sending exhibition materials to your sales office.
Sidhika is a computer technology professional, educator with experience in the information technology. She works in a multi-disciplinary role that combines IT Infrastructure, SAP Functional and Network Management. If you like this post, Please leave a comment.