Who's On?

	Membership:
	Latest: Lauren Beeker
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5222

	People Online:
	Visitors: 91
	Members: 0
	Total: 91

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chris Martin	825

Remove items PO135

4 Replies

1 Subscribed to this topic

44 Subscribed to this forum

Sort:

Author

Messages

rhorn01

Basic Member

Posts: 9

New Poster

9/26/2017 8:04 PM

We are fairly new to Lawson/Infor . . . in reviewing the latest PO135 we have identified items that have been paid outside of the PO and items that need to be removed for other reasons. What is the best way to remove these items from the PO135? Do we manually close the PO? I have seen some references to the MA180, but we had one consultant advise us not to run that report. Any specific information/screen names would be helpful. Any best practices in monitoring this report? Thanks!

Jeremy

Veteran Member

Posts: 129

New Poster

11/10/2017 6:14 PM

Have you tried cancel remaining on those PO's?

Kat V

Veteran Member

Posts: 1020

New Poster

Engaged Reader

Avid Reader

11/10/2017 7:19 PM

We do not back out the receipt or use MA180 as of v10. We go to PO20 and use FC V(Archive) on the PO line. This archives the receipt off the PO135/RNI and closes the PO line. This allows us to see the received quantity when we go back and look at usage.

rhorn01

Basic Member

Posts: 9

New Poster

2/8/2018 3:54 PM

Thanks for the info. We've implemented a process similar to what you've described Kat. How do you approach situation's where the archived PO line needs to be open/was archived accidentally? We aren't able to open a line in a subsequent month. Thanks!

Kat V

Veteran Member

Posts: 1020

New Poster

Engaged Reader

Avid Reader

2/8/2018 8:42 PM

We haven't found a way to process either. We process the invoice as a non-PO and comment on the PO or we add a new line. We prefer non-PO because it throws off our usage to add a line. *knock on wood* After the initial round of making the users provide documentation, scan and attach, and logging how many discrepancies they caused, the issue doesn't arise that frequently for us.