Sap Sale Module

RE:[sap-log-sd] No display of Sale Area when creating material/customer

Reply from godslavery on Jan 1 at 11:21 PM

Hi, thanks for concerning about this problem, now I have made it resolved. I take these steps as follows:

1. Using TCODE: ovxgn. It could be displayed like this
AWSO(Amer West Sales org) A1(Amer.distr.chan.01) A2(Amer.division 2)
AWSO(Amer West Sales org) A2(Amer.distr.chan.02) A1(Amer.division 1)
AWSO(Amer West Sales org) A2(Amer.distr.chan.02) A2(Amer.division 2)

2. Using TCODE: vor1(Define Common Distribution Channels)
AWSO A1(Dchl: Amer.distr.chan.01) A1(Dch.Conds) A1(Dch-Cust/Mt)
AWSO A2(Dchl: Amer.distr.chan.02) A2(Dch.Conds) A2(Dch-Cust/Mt)

3. Using TCODE: vor2(Define Common Divisions)
AWSO A1(Dv: Amer.division1) A1(DvCon) A1(Dv-Cust)
AWSO A2(Dv: Amer.division2) A2(DvCon) A2(Dv-Cust)

Now it's ok. But I have a question: what is Dch.Conds, Dch-Cust/Mt, DvCon, Dv-Cust and what's relationship between them? What's the logic run in the process?

I have found some descriptions about these concepts as follows in «Configuring SAP
? ERP Sales and Distribution»by Kapil Sharma Ashutosh Mutsaddi:

The next step in setting up the enterprise structure in SD is to define the common
distribution channel and common division. In situations where your sales organiza-tion contains more than one distribution channel and more than one division, this
customization setting is really helpful in reducing the master data maintenance
efforts and avoiding master data duplication within a sales organization. Using a
common distribution channel customization, you can define the master data for
one distribution channel, and all other distribution channels that belong to that
sales organization can use the same master data. You don't have to create the master
data separately for all the distribution channels.

Common division customization works the same way for divisions that share com -mon master data.

Always remember to define this setting irrespective of whether your business
requirement setup needs a common distribution channel and common division.
You won't be able to create master data using the sales area you just defined if this
customization setting is missing. If you don't have a business requirement demand -ing a common distribution channel and common division setup, maintain the entry
in VOR1 and VOR2 by keeping the source and target the same

---------------Original Message---------------
From: Marlkoos zheng
Sent: Wednesday, December 28, 2011 1:48 AM
Subject: No display of Sale Area when creating material/customer

Hi, I got a problem. I have defined the Sale Area by TCODE: ovxgn, and then I started to creat the material by TCODE:mm01. In the view of Organizational Level I wanted to use the Sale Area (Sales Org. & Distr. Channel) which specific to that material, but when I used the search help there is no display of that Sale Area ( Only Sales Org. display ) . How could this happen?

The problem is also subject to the TCODE:vd01 / xd01 when I tried to creat a custome

Is there anything wrong with my configuration in IMG?

Thanks&Regards

Reply to this email to post your response.

__.____._

Manage Settings | Unsubscribe | Create FAQ | Send Feedback

godslavery

	Mark as helpful
	View this online
	Ask a new question

Related Training

SAP Logistics Modules

> more training

In the Spotlight

Have an SAP Question? Ask Your Peers at Toolbox for IT

_.____.__

RE:[sap-log-sd] Access sequence in rebate processing

Reply from srikant on Jan 1 at 9:22 AM

Hi

what are the key fields maintained in your?Access sequence &?any Requirement for the field is maintained as exclusive for that table 970

Thanks
srikant?

---------------Original Message---------------
From: Reena Anirudh
Sent: Tuesday, August 02, 2011 8:40 AM
Subject: Access sequence in rebate processing

Hello,

I have a total of 60 steps in my rebate access sequence ZRAG with condition tables 601 to 606. I have created a new table 970 and added this as step no. 35 in my rebate access sequence ZRAG. Same has been added to the node "Assign Condition Types/Tables to Condition Type Groups" in SPRO against the relevant Condition Type Group and Condition Type.

My issue is when I create a rebate agreement and maintain the rebate condition records, this newly added access is shown as the last one where as I have added it in the fourth place in my access sequence. I want this new access at the fourth place instead of the last.

Can someone guide me how to get this new access at the fourth place?

Regards,

Thanks.

Reena Anirudh Nair

Reply to this email to post your response.

__.____._

Manage Settings | Unsubscribe | Create FAQ | Send Feedback

srikant
SAP SD Senior Cnsultant
3 achievements

	Mark as helpful
	View this online
	Ask a new question

Related Training

Supply Chain Logistics Management

> more training

In the Spotlight

Have an SAP Question? Ask Your Peers at Toolbox for IT

_.____.__

Re: [sap-log-sd] What is 'release status' in pricing table eg. table 304?

Reply from hovering_yogi on Jan 1 at 9:17 AM

The pricing date gives you that control already.

The release status (as far as I understand it at least) is to allow prices
to be entered in to the system and then used by certain reports for
simulation purposes. When the business team responsible for the proposed
changes are happy with their simulation runs then they can release the
changes and then the records will be picked up with the appropriate pricing
date as before.

I have yet to actually see a site actively using this functionality however
so most bespoke accesses will not include the release option.

Steve.

---------------Original Message---------------
From: saps
Sent: Saturday, December 31, 2011 9:20 PM
Subject: What is 'release status' in pricing table eg. table 304?

Hi Mr.Adriano,

Let us take an example here. Let us consider that the price for a product A is EUR 10 now. We have monthly price fluctuations and if suppose today is the last working day of the month and you have decided that from the next working day, which is the start of the month, the price should be EUR 11. So, we set the price on 30th itself and 'lock' the status of the price today, so that it gets 'released' tomorrow and the price EUR 11 does not reflect on 30th, but only on 1st.

The release status was an added feature. Prior to this, we had Access sequence PR00 with no release status. The latest pricing procedure has acc. seq. PR02, which has a release status.

Reply to this email to post your response.

__.____._

Manage Settings | Unsubscribe | Create FAQ | Send Feedback