LSMW method for transaction IW31 (Service Order)

Hi all,
I am looking for a way to create multiple Service Orders using LSMW, but no Recording.
Transaction would be IW31.
Can you give some tips please?
Thank you! Walter.

Hi Brenda, thanks for the confirmation you found in the notes!
Can you tell me how to use the BAPI for mass-upload / migration? I haven't done that before, but it looks to me that we won't use LMSW for that, but tr.code SE37, right?
I found out that the BAPI you mention belongs to Business Object BUS2088A, wich cannot be selected in the first LSMW-step.
So the idea is then to write an Abap-program which reads my input-file (which contains all the data to create the service-orders) and then call the BAPI several times to create the Service-Orders one by one. Am I right, or is there a standard way to use this BAPI for mass-upload?
Thanx again, Walter.

Similar Messages

LSMW method for transaction ME31K ( Create contract)

can anybody tell me in which method of LSMW i should use to create contract ( Tcode- ME31K). Is there any direct input method for this or i have to use BAPI_CONTRACT_CREATE?
please answer it in details...
Thnxx in advance..

In LSMW,
1st step Maintain Object Attributes. Here you can choose the kind of input method.
For your purpose you can choose Batch input recording and then go for Recording overview.
There you can do your recording for the tx.Similar to your BDC process.
Hope this helps to some extent!

Authorization for "Accept Quotation" Business Transaction in Service Order

Hello All,
I need of Authorization Control for doing "Accept Quotation" business transaction in Service Order.
Process goes as follows.
Service Order created with Planned cost components with DIP Profile
Service Quotation got created through DP80
Then, Accept Quotation will be done in Service Order
Release of Service Order
Execution, Billing, etc.,
Here, I want to control of doing "Accept Quotation" by only authorized people.
I couldn't find any suitable Authorization Object under I_VORG_ORD under field BETRVORG.
We can control that business transaction through User status. Is there any other standard object available to achieve this??
Hope I am clear in my query & looking forward your suggestions.
Thanks in advance.

Maheswaran KD
Sorry, but I can't check at this client as we are not using CS processes.
Try popping into debug mode using "/H" and put a break-point on "authority-check" before continuing.
The program should now stop at all authorisation checks. See if any of these are suitable.
If not, then you may need to use a user-exit or BADI.
PeteA

Delta update for Cube : 0CRM_PRI - Service Orders and Confirmations: Item

Dear experts,
For Cube : 0CRM_PRI - Service Orders and Confirmations: Item
Source data is from Two ODS
1. Confirmations (Item Data) : 0CRM_CNFI and
2. Service Orders: Item Data : 0CRM_PROI
I have done Init upload to this cube from both this ODS.
I am not getting delta option to this.
When I am trying update Delta after init from ODS message is No new deltas in DataStore object 0CRM_PROI for update. No delta option available . It is showing Initial and Full Update option only.
How i can initiate delta option for this Cube ? Please update us.
Thanks in advance.
Regards,

Hi,
you can use DTP's to laod data from ODS to cube .. it will take deltas ..
With a data transfer process, you can transfer data either in full extraction mode or in delta mode. In full mode, the entire dataset of the source is transferred to the target; in delta mode, only the data that was posted to the source since the last data transfer is transferred. The data transfer process controls delta handling and therefore allows you to fill several targets with different deltas from one source. With a data transfer process, you do not need to explicitly initialize the delta method as you do when copying data with an InfoPackage.
or you can create a sepeate Ip for delta apart form full and init .. that will laod delat data in cube ..
Regards,
shikha

User-exit for transaction co13: PP Order Cancel Confirmation

Hello!
Whether prompt, please,
exist what that user-exit for transaction co13: PP Order Cancel Confirmation?
Thanks,
Anton.

Hi Antonio,
Please check this all user exits (SMOD) available for CO13.
CONFPP01 - PP order conf.: Determine customer specific default values
CONFPP02 - PP order conf.: Customer specific input checks 1
CONFPP03 - PP order conf.: Cust. specific check after op. selection
CONFPP04 - PP order conf.: Customer specific input checks 2
CONFPP05 - PP order conf.: Customer specific enhancements when saving
CONFPP06 - PP Order Confirmations: Actual Data Transfer
CONFPP07 - Single Screen Entry: Inclusion of User-Defined Subscreens
CONFPS01 - PS confirmation: Determine customer specific default values
CONFPS02 - PS confirmation: Customer specific input checks 1
CONFPS03 - PS confirmation: Customer specific check after op. selection
CONFPS04 - PS confirmation: Customer specific input checks 2
CONFPS05 - PS confirmation: Customer specific enhancements when saving
CONF0001   - Enhancements in order confirmation
CONFPI01   -   Process order conf.: Calculate cust.specific default values
CONFPI02   -   Process order confirmation: Customer spec. input checks 1
CONFPI03   -   Process order conf.: Cust. spec. check after op. selection
CONFPI04   -   Process order conf.: Customer specific input checks 2
CONFPI05   -   Process order conf.: Cust. spec. enhancements when saving
CONFPI06   -   Process order confirmation: Actual data transfer
CONFPM01 - PM/SM order conf.: Determine cust. specific default values
CONFPM02 - PM/SM order confirmation: Customer specific input checks 1
CONFPM03 - PM/SM order conf.: Cust. spec. check after op. selection
CONFPM04 - PM/SM order conf.: Customer specific input check 2
CONFPM05 - PM/SM order conf.: Cust. specific enhancements when saving
Regards,
Ferry Lianto

Costing for Maintenance- and Service Orders

hi
Can any one tell me the Configuration steps for Costing for Maintenance- and Service Orders.
Kindly please guide me.
regards,
R.Ramakrishnaraj

Hi,
Please go through below mentioned threads.
Re: Activity Costing
Re: PM order costing.
Re: Planned cost not getting displayed in Maintenance Order
Re: Costs not appearing in service order
There are many threads available for Costing. Please search in the threads.
Regards,
Maheswaran.

Standard smartforms for SD-Notification, Service order, Rental agreement

Hello all,
Could anyone let me know if any standard SMARTFORMS
available for
Notification - SD
Service order - SD
Rental Agreements - SD
Reminder for order confirmation - MM
Goods issue - MM
Physical inventory slips - MM
Spare part labels - MM
Is there any SAPnotes available for this.
Awaiting your reply,
Thanks,
Balaji

Standard Smartforms
PO ---> /SMB40/MMPO_L
Request For Quotation ---> /SMB40/SDINQ_L
Invoice ---> /SMB40/SDINV_L
Delivery Note ---> /SMB40/SDDLN_L
Sales Quotation ---> /SMB40/SDQUO_L
/SMB40/SDPIK_L                 Picking List
/SMB40/SDSDA_L                 Scheduling Agreement
/SMB40/SDDLN_L                 Delivery Note
/SMB40/FIDUN_L                 ACC-FI-Dunning
/SMB40/MMCON_L                 Contract/Scheduleing Agreeme
/SMB40/MMDLS_L                 Delivery Schedule
/SMB40/MMGI1_L                 Goods Issue slip version 1
/SMB40/MMGI2_L                 Goods Issue slip version 2
/SMB40/MMGI3_L                 Goods Issue Slip version 3
/SMB40/MMGR1_L                 Goods receipt slip version 1
/SMB40/MMGR2_L                 Goods receipt slip version 2
/SMB40/MMGR3_L                 Goods receipt slip version 3
/SMB40/SDCSH_L                 Cash Sales

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

IW31 Service Order created with reference order,sold to party not populated

Hello
If one decides to create a new service order with IW31 but based on an old one using reference order field, not all data's are popullated to the new document:
It works for some data's like :
- operations
- components
It does not work for the following data's:
- service order description
- sold to party
- main workcenter
Does someone know if it is possible in the customizing to determine "copy rules" in order popullating values from the reference document to the new?
Is it a bug or a SAP standard behaviour?
Kind regards
Chris

Hello,
The behaviour you have described is correct - Description, partners, main work center are not copied from reference order. See note 197581.
-Paul

4.6C method for creating a Maintenance Order

Hi,
We have a requirement to create and update maintenance orders on a 4.6C system. The scenario is that we need to programmatically mimic what users can do in IW31 and IW32. The BAPI_ALM_ORDER_MAINTAIN function module is not available on this system (SAP delivered that BAPI in a later version.) We've looked at IBIP but it does not offer structures for order data. Using "call transaction" and BDC data structures directly seems to be an option but difficult to implement and prone to error.
What other options exist for creating/updating maintenance orders on a 4.6C system? Thanks in advance for any information or examples you can provide.
-Jason

Ok. I've actually figured out how this works.
I'll post what I've found out in case it helps anyone else.
The parameters seem to be: ( with my example data in brackets)
I_AUFNR order number
I_VAPLZ work center ( MAINT.)
I_VAWRK plant ( 0001)
I_PLNTY Task list type = ( A )
I_PLNNR Task list group ( 55)
I_PLNAL Task list group counter ( 1)
The problem I have is that this bapi is not released, and it is not remote enabled.
Are there any released BAPIs that would do the same thing?
Or would I need to write my own remote-enabled BAPI that calls this one, and then try to call my BAPI ( using .NET Connector ) ?
Thanks,
Derek

Screen exit for transaction IW31 for ref. object O150

Hi,
I need for find screen enhancement for trasaction iw31 in plant maintenance.
The requirement is to add 2 more fields (Functional location and Assembly) in the 'reference object' O150 on header tab. Currently the reference object has 2 fields and we want to add 2 more above mentioned fields.
Please help me, thanks
Sanjay Singh

HI
To search for a badi, go to se 24 display <b>class cl_exithandler.</b>
double click on method get_instance, get a break point on case statement.
execute and start the required transaction in new session.
look for variable <b>exit_name.</b> It would show the available badi's.
Please do reward if useful
Regards
Dinesh

User Exit / BADI for Transaction IW31 to create a POP-UP.

Hi,
I need to have a POP-UP Message in transaction IW31 on the press of ENTER. Could you give me the name of the EXIT or BADI which can be used for this purpose.

Hi!
In IW31/IW32, there is no user-exit/badi for pressing Enter. User-exits are attached to well determined event (enabling, closing, saving the order and so on).
If you wanted to solve it, it seems, you have to modify the standard COIH function group. Use SE80 transaction for it. The first dynpro is 3000.
Regards
Tamá

Purchase price for components in service orders

Dear Fellow SAPPERS,
I did not find any separate forums for service management nor did I find anything for plant maintenance. As a result I have to post it in this forum since SM/CS uses lot of settings from SD. If you do not find this relevant, please point to appropriate forum for my post.
Now the problem,
When users are entering components which are externally procured in the service order compoenent tab, the price is picking up automatically from the purchase inforecord. For some materials which are stocked and real materials we want it this way. But the client is also using generic materials like nuts, bolts, impellers etc where the purchase price is specific to the service order.
When the users are putting in a real price, the price from the purchase inforecord is overwriting the price the user entered. Then they need to reenter the price which if they forget, the purchase requisition gets a wrong price. We want to stop this overwriting of price from inforecord for certain materials.
How is this possible? We are exploring the function module CO_ZF_MAT_INFORECORD_READ where the price gets fixed from inforecord. Is modifying the funtion module the only way?
Thanks in advance for any help.
Andy.

Hello,
Its not that easy unfortunately. The users started complaining about this behavior many months after go live. Before that the indicator Info record update was already checked in the PO. Since these materials are generic with few materials, most of the info records are already created. Now when I delete the inforecords, I get an error message inside the service order that the inforecords are deleted. So I cannot go and delete the inforecords.
This needs to be done by a program. Anybody has experience modifying the function module CO_ZF_MAT_INFORECORD_READ by implicit enhancement?? Also any links explaining all the features / functionality of implicit enhancement.

ALE Configuration for Transactional Data (Purchase Order)

Dear Experts,
I want to configure ALE for Purchase Orders(Transactional Data).
For that:
I have done neccessary Condition Records at NACE with necessary Output Type Configuration. Configured Port and Partner Profile with Message Types: ORDERS and ORDECHG (as Outbound Parametrs) .Assigned those Message Types against defined Sender and the Receiver at Customer Distribution Model . Configured Port and Partner Profile at the Receiver System also.
Now I have 2 queries.
i) Is this much of ALE configuration is enough for Transactional Data for communication between 2 systems or I have to do something more?
ii) For Master Data we configure Change Pointer(we can see field assignments against Change Document Object at BD52 for Master Data Messaage Types) . Is it necessary to configure Change Pointer for Transactional Data or it will autometically handled by the system(field assignments cannot be seen against Change Document Objects at BD52 for Transactional Data Messaage Types)?
Regards
Arnab

Hi kumar,
what Alexander said is absolutely correct .
from your second question no master data distribution configuration is required for the transactional data distribution.
let us know once if you face any problems.
~linagnna

PReq for Components in Service Order

Hi,
I had created a Repair Order for a Product and via this Repair Order, system automatically created a Service Order (SM03)
I added a component (spare part) in the Service Order that has to be consumed for Service on the Product. Upon saving the Service Order, system is prompting "Should a PReq also be created for component xxxxxxxxx ?"
What setting / conditions in the System is enabling this prompt in the Service Order ?
Thanks for help.
Raj

Mr. Raj,
Check the itemcategory in the component tab of the Service Order, if the Item Category is N, then change it to L.
Praveen

LSMW method for transaction IW31 (Service Order)

Similar Messages

Maybe you are looking for