Purchasing

Get Involved. Join the Conversation.

Topic

    Gopinath Kartheesan
    PO Numbering logic for Shared Services Procurement Model
    Topic posted July 7, 2017 by Gopinath KartheesanBronze Trophy: 5,000+ Points, tagged How-To, Orders, Setup 
    164 Views, 2 Comments
    Title:
    PO Numbering logic for Shared Services Procurement Model
    Summary:
    Ability to generate PO number from the Legal entity associated to Bill to BU on the Purchase order with Shared services procurement model
    Content:

    We have 13 different BUs associated to 13 different Legal entities with in the same ledger.  We are utilizing Centralized Procurement Service model by creating a Central Procurement BU and not associated to any Ledger or Legal entity.  Enabled Procurement Business Functions for the Central Procurement BU.  Enabled Requisitioning and Material Management business function for the other 13 legal entities.
     
    Created a supplier record and a Site for the Central Procurement BU
    On the Site assignments, we have associated 13 different BU as client BU
    While creating the Purchase Order against Procurement Bu = Central Procurement BU, Requisition BU = One of the 13 BU, Sold to Legal Entity = respective LE associated to one of the 13 BU and Bill to BU is a common Payables BU .  But the PO Number is generated from the Sequence defined at the Sold to Legal entity.  If this is the case, then we have to manage 13 different numbering sequence for each of the Legal entity.  Instead, we expect the system to generate PO Number based on the sequence associated to the LE associated to the Bill_to BU so that we can manage with only one numbering sequence.  Please let us know the logic on how the PO Numbering works with Shared services procurement modeul where the Procurement BU is not tied to any Ledger or Legal entity

    Comment

     

    • Ivan Pena

      Hi Gopinath,

      As you mention. PO numbering is maintained by Sold to LE. You could assign the same Sold to LE to all the requisitioning BUs, and use balancing segment values to distinguish the transactions from the different BUs.

      Ivan

    • Gopinath Kartheesan

      Thanks Ivan.  That's exactly what we decided to last week after updating the Default LE for the respective Requisition BU under "Assign Business Unit Business Function" task.  This also required the flag "Multiple Legal entities on an Order" set to "Allow" under Configure Requisition Business Function task so that it defaults the LE from the Business Unit and not from the Default Delivery to Organization.