ALE issue

HI,
I am kind of new to ALE. The issue I am facing is, I have setup ALE Distribution model to replicate Inbound delivery from one client to different client and that's not an issue. When I create TO against that inbound delivery it should trigger IDOC back to source client and it was perfectly working fine. All of a sudden it stopped working.
I debugged lot and couldn't figure out much. Please help me and again I am using ALE BAPI technic.
Thanks
Sarath

Hi,
please check below link for TO Idocs may be useful for you to track
http://help.sap.com/saphelp_sm32/helpdata/en/52/16ace6543311d1891c0000e8322f96/content.htm
Regards
Vinit

Similar Messages

ALE ISSUE HRMD_A

HI Experts,
We have a issue where we are sending the data from one HR system to another HR system using ALE message type HRMD_A07. So in sending system if we create a record which has a validity date of 01/01/2011 to 12/31/9999. The change pointers take that record and update it in the receiving system which is fine but instead of delimiting the record on the receiving end it inserts the record. So in the receiving end we have two records with 12/31/9999 end dates which we dont want.
Is there a BAPI or Setting in the t77s0 table which will prevent this from happening and instead of directly updating the table it delimits the old record and create a new one. Any help would be much appreciated. Thanks

Hello Hasan,
Last year we had faced the same problem As per our investigation std. HRMD i/b idoc processing doesn't provide data delimition.(We were using an ECC6.0 system)
If you check the i/b processing FM IDOC_INPUT_HRMD, there is a BAdI HRALE00INBOUND_IDOC. You can use the method PROCESS_IDOC( ) for user-defined IDoc processing.
Inside the method you can call an FM (for e.g., HR_INFOTYPE_OPERATION ) which can delimit the infotype.
BR,
Suhas
PS: Alternatively you can use the function-exit 'EXIT_SAPLRHA0_003'.

ALE issue:No partner profiles (message control) maintained

Hi,gurus:
My ALE scenario is tranferring PO from client 800 to 900 client.
Now the logical system,partner profile，port，rfc，distribution model are created both the sender and receiver side.
In ME21N->MESSAGE, the output type is NEU,and medium is A,partner function is LS,partner is ECCCLNT900.
When I saved the PO,the status is red,and no idoc was generated.
I viewed the processing log,the information is: No partner profiles (message control) maintained.
But my distribution model is sender:ECCCLNT800;receiver:ECCCLNT900;MESSAGE：ORDERS;
The partner profile is ECCCLNT900(LS),and the outbound parameters are ORDERS,SYNCH. For ORDERS,the message control is EF,NEU,ME10.
Have you ever met this issue?
Thanks in advance.

Hi Li,
Please refer this threads...
Re: Message is not proposing automatically
Re: IDoc was saved but cannot or should not be sent
Hope you have to post this thread in ABAP General category..
Regards,
kumar.

BOM ALE issue

Hello all,
I am trying to ALE BOM changes from client 300 to 100. SO I changed the qauntity of a component and saved without using ECM . I did the ALE, but in target system it did not update the item quantity. Instead it added a new line item with a valid from date.
I want to update the quantity and not add a new line item. This functionality works right with ECM, but I want to see if it can do it without ECM. Thanks
Atul

Atul Katti wrote:
lets say the original component with qty 2 was valid from 5 June and today I did the ALE, the original line is left as is and a new line with the SAME item number is created with a valid from date of today with the changed qty.
this sounds like it works in create mode instead of change mode.
And this makes me think that it may have something to to with the situation explained in the ALEKZ note.
Had you checked whether your BOM in the target system has the ALEKZ active?
the note explains that you can only update records with this ALEKZ set.
How do you transfer the BOM? with transaction manually or automatically using change pointers?

More ale issues

Gurus,
In my scenario...
Business Serv(third party) to Business system ecc............idoc`s are failing with unable to convert sender to ale logical system..i have seen michal`s blog..etc
We are doing control rec mapping..and values are valid..any thoughts......
NB

hi,
if you've seen my blog then what's the problem?
did you maintain IDOC specifc attributes for this business service?
are you changing it's value in the mapping with "take sender from the payload" option ?
Regards,
michal

SIS - ALE issue

Hi experts, pls help. Thx.
It seems that msg type SISDEL is transferred from R/3 to R/3 successfully (Idoc w/staus "green" light). But I failed to find the relevant business data in the receiving system, i.e. outbound delivery.

I made firmware reinstall. After that I am able to install to phone memory. Before that I wasn't able to do that.
But when memory card inserted I am not able to install anything.
As I said before memory card is accessible, maps and photos are visible.
Looks like something wrong with memory card.
I have one micro SD card but it is at home. I will try to put it and will check does the problem exists.
The problem is taht I have no micro SD HC card reader and can't connect it to computer directly.
I would make copy of all data and reformatting in computer, than copy all data back.
Nokia E-72

Mapping and Interfacing files into R/3 as IDOCs using XI

We are trying to send an IDOC into R/3 thru XI. We generated one from R/3 into XI - it worked fine, however the reverse direction is not working well.
We are using XI 2.0 with R/3 4.6C.
We ran into two problems:
when we tried DEBMAS/DEBMAS06, we were getting a message in SXMB_MONI / IDX5 that the entry DEBMAS06 is not found (in table IDOCSYN) on XI. On our XI server we found that there were only 65 IDOC message types defined (I dont know why .. but none of the popular IDOC messages like DEBMAS, CREMAS, MATMAS, ORDERS, etc are in XI). We thought may be that is the reason. But we do not know thru config, how to add IDOC messages into XI - this is not the same as importing IDOC type .. we have already done that. Just importing an IDOC structure does not put an entry in tables like IDOCSYN, and others...
Then we tried using an IDOC message that was in XI IDOC tables - FLIGHT_SAVEREPLICA. This ones gets past the error we got with DEBMAS. However, we still do not see the IDOC in R/3. When we check IDX5 or SXMB_MONI, it says that the message is processed successfully and does not show any errors. We are not understanding why it does not reach R/3.
Has anyone mapped files into IDOCs and sent to R/3 thru XI. If you did, CAN YOU PLEASE HELP US OUT....
It looks like we are missing small config step .. somewhere ..
We created partner profiles, set up ports and RFC destinations. IN SLD we did define the logical systems. On the surface, from the config everything seems fine.
OSS note 669669 is already in.
Any help will be greatly appreciated ...

> We are trying to send an IDOC into R/3 thru XI. We
> generated one from R/3 into XI - it worked fine,
> however the reverse direction is not working well.
> We are using XI 2.0 with R/3 4.6C.
>
> We ran into two problems:
> when we tried DEBMAS/DEBMAS06, we were getting a
> message in SXMB_MONI / IDX5 that the entry DEBMAS06
> is not found (in table IDOCSYN) on XI. On our XI
> server we found that there were only 65 IDOC message
> types defined (I dont know why .. but none of the
> popular IDOC messages like DEBMAS, CREMAS, MATMAS,
> ORDERS, etc are in XI). We thought may be that is the
> reason. But we do not know thru config, how to add
> IDOC messages into XI - this is not the same as
> importing IDOC type .. we have already done that.
> Just importing an IDOC structure does not put an
> entry in tables like IDOCSYN, and others...
You need to change the outbound version to a lower version. ie send debmas03 not 06.
This is an ALE to ALE issue. Not XI related.
> Then we tried using an IDOC message that was in XI
> IDOC tables - FLIGHT_SAVEREPLICA. This ones gets past
> the error we got with DEBMAS. However, we still do
> not see the IDOC in R/3. When we check IDX5 or
> SXMB_MONI, it says that the message is processed
> successfully and does not show any errors. We are not
> understanding why it does not reach R/3.
>
Trace time....
> Has anyone mapped files into IDOCs and sent to R/3
> thru XI. If you did, CAN YOU PLEASE HELP US OUT....
>
> It looks like we are missing small config step ..
> somewhere ..
>
> We created partner profiles, set up ports and RFC
> destinations. IN SLD we did define the logical
> systems. On the surface, from the config everything
> seems fine.
> OSS note 669669 is already in.
>
> Any help will be greatly appreciated ...
Use SXI_SUPPORT and follow it in debug...
Cant tell what else is wrong.

Question on upgrade of SAP_BASIS & ABA component on Application component

We have been recommended to upgrade SP21 for component SAP_BASIS (13) and SAP_ABA (12) to resolve HR ALE issues where correction is available in SP21. We are in SRM6.0 SP03. My question is do we have to go for SRM6.0 support pack upgrade too which is SP06 latest or we can just upgrade SAP_BASIS and SAP_ABA component.
Thanks, Sachin

Found the solution:
Import the XI Contents via Tools->Import design objects.then run the SLD sync job via Visual admin.
Download Latest XI contents via CIM and upload that in SLD.
This will keep the XI Contents in SLD and IR at the same Support pack Level.
Thanks
Saif

Issue in Data transfers using ALE for E-Recruiting standalone system

Dear Experts,
We have an issue in data transfers using ALE. We are having standalone system where E-Recruiting is maintaind seperately and the version is EHP5.
When we configured iDoc in Sandbox and its working fine. But when it comes to Dev and Quality servers this is not working fine.
we have created iDocs using the following filters.
For Object P: Infotypes 0000, 0001, 0002, 0003, 0006, 0024, 0105.
For Objects O,S: 1032, Subtype: 0010
For Object: 1001, Subtype: A003, A008, A012, B007
For Object O: 1001, Subtype: A002, B002, B003, B012, Tyoe of related object: O,S
For Objects: C, O, S, Subtype: 1000, 1002, 1028
For Object:C, Subtype: 1001, Subtype: A007
When we do the data transfers in Sandbox using PFAL it is transferring the data properly.
But when we do the same iin Dev and Quality servers we are not able to do it and gettign 52, 51 errors.
Here we are facing a strange issue. For some Users when we transfer data it is transferring data but with 52 error messgae.
For some users I am getting 51 error where i could not transfer any data.
For some users, when we tranfer O, S, and P related data is moving but getting mostly 52 error and all the relationships are not moving here for O,S and properly. But P related CP, BP and NA are getting created successfully.
It is happening only in Dev and Quality server and that too some users are able to get transferred but not all.
Where will be the issue? How can we resolve this?
Any help will be appreciable.
Thank you in advance.

Hi Sekhar,
Have a look over these threads.
Errors in ALE data transfer to E-Recruiting.
http://scn.sap.com/thread/1535402
BR,
RAM.

EDI/ALE output Post Goods Issue from ME2O

Dear experts,
I have to create an outbound IDoc (I assume MBGMCR03) of a Goods issue done with ME2O (mvt type 541).
So far I have read through:
http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=88113280
http://scn.sap.com/thread/3146742
http://scn.sap.com/thread/2056081
but they all talk about printing the message - I need to create an IDoc.
In NACE:
- Application "ME"
- but which condition record can I choose?
- output types are all set up with print parameters - no EDI/ALE as far as I can see. Do I have to create new ones?
Can you please help on how to set this up in NACE?
Next step would be MN21 for the output condition record I assume,
WE20 to define output for logical system.
Thank you for your help.
Best regards,
Peter

Dear experts,
I am a little further now.
I used output condition WA01 which is already set up in NACE and in MN23 I set up:
In SP01 I can see the created Spool entries after creating the Good issue with ME2O. So the print out would work. But I need an EDI output....
I created a new output condition ZWA1 in NACE and set "Processing routines" to EDI.
I set "Partner functions" to EDI and LS - logical system.
In MN23 I have:
I set Event Type to "WA" because when I look at a material document in MB03 it also shows WA:
In WE20 I have my LS - logicals system and set up the output for MBGMCR03:
What confuses me is: I have to send the EDI output to a LS - logical system. But in MN23 I can't set the LS - it gives error: "You cannot enter a partner function for output ZWA1"
No IDoc is created so far - please help. Thank you.
Best regarsd,
Peter

Issue in transporting changed material type using ALE-IDOC

Hi All,
I am sending the material master data from one system to another using ALE-IDOC.The issue is that teh material type is not getting sent from one system to another after changing the material type.I mean the changes in material type are not getting updated.I will be indeed thankful if anyone can guide me resolve this issue.
Thanks.

Hi,
Not all the fields that are changed in material master are sent in the Idoc. Material type is one such field.
Create change pointer on some other field ex. net value or material desc. and transfer the material type changes under it.
KR Jaideep,

E-Recruitment - Loggin in Issues in E-Rec instance after ALE transfer

Hi,
We are running E-Rec in seperate instance and we have plans to implement the ALE Data transfer as a scheduled periodical Background job from HR system to E-Rec system.
We have also cutomized the ALE to set a default password when the data is transferred in to the E-Rec system.(We had done this to avoid the time & effort required from SAP Basis admin to reset the password of each E-Rec user whenever the ALE data transfer is performed)
After performing the ALE data transfer, when logging in the portal and accessing the E-Rec start page link the system prompts the user for a new password.
We are looking at an option where the ALE program can be modified to set a confirmed password instead of initial password.
Any suggestions on fixing this issue please. I request a solution for this on a high priority.
Thanks
G Raj

Sorry to be this direct,
but the first question which comes to my mind: Are you kidding?
You describe that you set the password of each user to the same default value just the bais admin is too lazy? And if this would not be enough you want that everyone can keep this password for eternity so everyone has always the possibility to log into every account including the recruiter / admin ones as they would be part of the ALE as all employees are part of the ALE and noone ever has to change the password (usually if you do not force someone to change his password he will never do)? Seems your security team died from an heart attac when u presented this idea so they do not have to be asked any longer.
Back to business:
The ALE creates a password on user creation. If the candidate is updated later the password won't be touched. Also if the user already exists when ALE is transfering an employee for the first time, the user will keep his password as before assigne authorization.
E-Recruiting has a standard function that the user can get a new password and unlock the user so no admin has to move a finger as long as the candidate has an email address where the system can send the new password.
If you do not want to bother the user with varius logins and passwords whild keeping a secure solution you shoul invest in a SSO solution.
Best Regards
Roman

ALE and IDocs Relevant Issue

Dear Gurus,
I created a Master Data (MD)u2018testmrtu2019 via MM01 in our DEV environment.
Now I want to transfer it into QAS environment via ALE mode. (The ALE configuration work was done.)
The MD was successfully sent from DEV via BD10. (The light was green via WE05 in DEV.)
But Iu2019ve failed when I receiving the MD in QAS and can see error logs via BD73.
Error Log:
Message Type: MATMAS
IDoc Status: 51
Status Grouping: Red Lights.
Status text: Application document not posted.
Double Click 'Application document not posted.' and expand the 'Status Records' of 51, I can see:
'Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT'.
Have you come across this problem? How to solve the problem?
Thank you very much!
Jason

Hi ,
For the Error: Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT'
Error Log:
Idocs would be failing in 51 status in Error state.
for
Message Type: MATMAS
IDoc Status: 51
Status Grouping: Red Lights.
Status text: Application document not posted.
Diagnosis
The function module AFS_RETAIL_ARTMAS_IDOC_INPUT'
and the application object type which were determined are not valid for this IDoc.
Procedure
1. Please check that the process code in the inbound partner profile is correct.
2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code
and see whether the specified function module and application object type are correct.
3. If this is also the case, then the function module and the application object type are not permitted
for the logical message type, message variant, message function and basis type that are contained
in the IDoc control record.
You should check whether the correct values have been assigned to these fields in the control record.
If they do have the correct values, then the assignment to the function module and the
application object type needs to be maintained.
Please check and revert in case u still face the issue .
Regards,
Shravan A

ALE Error Handling Issues

Hi Experts:
For instance,
A company distribute PO to B company SO by ALE Order (ORDERS).When sales order creating,
IDOC will diaplay error message if some missing in material master ,but it shows 1 issue once only.
Suppose that there are 4 missing in material master causes sales order can not be created successfully,
is it possible IDOC shows all of error messages at the same time that make easy to trouble shooting?

Hi Jeff,
Your concern is right..we must get all the errors at once..
But this is not the right approach..SAP ALe programs written in procedural way..i.e. step by step..
its obivious that if some error in step 1 is coming then step 2 is not possible...so system also stop processing when an error occur..
In many Process codes this has done but they are very few...
so we have to go one by one error..
cheers

Help: one request using ALE&IDOC to Posting Goods Issue about MaterialScrap

Hi Exports,
i got a situation. My client is using ALE&IDOC to deal with the Material Scrapping. The business scenario is:
1. One third system (Non-SAP) Send IDOC to SAP Production Server through the Intermedia SEEBEYOND.
    Message Type: MBGMCR
    IDOC Type: MBGMCR02
    BUSINESS OBJECT: BUS2017
2. SAP Production Server use "Message Type: MBGMCR" to find out the BAPI in Distribution Model and trigger the BAPI.
the Distribution Model:
Model View
SEEBEYONG
PRODUCTION
GoodsMovement.CreateFromData
Reciever determination: no filter
Now my client's request is:
When the Movement Type is 551 in the IDOC Segment "E1BP2017_GM_ITEM_CREATE", This IDOC will be ignore and not trigger the BAPI to post goods issue.
i try to add the destination filter in the Distribution Model. but when i add the filter group, there are only two filter parameter ("Plant" and "Storage Location") and don't allow to add others.
i have no idea now. can anyone give me a favor. thank you very much in advance.
Edited by: Dave Wang on Feb 29, 2008 7:09 AM

We got hold of the Idoc type 'DELVRY03 PGI SHPCON' we are able to post the Idoc but we are able to do the packing only or we are able to change the deliveries but the PGI is not happening..
please help us on this.. is there some condig that updates the delivery with the PGi or is there something else do be done in the Idoc....
will provide additional details if required.
Thanks
Arun

ALE issue

Similar Messages

Maybe you are looking for