- About Us
- Events and Webinars
- Contact Us
Log into Oracle R12 with WIP responsibility and navigate to “View Move Transactions” form. Navigation: Work in Process –> Move Transactions –> View Move Transactions. Query up a record. Using the “Examine” functionality under the “Help” Menu and “Diagnostics” sub-menu find the block where you want to have attachments enabled. In this case W_MOVE_TXNS_V is the block for form WIPTQSFM. In addition, determine what the base table is for this form. Once you have noted what form, block and base table to use it’s time to switch to “Application Developer” responsibility as the following steps assume you have switched responsibilities.
Navigation: Attachments –> Document Entities. Query up the base table you determined in step one. If there is no record then add a record for the base table. In this case we have inserted a new record for “WIP_MOVE_TRANSACTIONS” base table. The entity ID we used “WIP_MOVE” and for the entity name we used “Move Transactions” and the prompt also “Move Transactions”. The application should be self explanatory, but just in case use “Work in Process”.
(Document categories provide security by restricting the documents that can be viewed or added via a specific form or form function. When a user defines a document, the user assigns a category to the document. The attachments form can only query documents that are assigned to a category with which the form or form function is associated).
Navigation: Attachments — > Document Categories. Query up the category starting with “WIP%”. If no category exists then create a category. In this example I have used “WIP Move” as the category name and assigned to the Work in Process application. Save the record.
Navigation: Attachments –> Attachment Functions. Query up functions starting with “WIP%” if the function you are looking for does not exist you will need to create new record. In this example I have created a new function called “WIP_WIPTQSFM” designating the form from step 1 above. The User Name field we called “View Move Transactions” and verified the “enabled” checkbox was checked. Next click on the Categories button and assign the category from the previous step to this function. (We used “WIP Move”. Next click on the Blocks button and enter the block name from step 1 above (”W_MOVE_TXNS_V”) and set the method to be “Allow Change”. Next click on the entities button. Use the LOV and select “Move Transactions” as the Entity defined in step 2. The display method can be set to “Main Entity”. You can leave the “Privileges” and SQL statement tabs default. However, you will want to change the primary key fields to the following: Key 1: PARAMETER.ORG_ID and Key 2: W_MOVE_TXNS_V.TRANSACTION_ID. Note: You must have at least one key defined. Enter the names of the fields in the calling form from which the primary keys for the entity can be derived. Use the syntax block.field. You must include the block name (for example, W_MOVE_TXNS_V.TRANSACTION_ID). Use the unique column on the base table if you must.
Once you have completed these steps you can test out the “enabled” attachment functionality by switching to a Work in Process responsibility and navigate to “View Move Transactions”, query up a transaction and the attachment icon should now be active.
You can also find out more on attachments by searching Oracle Metalink!
Centroid is a cloud services and technology company that provides Oracle enterprise workload consulting and managed services across Oracle, Azure, Amazon, Google, and private cloud. From applications to technology to infrastructure, Centroid’s depth of Oracle expertise and breadth of cloud capabilities helps clients modernize, transform, and grow their business to the next level.