You’re offline. This is a read only version of the page.
65
We are trying to create a process to automate the creation of PO from a Sales Order.
We are trying to use taSopToPopLink but unsuccessful so far.
The follow eConnect call comes back with no error, any guidance will be helpful.
<eConnect xmlns:dt="urn:schemas-microsoft-com:datatypes">
<taSopToPopLink>
<SOPTYPE>2</SOPTYPE>
<SOPNUMBE>000002</SOPNUMBE>
</taSopToPopLink>
</eConnect>
Thanks
RG
*This post is locked for comments
Finally found the issue, one step forward
taSOPtoPOPLink actually does create the PO documents. The issue that I found was that it was expecting <SOPtoPOPTransactionType> element in it. The following did work and I can see the PO created and POP10100 and POP10110 tables.
It should be as -
<eConnect xmlns:dt="urn:schemas-microsoft-com:datatypes">
<SOPtoPOPTransactionType>
<taSopToPopLink>
<SOPTYPE>2</SOPTYPE>
<SOPNUMBE>000002</SOPNUMBE>
</taSopToPopLink>
</SOPtoPOPTransactionType>
</eConnect>
Thanks all for looking at it.
Rajeev Gupta
www.mydbsync.com
The Schema you are using creats a link between an existing POP document and an existing SOP document. It creates a commitment whereby a POP document is committed to a SOP document.
For this schema to run properly, both documents have to exist already.
This schema will not auto create a POP document from a SOP document.
As far as I know there is no Schema to achieve this. You could however just run the POP create schema off the same data that you use to create the SOP document, and then use the schema above to link them.
(note that the schema to remove this link is situated in the POP schemas).
Ian.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (