Error during Purchase Requisition Creation .

Dear All ,
Please help i m not able to create a Purchase Requisition in testing system am gettign an error as given below ;-
Internal number assignment not defined (please enter number)
Message no. 06243
Diagnosis
The system cannot assign a number because internal number assignment has not been defined in this case.
Procedure
Enter a number that lies within the valid number range for the document.
Any suitable help will b appreciated.
rgds,
sap11

Hi,
here in IMG for this doc type , there is no entry in column for " NoRngInt " but
Maintain here 01 in front of Nointreg your doc type and save...
Def it will work
Utsav

Similar Messages

Item category determination during Purchase Requisition creation from APO

Im creating a SNP Purchase Requisition in APO and when it is published to R/3, a Purchase Requisition document is created in R/3.
When this PR is created in R/3, I want the Item Category to be determined based on the Material master Special Procurement Type. ( eg: Id like the Item category to be L if the Material master Special Procurement Type = 30 (Subcontracting) ). But by standard, this field is coming as Blank and this field could only be populated during the creation from APO.
I found a user exit ( CIFPUR02 : Enhancement of Purchase Order Interface (Inbound) ) on R/3 where I tried to populate the Item Category, but when I do this, all the purchase order related data is getting deleted and hence no PRs are getting created in R/3.
Could anyone please tell me if this could be resolved using configuration and if not any tips to do this technically would be very helpful.
Thanks,
Harsha

Hi Karun,
This is the code i'm using...
select single * from marc into lit_marc
where matnr = c_eban-matnr
and werks = c_eban-werks.
append lit_marc.
read table lit_marc with key matnr = c_eban-matnr
 werks = c_eban-werks
 sobsl = 30.
if sy-subrc = 0.
c_eban-pstyp = '3'.
endif.
Here sobsl = 30 is the Special procurement type
But when i try to populate c_eban-pstyp = '3', during the creation of Purchase Requisitions in R/3, in the program SAPLEMPI -> LMEPIF01
this condition is encountered which deletes all the data in the tables that is used to create Purchase requisitions.
* get rsnum in the case of subcontracting
 IF XEBAN-PSTYP EQ PSTYP-LOHN AND "RB240999
 EXITFLAG_ORDID IS INITIAL. "RB240999
refresh all component tables
 CALL FUNCTION 'ME_COMPONENTS_REFRESH'
 EXCEPTIONS
 OTHERS = 1.
Could you please suggest me anything to get around this.
Thanks,
Harsha

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

Error code 083 on LSMW - Purchase Requisition creation

Hii all,
I have generated a bapi program for purchase Requisition creation.
the followings are the programe details:
Business Object
BUS2105
Method
CREATEFROMDATA1
Message Type
PREQCR1
Basic Type
PREQCR101
I have divided the structures into 3 sections:HEADER,ITEM DETAIL,ACCOUNT ASSIGNMENT.In the account assignment group at the "Maintain Field Mapping and Conversion Rules" (E1BPMEREQACCOUNT), wbs element field marked as "move".
At the "E1BPMEREQACCOUNTX" the wbs field was mared as "X".
the programm can read the feild & displays the WBS element that it can read from the datafile.
the problem is that during the stage of " Create IDoc Overview"
it provides the following error:
Enter WBS Element
Message no. ME083.
I have checked the WBS element& nothing is wrong with it.
any one can help me out on this?
thanks
M S

Hi Jurgen,
Thanks for replying.
1. For BAPI, at step 14. when i execute, it is a warning message
No Data could be selected
2. yes, I have activated the IDOC Settings.
Please suggest.
Thanks,
Sahil

Materials available only for Purchase requisition creation

Hi Experts,
My client wants some materials available only for Purchase requisition creation and some materials donu2019t want available only for Purchase requisition creation.
How we can control
Thanks in advance,
Chandhu

1) Solve your issue first you have to bifurcate between the materials where requisition is possible & where not...u can do this by selecting some field which is not in use presently in material master-basic data view & maintain some unique value for those materials for which PR will be not possible....otherwise check whether you can bifurcate it through material groups or not...
After this take help of your ABAP person and implement BAdI::ME_PROCESS_REQ_CUST...here use the logic that after user enters the material code in PR system will check in the background what has been maintained in the said field in the basic data view of the material...if found blank then it will allow the user process further or if found any data in that field then system will stop the user from processing the same by throwing some customized error message.
2) Use the Plant-sp.matl status in purchasing view as Blocked for procment/whse for those material against which you don't want to create any PR.But this will be plant specific and both PR & PO will get blocked.
Regards,
Indranil

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.

Problem in Purchase Requisition Creation

Dear Experts:
We are facing a problem while purchase requisition creation. We have created an Internal order No. 600406 and an Asset in Company Code AB01 but while creation of Purchase Requisition level when we are selection that Order and Asset in Purchase Requisition system automatically changing my Order no. 600020 instead of 600406. I've checked OKB9 where Order no. maintained as 600020 against Company code AB01 which I deleted and save but after that Purchase requisition asking for Order Number that means we have to maintain Order number in OKB9. Now can you please advise how can we get my current order number in requisition instead of any default number.
Thanks in advance and your kind suggestion is highly appreciated.
Best Regards.
Ripon Kumar Paul

Please find attached screen shots of OME9

No Subcontracting Purchase requisition creation

Hello everybody,
I have a strange system behavior : the external purchase requisition creation at Production order type level (AFVG-AUDISP) is set to "3", so I want that the system always create automatically the related purchase requisition.
It randomly happens that certain number of production order are created without purchase requisitions, and into the external operation the system "automatically" move the external purchase requisition creation to "1".
Looking into the OSS notes I found the note 1493286, unfortunately there is inside just a workaround and I am not able to reproduce the behavior.
I know that the value "1" is placed because the system is not able to create the Purch Req, but I am not able to find the real reasons in order to remove them.
We are speaking about "kanban" order creation... is there someone that had similar problems ?
Could you please help me ?
Thanks
Salvatore Testa

Creating (ME51N) is not changing, hence you dont have change documents in CDHDR and CDPOS.
And the table EBAN just has a creation date, but not creation time.
SAP is probably the opinion that the creation time of a requistion is not needed for an ERP process.
(Adding a new item to an existing requisition is a change and will update CDHDR)

Purchase Requisition Creation From Release

Dear PM Gurus,
For Manual material availability Check to work before release, the Purchase Requisition check is to be set to Immediately in SPRO-> Define Change Docs and Collective PR or Activating Pr from Now On from Maintenance Order. The issue is that I want to restrict the creation of Purchase Requisition to Release of Maintenance Order but what is happening is upon saving the Maintenance Order, the PRs for all non stock materials are created and I also want the manual availability check to work before release.
Simplifying above details:
I want Manual material availability check to work and PR generation from release both in my Maintenance Order to work..
Regards..

Hi DP Singh,
I had seen the configuration settings that you are telling me but you see the Problem is:
If in Define Change Docs, Collective Purc. Req. Indicator, Operation No. Interval, you define the Res/PReq Indicator as Immediately, then the Manual Material Availability Check would work accurately but upon saving the Order, System would generate the Purchase Requisition.
and If in Define Change Docs, Collective Purc. Req. Indicator, Operation No. Interval, you define the Res/Preq Indicator as From Release, then the Manual Material Availability Check would not work as no material is as such MRP relevant till the time of releasing the Order but the Purchase Requisition would be created only when the Order is released.
Now What I want is both the Manual Availability Check to work and Purchase Requisition Creation From Release, but this is not possible according to the Standard SAP System. A workaround could be that I configure the automatic material availability upon release and configure the Res/Preq indicator as From Release, that way the material availability would be checked when the order is released and Purchase Requisitions would also be created from Release but still the Manual Availability Check would not work.
The Ideal Solution should have been configuring the Res/Purchase Requisition Indicator for all Non Stock Materials to be From Release and the Res/ Purchase Requisition Indicator for all Stock Materials to be Immediately. This way your manual availability Check would work for all Stock Materials and Purchase Requisition for all Non Stock materials would only be created upon Release. But this But still this is an ideal solution not the actual solution for standard SAP does not give you the flexibility to do such a setting in customizing or using Enhancement.
The Work Around Solution given by SAP is as follows: The system provides the following workaround:
After you change the indicator for materials planning-relevance to
"immediately" you can execute the availability check as required. You must
not save the order or network.
Regards,
Muhammad Usman Kahoot
Edited by: Usman Kahoot on May 27, 2010 1:32 PM

Handling Errors in Purchase Requisition

Hi guys,
For handling errors in Purchase Orders is quite simple because it can be used mm_messages_mac.
and there can be used macros:
- for adding new errors
mmpur_message_forced 'E' 'ZM' '048' TEXT-003 ' ' ' ' ' ' .
- for removing errors, it can be used:
mmpur_remove_messages_by_id *ID*
Almost all the macros from mm_messages_mac. uses this ID. What is that ?
So, for PO (Purchase Order - ME2XN) is very simple to implement BADI's like ME_PROCESS_CUST_PO, where there can be found that ID in the methods structures (mepo*), which is used by those macros.
But how can you handle errors in Purchase Requisition (PR - ME5XN) ??? In ME_PROCESS_REQ_CUST, for exemple, none of the methods contains structures with that ID field.
Please Help.
I couldn't find any answer on the internet. It seems that nobody knows. Isn't it ??

Hi Babu,
How can i handle errors from here??
For exemple I need to give my own message, delete a standard one, and position cursor on a custom field.
In Purchase Order I could use macros from mm_messages_mac.
For example: mmpur_remove_messages_by_id ID
But the problem is that this ID i couldn't find.
Please help.
Have a nice day

Error During Purchase: Please try again later

We have created an app that has free content and are now trying our first in-app purchase. We've updated the app with the in-app purchase and have gotten Apple's approval and it is now available for download on the App store. The problem we are having is that some users are able to download the in-app purchase folio with no problems, while others are getting this error: "Error During Purchase: Please try again later." We are not seeing any differences between the iPad's/app versions being used. The latest versions of iOS and of the app are producing these inconsistent errors. For the ones having errors, we have tried deleting and reinstalling the app, but still getting the same error message. Any advice on what could be going on?

Bob,
answering your questions:
- Did you use the same Product ID when creating the in-app purchase and publishing the folio?
Yes, I'm using the same Product ID. So, after publishing the folio, it appears at my in-app test.
- Are the retail folios set as public?
If I publish a free issue, I can test the download. The problem is when I set it as retail. The issue and the price appears, but when I try to make the purchase, after I confirm my purchase with an Apple test user, with the [Environment: Sandbox], it says: "ERROR DURING PURCHASE - Please try again later"
- Are your in-app purchases cleared for sale?
I think so. When I published, I've set as Public, Retail and the same Product ID I used at iTunnes Connect. So, when I'm testing at my in-app, the folio appears. Is there any other place I have to go?
Regards,
Filipe.

XML log: Error during temp file creation for LOB Objects

Hi All,
I got this exception in the concurrent log file:
[122010_100220171][][EXCEPTION] !!Error during temp file creation for LOB Objects
[122010_100220172][][EXCEPTION] java.io.FileNotFoundException: null/xdo-dt-lob-1292864540169.tmp (No such file or directory (errno:2))
 at java.io.RandomAccessFile.open(Native Method)
 at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
 at java.io.RandomAccessFile.<init>(RandomAccessFile.java:98)
 at oracle.apps.xdo.dataengine.LOBList.initLOB(LOBList.java:39)
 at oracle.apps.xdo.dataengine.LOBList.<init>(LOBList.java:30)
 at oracle.apps.xdo.dataengine.XMLPGEN.updateMetaData(XMLPGEN.java:1051)
 at oracle.apps.xdo.dataengine.XMLPGEN.processSQLDataSource(XMLPGEN.java:511)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeData(XMLPGEN.java:445)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeGroup(XMLPGEN.java:1121)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeGroup(XMLPGEN.java:1144)
 at oracle.apps.xdo.dataengine.XMLPGEN.processSQLDataSource(XMLPGEN.java:558)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeData(XMLPGEN.java:445)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeGroupStructure(XMLPGEN.java:308)
 at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:273)
 at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:215)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:254)
 at oracle.apps.xdo.dataengine.DataProcessor.processDataStructre(DataProcessor.java:390)
 at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:355)
 at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:348)
 at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:293)
 at oracle.apps.fnd.cp.request.Run.main(Run.java:161)
I have this query defined in my data template:
<![CDATA[
SELECT lt.long_text inv_comment
FROM apps.fnd_attached_docs_form_vl ad,
apps.fnd_documents_long_text lt
WHERE ad.media_id = lt.media_id
AND ad.category_description = 'Draft Invoice Comments'
AND ad.pk1_value = :project_id
AND ad.pk2_value = :draft_invoice_num
]]>
Issue: The inv_comment is not printing on the PDF output.
I had the temp directory defined under the Admin tab.
I'm guessing if it's the LONG datatype of the long_text field that's causing the issue.
Anybody knows how this can be fixed? any help or advice is appreciated.
Thanks.
SW
Edited by: user12152845 on Dec 20, 2010 11:48 AM

Hi All,
I got this exception in the concurrent log file:
[122010_100220171][][EXCEPTION] !!Error during temp file creation for LOB Objects
[122010_100220172][][EXCEPTION] java.io.FileNotFoundException: null/xdo-dt-lob-1292864540169.tmp (No such file or directory (errno:2))
 at java.io.RandomAccessFile.open(Native Method)
 at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
 at java.io.RandomAccessFile.<init>(RandomAccessFile.java:98)
 at oracle.apps.xdo.dataengine.LOBList.initLOB(LOBList.java:39)
 at oracle.apps.xdo.dataengine.LOBList.<init>(LOBList.java:30)
 at oracle.apps.xdo.dataengine.XMLPGEN.updateMetaData(XMLPGEN.java:1051)
 at oracle.apps.xdo.dataengine.XMLPGEN.processSQLDataSource(XMLPGEN.java:511)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeData(XMLPGEN.java:445)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeGroup(XMLPGEN.java:1121)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeGroup(XMLPGEN.java:1144)
 at oracle.apps.xdo.dataengine.XMLPGEN.processSQLDataSource(XMLPGEN.java:558)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeData(XMLPGEN.java:445)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeGroupStructure(XMLPGEN.java:308)
 at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:273)
 at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:215)
 at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:254)
 at oracle.apps.xdo.dataengine.DataProcessor.processDataStructre(DataProcessor.java:390)
 at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:355)
 at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:348)
 at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:293)
 at oracle.apps.fnd.cp.request.Run.main(Run.java:161)
I have this query defined in my data template:
<![CDATA[
SELECT lt.long_text inv_comment
FROM apps.fnd_attached_docs_form_vl ad,
apps.fnd_documents_long_text lt
WHERE ad.media_id = lt.media_id
AND ad.category_description = 'Draft Invoice Comments'
AND ad.pk1_value = :project_id
AND ad.pk2_value = :draft_invoice_num
]]>
Issue: The inv_comment is not printing on the PDF output.
I had the temp directory defined under the Admin tab.
I'm guessing if it's the LONG datatype of the long_text field that's causing the issue.
Anybody knows how this can be fixed? any help or advice is appreciated.
Thanks.
SW
Edited by: user12152845 on Dec 20, 2010 11:48 AM

Re: Purchase REquisition creation with ref to SAles Order

Hi All,
I need help on an issue.
I have sales order creation and when saving Purchase REq is created at the back end. But for the sales order for item category n schedule line category combination does not allow creation of Pur Req. n pur req no. is not dislayed in Sales order.
But I have Pur Rq created with ref to sales order.
How is it possible.
In Pur req I checked the creation indiacotr, it is with ref to sales order.not manually.
Can you please help it out..
Regards,
Smitha

Hi,
Purchase Requisition creation from Sales Order is dependent on the configuration of Schedule line category not Item category. Check configuration of Schedule line category in VOV6.
Also to see the PR No in Sales Order, double click on the Sales line item and click on the "Purchase Requisition" button under "Schedule Lines" Tab.

Purchase requisition creation (STO) from Sales order

Hi Gurus,
Read the following scenario:
Sales order is created with delivery plant A. No stock on plant A.
Purchase requisition is created from plant B to plant A (intra-company flow or stock transfer order).
Problem is that the purchase requisition needs a price. It is not logical because intra-company flow (stock transfer in same company flow) is like a stock transfer without purchasing. So in my mind, I don't have to maintain price.
Also if I use ME27 to create manually STO between both plants, price is not asked.
Other question is: is it possible to create directly a purchase order when sales order creation (and not purchase requisition, newt convert into PO)?
Many thanks.
Stéphane

Hi Stéphane Vituret, Did you manage to find a solution for this. I have a similar problem as well.
Please find the scenario below.
Cusotmer places order of Mat-XX to Company A. The Company A creates PO to Company B. Company B delivers to Company A and then invoices Company A. Company A receives the goods into own stocks. Now the Company A delivers to the customer from its own stocks and then invoices Customer.
I decide to go ahead with the Individual Purchase order solution and since the Company A is buying from Comapny B, I decided to integrate the Cross Company STO flow in the procurement part. Hence the flow in SAP is like;
Cusotmer placese order to Company A
Comapny A creates a Individual Purchase order type Sales order. So the Item category is TAB.
This sales order generates a PR. PR is conveted into a CC_STO as thenvendor is Plant B in this case . Now this STO appears in the delivery due list of plant B.
Now I genreate the delivery to move stocks from plant B(of co.cd B) to Plant A(of co.cd A).
Here is the problem. I am not able to do PGI as the system checks for "sales order" stock at plant B and throws error
"Sales order stock 36637 000010 does not exist". This should not be the case as the stocks should get attached to the sales order only when recieved into Plant A. Hence system should not check for "sales order stock" at plantB while trying to deliver from Plant B to Plant A.
Lets take a normal IPO scenario.
CusotmerA places order of Mat-A to Company A. This sales order generates a PR. The Company A converts the PR into a std.PO to external vendor. The PO from the sales order will have a account assignment "M- Ind. cust. w/o KD-CO". The stocks will be received into Plant with spl indicator "E" while GR (MIGO). Now the system ensures that this stock can only be delivered against the particular sales order. Thus the stock procured for the customerA is delivered to customerA and not consumed by anybody else. In this case there is only one delivery involved, in SAP, which is 601 mvmt type from the Plant A.
However if the vendor becomes another Plant (Plant B) belonging to another company code then there are two deliveries involved in the SAP system one with mvmt type 643, from Plant B to Pant A, and the second with 601 from Plant A to the customer. Hence the system should check if the stocks are attached with a spl indicator only during the second delivery of 601 mvmt type. I am facing a problem because the system does it for the first delivery itself. If you know the answer please do let me know. I really appreciate it. Thanks a lot in advance.

Error in Purchase requisition - system is picking incorrect Funds Center

Hello,
During creation of Purchase Requisition,The User receives a message saying that he has no authorisation to the Funds Center C3101 although the Funds Center he entered in C3006.
The correct funds center is C3006.
Regards
Prasad

Hello Prasad,
Please answer me the following questions:
1) Have this PR more than one line?
2) Please inform your current EA-PS package so I can find something useful to you.
3) Please reproduce again the same error and tell me the complete error message (using /nSU53) when the error is issued in the screen.
Best Regards,
Vanessa Barth.

Error during Purchase Requisition Creation .

Similar Messages

Maybe you are looking for