Arif's Profile
Agile Angel
2342
points

Questions
19

Answers
172

PLM Enthusiast since 2011. Like Developing extensions,utilities,scripts and provide Configuration and Support on PC,PPM, PG&C, PQM,PCM on 9.3.5,9.3.3 and 9.3.2,9.34 Experienced in dev,config and design on PLM4P(6.0.0.3 till 6.1.1.x)
Title Agile PLM Technical Consultant
Company Company Not Entered
Agile Version 9.3.5, 9.3.3 , 6.X.X.X.,9.3.4
  • Did you set up necessary criteria and privilege for that. Recommend you to go through Admin guide.

    • 31 views
    • 1 answers
    • 0 votes
  • Agile Angel Asked on November 5, 2018 in Product Collaboration.

    Agree with you Swagoto. Have seen this behavior, it does override in 9.3.5 that i am using.

    • 157 views
    • 3 answers
    • 0 votes
  • Agile Angel Asked on November 5, 2018 in Agile PLM (v9).

    Hi Raju,

    Please find the attached query for getting where-used details. Different organization utilize the WhereUsed concept to suit different business purposes like determining unique part assembly etc. There are lots of additional fields that is incorporated as part of business requirements.

    The Select query shared is used to give standalone details of an Item and it’s corresponding where-used items. In below query just replace the item number i have mentioned with one you have.

    However if your requirement is building a reports for user, i suggest you to write a procedure by passing item number as input. You can utilize the below query for that purpose.

    ——————————————————————————————————————————————————
    SELECT
                 LEVEL,
                 NVL (N1.DESCRIPTION, ”) AS “Part Type / Document Type”,
                 I1.ITEM_NUMBER,
                 I1.DESCRIPTION AS “Part Description”,
                 NVL (N2.DESCRIPTION, ‘Preliminary’) AS “Lifecycle Phase”,
                 I2.ITEM_NUMBER AS “WhereUsedPartNumber”,
                 A.QUANTITY AS “QTY”,
                 NVL (N3.DESCRIPTION, ‘Preliminary’) AS “WhereUsedLife”,
                 I2.DESCRIPTION AS “WhereUsedPartDescription”
          FROM   AGILE.BOM A,
                 AGILE.ITEM I1,
                 AGILE.NODETABLE N1,
                 AGILE.NODETABLE N2,
                 AGILE.REV R,
                 AGILE.ITEM I2,
                 AGILE.NODETABLE N3,
                 AGILE.REV R1
         WHERE       A.ITEM = I1.ID(+)
                 AND I1.SUBCLASS = N1.ID(+)
                 AND I1.ID = R.ITEM(+)
                 AND I1.DEFAULT_CHANGE = R.CHANGE(+)
                 AND R.RELEASE_TYPE = N2.ID(+)
                 AND A.COMPONENT = I2.ID(+)
                 AND I2.ID = R1.ITEM(+)
                 AND I2.DEFAULT_CHANGE = R1.CHANGE(+)
                 AND R1.RELEASE_TYPE = N3.ID(+)
    START WITH   (A.COMPONENT =
                     (SELECT   DISTINCT B.COMPONENT
                        FROM   agile.item i, agile.bom b
                       WHERE   i.item_number = b.item_number
                               AND i.item_number = ‘240-032279’)
                  AND NVL (A.change_out, 0) = 0
                  AND (SUBSTR (A.flags, 5, 1) = 1)
                  AND A.id NOT IN (SELECT   C.prior_bom
                                     FROM   AGILE.bom C
                                    WHERE   C.item = A.item))
    CONNECT BY       PRIOR A.ITEM = A.COMPONENT
                 AND NVL (A.change_out, 0) = 0
                 AND (SUBSTR (A.flags, 5, 1) = 1)
                 AND A.id NOT IN (SELECT   B.prior_bom
                                    FROM   AGILE.bom B
                                   WHERE   B.item = A.item)
      ORDER BY   LEVELRegards,

    ————————————————————————————————————————————————————————

    Regards,
    Arif

    • 75 views
    • 2 answers
    • 0 votes
  • As i see you are using 9.3.5.  In case you have SSO enabled, Can you check what is the value of agile.sso.expirationTime is set in agile.properties file. By default it is set to 120, if that’ s the case then you can  try to set it to a higher value once say 120

    Go for a clean restart i.e. shutting down admin and other nodes. Deleting server cache folders and bring up the Admin and nodes thereafter.

    • 142 views
    • 6 answers
    • 0 votes
  • Yes Mayur. If you want to restart then. Logon to server

    Navigate to –> /Agile/Agile935/FileManager/bin
    First Execute : shutdown.sh
    Then Execute: startup.sh

    • 142 views
    • 6 answers
    • 0 votes
  • Hi Mayur,

    That can be due to multiple reasons. Can you ensure this two things to start with:

    1. Check if your file manager server is up and running. Generally your file-server is “http://ServerName:8080/Filemgr/Configuration Check if this page loads properly or not. If not then try re-starting it once.
    2. If 1 is alright then Check if there is enough space on server.

    Regards,
    Arif

    • 142 views
    • 6 answers
    • 0 votes
  • Agile Angel Asked on October 31, 2018 in Product Collaboration.

    Hi Steven,

    You can look up to this thread –> http://myagileplm.com/questions/reg-agile-automation/
    I have shared step by step details of bulk attachment upload using File-Load utility.

    Regards,
    Arif

    • 78 views
    • 7 answers
    • 0 votes
  • Hi Mayur,

    Are you trying to get the lifecycle phase of BOM-Items ? You can elaborate the question.

    If your requirement is to get Lifecycle phase  you can use the below code.

    You can use the below code for reference.

    IItem item = (IItem) m_session.getObject(IItem.OBJECT_TYPE, “711-021263”);
                    String lifecycle = item.getValue(ItemConstants.ATT_TITLE_BLOCK_LIFECYCLE_PHASE).toString();
                    System.out.println(lifecycle);

                    ITable bomTable = item.getTable(ItemConstants.TABLE_BOM);

                    Iterator<?> myIter = bomTable.iterator();

                    while (myIter.hasNext()) {
                        IRow m_row = (IRow) myIter.next();
                        String life = m_row.getCell(ItemConstants.ATT_BOM_ITEM_LIFECYCLE_PHASE).toString();
                        System.out.println(
                                “Lifecycle of bom ” + m_row.getValue(ItemConstants.ATT_BOM_ITEM_NUMBER) + ” is ” + life);

                    }

    Regards,
    Arif

    • 61 views
    • 2 answers
    • 0 votes
  • Agile Angel Asked on October 25, 2018 in Other APIs.

    This is a common issue which most of us faced. Did you ensure these things:

    1. As suggested by Madhu, please ensure that you have added META-INF –> Services –> com.agile.px.ICustomAction –> YourPackageName.YourMainClassName  
    (this is for action based PX, for even based use the related deployment descriptor)
    Also ensure the META-INF folder is added at the same level as that of your Source folder in the project.

    2. If you are deploying the solution on a clustered environment, please ensure you have copied to “../Agile/Agile935/integration/sdk/extensions”  path on all the individual nodes.

    Please re-try after that. At times i prefer closing existing Java-client and relaunching it to see it in Javaclient.  It should work.

    • 75 views
    • 3 answers
    • 0 votes
  • Agile Angel Asked on October 24, 2018 in Product Collaboration.

    The particular table i have shared doesn’t have exact the same naming convention as Java-Client. Back-end tables are created bit differently.

    If you want to see the exact same information you can use the below query but i am not sure how it traces it to the object name. Maybe other experts can guide you on that.

    SELECT * FROM NODETABLE WHERE DESCRIPTION=’CRITERIA_NAME’ AND PARENTID=3642

    As i see, go ahead with approach 1/2, looks the best fit for purpose.

    • 172 views
    • 21 answers
    • 0 votes