Another useful property will be a default value in the page customization. You can put default value for extension but not for standard fields… yes you can do it through template you will say!
Ok do a template and try to force the user to only create a project through template…
No you can’t because you can’t remove the create button on all the report of project for e.g. If you do so it will remove it also the create button on all report and then you can’t create new localized resource or vendor for example.
Hi,
there is a bug on the next event due date. If you create a project from a template, the next event due date is the date of the creation of the template.
Even if this problem is corrected once you change phase it’s not normal because all your tasks will appear red when they shouldn’t.
This bug should be resolved in the release 5.1.05 that should be out mid august.
Hi,
This week I begin a new series of post with some missing functionality that client often ask but missing in SAP E-sourcing.
The first and the most important functionality that is missing in sap e-sourcing is really a web2.0 interface. Now when you make a page custom on the field and you want to set a dimension on another field it will not work unless you reload the page.. what a pity when all user can see on any application on the web field that appears only if some conditions are meet..
In the toolbar customization you haven’t all the detail level that you should have. For example sometimes you want that the user use only the template to create a rfx or an auction but you can’t hide the create rfx button on reports.
For the collection it’s the same, sometimes you want to remove the delete or the reorder button but if you do it it will disappear on all collections.. What could be a bad idea.
Today I’ve met a real problem. I was developing a script, I’ve put it on the platform, test it, then I saw that I had a problem in my script. I changed my script and when I have try to access my script again on the platform, a page has appear saying that I can’t access this page anymore.
I thought it was a problem of cache or that I should restart the platform. I made it but still facing the same problem.
I sent a message to sap and after some (long) hour I received a response. SAP saying that it’s a known bug and that we can’t do anything to make it works again…
My script is to heavy to be displayed it makes 65kb whaw and that generates a java stack overflow…
The only things to do is to install sap e-sourcing 5.1.04.
We are in 5.1.03 and we have already another bug that will be solved in the 5.1.05 that will normally be out mid-august 2009.
So it means 2 platform upgrade in 15 days.
Thanks SAP…
So I’ve got a great question, does it exist an official mailing or google group for developer in SAP E-Sourcing?
So we can know when there are new release, when a bug has been found or when he will be resolve. So those kind of things will not block me and my clients again…
When you use E-Sourcing, you’re better to set conventions before beginning a project.
Here are some important convention used in SAP E-Sourcing:
FCI-… those three letters are set at the begining of an internal name. Itcan be a table, a report, a query, etc.. Never use this in your name, so you can see what is standard and what’s you’ve created.
A good convention is to start all your internal name with the three letters of your clients. E.g: you add a new field for the client named ABCorp, you will begin all your internal name with ABC-.
For the name, keep in mind that in SAP E-Sourcing each word begin with a capital letter eg: FCI-InactiveActivities.
When you must define a bundle name ressource, don’t forget that this bundle name is case sensitive! E.g: ABCorp is different from abcorp.
In queries, when you use a table, it’s better if you precede the table name by <%SCHEMA%>. This token ensure that you use the good database schema. E.g: FROM <%SCHEMA%>.FCI_PRO_PROJECTS T1. If you use an extensin table you can also precede the <%EXT_TABLE(classlogicalname)%> by <%SCHEMA%>.
Still in queries, the WHERE clause have some conventions:
- The first convention is to set T1.INACTIVE = 0, so the query doen’t display the inactive project contract of whatever is in the table T1.
- The second is to set T1.IS_TEMPLATE = 0, so the template aren’t displayed in the results.
- The third convention is to set T1.CONTEXTID = <%CONTEXT(projects.projects)%>. So you are sure that the documents come from the proper context. (Here the context is projects.projects for FCI_PRO_PROJECT, but don’t forget to change the class logical name(projects.projects) with the class logical name that you want to use!)
If in the result you use a function you can also precede it by <%SCHEMA%>.
Let’s talk about the special SQL function develloped by SAP E-Sourcing.
Those functions have no documentation, so I will explain the first function that I’ve discovered.
The SQL function FCI_DOC_CUR_CONVERT allows you to convert a currency to another one. This function has three parameters. The first parameter is the value that you want to convert, the second parameter is the initial currency object ID and the third parameter is the target currency object ID.
An exemple of use could be FCI_DOC_CUR_CONVERT (FCI_PRO_PROJECTS.BUDGETED_PRICE, FCI_PRO_PROJECTS.BUDGETED_CURRENCY, <%COMPANY_CURRENCY_OBJ_ID%>);
the <%COMPANY_CURENCY_OBJ_ID%> will return the object ID of the currency that is set for the company associated with the current logged-in user at the time of query execution.
I’ve searching some hours before I can’t ind it, looks in all table an can’t see any vendor comment. This comment is only displayed in the vendor side, so I’ve got no RG in this part.
Finally I’ve made some tests and I’ve found that the vendor comment was called BUYER_COMMENT! Thank you frictionless….
You can find this field in the table FCI_ONT_LINE_ITEM_RESP
