Supplier Management

Get Involved. Join the Conversation.

Posts

  • Shivani Roy
    How to use REST APIs for supplier payment attributes5.0
    Topic posted November 29, 2019 by Shivani RoyBronze Medal: 1,250+ Points, tagged How-To, Supplier Profile Management, Tip, Web Services 
    Title:
    How to use REST APIs for supplier payment attributes
    Summary:
    How to retrieve and update payment attributes of suppliers, their addresses or sites using REST
    Content:

    Suppliers can be created and updated using the suppliers REST API.

    To get or update the payment attributes of suppliers, their addresses or sites, you need to use the external payees REST APIs.

    • Path: Format to be used for the request path:

               https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees

    • Content Type:application/json

               The content type of request and response is in the json format

    • Parameters

               Following table explains each of the parameters which can be used as part of the REST API call which are relevant to suppliers payment attributes.

               Sample payload is provided as part of this post.                                                                                                                                                                                                                                           

     Body Parameters

    Data Type

    Description

    PayeePartyIdentifier

    Integer

    Corresponds to the SupplierPartyId retrieved using Suppliers GET operation.

    Required to retrieve PayeeId corresponding to supplier payment attributes.

    PayeePartySiteIdentifier

    Integer

    Corresponds to the SupplierPartySiteID retrieved using Supplier Address GET operation.

    Required to retrieve PayeeId corresponding to supplier addresses payment attributes.

    SupplierSiteIdentifier

    Integer

    Identifier of a supplier site. Corresponds to SiteId retrieved using Supplier Site GET operation.

    Required to retrieve PayeeId corresponding to supplier sites payment attributes.

    PayeeId

    Integer

    Application-generated identifier of the external payee. Can be retrieved using the External Payee GET operation. Useful for PATCH operation.

    Required to PATCH payment attributes.

    DeliveryChannelCode

    DeliveryChannelName               

    String

    Code/Name of the delivery channel for an external payee.

    SupplierNumber

    String

    Application-generated party number in Procurement.

    SupplierSiteCode

    String

    Code of a supplier site.

    SettlementPriority

    String

    Priority with which the financial institution or payment system settles payments for an external payee.

    PaymentTextMessageOne

    PaymentTextMessageTwo

    PaymentTextMessageThree

    String

    First, second and third text payment message to an external payee.

    ServiceLevelCode

    ServiceLevelName

    String

    Code/Name of the service level for an external payee.

    PayEachDocumentAloneOption

    String

    Indicates whether documents payable for an external payee are prevented from being grouped with other like documents payable for payment.

    BankChargeBearerCode

    BankChargeBearerName

    String

    Code of an external payee who is responsible for paying regular or express bank charges, such as Payee or Payer. Values are from the IBY_BANK_CHARGE_BEARER lookup.

    Name of an external payee who is responsible for paying regular or express bank charges, such as Payee or Payer.

    PaymentReasonCode

    PaymentReasonName

    String

    Code/Name of the reason for paying an external payee.

    PaymentReasonComments 

    String

    Text field available for entering information about an external payee payment.

    DeliveryMethod

     

     

    String

    Delivery method that is set on the external payee level. If the Override with Payee Delivery Method Preference option on the payment process profile is turned off, the setting is ignored. Values from the IBY_DELIVERY_METHODS lookup include EMAIL, FAX, and PRINTED.

    Email

    String

    Email address at which an external payee receives remittance advice.

    Fax

    String

    Fax number at which an external payee receives remittance advice.

    DefaultPaymentMethodCode

    DefaultPaymentMethodName

    String

    Code/Name of the default payment method for an external payee.

    Step 1: Retrieve PayeeId for supplier, address or site level payment records

    PayeeId: This is a unique identifier for the set of payment attributes. It is auto generated individually when a supplier, address or site record is created. You need to use this value to identify a payment record to be updated. PayeeId can be retrieved using the external payee GET operation as shown below. 

    Note:    First you need to run the supplier GET operation to get SupplierId and SupplierPartyId.

    SupplierId will be used to retrieve supplier site and supplier address PayeeId.

    SupplierPartyId will be used to get PayeeId for Supplier payment record.

                 https://<hostname>:<port>/fscmRestApi/resources/latest/suppliers?q=Supplier LIKE <Supplier Name>

    • GET PayeeId for Supplier:

               Run the external payee GET operation to get the PayeeId for a supplier payment record

               https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees?finder=ExternalPayeeSearch;Intent=Supplier,PayeePartyIdentifier=<SupplierPartyId>

    • GET PayeeId for Supplier Address:

               Run the supplier address GET operation to get SupplierAddressId

               https://<hostname>:<port>/fscmRestApi/resources/latest/suppliers/<SupplierId>/child/addresses

              Run the external payee GET operation to get the PayeeId for a supplier address payment record

              https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees?

              finder=ExternalPayeeSearch;Intent=Supplier,PayeePartyIdentifier=<SupplierPartyId>&q=PayeePartySiteIdentifier=<SupplierAddressId>

    • GET PayeeId for supplier site:

               Run the supplier site GET operation to get SupplierSiteId

               https://<hostname>:<port>/fscmRestApi/resources/latest/suppliers/<SupplierId>/child/sites

               Run the external payee GET operation to get the PayeeId for a supplier site payment record

               https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees?

               finder=ExternalPayeeSearch;Intent=Supplier,PayeePartyIdentifier=<SupplierPartyId>,SupplierSiteIdentifier=<SupplierSiteId>

    Step 2: Update the payment record corresponding to the supplier, address or site using the PATCH operation

    PATCH operation URL: https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees/<PayeeId>

    Sample PATCH Payload

    {
    "PaymentReasonName": "143",
    "PaymentReasonCode": "BE_143",
    "SettlementPriority": "NORMAL",
    "DeliveryChannelCode": "CH_DTACHECK",
    "BankInstructionCodeOne": "NL_N",
    "BankInstructionCodeTwo": "NL_2",
    "ServiceLevelCode": "SDVA",
    "BankChargeBearerCode": "SHA"
    "DeliveryMethod": "EMAIL",
    "Email":"alex@hotmail.com"
    }

    Points to consider: 

    1.    Important to identify the attributes used in these payloads. As already detailed above:

    • PayeePartyIdentifier represents a supplier
    • PayeePartySiteIdentifier represents a supplier address.
    • SupplierSiteIdentifier represents a supplier site.
    • PayeeID represents a record that has payment information for a supplier, a supplier address or a supplier site.

    2.    As detailed above, a payee row is automatically created for suppliers, supplier addresses or supplier sites, whenever they are created. This implies that you can directly use PATCH operation to update payment attributes for suppliers, their addresses or sites.

    3.    If a user’s access to patch supplier site payment attributes is denied, you need to review the procurement BU access and maintain supplier site privilege for that user.

    References:

    Suppliers REST document: Suppliers REST API
    External Payees REST document: External Payees REST API
    External Payee functional and data security document: Doc ID 2540702.1

      

  • Kelly Cooper
    SCM – Supplier Onboarding: Deep Dive and Best Practices, 2...6
    Topic posted November 14, 2019 by Sona SrinivasanSilver Medal: 2,000+ Points, tagged FAQ, How-To, Setup, Supplier Communication, Supplier Creation, Supplier Merge, Supplier Registration, Tip 
    Title:
    SCM – Supplier Onboarding: Deep Dive and Best Practices, 21 November 2019, 9 a.m. PT - Submit Questions
    Content:

    Submit your questions for the SCM – Supplier Onboarding: Deep Dive and Best Practices session to have them answered during the live event. Post your questions by posting a new comment to this topic.

    Please submit your questions by Wednesday, 20 November 2019.

  • Hong Gao
    Tips: Configure Supplier Outbound Synchronization Service75.0
    Topic posted October 31, 2018 by Hong GaoGold Medal: 3,500+ Points, tagged Tip 
    Title:
    Tips: Configure Supplier Outbound Synchronization Service
    Summary:
    Tips for configuring and setting up Supplier Outbound Synchronization Service
    Content:

    Supplier Outbound Synchronization Service feature generates a supplier record snapshot for any external supplier repository to consume. When any update is made to a supplier record the system will generate a snapshot of the supplier record in an XML file and transport the document over HTTPS to a single server destination.  This post provides some tips on configuring and setting up the supplier outbound synchronization service.

    To configure the supplier outbound synchronization service, navigate to Setup and Maintenance work area and use task Configure Supplier Outbound Synchronization Service to define the server location of the service.  On the page, you will need to provide URL for your service and the username and password. 

    1. follow the URL example here: https://www.turnertoolinginc.com/turnerToolingService/SupplierExportOutboundService.  This should be the URL for the service, not a link that points to the WSDL.
    2. provide a URL that starts with "https", as the XML file transferred is only done over HTTPS.
    3. the security policy is read-only and set as: oracle/wss_username_token_over_ssl_client_policy.  Therefore, please ensure that you have a SSL certificate that is issued by a valid Certification Authority.

    When the system generates supplier snapshot as mentioned above, the supplier profile data will be sent as a string (the string will be in xml format). Additionally, when creating and setting up the synchronization service, you can also refer to the sample xsd file in the reference link below.  The whitepaper in the same link also provides examples on setting up service interface java class as well as the WSDL for the service.

    Please note that supplier outbound synchronization service creates a snapshot of a supplier record.  It does not highlight changes. It does not include only the changed part of the profile either.  To track changes, please consider using supplier audit functionality.

    Reference: Supplier Outbound Synchronization Service 11.1.13.0.0 (MOS login is needed to access the link.)

  • Shivani Roy
    Data Access Control on Supplier SitesAnswered95.0
    Topic last edited January 31, 2019 by Shivani RoyBronze Medal: 1,250+ Points, tagged Security, Setup, Tip 
    Title:
    Data Access Control on Supplier Sites
    Summary:
    Understanding the configuration of data access control on supplier sites
    Content:

    There are two levels of security that allows access the supplier site information:

    1. Security privileges:
      • View Supplier Site (POZ_VIEW_SUPPLIER_SITES_PRIV): Allows view access to supplier site information.
      • Maintain Supplier Site (POZ_MAINTAIN_SUPPLIER_SITES_PRIV): Allows edit access to supplier site information.
    2. Manage Procurement Agents setup task: Agents access control is given at the "Manage Suppliers" level on this setup task. This setup provides procurement business unit based edit access to users. Supplier sites being the entity linked to procurement business units the users can only edit those sites of a supplier for whom the agent access has been given at the "Manage Suppliers" level.

    Let’s review these use cases to better understand the data access control on supplier sites:

    • Configuration for senior management users who need view only access to sites:

    To ensure the user has view access to all sites information i.e. sites belonging to all procurement business units, grant the privilege View Supplier Site to the user.

    • Configuration for supplier administrators or managers who need edit access to sites.

               There are two steps involved:

    1. Identify the procurement business units for which the user should be allowed to maintain supplier site   information. For all such procurement business units, make the user a procurement agent allowed to Manage Suppliers in the setup task Manage Procurement Agents.
    2. After making the user procurement agent for all procurement business units that user is allowed to maintain sites from, grant the privilege Maintain Supplier Site.

    Points to Consider:

    • Maintain Supplier Site privilege should only be given to users who are allowed to edit supplier site information. If they are allowed to maintain supplier sites, they MUST be made procurement agents with Manage Suppliers action for the procurement business units.
    • If the user needs to have edit access to all sites, then make the user procurement agent for all the procurement business units along with the Maintain Supplier Site privilege.
    • For view only access to sites, user must only be granted the View Supplier Site privilege.Agent access setup will not be required in this case.
  • John Binder
    RightFax Fax Integration and Oracle Fusion Cloud1
    Topic posted November 8, 2019 by John Binder, tagged How-To, Supplier Communication, Tip 
    Title:
    RightFax Fax Integration and Oracle Fusion Cloud
    Summary:
    Looking to see what other customers are using for Fax Capabilities with Oracle Cloud
    Content:

    Hello Everyone,

    I was doing some research to determine what Oracle supports in terms of Faxing Software.  Our organization is utilizing RightFax and we trying to migrate our Enterprise over to using strictly RightFax.  I noticed that Oracle doesn't support Rightfax and only uses CUPS for Printing and Faxing capabilities.  I wanted to reach out to the community to see if anyone was using software other than CUPS or even RightFax and what the experience has been.  For us our Supply Chain team has a requirement to be able to Fax some suppliers that still require Fax. 

    Thank you,

    John Binder

    Hopefully I chose the right place to put this question. New to the community and still learning.

    Oracle Doc for reference: https://docs.oracle.com/cd/E23943_01/bi.1111/e22255/print_servers.htm#BIPAD510

     

    Version:
    Oracle Cloud 19D
  • Lot
    Broad-Based Black Economic Empowerment (B-BBEE)15.0
    Topic last edited November 8, 2019 by Lot, tagged FAQ, How-To, Supplier Registration, Tip, White Paper 
    Title:
    Broad-Based Black Economic Empowerment (B-BBEE)
    Summary:
    Documentation on how to configure Broad-Based Black Economic Empowerment (B-BBEE)
    Content:

    Hi, 

    Is there a documentation available on how to configure Broad-Based Black Economic Empowerment (B-BBEE)  for South Africa and what Oracle Cloud version is this available?

    Topics Requested:
    -Documentation on how to configure B-BBEE 
    -How to enable  (PPPFA) Scores Report, BBBEE Rating etc)
    -What Oracle CLoud version is this available ?

     

     

    Version:
    Oracle Cloud R13 19C
  • Shivani Roy
    How to configure Supplier Registration Approved Email...25.0
    Topic last edited November 6, 2019 by Shivani RoyBronze Medal: 1,250+ Points, tagged Approvals/Notifications, Business Intelligence, Customization, Supplier Registration, Tip 
    Title:
    How to configure Supplier Registration Approved Email notification using Business Intelligence Publisher template
    Summary:
    Steps to configure Supplier Registration Approved Email notification using Business Intelligence Publisher template.
    Content:

    Summary: Steps to configure Supplier Registration Approved Email notification using Business Intelligence Publisher template.

    Description:

    Buying organizations can include additional information to be sent to the supplier by configuring the email notifications using BIP.

    E.g: In the Supplier Registration Approved Email notification, if you want to add a paragraph detailing the organizations quality policies and also want to display additional information dependent upon a supplier registration attribute, then follow the below steps:

    Note:

    1. In order to configure the BIP template the user should have the role: BI Administrator.
    2. This feature is opt in controlled. You need to enable feature Configure Supplier Registration Approval Decision Notifications with Business Intelligence Publisher.

    Step 1: Create a copy of the template

    Sign in to Oracle Business Intelligence Publisher. In the Suppliers Business Intelligence Catalog, locate the External Supplier Registration Approved FYI Email Report template, and then click Customize. This creates a copy of the template in your Custom folder.

    image2019-10-31_11-45-39.png?version=1&modificationDate=1572502540680&api=v2

     

    Step 2: Download and install BI publisher word add-in

    If BI publisher add-in is not installed for word you can download it from the below link:

    https://www.oracle.com/technetwork/middleware/bi-publisher/downloads/index.html

     

    Step 3: Download sample data

    Sample data will be required in order to add additional supplier registration attributes to the template. Sample data contains a list of supplier registration attributes along with sample values for these attributes. This when loaded to the template gives you a list of the supplier registration attributes which can be added to the template. Furthermore the sample data is also useful when you want to preview a report for the configuration done.

    To download the sample data follow the below steps:

    Edit the External Supplier Registration Approved Email Data Model available under the Data Models folder.

    screenshot1.png?version=1&modificationDate=1572501032000&api=v2

    Click on the properties from the panel on the left hand side. Download and save the sample.xml

    2.png?version=1&modificationDate=1572501071000&api=v2

    Note: If the sample data does not contain the required attributes, you can edit the sample.xml file using notepad and manually add the required tag and value combination under the correct mapping set.

    To fetch the correct Tag Name and mapping set, open the data model, Click on the Data Sets from the panel on the left hand side and go to Structure tab. XML Tag Names and their mapping sets are listed here.

    datamodel.png?version=1&modificationDate=1572501102161&api=v2

     

     

    Step 4:  Customizing the copy of the seeded template.

    1. Go to Custom folder> Procurement> Suppliers > External Supplier Registration Approved FYI Email Report template. Click on Edit and download the ExtSuppRegNotifApprovalFYIReport.rtf.
    2. Go to BI publisher tab and load sample.xml saved in Step 3.
       3.png?version=1&modificationDate=1572501122090&api=v2
    3. Adding text content: Go to the Insert tab, expand ‘Quick Parts’ to see available pre-existing layouts which can be used to configure the template.
      To add text choose BIP Paragraph of Text from the list.
      4.png?version=1&modificationDate=1572501145000&api=v2
      Add text which is to be displayed in the email.
      5.png?version=1&modificationDate=1572501165000&api=v2
    4. Adding an attribute from the data model to conditionally display content on the BIP report:
      We can also add conditions on any of the supplier attribute to conditionally display content. Example given below shows how to use DFF attribute to conditionally display content on the email. DFF attribute ATTRIBUTE20 is used in the supplier registration to capture the supplier response to the question on the buying organization’s quality policies.
    • To add a condition click on Conditional Region under BI publisher tab.
    • Under General: Select the required attribute from the Data field list. Select the corresponding data type.
    • Under Condition1: Manually enter the value expected to satisfy the condition.
    • Add the required content to be displayed inside the conditional tags <C><EC> as shown below.
      12.png?version=1&modificationDate=1572501190212&api=v2

     

    Step 5:   Viewing a sample report for the customization.

    Note: Temporarily delete the portion highlighted in yellow before viewing a sample. Paste it back after viewing the sample report.

    These tags are references to other folders in the BI and hence will throw error when we try to view a sample report locally.

    Under BI publisher tab click on any of the formats to view a sample report.

    15.png?version=1&modificationDate=1572501214000&api=v2

    Sample report in the pdf format.

    14.PNG?version=1&modificationDate=1572501238878&api=v2

     

    Step 6: Save the template and upload it back into the BI publisher.

    Under Custom folder> Procurement> Suppliers > External Supplier Registration Approved FYI Email Report, note down the layout name and delete the existing template. Click on Upload to upload the configured template. Please note to use the existing name for layout name. For External Supplier Registration Approved FYI Email Report template the layout name is ExtSuppRegNotifApprovedFyi.

    image2019-10-31_11-47-30.png?version=1&modificationDate=1572502650267&api=v2

     

    Once the upload is complete click on View a list on the top right corner and verify that the Default Layout checkbox is checked.

    11.png?version=1&modificationDate=1572501609000&api=v2

     

    Other references:

     

  • Piyush Singh
    How to make an attribute as required using page composer?24.0
    Topic last edited April 26, 2018 by Alan NgBronze Trophy: 5,000+ Points, tagged Customization, How-To, Supplier Registration, Tip 
    Title:
    How to make an attribute as required using page composer?
    Summary:
    Customization using page composer in design mode to make an attribute required.
    Content:

    Attached is the step-by-step guide to show how to make an attribute as required using page composer. The document covers steps to customize supplier registration attribute 'Supplier Type' as required using page composer.

    Thanks,

    Piyush

  • Shivani Roy
    Points to consider when importing supplier attachments using...5.0
    Topic last edited October 25, 2019 by Shivani RoyBronze Medal: 1,250+ Points, tagged How-To, Import, Supplier Profile Management, Tip 
    Title:
    Points to consider when importing supplier attachments using Import Supplier Attachments FBDI template.
    Summary:
    Here are some useful tips for importing supplier attachments using the supplier attachments import template:
    Content:

    1. Pick the correct template as per your quarterly update. Refer to this post to access the correct FBDI template for your quarterly update:

    Where can I find FBDI Import templates for my current quarterly update?

    2. In general an import job can complete successfully and still have error status even if one of the records failed to import due to incorrect data provided. Check the report to ensure all attachments are    imported successfully and identify any failed records.

    3. The Supplier Attachment Import template contains three individual worksheets for importing supplier profile, supplier site and business classification attachments.The instructions to run the import are given in the ‘Instructions and CSV Generation’ worksheet of the import template.Do not delete worksheets corresponding to levels of attachments that you do not intend to import. Delete only the sample data from these unused worksheets.

    4. For a file attachment consider the following points:

    • Limit the number of attachments in each .zip file to less than 300.
    • Reduce the number of attachments in the .zip file even further if the .zip file size is more than 1.5GB. Use one or more zip files for each batch and use batch name as part of zip file name for ease of data entry in the spread sheet.
    • Execute import in multiple smaller batches as opposed to a single big batch to expedite the import process.
    • Make sure the zip filename matches the zip file uploaded in the UCM server.
    • Make sure the ‘File/Text/URL*’ column value in the spreadsheet has the full folder hierarchy of the attachment file inside the zip folder including subfolders if any. Take a look at the example below.

                             e.g: we have a zip file named: Policies.zip

                                    Subfolder: SupplierPolicies is a subfolder in the zip file

                                    File Name: Terms.doc is the file inside the subfolder

                                    Input for column ‘File/Text/URL*’: SupplierPolicies/Terms.doc

                                    Input for column ‘File Attachments .ZIP’: Policies.zip

    • Some of the special characters are currently not supported for a filename:

               <  >  *  ?  |  ;  "  :  /  \\  %  $  ( )

     

    Readiness training video is available for further reference: Supplier Attachments Import

    Tips on general supplier import: Supplier Import Tips

  • Aishwarya Pawar
    Enabling Supplier Audit HistoryAnswered75.0
    Topic posted February 22, 2018 by Aishwarya PawarGold Medal: 3,500+ Points, tagged Audit, How-To, Tip 
    Title:
    Enabling Supplier Audit History
    Summary:
    Tips for enabling Supplier Audit History
    Content:

    Supplier Audit History allows tracking and reporting of changes made to supplier profile information to support internal audit controls and governance as well as external regulatory compliance such as SOX.

    Here are some tips that will allow you to set up this feature correctly and leverage everything it has to offer:

    • Ensure attributes that need to be audited have been enabled for audit tracking using the Manage Audit Policies task as shown in the screenshot below. Changes to an attribute will be tracked only if it is enabled for audit. Refer to the steps listed below explaining how attributes can be enabled for audit.
    • Ensure that the business object to be audited is selected in addition to its individual attributes.
    • Payments information i.e. Payment Methods, Bank Accounts and Payment Attributes can be specified for a supplier, its addresses and sites. Corresponding attributes can be enabled for audit using one of the three business objects available: Supplier Payment Methods, Supplier Bank Accounts and Supplier Payment Attributes. Enabling an attribute that belongs to these business objects will track changes made to the attribute at all three levels: supplier, address and site.
    • Changes made to audit setup are prospective and not retrospective. Consequently, for an attribute which has not been previously enabled for audit, any changes made to it prior to enabling it for audit will not be tracked. To optimize performance only enable attributes that need to be tracked.

    image2018-2-20%2016%3A0%3A19.png?version=1&modificationDate=1519171219000&api=v2

    Following steps will guide you to setup audit tracking on the list of supplier profile attributes:

    1. Access the Setup and Maintenance workarea and look for the Manage Audit Policies task.
    2. On the Mange Audit Policies page, set the Audit Level as Auditing and take the Configure Business Object Attributes action.
    3. On the Configure Business Object Attributes page, select Procurement as the product.
    4. Select the appropriate object in the Objects tree table. This corresponds to the object to which the attribute you want audited belongs. For example, if you want to track changes to Alternate Name of a supplier, you should select the Supplier object. Likewise if you want to audit the Address Name, you should select the Supplier Addresses object.
    5. After selecting the object, take the Create action available under the Audited Attributes section on the right. A list of attributes that can be tracked using audit will be made available to you.
    6. Select the attributes that need to be audited. This will allow any changes made to these attributes to be tracked and reported.
    7. Take the Save the Close action.

    Refer to the following for more details on what the Supplier Audit feature offers: