I'm trying to use the SITA Web Services to add an emergency contact to a booking. I'm using this XML, but I keep getting "013 - ACTION" error
<OTA_AirBookModifyRQ xmlns:="http://www.opentravel.org/OTA/2003/05" TransactionIdentifier="" Version="2003.5.0">
<AirBookModifyRQ BookingReferenceID="JKYZJ" ModificationType="5">
<TravelerInfo>
<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest SSRCode="PCTC" Status="11" TravelerRefNumberRPHList="1">
<Airline Code="XS"></Airline>
<Text>DOCTOR DR/XS222H.SISTER</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>
</TravelerInfo>
</AirBookModifyRQ>
The reason you're getting "013 - ACTION" is that you are specifying "11" (which means NN -Need) as the status. Change the status to "26", which means HK - Hold Confirmed).
Note also, for PCTC the element must be in a specific format to be correctly accepted by reservation system. See the Agent Reservation guide for more details on this.
Related
step 1:
request create inbound shipment plan api.
http://docs.developer.amazonservices.com/en_US/fba_inbound/FBAInbound_CreateInboundShipmentPlan.html
response:
[
//usualy 1-5 plan has been reply,no any one plan contain full of my items.
//the plan 1
{
"ShipToAddress": {
... ignore address detail
},
"ShipmentId": "FBA15CQQTFFM",
"DestinationFulfillmentCenterId": "PHX3",
"LabelPrepType": "NO_LABEL",
"Items": [
//item list, it is alway not full of my provide items.
{}
]
},
//the plan2, and more plan
{},{},...
]
step 2:
choose max count items of plan for create inbound shipment.
i cant edit item in this step.
http://docs.developer.amazonservices.com/en_US/fba_inbound/FBAInbound_CreateInboundShipment.html
step 3:
update inbound shipment plan for add all of item to this plan.
http://docs.developer.amazonservices.com/en_US/fba_inbound/FBAInbound_UpdateInboundShipment.html
request url: https://mws.amazonservices.com/FulfillmentInboundShipment/2010-10-01
request params:
SellerId=xxxxxxxxxxxxxxxxxx
AWSAccessKeyId=xxxxxxxxxxxxxxxxxxx
SignatureVersion=2
SignatureMethod=HmacSHA256
Version=2010-10-01
InboundShipmentHeader.ShipmentStatus=WORKING
ShipmentId=FBA15CR0QLLR
InboundShipmentHeader.ShipmentName=2018-05-16-AAA
InboundShipmentHeader.ShipFromAddress.Name=Wang%20Jingang
InboundShipmentHeader.ShipFromAddress.AddressLine1=396haozhiyihao
InboundShipmentHeader.ShipFromAddress.AddressLine2=
InboundShipmentHeader.ShipFromAddress.City=Guangzhou
InboundShipmentHeader.ShipFromAddress.DistrictOrCounty=
InboundShipmentHeader.ShipFromAddress.StateOrProvinceCode=Guangdong
InboundShipmentHeader.ShipFromAddress.CountryCode=CN
InboundShipmentHeader.ShipFromAddress.PostalCode=510080
InboundShipmentItems.member.1.SellerSKU=A71231811510311-
InboundShipmentItems.member.1.QuantityShipped=20
InboundShipmentItems.member.2.SellerSKU=A5W3E3112HE0
InboundShipmentItems.member.2.QuantityShipped=80
InboundShipmentItems.member.3.SellerSKU=A71231811540010-
InboundShipmentItems.member.3.QuantityShipped=20
InboundShipmentItems.member.4.SellerSKU=A71231811540011-
InboundShipmentItems.member.4.QuantityShipped=30
InboundShipmentItems.member.5.SellerSKU=A71231811515411-
InboundShipmentItems.member.5.QuantityShipped=20
InboundShipmentItems.member.6.SellerSKU=J8S109225HE90
InboundShipmentItems.member.6.QuantityShipped=10
InboundShipmentItems.member.7.SellerSKU=J8S109225HE92
InboundShipmentItems.member.7.QuantityShipped=33
InboundShipmentItems.member.8.SellerSKU=J8S109225HE93
InboundShipmentItems.member.8.QuantityShipped=10
InboundShipmentItems.member.9.SellerSKU=J8S109225ND90
InboundShipmentItems.member.9.QuantityShipped=8
InboundShipmentItems.member.10.SellerSKU=J8S109225ND91
InboundShipmentItems.member.10.QuantityShipped=12
InboundShipmentItems.member.11.SellerSKU=J8S109225ND92
InboundShipmentItems.member.11.QuantityShipped=17
InboundShipmentItems.member.12.SellerSKU=J8S109225ND93
InboundShipmentItems.member.12.QuantityShipped=14
InboundShipmentItems.member.13.SellerSKU=J8S109225ND94
InboundShipmentItems.member.13.QuantityShipped=5
InboundShipmentItems.member.14.SellerSKU=J8S109225QC90
InboundShipmentItems.member.14.QuantityShipped=10
InboundShipmentItems.member.15.SellerSKU=J8S109225QC91
InboundShipmentItems.member.15.QuantityShipped=5
InboundShipmentItems.member.16.SellerSKU=J8S109225QC92
InboundShipmentItems.member.16.QuantityShipped=9
InboundShipmentHeader.AreCasesRequired=false
Action=UpdateInboundShipment
Timestamp=2018-05-18T13%3A08%3A04%2B08%3A00
Signature=LCFu1NoX1QnENH1oCFEbwsXy1JVh7QNjpe2enGj258Q%3D
sometime success.
sometime fail, and tell me [skuType=MSKU, sku=..., reason=NOT_ELIGIBLE_FC_FOR_ITEM.]
do not change anything.
replicated 1-3.
sometime success.
sometime fail, and tell me [skuType=MSKU, sku=..., reason=NOT_ELIGIBLE_FC_FOR_ITEM.]
imcomprehensible it is, sku maybe not equal with last time. it is random, maybe one, mabe two.
can you tell me waht wrong?
HOW CAN I TO DO, MAKE ALL ITEMS IN ONE PLAN?
I got the sam error before, I found a ref.:
https://help.scanpower.com/support/solutions/articles/11000037578-what-does-the-not-eligible-fc-for-item-error-mean-
FYI, sure, I have a SKU, when creating inbound shipment, to old account, it's OK, but to new account, API will reponse the error you said.
Unfortunately, this error is coming directly from Amazon. There is a product in your shipment that is causing a conflict with the inbound shipping and/or the fulfillment center, but Amazon does not give us any indication as to the specific issue.
We have contacted Amazon and they suggest each seller experiencing this issue contact Seller Support for more information on the error. Please let them know that you are listing said item(s) via their MWS API and are receiving the following message: (insert the text of YOUR SPECIFIC ERROR MSG HERE what you see below is an example)
Invalid Items found - ShipmentId [FBA53HXYFX] MerchantCustomerId [A2WOJIKNACJWE4] InvalidItems[ (skuType=MSKU, sku=2016-11-30-B0006SGYS8-1099, reason=NOT_ELIGIBLE_FC_FOR_ITEM)]Shipment Id: FBA53HXYFXRequest Id: fb04a1f9-721f-4be3-a9c7-ba4063c13f69
I want to define a Ring Group that, when called, rings one extension and one external number (mobile phone). What is the best way to achieve that?
Right now only the extension is called. So just entering an external number in the Destination field does not work, the logs say
[NOTICE] switch_cpp.cpp:1376 [ring groups][call forward all] user_exists id <mobileno> <domainname>
and later
[DEBUG] switch_ivr_originate.c:3865 Originate Resulted in Error Cause: 27 [DESTINATION_OUT_OF_ORDER]
It will check all calls using the dialplan to see if the destination is a local number for an external number it should say user_exists false every time.
This [DESTINATION_OUT_OF_ORDER] indicates that it may not have found a matching outbound route that matches the number of digits of the external phone number. Or it may mean that your carrier rejected the call maybe didn't like the caller ID that was sent. Easiest thing to try is attempt it with an outbound rout to different carrier.
In case you weren't aware FusionPBX 4.4 was release on 5 April 2018. Instructions to upgrade are post on docs.fusionpbx.com. Search term upgrade (version upgrade).
I am using square_connect ruby gem to refund payments.
body =
#<SquareConnect::CreateRefundRequest
#amount_money=#<SquareConnect::Money #amount=200, #currency="USD">,
#idempotency_key="be70cc12-28dd-4168-96ea-6eb78f299207",
#tender_id="asdkasdkakdakdakda">
All other parameters are just as intended. I have changed Tender key too.
result = api_instance.create_refund(authorization, location_id, transaction_id, body)
This gives me INTERNAL SERVER ERROR.
ETHON: performed EASY effective_url=https://connect.squareup.com/v2/locations/BP6GXQNEANA9B/transactions/b2fd4689-af1b-40a4-b706-aafd592e1111/refund response_code=500 return_code=ok total_time=1.883598
SquareConnect::ApiError: Internal Server Error - {"errors":[{"category":"API_ERROR","code":"INTERNAL_SERVER_ERROR","detail":"An internal error has occurred, and the API was unable to service your request."}]}
Are you sure that your tender_id matches a tender you want to refund? 500 isn't the correct response, but it seems like you are likely not selecting a correct tender to refund.
Also you should look into upgrading your SDK to the latest version.
This is a major bug in the Square Connect API. I was actually trying with a wrong transaction ID, instead of getting something like "Incorrect Transaction ID" I was getting 500 Internal Server Error.
I have been using Stripe, Payflow. Authorize.net, Braintree and Moneris API for almost 2 years now but I have never received a 500 Internal server error for a wrong transaction Id. So Square needs to address it on urgent basis.
How to change the default currency in Odoo 10.0 without exchange rate ?
I tried the method from http://www.surekhatech.com/blog/change-currency-in-pos-in-odoo-10
But I got the errors such as
When in POS, I tried to "Validate Closing & Post Entries", I got Odoo warning There is no account defined on the journal Cash for Profit involved in a cash difference and can not post the POS transaction.
While in POS checkout, the unsolved problems on https://www.odoo.com/forum/help-1/question/10-0-a-transaction-can-t-have-a-0-amount-none-error-on-validate-odoo-pos-payment-121554
How to fix them ?
I also includeed the recorded screen on youtube at : https://youtu.be/IahubLwnDDE
In solution of your 1st error you need to define opening and closing account in payment methods define in POS front. For that POS >> Configuraion >> Payment Methods. In that choose payment method which active in POS and from that there are 2 fields name "Default Debit Account" and "Default Credit Account" define accounts here. By adding accounts here your 1st error is resolved. Don't know much about second error if you know then late me know. :)
here i have got one issue.can some one please help me to resolve this.
i was trying to extract some data to DS 0FI_AP_6...
then in InfoPackage Monitor I can see like..
-->Requests (messages): Everything OK
-->Extraction (messages): Everything OK
-->Transfer (IDocs and TRFC): Missing messages or warnings
-->Info IDoc 2 : sent, not arrived ; IDoc ready for dispatch (ALE service)
Data Package 1 : 23752 Records arrived in BW
Data Package 2 : 15216 Records arrived in BW
Request IDoc : Application document posted
Info IDoc 1 : Application document posted
Info IDoc 3 : Application document posted
Info IDoc 4 : Application document posted
-->Processing (data packet): Everything OK
Data Package 1 ( 38672 Records ) : Everything OK
in Status Menu I am having message like...
Missing data packages for PSA Table
Diagnosis
Data packets are missing from PSA Table . BI processing does not
return any errors. The data transport from the source system to BI was
probably incorrect.
Procedure
Check the tRFC overview in the source system.
You access this log using the wizard or following the menu path
"Environment -> Transact. RFC -> Source System".
Error handling:
If the tRFC is incorrect, resolve the errors listed there.
Check that the source system is connected properly to BI. In
particular, check the remote user authorizations in BI.
Please suggest me how to resolve this issue...
thanks in advance for your help and quick reply is much appreciated.
But what the worst thing is I deleted the infopackage in PSA by mistake.
In the normal case, if I repeat the process again, the delta load would be OK, but now the delta load remains error.
so gurus,
1. how can I restart my delta loading correctly?
2. I want to modify the timestamp in the delta table, but how to do it ?
Go to T-Code RSA7 in the source system. This will tell you the date/timestamp that the delta is set to. If the date was changed to a range that no longer works then you will need to re-initialize the datasource in the BW system side. However, the Delta date may still be fine becauase it may have never been changed when you tried to first do your load because of the connection issues.
You can create a new infopackage and set the update to Initialize Datasource with Data Transfer. This will essentially run a full load from the datasource and then reset the delta pointer date/timestamp to when you ran it. This way you will capture all the data that you needed and anything that was already in the PSA should be overwritten.
Also note that you should delete or set the request status to red on the previous request that may contain bad data in the PSA.
From the original error it seems like you are having an RFC connection issue between the datasource and BW. Contact your BASIS support and have them check the connection to make sure it is good. To ensure that your datasource is extracting properly you can run t-code RSA3 on it in the source system. This will ensure that the extraction of data is working properly.