WMS 810 ER023-090: Difference between revisions
(Created page with "<!-- MEDIA LANDSCAPE YES --> {{#vardefine:System|WMS}} {{ERHeader |SystemVersion=WMS 810 |ERNumber=ER023-090 }} {{ERTableHeader}} {{ERTableRow |DATA_CONF_EDI_OUT_MSG_346026.sql...") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 11: | Line 11: | ||
|Data Script | |Data Script | ||
|4.1 | |4.1 | ||
| | |346026 | ||
| | |- | ||
| | |3 | ||
| | |A new outbound EDI message type has been created, JNL_DTL. This is a copy of the existing ADJUSTMENTS message type amended to exclude journal transactions where either: | ||
| | a) A record has been entered in the Transaction Type Exclusion List screen for the transaction type with no reason, or | ||
b) A record has been entered for the transaction type and reason code. | |||
i.e. A record with no reason codes will cause the transaction type to always be excluded, no matter what the reason code. A record with both transaction type and reason code will only exclude the transaction if both the transaction type and reason code match. | |||
A new record will need to be setup in the Dynamic Outbound EDI message definition screen (XFM0050) with EDI Structure set to JNL_DTL. | |||
The new message type will then need to be set up in the following EDI screens: | |||
XF Command Screen (XFM0012) | |||
XF Re-sequence (XFM0011) | |||
XF Monitor (XFM0020) | |||
|Steve Carpenter | |||
}} | }} | ||
{{ERTableRow | {{ERTableRow | ||
Latest revision as of 11:01, 18 October 2017
EMERGENCY RELEASE - WMS 810
RELNOTE ER023-090
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks | Reporter |
| DATA_CONF_EDI_OUT_MSG_346026.sql | Data Script | 4.1 | 346026 | - | 3 | A new outbound EDI message type has been created, JNL_DTL. This is a copy of the existing ADJUSTMENTS message type amended to exclude journal transactions where either:
a) A record has been entered in the Transaction Type Exclusion List screen for the transaction type with no reason, or b) A record has been entered for the transaction type and reason code. i.e. A record with no reason codes will cause the transaction type to always be excluded, no matter what the reason code. A record with both transaction type and reason code will only exclude the transaction if both the transaction type and reason code match. A new record will need to be setup in the Dynamic Outbound EDI message definition screen (XFM0050) with EDI Structure set to JNL_DTL. The new message type will then need to be set up in the following EDI screens: XF Command Screen (XFM0012) XF Re-sequence (XFM0011) XF Monitor (XFM0020) |
Steve Carpenter |
| DATA_CONF_EDI_OUT_MSG_LEVEL_346026.sql | Data Script | 4.1 | " | " | " | " | " |
| DATA_CONF_EDI_OUT_MSG_LEVEL_COLS_346026.sql | Data Script | 4.1 | " | " | " | " | " |
| DATA_CONF_EDI_OUT_TRIGGER_POINT_346026.sql | Data Script | 4.1 | " | " | " | " | " |
| DP_CONF_EDI_OUT.sql | Outbound Configurable EDI | 4.21 | " | " | " | " | " |
| TRG_INS_IAJD_AIS.sql | Trigger | 4.5 | " | " | " | " | " |
