Error FWM 02021 Using SAP Business Objects 4.3

[RPD]

I am currently using the Loadrunner Professional Version 2023 R1 Patch 3 to create a performance testing program for my company's SAP BO 4,3 application. I am also using the SAP WEB Loadrunner protocol to generate this performance testing program. In order to do that, the Loadrunner Professional IDE known as Vugen is used to RECORD the actual SAP Web traffic. After that is done, the next step is to identify all the dynamic data from that Vugen recording and then parameterize that dynamic data so that multiple iterations of that performance testing program can be run simultaneously. Given that background,  I have the following issue to post.

The error FWM 02021 is occurring when executing the following URL after I have successfully completed an Enterprise login to my company's BO 4.3 application.

https://biqat3.core.cpa.state.tx.us/BOE/portal/2307200817/biprwsproxy/biprws/logon/token

This is a URL to a Business Objects 4.3 application. The FWM 202 error states in the Response Body of this failing web request:

<error>
<error_code>FWM 02021</error_code>
<message>The property with ID SESSIONID does not exist in the object (FWM 02021)</message>
</error>

However, the login token that is in the Request Body associated with this URL was based on dynamic data that was generated in the web request below, which was done immediately BEFORE the web request listed above failed.

web_submit_data("main.jsp",
        "Action=https://biqat3.core.cpa.state.tx.us/BOE/portal/2307200817/FioriBI/main.jsp?service=%2Fcommon%2FappSe...",
        "Method=POST",

How can "The property with ID SESSIONID" NOT EXIST when the content of that value was just created in the web request right BEFORE that request?

The Request Body of the web request that fails with this FWM 2021 error is properly formatted and is shown below. Note also the number 335559 is higher that the six digit number that was SUCCESSFULLY RECORDED by the Loadrunner 2023 R1 Script Development IDE known as Vugen. It is common that for every new call to this URL that 6 digit number is higher. Consequently, it appears that the logonToken that was passed in this request is valid. It is NOT CLEAR at all what part of this logonToken is invalid and where do I find the correct value for the logonToken parameter. Since this is DYNAMIC data of some type, that type of data is usually found in the web requests PRIOR to the web request in which it is needed. But I have studied these requests and I believe that I correctly created this logonToken parameter.

{"logonToken":"3&5U=335559JxooGYHCpfWLCQ8Sj8UEdEYHhfjGIbXTW335558Jg9VvcOloH1B7NoFx5MNnv841xraZMh1V,8P&10U,88&1=DO+NOT+DELETE%0D%0APW+@L0ad2024,8P&63=secEnterprise,8P&35=bitesterload,8P&S5,88&pa,8P&ua=Af9fX5We.TVJu_6eVqnxufQ,8P&ub=335558Jg9VvcOloH1B7NoFx5MNnv841xraZMh1V,8P&3k=335558Jg9VvcOloH1B7NoFx5MNnv841xraZMh1V,8P&3k=@BOQA43,8P&4F=303002,8P&Tm=36500,83&Tn={3&U=3,83&.1={3&2=303003,83&O=FavoritesFolder,8P},?z&.2={3&2=303004,83&O=PersonalCategory,8P},?z&.3={3&2=303005,83&O=Inbox,8P},?z},?z&7r,83&2r=cautswap0021.core.cpa.state.tx.us:6400,8P&lu=1033,83&PP=1024,83&ux=AdAxiJtoDGJKqzs4CMlACx4,8P&uy=-2,8L","tokenType":"serializedSession"}

I would appreciate any comments that anyone may have. My company has a large SAP applicaton and is in the process of upgrading to BO 4.3 and a performance test of the new version of SAP is a requirement.