Payment Term on AR Transactions

This post explains how AutoInvoice populates Payment Term on AR transaction when you are using a Payment Term on Sales Order which is different from the Default Payment Term assigned to Customer. For Example: The Payment Term populated on Sales Order is '30 NET' and  you have changed it to 'CREDIT'.
In this kind of scenario, AutoInvoice program checks following conditions to populate the Payment Term on Transaction as on Sales Order.

1. 'Override Terms' check box should be enabled at Customer account and site levels.

Navigation to check this option at Customer Account Level:
Customers -- Customers -- Search for the customer
Click on Account Details.

'Override Terms' check box should be enabled Under 'Account Profile' Tab.


Navigation to check this option at Customer Address Level:
Customers -- Customers -- Search for the customer
Click on Account Details.
Under Sites Tab, Click on Details for 'Bill To' customer site.

'Override Terms' check box should be enabled Under 'Profile' Tab.By checking the Override Terms check box, you are saying that when a user creates an invoice for this customer, he is allowed to change the Payment Term that defaults in. This feature allows you to create
non-balance forward transactions within a BFB-enabled site.

So, the purpose of Override Terms option is to create non-balance forward transactions for a BFB-enabled site. For BFB enabled customer, override functionality work only with NON-BFB payment Terms .

2. If you have Override Terms check box checked, you still cannot override the payment term if the following conditions are true:

-- The customer you are interfacing data for is a Balance Forward Billing (BFB) enabled customer
-- The payment term you are providing in the interface tables is a BFB term that is different from the default payment term you have set up at the Account or Site profile
That means for a BFB enabled customer, we can not override the Default Payment Term with BFB enabled Payment Term.

If you try to override the default payment term with Non-BFB Payment Term, it will work.

For example:

1.Customer - BFB Enabled
Default Payment Term - 30 NET
Override Payment Term - CREDIT (BFB Enabled)

Payment Term on AR Transaction - 30 NET

2. Customer - BFB Enabled
Default Payment Term - 30 NET
Override Payment Term - IMMEDIATE ( NON-BFB Payment Term)

Payment Term on AR Transaction - IMMEDIATE  Note: Receivables uses the following hierarchy to determine the default payment terms, stopping when one is found:

customer Bill-To site level customer address level
customer level
Transaction Type 

Error while creating a Project - 'This Customer does not exist'

This post explains how to debug the error 'This customer does not exist' while creating a project.

Problem Description:

=================
In the project creation screen, the customer field's list of values shows and allows to select a particular customer. But when we hit FINISH to create the project, it gives the error message "This customer does not exists". 

Responsibility: Project Super User (or) Project Manager

Navigation: Projects : Delivery → Create Project

1. Select Create Project from Template.

2. Enter template name and click on continue.

3. Enter required fields and select the customer.

4. Click on Finish button to create the project.

Error appears as 'This Customer does not exist'.

How to Debug the issue:

===================

Run Customer Data Collection Test to check if the customer has been defined properly.

Responsibility: Application Diagnostics

Navigation: Diagnose

Select the Application Short Name: AR

select Customer data collection test and click on Execute.

Provide the required parameters Responsibility ID and customer account number then submit the request.

View report output for any issues with customer data.

Cause of the problem:

=================

The Party Name in  HZ_PARTIES (Customer Account) has the character '~'. This can be verified in Customer Data collection Diagnostics report.

The reason for the ~ character is stated in the diagnostic -
ATTENTION - The above data contains leading or trailing spaces. Values with spaces are shown between tilde (~). Search for tilde (~) in this report to find the values with spaces.

In order for PA to have a row returned to its select on the customer name, the trailing space will need to be removed.

AR data will need to be cleaned.

Solution:

========

Update the Party Name or the field with tilde (~) in HZ_PARTIES table.