Quantcast
Channel: SCN: Message List - SAP Business One Integration Technology
Viewing all 973 articles
Browse latest View live

Re: SAP business one mobile client dashboards won't show


Re: HTTP Call or Web Service

What is the best introductory resource for learning B1i?

$
0
0

I have been asked to begin learning how to use B1if to do more for our clients, but I can't find any introductory information on how to start. Are there any resources available to start learning how to do things with it?

"Scenario Package is not in your namespace"

$
0
0

I was watching a video to try and learn how to use the B1i Scenario Package Design tool, and made a mistake (I pressed plus too many times in step design) I then tried to delete some of the steps, but I continually got an error telling me "Scenario package is not in your namespace."

 

I literally just created this scenario package. Why am I getting this error?

 

I tried logging out and logging back in, and it let me delete the package, but now it's still showing up on "Step Design," and it says "Read-Only Mode" and won't let me edit it.

Re: HTTP Call or Web Service

$
0
0

Hi Antonio,

 

I assume the webservices you want to communicate with are REST webservices, and not SOAP?

 

The naming of the atoms is a bit confusing, but use the Call web service atom for SOAP webservices, and the Call HTTP atom for REST webservices.

 

To make matters a bit more confusing, you can use the Call HTTP atom also for SOAP, but that's a lot more work.

Re: (-105) Unable to initialize OBServerDLL.dll

Re: "Scenario Package is not in your namespace"

$
0
0

Hi Dallin,

 

Maybe your scenario is active and changes are not allowed with the scenario active.

Go to the Scenarios page -> Control option in left menu and look if your scenario is active, if yes, deactive it and try make your changes again.

 

Hope it helps.

 


Best regards,

Diego Lother


View Diego Lother's profile on LinkedIn

Re: Security Error on Iphone Sap Business One Application 1.11.1SAP

$
0
0

I have follow all the steps described on the notes, I'm able to connect with Android devices but not with IOS, it say that there's a certificate error.

I did the troubleshooting on IF with my IPAD info, and everything is ok.

Why I can connect with Android and not with IOS?

 

Please help me out.

 

Regards.


URL Request

$
0
0

Hello

I’m trying to understand webservices with B1IF. I followed the examples and create a scenario with the query ‘select CardCode, DocNum, Doctotal from ORDR where DocStatus = ‘O’’. In test mode the scenario works fine and I get the results of the query. Now I want to test the scenario outside B1IF. I understand that SOAPUI is a good tool for it. But where can I find the URL for the request in my package, so I can get the same results outside B1IF as in the test mode of the scenario.

 

regards Dan

Re: URL Request

Re: URL Request

$
0
0

Hi Dan

Have you already tried to create your WSDL file? If not check this:

How to consume B1if Web Services with HTTPS by DotNet?

Once you got it you can go the element: 'wsdl:portType' and in the 'name' attribute is your URL. In child elements 'wsdl:operation' you can check what are the names of your web methods.

In general this URL is similar to this one: ipostep_vP.001sap0011.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc

Please mind that '001sap0011' is the system Id (from SLD) which is assigned to your scenario as a sender system.

btw

I think that you need to create WSDL file in order to be able to test your scenario using SOAP UI - at least that's what I do.

 

Kind regards,

Radek

Re: URL Request

$
0
0

hi Radek

 

I generate the wsdl file and found the 'url' like yours:

<wsdl:portType name="ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc">.

But it looks to me not the kind of url that I know, missing Ip adress?

In SoapUI I get the error:

"Error loading [file:/C:/Program%20Files/SmartBear/SoapUI-5.2.1/bin/ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc]: java.io.FileNotFoundException: C:\Program Files\SmartBear\SoapUI-5.2.1\bin\ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc (The system cannot find the file specified)"

 

What do I miss or what do I wrong?

 

I past the whole WSDL here below.

 

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

  <wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="urn:ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc" name="ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc" tns:force="" http:force="" soap:force="" xsd:force="">

  <wsdl:documentation>

  WSDL interface-definition generated by B1iP for the IPO-Step + port &apos;ipostep:/vP.0010000112.in_WCSX/com.sap.b1i.vplatform.runtime/INB_WS_CALL_SYNC_XPT/INB_WS_CALL_SYNC_XPT.ipo/proc#Ip&apos;.

  If your development tool of choice rejects to use this generated WSDL-file, please do remove the various artificial attributes &apos;xxx:force...&apos; out of

  the root-element &apos;wsdl:definitions&apos;. These attributes do not comply to the WSDL 1.1 specification, but are an unavoidable generation-artefact!

  </wsdl:documentation>

  <wsdl:types>

  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

  <xs:element name="Aufragstatus" type="AufragstatusType">

  <xs:annotation xmlns:bfa="urn:com.sap.b1i.bizprocessor:bizatoms">

  <xs:documentation>Root element for the document</xs:documentation>

  </xs:annotation>

  </xs:element>

  <xs:complexType xmlns:bfa="urn:com.sap.b1i.bizprocessor:bizatoms" name="AufragstatusType">

  <xs:annotation>

  <xs:documentation>Automatically generated complex type comprising the whole document for the purpose of schema re-use</xs:documentation>

  </xs:annotation>

  <xs:sequence>

  <xs:element name="Auftragsnummer" form="unqualified" type="xs:string"></xs:element>

  </xs:sequence>

  </xs:complexType>

  </xs:schema>

  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

  <xs:element name="Status" type="StatusType">

  <xs:annotation xmlns:bfa="urn:com.sap.b1i.bizprocessor:bizatoms">

  <xs:documentation>Root element for the document</xs:documentation>

  </xs:annotation>

  </xs:element>

  <xs:complexType xmlns:bfa="urn:com.sap.b1i.bizprocessor:bizatoms" name="StatusType">

  <xs:annotation>

  <xs:documentation>Automatically generated complex type comprising the whole document for the purpose of schema re-use</xs:documentation>

  </xs:annotation>

  <xs:sequence>

  <xs:element name="txt" form="unqualified" type="xs:string"></xs:element>

  <xs:element name="Artikel" form="unqualified" type="xs:string"></xs:element>

  <xs:element name="Artikelbezeichnung" form="unqualified" type="xs:string"></xs:element>

  <xs:element name="Offene_Menge" form="unqualified" type="xs:string"></xs:element>

  <xs:element name="Lieferdatum" form="unqualified" type="xs:string"></xs:element>

  </xs:sequence>

  </xs:complexType>

  </xs:schema>

  </wsdl:types>

  <wsdl:message name="Aufragstatus">

  <wsdl:part name="body" element="Aufragstatus"></wsdl:part>

  </wsdl:message>

  <wsdl:message name="Status">

  <wsdl:part name="body" element="Status"></wsdl:part>

  </wsdl:message>

  <wsdl:portType name="ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc">

  <wsdl:operation name="Z.WSOrderStatus">

  <wsdl:input message="tns:Aufragstatus"></wsdl:input>

  <wsdl:output message="tns:Status"></wsdl:output>

  </wsdl:operation>

  </wsdl:portType>

  <wsdl:binding name="ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc_SoapBinding" type="tns:ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc">

  <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"></soap:binding>

  <wsdl:operation name="Z.WSOrderStatus">

  <soap:operation soapAction=""></soap:operation>

  <wsdl:input>

  <soap:body use="literal"></soap:body>

  </wsdl:input>

  <wsdl:output>

  <soap:body use="literal"></soap:body>

  </wsdl:output>

  </wsdl:operation>

  </wsdl:binding>

  <wsdl:service name="ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc_Service">

  <wsdl:port name="ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc_SoapBinding_HTTP" binding="tns:ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc_SoapBinding">

  <soap:address location="http://LAB-DEM01.localdomain:8080/B1iXcellerator/exec/soap/vP.0010000112.in_WCSX/com.sap.b1i.vplatform.runtime/INB_WS_CALL_SYNC_XPT/INB_WS_CALL_SYNC_XPT.ipo/proc"></soap:address>

  </wsdl:port>

  <wsdl:port name="ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc_SoapBinding_HTTPS" binding="tns:ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc_SoapBinding">

  <soap:address location="https://LAB-DEM01.localdomain:8443/B1iXcellerator/exec/soap/vP.0010000112.in_WCSX/com.sap.b1i.vplatform.runtime/INB_WS_CALL_SYNC_XPT/INB_WS_CALL_SYNC_XPT.ipo/proc"></soap:address>

  </wsdl:port>

  </wsdl:service>

  </wsdl:definitions>

Re: URL Request

$
0
0

Hi Dan

Please check location in soap:address in wsdl:port element:

<wsdl:port name="ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc_SoapBinding_HTTP" binding="tns:ipostep_vP.0010000112.in_WCSX_com.sap.b1i.vplatform.runtime_INB_WS_CALL_SYNC_XPT_INB_WS_CALL_SYNC_XPT.ipo_proc_SoapBinding">      <soap:address location="http://LAB-DEM01.localdomain:8080/B1iXcellerator/exec/soap/vP.0010000112.in_WCSX/com.sap.b1i.vplatform.runtime/INB_WS_CALL_SYNC_XPT/INB_WS_CALL_SYNC_XPT.ipo/proc"/></wsdl:port>

Kind regards,

Radek

Re: SAP B1 and python

Re: B1iSN/B1if:BizFlow:Producing multiple inbound B1 objects


Re: Security Error on Iphone Sap Business One Application 1.11.1SAP

$
0
0

Dear Juan, others,

 

I'm closing this old thread now. for recent issues please create a new question in this space.

 

For your iOS device, it looks like an issue with installing the certificate.

 

Best, Peter

Customer reference field in business one mobile

$
0
0

Hello,

 

Can anyone tell me if it's possible to encode a customer reference (oqut.numatcard) in the business one mobile application (1.11.6).

 

Our customer is in SBO 9.0 PL 12 (SQL) and Business One Mobile 1.11.6

 

Seems obvious that it should be there ...

 

Thanks for your replies.

 

Vincent

Re: Basic getting value from SQL Call

$
0
0

Hello Antonio,

 

proceed the changes on image attached...pastedImage_1.png

It will be like this:

<xsl:template name="transform">

<xsl:variable name="DocEntry" select="/vpf:Msg/vpf:Body/vpf:Payload[@id='atom2']/jdbc:ResultSet/jdbc:Row/jdbc:DocEntry"/>

 

<Sql>UPDATE mocrm_qut1 set Status='X' Where DocEntry = <xsl:value-of select="$DocEntry"/></Sql>

</xsl:template>

 

 

Regards,

 

Leo

Re: Basic getting value from SQL Call

$
0
0

Thank you so much Leo and really sorry for bothering you, still cannot get it to work.

 

Here is my transformation atom3

 

But the result still NaN:

 

 

I´m very sorry for bothering you so much.

 

Thank you.

Re: Basic getting value from SQL Call

$
0
0

Antonio,

 

no problems, the atom3 needs to be after atom2 and before atom1 at process flow, could you please print me the flow? It seems that you create the new xsl atom before the atom that return the docentry value, instead after...

 

 

Regards,

 

Leo.

Viewing all 973 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>