Issues in ALE

hi experts ,
I have some issues like, basically a PO is raised in nonsap and this po should be made it as PO requsition based on some conditions in SAP but there are some conditions,based on these IDOC should be created-
1)IDoc with one line item containing all listed requirements for a domestic purchase
2)Two IDocs, each with one line item, for the same vendor/article/delivery date creation
and an error should raise based on -
1)One item IDoc with an invalid vendor/article combination
2)Two item IDoc with one line item containing an invalid vendor/article combination
3)Two item IDoc with one line item containing two different payment terms
4)One item IDoc with an invalid vendor number
5)One item IDoc with an invalid article number
how can i achieve..do i need todo some coding stuff or else is there any predefined programs are there..

solved

Similar Messages

Client issue with ALE Configurations

Hi Experts,
I am trying to connect to a different SAP System through ALE. I have defined logical systems. When i am trying to assign destination logical system to destination client, i am getting an error - "Entry already exists" as there is another system aready assigned with this same client number.
My Question is - Is there any way to connect to 2 Diff SAP systems having same client number? Otherwise, if there is a client (Say 400) that is already assigned to an SAP System, Then cannt we connect to another SAP system having the same client number( 400)?
Rgds,
SURYA.

No, SCC4 is only for defining the clients of current system (and the corresponding logical system, which must be unique throughout the landscape), it's not about communication at all (apart the logical system).
Use SM59 to define an RFC destination, you'll define the target host and client .
Use WE21 to create an RFC port, referring to the RFC destination above.
Use WE20 to assign this RFC port to the logical system.
By "distribute model", I don't know if you're talking about the "distribution model", in that case I recommend you to go though this thread where there are general information : Distribution model for Message control ?
Sandra

IDOC Issue using ALE

Hi,
I am trying to create Invoice using T-code FB60/FBV1. When I save the document should see the entries in NAST table right? but I am not able to find those entries. When I have entry in NAST table only then I can send IDOC to the XI system.
When I ran Report-RSEOUT00, with Basic Type- invoic02, Port Of Receipientt-SAPXITRFC, Logical Message-INVOIC. But I am getting error msg that No IDOC is ready to process....
Can anyone please help me out?
Thank-You,
Venky

Hi Srinivas,
NACE -> V3 -> Procedures -> V10000 (Billing Output) -> Control -> Condition Type RD00 (Invoice) and Requirement 62 (BillDoc:ReleasePost) -> Save.
NACE -> V3 -> Output Types -> RD00 -> Processing Routines -> Medium A (Distribution ALE), Program RSNASTED, Form Routines ALE_PROCESSING -> Partner Function -> Medium EDI, Function BP and Name Bill-to party -> Save.
VV32 -> Output Type RD00 -> Key Combination -> i.e Sales Organization/Billing Type -> Enter -> Select your Sales Org. and Billing Type -> Execute -> Enter Condition Records -> i.e Bill Type F2, Partner Function BP, Partner 100001, Medium A (ALE), Dispatch 1 (Send with periodically scheduled job) and Language EN -> Save.
Can you please give me in-detail out to look at the output type. Because I am using T-code FBV1 n FB60 to create Invoices.
Thank-You,
Venky

Issue with ALE configuration for creating the idoc for Purchase orders

Hello,
I am trying to send the purchase order through message type configuration using ALE.
I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
I have done ALE distribution using BD64.
Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
In NAST table, the entry is there but on executing RSNAST00 nothing happens.
Please provide me the pointers to solve the given problem.
Regards,
Mayank

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

How to add BAPI in ALE-distribution model?

HI all,
I have to send The post goods issue through ALE-IDOC, this have to create the Goods Receipt in the receiving side.
I came to know that the message type for this is MBGMCR , when i am trying to add this in the distribution model , it is prompting an error message that this message type belongs to BAPI.
So , to send the required data , i have to add the BAPI.
Please help me clearly on how to add this and what are the steps involved in distributing data through BAPI ?
Thanks,
Vamshi

In we20
process code will be BAPI and setting will be same as in other process codes
in bd64 i have example..
TCode BD64
Add ADRMAS in Distribution Model u2018TestERDToEXDu2019 as follow:
Click on u2018Add BAPIu2019 Buton.
Give Object Name as AddressOrg
Give Method Name as SaveReplica
You will get a entry as follows
Edited by: Madan Gopal Sharma on Jul 1, 2008 9:02 AM
Edited by: Madan Gopal Sharma on Jul 1, 2008 9:04 AM

Migration project: FI/CO/SD/MM/PS/RE (4.6c R/3 - ERP6 with unicode)

Hi,
Before getting to my question I have for you let me explain you some background:
As project manager, I am involved in a pre-study of a project for migrating an existing non-hrm solution (FI/CO/SD/MM/PS/RE/Workflow) from a local 4.6c R/3 landscape towards a global ERP6 (UC) instance. The existing non-hrm solution is integrated with HR mainly for Payroll postings. The 4.6c feeds a BW3.1, the ERP6 feeds a BI7.0.
The project consists of 5 major deliverables:
1) technical migration of applicative/reporting layer (Programs, DDIC, BW reports ...)
2) adaptation interfacing (integration points HR-Non-HRM will be handled through standard ALE
3) process integration (non-hrm will get integrated with existing global processes such as Global Organizational management, Global Personal administration)
4) reporting integration (non-hrm reportings will get integrated with existing global reportings)
5) data migration (all non-hrm data pass from 4.6c to ERP6)
As you can read this project is about a carve-out of existing processes and the migration/integration of them into a global platform. Main driver for this project is the globalization of non-hrm processes.
Now my question is a rather technical one, concerning point 5 "Data migration": the project approach would be to use a standard ALE initial/LSMW load for migrating the FI/CO/MM/SD/PS data from 4.6c to ERP6. Now, after discussion with SAP Basis team, it was issued that such a direct data migration is impossible due to the fact that there is a difference
- in SAP version (4.6c vs ERP6)
- in database character set (NUC in 4.6c vs UC in ERP6)
(I personally doubt that this is an issue since ALE is able to cope with different SAP versions)
So the SAP Basis team propose to do such a project in 3 steps (in stead of one):
1) split non-hrm and bring in to a new 4.6c instance
2) upgrade that new 4.6c with non-hrm to ERP6 (local instance)
3) migrate non-hrm from ERP6 (local instance) to the other ERP6 (global instance)
Can someone share some experience and/or confirm the best data migration approach for such a project?
Thanks
Bert Caryn
Edited by: Bert Caryn on Jan 18, 2008 3:00 PM
Edited by: Bert Caryn on Jan 18, 2008 3:01 PM

This is a really BIG project
> Query
>
> 1)     What is the possibility of merging this two system
> of SAP to one single system of SAP as 4.7 or Ecc6.0?
> 2)     If merging is possible
> a) What are all the points we should take care since
> both are in different platform?
I suggest the following:
Read Note 481938 - System Landscape Optimization Services
and
http://service.sap.com/slo
There is a group @ SAP named "System Landscape Optimization", who does those kind of things:
          o Delete, merge, split or rename company codes, controlling areas etc.
          o Harmonize customizing and master data like chart of accounts or vendors
          o Reorganize System Landscape (merge systems, move business areas)
Since you environment is pretty complex, I suggest opening an OSS call on XX-SER-CS, describe just what you wrote here and you will get contacted.
I would NOT do such a merge on my own without involvement of SAP and the corresponding people who know the underlying data model.
Markus

Inbound Idoc Generation

Hello All,
We have a ALE concept to transfer data between clients. We have made the settings and the process was fine. But on some days Inbound Idoc is not getting generated with respect to the outbound Idoc, and after some times once again system comes to normal state and the idoc generation is fine. How ever we dont have any root cause for the failure of Idoc generation. Could someone let me know where i can chk the info and what all the parammetres needs to be checked.
Note ; There are no issues in ALE ocnfig settings.

Hi ,
See the following code :
Program To Generate IDoc
*& Report ZZ_Program_To_Create_Idoc
report zz_program_to_create_idoc                     .
tables: ekko,ekpo.
selection-screen skip 3.
selection-screen begin of block b1 with frame title titl.
selection-screen skip.
select-options s_ebeln for ekko-ebeln.
selection-screen skip.
selection-screen end of block b1.
data: header_segment_name like edidd-segnam value 'Z1EKKO',
      item_segment_name like edidd-segnam value 'Z1EKPO',
      idoc_name like edidc-idoctp value 'Z19838IDOC1'.
data: header_segment_data like z1ekko,
      item_segment_data like z1ekpo.
data: control_record like edidc.
data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
data: i_communication like edidc occurs 0 with header line,
      i_data like edidd occurs 0 with header line.
data: begin of i_ekko occurs 0,
      ebeln like ekko-ebeln,
      aedat like ekko-aedat,
      bukrs like ekko-bukrs,
      bsart like ekko-bsart,
      lifnr like ekko-lifnr,
      end of i_ekko.
data: begin of i_ekpo occurs 0,
      ebelp like ekpo-ebelp,
      matnr like ekpo-matnr,
      menge like ekpo-menge,
      meins like ekpo-meins,
      netpr like ekpo-netpr,
      end of i_ekpo.
start-of-selection.
select ebeln aedat bukrs bsart lifnr from ekko
          into table i_ekko where ebeln in s_ebeln.
select ebelp
       matnr
       menge
       meins
       netpr
       from ekpo
       into table i_ekpo
       where ebeln in s_ebeln.
control_record-mestyp = messagetyp.
control_record-rcvprt = 'LS'.
control_record-idoctp = idoc_name.
control_record-rcvprn = '0MART800'.
loop at i_ekko.
header_segment_data-ebeln = i_ekko-ebeln.
header_segment_data-aedat = i_ekko-aedat.
header_segment_data-bukrs = i_ekko-bukrs.
header_segment_data-bsart = i_ekko-bsart.
header_segment_data-lifnr = i_ekko-lifnr.
i_data-segnam = header_segment_name.
i_data-sdata = header_segment_data.
append i_data.
select ebelp
       matnr
       menge
       meins
       netpr
       from ekpo
       into table i_ekpo
       where ebeln = i_ekko-ebeln.
loop at i_ekpo.
item_segment_data-ebelp = i_ekpo-ebelp.
item_segment_data-matnr = i_ekpo-matnr.
item_segment_data-menge = i_ekpo-menge.
item_segment_data-meins = i_ekpo-meins.
item_segment_data-netpr = i_ekpo-netpr.
i_data-segnam = item_segment_name.
i_data-sdata = item_segment_data.
append i_data.
endloop.
clear i_ekpo.
refresh i_ekpo.
endloop.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control                  = control_record
OBJ_TYPE                             = ''
CHNUM                                = ''
tables
    communication_idoc_control           = i_communication
    master_idoc_data                     = i_data
exceptions
   error_in_idoc_control                = 1
   error_writing_idoc_status            = 2
   error_in_idoc_data                   = 3
   sending_logical_system_unknown       = 4
   others                               = 5
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
         with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
else.
loop at i_communication.
    write: 'IDOC GENERATED', i_communication-docnum.
endloop.
commit work.
endif.
initialization.
titl = 'ENTER THE PURCHASE ORDER NUMBER'.
Reward points if helpful.
Regards.
Srikanta Gope.

Outbound INVOIC idoc to partner type LS

Hello,
We are trying to issue outbound invoices( Message type INVOIC / basic type INVOIC02) to a 3rd party who will be doing the billing on our behalf. We are trying to issue an ALE output type to a LS (logical system) partner type and we are receiving a message B1131, that says that partner type LS cannot be used here, only KU and LI partner types allowed.
We can create the idocs if we setup our partner as a KU customer. However, given that we are sending these to a 3rd party system, it seems that we should be using LS. Does anybody know if there is some configuration where we can choose to be able to send an idoc of message type INVOIC to a partner type LS - logical system?
Thanks in advance.
Mark Monroe

Hi Mark,
For your requirement you, create partner profile for LS with following steps :
Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
Message Type      : INVOIC
Under Outbound Option u2013 Tab
Receiver Port      : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
Pack Size           : 1
Transfer IDoc Immediately (Select)
Basic Type           : INVOIC02
Cancel Processing After Syntax Error (Select)
Under Message Control - Tab
Application           : V3
Message Type      : RD00
Process Code           : SD09
Hope, your problem will get resolve.
Regards..
Imran

Reg messagtype MATQM

hi abapers,
i have an issue , in ale out bound configurations all setting i did..
maintaing outbound partner profiles giving message type matmas and basic type MATMAS05.
maintaing distribution model with sender and receiver and message type matmas,generating partner profiles,distributing model view.
but probelm what i face is when i go to BD10 and send a material , it the idoc is generated with message type MATQM.
but when i see status it showing green with message type matmas and basic type matmas05..
in receiving system it is not posting it giving ststus 56..

Hi,
While sending material usind BD10, if you are checking the checkbox "send material in Full", then only it will generate MATQM idoc. So make sure it is unchecked befor trigeering idoc.
Thanks,
Asit Purbey.

Data extraction is not taking place from BW to R/3

Hi Experts,
We recently upgraded our BW 3.1 system to NW2004s/BI (BW 700). Now we are
not able to extract data from R/3 4.6C source system.
We checked and data extraction job is not getting triggered in R/3. It is
not receving Idoc.All the settings are correct in WE20 and WE21. I will appreciate your quick help.I am not sure if the question has been posted in correct forum or not as I am a newbee in SDN forum. If its not there in the correct forum,please let me know.
Many Thanks

hi Arun,
Thanks for your quick reply. and also I have made the mistakein the post subject . It is from R/3 to BW. But I checked all the ALE setings and RFC connection. Everyhthing is alright.but dont know why its not getting extracted. I think some problem might be lying with the function module. If you have any other idea apart from RFC/Delta please let me know. I am damn sure this isnot an issue with ALE config.
Just to make this issue little bit clear, the exact issue now I am facing is related to Idocs. Idocs are going to the state 56 in R/3 and all the control records are blank in R/3. This has created a nightmare. All the efforts are going in vain...
Many Thanks,
Chinmaya
Message was edited by:
Chinmaya Dash

User creation from existing SU01 user

Hi All
While creating a user from an existing Su01 user, i am getting the follwoing error:
'Action is not possible, HR/ALE distribution active'
Could someone help me with this ?
Regards

Hi,
We are facing same issue " HR/ALE distribution is active. Distribute the user information newly".
But in our case we have HR integration is there since all HR master coming from HR system. Now this is strange because we are facing this issue only for one user. Rests of the users are ok.
I think in our case we can not change the status of PBPHR as off.
Is there any other opinion on this?
Thanks,
SRM

Need RICEF Security specfifications for Interfaces and Conversions

Hi All,
I need RICEF security specfications for Interfaces and Conversions. Can anyone provide any input on this.
Regards
Plaban

Hi Plaban,
Thanks for the detailed explanation. As mentioned, as per my knowledge there is no specific guideline/template that you may adapt while designing the security design for the Interfaces and Conversions.
However, the most common issues that occurs with IDOCs is with file interfaces are related to file permissions, file ownership and character conversions moving between platforms.
Ensure that the appropriate authorization (read/write and with filters) authorization is provided. Identify the various levels of authorizations required and implement the same.
Further, most issues with ALE interfaces are with RFC user ID permissions. Ensure that the appropriate and only the Required authorization is provided to these IDs. This way you can tighten the authorization to the specific level. You may need to completely test the functionality before implementing this.
It is always important to understand these limitations during the functional design. If any specific additional functionality is required, you may need to have a custom based solution.
Hope this answers your question!!
Warm Regards,
Raghu

Installed R/3 language pack

the default R/3 Server Language pack is german and english
after i installed Chinese language pack, the system start as normal ,
but when i check my NWDS J2EE Engine the Node is not appear there neither to access the application that i have deploy to the system previously.
http://servername:50100/index.html not work also

This is probably because Greek ISO code has been changed. We have this issue on ALE between 4.6c and 4.7. We need to convert the old code of EL to new GR. Try using GR or EL for your ITS.

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.

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

Issues in ALE

Similar Messages

Maybe you are looking for