Whenever a Prodn order is created , release can be carried out automatically by defining in the production scheduling profile.. But this applies to all the operations in the order.
You need to cretae a trigger point and assign it to first operation . In the trigger point need to specify that when the order has created status release the first operation.
My suggestion was to create triggerpoint to operation n:o 2 - So when that one is created i released REL all the previous operations. BUT according to a collegue of mine I can't set that trigger point since the only statuses available for triggerpoints is REL CNF PCNF.
Do you have a way of using status CRTD as a base for trigger point... Please tell me how
If we try with status profile we get the other way around. That is when status of an operation changes then the status of the Status profile is changed. We want the other way around. When the status of the Order is CREATED then we want the status of the operation to be RELEASED.
Feels like complex configuration - Please let me know if are able to guide me through this problem..
Can you check whether Seletion profile functionality helps.
Selection profile
Ddefine selection profiles that you can use to specify status combinations for selecting objects (for example, orders or operations). A selection profile is especially useful if you select a large number of objects repeatedly according to the same selection conditions (for example, orders for printing shop papers, for collective release, or for creating order valuations).
This selection profile can be assigned to Trigger point under parameters.
Good news is that we solve our basic issue with trigger points to change status to REL for the operations we want to.
Bad news is that Triggerpoints does not work in background mode.
See error message from SAP when we get our Operation to be Confirmed via background interface to the entry of "Time Ticket".
-
Short Text
A confirmation function can only be executed in dialog mode
Diagnosis
An online step may be necessary with the individual confirmation functions (for example, exploding trigger points). If the confirmation is created in a background job (for example, PDC posting) or with a BAPI then no dialogue is possible with the SAP System.
System Response
The creation/deletion of such a confirmation is terminated as "incorrect".
-
I need Triggerpoints to be activated also during background job (BAPI). Then I would get the next operation or up until a trigger stop point to be released.
Do you have a work-around for this problem, please let me know..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.