We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

Re: RE:[sap-log-mm] How do I determine tax pricing Condition in STO with no condition records?

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by Nyandiek
on Jun 16 at 12:05 PM
Mark this reply as helpfulMark as helpful
Actually it does clarify. But still you realise how many times you mention the word 'condition' in either you using or not using. Well I now see you do not want to use a condition 'record'.

Again for trying to understand the terms, condition records are based on other 'If/Else' conditions in codes either for calculation procedures or not.

I suggest you include all your tax calculations in a code in your STO pricing program completely outside condition (anything) so that you directly refer to the parameters in the material master and your import documents. This determination should be based on 'applicable' but on 0 or any other value greater than zero.

I guess the reason you do not need condition records is because your determinant parameters are permanent and will not be conditional changed for any reason and so can be hidden or hardcoded.

Maybe I don't get.
Soulman Nyandiek

-----Original Message-----
From: "Robert_Smith via sap-log-mm" <sap-log-mm@Groups.ITtoolbox.com>
Date: Wed, 16 Jun 2010 14:37:52
To: Nyandiekemail@removed
Reply-To: sap-log-mm@Groups.ITtoolbox.com
Subject: RE: RE:[sap-log-mm] How do I determine tax pricing Condition in STO with no condition records?



So Maybe I am not being clear. Let me try again. When I refer to "'based on certain conditions being met in the material master' I am not referring to pricing conditions I am referring to ie. Certain entries existing at Material master level that will be used to determine the tax liability to be captured in the condition type in the STO.

Essentially we are setting up a bonded warehouse. During STO creation we want a condition type to default into the STO capturing the duty payable to the revenue for the release from bond.

The value captured in the condition type will be based on ie. a breakdown of the number of litres contained within the shipped case and a calculation of the overall alcohol content of the total number of litres shipped.

All of this info is held in the material master. The team that own the pricing function are traditionally weak and given that we are dealing with revenue there is no room for error here.

What I am proposing is that we create a new condition type that will be mandatory for items coming out of a specific storage location and that will calculate a price based on a look up of info from the material master. In other words each STO will default in this condition type and the value of this condition type will be determined by coded logic and not by associated values in a condition record. I want to auto determine the condition type without using a condition record.

So, when the STO is created and pricing determination is executed in the background an access sequence will determine the condition type BUT the values pulled in will not relate to any condition record

Does this clarify?

Tnks
Rob Smith
IS Retail WM







From: Nyandiek via sap-log-mm [mailto:sap-log-mm@Groups.ITtoolbox.com]]
Sent: 16 June 2010 13:16
To: Robert Smith
Subject: Re: RE:[sap-log-mm] How do I determine tax pricing Condition in STO with no condition records?

Posted by Nyandiek
on Jun 16 at 8:13 AM Mark as helpful


All those are conditions! That is why you contradict your first line with this 'based on certain conditions being met in the material master'.

Coding your requirement is another way but setting the pricing conditions on your STO pricing procedure and indicating which tables and which parameters to determine your document behaviour is the decent way to go.

The background coding for price conditioning has been done and you only need to 'maintain' relevant relatioship. Less coding Better SAP'.
Soulman Nyandiek

-----Original Message-----
From: "Robert_Smith via sap-log-mm" <sap-log-mm@Groups.ITtoolbox.com>
Date: Wed, 16 Jun 2010 11:23:56
To: Nyandiekemail@removed
Reply-To: sap-log-mm@Groups.ITtoolbox.com
Subject: RE: RE:[sap-log-mm] How do I determine tax pricing Condition in STO with no condition records?



I want to do this without condition records. In other words, each time I create an STO I want a pricing condition to default in (based on certain conditions being met in the material master) and for the value in the condition applied in the STO to be based on logic I will define in coded requirement. Is this possible? (I'm sure it is and have seen in the past but cant recall how to achieve it?

Rgds
Rob Smith
IS Retail WM

From: ha_tran via sap-log-mm [mailto:sap-log-mm@Groups.ITtoolbox.com]]]
Sent: 16 June 2010 10:33
To: Robert Smith
Subject: RE:[sap-log-mm] How do I determine tax pricing Condition in STO with no condition records?

Posted by ha_tran (Senior SAP Supply Chain Business Analyst)
on Jun 16 at 5:33 AM Mark as helpful


Hi,

You will have to maintain the condition record via Transaction MEK1.

Cheers,
HT

---------------Original Message---------------
From: Robert_Smith
Sent: Tuesday, June 15, 2010 12:26 PM
Subject: How do I determine tax pricing Condition in STO with no condition records?

> I want to create a new condition type to capture a tax charge in an STO. The tax charge is something that will be calculated based on a look up of certain entries. I plan to do this is a coded requirement.
>
> My question is, When I create the condition type how do I trigger its determination in STO's based on these conditions being met. Do I leave the access sequence on the condition type blank ?, or do I have to do this and more? What am I missing?

__.____._
Copyright © 2010 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Related Content
White Papers

In the Spotlight
Earn Recognition for Your Contributions at Toolbox for IT. Gain Points for Community Achievements
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language