Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Harshith Eshwar Shaila
    Issues with Requisition ImportAnswered
    Topic posted October 31, 2019 by Harshith Eshwar ShailaBronze Medal: 1,250+ Points, tagged Requisition Import 
    38 Views, 7 Comments
    Title:
    Issues with Requisition Import
    Content:

    Hi all,

    Every mass Requisition Import through FBDI, we face a lot of issues. So is there a pre-requisite we need to follow for the data related to specific attributes before uploading the zip files.

    Next, we find the same issues even when the value provided in zip files are right, below are few errors for reference

    CURRENCY_AMOUNT 210 Amount is not applicable for goods lines. 
    ITEM_REVISION 1 The value of the attribute Item Revision is not valid. 
    ITEM_NUMBER S0210506 The value of the attribute Item is not valid. 
    SUGGESTED_VENDOR_SITE DETROIT LAKES The value of the attribute Supplier Site is not valid. 

    Note: Item provided was with right format, supplier site was available, and errors are not related to same requisitions.

    Is there a way we can tackle these issues, because need to know the exact background process how these errors are generated/triggered from technical point of view.

     

    Thank you,

    Harshith   E S

    Version:
    19C

    Best Comment

    Mara Prieto

    Hi Harshith Eshwar Shaila

    The first thing to notice is an invalid item error. When you get invalid item you will probably get a lot of other invalid errors. A lot of validations depend on the item. For description-based lines, then category is very important. For items, make sure you provide an inventory organization or the application cannot validate your item and you get the error.
    If you are providing item, then your line is for Goods, as opposed to Fixed Price Service. For Goods you provide price, and not amount. For service you provide amount, and not price.
    Below is a link of our requisition import whitepaper with the description of the columns. Even though the link below indicates Web Service, the document itself covers both, FBDI and Web Service.

    https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=193624402708676&id=2121754.1&_afrWindowMode=0&_adf.ctrl-state=448monjvt_53

    hope this helps,

    thanks
    mara

    Comment

     

    • Ashok

      Harshith

      I understand what you are saying. We do have an exercise planned in the backlog to review these error messages and perhaps provide more detail and context. But that is not going to materialize in the near or medium term due to several other customer priorities. 

      To answer your question, the FBDI template should have help or notes for each attribute. Have you explored that to see if that helps? In addition, you should be able to review the table column specs for the data model that in a few cases also helps explain what is needed for each attribute.

      Let me know if the above is not what you are looking for in terms of your question.

      • Harshith Eshwar Shaila

        Hi Ashok,

        Help/Notes and table column specs for the data model helps before the upload, where we have followed those during the upload. We might need even more specific interrelation on all the attributes and exact error messages of the issues after the upload.

        Regards,

        Harshith E S

    • Ashok

      Harshith 

      If this post is actually about asking for better (more detailed) messages that help debug the issues related to import, do me a favor. Search the Ideas Lab to see if an idea already exists. If not, please create one. But I would need more details on the difficulty that the current messages you provide here pose. You need to explain clearly as to why the message that is provided is not sufficient to debug the issue. This you can only do if you know what caused the error in the first place and once you resolve it, you take a look at the current error message and identify what can be done to improve it.

      • Harshith Eshwar Shaila

        Hi Ashok,

        Below are the errors generated with right data provided to it,

        CURRENCY_AMOUNT 210 Amount is not applicable for goods lines. 
        ITEM_REVISION 1 The value of the attribute Item Revision is not valid. 
        ITEM_NUMBER S0210506 The value of the attribute Item is not valid. 
        SUGGESTED_VENDOR_SITE DETROIT LAKES The value of the attribute Supplier Site is not valid. 

        Note: Item provided was with right format, supplier site was available, and errors are not related to same requisitions

        But these errors are displayed as collateral issues to a main issue, but finding that main issue would be problem among these collateral issues. When the main issue is resolved all the collateral issues gets resolved. Hence showing these collateral issues should be negated by highlighting only the main issue.

         

        Regards,

        Harshith E S

    • Ashok

      Hi Harshith

      You have copied the text from your first post again? Sorry I was not clearer. I read your first post and my responses were actually based on those details. You mentioned something like: When the main issue is resolved.....

      I imagine you found the main issue and then figured that these messages were not really helping identify that main issue. I can't tell from your post whether you are reporting a current and ongoing issue or an issue for which you are seeing the error messages details or lack thereof as a concern that you wish to raise. That is why I was trying to clarify exactly what your question was.

      You also say they are not even related to the same requisitions. So then I am basically looking at 4 or 5 distinct error messages and I am not quite sure how to help triage them. 

      Summary: If this is a current unresolved and ongoing specific issue, log an SR and provide the FBDI template and data that you used to support so they can help troubleshoot the specific issue. If your question is broader and more about improving the message details, then please read my earlier email asking for more details on how you resolved the same and create an idea.

      Thanks

      Ashok

       

    • Mara Prieto

      Hi Harshith Eshwar Shaila

      The first thing to notice is an invalid item error. When you get invalid item you will probably get a lot of other invalid errors. A lot of validations depend on the item. For description-based lines, then category is very important. For items, make sure you provide an inventory organization or the application cannot validate your item and you get the error.
      If you are providing item, then your line is for Goods, as opposed to Fixed Price Service. For Goods you provide price, and not amount. For service you provide amount, and not price.
      Below is a link of our requisition import whitepaper with the description of the columns. Even though the link below indicates Web Service, the document itself covers both, FBDI and Web Service.

      https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=193624402708676&id=2121754.1&_afrWindowMode=0&_adf.ctrl-state=448monjvt_53

      hope this helps,

      thanks
      mara

      • Harshith Eshwar Shaila

        Hi Mara,

        It did help actually. But i was looking specifically into information like below,

        1.

        ITEM_REVISION                 -               The value of the attribute Item Revision is not valid. 

        This issue is caused because Item is defined as not being revision controlled. If a revision is provided for a non-revision controlled item, the transaction will fail

        PIM >> Manage Items >> Search for the Item >> Inventory Specifications >> Revision Control is set to No   

         

        2.

        CURRENCY_AMOUNT                      -               Amount is not applicable for goods lines.

        QUANTITY                                          -               The attribute Quantity is required. 

        CURRENCY_UNIT_PRICE                -               The attribute Price is required.

        UOM_CODE                                       -               The attribute UOM is required. 

         

        When considering the expense lines, you also need to look at the line type.

        1.  Service line type – should include Amount but not quantity, unit of measure, or Price.
        2. Goods line type – Should include Quantity, UOM, Price, but not Amount.