Integration framework for SAP Business One 06 APIs

Integration framework
for SAP Business One

Guide 06

APIs

Author: Heinz Pauly Version: 1.0 Date: July 30, 2010

-1-

Integration framework for SAP Business One 06 APIs

Content
1. API Call........................................................................................................3 1.1 JobCreator..............................................................................................4 1.2 B1ifAPI ...................................................................................................6 2. SLD Entry ....................................................................................................7 2.1 Create, Update, Delete an SLD entry.....................................................7 2.2 Generate a new SLD entry ...................................................................12 3. Scenario APIs ............................................................................................14 3.1 Scenario Refresh..................................................................................14 3.2 Scenario Activation/Deactivation ..........................................................15 3.3 Add a System to an existing Scenario Package ...................................16 3.4 Generate/Add a System to an existing Scenario Package ...................17 3.5 Delete a System in an existing Scenario Package ...............................19 Copyrights, Trademarks, and Disclaimers .....................................................20

-2-

Integration framework for SAP Business One 06 APIs

1. API Call
The APIs in the Integration framework are bizflows. There are multiple ways how to call them. You can call the APIs synchronously via the Include atom inside your processing flow. How to call them in an asynchronous manner, please check the following graphic which depicts the the API infrastructure.

APIs gets called asynchronous via jobs. The setup routine of B1if is calling the JobCreator which is adding a new job into the internal jobqueue document. You can also us this mechanism during the processing flow via the Include atom to call the JobCreator. Whenever you start/re-start the B1if server, the JobExecutor is triggered. The JobExecutor retrieves all jobs from the internal jobqueue document and stored API jobs into the internal Job Queue. You can also use the atom Put To Internal Queue during an processing flow to add new jobs directly to this queue. The name of the queue is Q.JobQueue and the name of the stream is S.Job. You can also call via http the API inbound B1ifAPI to store a job into the internal Job Queue. The APICaller is triggered by entries in the internal Job Queue and will call the appropriate API. APICaller is following strictly the order of the jobs. The result of this asynchronous calls you can find in the internal job execution document .

-3-

Integration framework for SAP Business One 06 APIs

1.1 JobCreator
Creates a job in the job queue document for the JobExecutor. JobCreator is used for Bizflow calls which are using xcellerator functionality in case the excellerator is not available (e.g. during installation) or in case asynchronous processing is intended. Bizflow: /com.sap.b1i.vplatform.system/bfd/JobCreator.bfd Parameter: The JobCreator has one parameter (bfd) to specify the bizflow to call and covers in addition all typical parameters of all B1ifAPI call. Please refer to the particular chapter of the call for the semantics of the parameters. bfd name of the bizflow to call (full Bizstore URI) in syntax /ds/grp/x.bfd

parameter of the Bizflow to call.

Job Queue Document: /com.sap.b1i.vplatform.system/job/jobqueue.xml

<jobqueue xmlns=""> <job bfd="bizflow" jobid="guid" created="ts"> <par name="name" value="value"/> ... </job> ... <job bfd="bizflow" jobid="guid" created="ts"> <par name="name" value="value"/> ... </job> </jobqueue>

Result: The bizflow returns a 3-digit code in text format. In case the return code is not 000, there is no job created. - 000 - 001 (Bizflow is empty)

Job Executor Retrieves all jobs from the job queue document and calls the referred bizflow. The JobExecutor is called on start of B1iP. Bizflow: /com.sap.b1i.vplatform.system/bfd/JobExecutor.bfd

-4-

Integration framework for SAP Business One 06 APIs

Job Queue Document: /com.sap.b1i.vplatform.system/job/jobqueue.xml The JobExecutor maintains a result document: /com.sap.b1i.vplatform.system/job/jobexecution.xml The entries will get inserted in a ring buffer with max entries of 100.
<jobexecution> <job bfd="bizflow" jobid="guid" created="ts" executed="ts" result="result"> <par name="name" value="value"/> ... </job> ... <job bfd="bizflow" jobid="guid" created="ts" executed="ts" result="result"> <par name="name" value="value"/> ... </job> </jobexecution>

-5-

Integration framework for SAP Business One 06 APIs

1.2 B1ifAPI
Creates a job in the job queue (internal queue) for the JobExecutor. JobCreator (via HTTP call) is used to call an B1if API function via HTTP. URL: http://<ipaddress>:8080/B1iXcellerator/exec/ipo/vPlatformIDE/com.sap.b1i.vpl atform.ide/ipo/vPlatform.ide.ipo/B1ifAPI?bfd=<bfd>

Parameter: <ipaddress>: ip address or logical name of the B1if server <bfd>: The JobCreator has one parameter (bfd) to specify the bizflow to call and covers in addition all parameters of all B1ifAPI calls. Please refer to the particular chapter of the call for the semantics of the parameters.

Example: http://localhost:8080/B1iXcellerator/exec/ipo/vPlatformIDE/com.sap.b1i.vplatfo rm.ide/ipo/vPlatform.ide.ipo/B1ifAPI?bfd=vPacAddSystem&vpac=sap.Xcelsius &sldref=001sap0001&par0=entryname&par3=newcompany

Result:
<result status="status"> <job bfd="bizflow" jobid="id" created="ts" par="parstring" /> </result>

status: status of the job creation: 000 if successful, 001 if error jobid: identifier of this job, can be used to check the job result after processing created: timestamp of job creation par: all parameter with values

-6-

Integration framework for SAP Business One 06 APIs

2. SLD Entry
There are two APIs available to manipulate an entry in the System Landscape Directory (SLD). You use the API SLDCreateSysId (chapter 3.1) to create, update or delete an SLD entry with a known SysId (SLD entry identifier). In case you want to create a new SLD entry and you want the API to generate a new SysId, you can use the API GenSystemToSLD (chapter 3.2).

2.1 Create, Update, Delete an SLD entry

This service can create, update or delete an SLD entry. To create an entry the handover of parameters is optional as the default values will be used instead. To update an entry, you can handover the values, you want to update, only. Other values will not be modified. In case of deletion, you just handover the action to indicate deletion and the sysid. Bizflow: /com.sap.b1i.vplatform.system/bfd/SLDCreateSysId.bfd The follow operations will be performed: (1) Create, update or delete the following SLD documents /com.sap.b1i.system.sld.directory/SysId.xml/sysid(Id) /com.sap.b1i.system.sld.directory/SysId.xml/b1Server!!company(SourceSit e!!EventSource) (if B1) /com.sap.b1i.system.sld.directory/SysId.xml/company(EventSource) (if B1) (2) Update or create the routing tree document /com.sap.b1i.system.sld.directory/RoutingTree.xml/RoutingTree(unified) (3) Update or create the deployment document for test connection /com.sap.b1i.system.xc/xml.deployments/com.sap.b1i.system.sld.connecti on.xml(unified)

Parameter: action, sysid, systype, crypt, par0, ..., par28 Mandatory parameters: for delete: action=delete, sysid=sysid for update: sysid=sysid,systype=systype

Parameter: action
empty Mode is create in case the entry does not exist, Mode switches to update in case the entry exists already. insert Mode is create in case the entry does not exist, Mode switches to update in case the entry exists already. update Mode is create in case the entry does not exist, Mode switches to update in

-7-

Integration framework for SAP Business One 06 APIs case the entry exists already. delete Mode is delete. In case (Mode=create) and some of the parameters par0 par20 are not handed over, the fix default values will be used. In case (Mode=update) and some of the parameters par0 par20 are not handed over, the existing values will be used.

Parameter: sysid
a 10-digit SysId, following the syntax 001xxxxxxx SAP allows you to define unique identifier (Sysids) for the systems in the SLD (System Landscape Directory). The vendor is responsible for uniqueness. The syntax is 001xxx0001. xxx = Vendor namespace. This is the unique vendor abbreviation, provided by SAP.

Parameter: systype
B1.2004 B1.2005 B1.2007 B1.8.8 ECC6.0 R3.46C R3.47.100 R3.47.200 F.AnySystem H.AnySystem J.AnySystem W.AnySystem (T.AnySystem SAP Business One 2004 SAP Business One 2005 SAP Business One 2007 SAP Business One 8.8 SAP ERP ECC 6.0 SAP ERP R/3 4.6 C SAPERP R/3 4.7 100 SAPERP R/3 4.7 200 File System HTTP Database Web Service FTP not yet supported)

Parameter: crypt
true false all passwords will be encrypted (default in case parameter is not handed over) all passwords will be stored in plain text

Parameter: par0, , par28

These parameter are dependent on the systype. Please refer to the appropriate chapter.

Return Code
<result jobid="" sysid=""> <result>3 digit number</result> </result>

result returns a 3-digit code, optional with additional information. In case the return code is not 000, there is no change in the SLD. - 000 - 001 (SysId is empty) - 002 (length of SysId is not 10) - 003 (SysId does not start with '001')

-8-

Integration framework for SAP Business One 06 APIs

- 004 (SysType is empty) - 005 (wrong SysType systype) - 006 (not correct systype currentsystype - systype) - 007 (nothing to delete) - 008 (sequence number wrong) - 009 (sequence number overflow) jobid is the job id in case the task is triggered via the JobCreator (chapter 1) sysid is the identifier of the created/modified/deleted SLD entry

Parameter for SAP B1

par0 par1 par2 par3 par4 par5 par6 par7 par8 par9 Name of the system (default: sysid) b1Server IP-Address (default: 127.0.0.1) license Server (default: b1Server:30000) Name of company db (default: SBODemoUS) Database Type (default: 4), 1=MSSQL, 2=DB2, 4=MSSql2005, 5=MaxDB, 6=MSSql2008 DB user (default: sa) DB password (default: sa) B1 user (default: B1i) B1 password (default: B1i) Language for B1 login (default: 4), 1=Hebrew, 2=AR Spanish, 3=US English, 5=Polish, 6=SG English, 7=PA Spanish, 8=GB English, 9=German, 0=Serbian, 11=Danish, 12=Norwegian, 13=Italian, 14=Hungarian, 15=Chinese, 16=Dutch, 17=Finnish, 18=Greek, 19=Portuguese, 20=Swedish, 21=CY English, 22=French, 23=Spanish, 24=Russian, 25=LA Spanish, 26=Czech, 27=Slovak, 28=Korean, 29=BR Portuguese, 30 Japanese, 31=Turkish, 35=TrdtnlChinese HK.Chinese, empty=default setting in B1. IP-address of DIproxy (default: b1Server) Port od DIproxy (default: 2099) IP-address od proxy server (default: empty) Port of proxy server (default: empty) JDBC driver default if db type=4: com.microsoft.sqlserver.jdbc.SQLServerDriver default if db type=5: com.sap.dbtech.jdbc.DriverSapDB default if db type=6: com.microsoft.sqlserver.jdbc.SQLServerDriver otherwise empty JDBC url default if db type=4: jdbc:sqlserver://b1server:1433;integratedSecurity=false; databaseName=company;selectMethod=cursor default if db type=5: jdbc:sqlserver://b1server:1433;databaseName=company; SelectMethod=Cur default if db type=6: jdbc:sqlserver://b1server:1433;integratedSecurity=false; databaseName=company;selectMethod=cursor otherwise empty DB user (default: par5) DB password (default: par6)

par10 par11 par12 par13 par14

par15

par16 par17

Parameter for a Web Service

par0 par1 par2 par3 Name of the system (default: sysid) destProtocol (default: http) destHost (default: empty) destPort (default: empty)

-9-

Integration framework for SAP Business One 06 APIs par4 par5 par6 par7 par8 par9 par10 par11 par12 par13 destPath (default: empty) query (default: empty) proxyHost (default: empty) proxyPort (default: empty) authentication (default: basic) user (default: empty) password (default: empty) sslTruststorePath (default: empty) sslTruststorePassword (default: empty) associatedSrvIP (default: empty)

Parameter for an HTTP Call

par0 par1 par2 par3 par4 par5 par6 par7 par8 par9 par10 par11 par12 par13 par14 par15 par16 Name of the system (default: sysid) destProtocol (default: http) destHost (default: empty) destPort (default: empty) destPath (default: empty) query (default: empty) proxyHost (default: empty) proxyPort (default: empty) authentication (default: basic) user (default: empty) password (default: empty) sslTruststorePath (default: empty) sslTruststorePassword (default: empty) associatedSrvIP (default: empty) method (default: post) user2query (default: empty) password2query (default: empty)

Parameter for a File System

par0 par1 par2 Name of the system (default: sysid) filePattern for incoming files (default: c:\b1if\in\*.*) character encoding (default: 1) 1=ISO-8859-1, 2= ISO-8859-2, 3= ISO-8859-3, 4= ISO-8859-4, 5= ISO-8859-5, 6= ISO-8859-6, 7= ISO-8859-7, 8= ISO-8859-8, 9= ISO-8859-9, 10= ISO-8859-11, 11= ISO-8859-13, 12= ISO-8859-14, 13= ISO-8859-15, 14= ISO-8859-16, 15=US-ASCII, 16=EBCDIC, 17=Shift-JIS, 18=EUC-JP, 19=ISO-2022, 20=GB2312, 21=EUC-KR, 22=Big-5, 23=UTF-7, 24=UTF8, 25=ISO-10646-UCS2, 26=ISO-10646-UCS4. delimiter in case inbound is csv file (default: ,) wrap char in case inbound csv file (default: empty) payload type of incoming file (default: 1) 1=automatic detection, 2=xml file, 3=dsv file, 4=txt file, 5=regex file rule document in case of offset/regex specified inbound transformation rule (default: empty ) filePattern for outgoing files (default: c:\b1if\out\*.xml)

par3 par4 par5 par6 par7

Parameter for a Database System

par0 par1 par2 par3 Name of the system (default: sysid) JDBC driver (default: com.microsoft.sqlserver.jdbc.SQLServerDriver) JDBC url (default: jdbc:sqlserver://IPADDRESS1433;integratedSecurity=false; databaseName=DBNAME;selectMethod=cursor DB user (default: sa)

- 10 -

Integration framework for SAP Business One 06 APIs par4 DB password (default: sa)

Parameter for an SAP R/3 System

par0 par1 par2 par3 par4 par5 par6 par7 par8 par9 par10 par11 par12 par13 par14 par15 Name of the system (default: sysid) Application Server [active and passive] (default: empty) Client [active and passive] (default: empty) User [active and passive] (default: empty) Password [active and passive] (default: empty) Language [active and passive] (default: EN) System number [active and passive] (default: 00) Maximum connections [active and passive] (default: 5) Gateway host [active and passive] (default: empty) Gateway service number [active and passive] (default: sapgw00) Sender partner [active] (default: empty) Sender port [active] (default: empty) Receiver partner [active] (default: empty) Receiver port [active] (default: empty) Program ID [passive] (default: empty) Unicode switch [passive] (default: false)

Parameter for an SAP ERP System (ECC6.0)

par0 par1 par2 par3 par4 par5 par6 par7 par8 par9 par10 par11 par12 par13 par14 par15 par16 par17 par18 par19 par20 par21 par22 par23 par24 par25 par26 par27 par28 Name of the system (default: sysid) Application Server [active and passive] (default: empty) Client [active and passive] (default: empty) User [active and passive] (default: empty) Password [active and passive] (default: empty) Language [active and passive] (default: EN) System number [active and passive] (default: 00) Maximum connections [active and passive] (default: 5) Gateway host [active and passive] (default: empty) Gateway service number [active and passive] (default: sapgw00) Sender partner [active] (default: empty) Sender port [active] (default: empty) Receiver partner [active] (default: empty) Receiver port [active] (default: empty) Program ID [passive] (default: empty) Unicode switch [passive] (default: false) destProtocol (default: http) destHost (default: empty) destPort (default: empty) destPath (default: empty) query (default: empty) proxyHost (default: empty) proxyPort (default: empty) authentication (default: basic) user (default: empty) password (default: empty) sslTruststorePath (default: empty) sslTruststorePassword (default: empty) associatedSrvIP (default: empty)

- 11 -

Integration framework for SAP Business One 06 APIs

2.2 Generate a new SLD entry

This service generates a new SysId and creates an SLD entry. To create an entry the handover of parameters is optional as the default values will be used instead. Bizflow: /com.sap.b1i.vplatform.system/bfd/GenSystemToSLD.bfd Mandatory Parameter sldref Parameter: sldref, par0, , par28

sldref Instead of handing over all the parameters to specify the new SLD entry, you can handover the parameter sldref to specify a reference system in the SLD from which the values will be taken for all parameters which are not explicitly handed over. This is helpful in case you want to add a new SLD entry for a new added company database of an SAP Business One system and there is already an entry in the SLD for another company database. The parameter sldref is optional and can be a SysId, a SysType or a b1server address. First the API will search for a matching SysId. If it fails it will take the value of the sldref parameter as a SysType and will pick up the first SLD entry of this type. If it fails as well it will take the value of the sldref parameter as a b1server and will pick up the first SLD entry that has this value in the parameter b1server. If this fails as well, there is no SLD reference and the handed over parameters will be used, resp. the default values of the API SLDCreateSysId (chapter 3). par Please refer to the parameters, defined in chapter 2.1.

Return Code
<call jobid=""> <sysid>0010000180</sysid> <result>000</result> <operation status="000" jobid="" systype="B1.8.8" sldref="0010000112" vpac=""> <biulist /> <SLDParams>parameter ...</SLDParams> </operation> </call>

result returns a 3-digit code, optional with additional information. In case the return code is not 000, there is no change in the SLD.

- 12 -

Integration framework for SAP Business One 06 APIs

- 000 - 008 (sequence number wrong) - 009 (sequence number overflow) jobid is the job id in case the task is triggered via the JobCreator (chapter 1). The element sysid (in the above example 0010000180) is the generated SysId.

- 13 -

Integration framework for SAP Business One 06 APIs

3. Scenario APIs
3.1 Scenario Refresh
This service will run through all Scenario Steps of a particular Scenario Package. For each Scenario Step it will re-generate all xsl documents and Bizflow definition based on the definitions to guarantee a consistent status. Its strongly recommended to run this service before activation of a Scenario Package via an API. Bizflow: /com.sap.b1i.vplatform.system/bfd/vPacRefresh.bfd You can call this bizflow directly from your Bizflow, from external or in-direct via JobCreator. Parameter: id, mode id Name of the Scenario Package mode Working mode of the service. The value ALLBFDXSLVAR is regenerating all involved documents.

Result An xml document with the following structure

<call jobid="number" id="package identifier" mode="ALLBFDXSLVAR"> <result>000</result> </call>

result 000 001 (Parameter id is not defined) 002 (Parameter id is empty) 003 (Scenario Package does not exist)

- 14 -

Integration framework for SAP Business One 06 APIs

3.2 Scenario Activation/Deactivation

This service will activate or deactivate a Scenario Package. Prerequisite is the existing setup definition in the B1i BizStore, defined in the document /com.sap.b1i.vplatform.scenarios.setup/vPac.identifier/vPac.xml. For the schema, please refer to reference guide 05, chapter 5.1. Its strongly recommended to run the refresh service (chapter 3) before activation of a Scenario Package.

Bizflow: /com.sap.b1i.vplatform.system/bfd/vPacActivate.bfd You can call this bizflow directly from your Bizflow, from external or in-direct via JobCreator. Parameter: id, mode id Name of the Scenario Package mode Working mode of the service. Set mode to activate will activate the Scenario Package. Set mode to deactivate will deactivate the Scenario Package.

Result An xml document with the following structure

<call jobid="number" id="package identifier" mode="mode"> <result>000</result> </call>

result 000 001 (Parameter id is not defined) 002 (Parameter id is empty) 003 (Scenario Package does not exist) 004 (Parameter mode is not defined) 005 (Parameter mode is empty) 006 (Parameter mode has a wrong value (activate, deactivate)) 007 (Scenario Package is not setup)

- 15 -

Integration framework for SAP Business One 06 APIs

3.3 Add a System to an existing Scenario Package

This API will update the Scenario Package configuration. In case the Scenario Package is active it will be re-activated automatically.

Bizflow: /com.sap.b1i.vplatform.system/bfd/vPacAddSystem.bfd Mandatory Parameter sysid, vpac Parameter: sysid, vpac, sbiu, rbiu

sysid SLD Identifier (SysId) of the system, that should be added to the Scenario Package configuration. vpac Identifier of the Scenario Package for which you want to add the new system. This parameter is mandatory and the API will not do any changes in the setup of the Integration framework in case this parameter is not correct. sbiu This parameter is optional. By default the new system will be added as a sender system for all Scenario Steps of the Scenario Package (parameter vpac) where the inbound channel is the system type of the SysId. In case you want to add the new system as sender system for particular Scenario Steps only, you can list the relevant Scenario Steps in this parameter, separated by comma. If this parameter is handed over, the new system will be added as sender system only for Scenario Packages, that are listed here. rbiu This parameter is optional. By default the new system will be added as a receiver system for all Scenario Steps of the Scenario Package (parameter vpac) where the outbound channel is of the system type of the SysId. In case you want to add the new system as receiver system for particular Scenario Steps only, you can list the relevant Scenario Steps in this parameter, separated by comma. If this parameter is handed over, the new system will be added as receiver system only for Scenario Packages, that are listed here. Result 000 001 (sysid empty) 002 (vpac empty) 003 (wrong sysid)

- 16 -

Integration framework for SAP Business One 06 APIs

3.4 Generate/Add a System to an existing Scenario Package

This API will first create an entry in the SLD, then it will update the Scenario Package. In case the Scenario Package is active it will be re-activated automatically.

Bizflow: /com.sap.b1i.vplatform.system/bfd/vPacGenAddSystem.bfd Mandatory Parameter vpac, [systype | sldref] Parameter: vpac, systype, sldref, sbiu, rbiu, par0, , par28

vpac Identifier of the Scenario Package for which you want to add the new system. This parameter is mandatory and the API will not do any changes in the setup of the Integration framework in case this parameter is not correct. systype This parameter is mandatory if no parameter sldref is specified. Here you specify the type of system you want to add to the Scenario Package. If you are using the parameter sldref, the systype is determinate by the SysType of the referred SLD entry. sldref Instead of handing over all the parameters to specify the new SLD entry, you can handover the parameter sldref to specify a reference system in the SLD from which the values will be taken for all parameters which are not explicitly handed over. This is helpful in case you want to add a new SLD entry for a new added company database of an SAP Business One system and there is already an entry in the SLD for another company database. The parameter sldref is optional and can be a SysId, a SysType or a b1server address. First the API will search for a matching SysId. If it fails it will take the value of the sldref parameter as a SysType and will pick up the first SLD entry of this type. If it fails as well it will take the value of the sldref parameter as a b1server and will pick up the first SLD entry that has this value in the parameter b1server. If this fails as well, there is no SLD reference and the handed over parameters will be used, resp. the default values of the API SLDCreateSysId (chapter 3). sbiu This parameter is optional. By default the new system will be added as a sender system for all Scenario Steps of the Scenario Package (parameter vpac) where the inbound channel is of the system type, specified by the parameter systype. In case you want to add the new system as sender system for particular Scenario Steps only, you can list the relevant Scenario - 17 -

Integration framework for SAP Business One 06 APIs

Steps in this parameter, separated by comma. If this parameter is handed over, the new system will be added as sender system only for Scenario Packages, that are listed here. rbiu This parameter is optional. By default the new system will be added as a receiver system for all Scenario Steps of the Scenario Package (parameter vpac) where the outbound channel is of the system type, specified by the parameter systype. In case you want to add the new system as receiver system for particular Scenario Steps only, you can list the relevant Scenario Steps in this parameter, separated by comma. If this parameter is handed over, the new system will be added as receiver system only for Scenario Packages, that are listed here. par0, par28 The semantic of these parameter is related to the system type you want to add. Please refer to the chapter 3.

Result 000 001 (scenario package identifier missing) 002 (systype identifier missing) 003 (unknown systype) 004 (scenario package identifier is wrong)

Example if you want to call this function to add a new B1 company database to the package sap.Xcelsius. http://localhost:8080/B1iXcellerator/exec/ipo/vPlatformIDE/com.sap.b1i.vplatfo rm.ide/ipo/vPlatform.ide.ipo/B1ifAPI?bfd=vPacGenAddSystem&vpac=sap.Xce lsius&sldref=001sap0001&par0=entryname&par3=newcompany

- 18 -

Integration framework for SAP Business One 06 APIs

3.5 Delete a System in an existing Scenario Package

This API will first de-activate the Scenario Package in case it is active. Then it will update the setup of the Scenario Package in removing the particular system from all relevant Scenario Steps. In case the Scenario Package was active it will be re-activated automatically. In case the parameter sld is set to true the system will be removed also from the System Landscape Directory (SLD). Bizflow: /com.sap.b1i.vplatform.system/bfd/vPacDelSystem.bfd Mandatory Parameter vpac, sysid Parameter: vpac, sysid, sld

vpac Identifier of the Scenario Package in which you want to remove the system. This parameter is mandatory and the API will not do any changes in the setup of the Integration framework in case this parameter is not correct. sysid This parameter is mandatory and specifies the SLD identifier (SysId) of the system you want to remove. sld This parameter is optional, default is false. If set to true, the system will be removed also from the System Landscape Directory (SLD).

Result 000 001 (scenario package identifier missing) 002 (sysid missing) 003 (sysid is wrong) 004 (scenario package identifier is wrong)

Example if you want to call this function to remove the system 0010000555 from the package sap.Xcelsius and from the SLD. http://localhost:8080/B1iXcellerator/exec/ipo/vPlatformIDE/com.sap.b1i.vplatfo rm.ide/ipo/vPlatform.ide.ipo/B1ifAPI?bfd=vPacDelSystem&vpac=sap.Xcelsius &sysid=0010000555&sld=true

- 19 -

Integration framework for SAP Business One 06 APIs

Copyrights, Trademarks, and Disclaimers

Copyright 2010 SAP AG. All rights reserved. The current version of the copyrights, trademarks, and disclaimers at http://service.sap.com/smb/sbocustomer/documentation is valid for this document.

- 20 -