Production Order - relese rejected

Hi SAP Gurus
while releasing production order it shows the following error due to which i can not release the order
"Object ACT 1000921 0010 has system status WCRE (Work center until release). According to this status, transaction 'Release operation' is not allowed".
So how to solve this error.
Plz reply.
Rgds.

Dear,
The work center usage in CR03 is causing this problem.
For this usage in OP45, for usage and tasklist type you can find a Until rel ticke is active.
Either this has to be removed or you need to change the usage in WC.
Practically usuallay we create a Production version with this type of WC, Hence system will consider this PV during MRP, after that we will allocate the quantity to different lines and WC will get changed. Hence when we createa Production order it will not create any problem.
In yoyur case alos may be same. Just check and come back.

Similar Messages

Production order relese

hi sap guru
i am doing the production order relese senario, but order not relese ,system give massege ' system status WCRE is active' so the order relese has been rejected. in co40.
thnk
paresh

presently the usage key that is enter is009- all task list usage
which usage key should we use
will it be afect to the production order
regards
paresh

Rejected Qty Production Order

Suppose I have got a production order for 100 Nou2019s. I have maintained the rejection percentage as 2%. I have maintained 4 operations 10, 20, 30 and 40. While running MRP, planned order generated for 102 Nou2019s. After that I have released the production order. Now during confirmation of operation 10, 4 Nou2019s have rejected. So in this case, what will happen? Whether again new planned order will generate? If yes, then for what Qty (2 or 4)? Please explain in detail?

Hi ,
Rejection % u defined that is planned rejection( as per ur past exp.). and rejection happen during operation is unplanned .
It will not create any planned order.

Rejected production order quantity (very urgent)

hi all
can somebody tell me how to chek the rejected qty for a production order
thanx

Hi,
CO14 - Display confirmation of prod. order
enter prod order number, display how many confirmed qty / scrap(rejected)
COOIS - Production Order Information System
CO03 - Display production order
CO26 - Order Information System
Regards,
Sankaran

Standard procedure of component Rejection in production Order

Dear All,
I want to know what is the exactly standard procedure for posting rejection of component in production order?
Some points to be noted !
1).Rejection quantity is not constant. For example, material A can be rejected with 5 EA quantity or 20 EA quantity. so not a static quantity in BOM should be referred.
2) For example, If m going to post rejection of semi finish material abc which exist in finished material BOM. Semi finish material abc contains another semi finish material in its bom. Then how rejection process should be catered in this scenario.
Waiting for your kind responce
Regards
Ahmed

Hi,
You can reject/scrap the semi finish material while it's operational confirmation e.g. by CO11N.
You can put the rejected quantity in scrap or if require to rework then put it into Rework field. See the fields in below screen snap of CO11N,
If your semi finish BOM include another semi finish then at any operational confirmation if is consumed then cost of it considered and ultimately the same is also rejected.
Regards,
Narresh

Can not delete a Production Order is the Sales order item is rejected?

Hello everyone,
I can not delete the production order as the Sales order line item is rejected.
Does anybody know if any configuration change is required or any work around?
Thank you,
BG

Hi,
Could you pl. explain how the production order is created?
Also did you try by choosing Function in the menu (CO02 transaction) & try to set deletion flag or Technically complete?
If so did you get any error message ?
Regards,
Senthilkumar

Reason ofr rejecting the production order

Dear Consultants,
When i am trying to release the production order the same is getting rejected. The following message i am getting.
"Release rejected (check log)
Message no. C2039".
When i check the log i found following two error messages.
1) Order type 8686 plant 8686: No checking rule maintained for operation
Message no. CO288
Diagnosis
To carry out a material availability check, the system needs a check rule. No check rule has been maintained for order type 8686 and plant 8686 for this business transaction (for ex. "order creation" or "order release").
Procedure
Maintain the checking group for the corresponding plant, order type and key (business transaction).
Key 1: control for automatic checking on
order creation or manual checking for orders that have not been released.
Key 2: control for automatic check on order release or manual check for
partially released or released orders.
2) Release of order not possible
Message no. CO118
Diagnosis
The order could not be released.
Please provide a solution to me. I need to release the production order.
Thanks in advance.
Anand.
Procedure
Check the entries in the release log.

Well, i m not a PP consultant but i guess thismessage ( CO288) is due to incorrect customizing.
Please check the data in OPJK for this ordertype/plant combination and enter a corect strategy
I guess anyway you should address this question to a logistic forum, this is for CO /FI/EC and
your issue ios clearly PP (so. logistic)
br, Guido

Change BOM and Production Order

Hello Expert,
I have recuuring problem, hope you can lean help to me. Can you explain to me why this happen?
we have change a component BOM in CS02, first we create change number in CC01. with effective date for 30.09.2008.
In BOM 6083, there exist a component 10020379. we want this component to be deleted on 30.09.2008 and be replace with a new component material 10060530 effective on the date 30.09.2008. that was the new set up of the BOM of material 6083 (at this date august).
Today (27.08.2008) we create a production order for material 6083, relesed it and when we will look at the PO Component Overview of our created PO both BOM component material 10020379 and 10060530 was present both backflushed was tick. but 10060530 component has zero req. qty compared to 10020379 it has a value on req. qty.
why that even we create the PO in August replacement material 10060530 was exploded and included in PO since this material will be effective on 30.09.2008?
and when we confirmed the PO via CO11N, we have a COGI error for the replacement material 10060530 "Enter Storage Location"?
How all this happen Guru?.
Thanks and more Power

Hi,
in this scenario, you can control the BOM explosion better with Revision Levels.
say you have created the Revision Level with CC11, using the same change master which is effective from 30.08.2008.
Every time, when you create an Order, system will pick the latest/relevant Revision level.
If you create an Order on 01.01.2009, suppose there is a chanege again to your BOM, still at the time of confirmation/backflush system will explode the BOM as on 30.08.2008.
Hope this helps..
Regards,
Siva

Inspection lot with Production Order

Hi friends,
I am PP consultant and need some help in setting up a scanario of Production order with inspection lot.
I need to setup a scenario where a inpspection lot is created from production order manually (not at the time of release). The purpose is to post few quantity of production order to scrap storage location. Inspection lot needs to be created only in certain production orders where some of the quantity has to be declared as scrap and that needs to be rejected with usage decision.
can any one please suggest the overview of such scenario.
Regards,
Rohit

Dear Rohit,
You want to create a manual inspection lot only for the purpose of Scrapping and also want it to be done with Usage Decision.
You can not use inspection type 89, as it is not stock relevant (Inspection type for Miscellaneous inspection),
There is one another solution with inspection type 08( inspection for Material Movement), but it might look Lengthy.
1. Release a Production order. say 100 qty.
2. If during process, 10 is scrap, then perform Partial Confirmation of 10 Qty.; Stock will be in Unrestricted.
3. Now, through MB1B, transfer 10 qty from Unrestricted to QI.
4. As you have inspection type 08 active, System will create an Inspection lot for 10 Qty.
5. You can post this whole 10 qty to Scrap while giving Usage Decision.
I think, in your process, Scrapping is not done frequently, that is why you do not want inspection lot at every production order.
in that case this solution may solve your problem.
regards,
Amol
Edited by: Amolbook on Jan 12, 2012 3:13 PM

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

Creation of production order report as per format

Hi!!!!
Gurus!!!!!
I want production order report in some required format.
How to see the format on production order
How to see the report in the following format.
Company name:-
Material requirement Number:-
date :-
Time:-
Due Date:-
Plan Date:-
Production Details:-
Item Code:-
Item Description:-
WH:-
Planned Quantity:-
Completed Quantity:-
Completed date:-
Rejected Quantity:
Waste and Scrap:-
Evaporation Quantity:-
Components:-
Sr.No.      Item No.   Desription             BOM Quantity Planned Quantity Issue Quantity
1     1000     RED                 20                     200                      200
2     1001     BLUE                 30                     300                      300
3     1002     Waste and Scrap -0.45987     -0.9845           -0.984567
          Total Quantity      50.45987     500.9845                     501.98888
Order Remark.
I want to see the report in this format.
Thanks with Regards,
Nitin

Nitin,
Your requirement certainly qualifies for creation of a new Production order Print form and custom print program if you are looking at printing at individual order. If you are looking at report, then certainly a custom report.
Regards,
Prasobh

Early Inspection for a Goods Receipt for production order

Dear Experts,
This is with respect Early Inspection for a Goods Receipt for inspction type 04.( 03 is also active in material master)
We made partial confirmation 250 qty for production order using t code co11n ( total qty of production order is 1000).
made the usage decision with an acceptance and posted all open stocks. to unrestricted.
Now in second partial confirmation prodn order of 250 qty was made . This suppose to be rejected . but sytem will add this 250 qty directly to unrestricted stock . how to over come this .
Regards
Sandeep

Don't make the UD until all stock has been receipted?
You basically approved the batch. So why wouldn't the system put the stock to unrestricted?
Why would you make a UD when you still have stock to be posted anyway? You can post stock without without making a UD so why not just post some if you need it, and wait on making the UD?
Craig

Material backflush in production order after finished goods GR

Dear all,
I once started similiar topic several months ago, but didn't recieved any response. I'm gonna give it another try, so maybe you'll be able to support me after all.
So, the situation is like this. We have a production order, in which MC team maintained the materials to consume. The problem is, that very often it comes that we have to use same material part, but under 2-3 different partnumbers. E.G.:
Production order target: 1000 finished goods
Required materials: Part A 1000 pcs, Part B1 700 pcs, Part B2 300 pcs, Part C 1000 pcs, Part D1 150 pcs, Part D2 450 pcs, Part D3 400 pcs.
So yes, in case when it is Part B1, B2 and etc. it means that we're using physically the same part, but under different partnumbers. The problem is, that those material are all coming in pieces, not in meters or anything, and we can't allow to have, for example, 0.7 pcs of any of those materials (cause obviously you can't have 0.7 pcs of LCD panels stored in the warehouse).
It wouldn't be a problem if we could just confirm all operations in production order in 1 batch, but production order is being confirmed partially, every time the pallet with finished goods is being released from production line (we have integrated system, that sends requests to SAP to confirm specific quantity of finished goods in production order). So, as an example, if 1 pallet contains 15 pcs of finished goods, you have 67 confirmations for production order [(66*15)+(1*10)]. And, since all those materials come in PCS, SAP is rounding up consumption if it has decimal, which leads to wrong materials consumption.
Initially, I had an idea of adding 1 more operation in production order, which was supposed to be a manual use only, after finished goods GR, and MC team supposed to assign those B1\B2 and etc. material to this operation E.G.:
Operation 0010 - consume material from work center A
Operation 0020 - consume material from work center B
Operation 0030 - finished goods GR (milestone)
Operation 0040 - consume material from work center C
My idead was rejected, since I was told that after GR for finished goods is done and you continue consuming materials in production order - it will not be shown in financial reporting (don't know the details, it was quite a straight reject, without much explanation).
So, question is - is there a way to consume materials after finished goods GR without creating mess in financial reporting, or if not - what other options do I have?
thank you in advance

Hi Valentin,
After GR also you can do goods issue. Till the order status is CLSD (Closed) you can book cost on to the order.
Two ways to consume materials on order.
In order component overview maintain the required part number with quantity. GI as can done with reference to order MB1A 261 movement type.
Directly do GI with MB1A -261 movement type - Input the order number, material number and qty.
Refer to the below discussion on unplanned GI which was discussed yesterday,
http://scn.sap.com/message/14850196#14850196
Thank & Regards,
Ramagiri

Goods Issue from Production Order in SAP

Dear experts,
I faced one issue not yet solve is that my customer created the production order
then already issue for production for all quantities of child item .
Example:
Production OrderItem A
Item A1 = 2 Qty
Item A2 = 2 Qty
Item A3 = 2 Qty
Issue for Production Item A
Item A1 = 2 Qty
Item A2 = 2 Qty
Item A3 = 2 Qty
But later on, my customer found out that 1 Qty of Item A1 already damaged.
So they want to issue one more Qty of Item A1 instead of one that already damaged.
How can I issue one more Qty for this item?
Please your advices are necessary for me.
Best regard,
Borey

Hello Borey,
Solutions may depend upon the way you want to book the cost for the damaged part A1.
     (a) If you want to book the cost to the production order itself (production order is a cost object), manually book consumption for another quantity using MB1A, 261 movement (you will have to mention the production order during posting this consumption).
     (b) If you do not want to book higher cost to that production order, you can:
           1. Extract damaged quantity of A1 from that production order using MB1A 262 movement.
           2. Create a manual QM lot and after rejection, move that damaged quantity to blocked stock.
           3. You can scrap or rework from that blocked quantity later.
           4. Issue another quantity of A1 from unrestricted stock to that production order using MB1A                261 movement.
Hope I could help you.
Best Regards.
Rajen

Grouping of Production orders

In Assessment or distribution cycle, we have production orders as the receivers. Since the list of production orders can be huge for month, creating the group through menu Extras/ Create group is not practical. I also tried to make set for the prodcution orders. But then this is set is not taking in the Assessmement cycle or distribution cycle.
I am getting the error message like:
Set PRD1 may not be used
Message no. GS076
Diagnosis
In this transaction, only certain set classes are permitted: Order Groups. PRD1, however, belongs to set class Set.
System Response
The entry is rejected.
Procedure
Use a set from set class Order Groups.
Or do we have any other method of assigning the groups.
How to solve this.
Please help.
Regards
Kami

Hi Kamijha,
I think you will find that the follwing should work for your purpose:
Go to Transaction OKOV. Choose a name for your variant and hit "create".
Now you can define the orders you want to select in your cycle not only by numbers or number ranges, but dynamically by characteristics such as order type, release date, anything you want. I suggest selecting by order type and additionally any characteristic that you find allows you to determine if the production order was "active" in the current period. If you only select by order type, the cycle will take much longer. Restricing to "active" orders in the variant may make it necessary to adjust the variant once per month before running the cycle though.
The selection variant you create here can be used as order group in your cycle.
There is just one more little thing you need to know: When you created the selection variant in OKOV and you chose the name "NAME" there, in your cycle, you will have to input ".NAME" for the group.
The same is true when you want to use the selection variant created in OKOV for the selection for a report in the internal order info system: you always need to put a "." in front of the name you gave the selection variant when you created it.
I just ran a test run with a cycle like yours in our system and the production orders were successfully selected.
Regards
Nikolas

Production Order - relese rejected

Similar Messages

Maybe you are looking for