Unable to Search Customer in Customers HTML Form after creating through Customer Interface

Customer successfully created through Customer Interface
Query the newly created customer in the Customer Masters screen, and system won't show this customer
Same Customer appears in the customer list in the Sales Order form in OM and the Transactions Form in AR
Not able to View/Find/Search the Customer from Customer Forms
There is no problem with Manually created Customers

So need to make sure those data are in staged table.
After importing the customers via customer interface you need to run the 'DQM Staging Program' to make it available in the Customer search .

Solution:

Please run DQM Staging program with STAGE_ALL_DATA parameter.
Once this program finishes successfully, Customer can be searched in Customers form.

Unable to import Payroll journal in GL "This new code combination includes summary segment"

Issue:

This new code combination includes summary segment
EF04    This is an invalid Accounting Flexfield.  Check your cross-validation rules and segment values.

Solution:


To import journals from a subledger into General Ledger:

     1.  Navigate to the import journals form.

     2.  Enter a source and group ID.

     3.  Select run options and import descriptive flexfields option.

     4.  Enter a date range.

     5.  Click on the [Import] button.

This spawns a concurrent request.  In the view my request form the process
completed with a status of "Normal."

Click on [Report] and view the journal import execution report, the following
error is shown:

      EF04:  This is an invalid Accounting Flexfield.
             Check the cross-validation rules and segment values.

The specific error message is:
'Value 000 has been disabled'
for disabled segment values and
'This new code combination includes summary segment'
for parent segment values

This error is specific to journal import and is not caused by consolidation
mappings.  The only reason the error show up when consolidation is run is due
to the run option (journal import) being enabled in the consoldation mapping
form.  If the process is run separately, the error will show up on the journal
import.

Cross-validation rules are set up as follows:

Include: AAA.AAAAAA.AAAAA.AAA.AAA.AAAAA - 999.999999.99999.999.999.99999
Exclude: AAA.131000.AAAAA.AAA.001.AAAAA - 999.131000.99999.999.999.99999
change: NOTE ROLE:  The Navigation Path is:
            Responsibility = General Ledger Super User
       Navigation = Setup>Financials>Flexfields>Key Rules
       Form Name  = FNDFFMCV (Cross-Validation Rules)


            Responsibility = General Ledger Super User
       Navigation: Setup>Financials>Flexfields>Key>Segments
   Form Name  = FNDFFMIS (Key Flexfield Segments)
cause: Cross validation rules and/or segment values exist which do not
allow the journal import process to complete successfully.



fix:

The following options are supported:

I.   Check cross-validation rules defined as follows:
 
     1.  Navigate to cross-validation rules form.

     2.  Cross validation rules evaluate from numeric to alphanumeric.

        a. Include should be:
           000.000000.00000.000.000.00000 - AAA.AAAAAA.AAAAA.AAA.AAA.AAAAA


        b. Exclude should be:

           999.131000.99999.999.999.99999 - AAA.131000.AAAAA.AAA.001.AAAAA


II.  Check segment values as follows:
 
     This error could also mean that posting is being attempted to a parent
     account.  Oracle General Ledger does not allow posting to parent accounts.
     Change the values to non-parent values or create child accounts and
     use those accounts to post to.  Make these changes on the
     Segment Values form.

III. Disable the cross-validation rule that is causing the error and re-run the
     consolidation process with the run option set to run journal import.

IV.  Change the cross-validation rules to not exclude the combination that is
     causing the error.

V.   Fix the combination at the source and re-run process.

APP-SQLAP-10715 This purchase order closed for invoice. You may want to review purchase order before continuing with this match.

Matching an invoice to a PO for the entire quantity closes the PO for invoicing.

When the matched invoice line is discarded (using the Discard button), this reverses the PO match. 

The Match button is again available, so the invoice is matched again to the same PO for a different quantity. 

At that time, the following message occurs: 

APP-SQLAP-10715: This purchase order line is closed for invoicing. You may want to review the purchase order before continuing with this match.

Solution: 

In R12, when we discard the line, the status is updated only at validation time. 

Similarly, we update the quantity billed and amount billed for PO's when we match or reverse, but the status is affected ONLY when we validate the invoice. 

So, after pressing the Discard button, validate the invoice before proceeding with any other actions on the invoice.

How to create supplier as a customer in R12

Customer has to create from supplier..

Step-1

Attach the profile option at site level.

AR: Show parties without Accounts in DQM

Step – 2

Create the supplier..

Step – 3

Note down the register number

Navigate to receivables responsibility and query the customer using registry number…and click GO

Step – 4

This will query the records from HZ_PARTIES tables, since supplier information will not have customer page such as Account number, description, Bill to and ship to sites.

We must create the customer account manually by click “Create Account” and add further information such as bill to and ship to etc…

Now supplier is also been a Customer ..