Depot Sales

3/12/13 Depot sales | ABAP, SAP, benX AG, benXBrain, Brain
brain
store
Login
Signup
Query - you can use e.g. CL_* for classes
We are currently in a beta-phase, there could be some issues. Please be patient. Please send us your Feedback .
Home
Documents 6
My files
All documents 6
Top files
Top downloads
Thread
SAP Object
Detail
Documentation
Wiki
My Notes
tcdw0_f01_unicode.benxbrain.com/en(bD1lbiZjPTAwMQ==)/index.do?onInputProcessing=brai_thread&001_thread_id=2099178 &001_temp=R3TR%7cDTEL%7cVBTYP%7c%7cWD4 1/19

Files
SDN 687
Favourites
All favourites
Classes/Methods
Domains
Data elements
Functions
Messageclasses
Reports
Tables
Transactions
BSP-Views
SAP Objects 8.290.783
Classes/Methods 408.877
Functions 849.322
Data elements 790.293
Reports 430.439
Tables 770.254
Transactions 152.473
Messageclasses 17.771
BSP-Views 1.536
Options
Account
Home | SAP Object | Thread | VBTYP
VBTYP Data Element

Share!
Facebook
Twitter
Mail
Description SD document category

Creator SAP
Created on
Package BV
Description SD Cross-application Objects
Available at
Component
Change System
CRM
ECC
SOLUTION MANAGER
NETWEAVER
#1 Depot sales Original

Hi All,
Please provide me the solution on the following.
Use of routine 356 in depot sales pricing procedure

(ii) Steps involved in depot sales (right from the STO i.e. plant to depot & from depot to cust)
(iii) Excise transaction type for scrap sales
(iv) Where do we define ETTs
(v) Scrap sales excise invoice is created through which t.code
(vi) In system landscape client 800 called as
(vii) Use of different payment terms at company code data & sales area data in XD01
(VIII) MTO & MTS for single material code is configured. At VA01 system not considering un-restricted stock and while doing MRP Run requirements are get
generated for sales order total quantity
Regards

Chowdary
#2 Re: Depot sales Original
hi
i sto process: vao1-vl01n-vf01-j1iin it foe sd process ofter mm people doing migo- j1ig , it means when u create the migo document stock can transfer to depo
plant and storage location . ofter j1ig can capture. its for closing the sto
foter depo sales: va01-vl01n-j1ij-vf01.
it si for depo process .
i n sto can use deferent process so based on your requirment .
in use of 356 ; routine
----
INCLUDE FV64A356 *

----
&----
*& *
*& *
*& *
&----
data: begin of t_rg23d occurs 0.
include structure j_1irg23d.
data: end of t_rg23d.
*********************************************************
APPL COUNTRY SPECIFIC
form frm_kondi_wert_356.
For depot sale : picks the excise value from RG23D
************************************************************************
This formula when in the billing or proforma document, picks up the

excise value posted for the delivery if the excise has been posted.
In case the excise is not posted, then it continues with the excise
value calculated in the system . It shows the calculated value in
the sales order also
----
TABLES : J_1IRG23D.
DATA : tline type i,
ZKOMV LIKE KOMV,
LAND1 LIKE T001-LAND1,
KALSM LIKE T005-KALSM.
DATA : result type f.
DATA : zvbrp like vbrp .
if komk-vbtyp = 'M' or komk-vbtyp = 'U'.
billing document or proforma document
read table t_rg23d with key vbeln = komp-vgbel
posnr = komp-vgpos.

if sy-subrc ne 0.
refresh t_rg23d.
endif.
describe table t_rg23d lines tline.
if tline eq 0.
select * from j_1irg23d into table t_rg23d
where vbeln = komp-vgbel
and posnr = komp-vgpos
and status <> 'B'.
if sy-subrc ne 0.
exit.
endif.
endif.
if j_1iexcdef-j_1itaxcal is initial.
get customisation parameters
select single land1 from t001 into land1
where bukrs = komk-bukrs.
select single kalsm from t005 into kalsm

where land1 = land1.
select single * from j_1iexcdef
where j_1itaxcal = kalsm.
endif.
get the condition names
clear xkwert.
get the excise value
loop at t_rg23d.
case xkomv-kschl.
when j_1iexcdef-j_1icbedar.
xkwert = t_rg23d-exbed + xkwert.
when j_1iexcdef-j_1icsedar.
xkwert = t_rg23d-exsed + xkwert.
when j_1iexcdef-j_1icaedar.
xkwert = t_rg23d-exaed + xkwert.
*NCCD changes start
WHEN J_1IEXCDEF-J_1ICNCCDAR.
XKWERT = T_RG23D-NCCD + XKWERT.

*NCCD changes end
*ECS changes start
WHEN J_1IEXCDEF-J_1ICECSAR.
XKWERT = T_RG23D-ECS + XKWERT.
*ECS changes end
WHEN J_1IEXCDEF-J_1ICCESAR.
xkwert = t_rg23d-cess + xkwert.
endcase.
endloop.
exit.
elseif komk-vbtyp = ' '.
saving the document, get the value from the internal table XKOMV
read table xkomv into zkomv
with key kschl = xkomv-kschl.
xkwert = zkomv-kwert.
elseif komk-vbtyp = 'H'.
billing document or proforma document
read table t_rg23d with key vbeln = komp-vgbel
posnr = komp-vgpos.
if sy-subrc ne 0.
refresh t_rg23d.
endif.
describe table t_rg23d lines tline.
if tline eq 0.
select single * from vbrp into zvbrp where vbeln = komp-vgbel and
posnr = komp-vgpos .
if sy-subrc ne 0.
exit.
endif.
select * from j_1irg23d into table t_rg23d
where vbeln = zvbrp-vgbel
AND POSNR = KOMP-VGPOS
and status <> 'B'.
if sy-subrc ne 0.
exit.
endif.
endif.
if j_1iexcdef-j_1itaxcal is initial.
get customisation parameters
select single land1 from t001 into land1
where bukrs = komk-bukrs.
select single kalsm from t005 into kalsm
where land1 = land1.
select single * from j_1iexcdef
where j_1itaxcal = kalsm.
endif.
get the condition names
clear xkwert.
get the excise value
loop at t_rg23d.
case xkomv-kschl.
when j_1iexcdef-j_1icbedar.
result = t_rg23d-exbed / T_rg23d-MENGE .
xkwert = result * komp-mglme .
when j_1iexcdef-j_1icsedar.
result = t_rg23d-exsed / T_rg23d-MENGE .
when j_1iexcdef-j_1icaedar.
result = t_rg23d-exaed / T_rg23d-MENGE .
*NCCD changes start
WHEN J_1IEXCDEF-J_1ICNCCDAR.
result = t_rg23d-NCCD / T_rg23d-MENGE .
*NCCD changes end
*ECS changes start
WHEN J_1IEXCDEF-J_1ICECSAR.
result = t_rg23d-ECS / T_rg23d-MENGE .
*ECS changes end
WHEN J_1IEXCDEF-J_1ICCESAR.
result = t_rg23d-cess / T_rg23d-MENGE .
endcase.
endloop.
exit.
else.
document other than the billing or the proforma
exit.
endif.
endform.
this for standerd routine at vofm
5) __scrap scales excise invoice t.code j1iin__

6) payment terms use based on customer , u can differentiate to the customer . it whole sale customers , retail customer s.
7) in mto u can maintain the requirement type kek- so it means it is for special stock ,
so material u can define with mrp views, u can maintain the schedule line CP,
This is mto, scenario,
on MTS scenario u can maintain deferent requirement type ,
U CHECK THE setting in availabulity cheek
8)With in CIN the account determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you
need alternate account determination for handling various scenarios you can define sub transaction types. The sub transaction types and corresponding account
assignments needs to be maintained in CIN customization
Edited by: bojjasivasankarreddy on Dec 15, 2011 7:08 AM
*Please find below my comments..*
Use of routine 356 in depot sales pricing procedure
This formula when in the billing or proforma document, picks up the
excise value posted for the delivery if the excise has been posted.

In case the excise is not posted, then it continues with the excise
value calculated in the system . It shows the calculated value in
the sales order also
(ii) Steps involved in depot sales (right from the STO i.e. plant to depot & from depot to cust)
Create STO(ME21N - Doc.type: UB at receiving plant) -
>Create Delivery(VL10B from Supplying Plant)----->PGI( VL02N from supplying Plant)-->_Create excise invoice for other movement (J1IS)_---
>GR at Receiving Plant based on Outbound Delivery at Receiving Plant
(iii) Excise transaction type for scrap sales
EWPO
(iv) Where do we define ETTs
SPRO -> logistics general -> tax on goods movement

(v) Scrap sales excise invoice is created through which t.code
J1IIN
(vi) In system landscape client 800 called as
It depends upon the client whether it is located in DEV, QTY, PRD servers
(vii) Use of different payment terms at company code data & sales area data in XD01
Based on your Company code and Sales Area data, the payment works based on your configuration like whether it can be 100% advance before
delivery for 1 sales area but the same customer can have option to pay after delivery in an different sales area. all these are based on ur payment
terms given in xd01
(VIII) MTO & MTS for single material code is configured. At VA01 system not considering un-restricted stock and while doing MRP Run requirements are get
generated for sales order total quantity
Reason could be that the stock needs to assign to particular sales order using MBIB - E
Please put some efforts to find out answers to your question. Moreover, avoid dumping too many questions in one thread. Most importantly, go through the
forum rules which you can find on top (first three threads) and adhere to forum rules.
G. Lakshmipathi
©benX AG
About benX AG
|
Press
|
Company
Terms & Conditions

|
Privacy Statement
|
Disclaimer
Glyphicons Free licensed under CC BY 3.0 .
Feedback
×
Feedback
You can send us your feedback to feedback@benx.de.
or
fill out this form.

Name
Name
Feedback
Send!
Close

Depot Sales

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Depot Sales

Uploaded by

Copyright:

Available Formats

3/12/13 Depot sales | ABAP, SAP, benX AG, benXBrain, Brain

Query - you can use e.g. CL_* for classes

tcdw0_f01_unicode.benxbrain.com/en(bD1lbiZjPTAwMQ==)/index.do?onInputProcessing=brai_thread&001_thread_id=2099178 &001_temp=R3TR%7cDTEL%7cVBTYP%7c%7cWD4 1/19

Home | SAP Object | Thread | VBTYP

VBTYP Data Element

Description SD document category

#1 Depot sales Original

Please provide me the solution on the following.

Use of routine 356 in depot sales pricing procedure

(iii) Excise transaction type for scrap sales

(iv) Where do we define ETTs

(v) Scrap sales excise invoice is created through which t.code

(vi) In system landscape client 800 called as

tcdw0_f01_unicode.benxbrain.com/en(bD1lbiZjPTAwMQ==)/index.do?onInputProcessing=brai_thread&001_thread_id=2099178 &001_temp=R3TR%7cDTEL%7cVBTYP%7c%7cWD4 4/19

#2 Re: Depot sales Original

foter depo sales: va01-vl01n-j1ij-vf01.

it si for depo process .

i n sto can use deferent process so based on your requirment .

in use of 356 ; routine

tcdw0_f01_unicode.benxbrain.com/en(bD1lbiZjPTAwMQ==)/index.do?onInputProcessing=brai_thread&001_thread_id=2099178 &001_temp=R3TR%7cDTEL%7cVBTYP%7c%7cWD4 5/19

data: begin of t_rg23d occurs 0.

include structure j_1irg23d.

data: end of t_rg23d.

APPL COUNTRY SPECIFIC

For depot sale : picks the excise value from RG23D

This formula when in the billing or proforma document, picks up the

tcdw0_f01_unicode.benxbrain.com/en(bD1lbiZjPTAwMQ==)/index.do?onInputProcessing=brai_thread&001_thread_id=2099178 &001_temp=R3TR%7cDTEL%7cVBTYP%7c%7cWD4 6/19

value calculated in the system . It shows the calculated value in

the sales order also

DATA : tline type i,

ZKOMV LIKE KOMV,

LAND1 LIKE T001-LAND1,

KALSM LIKE T005-KALSM.

DATA : result type f.

DATA : zvbrp like vbrp .

if komk-vbtyp = 'M' or komk-vbtyp = 'U'.

billing document or proforma document

read table t_rg23d with key vbeln = komp-vgbel

tcdw0_f01_unicode.benxbrain.com/en(bD1lbiZjPTAwMQ==)/index.do?onInputProcessing=brai_thread&001_thread_id=2099178 &001_temp=R3TR%7cDTEL%7cVBTYP%7c%7cWD4 7/19

describe table t_rg23d lines tline.

select * from j_1irg23d into table t_rg23d

where vbeln = komp-vgbel

and posnr = komp-vgpos

and status <> 'B'.

get customisation parameters

select single land1 from t001 into land1

where bukrs = komk-bukrs.

select single kalsm from t005 into kalsm

where land1 = land1.

select single * from j_1iexcdef

where j_1itaxcal = kalsm.

get the condition names

get the excise value

xkwert = t_rg23d-exbed + xkwert.

xkwert = t_rg23d-exsed + xkwert.

xkwert = t_rg23d-exaed + xkwert.

*NCCD changes start

XKWERT = T_RG23D-NCCD + XKWERT.

*NCCD changes end

*ECS changes start

XKWERT = T_RG23D-ECS + XKWERT.

*ECS changes end

xkwert = t_rg23d-cess + xkwert.

5) scrap scales excise invoice t.code j1iin

Please find below my comments..