Do you have the option to use Migration Jobs in Apps8 (I’m working with Apps9) with MIGRATE_SOURCE_DATA? If so, you can check what procedures/functions are used when you move one part manually (using Debug Console), create a Migration Job that calls them and supply it with the parts you want to move by writing a query to fetch them and putting it in ‘Source Name’ (remember to have it enclosed by parenthesis).
You should be able to fetch attached documents from doc_reference_object_tab - just need to find your custom LU in there (use lu_name), find specific attachment (using key_value or key_ref which should contain the objkey/rowkey) and then use Doc_Reference_Object_API.Insert_Docs to attatch your document to second LU. To build the doc_list_ parameter you should be able to use Message_SYS: Message_SYS.ConstructMessage_SYS.Add_Attribute Or write it out by yourself: '!' || chr(10) || '$DOC_CLASS=' || doc_class_ || chr(10) || '$DOC_NO=' || doc_no_ || chr(10) || '$DOC_SHEET=' || doc_sheet_ || chr(10) || '$DOC_REV=' || doc_rev_;
I’d suggest one of two options: Create another event that blocks users (whith something like Error_SYS.Record_General) from removing rows in APPROVAL_ROUTING_TAB if its &NEW:LINE_NO <> max_line_no_, where max_line_no_ is fetched with a cursor Instead of creating separate event, you can put 1. code in your existing event Both of these would require PRAGMA AUTONOMOUS_TRANSACTION (in DECLARE) - if you decide to use it I’d personally go with 1st option since you really don’t want to do anything else with autonomous transactions aside from blocking users.
I presume that your WHERE part of query is within the IAL - that should be the reason. When you use “Use data source condition”, the navigation uses conditions set in data source to filter data in form/table you’re sent to. You can try doing your data aggregation within IAL and moving WHERE to data source (shouldn’t be an issue if your IAL is set for ‘Live Data’). If you were to use different Lobby Elements you can also make use of ‘Column values’:
You can try going about it this way: Data source: You want the parameter to be in parenthesis because you’ll be supplying it with a list. This way you can also set the default value as a query. Lobby: Each value has to be in between apostrophes since it’s a string. Default value can be set to a query - fetching all possible states.
Already have an account? Login
No account yet? Create an account
Enter your username or 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.
