Backend System Type In Table BBP_BACKEND_DEST

Hi,
We have an SRM 5.0 system configured as extended classic communicating with an ECC6 ERP system.
While debugging some service po replication issues to the backend ERP system, I discovered that in the SRM system in the BBP_BACKEND_DEST table, our backend system is defined as R/3_4.70 type. One of the things this setting dictates is what functions are called in SRM system when creating the PO in the backend system.
My questions are,
1) Should the setting be ERP2 or R/3_4.70?
2) What are implications of changing the setting to the correct value post go live?
Thanks,
Jerry Martinek

Hi,
The setting should be ERP2 for ECC 6.0 R/3 backend system.This particlarly affects the Function modules/BAPI's which are called while replication of docs e.g. For PO ,whether to call BAPI_PO_CREATE(For R/3 4.7)/BAPI_PO_CREATE1(For ECC ) in the connected R/3 system and acc this might affect the system behaviour.
HTH
BR,
Disha.
Pls reward points for useful answers.

Similar Messages

How to get Backend (R/3) system type

Hi team,
Currently backend (R/3) system details are maintained in SPRO ->Supplier Relationship Management ->SRM Server -> Technical Basic Settings -> Define Backend Systems. Here we maintain entry of logical system, its description, RFC Destination, system type and other fields. Values of backend systems are used at lots of place by referring table BBP_BACKEND_DEST quoting system type in where clause of select query. Currently values of system type are hardcoded as R3470 but now our backend (R/3) system is upgraded to ECC6.0 and this can happen later as well whenever SAP plans for new release.
So now we are looking how we can remove this hardcoding from select query so that whenever system is upgraded, this detail need not to be changed. Please suggest the place either table or function module from where we can get details for system type.
Thanks
Siddarth

Hello Siddarth,
When you have only one backend system, better way is to use BBP_GET_BACKEND_SYSTEMS function module instead of reading directly BBP_BACKEND_DEST table using SYS_TYPE as select criteria.
If more than one backend is linked to SRM, you have to use LOGSYS given by ET_LOGICAL_SYSTEMS table from function module above.
In this way, your logsys will be used as select criteria, depending on which backend must receive RFC call. It will be also hard coded in your select, but normally you never change a log system, contrary to system type (due to upgrade).
Regards.
Laurent.

Create IDOC Type ORDERS in BackEnd System

Hello together,
we use " extended classic scenario" in our SRM 4.0 and replicate PO's in the ECC 6.0 ERP Backend System. We would like create during the replicat a Message Type (IDOC) ORDERS in Backen System. I háve customized (NACE / MN05) but it is not poosible to generate a IDOC. I have read it is necessary to activate a USER-EXIT for BBP PO's.
My question:
Which USER-EXIT and how must i create this!
Thanks for Answer!
Regards,
didisap
Edited by: Dietmar Blome on Feb 8, 2011 11:59 AM
Edited by: Dietmar Blome on Feb 8, 2011 12:01 PM

Hi,
Pls refer to following links for sample code ->
Re: Status distribution incorrect in GOA
Re: Distribution of GOA in R/3
Re: GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
Re: Source determination in backend (R/3) for distributed contract i.e. GOA
FM or BADI s' used to create a GOA
BR,
Disha.
Do reward full points for useful answers and close the thread if your query is answered.

What types of backend systems are involved (mainframe, SAP, etc.) for xi ?

What types of backend systems are involved (mainframe, SAP, etc.) for xi project?

Hi,
you could involve all systems with PI (it depends of your scenario).
This page is a good starting point for getting a better overview:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/first%252bstep%252bto%252blearn%252bsap%252bxi%252bor%252bpi
Regards
Patrick

Backend System with Release 701 are not supported

SRM 5.0
Extended Classic Scenario
CCM 2.0
When updating the vendors in SRM system using TC - BBPUPDVD getting the below error message :-
Backend System with Release 701 are not supported
Have checked in table - BBP_BACKEND_DEST, the backend entry is properly maintained.
Can any one advice.
Regards,
Jayoti
Edited by: SAP jayoti on Dec 7, 2010 1:11 PM

The problem is resolved for vendor relication after applying the below notes 1313972 and 1372175.
ECC sandbox seems to be in 701 release. When the backend system ECC is in release 701, vendor replication fails with the error message that 'Backend system release 701 not supported'. We need to apply notes 1313972 and 1372175 to fix this issue. I have applied them in Sandbox and the issue is resolved now.

How to replicate customer fields in the backend system.

Hi All,
I need to transfer PO customer fields that were created in the SRM system to backend SAP system.
I am using Extended Classic Scenario in SRM and SRM Version is 5.0.
I am able to replicate the data created in SRM system to the backend.
How ever, I found the following BADI while debugging.
1. BBP_DOC_SAVE_BADI
2. BBP_CTR_RELVAL_ICC
3. BBP_DOC_SAVE_ICC
4. BBP_F4_SAVE_DB
5. HRSYNC_P
Hence, please tell me which BADI, I need to use to send my customer fields to the backend system.
Regards,
Venky.

Hi
As Disha told, You need to create a customer Implementation of any othe BADIs using SE19 Transaction.
Say, you create an active customer Implementation of BBP_ECS_PO_OUT_BADI...
See links given in earlier reply for detailed sample code.
Write the following sample code (pls change it as per your business requirement)
METHOD if_ex_bbp_ecs_po_out_badi~bbp_b46b_po_outbound.
** Customer fields
MOVE 'POHEADER' TO w_customer_fields-refobject.
*PO approver
MOVE 'ZZAPPROVER' TO w_customer_fields-fieldname.
MOVE is_header-zzlastapprover TO w_customer_fields-container.
APPEND w_customer_fields TO ct_bapi_customer_fields.
*SC Date
MOVE 'ZZSCDATE' TO w_customer_fields-fieldname.
MOVE lv_scheader-created_at TO w_customer_fields-container(15).
APPEND w_customer_fields TO ct_bapi_customer_fields.
*Requester Org
MOVE 'ZZORGA' TO w_customer_fields-fieldname.
MOVE w_requester_orgunit TO w_customer_fields-container.
APPEND w_customer_fields TO ct_bapi_customer_fields.
endmethod.
BBP_PO_INBOUND_BADI in R/3.
method IF_EX_BBP_PO_INBOUND_BADI~BBP_MAP_BEFORE_BAPI.
data wa_customer_fields TYPE BBPS_IF_CUSTOMER_FIELDS.
data : WA_BAPI_TE_MEPOHEADER type BAPI_TE_MEPOHEADER,
WA_BAPI_TE_MEPOHEADERX type BAPI_TE_MEPOHEADERX.
data WA_EXTENSIONIN TYPE BAPIPAREX.
data txt_960(960) type c.
*** EKKO Customer fields.
*PO Number
move BBP_POHEADER-PO_NUMBER to WA_BAPI_TE_MEPOHEADER-PO_NUMBER.
move BBP_POHEADER-PO_NUMBER to WA_BAPI_TE_MEPOHEADERX-PO_NUMBER.
*ZZAPPROVER
READ TABLE BBP_CUSTOMER_FIELDS INTO wa_customer_fields
WITH KEY refobject = 'POHEADER'
fieldname = 'ZZAPPROVER'.
IF SY-SUBRC EQ 0.
MOVE wa_customer_fields-container TO WA_BAPI_TE_MEPOHEADER-ZZAPPROVER.
WA_BAPI_TE_MEPOHEADERX-ZZAPPROVER = 'X'.
endif.
*ZZSCDATE
READ TABLE BBP_CUSTOMER_FIELDS INTO wa_customer_fields
WITH KEY refobject = 'POHEADER'
fieldname = 'ZZSCDATE'.
IF SY-SUBRC EQ 0.
MOVE wa_customer_fields-container TO WA_BAPI_TE_MEPOHEADER-ZZSCDATE.
WA_BAPI_TE_MEPOHEADERX-ZZSCDATE = 'X'.
endif.
*ZZORGA
READ TABLE BBP_CUSTOMER_FIELDS INTO wa_customer_fields
WITH KEY refobject = 'POHEADER'
fieldname = 'ZZORGA'.
IF SY-SUBRC EQ 0.
MOVE wa_customer_fields-container TO WA_BAPI_TE_MEPOHEADER-ZZORGA.
WA_BAPI_TE_MEPOHEADERX-ZZORGA = 'X'.
endif.
CLEAR txt_960.
CLEAR WA_EXTENSIONIN.
write WA_BAPI_TE_MEPOHEADER to txt_960 left-justified.
WA_EXTENSIONIN-STRUCTURE = 'BAPI_TE_MEPOHEADER'.
WA_EXTENSIONIN-VALUEPART1 = txt_960(240).
WA_EXTENSIONIN-VALUEPART2 = txt_960+240(240).
WA_EXTENSIONIN-VALUEPART3 = txt_960+480(240).
WA_EXTENSIONIN-VALUEPART4 = txt_960+720(240).
append WA_EXTENSIONIN to BAPI_EXTENSIONIN.
CLEAR txt_960.
CLEAR WA_EXTENSIONIN.
write WA_BAPI_TE_MEPOHEADERX to txt_960 left-justified.
WA_EXTENSIONIN-STRUCTURE = 'BAPI_TE_MEPOHEADERX'.
WA_EXTENSIONIN-VALUEPART1 = txt_960(240).
WA_EXTENSIONIN-VALUEPART2 = txt_960+240(240).
WA_EXTENSIONIN-VALUEPART3 = txt_960+480(240).
WA_EXTENSIONIN-VALUEPART4 = txt_960+720(240).
append WA_EXTENSIONIN to BAPI_EXTENSIONIN.
endmethod.
Hope this will help.
Regards
- Atul

No PO Created in backend system after Bid is accepted

We are on SRM 4.0. using Classic Scenario
We can create a bid invitation in SRM and we have used the BADI - BBP_DETERMINE_LOGSYS to indicate to the system to create a purchase order in the backend system after the bid is accepted. We keep getting the following error in SM21: Purchase orders cannot be created without IPC pricing
Did you have to turn on the IPC in order to create the purchase order in R/3? Also, if you have used the BBP_DETEMINE_LOGSYS Badi and have example code that might be helpful as well.
If anyone has some useful BID INVITATION configuration document or tips that will be appreciated. email id is [email protected]
Thanks,
Ashwani

Hi,
The BADI is used in case of Backend contract creation.Please read the documentaion of the BADI carefully.
You can use the Business Add-In BBP_DETERMINE_LOGSYS to define your own
criteria for determining the backend system / company code. You use thi
BAdI to determine the source system for
o Shopping cart items
 In the standard system, the backend system is determined using the
 product category Define Backend Systems. The backend System is
 placed in the field ITEM_DATA-LOGICAL_SYSTEM. Then the system calls
 the Business Add-In BBP_DETERMINE_LOGSYS.
 The company code is put in the field ITEM_DATA-BC_CO_CODE. Then the
 system calls the Business Add-In BBP_DETERMINE_LOGSYS.
o Contracts
 In the standard system, the system creates contracts locally from
 Sourcing and SAP Bidding Engine You can use this BAdI to determine
 backend system.
Example
Shopping Cart:
Backend system A is determined for product category OFFICEMATERIAL. You
also want to consider the vendor and purchasing organization fields
during determination of the backend system. The purchase order is to be
created in backend system B for the vendor OFFICE1 and purchasing
organization 0001. You overwrite the field ITEM_DATA-LOGICAL_SYSTEM wit
B.
Contract:
The local system used by the standard system to create contracts is
XYZ4711. In the field CV_LOGSYS, you enter the logical system ABC0815
that links to a backend system. In this way, contracts are created in
the backend system.
Sample codes for the BADI:
method IF_EX_BBP_DETERMINE_LOGSYS~DETERMINE_LOGSYS.
data: w_acct_data type enriched_acct_data.
data: w_acct_icom type BBP_PDS_ACC_ICOM.
data: w_et_messages type BBP_TMESSAGES_BADI.
data: re_obj(40).
data: imkey(8).
field-symbols: <waItem> type bbp_oci_enritem.
field-symbols: <waAcct> type bbp_oci_enracct.
field-symbols: <f1> type any.
if not acct_data[] is initial.
loop at item_data assigning <waItem>.
loop at acct_data assigning <waAcct> where line = <waitem>-line.
check <waAcct>-acc_cat = 'RE'.
if not <waAcct>-acc_str is initial.
CALL FUNCTION 'Z_RE_ACCT_ASSGN'
EXPORTING
ACC_STR = <waAcct>-ACC_STR
BUKRS = <waItem>-BE_CO_CODE
IMPORTING
RE_OBJ = RE_OBJ
IMKEY = IMKEY
TABLES
BBP_RETURN = w_et_messages.
endif.
if not imkey is initial and w_et_messages[] is initial.
move imkey to <waAcct>-rl_esk_key.
move re_obj to <waAcct>-acc_str.
modify acct_data from <waAcct>.
endif.
endloop.
endloop.
endif.
endmethod.
OR
method IF_EX_BBP_DETERMINE_LOGSYS~DETERMINE_LOGSYS.
data: ztprod type zprod1.
data result(4).
data tline TYPE LINE OF bbpt_detlogsys_item.
loop at item_data into tline.
 case sy-uname.
 when 'BUYER3'.
 if tline-product eq '69E2D3C8AF4B5C4CBDCC73A50C58EFA2' or
 tline-product eq '6BB856ADA25D584FA0B5A2FDCDA27766' or
 tline-product eq 'F31AD68E8EDCE646A9C7ECC4F24CE464' or
 tline-product eq 'ABC0320E1A37E743B75406DF0B7C53BF' or
 tline-product eq '3C0665006B2D2A43B3A1CC74B560E8A9' or
 tline-product eq '8F97635441496647A69CD021A5FFF4D2'.
 tline-be_co_code = '1000'.
 tline-logical_system = 'F47CLNT800'.
 tline-BE_PUR_ORG = 'O 50000660'.
 tline-BE_PUR_GROUP = 'O 50000662'.
 modify item_data from tline.
 endif.
 when others.
 select single * from zprod1 into ztprod where product eq tline-product.
 if sy-subrc eq 0.
 tline-be_co_code = '3000'.
 tline-logical_system = 'F47CLNT800'.
 modify item_data from tline.
 elseif tline-product is initial.
 tline-be_co_code = '3000'.
 tline-logical_system = 'F47CLNT800'.
 tline-BE_PUR_ORG = 'O 50000612'.
 tline-BE_PUR_GROUP = 'O 50000614'.
 modify item_data from tline.
 endif.
 endcase.
endloop.
endmethod.
Also if you have activated "EXTENDED CLASSIC SCENARIO"( SPRO>Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario),then IPC is mandatory for ECS .
BR,
Disha.
Do reward points for useful answers.

RARs' criteria for analyzing roles in ECC backend system?

Hi All,
I'm working on setting up a prototype of Access Control 5.3. In RAR I notice the analyzis of roles is not done for all roles.
I have taken note 1179717 into consideration, and also performed mass user compare. But not all roles are analyzed yet.
Some of the roles are not tied to a profile, but it seems RAR does not segregate on this.
Does anyone have a list of criteria RAR uses when looking at what roles to analyze?
Thanks in advance,
Leif Nilsson

Hello Leif,
You can find SAP Notes only on SAP Service Marketplace
https://websmp103.sap-ag.de/notes
You cannot directly compare the numbers of RAR with the roles you want to analyze, without following the below steps completed successfully.
1- Connect the SAP backend system to Risk Analysis and Remediation and complete all post-install activities.
2- First you have to run the report RHAUTUPD_NEW in your backend system.
3- Select all roles, select 'Perform User Master Comparison', but check only "cleanups" from the 'editing types'.
4- Now execute the report.
5- When finished re-run a full user, role, profile synchronization for this SAP backend system in Risk Analysis and Remediation.
There are two types of synchronization, Full and Incremental:
6- Select Full synchronization
7- Perform Batch Risk Analysis. This is the core function of RAR. By performing a batch risk analysis, the security of the users/roles/profiles are compared against the Segregation of Duties rules to identify possible conflicts. It then makes a call to the back-end system to retrieve the authorization assigned to each of these user/roles/profiles. It then performs the analysis against the rules in the front-end.
8- Run Management Reports. Running this piece of the job is what ultimately updates the numbers you see on the Management Report and table virsa_cc_prmvl is updated.
9- You will get the list of total Number of Violations , the Violation count by Risk and Violation Count by Permission
Now you are ready to compare the numbers in the following way, seen below.
10- Log on to your SAP backend system and use transaction SE11 to identify single roles with profiles from table AGR_1016, but note that roles having multiple profiles appear multiple times in this table.Count the number of distinct roles in table AGR_1016.
11- Now, only count those distinct roles in AGR_1016 that have also an entry in AGR_DEFINE. You can do this with a small custom report or with Excell.
12- In your SAP backend System use transaction SE11 to count the number of profile in table USR10 having the flag 'AKTPS' set to 'A'. Each profile appears only once in this table.
This number should match the number on profiles synchronized in Risk Analysis and Remediation.
Thanks,
Mohi

Error while reading the PO in the Backend system   !

Hi all,
We are working on SRM 5.0(SP12) and Extended classic scenario.
The problem is that after the PO ís ordered it gives the message " Error while reading PO in backend system Inform system administrator" .
When I check the PO number in R/3 it does not exist.
The number range is correct both in SRM and R/3 (external no. range is ticked).
In RZ20,i find the log:
The error ocurred by processing event SENT_AGAIN with GUID 490F3C0834351AC6E10000000AE48838 and object_id= 3000000307
The R/3 System Version is 4.6C.
Any help is highly appreciated.

Hi,
Thanks for the response.
This problem is hapeening for all PO's in the system.
The no range is smae in both the systems.In SPRO ,howevre we have not maintained the no range in SRM for R/3 system.
Here is the config details:
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Number Ranges>SRM Server Number Ranges-->Define Number Range for Local Purchase Orders
EC     3000000000     3999999999     3000000320
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Number Ranges>SRM Server Number Ranges-->Define Number Ranges per Backend System for Follow-on Documents
SAPE02_050     EC            RS
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings-->
Define Transaction Types
ECDP     PO: Direct Material     03     02
ECPO     Purchase Order     EC
I have already gone thorugh note Note 1258634 - Certain events cannot be de-activated.
This note is however valid for SRM 6 and 7.
PO is not reaching R/3 system.
No error in sm58/sm12.
The status in BBP_PD for the PO is :
Stats:
           Status         Description                    Inact
HEADER     I1009          Held                           X
HEADER     I1015          Awaiting Approval              X
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1043          Ordered
HEADER     I1080          In Transfer to Execution Syst. X
HEADER     I1180          Document Completed
Awaiting your inputs.

Error while posting return delivery to backend system

Hi All,
We are facing problem when we are posting return delivery. Currently we are in ECS implementation. Our SRM is 7.0 EHP3.
Scenario goes as, SC is created then PO is created then further confirmation is created and on creating return delivery of this confirmation, this return delivery goes error in process.
Now on further analyzing, I found out that outbound IDoc in SRM is getting posted successfully but when ECC receives this IDoc it is saying please enter reason for movement 122. This reason for return is already entered while creating the return delivery. But this reason is not flowing in IDoc (Message Type MBGMCR and Basic Type MBGMCR01) in SRM and further to ECC. This field MOVE_REAS in IDoc is populating blank.
Can anybody help me resolving this problem? Any pointers or SAP notes related to can also be suggested.
Thanks
Siddarth

Hi Siddarth,
Please implement the note below, which is included in SP05.
2007628 - Return delivery cannot be posted in backend system as reason for return delivery is empty
Regards,
Wendy

How to find out Shopping Cart created in backend system or ECC system

Hi All,
I am new to SAP SRM7.0. The Client has implemented "Extended Classic Scenario". i.e. SC>Approval>PO>Confirmation>Invoice process in ECC.
We created few SC with "Free text" i.e. Describe what you need option in SC.
The SC is created with 4 digit number 2690. Also, the Status " Approved". since its low value.say 5 GBP.
I have like 25 to 30 SC created like this: I need to know the following:-
1. When i open SC and look for Related document, i see only SC number , but no Follow on document. not sure why ?
2. How can i know the list of SC in backend system. i.e like ECC of the SRM backend system. Please let me know the table name it get stored.. I searched EBAN and found only those which has PO is stored.
also can you please advise if by creating the SC in SRM.. will get replicated in ECC system ?. or only if Follow on doc gets created it will get replicated in ECC system?.
Thx
MJ

Hi,
SC is never replicated to backend.
Extended scenario document flow is SC -> SRM PO(Main) -> ERP PO(Copy).
Please go to BBP_PD transaction and navigate to SC item detail. You see what is the follow-on document.
Regards,
Masa

Goods Receipt not transferred to the Backend System R/3

We are currently using BBPCRM4.0 & SAP R/3 4.7 (extended scenario)
For a particular Purchase Order which has a material number, We cannot transfer GR to the Backend System R/3 successfully.(The shopping cart of unsuccessfully transferred GR is created by using material)
When I check R/3 using WE05, I can find the message "The plant data of the material G09002202 is locked by the user MRP_RFC". This must be the reason why GR is not transferred successfully to the Backend System, but I do not know what this message mean.(As you see, MRP_RFC is the user name that connects SRM and R/3. + That moment the material is not locked by any user in R/3)
If we try to create the GR document again in SRM, the message "Item is already being processed" is shown, so cannot make BUS2203 Docs.
To sort out this, we remove the GR Transfer Error Information in
BBP_DOCUMENT_TAB.
After removing the information of this error in BBP_DOCUMENT_TAB, surprisingly we can make GR successfully.
Weird!.
Only for a particular PO which has a material, but not everytime.
Sometimes this problem happens.
At the first time, it doesn't work, but after removing the data from BBP_DOCUMENT_TAB, when we try GR again it works.
Could you help me why this symptom happends..?
Edited by: Hyangsook Moon on Feb 28, 2008 6:44 AM

Hi Hyangsook Moon,
The system is allowing you to create Confirmation again in SRM because the status is not yet updated in SRM since the G.R is not created in the backend successfully.
Since the confirmation is created in SRM and could not able to create G.R in R/3 through IDOC the system is giving you message as " Document is being processed".
So the system is allowing you to create confirmation again once you delete the table entry.
Hope this makes you more clear.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

How to Change Source system type of ECC6.0 in BW system

Hi BW Experter,
 I connected ECC6.0 PRD system with BI7.0 PRD system , the connection is successful,
but the source system type of ECC6.0 PRD is not collect . The ECC6.0 PRD is as a
BW system type in the source system list of bw system .
 I found that Tcode RSA1 has ever been run in PRD ECC6.0 , So I did a connection testing of
ECC6.0 QA with BI7.0 PRD .
 Step 1. Connect ECC6.0 QA with BI7.0 PRD , ECC6.0 QA was as SAP system type in source system list of bw system .
 Step 2. Run tcode RSA1 in QA ECC6.0
 Step 3. Delete connection of ECC6.0 QA with BI7.0 PRD .
 Step 4. Connect ECC6.0 QA with BI7.0 PRD again , ECC6.0 QA was as SAP system type in source system list of bw system .
 I want to know how to change ECC6.0 PRD source system type to SAP .
If it can't been change to SAP ,Is there any impact when ECC6.0 PRD is as bw system type in source system .
Thank you for your help .

I got the soulution from note: 1087980 - ECC Source systems appearing in BI folder
Summary
Symptom
Source system connection for an ECC system appears in the BI folder, rather than in SAP folder, as expected.
Other terms
Wrong folder,RSA1, RSBASIDOC, RSAP_BIW_DISCONNECT
Reason and Prerequisites
Transaction RSA1 was inadvertently used on an ECC system , thereby creating a 'Myself' source system entry in RSBASIDOC table
Solution
This is just a display issue and does not cause any operational issues. Therefore, it need not be corrected, especially if the ECC system in question is used as a BI system as well.
If it is absolutely required that the ECC source system appear in the correct folder, perform the following steps.
1. Check that an entry with SRCTYPE 'M' exists in table RSBASIDOC table of ECC source system.
2. Note the values for SLOGSYS and RLOGSYS. It should be same.
3. Run the function module RSAP_BIW_DISCONNECT in the ECC system.
 NOTE: Never run that function module in a BI system!
4. Enter the following values :
I_BIW_LOGSYS <RLOGSYS> as noted in step 2
I_OLTP_LOGSYS <SLOGSYS> as noted in step 2
I_FORCE_DELETE <X>
< DO NOT ENTER ANY VALUE IN THE FIELD - RFC target sys !!!!! >
5. Go to RSA1-> Source systems in the BI system connected to the ECC system.
6. Select the ECC source system and select RESTORE in the right click menu.
Now the ECC system should appear in the SAP folder.
If running RSAP_BIW_DISCONNECT results in an error like OTHER_ERROR, please check if a valid RFC connection exists in transaction sm59.
If the myself source system connection cannot be deleted in any case, log a service marketplace message with SAP Support.
Edited by: fang frank on Jul 15, 2009 8:31 AM

JDBC Adapter - DELETE operation not working in receiver backend system

Hi All,
In my scenario ,I want to delete entire records of the table from one backend system.
I have created the inbound message and after mapping it is as below:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:abc_delete xmlns:ns0="http://abc/xi/BACKEND/IB_IF_18/100">
<STATEMENTNAME>
<F12345 action="DELETE" />
</STATEMENTNAME>
</ns0:abc_delete>
here F12345 is the table name.
When I execute this scenario I get black and white flag in XI SXMB_MONI but in backend system (SQL Server) no records get deleted the table is as it is.

Please have a look on this (same mentioned by Bhavesh)...
http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/frameset.htm
 <StatementName3>
<dbTableName action=DELETE>
<key1>
<col2>val2old</col2>
<col4>val4</col4>
</key1>
<key2>
<col2>val2old2</col2>
</key2>
</dbTableName>
</StatementName3>
● action=DELETE
Statements with this action cause existing table values to be deleted. One or more <key> elements formulate the condition for which table values are deleted. The names of <key> elements are arbitrary. Column values within a <key> element are combined with a logical AND; different <key> elements are combined with a logical OR.
The corresponding SQL statement for StatementName3 in the example above is as follows:
DELETE FROM dbTableName WHERE ((col2=val2old AND col4=val4) OR (col2=val2old2))
The response document contains the following element:
<delete_count>count</delete_count>
If there is no <key> element, or if there is a <key> element but it is empty, then no condition is specified and the entire table is to be deleted. This may not be permitted by the configuration of the JDBC adapter for security reasons and will therefore result in an error during message processing and an appropriate error message.
Thanks
Farooq.

Change in backend system

Hi SRM Gurus,
Project Scenario is ECC5 as backend system integrated with SRM 4.0( SSP scenario and with Catalog CCM2.0)
Implementation scenario is Extended classic.
Backend system will be changed to ECC6 from ECC 5.0 with company code consolidation.
ECC6 is installed on separate server for implementing changes in FI (separate Dev, QA, Prod environment ) and will be integrated with SRM4.0
Question is that when we integrate SRM4.0 with ECC6, do we need to run transaction BDLS to change logical system name in SRM for backend system?
As all product categories and vendor are same in ECC 6.0 will this work.
Also there is GUID reference in table CRMLSSGUID & CRMPRLS in R3. How this will be taken care.
Option 2:
no need to run BDLS in SRM. We need to define new backend system and replicate all master data (product categories, UOM & vendor master) from ECC6 to SRM4.0.
SRM experts, please suggest as for me option 2 is suitable way.
Thanks & Regards,
Avinash

Hi SRM experts,
In Org structure Product categories will be maintained with Source system (new backend system) in extended attributes. Also for vendors new backend system maintained in attributes.
With these settings user will able to see the product categories, vendors pertaining to New backend system.
Please share your views.
Regards,
Avinash

Backend System Type In Table BBP_BACKEND_DEST

Similar Messages

Maybe you are looking for