2.3 Task Creation - Process Steps

This topic provides the process steps for the task creation.

Contract Reference Checks

• Exact Match: If both Tag 21 and Tag 20 match data in OBTF, proceed with task creation in OBTFPM (STP).
• Tag 21 Found, Tag 20 Mismatch: Create task with override and add note: "Mismatch in Sending Bank's TRN between Incoming Message and Contract".
• Tag 21 Found, Tag 20 Not Available: Create task with override and add note: "Sending Bank's TRN not available in OBTF".
• Tag 21 is NONEEF, Tag 20 Available: Create task with override and add note: "Related Contract Reference not available in Incoming Message".
• Tag 21 is NONEEF, Tag 20 Mismatch or Not Available: Apply Partial STP approach.
• When a contract reference cannot be identified, create a partial STP task. This is placed in the Free Task Queue for further user review, where the user can initiate a new process, link to an existing contract, or decide no action is required.

Special Contract Statuses

If a contract's status is Closed, Cancelled, Reversed, or Liquidated, the message appears with status K – User Handling Required in the “Incoming Message Queue”. The system provides remarks such as:

• "Contract already in Closed status. User handling required."
• "Contract already in Cancelled status. User handling required."