Skip to Content
Odoo मेन्यू
  • Sign in
  • मुफ़्त में आज़माएं
  • ऐप्लिकेशन
    फ़ाइनेंस
    • अकाउंटिंग
    • इनवॉइसिंग
    • एक्सपेंस
    • स्प्रेडशीट (बीआई)
    • डॉक्यूमेंट्स
    • साइन
    सेल्स
    • सीआरएम
    • सेल्स
    • पीओएस शॉप
    • पीओएस रेस्टोरेंट
    • सब्सक्रिप्शन
    • रेंटल
    वेबसाइट
    • वेबसाइट बिल्डर
    • ई-कॉमर्स
    • ब्लॉग
    • फ़ोरम
    • लाइव चैट
    • ई-लर्निंग
    सप्लाई चेन
    • इन्वेंट्री
    • मैन्युफ़ैक्चरिंग
    • पीएलएम
    • परचेज़
    • मेंटेनेंस
    • क्वालिटी
    मानव संसाधन
    • कर्मचारी
    • रिक्रूटमेंट
    • टाइम ऑफ़
    • अप्रेज़ल
    • रेफ़रल
    • फ़्लीट
    मार्केटिंग
    • सोशल मार्केटिंग
    • ईमेल मार्केटिंग
    • एसएमएस मार्केटिंग
    • इवेंट
    • मार्केटिंग ऑटोमेशन
    • सर्वे
    सेवाएं
    • प्रोजेक्ट
    • टाइमशीट
    • फ़ील्ड सर्विस
    • हेल्पडेस्क
    • प्लानिंग
    • अपॉइंटमेंट
    प्रॉडक्टिविटी
    • डिस्कस
    • अप्रूवल
    • आईओटी
    • वीओआईपी
    • नॉलेज
    • WhatsApp
    तीसरे पक्ष के ऐप्लिकेशन Odoo स्टूडियो Odoo क्लाउड प्लेटफ़ॉर्म
  • इंडस्ट्री
    रीटेल
    • बुक स्टोर
    • क्लोदिंग स्टोर
    • फ़र्नीचर स्टोर
    • ग्रॉसरी स्टोर
    • हार्डवेयर स्टोर
    • टॉय स्टोर
    Food & Hospitality
    • बार और पब
    • रेस्टोरेंट
    • फ़ास्ट फ़ूड
    • Guest House
    • बेवरिज डिस्ट्रीब्यूटर
    • होटल
    रियल एस्टेट
    • Real Estate Agency
    • आर्किटेक्चर फ़र्म
    • कंसट्रक्शन
    • एस्टेट मैनेजमेंट
    • गार्ड्निंग
    • प्रॉपर्टी ओनर असोसिएशन
    कंसल्टिंग
    • अकाउंटिंग फ़र्म
    • Odoo पार्टनर
    • मार्केटिंग एजेंसी
    • लॉ फ़र्म
    • टैलेंट ऐक्विज़िशन
    • ऑडिट & सर्टिफ़िकेशन
    मैन्युफ़ैक्चरिंग
    • टेक्सटाइल
    • Metal
    • फ़र्नीचर
    • फ़ूड
    • Brewery
    • कॉर्पोरेट गिफ़्ट
    हेल्थ & फिटनेस
    • स्पोर्ट्स क्लब
    • आईवियर स्टोर
    • फिटनेस सेंटर
    • वेलनेस प्रैक्टिशनर
    • फॉर्मेसी
    • हेयर सैलून
    Trades
    • Handyman
    • आईटी हॉर्डवेयर और सपोर्ट
    • Solar Energy Systems
    • Shoe Maker
    • Cleaning Services
    • HVAC Services
    अन्य
    • Nonprofit Organization
    • एन्वायरमेंटल एजेंसी
    • बिलबोर्ड रेंटल
    • फ़ोटोग्राफी
    • बाइक लीजिंग
    • सॉफ़्टवेयर रीसेलर
    Browse all Industries
  • कम्यूनिटी
    सीखें
    • ट्यूटोरियल्स
    • दस्तावेज़
    • सर्टिफ़िकेशन
    • ट्रेनिंग
    • ब्लॉग
    • पॉडकास्ट
    शिक्षा को बढ़ावा दें
    • एजुकेशन प्रोग्राम
    • स्केल अप! बिजनेस गेम
    • Odoo के ऑफ़िस में आएं
    सॉफ़्टवेयर पाएं
    • डाउनलोड
    • वर्शन की तुलना करें
    • रिलीज़
    साथ मिलकर काम करें
    • Github
    • फ़ोरम
    • इवेंट
    • अनुवाद
    • पार्टनर बनें
    • Services for Partners
    • अपना अकाउंटिंग फ़र्म रजिस्टर करें
    सेवाएं पाएं
    • पार्टनर ढूंढें
    • अकाउंटेंट खोजें
    • सलाहकार की मदद लें
    • इम्प्लिमेंटेशन सेवाएं
    • कस्टमर रेफ़रेंस
    • सहायता
    • अपग्रेड
    Github Youtube Twitter Linkedin Instagram Facebook Spotify
    +1 (650) 691-3277
    डेमो देखें
  • कीमत
  • सहायता

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

  • सीआरएम
  • e-Commerce
  • लेखांकन
  • इन्वेंटरी
  • PoS
  • प्रोजेक्ट
  • MRP
All apps
You need to be registered to interact with the community.
All Posts People Badges
टैग (View all)
odoo accounting v14 pos v15
About this forum
You need to be registered to interact with the community.
All Posts People Badges
टैग (View all)
odoo accounting v14 pos v15
About this forum
Help

Apply inventory action usage with JSON-RPC API

Subscribe

Get notified when there's activity on this post

This question has been flagged
actionstockapiwebservicejsonrpc
1 Reply
4497 Views
Avatar
Sébastien Feugère

Hi,

I am porting a script that synchronize our Odoo instance stock data with an internal stock management system. The original script used the XML-RPC​ interface and worked fine. We use the Perl programming language, and our ageing XML-RPC​ client made us decide to move to JSON-RPC: we guessed that it would be more reliable and that we would be able to find more code examples (porting from Python to Perl is not a problem). Since the Odoo UI also use the JSON-RPC​ interface it looked like a quality improvement to us, so we made the switch.  ​

I'll post some Perl code and the generated JSON here, but please consider that as pseudocode, as it's the same as Python in functionalities. If you don't know Perl, don't worry: the syntax is similar to PHP. My biggest concerns are:

  • which method to use (especially for the action_apply_inventory​​ call)
  • what parameters to pass
  • in what data structures those parameters should be stored

This is what I do for a specific Product id​​. It's the same method as what is described in this post. 

First, we create a new entry through the stock_quant​​ model​:

my %params = (
args => [
# It prepares the login params list
$self->_aggregate_auth_params(),
'stock.quant',
'create', {
location_id => $location_id,
product_id  => $odoo_product_id,
in_date     => $odoo_now,
owner_id   => $owner_id,
quantity    => $new_quantity,
inventory_date      => $odoo_now,
    },
],
service => 'object',
method        => 'execute',
);

my ($fail, $res, $err) = $self->object_service->call_named(
'call',
%params,
);

$self->_check_errors({ err => $err, res => $res, fail => $fail });


Generated JSON:

{
"method": "call",
"jsonrpc": "2.0",
"params": {
"args": [
"CENSORED_DATABASE",
666,
"CENSORED_PASSWORD",
"stock.quant",
"create",
{
"quantity": 20,
"inventory_date": "2024-08-29 13:47:40",
"in_date": "2024-08-29 13:47:40",
"product_id": 4337,
"location_id": 76
}
],
"service":"object",
"method":"execute
}     


After running that, $res​​ contains the id​ of the stock_quant​​ added item. I checked the stock_quant​​ table: it does have a new entry with the information stored. It worked!

Something to notice is that after some time (a couple of hours), the entry is purged and deleted from the database: obviously it's marked as not applied and is removed by a cron.

Then, we proceed to the action_apply_inventory​​ method call. This one is not conclusive:

  

my %paramss = (
  args => [
    $self->_aggregate_auth_params(),
    'stock_quant',
    'action_apply_inventory',
    ["" . $new_stock_quant_id]
  ],
# Also considered 'action' here
  service       => 'object',
# Also considered 'action_execute' here
  method        => 'execute',
);

my ($faill, $ress, $errr) = $self->object_service->call_named(
  'call',
  %paramss,
);

$self->_check_errors({ err => $errr, res => $ress, fail => $faill });


Generated JSON:

{
"id":0,
"params": {
"args" [
"CENSORED_DATABASE",
666,
"CENSORED_PASSWORD",
"stock.quant",
"action_apply_inventory",
["14505"]
],
"method": "execute",
"service": "object"
},
"method": "call",
"jsonrpc": "2.0"
}                                                                                                                             

The following exception is returned:

{
  code      200,                                                                        data {
arguments [
[0] "Record does not exist or has been deleted. (Record: stock.quant('14505',), User: 666)"
],
context     {},
debug       "Traceback (most recent call last):
File \"/usr/lib/python3/dist-packages/odoo/http.py\", line 1765, in _serve_db
return service_model.retrying(self._serve_ir_http, self.env)
File \"/usr/lib/python3/dist-packages/odoo/service/model.py\", line 133, in retrying
result = func()
File \"/usr/lib/python3/dist-packages/odoo/http.py\", line 1792, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File \"/usr/lib/python3/dist-packages/odoo/http.py\", line 1996, in dispatch
result = self.request.registry['ir.http']._dispatch(endpoint)
File \"/usr/lib/python3/dist-packages/odoo/addons/website/models/ir_http.py\", line 235, in _dispatch
response = super()._dispatch(endpoint)
File \"/usr/lib/python3/dist-packages/odoo/addons/base/models/ir_http.py\", line 222, in _dispatch
result = endpoint(**request.params)
File \"/usr/lib/python3/dist-packages/odoo/http.py\", line 722, in route_wrapper
result = endpoint(self, *args, **params_ok)
File \"/usr/lib/python3/dist-packages/odoo/addons/base/controllers/rpc.py\", line 155, in jsonrpc
return dispatch_rpc(service, method, args)
File \"/usr/lib/python3/dist-packages/odoo/http.py\", line 388, in dispatch_rpc
return dispatch(method, params)
File \"/usr/lib/python3/dist-packages/odoo/service/model.py\", line 35, in dispatch
res = execute(db, uid, *params[3:])
File \"/usr/lib/python3/dist-packages/odoo/service/model.py\", line 65, in execute
  res = execute_cr(cr, uid, obj, method, *args, **kw)
File \"/usr/lib/python3/dist-packages/odoo/service/model.py\", line 50, in execute_cr
  result = retrying(partial(odoo.api.call_kw, recs, method, args, kw), env)
File \"/usr/lib/python3/dist-packages/odoo/service/model.py\", line 133, in retrying
  result = func()
File \"/usr/lib/python3/dist-packages/odoo/api.py\", line 468, in call_kw
  result = _call_kw_multi(method, model, args, kwargs)
File \"/usr/lib/python3/dist-packages/odoo/api.py\", line 453, in _call_kw_multi
  result = method(recs, *args, **kwargs)
File \"/usr/lib/python3/dist-packages/odoo/addons/stock/models/stock_quant.py\", line 413, in action_apply_inventory
  rounding = quant.product_uom_id.rounding
File \"/usr/lib/python3/dist-packages/odoo/fields.py\", line 2895, in __get__
  return super().__get__(records, owner)
File \"/usr/lib/python3/dist-packages/odoo/fields.py\", line 1209, in __get__
  self.compute_value(record)
File \"/usr/lib/python3/dist-packages/odoo/fields.py\", line 1389, in compute_value
  records._compute_field_value(self)
File \"/usr/lib/python3/dist-packages/odoo/models.py\", line 4869, in _compute_field_value
  fields.determine(field.compute, self)
File \"/usr/lib/python3/dist-packages/odoo/fields.py\", line 105, in determine
  return needle(records, *args)
File \"/usr/lib/python3/dist-packages/odoo/fields.py\", line 695, in _compute_related
  values = [first(value[name]) for value in values]
File \"/usr/lib/python3/dist-packages/odoo/fields.py\", line 695, in
values = [first(value[name]) for value in values]
File \"/usr/lib/python3/dist-packages/odoo/models.py\", line 6597, in __getitem__
  return self._fields[key].__get__(self, self.env.registry[self._name])
File \"/usr/lib/python3/dist-packages/odoo/fields.py\", line 2895, in __get__
  return super().__get__(records, owner)
File \"/usr/lib/python3/dist-packages/odoo/fields.py\", line 1188, in __get__
raise MissingError(\"\n\".join([
odoo.exceptions.MissingError: Record does not exist or has been deleted.
  (Record: stock.quant('14505',), User: 666)


I get the exceptions from the JSON-RPC API so forgive me if it's badly formatted.

At the time of execution, the 14505​​ stock_quant​ entry does exist, so I don't understand: I guess it's marked as in a specific status, but the entry does exist for sure in the database...​

Yesterday I posted a similar question.  The $params​ data structure were wrong during the JSON-RPC POST query: the answer from one of the community members was very useful and unblocked the situation quickly. I am pretty sure I am doing something silly.


Other paths I followed

  • ​inventory_quantity_auto_apply​​ : I did tests with that, but couldn't obtain any interesting results
  • tried to use action_set_inventory_quantity​​

Thanks!​

0
Avatar
Discard
Adrià Navarro

What version of Odoo is the database?

Sébastien Feugère
Author

This is Odoo v17.

Sébastien Feugère
Author

17.0+e-20240418 (Enterprise Edition)

Gombár Tamásné e.v.

Hi Sébastien

Are you sure with that concept ?  inventory_diff_quantity is for the purpose as :


/// <summary>

/// inventory_diff_quantity - float  <br />

/// Required: False, Readonly: True, Store: True, Sortable: True <br />

/// Help: Indicates the gap between the product's theoretical quantity and its counted quantity. <br />

/// </summary>


Avatar
Sébastien Feugère
Author Best Answer

Answering my own question. Apparently, the whole methodology was wrong.

The right way to do that is to:

  • update an existing stock.quant​ entry with the write​ method and set the inventory_diff_quantity​ field
  • call action_apply_inventory on the same stock.quant to update the quantities and set the inventory history (stock.move.line​): note this is an automatic process, you don't have to set stock.move.line​ manually.


0
Avatar
Discard
Enjoying the discussion? Don't just read, join in!

Create an account today to enjoy exclusive features and engage with our awesome community!

Sign up
Related Posts Replies Views Activity
Odoo JSON-RPC API
api jsonrpc
Avatar
0
फ़र॰ 25
2827
What is the API endpoint for JSON-RPC?
api jsonrpc
Avatar
0
अक्तू॰ 20
5756
jsonrpc bulk write
api odoo jsonrpc
Avatar
Avatar
1
अप्रैल 25
1844
Do the JSON-RPC external API support the IN operator ?
api operators jsonrpc
Avatar
2
अग॰ 24
36
How to set limit and offset in jsonrpc api?
api jsonrpc odoo12
Avatar
Avatar
Avatar
2
मई 23
11817
कम्यूनिटी
  • ट्यूटोरियल्स
  • दस्तावेज़
  • फ़ोरम
ओपन सोर्स
  • डाउनलोड
  • Github
  • रनबॉट
  • अनुवाद
सेवाएं
  • Odoo.sh Hosting
  • सहायता
  • अपग्रेड
  • कस्टम डेवलपमेंट्स
  • शिक्षा
  • अकाउंटेंट खोजें
  • पार्टनर ढूंढें
  • पार्टनर बनें
हमारे बारे में
  • हमारी कंपनी
  • ब्रांड ऐसेट
  • संपर्क करें
  • नौकरियां
  • इवेंट
  • पॉडकास्ट
  • ब्लॉग
  • ग्राहक
  • लीगल • गोपनीयता
  • सुरक्षा
الْعَرَبيّة Català 简体中文 繁體中文 (台灣) Čeština Dansk Nederlands English Suomi Français Deutsch हिंदी Bahasa Indonesia Italiano 日本語 한국어 (KR) Lietuvių kalba Język polski Português (BR) română русский язык Slovenský jazyk slovenščina Español (América Latina) Español ภาษาไทย Türkçe українська Tiếng Việt

Odoo, बिज़नेस से जुड़े ऐप्लिकेशन का एक कलेक्शन है जो ओपन सोर्स पर आधारित है. इसमें आपकी कंपनी की हर ज़रूरत के लिए ऐप्लिकेशन हैं. जैसे, सीआरएम, ई-कॉमर्स, अकाउंटिंग, इन्वेंट्री, पॉइंट ऑफ़ सेल, प्रोजेक्ट मैनेजमेंट वगैरह.

Odoo की सबसे बड़ी खासियत है कि यह इस्तेमाल करने में बहुत आसान है और यह पूरी तरह से इंटिग्रेट किया हुआ है.

Website made with

Odoo Experience on YouTube

1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.

Live support on Youtube
Watch now