Error in Outbound scenario : AE_DETAILS_GET_ERROR

Hello Experts,
Need your help urgently
right now i am doing outbound scenario, in that R/3 -> XI -> Oracle.
Here when i trigger 1 outbound IDOC then it is working fine... but when i try to send 100s of idocs at a time then half of them i getting through and half of them are going into error saying
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Error while reading from the secure store: ERROR_U: No service user password found for Adapter Engine</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When i try to restart them into the SXMB_MONI at that time they are getting through.
I am not able to trace that y it is happening like this....
Some of them are going into the "System Error - Manual Restart Possible" and some of them are going in to the "System Error - Restart Not Possible".
Can anybody please help me out in this problem? I am not able to understand that y it is happening.
Regards,
Hetal

Hi Hetal,
Check ur adapterframework service username,password in the exchange profile are given correctly.
Also check in the Business system of the XI server, please verify the URL in the pipeline.It should be:
http://<servername>:<HTTP Port>/sap/xi/engine?type=entry.
Regards,
Prasanthi.

Similar Messages

Cancel or Reprocess BPM message with error on outbound state

I have a BPM scenario, IDOC comes from R3 and triggers a BPM. The BPM has a fork step which sends the message across 4 branches. Each branch has its own steps. Now, the problem is the IDOC has come and has trigerred the BPM but has errored on outbound side. The first step in each branch is a mapping step and the BPM has failed at this due to Jco communication failure. This has been fixed now. Now I need to reprocess this message, but can not restart as it shows succes message in inbound side.
I have to re process this message, but how?
Regards,
Jaishankar

Jai,
I dont know whether it is the correct appraoch.
Have a look at the transaction SWWERRE_DEBUG
Regards,
Sudharshan N A

Message has Error Status Outbound Side

Hi All,
I have one question.... we procssed one file from ftp it should creates Idocs in R/3 side we developed this scenario using BPM....it processed successfully inbound side but in Outbound side it is showing Red Flag (Error Meaase : Message has Error Status Outbound Side) and its not creating IDOCs in R/3 Side but in Process engine all steps completed Sucessfully and created Idocs in XI....i tried so many ways...like in Queues and Refreshed Cache and checked RFC connection in Both ways and checked passwords in communication channels.... i could't find any this....if any body help me on this....it would be appritiated.
This was i am testing on Test system i got this type of problem but in Development box it is working successfully we are using the same fuctionality and same code also i don't know why its happening.
Thanks,
Sudheer.

Hi,
Where are you find the Error and
> Process engine all steps completed Sucessfully and created Idocs in XI....
Can you explain in detail
Regards
Sangeetha

Message has error on outbound side in sxmb_moni

Dear All,
I have a query related to sxmb_moni messages.
Scenario : FILE - XI - IDOC
In sxmb_moni, message is successfully processed by XI but it is showing error " message has error on outbound side".
My questions are:
1)Is it possible to restart the message . When I tried to restart the sucessful message with error on outbound side it showed me message " You cannot restart xml message".
2)I tried to analyze error for outbound side using SM58, it showed me message "No connection to database,session terminated" .
Can anyone please advice what could be the reason for this .
Thanks & Regards
Prabhat

Hi Prabhat,
the message was send to the IDoc adapter. The error occures there.
Control, if the send XML can be translated to IDocs (use a message mapping).
Control, if the SM59 destination to R/3 is working.
Conrol, if the communication channel is customized in the right way. Control, if the port is customized (transaction IDX1).
Also the metadata for that IDoc should be in IDX2, that should happen automaticly, if not, assumedly the destination is not working.
Regards,
Udo

Testing Outbound Scenario with File Adapter

Testing an Outbound Scenario, This uses File Adapter. I checked Payloads in the Transaction SXMB_MONI in R/3 as well as XI. There was no message for error. So I suppose to get the data downloaded to a directory. The output file is a text file. The file is not getting downloaded. Can any one please help me out to solve this issue? Please let me know if you need any more information.
Transport protocol: FTP.
Message Protocol: File Content Conversion
Adapter Engine: IS
Thanks,
Rajan.SA

Chcek whether your Receiver Adapter is activated properly.
http://<host>:5<sysnumber>00/mdt/amtServlet XI > SP09
http://<host>:5<sysnumber>00/AdapterFramework <= SP09
If everything is correct, check the message in the Adapter Engine
http://<host>:5<sysnumber>00/MessagingSystem for the receiving message. You will find more information here why the message is failed to deliver to the endpoint.
regards
SKM

SAP TAO | getting an error "replay Error" for the scenario

Hi,
I am getting the "replay error" for a scenario.
When tested the individual components, they were passing separately in HP ALM, but when consolidate all of those test cases in one test scenario then this error "replay error" is shown.
Could anyone help in resolving this issue.
regards,
Sunil Kumar

Dear sunil kumar
You have posted the query in Career Center..
Is your question related about Career ???
Please read the document before posting any query.
Find Topic Spaces on SCN (Forums)

IDoc error :'Message has error at outbound side'.

Hi Experts,
am working on JMS-->IDoc, where TIBCO sends MBGMCR01 IDoc to ECC through XI .
in SXMB_MONI : shows red flag in outbound:with the message as 'Message has error at outbound side'.
please, suggest to solve the issue.
thank you,
MK

Hi
Have a look this
Message has error on outbound side in sxmb_moni
BPM - Message has error on the outbound side
Reprocess a message with error at outbound side

Why IDoc Sender Channel Used in Outbound Scenario's

Hi Team,
In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
Can you give me clear idea on it / suggect any blogs.
Thanks.
Drumi

HI,
In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
we dont necessary to create Sender Communication channel for IDOC and Proxy and http because xi and sender systems(out bound) resides on abap stack and also dont need for any idoc.
The reason is that R/3 can directly send Idocs to XI via ALE layer using RFC destination specified in SM59.
This IDoc after reaching XI is converted in IDoc-XML. This is done when we specify IDoc metadata IDX2 in XI. It is then used in IR for mapping.
Now for the receiver side, when IDoc-XML is created after mapping program run is sent to R/3. Before that, it has to
be converted into IDoc. This conversion is IDoc-XML to IDoc is done by IDoc Receiver adapter.
one case we need to create sender IDoc Communication channel for IDOC packaging concept thats all.
thanks,
Edited by: bhavanisankar.solasu on Dec 16, 2011 7:12 AM

AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

Urgent :Getting error "No ALE scenario active in Profit Center Accounting"

Hi Experts
I am working on a LSWM project ,which uses BAPI BAPI_PROFITCENTER_CREATE for upload of data,but I am facing a strange problem during the IDOC posting the error "No ALE scenario active in Profit Center Accounting" is shown and the status of IDOC goes to 51.
I have done all the ALE setting required for LSMW like File port ,partner type and partner number.
Please help me to solve this error.
Thanks
-Mitesh
Message was edited by:
 Mitesh Parekh

Hi,
Refer This SDN Blog, which gives you steps in detail....
LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
 Most of the functions are within R/3, hence platform independence.
 Quality and data consistency due to standard import techniques.
 Data mapping and conversion rules are reusable across projects.
 A variety of technical possibilities of data conversion.
 Generation of the conversion program on the basis of defined rules
 Interface for data in spreadsheet format.
 Creation of data migration objects on the basis of recorded transactions.
 Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
 o If no standard programs available
 o To reduce number of target fields.
 o Only for fixed screen sequence.
 BAPI
 IDOC
 o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
 Choose settings -> IDOC inbound processing in LSMW
 Set up File port for file transfer, create port using WE21.
 Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
 Setup partner type (SAP recommended US) using WE44.
 Maintain partner number using WE20.
 Activate IDOC inbound processing.
 Verify workflow customizing.
Steps in creating LSMW Project:
 Maintain attributes choose the import method.
 Maintain source structure/s with or without hierarchical relations. (Header, Detail)
 Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
 Fields can be maintained individually or in table form or copy from other sources using upload from a text file
 Maintain relationship between source and target structures.
 Maintain Field mapping and conversion rules
 For each Target field the following information is displayed:
 o Field description
 o Assigned source fields (if any)
 o Rule type (fixed value, translation etc.)
 o Coding.
 o Some fields are preset by the system & are marked with Default setting.
 Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
 Specify Files
 o Legacy data location on PC / application server
 o File for read data ( extension .lsm.read)
 o File for converted data (extension .lsm.conv)
 Assign Files to defined source structures
 Read data Can process all the data or part of data by specifying from / to transaction numbers.
 Display read data To verify the input data being read
 Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
 Display converted data To verify the converted data
Import Data Based on the object type selected
 Standard Batch input or Recording
 o Generate Batch input session
 o Run Batch input session
 Standard Direct input session
 o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
 IDOC creation
 o Information packages from the converted data are stored on R/3 Database.
 o system assigns a number to every IDOC.
 o The file of converted data is deleted.
 IDOC processing
 o IDOCS created are posted to the corresponding application program.
 o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
 R/3 Transport system
 o Extras ->Create change request
 o Change request can be exported/imported using CTS
 Export Project
 o Select / Deselect part / entire project & export to another R/3 system
 Import Project
 o Exported mapping / rules can be imported through PC file
 o Existing Project data gets overwritten
 o Prevent overwriting by using
 Import under different name
 Presetting for Inbound IDOC processing not transportable.
One Last thing, Check in BD64 is the Distribution model is Active for Profit Center.
Cheers...
Santosh.D
Mark All the Usefull Answers.

Error in outbound processing:ALE/IDOC

Dear all,
I am getting an error in outbound processing as follows(I have extended the BD12 IDOC for customer master).
The issue is that there is no hierarchie of segments in IDOC transaction we05.(Thogh the hierarchie can be observed in WE30)
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1KNA1M_ADRC does not occur at the current level of the basic type DEBMAS06 (extension ).
This error can have several reasons:
u2022     The segment Z1KNA1M_ADRC is assigned to a group whose header segment does not occur.
u2022     The segment Z1KNA1M_ADRC does not exist in the syntax description of the basic type DEBMAS06 (extension ).
u2022     The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type DEBMAS06 (extension ).
I will be thankful if anybody can help resolve the issue.
thanks.
Edited by: sanjivrd on Aug 4, 2009 2:17 PM

hi,
after adding those segments you need to release it.
check it menu you can see the release option, you need to release it.
then only it will work
[Refer following link|EDI: Syntax error in IDoc (segment cannot be identified)]
In the menu edit-> set release
click on it and release
Even check If the Hierrarchy of the segment is correct. This also will result in Syntax Errors.
thanks & Regards,
ShreeMohan

Error in Outbound Queue while Releasing order from CRM to ECC

Hi,
When I release my sales order from CRM to ECC, I got an error in Outbound Queue saying "Screen output without Connection to User".
This is occuring in FM : BAPI_SALESDOCU_PROXY_UPLOAD
Can you please tell me why this error is coming?
Thanks,
Sandeep

Hello Sandeep,
During the RFC call from CRM to ECC, this is a background processing, the screen call is not allowed.
If a call screen is executed, there is the mentioned error.
Please check in your ECC system, whether you have any user exits that have the coding 'call screen'.
Best regards,
Maggie

Interchange Acknowledgment TA1 In Different Outbound Scenarios!

Outbound Scenario:
The scenario I have here is Remote Trading Partner(TP1) doesn't need TA1's either at successful or at failure scenarios. And TP2 need TA1's both in success and failure scenarios. How to achieve the scenario with single document definition(ex: 834) created under single version(5010X220A1)?
I have a Host Trading Partner and Multiple Remote Trading Partners configured. I have one Document Definition created for both the trading partners. While defining the version we have to mention the Interchange Acknowledgment Requested under Interchange tab as either 0 or 1 based on the requirement and TA1 as Always or OnError. As we mention TA1 requirement while configuring document definition itself how to achieve when the trading partners have different requirement.
If each Trading Partner has different Vendors then there is no issue as I will create different version and will update the Interchange tab accordingly as per the requirement. So the issue is if all the Trading Partners require same version, how to achieve ???
Hope I am making sense, please correct me if wrong...
Thanks

It is supported out of the box. Please follow below steps -
1. Select the remote TP profile and navigate to the "Documents" tab
2. Select your doc def and check the box against "Override Version Param"
3. Now in TA1 drop-down select the desired value
4. Delete the corresponding agreement and recreate it again
5. Deploy it and run a test again
By this way, you may have different value for TA1 flag for different TP's in spite of using same doc def.
Regards,
Anuj

AIF Value mapping for outbound scenario

Hello All,
Is there any possibility of using same value mapping which is defined for Inbound scenario can be reused for outbound scenario as well ?
Since, AIF value mapping can be defined based on Sending system but there is no option of creating value mapping pair between sending system and receiving system (similar to SAP PI value mapping) , is it only defined to use for Inbound scenarios ?
Thanks & Regards,
Dijesh Tanna

Michael
-->>>>you cannot have the same target value for two source values ?
What does this mean? Can't we have If name = A1, then value in the target should be Sales consultant
and if name = A2 then value in the target should be sales consultant?
My question was :
If name = A1, then value in the target should be sales consultant
If surname = A1, then value in the target should be purchase consultant
In the same graphical message mapping, can this be achieved using value mapping?
Thanks

CRM Middlware Outbound Scenario

Hi Experts,
I am developing a CRM Middleware outbound scenario to replicate a Z-table from CRM ro R/3.
I have created a BDoc type for that. Could anybody list down what all steps I have to follow in CRM and R/3 side.
Help will be appreciated.
Thanks,
Naren

Narendra
Did you resolve this? I have a similar requirement but am not getting any BDocs created. I have performed the following so far:
1. Created the Z customer table in both systems.
2. Created a new messaging BDoc in CRM and linked it to the R/3 Site Type.
3. Created a new mapping function module in CRM that takes the data from the BDoc and maps it to the BAPIMTCS structure.
4. Created a new Adapter Object that links to my BDoc, contains the new customer table as the source table in CRM and contains the mapping Module.
5. Created a new Replication Object based on my new BDoc.
6. Created a new Publication and assigned it to the Replication Object.
7. Created a new Subscription and assigned to the Publication and Replication Object. Also assigned it to my R/3 site.
On the R/3 side we have created a mapping module to map the data from the BAPI structure into the equivalent R/3 table. We also have an entry in table CRMSUBTAB.
To me it looks as though the Delta update to the Z table is not triggering the CRM Outbound Processing. I am not sure if I need another FM that picks up the delta changes. If so where do we then pass this information to invoke the above process?
Regards
Ian

Error in Outbound scenario : AE_DETAILS_GET_ERROR

Similar Messages

Maybe you are looking for