Purchasing

Get Involved. Join the Conversation.

Posts

  • Boyuan Zhu
    How to Import Orders and Agreements Using the ERP...45.0
    Topic posted November 1, 2018 by Boyuan ZhuGold Medal: 3,500+ Points, tagged Agreements, How-To, Orders, Web Services 
    Title:
    How to Import Orders and Agreements Using the ERP Integration Service
    Content:

    You can use the ERP Integration Service to automate file based data import (FBDI) between your system and Oracle Procurement Cloud. For example, you can create a program to convert import data from your system into the FBDI CSV format, encode the resulting ZIP file into the SOAP payload, and invoke the integration web service with the payload. The following section contains example payloads for importing purchase orders, blanket purchase agreements and contract purchase agreements. 

    Each payload includes a ParameterList of parameters for the import job. The examples below explain, in order, what each parameter is and what values are valid. Note that the parameters and the order of the parameters differ for each job. To figure out the value for id based parameters, you can look at the values for previous jobs on the Scheduled Processes Page, as seen in the screenshot below.

    Import SPO 

    Payload:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
     <soapenv:Header/>
     <soapenv:Body>
     <typ:importBulkData>
     <typ:document>
     <erp:Content>INSERT YOUR ZIP FILE IN BASE64 ENCODING HERE</erp:Content>
     <erp:FileName>PoImportOrders.zip</erp:FileName>
     </typ:document>
     <typ:jobDetails>
     <erp:JobName>/oracle/apps/ess/prc/po/pdoi,ImportSPOJob</erp:JobName>
     <erp:ParameterList>204,100010026863783,NONE,204,2021,N,#NULL,N</erp:ParameterList>
     </typ:jobDetails>
     </typ:importBulkData>
     </soapenv:Body>
    </soapenv:Envelope>
    

    Parameters: 

    Procurement BU: Specify the id of the Procurement business unit that these documents should be imported into.

    Buyer: Specify the id of the buyer to be used when one is not included in the import data.

    Approval Action: NONE - Imports the document in Incomplete status requiring manual interaction. SUBMIT - Imports the document and submits it to the approval process after the document is imported. BYPASS - Imports the document in Open (approved) status without going through the approval process.

    Default Requisitioning BU: Specify the id of the Requisitioning business unit to be used when one is not included in the import data.

    Batch ID: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Batch ID = 123. Use it in conjunction with Import Source to identify the documents to be loaded to the application tables.

    Create or Update Item: Y to create an item that does not exist or update an existing item. N to not create or update any items. 

    Import Source: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Import Source = External Contracts. Use it in conjunction with Batch ID to identify the documents to be loaded to the application tables.

    Communicate Document: Y to have imported purchasing documents communicated to the supplier. N to not have imported purchasing documents communicated to the supplier.

     

    Import BPA 

    Payload:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
     <soapenv:Header/>
     <soapenv:Body>
     <typ:importBulkData>
     <typ:document>
     <erp:Content>INSERT YOUR ZIP FILE IN BASE64 ENCODING HERE</erp:Content>
     <erp:FileName>PoImportBlanketAgreements.zip</erp:FileName>
     </typ:document>
     <typ:jobDetails>
     <erp:JobName>/oracle/apps/ess/prc/po/pdoi,ImportBPAJob</erp:JobName>
     <erp:ParameterList>204,100010026863783,N,NONE,2021,#NULL,N</erp:ParameterList>
     </typ:jobDetails>
     </typ:importBulkData>
     </soapenv:Body>
    </soapenv:Envelope>
    

    Parameters: 

    Procurement BU: Specify the id of the Procurement business unit that these documents should be imported into.

    Buyer: Specify the id of the buyer to be used when one is not included in the import data.

    Create or Update Item: Y to create an item that does not exist or update an existing item. N to not create or update any items. 

    Approval Action: NONE - Imports the document in Incomplete status requiring manual interaction. SUBMIT - Imports the document and submits it to the approval process after the document is imported. BYPASS - Imports the document in Open (approved) status without going through the approval process.

    Batch ID: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Batch ID = 123. Use it in conjunction with Import Source to identify the documents to be loaded to the application tables.

    Import Source: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Import Source = External Contracts. Use it in conjunction with Batch ID to identify the documents to be loaded to the application tables.

    Communicate Document: Y to have imported purchasing documents communicated to the supplier. N to not have imported purchasing documents communicated to the supplier.

     

    Import CPA

    Payload:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
     <soapenv:Header/>
     <soapenv:Body>
     <typ:importBulkData>
     <typ:document>
     <erp:Content>INSERT YOUR ZIP FILE IN BASE64 ENCODING HERE</erp:Content>
     <erp:FileName>PoImportContractAgreements.zip</erp:FileName>
     </typ:document>
     <typ:jobDetails>
     <erp:JobName>/oracle/apps/ess/prc/po/pdoi,ImportCPAJob</erp:JobName>
     <erp:ParameterList>204,100010026863783,NONE,2021,#NULL,N</erp:ParameterList>
     </typ:jobDetails>
     </typ:importBulkData>
     </soapenv:Body>
    </soapenv:Envelope>
    

    Parameters: 

    Procurement BU: Specify the id of the Procurement business unit that these documents should be imported into.

    Buyer: Specify the id of the buyer to be used when one is not included in the import data.

    Approval Action: NONE - Imports the document in Incomplete status requiring manual interaction. SUBMIT - Imports the document and submits it to the approval process after the document is imported. BYPASS - Imports the document in Open (approved) status without going through the approval process.

    Batch ID: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Batch ID = 123. Use it in conjunction with Import Source to identify the documents to be loaded to the application tables.

    Import Source: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Import Source = External Contracts. Use it in conjunction with Batch ID to identify the documents to be loaded to the application tables.

    Communicate Document: Y to have imported purchasing documents communicated to the supplier. N to not have imported purchasing documents communicated to the supplier.

    Document:
  • Boyuan Zhu
    Control Visibility of the Flexfields for Purchasing...55.0
    Topic posted June 29, 2018 by Boyuan ZhuGold Medal: 3,500+ Points, tagged Agreements, How-To, Orders 
    Title:
    Control Visibility of the Flexfields for Purchasing Documents
    Content:

    You can use Page Composer to control the visibility of the flexfield region and flexfield segments for purchasing documents. By adding your own logic to the existing EL expression, you can show or hide flexfields for your business use case.

    Control Visibility for the Entire Flexfield Region

    In the example below, the entire PO header flexfield region is hidden when the PO's Sold-to LE is "Vision Operations."

    1. Enter a sandbox and navigate to the order page. 
    2. Take the Customize Pages action and select Source from the View dropdown.
    3. Find the showDetailHeader: Additional Information component. This contains the entire flexfield region. 
    4. The existing EL expression for Visible is #{!(bindings._FLEX_NumOfVisibleSegments.inputValue ==0)}. You can add your logic to it: #{!(bindings._FLEX_NumOfVisibleSegments.inputValue ==0) and bindings.SoldToLegalEntityName.inputValue != 'Vision Operations'

    Control Visibility for a Flexfield Segment

    In the example below, a flexfield segment is hidden when the PO's Sold-to LE is "Vision Operations."

    1. Enter a sandbox and navigate to the order page. 
    2. Take the Customize Pages action and select Source from the View dropdown.
    3. Find the showDetailHeader: Additional Information component.
    4. Drill down to find the descriptiveFlexfield component. 
    5. Open the component and switch to the segment tab. 
    6. Find the segment that you want to change the visibility of. 
    7. The existing EL expression for Rendered is true. You can add your logic to it: #{bindings.SoldToLegalEntityName.inputValue != 'Vision Operations'
  • Rain Tsui
    How to enable requested delivery date validation against...45.0
    Topic posted March 28, 2019 by Rain TsuiGreen Ribbon: 100+ Points, tagged Agreements, Approvals, How-To, Orders 
    Title:
    How to enable requested delivery date validation against agreement's effective dates
    Content:

    Business Case

    You want to enforce the agreement's start/end dates for any purchases made against those agreements.

    Solution

    You can use the profile option "PO_REQUESTED_DELIVERY_DATE_VALIDATION" to validate that the requested delivery date is within the source agreement's effective dates. This applies to both contract purchase agreements (CPA) and blanket purchase agreements (BPA).

    With this option enabled, you can prevent submission of POs whose requested delivery date falls outside the agreement's start and end date. 

    Example

    You have created the  following agreements for the same supplier, item, and UOM:

    Agreement Number
    Start Date
    End Date
    123 01-JAN-2019 30-JUN-2019
    456 01-JUL-2019 31-DEC-2019

    A PO with requested delivery date of 01-AUG-2019 will fail submission validation if agreement 123 is referenced, regardless of the profile option setting.

    A PO with requested delivery date of 01-MAY-2019 will fail submission validation if agreement  456 is referenced and the profile option is enabled, but will pass submission validation if the option is disabled. 

    How to set up

    You can go to Manage Purchasing Profile Options and search by PO_REQUESTED_DELIVERY_DATE_VALIDATION.

    Screen%20Shot%202019-03-18%20at%202.32.51%20PM.png?version=1&modificationDate=1552944882000&api=v2

     
  • Nishanth B Jain
    Order Creation Options in Blanket Purchase AgreementAnswered105.0
    Topic posted August 9, 2018 by Nishanth B JainBronze Crown: 15,000+ Points, tagged Agreements, Fusion, Orders 
    Title:
    Order Creation Options in Blanket Purchase Agreement
    Summary:
    Automatically generate orders should be uncheked by default
    Content:

    Hi,

    We are trying to uncheck the Automatically generate orders option by default in BPA.

    Currently its checked for all BPA's as shown in attached screen. We want it to be unchecked by default.

    Any suggestions on this?

    Thanks,

    Nishanth

    Image:
  • Ivan Pena
    Desupport Notice for Oracle B2B Gateway in Procure-to-Pay...25.0
    Topic posted August 9, 2019 by Ivan PenaBronze Crown: 15,000+ Points, tagged Agreements, Orders, Payables, Supplier Communication 
    Title:
    Desupport Notice for Oracle B2B Gateway in Procure-to-Pay B2B Communications in Update 20A
    Summary:
    B2B Gateway desupported as communication method for Procure to Pay Flow in Update 20A
    Content:

    Present Behavior:

    When setting up a supplier site in Oracle Procurement Cloud, you have three options for the B2B communication method you want to use to exchange B2B messages with the supplier:

    • None
    • Oracle B2B Gateway - Deprecated
    • Collaboration Messaging Framework

    The Oracle B2B Gateway - Deprecated and Collaboration Messaging Framework achieve the same end result, but have different setup and management capabilities. Oracle Collaboration Messaging Framework Cloud provides better capabilities to set up and manage B2B messaging with trading partners, including features such as message configuration and the ability to reprocess messages.

    Future Behavior:

    Starting in Update 20A, the Oracle B2B Gateway – Deprecated option will be desupported, and it will be removed as an option in a later release. 

    Effect on Customers:

    New Oracle Procurement Cloud implementations must not use the Oracle B2B Gateway - Deprecated option. If you are an existing customers using this B2B communication method, you must migrate your setup to use Collaboration Messaging Framework for all supplier sites enabled for B2B messaging. Refer to the Oracle Supply Chain Collaboration and Visibility Cloud What’s New for Release 19B and the Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework white paper (Doc ID 2564389.1) for details about the migration process.

  • Dev Thota
    How to write approval rules for “Outside Processing P...25.0
    Topic posted July 30, 2019 by Dev ThotaGold Trophy: 10,000+ Points, tagged Agreements, Approvals, Approvals/Notification, Approved Supplier List, BI Publisher Reports, Business Intelligence, Create Requisition, FAQ, Financials, Fusion, General Ledger, How-To, Manage Procurement Catalog, Notifications, Orders, OTBI, Payables, Public Sector, Requisition Processing, Security, Setup, Supplier Communication, Supply & Distribution Planning Cloud, Web Services, White Paper 
    Title:
    How to write approval rules for “Outside Processing Purchase Order” through BPM?
    Summary:
    How to write approval rules for “Outside Processing Purchase Order” through BPM?
    Content:

    Hi all,

    When we are releasing the work order our requisitions are auto approving and POs are getting created automatically. As per the Oracle, we can't control the approvals of PR so we want to enable the approval flow for the purchase orders(OSP orders). If anyone has any idea on how to create a BPM rule for these kinds of POs please let me know.

    Version:
    19B
  • Boyuan Zhu
    How to Make BPA Lines Read-Only5.0
    Topic posted August 17, 2018 by Boyuan ZhuGold Medal: 3,500+ Points, tagged Agreements, How-To 
    Title:
    How to Make BPA Lines Read-Only
    Content:

    If you have an administrator that uploads agreements through FBDI, you may not want users to make changes to agreement lines in the application. To restrict users from editing existing BPA lines, you can disable the create, edit, and delete functionality in the lines table. 

    1. Use Page Composer on the Edit Agreement page and hit the edit button for the Lines applicationsTable.
    2. Set the Enabled value for Create, Edit, and Delete to false and the Disabled value to true. If you want to retain these functions for application administrators, you can use the expression #{securityContext.userInRole['ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB']}. 
    3. Drill down into the table component and set it to readOnly.
    4. Lastly, set the Edit button inside the table to disabled as well. 
    Document:
    Document:
    Document:
    Document:
  • Boyuan Zhu
    Change Default Attachment Category25.0
    Topic posted May 8, 2018 by Boyuan ZhuGold Medal: 3,500+ Points, tagged Agreements, How-To, Orders, Tip 
    Title:
    Change Default Attachment Category
    Content:

    The default attachment category when uploading attachments is "From Supplier". Buyers that regularly upload attachments of a different category can change the category name so that the desired category shows as the first and default entry in the LOV.

    1. In Setup and Maintenance, navigate to the task Manage Attachment Categories.

    2. Search for the module Common Purchasing Entities. The results are the avaialable attachment categories.

    3. Rename the user name for the attachment category you want to have as the default. For example, change "To Approver" to "1 - To Approver", and it will default as the first entry in the LOV.

  • Manjula Evans
    Sender E-mail Address for Purchasing Document Communication4.7
    Topic posted September 17, 2016 by Manjula EvansBlue Ribbon: 750+ Points, tagged Agreements, Orders, Setup, Supplier Communication 
    Title:
    Sender E-mail Address for Purchasing Document Communication
    Summary:
    Flexibility to define the e-mail sender for purchasing document e-mails sent to suppliers
    Content:

    You can use the new profile option " Purchase Order E-mail Sender " to select between the Buyer's e-mail address or an automatically generated e-mail address as the sender address for purchasing document communication e-mails.

    Using the buyer's e-mail address allows suppliers to reply and communicate directly with the buyer. 

    Using the automatically generated e-mail address helps in cases where the supplier's e-mail system filters out buyers' e-mails as spam, or if the buyer's role is not clearly defined in your organization.

  • Siva Kumar
    Auto Approval not happening for purchase order sourced from...34.3
    Topic posted January 23, 2019 by Siva KumarGold Trophy: 10,000+ Points, tagged Agreements, Approvals, Approvals/Notification 
    Title:
    Auto Approval not happening for purchase order sourced from BPA
    Summary:
    Auto Approval not happening for purchase order sourced from BPA
    Content:

    Hello,

    We created a purchase order from a blanket and submitted it. The status is Pending Approval instead of Open . PO should have been  Auto Approved as all lines are negotiated. 

    Earlier the functionality was working fine.  Please help to resolve this issue.

    Thanks

    Siva.

    Version:
    18 C