SURVEY: missing DI objects ...

[#1]

We know that there are in DI API several missing objects

and properties, i.e. tables and columns in the B1 DB that

are not exposed by any DI object or property.

Pls tell us which are the most pressing ones for your

current developments. Which are the gaps in the DI API

that you would like to be closed ASAP ?

Looking forward to hearing your opinion.

[Former Member · Accepted solution]

Hello,

Object that should be added:

- LineType (INV10) in All Marketing Documents

In SAP B1 process:

- Please add UpdateDate, CreateDate in Employee Master Data (OHEM)

- Automatically update the UpdateDate of OITM when modified the table ITM1.

[Former Member · Accepted solution]

Hi all,

Function/Method to be added:

1) Able to close/cancel documents including Journal Entry

2) Able to set posting period - I understand now documents can be posted into any open period but for SBO 2004.2B PL 50 and PL 55 you cannot post any past post period using DI (don't know whether is a bug or not, a CSN message had been sent).

3) Recurring Posting.

4) Able to Delete or Remove row(s)/record(s) from UDT.

Thanks

Message was edited by: Erik Tang

[Trinidad · Accepted solution]

Hi Erik Tang,

Can you please give more information regarding

3) "Recurring Posting"? Which table is it linked to? A use case.

Point 4) Able to Delete or Remove row(s)/record(s) from UDT is already possible in SDK 2005 SP01 version, I don't know since when.

Thanks

Trinidad.

[jose_montanez]

Hi:

It is necessary have a Reconciliation object.

Thanks.

[Gianluigi]

All -

Thanks for your contribution. We collected all your needs and we are now

discussing with Product Definition on when to add them in B1 SDK. The next

releases of B1 will contain some of the enhancements required by you all. More

precise details in terms of what and when will be provided through the usual

official channels

Thanks again, this discussion is closed now.

Gianluigi

[Former Member]

Gianluigi:

I do believe this is a localization problem, but this is very very important here in Chile.

1) With DI-API we are able to change the folio number. But we have a field in the OINV that is the last page folio number. With DI API we can change the initial Folio number for the document, but the Last Page Folio Number remains null.

We need this property to be exposed by the DI-API

2) I know some countries can change the salesman afther the creation of a sales order, but in Chile (and other countries) we cannot. This should be done for Chile too.

3) The printed status is not exposed. When creating a new invoice, if this invoice is not "printed" we cannot search by folio number.

Thanks in advance.

Harold Gómez V.

[Former Member]

Is needed an object StarTransaction and EndTransaction for use Commit and Rollbak, with Recordset objects or UserTables. today the transactions working only with business objects of DI.

Regards,

Jorge

[Former Member]

CostingCode2,3,4,5. for OcrCode2,3,4,5 of marketting documents.

[Former Member]

Hello,

Please add more functionality in Print Layout Design. Like adding a formula for Adding only fields visible by the user, removing the hidden field value. In a situation where a customer want a report to hide the items without Output Tax in the computation of the report.

[Former Member]

I am craving for some improvements...

By order of importance:

-> Possibility to call UDO from DI API.

-> Reserved invoice object.

-> Delete method on valid values object (UserFieldsMD)

Other improvement which will be appreciated ():

-> Possiblity to link a user field to a SYSTEM table.

Regards,

[Former Member]

Thanks for the feedback, Cyril!

Reserve invoice is planned for the next version...

Can you be more specific regarding "SYSTEM table" - any prefererences / details you could provide - or is this a request to allow to add UDFs "everywhere"?

Thanks,

Frank

[Former Member]

Hi Franck,

By system table, I mean tables other than UDT. In SBO 2005 (SP00 or SP01), you can create a UDF on any UDT or an some system tables (and yes it would be good to improve that list too), but you can only link a UDF to a User Table.

For instance I have a UDT named @LOROGC for a distribution circuit. I can create a field U_LOROgci on BP table (OCRD) and link that field to my user table. What I cannot do though is creating a UDF U_LORBpcod on the UDF (nvarchar(15)) AND linking it to table OCRD. In some cases, this is a bit annoying.

Other functionalities which will be apreciated:

- GetAsXML() method on UserObjectsMD

- SaveXML() method on UserObjectsMD

Cheers,

Cyril

[Former Member]

Hi Cyril,

Thank you very much for the details!

I/we appreciate that.

Cheers,

Frank

[Private_Member_145664]

Hi, for MARIProjekt we are missing:

OPRC ProfitCenters / Distribution Rules OOCR

OPRJ Projects

Aproval Proceudes (we need a way to create documents (quots, invoices) via DI-API taking into account the aproval procedures and store depending on the procedures as a draft and sending the request)

Document: Header Footer

Greetings from Cologne, Germany

[Former Member]

Hi!

"OPRJ":

...is planned to be available in version "2006" as mentioned earlier in this thread.

"Approval procedures":

Thx for confirming the need ()

"Document: Header Footer":

Are you talking about PLD? Sorry, but I am missing the point obviously...

Regards,

Frank

[Former Member]

Our Main missing DI Objects:

- Expose the Print obejct

- Expose UDO's

Regards

Moty

[Former Member]

Hi Moty,

Thanks for the reply!

Sounds like nothing is wanted as much as UDOs in DI...

What about the "Print object":

Do you mean that printing capabilities should be added to DI API?

What about the "Printed" flag:

Wouldn't you eventually want to set it to "true" when your Add-On handled the printing?

Thanks,

Frank

[Former Member]

What I would most like to see is the object used internally when someone add's a document. Let me explain that one...

When someone add's a document (i.e. a Order) and hits the Add button, we want to add some business logic. Say we want to check every line, we have to loop trough the matrix and get all the values we need. This is a very slow procedure because we are not allowed to use the datasources.

Now I can't imagine SB1 isn't internally using the Document object for this. So isn't it possible we get access to this...? It would really boost performance. Please?

And also I'm desperatly needing the print object, so I would like to be able to start printing from the DI. (Select a PLD template and print a document)

Kind regards,

Rowdy

[Former Member]

Thanks for your reply (here and in the "Urgent" thread...)!

You are talking about something like an Implementation DLL for system objects - not just for UDOs... - i.e. some functional piece beneath the GUI that would get called just like the UDO Implementation DLL...

Moty Moshin's team was asking for the same just recently; we will take a note on that - and I know that it would resolve a lot of performance issues...

Re Printing:

Right that's a very common need too.

Thanks again,

Frank

[Former Member]

Mostly repeating what others have already asked for, and I myself have asked about on many occasions:-

1) UDO support

2) Delete production order lines

and an annoying little one that I found last week

3) Delete a contacts (Activity) object

Support for adding/updating and using stored procedures, views and additional indexes on standard tables (eg. let us add an index for recontact onto OCLG) would also be good, and help a great deal in improving performance of our add-ons.

John.

[Former Member]

Hello,

Please include the oDrafts for the Inventory Transfer. I'm currently updating the Draft's FromWareHouse through update query after saving the Draft Document.

[Former Member]

Hi,

I belive, OFCT (FORCAST) was not exposed fully.

B Ravi Shankar

[Trinidad]

Hi Ravi and Ibai,

In the SalesForecast object (exposed starting from 2005 SP01 version) you said there are missing properties.

Can you please specify which properties you need the most?

Thanks

Trinidad.

[rasmuswulff_jensen]

Hi. Just read on the Partner Portal that SBO2006A will change name to SBO2007A (Beta = Jan. 2007 | Rampup: March 2007 | Release: Q4 2007!) ... Does this mean for the SDK that all discussed here will first be available a year from now (to release to customers i mean... Or will some of this get into SDK for SBO2005A SP01 on the way)???

[Gianluigi]

Rasmus hi -

as already said in this forum, this is just to collect your needs. The information

about availability and schedule will follow the usual official channels. There is

nothing here that can be officially communicated to customers. It is a community

exercise that we believe is very useful to direct future product developments.

Gianluigi

[rasmuswulff_jensen]

OK... In that regard... Will you later do a survey of the UI and DI-Server later?

Message was edited by:

Rasmus Jensen

[Gianluigi]

Rasmus -

if you have a wishlist for UI or for DI Server go ahead and write it down in this

thread. This is mainly for objects but we are interested in hearing also other

needs.

Gianluigi

[Gianluigi]

Matt -

this thread is just to collect your wish-list. Which are the DI objects and

properties you are missing the most now ?

There is nothing here that should be communicated to customers. All the

communications to customers must follow the official channels. But it is

interesting for us to understand the needs of the community.

I hope I clarified the sense of this thread

Gianluigi

[Former Member]

Gianluigi,

I have already noted a request for deletion of Production Order Line Items earlier in the thread.

We have followed official channels in the past with little/no help. I'm just curious as to which requests in this thread you'll be looking at implementing in the near future. Will you let us know (unofficialy even?) through this forum or will we just have to wait and see as tends to be the case at the moment. As you can imagine, the wait and see approach can be very frustrating both for the customers, and the developers they complain to...

[Former Member]

The property CHAPTERID in ITEM DIAPI is MISSING

and it is mandatory in the object. I am not able to store item details thru the object.

Amal

Nastek Solutions, MUMBAI

[Former Member]

Hi Amal,

Are you talking about the Item<u>s</u> object in DI API?

...and eventually some property that is specific for 2005B or 2004B?

I didn't hear about a mandatory property missing in the Items object - and I would expect this to be found as one of the first issues...

...or is it mandatory only in a sepcific country?

Could you recheck/ provide more details?

Thanks,

Frank

[Former Member]

Frank / Gianluigi,

Would you be able to provide some feedback as to which objects/properties you will be looking at / implementing from our suggestions?

It would be nice to be able to relay some information to the customer.

Many thanks,

Matt

[Former Member]

Hi Frank,

yes it is with DI API,item object say,

dbtab = dbds.Tables("Table")

For intCount = 1 To dbtab.Rows.Count

Dim vItem As SAPbobsCOM.Items

vItem = vCmp.GetBusinessObject(BoObjectTypes.oItems)

vItem.ItemCode = dbtab.Rows(intCount)("GRP")

vItem.ItemName = dbtab.Rows(intCount)("TEX")

RetVal = vItem.Add

If RetVal <> 0 Then

vCmp.GetLastError(ErrCode, ErrMsg)

MsgBox(ErrCode & " " & ErrMsg)

Exit For

End If

Next

on adding this item i'm getting error saying invalid code[OITM.ChapterID]

it seems chapterID is being mandatory for insertion of item

Regards

Amal

[Former Member]

Table: CUDC

I would like this table can be exposed to developer.

otherwise if i want to add a categroired in a UDF form. we have to use the sql

thanks!

[Former Member]

an other functionality (service) needed is the possibility to manage the user defined fields of the form with the DI.

When we create an ISV AddON, we create fields on system object. It would be great be able to create categories, beeing able to set fields visible, active on the form that contains all the user fields. This functionality is only avaliable thru the application.

Like this the customer can create its own user fields, and he would see only them, and not the AddOn fields on the form

the problem today is that we can't let them acces this form, as they can access to our user fields, and modify the value while we can have some business logic linked

Sebastien

[Former Member]

I totally agree with sebastien, and the related table is OQCN.

UPS... mixed category tables. CUDC is the right one as said in the next post.

Ibai

[Former Member]

oItems in DIAPI not having excise information

For example : excisable item YES/NO in item master

regards

Amal

Nastek, MUMBAI

[Former Member]

An inportant feature that we surely miss is in the DI api is the Downpayments

(ODPI).

[Former Member]

Hello,

1. Visual Order (Read/Write) exposed from the DIAPI on Document_Lines object.

This will be very helpful when insert and update Sales Orders, Quotations, Invoices.

2. Alternative Item (OALI) Inventory->Item Management

Regards,

Sheetal

[Former Member]

1. The ability to delete Production Order lines (WOR1). This is crucial for a customers requirements and we have already raised a message with SAP only to be told there were no timeframe to include it to the SDK.

[Trinidad]

Hi Sheetal,

What you are asking in point 1. is the possibility to specify the position in the lines order you want to add a new line?

Something like insert(pos) or add(pos) method???

Thanks

Trinidad.

[Former Member]

Hi,

Trinidad, I made a mistake. Forecast are OK, but we would need to be able to add Order Recomendations in the ORCM table.

Regards,

Ibai

[Former Member]

In terms of priority, for us UDO's are the most important objects not exposed.

Regards,

Ian

[Former Member]

For migration purposes, an important object missing both in DI API and DTW is the Document Installments (<b>INV6</b>). Which would also be particularly useful when you have user fields for Addon use.

[Former Member]

- UDO Objects is missing.

- How to transfer UDO objects from one database to another database.

- How to create UDO objects from the tables by using DI API

Thanks and Regards

Amal

Nastek Solutions, MUMBAI

[Former Member]

Appart from what I say before, we will be very interested on:

- ORCM table, Order Recomendation Report.

- OFCT table, Forecasts.

Although end users won´t be able to modify them using the GUI, we need it through DI API.

Regards,

Ibai Peñ

[Former Member]

Hello,

We want also to add an A/R Invoice with WithHolding Tax even without defining a default WTCode for that Business Partner.

[Former Member]

Hello,

- Please add also the matrix.CellHeight, matrix.TitleHeight.

[Former Member]

Hi,

we are in desperate need of being able to print documents via the DI.

Thanks

[AlexGrebennikov]

Not sure it has been already implemented in v2005 (or has been planned to implement in v2006), but the gap in 2004 is impossibility to post documents in closed/inactive period (equal to change the period using DI API).

I know it's too dangerous to give such opportunity for end users. Say it could be an option to be able to change posting period via DI for superusers only.

[Former Member]

Hello,

There should be some way to sort drop-down-list options using DI-API

If possible.....

Thanks.

[Former Member]

Invoice line comments : INV10 and similar in other documents too.

[Trinidad]

Hi Indika,

INV10 and similar tables in other Documents (for text and subtotal lines) will be covered in 2006 version.

Regards

Trinidad.

[Former Member]

Here are the two suggestions to include in DI API.

1.Allow to accept Discount amount in addition to DiscountPercent property in Documents Object

2.Allow Price Before Discount property in Documents Object

Best Regards

Ramachandran

[Former Member]

Hi,

Please incluse DI object for Prodution(OWOR), Bank codes(ODSC).

Regards,

BBN

[rasmuswulff_jensen]

Most needed from my part...

- Userdefined Objects (Table: OUDO)

- Item Discount Groups (Table: OSPG)

[Former Member]

Very usefull to us (heard this from many others too) would be the projects (OPRJ).

[Former Member]

IMHO very important:

Expose Approval procedures through DI API (or at least include DI objects into the regular approvals!)

Anyone out there who agrees?

[Former Member]

...I thought noone seemed to need that until Ingo posted this one...:

Thx!

[Former Member]

Following fields in Read Only on all DI objects that have the values in the table

- Usersign Create

- Create Date

- Usersign Update

- Update date

in general, all fields generated by the application in read only (like insid on OSCL..)

Objects that should be added:

Service Call Type (OSCT)

Service Call Problem Type (OSCP)

Service Call Status (OSCS)

Branch (OUBR)

Department (OUDP)

Predefined Text (OPDT)

Employee Role (OHTY)

Business partner properties (OCQG)

Item Master Data properties (OITG)

Hability to delete row on all objects that contain line (BOM, Production Order)

[Former Member]

Sebastian just covered most of mine but I'd also really like to see:

Projects (OPRJ)

[Former Member]

Projects should be exposed in version 2006.

...as well as DLN7 + DLN8 (packaging related stuff)

[Former Member]

- UDO objects.

- Header user fields parametrizations.

- Text and subtotals lines.

[Trinidad]

Please give us the exact name of the missing tables/objects you will like to have exposed with your priority order.

We will like to know which ones are the most important for you to try to implement them in your priority order.

Text and subtotal lines is pretty sure they will come with B1 2006A.