Purchase Reqs created through work orders

Currently when I attach a non-stock item into a work order it create a purchase req. The purchase req is automatically released, or is released when the work order is. The problem is that we have a release strategy that we must follow here at my company. When the Reg is automatically release it does not follow this strategy.
Is there a way that i could turn off this functionality, and have those req follow our standard release strategy.

Hello!
If you don't want to convert PR into PO, then why you are creating it. There can be two cases:
1. You want to create PR but don't want the material right now. In that case change the delivery date.
2. You don't want to do anything now. You want material after 6 months, only you want is to create a maintenanc eorder. In
that case you can enter the material nad service on ly at the time of requirement.
You can talk to MM consultant also you can put control this by release strategy also.
Is there any other case that you are facing. Please discuss.
- Vaibhav Mishra

Similar Messages

Problem while Creating Service order through Work Order

Hi Gurus,
I have a problem While creating Service order (me21n) through - Work order it contains service requisitions.
So that means they carry information such as G/L and work order number while entering the requistion no in PO Creation Screen (me21n) which automatically should be picked from the work order refference.
But problem here is the service items and all other are assigned to PO except the Account Assingnment tab which is GL Account and Work Order No and Cost center..
Can anyone explain me this?
Is this something that one can explain?
Regards,
Murugesh R
Rewards for value replies.

Closed..

When Creating a Work Order Import Standard Operations

A client is requesting the following functionality when creating a Work Order: Create the first nine operations with different work centers and number operations 0001 u2013 0009. For operation ten continue numbering with 0010 and increase by 10, ie, 0020, 0030, etcu2026 . And operation 0010 would default header data.
Can this be accomplished through standards configuration or would this entail a user exit?
Thanks in advance!!
JAM

It can be possible, depending on how you create the Work Order. If these operations are used often and are in a task list, you can create a work order and import the task list operations by using the menu "extras -> task List selections" inside the work order. If it is part of a preventative maintenance plan, you can configure that your task list is automatically copied to the notification/work order when generated by your maintenance plan. Of course in the task list you could save all the increments and work centers as you want. But this would never be a dynamic check to your header data, it would only be as accurate as your task list.

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

Customization for create 2 Work orders for different vendors against 1 PR

Hi,
What are the customization settings to create 2 work orders for 2 different vendors against 1 PR with half-half quantity?

thank you Mario.
Actuly its infrastructure cmpany & user wants create Purchase order(service work order) for two different vendors with reference to single PR with alocating 60% quantity to 1st vendor & remaining 40% to another vendor.
user allready created Po for 1st vendor (60% Quantity).
Now system showing error " Quantity is allready full for reference PR"
I want to know what is the procedue to solve this issue & customization.

Create a work order using the BAPI for IW31

Hi,
      I want to create a work order using the BAPI for IW31 tr. can any one help me with the program description.
Full points will be awarded for the useful answers.
Thanks and regards,
Sunil

hi,
first use fm "bapi_po_create".
then use fm "BAPI_ACC_GL_POSTING_POST"
The demo environment was made with real business scenario in mind, but following subjects need to be addressed in a live implementation:
     No exceptions and error handling is implemented, except the order rejection (e.g. partly delivery);
     In Navision both XML Ports and the XML DOM has been used to integrate with SAP XI, because XML ports has some drawbacks regarding to Namespaces in XML Documents (mandatory in SAP XI);
     A minimum of SAP and Navision customization is required to implement this solution. (e.g. user exit in SAP, Navision XML DOM).

How to avoid purchase req and stock transport order to take part in MRP.

Please suggest how to avoid purchase req and stock transport order to take part in MRP.

hi,
check the settings for the MRP type...there you need to show which doc will be taken into considerations...
SPRO >> MM >> CBP...
Under CBP check for the MRP settings where it is placed(check under master data settings)...and check for the indicator for PR's and STO's release orders under tab "Additional external req. in the reorder point planning"..
Regards
Priyanka.P

Purchase requisition created through plant maintenance order

Hi Dear Experts,
Is there report where i can see purchase requsitions (thats are created from PM order) with PM order number?
Regards,
Aktolga

hi
you can check in IW37N, IWBK
regards
thyagarajan

Updating PO confirmation and ASN through Work Order Confirmation

Hi,
We implemented PO collaboration and Supplier is doing PO Delivery confirmation and ASN.Now we are implementing Work Order Collaboration and system created Work Order with reference to Purchase order.
I want to know whether PO confirmation and ASN date gets copied from Work order dates(after doing confrimation for phase Transport).
I want to know what setting we need to do as presently it is not getting copied to Work order. And I want to know how it updates ECC confirmation tab for Purchase Order.
Please do the needful
Regards
Raghavendra Pai

Hi Raghavendra
The above validation check will prevent supplier confirming purchase order request lines in PO details screen, so only supplier can confirm through WO confirmations, i.e by accepting the work order request lines in delivery overview, adapt the work order
This will make the work status as CIAG from CINE, in negotiation to in agreement
Then you can publish the work order, this will copy the confirmed data from the work order as identical request data and confirmation data to the purchase order. this data will be picked by ROC_Out and updates the po data in backend
Please check whether ROC_out is available in customizing
SPRO-SNC-BASIC SETTINGS-PROCESSING INBOUND & OUTBOUND-PROCESS TYPES OUTBOUND MESSAGES
ASSIGN OUTBOUND MESSAGES TO DEFAULT PROCESS TYPES
REPLORDC_O ASSIGNED TO ICH SUPPLIER COLLABORATION
Still if does not trigger, kindlly check the log slg1
it could be problem with ODM's ,POS etc
Best Regards
vinod

Purchase Requisition created from Maintenance Order can not deleted

Hi Gurus,
I've create a Maintenance Order for External Service (Control Key: PM02) and Purchase Requisition already created related to this Maintenance Order.
But when I want to cancel/delete the Purchase Requisition, there is error message "This item is only deletable via the associated production order". So II can not delete the PR.
Any solution for this problem ?
Regards,
Tri W

Hi,
If the PR has not been approved and no PO has been created yet, you have to delete the external service operation (PM02) in the work order. This should delete the Pruchase Requisitions.
Regards,
Joey

Creating new work order - error on %001

Hi all,
Creating a new work order from the SAP Work Manager 6.0 application should be a standard functionality,
However, on the system of our client, this goes wrong.
Upon creating a new work order, we get the error 'Enter a numerical operation number'.
New objects get an ID that starts with 'LOCAL_xx:xx:xx', which is converted to %001.
SAP should recognize this and convert this automatically to 0010, 0020, ...
how come this does not happen?
it works fine on our SAP system, our customer's system gives an error.
Kind regards,
Judith

Have you done any enhancement to standard product "specifically create method of Work Order Class handler" . or the standard product functionality itself is not working ?
I don't see any reason why it works in your system but not in customer system. Try to put break point in create method of Work order class handler and check what values are passed for operation number before invoking Work Order create BAPI.
Infact Work Manager product converts local numbers to incremental sequential numbers before invoking create BAPI for Work Order.
BR,
Manju - SAP CEG UX/Mobile

Purchase req release through workflow

Hi all,
         i am under the process of releasing purchase req in workflow its a overall release there are two business objects for that one is bus2009 and the other is 2105 actually 2105 is for overall release but there are no attributes for that particular object if i need to add any value as expression in my mail do i need to create my own attribute or is there any other way to handle this.....
Thanks

The required value that is required for Release is Release Code. If you are using Standard Wflow then this is passed along with event only you have to make sure you have proper configuration in SPRO. The PR number gets passed automatically thu event. You can make use of Workflow Template WS00000038.
Any custom stuff you can code in Attribute but in that case you have to create a subtype of standard Business object and then code in it and then delegate it. You can delegate by
SWO1->Give Business Object Name->Settings->Delegate
Check this link for programming related to attributes
http://help.sap.com/saphelp_47x200/helpdata/en/8c/1923d1932b11d2a5ea0060087a79ea/frameset.htm
<b>Reward points only if useful</b>
Message was edited by:
        Arghadip Kar
Message was edited by:
        Arghadip Kar

Deletion Purchase requisition created by sales orders

Hi gurus,
in my SAP system there are purchase requisition created by schedule line from sales orders. For different reasons the sales orders were deliveried and billed with stock free and not with customer stock.
When I try delete de purchase requisition, because the sales order is completed, the system alarms a message that is not posible to delete in purchase requisition else in sales order. But the sales order is completed and we don't touch it.
Any idea to delete this purchase requisitions?
Thank you, I will revvard all answers..

Hi ,
We can not delete the purchase requisition if there is any subsequesnt documents created against this.
If you want to delete the same then reverse the delivery then delete the delivery and then delete the purchase requisition by using the guide lines given in below path.
www.passhe.edu/.../ME52N%20-%20Delete%20a%20Purchase%20Requisition.pdf
Hope it helps.
Regards,
Pasapula.

Creating a Work Order List with a BLS Transaction

I'm trying to create a list of work orders at a specific plant with a BLS transaction. I'm running 4.6c. I'm having trouble finding a BAPI that I can use for this. The BAPI list in BAPI Explorer seems rather abbreviated when it comes to plant maintenance functions. Any ideas?

I did find one BAPI that looked promising 'BBP_PMORDER_GET_LIST' but unlike other BAPI's that had an INPUT section and an OUTPUT section, this one just had a TABLES section (and I couldn't find any documentation with it)
What is involved in creating a custom BAPI?
(We'll be on ERP2005 next spring so these 4.6c issues are temporary.)
I appreciate your help with this.

Movement type 262 when creating a work order (tx IW31)

Hi experts!!!!!
I need to cover the following scenario:
*sometimes, when the client carries out a work, they recover one item. Ideally they want to take into consideration this item as well from a point of view of costs, which means that in order to carry our the work some items and labour will be used and it will be considered as a cost but the item recovered will be considered as less cost (profit). In customizing (plant maitenance -->Maitenance and service orders --> General data -->define movement types for material reservations) that it is possible to customize the movement type to be used in case of reservations (goods issues and cancellation of goods issues). I have checked that if I change the customizing and I put 262 instead of 261, the system behaves as desired. The thing is that this affects to all the components and this is not correct. Therefore, from the work order (IW32 or IW31) I have tried to change the movement type manually, but I found that the field movement type (at component level for items L, field RESBD-BWART) is grey and it can not be changed.
Therefore, my question is:
*how to customize field RESBD-BWART so that I can change whenever I create or change a work order
*which is the meaning of having cancellation of goods issue in the customizing if then I only can use movement 261.
On the other hand, I have checked the functionality "refurbishment" but I doesn't fit because we have to use valuation type and this is not desired....
Best regards

Hi,
The materials that you are entering in the component tab are "Planned" materials that you may use during the execution of the order. In your case i don't see the necessity to enter it here, You could directly do a Return goods issue against the order using movement type 262, for that specific material.This should solve your needs.
Regards
Narasimhan

Purchase Reqs created through work orders

Similar Messages

Maybe you are looking for