Shyam SanthanamBronze Medal: 1,250+ Points

Oracle Cloud ERP Financials Product Management

Comments

  • Shyam Santhanam

    Hi Ashok

     

    Period end accrual is accruing uninvoiced receipt quantity/amount for a purchase order distribution. So if there are multiple receipts for a PO distribution, then the accrual will sum all the receipt qty and compute the accrual amount. We fundamentally cannot use the receipt date rate. Can you help understand why receipt date rate needs to be used for period end accrual POs? Would recommend considering accrue at receipt with 'receipt match option' to get the receipt date exchange rate. 

     

    Regards

    Shyam

  • Shyam Santhanam

    Hi Arghishti

    You can try to model them as inbound or outbound Accounting overhead rates. You can also decide to expense it out instead of including it in inventory. Also using per transaction cost would let you expense out a fixed transportation cost over all the qty on the transaction,

     

    Regards

    Shyam

  • Shyam Santhanam

    Hi Suresh

     

    If you dont find the source listed here, then AP has to add it into SLA sources via an ER. However I suggest to query all supplier related sources and look for any closest proxy to supplier type or something that can help represent the nature of liability 

     

    Regards

    Shyam

  • Shyam Santhanam

    Hi Ravi

    This source should still work for AP. Transaction legal entity will look at the LE on invoice header. So please try to use without waiting for ER

     

    Regards

    Shyam

  • Shyam Santhanam

    Please check the mapping set used for the account rule tied the receiving inspection account for event type 'Deliver to expense'. In the mapping set, look for the input attribute and make sure there is a mapping row for the value that is passed on the transaction. for example, if input is 'inventory org', then check whether there is a mapping for the inventory org code that is on the transaction

  • Shyam Santhanam

    Hi Kiran

    We have profile options to hold back transfer to fusion GL. If you enable it, AH subledger journals wont be posted to fusion GL. 

    But what is the use case here not to transfer to GL?

     

    Regards

    Shyam

     

  • Shyam Santhanam

    Hi Kiran

    Reference object concept is not supported in AH cloud. You will have to flatten the transaction object to include the reference object attributes. This will have to be done as part of pre-processing (outside AH cloud) the data for generating AH cloud feed.

     

    Regards

    Shyam

     

     

  • Shyam Santhanam

    Hi Kapil

    Taking a step back, moving to R13 FAH cloud is not an 'upgrade'. It will technically be a re-implementation. The architecture for integration is different and I would highly recommend you to review the model and reassess the design implications. My understanding is you would probably just need ledger definitions to tag ledger name along with transactions fed into Accounting Hub Cloud. 

    Feel free to reach out to me at shyamsundar.santhanam@oracle.com for further conversation. Would like to understand your current use case/implementation model to provide a firmer advice

     

    Regards

    Shyam

     

     

  • Shyam Santhanam

    Hi Prithis

    FSM export/import in 18C supports csv file based configuration package. You can download them as a template package and create the rules in that. Only pre-req is you should first create AH subledger using rapid implementation spreadsheet and then download the template. Please try that and let me know.

     

    Regards

    Shyam

  • Shyam Santhanam

    Hi Ravi

    Did you try using this source (please see attached)?

     

    Also just curious, are these PO matched invoices or standalone expense invoices?

     

    Regards

    Shyam

  • Shyam Santhanam

    Hi Rabi

    Spreadsheet upload is not available at this point. One exception is mapping set, where we do support spreadsheet upload of the mappings.  We are working on FBDI web service for Mapping set entries. But dont have a release ETA at the moment. As best practices, we recommend structuring the rules to maximize the use of mapping sets. That will make change management much more easier and controllable. 

     

    Regards

    Shyam

  • Shyam Santhanam

    Hi Yasmin,

    Its really a cross functional flow. Unfortunately we dont have anything out-of-the-box documentation for you. But its a good idea to explore capturing the steps by this way, Will have to take this as a feedback for future action.

    For now, here are some high level guidances

    I assume you already have defined LE and ledgers

    1) Define business units : Create Business units and assign business functions according to option 1

    • One profit center BU per inventory org designate as 'Below LE'. Assign Materials Management business function. Designate the owning LE for this BU. 'Defaul LE' is actually the owning LE.
    • One Service BU per ledger: Assign  procurement, requisitioning, payables and materials management business functions. Designate a 'default' LE from the ledger. This will be the one defaulted on the invoices. You dont have to enable 'Below LE' flag here.

    2) Define inventory organization:

    • For each inventory org, pick the ledger, owning LE, corresponding profit center BU and the common 'management BU'

    This will complete the enterprise structure side setups. Then you can do the rest of the business function configurations in each of these entities.

     

    Hope this helps.

     

    Regards

    Shyam

     

     

  • Shyam Santhanam

    Whenever you say BU, please qualify as BU with 'what business function'? Here I assume it is BU with "Material Management' and/or 'Requsition' function. 

    LEs are not assigned to BU. 

    1) Inventory org is assigned to LE

    2) Inventory org is assigned to 'Management BU'.

    3) Thus 'Management BU' manage multiple inventory organization belonging to different LEs

     

    Hope this clarifies.

     

    For BU with Payables function, 

    1) BU is linked to Ledger and a 'default LE'

    2) BU are not hard linked to a list of LEs. All the LEs assigned to the ledger are available for the BU to process invoices.

     

    regards

    Shyam

  • Shyam Santhanam

     You are probably looking at option1 in my slide deck referred below. Please review if it meets your requirements. 

    -- so no inventory shared services in this case, maybe only purchasing shared services, right?

    Shyam: Yes. Only purchasing and requisitioning is centralized. 

     

    Find attached my take on the requirements. Please note i am not expert in all these areas. So have not filled in for some questions. These are my guidances only for enterprise structure modeling that will enable you to achieve these requirements. Please thoroughly validate before making final recommendations.

  • Shyam Santhanam

    Did a quick read of the requirements. couple of comments

    1) Warehouse is a real world term. In Cloud Inventory, it could be one or more inventory orgs. As long as they tie to same 'management BU', they still fall under one broad real world warehouse.

    2) Requirement #3, is it an internal transfer within the warehouse or from one warehouse to another? What attributes will tell it belongs to LE1 or LE2 in their business world? 

    3) Your scenario 4 comes closest to requirements. But let me qualify that. The BU you have is the 'Management BU' with requisition and materials management business functions. You still need another BU representing profit center BU per inventory org. 

    4) You are probably looking at option1 in my slide deck referred below. Please review if it meets your requirements.