ROI HSP Project Approach to handling NI codes inbound to ROI IGG - PowerPoint PPT Presentation

ROI HSP Project Approach to handling NI codes inbound to ROI IGG 11-01-12

Approach to handling NI codes inbound to ROI There will be a new rejection reason code “DIJ” (Data Invalid in Jurisdiction) as part of harmonisation. The scenarios where this new code will , or will not , be used are described here : A. Where there is already an existing validation that results in a rejection message with an existing rejection reason code – the current rejection code will continue to be used , and not DIJ B. Where a Supplier populates a field on a message that is inbound to ESBN but this field is not valid in ROI for that message. – There will be no rejection : approach is that ROI will ignore this C. If a Supplier chooses to populate a field with a code that is deemed as not mandatory for a process – This will be rejected if the code is not valid for ROI

Approach to handling NI codes inbound to ROI D. Where it is possible to receive a non ROI value in a MM on an enumerated field and the scenarios above do not apply , then “DIJ” will be used : • Some rejection messages currently contain only one rejection reason code i.e. when processing the inbound message as soon as one validation fails then the message is rejected – For these, the approach will remain as-is and therefore we will continue to reject as soon as one validation fails i.e. if we find an invalid code for ROI then we will reject with “DIJ”. • Other messages are validated completely before a rejection message is issued and so they may be rejected for more than one reason. – For these, the approach will remain as-is and therefore if there is more than one “DIJ” validation failure then each of these reason codes will be populated on the rejection message. E. Where there is no rejection message for an inbound MM eg MM260. – Specific Supplier queries will be handled on a case by case basis by ESBN

Approach to handling NI codes inbound to ROI Inbound Message Field Outbound Message ��������� 010 101R/102R ���������������������������� 010 101R/102R 010 CustomerServiceDetailsCode 101R/102R ��������� 013 014R ��������� 016 116R ���������������������������� 016 116R 016 CustomerServiceDetailsCode 116R ��������������������������� 017 117R ���������������������������� 017 117R ��������� 017 117R ������������������ 017 117R ���������������������������� 017 117R ������������������� 030 130R �������� �!������������ 030 130R ������������������ 030 130R This table shows the fields that will be validated and may result in a DIJ, the inbound message in which they may be populated, as well as the corresponding rejection message.