Create Accounting

1. What are the Subledger Accounting Setup and Usage FAQ’s?

This Document includes FAQs Customers found when setting up SLA, and issues found when transferring to General Ledger due to product usage:
– How to Transfer Accounting to General Ledger in Release 12
– How to Import and Create accounting definitions
– How to Transfer Invoices with Rules to General Ledger
See Note 559064.1 for more information.

2. What are the FAQ’s for the R12 SLA Pre-Upgrade Process?

1. What is the function of the R12 SLA (Subledger Accounting) Pre-Upgrade program?
2. When and how do I run the R12 SLA Pre-Upgrade program?
3. What table is updated by the R12 Pre-Upgrade program?
4. What are the different status codes in the GL_PERIOD STATUSES table?
5. What criterion does the R12 Pre-Upgrade Program follow?
6. Where can I find the documentation for the R12 Pre-Upgrade Program?
7. What are the Application IDs that are considered by the R12 Pre-Upgrade program?
8. Once I have run the Pre-Upgrade program, can I re-run it with a different set of dates?
9. Where can I find information on the GL_PERIOD_STATUSES table?
10. How do I upgrade the accounting transactions after I have completed the R12 Upgrade?
For answers to these questions and more information, see Note 604893.1.

3. How do you Run the Transaction Objects Diagnostics Program?

The Transaction Objects Diagnostics program basically depends on the Accounting Program for parameter values. Below are the steps to be followed to submit this program:
a. (N) System Administrator Responsibility>Profile>System
Set the Profile, SLA: Enable Diagnostics to Yes at user level.
b. (N) Payables Responsibility>Other>Requests>Run
Submit the Create Accounting program so as to pick some transactions or the problem transactions for accounting.
c. After the Create Accounting program completes, you can run the Transaction Objects Diagnostics program for the Invoice/Payment. Alternatively, you can run this program for the Accounting Program Request ID.
See Note 558196.1 for more information.

4. What are the differences from the Subledger Accounting Methods, Standard Accrual Method and China Standard Accrual?

1. The China Standard Accrual SLAM (JA_CN_STANDARD_ACCRUAL) only has Application Accounting definitions defined for the Payables and Loans applications.
2. The China Standard Accrual SLAM (JA_CN_STANDARD_ACCRUAL) supports Project Number supporting reference on journal lines/headers to meet China localization requirement.
See Note 602109.1 for more information.

5. How to Create A Manual Subledger Journal Entry

Manual entries are adjustments. If the adjustments are due to specific subledger activity such as Payables, then you may want to enter an SLA manual entry instead of a GL entry.
Entries recorded in SLA are tied to the subledger source and therefore provided more accurate subledger accounting reporting.
Enter account, debit, and credit amounts, and accounting class.
Optionally enter third party information, description, and currency details for each line of the subledger journal entry.
View the total accounted amounts of all subledger journal entry lines in the ledger currency.
Navigation: Accounting > Subledger Accounting > Journal Entries
There you can see Create Journal Entry button at the left side after the Advanced Search block.
See Note 452748.1 for more information.

6. How to Correct Invalid Accounts Reported by the Create Accounting Process in R12 Payables

The Update Accounting Entries form was available in earlier releases of R11i to allow update/correction of invalid accounts created by the Payables accounting process. The R11i Update Accounting Entries form is phased out in 11.5.10 and is not available in R12. In R11i version 11.5.10, accounting is not created with invalid accounts; instead the accounting is reported in error and rolled back. The users are required to fix the invalid account referenced in the transaction data at the transaction level. R12 has similar functionality, if an account is invalid, the accounting is created with a status = Invalid. When accounting is created with a status = Invalid due to invalid accounts, the user should correct the transaction data or rule referencing the invalid account and then run the Create Accounting process again. Accounting with status = Invalid and Draft can be recreated each time the Create Accounting process is run. You can modify transaction data and rules to correct and change the accounting until you see accounting status = Final.
See Note 459274.1 for more information.

7. How to Make the ‘About This Page Link’ or ‘Errors Details Link’ Available on R12 OAF Pages

To help diagnose errors in detail or see the About this Page information on an R12 OAF page, set the FND: Diagnostics profile to ‘Yes’ at the site level. The profile controls the display of the ‘About this page’ link. Setting the profile to ‘Yes’ also ensures that a detailed error stack can be viewed to help diagnose unhandled exceptions. When this is set to ‘No’, a simple error message asking the user to contact the System Administrator is shown; the detailed error stack is not accessible.
1. Navigate: System Administrator > Profiles > System
2. Query Profile Name = FND: Diagnostics and set it to ‘Yes’ at the site level.
3. Log out of the application and log back in.
4. Verify the ‘About this Page’ link is now available on R12 OAF pages.
5. Verify the ‘errors detail’ link is now available on R12 OAF page exception messages.
See Note 454759.1 for more information.

GL Transfer

1. SLA: How to Troubleshoot AP TO GL Reconciliation

The purpose of this AP-GL Reconciliation Troubleshooting Guide is to assist the reader with reconciliation issues. In the simplest terms, AP-GL reconciliation means tallying the amounts in Accounts Payable (i.e., AP) for a CCID/Supplier and reconciling it to the figures in the General Ledger (GL).
See Note 605707.1 for more information.

2. How to Setup Transfer to GL in Detail or Summary

Payables Manager responsibility has setup access to subledger options:
Setup #1
1) On the Navigator page, hit CTRL L to get list of forms
2) Select > Accounting Setup Manager Main Page
3) Find the ledger and click Go
4) Click Update Accounting Options
5) Scroll a little down to Primary Ledger heading section
6) Subledger Accounting Options click UPDATE
7) Click Next to find Payables
8) Click Update Accounting Options
9) General Ledger Journal Entry Summarization setup No Summarization
10) Click Apply when done
Setup #2
11) On the Navigator page, Setup > Accounting Setups > Accounting Methods Builder > Journal Entry Setups > Journal Line Type
12) Define how each line type will be transferred to the GL
13) Log out and back into applications
14) Test the Transfer to GL
See Note 564706.1 for more information.

Period Close

1. How to Run the Unaccounted Transactions Sweep Program

See Note 560378.1 for instructions on how to run the Unaccounted Transactions Sweep Program. The information presented is complementary to the Oracle Payables User’s Guide Release 12, Part No. B25454-04.

2. How to Troubleshoot Closing Periods in Payables

A period cannot be closed unless the following criteria is met for ALL operating units assigned to a ledger:
•All payment batches must be confirmed
•All transactions must be accounted
•All accounting entries must be transferred to general ledger
•All future dated payments which have reached maturity in the accounting period must have their status updated to negotiable and be accounted
See Note 437422.1 for steps.

Trial Balance Report

1. How to Run the Accounts Payable Trial Balance Report in R12

Report Definition is required to run the Accounts Payable Trial Balance in R12.
If upgraded from R11i, Report Definitions should have been defined during the upgrade with the following name scheme: Liabilities Payables, i.e. Liabilities Payables, Vision Operations (USA)
If new install of R12, Navigate to: Payables Responsibility > Setup > Accounting Setups> Open Account Balances Listing Definitions
Review the Oracle Subledger Accounting Implementation Guide section on “Creating Open Account Balances Listing Definitions” for instructions on how to setup a new report definition.
See Note 554785.1 for more information.

2. How to Make the R12 Accounts Payable Trial Balance Report Show Detail or Summary Output

The R12 Accounts Payable Trial Balance has 4 templates available that control the output that is
displayed. The four templates available are:
Accounts Payable Trial Balance – Group by Account, Summary
Accounts Payable Trial Balance – Group by Account, Detail
Accounts Payable Trial Balance – Group by Third Party, Summary
Accounts Payable Trial Balance – Group by Third Party, Detail
Do the following to change the template that is used when the report is submitted:
1. Navigate: Payables Responsibility>Other>Request>Run
2. Select the Accounts Payable Trial Balance
3. Enter all of the parameters for the report. DO NOT SUBMIT THE REPORT.
4. Click on the Options button in the Upon Completion section of the Submit Request screen.
5. Select the desired template name.
6. Submit the Trial balance.
Do the following to change the default template used when the report is submitted:
1. Navigate: System Administration Responsibility>Concurrent>Programs
2. Search for:
Application = Payables
Program = Accounts Payable Trial Balance
Click on Go
3. Click on Update for the Accounts Payable Trial Balance program
4. Select the Onsite Setting tab
5. Select the default template from the Template dropdown in the General section.
6. Click on Apply to save the changes.
See Note 444044.1 for more information.

3. How to Have a Text Output for the Accounts Payable Trial Balance

In the Concurrent programs form for APTBRPT program check that ‘Output Format’ is XML.
In submit request form, select Output button in upon completion region, under layout region, choose a format like PDF or RTF.
For more information, see Note 554060.1.

4. How to Create R12 XML Report Output Formatted in Excel Instead of PDF

Do the following to change the Output Format that is created when the report is submitted:
1. Navigate: Payables Responsibility > Other > Request > Run
2. Select the report with XML output i.e. Payables Posted Invoice Register, Create Accounting Process, Accounts Payable Trial Balance, etc…
3. Enter all of the parameters for the report. DO NOT SUBMIT THE REPORT.
4. Click on the Options button in the Upon Completion section of the Submit Request screen.
5. Change the Format from PDF to Excel
6. Submit the report.
Note: XML reports should still be set to create XML output in the Concurrent Program Define form i.e. System Administrator > Concurrent > Program > Define > Set Output set to XML. And review Note 178133.1 “Setting up Word or Excel as a Viewer Option:” to make sure the Viewer Options and System Profile Options are set correctly to view Excel output.
See Note 568031.1 for more information.

5. How to Have a Text Output for the Accounts Payable Trial Balance

In the Concurrent programs form for APTBRPT program, ensure the ‘Output Format’ is XML.
In the submit request form, select the Output button in completion region, under layout region, choose a format like PDF or RTF.
See Note 554060.1 for more information.

6. How to Apply Journal Line Definitions Rules to the Manual Journal Entries

Is it possible to add the seeded Oracle Manual event class to an Application Accounting Definition? This would allow the users to define rules to be applied to manual journal entries in the subledger.
The answer is no. Manual SLA journal does not use rules. In R12, rules do not apply to manual journal entries in the subledger.
Whatever line type/account you enter, the system will take it and create an entry. The System will not consider rules for Manual Journal Entries.
See Note 452739.1 for more information.

ATTENTION: Oracle Payables Community Join our growing Payables Community and learn from your peers and Oracle on how to address your unique issues in AP.

IMPORTANT If you did not find the information you were searching for, please review the following Payables documents:
Note 578232.1 R12 Proactive Intelligence Center: Oracle Payables
Note 396084.1 Oracle Payables Documentation Resources, R12
Note 562887.1 R12 Helpful Tips for a Successful R12 Oracle Payables Implementation
Note 557869.1 EBS R12 Oracle Financials Critical Patches
Note 405627.1 Oracle Payables Release 12 Known Issues
Additional R12 documents:
Note 580299.1 R12 Best Practices for Adopting Oracle E-Business Suite
Note 461705.1 EBusiness R12 Upgrade Guide
Note 602615.1 How to Locate the Latest R12 Product-Specific Information using New MetaLink Features

References

NOTE:437422.1– R12 Troubleshooting Period Close in Payables
NOTE:444044.1– How do you make the R12 Accounts Payable Trial Balance Report show Detail or Summary output?
NOTE:452739.1– R12: How to Apply Journal Line Definitions Rules to the Manual Journal Entries
NOTE:454759.1– How to make the About this Page Link or Errors Details link available on R12 OAF pages
NOTE:458371.1– R12: How to Get the R12 Trace and FND Debug File / FND Log for Payables Processes
NOTE:459274.1– How do you correct invalid accounts reported by the Create Accounting process in R12 Payables?
NOTE:554060.1– R12: How to Have a Text Output for the Accounts Payable Trial Balance
NOTE:554785.1– How do you run the Accounts Payable Trial Balance report in R12?
NOTE:560378.1– Unaccounted Transactions Sweep Program
NOTE:564706.1– R12: How to Setup Transfer to GL in Detail or Summary
NOTE:568031.1– How to Create R12 XML Report Output Formatted in Excel Instead of PDF
NOTE:605707.1– SLA: A TECHNICAL PERSPECTIVE OF THE AP TO GL RECONCILIATION 
select prh.segment1 “PO Requisition Number”,
       pha.segment1 “PO Number”,
       aps.SEGMENT1 “Supplier Number”,
       aps.vendor_name,
       apss.vendor_site_code,
       apsc.first_name,
       apsc.last_name,
       pla.item_id,
       plla.ship_to_organization_id,
       plla.ship_to_location_id,
       rt.transaction_type,
       rt.destination_type_code,
       rsh.receipt_num “PO Receipt Number”,
       aia.invoice_num,
       aida.dist_code_combination_id,
       aca.check_number,gjh.ledger_id,
       gjh.name
  from po_requisition_headers_all prh,
       po_requisition_lines_all prl,
       po_req_distributions_all prd,
       po_headers_all pha,
       po_lines_all pla,
       po_distributions_all pda,
       po_line_locations_all plla,
       ap_suppliers aps,
       ap_supplier_sites_all apss,
       ap_supplier_contacts apsc,
       rcv_transactions rt,
       rcv_shipment_headers rsh,
       rcv_shipment_lines rsl,
       ap_invoices_all aia,
       ap_invoice_lines_all aila,
       ap_invoice_distributions_all aida,
       ap_invoice_payments_all aipa,
       ap_checks_all aca,
       xla.xla_transaction_entities xte,
       xla_events xe,
       xla_ae_headers xah,
       xla_ae_lines xal,
       xla_distribution_links xdl,
       gl_import_references gir,
       gl_je_batches gjb,
       gl_je_headers gjh,
       gl_je_lines gjl
 where prh.segment1 = :RequitionNumber –Right click :RequitionNumber from Toad Enable Prompt For Substitution Variables
   and aps.vendor_id = pha.vendor_id
   and apss.vendor_id = aps.vendor_id
   and apss.vendor_site_id (+) = pha.vendor_site_id
   and apss.vendor_site_id  = aca.vendor_site_id
   and apsc.vendor_site_id = apss.vendor_site_id
   and apsc.vendor_contact_id = pha.vendor_contact_id
   and prl.requisition_header_id = prh.requisition_header_id
   and prd.requisition_line_id = prl.requisition_line_id
   and pda.req_distribution_id = prd.distribution_id
   and pla.po_header_id = pda.po_header_id
   and pla.po_line_id = pda.po_line_id
   and pha.po_header_id = pla.po_header_id
   and pha.org_id = 204
   and plla.po_header_id = pla.po_header_id
   and plla.po_line_id = pla.po_line_id
   and rt.transaction_type = ‘DELIVER’
   and rt.po_header_id = pha.po_header_id
   and rt.po_line_id = pla.po_line_id
   and rsh.shipment_header_id = rt.shipment_header_id  
   and rsl.shipment_header_id = rsh.shipment_header_id
   and rsl.shipment_line_id = rt.shipment_line_id
   and aila.po_header_id = pha.po_header_id
   and aila.po_line_id = pla.po_line_id
   and aia.invoice_id = aila.invoice_id
   and aida.invoice_id = aila.invoice_id
   and aida.invoice_line_number = aila.line_number
   and aipa.invoice_id = aia.invoice_id
   and aca.check_id = aipa.check_id
   and xte.entity_code = ‘AP_PAYMENTS’
   and xte.transaction_number = aca.check_number
   and xte.source_id_int_1 = aipa.check_id
   and xte.security_id_int_1 = aia.org_id
   and xe.entity_id = xte.entity_id
   and xah.event_id = xe.event_id
   and xal.ae_header_id = xah.ae_header_id
   and xal.ae_line_num = aida.invoice_line_number
   and xdl.ae_header_id = xah.ae_header_id
   and xdl.ae_line_num = xal.ae_line_num
   and xdl.applied_to_dist_id_num_1 = aida.invoice_distribution_id
   and gir.reference_5 = xte.entity_id  — Entity Id
   and gir.reference_6 = to_char(xe.event_id) –Event Id
   and gir.reference_7 = to_char (xah.ae_header_id) — AE Header Id
   and gir.gl_sl_link_id = xal.gl_sl_link_id
   –and gir.created_by = 1318
   and gjb.je_batch_id = gir.je_batch_id
   and gjh.je_batch_id=gjb.je_batch_id
   and gjh.je_header_id = gir.je_header_id
   and gjl.je_header_id=gjh.je_header_id
   and gjl.je_line_num= gir.je_line_num
select ooha.order_number,ooha.org_id,
       hca.account_name,
       hp.party_name “Customer Name”,
       hcasab.orig_system_reference      BILL_TO_ORIG_REF,
       hpsb.status                       BILL_TO_STATUS,
       ‘ADDRESS1 – ‘||bill_loc.address1||’,’||CHR(10)|| ‘ADDRESS2 – ‘||bill_loc.address2||’,’||CHR(10)||
       ‘ADDRESS3 – ‘||bill_loc.address3||’,’||CHR(10)|| ‘CITY     – ‘||bill_loc.city||’,’||CHR(10)||
       ‘POSTAL CD- ‘||bill_loc.postal_code||’,’||CHR(10)|| ‘COUNTRY  – ‘|| bill_loc.country  BILL_TO_ADDRESS,
       hcasas.orig_system_reference      SHIP_TO_ORIG_REF,
       hpss.status SHIP_TO_STATUS,
       ‘ADDRESS1 – ‘||ship_loc.address1||’,’||CHR(10)|| ‘ADDRESS2 – ‘||ship_loc.address2||’,’||CHR(10)||
       ‘ADDRESS3 – ‘||ship_loc.address3||’,’||CHR(10)|| ‘CITY     – ‘||ship_loc.city||’,’||CHR(10)||
       ‘POSTAL CD- ‘||ship_loc.postal_code||’,’||CHR(10)|| ‘COUNTRY  – ‘|| ship_loc.country  SHIP_TO_ADDRESS,
       oola.inventory_item_id,oola.ordered_item,
       msib.description item_description,
       wnd.name delivery_number,
       rct.trx_number “AR Invoice Number”,
       acr.receipt_number “AR Receipt Number”,
       gjh.ledger_id,
       gjh.name
  from oe_order_headers_all ooha,
       oe_order_lines_all oola,
       hz_parties hp,
       hz_cust_accounts hca,
       hz_party_sites hpss,
       hz_party_sites hpsb,
       hz_locations bill_loc,
       hz_locations ship_loc,
       hz_cust_acct_sites_all hcasab,
       hz_cust_acct_sites_all hcasas,
       hz_cust_site_uses_all hzsuab,
       hz_cust_site_uses_all hzsuas,
       mtl_system_items_b msib,
       wsh_delivery_details wdd,
       wsh_new_deliveries wnd,
       wsh_delivery_assignments wda,
       ra_customer_trx_all rct,
       ra_customer_trx_lines_all rctl,
       ra_cust_trx_line_gl_dist_all rctld,        
       ar_cash_receipts_all acr,
       xla.xla_transaction_entities xte,
       xla_events xe,
       xla_ae_headers xah,
       xla_ae_lines xal,
       xla_distribution_links xdl,
       gl_import_references gir,
       gl_je_batches gjb,
       gl_je_headers gjh,
       gl_je_lines gjl
 where ooha.order_number = :SalesOrderNumber –Right click :RequitionNumber from Toad Enable Prompt For Substitution Variables
   and ooha.org_id = 204
   and hca.cust_account_id    = ooha.sold_to_org_id
   and hp.party_id            = hca.party_id
   and hpss.party_id            = hca.party_id
   and hpsb.party_id            = hca.party_id
   and bill_loc.location_id = hpss.location_id
   and ship_loc.location_id = hpsb.location_id
   AND hcasas.cust_account_id  = hca.cust_account_id
   AND hcasab.cust_account_id  = hca.cust_account_id
   AND hcasas.party_site_id    = hpss.party_site_id
   AND hcasab.party_site_id    = hpsb.party_site_id
   and hzsuas.cust_acct_site_id = hcasas.cust_acct_site_id
   and hzsuab.cust_acct_site_id = hcasab.cust_acct_site_id
   and hzsuas.site_use_id = ooha.ship_to_org_id
   and hzsuab.site_use_id = ooha.invoice_to_org_id            
   and wda.delivery_id        = wnd.delivery_id(+)
   and wdd.delivery_detail_id = wda.delivery_detail_id
   and wdd.source_header_id   = ooha.header_id
   and wdd.source_line_id     = oola.line_id
   and wdd.organization_id    = msib.organization_id(+)
   and wdd.inventory_item_id  =msib.inventory_item_id(+)
   and rct.interface_header_attribute1 = to_char(ooha.order_number)
   and rct.org_id = ooha.org_id
   and rctl.customer_trx_id = rct.customer_trx_id
   and rctl.sales_order = to_char(ooha.order_number)
   and rctld.customer_trx_id = rct.customer_trx_id
   and rctld.customer_trx_line_id = rctl.customer_trx_line_id
   and acr.receipt_number = ‘G-1001’
   and acr.pay_from_customer = rct.sold_to_customer_id
   and acr.org_id = ooha.org_id
   and acr.customer_site_use_id = rct.bill_to_site_use_id
   and xte.transaction_number = acr.receipt_number
   and xte.entity_code = ‘RECEIPTS’
   and xe.entity_id = xte.entity_id  
   and xah.event_id = xe.event_id
   and xal.ae_header_id = xah.ae_header_id
   and xal.accounting_class_code = ‘CASH’
   and xdl.ae_header_id = xah.ae_header_id
   and xdl.ae_line_num = xal.ae_line_num
   –and xdl.source_distribution_id_num_1
   and gir.reference_5 = xte.entity_id  — Entity Id
   and gir.reference_6 = to_char(xe.event_id) –Event Id
   and gir.reference_7 = to_char (xah.ae_header_id) — AE Header Id
   and gir.gl_sl_link_id = xal.gl_sl_link_id
   and gir.created_by = 1318
   and gjb.je_batch_id = gir.je_batch_id
   and gjh.je_batch_id=gjb.je_batch_id
   and gjh.je_header_id = gir.je_header_id
   and gjl.je_header_id=gjh.je_header_id
   and gjl.je_line_num= gir.je_line_num
 Important Profiles
1. Receiving transaction Processor concurrent not visible
TP: INV Transaction processing mode                 —         On-line

RCV: Processing Mode                                   —         On-Line  set to User & Resp.

2. Auto creates tools copy document next document form not pop-up.

PO: Display the Autocreated Document               —         No to Yes

PO: Display the Autocreated Quotation                —         No to Yes

PO: Allow Buyer Override in Autocreate Find        —         Yes or No

PO: Allow Category Override in Autocreate Find   —         Yes or No

PO: Allow Referencing CPA Under Amendment    —         Yes or No

PO: Allow Requisition Approval Forward Action     —         Yes or No

HR: Supervisor Hierarchy Usage —Use Assignment-based  Supervisor Hierarchies
                                                     Use Person-based Supervisor Hierarchies

HR: Display Position Hierarchy                           —         Yes or No

PO: Allow Requisition Approval Forward Action     —         Yes or No       

3. Requisition Import required Internal & Purchase Requisition

PO: Legal Requisition Type                                             —         Both

PO: Restrict Requisition line modify to quantity split         —         No

RCV: Allow routing override                                             —         Yes

OM: Display New Order after Copy                                  —         Yes

OM: Item Change Honors Frozen Price                            —         Yes

OM: Return Item Mismatch Action                                   —         Allow

4. Sales Order Number not automatic sequencing

Sequential Numbering                                                    —         Always Used

AR:Maximum lines per AutoInvoice                                  —        20

AR: AutoInvoice Gather Statistics                                    —         No

AR: Use Invoice Accounting For Credit Memos                 —         Yes

eBTax: Allow Override of Customer Exemptions                —         Yes

WIP:Job Name Updatable                                               —         Yes to No

Drop ship

OM: Population Of Buyer Code For Dropship Lines           —         Order Creator     (not mandatory)

Requisition import & Create release both should run at a time

PO: Release During ReqImport                                        —         Yes

Localization Profiles

Responsibility    —          Purchasing

JG: Application                          —         Purchasing

JG: Product                               —         Asia/Pacific Localizations

JG: Territory                              —         India

JG: Company Operating Unit       —         Operating Unit Name

Responsibility    —          Inventory

JG: Application                          —         Inventory

JG: Product                               —         Asia/Pacific Localizations

JG: Territory                              —         India

JG: Company Operating Unit       —         Operating Unit Name

Responsibility    —          Order Management

JG: Application                          —         Order Management

JG: Product                               —         Asia/Pacific Localizations

JG: Territory                              —         India

JG: Company Operating Unit       —         Operating Unit Name

Any changes from SO Header level it won’t affect to line level need to set the profile – R12 Futures:-

OM: Sales Order Form:
Cascade Header Changes to Line               —    Automatic

QP: Item Validation Organization               —    IMO

OM: Item Validation Organization             —    IMO setting up both should Same
                                     (then only Item should be listing in price list and modifier)

FND: Record History Enabled

FND: Diagnostics                     —    Yes (Customer web page view record history

Personalize Self-Service Defn–>

                                            No to Yes (Customer web page view record history)

HZ: Enable Duplicate Prevention at Party Creation —   Disabled

                                                                               Organization only

                                                                               Organization and Person

                                                                                Person only

HZ: Enable DQM Party Search                          —    Yes

ASO : Price List Override                                   —    Yes

PO: Allow Buyer Override in Autocreate Find       —     Yes

Transaction type added Customer PO mandatory —    Check box enabled
                                                                              Organization Type
In a Human Resources responsibility, the navigation is Other Definitions > Application Utilities Lookup.

    Works
    Non-Works
    Dump
    Branch
    Warehouse
    Goodown

1. Define FOB: AR à Purchasing lookup à Query FOB      —         Add the Value
                                                                             
2. Define Freight carrier: Order Management à Setup à Shipping à Freight Carrier, Cost Type à Freight Carrier      —         Add the value

3. Define Freight Terms: Order Management à Setup à Quick Codes à Order Management à Query Freight Terms   —   Add the Value

AR: AutoInvoice Gather Statistics               —         No to Yes

( AutoInvoice Master Program concurrent error)

AR:Maximum lines per AutoInvoice worker    —         10000 (null to 10000)

Credit Memo Profile

AR: Use Invoice Accounting For Credit Memos         —        Null to Yes

AR: Transaction Batch Source                                 —         Null to
                                                                                    
INV: Advanced Pricing for Inter-Org Transfers        —         Null to Yes

INV: Advanced Pricing for Inter-Org Transfers        —         No

Price list security:-
Price list and Modifier need to set to Operating Unit level or Global
QP: Security Control                                                —         OFF / ON

QP: Security Default Maintain Privilege                    —  Global
                                                                                      None
                                                                                      Operating Unit
                                                                                      Responsibility
                                                                                      UserQP: Security Default ViewOnly Privilege                   —   Global
                                                                                      None
                                                                                      Operating Unit
                                                                                      Responsibility
                                                                                      User

CST: Transfer Pricing Option                                     —         No

 Internal Sales Order Price Defaulted from Inventory Item cost à Sales Order à Line items à pricing tab à Calculate Price flag set Freeze price to Calculate price.

OM: E-Mail Required on new Customers  — No to Yes (When create new customer or add Contact)

Parallel Pick Future R12
Set the profile site level to
1. WSH: Number of Pick Release Child Processes’  –  50

Consigned Inventory functionality set this Profiles
INV: Allow Expense to Asset Transfer = Yes.

Check following 2 condition for your environment.
1) OE: Autobackorder is only effective if the profile, OE: Reservation = Yes
2) only affects items in a kit, model, or ship set during Pick Release.