Release a production order for partial quantity

Hi gurus,
Can you please tell me how can i release a production order for partial quantity without splitting the order?
Regards
Rajib Pathak

Dear,
Best way you can conver the planned order to production oreder in partial in CO40.
Or from MD04 screen click the planned order, choose pratial release and enter the quantity you want to release and press Generate button. the order gets converted to production orders of yr specified quantity and rest planned order remains for further processing.
Or,
Create order
Goto operation overview
Select the operation and click on release button...which will release the opration alone instead of releasing the order. If you release the order, then all the eperatios are released onec for all.
If you go for operation release...you can release operation by operation, which will be partial release of order at header level.
at operation level - partial release
Hope it will help you.
Regards,
R.Brahmankar
Edited by: R Brahmankar on Nov 12, 2008 9:44 AM

Similar Messages

Automatic release of production order for perticular work center

hello,
any body please help me how to set automatic release of production order when creation for a particular work center. please suggest me.
Thanks & Regards
Bhakta

Dear,
Use T Code COHVOMRELEASE here select work center as ZPACK then in header menu Program--Schedule in background here define as perodic job and set ferquency as Hr.
Or Use Transaction SE38 to create the variants for program PPIO_ENTRY and schedule it through SM36 or use standard variant as SAP&RELEASE.
Please try and come back.
Regards,
R.Brahmankar

Sap pp-releasing the production order?

at are the activities carried out while releasing the production order?

Hi,
Order Release
Use
A production order must be released, before it can be processed. You can use the time period between creating and releasing a production order, for example, to carry out company checks and preparations. If you do not require this time period, you can automatically release the production order when it is created (see Automatic Release).
A newly created production order initially receives the status CRTD (created). The following restrictions apply to a production order that has been created:
Confirmations for the order cannot yet be executed.
Shop floor papers cannot be printed.
Goods movements for the order cannot yet be executed.
Releasing the order lifts these restrictions.
Features
Order release can be executed at the following levels:
With Release at Order Header Level all operations are released. The order and the operations receive the status REL (released).
With Release of an Operation the operation receives the status REL and the order receives the status PREL (partially released). If all operations in an order have been released, the order has the status REL.
Hope this helps.
Revert if you need more information.
Regards,
Tejas

Error while release of production order u201CNext period is not openu201D

Hi Experts,
Need your opinions on this issue where my client is facing a problem while create and release a production Order on the last day of the month (Last day of period change).
While create and release of production order for Plant xxxx, system uses to give the error; period Next (e.g. 12) is not open. Same thing if I have created the order using T. code CO01; but when I tried to release and save the order through T. code CO02 then it gave me the same error (Next period is not Open), it checks for the next period to open.
The above scenario happens only on last day of the month. Earlier this kind of error was not there so the question is why the period check is happening while saving the production order.
After speaking to the user, it is determined that they are facing this problem since upgrade (Since last 8 month). Hence need to check what additional check has been implemented with upgrade from R/3 4.7 to ECC 6.
Error Message No F5201
Appreciate your help how to dig up this issue.
With Regards
Anant

Hi Guys,
Please throw some light why on the last day of the month (Last day of period change) at the time of release the order user is getting error: Period Next (FI Next period) is not open ( message No. F5201).
My question is why system carried out period checks at the time of release of Production Order.
With Regards
Anant

Component pick release for partial quantity

Hi All,
For R12 environment , customer needs move order to be created for partial quantity using component pick release.
As far as I know component pick release cannot be done for partial pick release and only possible when onhand qty is not available.
Can any one pleas elet us know if we can have any alternate solution or easy customization so that client can edit the quantities before going to move order creation?
Thanks
Vasudha

when the move order is created..update the allocation and then perform transact move order
ex if for 10 qty move order is created..but if u wish to issue 5 qty to the job..then update the allocation..for the remaining u can just backorder the move order
HTH
Mahendra

Don't release Production Order for negative stock.

Actually i don't want Production Order to be released, if component (child) items falls into negative stock. Is there any solution for that. If yes, please help me out.
Thanks

HI!
you can write a SP to block Release a production order from planned state.
Check the onHand stock of all child items w.r.t the warehouse and block updating the status to release

Cannot release production order for a plant

Hi:
When I try to release a process order , I get this error message:
"CAnnot release production order for plant".
I get this message for a particular material in the plant. For other materials, it's working fine.
Please give your suggestions!
Gautham

Hi,
Check the Tasklist usage for your routing for that material.
For this usage ,check in op45 against the task list type whether until release indicator has been enabled.If so remove
and do the release.
or
check whether workcenter which is used for producing the material has been locked in work center itself.
Indicator: Usage only until release in orderIndicator used to specify for a task list usage and a task list type that an operation in the order cannot be released. This occurs when a work center group that is not intended for production is allocated to this operation.
When this type of operation in the order is released you must enter the work center where production should take place.
Regards,
nandha

How to get all production orders for a workcenter

Hello ...
I have a requirement to create a report of all production orders for a given workcenter. The user enters the workcenter (CRHD-ARBPL), plant (CRHD-WERKS) and a date range, and wants to see a list of orders (AUFNR) that fall within that date range along with some other data from AFKO and AFPO.
I can't figure out a good, consistent way to get from workcenter to production orders.
Any ideas?
Thanks!
Sharon

Hi there check this program for relation between SO PO and Production order
REPORT z_so_info.
TABLES: vbak, vbap, afko, afpo.
*Field catalog
TYPE-POOLS: slis.
DATA: lv_repid TYPE sy-repid VALUE sy-repid,
xfield TYPE slis_t_fieldcat_alv,
afield TYPE slis_fieldcat_alv.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(25) text-002.
SELECT-OPTIONS: so_so FOR vbak-vbeln OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-003.
PARAMETERS:
p_kunnr LIKE vbak-kunnr, " sold-to
p_kunwe LIKE vbak-kunnr. " ship-to
SELECTION-SCREEN END OF BLOCK b2.
*Constants
CONSTANTS: c_zor TYPE vbak-auart VALUE 'ZOR',
c_we TYPE vbpa-parvw VALUE 'WE',
c_ag TYPE vbpa-parvw VALUE 'AG'.
* c_space TYPE space.
*Ranges
RANGES: ra_parvw FOR vbpa-parvw,
ra_kunnr FOR vbpa-kunnr.
*Tables
DATA: BEGIN OF gt_output OCCURS 0,
vbeln LIKE vbak-vbeln, " sales order number
posnr LIKE vbap-posnr, " SO item number
matnr LIKE vbap-matnr, " material number
sh LIKE vbpa-kunnr, " Ship-to
sp LIKE vbpa-kunnr, " Sold-to
lifnr LIKE ekko-lifnr, " Vendor
bstnk LIKE vbak-bstnk, " PO number
banfn LIKE vbep-banfn, " Purchase requi
po_st TYPE char30, " PO status text
pstyv TYPE vbap-pstyv, " Item catagory
aufnr LIKE afpo-aufnr, " Production Order
prd_stat TYPE string, " Prd order status
END OF gt_output.
DATA: wa_output LIKE gt_output.
FIELD-SYMBOLS: <fs_output> LIKE gt_output.
*Table for sales order and PO
TYPES : BEGIN OF gs_data,
vbeln TYPE vbak-vbeln,
posnr TYPE vbap-posnr,
pstyv TYPE vbap-pstyv,
matnr TYPE vbap-matnr,
END OF gs_data.
DATA: gt_data TYPE STANDARD TABLE OF gs_data,
wa_data TYPE gs_data.
*Table for Production Orders
TYPES: BEGIN OF gs_prd,
aufnr TYPE afpo-aufnr,
posnr TYPE afpo-posnr,
kdauf TYPE afpo-kdauf,
kdpos TYPE afpo-kdpos,
wepos TYPE afpo-wepos, "Goods Receipt Indicator
elikz TYPE afpo-elikz, "Delivery Completed Indicator
objnr TYPE aufk-objnr, "Object number
* getri TYPE afko-getri, "Confirmed Order Finish Date
* gltri TYPE afko-gltri, "Actual finish date
END OF gs_prd.
DATA: gt_prd TYPE STANDARD TABLE OF gs_prd,
wa_prd TYPE gs_prd.
*Table for partner data
TYPES: BEGIN OF gs_partner,
vbeln TYPE vbak-vbeln,
posnr TYPE vbap-posnr,
parvw TYPE vbpa-parvw,
kunnr TYPE vbpa-kunnr,
END OF gs_partner.
DATA: gt_partner TYPE STANDARD TABLE OF gs_partner,
wa_partner TYPE gs_partner.
TYPES: BEGIN OF gs_po,
ebeln TYPE ekkn-ebeln,
ebelp TYPE ekkn-ebelp,
vbeln TYPE ekkn-vbeln,
vbelp TYPE ekkn-vbelp,
END OF gs_po.
DATA: gt_po TYPE STANDARD TABLE OF gs_po,
wa_po TYPE gs_po.
TYPES: BEGIN OF gs_preq,
vbeln TYPE vbep-vbeln,
posnr TYPE vbep-posnr,
banfn TYPE vbep-banfn,
END OF gs_preq.
DATA: gt_preq TYPE STANDARD TABLE OF gs_preq,
wa_preq TYPE gs_preq.
TYPES: BEGIN OF gs_po_stat,
ebeln TYPE ekko-ebeln,
procstat TYPE ekko-procstat,
lifnr TYPE ekko-lifnr,
END OF gs_po_stat.
DATA: gt_po_stat TYPE STANDARD TABLE OF gs_po_stat,
wa_po_stat TYPE gs_po_stat.
*Field symbols
FIELD-SYMBOLS: <fs> TYPE tj02t-txt04,
<fs_temp> TYPE tj02t-txt04,
<fs_stat> TYPE char30.
START-OF-SELECTION.
PERFORM fr_build_range.
PERFORM fr_get_data.
PERFORM fr_build_fc.
PERFORM fr_output.
*& Form fr_get_data
* text
* --> p1 text
* <-- p2 text
FORM fr_get_data.
*Get SO
SELECT a~vbeln a~posnr a~pstyv a~matnr
FROM vbap AS a
JOIN vbak AS b
ON a~vbeln = b~vbeln
JOIN vbpa AS c
ON b~vbeln = c~vbeln
INTO TABLE gt_data
WHERE b~vbeln IN so_so
AND b~auart EQ c_zor "Only Sales Orders
AND c~kunnr IN ra_kunnr. "from selection screen
DELETE ADJACENT DUPLICATES FROM gt_data COMPARING vbeln posnr.
*get data of the production order
IF NOT gt_data[] IS INITIAL.
SELECT a~aufnr a~posnr a~kdauf a~kdpos a~wepos a~elikz
b~objnr
FROM afpo AS a
JOIN aufk AS b
ON a~aufnr = b~aufnr
INTO TABLE gt_prd
FOR ALL ENTRIES IN gt_data
WHERE a~kdauf EQ gt_data-vbeln
AND a~kdpos EQ gt_data-posnr.
ENDIF.
*Get partner data
IF NOT gt_data[] IS INITIAL.
SELECT vbeln posnr parvw kunnr
FROM vbpa
INTO TABLE gt_partner
FOR ALL ENTRIES IN gt_data
WHERE vbeln EQ gt_data-vbeln.
ENDIF.
*Get Purchase Order
IF NOT gt_data[] IS INITIAL.
SELECT ebeln ebelp vbeln vbelp
FROM ekkn
INTO TABLE gt_po
FOR ALL ENTRIES IN gt_data
WHERE vbeln EQ gt_data-vbeln
AND vbelp EQ gt_data-posnr.
SELECT vbeln posnr banfn
FROM vbep
INTO TABLE gt_preq
FOR ALL ENTRIES IN gt_data
WHERE vbeln EQ gt_data-vbeln
AND posnr EQ gt_data-posnr.
ENDIF.
IF NOT gt_po[] IS INITIAL.
SELECT a~ebeln a~procstat a~lifnr
FROM ekko AS a
JOIN ekpo AS b
ON a~ebeln = b~ebeln
INTO TABLE gt_po_stat
FOR ALL ENTRIES IN gt_po
WHERE b~ebeln EQ gt_po-ebeln
AND b~ebelp EQ gt_po-ebelp.
ENDIF.
*Move data to output table
LOOP AT gt_data INTO wa_data.
wa_output-vbeln = wa_data-vbeln.
wa_output-posnr = wa_data-posnr.
wa_output-pstyv = wa_data-pstyv.
wa_output-matnr = wa_data-matnr.
READ TABLE gt_po INTO wa_po WITH KEY vbeln = wa_data-vbeln
vbelp = wa_data-posnr.
IF sy-subrc EQ 0.
wa_output-bstnk = wa_po-ebeln.
READ TABLE gt_po_stat INTO wa_po_stat WITH KEY ebeln = wa_po-ebeln.
IF sy-subrc EQ 0.
wa_output-lifnr = wa_po_stat-lifnr.
CASE wa_po_stat-procstat.
WHEN '01'.
wa_output-po_st = 'Version in process'.
WHEN '02'.
wa_output-po_st = 'Active'.
WHEN '03'.
wa_output-po_st = 'In release'.
WHEN '04'.
wa_output-po_st = 'Partially released'.
WHEN '05'.
wa_output-po_st = 'Released Completely'.
WHEN '08'.
wa_output-po_st = 'Rejected'.
ENDCASE.
ENDIF. "inner read subrc
ENDIF. "outer read subrc
READ TABLE gt_preq INTO wa_preq WITH KEY vbeln = wa_data-vbeln
posnr = wa_data-posnr.
IF sy-subrc EQ 0.
wa_output-banfn = wa_preq-banfn.
ENDIF.
READ TABLE gt_prd INTO wa_prd WITH KEY kdauf = wa_data-vbeln
kdpos = wa_data-posnr.
IF sy-subrc EQ 0.
wa_output-aufnr = wa_prd-aufnr.
*get the purchase requisition for production order as well
SELECT SINGLE banfn
FROM ebkn
INTO wa_output-banfn
WHERE aufnr EQ wa_prd-aufnr.
*Get the status of the production order
PERFORM fr_get_prd_stat USING wa_prd-objnr
CHANGING wa_output-prd_stat.
ENDIF. " sy-subrc
READ TABLE gt_partner INTO wa_partner WITH KEY vbeln = wa_data-vbeln
parvw = c_we.
IF sy-subrc EQ 0.
wa_output-sh = wa_partner-kunnr.
ENDIF.
READ TABLE gt_partner INTO wa_partner WITH KEY vbeln = wa_data-vbeln
parvw = c_ag.
IF sy-subrc EQ 0.
wa_output-sp = wa_partner-kunnr.
ENDIF.
APPEND wa_output TO gt_output.
CLEAR: wa_data, wa_prd,wa_partner,wa_output.
ENDLOOP.
ENDFORM. " fr_get_data
*& Form fr_build_range
* text
* --> p1 text
* <-- p2 text
FORM fr_build_range .
*Range for partner function
MOVE 'I' TO ra_parvw-sign.
MOVE 'EQ' TO ra_parvw-option.
MOVE 'SH' TO ra_parvw-low. " we
APPEND ra_parvw.
CLEAR ra_parvw.
MOVE 'I' TO ra_parvw-sign.
MOVE 'EQ' TO ra_parvw-option.
MOVE 'SP' TO ra_parvw-low. " ag
APPEND ra_parvw.
CLEAR ra_parvw.
*Range for ship-to and sold-to
MOVE 'I' TO ra_kunnr-sign.
MOVE 'EQ' TO ra_kunnr-option.
MOVE p_kunnr TO ra_kunnr-low.
APPEND ra_kunnr.
CLEAR ra_kunnr.
MOVE 'I' TO ra_kunnr-sign.
MOVE 'EQ' TO ra_kunnr-option.
MOVE p_kunwe TO ra_kunnr-low.
APPEND ra_kunnr.
CLEAR ra_kunnr.
ENDFORM. " fr_build_range
*& Form fr_build_fc
* text
* --> p1 text
* <-- p2 text
FORM fr_build_fc .
* sales order number
afield-fieldname = 'VBELN'.
afield-seltext_s = 'Sales #'.
afield-ref_tabname = 'VBAK'.
APPEND afield TO xfield. CLEAR afield.
* sales ITEM number
afield-fieldname = 'POSNR'.
afield-seltext_s = 'Item #'.
afield-ref_tabname = 'VBAP'.
APPEND afield TO xfield. CLEAR afield.
* Material Number
afield-fieldname = 'MATNR'.
afield-seltext_s = 'Material #'.
afield-ref_tabname = 'VBAP'.
afield-outputlen = 10.
APPEND afield TO xfield. CLEAR afield.
*Vendor Number
afield-fieldname = 'LIFNR'.
afield-seltext_s = 'Vendor Num.'.
afield-ref_tabname = 'EKKO'.
APPEND afield TO xfield. CLEAR afield.
* ship-to-party
afield-fieldname = 'SH'.
afield-seltext_s = 'Ship-to'.
afield-ref_tabname = 'VBPA'.
APPEND afield TO xfield. CLEAR afield.
* sold-to-party
afield-fieldname = 'SP'.
afield-seltext_s = 'Sold-to'.
afield-ref_tabname = 'VBPA'.
APPEND afield TO xfield. CLEAR afield.
*PO number
afield-fieldname = 'BSTNK'.
afield-seltext_s = 'PO NUM'.
afield-ref_tabname = 'EKKO'.
APPEND afield TO xfield. CLEAR afield.
*PO status
* afield-fieldname = 'PO_STAT'.
* afield-seltext_s = 'Step'.
* afield-ref_tabname = 'zbacklog_v2'.
* APPEND afield TO xfield. CLEAR afield.
*PO step status
afield-fieldname = 'PO_ST'.
afield-seltext_s = 'PO.Status'.
afield-ref_tabname = 'zbacklog_v2'.
APPEND afield TO xfield. CLEAR afield.
*Purchase requisition
afield-fieldname = 'BANFN'.
afield-seltext_s = 'Pur. Req.'.
afield-ref_tabname = 'VBEP'.
APPEND afield TO xfield. CLEAR afield.
*Item catagory
afield-fieldname = 'PSTYV'.
afield-seltext_s = 'Itm. Catg'.
afield-ref_tabname = 'VBAP'.
APPEND afield TO xfield. CLEAR afield.
*Prodcution Order number
afield-fieldname = 'AUFNR'.
afield-seltext_m = 'Prod.Order'.
afield-ref_tabname = 'AFKO'.
APPEND afield TO xfield. CLEAR afield.
*PRODCUTION status
afield-fieldname = 'PRD_STAT'.
afield-seltext_s = 'Prd. Step'.
afield-ref_tabname = 'zbacklog_v2'.
afield-outputlen = 20.
APPEND afield TO xfield. CLEAR afield.
*PRODUCTION step status
* afield-fieldname = 'PRD_ST'.
* afield-seltext_s = 'Prd. Status'.
* afield-ref_tabname = 'zbacklog_v2'.
* APPEND afield TO xfield. CLEAR afield.
ENDFORM. " fr_build_fc
*& Form fr_output
* text
* --> p1 text
* <-- p2 text
FORM fr_output .
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
i_callback_program = sy-repid
* I_CALLBACK_PF_STATUS_SET = ' '
* I_CALLBACK_USER_COMMAND = ' '
* I_STRUCTURE_NAME =
* IS_LAYOUT =
it_fieldcat = xfield[]
i_default = 'X'
i_save = 'A'
TABLES
t_outtab = gt_output
EXCEPTIONS
program_error = 1
OTHERS = 2.
ENDFORM. " fr_output
*& Form fr_get_prd_stat
* text
* -->P_WA_PRD_OBJNR text
FORM fr_get_prd_stat USING p_objnr CHANGING p_prd_stat.
DATA: lt_status TYPE STANDARD TABLE OF jstat,
wa_status TYPE jstat,
lv_status TYPE tj02t-txt04,
lv_temp2 TYPE char5,
lv_buff TYPE string.
CALL FUNCTION 'STATUS_READ'
EXPORTING
client = sy-mandt
objnr = p_objnr
only_active = 'X'
TABLES
status = lt_status
EXCEPTIONS
object_not_found = 1
OTHERS = 2.
LOOP AT lt_status INTO wa_status.
IF wa_status-stat(1) EQ 'I'.
SELECT txt04 FROM tj02t
INTO lv_status
WHERE istat EQ wa_status-stat
AND spras EQ 'E'.
ENDSELECT.
lv_temp2 = lv_status.
CONCATENATE lv_temp2 p_prd_stat INTO p_prd_stat
SEPARATED BY ','.
ENDIF.
CLEAR: wa_status, lv_status, lv_temp2.
ENDLOOP.
lv_buff = p_prd_stat.
*Status of Production Order
IF lv_buff CS 'CRTD'.
p_prd_stat = 'Not Active'.
ENDIF.
IF lv_buff CS 'REL'.
IF lv_buff CS 'GMPS'.
p_prd_stat = 'Printed In Prod'.
ELSE.
p_prd_stat = 'Printed'.
ENDIF.
ENDIF.
IF lv_buff CS 'TECO'.
p_prd_stat = 'Technically Compt.'.
ENDIF.
ENDFORM. " fr_get_prd_stat

Create a Production order for rework

Hi,
I would like to create a Production order for rework.
But I don't want to do it in the master PO with trigger point.
I would like to create a new PO for rework and asign to account to the old or master PO.
I've tried to do it but I want to know if it's correct.
CO07, maintained the qty, in the settlement rule maintained (category= order,settlement reciever= master PO number) released the order and by confirmation where can I maintain the qty? (as Yield or as rework qty)
Thanks

Hi,
Use T code CO07- creation of PO w/o material, settelment rule as u mentioned and the quantity has to be maintained in rework.
When u confirmed the order and settel it, it will be settel againts the main order.
Regards
JDB

No release of production order without standard cost estimate

Hi All,
I have an requirement, that is production order for a material should not be released or saved if standard cost estimate for that period is not released. Basically it should not allow to release or save the production for that material, is SCE is not run for that period. I tried various options, i also overheard its possible through user exit and many people have succeed in that.
Has anybody overcome this problem, please do let me know. And which user exit??
Thanks in advance
With Best Regards
GJ.

Hi...
I have faced the same problem in my previous project. What i have instructed to my client is to take control of Master data and put the status as "03" Blocked for movement till the statndard cost is released for this material.
You can relase the status to "E2" in Cross Plant Status Field in Costing one view once the cost estimate is released for the material.
I hope this works for you.
Please let me know if you require any fruther information.
Thank you,
Regards,
Santosh
Rewards points if helpful.

IDOC on create or release of production order

Hi All,
I want to create IDOC on creation or release of production order (CO01), can anyone provide me steps and setting that i need to do to achieve this functionality. Business object used for his is BUS2005, and on release of Production order RELEASED event of object type AFVC_PM is getting triggered.
Thanks

Check below badis.
AFABD_CHANGE
CAUFVD_CHANGE
SIDAT_UPDATE
Regards,
Mkhan

How do we Prevent Creation of Production Orders for Phantom materials.

Dear Experts;
We have some materials which are Phantoms.
We have set "special procurement type" as 50 in MRP2 and "Strategy Group" as 59 in MRP3
These are non stchable items, but have BOMS.
We dont create orders for them, however at the mement the system allows order creation. How do we prevent creation of production orders for these items in the system.
Thanks in Advance
Richard.

Dear Richard,
Check using this BADI - WORKORDER_UPDATE using method IN_UPDATE or Release by including a check if MATNR and for
WERKS combination if SOBSL = 50 from table MARC,then do not allow to save.
Check whether this works or else you have to set a plant specific status using OMS4 for not allowing production order
creation and assign this value in the material master of the phantom assemblies.
Check and revert
Regards
Mangalraj.S

Problem while releasing the production order.

Hai gurus,
When i release the production order , SAP doesn't block when i have a deficit of stock for some materails.I checked all the customizing and found every thing is fine.
As the materials that has defict stock has back flush indicator, is that the reason why the system is assuming the stock when releasing.

Hi,
You need to consider the following customization settings
(1) OPJK - For the Plant/Order type/Availability check-2 for the material availability - Release material - set the indicator '3' No release if parts are missing
(2) OPJJ - For availability check & checking rule - check what all elements are considered as part of ATP check.
With these settings - in the production order if the order header has status MSPT - Missing parts (i.e. components are missing) only then system will stop the release of the order.
I hope this addresses your query
Warm regards,
Umesh

Control availability check during release of production order

friends,
Can you guys help me find the user exit/BADI which will allow me to control the release of production order after the availability check is complete.
In detail, the scenario is that : based on a flag on material master, I should be able to ignore this product's availability during release. I cannot change the availability check to "KP" ( No check) as this product can be sold seperately. So what I thought was that if I get to control the availability check during production order release I would be able to ignore this product before check or may be after check and before the status change.
I found PPCO0021 exit and function module EXIT_SAPLCOZR_003 which is actually intended for release control for automatic batch determination. I am not sure if I can use this.
Please let me know if you guys have any idea.
Thanks
Prod_Planner

Let me rephrase the scenario :
I have a production order for a product P1 which consumes raw materials R1 and R2. R1 is supplied by a nearby vendor every 1 hour to my plant so I do not need to worry about the availability of it when releasing the order but R2 availability should be taken into consideration. So, function 1 or 2 in OPJK will not work (as release need to be stopped if R2 not available) hence I will be using 3. If I use 3, R1 availability is also considered hence the whole order is not released. I will maintain a flag on material master so if R1 has flag, I need to ignore R1's availability but still considering R2.
As mentioned, I found PPCO---21 which could help me but need your help to understand if there is any other way.
Thanks
Prod_Planner

Goods Issue Production Order for Confirmed Qty Component

Dear PP Gurus,
Here is my case :
Stock Qty for Sparepart A : 100 un
First production will require 80 un A, and availability check confirmed. Second Production Order will require 70 un A, where 20 un confirmed and 50 un is not confirmed on availability check. When i try to goods issue the second production order, it is allowed to consumed all 70 un because unrestricted stock is 100. How can i forbid goods issue in second production order only for 20 un A which is confirmed before.
Thanks,
Arman Lie

Dear
First of all what ever qty u release during production it well get copied in confirmation so as u said first production order is 80 so the balance qty is 20 out of 100 units so for 20 production order is confirmed so u need another production order for 70 in that case u have deflicit stock of 50 so for that reason ur production order not get confirmed for 50 in order to confirm this order u need t make a stock of 50.
1. check in the OPK4 enable the actual qty
2.check t-code OPJK Checking Rule and check when material availability when saving the order
and please check in the material master what availability check u have maintained in mrp
[http://help.sap.com/erp2005_ehp_04/helpdata/EN/cf/70124adf2d11d1b55e0000e82de178/frameset.htm]
With Regards
Pushpalas

Release a production order for partial quantity

Similar Messages

Maybe you are looking for