Helpful Links:

http://help.sap.com/saphelp_erp60_sp/helpdata/en/4d/2b912a43ad11d189410000e829fbbd/content.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4d/2b910343ad11d189410000e829fbbd/content.htm
STOCK TRANSPORT ORDER
Pre-Requisites :
1. Creation of Customer Master data u2013 Create both the Plants are Customers in XD01
2. Creation of Vendor Mater data u2013 Create both the Plants are Vendors. For each Vendor select the other Plant as the Customer (already created in
Serial No.1).
3. IMG Settings : In MM > Purchasing > Purchasing Order > Set up STOCK Transport Order > Define Shipping data for Plants.
Select each Plant and enter Customer number of the other plant created in Step1 along with the data of Sales Org, etc.
4. Excise Master Data - In J1ID see that the material data is entered for both the Plants.
Process Flow
Step 1 - Creation of STOCK Transport Order.
In ME21N mention the Issuing Plant. Please check the item tab Invoice and see the Tax juridiction code as IN00. Check and Save the PO.
Step 2 u2013 Transfer Posting
Do the transfer posting in MB1B with proper Plant selection and movement type 351. Refer the PO and adopt the details. Note the Material document
number.
Step 3 u2013 Creation of Excise Invoice
Create Excise Invoice for other movements in J1IS Select the document type as MATD. See that the system is automatically creating the Invoice. Note
the Excise Invoice Number and FI document number created by the system.
Step 4 u2013 Posting of Excise Invoice
The Transaction code is J1IV Save the document and take the print.
Now the Material is reached at 2nd Plant. The activities at that Plants are :
Step 5 u2013 Capturing of Excise Invoice
Its an ordinary J1IEX transaction. Capture the Invoice against the STOCK Transport Order. See that Plant 2 is automatically appeared. Enter the required
detail and save the document and note the internal number.
Step 6 u2013 Goods Receipt
It is also an ordinary MIGO transaction. Enter the excise invoice details, save the document and note the material document number.
Step 7 u2013 Posting the Excise Invoice
J1IED transaction. Select the tab as posting against Vendor Excise Invoice. Input the required detail. Click on SIMULATE CENVAT and see the postings. If
it is OK, Post the Invoice. Note the serial number and Accounting document number.

Four Pricing Procedures in SAP SD:

1.
2.
3.
4.

JINFAC: SALES FROM FACTORY

JINEXP: EXPORT SALES
JINDEP: DEPOT SALE
JINSTK: STOCK TRANSFER

Based on the following setting system come to know which pricing procedure it should pick.
SALES ORGANISATION +DISTRIBUTION CHANNEL+DIVISION+CUSTOMER Pricing Procedure in Customer Master and Document Pricing Procedure and they are mapped
for the Pricing in:
SPRO>SD>Basic Functions>Pricing>Pricing Control>Define And Assign Pricing Procedures>Define Pricing Procedure Determination
** Here you will find unique combination and pricing Procedures.So in case you can have different Document types such as for Local SALE Export, DEPOT etc. and from here
each will pick different pricing procedure.
Through this ways system knows which pricing it should pick.
I will take one example for Factory SALE
VA41>VA01>VL01N>VF01>J1IIN
Please remember that all the excise condition types needs to be assign to
SPRO>Logistics - General>Tax on Goods Movements>India>Basic Settings>Determination of Excise Duty>Condition-Based Excise Determination>Maintain Excise
Defaults>TAXINN
here you assign respective pricing condition type so that during J1IIN it can bring the value all Excise SD related conditions are assigned to column starting with A/R i.e.
Account Receivables.

Read Saravanan blog which is bookmarked

Generally, STO process are of 2 types.
1) Inter-company STO(Stock transfer between plants assigned to 2 diff. company codes)-PO of doc type NB
2) Intra-company STO(Stock transfer between plants in same company code)-PO of doc type UB
In both the cases, once the PO is created. Ensure you find Shipping tab in the PO item level. This is the key to bring this PO in VL10B.
Get in VL10B, try to create delivery for the PO. Once the delivery is created. It doesnt' t mean stock is moved.
Delivery has to be picked, PGI'd.
In Tcode OMGN-> You have a indicator which decides whether to automatically post the goods in receiving plant once it is PGI'd from supplying plant.
One-Step procedure- If this is set for particular supply. and rec. plant. Goods will be automatically posted in receiving plant the moment it is issued from the
supplying plant.
If not, you will have to manually do MIGO_GR and receive the stock in Rec. plant.
So, this is the general process flow.
But if you are stuck in any of the steps mentioned. In that case, you have to relook the suggestions provided by us in our earlier posts. Because one of those could
be the reason which blocks you from proceeding ahead.
Please let us know the outcome.
If this is not the one you are looking for. Please be more specific and give us more details on the issue you are facing.

================================================================
Hi Bhaskar,
Is the PO not showing in VL10B? or is the Delivery not being created?
If the PO is not appearing in VL10B
You need to check and ensure following things
1) Please check if the Purchase order has Shipping tab at item level.
2) As Ivano rightly pointed out, check if there is an entry in table VETVG.
3) Please check if Delivery complete indicator is set in the PO item.
4) Please check if you have provided the right shipping point in selection screen of VL10B. Shipping point should be the one which you see in Purchase order
shipping tab.
5) Please check that the PO line item is not deleted or locked.
If the delivery is not getting created though the PO appears in VL10B
You need to check following things
1) Get in the PO item Shipping tab for Shipping point. Go to Material master Plant data/Storage view and identify the storage conditions.
With the Shipping point, Storage conditions and Supplying plant Go to table TVKOL- Picking location determination and check the sloc. setup.
2) Go to MMBE and check if there is enough stock in the Sloc fetched in the above step.

Configuration steps involved in STO:

STO -- Following are the steps:

1.Create a vendor for the company code of receiving plant, using account group :0007 using T-Code XK01.
2 Assign this vendor to Delivering plant
Go to XK02 >Purchasing view>Extras>Add. Purchasing data>Plant
3. Create internal customer with the sales area of the vendor. Go To XD01
4.In Pricing procedure determination relevant to STO, assign document Pricing Procedure and customer pricing procedure appropriate for STO to get the pricing in
the invoice.
5.Maintain condition records for the relevant pricing condition.
6. Some more setting for STO: Go to MM> Purchasing > Purchase Order > Set up STO> define shipping data for plants > Go to Receiving plant >assign customer here
& Supplying SA (for billing) to Receiving plant here
7. Go to MM> Purchasing > Purchase Order > Set up STO> define shipping data for plants > Go to Supplying plant and assign the sales area of receiving plant.
8. Go to MM> Purchasing > Purchase Order > Set up STO> assign delivery Type & Checking rule
Assign the delivery type to document type. In this case, Delivery type NLCC is assigned to Document type NB
9. Go to MM> Purchasing > Purchase Order > Set up STO>Assign document Type, One step Procedure, Under delivery tolerance,
Assign the document type NB to supplying plant and receiving plant
10. After all settings , Create the STO using T-Code:ME21n and Save.
11. Create Delivery :VL10G
Click on the Background Button after selecting line item
A message is flashed : See log for information> next Click on Log for delivery creation Button >click on line item>click on document button to get Delivery document
No
12. Picking, PGI:[VL02n
13. Billing:VF01n
Save the document and its done

as well ref the blw links

http://help.sap.com/saphelp_erp2005vp/helpdata/en/4d/2b8ec943ad11d189410000e829fbbd/frameset.htm
Stock Transfer with Delivery
http://help.sap.com/bp_blv1600/V5600/BBLibrary/HTML/134_EN_IN.htm
Stock Transfer without Delivery
http://help.sap.com/bp_blv1600/V5600/BBLibrary/HTML/135_EN_IN.htm

=================================================================================

https://www.google.co.in/search?q=sap+sd+overview&oq=sap&aqs=chrome.0.69i59l2j69i57j69i65l3.42
37j0j7&sourceid=chrome&espv=210&es_sm=93&ie=UTF-8

Deemed Export
Welcome to the SD-CIN-Deemed Export page.
This process is specific to India Localisation Business Scenario.

Overview
This scenario deals with Deemed Export or CT-1/CT-3 or SEZ sales that refer to sale of goods to customers within India, who are generally holders of an export license. The
materials sold are required to be used in the production of goods meant for ultimate export. The customers can be an export-oriented unit (EOU) or located in one of the
following areas:

An Export processing zone

An Electronic hardware technology park
A Software technology park.

Sales Process
For this Deemed Export sale:
An inquiry can be the first step in the order cycle. The purpose of this activity is to create an inquiry to represent the customers inquiry in the system.
Then a quotation can be created to determine material, their quantities, prices and payment terms that are valid for a given sold-to customer during a specified time period. As
prerequisites, it can be referred from an existing inquiry and terms of payment need to be in place.
Then in system we need to capture the Customers License Details. This done for

Deemed Export License is captured in the system to represent customers licenses.

For capturing Customers License details like material, quantity, value, expiry date etc.,
Deliveries will take place against the license quantity / value.

As prerequisites, a copy of the license obtained by the customer from issued by relevant authorities.
Then a Sales Order is created to represent the customers requirement in the system. That will calculate the price and check for the availability of materials. As prerequisites, it
can be referred from an existing quotation and should mention material that are mentioned in customer licence details.
Then with reference to the created sales order, a Pro Forma Invoice can be created in order to inform the customer about the value of the goods, so that he will make
arrangements for the payment to be made, when goods arrive at his place.
With reference to the created sales order, the delivery document is created for shipping point mention in sales order to pick the goods and post goods issue based on availability
of the ordered material.
With reference to post goods issue delivery material, a billing document is created to send a commercial invoice to the customer. It also updates the corresponding GL Accounts.
Further its output can be taken.
With post goods issue completed for the delivery and respective billing document generated, the Excise Invoice created for the excise authorities. And subsequently print for
accompanying materials that are being sent to the csurtomers.
ARE-3/ARE-1document is created with reference to generated outgoing Excise Invoice. This is assigned to a License captured for the customer. This document is a proof that,
goods are treated as Deemed exports and Excise duty does not need to be paid for these goods, which are mentioned in the ARE-3/ARE-1.
After the responsible official confirms that all the details are correct, we can post the ARE-3/ARE-1 document. The changes are allowed to the ARE-3/ARE-1 document only if, it is
in the process pending posting. Once posted, the ARE-3/ARE-1 cannot be changed but can only be cancelled.
Going further, we can print the ARE-3/ARE-1 documents for submitting to the customer and the excise authorities. After ARE-3/ARE-1 Document is created and posted and also
when the goods arrive at the Customers premises, they will check them against the excise invoice and the ARE-3/ARE-1. If there are any discrepancies in the quantity of the
goods, the customer will record the actual quantity received on the ARE-3/ARE-1.To record the customers confirmation of the quantity delivered, we update the ARE-3/ARE-1

document.Finally, when the countersigned ARE document arrives back at your premises from the customer, the ARE-3/ARE-1 is further updated with the date of receipt. This
closes the ARE-3/ARE-1.

Figure: Flow Chart for the Scenario: Deemed Export from supplier point of view.
Also refer SDN wiki link on ARE1: CIN Creation - Updation - Post - Cancel for process flow with transaction code in ARE1.

System Configuration Considerations

1

Defining Sales Document Type for deemed export

Creating Pro Forma Invoice for deemed export

Creating Billing Type for deemed export.

Assigning Billing Types to Delivery Types

Maintaining Item Categories

Copying Control for

a. Sales Document to Sales Document (Inquiry Quotation, Quotation Deemed Export Sal Doc Type)
b. Sales Document to Billing Document (Deemed Export Sal Doc Type Pro Forma Invoice)
c. Sales Order type to Delivery Type (Deemed Export Sal Doc Type Delivery Doc)
d. Delivery type to Billing Type (Delivery Doc Billing Doc)

Configuring Pricing
a. Pricing procedure for pricing
b. New customer pricing procedure (Cust.pric.proc. is maintained at customer master) need to be maintain for deemed export for differentiating from export

pricing while pricing determination.

8

Account determination

Maintaining Number Range for Excise Bonding License for object J_1ILIC

10

Creating a new Series Group (maintain new series group

a. Maintaining Number Range for Local Excise Invoice for object J_1IEXCLOC
b. Making Settings for ARE-3/ARE-1 Procedure
c. Maintaining Number Range for ARE-3/ARE-1 for object J_1IARE3/J_1IARE1
d. Defining Processing Modes per Transaction, this will make ARE-3/ARE-1 options active in the ARE-3/ARE-1 screen
e. Defining Reference Documents per Transaction

11

Maintaining an output types for ARE-3/ARE-1 Sales which will be based on plant.

12

The following Master Data will attract attention,

a. Maintaining Customer Master, particularly, Cust.pric.proc. in pricing section of Sales Tab in Sales data.
b. Customer CIN details (J1ID)
c. Maintaining Material Master
d. Material CIN details (J1ID)
e. Maintaining relevant conditions records for:

i.

Pricing

ii.

Tax

Development activity to be consideration

Following output type & program we may need to maintain/modified as per requirement:
Object

Object Name

Object Desc

Configuration

Output Type

J1ID

Excise Bonding ARE

New config may be required

Output Type Access Sequence

ZJ1D

ARE3 Op Acc Seq

New config may be required

Program

J_1IPRNTARE

Print program for ARE

Std config available

Form

J_1I_ARE3

J_1I_ARE3 Printing

Std config available

Further Information:
Following are few of the License Types:
1. CT1,
2. CT2,
3. 108/95 (un-projects),
4. 15/2009(solar projects), etc.
So, when CT1 is one of the license types, for that you need to create ARE3 use TCode J_1IARE3. Then you need to capture license by using TCode J1ILIC01.
Further, if your scenario is of exporting under bond, then you might need to create ARE1 use TCode J_1IARE1 and also create bond by using TCode J1IBN01.

==================================================================

One Step Procedure for STO between storage locations (iff Intra plant)