I have to create a thorough interface for projects, tasks, chores, chores and events. Should I create a single assembly table or package for all api il or separate tables and packages? Let me know a better approach and please provide the technical design and code for the interface. Hello Krish,Unless you use a third-party project system, then it might be taking a look at the More4Apps software suite, there are solutions to do all of the above, prefabricated by Excel designed for your end user. 1) Create a project with the respective PSP structure and other information needed mainly classifications.2) Now that the structure is created, try to bring in budget information. Baseline it.3) Funding the project with agreements.4) Create events now. Thank you for your quick reaction. My requirement is that once projects have been created, we need to define agreements and funding amounts on Rs 1 and core funding to establish billing events. Please send an example code. 1) pa_project_pub for Project and wbs2) pa_budget_pub PA_PROJECTS_PUB can be used to create your projects and tasks, but you must respect all required key members and other quick entry elements, as you need to integrate them.
The API misrepreses some errors in multi-line objects. You can use composite or load/execute/fetch procedures in the API. There are many errors and omissions that require circumvention of problems. We take data from another system. Enter the sample code for the above requirements. For tasks, the situation is even more complex. Is the structure of the order of work activated? If so, will the financial structure be shared with the structure of the order of work? Is the version activated? You may need to publish or you may not be able to use the new tasks. Baselining does not create billing events. PA_EVENTS_PUB is used to create billing events. This is straighter without significant errors. The basic API details required for this task are: For more information, see the project API manual B34956_01. This will guide you on how you use the APIS.
This is a very complex area and there are many obstacles to overcome. If you are trying to develop basic knowledge without a good module project, this will be a difficult task for you and costly for your client. For all these APIs are public. You can use API assistant software to easily work with these public APIs without programming, i.e. no need for code. Then create agreements and funding lines with PA_AGREEMENT_PUB. The procedure in this API for baselining funding does not work in certain circumstances. In these cases, you must use a private API. The IP needed to overcome these barriers is not included in any development platform. This is a complex interface where I think you should create a separate editing table for each info (just for voting) and where you have to keep an overview of all the classifications.
If your solution can use MS-Excel to load, the recommendation for using More4Apps is based on more than 16 years of development using project module APIs. Be very skeptical of anyone who says that a basic substitute for ADI can solve your problems and eliminate all this complexity for you. As for the code, there are a lot of references posted on the web by our gurus.