Operation Deletion Indicator In Work Order (Iw31)

Hi experts,
I want to create a checking on IW31 in this senario:
Task List A must be pair with Task List B..Task List A alone is not allowed.
I used user exit ZXWOCU07 to enter the checking and play around with data within internal table tafvgd_get.
My problem is in REL status: if user enter Task List A then enter task list B and save-its just fine.
But then user can use IW32 and delete Task B and system allowed.
How can I know on specific row (Task List B) that user is perform 'Delete' or 'Update'
as in debugging tafvgd_get-vbkz just update it to 'U'?
I need to perform the checking before it is save and I need deletion indicator to do that.
Kindly help.
Thank you

Hello Avanti,
I would recommend you to use user exit IWO10009. This user exit will work at the time of saving amaintenance order.
Write a code "if system status = DLFL,then check whether it is active or inactive" or vice versa, as per your requirement. You
can raise a error message if your condition is not satisfied. System will not allow the user to save the order unless your
condition is not satisfied.
Regards,
Vaibhav Mishra

Similar Messages

Removal of deletion indicator in Production order

Hi,
Can any one explain me how to remove the deletion indicator in production order.
thanks and regards
Murugesan

As I know we have delition flag status and delition flag in the control data tab page.
both are related, whenever you set the status as delition flag set, this indicator will come automatically, and visa versa. I am not sill clear which you are refering as delition indicator?
Is it some thing different from what I am talking about?
If so what is the significance of this indicator and why you are using this?
Form dlition inicator many of he fuctions can be blocked. Is there any function which can be blocked after delition indicator than delition flag indicator what I am refferring?

How is the object link populate into work order - IW31

Hello,
I am new in PM and am in the process of trying to picking up the concept.
Question:
When I create a maintenance order (IW31), how are all the relevant data being pull out and populate into the work order?
For example,
The maintenance plan includes functional area and equipment object, material objects, and task list object.
Next, you have the equipment master, which also includes the task list, and functional location.
Finally, you have the task list which includes the Maintenance BOM component.
Hence, when I create the PM order via IW31, how are all those object information pull out and import into the order? What is the sequence? I am confused on this.
Thanks
Daniel

Daniel,
When the work order is created from the maintenance plan it copies the maintenance item data into the order e.g. Floc, Equipment, Order Type, Main Work Centre, Priority, etc.
The operations for the order are determined from the task list assigned to the maintenance item dependent upon the rule governed by the maintenance plan type (performance, strategy,etc).
PeteA

Is there any way to put deletion indicator on sales order

Hi All
We are using MTO assembly order concept in our environment. Every sales order item will automatically create a production order. And there were thousands of productions orders which does not have any deletion indicator on them. So when I am running product costing jobs on these production orders, the jobs are running for ever. If I can put a deletion indicator on the production order then my jobs will run faster. To my knowledge, I cannot put the deletion indicator on the assembly order directly and it has to come from Sales order. I do not want to physically delete sales order-But I want to put some kind of deletion indicator on the sales order which will put a deletion indicator on the production order.Is ther any way of doing that?
Thnaks in adavnce for looking into this

Hi Michael
Does the rejection of a line item have any impact on any other scenarios after delivery doc and billing doc wass created?. My manager seems to be doubdtful abt this approach .... does all the companies follow this scenario?.
Note 308513 says-Deletion indicator should be kept for all the old production orders, but it does not say anything abt the assembly order.

How can I make settlement rule mandatory in create work order (IW31)

How can I make settlement rule mandatory in create workorder and saving without release.
I kanow we can make settlement rule mandatory upon Release order but here requirement is
Create work order (IW21) save without releasing that time settlement rule should default.

Hi,
1.If you want the settlement rule default then maintain account assignment data in technical object and when MO is created on that it would be copied into the settlement rule...
2. If you want to make those fields mandatory .... plz check up field selections in config , if you cannot find those then use SHD0 Transaction variant to make those fields mandatory.
3. Enter SHD0 , Enter IW31 in transaction and ZIW31 for transaction variant ..click create option and this takes you to IW31 initial screen , here enter required values of technical object etc and press enter and this gives you IW31 Initial scree screen variant , click continue and this takes you to inside screen and here enter required field values and on pressing enter gives you screen variant .. so you need to enter field values and check the flow of screen variants and on getting settlement rule screen variant select required option for the fields you need.
4. Finally you can save that in package created in SE80 for transporting to other client .., you can activate the variant in SHD0 -->Standard variants -->you can find activate option ..
regrds
pushpa

Error in Work order -IW31

Hello All,
We are facing one error while creating work order.
When we are creating work order from IH01 > Goto> Create order or directly creating from IW31 by putting PM03 in type , priority and equipment details then after release if we press save button then system says that invalid account group.
What can be reason for same.
Regards
Himanshu

Hi,
Are you facing this issue during Normal order creation with that functional location ?
Please check CC assignment to functional location and settlement rule applied while saving order.
Thanks
Riyaj

Setting of Deletion Indicator in purchase order

Dear friends,
Plz tell me how to set the deletion indicator in a purchase order.
thks

Hi
Just have to select the line item and under item overview you have delete button.
regrds
Yogesh

FM for Uploading Delivery address for Components for PM Work Order (IW31)

Can any one please help me out in finding any Function module or any other method for uploading the Delivery address for Components to SAP system in transaction IW31 for PM Work Order.

Hi
I am using text items (T Text item).Therefore, there will be no checking for those items form a MM prespective.
There is no error appear. The only thing is that i have status MANC (Mat.availability not checked) on my WO
I'm just trying to figure out if status should be removed some how, or if this is the normal behaviour.
Many thanks
Joana

Authorization check creating Work Orders (IW31)

Hello everyone,
We need to make an authorization check when creating a Work Order in transaction IW31.
That check is based on the field "Main work center for maintenance tasks"
No check apart from the plant associated to the work center is done, but the problem is that there exist different Work Centers associated to the same plant, and we need to restrict it.
Our authorization model considers the Cost Center associated to the Work Center, but the Cost Center is not checked in this IW31 when entering the Work Center.
We have also tried using the classification system, but despite activating authorization obejct C_KLAH_BKL, is neither checked.
(It is amazing the difference between the number of objects marked to be checked in SU24 for this IW31 and the objects really checked when looking at authorizations trace)
We know that Work Center field exit could be used, but we would prefer not to change ABAP code.
Could you please give us a hint about how we can restrict this field?
Thank you very much.
Best regards.
Jose Sanz.

Hi Jose,
You can look at the object C_ARPL_WRK,
if you work with this , i hope you would be able to find a solution for this situation.
Thanks,
Vijay

Badi for work orders (IW31)

Hi,
Can any one tell me a badi or exit for work order, transaction IW31. The exact problem is population of a field value by default on entering IW31.
Thanks
Deepti

Hi!
You can use the following code in any user-exits within IW31:
PERFORM caufv_upd_ih(saplcobh) USING caufvd_imp.
    CALL FUNCTION 'CO_VG_GET_HEADER'
         EXPORTING
              caufvd_imp = caufvd_imp.
This will update all the header level data, however it's not a very nice solution, calling directly the standard codes
Personally I prefer checking the necessary data before the order releasing (using exit IWO10002 - EXIT_SAPLCOIH_002), or before the docuemnt save (IWO10009 - EXIT_SAPLCOIH_009).
Regards
Tamá

ESTF Requisitions generated from Work Orders (IW31)

I am generating purchase requisitions from work orders via IW31. I can edit field selection key ESTF to open certain fields for editing in transaction ME52N.
However if I generate a service requisition the service line item fields are not available in field selection key ESTF. Where can I allow the service fields to be edited for requisitions generated from work orders. What field selection key should I update?
Any guidence or ideas would be greatly appreciated.

ML90 - IW31 controls what fields are available for change in the work order transaction IW31. It does not control what fields are available from ME52N. The issue face is that our maintenance staff are creating purchase requisitions from work orders. Purchasing then needs to be able to adjust the pricing on the service lines in the requisition, however since these originated from a work order the fields are unavailable for input.
We were able to get around this issue by editing field selection key ESTF in the requisition screen layout config. This works for material purchase requisitions but not services. I am looking for an extension of ESTF in transaction ML90 if that makes sense. Any guidence you could provide would be appreciated.

How is Standard Operation attachments copied to Work Order (Jobs)?

It seems the Job is linked to the Standard Op attachment, and as the Standard Op attachment is changed, it changes the attachement for previously Closed Jobs.
Is there a way to copy the attachement at the time of Work Order creation?

yes

Deletion indicator not working after user exit error

Hi Gurus,
I had one requirement in Purchase Requisition. If the number of items increase by 36 , there should be an error saying that maximum items reached but once that item is deleted that error should disappear.
I have written the coding in an Exit: EXIT_SAPLMEREQ_010.
And the coding is :
IF gs_eban-bsart = gcz902.
LOOP AT gt_eban INTO gs_eban
where loekz is initial.
LOOP AT gt_ebkn INTO gwa_ebkn WHERE banfn = gs_eban-banfn
and bnfpo IN r_bnfpo.
recherche division- ordre interne
LOOP AT ot_div into gwa_div WHERE ot = gwa_ebkn-aufnr AND div = gwa_ebkn-bnfpo.
ENDLOOP.
IF sy-subrc NE 0.
gwa_div-ot = gwa_ebkn-aufnr.
gwa_div-div = gwa_ebkn-bnfpo.
APPEND gwa_div TO ot_div.
ENDIF.
ENDLOOP.
ENDLOOP.
DESCRIBE TABLE ot_div LINES n.
IF n >= 37.
case sy-ucomm.
WHEN 'MESAVE'.
MESSAGE e111(zpfr) with n.
exit.
ENDCASE.
ENDIF.
ENDIF.
So now the exit is working fine......but when i go to delete that extra item it is not getting deleted , so while saving the information message comes that no data changed.
So ho wto delete that extra item.
Do anyone have reply....
thanks in advance.

Hello.
If you insert 37 lines you get your error message. But if you delete 1 row, you get error message again, right?
I think that's because you are not refreshing internal table ot_div. Shouldn't you refresh it before LOOP AT gt_eban INTO gs_eban?
Regards.
Valter Oliveira.

Error in BDC program which is creating Work Order IW31

Hi All,
I am getting an error - 532 - " Specify only one start time/date " when running bdc program for txn IW31 in back ground. I run the same program in the foreground.. there is no error.. but when I run in background.. I am experiencing the above error.
Thank for Ur time.
Cheers
Senthil

Hi,
Are you facing this issue during Normal order creation with that functional location ?
Please check CC assignment to functional location and settlement rule applied while saving order.
Thanks
Riyaj

BAPI for transaction IW31 (creating a work order)

Hi all,
I need to be able to create a work order ( IW31) using ABAP code and was wondering if any knew if there was a BAPI that should be used for this functionality.
Thanks in advance
Mart

hi,
You can use
BAPI_ALM_ORDER_MAINTAIN.
Have a look at the following documentation.
FU BAPI_ALM_ORDER_MAINTAIN
Text
Process Maintenance-/Service Order
Functionality
This Business Application Programming Interface (BAPI) is used for changing maintenance- or service orders and their lower-level objects. The following objects of an order can be processed (for restrictions, see the note at the end of the documentation):
Order header
Partner
User status
Order operations
Relationships
Components
Long texts for order header, operations, and components
Function
Calling up this BAPI once allows you to perform all the operations. For this the system supplies the function module with a method table containing the methods to be performed. The entries in the method table refer to data records in the optionally filled-out data tables. All the methods from the method table are performed. Alternatively, just lower- level objects from existing orders can be changed.
You can process the transferred data with the Business Add-In (BAdI) IBAPI_ALM_ORD_MODIFY to, for example, merge data from the external system with data from the R/3 system. The BAdI is called up as soon as the transferred data is converted into the internal format. The tests then take place after this.
Construction of Method Table
REFNUMBER Reference number for linking object methods - attributes
The reference number is the line of the database which contains the corresponding data. The data table is determined by the object type.
OBJECTTYPE Object category
The object category specifies which object from the order should be processed. The key words listed here are not language-dependent and must be transferred exactly as they are. The following objects exist:
HEADER Order header
PARTNER Partner data
USERSTATUS User status
OPERATION Operation data
RELATION Relationships
COMPONENT Components
TEXT Long texts
(empty) ,General BAPI functions (save)
METHOD Methods
The methods with which the data should be processed. The following functions exist:
CREATE Create objects
CHANGE Change objects
DELETE Delete objects
RELEASE Release
TECHNICALCOMPLETE Technically complete
ATPCHECK Availability check
CALCULATE Calculate
SCHEDULE Schedule
DELELTEDSEX Delete the status for external scheduling at operation level
SAVE Save all data
DIALOG Call-up dialog. See explanation below.
TRACE Write trace file in the specified file to the frontend
OBJECTKEY SAP external object key
This key is for assigning the lower-level objects correctly to the corresponding objects, as there is always just one key in the data table. The key must have the following structure:
1-12 Order number
When creating orders with internal number assignment, a reference number beginning with % must be entered here. The BAPI then returns this number and the number actually assigned.
13-16 Operation number
17-20 Sub-operation number
For relationships, the key is structured as follows:
1-12 ,Order number from
13-16 Operation number from
17-28 Order number to
29-32 Operation number to
The following methods are permissible for the individual objects:
HEADER:
CREATE, CHANGE, RELEASE, TECHNICALCOMPLETE, ATPCHECK, CALCUALTE, SCHEDULE
OPERATION
CREATE, CHANGE, DELETE, DELETEDSEX
PARTNER, RELATION, COMPONENT, USERSTATUS, TEXT:
CREATE, CHANGE, DELETE
(empty):
SAVE, DIALOG, TRACE
Data tables and update tables
The objects have one or more data tables. For some objects you can specify which of the fields specified in the structure should be changed. For this you must set the field in the corresponding table to X as in the data table. If no update-table is transferred, then only those fields are set that have a value that is not initial. This simplifies the transfer data. However, this means it is not possible to delete fields. If an update structure should only be specified for some data records, the table with the update fields must nonetheless have the same amount of lines as the data table. The empty lines are then treated as if no update structure was transferred. The objects "Partner", "User Status", and "Text" have no update tables. The whole data record is always copied here.
References
The objects use the field REFNUMBER from the method table to refer to the lines in the data table. Counting always begins with 1. In doing this, REFNUMBER also refers to the update table. However, in the method table there is a second reference to higher-level objects for lower-levels objects. The field OBJECTKEY must be filled with order number, operation number, and sub-operation number, as specified above. If lower-level objects of a newly-created order should be changed, then you must enter a temporary order number that must begin with %. Several orders can be numbered serially, for example, with %00000000001, %00000000002 ... .
The following objects have special treatment for REFNUMBER:
Partner
Texts
Partners have an order number in the data table. During processing of the method table, all those entries in the data table are processed which have an order number that is the same as that in the line to which the method refers. Thus, through just one entry in the method table, several partners can be changed.
Texts are composed of two tables. The first table (IT_TEXT) is made up of the header data of the text. Here you must specify the object and the first and last line of the text table (respectively inclusive, counting from 1). Through this, a line segment is specified in the text line table (IT_TEXT_LINES).
Peculiarities in processing
The BAPI processes the transferred methods in a particular sequence, which must not correspond to the sequence in the methods table.
Write trace file
Change user status time period 1
Delete objects (dependent first)
Create new objects
Change existing or newly-created objects
Change user status time period 2
Status change of order
Save data
The methods are performed such that lower-level objects can also be assigned to newly-created objects. For example, first the operations are created, and then the components. Long texts can also be created for the objects.
Components have an exceptional position. Components are created through the assignment to an operation, that is, using the "key" order/ operation (item number). However, as this is not the unique component key, you can only access the components to change them, delete them, or add long texts by using the reservation number/-item, which is only given after saving. This means that, for example, you cannot create a long text when you create the component.
User status changes can take place at two different time points. Time point 1 is before the object changes, time point 2 is after the object changes and before the status change of the system. These time points should be defined in the transfer table in the field CHANGE_EVENT. The field documentation contains the possible values.
The external scheduling is offered by the BAPI as a special function. THe BAPI can set the date field directly at the operation level, and select the operation with the status DSEX "Date set by external system". This status prevents any further scheduling of the operation, it keeps the transferred dates. For this, set the category 'X' in the restriction categories. When reading the operation, this category is also returned, independent of the category of restriction set in the dialog. To delete the status, you can call up the method DELETEDSEX for the object operation. The external scheduling cannot be influenced in the dialog. All changes to the scheduling restrictions in the dialog are saved as normal, but are not relevant for the scheduling as long as the status DSEX is active.
Every time the BAPI is called up, a SAVE or DIALOG method must be transferred. Normally, calling up a BAPI is seen as a transaction. All data that is changed in the BAPI should be saved to the database immediately. The BAPI checks whether a SAVE method exists, otherwise it terminates processing. A test run of the BAPI is composed of a normal call-up using the SAVE method and a subsequent BAPI_TRANSACTION_ROLLBACK. To call up the BAPI without the SAVE method, for example, to realize dialog transactions, the BAPI can be called up with the DIALOG method. This switches off the check for the SAVE method. The processor must then ensure that later either a SAVE method or a BAPI_TRANSACTION_ROLLBACK is called up.
A BAPI_TRANSACTION_COMMIT without SAVE method terminates processing in the update to ensure that no inconsistent data is written to the database. The processor who called up the BAPI does not receive any confirmation for the termination of the update in the target system. This logic is necessary as the order data was flagged for updating with BAPI_TRANSACTION_COMMIT through the SAVE method. However, the status information was already flagged for updating when the BAPI was called up. A BAPI_TRANSACTION_COMMIT without SAVE method then just saves the status information and would generate inconsistent orders, if the updating was not terminated.
Customer Enhancement
The BAdI IBAPI_ALM_ORD_MODIFY can be used to change the transferred data. The BAdI is called up after the conversion of the transfer structure into the structures used internally. Additional data can be transferred using the table EXTENSION_IN. Only then is the data checked.
Example
The following examples should clarify the use.
Creating an order
OBJECTKEY should be filled with a temporary key. The BAPI returns this key together with the assigned order number in the return table ET_NUMBERS . The order number in the HEADER table should also be filled with the number. For external number assignment, the external number should be specified. The update structure can be transferred if necessary.
Methods table
REFNUMBER OBJECTTYPE METHOD OBJECTKEY
1 HEADER CREATE %00000000001
IT_HEADER
ORDERID ORDER_TYPE PLANPLANT ...
%00000000001 PM01 1000 ...
Creating an order with operation and long text
Methods table
REFNUMBER OBJECTTYPE METHOD OBJECTKEY
1 HEADER CREATE %00000000001
1 OPERATION CREATE %00000000001
1 TEXT CREATE %000000000010010
IT_HEADER
ORDERID ORDER_TYPE PLANPLANT ...
%00000000001 PM01 1000 ...
IT_OPERATION
ACTIVITY SUB_ACTIVITY CONTROL_KEY WRK_CNTR ...
10 PM01 MECHANIC ...
IT_TEXT
ACTIVITY ... TEXTSTART TEXTEND
10 ... 1 2
IT_TEXT_LINES
TDFORMAT TDLINE
Longtext for operation 10, line 1
Line 2 of the long text
Notes
Using the BAPI to process the order data cannot support all the functions of the transaction. This applies in particular for the following functions:
Order header data
The object list cannot be processed.
Refurbishment orders are not supported.
The estimated costs cannot be processed - only the estimated overall costs of the order.
Notification data cannot be processed with the order BAPI. Even if the settings in Customizing are such that the orders and notifications can be maintained on one screen, no notification is created for the order.
Permits cannot be processed.
The order addresses cannot be processed.
Individual partner addresses cannot be maintained.
The settlement rule cannot be maintained.
Order functions
Printing the papers is not possible.
Locking and unlocking the order is not possible.
Accepting and rejecting quotations is not possible.
Business completion is not possible.
Flagging for deletion is not possible.
The log cannot be displayed.
User default values are not used.
The field selection is not checked.
The Customer Exits/BAdIs are not executed completely.
Joint ventures are not supported.
Funds Management is not supported.
Investment orders are not supported.
No integration of service products with task lists possible.
No integration of configurable service products possible.
Assignment of sales document items with service products in accordance with the aforementioned conditions.
Operation data
A change of the control key in the operation is not possible, if this leads to a change of the processing type (internal-/external processing)
User status change not possible.
Production resources and tools cannot be processed.
Service lines cannot be processed.
Task list integration is not supported.
Linking operations with object list is not supported.
Component data
User status change not possible.
BOM data cannot be processed.
The delivery address cannot be processed.
Further Information
See also the documentation for the individual transfer tables.
Parameters
IT_METHODS
IT_HEADER
IT_HEADER_UP
IT_HEADER_SRV
IT_HEADER_SRV_UP
IT_USERSTATUS
IT_PARTNER
IT_PARTNER_UP
IT_OPERATION
IT_OPERATION_UP
IT_RELATION
IT_RELATION_UP
IT_COMPONENT
IT_COMPONENT_UP
IT_TEXT
IT_TEXT_LINES
EXTENSION_IN
RETURN
ET_NUMBERS
Exceptions
Function Group
IBAPI_ALM_ORDER
~~Guduri

Operation Deletion Indicator In Work Order (Iw31)

Similar Messages

Maybe you are looking for