DMT Transfer of PO

You will need to unapproved all POs and after the import run a DMT to approve the PO.  If you are bringing over closed POs and or closed lines on open POs you will need to re-open and close once the DMT is complete. 

The DMT tool is used to make sure you do not circumvent the system. 

Sent from my iPad

On Mar 21, 2014, at 6:29 PM, <marcus@...> wrote:

 

<div id="ygrps-yiv-85045209ygrp-text">
  
  
  <p>Hi fellow E9 Users,</p><div><br></div><div>My company is upgrading from Vantage to E9 and we are in the process of importing data into our pilot system for CRP. We have successfully transferred Customer, Supplier, Part &amp; MOM, Quote, Order, Job, and RMA&#39;s, but we are having major difficulties with transferring in all our PO&#39;s. We are using the DMT tool and we keep getting errors ever time we try to process our data. When we upload the PO Header table we get the following errors:</div><div><br></div><div>Table: POHeader Msg: Purchase order 130889 is approved, cannot update.<br></div><div>Table: POHeader Msg: Purchase order 131201 is closed, cannot update.<br></div><div>Table: PODetail Msg: The PO had been approved. &nbsp;Changes not allowed.<br></div><div>Table: &nbsp;Msg: A valid part is required<br></div><div>Table: POHeader Msg: PO is not approved and cannot be flagged as Ready To Print.<br></div><div><br></div><div>We were under the impression that the DMT tool could circumvent the restrictions of updating PO&#39;s regardless of whether they are approved/closed/void. Has anyone else had a problem uploading PO&#39;s?</div><div><br></div><div>The current fields we are trying to import are as follows:</div><div>Company</div><div>OpenOrder</div><div>VoidOrder</div><div>PONum</div><div>EntryPerson</div><div>FOB</div><div>ShipViaCode</div><div>TermsCode</div><div>BuyerID</div><div>VendorNum</div><div>OrderHeld</div><div>ReadyToPrint</div><div>PrintAs</div><div>Approve</div><div>ApprovalStatus</div><div>ApprovedAmount</div><div>OrderNum</div><div>PODetail#Company</div><div>PODetail#OpenLine</div><div>PODetail#VoidLine<br></div><div>PODetail#PONum<br></div><div>PODetail#POLine<br></div><div>PODetail#LineDesc<br></div><div>PODetail#IUM<br></div><div>PODetail#UnitCost<br></div><div>PODetail#DocUnitCost<br></div><div>PODetail#Taxable<br></div><div>PODetail#PUM<br></div><div>PODetail#CostPerCode<br></div><div>PODetail#PartNum<br></div><div>PODetail#VenPartNum<br></div><div>PODetail#RevisionNum<br></div><div>PODetail#RcvInspectionReq<br></div><div>PODetail#VendorNum<br></div><div>PODetail#Confirmed<br></div><div>PODetail#ConfirmedDate<br></div><div>PODetail#OrderNum<br></div><div>PODetail#OrderLine<br></div><div>PODetail#CalcOurQty<br></div><div>PORel#Company<br></div><div>PORel#PONum<br></div><div>PORel#POLine<br></div><div>PORel#PORelNum<br></div><div>PORel#OpenRelease<br></div><div>PORel#VoidRelease<br></div><div>PORel#DueDate<br></div><div>PORel#XRelQty<br></div><div>PORel#PurchasingFactor<br></div><div>PORel#RelQty<br></div><div>PORel#JobNum<br></div><div>PORel#AssemblySeq<br></div><div>PORel#JobSeqType<br></div><div>PORel#JobSeq<br></div><div>PORel#WarehouseCode<br></div><div>PORel#ReceivedQty<br></div><div>PORel#ExpOverride<br></div><div>PORel#Plant<br></div><div>PORel#PromiseDt<br></div><div>PORel#ProjectID<br></div><div>PORel#Comfirmed<br></div><div>PORel#ConfirmVia<br></div><div>PORel#OrderNum<br></div><div>PORel#OrderLine<br></div><div>PORel#OrderRelNum<br></div><div>PORel#ShippedQty<br></div><div><br></div><div>Are there any fields you suggest we include/exclude to/from this list? Any help would be much appreciated!</div><div><br></div><div>Thanks,</div><div>-Marcus</div><div><br></div><div><br></div><div><br></div><div><br></div><p></p>

</div>
Hi fellow E9 Users,

My company is upgrading from Vantage to E9 and we are in the process of importing data into our pilot system for CRP. We have successfully transferred Customer, Supplier, Part & MOM, Quote, Order, Job, and RMA's, but we are having major difficulties with transferring in all our PO's. We are using the DMT tool and we keep getting errors ever time we try to process our data. When we upload the PO Header table we get the following errors:

Table: POHeader Msg: Purchase order 130889 is approved, cannot update.
Table: POHeader Msg: Purchase order 131201 is closed, cannot update.
Table: PODetail Msg: The PO had been approved.  Changes not allowed.
Table:  Msg: A valid part is required
Table: POHeader Msg: PO is not approved and cannot be flagged as Ready To Print.

We were under the impression that the DMT tool could circumvent the restrictions of updating PO's regardless of whether they are approved/closed/void. Has anyone else had a problem uploading PO's?

The current fields we are trying to import are as follows:
Company
OpenOrder
VoidOrder
PONum
EntryPerson
FOB
ShipViaCode
TermsCode
BuyerID
VendorNum
OrderHeld
ReadyToPrint
PrintAs
Approve
ApprovalStatus
ApprovedAmount
OrderNum
PODetail#Company
PODetail#OpenLine
PODetail#VoidLine
PODetail#PONum
PODetail#POLine
PODetail#LineDesc
PODetail#IUM
PODetail#UnitCost
PODetail#DocUnitCost
PODetail#Taxable
PODetail#PUM
PODetail#CostPerCode
PODetail#PartNum
PODetail#VenPartNum
PODetail#RevisionNum
PODetail#RcvInspectionReq
PODetail#VendorNum
PODetail#Confirmed
PODetail#ConfirmedDate
PODetail#OrderNum
PODetail#OrderLine
PODetail#CalcOurQty
PORel#Company
PORel#PONum
PORel#POLine
PORel#PORelNum
PORel#OpenRelease
PORel#VoidRelease
PORel#DueDate
PORel#XRelQty
PORel#PurchasingFactor
PORel#RelQty
PORel#JobNum
PORel#AssemblySeq
PORel#JobSeqType
PORel#JobSeq
PORel#WarehouseCode
PORel#ReceivedQty
PORel#ExpOverride
PORel#Plant
PORel#PromiseDt
PORel#ProjectID
PORel#Comfirmed
PORel#ConfirmVia
PORel#OrderNum
PORel#OrderLine
PORel#OrderRelNum
PORel#ShippedQty

Are there any fields you suggest we include/exclude to/from this list? Any help would be much appreciated!

Thanks,
-Marcus




DMT follows all business rules. When I was taught how to troubleshoot a DMT run, the process was to attempt the same update in the client and make note of any requirements that you will need to meet in the upload file.

 

I first uploaded Headers with Approve set to false and then the same set with Approve true and ApprovalStatus = A when done.                                                                                                                                                                                                                                            

 

I did not use PO Combined when I did mine, but I would assume you would still do combined as unapproved and then a header file to approve them all.

 

Good Luck

 

Greg Payne

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of marcus@...
Sent: Friday, March 21, 2014 6:30 PM
To: vantage@yahoogroups.com
Subject: [Vantage] DMT Transfer of PO

 

 

Hi fellow E9 Users,

 

My company is upgrading from Vantage to E9 and we are in the process of importing data into our pilot system for CRP. We have successfully transferred Customer, Supplier, Part & MOM, Quote, Order, Job, and RMA's, but we are having major difficulties with transferring in all our PO's. We are using the DMT tool and we keep getting errors ever time we try to process our data. When we upload the PO Header table we get the following errors:

 

Table: POHeader Msg: Purchase order 130889 is approved, cannot update.

Table: POHeader Msg: Purchase order 131201 is closed, cannot update.

Table: PODetail Msg: The PO had been approved.  Changes not allowed.

Table:  Msg: A valid part is required

Table: POHeader Msg: PO is not approved and cannot be flagged as Ready To Print.

 

We were under the impression that the DMT tool could circumvent the restrictions of updating PO's regardless of whether they are approved/closed/void. Has anyone else had a problem uploading PO's?

 

The current fields we are trying to import are as follows:

Company

OpenOrder

VoidOrder

PONum

EntryPerson

FOB

ShipViaCode

TermsCode

BuyerID

VendorNum

OrderHeld

ReadyToPrint

PrintAs

Approve

ApprovalStatus

ApprovedAmount

OrderNum

PODetail#Company

PODetail#OpenLine

PODetail#VoidLine

PODetail#PONum

PODetail#POLine

PODetail#LineDesc

PODetail#IUM

PODetail#UnitCost

PODetail#DocUnitCost

PODetail#Taxable

PODetail#PUM

PODetail#CostPerCode

PODetail#PartNum

PODetail#VenPartNum

PODetail#RevisionNum

PODetail#RcvInspectionReq

PODetail#VendorNum

PODetail#Confirmed

PODetail#ConfirmedDate

PODetail#OrderNum

PODetail#OrderLine

PODetail#CalcOurQty

PORel#Company

PORel#PONum

PORel#POLine

PORel#PORelNum

PORel#OpenRelease

PORel#VoidRelease

PORel#DueDate

PORel#XRelQty

PORel#PurchasingFactor

PORel#RelQty

PORel#JobNum

PORel#AssemblySeq

PORel#JobSeqType

PORel#JobSeq

PORel#WarehouseCode

PORel#ReceivedQty

PORel#ExpOverride

PORel#Plant

PORel#PromiseDt

PORel#ProjectID

PORel#Comfirmed

PORel#ConfirmVia

PORel#OrderNum

PORel#OrderLine

PORel#OrderRelNum

PORel#ShippedQty

 

Are there any fields you suggest we include/exclude to/from this list? Any help would be much appreciated!

 

Thanks,

-Marcus

 

 

 

 



CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at 727-578-6280 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."