Unable to get Intercompany transaction notification from Recipient user for inbound transaction

Please check your workflow background engine and agent listener are working fine,

Follow the below process step to ensure workflow services up and running,,,

1) Start the Workflow Agent listener Service:

a. Workflow administrator Web Applications Responsibility.
b. Workflow Manager.
c. Click on Service Components icon.
d. Click on the Workflow Agent listener Service link (Container column).
e. Select Workflow Agent listener Service.
f. Select Start from the list of values (top).
g. Click on go.
h. Wait until the Workflow Agent listener service is "Activated".

2) Retest the issue

Customer Interface Issue: Cannot Populate Account_Name In RA_CUSTOMER_PROFILES_INTERFACE

You cannot create Account Name using Customer Interface (RACUST) as this column does not exist in RA_CUSTOMER_PROFILES_INTERFACE.

Your alternative would be to use TCA API procedure to populate the Account Name:
Procedure: HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
Parameter Name = account_name


For More information:

Please refer the oracle support Notes:

1. Trading Community Architecture API User Notes
2. Note 189369.1 How To Create A Customer Via TCA API
3. Note 230753.1 Different uses of TCA API

Workflow error in AP payments (ap_payment_event_wf_pkg.rule_function' for event 'oracle.apps.ap.payment

Issue:

To SYSADMIN
Sent 18-Jun-2015 12:44:57
ID 1191209

An Error occurred in the following Event Subscription: Event Subscription

Event Error Name: WFE_DISPATCH_RULE_ERR
Event Error Message: 3825: Error '100 - ORA-01403: no data found
ORA-01403: no data found' encountered during execution of Rule function 'ap_payment_event_wf_pkg.rule_function' for event 'oracle.apps.ap.payment' with key '58478'.
Event Error Stack:
Wf_Event.dispatch_internal()

Cause:
AP_PAYMENT_EVENT_WF_PKG.RULE_FUNCTION has errors

When attempting to do remittance note test in vendor site set to email address then it errored out.

Technical Description:

When attempting to do remittance note test in vendorsite set to email address the following error occurs. Event Error Name: WFE_DISPATCH_RULE_ERR Event Error Message: 3825: Error 100 - ORA -01403:no data found ORA -01403:no data found encountered during execution of
Rule function 'ap_payment_event_wf_pkg.rule_function' for event 'oracle.apps.ap.payment'
with key '10040'.

Event Error Stack: Wf_Event.dispatch_internal()

Resolution:

The error occurs because there was some coding error in the package AP_PAYMENT_EVENT_WF_PKG, where the org context was not set properly for R12. So changed the code for proper setting of org context by the following code:
mo_global.set_policy_context('S',l_org_id);

And after the org context is set , still the work flow was not getting set and the reason was that procedure get_remit_email_address didn't fetch any data with respect to the email address as the query written to fetch the query was wrong for R12 as in R12 the data stored for payment details tab in the supplier window id stored in IBY_EXTERNAL_PAYEES_ALL instead of po_vendor_sites.

So changed the query from

SELECT remittance_email
INTO p_email_address
FROM po_vendor_sites
WHERE vendor_id = l_vendor_id
AND vendor_site_id = l_vendor_site_id;
to
SELECT remit_advice_email
INTO p_email_address
FROM IBY_EXTERNAL_PAYEES_ALL
WHERE supplier_site_id = l_vendor_site_id;


Solutions.:-


1) Please download and review the readme for patch 6119080:R12.AP.A.
6119080:R12.AP.A - brings appewfpb.pls 120.2.12000000.2 which just fixes the bug 6119080 (AP_PAYMENT_EVENT_WF_PKG.RULE_FUNCTION).
2) In a test environment, please apply Patch.6119080:R12.AP.A
3) Please confirm the following file versions:
$AP_TOP/patch/115/sql/appewfpb.pls 120.2.12000000.2
You can use the commands like the following:
strings -a ffffffff |grep '$Header'
4) Bounce all application services (adstpall.sh apps/<apps> & adstrtal.sh apps/<apps>).
5) Please retest the issue.
6) If the issue is resolved, please migrate the solution as appropriate to other environments.

Posting Throws 'APP-SQLGL-08090: Please open the period you have selected for this batch before posting

Cause:

This error is thrown when the batch being posted is expected to affect multiple ledgers (including Reporting Currencies) which do not have the same periods opened. 

In R12 a batch can contain many journals for many ledgers. They should all have the posting period for the batch opened, otherwise the error will be thrown and the batch will not post.

Solution:

1. Identify all ledgers affected by this batch being posted
2. Make sure they all have the posting period in Open status
3. Retest after opening the needed periods and confirm this worked fine

To avoid re-occurrence of this issue you could define a Ledger Set including all your ledgers and consider opening the periods for it.

Oracle General Ledger Implementation Guide page 1-122

Defining Ledger Sets
A ledger set is a group of ledgers that share the same chart of accounts and calendar/period type combination. Ledger sets allow you to run processes and reports for multiple ledgers simultaneously.
For example, you can open/close periods for multiple ledgers at once [...]

How To delete or Purge Customers from Oracle Receivables

At this time there is no functionality available to purge/delete customer information from Oracle Receivables and hence Oracle support can not provide a script to delete the customers incorrectly loaded or the customer that will never be used. Customer information is stored in about 20 to 25 tables. It is not supported solution to delete the record from the database by any unsupported means.

How To Create a Customer That is Also a Supplier

Step to create customer as a supplier:

1. Enable the profile option at site level : POS:SM: Supplier Data Hub Configuration

2. Set this profile option to "Standalone" if you are implementing Supplier Hub as a Standalone MDM instance.


3. Steps below to reproduce the same:

a. Create Customer Party
b. Login to Supplier Data Librarian Super User responsibility
c. Click "Select" and click the "Enable As Supplier" button & Save
d. Search for the customer created.
e. Navigate to Payables --- Supplier page and see "Enable As Supplier" option available
f. The customer that was enabled as a supplier is now available for further action.