, , ,

Oracle E-Business Suite: Creating Item templates

An Item template is a set of attributes that enable the ‘quick’ creation of an Item. In this recipe, we will create an Item template that can be used to create many similar Items. We will copy from the Finished Good template to our new template called ACME Finished Good.

Getting ready

Log in to Oracle E-Business Suite and select the Inventory responsibility.

How to do it…

Let’s list the steps required to create an Item template:

  1. Navigate to Setup | Items | Templates.
  2. Select the Inventory Organization.


 From the Find Item Templates form, click on New button or press Alt+N.

In the Template field, enter the name of the new template; for example, enter ACME Finished Good.
In the Description field, enter a suitable description, for example, enter ACME Finished Good Template.

  1. Select Copy Template from the Tools menu.
  2. We can use this form to select the attributes groups that we want to copy from the Finished Good template.
  3. Click on the Apply button.
  4. Click on the Done button.
  5. In the dialog box presented to us, with the message “Do you want to save the changes you have made?”, click on the Yes button.

How it works…

Item templates can be created from scratch. To make the template creation process easier, Oracle has provided us with a number of seeded templates as a starting point to copy from. We can also combine templates and manually amend the attributes to define our template. When we copy from an existing template, we have choices that determine how the copy will occur.

The three main choices are as follows:

  1. Overwrite: All selected attribute values are copied to the new template and any values that we have manually created will be overwritten.
  2. Append: Attributes that have no value will be copied across to our template. This mode is useful if you are using a combination of templates.
  3. Overwrite Not Null: Only the selected attributes that contain values will be copied.

There’s more…

Let’s amend the template to allow us to automatically populate the template with some default values. Let’s create an Item and apply the amended template to the Item.

Amending the template

Let’s search for the template and amend the templates to include some of the default values:

  1. Search for the ACME Finished Good template by navigating to Setup | Items | Templates.
  2. Enter ACME Finished Good in the Template field and click on the Find button.
  3. Click on the Open button to view the template.


In the Attributes Group region, select Purchasing and enter some default values, for example:

  • Default Buyer: Stock, Ms. Pat
  • Input Tax Classification Code: VAT-15%
  • Taxable: Yes
  • Allow Description Update: Yes
  • Receipt Required: Yes

 Save the template.


 In the Attributes Group region, select Receiving and enter some default values, for example:

  • Over-Receipt Qty Action: Warning
  • Receipt Routing: Direct Delivery
  • Days Early Receipt Allowed: 5
  • Days Late Receipt Allowed: 2
  • Receipt Date Action: Warning

Save the template.
In the Attributes Group region, select Invoicing and enter some default values, for example:

  • Accounting Rule: Immediate
  • Payment Terms: Immediate

Save the template.

Creating an Item and applying the template to the Item

Let’s create an Item and apply the template to the Item:
Navigate to Items | Master Items.
Enter the Item code and description.
Select Copy From in the Tools menu.

 
Click on the Apply button.
Click on the Done button. This action will validate the template created.

 
Click on the Purchasing tab to review the default values of the attributes assigned automatically by the template.
Save the Item.

Exploring Item controls

During the creation of Items, we may decide to restrict the use of the Items by controlling Items within an Inventory Organization. When an Item is defined, it is defined in the Item Master Organization and can then be assigned to other Inventory Organizations. Items are then held in Subinventories, which can contain Locators. Locator, Serial number, Lot number, and Revision number within a Subinventory can be used to control Items. In this recipe, we will explore some of the control parameters for Items.

Getting ready

Log in to Oracle E-Business Suite and select the Inventory responsibility.

How to do it…

Let’s explore the following Item controls:

  1. Item Status
  2. Item Attribute

The Item Status is the status of an Item and it determines the actions that can be performed on an Item. For example, an obsolete Item may not be sold to the customer, but can be used as parts for repairs and can still be stockable. Let’s create an Item status for obsolete Items.
Navigate to Setup | Items | Status Code. 

In the Status field, enter Obsolete and ACME Obsolete in the Translated Status field.
Enter a Description, for example, ACME Obsolete Items.

 Enable the following attributes:
  • BOM Allowed
  • Stockable
  • Transactable

Save the form.

The levels that the attributes can be controlled at are set in the Item Attribute Controls form. Let’s look at some of the Item Attribute Controls:
     Navigate to Setup Items | Attribute Controls|
     From the menu, select View | Query By Example | Enter (or press F11 on the keyboard).
     In the Group Name field, enter Main%. 

     From the Menu, select View | Query By Example | Run (or press Ctrl+F11 on the keyboard).
     Observe that some attributes are controlled at the Master Level and some at the Org Level.
     Close the form.

There’s more…

Items are stored in a Subinventory and can be controlled using a locator. Items can be identified by lot and by serial numbers.

Storing Items by Subinventories

Subinventories are distinct separations of Items within an Inventory Organization. Subinventories can be physical or logical. Items within an Inventory Organization must reside in a Subinventory.
Transactions are performed from the Subinventories. Examples of Subinventories include: finished goods, van, stores, staging area, and fast moving goods. Let’s create a finished goods Subinventory and restrict an Item to the Subinventory.
    Navigate to Setup | Organizations | Subinventories.
    Click on the New button. 
        In the Name field, enter ACME-FG.
        In the Description, enter ACME Finished Goods.
        In the Locator Control field, select Item level. This will enable the Inventory transactions for 

         this Subinventory to use locator control, which we define at the Item level.
Save the record.
 Let’s restrict an Item to the Subinventory:
      Navigate to Items | Organization Items.
      Search for the PRD20001 Item.
 Oracle E-Business Suite: Creating Items in Inventory
Select the Inventory tab and select the Restrict Subinventories checkbox.
d.

    In the Tools menu, select Items Subinventories.
    Select ACME-FG in the Subinventory field.

    Save the record.

Storing Items by locators

Stock locators identify the physical areas where Items are stored. Additional controls can be placed on the Items in stock locators. For example, we can control the shelf life of an Item with stock locators. Stock locators are usually defined as Row, Rack, and Bin. Let’s create three stock locators for the ACME Finished Goods Subinventory and restrict an Item by locator control:
Navigate to Setup | Organizations | Subinventories. 

Search for the ACME-FG Subinventory (press F11 on the keyboard, and enter the search mask ACME%, then press Ctrl+F11 on the keyboard).
Click on the Locator button to enter the locator details.

   Enter A1.1.1 in the Locator field.
   In the Description field, enter ACME FG 1.
   In the Type field, select Storage Locator.
   Enter another row for A1.1.2, ACME FG 2, with Storage Locator in the Type field.
   Repeat for A1.1.3, ACME FG 3, with Storage Locator in the Type field.

Save the record. 

The structure of the stock locator is defined in the stock locator Flexfield structure and can be defined to fit your business requirements. Locator Control can be “prespecified” before they are used or can be defined dynamically as Items are received or shipped.
Let’s restrict an Item to the Locator:
    Navigate to Items | Organization Items.
    Search for the PRD20001 Item.

 
     Select the Inventory tab, select the Restrict Locators checkbox, and then select the Locator Control as Prespecified.
Save the record.
In the Tools menu, select Items Subinventories.
Select A1.1.1 in the Locator field.
Save the record.

Identifying Items by lot control

A lot of numbers can be used to identify Items that share the same specifications. For example, lot numbers can be used to specify the expiry period of an Item. Let’s look at how to use lot numbers to control Items. We will impose a shelf life of 30 days on the Item and assign lot numbers to the Item:
     Navigate to Items | Organization Items.
     Search for the PRD20001 Item.

Select the Inventory tab.
In the Lot Expiration (Shelf Life) region, select the Control field and select Shelf Life Days.
Enter 30 as the number of days.
In the Lot region, select Full Control in the Control field.
Save the record.

Tracking Items using serial control

Serial numbers can be used to track an Item. A serial number is assigned to each unit of the Item, if serial control is used:
Navigate to Items | Organization Items.
Search for the PRD20001 Item.

Select the Inventory tab.
In the Serial region, select the Generation field, and select At Receipt. This will allow us to specify the format of the serial numbers at the time of receipt.
Save the record.

Controlling Items using revisions

Items can have versions. Item versions are controlled using revisions. For example, we can decide to make the PRD20002 revision controlled, and have another version of the Item. Let’s change the attribute to revision controlled and add a revision B to the Item:

Navigate to Items | Organization Items.
Search for the Item PRD20002.

In the Inventory tab, enable the Revision Control checkbox.
In the displayed message, select OK.
Save the Item.

From the Tools menu, select Revisions.
Add a line for Revision B of the Item with the description Revised Widget.
Save the record.

Summary

This article included recipes for creating Items and exploring the Item attributes. It then continued with creating Item templates and exploring Item controls.

/by
, , , ,

Order Management Tables and its details

Order Management Tables. Entered
oe_order_headers_all 1 record created in header table
oe_order_lines_all Lines for particular records
oe_price_adjustments When discount gets applied
oe_order_price_attribs If line has price attributes then populated
oe_order_holds_all If any hold applied for order like credit check etc.
Booked
oe_order_headers_all Booked_flag=Y Order booked.
wsh_delivery_details Released_status Ready to release
Pick Released
wsh_delivery_details Released_status=Y Released to Warehouse (Line has been released to Inventory for processing)
wsh_picking_batches After batch is created for pick release.
mtl_reservations This is only soft reservations. No physical movement of stock
Full Transaction
mtl_material_transactions No records in mtl_material_transactions
mtl_txn_request_headers
mtl_txn_request_lines
wsh_delivery_details Released to warehouse.
wsh_new_deliveries if Auto-Create is Yes then data populated.
wsh_delivery_assignments deliveries get assigned
Pick Confirmed
wsh_delivery_details Released_status=Y Hard Reservations. Picked the stock. Physical movement of stock
Ship Confirmed
wsh_delivery_details Released_status=C Y To C:Shipped ;Delivery Note get printed Delivery assigned to trip stopquantity will be decreased from staged
mtl_material_transactions On the ship confirm form, check Ship all box
wsh_new_deliveries If Defer Interface is checked I.e its deferred then OM & inventory not updated. If Defer Interface is not checked.: Shipped
oe_order_lines_all Shipped_quantity get populated.
wsh_delivery_legs 1 leg is called as 1 trip.1 Pickup & drop up stop for each trip.
oe_order_headers_all If all the lines get shipped then only flag N
Autoinvoice
wsh_delivery_details Released_status=I Need to run workflow background process.
ra_interface_lines_all Data will be populated after wkfw process.
ra_customer_trx_all After running Autoinvoice Master Program for
ra_customer_trx_lines_all specific batch transaction tables get populated
Price Details
qp_list_headers_b To Get Item Price Details.
qp_list_lines
Items On Hand Qty
mtl_onhand_quantities TO check On Hand Qty Items.

Payment Terms
ra_terms Payment terms

AutoMatic Numbering System
ar_system_parametes_all you can chk Automactic Numbering is enabled/disabled.
Customer Information
hz_parties Get Customer information include name,contacts,Address and Phone
hz_party_sites
hz_locations
hz_cust_accounts
hz_cust_account_sites_all
hz_cust_site_uses_all
ra_customers
Document Sequence
fnd_document_sequences Document Sequence Numbers
fnd_doc_sequence_categories
fnd_doc_sequence_assignments
Default rules for Price List
oe_def_attr_def_rules Price List Default Rules
oe_def_attr_condns
ak_object_attributes
End User Details
csi_t_party_details To capture End user Details

Sales Credit Sales Credit Information(How much credit can get)
oe_sales_credits

Attaching Documents
fnd_attached_documents Attched Documents and Text information
fnd_documents_tl
fnd_documents_short_text

Blanket Sales Order
oe_blanket_headers_all Blanket Sales Order Information.
oe_blanket_lines_all

Processing Constraints
oe_pc_assignments Sales order Shipment schedule Processing Constratins
oe_pc_exclusions
Sales Order Holds
oe_hold_definitions Order Hold and Managing Details.
oe_hold_authorizations
oe_hold_sources_all
oe_order_holds_all

Hold Relaese
oe_hold_releases_all Hold released Sales Order.

Credit Chk Details
oe_credit_check_rules To get the Credit Check Againt Customer.
Cancel Orders
oe_order_lines_all Cancel Order Details.
/by
, , , , ,

Order Management Drop Shipment, Functional Setup and flow

 E-commerce site like ebay, ubid.com and amazon.com which are very common place in advance countries like USA, UK & Singapore where people can sell or buy there product. Have you ever think ,what is similar situation in real world , when the the word ‘drop shipment’ comes to your mind. ……a business situation when the retailer or trader has no stock himself, instead giving customer details directly to the seller, and then saler than fills the order and send it to customer directly.How its sounds…
In other words, Drop Shipment is a process where the customer places a purchase order on a company and this company instructs its supplier to directly ship the items to the customer. A Drop Shipment occurs when a customer order is sourced from and delivered by a supplier.Order Management sends information to the Purchasing Application to create that PO, and then when that PO is received (to indicate shipment from the supplier to your customer), the order line is automatically updated to indicate that it was fulfilled. In this process, the company running Order Management is modeled as the company to whom the end customer places the original order.
We need to make sure these are attribute setup Correctly:
Item Attributes
Purchased : Enabled
Purchasable : Enabled
Transactable : Enabled
Stockable : Optional
Reservable : Optional
Inventory Item : Optional
Customer Ordered : Enabled
Customer Order Enabled : Enabled
Internal Ordered : Disabled
OE Transactable : Enabled
Shippable : Optional
And We do set up for Order Source Type as External.
Drop Shipment Setup checklist
Ensure you have created your Order Management Transaction Types and linked your Transaction Types to order and line workflows that support drop shipments.
Ensure the Oracle Workflow Background Engine is running.
Ensure all Drop ship locations you will use to perform drop shipments have the Ship To Site and Receiving Site defined.
Ensure you have defined the Internal Ship To Locations for your drop shipment customers (Oracle Receivables Standard Customer window, Business Purpose Details Tab).
Ensure your standard items have an associated List Price defined within your PO Inventory organization (Oracle Payables Financial Options window, Supplier-Purchasing Tab).
Drop Shipment – Process Steps
Create a Sales Order with line where the line source is External
Book and Schedule the Sales Order
Run Requisition Import Process
Now the line status will be in Awaiting Receipt
Login to the Receiving Organization (Purchasing) who has been setup as an Approver
Run Requisition Import
Create Purchase Order from the Requisition
Approve the PO
Receive the full quantity
Run Auto Invoice
Verify Invoice in Sales Order
Check the details here .

Things not to forget in a Drop Shipment

Release 11i/12 does not support Drop Shipment across operating units.
Blanket PO’s will not used with Drop Shipment , the reason the PO must be created when OM notifies PO that a Drop Ship order has been created.
You can’t cancelled Drop Shipments once Oracle Purchasing obtains the receipt.
Standard Items can be used for Drop Shipment.
In 11i, PTO’s and ATO’s cannot be drop shipped

Difference between “Internal” and “External” Drop-Ship

In Oracle Context External Drop-Shipping means your Oracle Order Management uses purchase orders to outside suppliers that are automatically generated from sales orders for goods supplied directly from the supplier. The “external ” supplier ships the goods directly to the 3rd Party customer and confirms the shipment through the use of an Advanced Shipment Notice(ASN). Note:Oracle uses this ASN to record a receiving transaction into inventory followed by an immediate logical shipping transaction. From these transactions, conveyance of title takes place and the customer can be invoiced and the supplier’s invoice can be processed. where as “Internal” context Drop-Shipping functions in a similar fashion. The key difference is that no inventory transactions take place on the books of the selling operating unit; transfer of ownership of the goods from shipper to seller to customer with the only physical movement of the goods being out of the shipping organization.

Parallel Pick Release

Parallel pick release enables multiple pick release processes to run simultaneously as child processes through the Pick Release SRS Parameters window and Release Sales Orders window through the concurrent mode. Parallel pick release is available when pick releasing from the Tools menu on the Shipping Transactions form through the concurrent mode.
Parallel pick release enables you to set a default number of child processes by defining the profile option: WSH: Number of Pick Release Child Processes.
Ship sets and ship models are processed first during pick release. They are included as part of the child processes.
Parallel pick release can be run from the Shipping Transactions form Tools menu. It cannot, however, be executed from the Shipping Transactions form action Launch Pick Release. Parallel pick release does not run when Pick Release is executed Online.

/by
, , , ,

What is auto lockbox in oracle applications?

Lockbox is a service provided by banks by which your company gets the customers payments directly to a lockbox interface tables and creates receipt for the payments deposited into your account. If you have an Auto Lockbox, the bank records the information that you request such as check number, check amount, numbers and amount for the invoices to be paid.
Oracle provides you with the tools to:
* Oracle interface tables for the data received from the bank
* Validate the data to see if it is accurate, complies with the controls provided
* Correct the data
* Apply the receipts to the customer’s open invoices.

A typical Lockbox transmission contains various different records, each with relevant data. Controls are provided at each level to ensure that the transmission was successful and to verify that the count and dollar amounts are consistent with what the bank indicated. These controls are at the transmission, Lockbox, batch and receipt levels. The records also contain information such as your bank account (by Lockbox) and the details for the receipts the bank received. The Lockbox may be used for checks, wires and any other receipts that you receive. You define what the data from the bank will look like and how you will use it.
Oracle Accounts Receivables Module provides the feature such that the customer can directly make the payment for their invoices in the Bank.The Bank would send a datafile in a  agreed transmission format which we we import in Receivables through AutoLockbox.After successful import the Receipts get created in the final stage.
This is a three step process
1) Validate the data file
2) Import the data file which created the Post Batch
3) Run the Post Batch  (ie Post Quick Cash) which would actually create the Receipts and applies against the Invoice on the Information provided in the data file.
Following are the main tables for auto lockbox

AR_PAYMENTS_INTERFACE_ALL
AR_INTERIM_CASH_RECEIPTS_ALL
AR_INTERIM_CASH_RCPT_LINES_ALL
AR_CASH_RECEIPTS_ALL
AR_CASH_RECEIPT_HISTORY_ALL
AR_DISTRIBUTIONS_ALL
AR_RECEIVABLE_APPLICATIONS_ALL
AR_PAYMENT_SCHEDULES_ALL

/by
, , ,

Troubleshooting Remit To Address in Oracle Receivables

Troubleshooting Details

1.  Setup and Usage of Remit-To Address in Oracle Receivables

Define remit-to addresses to let your customers know where to send payment for their invoices. Receivables uses the addresses that you define in the Remit To Addresses window to provide default remit-to information when you enter transactions.  Remit-To Addresses are also printed on invoices and optionally printed on Statements and Dunning Letters (Based upon the selections in the System Options window for AR). 

If you use AutoInvoice but have not defined a remit-to address that can be derived for a specific bill-to address,  AutoInvoice will reject all invoices for which it could not determine a remit-to address with the following message in the AutoInvoice Import Execution report:

Errors: 1) Cannot get remit to address

If you do not wish to set up a remit-to address for each location, you can set up one remit-to address with a default assignment. Receivables will then use this address for all locations or for any locations for which you do not have specific location assignments. This ensures that AutoInvoice will not reject invoices because it could not determine a remit-to address.

For more on setting up Remit-To Addresses in Oracle Receivables including step-by-step instructions and screenshots, refer to Note 1101666.1, How to Setup a Remit-To Address in Release 12 Oracle Receivables.
2. Troubleshooting Remit-To Address Issues and Errors on Transactions

    a. Error: Cannot Get Remit To Address

This is the most common error reported for Remit-To Addresses.  The steps below outline how you can determine what value should be used and also how to fix this problem.

Alternate Error Presentations:

WARNING: No default remit-to address found
WARNING: No default remit-to address (country) found

        i. Identify The Customer Bill-To Address

The Remit-to Address is derived based upon the customer Bill-To Address.  You should therefore begin troubleshooting by identifying the Bill To Address (State, Postal Code and Country)

        ii. Identify the Operating Unit on the Transaction

For a Manual Invoice, this can be found by looking at the list of values on the Transaction Source as shown below:

For AutoInvoice this can be found
Responsibility:  Receivables Manager
Navigation:  Control > AutoInvoice > Interface Lines

As shown above the Operating Unit field will be displayed.  If AutoInvoice failed with an error, query this form for any rows where the “Errors Exist” checkbox is checked.  This will return a listing of all rejected records.  Find the row that is showing a rejection reason of ‘Cannot Get Remit To Address’ and take note of the operating unit displayed for that row.

        iii. Check your Remit-To Address Setup

Note 1101666.1 explains in detail how to set up a Remit-To Address. 

Open the Remit-To Address form as shown below

Responsibility: Receivables Manager
Navigation:  Setup > Pring > Remit To Address

Find the row or rows associated to your Operating Unit and check to see if the bill to address is covered by the “Receitps From” definition.

The most common cause of an error in deriving a Remit-To address is in this “Receipts From” mapping.  A best practice to avoid problems is to set a default remit-to address for all countries where you transact.  This allows you to avoid errors during AutoInvoice and transaction entry.  In the example above we have defined this California address as the default for all Canadian bill-to addresses. 

Note: You can derive an alternate remit-to address with a more narrow definition.  For example, if you have a default for the United States with a New York address but then have a California address that is mapped to a specific Postal Code range, the system will use the California address ahead of the default address for any address in the from/to postal code range

In this example the Invoice had a Florida address but tthe Receipts From shows no combination that includes this Florida Address.   Assuming the Row above with the New York address also does not cover this Florida addess we can fix this defaulting issue by modifying the “Receipts From” to include the Bill  To address from the Invoice.

    b. Can I Use Additional Factors to Default the Remit-To Address?

At this time the only factors available to derive remit-to address are Geography and Operating Unit.

    c. Remit-To Address is not Defaulting

Refer to section 2a and verify that the address is properly mapped in the ‘Receipt From’ setup.

    d.  Unable to Delete Obsolete Remit-To Address

Receivables does not allow for a remit-to address to be deleted.  It is suggested that instead of deleting an address, the Receipt From values under the address simply be deleted.

    e. Remit-To Address Does Not Include All Address Segments

ARXSURMT.fmb , Remit to Address Form has Record group State based on the following query:

select state_code, description
from ar_remit_to_state
where country = :loc.country

Ar_remit_to_state is a view based on hz_locations table.  Data is populated in this table as customer addresses are created thus if you have not yet defined customers the LOV will not show the segments as available for selection. 

For more on configuring geographies in R12 refer to Note 554492.1 Setting Up Geography Hierarchy And Address Validation in Release 12

    f. Remit-To Bugs and Other Common Errors

Row
 Release Error String or Presentation  Cause Recommended Fix*
1
 12.0 When using Multiple Org’s in AR, if a transaction type is entered for operating unit “A” and then subsequently changed to a transaction type associated with operating unit “B”, the Remit-To address is not being updated to reflect this change. Bug 8642210 Remit To Address not properly refreshed Recommended Patch: 
12.0 Patch 9451008
12.1 Patch 9343518
Fixed File: ARXTWMAI.pld 12.0: 120.163.12000000.72
12.1: 120.180.12010000.46
2
 12.0
Re-display the remit-to address details, the following error message is displayed:
No HZ_CUST_ACCT_SITES was found for ID XXXX
 Bug 8522000 Recommended Patch:
12.0: patch 8331653
Fixed File: HzPuiAccountSiteAMImpl.java 120.22.12000000.3
12.1Patch 8522000
Fixed File: HzPuiAccountSiteAMImpl.java 120.25.12010000.2

Fix is included in 12.0.6 and 12.1.2 forward
3
 12.0 iSetup is creating duplicate Remit-To addresses instead of updating existing records Bug 6729003 Patch 6729003
See also Note 550257.1
4
 12.0 AR_DEPOSIT_API is not Defaulting the correct remit-to address via the Bill To Location Bug 9451008 Recommended Patch:  Patch 9451008
Fixed File: ARXDEPLB.pls
12.0.6
120.11.12000000.4
12.1
120.12.12010000.3
5
 12.0 
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-1419: MSG-00100: DEBUG: BeforeReport_Trigger +
 Remit-To Address was not defined and invoice print was attempted Define remit to address and/or default remit-to
6
 12.0
Query a transaction returns:
ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "APPS.ARP_TRX_DEFAULTS_3", line 1463
Debug log showed:
selecting the default remit to address.
EXCEPTION: arp_trx_defaults_3.get_default_remit_to()
EXCEPTION: arp_trx_defaults_3.get_remit_to_address()
---------- Parameters for arp_trx_defaults_3.get_remit_to_address() ----------
p_match_state : NJ
p_match_country : US
p_match_postal_code : 07095
p_match_address_id :
p_match_site_use_id :
EXCEPTION: arp_trx_defaults_3.get_remit_to_default()
 Remit-To address not properly defined Review/correct setup.
7
 11.5 – 12.1
When printing a specific credit memo, it errors with the following:
MSG-43749: There is no remit to address defined for country US and state XX.
REP-1419: 'remit_to_control_idformula': PL/SQL program aborted.
 The zip code for this credit memo was not included in any of the existing remit-to ranges. Make sure a valid range is defined for the zip code on the transaction.

1. SetupPrintRemit-To Address –> Add a range for zip code 09136 (this problem zip code in this example) which is the zip for the credit memo.
2. A new line can be added, or you can alter the existing range for the that state to include the new zip code

Alternately you can set a default to be used to avoid this issue.
8
 11.5 – 12.1 
APP-FND-00676 The flexfield routine FDFGDC cannot read the default 
reference field specified for this descriptive flexfield
 Incorrect setup of descriptive flexfield for Customer Form Customer form and Remit-To address form share a common foundation.  Enhancement 3100593 was logged to split these apart.  Until this is fixed it is suggested that the DFF not be used on the Reference Field for the Address InformationDFF
9
 11.5 
Remit-to Address Does Not Exist In The List of Values.
State/Country combination already exists.
APP-AR-96282 Error: Invalid value for party_site_id
 Data Corruption of unknown origin (rare occurrence) Perform the following steps to resolve this issue: Verify Issue
1.) select address_ id
from ra_remit_tos_all
where country = ‘DEFAULT’
and state = ‘DEFAULT’;

2.) Select address1, address2, address3, city, state
from ra_addresses_all
where address_id = ‘&address_id_step1’;

If query 2 returns no rows then corruption exists.  Contact Support for assistance
10
 11.5
Entering new Remit-To address returns:
APP-AR-96282: Error: The following SQL error occurred:
ORA-29861: domain index is marked LAODING/FAILED/UNUSABLE
 Corrupt domain index 1. Rebuild the domain indexes associated to the form as described  in Note 165115.1

HZ_CUST_ACCT_SITES_ALL_T1
HZ_LOCATIONS_N15
HZ_STAGE_PARTY_SITES_T1
11
 11.5
Opening Remit-To Form from OM returns:
ORA-06550: line 1, column 7:
PLS-00905: object APPS.ARP_STAX_165 is invalid
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
ORA-06512: at "APPS.ARP_STAX", line 371
Item Validation Organization is not set. 1. Order Management Responsibility, N: Setup > System Parameters > Values
2. Select the ‘Generic Parameters’ Category.
3. Pick your org into ‘Item Validation Organization’
4. Save your work.
12
 11.5 
ORA-06550: line 1, column 7:
PLS-00905: object APPS.ARP_STAX_5749 is invalid
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
ORA-06512: at "APPS.ARP_STAX", line 371
FRM-40735: WHEN-NEW-FORM-INSTANCE trigger raised unhandled exception ORA-06550.
Tried to compile ARP_STAX_5749 package and got the following error message:
PLS-00920: parameter plsql_native_library_dir is not set.
 ARP_STAX package for this ORG_ID was in status invalid. set parameter plsql_native_library_dir and bounce the DB to take effect
13
 11.5 
APP-AR-96282 Error:Value for Party_site_number must be unique.
 The profile HZ: Generate Party Site Number is ‘No’

The remit-to-address does not have the field to enter the site number in that case must be generated

 This is ER: 3297103: ‘GENERATE PARTY SITE NUMBER’ IS ‘NO’,SITE NUMBER IS
COUNTED BY AUTO.

Workaround
———-

1. Go into the responsibility: System Administrator
2. Create a new responsibility to have the privileges to create the remit-to-address setup
3. Assign thjavascript:void(0)at responsibility to the user in charged to do that

or

1. Go into the responsibility: system Administrator
2. Navigate to Profile System
3. Put the profiles
HZ: Generate Contact Number
HZ: Generate Party Number
HZ: Generate Party Site Number
in Yes, for the User designated to create the remit-to-address or a Dummy user that will do that
14
 11.5 
Rep-1401: 'C_Remit_To_Concatenateformula' Ora-01403: No Data Found
 Remit-To Address and/or Default not defined Setup Remit-To Address as per Note 1101666.1
15
 12 Remit to address does not show in Dunning  Bug 9437627 Patch 10198415

Fixed File ardlgm.lpc 115.47.15104.38 (or higher).

*Note: that the patch recommendation is for the latest released version of the file and not necessarily the version that included the fix.  For example, if version 46 is the fixed file, the recommended patch may contain version 72 of the fixed file.  This fix will include the bug fix referenced here as well as any other bug fix released since the bug was resolved.

3. Troubleshooting Printing Related Remit-To Address Issues and Errors

    a. Remit-To Address is Not Printing, No Errors

By default the system should print the remit-to address from the invoice when printing statements, dunning and invoices.  If this does not print verify the following:

1) Check in Setup -> System -> System options, Alternate Region- Miscellaneous if the Print Remit to Address flag is checked
2) Verify that the invoice has a remit-to address defind

    b.  Remit-To address Errors with MSG-43749: There is no remit to address defined for country and state

This problem has been reported when the default value contains postal codes.  Removing the postal code has proven to remedy this symptom.

    c. Is it possible to highlight the Remit-To Address when printing?

In BPA, you can select “Bold” or “Regular” for the content item value.

Hence, you can duplicate the default template and make the remit to address as “Bold”.  It is even possible to make BOLD only a part of the Remit-To address.
Instead of using BPA content item ‘Remit To Address Formatted’, use each individual content item such as ‘Remit Address 1’, ‘Remit Address 2’ etc.

4.  Descriptive Flexfields on Remit-To Addresses

The top zone of the Remit-To Address form displays the “Address Information” DFF. This is by design. This allows one to see additional address info for the current address displayed. The “Receipts From” zone is where the “Remit Address Information” DFF is available

/by