PACS003 GENERATION FAILED DUE LOCAL INSTRUMENT WHILE PROCESSING AFTER INPUT LOCAL INSTRUMENT IN TR (Doc ID 3017173.1)

Last updated on MAY 28, 2024

Applies to:

Symptoms

On : 14.7.0.3.0 version, Production Support

PACS003 GENERATION FAILED DUE LOCAL INSTRUMENT WHILE PROCESSING AFTER INPUT LOCAL INSTRUMENT IN TR

Network Rule maintenance is if Local instrument is B2B then system should resolve SEPADDB2B.

SDD transaction moved to Repair Queue due to Local instrument.

ACTUAL BEHAVIOR
-----------------------
issue 1) System not showing Sepa DD related local instrument code in LOV present in PQSNWRQU screen like CORE m B2B.

issue 2) When transaction repaired and input B2B in repair screen. pacs003 dispatch is failed due to local instrument.


EXPECTED BEHAVIOR
-----------------------
1) Sepa DD related local instrument code in LOV should present in PQSNWRQU screen like CORE m B2B.

2) When user input repair data in Repair screen, system should dispatch the pacs003 by considering the local instrument code.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upload pain008 without Local instrument.
2. As network rule failed, batch moved to network resolution queue.
3. User select Network SEPADDB2B and completed the process.
4. User input B2B in repairable data.
5. Dispatched the pacs003.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.