Posting journal entry API causes "error "SRT: Plain SOAP: Reliable messaging (RM) configured..."

[HKD]

Hi, Experts,
I would like to post journal entry into S4 HANA cloud using "Journal Entry - Post (Asynchronous)"API ". But when I post it by Postman, I get the error "SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided." in S4 HANA cloud.  Is there anyone who can find the cause?

API Reference | Journal Entry - Post (Asynchronous) | SAP Business Accelerator Hub

SAP S/4HANA Cloud Public Edition , API , SAP S/4HANA Finance 

Below XML body was posted :

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

    <soap:Header>

        <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>

    </soap:Header>

    <soap:Body>

        <JournalEntryBulkCreateRequest xmlns="http://sap.com/xi/SAPSCORE/SFIN">

            <MessageHeader>

                <ID schemeID="MSG_2024-03-28"/>

                <CreationDateTime>2024-03-28T12:00:00.1234567Z</CreationDateTime>

            </MessageHeader>

            <JournalEntryCreateRequest>

                <MessageHeader>

                    <ID/>

                    <CreationDateTime/>

                </MessageHeader>

                <JournalEntry>

                    <OriginalReferenceDocumentType>BKPFF</OriginalReferenceDocumentType>

                    <BusinessTransactionType>RFBU</BusinessTransactionType>

                    <AccountingDocumentType>KR</AccountingDocumentType>

                    <DocumentReferenceID>Test</DocumentReferenceID>

                    <OriginalReferenceDocument>XXXX</OriginalReferenceDocument>

                    <DocumentHeaderText>Test</DocumentHeaderText>

                    <CompanyCode>1510</CompanyCode>

                    <CreatedByUser>API User</CreatedByUser>

                    <DocumentDate>2024-03-28</DocumentDate>

                    <PostingDate>2024-03-28</PostingDate>

                    <Item>

                        <ReferenceDocumentItem>1</ReferenceDocumentItem>

                        <CompanyCode>1510</CompanyCode>

                        <GLAccount listID="0065001000"/>

                        <AmountInTransactionCurrency currencyCode="JPY">100</AmountInTransactionCurrency>

                        <DebitCreditCode>S</DebitCreditCode>

                        <DocumentItemText>text Test</DocumentItemText>

                        <Tax>

                            <TaxCode>V3</TaxCode>

                            <AccountAssignment>

                                <CostCenter>15101201</CostCenter>

                                <FunctionalArea>YB20</FunctionalArea>

                            </AccountAssignment>

                        </Item>

                        <CreditorItem>

                            <ReferenceDocumentItem>2</ReferenceDocumentItem>

                            <Creditor>15300001</Creditor>

                            <AmountInTransactionCurrency currencyCode="JPY">-100

                        </AmountInTransactionCurrency>

                            <DebitCreditCode>H</DebitCreditCode>

                        </CreditorItem>

                    </JournalEntry>

                </JournalEntryCreateRequest>

            </JournalEntryBulkCreateRequest>

    </soap:Body>

</soap:Envelope>

[Enda]

Hi @HKD 

Usually the error "SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided." comes in Asynchronous posting if the Enable WS-A addressing is not flagged and Generate MessageID is not enabled.

Kindly check the SAP Blog Post Guidelines for Testing Journal Entry API with SOAPUI and Checking Response Message part 3. How to Test Asynchronous API with SOAPUI

Best Regards

Enda

[HKD]

Hi Enda, Thank you for your comment! It worked on SOAPUI, but SOAPUI is not allowed in my environment. when I try to post the same body on Postman, it still have the same error. Is there any solution for postman?