2014 Mar 25 6:50 AM
Hello,
I would like to lock a debit item for automatic clearing but let it be paid via FPY1.
When trying to lock it using the posting lock it can't be paid via FPY1.
What can I do ?
Thanks,
Vered
2014 Mar 26 5:14 PM
Vered:
this is not possible. the best case is to schedule FPY1 to run prior to auto clearing, and to set a clearing lock until a date when the payment is scheduled. To my ears, the real issue is why there are items which could clear an item yet you want to take a payment for it. Maybe you also revisit your clearing rules to exclude certain items if they can be identified properly.
regards,
bill.
2014 Mar 26 5:17 PM
When i say not possible - i mean using locks. The lock for clearing will lock from payment run also. You might identify a custom field to update on a document item, then use that value as indicator during auto clearing that the item should be excluded. this would likely involve one or two enhancements.
2014 Mar 27 7:23 AM
Hi ,
In
CA/A/r a/p--basic function--open item management --clearing control--define specification for clearing types --define defaults for account maintenance
click on the clearing type (03,04) and go to selection criteria define for clearing category and the concerned main/sub , tick the NC column , this will exclude the particular main sub from clearing .
similarly for account maintenance during invoicing go to
sap utilities --- invoicing ---invoice processing --item selection in invoicing --item selection in account maintenance for the clearing type , click on item selection for account maintenance , for the main/sub, mark OISEL ="9"
2014 Mar 27 12:38 PM
Hi,
Setting the clearing restriction Z - "Clearing Only by Payment Program" upon posting should do the job, I believe (I have not verified this...).
cheers
Janis
2014 Mar 27 1:35 PM
Janis:
That is a good thought - except there is not a manual means to add the restriction. Manually you can only remove a restriction.
Vered - what is your business process here?
regards,
bill.
2014 Mar 28 7:15 AM
Hi,
Indeed, and standard uses it within credit processing... It should be possible to set it upon posting debit in FQEVENT 0061, provided other restriction was not set prior to it. The credit processing can set it via FKK_DOCUMENT_CHANGE as well, so custom logic for setting it on existing debits may be possible. But whether it's really good idea to extend the use beyond that intended in standard, even if it does work - I'm not so sure anymore... I don't find any guidance...
cheers
Janis