Order deletion process

Considering COO2 and marking the order for deletion is the standard deletion process, i would like to know what are the effects of this transaction. How do we reconcile the materials to the WH ( if lets say, production has ensued in the WH and some raw materials were already used up )

dear,
please note that when you delete the order with delition flag, then system will check internally and give error if there is any open reservation, or WM TR/TO.
Hence before deliting the order you need to delete all the associated documents and then only you can delete the order.
Hence reconcellation happens before delition
I hope you got it, else come back with you clear explanation so that we can help you.

Similar Messages

Change material code in process order or delete process order

Hi experts,
While creating a process order in COR1 transaction code, wrong material code was entered.
Can we change the material code in process order. If not, what is the complete procedure to cancel or delete the process order.
Request you to revert.
Thanks in Advance.
Regards,
Farha.

Dear ,
One the Process Order has been created with any material either it is wrong code or correct code , it can not be deleted .If it wrong code , then do not perfom goods Issue -MIGO-261 or through Backflash and also operation confirmation etc .
If Goods Issue , Confirmation happend then you need to reverse those txn once again .
In that case the best oiption will be goto COR2-Enter the Process Order -Select Process Order from Header -Restrict Processing -Choose Technically Complete .
Now , once you did TECO , then there will not be any farther txanationl posting like Goods Issue , confirmation will not be possible .Likewise , you can also Lock or make set CLOSE from COR2 in case there is no WIP , Variance .
Hope this is clear
Regards
JH

How to delete process order

Hi Guru's,
I have created a processorder in T-code COR1..now i want to cancel the confirmed process order..plz tell me the process.
Thanks & regards
cherukuri

Cherukuri,
Deleting a process order has multiple steps... I would suggest you to just set "TECO" and "CLSD" status in the change mode of the order. This would prevent any further processing of the order in terms of confirmation, goods movment and costs. From menu bar
You need to follow the steps below for archiving and deleting process order,
1. Use program "PRARCHP1" to set deletion flag (Can be reset). The prerequiste i would suggest is to create a selection profile to select orders with status "CLSD"
2. Use program "PRARCHP1" to set deletion indicator (Cannot be revoked)
3. Use program "PRARCHA1" to archive (Already basis should have setup the database link for storing)
4. use program "PRARCHD1" to delete and remove the data from the R/3 system.
Regards,
Prasobh

Can we delete production order or Process Order

1.Can we delete production order or Process Order
2. Significance of TECO
3. How we can do Goods Reciept apart from production scheduling profile

Dear,
Delete production order check this link,
http://www.sap-img.com/production/how-to-delete-old-production-orders.htm
Go to CO02- Change production orderin menu choose-Functions--Restrict Processing-Technically Complete
Teco will close the Production order from Logistic point of view , reservation get deleted, capacity requirement also get deleted.
Auto GR can possible through control key with mark as auto GR in work center.
Regards,
R.Brahmankar

Process Order Deletation Flag

Dear All,
I have issue regarding Process Order Deletion Flag
I created a Process Order and for that phase confirmation and goods movement done . but some how i have to reverse it so i cancell Phase confirmation and goods issue through transaction CO14 and also discard the control recipe
Now i am going for process order deletion flag Active but system is giving me a Error like
"Unprocessed future change recs for order 1100044297 prevent del. flag/completion
Message no. CO688
Diagnosis
There are still future change records or error records to be processed from the confirmation for the confirmation processes in order 1100044297. Possible confirmation processes are:
Automatic goods receipt
Backflushing
Calculation of actual costs
Data transfer to HR
System Response
You are not meant to set the deletion flag/'completed' status for orders with future change records that have not been processed.
Procedure
You should process the open future change records using
Predefined confimration process or
The CORUPROC program, by dispatching it in Customizing in a background job (dispatch background jobs: dispatching processes).
Check if incorrect goods movements or incorrect actual cost calculations exist for the order, and reprocess these if necessary:
Reprocessing incorrect goods movements
Reprocessing incorrect actual cost calculations"
and Order current status is like below
"TECO CRAB PRC BASC BCRQ GMPS MANC PIGN"
So pls guide me.
Regards,
Murari Shah

Hi,
Pl. check in COGI whether any erroratic goods movements are pending for posting for your process order.
Even order status mentioned by you shows that DLV status is missing so there may be errors related to GR for the order which you can find in COGI.
Clear COGI records & then try.
If problem still persists, pls revert.
Regards,
Tejas

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

PPDS Order Deletion

Hi All,
Is there a method to perform Order No. wise PPDS order deletion.As the standard report /sapapo/delete_pp_order does not support order wise processing. Couldnt find any BAPI for the same either.
Thanks
Renjith

You are right - RLCdelete can not be used for PPDS order deletion (after 4.1 I think - before it was possible).
You can use this BAPI however:
BAPI_POSRVAPS_DELMULTI
Best regards,
Søren

PO-item     block delete process

Hi all,
is possible to annul the deletion process of an item in purchase order ?
In other word, when the user press delete button, the system go in exit MM06E005
or in BADI ME_PROCESS_PO_CUST:    inside this exit or BADI, exist a way to cancel the delete process ?
I found only           CALL METHOD im_item->invalidate( ).
in IF_EX_ME_PROCESS_PO_CUST~PROCESS_ITEM, but this is not correct beaucose I invalidated the item and not annulled the delete process !!!
Any idea ???

not possible ?

Order of processing

Hi all,
I am facing a problem while trying to execute a multi-stage mapping. As an example consider a mapping in which the data from a joiner operator is inserted into a table A. This data is then passed to a procedure P which applies some business logic and then inserts into table B which is further processed and output is written to a flat file via a set operator. I am finding that the insertion into table B is happening after generation of the flat file. Insertion into table A is happening at the correct point in time.
Is it possible to manually set the order of processing of such a multi stage mapping to get OWB to process the mapping in the correct sequence.
Pls. suggest a workaround in case the above is not possible.
Thanks in advance.
Regards,
Amit.

Not sure what OWB version you are talking about here, but in the newer versions (9.0.4 or 9.2) the best workaround would be to divide your mapping into 3 different mappings and execute them sequentially from a process flow.
Regards:
Igor

Payment order Deleted

Hello Experts,
I have a query as below,
Vendor master created with Payment method C(Cheque) -No payment order configured in FBZP
Customer has been assigned in Vendor master and Customer has been created with Payment method Q(Payment method configured(FBZP)_
MIRO posted for Vendor and System included for payment proposal and Payment order has been posted for Vendor line item
Not sure how user has deleted the payment order,Upon checking table PYORDP, System resulted No entry exists.
Now after payment order deleted i can still see payment order exist in line item i.e. in document
If we try to execute payment now system doesnt considering this line item for payment.
Please tell me the way forward on this
Note:-Sorry with my presentaion as i am new to SCN
Regards
Kiran

Hello Jayj,
Thanks for the reply,
But as i already mentioned above user has already deleted payment order, and it doesnt exist in PYORDH and PYORDP respectively.Meanwhile even after deletion i still can see Payment order in line item of the docment and because of this system doesnt considering this for F110.
Please tell me how can make this entry considerble inF110
Regards
Kiran

Payment Order deletion

Dear gurus,
I need a help in APP.
In Autometic payment program our client is using payment orders. While clearing from the bank due to some techinal issue open item has not been cleared but clearing document has been created against the vendor.
This transaction is happend in 2001 fisical year. That payment orders deleted from the data base. Due to that i am not able to clear the payment order in the vendor invoice.
In this senario, is there any way to delete the payment order in the vedor invoice.
While testing in DEV,i deleted the entris from REGUP & REGUH. Even it is not working.
Please suggest me how to slove this issue.
Regards,
Ramana
Edited by:

This issue solved.

Sale order costing process : Help required

Hello All,
Belatted Happy New Year 2011 to all.
I have a question related to Sale Order Costing. It goes like this,
My client is into Pipe coating business who receives the pipe from the customers, coats it as per there requirements and despatches it thereon. There is no concept of FG here as its only the service he is doing on it and also when he receives the pipe there is no raw material cost on it. Raw materials for him would be chemicals etc which he uses to coat the pipe.
And also this demands variant configuration from SD and PP angel.
As this scenario is customer specific, it demands Sale Order based costing(Sale order cost estimate).
My doubt is, how the sale order costing process goes with.
In general scenarios, Make to stock, we use production order based costing where standard cost estimate is calculated for planned cost and actuals are incurred on PO settling the variance to COPA
Similarly how the costing goes with if Sale order cost estimate is used. What i think is, here instead of Standard cost estimate for plan, we will go with Sale order cost estimate at sale order level, and incur actual cost at production order and settle the cost of Production order to Sale order. Correct me if i am wrong, and request you ppl there to explain me the process of costing in the scenario said above.
apart from that, my client wants the flexibility to change the cost estimate at quotation level.
Please suggest me with solution explaining the process of costing here.
Thanks in advance,
Ravi Kumar

Hi Ravi
Your understanding of the scenario is very much right...
In your case, you need to have sales order as cost object...
Process
Your stock would be non valuated stock, because the FG is not your stock.. You are just doing a service
Based on the characteristics chosen in the Sales orders, system would determine the Sales order BOM
Based on sales order BOM, Sales order cost estimate would be calculated....
You would receive the Customer pipe in your stock against the sales order... It would be a non valuated GR... You can track the Qty only
Sales order would trigger a production order... The prod order can have its planned cost, which is only for information sake
The Customer Pipe, Chemicals would be issued to prod order to coat the pipe... And also Labor/machine hrs may be confirmed
There after your production order would be settled on Sales order
Then you would do PGI (Post Goods Isue).. This will not trigger any accounting doc
Then you do billing... The sales revenue would be posted on the sales order
Then you settle the sales order to COPA.. This will close the cycle
Configuration
The IMG Settings required would be as below
1. You would use account assignment category (AAC) E
2. Create a Requirement class with
a. AAC = E.... (Means sales order is CO Object)
b. Valuation Indicator = BLANK (Means Non Valuated Stock)
c. Costing ID/Costing Method = As per your choice to calculate the Sales order cost estimate
3. Assign this req class to Requirement Type
4. Give this req type to your PP/SD team.. They would assign it to Strategy group / Item Category to determine it in the sales order
Regards
Ajay M

SNP planned order deleted in APO, but not in R/3.

OK Guru's,
We have a situation where during the weekend SNP planning runs, SNP Planned orders are deleted in APO, but the order is never deleted in R/3. The change pointer is not in CPP and there are no failed queues. Also, when you run CCR on planned orders, we will get an error on some orders saying "Not in APO" and the only option to reconcile that order is to "Send to APO". The option that should exist is "delete in R/3" becuase the deletion never occured in R/3.
If you send the order back to APO, the order will show in the "Production Confirmed" line of the Planning Book. This is because APO is thinking that this order is an order that was created in R/3 when in fact is it really is a SNP planned order.
Any clues to why this would happen?
thanks,
Brian

How are you getting the SNP Planned Orders to R/3 in the first place.
If you are transferring them using /SAPAPO/RRP7 then I guesss its a manual transfer and system does not consider SNP Planned Order deletion flag relevant for transfer to R/3.
You will need to look into CIF enhancement to send the deletions to R/3.
Normally SNP Planned Orders are not relevant for transfer to R/3 unless its replaced or converted to a PPDS planned order.
Somnath

Unmarking of Purchase Order deletion indicator

Hi
Purchase order deletion indicator was flaged for the line itme due to which not able to do the goods receipt
Reset the deletion flag , still i am not able to do the GR
It is giving the error message - PO has the deletion indication
Could you please help on this
Thanks
Tanvi

Hi
In EKPO table deletion indicator is not there
In EKKO table deletion indicator field has the value C
How to unflag the deletion indicator at header level
Error message is
Purchase order 4511582854 has deletion indicator
Message no. M7031
Could you please suggest how to move further
Thanks
Tanvi

Can i create production order using process material ?

Dear All.
Please help me.
I want to create production order using process material (material type is PROC).
For may knowledge, process order is standard for the process material, but my customer want to use the PP module for the process material.
But I cant convert the planned order of precess material to production order in MD05.
The system message is "System does not support planned orders for process materials."
The followings are my test steps.
1. Master Creation
      - Material Master, BOM, ROUTING
In standard, process material (Material Type : PROC) need creation of master recipe. But due to my clients need (Using production order
           for the process material), I create the work center and ROUTING
2. DM Creation
      - In MD61, I create the planned independent requirement (Type : LSF)
3. Planned order creation for the process material using MRP
      - In MD01, I run the total MRP, the the planned order is created.
        It's order type is "LA"
4. Converting the planned order to Production Order
      - In this step, the system give the error "System does not support planned orders for process materials."
         and can not do anything.
I want to know that the above case is possible, and how.
Please Help meu2026..

Hi
First of if yur want to create production order or process order why do you go for material type :PROC.
you can create the same material as FERT & go ahead.
I do not understand the logic to select the material type as PROC.
Pl. go through SAP library where PROC is used.
Regards
YMREDDY

Order deletion process

Similar Messages

Maybe you are looking for