WorkWise ERP EDI Integration – Part 2 – Customer Outbound Transactions

The WorkWise ERP EDI Module supports the following outbound customer EDI transactions as part of the ERP software:

  • Advanced Ship Notices (X12 856/EDIFACT DESADV)
  • Invoices (X12 810/EDIFACT INVOIC)

The TRG EDI Connector extends the WorkWise ERP EDI functionality by also offering the following transactions with no customization required to the WorkWise ERP:

  • Purchase Order Acknowledgement (X12 855/EDIFACT APERAK)
  • Inventory Advice (X12 846/EDIFACT INVRPT)

Advanced Ship Notices (ASN)

In WorkWise ERP, the ASN transaction is generated during the Shipment Confirmation process. When the shipment is confirmed, transactions are written to the 856 Holding table – there is a report prompt in WorkWise ERP when ASNs are interfaced and a log file that will show that the ASN is created successfully and will show any errors.

The ASN data that is captured in the WorkWise ERP ASN holding table is defined by a template that is defined in the WorkWise ERP EDI module and attached to the ship-to in the Trading Partner master. The template definition process requires some in-depth knowledge of the WorkWise ERP EDI module and the WorkWise ERP data structures.

For the TRG EDI Connector, we have defined standard templates that capture the data we integrate into the TRG EDI Connector database.

Standard WorkWise ERP EDI then requires an export to a flat file of the captured data – then a translator can pick it up and convert it to the appropriate EDI format. The TRG EDI Connector bypasses the flat file method and interfaces directly into the WorkWise ERP ASN holding file and pulls ASNs automatically, translates and sends them out on a predetermined schedule. An audit report of ASNs sent is emailed by the TRG EDI Connector to designated users.

Invoices

In WorkWise ERP, the EDI invoice transaction is generated during the “Print Invoices” process. When the invoices are printed and the user answers “Yes” to the “Are all invoices OK?” question, transactions are written to the 810 Holding table – there is a report prompt in WorkWise ERP when invoices are interfaced and a log file that will show that the invoice is created successfully and will show any errors.

The invoice data that is captured in the WorkWise ERP Invoice holding table is defined by a template that is defined in the WorkWise ERP EDI module and attached to the bill-to in the Trading Partner master.

For the TRG EDI Connector, we have defined standard templates that capture the data we integrate into the TRG EDI Connector database.

Standard WorkWise ERP EDI then requires an export to a flat file of the captured data – then a translator can pick it up and convert it to the appropriate EDI format. Again, the TRG EDI Connector bypasses the flat file method and interfaces directly into the WorkWise ERP Invoice holding file and pulls invoices automatically, translates and sends them out on a predetermined schedule. An audit report of invoices sent is emailed by the TRG EDI Connector to designated users.

Purchase Order Acknowledgement

The TRG EDI Connector interfaces to WorkWise ERP customer orders to determine PO acknowledgements that need to be sent to the customer.

Using the “PO Acknowledgement Print” flag, once the Acknowledgement is printed (or the flag is set to “Printed”), the TRG EDI Connector will interface the order data, map out the PO acknowledgement and send it to the customer.

Each customer will have a defined set of valid PO acknowledgement codes that are valid to be returned at the header level and for each line item. These are configurable in the TRG EDI Connector and are set up as part of the mapping/definition process. Appropriate codes are set as “defaults” for certain conditions, such as Item Rejected, Date Changed, etc.

The TRG EDI Connector compares the WorkWise ERP customer order to the original PO sent in by the customer and determines if the quantity has changed, if the date has changed, if the price is different, or if you have rejected the line item (by setting the quantity to 0). It then sets the appropriate response, sends the updated order details from WorkWise ERP directly to the customer.

Inventory Advice

In some retail applications, customers expect to receive a daily update of available inventory.

The TRG EDI Connector reaches directly into your WorkWise ERP inventory to send the available inventory quantities to your customer. Using either the Customer item cross-reference or item attributes, you can define which items should go back on the inventory advice to your customer.

TRG has worked with WorkWise ERP for over 20 years – the TRG EDI Connector incorporates that experience and knowledge to give you the best EDI integration available for your WorkWise ERP system.

The WorkWise ERP EDI Module supports the following outbound customer EDI transactions as part of the ERP software:

  • Advanced Ship Notices (X12 856/EDIFACT DESADV)
  • Invoices (X12 810/EDIFACT INVOIC)

The TRG EDI Connector extends the WorkWise ERP EDI functionality by also offering the following transactions with no customization required to the WorkWise ERP:

  • Purchase Order Acknowledgement (X12 855/EDIFACT APERAK)
  • Inventory Advice (X12 846/EDIFACT INVRPT)

Advanced Ship Notices (ASN)

In WorkWise ERP, the ASN transaction is generated during the Shipment Confirmation process.  When the shipment is confirmed, transactions are written to the 856 Holding table – there is a report prompt in WorkWise ERP when ASNs are interfaced and a log file that will show that the ASN is created successfully and will show any errors.

The ASN data that is captured in the WorkWise ERP ASN holding table is defined by a template that is defined in the WorkWise ERP EDI module and attached to the ship-to in the Trading Partner master.  The template definition process requires some in-depth knowledge of the WorkWise ERP EDI module and the WorkWise ERP data structures.

For the TRG EDI Connector, we have defined standard templates that capture the data we integrate into the TRG EDI Connector database.

Standard WorkWise ERP EDI then requires an export to a flat file of the captured data – then a translator can pick it up and convert it to the appropriate EDI format.  The TRG EDI Connector bypasses the flat file method and interfaces directly into the WorkWise ERP ASN holding file and pulls ASNs automatically, translates and sends them out on a predetermined schedule.  An audit report of ASNs sent is emailed by the TRG EDI Connector to designated users.

Invoices

In WorkWise ERP, the EDI invoice transaction is generated during the “Print Invoices” process.  When the invoices are printed and the user answers “Yes” to the “Are all invoices OK?” question, transactions are written to the 810 Holding table – there is a report prompt in WorkWise ERP when invoices are interfaced and a log file that will show that the invoice is created successfully and will show any errors.

The invoice data that is captured in the WorkWise ERP Invoice holding table is defined by a template that is defined in the WorkWise ERP EDI module and attached to the bill-to in the Trading Partner master.

For the TRG EDI Connector, we have defined standard templates that capture the data we integrate into the TRG EDI Connector database.

Standard WorkWise ERP EDI then requires an export to a flat file of the captured data – then a translator can pick it up and convert it to the appropriate EDI format.  Again, the TRG EDI Connector bypasses the flat file method and interfaces directly into the WorkWise ERP Invoice holding file and pulls invoices automatically, translates and sends them out on a predetermined schedule.  An audit report of invoices sent is emailed by the TRG EDI Connector to designated users.

Purchase Order Acknowledgement

The TRG EDI Connector interfaces to WorkWise ERP customer orders to determine PO acknowledgements that need to be sent to the customer.

Using the “PO Acknowledgement Print” flag, once the Acknowledgement is printed (or the flag is set to “Printed”), the TRG EDI Connector will interface the order data, map out the PO acknowledgement and send it to the customer.

Each customer will have a defined set of valid PO acknowledgement codes that are valid to be returned at the header level and for each line item.  These are configurable in the TRG EDI Connector and are set up as part of the mapping/definition process.  Appropriate codes are set as “defaults” for certain conditions, such as Item Rejected, Date Changed, etc.

The TRG EDI Connector compares the WorkWise ERP customer order to the original PO sent in by the customer and determines if the quantity has changed, if the date has changed, if the price is different, or if you have rejected the line item (by setting the quantity to 0).  It then sets the appropriate response, sends the updated order details from WorkWise ERP directly to the customer.

Inventory Advice

In some retail applications, customers expect to receive a daily update of available inventory.

The TRG EDI Connector reaches directly into your WorkWise ERP inventory to send the available inventory quantities to your customer.  Using either the Customer item cross-reference or item attributes, you can define which items should go back on the inventory advice to your customer.

TRG has worked with WorkWise ERP for over 20 years – the TRG EDI Connector incorporates that experience and knowledge to give you the best EDI integration available for your WorkWise ERP system.