Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from CWK on Feb 21 at 9:15 AM You should not get such poor performance from COHV, but it would be helpful to understand just how you are employing this transaction.
I assume you are using Mass Processing function Close (230). Have you chosen Execute Function = Execute Immediately or Execute in Background?
For a large volume of changes I would suggest Save Log = "From Warning, Error, or Termination Message"
Are you running COHV wide-open? That is, without specifying any Selection parameters. I wouldn't recommend this.
Also, any time you are going to act on a large number of orders with COHV, it is best to test what you are going to do in a development or quality testing environment of some kind - not in Production.
We have, on rare occasions, used COHV to do mass changes to 10's of thousands of orders. We have always, however, entered selection criteria that limited any given execution of COHV to four or five thousand orders. It's okay to run multiple COHV sessions (just try to make sure you don't overlap orders in your selection criteria).
Good luck,
Carl
| | | ---------------Original Message---------------
From: Pugazhendi Subramani
Sent: Thursday, February 16, 2017 5:11 AM
Subject: Production Order CLSD Status
I have 450000 production orders in TECO status. I want to set the CLSD status for those orders by using mass t code COHV. But in this program only four orders completed per hour by background. I want to speed up my activity. Please suggest to do the same.
Regards,
S . Pugazhendi. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
