hello.

i try to use

TYPE abap_trans_parmbind_tab contained in type-pool ABAP

inside xslt transformation.

the value is transported into xslt using PARAMETERS in CALL TRANSFORMATION.

my question is how to  declare sap:type  inside xslt

for this parameter ( param_tab ),

so i can use it's values in the transformation.

<xsl:param name="PARAM_TAB" sap:type="?"/>

thanks

Ronen

Thanks for your reply, Marius and Artem.

I have already tested with userids that have SAP_ALL, but I'm still getting the error. I also ran the authorization trace but I cannot see any error in the trace file.

I noticed that I'm only getting this error on ZMHF documents that were created by the test user ids  (ie. Change Manager test user). The test user ids  don't have SAP_ALL.

The ZMHF documents that I created using my userid (with SAP_ALL) doesn't show this error.

Regards,

Tess

Hello,

For the error, solution would be to implement the SAP Note 1671117

or
SPAM   > Extras   > Settings   > Import Queue
    > Uncheck "Check for active DDIC user"
(deactivate the DDIC check in SPAM); which is not possible in current scenario as SPAM is locked.

SAP Note 1671117 contains quite large number corrections to implement manually.

So the best way would be to restore the system and start the the import again after unchecking the DDIC Check.

Regards,

David

Dear All,

i've check and there is an enhancement in FAGLL03, and now i need abaper to understand the enhancement.

Thank tou all for your support.

Best regards,

Iwan Siahaan

Hi Dwarakanath P

Please check and the close the Thread with correct and helpful answers

Regards

Kennedy

Hi Dwarakanath P

Please check and the close the Thread with correct and helpful answers

Regards

Kennedy

Dear Naga,

the query above  will query the 

Base Price from Jan-Dec,

Sales Prices from Jan-Dec,

Gross Profit from Jan-Dec.

but when I go to check the Trial Balance Report in SAP, the value of Base Price for year 2012 is different from this Base Price. Sale Prices also wrong, Gross Profit also wrong.

So it means , maybe i query data from the wrong place?

Best Regards,

Svay Tyvann

Hello Federico,

Check the pach in jcoPath --> C:\Program Files (x86)\SAP\SAP Business One DI API\JCO\LIB

and

The user must be B1i with license B1iINDIRECT_MSS and passwords between the bases and the settings should be the same.

https://websmp230.sap-ag.de/sap/support/notes/1619422

http://scn.sap.com/thread/1864248

Regards,

Marcelo Silva Santos

Hi Jonathan Brotto

Check with the Banking -- Banking Reports -- Payments Drafts Report

Regards

Kennedy

Troubleshooting on B1ic Version 9.0

1.1 The request dashboard does not exist.
Dashboard: /com.sap.b1.dashboards/0010000100.sap_dashboard_001.dab001/default.html
If this dashboard is newly imported, ensure that the SAP Business One EventSender Server has been started; then wait for several minutes and try again.

• Root cause: After installation of B1ic, the company is not listed in the SLD
• Solution: Please do the following
  • Stop B1i services (DI Proxy, EventSender and Integration)
  • Use below query to delete all entries of SLSP and SLSPP tables in SBO-COMMON database.
    • delete from SLSP
    • delete from SLSPP
  • Restart B1i services
  • In SAP Business One application login in each of the companies

Troubleshooting on B1ic Version 8.81,8.82

First test the B1DI and JDBC connection from the SLD (System Landscape Directory) in the Integration Framework for SAP Business One window.

1.1 Test Connection from the SLD to the defined SAP Business One database returns an error

• Common Error 1: -111 Unable to connect to SBO-COMMON
• Root cause: For the host server address a server name is used instead of a unique IP address and this name is not maintained in network configuration.
• Solution: Type in the IP address of the SAP Business One server. Logical names can be used. It’s important that the string you type here is the same string, that is used in the EventSender setup for this SAP B1 system (e.g. if you used the logical name in EventSender you need to type in here also the logical name).

        Note:Before doing this step it is recommended to first address the network configuration if possible

• Common Error 2: Unknown host
• Root cause: Incorrect diProxyhost.
• Solution: You should specify the IP address of the server where the DI Proxy is running.

• Common Error 3: -107 - Wrong B1i password/8.81: Internal error (500)
• Root cause: Incorrect B1i password (-107 - Wrong B1i password)/8.81: Internal error (500)
• Solution: The B1i password must be set up and changed in SAP Business One. In case of doubt you should reset the B1i password and test again.

• Common Error 4: 8012 Company version mismatch
• Root cause: Mismatch between DI, SBO-Common and Company database versions.
• Solution: DI: go to Start -> Run and type %temp%. Locate the folder SM_OBS_DLL and delete/rename it. Then open the SAPBobsCOM.dll -> right click Properties and ensure the version is 8.8 PL12 or higher.
  SBO-Common: query the table SINF (select Version, PatchLevel from SINF) and ensure the version is 880230 and patch level is 12 or higher.
  If it's not correct run the SBO-Common upgrader from PL12 or higher again.
  Company DB - query the table CINF (select Version from CINF) and ensure the version is 880230 or higher.

• Common Error 5: -103 Failed to connect
• Root cause: Incorrect company selected/company not upgraded.
• Solution: Ensure in the company field the correct database is used. Also ensure the database has been upgraded to the correct patch. The database that is installed when you install B1iC is called B1if. This is not a normal SAP Business One database so should update the SLD to an actual SAP Business One database name.

• Common Error 6: 100000013 - Wrong B1i license or 100000048 – No SAP licenses
• Root cause: License has not been assigned.
• Solution: Ensure the licenses B1iINDRIECT_MSS and B1ihave been assigned to the B1i user.

• Common Error 7: Java.lang.NullPointerException
• Root cause: JCO not installed or path incorrect after warning was ignored during setup.
• Solution: When installing the DI API ensure you select the JCO component for installation – you can click on the Custom installation to do this. Also ensure the JcoPath is correctly set in the diproxyserver.properties.
• Solution 2: Uninstall the DI API and Reinstall the DI API from the B1_SHR folder on the B1ic computer and then follow solution 1.

• Common Error 8: Nested exception: java.rmiConnectException: Connection refused to host: 12.13.14.156: nested exception is: java.net.ConnecdtException: Connection refused connect
• Root cause 1: Problem with the diProxyHost or diProxyport.
• Solution 1: In the field diProxyhostreplace the computer name with the machine's IP address. Also add this IP to the PROXYHOME entry in the diproxyserver.properties file (C:\Program Files\SAP\SAP Business One Integration\DIProxy).
• Root cause 2: B1if and DI Proxy are located on different machines.
• Solution 2: If this is the case the firewall could be the root cause. Ensure port 2099 of the DI Proxy is enabled.
• Root cause 3: DI Proxy service is not started.
• Solution 3: Ensure the DI Proxy service is started.

• Common Error 9: ‘com.sap.b1i.adapter.dia.exception.ConnectionFailedException: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.sap.smb.sbo.api.SBOCOMUtil .’
• Root cause 1: The JCO path is not correctly set in the diproxyserver.properties.
• Solution 1: Locate the Java Connection for SAP Business One DI API (default path is C:\Program Files\SAP\SAP Business One DI API\JCO\LIB). Enter this path with double back-slashes in the JCO patch of the diproxyserver.properties file (default path is C:\Program Files\SAP\SAP Business One Integration\DIProxy).
• Root cause 2: Relevant *.Jar files from the DI API are no longer in the file system.
• Solution 2: Reinstall DI API from the same version as SAP Business One application. The check if sboapi.jar and sbowrapper.jar files were created in C:\Program Files\SAP\SAP Business One DI API\JCO\LIB folder.

• Common Error 10: (126) Unable to load OBServerDLL.dll
• Root cause 1: OBServerDLL.dll file is not stored in the temporary folder.
• Solution 1: Copy all files from OBServer folder under SAP Business One DI API folder to:
  1.1 C:\Windows\Temp\SM_OBS_DLL\882068 (create this folder)
  1.2 (%temp% folder) \SM_OBS_DLL\882068
• Root cause 2: TEMP and TMP Environment Variables are not correctly configured.
• Solution 2: Change the Environment Variables:
  2.1 in the User variables section to %USERPROFILE%\AppData\Local\Temp
  2.2 in the System variables section to %SystemRoot%\TEMP

• Common Error 11: ‘XCE001 Nested exception: java.rmi.RemoteException: Error on completion of HTTPS-roundtrip: java.net.SocketException: Connection reset; nested exception is: java.net.SocketException: Connection reset’
• Root cause1: diProxyhost field in the company detail in the SLD is pointing to another server that does not host the DI Proxy.
• Solution1: In the field diProxyhostreplace the value with the server that hosts the DI Proxy.
• Root cause2: SAP Business One DI Proxy Service is not running.
• Solution2: Restart SAP Business One DI Proxy Service.

1.2 Error HTTP 401

First test the B1DI and JDBC connection from the SLD (System Landscape Directory) in the Integration Framework for SAP Business One window.

• Root cause 1: Incorrect SAP Business One Version installed and warning was ignored during set-up.
• Solution 1: Ensure you are not trying to connect to the Cockpit/Dashboard when running SAP Business One 8.8 PL11 or lower.

• Root cause 2: User selected an old JCO folder during installation and warning was ignored during set-up.
• Solution 2: Change the DIProxy properties files to point to correct JCO path and restart the DI Proxy services. To do this open the file (default location is C:\Program Files\SAP\SAP Business One Integration\DIProxy\diproxyserver.properties) and update the field JCOPATH.

        Note: 8.8 PL2 and B1iC 8.81 validates the DI version and if incorrect a warning will appear in the setup process and will be included in the install_log.ini file.

• Root cause 3: B1i user is not a super user.
• Solution 3: Ensure in SAP Business One the B1i user is set as a super user.

• Root cause 4: User is locked after 5 consecutive failed attempts.
• Solution 4: See Note 1556041 on how to resolve this.

• Root cause 6: DI Proxy port conflict.
• Solution 6: Change the DI Proxy port in the SLD for the SAP Business One database (different to 2099, 2100 for example). Enter same port number in RMI_PORT property(before 8.81PL10 and 8.82PL03) or HTTPS_PORT property (from 8.81PL10 and 8.82PL03) of diproxyserver.properties file (folder Program Files/SAP/SAP Business One Integration/DIProxy). For B1iC 8.8 deactivate sap.Xcelsius package and activate sap.Xcelsius package.

• Root cause 7: localhost was not added to Trusted Sites.
• Solution 7: Add http://127.0.0.1 to Trusted Sites (Tools->Internet Options->Security tab->Trusted Sites)

1.3 Error HTTP 403 Forbidden - XCL198 HTTP access currently not allowed from remote clients, as B1iP runs in local-mode or safe-mode

• Root cause: You use localhost in the B1i Server address.
• Solution: Ensure instead of localhost you use the IP address or the server name to connect. Open the Integration Framework -> Maintenance -> Cfg Runtime and change the corresponding setting.

1.4 Error HTTP 404 not found/File not found

• Root cause 1: The user manager is used instead of the B1i user.
• Solution 1: Ensure the user B1i is used during setup and connection in the SLD and the B1i user has been correctly set up in SAP Business One.

• Root cause 2 :  Incorrect JDK installed for a 64bit environment.
• Solution 2: In 64bits machines you need to have JDK installed for both 32 and 64bits and point to both during the installation of B1ic.

• Root cause 3: There is an SQL server instance name.
• Solution 3: If you are using an SQL named instance make sure each instance uses a different TCP/IP port and, during the installation of the integration component, enter the server name as <server name> rather than <server name>\instance name.
• Note: PL08 and higher will provide regular support for named instances – see note 1621563

• Root cause 4: The IPO user was deactivated.
• Solution 4: Go to B1iP Control Center -> Configuration -> User Admin IPO-Steps – Toggle Activation for user B1iadmin and B1ipeer. Restart the Integration server and Event Sender service and retry.

• Root cause 5: The Proxy host was configured in the Event Sender set up.
• Solution 5: On Step 3/5 of the Event Sender set up ensure you do not configure Proxy Host or the Proxy Port.

• Root cause 7: The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error.
• Solution 7a: Ensure the correct company database appears in the SLD. Deactivate and re-activate the dashboard in SAP Business One’s General Settings.
• Solution 7b: Check the Message Log in the Integration Framework -> Monitoring for errors (Failure) connected to “Sender Trigger / Object” “500” (event to create SLD entry) or “120000008” (event to deploy dashboards)
• Solution 7c: Check the Queue Monitor in the Integration Framework -> Monitoring for pending processes – after installation / upgrade some post-installation processing time may be required (depending on various factors up to 2 minutes per B1 DB on slow systems)
• Solution 7d: Go to the B1iP Control Center -> Maintenance -> IPO-Step Status and check “Deactivated steps only to check whether any processes are halted. If so, the relevant error may be displayed – giving a hint for details that require fixing.Activate the deactivated steps – and press “Refresh” to see whether the steps can successfully be reactivated.

• Root cause 8: SQL Server/Tomcat Services have not been started.
• Solution 8: Ensure SQL Server//Tomcat Services are started:
  • - Click Start -> Control Panel -> Administrative Tools -> Services
  • - Locate the service name SQL Server (MSSQLSERVER) / Tomcat and ensure they are started

• Root cause 9: Https Port 8443 is being used by another program.
• Solution 9: Open https://localhost:8443 via the browser and ensure it is the home page of Apache Tomcat. If not, the 8443 port is occupied by another program. Disable the other program that is using port 8443 or assign another port to the other program.

1.5 Error HTTP 500 – Internal Error

• Root cause 1: The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error.
• Solution 1a: Ensure the correct company database appears in the SLD. Deactivate and re-activate the dashboard in SAP Business One’s General Settings.
• Solution 1b: Check the Message Log in the Integration Framework -> Monitoring for errors (Failure) connected to “Sender Trigger / Object” “500” (event to create SLD entry) or “120000008” (event to deploy dashboards)
• Solution 1c: Check the Queue Monitor in the Integration Framework -> Monitoring for pending processes – after installation / upgrade some post-installation processing time may be required (depending on various factors up to 2 minutes per B1 DB on slow systems)
• Solution 1d: Go to the B1iP Control Center -> Maintenance -> IPO-Step Status and check “Deactivated steps only to check whether any processes are halted. If so, the relevant error may be displayed – giving a hint for details that require fixing.Activate the deactivated steps – and press “Refresh” to see whether the steps can successfully be reactivated.

1.6 Error “The IPO-Step to create a cached authentication config-node for is not known”

• Root cause 1: Installation did not install the systems in the System Landscape directory.
• Solution 1: Run the EventSender setup. Or detach the database from SQL Server Management Studio. Refresh company list and attach the database once again in SQL. Click refresh in the Choose Company window in SAP Business One.

• Root cause 2: Scenario has not been activated
• Solution 2: Open the Integration framework -> Scenarios -> Scenario Package Control. For the sap.Xcelsius click Activate.

• Root cause 3: Changes made without restarting.
• Solution 3: If changes are made ensure Integration Service and Event Sender are restarted.

• Root cause 4: Internal functions / IPO steps may have been “deactivated”.
• Solution 4: Go to the B1iP Control Center -> Maintenance -> IPO-Step Status and check “Deactvated steps only” to check whether any processes are halted. If so, the relevant error may be displayed – giving a hint for details that require fixing. Activate the deactivated steps – and press “Refresh” to see whether the steps can successfully be reactivated.

1.7 Error “Action Cancelled”

• Root cause 1: SAP Business One integration service may be stopped.
• Solution 1: Ensure the SAP Business One integration service is running. Stop and start the service and retry.

• Root cause 2: Port 8080 is being used by another program
• Solution 2: Open http://localhost:8080 via the browser and ensure it is the home page of Apache Tomcat. If not, the 8080 port is occupied by another program. Disable the other program that is using port 8080 or assign another port to the other program.

        Note: From B1iC 8.81 PL05 to change the port you should follow the instructions in the AdministrationGuide_Integration_Component section 2.7

1.8 What is the username and password for explicit Authentication

      You will receive the prompt “The server xxxx at B1iP_ipo_/vP.001sap0004.in_HCSX/com.sap.b1i.vplatform.runtime/INB_HT_CALL_SYNC_XPT.ipo/proc requires a username and password”.

• Solution: If this occurs in SAP Business One you should restart the SAP Business One client.

1.9 The request dashboard does not exist.
Dashboard: /com.sap.b1.dashboards/0010000100.sap_dashboard_001.dab001/default.html
If this dashboard is newly imported, ensure that the SAP Business One EventSender Server has been started; then wait for several minutes and try again.

• Root cause 1: Cockpit not activated correctly
• Solution 1: Please do the following
  • Deactivate the cockpit in your Business One database - Disable My Cockpit and also disable cockpit in General Settings
  • Run EventSender Setup (in first step try to avoid using localhost or IP addresses), in third step press Test Connection, in fourth step make sure that your database is checked, press also Receiver button and then Test Connecion. Finish EventSender setup.
  • Click on SLD in the B1i Framwork and ensure connection to the Company databsae (B1DI and JDBC) is successful.
  • Go back to B1i Framework UI, click Scenarios in upper menu, then select Control in left menu and (re)activate Xcelsius scenario.
  • Restart EventSender service, Integration Service and Proxy services via Servies (Computer Management)
  • Now you can enable cockpit in your Business One database - enable cockpit in General Settings and then enable My Cockpit.

• Root cause 2: After installation of B1ic, the company is not listed in the SLD
• Please do the following
  • Stop B1i services (DI Proxy, EventSender and Integration)
  • Use below query to Delete all entries of SLSP and SLSPP tables in SBO-COMMON database
    • Delete from slsp
    • Delete from slspp
  • Restart B1i services
  • In SAP Business One application refresh the company list

1.10 Install SAP Business One Integration Service before enabling the dashboard widget

• Root cause: Previous Tomcat/B1ic installation exists.
• Solution: Remove the Integration component and any Tomcat deployment before you upgrade/reinstall again.

1.11 No Company database appears in the SLD

• Solution: De-activate and re-activate the sap.B1System scenario (B1i Framework UI, click Scenarios in upper menu, then select Control in left menu).

1.12 Error #2032 Connection type: XML Data

• Root cause 1: Incorrect setting in Server Manager
• Solution 1: Start "Server Manager"-> Under the "security information section, click on the Configure IE ESC" link and Turn off for Administrators.
  
  
• Root cause 2: Improper IE setting
• Solution 2: In toolbar of the Microsoft Windows Internet Explorer, choose Tools -> Internet Options. In the Settings section of the Advanced tab, navigate to the Security list, and deselect the checkbox Do not save encrypted pages to disk.

1.13 SAP Business One Integration Service authentication failed. Log off from the application; then log on and try again. If the problem persists, contact your system administrator.

• Root cause 1: The username or password contains a special character that is not supported by the B1i server. (e.g. “, &, ‘, <, >)
• Solution 1: Update the username or password so that it does not contain any of those special characters.
  
  
• Root cause 2: [hostname] is used in some configuration settings, and [ip-address] is used in others.
• Solution 2: Ensure you use exclusively either the [hostname] or the [ip-address] in all the following configuration settings:
  • Integration Framework > SDL > B1i Server > [company database] > B1DI > b1Server
  • Integration Framework > SDL > B1i Server > [company database] > JDBC > url
  • Integration Framework > SDL > B1i Server > HAnyforXcelsius > associatedSrvIP
  • EventSender Setup > Step 1 > DB Server Name
  • License Manager > Configure Security > DB Server
    
    
• Root cause 3: There are duplicate entries for the Company Database in Integration Framework > SLD.
• Solution 3: Remove the duplicate entries. Ensure the details for the remaining Company Database are correct. And restart the SAP Business One Integration Service if required.

1.14 Did not supply an appropriate user-ID integer (Param6).

• Root cause 1: The url property (SLD->company entry->JDBC section) for the company entry is not pointing to the correct Database.
• Solution 1: Change the url to point to the correct company database. It should look like:
  jdbc:sqlserver://[Server]:1433;integratedSecurity=false;databaseName=[company database name];selectMethod=cursor

1.15 Dashboard does not display the correct data (i.e year 3799 in the Fiscal Year Analysis in the Sales Analysis)

• Solution: Assign Groups to Dashboard Queries:
  1. Go to 'Tools->Queries->Query Manager' and select 'Manage Categories' button
  2. Select queries SAP_DASHBOARD_XXX_DABXXX_QUERY and assign desired Groups to them 

1.16 Cannot connect to B1i server.1.The remote server returned an error :(500) Internal server error.

• Common Error 1 : Cannot connect to SAP Business One Integration Service. Proceed as follows: 1. In the Microsoft "Services" window, ensure that this service has been started. 2. Log off from the application; then log on and try again.
• Root cause 1: Firewall is blocking connection from a client workstation to server
• Solution 1: Ensure firewall is not blocking ports 8080 and 8443 in the server 

• Root cause 2: sap.Xcelsius package is not active in Business One Integration Component.
• Solution 2: Go to Integration solution for SAP Business One -> Scenarios -> Control -> tick the check box for 'sap.Xcelsius' -> Activate -> OK

Troubleshooting on B1ic Version 8.8

First test the B1DI and JDBC connection from the SLD (System Landscape Directory) in the Integration Framework for SAP Business One window.

1.1 Test Connection from the SLD to the defined SAP Business One database returns an error

• Common Error 2: -111 Unable to connect to SBO-COMMON
• Root cause: For the host server address a server name is used instead of a unique IP address and this name is not maintained in network configuration.
• Solution: Type in the IP address of the SAP Business One server. Logical names can be used. It’s important that the string you type here is the same string, that is used in the EventSender setup for this SAP B1 system (e.g. if you used the logical name in EventSender you need to type in here also the logical name).

        Note:Before doing this step it is recommended to first address the network configuration if possible

• Common Error 2: Unknown host
• Root cause: Incorrect diProxyhost.
• Solution: You should specify the IP address of the server where the DI Proxy is running.

• Common Error 3: -107 - Wrong B1i password/8.81: Internal error (500)
• Root cause: Incorrect B1i password (-107 - Wrong B1i password)/8.81: Internal error (500)
• Solution: The B1i password must be set up and changed in SAP Business One. In case of doubt you should reset the B1i password and test again.

• Common Error 4: 8012 Company version mismatch
• Root cause: Mismatch between DI, SBO-Common and Company database versions.
• Solution: DI: go to Start -> Run and type %temp%. Locate the folder SM_OBS_DLL and delete/rename it. Then open the SAPBobsCOM.dll -> right click Properties and ensure the version is 8.8 PL12 or higher.
  SBO-Common: query the table SINF (select Version, PatchLevel from SINF) and ensure the version is 880230 and patch level is 12 or higher.
  If it's not correct run the SBO-Common upgrader from PL12 or higher again.
  Company DB - query the table CINF (select Version from CINF) and ensure the version is 880230 or higher.

• Common Error 5: -103 Failed to connect
• Root cause: Incorrect company selected/company not upgraded.
• Solution: Ensure in the company field the correct database is used. Also ensure the database has been upgraded to the correct patch. The database that is installed when you install B1iC is called B1if. This is not a normal SAP Business One database so should update the SLD to an actual SAP Business One database name.

• Common Error 6: 100000013 - Wrong B1i license or 100000048 – No SAP licenses
• Root cause: License has not been assigned.
• Solution: Ensure the licenses B1iINDRIECT_MSS and B1ihave been assigned to the B1i user.

• Common Error 7: Java.lang.NullPointerException
• Root cause: JCO not installed or path incorrect after warning was ignored during setup.
• Solution: When installing the DI API ensure you select the JCO component for installation – you can click on the Custom installation to do this. Also ensure the JcoPath is correctly set in the diproxyserver.properties.
• Solution 2: Uninstall the DI API and Reinstall the DI API from the B1_SHR folder on the B1ic computer and then follow solution 1.

• Common Error 8: Nested exception: java.rmiConnectException: Connection refused to host: 12.13.14.156: nested exception is: java.net.ConnecdtException: Connection refused connect’
• Root cause 1: Problem with the diProxyHost or diProxyport.
• Solution 1: In the field diProxyhostreplace the computer name with the machine's IP address. Also add this IP to the PROXYHOME entry in the diproxyserver.properties file (C:\Program Files\SAP\SAP Business One Integration\DIProxy).
• Root cause 2: B1if and DI Proxy are located on different machines.
• Solution 2: If this is the case the firewall could be the root cause. Ensure port 2099 of the DI Proxy is enabled.

• Common Error 9: ‘com.sap.b1i.adapter.dia.exception.ConnectionFailedException: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.sap.smb.sbo.api.SBOCOMUtil .’
• Root cause 1: The JCO path is not correctly set in the diproxyserver.properties.
• Solution 1: Locate the Java Connection for SAP Business One DI API (default path is C:\Program Files\SAP\SAP Business One DI API\JCO\LIB). Enter this path with double back-slashes in the JCO patch of the diproxyserver.properties file (default path is C:\Program Files\SAP\SAP Business One Integration\DIProxy).
• Root cause 2: Relevant *.Jar files from the DI API are no longer in the file system.
• Solution 2: Reinstall DI API from the same version as SAP Business One application. The check if sboapi.jar and sbowrapper.jar files were created in C:\Program Files\SAP\SAP Business One DI API\JCO\LIB folder.

1.2 Error 500 – Internal Server Error Malformed escape pair at Index 53 when testing connection to SAP Business One database

• Root cause: Special character e.g. $,%,# exist in the password.
• Solution : Ensure special characters are not included in any password – this is currently a limitation and may change in the future.

1.3 Error HTTP 401

       First test the B1DI and JDBC connection from the SLD (System Landscape Directory) in the Integration Framework for SAP Business One window.

• Root cause 1: Incorrect SAP Business One Version installed and warning was ignored during set-up.
• Solution 1: Ensure you are not trying to connect to the Cockpit/Dashboard when running SAP Business One 8.8 PL11 or lower.

• Root cause 2: User selected an old JCO folder during installation and warning was ignored during set-up.
• Solution 2: Change the DIProxy properties files to point to correct JCO path and restart the DI Proxy services. To do this open the file (default location is C:\Program Files\SAP\SAP Business One Integration\DIProxy\diproxyserver.properties) and update the field JCOPATH.

         Note: 8.8 PL2 and B1iC 8.81 validates the DI version and if incorrect a warning will appear in the setup process and will be included in the install_log.ini file.

• Root cause 3: B1i user is not a super user.
• Solution 3: Ensure in SAP Business One the B1i user is set as a super user.

• Root cause 4: User is locked after 5 consecutive failed attempts.
• Solution 4: See Note 1556041 on how to resolve this.

• Root cause 5 B1iC 8.8: B1iServer address is incorrect
• Solution 5: Ensure the B1iServer address is correct – this is valid for B1iC 8.8 only

       http://<server_name>:8080/B1iXcellerator/exec/ipo/vP.001sap0004.in_HCSX/com.sap.b1i.vplatform.runtime/INB_HT_CALL_SYNC_XPT/INB_HT_CALL_SYNC_XPT.ipo/proc

• Root cause 6: DI Proxy port conflict.
• Solution 6: Change the DI Proxy port in the SLD for the SAP Business One database (different to 2099, 2100 for example). Enter same port number in RMI_PORT property(before 8.81PL10 and 8.82PL03) or HTTPS_PORT property(from 8.81PL10 and 8.82PL03) of diproxyserver.properties file(folder Program Files/SAP/SAP Business One Integration/DIProxy). For B1iC 8.8 deactivate sap.Xcelsius package and activate sap.Xcelsius package.

• Root cause 7: localhost was not added to Trusted Sites.
• Solution 7: Add http://127.0.0.1 to Trusted Sites (Tools->Internet Options->Security tab->Trusted Sites)

1.4 Error HTTP 403 Forbidden - XCL198 HTTP access currently not allowed from remote clients, as B1iP runs in local-mode or safe-mode

• Root cause: You use localhost in the B1i Server address.
• Solution: Ensure instead of localhost you use the IP address or the server name to connect. Change the connection string in SAP Business One General Settings.

1.5 Error HTTP 404 not found/File not found

• Root cause 1: The user manager is used instead of the B1i user.
• Solution 1: Ensure the user B1i is used during setup and connection in the SLD and the B1i user has been correctly set up in SAP Business One.

• Root cause 2 B1iC 8.8/B1iC 8.81 before GA: Incorrect JDK installed for a 64bit environment.
• Solution 2: In 64bits machines you need to have JDK installed for both 32 and 64bits and point to both during the installation of B1ic.

• Root cause 3: There is an SQL server instance name.
• Solution 3: If you are using an SQL named instance make sure each instance uses a different TCP/IP port and, during the installation of the integration component, enter the server name as <server name> rather than <server name>\instance name.

• Root cause 4: The IPO user was deactivated.
• Solution 4: Go to B1iP Control Center -> Configuration -> User Admin IPO-Steps – Toggle Activation for user B1iadmin and B1ipeer. Restart the Integration server and Event Sender service and retry.

• Root cause 5: The Proxy host was configured in the Event Sender set up.
• Solution 5: On Step 3/5 of the Event Sender set up ensure you do not configure Proxy Host or the Proxy Port.

• Root cause 7: The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error.
• Solution 7a: Ensure the correct company database appears in the SLD. Deactivate and re-activate the dashboard in SAP Business One’s General Settings.
• Solution 7b: Check the Message Log in the Integration Framework -> Monitoring for errors (Failure) connected to “Sender Trigger / Object” “500” (event to create SLD entry) or “120000008” (event to deploy dashboards)
• Solution 7c: Check the Queue Monitor in the Integration Framework -> Monitoring for pending processes – after installation / upgrade some post-installation processing time may be required (depending on various factors up to 2 minutes per B1 DB on slow systems)
• Solution 7d: Go to the B1iP Control Center -> Maintenance -> IPO-Step Status and check “Deactivated steps only to check whether any processes are halted. If so, the relevant error may be displayed – giving a hint for details that require fixing.Activate the deactivated steps – and press “Refresh” to see whether the steps can successfully be reactivated.

• Root cause 8: SQL Server/Tomcat Services have not been started.
• Solution 8: Ensure SQL Server//Tomcat Services are started:
  • - Click Start -> Control Panel -> Administrative Tools -> Services
  • - Locate the service name SQL Server (MSSQLSERVER) / Tomcat and ensure they are started

• Root cause 9: Https Port 8443 is being used by another program.
• Solution 9: Open https://localhost:8443 via the browser and ensure it is the home page of Apache Tomcat. If not, the 8443 port is occupied by another program. Disable the other program that is using port 8443 or assign another port to the other program.

1.6 Error HTTP 500 – Internal Error

• Root cause 1: The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error.
• Solution 1a: Ensure the correct company database appears in the SLD. Deactivate and re-activate the dashboard in SAP Business One’s General Settings.
• Solution 1b: Check the Message Log in the Integration Framework -> Monitoring for errors (Failure) connected to “Sender Trigger / Object” “500” (event to create SLD entry) or “120000008” (event to deploy dashboards)
• Solution 1c: Check the Queue Monitor in the Integration Framework -> Monitoring for pending processes – after installation / upgrade some post-installation processing time may be required (depending on various factors up to 2 minutes per B1 DB on slow systems)
• Solution 1d: Go to the B1iP Control Center -> Maintenance -> IPO-Step Status and check “Deactivated steps only" to check whether any processes are halted. If so, the relevant error may be displayed – giving a hint for details that require fixing.Activate the deactivated steps – and press “Refresh” to see whether the steps can successfully be reactivated. If the step cannot be activated, then please deactivate the integration scenario (Scenarios – Control and untick the scenario package for sap.Xcelsius). The you should be able to activate the IPO steps and afterwards the scenario package needs to be activated again.

• Root cause 2: The JDBC URL is incorrect as the company was created manually with incorrect information.
• Solution 2: Ensure the correct Server/port and database details have been entered in the JDBC URL

• Root cause 3: The address in the B1iServer name is incorrect (valid for B1iC 8.8 only)
• Solution 3: Use the correct server address and ensure you replace <server_name> with the name or IP of your own server – do not use localhost. Ensure there is no spaces etc in the link. http://<server_name>:8080/B1iXcellerator/exec/ipo/vP.001sap0004.in_HCSX/com.sap.b1i.vplatform.runtime/INB_HT_CALL_SYNC_XPT/INB_HT_CALL_SYNC_XPT.ipo/proc

1.7 Error “The IPO-Step to create a cached authentication config-node for is not known”

• Root cause 1: Installation did not install the systems in the System Landscape directory.
• Solution 1: Run the EventSender setup. Or detach the database from SQL Server Management Studio. Refresh company list and attach the database once again in SQL. Click refresh in the Choose Company window in SAP Business One.

• Root cause 2: Scenario has not been activated
• Solution 2: Open the Integration framework -> Scenarios -> Scenario Package Control. For the sap.Xcelsius click Activate.

• Root cause 3: Changes made without restarting.
• Solution 3: If changes are made ensure Integration Service and Event Sender are restarted.

• Root cause 4: Internal functions / IPO steps may have been “deactivated”.
• Solution 4: Go to the B1iP Control Center -> Maintenance -> IPO-Step Status and check “Deactvated steps only” to check whether any processes are halted. If so, the relevant error may be displayed – giving a hint for details that require fixing. Activate the deactivated steps – and press “Refresh” to see whether the steps can successfully be reactivated.

1.8 Error “Action Cancelled”

• Root cause 1: SAP Business One integration service may be stopped.
• Solution 1: Ensure the SAP Business One integration service is running. Stop and start the service and retry.

• Root cause 2: Port 8080 is being used by another program
• Solution 2: Open http://localhost:8080 via the browser and ensure it is the home page of Apache Tomcat. If not, the 8080 port is occupied by another program. Disable the other program that is using port 8080 or assign another port to the other program.

Note: From B1iC 8.8 PL05 to change the port you should follow the instructions in the AdministrationGuide_Integration_Component section 2.7

1.9 What is the username and password for explicit Authentication

      You will receive the prompt “The server xxxx at B1iP_ipo_/vP.001sap0004.in_HCSX/com.sap.b1i.vplatform.runtime/INB_HT_CALL_SYNC_XPT.ipo/proc requires a username and password”.

• Solution:

UserName: Language/user_name/company_name (e.g. en-US/manager/SBODemoUS)

Password: The SAP Business One user password (e.g. manager password)

(language enumeration:
cs-CZ, da-DK, de-DE, el-GR, en-CY, en-GB, en-US, en-SG, es-AR, es-CO, es-ES, es-PA, fi-FI, fr-FR, he-IL, hu-HU, it-IT, ja-JP, ko-KR, nl-NL, no-NO, pl-PL, pt-BR, pt-PT, ru-RU, sk-SK, sr-YU, sv-SE, xx-XX, zh-CN, zh-TW).

Note: if this occurs in SAP Business One you should restart the SAP Business One client.

1.10 Error opening Cockpit or Tomat server page opens instead

• Root cause: B1i server address provided in General Settings is incorrect.
• Solution: Provide correct server address as documented in the Administration Guide http://server_name:8080/B1iXcellerator/exec/ipo/vP.001sap0004.in_HCSX/com.sap.b1i.vplatform.runtime/INB_HT_CALL_SYNC_XPT/INB_HT_CALL_SYNC_XPT.ipo/proc

1.11 Error invalid URl: The format of the URl could not be determined

• Root cause: Incorrect B1i server address given in Administration -> System Initialisation -> General Settings -> Cockpit -> B1i Server Address.
• Solution: Use the correct server address and ensure you replace <server_name> with the name of your own server

http://<server_name>:8080/B1iXcellerator/exec/ipo/vP.001sap0004.in_HCSX/com.sap.b1i.vplatform.runtime/INB_HT_CALL_SYNC_XPT/INB_HT_CALL_SYNC_XPT.ipo/proc

1.12 Error #2032 Connection type: XML Data

• Root cause 1: Incorrect setting in Server Manager
• Solution 1: Start "Server Manager"-> Under the "security information section, click on the Configure IE ESC" link and Turn off for Administrators.
  
  
• Root cause 2: Improper IE setting
• Solution 2: In toolbar of the Microsoft Windows Internet Explorer, choose Tools -> Internet Options. In the Settings section of the Advanced tab, navigate to the Security list, and deselect the checkbox Do not save encrypted pages to disk.

Hi Jon,

You can open the past draft document as long as the document did not delete or remove yet by the document owner.

You can open from module banking --> banking reports --> payment drafts report.

Rgds,

JM

Hi,

- I given you the general document, where you need to look for your requirement, More over I just interpret the term foreign as 3rd party. It doesn't mean any specific product from anyone.

- Please follow the wiki doc.

Regards

Jansi

Customer created partial deliveries, then closed remaining opens.  Balance Utility was required.  thank you for suggestions.

Dear experts,

I have a question on the Logistics invoice verification.  During the MIRO process, the condition value maintained in PO are not being copied/auto populated/allocated in the MIRO. 

Have been searching in the forum without any concrete solution obtained.  Have also been searching for SAP notes but doesn’t seems to solve my problems--sapnote_0001754797, sapnote_0001565905.

Here is the scenario:

1. We cut a “asset PO" (acct asign "A") whereby it is a “GR non-valued”; without multiple account assignment; the GR bsd IV Indicator is marked in PO
2. In the PO, we maintained some conditions such as freight cost for the same vendor
3. We perform goods receipt via MIGO.  Of course, there is no financial posting for this GR since it is GR non-valued.
4. There is no issue of duty and taxes in the PO.
5. But when comes to MIRO process for planned delivery cost, the system does not auto populate the PO condition value.  Why?  (However, the asset/material value maintained in the PO get auto populated in PO).

Note: we tried create a different "non-asset" PO using the same PO condition, e.g. freight cost, and it is working perfectly fine.  In other words, during MIRO process, the planned delivery cost are automatically populated in the MIRO screen.

Appreciate if you can enlighten me on this issue.  Otherwise it is not logical to enter the value manually---Imagine if I have many POs having 20-30 items per PO and various freight conditions.  (we don't do PO header conditions). 

Is this a standard SAP functionality that condition value allocation in MIRO is based on "GR-valued PO" as explained in various experts in this forum? Any SAP notes can perfectly explain such system behaviour? 

Many thanks in advance.

Hi Dubey,

We are currently facing similar issue, would you be able to share your solution?

CALL METHOD g_alv_tree->GET_OUTTAB_LINE is returning 0 value for the subtotal.

Thank you.

Hello Darren,

were you able to resolve this issue? having the same issue now

Thanks,
Jeff

Hi Swati,

Thanks for the reply.

RESET_SELECTION_FIELD will clear the field, but I want to keep the values entered in the selection screen for the first run when come back from second screen.

Regards,

Hello, debrah,

i have similar issue.

Node in interface controller INM_SDC_PPM_OBJECTS is nor getting updated with appendind z fields.

Could you describe steps to reach results, please?

Hi ,

i got solution

Step: add new field in strcture /SAPSRM/S_POWL_RESULT_SC_ITM

         2. Add new field in SPRO-POWL LAYOUT ADJ

         3. Enhance badi /SAPSRM/BD_POWL_CHNG_SEL_RSLT

Regards

rAM.

Hi Krishna,

I able to provide any one of the color in my ALV column, but my requirement is to assign the different colors(in alv progress indicator) based on other field data like status indications. Hope you understand my requirement.

Regards

Venkat