Status Profile configuration

[shashi_vd5]

Hello All,

Can a status profile be configured in a sales order in a way that when applied it prevents demand from passing in to MRP.
I have acheived this to a certain extent by using a routine in the Transfer of requirement configuration, however it is having some unwanted negative effect.

Regards
Shashikant

[mike_ac]

No. Please do a search -- this question has been answered several times in the past. There are some good discussions on the topic, as well.

[shashi_vd5]

Hi Mike,


I have read the post mentioned in the below link ,

viewtopic.php?f=5&t=218638&hilit=Transfer+of+requirements

Like mentioned in the post, I am using the transfer of requirement routine to set the confirmed qty to zero in the schedule line when a particular status is applied. This works well, However when the status is removed, the system does not show me the Delivery proposal @ schedule line instantly which would happen when i remove a delivery block which is configured to block confirmations.

When i remove the status , my confirmed qty remain Zero until i save the order or Manually perform an availability check for the line.

How can i get the confirmed Qty to change / re-atp when the Status is removed / deactivated/

Regards
Shashikant

[mike_ac]

Status? Unless SAP has thrown out some new functionality in the last couple of years (it happens), status management isn't very helpful here.

To get a confirmation, you need to assign a schedule line category. If you are trying to do this in a save document exit, it is way after the availability check. You can try to debug the standard order and re-execute the order item checks, but it isn't a small task, and not reliable (upgrades tend to change internal coding). You can also look for a more effective user exit.

You're best off using a (manual) schedule line category, and changing it when you need to stop/start transfer of requirements.

[shashi_vd5]

Thx Mike,

I missed out mentioning the fact that the Fix date and Qty flag is defaulted from the config in our system design, when the sales order line is created the fix date and qty flag is activated by default, Hence that would be a reason why the Sales order is not performing an ATP in VA02. V_V2 is not used in this business.

I agree with your proposal on controlling the requirmeent transfer using the Schedule line category, However the problem is our sales order have lot of line item, 30 to 40 on an Avg....It could be very tedious for the user to change it manually.

I will try if something is possible in the ATP user exit.

Regards
Shashikant

[Sharpshooter]

I once accomplished this by setting the order probability (VBAP-AWAHR) to zero or 100% depending on the status in a userexit. If memory serves, the userexit was save_document_prepare in mv45afzz.

[mike_ac]

I once accomplished this by setting the order probability (VBAP-AWAHR) to zero or 100% depending on the status in a userexit. If memory serves, the userexit was save_document_prepare in mv45afzz.

This is a good idea. I'm surprised it works so late (save doc prepare), but the theory is spot on.

[Sharpshooter]

I once accomplished this by setting the order probability (VBAP-AWAHR) to zero or 100% depending on the status in a userexit. If memory serves, the userexit was save_document_prepare in mv45afzz.

This is a good idea. I'm surprised it works so late (save doc prepare), but the theory is spot on.

Found my notes....you're right about it "being late". To make it work, I had to run the following routines whenever the field was changed:

Code: Select all

loop at xvbap.
* Do your thing here
    modify xvbap.
    perform xvbap_lesen_direkt(sapfv45p) using xvbap-posnr 
                                                                           svbap-tabix. 
    perform vbap_bearbeiten_vorbereiten(sapfv45p).         
    perform vbap_bearbeiten(sapfv45p).
    perform vbap_bearbeiten_ende(sapfv45p).

endloop.


There might be a better place to put it to avoid the additional processing!

[mike_ac]

I seem to recall that the way status management runs, you have to call some SAP routines at one point or another. It just isn't all that integrated until SAP specifically codes for a status-driven event.

But, you wouldn't necessarily have to use status management for your idea to work. You might be able to do it in an order runtime exit, if you could get the exit to trigger consistently.

[Sharpshooter]

Right....in this case, the client was already using user statuses and this fit right in to that process. One nice thing about the way it worked is that the user statuses can be authorisation controlled natively in SAP making it easy to control which users could release a requirement for MRP.

[shashi_vd5]

Thx Mike and Dave for your suggestions, Can you explain in little detail how the order probability field was used to prevent demand from flowing to MRP. As far as i undersatnd this is a Statistical field....what am i missing ?

[Sharpshooter]

It is definitely NOT (only) statistical. The order quantity is multiplied by the probability to determine the requirement for MRP (for schedule lines relevant for MRP). The field is only available for input in quotations (not sales orders) in the standard, so you would have to configure an MRP-relevant schedule line category for quotations in order to see its effect on the MRP requirements there.

[shashi_vd5]

Ok. Thx for the input, I understand it now, did not know about this functionality.