Rework Order Creation Problem

Hi,
I have created trigger point in routing. I have also maintained the scheduling parameters for new order type for rework order. When trigger activates during confirmation it goes to the Rework order creation screen but gives the message of
"Scheduling parameters are not defined for production orders"
It is not picking the parameters.
Regards
HHS

Plz also check the assigned rework workcente to the operation.
Apart from order type scheduling parament .You have to consider the master too.Plz check and let us know

Similar Messages

Purchase order Creation Problem

Dear All
For Local purchase NB order creation SAP Asking the Account assignement category.
for only particular plant ,It should ask only Service orders. but why its asking the NB orders.
Even Valuation grouping code already assigned for that plant.
Any other settings required..
Please guide..
Regards
Kumnar

Dear All
For Local purchase NB order creation SAP Asking the Account assignement category.
for only particular plant ,It should ask only Service orders. but why its asking the NB orders.
Even Valuation grouping code already assigned for that plant.
"System Throughout the error "Account assignment mandatory for the material 200011"
The material type is verp. and accounting view already extented for this plant
Any other settings required..
Please guide..
Regards
Kumnar

Planned order creation problem

Hello everybody,
When I am creating a planned order manually in MD11, I receive the message "Planned order xxxxx will be created".
Then I receive a popup window telling me "Express document 'Update was terminated' ".
But, when I am having a look in MD04 to see the planned order, I can't see it.
It was still okay yesterday morning, but since yesterday afternoon, no more planned orders can be created manually. Do you have an idea about what can be the reason of this?
It's just like if the order creation was delayed... But for how long, and waiting for what???
Thanks in advance for your help.
Regards,
Rudy

Hi,
There is something issue with ur data while saving..hence it is not saving and throwing the message. so that while upadting data in table is not acccepting.
GOTO SM14->click on ALL UPDATEREQUESTS push button->U will find the reocrds,select ur userid and double click on it,now u can see the module name,select it and double click on it,now u will get one small dialog box,there u can find the abap editor symbol ,click on it..it will take u to the program where it has taken place
Please refer this thread,
Update was terminated
Regards,
R.Brahmankar

Automatic rework order creation

Hi,
I have 7 operations in routing . at the time of operation level confirmation when I will put quantity in rework system should generate rework order for the rework Qty.I have two different Order types.
Regards,
Manoj Jadhav

Hi,
Please fallow the below steps for auto rework order.
1) Create Reference Grp - CA11
2) Create Std Trigger Point - CO31
Select Create Order With Reference & enter system status as PCNF/CNF. Enter parameterfor the selected function as reference grp & seperate order Type for rework, if available.
3) Use this trigger point in the opration where you want trigger & select the indicator for Trigger point used for trigger point functions.
4) Create the production order.
5) Do partial/fully confirmation with rework quantity. Then, system should propose to create the rework order quanitity eq to rework quanity.
Rgd,
Chetan

Process order creation problem

I am creating a process order . while creating the process order system is throwing error as Auto batch numbering not set up for material type XXXX in plant xxxx . System is not allowing to create process order.
How to resolve the issue.

Check in CORW and switch off batch creation to isolate the problem if needed. Also see whether you have any batch managed compoents for which you have set master data for automatic batch determination.
There is no setting for material types and plant for batch. May be the error message is not correct. What is the message number?

Service order creation problem

Hi Experts, I have a requirement to create a Service order using a BAPI. I'm trying to use the BAPI BAPI_BUSPROCESSND_CREATEMULTI. I found some code related to this BAPI on this forum . THE service order is created
but ibase / component is not filled . How can i give the Ibase through the bapi and in which parameter of the bapi i have to fil this. Could anyone please help me figure out what the problem is . my code is as follows.

Please find the code current thread and below thread.
FUNCTION ZBAPI_SERVICE_SORDER2.
DATA : IS_HEADER            TYPE TABLE OF      BAPIBUS20001_HEADER_INS,
        WA_HDR               TYPE               BAPIBUS20001_HEADER_INS,
        IS_ITEM              TYPE TABLE OF     BAPIBUS20001_ITEM,
        WA_ITEM              TYPE               BAPIBUS20001_ITEM,
       IT_ACTIVITY             TYPE TABLE OF      BAPIBUS20001_ACTIVITY_INS,
       WA_ACTIVITY           TYPE               BAPIBUS20001_ACTIVITY_INS,
        IT_PARTNER             TYPE TABLE OF      BAPIBUS20001_PARTNER_INS,
        WA_PARTNER           TYPE               BAPIBUS20001_PARTNER_INS,
        IT_SALES             TYPE TABLE OF      BAPIBUS20001_SALES,
        WA_SALES             TYPE               BAPIBUS20001_SALES,
        IT_ORG             TYPE TABLE OF      BAPIBUS20001_ORGMAN_INS,
        WA_ORG               TYPE               BAPIBUS20001_ORGMAN_INS,
        IT_PRICING             TYPE TABLE OF      BAPIBUS20001_PRICING,
        WA_PRICING           TYPE               BAPIBUS20001_PRICING,
        IT_SERVICE           TYPE TABLE OF      BAPIBUS20001_SERVICE_OS_INS,
        WA_SERVICE           TYPE               BAPIBUS20001_SERVICE_OS_INS,
        IT_RETURN              TYPE TABLE OF     BAPIRET2,
        WA_RET               TYPE               BAPIRET2,
        IT_PROD             TYPE TABLE OF      BAPIBUS20001_PRODUCT,
        WA_PROD              TYPE               BAPIBUS20001_PRODUCT,"PROCESS_QTY_UNIT -EA
*        IT_SCHED             TYPE TABLE OF     BAPIBUS20001_SCHEDLIN, "QUANTITY
*        WA_SCHED             TYPE              BAPIBUS20001_SCHEDLIN,
        IT_SCHEDLINEs         TYPE TABLE OF     BAPIBUS20001_SCHEDLIN,
        WA_SCHEDLINEs         TYPE              BAPIBUS20001_SCHEDLIN,
        lv_partner_fct1      TYPE               crmt_partner_fct,
        lv_partner_fct2      TYPE               crmt_partner_fct,
        lv_partner_fct3      TYPE               crmt_partner_fct,
        lv_partner_fct4      TYPE               crmt_partner_fct,
        LV_HANDLE            TYPE               CRMT_PRP_HANDLE,
        t_object_to_save     TYPE               crmt_object_guid_tab,
        IT_OBJECT_TO_SAVE    TYPE TABLE OF      crmt_object_guid_tab,
        ts_object            type               CRMT_OBJECT_GUID,
        It1_object_to_save   TYPE TABLE OF      BAPIBUS20001_GUID_DIS,
        W_OBJECT_TO_SAVE     TYPE               BAPIBUS20001_GUID_DIS,
        LV_LOG_HANDLE        TYPE               BALLOGHNDL,
        IT_RETURN1              TYPE TABLE OF     BAPIRET2,
        it_saved_objects     type             crmt_return_objects,
        t_exceptions         type              CRMT_EXCEPTION_T,
        t_objects_not_saved type              CRMT_OBJECT_GUID_TAB,
        WA_INPUT_FIELDS      TYPE              BAPIBUS20001_INPUT_FIELDS,
        IT_INPUT_FIELDS      TYPE TABLE OF     BAPIBUS20001_INPUT_FIELDS,
        ITAB_CREATED_PROCESS TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
        WA_CREATED_PROCESS   TYPE              BAPIBUS20001_HEADER_INS,
        IT_OBJECTS           TYPE TABLE OF     BAPIBUS20001_OBJECTS,
        WA_OBJECTS           TYPE              BAPIBUS20001_OBJECTS.
DATA:   CV_LOG_HANDLE        TYPE              BALLOGHNDL,
        i_saved_objects      type table of     BAPIBUS20001_OBJECT_ID,
        IT_RET2              TYPE TABLE OF     BAPIRET2,
        WA_SAVed_objects     type BAPIBUS20001_OBJECT_ID,
        g_objnr              type CRMT_OBJECT_ID.
DATA :
        LV_GUID1   TYPE       GUID_32,
        LV_GUID2   TYPE       GUID_32,
        LV_GUID3   TYPE       GUID_32,
        V_OBJNR22 TYPE       IBIN-OBJNR,
        V_GUID16     TYPE       COMT_PRODUCT_GUID,
        V_OBJID    TYPE       COMT_PRODUCT_ID.
*************HEADER-GUID**********
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    EV_GUID_32       = LV_GUID1.
***********ITEM-GUID************
CALL FUNCTION 'GUID_CREATE'
IMPORTING
   EV_GUID_32       = LV_GUID2
*********SCHEDULELINE********
CALL FUNCTION 'GUID_CREATE'
    IMPORTING
      EV_GUID_32       = LV_GUID3
************DATA IN HEADER**********
WA_HDR-GUID = LV_GUID1.
WA_HDR-PROCESS_TYPE = 'YESV'.
WA_HDR-DESCRIPTION = PROCESS_DESCRIPTION.
APPEND WA_HDR TO IS_HEADER.
*************** INPUT FIELDS HEADER**************
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'GUID'.
wa_input_fields-fieldname = 'MODE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'PROCESS_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'DESCRIPTION '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN ITEM**********
WA_ITEM-GUID = LV_GUID2.
WA_ITEM-HEADER = LV_GUID1.
WA_ITEM-ORDERED_PROD = PRODUCT.
WA_ITEM-DESCRIPTION = PROD_DESCRIPTION. "product name
WA_ITEM-ITM_LANGUAGE = 'EN'.
WA_ITEM-ITM_TYPE = ITEM_CAT.
WA_ITEM-NUMBER_INT = ITEM_NO.
WA_ITEM-MODE = 'A'.
INSERT WA_ITEM INTO TABLE IS_ITEM.
*******INPUT FIELDS ITEM*****************
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ORDERED_PROD'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'DESCRIPTION '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ITM_LANGUAGE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ITM_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'NUMBER_INT'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN ACTIVITY**********
WA_ACTIVITY-REF_GUID = LV_GUID1.
WA_ACTIVITY-PRIORITY = PRIORITY.
APPEND WA_ACTIVITY TO IT_ACTIVITY.
*************INPUT FIELDS SALES*************
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'C'.
WA_INPUT_FIELDS-OBJECTNAME = 'ACTIVITY_H'.
WA_INPUT_FIELDS-FIELDNAME = ' PRIORITY'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN SALES**********
WA_SALES-REF_GUID = LV_GUID1.
WA_SALES-PO_NUMBER_SOLD = SOLD_T0_PARTY.
wa_sales-ref_kind = 'A'.
APPEND WA_SALES TO It_SALES.
*************INPUT FIELDS SALES*************
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'SALES'.
WA_INPUT_FIELDS-FIELDNAME = 'PO_NUMBER_SOLD'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN PARTNER *********
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000001'.
WA_PARTNER-PARTNER_NO = SOLD_T0_PARTY .
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000014'.
WA_PARTNER-PARTNER_NO = EMPLOYEE_RESPONSIBLE .
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000056'.
WA_PARTNER-PARTNER_NO = SERVICE_EMPLOYEE_GROUP.
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000003'.
WA_PARTNER-PARTNER_NO = BILL_TO_PARTY.
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
*INPUT FIELDS PARTENER
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
wa_input_fields-ref_guid = lv_guid1.
wa_input_fields-ref_kind = 'A'.
wa_input_fields-objectname = 'PARTNER'.
wa_input_fields-fieldname = 'KIND_OF_ENTRY '.
wa_input_fields-logical_key = '0001'.
APPEND wa_input_fields TO it_input_fields.
wa_input_fields-ref_guid = lv_guid1.
wa_input_fields-ref_kind = 'A'.
wa_input_fields-objectname = 'PARTNER'.
wa_input_fields-fieldname = 'NO_TYPE '.
wa_input_fields-logical_key = '0001'.
APPEND wa_input_fields TO it_input_fields.
wa_input_fields-ref_guid = lv_guid1.
wa_input_fields-ref_kind = 'A'.
wa_input_fields-objectname = 'PARTNER'.
wa_input_fields-fieldname = 'DISPLAY_TYPE '.
wa_input_fields-logical_key = '0001'.
APPEND wa_input_fields TO it_input_fields.
as follows.
please find below thread.
Edited by: venkatrao veeramaneni on Nov 4, 2011 3:54 PM
Edited by: venkatrao veeramaneni on Nov 4, 2011 3:57 PM

Purchase order creation problem.. me21n

Hi All,
I have the following requirement in creation of PO.
When the Purchase Order of some type, say for eg. in my case its a custom type ZNB denoting intercompany pricing is created from a Purchase Requisition, the system should check the Account Assignment Category of the Items in Purchase Requisition. For the Item that has an account assignment category 9 indicating that the item is for free ( for eg. if a cylinder of chemical gas is considered , them the cylinder/ container should not be billed ), the flag Free should be ticked for this particular item. As a result the Pricing will not be applicable for such an item.
I would like someone to please throw light on how this can be achieved. is there any user exit to get this done ?
Thanks in advance ..
Sharat.

Hi Sharat,
the Badis ME_PROCESS_PO_CUST & ME_PROCESS_PO may be helpful to u...

Prod order creation problem

Hi PP gurus..
Pls help me in problem abt prod order..i creat material with type FERT with order type PP01and go through it all sequence but when i creat prod order abt same system show msg.valuation type INLAND is not allow in in house production..
Regards.and thanx in advance
Amit Naik

Hi
I think while creating material in MM01 you had selected the valuation type which is not define for INhouse production that you are getting this error. See setting for valuation type.
Regards
Abhijit Gautam

Sales order creation problem

dear all my friends
i want to create a sales order from the BAPi BAPI_SALESORDER_CREATEFROMDAT2 but i want to but the material bar code instead of material number in line item of table ORDER_ITEMS_IN - EAN_UPC put i found the flowing error
EAN 4006381157926 does not match material and unit of measure
what should i do

Seems like it's trying to input the scanned material number into the Unit of Measure field and hitting Enter. You need to configure your bar code scanner to hit tab after each scan Material number scan, Quantity Scan.

PO order creation problem

Dear All,
While I am trying to create a PO in dev client system throws an error message "Internal number assignment not defined (plz enter no)" . Message no :06243.
Plz let me know where I ll set this no range .
Regards
Abhijit Das

hi,
first you define no range in OMH6
second one -
go to ---material management -purchasing---purchase order -
define document type ---define insted of that document type which you are define assign the no range --- save
now create po me21n
thanks
santosh.

Error when creating rework order

Hi
When I am creatng a rework order for a material it is showing an error message that referance doesnt exist why is that error coming

Dear Pradeep,
Cofiguration Settings For Rework order
1) just copy std re-work order type & give new name as u required in OPJH
2) in OPL8, copy existing rework order type & give ur re-work order type & plant & save
Master data for rework order
1) CA11 - Creating reference operation set
1) after Executing CA11, just enter without giving data in initial screen
2) usage - 1, status - 4. from lot -1, then click on operations
3) then give work center & descrption
4) Double click on Description, then give timings for setup, machine & labour & save
Rework order Creation
1) Normally rework order is created by t-code CO07
2) while doing confirmation of header material in CO11N or CO15, we give re-work quantity
3) then creat re-work order in CO07
4) in CO07, give plant then order type (rework order type) then enter
5) materail description, quantity to be reworked then date enter
6) system will ask u refernece opeartion set (it should be created before only in CA11)
7) then give the referce operation set Number then system will take u to settelment Rule
8) here for CAT, give as ord, then in settelment receiver give ur header order number then percentage as 100 %
9) then clcik on component overview icon, then give ur BOM componets (which to re-worked & assign an opeartion to it)
10) then save the order
11) then do the confirmation to re-work order
12) then do GR to header order & settelment will take place to header order only not to re-work order
Note : For rework work, GR will not take place
Regards
Madhu

Automatic Rework Order

Hi Team,
Can you tell me the setting for Automatic Rework Order creation by the system when the product is rejected while confirming the production order.
Samar

Hi,
Pls follow the below mentioned procedure:
1. Create a Reference op set in tcode CA11.
Enter the plant, Description, usage and status
for the ref op set
2. Create a Standard trigger point in CO31.(Ex
Production)
Enter the Trigger Point usage /Group as FERT.
3.Tick the Trigger Point Functions.
4. Enable the indicator create order with Reference .
5.Enter the system status as PCNF.
6.The system will says standard trigger point exists from which you can
select the created Trigger Point (EXx Production)and save.
7. MD02/MD04.
8. Convert the Planned Order into Production Order and Release the order.
9 .Now confirm th ops.
10. For the last op enter the yield and rework qty
and set the status as PCNF.
11. If the status of last op is PCNF then in the
system a POP UP will appear as Activited by
Trigger Point /Create order with reference/order
number/sequence and op number which trigger point
works and enter.
12. Now a rework order will be created.
13. In c003 enter the number which is next to the actual prodn order no.Rework order will be seen.
Hope this helps.
Regards,
Tejas

BAPI - Problem in Sales order creation

Hi Friends,
I have problem in Sales order creation using BAPI ,I am getting a messsage - Error in creating document ,I have sent the code along with this mail ,can you help it out.
Code:
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
Regards,
Dinesh

what messages u are gettting in RETURN ? Please check the RETURN tables data.
[code]CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
EXPORTING
sales_header_in = header
sales_header_inx = headerx
IMPORTING
salesdocument_ex = v_vbeln
TABLES
return = return
sales_items_in = item
sales_items_inx = itemx
sales_schedules_in = lt_schedules_in
sales_schedules_inx = lt_schedules_inx
sales_partners = partner.
Regards
Prabhu

Problem in settlement of rework order

Hi
I have raised a production order and settled all the products in the order. But in quality inspection i have cleared only some quantity and made some quantity rework. I have raised a rework order for the same and settled the rework order.But the quantity is not settled to the main production order.Where is the problem in the rework order
Regards,
PradeepM.

Hi Pradeep,
Are you expecting
1. the rework cost in the rework order to be settled to the parent order or
2. the confirmed quantity in the rework order to be added to the parent order.
Up to my knowIedge I dont think the 2nd point will happen.
Let us confirm with other Experts opinion.
BR,
UK

Problem in process order creation.

Dear Sir/ Madam
i am facing a problem while process order creation.
the problem is:
Error when calculating cost for order ATFEDEC11 "see log Log is deleted when saving
Do you still want to save?"

Hi,
The log for production order preliminiary costing is not saved. Therefore, once the order is saved, there is no log available anymore (this is by the way a question of PP; none of the logs is saved).
Hope that helps...
Regards,
Declan

Rework Order Creation Problem

Similar Messages

Maybe you are looking for