We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

[sap-acct] Lockbox Not Clearing Invoices in Company Code

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Question from connie_durham on Jul 25 at 5:44 PM
Hi to All,
We are having problems getting the usesr exit to wrok as we have anticipated it should. We have activated both EXIT_RFEBLB20_001 and EXIT_RFEBLB20_002. We are attempting to post cash to company 3000, where the lockbox is defined. The invoice 18107001, that is being paid belongs to another company code, 1000.

We have updated AVIP-ABWBU to be the company code 1000. We have also updated fields
AVIP-ABWKO and AVIP- KONTO to reflect the customer number for the invoice that was posted to BSID. It appears that we are writing 2 records to AFIP for every record written to AVIK.

The first update program ends in an error message: Accounts Receivable posting Error: ( F5 170 No open items were found) and a Posted on account classification of the payment posted. FS10n shows the amount posted to the cash account. This customer is defined for both companies 1000 & 3000. On the next report output we get the messages, No customer with MICR number and *18107001 Document not found.

The clearing piece of the lockbox applications is not looking at company code 1000 open items. It is still looking at company code 3000. Please what can we do now to guide the clearing to company code 1000 and generate the cross company entries.

Thanks,
Connie
 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2014 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
connie_durham  

IT/IS Professional/Admin/Staff
achievements
 
View this online
Ask a new question
 
In the Spotlight
Become a blogger at Toolbox.com and share your expertise with the community. Start today.

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language