SUbcontracting Challan for differnt sales area under same plant

[kunal_ingale]

Hello all ,

I have a scenario where we have two product lines differentiated by Distribution channel and Division under same sales org.

now SAP provided solution for creation of subcon challan with GST and in that they refer the customising node V_001W_IV ( STO config).

at this node I can have only one sales area under one plant So now how can we create challan for other sales area without extending the material and customer master ( its in bulk volume).

does anyone have such scenario in their organisaiton?

thanks

kUnal

[kunal_ingale]

Hello ,

no one have similar situation?

thanks

kUnal

[JL23]

Please see OSS note 170082 - Enhancd sales area determination f.standard system

[JL23]

The question about different sales areas for Stock transfers has probably been asked about a 100 times, and either got no answer or a kind of "not possible" answer, or you have to do all this with user exits. You just add the CHALLAN as addition requirement.

I don't even know how a CHALLAN looks like, but if the Challan is a legal requirement then it has probably not much to do with sales areas, as even companies who do not use SAP need to file their CHALLAN

[kunal_ingale]

hey Jurgen....thnks for reply

I have already started developement for it ,but need to know if anyone else have the same scenario as SAP replied me tht its only me who asked for this requirement.

AS per gst solution provided by SAP , challan is a performa invoice which cheks the Sto sales area and then look for master data in that sales area to create performa invocie. this doesn't allow me to use other dc and div.and only solution is to exyend all my master data to Sto sales area.

The standard SAP provide me functionality to bifurcate my business based on dc and div. Then while doing this challan why it considers the config of sales are which is rigid to have only one sales area at a time.

anyways....was just looking if i am not the only one who is looking for this finctionality. I will say this is a bug or limitation of solution deployes by SAP.

Thanks

kUnal