Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8088

Re: Condition records for batch determination

$
0
0
Hi MK,
Let me ask your three points:
1- The priority is the sequence. This is clearly defined by the access number.
ME01.jpg
2- The priority is also defined by the sequence. ME01 has more priority than ME02, and ME02 has more priority than ME03.
As you can read in this article:
Batch determination access sequences have multiple condition tables (key combinations) assigned in a sequence of priority. This facility allows you to create data for many key combinations so that even if the search of batches fails on the first key combination condition the rest in the priority would help in search.
3- The difference are the business processes in which you apply the batch determination:

For Inventory management - MBC1 – Create, MBC2 – Change, MBC3 – Display

For production Order /Process order - COB1 – Create, COB2 – Change, COB3 – Display

For Sales and Distribution - VCH1 – Create, VCH2 – Change, VCH3 - Display

For Warehouse Management - LS51 – Create, LS52 – Change, LS53 – Display

So for example, if you want to setup the batch determination at the process order release, then you will maintain the conditions in COB1.
If you want to determine the batch at the delivery or sales order, then you will maintain your conditions using VCH1, etc.. etc..
Kind Regards,
Mariano

Viewing all articles
Browse latest Browse all 8088

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>