Purchase request from production order - tryton

I've just started testing Tryton ERP with regards to production planning, and I don't get automatic procurement working;
I define "Part A" with a vendor and price.
I then define "Product B" with a BoM of 1 * Part A.
Now when I create a production order, I'd expect a purchase request for Part A at some point, but I don't.
I tried installing the "Sale Supply" module, but that only seem to work on actual sales orders. I want to create production orders without actual sales yet.
Is this possible? It seems like a really easy thing to do...

Related

Intent Data - How exactly are traceable urls used to track interest in b2b topics?

I've been doing some research on intent data and I have some technical questions, especially about how two businesses might be collecting "contact level" i.e. personally identified web traffic details without using third-party cookies.
Some quick background: Most of the large providers of intent data (bombora, the big willow/aberdeen/Spiceworks Ziff Davis, Tech Target etc.) offer "account" based intent data - essentially when users visit websites in their network, they do a reverse IP addresses lookup, match them to know IP addresses of large companies (usually companies with at least 250 employees) and note what topics are "surging" - aka showing unusual traffic on a given week. This largely makes sense to me. I'm assuming that when a visitor shows up at your site, google analytics and similar tools can tell you what google search keywords were used to arrive at your site, and that's how they can say things like - we can "observe intent signals across an unlimited number of contextual keyword categories, allowing you to customize your keywords and layer these insights onto your campaigns for optimal performance." Third party cookies, and data from DSP's (demand side platform's enabling ad buyers to buy ads across many platforms) are also involved in providing data, those these will be less useful sources of data after google sunset's third party cookies on Chrome.
Two providers - intentdata.io, and intentflow.com are offering contact level intent data. You can imagine why that would be of interest - if the director of sales is interested in your sales SaaS tool, you have a better idea of how qualified that lead is and who to reach out to. Only one of the two providers is specific about what exactly they're collecting - i.e. what "intent" they are capturing and how they're collecting it.
Intentdata.io:
Intentdata.io looks like a tiny company (two employees on LinkedIn). The most specific statement I've found about what their data is was in an Impact+ podcast interview - Ed, the CRO at intentdata.io, mentions that the data is analogous to commenting on a Forbes article or a conversation on LinkedIn. But he's clear - "that's just an analogy." They also say elsewhere that the data they provide mentions specifically what action the contact took that landed them in the provided data.
Ed from intentdata.io is also asked about GDPR compliance in his Impact+ interview - he basically says, some lawyers will disagree but he believes their data to be GDPR compliant, and it is in use by some firms in the EU. He does mention though that some firms have asked them to exclude certain columns from the data, like email addresses.
Edit: Found a bit more on intentdata.io - looks like they build a custom setup to pull "intent" data for each customer - they don't have a database monitoring company interaction with content across social media and b2b sites, instead you provide them with "lists (names and URLs) of customers, competitors, influencers, events, target accounts and key terms that would indicate intent at different stages in the buying journey. Pull together important hashtags, details on your ideal buyer (job titles, functions, seniority) and firmographics (size, industry, location)" - then they create a custom "algorithm" from this info, and they iterate on that "algorithm" a little bit over time.
They also make this statement on their site: "IntentData.io's data is collected from observing public actions that users are taking around the web. That means that first, we observe action (not reading, searching, browsing, being shown an ad, etc.) which we believe is a more concrete manifestation of intent. Second, people are taking these actions publicly for the world to see. We do not use any cookies, bidstream data or reverse IP lookups."
Finally one piece of their sales collateral asks: What ad budget do you have for PPC nurturing ads? So their may be some targeted PPC ads involved in the "algorithm."
Edit 2: Their sales collateral also states that they use "a third-party intent data methodology that uses multi-variable linear regression analysis to correlate observed actions with a specific contact. This is the method that the LeadSift engine of IntentData.io data uses."
Intentflow.com:
Intentflow.com seems like the sketchier of the two providers if I'm honest. They provide a video walkthrough of how they get their data at intentflow.com/thesis - but I'm not following how using "traceable urls" with no cookies involved, could give you contact level information. They also say they lookup what the most popular articles/pages are for 5k to 40k unique keywords or phrases that are related to 10-50 keywords or phrases you give them to target. And they use "traceable urls" to track who visits those sites. Again - no cookies involved. Supposedly fully compliant at least with US laws. They don't provide data for the EU "by design" so presumably they're not GDPR compliant? They also claim they can identify the individuals who are visiting your website, again using "traceable urls" - it seems clear from the pitch that you're asked to reach out to your backlink providers around the web to use this traceable url.
I've seen an interview where a rep from Bombora says they tried for a while to do contact level intent data and it wasn't very useful - and it wasn't really doable in a compliant way. Ed seems to be aware they've said that publicly, and he says "that's just not true."
So what's going on here? How exactly are these two small firms getting contact level intent data? Do you think they're doing it in a compliant way?
Got more information:
Intentdata.io use public comments, likes, shares etc. on blogs, social posts via web crawling and scraping for events, influencers, hashtags, articles etc. that the customer deems worth tracking. They do some work to try and connect the commenters with an identifiable contact. They bill on a quarterly basis for this.
Intentflow.com doesn't seem to use "traceable urls" at all. They take bidstream data, and identify the individual visitors via an "identity graph." They provide a minimum of 5k contacts per month at $2 per contact, making their data very expensive ($120k+ per year). You can't get lower than however many contacts their system spits out per month so it seems like there's not a good firm limit on what you will be charged. They say they can identify ~70% of web traffic, and they only provide data on US site visitors. Each row of their output would include not just the contact, but the site that contact was shown an ad on. Definitely interesting data - but I'm guessing they will be very affected by upcoming changes to third party cookies, privacy laws, etc.

Google analytics - last tracking causes previous tracking records to change

We set up enhanced ecommerce tracking for our shop where we among other things track payment method for each order. In our shop, as a customer, I completed two orders with visa payment option, which can be seen in GA:
Two orders created with visa option, all fine (don't mind the duplicate records for now).
But then I create a third order in our shop with sofort banking (just another payment option) and look how things change:
All order payment methods were changed to sofort banking. Of course I've tried hard reload to see if caching is not involved and even waited a day to see if it changes anything but no, the records stay with sofort banking.
Now we come to the second problem - the duplication. For some reason when I filter with Secondary dimension: Checkout Options (as can be seen on the pics) I get for each tracked order 2 records in the table. Those two problems might be somehow connected.
The question is: Does anyone have an experience with this and knows where the problem might be? If you need additional info please let me know, as of now I don't know in which direction to elaborate.

About the infomation we can confirm by Google Analytics

In my EC site, product data have the information below.
 ・Brand
 ・category
 ・Sub-category
 ・Division
 ・Style
 ・Color-way
 ・Gender
 ・Season
Can we send and confirm the information in Google Analytics?
I searched in help, and think only we can send Brand,Category, Sub-category.
https://developers.google.com/analytics/devguides/collection/analyticsjs/ecommerce
BestRegards,
Kazuhito
Check "Enhanced Ecommerce" for a few more options: https://developers.google.com/analytics/devguides/collection/analyticsjs/enhanced-ecommerce
It's important to understand, that there are multiple sections. Dependent of what you want to do, you've got other limits. If you want to send "Product Data", then your limits are: id, name, brand, category, variant, price, quantity, coupon, position
As I was in my past also in your situations and at least in my unlucky situation the reality was, that divisions could change... So I would recommend you to use what you have and ensure that you send the SKU. Then you can export GA data and export the actual data of your e-commerce system and map the two data parts over the unique identifier SKU together (VLOOKUP and so on).
If you want everything in GA you also can extend the available fields with any field you want to have over custom-dimensions/custom-metrics: https://support.google.com/analytics/answer/2709828?hl=en
If you're going for custom-dimensions/custom-metrics I really can recommend first building a concept and really think also about the future. Otherwise you will regret it.
I hope this helped :)

Database relations query

I have two database tables
this is a sample database of a Ticketing system.
Figure 1: Sample table of air ticket.
Figure 2: Sample table of tax.
Requirement:
When ticket is made from the interface, it has multiple taxes of different names every time.
How can I store this information i.e. 'n' number of taxes for each ticket with different names every time.
I have tried to make many to many relationship but the problem is:
For each ticket if the tax is not setup, then need to add the tax first.
Any optimal solution for this?
"the problem is: For each ticket if the tax is not setup, then need to
add the tax first."
This is not a real-life problem. In real life governments declare taxes well in advance of collecting them, This gives organizations sufficient time to amend their systems which need to handle taxes. Tax is never a surprise.
"But this is very tiring solution for the end user.... to make bunch
of tax setup for each ticket"
This sort of thing is reference data, and is the duty of the system developer (hint: that's you) to populate the reference data tables. Or at least provide a screen where the user can create or amend various taxes. This is a different function from defining a ticket type.
The Ticket Creation screen should have a drop-down list (or similar widget) displaying all the existing taxes, which allows the user to pick the relevant one(s). If you reall think it's necessary you can include a link to the Create Tax screen, but that really is a very confusing workflow.
If the commentators are correct, and this is a ticket purchasing function, then your design is seriously wrong. Sales taxes must be included automatically to the cost of the purcahse as part of the transaction. Otherwise nobody would pay any tax.

Obscuring published items from the publishing queue

I have a Tridion implementation that is, in essence, multi-tennent. Different interest groups use the same environment. Security takes care that users cannot see publications/content from groups they are not permitted to see. However, in the publishing queue, all users can see the title of items that are in the queue; they cannot open the item but they can see the title (e.g. "Our company releases sky high profits!")
For sensitivity reasons I would like hide the title of the item when the queue list is loaded according to the scoped publications of the user viewing the queue. So, for example, If I am only able to work in publications b & c but not in a & d when the queue loads, I can see the titles of content coming from b & c but not a & d. I will see something like "Item from publication D".
Is this straight-forward to do with an extension and does any one have some examples of how to do this?
The logic is the most complicated thing about it. You need to work out what the user can see or not.
This is a good candidate for a Data Extender to the CME. Filter out the items on the server before the response is returned. There is a section of the online documentation dedicated to the topic, so that is hopefully enough to get you started.
A crafty person would still be able to access the information by directly querying the API / Core Service, but I imagine that is not a high priority in this case.

Resources