Hi Arvin, SCMNet is a integration between Agile and ERPs developed by Hitachi Consulting. This integration is capable to create items, BOMs and Change Orders in the ERP originally created in Agile and it can return data changed in ERP to Agile related to the changes.
In Hitachi’s words:

SCMnet™ is a highly configurable integration application that deploys seamlessly between the Agile and ERP systems and uses standard interfaces to transfer product change records from the PLM to ERP. When a Change Order is released in Agile, the Item, BOM, AML and Change information is captured in an AGL (ChangeCAST) or XML
(ACS) file. SCMnet™ retrieves this information, applies transformations to the data in accordance with pre-configured business rules, and propagates the updated information
into the ERP system. All of this processing happens behind the scenes, without the need for any user intervention, and may be monitored using a user-friendly browser-based GUI.
SCMnet may be configured to notify users in case of successful/failed transfer of ECOs.
Please refer to the attached file for more info.

My best Carlos

Hi Venkata,

I’d suggest you shutdown file manager and start it again.
Sometimes Tomcat stops working without any signal.

My best
Carlos

Hi Smitha,

what is the kind of object do you intend to mass update?
You can use the Import utility to do it, it’s a safer method.

Regards
Carlos

Clóvis, I reproduced your issue on a 9.3.5 version environment.
It seems that is nor working as required, I suggest you raise a SR.
I went a little bit further in tests over here and I realized that if the item is related to only one site, the “not in” search works fine, but if the item is related to more than one, it doesn’t work as required.

My best
Carlos

Shrivatsak,

you can still do exactly what were asked using Antonio’s suggestion.
Anyway, you can look for more info at Agile Product Lifecycle Management Administrator Guide

21.3.3 Invoking Notifications Programmatically

SDK and Scripting enables notifications to be sent out programmatically. A notification invocation uses the following parameters, whose use is explained:

• SendNotification – the program module or method used to send out a notification.

• Notification Name – the name of the notification.

• Urgent – whether the notification is to be flagged as Urgent or not; the value can be True or False.

• Addressee List – list of users who may be notified; this set of values is appended to the list of people listed in the “To” field of the notification. This list of Addressees is only picked up if $NOTIFY is assigned in the “To” field.

• Comment – refers to the comment passed to the Comment data tag, if assigned in the notification template.

• Object – an object of the type corresponding to that associated with the notification in its definition. For example, an ECO object must be passed to a notification tied to a notification associated with the ECO subclass (it can also be passed to a notification tied to the Change Orders class or Changes base class). This object is used to derive the values of variables used in the notification Subject, Body, and To fields.

For more information about sending notifications using Agile SDK, see Chapter 9, “Subscribing to Agile PLM Objects” in the Oracle Agile PLM SDK Developer’s Guide.

Carlos

Well done Arif, pretty forward example.
Thank you for sharing.

My best
Carlos

Venkata I got interested on that matter and I found at

http://www.oracle.com/technetwork/indexes/samplecode/agileplm-sample-520945.html

a groovy sample code that can do exactly what you are looking for, at the page provided search for a file called GenerateItemDescriptionPX.ZIP. It provides the step-by-step on how to create item descriptions based on attributes concatenation.
You can go a little bit further creating events type: Create Object and Update Title Block.
You also can modify “modify parts” privilege avoiding users to modify the automatic created descriptions.

Enjoy, I did.

My best
Carlos.

Hi Venkata, it’s not possible to change an attribute type, what I mean is that the description attribute is a text type attribute and you can’t change it.
I suggest that you create required attributes that based on the choose values a groovy script will concatenate those values to create a description in the description attribute.
Post edition will be allowed.

My best

Carlos

Hi Wagner, I suggest you to create a custom search that retrieves the desired items and export the data using .agl file. On the supplier side, install Agile Express to read the file. Agile Express is a free app that can read the .agl files exported from Agile
You also can write some custom code or allow the supplier to be part of the users list.
My best
Carlos

Hi Cyn, you can change default users calendar by import.Please refer to the attached file, it contain an Excel file as import example.
My best
Carlos