MM SUS Vendor Replication Error: Error in ALE Service

Dear Experts,
We are implementing MM SUS (SRM 5.0). As a part of this we need to replicate vendors from ECC to SUS system via XI. We have created a Reduced Message Type Z_CREMAS_SUSMM and had set up the partner profile in WE20 with SUS logical system as destination and specifing the Message Type, and port of the XI system
We executed the transaction BD14 for replication, it is resulting in error 29 : Error in ALE Service : Entry in Outbound table not found.
Please provide inputs to overcome this problem
Thank you,
Regards,
Ravi

Hi Ahmed,
Thanks for your reply. We have configured as per SAP configuration guide(plan driven procurement). As per this we had set up partner profile for SUS logical system and define the outbound parameters with receiver port of XI system.
If you feel one more partner profile need to be setup for XI system then please advise us for necessary configuration.
Thanks
Ravi

Similar Messages

SUS Vendor Replication Error (CL_BBPX_TRADING_PARTNER_SUS_IN)

Hi SRM Gurus!
We are in the process of replicating our SRM vendors to SUS via XI and we are encountering some error. After running tcode BBP_SUPP_INI, we checked tcode SXMB_MONI in SUS and we found 2 flags, one is checkered (processed successfully) and the other is red (system error). We checked the trace of the XML file and we found this error:
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:00:282 -The password must contain at least 1 special characters E:BBP_BUPA:060 -Error while trying to create contact person. Inform system administration Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
The same error is shown in transaction SLG1. (The password must contain at least 1 special characters)
We are wondering which password is the system checking? The password of PIAPPLUSER, the XI service user processing the transaction already contains a special character and we do not know of any other user that the system may be calling.
We hope anyone could shed light in this issue. We are in SRM 5.5 SP13, PI 7.0.
Thanks in advance!

Hi
assume that you have replicated vendors to sus. how the supplier to acess your SUS browser?
check with basis person ? what profile he maintained to create a pasword ?
SAP Note 1003820 - Supplier cannot be registered
Symptom
After you replicate a supplier in SRM-SUS, the supplier receives an e-mail
that contains the registration ID. When the supplier attempts to use the
logon link to register, the system displays the error message stating that
the registration ID is not valid, and the supplier cannot be registered.SAP Note 880735 - UME/SUS: error with administrational
user creation
br
muthu

Will MM-SUS scenario work perfectly if we replicate SUS vendors from SRM

Dear Gurus'
We are going to use MM-SUS scenario in our classic implementation of SAP SRM. However, we are not replicating the SUS vendors directly from MM system using BD14.
Instead, we are replicating the SUS vendors from SRM system by ticking the 'Portal Vendor' check box in SAP SRM.
Will all MM-SUS scenario work perfectly in such cases? If I refer the configuration of MM-SUS scenario, it mentions about special configuration for transferring the confirmation key from ECC vendor master data to SUS system. How it will be taken care in SRM-SUS vendor replication?
Could you please share your experience?
Thanks and regards,
Ranjan
Ranjan Sutradhar

hi,
Are the Suppliers getting Time Out Errors?
are they able to create the documents ?
I have seen these sort of problems in many customers , there is one performance note created by SAP to resolve this issue.
I do not have the note number now.
But you can search the same with keyword performance along with the component areas
SRM-SUS
ans SRM-EBP-TEC-PFM.
Best would be to enquire with SAP also..

Vendor Master Replication Error from ECC to SUS : Error in ALE Service

Dear Experts,
We are implementing MM SUS (SRM 5.0). As a part of this we need to replicate vendors from ECC to SUS system via XI. We have created a Reduced Message Type Z_CREMAS_SUSMM and had set up the partner profile in WE20 with SUS logical system as destination and specifing the Message Type, and port of the XI system
We executed the transaction BD14 for replication, it is resulting in error 29 : Error in ALE Service : Entry in Outbound table not found.
Please provide inputs to overcome this problem
Thank you,
Regards,
Ravi

Hi,
Check
Re: Idoc Error Status "Entry in outbound table not found "
Looks like some issue with the partner profile set up for the sender or receiver of the EDI message in WE20.
Set up them again and When these have been set up try reprocessing your IDocs from BD87

Error in ALE Service While Creation of Vendor Master

hi,
I am using a scenario where a third party system is sending vendor master data to a R/3 system The file is picked up by the file adapter(sender) and mapped to IDOC format, using Idoc adapter (receiver). A Vendor is then created by posting the CREMAS03 IDOC into the R/3 system.
Everything goes fine till the Idoc comes into the R/3 system. There in BD87(Idoc Status Monitor), getting the "Error in ALE Service" error. When expanded further the specific error is that of "Cross-system company code xxxx does not exist". What is generally the cause of this error and how would I resolve it?
For those of you who have attended TBIT 40, this scenario is Example 1 - Creation of Vendor Master Data.
Any help would be appreciated?
regards,
SK

one more thing
if you want to be sure that you're using the right data
try to set your system to send the vendor data out
first - send it from BD14
and then you'll know which fields do you need
if you do that take a look at segment E1LFB1M
and check for BURKS
Regards,
michal

Vendor replication Error. SAP R/3 to EBP system

Hi Guys,
I am using SRM 5.0. I am getting error while replicating the vendor master from SAP R/3 to SRM system.
T-code: SLG1
Warning 1:Error: No Industry Sectors Maintained No Industry Sectors Transferred
Warning 2:Error: No Bank Master Data Maintained No Bank Data Transferred
Error 1:Error: Error while Creating Business Partner (BP) Module: BUPA_CREATE_FROM_DATA Vendor: 0000100000
Error 2:Enter country
Please guy help to sort the problem.
Regards,
Apparao A

Hi Atul and Marcin,
Thanks for you reply.
Country field is maintained for that vendor. I am trying with One vendor only . I have checked the country field in R/3 before posting this message.
One more question. I have created some vendor in SRM. Now i want to replicate these vendor in backend. Is this is possible ?.
Our business senorio is like this. For e-procurement of materials they will invite bids from different bidders(Register in SRM only). Once they finalized the L1 bidder they will issue PO to that bidder. That PO has to Copy in to backend.
To copy PO to backend, i think bidder data should be copied in to backend before. How to acheive this ?
Regards,
Apparao.A

IDOC: Error in ALE Service

Hi All,
I have created a new outbound idoc type ZSLSRPT and assigned it to a partner profile with type LI in we20. I tried running my customized program for idoc outbound and the status shows Error in ALE Service, Entry in outbound table not found.
Am I missing something with the partner definition? Do I need to configure the vendor output type in NACE? Please help.
Thanks,
Kenny

Hi Kenny,
Have you setup the distribution model (BD64) for the corresponding message type?
Also check this link for your reference.
http://help.sap.com/saphelp_nw04/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm
Regards,
Ferry Lianto

IDocStatus:Error in ALE service Cross-system company code does not exist

HI All,
I am sending CREMAS04 IDOC from XI to one R/3 system,and in R/3 a vendor should get created in master table.
My IDOC is getting posted successfully but in R/3 system I am getting error that
IDoc: 0000000000705816 Status: Error in ALE service
T100 Text: Cross-system company code XXX does not exist
I have created partner profiles in receiver system and in partner profiles I have set the process code as CRE1.
Please help me to resolve this problem.

Hi Shweta
Have you checked with the data i.e. company code .
May the company code which you are passing is not there in ur receiver system.
Just check it out.
Regards
-Mitesh

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

Vendor replication to SUS

Hi,
We are setting up the service procurement scenario with supplier enablement. We have EBP on one client (100) and SUS (110) on another client. All the XI configuration is done properly.
When we replicate vendors from EBP (XML/XI) as the communication method, using BBP_SP_SUPP_INI, the XI montior is a green message for the outbound in EBP, green in XI. when it comes to SUS, there is an error for the inbound XML.
Here is the error.
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:StandardMessageFault xmlns:nr1="http://sap.com/xi/SRM/Basis/Global">
- <standard>
<faultText>An error occured within an XI interface: Exception occurredE:R11:123 -Enter at least one number for the business partner Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</faultText>
</standard>
</nr1:StandardMessageFault>
All the Business number ranges are set properly and internal no. ranges have to be taken.
Any idea to resolve this error?
I appreciate the urgent help.
Regards,
DV

Hi Folks:
I am trying to replicate vendors from EBP to SUS using the
t-code BBP_SP_SUPP_INI.
But always internal numbers are created which I DO NOT want.
Say in EBP Portal vendor is 8536 and I need the same vendor number 8536 in SUS .I am attaching the XML payload .
How to create external vendor numbers in SUS.
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:SupplierPortalTradingPartner xmlns:nr1="http://sap.com/xi/EBP">
<Method>Create</Method>
- <TradingPartnerOrganization>
<TradingPartnerRole>Seller</TradingPartnerRole>
- <Identifier>
<PartnerID>0000008536</PartnerID>
</Identifier>
- <TaxIdentifier>
<CategoryCode>US2</CategoryCode>
<TaxNumber>13-7904380</TaxNumber>
</TaxIdentifier>
<SystemID>SAPEBP_MPX_100_X</SystemID>
<Language>EN</Language>
<Currency>USD</Currency>
<Title>0003</Title>
<Name1>GRAYBAR ELECTRIC CO INC</Name1>
- <Address>
<StandardAddress>true</StandardAddress>
<AddressID>0000010270</AddressID>
<Street>650 SOUTH 108ST STREET</Street>
<City>MILWAUKEE</City>
<PostalCode>53214</PostalCode>
<Region>WI</Region>
<Country>US</Country>
</Address>
- <Communication>
<CommunicationType />
- <Telephone>
<StandardTelephone>true</StandardTelephone>
<Number>817-213-1333</Number>
<TelephoneCountry>US</TelephoneCountry>
</Telephone>
- <Fax>
<StandardFax>true</StandardFax>
<Number>817-213-1339</Number>
<FaxCountry>US</FaxCountry>
</Fax>
- <Email>
<StandardEmail>true</StandardEmail>
<EmailAddress>[email protected]</EmailAddress>
</Email>
</Communication>
</TradingPartnerOrganization>
</nr1:SupplierPortalTradingPartner>

Vendor replication and exchange documents from SRM to SUS (using PI)

Hi Gurus,
We are implementing scenario plan driven procurement with suppllier collaboration on SRM 7.0.
Our architecture involve:
A server machine with SRM 7.0 (SRM server and SUS components both in this machine)
A server machine with Netweaver PI 7.0
A server machine with EP 7.0
A server machine with SAP R/3 4.6C
Now we are working on vendor replication process in order to carry out vendors from R/3 to SUS (on portal enviroment) and we made following steps:
- Replication of vendor from R/3 to SRM by mean tx BBPGETVD: OK
- Replication of vendor from SRM to SUS (on portal enviroment) by mean tx BBP_SP_SUPP_INI:
In this step we put the BP (created with tx BBPGETVD) on field "Supplier" but we obtained the Message no. BBP_XP004
"No vendor allowed for vendor portal"
So we want to know, in connection with mentioned architecture, the way to perform this activity in order to replicate the suppliers in SUS.
Is possible perform activities related to exchange documents (by mean Netweaver PI) between SRM and SUS (as necessary for our implementation scenario) if these mentioned components are installed and configured on the same phisical server machine?
What is the best recommendation about installation of SRM and SUS? A unique server machine or separated server machines?
Is there any inconvenience or technical reason having SRM and SUS in the same server machine?
Thanks in advance.
Regards,
Horacio

Hi Nikhil,
Thanks for your soon response.
Our process involve PR and PO manual creation in MM and then PO (with ALE message type) is routed to a supplier in SUS via XI. We could achieve that steps succsesfully.
We don´t have in scope neither use SRM for sourcing nor PO creation (via IDOC) in MM.
In connection with my previous explanation; Would you say that our process is MM-SUS?.
If yes, can I follow the steps mentioned in below link described at point u201CProcess Flow Without Supplier Registrationu201D?. What´s the difference between creating and replicating bussiness partner data?.
http://help.sap.com/saphelp_srm40/helpdata/en/c0/7a0859ee91d54aa48a69fb5d2c4089/content.htm
Thanks in advance.
Regards,
Horacio

Vendor replication from ECC to SUS

Hi Gurus,
We are replicating vendors from ECC to SUS.
The XML message is failing in the SUS side.
The error is
Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application
Please find below SXMB_MONI trace
<FAULT_TEXT>Error in XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Program:
It seems similar issue has been resolved in the below thread but there is no mention of solution.
ABAP Inbound Proxy Error !
Please help in resolving the issue.
With Regards,
Malay

Hi Malay,
Kindly check if you have defined the logical system of SUS system under T-code SALE in your SUS client.
Regards,
Nikhil

In what case, we need to use PI for vendor replication in MM-SUS?

Dear Experts,
In what scenarios, we need to use or configure the PI settings for vendor replication between MM and SUS? The SAP configuration guide for SRM 7.01 mentions about the PI settings for vendor replication from ECC to SUS.
However, we are able to replicate the vendor from ECC to SUS using the program BBPGETVD in SUS client?
In what circumstances, we need to configure the PI settings for vendor replication when we are able to do so in a much simpler way?
Thanks in advance,
Ranjan
Ranjan Sutradhar

Hi Ranjan,
In all circumstances you need to replicate vendors from MM to SUS via PI. BBPGETVD is not the right way to replicate vendors to SUS because the information like vendor class, assignment of this vendor class to an object and the vendor classification cannot be transferred via BBPGETVD.
Hence you will have to use PI. You can try sending a PO from MM to SUS and the PO will fail in SUS with a message like 'Vendor not present in SUS' if you use BBPGETVD.
Regards,
Nikhil

Status record 65 error in ale service

HI Experts,
               I have an issue when I tried to send a cost center idoc from one system to another. The company code for the record is 0093 in the sender system; however when the idoc gets created, in the idoc the value of the company code becomes SAH001. I dont know why this happens.
This is the record to in the corresponing table table- which is to be sent from sender to Receiver. The company code ie company code field value is 0093 .
The RFC/LS connections have been done and checked. I am able to send the cost center group data correctly. While sending the cost center I am encountering the following error:-
For an example
Content of created Idoc in sender
Company code field |   SAH001
The company code info is now SAH001. I wonder why ?
So when we send the idoc to recceiver, we get the same company code and I get an error that company code doesnt exist.
Content of idoc in receiver
Company code field |   SAH001
I want to display 0093.
Please tel me what is error and how to rectify?
Thanks & regards
Mathi

hI,
Testing inbound idoc :
Once you configured everything then goto WE19 Transaction :
Give message type or idoc type and execute .
now here you need to fill the Mandatory data in each segment,once you done then
idoc->edit control record -> here you need to fill sender and receiver details.
now you should get green color ,if you get red color then config issue.
now click on start inbound -> now you will get idoc number.
if you want to debug then click on inbound function module -> enter FM -> select call in debug mode and enter.
now cursor will go debug mode
http://www.photographybykevin.net/sap/idoc_overview.pdf
Testing Outbound idoc :
Once you done all configuration ..
Let me say example like invoice ,you need to send invoice from SAP R/3 to other system.
create invoice at VF01 -> Here customer should configure in Parter profile ,once you create invoice ,it creates the idoc.
debugging Outbound IDOC :
keep the break point in form routine above as i said
Create invoice or invoice list
when you maintain output type in invoice or invoice list -
Now click on Further data ->select peridoc scheduling-> back and save it.
Run RSNAST00 Program
Output application : V3
Object key : Invoice or invoice list number
Output type : RD00 or LR00
Medium = 6(EDI) ,A (ALE)
when you execute the program and it will goto debugging.
See the below status codes :
See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes
Successful Transmission:
03 - Successful outbound transmission
12 - Dispatch OK
IDoc being processed:
01 - IDoc created
30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)
ALE Error Messages:
02 - Error passing data to port
04 - Error within control information on EDI subsystem
05 - Error during translation
25 - Processing despite syntax errors (outbound)
29 - Error in ALE service
32 - Resubmit edited intermediate document (DO NOT USE)
Syntax Error Messages:
26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes
IDoc Processed Successfully:
50 - IDoc added
53 - Successful posting
IDoc ready for processing:
64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Errors in IDoc Processing:
51 - Error - application document not posted
56 - IDoc with errors added (You should never see this error code)
60 - Error during syntax check of IDoc (inbound)
61 - Processing despite syntax error (inbound)
63 - Error passing IDoc to application
65 - Error in ALE service - indicates partner profiles are incorrect
69 - IDoc was edited
Regards,
Nagaraj

Error in ALE Service

hi
using the t.code BD13, i got the Customer Master Record in to the system
WE02 / WE05
IDoc:207013 Status: Error in ALE Service
Could not determine recipents for message type DEBFET
then i did in t.code WE19-- Function module IDOC_INPUT_DEBFET (in background)
Pop-up window
No Object for request IDoc selected for sending
Pop-up window
IDoc 207014 was saved and processed by function IDOC_INPUT_DEBFET
I cheked the status in WE02
IDoc:207014 Status: Application document not Posted
No Object for requested IDoc selected for sending
56 - EDI : Partner profile inbound not available.
please give me the solution, where i have to correct the issue
and i am not getting the function IDOC_INPUT_DEBITOR_MDM
Babu rao

in WE20, can yoy pls check if you have the partner profile maintained. If not pls maintain the same and the issue should be resolved.
Hope this helps.
rgds

MM SUS Vendor Replication Error: Error in ALE Service

Similar Messages

Maybe you are looking for