Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Issue with LoadablePms with Simphony V2 1

Status
Not open for further replies.

Dananjaya

Programmer
Jan 17, 2020
39
OM
Hi All,
Does any having an idea how to resolve the error message ("Simphony Pos Api: POS API: EError Ids Driver Comms Error") while posting data to Opera PMS ( Room ) via Simphony V2. We are using LoadablePms with Transaction API to achieve this. The work floor should be as follows,

1. Posting happen from external application by using Simphony transaction API specification.
2. Simphony post the data to Opera PMS ( Room Charge ) by using "Micros.Payment.LoadablePmsModule.dll" & "OperaWSPayment.dll"
3. Once the posting is completed, Simphony closes the guest check.

But we are facing an issue while posting data from Simphony to Opera PMS ( Step #2 ) and posting not completing. The error message in EGatewayLog file says "Simphony Pos Api: POS API: EError Ids Driver Comms Error".
Transaction Service API Payload is,
XML:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope 
               xmlns:xsi="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema-instance"[/URL] 
               xmlns:xsd="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema"[/URL] 
               xmlns:soap="[URL unfurl="true"]http://schemas.xmlsoap.org/soap/envelope/">[/URL]
 <soap:Body>
    <AddToExistingCheckEx xmlns="[URL unfurl="true"]http://micros-hosting.com/EGateway">[/URL]
      <vendorCode/>
      <pGuestCheck>
        <CheckEmployeeObjectNum>90001</CheckEmployeeObjectNum>
        <CheckNum>5</CheckNum>
            <CheckOrderType>1</CheckOrderType>
        <CheckRevenueCenterID>101</CheckRevenueCenterID>
        <CheckSeq>466404770</CheckSeq>
      </pGuestCheck>
      <ppMenuItems>
      </ppMenuItems>
      <ppComboMeals/>
      <pServiceChg>
        <SvcChgObjectNum>0</SvcChgObjectNum>
      </pServiceChg>
      <pSubTotalDiscount>
        <DiscObjectNum>0</DiscObjectNum>
      </pSubTotalDiscount>
      <pTmedDetail>
           <TmedEPayment></TmedEPayment>
        <TmedObjectNum>1003</TmedObjectNum>
        <TmedPartialPayment>2.50</TmedPartialPayment>
        <TmedReference>
          &lt;ExtraData&gt;
          &lt;RoomNumber&gt;5103&lt;/RoomNumber&gt;
          &lt;GuestName&gt;paras&lt;/GuestName&gt;
          &lt;PaymentModule&gt;Other1:LoadablePms&lt;/PaymentModule&gt;
          &lt;/ExtraData&gt;
          </TmedReference>
        </pTmedDetail>
    </AddToExistingCheckEx>
  </soap:Body>
</soap:Envelope>

Exact EGatewayLog messages are mentioned below
Code:
06/05/20 05:39:30.690, 5, 0,API         ,       10,Simphony Pos Api: API LOG_PATH is C:\Micros\Simphony\WebServer\[URL unfurl="true"]wwwroot\EGateway,[/URL]
06/05/20 05:39:30.690, 5, 0,API         ,       10,Simphony Pos Api: API CONFIG_PATH is C:\Micros\Simphony\WebServer\[URL unfurl="true"]wwwroot\EGateway,[/URL]
06/05/20 05:39:30.690, 5, 0,API         ,       10,Simphony Pos Api: API HANDLERS DIRECTORY is C:\Micros\Simphony\WebServer\[URL unfurl="true"]wwwroot\EGateway\Handlers,[/URL]
06/05/20 05:39:30.695, 5, 0,API         ,       10,Simphony Pos Api: POS API: DownloadDatastore,
06/05/20 05:39:30.696, 5, 0,API         ,       10,Simphony Pos Api: Api workstation id: 21,
06/05/20 05:39:31.469, 5, 0,API         ,       10,Simphony Pos Api: TSOPS: Finish DownloadDatastores,
06/05/20 05:39:33.038, 5, 0,API         ,       10,Simphony Pos Api: Begin Add to Existing Check,
06/05/20 05:39:33.038, 5, 4,API         ,       10,vendorcode : ,
06/05/20 05:39:33.273, 5, 4,API         ,       10,Request GuestCheck : <?xml version="1.0" encoding="utf-8"?><?micros-type SimphonyPosApi.SimphonyPosApi_GuestCheck‚ SimphonyPosApi‚ Version=2.5.0.0‚ Culture=neutral‚ PublicKeyToken=null?><SimphonyPosApi_GuestCheck xmlns:xsi="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema-instance"[/URL] xmlns:xsd="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema"><CheckDateToFire>0001-01-01T00:00:00</CheckDateToFire><CheckEmployeeObjectNum>90001</CheckEmployeeObjectNum><CheckGuestCount>0</CheckGuestCount><CheckNum>5</CheckNum><CheckOrderType>1</CheckOrderType><CheckRevenueCenterID>101</CheckRevenueCenterID><CheckSeq>466404770</CheckSeq><CheckStatusBits>0</CheckStatusBits><CheckTableObjectNum>0</CheckTableObjectNum><PCheckInfoLines[/URL] /><EventObjectNum>0</EventObjectNum></SimphonyPosApi_GuestCheck>,
06/05/20 05:39:33.504, 5, 4,API         ,       10,Request Menu items : <?xml version="1.0" encoding="utf-8"?><?micros-type SimphonyPosApi.SimphonyPosApi_MenuItem[]‚ SimphonyPosApi‚ Version=2.5.0.0‚ Culture=neutral‚ PublicKeyToken=null?><ArrayOfSimphonyPosApi_MenuItem xmlns:xsi="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema-instance"[/URL] xmlns:xsd="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema"[/URL] />,
06/05/20 05:39:33.783, 5, 4,API         ,       10,Request Combo Menu items : <?xml version="1.0" encoding="utf-8"?><?micros-type SimphonyPosApi.SimphonyPosApi_ComboMeal[]‚ SimphonyPosApi‚ Version=2.5.0.0‚ Culture=neutral‚ PublicKeyToken=null?><ArrayOfSimphonyPosApi_ComboMeal xmlns:xsi="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema-instance"[/URL] xmlns:xsd="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema"[/URL] />,
06/05/20 05:39:34.005, 5, 4,API         ,       10,Request Svc charge : <?xml version="1.0" encoding="utf-8"?><?micros-type SimphonyPosApi.SimphonyPosApi_SvcCharge‚ SimphonyPosApi‚ Version=2.5.0.0‚ Culture=neutral‚ PublicKeyToken=null?><SimphonyPosApi_SvcCharge xmlns:xsi="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema-instance"[/URL] xmlns:xsd="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema"><SvcChgObjectNum>0</SvcChgObjectNum></SimphonyPosApi_SvcCharge>,[/URL]
06/05/20 05:39:34.201, 5, 4,API         ,       10,Request SubTotal discount : <?xml version="1.0" encoding="utf-8"?><?micros-type SimphonyPosApi.SimphonyPosApi_Discount‚ SimphonyPosApi‚ Version=2.5.0.0‚ Culture=neutral‚ PublicKeyToken=null?><SimphonyPosApi_Discount xmlns:xsi="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema-instance"[/URL] xmlns:xsd="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema"><DiscObjectNum>0</DiscObjectNum></SimphonyPosApi_Discount>,[/URL]
06/05/20 05:39:34.505, 5, 4,API         ,       10,Request Tender media : <?xml version="1.0" encoding="utf-8"?><?micros-type SimphonyPosApi.SimphonyPosApi_TmedDetailItemEx‚ SimphonyPosApi‚ Version=2.5.0.0‚ Culture=neutral‚ PublicKeyToken=null?><SimphonyPosApi_TmedDetailItemEx xmlns:xsi="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema-instance"[/URL] xmlns:xsd="[URL unfurl="true"]http://www.w3.org/2001/XMLSchema"><TmedEPayment><AccountDataSource>SOURCE_UNDEFINED</AccountDataSource><AccountType>ACCOUNT_TYPE_UNDEFINED</AccountType><ExpirationDate>********************</ExpirationDate><IssueNumber>0</IssueNumber><PaymentCommand>NO_E_PAYMENT</PaymentCommand><StartDate>0001-01-01T00:00:00</StartDate></TmedEPayment><TmedObjectNum>1003</TmedObjectNum><TmedPartialPayment>2.50</TmedPartialPayment><TmedReference>[/URL]
          &lt;ExtraData&gt;
          &lt;RoomNumber&gt;5103&lt;/RoomNumber&gt;
          &lt;GuestName&gt;paras&lt;/GuestName&gt;
          &lt;PaymentModule&gt;Other1:LoadablePms&lt;/PaymentModule&gt;
          &lt;/ExtraData&gt;
          </TmedReference></SimphonyPosApi_TmedDetailItemEx>,
06/05/20 05:39:34.513, 5, 0,API         ,       10,Simphony Pos Api: Begin Add to Existing Check,
06/05/20 05:39:34.514, 5, 0,API         ,       10,Simphony Pos Api: POS API: Begin Pickup check,
06/05/20 05:39:34.516, 5, 0,API         ,       10,Simphony Pos Api: Begin Pickup check,
06/05/20 05:39:34.841, 5, 0,API         ,       10,Simphony Pos Api: POS API: End Pickup check,
06/05/20 05:39:34.886, 5, 0,API         ,       10,Simphony Pos Api: Success,
06/05/20 05:39:34.886, 5, 0,API         ,       10,Simphony Pos Api: Discount Engine: voids and returns,
06/05/20 05:39:34.887, 5, 0,API         ,       10,Simphony Pos Api: Success,
06/05/20 05:39:34.887, 5, 0,API         ,       10,Simphony Pos Api: POS API: Starting payment module,
06/05/20 05:39:34.916, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=0 State=0 NextState=0,
06/05/20 05:39:34.918, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=0 State=0 NextState=1,
06/05/20 05:39:34.920, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=0 State=1 NextState=1,
06/05/20 05:39:34.921, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=1 State=1 NextState=1,
06/05/20 05:39:34.922, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=1 State=1 NextState=2,
06/05/20 05:39:34.922, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=1 State=2 NextState=2,
06/05/20 05:39:34.922, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=2 State=2 NextState=2,
06/05/20 05:39:34.922, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=2 State=2 NextState=3,
06/05/20 05:39:34.923, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=2 State=3 NextState=3,
06/05/20 05:39:34.923, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=3 State=3 NextState=3,
06/05/20 05:39:34.923, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=3 State=3 NextState=5,
06/05/20 05:39:34.923, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=3 State=5 NextState=5,
06/05/20 05:39:34.923, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=5 State=5 NextState=5,
06/05/20 05:39:34.925, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=5 State=5 NextState=4,
06/05/20 05:39:34.925, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=5 State=4 NextState=4,
06/05/20 05:39:34.925, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=4 State=4 NextState=4,
06/05/20 05:39:34.930, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=4 State=4 NextState=99900,
06/05/20 05:39:34.930, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=4 State=99900 NextState=99900,
06/05/20 05:39:34.930, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=99900 State=99900 NextState=99900,
06/05/20 05:39:34.931, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=99900 State=99900 NextState=6,
06/05/20 05:39:34.931, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=99900 State=6 NextState=6,
06/05/20 05:39:34.931, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=6 State=6 NextState=6,
06/05/20 05:39:34.931, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=6 State=6 NextState=7,
06/05/20 05:39:34.932, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=6 State=7 NextState=7,
06/05/20 05:39:34.932, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=7 State=7 NextState=7,
06/05/20 05:39:34.932, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=7 State=7 NextState=8,
06/05/20 05:39:34.932, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=7 State=8 NextState=8,
06/05/20 05:39:34.933, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=8 State=8 NextState=8,
06/05/20 05:39:34.955, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=8 State=8 NextState=9,
06/05/20 05:39:34.955, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=8 State=9 NextState=9,
06/05/20 05:39:34.955, 5, 3,API         ,       10,Payment Client Continue Payment : PriorState=9 State=9 NextState=9,
06/05/20 05:39:34.996, 5, 0,API         ,       10,Simphony Pos Api: POS API: EError Ids Driver Comms Error.,
06/05/20 05:39:34.997, 5, 0,API         ,       10,Simphony Pos Api: Commit payment error EError Ids Driver Comms Error.,
06/05/20 05:39:34.999, 5, 4,API         ,       10,Commit payment error stack :    at SimphonyPosApi.TSOPS.CommitPayment(GuestCheck check‚ SimphonyPosApi_TmedDetailItemEx ppTmedDetailEx‚ String[]& ppVoucherOutput‚ String payCommandString‚ String tenderExtraInfo‚ PayableBase pData),
06/05/20 05:39:34.999, 5, 0,API         ,       10,Simphony Pos Api: POS API: Error in payment module. Error Message EError Ids Driver Comms Error.,
06/05/20 05:39:34.999, 5, 0,API         ,       10,Simphony Pos Api: EError Ids Driver Comms Error.,
06/05/20 05:39:35.000, 5, 4,API         ,       10,Error: EError Ids Driver Comms Error.. StackTrace -    at SimphonyPosApi.TSOPS.CommitPayment(GuestCheck check‚ SimphonyPosApi_TmedDetailItemEx ppTmedDetailEx‚ String[]& ppVoucherOutput‚ String payCommandString‚ String tenderExtraInfo‚ PayableBase pData)
   at SimphonyPosApi.TSOPS.AddToExistingCheckEx(String vendorCode‚ SimphonyPosApi_GuestCheck& pGuestCheck‚ SimphonyPosApi_MenuItem[]& ppMenuItems‚ SimphonyPosApi_ComboMeal[]& ppComboMeals‚ SimphonyPosApi_SvcCharge& pServiceChg‚ SimphonyPosApi_Discount& pSubTotalDiscount‚ SimphonyPosApi_TmedDetailItemEx& pTmedDetailEx‚ SimphonyPosApi_TotalsResponse& pTotalsResponse‚ String[]& ppCheckPrintLines‚ String[]& ppVoucherOutput),
06/05/20 05:39:35.433, 5, 3,API         ,       10,Simphony POS API error message: EError Ids Driver Comms Error.‚ Stack trace:    at SimphonyPosApi.TSOPS.CommitPayment(GuestCheck check‚ SimphonyPosApi_TmedDetailItemEx ppTmedDetailEx‚ String[]& ppVoucherOutput‚ String payCommandString‚ String tenderExtraInfo‚ PayableBase pData)
   at SimphonyPosApi.TSOPS.AddToExistingCheckEx(String vendorCode‚ SimphonyPosApi_GuestCheck& pGuestCheck‚ SimphonyPosApi_MenuItem[]& ppMenuItems‚ SimphonyPosApi_ComboMeal[]& ppComboMeals‚ SimphonyPosApi_SvcCharge& pServiceChg‚ SimphonyPosApi_Discount& pSubTotalDiscount‚ SimphonyPosApi_TmedDetailItemEx& pTmedDetailEx‚ SimphonyPosApi_TotalsResponse& pTotalsResponse‚ String[]& ppCheckPrintLines‚ String[]& ppVoucherOutput)
   at SimphonyPosApi.TransactionServicesClass.AddToExistingCheckEx(String vendorCode‚ SimphonyPosApi_GuestCheck& pGuestCheck‚ SimphonyPosApi_MenuItem[]& ppMenuItems‚ SimphonyPosApi_ComboMeal[]& ppComboMeals‚ SimphonyPosApi_SvcCharge& pServiceChg‚ SimphonyPosApi_Discount& pSubTotalDiscount‚ SimphonyPosApi_TmedDetailItemEx& pTmedDetailEx‚ SimphonyPosApi_TotalsResponse& pTotalsResponse‚ String[]& ppCheckPrintLines‚ String[]& ppVoucherOutput)
   at SimphonyPosApi_Web.SimphonyPosAPIWeb.AddToExistingCheckEx(AddToExistingCheckExRequest request‚ String vendorCode)
   at SimphonyPosApi_Web.SimphonyPosAPIWeb.AddToExistingCheckEx(String vendorCode‚ String& pGuestCheck‚ String& ppMenuItems‚ String& ppComboMeals‚ String& pSvcCharge‚ String& pSubTotalDiscount‚ String& pTmedDetail‚ String& pTotalsResponse‚ String& ppCheckPrintLines‚ String& ppVoucherOutput),

Any sort of help would be appreciated !

Thank you
 
For the people who may be facing the issue in future, we found the issue is with OPERA PMS system and the running version was 5.5.0.27. As per the observations we found that the version having a bug and was resolved in 5.5.0.27 (2) which is interim 2. Patch is attached to the ticket in case if someone need.
 
 https://files.engineering.com/getfile.aspx?folder=f16a30b0-9afc-4be1-90ff-8eb597324d13&file=p30440615_500500_Generic.zip
Hi Dananjaya,

did you manage to get this working?
as we are working on a simmilar project, we are struggeling to get the opera enchance interface posting activated on sending the Tender through the transaction service api.
Also we saw that your log files are much more detailed, how can we activate such?

any guidance would be really appriciated.

Best Regards, Joost
 
Open the load handlers text file in the same directory as the egateway logs.

Change the number after the API module from 0 to 5. That will increase the log verbosity to the maximum.

Do you want some custom SIM scripts developed. Contact me via my website
 
Hi CathalMF,

thanks got the same logging level now.
It looks exactly the same as above, but without the error, but no activation of the opera interface, or opera posting.

Best Regards,

Joost
 
Hi Joost Splinter,

Yes.. It was resolved. The issue was with OPERA PMS version. Otherwise everything in ORACLE PATT configuration document is straight forward and working. My OPERA PMS version was 5.5.0.27 and with that version PATT was not working. So we upgraded the system to 5.5.0.27 (2) which is interim 2 and all started working like charm.

That was the solution for me.

Hope it would help you as well.
Thameera
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top