Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Introduction
There were two queries in the past, where the control on TECO of Order was sought, in GI related matters.
1. Prevent TECO if Components exist and Goods movement not done for an Order.
2. Prevent TECO if open Reservations are there.
These questions are a sort of FAQ, during repetitions of which I often fail to search my own previous replies
having solutions, due to the fact that the Titles have many variations. Due to this, to make my search easier and
for the purpose of members to find solutions without posting a discussion, I am trying to preserve the solutions
I worked out for those queries, which I always test and post.
Note:
As always, there can be opinions that we should be able to achieve this through user status route, . But what I
observed is that this is not achievable through this method. That too complex requirements in the context of
Operations and Components line items of an Order the user-exit/enhancement route does always work perfect.
Now let’s see the solution codes for the above 2 codes.
UNASSIGN: <fs_resb1> .
This code, checks the entries in the AUFM table for Goods movement against the current Order and stops
TECO if no entries are found. This takes care of the Delete line items also.
UNASSIGN: <fs_resb> .
This code, checks whether all Reservation items have been done GI or not. If a single one is left without GI or
without Deletion indicator, then it prevents the TECO to happen.
Note:
Any user-exit codes we get, should be fine-tuned to our requirements by specifying its limits (like confining it
to certain Order type or some other parameter) by enclosing the code into IF and ENDIF.
All user-exits function when they are assigned to a project created through CMOD.
It is obvious that we should text our work well in Dev servers to satisfaction before we adopt it.