Configure OB EDI Delimiters By EDIConfig

• For OB EDI, EDI delimiters can be configured by setting up OB related columns: OBSEGMENT_DELIMITER, OBFIELD_DELIMITER, OBGROUP_DELIMITER, OBESCAPE_CHARACTER, OBREPEAT_CHARACTER, OBSEGMENT_SUFFIX of EDI_Config table for a partnership; this is used when user may want to apply delimiters other than default EDI delimiters which EDI standard does support.

• The EDI Config lookup would be based on Partnership for which generated OB EDI file needs to be send.

• Please note that if EDI Config is configured for any partnership for outbound transaction then OB EDI delimiters must be set on EDI Config table in case any custome delimiters needs to be apply on OB EDI. Else default/standard EDI delimiters would get apply on OB EDI based on EDI type like X12 or EDIFact.

Configure OB EDI 824 By EDIConfig

The OB EDI 824 can be configured by setting up Support824 column of EDI_Config table for a partnership. The EDI Config lookup would be based on matching sender/receiver identifiers of inbound EDI file for which business error needs to be send. Partner has support for same and this would be preferred when EDI Config is not at all configured for EDI transactions. Please note that if EDI Config is configured for any partnership for inbound transaction then valid configuration of EDI 824 (Support824) must be set on EDI Config table. So whether to send or suppress business error (824) is taken care by EDI Config.

Please find below details for (Partner) Respond_With_EDI824 and (EDI_CONFIG) Support824:

• The both flag Respond_With_EDI824 and Support824 can be used to configure OB EDI 824 whether to send EDI 824 or not.

• Partner's Respond_With_EDI824 flag is used when EDI config entry is not configured for inbound processing

• When EDI_CONFIG table has record for inbound EDI like sender/receiver identifiers matches with inbound EDI file then system would check Support824 flag on EDI_Config table

• Please note priority always given to EDIConfig record. In case EDI_Config is not used then system will check configuration on Partner table.

Configure OB EDI 997 By EDIConfig

The OB EDI 997 can be configured by setting up Supress997 column of EDI_Config table for the partnership. The EDI Config lookup would be based on matching sender/receiver identifiers of inbound EDI file for which acknowledgment needs to be send. EDI_Forward has support for same and this would be preferred when EDI Config is not at all configured for EDI transactions.

Please note that if EDI Config record is configured for any partnership for inbound transaction then valid configuration of EDI 997 (Supress997) must be set on EDI Config table. So whether to send or suppress acknowledgement for acceptance/rejection (997) is taken care by EDI Config.

Please find below details for (EDI_Forward) Supress997 and (EDI_CONFIG) Supress997:

• The both flag Supress997 from EDI_Forward/EDI_CONFIG table can be used to configure OB EDI 997 whether to send EDI 997 or not.

• When Supress997 flag is set to 1 means system shouldn’t send EDI 997 file whether inbound EDI file is accepted or rejected, the EDI 997 is get suppressed here.

• (EDI_Forward) Supress997 flag is used when EDI_CONFIG table entry is not configured for inbound processing

• When EDI_CONFIG table has entry for inbound EDI like sender/receiver identifiers matches with inbound EDI file then system would check Supress997 flag on EDI_Config table

• Please note priority always given to EDIConfig entry and if EDI_Config is not used then system will check configuration on EDI_Forward table. By default, ONE Integ system generates EDI 997 as acknowledgement for inbound file whether it is accepted or rejected by ONE system.

EDI Configuration specific to EDI Version

EDI version is optional field and can be used to configure any EDI version (4010, 4030, 5030, D97A etc) specific configurations. The EDI config matching the EDI version in the file will be taken into precedence if it's record present in EDI_Config table.

EDI Configuration sample for X12, EDIFact and IDoc

EDIConfig for X12 Inbound

EDIConfig for X12 Outbound

EDIConfig for EDIFact

EDIConfig for IDoc