(1) We suggest you to look at PO -> Processing -> Warehouse Receiving Process.  Advised if that will work for you. Warehouse Receiving Import is designed to have an easier user interface than legacy receiving;  (2) If you can use warehouse receiving process, then you can also look at PO -> Utility -> Warehouse Recv Import.

Please advise if warehouse receiving does not work for you and why. Thank you

You don't need to email the report when running defer processing.  There maybe some miss understanding here.  Can you verify the defer processing?  if the email option is turned on, you can simply turn it off.

Netcellent made a decision long time ago that we will phase out real-time inventory transaction processing in favor of batch. But we still keep the real-time method for backward compatibility. Therefore, we had been advising our users to switch from real-time mode to batch mode inventory transaction processing. Same principle applies to PO receiving. Over the years, all new features improvement are added to the batch mode processing only. For this reason, this suggestion does not fit our direction.

I think we had made some changes on AP credit memo. Specifically, we allow AP credit memo to use multiple times and can be used as the “Deposit” purpose. See the following KB article:
https://support.elliott.com/knowledgebase/articles/1965881-feature-support-ap-partial-payment-for-negative

Will you discus with Roger. If you still think Credit memo will not do it and Roger agree with you, then we can discuss further.

Edward M. Kwang
Netcellent System, Inc.

The desired feature can already be accomplished with the following procedure: (1) Go to Global Setup → Dist → I/M Global Control, Screen 2, change flag “17. Show All Loc When Drill To Stock Status Inq” to “Y”; (2) In order entry, line item scree, after entering the item number, user can press F3 to drill down to stock status inquiry.

This function should be handled as “Message Box” feature in the “Event” which Elliott already support.

We already have such a feature. Please speak with our support if you need more information.

We already have such a feature. Please call to discuss.

This change is not easily doable at this moment. Base on the current structure, we can accommodate 99 fields and they are all used up. See attached screen.

This is a subject we can re-visit in the future. We may use Report Desk as a basis to replace current invoice form setup.

I believe INV/DOC# is already required if you turn on PO Invoice Processing feature. We have to if you want to use that feature. We have to understand your point of view on why it is necessary to allow blank instead of just enter anything to by pass. Does it mean you don’t have either INV/DOC# most of the time? Does it means you don’t really use PO Invoice Processing feature? If that is the case, you should not turn on PO Invoice Processing feature in the first place.

There are global setup flags that can already accomplish this purpose. In Global Setup → Dist → I/M Global Control, screen 4, flag 1-3. If you set them to “Y”, then it will do exactly the same.

This issue will be addressed in Elliott v9. We can’t address this issue now with the current release

This requires a database change. This request should be made in the comment section under the Elliott V9 Changes Summary and Detail posting.

The quantity field in these tables is the quantity per parent field. This type of change would affect more than the three tables that are listed in this request. An enlargement to the quantity per parent field would affect the Product Structure file (BMPRSTR) as well as all of the corresponding production tables, engineering change tables, ATP, order invoice history, etc.

Woody, can you provide an example of where you require more than 9999 components per parent?

This request has been declined per the submitter’s request.

It would seems this request break the Elliott convention. That is if a user hit ESC key before the last screen, then the screen is cleared and nothing will be saved.

This is not easily implementable. Reports are generally run for a range of items, customers, etc. This concept will not work for most cases.

Database changes required. This project can be reviewed for V9. Please add comment to V9 database changes so this will be reviewed for V9 changes.

This is V9 project due to database changes required. Please add comment to V9 link so it will be reviewed with V9 project.

Lot Items should be reviewed for V9 because database changes should take place to support the feature better. Please add your ideas of lot support to V9 link so this can be reviewed for V9 project.

In many situations, the purpose of the pre-authorization is ensure the credit card is valid so it can be used for future charge. Use the $0 pre-authorization will ensure the transaction does not show up on card owner’s side as a pending transaction. This may be desirable since the goods is not shipped yet.

If we default pre-authorization to order amount, then (1) Are we talking about qty-to-ship amount, or total order amount base on quantity order? (2) Do we have all the freight, misc. charge and sales tax figured out on the order. This can be a complicated subject with no good answer.

Conclusion, default pre-authorization amount to $0 create no harm. So we think that is a good default position to take in this case.