EDI Core

EDI Core Documents - Functional acknowledgement inbound

Return to main page
-->

Functional acknowledgement inbound

When the Company requires the Trading partner to send a Functional Acknowledgement for outbound EDI files, the following is required:

  1. Create document Template Functional acknowledgement inbound.
  2. Add the Functional acknowledgement inbound document type to Trading Partner’s Incoming documents and Enable.
  3. For each Trading partner’s outgoing documents that requires to receive a Functional acknowledgement, set Acknowledgement to Yes.

Setting profiles

Users can access the form by navigating to EDI > Setup > Document types and filtering/selecting the Functional acknowledgement inbound document.
See Setting profiles for more details on how to create a Setting profile.

Field Description Options/example
Document type mapping Assign applicable document type mapping to setting Mappings setup at EDI > Setup > Document type mapping

View Staging table records

Functional acknowledgement inbound staging records

Users can access the form by navigating to EDI > Documents > Functional acknowledgement inbound.
Use this form to review staging records and optionally manually process the staging record.

List page

Field Description
EDI number EDI Staging table record id.
Company account Company account for the staging record.
Template Id Document type template used to process the document.
Staging to target status The current status of the staging. Options include:
Not Started: The staging record has been created but not processed.
Error: The staging record has been processed but there are errors with the record that need to be reviewed.
Completed: The staging record has been successfully processed.
Trading partner account Trading partner account for the staging record.
Trading partner GLN The trading partners’ global location number is shown here.
Company GLN The company’s global location number is shown here.
Group control number Company’s Group control number being acknowledged.
Created date and time The date and time the staging record was created
Sent Indicates if an Outbound Functional Acknowledgement has been sent.

Buttons

Button Description
Process selected Process selected records in the staging table. Button is only enabled for records with Staging to target status set to Not Started.
Process all Process all records with Staging to target status set to Not Started.
Inbound files View the inbound file record that created the functional acknowledgement staging record.
Trading partner View staging record’s Trading partner details.
Show log If there are Errors within the staging record, it is possible to review them at any time using this button. Shows only current version.
Version log View all defined errors. When a document’s status reset and reprocessed a new log version is created. If the log is not defined, more information can be viewed via Execution log.
Reset status Reset the staging’s Staging to target status to enable reprocessing of the staging record. Enabled where the record’s Staging to target status is not set to Not Started.
Edit reset status recurrence Option to edit the reset status recurrence for the record. Enabled where the Staging to target status is set to Error.

Header fields

Field Description
EDI number EDI Staging table record id.
Company Company account for the staging record.
Template Id Document type template used to process the document.
Staging to target status The current status of the staging record. Options include:
Not Started: The EDI file has been successfully processed from the inbound file to the staging table.
Error: The EDI file has been processed from the staging table but errored on processing to target. There are errors with the record that needs to be reviewed.
Completed: The EDI file has been processed to target which updates the original outgoing document with info that functional acknowledgement has been received.

Line fields

The Functional Acknowledgement only has header fields. Header details are repeated.

© DXC Technology Company