Trsct CO11N, how to confirm a prod. order withoout confirming activities?

Hello
We are using transaction CO11N to confirm production orders
Our production orders have several operations.
The last one creates the goods movement (control key PP03).
In the others operations we have several activities each one with a standard time taken from the routing.
Since we are not immediately informed about the time spent by the workers to do each activity, we would like to post the good receipt as first and only after we would like to confirm each operation with the right minutes for each activity.
But when we post the goods movement in the last operation, the system confirms automatically all the activities in all the operations using the standard values even if in transaction Co11n the fields activity's values are empty.
How can we post the goods movement without confirming activities so that we can confirm later the activities with the right values? I think I have to change some settings somewhere but I cannot understand where.
thanks
Regards
Giacomo

Hi,
you could always turn off auto gr feature so confirmation with co11n is seperated with mb31 gr production.
But if you still want to use as is config you can just left the activity blank and you branch to good movement to do auto gr and you can save it.
For your additional info : ypu can set whether the activity qty is proposed manually or not by setting confirmation paramater or single screen entry confirmation parameter.
I hope it helps
Best regards,
Freddy Ha

Similar Messages

How to stop the Confirmation of Prod. Order if GI to Prod Order not done?

Dear all
I am new to PP. Please bear with me with this silly question.
My user always forgets to perform GI to Order using MVT 261 and straightaway go ahead with Confirmation of Production Order (CO11).
It does give rise to some problem that some of the raw materials have been marked as Final Issue in Components Overview of Prod. Order but in real life, those raw materials are still sitting in the warehouse.
Please advise what can I do in system configure so that If GI to Order (MVT 261) has not been done, user is not allow to perform Confirmation of Prod ORder?
THanks in advance!

Hey,
GO TO
BS02
1) Create Status Prof with name XYZ,
    D.click on Status Prof, Select Object Type as PP/PM
    Go Back, now
    You will find a user status table
     Create status in status tab with two options,
               Status   Short text                                   int st
    Say 1) XY      Confirmation not allowed.          tick box
           2) YZ       Confirmation allowed.
Double click on XY Click on Create , You will find sum options with status like allowed, forbidden etc..
Now go to confim Order tab
1) Goods Movement             Set radio button on both 'Forbidden' and 'no activity' Button.
Now go back to user status Again, Double click on YZ button,
Again click on Create Button , You will find same options with status like allowed, forbidden etc.. this time you give set for
two options
1) Confirm Order                Set Radio Button on both 'Allowed' and 'Set'
2) Goods Movement           Set Radio Button on both 'Allowed' and 'Set'
Save the Request.
Go to Order type Parameter assign the Status Profile XYZ to Your Order Type.
This will work out,
Solve Your Problem.
As a Result,
In initial stage system will check the Confirmation status before GI, if Conf is not done system will give error.
If confirmation is done the system changes its status , allows the GI by Checking the Status .
Thank Regards,
J.K.Pavan Kumar.
SAP PP-PI.

How to confirm the CO Production Order?

Hi,all
The PP Production Order can confirm by TCode CO15.
Then how to confirm the CO Production Order(Created by KKF1)?

Hi,
As you are aware that Co Production Order is being used when there is no quantity structure. Hence, there shall be no routings with details of activities and the quantity of activities, etc and we cannot use confirmation as we are doing in regular Production Corder. Consequently, we are left with one alternative of passing on the activity cost(qty x price) to the CO Production through Direct Activity Allocaiton(KB21N).
Trust this helps much!
Cheers!

How to Confirm the SDAs deploy order of SCA in RemoteGUI of SDM

Hello everybody,
       We assemblied a sca file in NWDI when we finished development.
       But when we used RemoteGUI to deploy the SCA file in another NetWeaver2004s engine.The Deploy order is wrong.The SDM doesn't first deploy the Library,EAR.It deployed the SDA ordering by the letter order ,not the dependence order.
       For example,there are two SDA in the SCA file, one's name is <b>d_lib</b>,another name is <b>a_ear</b>.The a_ear depend on the d_lib.When SDM deploy the SCA,it first deploy the a_ear,not d_lib.
      How to Confirm the SDAs deploy order of SCA in RemoteGUI of SDM?

Hi Marc,
Thanks for your help!
I found the Prodiver.xml,and the content is:
<?xml version="1.0" encoding="utf-8" ?>
- <provider-descriptor>
<display-name>om/library</display-name>
<component-name>om/library</component-name>
<description />
<major-version>7</major-version>
<minor-version>00</minor-version>
<micro-version>0</micro-version>
<provider-name>pjs.com</provider-name>
- <jars>
<jar-name>pjs.comomwcalistwcalist_daoWcalistPackage.jar</jar-name>
<jar-name>pjs.comomlogequipdao~daoPackaged.jar</jar-name>
<jar-name>pjs.comomnotificationnotification_daoNotificationPackage.jar</jar-name>
<jar-name>pjs.comombasedaodaoPackaged.jar</jar-name>
<jar-name>pjs.comomlogareaareadaopackaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoPostPackage.jar</jar-name>
<jar-name>pjs.comompostpost_daoSpecialtyPackage.jar</jar-name>
<jar-name>pjs.comomtaskdaopackaged.jar</jar-name>
<jar-name>pjs.comomgradeprojectgradedaopackagSDA.jar</jar-name>
<jar-name>pjs.comomlogreconlredaopackaged.jar</jar-name>
<jar-name>pjs.comomsafeexcepreportExcepReportPackage.jar</jar-name>
<jar-name>pjs.comomsaferecorddaoapi.jar</jar-name>
<jar-name>pjs.comomlogelogelogdaopackaged.jar</jar-name>
<jar-name>pjs.comomsysdaopackaged.jar</jar-name>
<jar-name>pjs.comombasevindbasedaopackaged.jar</jar-name>
<jar-name>pjs.comomlogsearchpersondao~SearchPersonSDA.jar</jar-name>
<jar-name>pjs.comomplacarddaoplacardPackaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoPersonPackage.jar</jar-name>
<jar-name>pjs.comomsbillrecorddaosbillRecordPackaged.jar</jar-name>
<jar-name>pjs.comomdutyperson_dao~DutyPersonSDA.jar</jar-name>
<jar-name>pjs.comomrptdaoRptSDA.jar</jar-name>
<jar-name>pjs.comompostpost_daoEquipmentPackage.jar</jar-name>
<jar-name>pjs.comomlogtypelogdaopackaged.jar</jar-name>
<jar-name>pjs.comomsafeproeval_daoProEvalPackage.jar</jar-name>
<jar-name>pjs.comompersonpostdaopackaged.jar</jar-name>
<jar-name>pjs.comomlogsearchlogdao~SearchSDA.jar</jar-name>
<jar-name>pjs.comompublic~packaged.jar</jar-name>
<jar-name>pjs.comomspellgroupdaodaoPackaged.jar</jar-name>
<jar-name>pjs.comomlogpersonlogdao~packaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoRlogPackage.jar</jar-name>
<jar-name>pjs.comomschedule_dao~ScheduleSDA.jar</jar-name>
<jar-name>pjs.comomreportrptdaopackaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoRecordClassPackage.jar</jar-name>
<jar-name>pjs.comompostpost_daoReqpPackage.jar</jar-name>
<jar-name>pjs.comomlogshiftclassdao~ShiftClassSDA.jar</jar-name>
<jar-name>pjs.comomverifyrecorddao~RecordPackage.jar</jar-name>
<jar-name>pjs.comomunit_dao~UnitSDA.jar</jar-name>
<jar-name>pjs.comomdatadefinedefdaopackaged.jar</jar-name>
<jar-name>pjs.comomheader_dao~HeaderSDA.jar</jar-name>
<jar-name>pjs.comomspellspedaopackaged.jar</jar-name>
<jar-name>pjs.comomlogrecdlcddaopackaged.jar</jar-name>
<jar-name>pjs.comomlogsearchequip_dao~SearchEquipSDA.jar</jar-name>
<jar-name>pjs.comomcompanycomdaopackaged.jar</jar-name>
<jar-name>pjs.comommaceasyformdao~daoJAR.jar</jar-name>
<jar-name>pjs.comomdeclaredecdaopackaged.jar</jar-name>
<jar-name>pjs.comompostpost_daoFunlcodePackage.jar</jar-name>
<jar-name>pjs.comomlogeventlevdaopackaged.jar</jar-name>
<jar-name>pjs.comomclient_dao~ClientSDA.jar</jar-name>
<jar-name>pjs.comomlogdepldedaopackaged.jar</jar-name>
<jar-name>pjs.comomlogceqplceqdaopackaged.jar</jar-name>
<jar-name>pjs.comomrptinforptdaopackaged.jar</jar-name>
</jars>
</provider-descriptor>
I checked it and didn't find any error! What can i do?

Prod order confirmation cancellation for milestone op

Dear SAPper,
I want to cancel confirmation in prod order, let's say prod order has 2 operation
0010 control key with milestone
0020 control key with milestone with autoGR
This prod order has been confirmed.
I confirm op 0010 first because it is needed before i confirmed 0020
and the i confirm 0020 with autoGR
But when i want to cancel all the confirmation with CO13
Why i can cancel operation 0010 without cancelling operation 0010?
i think with 2 operation mile stone i must cancelled 0020 first before i can cancelled 0010
Is there any idea? please help.
Best regards,
Freddy Ha

Hi,
I have tried in OPK4 i have set it to E.
But in CO13 i still can cancelled op 10 without cancel op 20.
As i read in help file, it is for only check the confirm operation qty must adhered to previos conf qty.
Did i still miss something?
any idea is appreciated
Best regards,
FreddyHa
Edited by: Freddy Halim on Mar 25, 2009 2:52 AM

How to confirm activity for Internal order having object class PRODUCTION

Hi,
We have Internal order which has object class PRODUCTION. In it material and labour cost got confirmed
Here my doubt is how can I check the activity confirmation details in the system (Not CO15)
In otherwords how can I display internal order activity confirmation
I ll be grateful anybody answer quickly
Regards
Sneha

Hi Sneha
1. You can use KB21N - Screen variant ALL
2. If you want to check any postings on this Interna order - Use KOB1
Regards
Ajay M

How to confirm operation wise confirmation.

Hi,
   please tell me how to confirm operation wise confirmation in details.
       Thanks
        parag

Hi Parag,
Confirmation against a production order can be done in 2 ways :
1. Confirmation against each operation of an Order can be done in Tcode : CO11 /CO11N
2. Order Confirmation can be done in Tcode : CO15.
My understanding about your problem is you want to confirm operation wise and the procedure for the same is goto Tcode : CO11N and enter the production order number and Operation number say 0010 and enter the Yield/ Scrap qty and save it. If there are any components assigned to operation 0010 as back flush in routing / order, then system will consume those bom items with movement type 261. You can check the components which are assigned to this operation with backflush in teh goods movement Tab screen in Tcode : CO11N itself.
Next Enter the Prod order number and the next operation number say 0020 and enter the same yield qty as operation 0010 or different qty and save it. If any back flush items are assigned to this operation then on saving system does goods issue (with movt type 261) for those items.
After saving you can check the goods movement in the prodution order Tcode : CO03. Goto document goods movement s and chk the same. For showing this the order type dependent parameters should be configured for the same.

Capturing scrap in CO11N-time ticket confirmation

Dear All,
I would like to know how system is allow capturing of scrap in time ticket confirmation though total yield is confirmed.
Case-
Order created- I have production order number say 1000001 having 3 operations and total quantity of order is 100. There is no planning scrap in order.
confirmation -i have confirmed first and second operation as total yield for 100 each. After confirming total yield quantity of 100 for first operation, if i have enter again 10 quantity as a scrap for first operation, system is allowing to do so.
Query - Is this a standard behaviour of the system?, how system is allowing though i have confirmed total quantity of yield for the first operation.
Plz suggest how to control if total quantity is confirmed system should not allow to enter surplus quantity in scrap field of time ticket confirmation.
Regards,
Rajesh Sawant

Dear Rajesh,
This is standard only. When you are doing confirmation, system will not see the production order quantity against your confirmation quantity. Whatever quantity you are confirming will be stored against the production order.
Let say Prod. order no 1000001 need to produce 100 no.
In 1st operation yield -110 no. and crap - 0 no.
In 2nd operation yield - 105 no. and Scrap - 5 no.
In 3rd operation Yield - 100 no. and Scrap - 0 no.
So for this particular production order to produce 100 units, you have issued 110 units. Here yield can be number of units.
Hope you will understand.
Regards / US

Material staging only for released prod order parts

Hi Experts,
Could any of You pls help me to set material staging only for components of released production orders?
There is a PP-WM integrated system, where we have mat.staging indicator 3 in control cycle, and run MF60 for WMreleased order parts. Here all CRTD and REL prod order components are listed. But I would like to change it: only REL prod order parts should be seen and replenished.
Could You pls let me know, how to do that?
Answers will be apprecited

Eshwer,
If a material has its own production order then it should be closed ,Closed in the sense you have to do theVariance Calculation,Order Settlement & finally Close the order
So irrespective of whether the material is of FERT or HALB type,each production order need to be closed
Closing the FERT order will not suffice ,It will not take care of the HALB order
Order Settlement
When a production order is settled, the actual costs incurred for the order are settled to one or more receiver cost-objects (for example, to the account for the material produced or to a sales order). Offsetting entries are generated automatically to credit the production order:
If the costs for the production order are settled to a material account, the order is credited each time material is delivered to stock. The material stock account is debited accordingly.
If the costs for the production order are settled to another receiver (for example to a sales order), the order is credited automatically at the time of settlement. The cost-objects are debited accordingly.
Closing a Production Order
The Closed (CLSD) status has been introduced in the production order. It has the following characteristics:
No more costs can be posted to the order, that is, confirmations and goods movements are no longer permitted for the orderThe order can no longer be changed. Exceptions to this are revoking the CLSD status and setting the deletion flag.
All actions relating to the status technically completed (TECO) are executed.
In a collective order, the CLSD status is also set for subordinate orders.
If the system comes across an order in the collective order that cannot be closed, the orders that come between this order and the leading order are also not closed. Other subtrees are closed if they only contain orders that can be closed.
So for the above reasons all the individual orders need to be closed
Hope the above is clear
Reward points if useful
Regards,
SVP

WIP quantity in prod order

Dear All
The PP process in our client is like this,
One material is produced thru 10 operations, input material is 100 nos ROH, for producing 100 nos FG
now i created one Prod order for FG - 100 nos
and CNF the first opperation - qty cnf is 100 nos , All ROH is consumed to that opp,
Partial CNF second opperation 50 nos (balence to be cnf is 50 nos)
and third opp. 30 nos (Balence to be cnf is 20 nos at this time)
4th operation 20 nos(Balence to be Cnf is 10 nis at this time)
now how can i see the WIP quantity lying for the 3rd opp. and 4th operation
PL give mw the solution.
Thanks in Advance

Hi,
For this there is no STD SAP report. You need to develop on your own. Confirmed qty you can see in COOIS transaction. But you can't get the remaining confirmation qty as a Report.
Regards,
V. Suresh

Amending order qty in prod order

Hi, We need to amend the prod order qty incase of any rejections or scrap during manufacturing. How toimplement the same.

YS,
You can amend the order quantity whenever required, untill it has following statuses, either DLFL, TECO, LKD, CLSD.
You can change the order quantity in the order change mode i.e. CO02.
As soon as the order quantity increases the corresponding component quantity will be effective for the order.
Also the operation will be needed to be confirmed for this extra quantity.
Another option is of rework order.
Hope this helps you.
SmanS

WIP calculation for Prod.order with status TECO

Hello all.
My question is the similar to WIP calculation for Prod.order with status DLV
But I need that
- if the Production order has status TECO - the system calculate WIP
- if the Production order has status DLV u2013 the system settle the order.
1. I try to change u201CStatus Numberu201D in TCODE OKGC. But I have receive two different result:
- if I change u201CStatus Numberu201D for status DLV from 3 to 2, then during WIP calculation of the order with status DLV u2013 WIP have been calculated.
- but if I change u201CStatus Numberu201D for status TECO from 4 to 2, then during WIP calculation of the order with status TECO u2013 WIP have been CANSELED.
2. I try to change results analysis key for status TECO from u201CZu201D to u201CFu201D in TCODE OKG3. BUT during WIP calculation the system create error message KJ 363 which require that results analysis key must be change to u201CZu201D
How can I resolve my problem?

Hi,
I don't have the answer if the requirement is that even after producing the materials, till the time accountant checks the order and does this action, it should remain in WIP. Honestly it doesn't make any sense to me or i have not understood this problem. Anyways as per my current understanding I can suggest the following process for your scenario.
Once production is stopped in between the process, the order should be in PDLV status (partial confirmations happened in the order)
Now go and clear the reservations manually from the production order .( delete the component line items from the order). Now depending on whether you are following WIP at actual cost, system will post the difference between credit and debit of that production order as WIP for the month end process.
Once Accountant okays the entries in the production order, he can do the TECO and settle the order. Now WIP will be reversed and variance will be posted.
To avoid the already produced goods mixing up with your other stock, u might want use Quality Management with the help of your PP consultant.
Best Regards
Vimal

Time booking against prod order

How can I book the operator time in a prod order.
Is it needed that I should manitain the operator ID i

Hi,
You will have to configure the resource such that you have the standard value key to capture the operator hours. So when you do the confirmation of the operation, you can maintain the operation or labor time. You can define custom fields for operation where-in you can have provision to mention the operator ID if required during confirmation.
You can then run various SAP standard reports (COOIS) to fetch this information. Try it and revert back.
Regards,
Swapnil

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

Converting SNP Planned Order /Purch Req to Prod.Order/Purch.Order

Guys
What is the standard process to Convert the SNP Planned Order /Purch Req. into a Prod.Order/Purch.Order ?
Can the conversion indicator be set in APO for SNP Planned Order /Purch Req.and then transferred to R3 as Prod.Order/Purch.Order or can the convesrion of Planned Order /Purch Req to Prod.Order/Purch.Order can be done in R3 itself ?
I am not clear on how exactly this works. Would appreicate if you could provide me with the standard process and any config involved in the same such as Number Ranges and how to set the conversion indicator automatically through SNP planning runs ?
Thanks

When you set this indicator for a planned order or a purchase
requisition, the system automatically converts the order into a
Production order or purchase order after the transfer to the
connected SAP R/3 system.
The converted orders are then retransferred to the SAP APO system with a
different category; a purchase requisition with category BS-ANF becomes
a purchase order delivery schedule line with category BS-EIN.
Please check configuration setting in SPro for transfer setting to R/3.
1. Configure Transfer to OLTP Systems(SNP)
2.Maintain Global Parameters and Defaults(PPDS)
Also on R/3 side you can see it in MD04/MD07 collectively for a product . or individually on
MD13 : planned order
MB51n: PR
Manish

Trsct CO11N, how to confirm a prod. order withoout confirming activities?

Similar Messages

Maybe you are looking for