Try removing the app owner, or try replacing it with &AO. OMS_E_INV_SEQ_NO.NEXTVAL&AO.OMS_E_INV_SEQ_NO.NEXTVAL
IFS wants you to develop operational reports using only the _REP view.For example, you might want to join from CUSTOMER_ORDER_IVC_REP to CUSTOMER_INFO_CFV to go retrieve a custom field for a customer to put on an invoice.Joining the _REP view to another view can expose other data. In my experience, though, if your join condition is intelligently designed, this isn’t a problem.
If you're willing to be naughty, copy PROD to TEST, then do this in TEST first...UPDATE transaction_sys_local_tab SET queue_id = /* new_queue_id */, state = 'Posted', started = NULL, executed = NULL, error_text = NULL, sid = NULL, serial# = NULL WHERE id IN (12345678, 12345679, 12345680);Alternatively, go to Batch Queue Configuration, move those procedures to different queues, then create brand new jobs to duplicate the old ones. You can move a procedure by dragging it from one queue to another with the mouse.
Did you grant it? GRANT SELECT ON ifsapp.my_sequence_id TO ifssys WITH GRANT OPTION;GRANT SELECT ON ifsapp.my_sequence_id TO fnd_enduser; // or your preferred permission set Edit:Actually, this is coming from the application:ifs.fnd.services.plsqlserver.service.security.RejectedSqlExceptionI’ve never seen this error with a custom PL/SQL block. It typically lets you do pretty much anything. Is your block surrounded by BEGIN and END? Can you provide more details?
For a full list of last logins in Apps9 and Apps10 you can simply use the following… I don’t believe any specific auditing needs to be turned on to enable this: select username, last_login from SYS.DBA_USERS where account_status='OPEN' order by last_login desc; However, based on the Author’s later reply the above query will not track Azure AD authenticated account logins. Nick We were doing this - but after update to Oracle 19C it all seems to have fallen over - the table has not been updated since, other than for IFSAPP and other system users. Very strange This changed with 12.2. LAST_LOGIN was introduced with 12.1.0.2.https://docs.oracle.com/database/121/REFRN/GUID-309FCCB2-2E8D-4371-9FC5-7F3B10E2A8C0.htm#fnsrc_d1205367e629Starting with 12.2, when using proxy user authentication, only the proxy user will get their timestamp updated. With IFS Applications, that means IFSSYS will stay current, while the end user account will not get updated. That’s useless for us.htt
Profile entries are not in First Normal Form. They’re concatenated in CSV format for IEE or in JSON format for Aurena. If you add a field, it will need to be added to the OutlineNames entry. All the other entries like Left, LeftLabel, Top, TopLabel, etc. will need to be shifted by the same degree.Old:OutlineNames: FIELD_A,FIELD_B,FIELD_DTop: 100,120,140New, broken by the system:OutlineNames: FIELD_A,FIELD_B,FIELD_C,FIELD_DTop: 100,120,140(This moves the value 140 to FIELD_C and leaves FIELD_D with no value.)New, fixed by you:FIELD_A,FIELD_B,FIELD_C,FIELD_DTop: 100,120,160,140
It looks like you need to increase your shared pool size. The way to do this depends on whether you’re using Automatic Memory Management, Automatic Shared Memory Management, or manual memory management.What are the values of each of these parameters?shared_pool_size sga_target sga_max_size memory_target memory_max_target pga_aggregate_target pga_aggregate_limit
It’s worth asking whether they’re using the system correctly, and this isn’t necessarily a matter of opinion. Why would they pay for an ERP system and then not use it?
Create a PL/SQL block that sends an email via a background job. (My example assumes you have a mail sender MAIL_SENDER_HTML. Yours is probably something like MAIL_SENDER1 if you haven’t changed it.)DECLARE attr_ VARCHAR2(32767);BEGIN client_sys.clear_attr(attr_); client_sys.add_to_attr('FROM_USER_NAME_', fnd_session_api.get_fnd_user, attr_); client_sys.add_to_attr('TO_USER_NAME_', fnd_session_api.get_fnd_user, attr_); client_sys.add_to_attr('SUBJECT_', 'This is your subject line.', attr_); client_sys.add_to_attr('TEXT_', 'This is your message body.', attr_); client_sys.add_to_attr('MAIL_SENDER_', 'MAIL_SENDER_HTML', attr_); -- client_sys.add_to_attr('ERROR_TEXT_', NULL, attr_); -- client_sys.add_to_attr('ATTACH_', NULL, attr_); -- client_sys.add_to_attr('CC_', NULL, attr_); -- client_sys.add_to_attr('TIMER_', NULL, attr_); -- client_sys.add_to_attr('AUDIT_', NULL, attr_); -- client_sys.add_to_attr('FROM_ALI
I’m not sure why default values aren’t available in the application for numeric fields. Here’s a hack to use what’s already there.To demonstrate this, here’s a custom LU with a single field: The field is Persistent, Number, Unformatted, Insertable, Updateable, Searchable, LOV, Indexed, Public, Approved.Before publishing, I created the sequence and did a hack against the custom field table to set an expression default value.CREATE SEQUENCE c_demo_seq INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 10;UPDATE custom_field_attributes_tab SET default_value_type = 'EXPRESSION', default_value = 'c_demo_seq.nextval' WHERE lu = 'CDemoSequence' AND attribute_name = 'ID';COMMIT;Published.Created custom page, Table Window, and granted.Now subsequently hitting F5 produces new records with numbers pulled from the sequence:
Oracle 12 allows for 60 characters in object and column names. Thanks. I see now that they’re on Apps 10.12cR1 only supports 30.12cR2 goes up to 128.
Under System Parameters, in the "Reporting" category, check these settings:"The machine name where the Crystal Web Service is installed""The protocol of the Web Server where the Crystal Web Service is running""The IIS port for the above mentioned Web Server""The Virtual Directory names given to the Crystal Web Service instances in IIS"These can't be the same in Test as they are in Production because the Crystal engine connects to the database. You'll need a separate Crystal Web Services instance for each environment.
Hi,This error suggests you're running out of TEMP space, and it's because your joins are doing a lot of extra work.http://www.dba-oracle.com/t_ora_12801_parallel_query.htmThe TO_DATE function is intended to convert a string into a date. If you want just the day portion of a date, it's better to use TRUNC.There's no index on DATE_ENTERED, but there is one on HISTORY_NO that we can leverage.I recommend that aliases should be descriptive whenever possible.Oracle names can only be 30 characters long. (ENTERED_TO_CONF_PRINTED_DAYS_TAKEN is 34.)Here's a revised query: SELECT planned_.order_no, planned_.date_entered AS entered_date, planned_.userid AS entered_userid, planned_.hist_state AS entered_state, released_.date_entered AS released_date, released_.userid AS released_userid, released_.hist_state AS release_state, order_confirmation_printed_.date_entered AS conf_printed_date, order_confirmati
Where would I find either the API Explorer or the particular restful service I would need?
We’re running Apps 9, and we sign both IFS Enterprise Explorer and IFS Sales and Marketing with the same certificate that we use for HTTPS.This makes the message to the users a little less scary, gives us the option to crank up the security settings, and doesn’t train the users to ignore invalid certificate errors. Apps 10 now folds the application signing into the same step as the installation, and the default behavior is to use the same certificate for the application as for HTTPS, exactly as we do today in Apps 9.Are you using a trusted certificate for HTTPS?
You may want to look at the GROUP BY clause. This should be your first choice before using analytical window functions.
I frequently use the WITH clause. It works well when you know you want to force materializing a smaller result set before joining it with a larger one. If you don’t pre-filter your results, it will result in a slower execution plan.The WITH clause doesn’t look like valid SQL in a Quick Report, so you have to wrap it with a SELECT.SELECT * FROM (WITH my_with AS (SELECT /*+MATERIALIZE*/ 'Hello World' AS msg FROM DUAL)SELECT msg FROM my_with)(There is no such limitation when you’re creating an IAL.)
We use PL/SQL when we need to do a lot of this.BEGIN fnd_user_role_api.set_role('USER1', 'PERMISSION_SET1', TRUE); fnd_user_role_api.set_role('USER1', 'PERMISSION_SET2', TRUE); fnd_user_role_api.set_role('USER2', 'PERMISSION_SET1', TRUE); fnd_user_role_api.set_role('USER2', 'PERMISSION_SET2', TRUE); security_sys.refresh_active_list__(0);END;/If you don't like that, you might consider building your own import XML. I’m attaching a template you might use to do this in Excel.
If you find these documents are stored in the database and not over the network...Do you know if the IFS backup and restore process uses the legacy EXP/IMP utilities? If so, you would need to upgrade to the Data Pump EXPDP/IMPDP utilities to get LOB capabilities.To quickly test this, can you open any PDFs in the report archive?
I know I should use .add_to_attr but I’m an old dog and still use chr() method. Maybe I’ll update my templates one day! Probably the most compelling reason to use ADD_TO_ATTR is that it has an overload to automatically format DATE values. You won’t have to think much about your data types.
Hi @paul harland & @KristenGastaldo, Do you know if IFS are able to supply a list of LU’s that do not support custom fields so we know for future? I don't remember if this is available in Apps 8, but in Apps 9, at least, you can go to Solution Manager --> User Interface --> Custom Objects --> Excluded Logical Units.
One thing that debugging won’t show you is how to build values for the attr_ string. I used to concatenate CHR(31) and CHR(30) until I learned about the CLIENT_SYS package. /*IFS logical units have base views and base packages.Let's assume we have the logical unit HelloWorld.It'll have a base view HELLO_WORLD and a base package HELLO_WORLD_API. (Eachchange in character case, which represents a new word, is represented by anunderscore, since Oracle object names aren't ordinarily case sensitive.)*/DECLARE info_ VARCHAR2(32767); -- I like to use %TYPE constructions whenever possible. -- They make the code more self-documenting by revealing the purpose of variables. objid_ hello_world.objid%TYPE objversion_ hello_world.objversion%TYPE; attr_ VARCHAR2(32767);BEGIN -- This sets attr_ to NULL, but the exact implementation may change client_sys.clear_attr(attr_); -- This fills in the default values for a new record hello_world_api.new__(info_, objid_, objve
I think @alackas has made a similar migration, but they’re no longer on version 8.
We ran into problems upgrading from Apps 8 to Apps 9. From our thinking, "view" access on a document class should include *every* document in that class.We programmed a work-around that runs every hour. Under every Document Revision, Access tab, Definition tab, we populate records with all the necessary groups and their corresponding access rights.
The services exposed by IFS Applications 9 aren’t nearly as advanced as those exposed by Apps 10. Apps 9 does offer an Interface Browser:http://domain:port/interfacebrowser/#/
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
