Error during prdn order creation co01

Dear All,
During creation of production order by co01 a error message is generating i.e."13.05.2035 comes after end of factory calender" for some of my Fert materials only in one of my plants.Bom & Routings,Workcenters are valid for this FG & also for Sfg's which exists in as components in this fert material.At the time of availability check the system generates this error.Factory calender is valid for 2010 but if the error is due to validity of factory calender the system should generate error for all the Fert materials which we are producing in same plant which is not happening actually.The problem is for only a few of Fert materilas.Pls help suitable answer will be awarded with points.
Regards
R Sehgal

Hi Rakesh,
The problem i think should be in ur lead time for those materials for which the error is occuring.
See ur factory calender is valid up to 2010 but for some materials because of the order quantity and the lead time from routing its going beyond the 2010 ( means that order is getting scheduled beyond the2010) so it is giving the error.
Pls check the same and revert.
Regards,
Vinayak.

Similar Messages

Reg:error during transfer order creation

hi,
after quality inspection i move the stock into warehouse integrated storage location. if i clear inspection lot in qa32 for a material after saving it will pop up express message"error during creation of transfer order for a material".i configured that after qc inspection automatic TR is created.i just proceed with manual.
its a issue related with workflow or configuration....i checked with automatic TO all the things are deactivated.....where i am missing
Thanks
Muthuraman.D

hi,
goto VOV8
choose your sales order type
transaction flow - variant (remove the transaction variant if any)
but this will remove the transaction variant(custom) which you created , it will take the standard variant for your transaction VA01
regards
senya

Error during Production Order creation

Hi All,
Our's is MTO scenario. We have maintiain Account Assigment Category as 'M' in Requirement Type. During creation on production order with ref to sales order system gives error "Account assignment cannot be carried out because of different origin no."
If I create the production order with ref to quotation system does not gives any error. But my requirement is to create the prod order with ref to sales order.
Please guide
Regardsd

Hi Bala,
In SPRO goto>Sales and Distribution> Basic Functions-->
Availability Check and Transfer of Requirements
-->
         Transfer of Requirements
-->
             Define Requirements Classes
             Define Requirements Types
-->      Determination Of Requirement Types Using Transaction
Determination Of Requirement Types Using Transaction
In the standard system, requirements types are determined according to a specific search strategy beginning with the material strategy group.
Strategy for Determining the Requirements Type
1. First, an attempt is made to find a requirements type using the strategy group in the material master.
2. If the strategy group has not been maintained, the system will determine it using the MRP group.
3. If the MRP group has not been defined, the system uses the material type instead of the MRP group when accessing the corresponding control tables.
4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.
5. If this is not possible, a last attempt is made to find a requirements type with the item category only.
6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements.
Note
You can select an alternative search strategy in the 'Source' field, for example a transaction-related procedure for determining requirements type (source = 1 or 2).
Example
There are business transactions, such as consignment stock processing, in which the material with its planning characteristics is not important, rather the transaction itself. An issue from the customer's consignment stock should not trigger an availability check against planning at the plant as layed down by the planning strategy but rather against special stock.
Actions
1. Assign the item categories and MRP type to the requirements types.
2. Select an alternative search strategy in the 'Source' field if necessary.
By assigning the 1 or 2 to the Source you can have the requirements in MD04 refered to order instead of the initial source document which is usually quotation. If we don't assign this then the system by default refers to the initail document created i.e. Inquiry or Quotation whichever is the first document.
Regards,
Karthik.

Error during return order creation in CRM online

Hi all,
When I create return order via transaction CIC0 with reference to standard order ( B2C ) then some times system gives error after saving the return order. The text of the error message is very confusing , It says"
Message no. CRM_ORDER_MISC 020
Diagnosis
Errors have occured while transferring the document into another system. Remove the error messages from the enclosed log.
"Transmission log
Message no. CRM_ORDER_MISC 020
Diagnosis
Errors have occured while transferring the document into another system. Remove the error messages from the enclosed log.
Document xxxxxxxxxx doesn't have document category but (Notification E V2 068)
Sales document xxxxxxxxxx was not changed (Notification E V4 219)"
I have tried to replicate this return order with all the available tools but during save this message is coming from R/3.
Regards,

I would suggest you to try to create a return order in R3 system (from where the error is coming) with the same parameters.
Usually that should give you the same error... Resolve the issue, then try to create order in CRM online. Now error should not be there.
Regards,
Kaushal

Error during process order creation

while i create a process order following error is coming "recipe is empty"
please tell me where exactly i'm going wrong.

Dear Dhaval,
Welcome Back
Long time heard from you and nice to see your reply from long time
Good Luck !!!
Regards
Madhu

Error during Service Order creation

Hi,
I configure the Maintanance order for the plant and tried to create the Service ordeer for that Plant.
But system shows the Following Error Massage,
Field 'Additional Device Data' must still be filled
Can anybody guide me to proceed further on this
Thank You,
With Best Regards,
M.Suresh

Hi,
Thanks for your info PETEA.
Sorry Paul Meehan , I didn't see the field settings in OIAN properly last time.
There is a setting exist for field 'Additional data' as Mandatory. I removed this setting and tried to release the order and I succeeded.
Thanks Paul Meehan and PETEA for your Information.
M.Suresh

Error during purchase order creation

Hello friends;
System gives following error when i adopt already created purchase requsition.
"system error in routine F1_TAX_CHK_PRICING_DATA error code 13 function builder TAX 2."
Please help to solve this error.
Thanks in advance!!

Dear,
If you have access to OSS notes then please see:
400766 Changes in accounting interface and 112609 How are tax codes transferred to condition
Please check with FICO person.
TAX Procedure for the countrry for which ur working should be properly maintained inside OBQ3,
Regards,
R.Brahmankar

Update error in RV_SALES_DOCUMENT_ADD during Sales order creation

I get an Update/ ABAP runtime error during Sales order creation. The error occurs during processing of the update module -RV_SALES_DOCUMENT_ADD.
This error does not occuring always, as I am sometimes able to create a Sales order without getting update error. I am getting the error of all types of Sales orders and even contracts.
Am I missing any configuration parameters?
Thanks,
Chitra

Yes , I can see the error in ST22.
While exceuting VA01 (Oder type OR, Entering Sold-to-party, Purchase order NO, Material, Qty, Plant),
- I get run-time error "Run-time error "GETWA_NOT_ASSIGNED" occurred".
    Analysis of error shows:
     Update terminated in "Update module: RV_SALES_DOCUMENT_ADD"
      Fails in the Read table in one of the form
        Termination occurred in the ABAP program "SAPLV45U" - in "VBAP_BEARBEITEN"
The main program was "RSM13000 ". In the source code you have the termination point in
line 147 (READ TABLE FYVBAP WITH KEY VBAP_KEY.)
of the (Include) program "LV45UF0V".
The ABAP's say the functional module is trying to do an 'UPDATE' instead of 'INSERT" in the internal table FYVBAP.
Thanks,
Csuman

Dump during sales order creation for a config material (uding order BOM)

Dear all,
I am getting the following error during sales order creation for a configurable material
When I click on 'Engineering' tab in the characteristics value assignment for the parent material i.e. sales order material I get dump with following message,
'Field symbol has not yet been assigned'
Thanks,
Yogesh

Yogesh,
what was the problem ?
Thanks,
Pavan Verma
Edited by: Pavan Verma on May 11, 2010 9:31 AM

100% advance payment during sales order creation

Dear Experts,
One of our international client is having one requirement for collecting the 100% advance payment from customer during sales order creation itself. Our customer is in Germany.
For high risk customers they want to collect the advance payment for 100%. And if this 100% advance payment was not paid by customer then, sales order should not be processed.
And during regular sales invoice creation the same down payment also needs to be displayed in the invoice as advance payment.
Is it possible to setup this process using milestone billing.?? .or some other process is available to setup this process.
Thanks for your cooperation.
Warm Regards,
Velmurugan

Hi
Try with this with Credit management.Put High Risk with Error message.
When ever you will Create Sales Order it will Block due to Credit Chech.For this scenario Enter the Parking Vale at F-66.
Then make a entry for Customer-CR to BANK-DR.
This may solve ur requirement.
Regards
JS

Serial number in production order creation CO01 Transaction

Dear All,
we are maintaining serial numbers for each product by using serial number profile .
For some products we creating serial numbers automatically during production order creation.
For some products we are selecting predefined serial numbers from IQ03,during production order creation.
But some products , we are maintaining serial numbers in excel sheet ,when ever production order created , we used to copy the required
serial numbers from excel and pasting in CO01 serial no provision fields.Here it is allowing to paste 20 serial no's at a time, but we want to
give more than 20 serial no's at a time
please find the attached screen shots and provide solution
Production order creation
Execute Transaction : CO01
After entering qty , we usually go to Header and select serial numbers
then it will populate provision to enter serial number for 30 sets
Here we are entering required serial number manually fro few products
The serial number to be used for this production order against this product like below
M1001
M1002
M1003
M1004
M1005
M1006
M1007
M1008
M1009
M1010
M1011
M1012
M1013
M1014
M1015
M1016
M1017
M1018
M1019
M1020
M1021
M1022
M1023
M1024
M1025
M1026
M1027
M1028
M1029
M1030
Then we will copy all 30 serial number and try to past in below screen
But it allowing only 20 serial number at a time not for 30
After pasting 20 serial no's , user manually selecting remaining 10serial numbers and pating in the same screen by scrolling the page
For example if production order quantity is 500 , then user put serial numbers 25 times it consuming more time
Requirement:
System should allow to paste all serial numbers at a time
Regards
Satya

Hello Satya,
I checked this requirement and did not find anything relevant.Even for MIGO there is a note 1883420 - In the transaction MIGO only 6 serial numbers can be entered at the same time .So as per my view you can either
1. Create serial no's before hand which you want to paste from Excel or
2. Some custom/alternate development for CO01,discuss with your Abaper. or
3. Raise OSS messge to SAP.
Regards,

How to ignore Assembly Scrap of MRP during Production order Creation

Hi All,
We want to ignore the Assembly Scrap maintained in MRP View during production order creation.
We are maintaining assembly Scrap for planning so we do not want to remove that.
Please let us know if any User exit is there during Production Order Creation.
Thanks,
Amit

Dear Amit,
Assume in CO01,once after entering the total order quantity the system proposes the scrap quantity field separately,now
remove this quantity for scrap field and press enter and once again adjust the total quantity and check for what quantity the
system is proposing the BOM components.
check whether this works for your requirement.
Regards
Mangalraj.S

Error in : Purchase order Creation using BAPI_PO_CREATE1

Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
 i_create_order,
 i_cycle TYPE cycle,
 i_qty_acpt TYPE dzmeng,
 i_dly_date TYPE vbak-vdatu,
 i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
 i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
 i_vbap TYPE vbap,
 i_ekko TYPE ekko,
 i_ekpo TYPE ekpo,
 i_bsoh TYPE bapisdhd1,
 i_bsohx TYPE bapisdhd1x,
 i_bpoh TYPE bapimepoheader,
 i_bpohx TYPE bapimepoheaderx,
 i_vbeln TYPE vbeln_va,
 i_posnr TYPE posnr_va,
 i_contr TYPE vbeln_va,
 i_conit TYPE posnr_va,
 i_ebeln TYPE ebeln,
 i_ebelp TYPE ebelp,
 i_pargr TYPE pargr,
 i_thead TYPE thead,
 i_line TYPE tline,
 i_note TYPE txw_note,
 i_new_vbeln TYPE vbeln_va,
 i_new_ebeln TYPE ebeln,
 i_wa_bsoi TYPE bapisditm,
 i_wa_bsoix TYPE bapisditmx,
 i_wa_bsop TYPE bapiparnr,
 i_wa_bsos TYPE bapischdl,
 i_wa_bsosx TYPE bapischdlx,
 i_wa_vbpa TYPE vbpa,
 i_wa_vbkd TYPE vbkd,
 i_wa_bpoi TYPE bapimepoitem,
 i_wa_bpoix TYPE bapimepoitemx,
 i_wa_bpos TYPE bapimeposchedule,
 i_wa_bposx TYPE bapimeposchedulx,
 i_wa_bpop TYPE bapiekkop,
 i_wa_ekpa TYPE ekpa,
 i_message TYPE char72,
 i_bapiretn TYPE bapiret2,
 i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
 i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
 i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
 i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
 i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
 i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
 i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
 i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
 i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
 i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
 i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
 i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
 i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
 i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
 i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
 i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
 c_char_e VALUE 'E',
 c_char_p VALUE 'P',
 c_char_g VALUE 'G',
 c_char_i VALUE 'I',
 c_char_s VALUE 'S',
 c_char_x VALUE 'X',
 c_zsw(3) VALUE 'ZSW',
 c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
 IF NOT i_create_order IS INITIAL .
 CLEAR: i_create_order .
 MOVE: wa_order_split_create-docnr TO i_ebeln,
 wa_order_split_create-docitm TO i_ebelp .
 CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 IMPORTING
 po_ekko = i_ekko
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
 ENDIF .
* Fill PO Header
 i_bpoh-comp_code = i_ekko-bukrs .
 i_bpoh-doc_type = i_ekko-bsart .
 i_bpoh-vendor = i_ekko-lifnr .
 i_bpoh-langu = i_ekko-spras .
 i_bpoh-pmnttrms = i_ekko-zterm .
 i_bpoh-purch_org = i_ekko-ekorg .
 i_bpoh-pur_group = i_ekko-ekgrp .
 i_bpoh-currency = i_ekko-waers .
 i_bpoh-agreement = i_ekko-konnr .
 i_bpoh-incoterms1 = i_ekko-inco1 .
 i_bpoh-incoterms2 = i_ekko-inco2 .
* Fill PO update indicator 'X'
 i_bpohx-comp_code = c_char_x .
 i_bpohx-doc_type = c_char_x .
 i_bpohx-vendor = c_char_x .
 i_bpohx-langu = c_char_x .
 i_bpohx-pmnttrms = c_char_x .
 i_bpohx-purch_org = c_char_x .
 i_bpohx-pur_group = c_char_x .
 i_bpohx-currency = c_char_x .
 i_bpohx-agreement = c_char_x .
 i_bpohx-incoterms1 = c_char_x .
 i_bpohx-incoterms2 = c_char_x .
 CALL FUNCTION 'ME_EKPO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 pi_ebelp = i_ebelp
 IMPORTING
 po_ekpo = i_ekpo
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF .
* Fill PO Item
 i_wa_bpoi-po_item = i_ekpo-ebelp .
 i_wa_bpoi-material = i_ekpo-matnr .
 i_wa_bpoi-plant = i_ekpo-werks .
 i_wa_bpoi-stge_loc = i_ekpo-lgort .
 i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
 i_wa_bpoi-po_unit = i_ekpo-meins .
 i_wa_bpoi-tax_code = i_ekpo-mwskz .
 i_wa_bpoi-val_type = i_ekpo-bwtar .
 i_wa_bpoi-item_cat = i_ekpo-pstyp .
 i_wa_bpoi-acctasscat = i_ekpo-knttp .
 i_wa_bpoi-agreement = i_ekpo-konnr .
 i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
 APPEND i_wa_bpoi TO i_bpoi .
* Fill PO Item update indicator 'X'
 i_wa_bpoix-po_item = i_ekpo-ebelp .
 i_wa_bpoix-po_itemx = c_char_x .
 i_wa_bpoix-material = c_char_x .
 i_wa_bpoix-plant = c_char_x .
 i_wa_bpoix-stge_loc = c_char_x .
 i_wa_bpoix-quantity = c_char_x .
 i_wa_bpoix-po_unit = c_char_x .
 i_wa_bpoix-tax_code = c_char_x .
 i_wa_bpoix-val_type = c_char_x .
 i_wa_bpoix-item_cat = c_char_x .
 i_wa_bpoix-acctasscat = c_char_x .
 i_wa_bpoix-agreement = c_char_x .
 i_wa_bpoix-agmt_item = c_char_x .
 APPEND i_wa_bpoix TO i_bpoix .
* Fill PO Item Schedule
 i_wa_bpos-po_item = i_ekpo-ebelp .
 i_wa_bpos-sched_line = '0001' .
 i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
 i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
 APPEND i_wa_bpos TO i_bpos .
* Fill PO Item schedule update indicator 'X'
 i_wa_bposx-po_item = i_ekpo-ebelp .
 i_wa_bposx-sched_line = '0001' .
 i_wa_bposx-delivery_date = c_char_x .
 i_wa_bposx-quantity = c_char_x .
 APPEND i_wa_bposx TO i_bposx .
 CLEAR: i_pargr .
 SELECT SINGLE pargr
 INTO i_pargr
 FROM t161
 WHERE bstyp = i_ekko-bstyp
 AND bsart = i_ekko-bsart .
 CLEAR i_ekpa[].
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa[].
 LOOP AT i_ekpa INTO i_wa_ekpa .
 i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
 i_wa_bpop-langu = sy-langu .
 IF NOT i_wa_ekpa-lifn2 IS INITIAL .
 i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
 ELSE .
 i_wa_bpop-buspartno = i_wa_ekpa-parnr .
 ENDIF .
 APPEND i_wa_bpop TO i_bpop .
 CLEAR: i_wa_ekpa, i_wa_bpop .
 ENDLOOP .
 CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
 CALL FUNCTION 'BAPI_PO_CREATE1'
 EXPORTING
 poheader = i_bpoh
 poheaderx = i_bpohx
 IMPORTING
 exppurchaseorder = i_new_ebeln
 TABLES
 return = i_bapiret2
 poitem = i_bpoi[]
 poitemx = i_bpoix[]
 poschedule = i_bpos[]
 poschedulex = i_bposx[].
 i_order = i_new_ebeln .
 SHIFT i_order LEFT DELETING LEADING '0' .
 i_return-errortype = c_char_i .
 i_return-workarea = c_zsw .
 i_return-message = '064' .
 i_return-variable1 = i_order .
 loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
 append i_bapiretn to t_bapi_return .
 endloop .
 if t_bapi_return[] is initial .
 i_create_order = c_char_x .
 CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
 EXPORTING
 act_return = i_return. "Popup with new PO no.
 ENDCASE . " Docind
 ENDIF .
ENDLOOP.

Hi Shareen,
I think in the following parts of the code,
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa[].
Error in : Purchase order Creation using BAPI_PO_CREATE1
Posted: Mar 20, 2006 7:39 PM Reply E-mail this post
Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
 i_create_order,
 i_cycle TYPE cycle,
 i_qty_acpt TYPE dzmeng,
 i_dly_date TYPE vbak-vdatu,
 i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
 i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
 i_vbap TYPE vbap,
 i_ekko TYPE ekko,
 i_ekpo TYPE ekpo,
 i_bsoh TYPE bapisdhd1,
 i_bsohx TYPE bapisdhd1x,
 i_bpoh TYPE bapimepoheader,
 i_bpohx TYPE bapimepoheaderx,
 i_vbeln TYPE vbeln_va,
 i_posnr TYPE posnr_va,
 i_contr TYPE vbeln_va,
 i_conit TYPE posnr_va,
 i_ebeln TYPE ebeln,
 i_ebelp TYPE ebelp,
 i_pargr TYPE pargr,
 i_thead TYPE thead,
 i_line TYPE tline,
 i_note TYPE txw_note,
 i_new_vbeln TYPE vbeln_va,
 i_new_ebeln TYPE ebeln,
 i_wa_bsoi TYPE bapisditm,
 i_wa_bsoix TYPE bapisditmx,
 i_wa_bsop TYPE bapiparnr,
 i_wa_bsos TYPE bapischdl,
 i_wa_bsosx TYPE bapischdlx,
 i_wa_vbpa TYPE vbpa,
 i_wa_vbkd TYPE vbkd,
 i_wa_bpoi TYPE bapimepoitem,
 i_wa_bpoix TYPE bapimepoitemx,
 i_wa_bpos TYPE bapimeposchedule,
 i_wa_bposx TYPE bapimeposchedulx,
 i_wa_bpop TYPE bapiekkop,
 i_wa_ekpa TYPE ekpa,
 i_message TYPE char72,
 i_bapiretn TYPE bapiret2,
 i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
 i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
 i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
 i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
 i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
 i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
 i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
 i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
 i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
 i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
 i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
 i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
 i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
 i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
 i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
 i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
 c_char_e VALUE 'E',
 c_char_p VALUE 'P',
 c_char_g VALUE 'G',
 c_char_i VALUE 'I',
 c_char_s VALUE 'S',
 c_char_x VALUE 'X',
 c_zsw(3) VALUE 'ZSW',
 c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
 IF NOT i_create_order IS INITIAL .
 CLEAR: i_create_order .
 MOVE: wa_order_split_create-docnr TO i_ebeln,
 wa_order_split_create-docitm TO i_ebelp .
 CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 IMPORTING
 po_ekko = i_ekko
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
 ENDIF .
Fill PO Header
 i_bpoh-comp_code = i_ekko-bukrs .
 i_bpoh-doc_type = i_ekko-bsart .
 i_bpoh-vendor = i_ekko-lifnr .
 i_bpoh-langu = i_ekko-spras .
 i_bpoh-pmnttrms = i_ekko-zterm .
 i_bpoh-purch_org = i_ekko-ekorg .
 i_bpoh-pur_group = i_ekko-ekgrp .
 i_bpoh-currency = i_ekko-waers .
 i_bpoh-agreement = i_ekko-konnr .
 i_bpoh-incoterms1 = i_ekko-inco1 .
 i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
 i_bpohx-comp_code = c_char_x .
 i_bpohx-doc_type = c_char_x .
 i_bpohx-vendor = c_char_x .
 i_bpohx-langu = c_char_x .
 i_bpohx-pmnttrms = c_char_x .
 i_bpohx-purch_org = c_char_x .
 i_bpohx-pur_group = c_char_x .
 i_bpohx-currency = c_char_x .
 i_bpohx-agreement = c_char_x .
 i_bpohx-incoterms1 = c_char_x .
 i_bpohx-incoterms2 = c_char_x .
 CALL FUNCTION 'ME_EKPO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 pi_ebelp = i_ebelp
 IMPORTING
 po_ekpo = i_ekpo
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF .
Fill PO Item
 i_wa_bpoi-po_item = i_ekpo-ebelp .
 i_wa_bpoi-material = i_ekpo-matnr .
 i_wa_bpoi-plant = i_ekpo-werks .
 i_wa_bpoi-stge_loc = i_ekpo-lgort .
 i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
 i_wa_bpoi-po_unit = i_ekpo-meins .
 i_wa_bpoi-tax_code = i_ekpo-mwskz .
 i_wa_bpoi-val_type = i_ekpo-bwtar .
 i_wa_bpoi-item_cat = i_ekpo-pstyp .
 i_wa_bpoi-acctasscat = i_ekpo-knttp .
 i_wa_bpoi-agreement = i_ekpo-konnr .
 i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
 APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
 i_wa_bpoix-po_item = i_ekpo-ebelp .
 i_wa_bpoix-po_itemx = c_char_x .
 i_wa_bpoix-material = c_char_x .
 i_wa_bpoix-plant = c_char_x .
 i_wa_bpoix-stge_loc = c_char_x .
 i_wa_bpoix-quantity = c_char_x .
 i_wa_bpoix-po_unit = c_char_x .
 i_wa_bpoix-tax_code = c_char_x .
 i_wa_bpoix-val_type = c_char_x .
 i_wa_bpoix-item_cat = c_char_x .
 i_wa_bpoix-acctasscat = c_char_x .
 i_wa_bpoix-agreement = c_char_x .
 i_wa_bpoix-agmt_item = c_char_x .
 APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
 i_wa_bpos-po_item = i_ekpo-ebelp .
 i_wa_bpos-sched_line = '0001' .
 i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
 i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
 APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
 i_wa_bposx-po_item = i_ekpo-ebelp .
 i_wa_bposx-sched_line = '0001' .
 i_wa_bposx-delivery_date = c_char_x .
 i_wa_bposx-quantity = c_char_x .
 APPEND i_wa_bposx TO i_bposx .
 CLEAR: i_pargr .
 SELECT SINGLE pargr
 INTO i_pargr
 FROM t161
 WHERE bstyp = i_ekko-bstyp
 AND bsart = i_ekko-bsart .
 CLEAR i_ekpa[].
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa[].
 LOOP AT i_ekpa INTO i_wa_ekpa .
 i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
 i_wa_bpop-langu = sy-langu .
 IF NOT i_wa_ekpa-lifn2 IS INITIAL .
 i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
 ELSE .
 i_wa_bpop-buspartno = i_wa_ekpa-parnr .
 ENDIF .
 APPEND i_wa_bpop TO i_bpop .
 CLEAR: i_wa_ekpa, i_wa_bpop .
 ENDLOOP .
 CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
 CALL FUNCTION 'BAPI_PO_CREATE1'
 EXPORTING
 poheader = i_bpoh
 poheaderx = i_bpohx
 IMPORTING
 exppurchaseorder = i_new_ebeln
 TABLES
 return = i_bapiret2
 poitem = i_bpoi[]
 poitemx = i_bpoix[]
 poschedule = i_bpos[]
 poschedulex = i_bposx[].
it should be only i_bpoi, i_bpoix, i_bpos, i_bposx but not i_bpoi[], i_bpoix[], i_bpos[], i_bposx[].
CHange the code as follows:
DATA: i_insert,
 i_create_order,
 i_cycle TYPE cycle,
 i_qty_acpt TYPE dzmeng,
 i_dly_date TYPE vbak-vdatu,
 i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
 i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
 i_vbap TYPE vbap,
 i_ekko TYPE ekko,
 i_ekpo TYPE ekpo,
 i_bsoh TYPE bapisdhd1,
 i_bsohx TYPE bapisdhd1x,
 i_bpoh TYPE bapimepoheader,
 i_bpohx TYPE bapimepoheaderx,
 i_vbeln TYPE vbeln_va,
 i_posnr TYPE posnr_va,
 i_contr TYPE vbeln_va,
 i_conit TYPE posnr_va,
 i_ebeln TYPE ebeln,
 i_ebelp TYPE ebelp,
 i_pargr TYPE pargr,
 i_thead TYPE thead,
 i_line TYPE tline,
 i_note TYPE txw_note,
 i_new_vbeln TYPE vbeln_va,
 i_new_ebeln TYPE ebeln,
 i_wa_bsoi TYPE bapisditm,
 i_wa_bsoix TYPE bapisditmx,
 i_wa_bsop TYPE bapiparnr,
 i_wa_bsos TYPE bapischdl,
 i_wa_bsosx TYPE bapischdlx,
 i_wa_vbpa TYPE vbpa,
 i_wa_vbkd TYPE vbkd,
 i_wa_bpoi TYPE bapimepoitem,
 i_wa_bpoix TYPE bapimepoitemx,
 i_wa_bpos TYPE bapimeposchedule,
 i_wa_bposx TYPE bapimeposchedulx,
 i_wa_bpop TYPE bapiekkop,
 i_wa_ekpa TYPE ekpa,
 i_message TYPE char72,
 i_bapiretn TYPE bapiret2,
 i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
 i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
 i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
 i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
 i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
 i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
 i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
 i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
 i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
 i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
 i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
 i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
 i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
 i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
 i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
 i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
 c_char_e VALUE 'E',
 c_char_p VALUE 'P',
 c_char_g VALUE 'G',
 c_char_i VALUE 'I',
 c_char_s VALUE 'S',
 c_char_x VALUE 'X',
 c_zsw(3) VALUE 'ZSW',
 c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
 IF NOT i_create_order IS INITIAL .
 CLEAR: i_create_order .
 MOVE: wa_order_split_create-docnr TO i_ebeln,
 wa_order_split_create-docitm TO i_ebelp .
 CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 IMPORTING
 po_ekko = i_ekko
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
 ENDIF .
Fill PO Header
 i_bpoh-comp_code = i_ekko-bukrs .
 i_bpoh-doc_type = i_ekko-bsart .
 i_bpoh-vendor = i_ekko-lifnr .
 i_bpoh-langu = i_ekko-spras .
 i_bpoh-pmnttrms = i_ekko-zterm .
 i_bpoh-purch_org = i_ekko-ekorg .
 i_bpoh-pur_group = i_ekko-ekgrp .
 i_bpoh-currency = i_ekko-waers .
 i_bpoh-agreement = i_ekko-konnr .
 i_bpoh-incoterms1 = i_ekko-inco1 .
 i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
 i_bpohx-comp_code = c_char_x .
 i_bpohx-doc_type = c_char_x .
 i_bpohx-vendor = c_char_x .
 i_bpohx-langu = c_char_x .
 i_bpohx-pmnttrms = c_char_x .
 i_bpohx-purch_org = c_char_x .
 i_bpohx-pur_group = c_char_x .
 i_bpohx-currency = c_char_x .
 i_bpohx-agreement = c_char_x .
 i_bpohx-incoterms1 = c_char_x .
 i_bpohx-incoterms2 = c_char_x .
 CALL FUNCTION 'ME_EKPO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 pi_ebelp = i_ebelp
 IMPORTING
 po_ekpo = i_ekpo
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF .
Fill PO Item
 i_wa_bpoi-po_item = i_ekpo-ebelp .
 i_wa_bpoi-material = i_ekpo-matnr .
 i_wa_bpoi-plant = i_ekpo-werks .
 i_wa_bpoi-stge_loc = i_ekpo-lgort .
 i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
 i_wa_bpoi-po_unit = i_ekpo-meins .
 i_wa_bpoi-tax_code = i_ekpo-mwskz .
 i_wa_bpoi-val_type = i_ekpo-bwtar .
 i_wa_bpoi-item_cat = i_ekpo-pstyp .
 i_wa_bpoi-acctasscat = i_ekpo-knttp .
 i_wa_bpoi-agreement = i_ekpo-konnr .
 i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
 APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
 i_wa_bpoix-po_item = i_ekpo-ebelp .
 i_wa_bpoix-po_itemx = c_char_x .
 i_wa_bpoix-material = c_char_x .
 i_wa_bpoix-plant = c_char_x .
 i_wa_bpoix-stge_loc = c_char_x .
 i_wa_bpoix-quantity = c_char_x .
 i_wa_bpoix-po_unit = c_char_x .
 i_wa_bpoix-tax_code = c_char_x .
 i_wa_bpoix-val_type = c_char_x .
 i_wa_bpoix-item_cat = c_char_x .
 i_wa_bpoix-acctasscat = c_char_x .
 i_wa_bpoix-agreement = c_char_x .
 i_wa_bpoix-agmt_item = c_char_x .
 APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
 i_wa_bpos-po_item = i_ekpo-ebelp .
 i_wa_bpos-sched_line = '0001' .
 i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
 i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
 APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
 i_wa_bposx-po_item = i_ekpo-ebelp .
 i_wa_bposx-sched_line = '0001' .
 i_wa_bposx-delivery_date = c_char_x .
 i_wa_bposx-quantity = c_char_x .
 APPEND i_wa_bposx TO i_bposx .
 CLEAR: i_pargr .
 SELECT SINGLE pargr
 INTO i_pargr
 FROM t161
 WHERE bstyp = i_ekko-bstyp
 AND bsart = i_ekko-bsart .
 CLEAR i_ekpa[].
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa.
 LOOP AT i_ekpa INTO i_wa_ekpa .
 i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
 i_wa_bpop-langu = sy-langu .
 IF NOT i_wa_ekpa-lifn2 IS INITIAL .
 i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
 ELSE .
 i_wa_bpop-buspartno = i_wa_ekpa-parnr .
 ENDIF .
 APPEND i_wa_bpop TO i_bpop .
 CLEAR: i_wa_ekpa, i_wa_bpop .
 ENDLOOP .
 CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
 CALL FUNCTION 'BAPI_PO_CREATE1'
 EXPORTING
 poheader = i_bpoh
 poheaderx = i_bpohx
 IMPORTING
 exppurchaseorder = i_new_ebeln
 TABLES
 return = i_bapiret2
 poitem = i_bpoi
 poitemx = i_bpoix
 poschedule = i_bpos
 poschedulex = i_bposx.
 i_order = i_new_ebeln .
 SHIFT i_order LEFT DELETING LEADING '0' .
 i_return-errortype = c_char_i .
 i_return-workarea = c_zsw .
 i_return-message = '064' .
 i_return-variable1 = i_order .
 loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
 append i_bapiretn to t_bapi_return .
 endloop .
 if t_bapi_return[] is initial .
 i_create_order = c_char_x .
 CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
 EXPORTING
 act_return = i_return. "Popup with new PO no.
 ENDCASE . " Docind
 ENDIF .
ENDLOOP.

Error during Production Order Confirmation

I get a real wierd error during production Order confirmation. The error message is
"Additional items are not allowed
Message no. ZOAL010"
Can anyone throw some light on this?
Regards
Raj

it is not std SAP message.
you can check the user exit for confirmation.
check in transaction code CMOD/SMOD for CONF*

How to make material availability check work during Work Order creation

Hi Experts,
Kindly advice about these matters:
1. How to make material availability check work during Work Order creation?
My requirement is Work Order can not be created when it has missing parts. I have set the config to '3' can not created when is has missing parts, but it still does not work.
I have implemented SAP Notes 1148139 on my system (SAP ECC 6 Ehp 5) also, but still does not have any effect.
I must not set the config Res./Purch Doc creation to 'immediately', because it does not fit to my user requirement. Is there anyone knows how to solve this requirement?
2. How to make information message/ Availability check screen appear when sparepart is missing, without clicking Availability Check button? for example: appear when clicking Save button.
Thank you
-amoonra-

Hi Maheswaran,
I have implement the prerequisite notes. (Notes 790219 and 1034962). Do you know why it is still does not work?
Thanks
-amoonra-

Error during prdn order creation co01

Similar Messages

Maybe you are looking for