Production order to Exclude "Stk provided to vendor" in availability Check

Dear All
              During material availability check of production
order the system is considering stock provided to vendor.It should consider only plant stock.
              Iam using Checking rule as PP01 & Availability check as 02.
              Suggest me how to exclude this stock provided
to vendor ahile doing availability check against production
order components.
Shankar

Hai shankar ,
while mrp run ,it will considererd only plant stock . It will not considererd vendor stock.
suppose if u want considererd vendor stock also ..then what we have do ?
Explain me
mani

Similar Messages

Reg:Bapi for mass creation of production order/confirmation

Dear Experts,
I wanted to know with the following BAPI is it possible to create Multiple production orders for different semifinshed Materials along with material availability check and other functions similar to CO01 transaction.
I knew there are standard transactions for mass confirmation for production orders. But i need a confirmation on this BAPI . As i am planning to go-ahed with ,mass creation of production order creation / Order confirmation in single custom transaction.Need back flush activity even supported.
BAPI_PRODORD_CREATE to create the orders.
BAPI_PRODORD_RELEASE to release the orders.
BAPI_PRODORDCONF_GET_TT_PROP to get the default data for the confirmation.
BAPI_PRODORDCONF_CREATE_TT to ost the confirmation of production order.
Along with this BAPI do i need to commit any other BAPI to carry out back flush for components.
Need your suggestions to take it further.
Regards,
Daya.

Dear SAP Daya
If the issue has been solved, please close this thread.
You have already mentioned that the issue has been resolved, thefore, you should not ask for help on another thread before closing this one, as it looks like you are trying to force people to answer your threads.
Users are always trying to answer as many threads as possible on good will we don't need this kind of "incentive".
Please read carefully the The SCN Rules of Engagement, especially point 8:
Be responsive. If an SCN member has answered your question, please mark the answer as "helpful” or “correct”. Mark the discussion as “answered,” so that other members can find the answers more easily
Also, I checked your old threads and I could observe that there is only one closed. Please review your old threads and close those already solved.
BR
Caetano

Reservation for Production order

HI experts..
The system will reserve the qty once the planed order get generated.
Will it be possible after the production order release.. the reserved stock should get blocked
and we sud not use the planed reserved qty for other production orders.
pls guide me how to do this..

Sri Ram,
Availabiltiy checking can give you the functionality I think you seek.
Available To Promise (ATP) doesn't exactly 'block' stock. Instead, each order (planned order, or production order, or Sales order) can be configured to execute an ATP check for components. You can configure that production orders cannot be released unless they pass an availability check for components. So, the first production order is released, and because of the way you have set the ATP up, there is no more component stock available. Now, when you try to release an additional production order, the ATP will fail, and you may not release the order.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/fc/836ae8f66111d2b6a70000e8359890/frameset.htm
Rgds,
DB49

How can a qm-lot be excluded from availability check?

Hi experts,
in oppj I can exclude "stock in quality inspection" from availability check, but the qm lots are still handled as fixed receipts. This is ok, because the qm lots are not a stock. But the availability check shows available quantity and this is, what I don't want!
The question is: "How can qm-lots be excluded from availability check?"
Thanks for your help!
SAP Anwender

Dear,
when you talk about QM lot,
QM lot is created during PO GR or Production order GR. Hence before the GR, MRP showes a recipt is expected and recipt element is either production order or PO.
Now even after GR, system removes the PO/Production order and increase the stock.
Hence in availability check if you decativate QM stock, this stock will not be considered, if to be con sidered, then active the QM stock.
Pl come back if required

Set Availability Check to Exclude Planned Order

Hi All,
anyone know how to set the availability check so it will not include the planned order in the calculation ?
I find one setting in SPRO, the path is :
Sales & distribution ==> Basic functions ==> availability check and Transfer of Requirements ==> Availability Check ==> Availability Check with ATP Logic or Against Planning ==> Carry Out Control for Availability Check
select one of the record, and update filed "Incl. Planned Orders".
I've uncheck that field, but I can't get the appropriate result. When I create a new sales order, the availability check still take the planned order I created before into account.
The problem is, my user want to prevent creating delivery before the goods are already put in the stock. So the planned order should not be considered in the availblity check.
Thank you in advance
Rudy

Hi Rudy,
Concept of availability check is to verify if the stock is available at the time of creation of sales order. If available, when it can be ready for delivery (as Packing, arranging for transportation, etc may have lead time) & if not available, when it would be available considering Packing, arranging for transportation, etc lead time.
Availability check whether material is available on required delivery date (backward scheduling) or not. If not available on required delivery date, system will propose next available date (forward scheduling)
1. Define Checking Groups
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups
You define checking groups with which you specify the type of requirements records the system is to create when processing sales orders or deliveries
2. Define Material Block for Other Users
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Material Block for Other Users.
3 .Define Checking Groups Default Value
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups Default Value.
4. Carry out Control for Availability Check
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Carry Out Control for Availability Check.
5. Define Procedure by Requirements Class
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure by Requirements Class.
6. Define Procedure for Each Schedule Line Category
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure for Each Schedule Line Category.
7. Determine Procedure for Each Delivery Item Category
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Determine Procedure for Each Delivery Item Category.
8. Checking Rule for Updating Backorders
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Checking Rule for Updating Backorders.
9. Define Default Settings
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Default Settings.
Availability checks
1. Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the time taken to produce or obtain the material. It also performs several background functions such as Backorder processing, rescheduling and ATP quantities.
2. Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date.
3. Rescheduling: is a proposal of how confirmed quantities already assigned to a sales order can be reassigned to other sales orders that have a higher priority.
4. Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock + planned receipts (incoming stock) planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics sales & distribution sales environment availability overview.
5. Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP 2 (procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively RLT time, which is found on MRP 3 view.
6. RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check (Available To Promise). The value of RLT for a material is specified on material master record.
7. There are three types of availability checks
Check on basis of ATP quantities.
Check against product allocation.
Check against planning.
Configuring Availability check through Checking Groups
1. The checking group + checking rule determine how the availability check is to be performed.
2. The checking group determines whether and how the system checks the stock availability and generates requirements for material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements (daily/weekly) or individual requirements for each sales order.
3. The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking rule is specified internally within the system and cannot be changed.
4. The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be carried out with or without the replenishment lead time.
5. Briefly explaining the above checking group determines which type of requirement to be passed on to MRP whether it be individual or summarized and checking rule which is at the transaction level and can be configured independently for each application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check checking group has to work in conjunction with checking rule.
6. Advantages of individual processing over summarized processing
Backorder processing is possible.
You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and requirements placed on stock.
The system automatically uses individual requirements in case of special stock items.
7. Required data for the Availability check to be carried out
The Availability check must be switched on at the requirement class level.
The Availability check must be set at the schedule line level.
A requirements type must exist by which the requirements class can be found.
A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in MMR).
A checking group must be defined in the material master record in the MRP3 screen in the availability check field.
8. Configuring Availability check and defining Checking Groups
Checking groups are introduced into the sales order based on the setting in the material master record.
SAP standard checking groups are 01 summarized requirements and 02 individual requirements or you can create your own by copying the standard ones.
Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either individually or by day or week.
Block quantity required can be set if you want several users to be able to process the material simultaneously in different transactions without blocking each other.
The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check.
9. Defining material block for other users the block check box is an indicator that enables you to block material master records of a particular material during the availability check and restrict other users from accessing same master record and reserve the material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot: a) Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material.
10. Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the material master record.
However if there is no entry present in the material master record for the checking group, a default value can be set here, depending on material type and plant.
This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order.
If an entry exists, this default value is over written by MMR.
11. Controlling Availability Check in this section, you tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check in addition to whether or not to consider the replenishment lead time.
12. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sales and distribution transaction.
13. These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to be shipped.
14. It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage location level. This indicator is used to set the scope of the availability check.
15. It is used to switch off the check at storage location level. You create a reservation for a particular storage location. However, the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system carries out the check at plant level only and does not take the storage location into account that is specified in the reservation.
16. Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material to become available. It is only used when doing an ATP check and is taken from MMR.
17. Defining the elements in the availability check entirely depends on the business needs, but a few tips are given under
When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is going to come into the plant.
A shipping notification on the other hand - a confirmed purchase order is a good indicator of receiving stock on a specified date.
It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually receive the stock into plant or warehouse for which you are creating a delivery.
Please Reward If Helpful,
Thanks and Regards,
Sateesh.Kandula

Production order q's

Hi all ,
1) What should be the selection criteria in COOIS for open production order list for the one month frame ?
2) How can we know that for a production order Overhead , Varience, Settlement has been carried out if the production
if the order is not having the status CLSD ?
thanks in advance
Regards

Hi Venky,
specify production order status excluding DLV, CNF and period to get open production order in COOIS.
specify corresponding Production order statuses in selection screen of COOIS.
Regards,
Krishna Mohan

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

Production Order Cost Analysis - Goods Receipt

I have been assigned to create analysis of production orders. I need to show the volume variance as well as the cost variance using both the initial planned costs as well as the actual costs when the production order is completed. All this information is available in COR3 on cost analysis, but I need to allow for display of multiple orders based on plant and date information.
I have found that the ingredients are in the table RESB with most of the information that I need, I have not had luck in finding what table has the goods receipt information (produced product). SAP help says that the fields are in KKBCS_OUT, which is a structure that I can't find where populated from.
I would appreciate any assistance in this endeavor.
Thanks
Steven M Engel

Thanks for the suggestions, but they have not provided me with what I think I need to give a solution to my superiors.
I will attempt to clarify what I need to do. We are a manufacturing facility. We have a BOM that says to make 10 E, I need 3 A, 2 B, 3 C, and 4 D. Each of the components (A to D) have a set cost at the time the production order is created, this looks to be saved as part of the planned cost in RESB. Produced product E also has a planned cost at time production order created (as seen by COR3) but that is not stored in RESB.
At production time we actually use 2.5 A, 2.5 B, 3 C, and 5 D to make the 10 E. COR3 cost analysis is showing me the cost variance. This cost variance has two parts, part 1 is because the quantities of the inputs are different. Part 2 is because between the time the production order was created, and the production order was finished, the costs of A to E may have changed.
I need to breakout the different components to show management how much of the total cost variance is attributed to each part. I need a report that management can run (or have run) that will allow them choose by plant, date, end product, etc. so they can direct what changes need to be made to costing, pricing, and BOMs.
I hope that I have laid out what I am trying to do in a coherent manner. Also I am new to the SAP system with less than 1 year using the system.
Thanks for your time.
Steven M Engel

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

Purchase link Production order

HI Guru's,
I have requirement. The process like Buying material from Vendor and consuming for local production order and export production order.
We are creating sales order--> Planorder ---> Production order after MRP run.
The requirment is when iam using the material for local production order i will pay to the vendor is 100 INR
When i consuming material forexport production order i will pay to the vendor is 200 INR.
How to config in SAP.
Regards,
Kumar

Hi Ramakrishna,
If I rephrase your scenario then its like that you have a component which is procured externally. When there is a local Order, you procure the component and at 100 INr and if its for imported 200 INR. Are you using two different material codes for Header material i.e for which Prod. Order is created.
Anyways if your component which is procured externally at 2 diff. prices and under same material code then you can address this thru split valuation.
Ask your MM person to do the basic config.

Splitting the cost of Production Order

Hello Sapians,
We have a situation where a purchase order has all of its costs going to one production order but the services provided
on the purchase order were actual for three production orders. What is the process for adjusting this amount for the
production order costing?
For example, PO number is 10001 and this is currently all being charged to production order 60003. I would like
15000 USD be moved to both production orders 60001 and 60002.
Do we have any process of splitting the amount to two different Production Orders in SAP?
Thank you,
-Harter.

Hi Ajay,
I checked the Order and there are some actions after the Production Order is settled.
For example: The Order got settled twice in 12/10/2010 and 01/31/2011. And the Variance was there when settling the Order second time and it was also settled on 01/31/2011.
There are some operations that are on the Production Order before and after the second settlement dates. Even after 01/31/2011 month's settlement I can see some charges on the Production Order from the operations (Subcontracting, Overhead PRD, Personnel Hr)
My questions and doubts are
1. Do I need to reverse both the months settlements?
2. What are the impacts of the reversing the settlements on the other operations that were executed before and after the Order is settled? (Operations are Subcontracting, Overhead PRD, Personnel Hr).
Thank you,
-Harter.

Production order print program

Experts,
could some one please help me understand the following terms and functions in very layman terms
1. print program (report name?), form routine, sap scriptform with respect to Production order in OPK8. Can some one please explain who each one of these is interlinked when printing an order
2. what is output type and why it is not necessary for production order? I mean why standard sap does not provide output type for production order.

Hi there,
I would like to suggest to check out some information / available documents which will give You a good overview, such as general OSS note about prod. order printing; ex. 11104 is a good one:
http://www.sapossnotes.com/2010/12/sap-note-11104-pppr-general-note-on.html
Here You could also find, that there is no output type but list name - used in prod. ord printout forms.
I hope this will help.
Br

Personal ID on Production Order Confirmations

Hi everybody,
Please advise on this scenario. We have 10 work centers in the shop floor. We setup 4 data collection stations (computers) to perform confirmations on production orders... we have around 100 technicians available to work on the production orders, which have average of 10 operations... We setup specific sap user ids for each data collection station, but we want to know how perform the confirmation, SAP records the confirmation under the generic user id of the data collection station as the creator of the confirmation but we want to know who performed/reported it... is there an easy way to assign/use a personal id for each user without creation new SAP accounts for each technician and/or activating HR module?... A personal ID number is available on the confirmation screen but we donu2019t know how to configure it... please your advices will be appreciated...
Regards,
Alfonso Gilson

Thanks Bakhtiyar for looking into my question...
I found this forum is more for Manufacturing Execution using external systems... I think. Interface with system like MES, am I orrect?. In our current solution we are not using any external system or application. We setup in the shop floor 4 work stations (computers) where the technicians perform the confirmations. We customized a tcode to combine CO11N and IW41 in one screen, in the backgroup the program identify which tcode to use nase on the order type. In this way users donu2019t need to know which transition they need to use/execute for confirmations. The users login in this machines using a specific SAP user id/password, and this is the user id that is saved in the confirmations as creator. Now, we want to know who was the technician that performs each operation. As I mentioned we have around 100 technicians in the shop floor and they donu2019t have an user id/password setup, it will be too hard to maintain... We call these stations "Data Collection" because they scan the order and/or ticket numbers as a first step to perform the confirmations, then they enter the time and save it... simple...! But we want to track each person.... I was looking into the personnel id number, but looks a configuration in HR is required... we need an easy flag that later we can display on reports... I hope i provided more details...
Assigning a specific SAP user id to each technician is not practical... Iu2019m wondering how you guys deal with these scenario in the pass. Customized a table to track the notes / texts on the confirmations? I hope this is not the case...!!!! Thanks for any input on this question...
Regards,
Alfonso

Worklfow for GR of Production order.

HI .... is there any standard worflow template for GR of production order using MB31.
Thanks in advance.

Hi ,
Please check this SAP provide WF: WS20000387.
You can copy and make changes as per your requirement.
Thanks and Regards,
Swaminathan

Scheduling Parametrs for the Plant and Production Order Type

hi SAP Gurus,
Pls it is very urget
Pls let me know how to maitain the Scheduling parameters for the combination of Plant and Production Order type.
Pls provide me the Path also.....
Points will be rewarded .....
Ranjit Kumar

hi Murthy,
thanks for the solution... Problem resolved.
Assigned points...
Ranjit

Production order to Exclude "Stk provided to vendor" in availability Check

Similar Messages

Maybe you are looking for