Error Handling
The AR Transaction API rejects transactions that fail one or more of its validation requirements. Errors must be fixed in your original system before the API can validate the data and then create the transaction in Receivables. After you update the information, you can call the Transaction API again to create the transaction.
Following are problems that can cause a transaction to fail validation:
- Incomplete or missing data: You need to provide basic information for this transaction type. For example, to create an invoice, be sure to include an transaction source, GL date, transaction type and date, currency code, sales credit information, customer name or number, Bill-To location, and a document number.
- Incomplete sales credit information: The Transaction API requires that both sales credit amounts and percentages are included when validating your transaction information.
- GL date in a closed period: The Transaction API will reject transactions whose GL date is in a closed period.
The API uses two mechanisms to return error information to your feeder system. First, the program places any error messages and optional debugging information on the standard API message stack. You can retrieve these messages using the FNDMSG_PUB.Get() routine. You can control the level of debugging information by changing the value of the profile option FND: Message Level Threshold.
The API also returns error information by populating the p_errors parameter. This parameter contains additional information such as the number of the record that had the error and the incorrect value(s) that caused the error.
See Also
Running the Transaction API
Preparing Your System
