Error in transmission

Hi All,
One shopping cart was created with status as approved but in the Follow on Documents tab nothing was mentioned regarding the follow on documents created or not?
Then I checked the BBP_PD, and found that PO No has been assigned to the particular shopping cart wherein the status of each item was showing as Item in transfer process.
In order to get the status of shopping cart than I ran both the programs CLAEN_REQREQ_UP and BBP_GET_STATUS_2, but all in vain ,since the status of the shopping cart was still showing without any Follow on Documents.
Then i execute the BBP_PD_SC_RESUBMIT Function module,since the items were showing as Items in transfer process but after executing the same now the
shopping cart has started giving Error as "Error in transmission" and with an Error message as "Shopping Cart 0010128502 (Purchase order 3000061718): ME218 External document number 3000061718 already assigned "
Could you please provide any feedback regarding how to get back the status of the shopping cart with Follow On Documents No mentioned in the check status
option of the EBP Web version. We are working in SRM 4.0 /EBP V5.0.
An immediate respone in this regard is highly appreciated please.
Regards,
Pranab

Hi
Please go through the following SAP OSS Notes, which will defninitely help ->
Re: ECS describe requirement not transferred to backend
Re: Transfer PO from SRM to R/3 - Error in Process
Note 841021 - Manual price entered disappears - error 06 218
Note 932236 - BAPI_PO_CREATE1: Purchase order price unit not transferred
Note 580225 - Purchasing BAPIs: Conditions and pricing
Note 853970 - BAPI_PO_CREATE1: Net price is not transferred
Note 571860 - BAPI_PO_CREATE1: Price is not transferred
Note 487605 - ME21N: 06 218 'Net price must be greater than 0'.
Refer to these link as well for details.
Problem with BAPI_PO_CREATE1
PO created with status : Transfer Failed (E.Sys.)
Problem with BAPI_PO_CREATE1
Re: Error in pricing when doing sourcing in EBP 4.0
Re: STO classic scenario SRM 4.0
Re: Incorrect status in pricing - Short dump - IPC
Hope this will help.
Regards
- Atul

Similar Messages

Error in transmission with BBPSC01

I have typical problem where in
When ordered, SC created via BBPSC02 goes through without errors. But the cart that is created via BBPSC01 will have ' Error in Transmission, With an error 'SE142 please enter qunatity in line 3000111'. This error is coming from the backend in the RFC mode while debugging BBP_REQREQ_TRANSFER.
This happens only when number items in the cart are more than four, if the items were less than or equal to 4, follow on document is created even in case of BBPSC01.
We are implementing BADI for Follow-on-Document for service-category.
May I know 1.what could be the difference between these two templates.2.And where they exactly these dump the values 3. How could I go from here 4.what fields I need to look while debugging.
Input will be:
BBPSC02: User selects description item and the service button, enters the price, quantiy as 1 service unit and selects the a specific-service-Category
BBPSC01: Selects the Same category as in BBPSC02 enters the same data .
Thank you,
Manyam

Thank you.
This is a long code please bear with me. And provide your suggestion.
METHOD if_ex_bbp_create_req_back~fill_req_interface.
Method Parameters:
*LOGICAL_SYSTEM TYPE BBP_BACKEND_DEST-LOG_SYS OPTIONAL
*REQ_ITEMS TYPE BBP_REQ_ITEM_SPOOL
*REQ_ITEM_ACCOUNT TYPE BBP_REQ_ACCT_SPOOL
*REQ_ITEM_TEXT TYPE BBP_REQ_TEXT_SPOOL
*REQ_LIMITS TYPE BBP_REQ_LIMITS_SPOOL
*REQ_CONTRACT_LIMITS TYPE BBP_REQ_LIMITS_CONTR_SPOOL
*REQ_SERVICES TYPE BBP_REQ_SERV_SPOOL
*REQ_SERV_ACCOUNT TYPE BBP_REQ_SERV_ACC_SPOOL
*REQ_SERV_TEXT TYPE BBP_REQ_SERV_TEXT_SPOOL
*REQ_ADDRDELIVERY TYPE BBP_REQ_ADDRDELIVERY_SPOOL
This is the logic to create a Service Requisition based on a service
material group selected in the Shopping Cart. This logic is based on
SAP's standard function SPOOL_RQ_READ_BAPI_EXPORTS from which this
BADI is called.
INSERT FUNCTION SPOOL_RQ_READ_BAPI_EXPORTS TO REPROCESS DATA FOR
SERVICE SPECIAL REQUESTS. -- IOK 07/13/01
*function spool_rq_read_bapi_exports.
""Lokale Schnittstelle:
*" IMPORTING
*" VALUE(REQNO) LIKE REQHEAD-REQNO
*" VALUE(REQUIS_NUMBER) LIKE BAPIEBANC-PREQ_NO
*" EXPORTING
*" VALUE(SKIP_ITEMS_WITH_ERROR) LIKE BAPIMMPARA-SELECTION
*" VALUE(LOGICAL_SYSTEM) LIKE BBP_BACKEND_DEST-LOG_SYS
*" TABLES
*" REQUISITION_ITEMS STRUCTURE BAPIEBANC
*" REQUISITION_ACCOUNT_ASSIGNMENT STRUCTURE BAPIEBKN
*" REQUISITION_ITEM_TEXT STRUCTURE BAPIEBANTX
*" REQUISITION_LIMITS STRUCTURE BAPIESUHC
*" REQUISITION_CONTRACT_LIMITS STRUCTURE BAPIESUCC
*" REQUISITION_SERVICES STRUCTURE BAPIESLLC
*" REQUISITION_SRV_ACCASS_VALUES STRUCTURE BAPIESKLC
*" RETURN STRUCTURE BAPIRETURN
*" REQUISITION_SERVICES_TEXT STRUCTURE BAPIESLLTX
*" REQUISITION_ADDRDELIVERY STRUCTURE BBPS_RQADDRDELIVERY_46
*" CONTROL_RECORD STRUCTURE BBP_CONTROL_RECORD
*" EXCEPTIONS
*" INTERNAL_ERROR
---- Data Declaration - from LBBP_BS_RQTOP -
- Header -
DATA: reqheader TYPE reqhead.
- Header services -
DATA: reqheaders TYPE reqheads.
- References -
TYPES: reqreferences_type TYPE reqref.
DATA: reqreferences TYPE STANDARD TABLE OF reqreferences_type
 INITIAL SIZE 10.
DATA: l_reqreferences TYPE reqreferences_type,
 x_reqreferences TYPE reqreferences_type.
- Administrative lines requirement request -
TYPES: reqlines_type TYPE reqline.
DATA: reqlines TYPE STANDARD TABLE OF reqlines_type
 INITIAL SIZE 10.
DATA: l_reqlines TYPE reqlines_type.
- MRO-Lines requirement request -
TYPES: reqlinemas_type TYPE reqlinema_eci.
DATA: reqlinemas TYPE STANDARD TABLE OF reqlinemas_type
 INITIAL SIZE 10.
DATA: l_reqlinemas TYPE reqlinemas_type.
- SRV-Lines requirement request -
TYPES: reqlinesrs_type TYPE bbps_reqlinesr_eci.
DATA: reqlinesrs TYPE STANDARD TABLE OF reqlinesrs_type
 INITIAL SIZE 10.
DATA: l_reqlinesrs TYPE reqlinesrs_type.
- Texts requirement request -
TYPES: reqtexts_type TYPE reqtext.
DATA: reqtexts TYPE STANDARD TABLE OF reqtexts_type
 INITIAL SIZE 10.
DATA: l_reqtexts TYPE reqtexts_type.
*- Delivery address
TYPES: reqaddress_type TYPE reqaddress.
DATA: reqaddress TYPE STANDARD TABLE OF reqaddress_type
 INITIAL SIZE 10.
DATA: l_reqaddress TYPE reqaddress_type.
- Account assignment requirement request -
TYPES: reqaccts_type TYPE reqacct_470.
DATA: reqaccts TYPE STANDARD TABLE OF reqaccts_type
 INITIAL SIZE 10.
DATA: l_reqaccts TYPE reqaccts_type.
- tablekey with the shortlife-line -
DATA: BEGIN OF shortkey,
 client TYPE ec_client, "REQLINE-CLIENT,
 reqno TYPE ec_reqno, "REQLINE-REQNO,
 reqsline TYPE reqsline, "REQLINE-REQSLINE,
 reqlline TYPE reqlline, "REQLINE-REQLLINE,
 END OF shortkey.
- tablekey with the longlife-line -
DATA: BEGIN OF longkey,
 client TYPE ec_client, "REQLINE-CLIENT,
 reqno TYPE ec_reqno, "REQLINE-REQNO,
 reqlline TYPE reqlline, "REQLINE-REQLLINE,
 END OF longkey.
DATA: BEGIN OF bankey,
 preq_no TYPE banfn, "BAPIEBAN-PREQ_NO,
 preq_item TYPE bnfpo, "BAPIPOGN-PREQ_ITEM,
 END OF bankey.
any other working fields
DATA: h_preq_item TYPE bnfpo, "BAPIEBANC-PREQ_ITEM,
 h_srv_item TYPE bnfpo, "BAPIEBANC-PREQ_ITEM,
 h_logsys TYPE log_system. "reqref-logical_system.
DATA: h_serial_no TYPE dzebkn. "BAPIEBKN-SERIAL_NO.
DATA: h_packno_item TYPE packno, "BAPIESLL-PCKG_NO,
 h_packno_srv TYPE packno, "BAPIESLL-PCKG_NO,
 h_introw TYPE srv_line_no, "BAPIESLL-LINE_NO,
 h_serial_no_srv TYPE dzekkn, "BAPIESKN-SERIAL_NO,
 h_srv_outl_created,
 next TYPE i,
 h_index LIKE sy-tabix,
 h_wempf TYPE wempf. "bapiekkn-gr_rcpt.
------ End of std data declaration -
DATA: l_req_items TYPE bapiebanc,
 l_req_item_account TYPE bapiebkn,
 l_req_item_text TYPE bapiebantx,
 l_req_limits TYPE bapiesuhc,
 l_req_contract_limits TYPE bapiesucc,
 l_req_services TYPE bapiesllc,
 l_req_serv_account TYPE bapiesklc,
 l_req_serv_text TYPE bapieslltx,
 l_req_addrdelivery TYPE bbps_rqaddrdelivery_46.
DATA:
 old_req_items TYPE STANDARD TABLE OF bapiebanc,
 old_req_item_account TYPE STANDARD TABLE OF bapiebkn,
 old_req_item_text TYPE STANDARD TABLE OF bapiebantx,
 old_req_limits TYPE STANDARD TABLE OF bapiesuhc,
 old_req_contract_limits TYPE STANDARD TABLE OF bapiesucc,
 old_req_services TYPE STANDARD TABLE OF bapiesllc,
 old_req_serv_account TYPE STANDARD TABLE OF bapiesklc,
 old_req_serv_text TYPE STANDARD TABLE OF bapieslltx,
 old_req_addrdelivery TYPE STANDARD TABLE OF
 bbps_rqaddrdelivery_46.
DATA: l_mat_group TYPE comm_category-category_id.
DATA: f_change_required TYPE c,
 f_limit_change TYPE c,
 f_mat_sr_change TYPE c,
 f_first_change TYPE c VALUE 'X'.
Data declaration for Shopping Cart number and PO number
DATA: reqno TYPE ec_reqno,
 requis_number TYPE banfn.
DATA: l_current_item TYPE bnfpo,
 line_item(5) TYPE n.
---- Begin Processing ----
DATA: l_requis_number TYPE banfn. "jms 022802
DEBUG TOOL ****** Goto SM50
*data: i type i value 1.
*while i <> 0.
i = i + 1.
*endwhile.
END DEBUG TOOL *******
Get Req Number and Shopping Cart Number
read table req_items into l_req_items index 1.
requis_number = l_req_items-preq_no.
select single reqno
 into (reqno)
 from reqref
 where refnumber = requis_number.
read detailed data from the requirement request
call function 'BBP_REQREQ_GETDETAIL'
 EXPORTING
 reqno = reqno
 IMPORTING
 req_header = reqheader
 req_header_srv = reqheaders
 TABLES
 req_reference = reqreferences
 req_line = reqlines
 req_line_mat = reqlinemas
 req_line_srv = reqlinesrs
 req_text = reqtexts
 req_acct = reqaccts
 req_address = reqaddress
 EXCEPTIONS
 not_found = 1
 foreign_lock = 2
 no_enqueue_possible = 3
 others = 4.
if sy-subrc <> 0.
 raise internal_error.
 exit.
endif.
Begin JMS
PO_NUM = PO_HEADER-PO_NUMBER.
CMH Data declaration
TYPES: et_header TYPE bbp_pds_sc_header_d.
DATA: t_et_header TYPE STANDARD TABLE OF et_header INITIAL SIZE 0,
 x_et_header TYPE et_header.
TYPES: et_item TYPE bbp_pds_sc_item_d.
DATA: t_et_item TYPE STANDARD TABLE OF et_item INITIAL SIZE 0,
 x_et_item TYPE et_item.
TYPES: sc_header TYPE bbp_pds_sc_header_d.
DATA: x_sc_header TYPE sc_header.
TYPES: sc_is_pd TYPE xfeld.
DATA: l_sc_is_pd TYPE sc_is_pd.
TYPES: sc_item TYPE bbp_pds_sc_item_d.
DATA: t_sc_item TYPE STANDARD TABLE OF sc_item INITIAL SIZE 0,
 x_sc_item TYPE sc_item.
TYPES: sc_account TYPE bbp_pds_acc.
DATA: t_sc_account TYPE STANDARD TABLE OF sc_account INITIAL SIZE 0,
 x_sc_account TYPE sc_account.
TYPES: sc_partner TYPE bbp_pds_partner.
DATA: t_sc_partner TYPE STANDARD TABLE OF sc_partner INITIAL SIZE 0,
 x_sc_partner TYPE sc_partner.
TYPES: sc_confirm TYPE bbp_pds_con.
DATA: t_sc_confirm TYPE STANDARD TABLE OF sc_confirm INITIAL SIZE 0,
 x_sc_confirm TYPE sc_confirm.
TYPES: sc_longtext TYPE bbp_pds_longtext.
DATA: t_sc_longtext TYPE
 STANDARD TABLE OF sc_longtext INITIAL SIZE 0,
 x_sc_longtext TYPE sc_longtext.
TYPES: sc_limit TYPE bbp_pds_limit.
DATA: t_sc_limit TYPE STANDARD TABLE OF sc_limit INITIAL SIZE 0,
 x_sc_limit TYPE sc_limit.
TYPES: sc_orgdata TYPE bbp_pds_org.
DATA: t_sc_orgdata TYPE
 STANDARD TABLE OF sc_orgdata INITIAL SIZE 0,
 x_sc_orgdata TYPE sc_orgdata.
TYPES: sc_tax TYPE bbp_pds_tax.
DATA: t_sc_tax TYPE STANDARD TABLE OF sc_tax INITIAL SIZE 0,
 x_sc_tax TYPE sc_tax.
TYPES: sc_pridoc TYPE bbp_pds_prc.
DATA: t_sc_pridoc TYPE STANDARD TABLE OF sc_pridoc INITIAL SIZE 0,
 x_sc_pridoc TYPE sc_pridoc.
TYPES: sc_messages TYPE bbp_pds_messages.
DATA: t_sc_messages TYPE
 STANDARD TABLE OF sc_messages INITIAL SIZE 0,
 x_sc_messages TYPE sc_messages.
TYPES: sc_actval TYPE bbp_pds_actval.
DATA: t_sc_actval TYPE STANDARD TABLE OF sc_actval INITIAL SIZE 0,
 x_sc_actval TYPE sc_actval.
TYPES: sc_acc_actval TYPE bbp_pds_actval.
DATA: t_sc_acc_actval TYPE STANDARD TABLE OF sc_acc_actval
 INITIAL SIZE 0,
 x_sc_acc_actval TYPE sc_acc_actval.
TYPES: sc_header_rel TYPE bbp_pds_hrel.
DATA: t_sc_header_rel TYPE STANDARD TABLE OF sc_header_rel
 INITIAL SIZE 0,
 x_sc_header_rel TYPE sc_header_rel.
TYPES: sc_itmlim_rel TYPE bbp_pds_ilrel.
DATA: t_sc_itmlim_rel TYPE STANDARD TABLE OF sc_itmlim_rel
 INITIAL SIZE 0,
 x_sc_itmlim_rel TYPE sc_itmlim_rel.
TYPES: it_cuf_item_type TYPE bbps_cuf_item.
DATA: t_it_cuf_item TYPE STANDARD TABLE OF it_cuf_item_type
 INITIAL SIZE 0,
 x_it_cuf_item TYPE it_cuf_item_type.
- Contract limits -
TYPES: reqconlimits_type TYPE reqheads.
DATA: reqconlimits TYPE STANDARD TABLE OF reqconlimits_type
 INITIAL SIZE 10.
DATA: l_reqconlimits TYPE reqconlimits_type.
DATA: lv_abort TYPE xfeld,
 lv_is_pd TYPE xfeld,
 lv_deliv_date LIKE sy-datum,
 lv_tabix LIKE sy-tabix,
 lv_line TYPE introw,
 lv_msarg TYPE char200,
 lv_sc_guid TYPE bbp_pdview_iap-header,
 lv_req_guid TYPE bbp_pdview_iap-header.
DATA: x_requis_number TYPE bapiebanc.
IF NOT req_items[] IS INITIAL.
 CLEAR l_requis_number.
 READ TABLE req_items INTO x_requis_number INDEX 1.
 l_requis_number = x_requis_number-preq_no.
 requis_number = x_requis_number-preq_no.
ENDIF.
Get PO Guid from Backend Table.
SELECT SINGLE guid
 INTO lv_req_guid
 FROM bbp_pdbei
 WHERE be_object_id = l_requis_number
 AND be_object_type = 'BUS2105'.
Get Shopping Cart Guid from PO Guid
SELECT SINGLE header
 INTO lv_sc_guid
 FROM bbp_pdview_iap
 WHERE guid = lv_req_guid.
Get detail from shopping cart
CALL FUNCTION 'BBP_PD_SC_GETDETAIL'
 EXPORTING
 i_guid = lv_sc_guid
 i_with_itemdata = 'X'
 IMPORTING
 e_header = x_sc_header
 ev_is_pd = l_sc_is_pd
 TABLES
 e_item = t_sc_item
 e_account = t_sc_account
 e_partner = t_sc_partner
 e_confirm = t_sc_confirm
 e_longtext = t_sc_longtext
 e_limit = t_sc_limit
 e_orgdata = t_sc_orgdata
 e_tax = t_sc_tax
 e_pridoc = t_sc_pridoc
 e_messages = t_sc_messages
 e_actval = t_sc_actval
 e_acc_actval = t_sc_acc_actval
 e_header_rel = t_sc_header_rel
 e_itmlim_rel = t_sc_itmlim_rel.
lv_is_pd = l_sc_is_pd.
message handling
IF NOT t_sc_messages[] IS INITIAL.
 CALL FUNCTION 'BBP_BS_ADD_MESSAGES'
 IMPORTING
 ev_abort = lv_abort
 TABLES
 it_messages = t_sc_messages.
ENDIF.
if error occured set alert/ exception.
IF NOT lv_abort IS INITIAL.
 CALL FUNCTION 'BBP_ALERT_SB_LOCAL'
 EXPORTING
 msgid = 'BBP_PD'
 msgno = 280
 msgarg1 = lv_msarg
 EXCEPTIONS
 invalid_parameters = 1
 OTHERS = 2.
 RAISE internal_error.
ENDIF.
map shopping cart in new structure into old structure to be able
to continue with the old coding
REFRESH t_sc_messages.
CALL FUNCTION 'BBP_SC_MAP_PD_TO_REQ'
 EXPORTING
 is_new_header = x_sc_header
 IMPORTING
 es_reqhead = reqheader
 es_req_heads = reqheaders
 es_cuf_header = is_cuf_header
 TABLES
 et_req_reference = reqreferences
 et_req_line = reqlines
 et_req_line_mat = reqlinemas
 et_req_line_srv = reqlinesrs
 et_req_text = reqtexts
 et_req_acct = reqaccts
 et_req_address = reqaddress
 et_req_conlimit = reqconlimits
 it_new_items = t_sc_item
 it_account = t_sc_account
 it_partner = t_sc_partner
 it_longtext = t_sc_longtext
 it_limit = t_sc_limit
 it_orgdata = t_sc_orgdata
 it_tax = t_sc_tax
 it_actval = t_sc_actval
 it_itmlim_rel = t_sc_itmlim_rel
 et_messages = t_sc_messages.
 et_cuf_item = it_cuf_item
 et_cuf_acc = it_cuf_acc.
IF NOT t_sc_messages[] IS INITIAL.
message handling
 CALL FUNCTION 'BBP_BS_ADD_MESSAGES'
 IMPORTING
 ev_abort = lv_abort
 TABLES
 it_messages = t_sc_messages.
ENDIF.
if error occured set alert/ exception.
IF NOT lv_abort IS INITIAL.
 CALL FUNCTION 'BBP_ALERT_SB_LOCAL'
 EXPORTING
 msgid = 'BBP_PU'
 msgno = 326
 msgarg1 = lv_msarg
 EXCEPTIONS
 invalid_parameters = 1
 OTHERS = 2.
 RAISE internal_error.
ENDIF.
End insert 03/26/2003
ReqReferences doesn't list the PO item number. We'll need that to
associate the WBS to a Service Sub Item later. Let's put it in.
SORT reqreferences BY client refnumber reqlline.
LOOP AT reqreferences INTO x_reqreferences.
 IF x_reqreferences-refline IS INITIAL.
 IF l_requis_number = x_reqreferences-refnumber. "jms 022802
 ADD 1 TO line_item.
 ELSE.
 l_requis_number = x_reqreferences-refnumber. "jms 022802
 line_item = 1.
 ENDIF.
 Accumulate the line item
 x_reqreferences-refline = line_item.
 MODIFY reqreferences FROM x_reqreferences INDEX sy-tabix.
 ENDIF.
ENDLOOP.
SORT reqlines BY client reqno reqlline.
SORT reqreferences BY client reqno reqlline counter.
SORT reqlinemas BY client reqno reqsline reqlline.
SORT reqlinesrs BY client reqno reqsline reqlline.
SORT reqaccts BY client reqno reqlline serial_no. " note 359605
CLEAR: h_preq_item.
CLEAR: h_srv_item, h_srv_outl_created,
 h_packno_item, h_packno_srv, h_introw.
First, the Shopping Cart number should be extracted from REQREF table
based on the Req number.
take all items with the specific reference number
LOOP AT reqreferences
 INTO l_reqreferences "iok 091701
 WHERE refnumber EQ requis_number.
 if logical_system is initial.
 logical_system = l_reqreferences-logical_system.
 endif.
 MOVE-CORRESPONDING l_reqreferences TO longkey.
read table reqlines with key longkey binary search.
 READ TABLE reqlines INTO l_reqlines "iok 091701
 WITH KEY client = longkey-client
 reqno = longkey-reqno
 reqlline = longkey-reqlline
 BINARY SEARCH.
 CHECK sy-subrc EQ 0.
 h_preq_item = l_reqlines-reqsline+5(5).
clear h_preq_item.
Change line_type based on Material Group
add code here later.
 CLEAR: f_change_required,
 f_mat_sr_change,
 f_limit_change.
 SELECT SINGLE category_id
 INTO l_mat_group
 FROM comm_category
 WHERE category_guid = l_reqlines-category.
Check if Services Special Request
 IF l_reqlines-catalogid IS INITIAL AND
 l_reqlines-product IS INITIAL AND
 l_mat_group(1) = 'S' AND
 l_reqlines-line_type = '1'. "Service Special Request
 Set flags for future processing
 l_reqlines-line_type = '3'.
 f_change_required = 'X'.
 f_limit_change = 'X'.
Check if Material Special Request
 ELSEIF l_reqlines-catalogid IS INITIAL AND
 l_reqlines-product IS INITIAL AND
 l_mat_group(1) <> 'S' AND
 l_reqlines-line_type = '1'. "Material Special Request
 Set flags for future processing
 f_change_required = 'X'.
 f_mat_sr_change = 'X'.
 ENDIF.
 CHECK f_change_required = 'X'.
For Material Special Requests only need to select and store UNSPSC
code -- iok 092401
 IF f_mat_sr_change = 'X'.
 Get UNSPSC code (first hit) based on Material Group and store
 in text id B05. iok 092101
 READ TABLE req_items INTO l_req_items
 WITH KEY preq_item = h_preq_item
 mat_grp = l_mat_group.
 READ TABLE req_item_text INTO l_req_item_text
 WITH KEY preq_no = requis_number
 preq_item = l_req_items-preq_item
 text_id = 'B05'.
 IF sy-subrc <> 0.
 CLEAR l_req_item_text.
 Find a UNSPSC Code from a Material Group .. even it's arbitrary
 SELECT unspsc_code UP TO 1 ROWS
 FROM zxl8_category_id
 INTO l_req_item_text-text_line
 WHERE category_id = l_mat_group.
 ENDSELECT.
 If nothing found then fill in a dummy UNSPSC. The first
 letter of the Material will designate whether it's a Material
 or Service.
 IF sy-subrc NE 0.
 Move the Material Group value into a holding variable
 CONCATENATE l_mat_group(1) 'XXXXXXXX'
 INTO l_req_item_text-text_line.
 ENDIF.
 l_req_item_text-preq_no = requis_number.
 l_req_item_text-preq_item = l_req_items-preq_item.
 l_req_item_text-text_id = 'B05'.
 INSERT l_req_item_text INTO TABLE req_item_text.
 ENDIF.
 CONTINUE. "to next item.
 ENDIF.
 IF f_first_change = 'X' AND f_limit_change = 'X'.
 Save old P.Req. data and clear tables
 old_req_items[] = req_items[].
 old_req_item_account[] = req_item_account[].
 old_req_item_text[] = req_item_text[].
 old_req_limits[] = req_limits[].
 old_req_contract_limits[] = req_contract_limits[].
 old_req_services[] = req_services[].
 old_req_serv_account[] = req_serv_account[].
 old_req_serv_text[] = req_serv_text[].
 old_req_addrdelivery[] = req_addrdelivery[].
 REFRESH: req_items,
 req_item_account,
 req_item_text,
 req_limits,
 req_contract_limits,
 req_services,
 req_serv_account,
 req_serv_text.
 req_addrdelivery.
 CLEAR f_first_change.
 ENDIF.
Limit
 IF l_reqlines-line_type EQ '3'.
 and not reqheaders-limit is initial.
 DATA: l_reqreferences_temp TYPE reqreferences_type.
 +JMS 2/26/2002
 CLEAR l_reqreferences_temp.
 READ TABLE reqreferences INTO l_reqreferences_temp
 WITH KEY client = longkey-client
 reqno = longkey-reqno
 reqlline = longkey-reqlline
 BINARY SEARCH.
 IF sy-subrc = 0.
 h_preq_item = l_reqreferences_temp-refline.
 ENDIF.
 CLEAR l_req_items.
 READ TABLE old_req_items INTO l_req_items
 WITH KEY preq_item = h_preq_item.
 MOVE-CORRESPONDING l_req_items TO reqheaders.
 reqheaders-begdate = l_req_items-deliv_date.
 reqheaders-limit = l_req_items-c_amt_bapi.
 reqheaders-exp_value = l_req_items-c_amt_bapi.
 reqheaders-gr_ind = 'X'.
 reqheaders-reqno = l_req_items-preq_no. "jms 022602
 CLEAR l_req_items.
INSERT FORM **** CREATE_SERVICE_ITEM
 h_packno_item = h_packno_item + 1.
 h_packno_srv = h_packno_srv + 10000.
 h_introw = h_introw + 1.
 CLEAR l_req_items. " Note 364396
 MOVE-CORRESPONDING reqheaders TO l_req_items.
 l_req_items-preq_no = reqheaders-reqno. "jms 022602
 l_REQ_ITEMS-PREQ_NO = REQUIS_NUMBER. "jms 022602
l_REQ_ITEMS-PREQ_ITEM = H_PREQ_ITEM + 1. "iok 091801
 l_req_items-preq_item = h_preq_item. "iok 091801
 l_current_item = h_preq_item. "iok 092101
 h_srv_item = l_req_items-preq_item.
 h_preq_item = h_preq_item + 1.
 IF NOT reqheaders-limit IS INITIAL OR
 NOT reqheaders-exp_value IS INITIAL.
 IF reqheaders-gr_ind IS INITIAL.
 l_req_items-item_cat = '1'.
 ELSE.
 l_req_items-item_cat = '9'.
 ENDIF.
 l_req_items-deliv_date = reqheaders-begdate.
 ELSE.
 l_req_items-item_cat = '9'.
 ENDIF.
 IF l_req_items-del_datcat IS INITIAL.
 l_req_items-del_datcat = '1'.
 ENDIF.
 l_req_items-quantity = 1.
 l_req_items-pckg_no = h_packno_item.
 IF l_req_items-preq_name EQ space.
 l_req_items-preq_name = sy-uname.
 ENDIF.
 APPEND l_req_items TO req_items.
END OF FORM INSERTION ********
 l_req_limits-pckg_no = h_packno_item.
 l_req_limits-limit = reqheaders-limit.
 l_req_limits-exp_value = reqheaders-exp_value.
 l_req_limits-no_limit = reqheaders-no_limit.
 l_req_limits-no_frlimit = 'X'.
 APPEND l_req_limits TO req_limits.
*.... Account assignment
 clear requisition_srv_accass_values.
 CLEAR l_req_serv_account.
 l_req_serv_account-pckg_no = h_packno_item.
 MOVE-CORRESPONDING l_reqlines TO longkey.
 read table reqaccts with key longkey binary search. "iok 091801
 READ TABLE reqaccts INTO l_reqaccts "iok 091801
 WITH KEY client = longkey-client
 reqno = longkey-reqno
 reqlline = longkey-reqlline
 BINARY SEARCH.
 IF sy-subrc = 0.
 LOOP AT reqaccts
 INTO l_reqaccts
 WHERE reqno = l_reqreferences-reqno
 AND reqlline = l_reqreferences-reqlline.
INSERT FULL FORM *********** FILL_REQ_ACCT_SRV
 DATA: acctcomp1 TYPE bapiebkn,
 acctcomp2 TYPE bapiebkn,
 high_serial TYPE dzekkn. "LIKE BAPIEKKN-SERIAL_NO.
 CLEAR l_req_serv_account-serial_no.
 CLEAR acctcomp1.
 MOVE-CORRESPONDING l_reqaccts TO acctcomp1.
 CLEAR: acctcomp1-preq_no,
 acctcomp1-preq_item,
 acctcomp1-serial_no,
 acctcomp1-created_on,
 acctcomp1-created_by,
 acctcomp1-preq_qty,
 acctcomp1-distr_perc,
 acctcomp1-change_id,
 acctcomp1-currency.
 LOOP AT req_item_account INTO l_req_item_account.
 CLEAR acctcomp2.
MOVE-CORRESPONDING l_req_item_account TO ACCTCOMP2. "is blank
 CLEAR: acctcomp2-preq_no,
 acctcomp2-preq_item,
 acctcomp2-serial_no,
 acctcomp2-created_on,
 acctcomp2-created_by,
 acctcomp2-preq_qty,
 acctcomp2-distr_perc,
 acctcomp2-change_id,
 acctcomp2-currency.
 IF acctcomp1 EQ acctcomp2 AND h_srv_outl_created IS INITIAL.
 l_req_serv_account-serial_no = l_req_item_account-serial_no.
 EXIT.
 ENDIF.
 high_serial = l_req_item_account-serial_no.
 ENDLOOP.
 h_srv_outl_created = ' '.
 IF l_req_serv_account-serial_no IS INITIAL.
 MOVE-CORRESPONDING l_reqaccts TO l_req_item_account.
 l_REQ_item_ACCOUNT-PREQ_NO = REQUIS_NUMBER. "jms 022702
 l_req_item_account-preq_no = l_req_items-preq_no."jms 022702
 l_req_item_account-preq_item = h_srv_item.
REQUISITION_ACCOUNT_ASSIGNMENT-WBS_ELEM_E = REQACCT-BBP_PROJECT.
 l_req_item_account-serial_no = high_serial + 1.
 l_req_serv_account-serial_no = l_req_item_account-serial_no.
 APPEND l_req_item_account TO req_item_account.
 ENDIF.
END OF FORM INSERTION ***********
 h_serial_no = h_serial_no + 1.
 l_req_serv_account-serno_line = h_serial_no.
 l_req_serv_account-percentage = l_reqaccts-distr_perc.
 APPEND l_req_serv_account TO req_serv_account.
 ENDLOOP.
INSERT FULL FORM **************** CONVERT_ACCOUNT_***_CAT
data: account_tab LIKE bbp_pds_acc OCCURS 0 WITH HEADER LINE.
 DATA: account_tab TYPE STANDARD TABLE OF bbp_pds_acc.
 DATA: l_account_tab TYPE bbp_pds_acc.
 DATA: h_knttp TYPE knttp.
 move the accounting data to that item into the interface table
 LOOP AT reqaccts
 INTO l_reqaccts
 WHERE reqno EQ l_reqreferences-reqno
 AND reqlline EQ l_reqreferences-reqlline.
 MOVE-CORRESPONDING l_reqaccts TO l_account_tab.
 APPEND l_account_tab TO account_tab.
 ENDLOOP.
 call the convert API
 CALL FUNCTION 'BBP_ACCCAT_MAP_EXP'
 EXPORTING
 i_logical_system = logical_system
 IMPORTING
 e_r3_acc_cat = h_knttp
 TABLES
 i_pd_account = account_tab.
 IF h_knttp IS INITIAL.
 h_knttp = 'X'.
 ENDIF.
 +JMS 2/14/2002 Issue #1590
 CLEAR account_tab.
 REFRESH account_tab.
 account assignment category - set in the correct item
 LOOP AT req_items
 INTO l_req_items
 WHERE preq_item EQ l_req_item_account-preq_item.
 l_req_items-acctasscat = h_knttp.
 MODIFY req_items FROM l_req_items INDEX sy-tabix.
 ENDLOOP.
END OF FORM INSERTION ************
 ELSE.
INSERT FULL FORM ************* Form CONVERT_ACCOUNT_***_CAT_U
 LOOP AT req_items
 INTO l_req_items
 WHERE preq_item EQ l_current_item.
 l_req_items-acctasscat = 'U'.
 MODIFY req_items FROM l_req_items INDEX sy-tabix.
 ENDLOOP.
END OF FORM INSERTION ************
 ENDIF.
 Get UNSPSC code (first hit) based on Material Group and store
 in text id B05. iok 092101
 READ TABLE req_items INTO l_req_items
 WITH KEY preq_item = l_current_item
 mat_grp = l_mat_group.
 READ TABLE req_item_text INTO l_req_item_text
 WITH KEY preq_no = requis_number
 preq_item = l_req_items-preq_item
 text_id = 'B05'.
 IF sy-subrc <> 0.
 CLEAR l_req_item_text.
 Get UNSPSC Code from Material Group .. even if arbitrary
 SELECT unspsc_code UP TO 1 ROWS
 FROM zxl8_category_id
 INTO l_req_item_text-text_line
 WHERE category_id = l_mat_group.
 ENDSELECT.
 If nothing found then fill in a dummy UNSPSC. The first
 letter of the Material will designate whether it's a Material
 or Service.
 IF sy-subrc NE 0.
 Move the Material Group value into a holding variable
 CONCATENATE l_mat_group(1) 'XXXXXXX'
 INTO l_req_item_text-text_line.
 ENDIF.
 l_req_item_text-preq_no = requis_number.
 l_req_item_text-preq_item = l_req_items-preq_item.
 l_req_item_text-text_id = 'B05'.
 INSERT l_req_item_text INTO TABLE req_item_text.
 ENDIF.
 Don't send Internal Note to Backend
 delete req_item_text where text_id = 'B02'.
Service -- NOT NEEDED -- IOK 07/13/01
 elseif not reqlines-reqsline is initial
 and reqlines-line_type eq '2'.
 move-corresponding reqlines to shortkey.
 read table reqlinesrs with key shortkey binary search.
 if sy-subrc = 0.
 h_serv = reqlinesrs.
 append h_serv.
 endif.
material item -- NOT NEEDED -- IOK 07/13/01
 ENDIF.
ENDLOOP.
Services -- NOT NEED -- IOK 07/13/01
IF f_limit_change = 'X'.
Check multiple account assignment
 LOOP AT req_items INTO l_req_items.
 h_index = sy-tabix.
 CLEAR next.
 LOOP AT req_item_account
 INTO l_req_item_account
 WHERE preq_item EQ l_req_items-preq_item.
 next = next + 1.
 ENDLOOP.
 IF next > 1.
 l_req_items-distrib = '2'. "prozentuale Verteilung
 l_req_items-part_inv = '1'.
 l_req_items-gr_non_val = 'X'.
 MODIFY req_items FROM l_req_items INDEX h_index. "217191
 modify requisition_items. "217191
 ENDIF.
 ENDLOOP.
ENDIF.
Remap delivery address for backend processing
LOOP AT req_addrdelivery INTO l_req_addrdelivery.
 MOVE: l_req_addrdelivery-name_2 TO l_req_addrdelivery-name,
 l_req_addrdelivery-c_o_name TO l_req_addrdelivery-name_2.
 CLEAR: l_req_addrdelivery-c_o_name.
 MODIFY req_addrdelivery FROM l_req_addrdelivery INDEX sy-tabix.
ENDLOOP.
CHM 07/16/2003 Changed created by to always be actual creator even
 for on behalf of situations
 LOOP AT req_items
 INTO l_req_items.
 l_req_items-created_by = x_sc_header-created_by.
 MODIFY req_items FROM l_req_items INDEX sy-tabix.
 ENDLOOP.
CMH - end change
MA 12/10/04 - Pass MP2 number from Manu Prod# to Req Item Text
LOOP AT req_items INTO l_req_items.
 READ TABLE t_sc_item into x_sc_item
 WITH KEY number_int = l_req_items-preq_item.
 l_req_item_text-preq_no = requis_number.
 l_req_item_text-preq_item = l_req_items-preq_item.
 l_req_item_text-text_id = 'B06'.
 l_req_item_text-text_line = x_sc_item-manu_prod.
 INSERT l_req_item_text INTO TABLE req_item_text.
ENDLOOP.
ENDMETHOD.

Error in transmission for SC trying to create a PO .

What does this error mean I am getting the error in SC
Case 1 : ME 083 Enter Material Group however the material group =Product category is already in the SC .
Please explain on how to get this error fixed ?
Does the user have to recall the SC for the error to be rectified OR A new SC has to be created ?
Case 2 : For some SC though I see Error in transmission yet not able to see the SC in RZ20 . Pleas explain on how to diagnose and check what the error is ?
regards
Vinita

Hi Vinita,
For Case I - Please check the posts below. They are similar errors but not exactly the same.
http://scn.sap.com/thread/3233354
http://scn.sap.com/thread/3439656
https://scn.sap.com/thread/2083247
For Case II -
If you could find whether it is Local or Backend error then the analysis could be done with the focus way -
Otherwise If your not able to see in RZ20 - then try to go to BBP_PD -- Check for all master data -- check whether all things are maintained one by one in PPOMA as well as backend system.
I hope you must have already checked the material group in the both the systems.
I will check and update you if i could find anything.
Thanks.
From RBEI,
Snehal

Error in transmission but No Error

Hi,
We are trying to create PO with SC having catalog items. After status approved it shows status as error in transmission but shows no error.
Also there is no entry found in application monitorRZ20.
Even debugging FM BBP_REQEQ_TRANSFER also did not helped.
Please help.
~Vipin

PO may not be created so far.
you must get an error in rz20 . it takes 3 minutes to see error in rz20 or sc application monitor.
even if you dont have error. go to monitor shopping cart -> click follow on document icon- now error message will be thrown in rz20 after 2-3 minutes for quick analysis.
i am pretty sure there is some data problem in that shopping cart. check vendor / account assignment details available and valid.
however check slg1 log.
Muthu

Monitor Shopping cart does not find Error in transmission

hello,
We recenlty upgraded to SRM 5.0 stack SAPKIBKT15. Now we find that Monitor Shopping cart doesn't display the shopping cart with errors in transmission. We know we have them in the system but it displays only when the shopping cart number who has the error in transmission is also entered. So only looking for the status Error in transmission' doesn't give any shopping carts in monitor shopping cart but when entering the shopping number and status 'Error in transmission' it does show.
Any idea ?
Thanks as ever!

Ok I will give it another try, as you are so kind to help me!!
Users use Monitor Shopping cart in SRM (transaction BBP_MON_SC) With this transaction they can search for shopping carts on General data and item data. If shopping carts end in error in transmission they can search on status 'Error in transmission'. We now have shopping carts with an error in ttransmission. Monitor shopping cart doesn't display them unless I enter the shopping cart number as well. Previously we could enter only status 'Error in transmission and it displayed all the shopping carts with an error in transmission.
I see transaction Rz20 and I see the errors in the drill down you suggest but what do I need to do to make the Monitor shopping cart display all the errors in transmission when searching for that status ?
Thanks!

PO confirmation havinmg status error in transmission

Hi,
We did PO confirmation in EBP but faile din transfer to backend R/3.
In Bbp_pd the message is 'Error in transmission' and in PO follown documnets the message is "error in transfer"
Why it is haapeing and how to resolve it.
Thank you.

Hi,
Check in RZ20 for the detailed error message. Let us know what the message exactly is.
Most of the Service confirmation errors arise out of Acc.assignment. Check whether the Cost center or the GL account is blocked for posting to the respective company code / Profit center.
The best way would be to advise the user to post the entry sheet in R/3 over tcode ML81N.
At the time of saving the transaction, a pop-up will be displayed if its a error with the option to display the error log. click on the error log to display the actual error message.
Cheers,
Akash

Status I1112 "Error In Transmission"

Hi Experts,
I'm no technical expert in SRM but know a little on how it works.
We're currently implementing an Extended Classic Scenario (SANDBOX) and done several pre-configuration to make everything works (simple SC creation)
Current system we have is EP <> SRM 7.0 <> ECC 6.05.
The scenario we have now is 1 step shopping cart approval. What I understand for an extended classic scenario is that SC is created/approve in SRM and PR is created/approve in ECC (Is PR created manually once SC is created/approved or automatically created?). Then PO is created (when PR is sent to SRM??).
RFC configuration settings are working. Logical systems in SRM and ECC is maintained. Queues are registered.
Activated Activate Hierarchies for Product Categories, Suppliers, and Contracts (both int proc and ext: set as always for the time being)
Applied several notes that are applicable to current support package: 1498793, 1499352, 1514713, 1517301, 1641325. All packages are up to date both ECC and SRM (SRM_SERVER - SAPKIBKV10; SRM_PLUS - SAPKIBK210; SRM_EXPL - SAPK-70009INSRMEXPL; SRM_EXT 700 - SAPK-70010INSRMEXT) . Still no luck after shopping cart is approved.
Any hints or suggestions on what to do to make at least one SC into successful?

Hello,
As you are in Extended Classic Scenario, Shopping Cart created will give a Purchase Order as follow-on document in SRM.
Then, when approval workflow is finished for this SRM PO, purchasing document (PO) will be replicated to backend system.
Check OSS note below:
[1641325 - Shopping Cart status 'Error in transmission' with PO created|https://websmp109.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1641325&_NLANG=E]
You can also check all OSS notes dealing with status I1111 ('Item in Transfer Process'), I1112 ('Error in transmission') and I1113 ('Follow-on Document Created').
Analysis/correction reports Z_SC_STATUS_CHECK_XX are given with those OSS notes.
Regards.
Laurent.

Error in Transmission after SHC approved

Hi all,
I have a problem where my shopping cart is approved but throws an error while creating the backend follow on documents "Error in transmission"
I have read the earlier thread which is similar to this but did not help me great. There were suggestion of debugging FM BBP_REQREQ_TRANSFER. Please give me details of what areas in the FM i need to concentrate on, since my technical team is not too familiar with EBP.
These are the ALERTS that are found in BBP_PD of the SHC
Shopping basket\backend application errors
Arguement 1: 0000185325
Arguement 2: 3000037297
Arguement 3: SE142 Please enter quantity in line 3000111
(what does this exactly mean???)
Arguement 4: 00000000000000000000
Hoping to hear from you
Thanks
Regards,
Sunny

Hi Sunny,
Does it assign PO Number, PO Object BUS2012, Backend Doc Type for SC line Item. You can check these in BBP_PD. If you do not see these, then you have problem before transmission. But, normaly error in transmission, happens when PO creation is tried unable to do successfully.
As i mentioned earlier, debug thru Req transfer function module, see where it fails.
or You can use tocde BBP_MON_SC and debug thru, Put a breat point at META_PO_CREATE or META_PR_CREATE depending what is created in R/3.
I remembet you mentioned you are on live EBP system and happens to few carts. Hence, Pls check in R/3 are you able to create manually PO or PR for same data that SC is tring to create and see do you have any problem in R/3.
Regard,
Jay

SC error " error in transmission" for reservation

We are using SRM 5.0 with ECC5.0
We are able to create complete cycle with Shopping cart >PO in ECC5.0>Confimation-->Invoice in EBP
But when SC is created for stock items it is showing status as "error in transmission or error in process"
What is missing?
Rgds
NNK

Hi
What movement type are you using in the SRM org structure ?
- 201
What reservation number range did you configure in SRM and ECC ?
ECC - RS 0038300000 0038399999 (External)
SRM - RS 0038300000 0038399999
What transaction type have you in SRM
-SHC for shopping cart under transcation category BUS2121
We are able to see reservation number 003830005 created in SRM in T-CODE BBP_PD under object ID "BE_OBJECT_ID"
But in Status
0000000001 I1112 Error in transmission
In details screen following error appears
47CCE58225A94442A0B60421CAD71D27 I1111 X 004
47CCE58225A94442A0B60421CAD71D27 I1112 003
Regards,
NNK

PO Error in transmission SRM 7.0

Hi SRM Experts,
Need your Urgent support/advise on a PO Transmission error issue... Transfer from SRM 7.0 to Back End R/3 system
Pl. find below the details..
The PO 9XXXXXXXX has the status Error in Process...
I tried to manually push PO from SRM 7.0 to Back End R/3, The following error message was encountered in RZ20 log..
PO 9XXXXXXX EXCEPTION CONDITON "FAILURE " RAISED
PO 9XXXXXXX Transfer Failed Resubmit...
I checked some earlier posts on this related issue & found that one of the causes could be Account assignment data Not in Sync b/w SRM & Back End R/3.
Accordingly, when I checked the PO in SRM 7 & R/3 Back End, I found that item 2 ( the PO 9XXXXX has 3 items in SRM & only 2 in R/3 Back end) has been deleted in SRM 7 ..but not replicated to back end R/3..
So R/3 was rejecting further replication from SRM 7..,... I did the following:-
1.Via Change PO option, I Undelete item 2 & order/transfet..still material group error R/3 rejects the material group on item 2 as user had set product type to 02(services) instead of 01(materials) which is Not per CLient design..
2.Tried to delete item 2 ,Accnt assignment data in the portal & r eorder , still sytstem does not accept change, error in process continues
3.Tried to duplicate item 2 into a new line, still error in process
Pl can any one advise what I am missing?
Additonal Data:-
CLient on SRM 7.0 with ECS & back End R/3 with ECC 6.0
BR//Ranganath

Hi Ranganath,
You mentioned that line item 2 user selected Product type as Service and which is why you may be getting error. If you select Service product type then you have to set up Item category "D" in the backend system for the PO Document type.
Along with that you have to set up ECC system to have default values at client level. You can check that in SPRO --> Material Management --> External Service Management --> Source Determination and Default values --> For Client. In there just set up default unit of measure as AU if you would like to pass the line item.
Hope this helps.
Thank you
Ritesh

Process overdue error asynchronus transmission of info idoc 2 error

Hi
For an r/3 job i am getting the below message and it is not progressing from last 2 days and failing in BW with Process overdue error. Can somebody advise me on this.
data soucrce :0CO_OM_OPA_6
The job stucked for last 10 hrs and showing 0 records in BW.
Thanks
Subbu

Hi,
What are you trying to do...
are you performing any loads from the above said DataSource from R/3 to BW or
are you replicating the DataSource from your source system to BW side...
in any of the above cases..please check whether you have connected well to your source system from your BW system...
for this right click on source system in source system section of RSA1..and check..if everything is fine...then it should take such long time to complete your activity.
if not check in Tcode:SM59 to make sure the connectivity..which your problem can be solved sucessfully...
hope this is clear for you...
Regards
Ramsunder

SC - error in transmission

I have a SC that's errored out and the msg reads:
Shopping Cart # (Purch. Requisition #) ME013 Document type XXXX not allowed with doc. category B (Please check input).
The SC was created via a catalog. This doc type is set up properly in the backend and we know that because it's been in used for years now. We don't create PReq. It either creates a PO if it comes from a catalog, or special requests go to the sourcing cockpit.
Does anyone know what's causing this error? And how I can fix it?
Thanks.
SN

Hi
I am hoping that you can help me.
I am getting the error message ME 013, at the moment, and like you I am a little suspect if the error message is correctly indicating what the cause of the problem is. We are currently using EBP v3.0, and have never had any problem with configuration we have in place in our backend system with regard to item categories. Rather than do the double upgrade we are doing a new install of SRM 7.0, and wonder if there is something missing or incorrect with a setting in the Org Structure.
Although you mention more than one company, and at the moment I am only configuring for one company, it would be really helpful if you could tell me exactly what you did to resolve your problem.
Many Thanks
Claire

Error by sending a Web Service request

Hi,
we generated a WSDL from an outbound-interface and build a web application with it. When we send a Web Service request to SAP-XI from our Web Dynpro client application, we get an error "CALL_CONSUMER_ERROR" (of category "XI_J2EE_MESSAGING_SYSTEM"). We find the following entry in the message-log of the adapter engine:
Error: Return of synchronous errormessage to the calling application: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: iaik.security.ssl.SSLException: Server certificate rejected by ChainVerifier.
Error: The Transmission of the message with https://hpsaps01.inveos.com:8001/sap/xi/engine?type=entry failed, because: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: iaik.security.ssl.SSLException: Server certificate rejected by ChainVerifier
does anybody know, how to solve this problem?
Greetings
Hildegard

Hi Stefan,
correct certificates are established in the meantime and the error-message in the adapterlog has changed. The errorcode still remains "CALL_CONSUMER_ERROR" of category "XI_J2EE_MESSAGING_SYSTEM".
Adapter-log:
Error: Return of synchronous errormessage to the calling application: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: java.net.ConnectException: Connection refused.
Error: The Transmission of the message with https://hpsaps01.inveos.com:8001/sap/xi/engine?type=entry failed, because: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: java.net.ConnectException: Connection refused
Are there missing any more permissions or is this another error in the configuration?
Regards
Hildegard

Error : "Backend data could not be read"....

Hi
We are having SRM 4.0 with backend R/3 4.7.
When shopping cart is approved, getting error message "Backend data could not be read".
In BBP_PD, status is showing "Error in Transmission"
Observed that BE_OBJECT_TYPE and BE_OBJECT_ID fields are blank in table BBP_PDBEI.
At the bottom of BBP_PD, in the alert section in Monitor field a message appeared as "Shopping Basket\Spooler Communication errors".
Is this error something related to RFC authorization?
Please tell me what is the reason.
Thanks and Regards
Jagadish

Hi Jagdish,
As you said, this may be related to RFC communication.
During the SC approval, SRM will determine the follow on doc type (RS, RQ, PO) depending on your customizing, the SC item data, and what R/3 let you create (after META_INTERPRETE_DAT).
Just after this step, the backend doc type & ID are stored in SC item backend references. But here your fields BE_OBJECT_TYPE and BE_OBJECT_ID fields are blank.
It makes me suppose that a backend communication error made this process failure.
If the RFC authorizations were not correct, then this would be the case for ALL your SC !!! I don't think this is the case.
Do you have lots of errors like this one ?
Maybe the backend was not available or overloaded at that time. Is this an error in production ? What are your volumetrics ?
Can you check in SM37 if you have some jobs named PO_JOB created at this time or scheduled since this date ?
Rgds
Christophe
PS: please reward points for helpful answers

SC error in transmisstion

SRM Gurus,
I have a SC that's in error in transmission status and the error message is 06750: In case of evaluated receipt settlement, please enter tax code. Does anyone know what this is referring to? The error keeps the SC from creating a PO in the backend.
Thanks.
SN

Hi SN,
This error comes when the ERS (Evaluated Receipt Settlement) is active for the Vendor in the system.
Deactivate ERS check box in Vendor Master data in R/3 for that vendor and also from the Vendor Tab of the Vendor (Business Partner) in SRM using Manage Business Partners link based on your requirement.
This will definitely resolve your issue. Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Error in transmission

Similar Messages

Maybe you are looking for