ACCRUAL RECONCILIATION REPORT FOR RECEIPT ACCOUNTING GENERATING NO OUTPUT

he Accrual Reconciliation Report is not fetching the purchase order details which are already received but not invoiced.


Please ask the customer if they have run the following processes before
submitting the Accrual Reconciliation Report:
1.Create Accounting
2.Match Receipt Accruals

Supervisior Hierarchy with No value at the some approval level

We are having customer, need your insight to fulfill his requirement -

Customer using the approved UI when creating approval rules.

He is building a Requisition approval rules based on a Supervisor Hierarchy, and He need to use the "Requester Level 4 Supersior" field in order to match the client's logic.
The issue is that, not all of the future requesters have a Level 4 Supervisor, so the the entire approval structure fails when ever a requester without a level 4 supervisor is trying to submit a requisition, since the system cannot compare "IS IN" or "IS NOT IN" values to NULL.

So the question is: is it possible to use SQL functions (like NVL) within the approval rules in order to prevent an error?
For example: NVL("Requester Level 4 Supersion",1) IS IN ('John', 'Tom', 'Jason').

Could you please help us to capture this requirement.

Answere -
In order to avoid the error, can they add a 'is not blank' condition in the approval rule and re-try the same use case ?

The "is not blank" condition must come before the "equals" condition.

e.g Requisition Amount Equals 80 and Requester Level 4 Supervisor Is not blank and Requester Level 4 Supervisor Equals LastName,FirstName

How to override the charge of account at requisition to enter it manually

Approve is able to change the charge account however it does not get saved even after clicking save or submit button for Requisition Approval.

Customer is using default charge account rule but only natural account segment they have used the mapping set.

Answer - 

Based on your current set-up, the behavior of the system is

1) Derive a complete charge account (either automatically or from what user has entered depending on the configuration of your charge account rule)
2) Override the Natural Segment of the account derived from step 1.

This means - the Natural Account segment of the charge account entered by the Approver will be overwritten. To prevent this, you need to add the following condition to your mapping set rule (i.e. the segment overlay rule) - "Requisition Charge Account"."Natural Account Segment" Is not.

How it works - 
The above condition is saying - only trigger the rule inside the segment overlay rule(i.e. the mapping set) if there is no manually entered value for the Natural Account Segment. This means if user has manually entered a charge account, the rule will not be triggered and user's entry will not be overwritten.

When a user manually enters a charge account, the source for such manual entry is known as 'Requisition Charge Account'

Case 2 
Hi Team,
Currently customer implementing the production environment and there was a requirement from client to edit "requisition charge account" manually.

I found the solution in below note

(Segment Combination Cannot Be Saved On Purchasing Requisition Line Distribution (Doc ID 2077390.1))

Solution
Before you can apply the solution you are referring to, your setup needs to be the same as the setup for that solution. For that solution, the client had a segment overlay rule. When you have a segment overlay rule, then after TAB derives a complete charge account, it will trigger the segment overlay rule which will then replace a specific segment (Natural Account in this specific instance) in the just derived charge account combination. The client did not want this overlay to happen when a user has manually entered a charge account.

Normally, the solution to the problem would be to add a rule (see steps below) with a condition "Requisition Charge Account".<<SEGMENT_NAME>> Is not null as a first rule but due to a bug, the workaround was to use the condition "Requisition Charge Account"."All" Is not null.

Steps to adding a rule
a) Edit your custom charge account rule (Manage Account Rule > Purchasing > [YOUR_CHARGE_ACCOUNT_RULE]
b) The charge account rule consists of multiple rules (you will see these when you open it up for edit). Add a rule (first rule) with Source = Requisition Charge Account and condition = "Requisition Charge Account"."All" Is not null

How to setup TAD when using Fusion Projects

SR 3-11875360031
CENTRAL FLORIDA INVESTMENTS INC

Customer want to setup one accounting rule for both Projects and Non Project related requisitions.

customer has two accounting rules
1. For Purchasing which derives the account based on Item Category
2. For Projects related requisitions

Which works fine for both Independently, but customer is trying to create one Rule which works for both Project and non-project related requisitions

Can you please advise on how to do this setup? Uploading the screen shots showing the current setup they are having on their instance.

Research
======
How can we use Transaction Account Builder(TAB) for project related Requisitions and Purchase Orders? (Doc ID 1955590.1)
PJC: Unable To Access Project Fields On Project-Related Payables Invoice Distribution Line and Can't Setup Transaction Account Builder(TAB) For Projects (Doc ID 1490691.1)
PJC: Create Accounting In Error When Source 'Project Class Code' Value Set In Manage Account Rule (Doc ID 1914752.1)
PJC: How To Navigate Or Find Manage Subledger Applications For Scope Task To Set '‘Project Costing’ Scope (Doc ID 1536294.1)
Transaction Account Builder in Oracle Fusion Procurement (Doc ID 1507175.1)

Answer -
Hi Ramesh,

It looks like you are ONLY overlaying the Account segment for both project and non-project related lines. To combine all the rules, you should do the following

1) Creating a new account rule of type 'Segment'
2) In the Rules section, create the following rules

• Rule 1 for Project related lines and it will have the following condition -* "Destination
  Type Code"(PO) = EXPENSE 'AND'
  "Expenditure Organization ID" Is not null* . The value type for this rule will be Mapping Set and it will point to the Mapping Set you have created for your projects.
• Rule 2 for non-Projected related lines and this will not have any condition. The value type will also be mapping set and this will point to the Mappping Set you have created for item category

3) In your Transaction Account Defintion, specify the rule from step 2 above as your Account Segment overlay rule

The explanation is this -

a) The system will first derive a complete charge account based on the account combination rule in your TAD

b) Then the system will call the overlay segment rule. The system will check Rule 1 in your overlay rule. It says to check if the line is of type expense and also has an Expenditure Org ID (you get this when you specifiy Project Details for the line). If the conditions are true, it will look at the attached mapping set and will not call Rule 2. If the conditions are false, it will move to Rule 2