Do you know what version of QAD you are running?

We are on 2014 SE version 2.9.6.42.

So in the actual schedule, do you have anything in the Std Pack Qty?  Also remember that it also uses the order multiple set in 1.4.17, so make sure that is also set to zero.  This can cause the system to bucket quantities thus giving you unexpected results.  Also while you are in 7.3.13 checking the std pack also check what you have for the fields Req Ship DAYS, WEEKS and MONTHS.  I usually set these to zero so that the schedule reflects the customers requirements and usually if they are sending you a planning schedule it would be more than likely a monthly forecast anyway.

In 7.3.13 all the req sched days/weeks/months are set to 0.  As well as fab/raw auth days.  Std Pack qty is set to 1.  Plan/Ship SDP codes are set to "null".  Now for 1.4.7/17 (both are the same) Order qty, safety stock, all lead times, min/max order, and order mult is all set to 0.

Here is a snippet of how the schedule is getting re-bucketed.  You will notice that I'm using SDP of "07" (first of the month) since the day in each month is the first.  No matter the SDP the split happens.



Here you see it getting split:

Could you send me a screenshot of 1.4.17 for this part 

I also forgot to mention that this only affects our 7.5.1 Planning schedules. 

This is really interesting.  I also see that you do not use MRP for this part.  It is somehow splitting the quantity but it is not making it weekly it is making it as 4 orders on the same day.  do you have anything in the std pack quantity field on 7.3.13?

I want to apologize, that snap was me testing "07" SDP code.  Which the only difference is the dates.  Blank SDP code gives me 4 different dates and the 07 is forcing the date to be the first of the month.  Either way it is still splitting it into 4 seperate buckets.  

The standard qty in 7.3.13 is 1.

Here is a snap with a blank SDP code:

I have not seen this before.  So you did send me 1.4.17 didn't you, not 1.4.7?  The way you had it set up looks more like the settings for 1.4.7 when you use multiple sites to ensure MRP only runs in the sites you want based on 1.4.17.
Could you try changing the quantity to 200 and see if it still splits it into 4.  If it makes it as 8 @ 25 then there is a multiple type issue.  If it splits it in to 4 @ 50 then it is a schedule issue

That was a snap of our 1.4.17.  Which mimics our 1.4.7.   Here is a snap with the qty changes:

So something is causing it to split the order into 4 regardless of size.  Do you have anything set up in 7.3.3?
Sorry I am running out of ideas !

Yes.  It seems to always split the planned monthly order at the beginning regardless of SDP code.  Which causes issues when trying to use netting logic 3 or 4. 
No we don't use customer order periods.  I did try to add a monthly to see if there was any affect.  Doesn't seem to have an affect on it.

Does this happen to all parts?  Or is this an isolated incident?

This happens to all parts. 

In my current role I do not have access to a QAD DB to check further.  If you are able to do a screenshare we can go through each screen to see if there is someting else we are missing.  If you want to chat my email is [email protected]  I am no longer a consultant but am more than happy to try to help

With more digging.  I found in 2011 QAD talked about this.  Here is what I found.

Yes, but I thought that logic only applied if you were using the Req Sched Weeks field in the Order but you said that you have all of these set to zero

That logic is running in conjunction with SDP which is the first step RSS Update goes through.   The Req Sched Weeks is final step RSS Update goes through.  Which your correct I have all 3 (D/W/M) set to 0.  
Now I've tried to run a schedule with only "M" intervals and It still splits it into weekly buckets.  The note above says it only splits if weekly intervals are present with monthly intervals.  I'm still not sure how to prevent
the split.  

Final suggestion.  do you know if they have made any modifications to this or any of the other programs that support it.

So far that has been the only thing that I've found.  If I happend to find more later, I'll make sure to post it. 

Hi there, 

Jumping in late on this thread, have you tried running the Selective Req Ship Schedule Update, 7.5.6, and then reviewing the steps in the output to see exactly what is happening at each stage?

The detailed output of this program is often helpful in determining why the result looks the way it does.

John