![]() Only 1 value is currently allowed: -8 (Electronic Refund) The payment_schedule_id of the activity being applied to. Total applied to Electronic Refund, including this application and other applications on the same credit memo, must not fall outside the approval limits or Credit Memo refunds specified for the user/currency.ĪR_CKAP_OVERAPP, AR_REF_CM_APP_NEG, AR_REF_USR_LMT_OUT_OF_RANGE ![]() Must not cause the credit memo to be overapplied. The amount of the credit memo to apply to an activity. Must have a negative original amount due.ĪR_REF_NO_PAYMENT_METHOD, AR_REF_NO_CUST_BANK, AR_REF_NOT_OACM, AR_REF_CM_INCOMPLETE, AR_REF_CM_POSITIVE, AR_REF_MORE_THAN_CM_AMT, AR_REF_RCT_CLASS_REMIT, AR_REF_NO_REMIT_BANK Receipt method must have a remittance bank account. Receipt method must belong to a receipt class that allows remittance. Must be a completed on-account credit memo (not a regular credit memo related to an invoice where previous_customer_trx_id has a value). The following table lists the parameters that are relevant to the activity_application routine: ParameterĬustomer transaction identifier of the on account credit memo to be applied. This is the message in encoded format if x_msg_count=1 Number of messages in the API message list See: Exception Handling and Result Messages. Represents the API overall return status. Not to be used currently as this is a public API. Used by API callers to ask the API to commit on their behalf. In the current version of the API, you should pass in a value of 1.0 for this parameter.Īllows API callers to request that the API does initialization of the message list on their behalf. Unexpected error is raised if version in-compatibility exists. ![]() Used to compare version numbers of incoming calls to its current version number. The following table lists the standard API parameters which are common to all the routines in the credit memo application API: Parameter (p_global_attribute_category IN VARCHAR2, The input global descriptive flexfield parameter is a record of type global_ attribute_rec_type: TYPE global_attribute_rec_type IS RECORD The input descriptive flexfield parameter is a record of type attribute_rec_type: TYPE attribute_rec_type IS RECORD Input ParametersĪctivity application parameters: 12 (including 1 descriptive flexfield parameter and 1 global descriptive flexfield parameter) Output ParametersĪctivity application parameters: 4 required parameters (might vary depending on the adjustment type) Parameter Descriptions ![]() The API returns the receivable_application_id of the receivable_application created. Use this routine to apply an on-account credit memo to an activity, such as Electronic Refund. To apply or unapply an on-account credit memo to an activity, call the following APIs:Īr_cm_application_pub.activity_application: Applies an on-account credit memo to an activity.Īr_cm_application_pub.activity_unapplication: Unapplies an on-account credit memo from an activity.Īr_cm_application_pub.activity_application The Credit Memo Application API enables the following business actions:Īpplication of an on-account memo to the Electronic Refund activity, resulting in subsequent refund of the credit memo to the customer. Please refer to the Oracle Receivables User Guide for more detail on customer credit refund functionality. This public API currently allows the application of an on-account credit memo to an activity such as Electronic Refund, which creates a customer refund for the credit memo via the creation of a negative miscellaneous receipt. This document outlines in detail the Credit Memo Application API. 8/18 Credit Memo Application API User Notes Overview
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |