Idoc error - backend purchase contract
Hi
We are using the classic scenario. Backend purchase contract gets created from the winning bid.
the idoc fail with the following error " unable to interpret <.0 as a number" . the field it complians about is the tolerance field. Field EKPO-UNTTO contains "<.0"
Thanks
Lebo
hi lebo
did you resolve it? how doid you do?
muthu
Similar Messages
-
Backend purchase contract with no plant assigned to it
Hi,
We are implementing SRM 5.0 in a classic scenario deployment and we going to create backend purchase contracts directly from bids, that is, no Global Outline Agreements are involved.
The thing is we would like to create a backend contract that could be consumed by more than one plant, that is, we cannot have a specific plant assigned to that contract.
Is it a possible scenario to be implemented?
Best Regards,
EmiliaHello Emilia,
If you create a R/3 contract from a BID, linked to a BID INVITATION created from a SC, you might get the plant from the SC item.
Else, plant data (partner Location) is not mandatory in RFQ (at both header and item level).
So you could have to delete it in your RFQ (if created from a SC), or use the BADI BBP_CTR_BE_CREATE to change sent data:
Here you can delete plant data, so your R/3 contract is valid for all plants.
Rgds
Christophe -
How to use BLAREL03 standard iDOC to upload Purchasing contract to SAP
Hello
Guru's
Thanks in advance for your time.
we ae planning to upload purchasing contract details to SAP using BLAREL03 standard idoc.
can any one give me step step procedure to follow.
i am new to IDOC's i need little bit detail. give me with function modules names to upload.
In any way can we test it quickly,by creating text file with mandatory fields on the idoc and upload it.
we just worried about like contract start date,end date,(how it is handling while uploading) the fields which are on tree view of idoc, are not there,if we look at flat file structure of idoc.Hello
Guru's
Thanks in advance for your time.
we ae planning to upload purchasing contract details to SAP using BLAREL03 standard idoc.
can any one give me step step procedure to follow.
i am new to IDOC's i need little bit detail. give me with function modules names to upload.
In any way can we test it quickly,by creating text file with mandatory fields on the idoc and upload it.
we just worried about like contract start date,end date,(how it is handling while uploading) the fields which are on tree view of idoc, are not there,if we look at flat file structure of idoc. -
Issue with Idoc for creating purchasing contracts
Hello everyone,
I'm trying to create purchasing contracts using Idoc BLAORD3 through LSMW.
But i have a problem : all informations concerning account assignement are missing on this Idoc.
Does anyone know how to solve this problem? Maybe is there a BAPI which could replace my Idoc? Or is there another Idoc which could create account assignement seperatly?
Thanks in advance for your help.
CédricHi,
Try using E1EDK18 segment. Put "Number of days" ,Qualifier and check if this achievs the desired result or not? If yes then you have to use an user exit to put the number of days in the IDOC.
Cheers, -
Purchase Contract creation in SRM
Hi everybody,
I have a requirement. I need to create purchase contracts in SRM. Data is comming as a file from Oracle server. I tried searching for a BAPI to create contract, not able to find it out. Tring to use eCATT for this. Transaction BBP_CTR_MAIN is giving error in the recording of eCATT.
Pleae advice we how can I create the contracts in background from flat file.
Thanks in advance.
MahithaHi all experts,
I was unsuccessful like some of the users here in trying to create a contract at the backend. I have tried using "BBP_PD_CTR_CREATE" but i alway get 2 error message: create exactly one vendor and create exactly one employee. What could be wrong with the codes??
data: pc_id like CRMD_ORDERADM_H-OBJECT_ID.
data: pc_header_out like BBP_PDS_CTR_HEADER_IC.
data: pc_header_in like BBP_PDS_CTR_HEADER_D.
*data: pc_item type table of BBP_PDS_CTR_ITEM_D with header line.
data: pc_item type table of BBP_PDS_CTR_ITEM_ICU with header line.
data: pc_text type table of BBP_PDS_LONGTEXT.
data: pc_partner type table of BBP_PDS_PARTNER.
data: wa_part like line of pc_partner.
data: pc_org type table of BBP_PDS_ORG with header line.
data: pc_message type table of BBP_PDS_MESSAGES with header line.
Insert dummy data*****************************************************
pc_header_out-CURRENCY = 'SGD'.
pc_header_out-PROCESS_TYPE = 'PCTR'.
Insert Purchase Org data *********************************************
pc_org-PROC_ORG_RESP_ID = 'O 50000026'.
pc_org-PROC_ORG_ID = 'O 50000025'.
pc_org-PROC_GROUP_ID = 'O 50000026'.
Insert BP data - vendor, employee Purch Org and DSTA******************
*DSTA
wa_part-PARTNER_ID = '0000000001'.
wa_part-PARTNER_GUID = '4BD22A16AFA2B74D844E1595998AE7E5'.
wa_part-PARTNER_FCT = '00000038'.
wa_part-ADDR_TYPE = '1'.
wa_part-ADDR_NO = '0000010469'.
append wa_part to pc_partner.
clear wa_part.
*employee
wa_part-PARTNER_ID = '0000000006'.
wa_part-PARTNER_GUID = 'E3D4AAE842930D41B7B107F3CC60B44D'.
wa_part-PARTNER_FCT = '00000026'.
wa_part-ADDR_TYPE = '3'.
wa_part-ADDR_NO = '0000010472'.
wa_part-PERS_NO = '0000010474'.
append wa_part to pc_partner.
clear wa_part.
*vendor
wa_part-PARTNER_ID = '0000000311'.
wa_part-PARTNER_GUID = 'F0BC646129BE2D4BB7E301F8F3708B1E'.
wa_part-PARTNER_FCT = '00000019'.
wa_part-ADDR_TYPE = '1'.
append wa_part to pc_partner.
clear wa_part.
*purch org
wa_part-PARTNER_ID = '0000000002'.
wa_part-PARTNER_GUID = '48459C575651D04091BAF1B9A554CF51'.
wa_part-PARTNER_FCT = '00000051'.
wa_part-ADDR_TYPE = '1'.
wa_part-ADDR_NO = '0000010470'.
append wa_part to pc_partner.
clear wa_part.
Item data
pc_item-CATEGORY_ID = 'ARMOUR'.
pc_item-QUANTITY = '233'.
pc_item-PRICE = '1234'.
pc_item-VALUE = '4321'.
pc_item-UNIT = 'EA'.
pc_item-PRODUCT = 'B78A60018B6018418F6D0F1632E10F69'.
pc_item-DESCRIPTION = 'Russian T72 Tanks'.
*--Reset Buffer Tables
CALL FUNCTION 'BBP_PROCDOC_RESET_BUFFER'.
Create PC*************************************************************
call function 'BBP_PD_CTR_CREATE'
exporting
I_HEADER = pc_header_out
importing
E_HEADER = pc_header_in
tables
I_ITEM = pc_item
E_PARTNER = pc_partner
I_ORGDATA = pc_org
I_LONGTEXT = pc_text
E_MESSAGES = pc_message.
write: pc_header_in-guid.
the guid will be all 0s due to the error..... Thanks for taking time to read this. I will really appreciate if anyone is able to help me solve this. Of course point will be rewarded. Thanks again! -
Error while creating contract wrt pr
hi
i am creating a pr for cotract, via me51n..selecting outline agr req..then creating pr for a raw material...
i m releasing this pr in 54n...now i go to 31k...i select wrt pr....now when i give my pr no. i get this error message
"Requisition doc. type RV not allowed with doc. type"
i have tried a whole day with different material types...always getting same error msg....
plz throw some light on this issue, if u can..
help appreciated
regards
rahulSPRO>Materials Management>Purchasing>Contract>Define Document Types
Here you select your document type and select link to purchase requisation.You can which document typease are assigned.If your entry missed add your PR document type. -
Distribution of purchase contracts from SRM4.0 to ERP 2004
Hello all,
Any body has experience in distributing Purchase contract from SRM to R/3.
i have activated BADIs
BBP_DETERMINE_LOGSYS;BBP_CTR_BE_CREATE in SRM and BBP_CTR in R/3.
Right now i can create contracts in EBP,but i unable to transfer them to backend.
Until now i have followed the documentation stategic sourcing configuration guide.
Please give your valuble information to distribute service contracts.
Thanking you,
Mahesh Madasu.Hi Mahesh,
If you are using classic scenario then try these:
Go to Table: BBP_DOCUMENT_TAB. Check whether your contract no.
Then go to T. Code: WE20 in Backend system.
Check for the Partner TYPE of you backend system in Partner profiile.
Go to classification TAB. And check the partner status is Activate or not. The status should be 'A'. Check the inbound Parameter BLAORD is present or not.
Then go to YOur SRM system and go to WE20 and activate the partner status by setting the parameter to 'A'. Then redo the processes.
This may help you.
Regards,
Charles -
IDoc error In case of ERS procedure, please enter terms of payment
Hi,
I tried to use BAPI_PO_CREATE1 to post purchase order. However, I encountered this error.
IDoc error In case of ERS procedure, please enter terms of payment
I passed the payment term in IDOC PORDCH. Segment E1BPMEPOHEADER-PMTTRMS has value filled out. This value is passed into the BAPI correctly but for some reasons, it got cleared out in the BAPI. Any ideas or suggestions would be greatly appreciated.
ThanksCheck
BAPI_PO_CREATE1 - E 06 436 In case of account assignment -
SD Customer Contract and MM Purchase Contract
Good day
I need to know if anyone has a solution on forming a relationship between these documents, and be able to report at item level for example Item x bought at $10 in the Purchase contract and sold at $15 in the Sales Contract. We need to form such a relationship between these contracts so we can report and compare line items.
Regards,
IggyI had similar requirement and used Purchase Order Header field 'Collective No' EKKO-SUBMI and put the Contract number in there. Then I used BADI ME_PROCESS_PO_CUST to do the budget check. I configured a new Contract Doc type and New PO Document type (with field selection requiring entry for EKKO-SUBMI) to provide more control. You will also want to create a custom report that lists the run rate/burn of the contract.
Other considerations
1) When the check fails, do you want error or warning ? we programmed it to be changeable via a ztable entry.
2) do you want to do any date checking of the PO header date(s) and the Contract validity date ?
3) do you want to check / verfiy the Purchasing organization of the Contract vs the PO ?
Sorry its late ! -
Define status for backend purchase order in SRM7.02
Hi,
i am working in SRM 7.02 classic scenario using PI.
When the SC is converted to Backend PO, some PO XML are failed due to various reason. Instead i need to create a PO in held status.
For the same, we have settings 'Define status for Backend purchase order' in SPRO. If we maintain the information in this setting that is enough..??It will work??
1.I heard there is some enhancement need to done for the same to work ...??if it is what is the enhancement ???
2. if it is work, then all PO will be created in Held status or only error PO will be created in Held status?? remaining in released status ???
Kindly advice me ..
ThanksAs far as, BAPI_PO_CREATE1, you need to pass
MEMORY_UNCOMPLETE = abap_true
MEMORY_COMPLETE = abap_false
for POHEADER, pass,
MEMORY = 'X'
MEMORYTYPE = 'H'
for POHEADERX, pass,
MEMORY = 'X'
MEMORYTYPE = 'X'
Though you will be using ESOA for this, this knowledge would help.
Regards,
Ganapathi -
BAPI - BUS2014 - Purchasing contracts
Hi guru's,
I am using LSMW(BAPI - BUS2014) to create purchasing Contracts(MRO outline agreements). I am getting the following error - Tax Code I1 in procedure is invalid.
But I am passing the right tax code and also checked the tax procedure. (everything is right.
Still getting the error. But I manually tried to create using the sample tax code - no error. I am not sure what's is the problem.
Can anyone help me .......pleaseOK - stupid question. I did figure it out myself. Sorry for my impatience. This is my first BAPI program, so a bit too shaky
Cheers
EssKay -
Differences in local Purchasing Contracts and GOA?
Hi all,
I am new to SRM and trying to figure out what are the differences between local purchase contracts and GOA? I know that GOA can be distributed to multiple backend systems whereas the local purchase contracts cannot be. Are there any other differences apart from this? and how does these two make difference to the business?
Thanks in advance...
Regards,
Kumar
Edited by: Kumar on Apr 7, 2008 9:47 AMHi Kumar,
As mentioned by you GOAs can be distributed to backend systems.
However the major difference between a GOA and a local SRM contract is that with GOA you can create either a contract or a scheduling agreement in the backend R/3 system.
Whenever you refer these contracts / scheduling agreements while creating a P.O in backend the status gets updated in GOA created in SRM.
You can not refer these contracts / S.A s while craeting a P.O in SRM.
Similarly the local SRM contracts can not be refered while creating P.Os in R/3 system.
Hope this makes you more clear and helps in better understanding of the issue. Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja -
hi ,
i am using the message type BLAORD in my LSMW object for Purchasing contracts. I am facing this problem of clearing of the field ZTERM (Payment Term). The value for this field is being populated by the IDOC and also posted in the field, but once it goes to next screen it clears this value. This i checked by running the IDOC using WE19. Does anyone know if this due any config settings or there is a bug in this IDOC type or is there any condition i am missing to use in my LSMW.
Thanks.
Best Regards
swanandHi Chakrapani,
That is exactly what I don't want.
My requirement is more of a non-rolling contract. Where when I create a PO w/r to a contract, the contract quantity should be replenished with the amount that the PO was created for. This goes on until the Contract Validity Period expires. I should be able to create n number of POs referring that contract within the validity period.
Regards,
Imran -
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 = <b>i_ekpa[].</b>
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
<b> poitem = i_bpoi[]
poitemx = i_bpoix[]
poschedule = i_bpos[]
poschedulex = i_bposx[].</b>
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. -
How to copy custom fields in purchasing contract
Dear all, we have added to the standard field in the purchase contract position two custom fields.
These two fields (in value) are not taken when the user create a new contract by copying from another.
Are there some exit or BADI functions that allows to copy also custom ields into corresponding destination fields whitout modify the standard code ?
In customizing it seams there are aoly rulse for copy position texts.
Regards,
Riccardo Galli - Hera group.Hi
Try to check the BADIs ME_PROCESS_OUT_CUST or ME_PROCESS_PO_CUST or the enanchement M06E0005, perhaps u can do something in the routines triggered as soon as the document is saved.
Max
Maybe you are looking for
-
Can't see month view in iCloud calendar
When I click on the month view tab at the bottom of the iCloud calendar screen, nothing happens. For that matter, clicking on the day tab doesn't do anything either. As another annoyance, in the week view I see the weeks events that were brought in f
-
Two user accounts after using migration assistant
I used migration assistant to move my iTunes library (plus all my other files) from my iMac to my macbook. I wanted to sync my iPhone on my Macbook. I didn't think it had worked but I shut down my macbook and noticed I have two user ID's now (identic
-
FAQ: How do I share my System Information?
Many issues can be more easily tracked down if the engineers can examine your Photoshop System Info. Here's how to share it easily: Launch Photoshop Choose Help>System Info... Click the [Copy] button in the dialog and paste the info into any bug repo
-
How do I transfer my itunes music library to my new computer
How do I transfer my itunes music library to my new computer (not a mac owner)?
-
What is wrong with PBO (table control)
Hi, Another beginner's question. Unable to fill table control. Following in my Program report test_tab_con. controls flights type tableview using screen 100. data: ok_code type sy-ucomm, save_ok type sy-ucomm. data: fill type i, begin