When GP sales order is created via econnect it automatically takes the next master number.
Is it possible to specify a master number explicitly in the xml schema , so that a GP sales order is created with specified master number.
Please help me.
Next Master number is taken from SOP set up (table SOP40100). I don't know why you want change this number?
If you want to cange the master number,go SOP set up and change the next master number. I think it is not possible to specify a master number explicitly in the xml schema.
Actually i have created a sale sorder ORD2247 in GP which has the master number 560(Eg)
I am trying to create a Fulfilment order FULORD5567 through econnect for ORD2247. At this point the next master number 561 is used for FULORD5567. But i want 560 to be the master number for FULORD5567.
Help me for this scenario.
I am not wrong, You are going to transfer the Order to Fulfilment order.
I think you have used the taSopHdrIvcInsert schema(eConnect not contain any separate schema for SOP transfer).
If you used this schema , MSTRNUMB element is available for the Master Number.
Yes, I am trying to pass master number explicitly for <MSTRNUMB> node of taSopHdrIvcInsert schema.
The scenario is to create a FO using Econnect :
Order number ORDST2227 with master number: 560
The FO must be created such that the orignumb as ORD2227 and mstrnumb as 560.
<ORIGNUMB>ORD2227</ORIGNUMB> is of no issue.
Problem is with MSTRNUMB.- I could not explicitly assign, it automatically takes the next number 561.
How can i achieve this using Econnect?
I'm facing the same issue... can you please share the idea on how it is resolved?
Are you able to restrict the new master number creation?
Thanks in advance.
The Master Number is a unique, unchanging number assigned to a sales TRANSACTION. Each and every document in the transaction has the same master number. Sales order documents in transactions are linked in several manners, one of which is the Master Number. There is also the originating document number chain to consider.
Creating a new document with the same Master Number as another document assumes you are transferring the transaction from the original document to the new document. You need to update the line items of the original document to show them transferred (ordered, invoiced, backordered, etc), reduce the remaining open order amount in the header of the original, move items to history, et cetera, et cetera, et cetera.
Why not just transfer the document using GP Code?
PS You CANNOT create a NEW transaction with the same master number. And, you are asking for problems if you have multiple master number ranges when the ranges eventually overlap.
Richard L. Whaley Author, Publisher, Consultant
Enhancing your Dynamics Knowledge!
Richard is correct! The master number was clearly designed to be an application internal control number to chain a complete SOP Transaction flow, this is, from a quote, all the way to an invoice, excluding returns (you cannot link a return to a sales invoice, hence returns have their own master numbers). I actually don't even understand why it is exposed to the interface or why users are allowed to modify it. It should be an internal system control.
MG.-Mariano Gomez, MIS, MVP, MCP, PMP IntellPartners, LLC Blog: http://dynamicsgpblogster.blogspot.com
I print the master number on all sales transactions. It allows a user researching an issue to have a starting point that will expose the entire transaction rather than looking at an invoice and then the next document and then the next one and the next one........(shades of National Treasure!)
The scenario is to create a FO using Econnect.
I am trying to pass master number explicitly for <MSTRNUMB> node of taSopHdrIvcInsert schema, with the master number value of its order, which is throwing error.
Problem is with MSTRNUMB.- I could not explicitly assign.
Removal of this node creates a new master number.
Whats an 'FO'.
Consider the following: Will the master number not default? Why not just accept the default? If its a new transaction then you get a new Master Number, if its an existing transaction being modified / updated / moved along, then the existing master number will default and should be used. Either way, you don't need to worry about it. You should not be trying to interfere with this field (even if it looks like eConnect lets you).
With the above in mind, do you still have a problem? or have I missed something?
Ian Stewart MVP - International support for Dynamics GP. Local knowledge, local timelines, local GP talent. Genesys Financial Systems (Europe) Microsoft Gold Certified Partner http://dynamicsgp.wordpress.com/
Thanks for the response.
I'm trying to use the same master number of order to an FO.
Please note: FO is created using eConnect. eConnect does not allow to pass the exisitng master number, as it is not supported for transfer.
In this case, the FO creation, creates a new master number. I want this to not happen, as the FO needs to use the same master number of the order. Is there any way to restrict it?
YOU DO NOT need to mess with the master number. If you start to selectively assign which documents get which master number you will end up with corrupted data. If you want something to relate both documents, use some sort of user defined field.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13