Symptom
The issue is related to the API_APAR_SEPA_MANDATE_SRV where the fields for 'LastUsageDate' are filled in the API, but there is no effect in the created mandate.
Environment
SAP S/4HANA Public Cloud Edition
Reproducing the Issue
- Fill the fields for 'LastUsageDate' in the API_APAR_SEPA_MANDATE_SRV.
- Create the Mandate using the payload.
- Perform a GET request functionally or via API.
- Observe that the fields for 'LastUsageDate' remain blank.
Cause
'SEPAMandateLastUseDate' stores the last use date of the SEPA Mandate for a payment. In case of the first payment where a SEPA Mandate is used, the information regarding the "Last Use Date" is similar as the information about the "First Use Date".
You can visualize "Usage Data" information via SEPA Mandate API GET Request. With POST request you can update the "LastUsageDate" via SEPA Mandate API.
Resolution
SEPA Mandate API Documentation provides a GET request to inform "LastUsageDate" via SEPA Mandate API.
POST request updates this field.
URL: .../SEPAMandateSet(Creditor='{Creditor}',SEPAMandate='{SEPAMandate}')/SEPAMandateUsage
Method: POST
Body:
{
"Creditor": ".....",
"SEPAMandate": "....",
"SEPAMandateUseDate": "....",
"SEPAMandateUseObjectType": "....",
"SEPAMandateUsePaymentDoc":"....."
}
See Also
Keywords
API_APAR_SEPA_MANDATE_SRV, LastUsageDate, blank fields, GET request, POST, mandate creation, payload , KBA , CA-BK-SEP-2CL , SEPA Mandates: Public Cloud , How To