0% found this document useful (0 votes)
20 views

Understanding Integration Inventory Masters

The document discusses integration of inventory masters in Tally. It describes stock group, stock item, and unit of measure masters. It provides XML request samples to create, alter, and get responses for stock group and stock item masters. It also discusses optional attributes that can be added to a stock item like standard price, cost, batch, godown, and identifying items using alias or part number.

Uploaded by

Sanjay Gupta
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views

Understanding Integration Inventory Masters

The document discusses integration of inventory masters in Tally. It describes stock group, stock item, and unit of measure masters. It provides XML request samples to create, alter, and get responses for stock group and stock item masters. It also discusses optional attributes that can be added to a stock item like standard price, cost, batch, godown, and identifying items using alias or part number.

Uploaded by

Sanjay Gupta
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

Login

Home Developer Reference Integration Capabilities Introduction Integration of Inventory Masters

Integration of Inventory Masters


The inventory masters are similar to Accounting Masters. Inventory masters are needed to maintain
the stock details of an organization to realize the availability of stock in hand which is part of the
Balance sheet.

The following table describes the type of inventory masters and its purpose:

Master Information

Stock Group Stock groups holds collection of stock items.

A Stock item is the actual inventory master used in the 


Stock Items
transactions

Stock Items are transacted based on the quantity. The quantity


Unit of Measure
is measured by the Unit of Measure.         

To maintain the availability of stock at various locations. Stock


Locations/Godowns
items are stored under the Godowns

Stock Group
Stock Group in inventory are similar to Groups in Accounting masters. Stock Groups are useful to
classify the Stock Items. The stock group classification can be made based on some common
features such as brand name, product type, quality, etc. Grouping helps to locate Stock Items easily
and report their details in statements. The stock group can have collection of stock groups (sub
stock groups) as well.

The following XML request can be send to Tally from a TPA to create a stock group ‘Electronics’

<ENVELOPE>

<HEADER>
       <TALLYREQUEST>Import Data</TALLYREQUEST>

</HEADER>

<BODY>

<IMPORTDATA>

          <REQUESTDESC>

              <REPORTNAME>All Masters</REPORTNAME>

          </REQUESTDESC>

          <REQUESTDATA>

              <TALLYMESSAGE xmlns:UDF=”TallyUDF”>

                     <STOCKGROUP Action=”Create”>

                        <NAME>Electronics</NAME>

                     </STOCKGROUP>

         </TALLYMESSAGE>

          </REQUESTDATA>

</IMPORTDATA>

</BODY>

</ENVELOPE>

Stock Item
Stock Item refers to the goods that an organization manufacture, trade or maintains. A stock item
can be created by providing a Name in Tally. However, the inventory master UOM (Unit of Measure)
is mandatory to define the quantity. It is good to create the dependent masters of the stock items
before creating a stock item.

The following are the XML tags for creating a stock item:

Tag Data type Is mandatory Description

Name of the stock


NAME String Yes
item

BASEUNITS String No Name of the UOM

Creating a stock item


Stock item can be created in Tally from a third party application by using the below mentioned
sample XML request

<ENVELOPE>

         <HEADER>

              <TALLYREQUEST>Import data</TALLYREQUEST>

              <TYPE>Data</TYPE>

              <ID>All Masters</ID>

          </HEADER>

       <BODY>

              <IMPORTDATA>

                     <REQUESTDESC>

                            <REPORTNAME>All Masters</REPORTNAME>

                     </REQUESTDESC>

                     <REQUESTDATA>

                            <TALLYMESSAGE xmlns:UDF=”TallyUDF”>

                                   <STOCKITEM Action=”Create”>

                                        <NAME>Red Colored Striped Shirt</NAME>

                                         <BASEUNITS>lts</BASEUNITS>

                                          <NAME.LIST TYPE=”String”>

                                              <NAME>Red Colored Striped Shirt</NAME>

                                          </NAME.LIST>

                                   </STOCKITEM>

                            </TALLYMESSAGE>

                     </REQUESTDATA>       

              </IMPORTDATA>

       </BODY>

</ENVELOPE>

To create multiple stock items, the tag set <Stockitem> can be repeated as required.

Altering of stock item


Alteration of stock item can be done using the following tag and value
<STOCKITEM NAME=”Red Colored Striped Shirt” Action=”Alter”>

UOM of a stock item cannot be altered when the stock item used in a transaction or in
a master

XML response for import data request

Tally responses in the following XML format for the XML request:

Tag Description

<RESPONSE> Opening tag of response XML

<CREATED>0</CREATED> Number of masters/transactions created

<ALTERED>0</ALTERED> Number of masters/transactions altered

<DELETED>0</DELETED> Number of masters/transactions deleted

<LASTVCHID>0</LASTVCHID> Master ID of last imported voucher

<LASTMID>0</LASTMID> Last Master ID (it always returns 0)

<COMBINED>0</COMBINED> Number of combined masters

<IGNORED>0</IGNORED> Number of ignored masters

<ERRORS>0</ERRORS> Number of errors while importing the request

<CANCELLED>0</CANCELLED> Number of transactions cancelled

</RESPONSE> Closing tag of response XML

Other optional attributes of a stock item


Depending on the features enabled in Tally, the tags can be added in the XML request.

Example:

Name Usage of the Tag Tag


Standard Selling price To provide standard selling <STANDARDPRICELIST.LIST>
for stock item
     <DATE>14092016</DATE>
 
     <RATE>1145.99</RATE>

</STANDARDPRICELIST.LIST>

<STANDARDCOSTLIST.LIST>

To provide standard cost for       <DATE>12092016</DATE>


Standard Cost price
stock item       <RATE>875.23</RATE>

</STANDARDCOSTLIST.LIST>

To provide stock group name <PARENT>”Electronics”


Parent
to stock item name </PARENT>

<BATCHNAME>

BatchName To provide batch name.        Apr2016

</BATCHNAME>

To provide opening quantity <OPENINGBALANCE>25


Opening balance
for the item </OPENINGBALANCE>

To provide opening rate for <OPENINGRATE>490


Opening Rate
the item </OPENINGRATE>

To provide opening value for <OPENINGVALUE>12250


Opening value
the item </OPENINGVALUE>

Godown Name To provide godown name. <GODOWN>


Incase,  godown feature is
       Main Location
not enabled, the name of
godown can be set to Main </GODOWN>
Location as this is the
default value in Tally

 
Identify/map items pushed by TPA
There may be a need to map the stock items maintained in Tally vs stock items maintained in TPA.
In such case, it is necessary to store a reference value in stock item master. This can be achieved
using the fields Alias or Part number of the stock item. Tally has a capability to provide multiple
Aliases and Part numbers to a master.

Alias
The Alias field gets enabled by the option “Provide aliases along with name?” in Stock item master
configuration.

Tag Data type Is mandatory Description

NAME.LIST
List Yes It is the header of alias list
                  

NAME String Yes Alias name

TPA can store multiple unique aliases using this following XML tags

<NAME.LIST TYPE=”String”>

    <NAME>Red Striped Shirt</NAME>

    <NAME>Stockno12345</NAME>

    <NAME>TPA-Item-001</NAME>

</NAME.LIST>

Part No
The Part No. field gets enabled by the option “Use Part Number for stock items?” in Stock item
master configuration. This field is used to enter the catalogue number.

Tag Data type Is mandatory Description


MAILINGNAME.LIST List Yes It is the header of
part number list

To provide the Part


MAILINGNAME String Yes
number

TPA can store multiple unique Part numbers using this following XML tags

<MAILINGNAME.LIST TYPE=”String”>

       <MAILINGNAME>TPA-Stockno-00001</MAILINGNAME>

       <MAILINGNAME>00001</MAILINGNAME>

</MAILINGNAME.LIST>

Units of Measure
Stock Items are purchased or sold on the basis of quantity. The quantity is measured by Units.
There are two type of UOMs, Simple and Compound.  Simple unit is for basic requirement such as
numbers, meters, kilograms, and pieces. Compound units can be used with the combination of two
UOMs, like 1 box of 10 pieces [1 box = 10 pieces], to measure the stock items in two
aspects                                        

Simple UOM
Simple units are nos, pcs, and so on.

Compound UOM
A Compound unit is a relation between two Simple Units. Hence, before you create a Compound
Unit, ensure that you have already created two Simple Units.

For example, To Create Compound unit – Doz (Dozen) of 12 Nos (Numbers), you have to create two
simple units, Doz (Dozen) and Nos (Numbers) and set the conversion factor as 12.

UOM contains the following fields.

Tag Data type Is mandatory Description

NAME String Yes Name of the UOM.


This would be used
as symbol for unit.

(Applicable for simple


unit. however, Tally
creates the name for
compound unit based
on the conversion
factor of Base unit
and additional unit)

To set the unit as


ISSIMPLEUNIT Logical Yes
simple or compound

Formal name for the


ORIGINALNAME String No
unit

To provide number of
decimal places.
DECIMALPLACES Number No
(Applicable for simple
unit)

To provide the name


of base unit

BASEUNITS String Yes (Applicable for


Compound unit)

To provide the name


of additional unit
ADDITIONALUNITS String Yes
(Applicable for
Compound unit)

To provide the
conversion factor
from base to
CONVERSION Number Yes
additional unit

(Applicable for
Compound unit)

Simple & compound unit creation


XML tags for simple unit and compound unit creation are as follows.

In compound unit creation, <NAME> tag value will not be considered. Tally creates the
name for compound unit based on the conversion factor of Base unit and additional
unit.
 

Simple Unit Compound Unit

<ENVELOPE> <ENVELOPE>

<HEADER> <HEADER>

<TALLYREQUEST>Import <TALLYREQUEST>Import
Data</TALLYREQUEST> Data</TALLYREQUEST>

</HEADER> </HEADER>

<BODY> <BODY>

<IMPORTDATA> <IMPORTDATA>

   <REQUESTDESC>    <REQUESTDESC>

       <REPORTNAME>All Masters              <REPORTNAME>All Masters         


</REPORTNAME>   </REPORTNAME>

   </REQUESTDESC>    </REQUESTDESC>

   <REQUESTDATA>    <REQUESTDATA>

     <TALLYMESSAGE      <TALLYMESSAGE xmlns:UDF=”TallyUDF”>


xmlns:UDF=”TallyUDF”>
         <UNIT Action = “Create”>
       <UNIT Action = “Create”>
         <NAME>Dozen of 12 Pieces</NAME>
       <NAME>Pcs</NAME>
         <ISSIMPLEUNIT>No</ISSIMPLEUNIT>
      
        
<ISSIMPLEUNIT>Yes</ISSIMPLEUNIT>
<ORIGINALNAME>Liters</ORIGINALNAME>
       <ORIGINALNAME>Pieces
        
</ORIGINALNAME>
<DECIMALPLACES>2</DECIMALPLACES>
      
         <BASEUNITS>Doz</BASEUNITS>
<DECIMALPLACES>2</DECIMALPLACES>
<ADDITIONALUNITS>Pcs</ADDITIONALUNITS>
       </UNIT>
         <CONVERSION>12</CONVERSION>
       <UNIT Action = “Create”>
         </UNIT>
       <NAME>Doz</NAME>
       </TALLYMESSAGE>
      
<ISSIMPLEUNIT>Yes</ISSIMPLEUNIT>      </REQUESTDATA>

       <ORIGINALNAME>Dozen    </IMPORTDATA>


</ORIGINALNAME>
</BODY>

</ENVELOPE>
      
<DECIMALPLACES>0</DECIMALPLACES>

       </UNIT>

     </TALLYMESSAGE>

       </REQUESTDATA>

</IMPORTDATA>

</BODY>

</ENVELOPE>

Location/Godown
Location/Godown is the place where Stock Items are stored. You can obtain stock reports for each
godown and account for the movement of stock between locations/godowns. Click here for the
steps to create a Godown, manually in Tally.

The following XML request can be send to Tally from a TPA to create a Location/Godown ‘Factory’

<ENVELOPE>

<HEADER>

       <TALLYREQUEST>Import Data</TALLYREQUEST>

</HEADER>

<BODY>

<IMPORTDATA>

          <REQUESTDESC>

              <REPORTNAME>All Masters</REPORTNAME>

          </REQUESTDESC>

          <REQUESTDATA>

              <TALLYMESSAGE xmlns:UDF=”TallyUDF”>

                     <GODOWN Action=”Create”>

                        <NAME>Factory</NAME>

                     </GODOWN>

              </TALLYMESSAGE>

          </REQUESTDATA>

</IMPORTDATA>
</BODY>

</ENVELOPE>

There is a default godown ‘Main Location’ available in Tally. Incase the feature
‘Maintain multiple godowns?’ is not enabled in Tally, the name of godown can be set to
‘Main Location’, as it is a default value in masters and transactions

Guidelines
The mandatory tags required to import/create the inventory masters in Tally is explained in this
document. To understand other tags, create a sample master with the required features in Tally and
export the same in XML format. Click here for the steps to export the masters from Tally.

Extracting/pulling the Inventory masters from Tally to TPA is covered under the section Export
Reports/Data from Tally.

Related Topics
Understanding Accounting Masters Integration

How to Create Kenya VAT Masters: Stock Group, Items, and…

How to Create Job Work Masters in TallyPrime

VAT Masters, Transactions, and Reports in TallyPrime

How to Configure Masters in TallyPrime (Excise for…

You might also like