B2B Gateway > Introducing B2B Gateway > File Patterns
  

File Patterns

The following table lists the patterns that are supported when you provide file names in Outbound and Outbound Acknowledgement tab:
Pattern
Description
msgType
Message type of the EDI X12 or EDIFACT message.
groupCtrlNo
The control number for the functional group .
interchangeCtrlNo
The interchange control number of the message.
YYYY
Pattern for year in four-digit format. If you provide the input file pattern as ($YYYY), the file name on the Events page will include YYYY format. For example, 2023.
YY
Pattern for year in two-digit format. If you provide the input file pattern as ($YY), the file name on the Events page will include YY format. For example, the file name will include 23 for the year 2023.
MM
Pattern for month in two-digit format. If you provide the input file pattern as ($MM), the file name on the Events page will include MM format. For example, the file name will include 04 for the April month.
DD
Pattern for day in two-digit format. If you provide the input file pattern as ($DD), the file name on the Events page will include DD format. For example, the file name will include 12 for the 12th day of a month.
HH24
Pattern for hour in day (1-24 hours) . If you provide the input file pattern as ($HH24), the file name on the Events page will include HH24 format. For example, the file name will include 18 for 6 PM.
HH12
Pattern for hour in day (1-12 hours). If you provide the input file pattern as $HH12, the file name on the Events page will include HH12 format. For example, the file name will include 06 for 6 PM.
MN
Pattern for minutes. If you provide the input file pattern as $MN, the file name on the Events page will include MN format. For example, the file name will include 32 for 3:32 PM.
SS
Pattern for seconds. If you provide the input file pattern as $SS, the file name on the Events page will include SS format. For example, the file name will include 06 for 3:32:06 PM.
sss
Pattern for milliseconds. If you provide the input file pattern as $sss, the file name on the Events page will include sss format. For example, the file name will include 543 for 3:32:543 PM.
Z
Pattern for timezone. If you provide the input file pattern as $Z, the file name on the Events page will include Z format. The file name will include values such as IDT, IST, PST, and so on.
eventId
Unique identifier for the event associated with processing the EDI group.
partnerName
The name of the partner.
senderInterchangeId
The identification code published by the sender for other parties to use as the receiver ID to route data. You can use this parameter in the file patterns that are provided for the EDI X12 messaging.