B1 2007 SDK tips

[Trinidad]

Hi,

Before using B1 2007 version please read carefully the new

and pay special attention to the Compatibility document and notes released for this new version.

An important point regarding DI API "Production Order" documents has changed in the new version (listed in the Compatibility document):

<i>Historically the GetByKey method for Production Orders got the DocNum as input (different from any other document that got the DocEntry property as input).

<b>Starting from SAP Business One 2007 A release the GetByKey for production order will get as input the DocEntry property (like any other document)</b>.

Same rule applies when adding an Issue For Production via the DI API, the property BaseEntry of the DocumentLines object must be set to the relevant DocEntry of the Production order when you reference a base document.

</i>

Please note that the following restrictions apply to partners who are not participating in Ramp-Up:

• No productive use is allowed

• No support will be provided

Important Note regarding February patch PL15, please check Note number 1126824.

Internal message cannot be sent with MessagesService using the DI API when setting the property MessageDataColumn.Link to equal 1.

The problem will be fixed with SAP Business One 2007 A March patch.

Best Regards

Trinidad.

Edited by: Trinidad Martinez on Jan 15, 2008 9:50 AM

[Former Member · Accepted solution]

Just a quick response:

> <i>Historically the GetByKey method for Production

> Orders got the DocNum as input (different from any

> other document that got the DocEntry property as

> input).

> <b>Starting from SAP Business One 2007 A release the

> GetByKey for production order will get as input the

> DocEntry property (like any other document)</b>. </i>

To my opinion, this was already the case since SBO2005, and is not new in 2007.

> <i>Same rule applies when adding an Issue For Production

> via the DI API, the property BaseEntry of the

> DocumentLines object must be set to the relevant

> DocEntry of the Production order when you reference a

> base document.</i>

This is indeed a <i>breaking</i> change in 2007 that was only acknowledged recently and cost us many head-aches

Regards,

Rein de Boer

Trimergo

[Former Member]

I am new for SDK Can you send me some tutorial about SDK or any thread link for basic kowledge.

Jitender

[Former Member]

What program do I use to read the XML files containing the 2007A changes list?

[Trinidad]

Hi Mike,

To read the DbChangesList xml file you can use the DbBrowser tool included inside both packages: B1TE and B1DE.

For reading the UIChangesList there is no tool for the moment, you need to use a simple Xml editor.

Regards

Trinidad.

[Former Member]

Hi Trinidad,

Error in B1 DB Profiler:

Even though I configured my SBO_SP_Transaction Notification stored Procedure, I am getting the Error like below.

"An addon test has been run.Several lines should appear in the B1DbProfiler is not correctly configured.If failed please check you have copied the needed code into the SBO_SP_TransactionNotification stored procedure."

[Former Member]

Hi Trinidad,

I tried to read the file at:

Business One Application and SDK 2007 New Features (PDF 3.3MB)

This presentation gives you an overview of the new features of the SAP Business application and SDK for the 2007 version.

and I get an error message saying that the file is damaged and could not be repaired. Do you know if other are getting this message as well?

Thanks,

Mike

[Former Member]

Upgrading to Adobe Acrobat Reader 8.0 did the trick.

[Former Member]

Hi Mike,

Could you please send the file to me ? or if you have exact link, please share to me. Thx

Edu

[Former Member]

Hi Edu,

Which file do you mean?

Thanks,

Mike

[Former Member]

Hi Trinidad,

Would you look at my issue called "Doc numbering error when adding a UDO in 2007 A", and comment? Or maybe my description below is adequate and you can comment here.

Let me first define terms to simplify my explanation. A simple UDO has only a header table supporting it. A compound UDO has both a header and line table to support it.

It looks like 2005A is handling UDO doc numbering differently compared to 2007A. For 2005A, the NNM1 table has a row for all UDOs regardless of whether they are simple or compound. For 2007A, the NNM1 table has a row only for the compound UDOs. If this is true, there is a problem with upgrading from 2005A to 2007A if the add-on already includes a simple UDO. The problem this creates in 2007A is the inability of the user to add to a UDO if it only has a header table.

Is this an over-sight by SAP?

Thanks,

Mike

[Former Member]

Hi Trinidad,

I couldn't find anything on the forum that addressed this.

I had heard that there is a maximum patch level for 2005 for upgradability to the pre-release version of 2007. If this is true what patch level is that?

Thanks,

Mike

[Trinidad]

Hi Mike,

You can read the information you are asking for on the page where you can download the B1 2005 SP01 patches in the SAP Service Marketplace web site.

The limitation is only during the rampup of the 2007A version.

Here you have the exact text on SMP:

For customers who plan to participate in the SAP Business One 2007 A Ramp-Up program, the last regular SAP Business One 2005 A SP01 patch that can be applied is patch 22.

Applying PL23 or higher will prevent you from upgrading to SAP Business One 2007 A prior to the end of Ramp-Up of this release !

Regards

Trinidad.

[Former Member]

Hi Trinidad.

I'm having problems adding text lines in quotations via SDK with SBO 2007.

()

Have you some code example for this issue?

SAP Business One 2007 key topic document hasn't it

Thnx in advance

[Trinidad]

Hi Juli,

I have answered to your thread at

Please don't use this thread for questions.

Regards

Trinidad.

[Former Member]

Trinidad,

Would you please explain the statement in your post?

"Same rule applies when adding an Issue For Production via the DI API, the property BaseEntry of the DocumentLines object must be set to the relevant DocEntry of the Production order when you reference a base document."

I looked at the documentation on your website and didn't find anything on it.

-

---

Also the statement:

"Historically the GetByKey method for Production Orders got the DocNum as input (different from any other document that got the DocEntry property as input).

Starting from SAP Business One 2007 A release the GetByKey for production order will get as input the DocEntry property (like any other document)."

appears to be wrong. The functionality that this statement describes for 2007A appears to already be incorporated into 2005A.

Can you shed some light on this?

Thanks,

Mike

[Trinidad]

Hi,

Rein de Boer is right when he said the GetByKey function already ask as input the DocEntry for ProductionOrders documents.

The change in 2007 is regarding the BaseEntry property when creating an Issue for Production based in a ProductionOrder document. Prior to 2007 the BaseEntry property accepted a DocNum as base document, 2007 will not accept DocNum anymore. It waits for a DocEntry.

Example:

Production order with DocEntry = 32 and DocNum= 501

Dim issue As Documents

Set issue = sbocompany.GetBusinessObject(oInventoryGenExit)

issue.Lines.BaseEntry = 32 'DocEntry from Production Order

issue.Lines.BaseLine = 0

issue.Lines.BaseType = BoObjectTypes.oProductionOrders

In 2005 SP01 BaseEntry = ProductionOrder DocNum (you can have a look to Note 901524)

Hope it helps

Trinidad.