SAP for Banking Discussions
Join the conversation about navigating compliance, enhancing customer experience, and driving growth in the banking industry with SAP.
cancel
Showing results for 
Search instead for 
Did you mean: 

Tracking External Payment Forms for "blocking/locking". How?

Former Member
0 Kudos
157

Hi folks,

     Could you please advise on an effective way in SAP BaS to perform the following requirement?

Setting the scene: SWIFT messaging to systematically create PLM Documents on SAP.

The Bank is notified of the payment form to dishonour / block via SWIFT message.  How do we automatically register this fact in SAP BaS automatically, so that if the payment arrives thereafter it is not honoured?

   Also, on the Creation of the PLM document to lock Value Transactions, SAP must check whether the transaction has already been processed in SAP BaS. Dependent on the type of transaction, a date range will have to be used to check for the posting of the transaction in SAP. If the transaction has been processed to the account, the creation of the PLM document must Fail and a correspondence to be generated to the relevant department with the details that was received in the inbound Swift message.

   Any thoughts you have on how you would handle this / how you have ahndled this, would be greatly appreicated. 

Cheers everyone.

Russ

1 ACCEPTED SOLUTION

0 Kudos
125

Hi Russ,

If this is a "payment form" (i.e,cheque or other such form) then the lock is straightforward. The payment form itself can be uniquely locked as a PLM document using standard functionality.

If this is an alternate form of payment then the lock functionality you are looking for is more akin to an idempotency check as opposed to a standard PLM lock as you would need to check for a unique transaction reference as a means to enforce the lock.

In terms of the check you are looking to perform prior to the creation of the lock this depends largely upon the way in which you orchestrate your integration. At a simple level you are performing a business rule check to determine the status of the payment form. If cashed you could use this to stop the processing of the payment form and the generation of a correspondence event. If however payment information is required then more complex processing is required.

Hope this helps

Regards

Keith

View solution in original post

2 REPLIES 2

0 Kudos
126

Hi Russ,

If this is a "payment form" (i.e,cheque or other such form) then the lock is straightforward. The payment form itself can be uniquely locked as a PLM document using standard functionality.

If this is an alternate form of payment then the lock functionality you are looking for is more akin to an idempotency check as opposed to a standard PLM lock as you would need to check for a unique transaction reference as a means to enforce the lock.

In terms of the check you are looking to perform prior to the creation of the lock this depends largely upon the way in which you orchestrate your integration. At a simple level you are performing a business rule check to determine the status of the payment form. If cashed you could use this to stop the processing of the payment form and the generation of a correspondence event. If however payment information is required then more complex processing is required.

Hope this helps

Regards

Keith

0 Kudos
125

Hi Keith, thank you very much for your response. 

   Indeed, it is a payment form... but of other banks.  Thus, no record of the numbers issued etc will be stored in the local bank's "payment forms".  That's the tricky bit.  Let me chat a bit more with those involved here and get back to you with more details, perhaps.

Thanks again Keith for your reply and you help!

Greatly appreciated!

Russ