Idocs with same client

hello sap gurus,
I have one dought.i want to transfer idoc from one server to another whose clients are same .
can u give me the solution ?
Regards,
Vijaya.

hi,
Yes I hope you can do that . Though the clients are same the HOST will be varying.
Regards,
Sharath

Similar Messages

Genrating Idoc in same client

Hi,
Is It possible to generate the idoc in same client only.If possible can any one help me ,how to set up logical file system and partner profile for that..
Thanks
kisu

Hi!
There is the way to set up distribution scenario in the same client.
Let's assume that LOGSYS0100 is the logical system name of the client we want to work with, and that MATMAS(material master) is the message type of the distribution model. Follow these steps:
1.Create a "dummy" logical system name. Using transaction SALE, choose "Sending and Receiving Systems->Logical Systems->Define Logical System", enter LOGSYSD100, give it any name you want and save.This dummy logical system will serve as the receiver system in the distribution scenario.
2.Using transaction SM59, create RFC destination LOGSYSD100 for the dummy logical system. The RFC destination addresses the same client.
3.Create a distribution view in transaction BD64 with LOGSYS0100 as the sender, LOGSYSD100 as the receiver, and message type MATMAS.
4.Generate partner profiles for the newly created distribution view using transaction BD82, or in transaction BD64 select "Enviroment->Generate partner profiles". Note that this step will generate only the outbound parameters.
5.Using transaction WE20, create the inbound parameters of logical system LOGSYS0100 for message type MATMAS. The approporiate process code for MATMAS is MATM.
Now test your settings by sending material master IDocs via transaction BD10 to LOGSYSD100 and check the results with monitoring transaction WE02.
Regards,
Maxim.

ALE with Same Client

Is it possible to use ALE with Same client...when PO created and send message to IDOC. Than come back the same client to create the SO? As i know, it is possible to go for another client or system. I am not sure is it possible in the same client and also any limition about this?
For eg:-
A purchase order is created in company code 1000.
Then using ALE,the system will generate an Idoc to transfer data to another company code 2000.And the system will generate corresponding CustmerOrder(SO) in company code 2000.

Hi,
Configuring the ALE/Idoc scenerio for the same client is very much possible, because you would defining the same client/port but might used different message type. But so you think this will help you rather than that if the clinet is same rather than configuring the ALE/IDOC setting why not write a piece of ABAP code finding the proper USER EXIT/INCLUDE .i.e. when a PO is created with company code ABC then that USEREXIT will trigger which will send those data to another company code. The user exit can easily be identified by the functional guys.
Mostly the ALE/Idocs scenerios are used when we have multiple clients or multiple system.
Hope this helps.
Cheers,
Jay

Is SAP BI reporting is possible in ECC 6.0 with same client

Hi all,
                         My requirement is, we need to design SAP BI data flow in ECC 6.0 with same client only. Now I am designing the BI data models as per the requirement of SD sales reports in ECC 6.0.For this, when i was extracting the data from SD datasource(2lis_11_vahdr) in RSA3 its showing 0 records,actually as per VA01 some records are available but its not showing in the RSA3.
                          My doubt is , is it possible to extract the data from ECC 6.0 and load the data to the datatargets and get the SAP BI reports in ECC6.0 with the same client.
                          Please suggest as soon as possible.
Thanks

It is possible to load the data from the same client. It all depends on the source system and the client which has been connected in the RFC connection.
Let me know if this helps.
Regards,
Avinash

Two idocs with same idoc number in idx5

We are using an idoc to file scenario where idocs are bundled using bpm and posted to ftp. here the issue is we are getting two idocs with same idoc number in idx5. due to which the file in ftp is getting overwritten.
Could anyone suggest me what to do in this regard.

Hi,
>>>check your sender system is sending same IDoc twice ?
if you send the same IDOC twice they both get different numbers as IDOC number is taken from the IDOC num range
unless you're able to send the same IDOC twice with the same IDOC num somehow
Regards,
Michal Krawczyk

How to create an inbound Idoc from an inbound IDoc in same client

How to create an inbound Idoc from an inbound IDoc in same client
Idoc will come from XI as an inbound idoc to SAP, now I have to read this inbound Idoc and split it into Several Inbound Idocs and now needs to be posted in the same client.
please let me know the procedure..
Thanks in advance,
Sagar

Hi Sagar,
Develop a cusom Z-Inbound function module, configure the Z-FM to trigger when idoc is recieved from XI. In your Z-Inbound function module split the idoc (Recieved from XI) into respective Idocs and Using MASTER_IDOC_DISTRIBUTE post the IDOCs into the same system.
Thanks & Regards

REPROCESSING AN IDOC WITH SAME NUMBER

hi ppl,
i hv sent an idoc to the inbound system with a generated idoc number.
and now i had added some fields fo the same idoc and have to resend it to the same inbound system
with the same IDOC NUMBER.
how can we RESEND AN IDOC with SAME IDOC NUMBER.
thanx very much...
regards,
RAVI.

>
ChakravarthiPonnam wrote:
> with the same IDOC NUMBER.
> how can we RESEND AN IDOC with SAME IDOC NUMBER.
Was that IDOC ended with status 53? If so then I donu2019t think if you could able to edit the segments and reprocess straight forward.
If that IDOC has been ended with Error then just edit this IDOC(WE02>Double click on segment then from menu "Data record>change") now the status has been change to 69. then just reprocess with BD87.
NOW, if your IDOC has ended with 53 and you want to edit this then a minute work-around we have to do. Like first change the IDOC status from 53 to 69 then do the same like for error one,
Cheers
Amit.

Creation of SO from PO through Idocs in Same client

Hi frnds,
     Can we create SO from PO through IDOC's in the same client with different company codes.
Ex: PO created in 100 client in company code AB00. i have to create SO in 100 client in company code AB01.
Any suggestion on this is highly appreciated. Please provide the steps and idocs or let me know the other approach.

for posting the IDOC to same system
use this logic
The steps to send and receive an IDoc in the same system are as follows:
u2022     Create a Dummy Logical System.
     Goto T-Code SALE-> sending and Receiving Systems -> Logical Systems -> New entries. Enter SYSID_CLNT, but this one is Dummy so use the first two characters of the SYSID and prefix 'D' then underscore and then the Client number.
E.g., If ERP_100 is the logical system of the R/3, then create ERD_100 as the dummy system.
u2022     Create Port for the Original System, (ERP_100)
     Goto WE21 and select Transactional Port and press the Create button. Name the Port as "SAP" concatenated with the SYSID in our example it would be SAPERP Select the appropriate version and enter the RFC destination of the system that you are working on in this case it will be 'ERP'.
u2022     Create Partner Profile in partner type LS:
     Receiver Side (Outbound to): In Partner type LS name ERD_100create the Outbound Parameters, give the Message type, Receiver Port same as the port we created in step 2. Enter the Basic type.
     Sender Side (Inbound from): In partner type LS name ERP_100 create the Inbound Parameters, give the appropriate message type and the process code.
u2022     Now create the stand alone program to send the IDoc:
     The program will at some point calls the MASTER_IDOC_DISTRIBUTE function module. When you pass the EDIDC structure it will be populated as follows:
i_edidc-mestyp = message type.
i_edidc-idoctp = basic type.
i_edidc-rcvprt = 'LS'.
CONCATENATE 'SAP' sy-sysid INTO l_port.
i_edidc-RCVPOR = l_port.
i_edidc-rcvprn = 'ERD_000'.
CONCATENATE sy-sysid '_' sy-mandt INTO l_sndprn.
i_edidc-SNDPRN = l_sndprn.
i_edidc-sndprt = 'LS'.
i_edidc-sndpor = l_port.
u2022     Observe that the Sender port and the receiver port is the same, this does the trick. The outbound Idoc is sent on the port SAPERP with the Sender as ERP_100 and receiver as ERD_100 and then the Inbound IDoc is also sent to the same port SAPERP with the Sender as ERP_100 and receiver as ERD_10.
this is the method for creating logical system and setting
and use the respective function module and mesg type for posting it.
cheers
s.janagar
Edited by: Janagar Sundaramoorthy Nadar on Apr 29, 2009 6:32 AM

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear:   g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'.   "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'.              "Direction
* Receiver
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
    g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'.             "Partner type
g_idoc_control_record-rcvpfc = ''.               "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'.             "Partner type
g_idoc_control_record-sndpfc = ''.               "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam               = 'E1BPACHE09'.
g_edidd-segnum               = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
    exporting
      pi_idoc_control_rec_40              = g_idoc_control_record
*     PI_DO_COMMIT                        = 'X'
*   IMPORTING
*     PE_IDOC_NUMBER                      =
*     PE_ERROR_PRIOR_TO_APPLICATION       =
    tables
      pt_idoc_data_records_40             = g_edidd
    exceptions
      idoc_not_saved                      = 1
      others                              = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
    in background task as separate unit
    tables
      idoc_control_rec_40 = g_idoc_control_record
      idoc_data_rec_40    = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Creatin and posting idocs in same client

Hi ,
This is laxman,
My requirement is , when the customer create sales order i want create one more sales order with some changes in same client.
i am using the inbound and outbound idoc with orders message type and process code sd10 for outbound idoc , and i have created new process code for inbound .
and i have created logical sys for client 030 and one more dummy logical sys with ports .then generating the partner profile everything ok.
i am trying to distribute model view while i got error ,model view has not been modified reason is distribution model currently being processed.
Outbound IDoc was created and inbound IDoc was created with status 56(IDoc added with errors ).
means my function module is not triggered.
How can i solve this prob.
have any alternative code for this object.
please help me.
Thanks & Regards
laxman

laxman,
i would highly advise you to post this message over at the ABAP forums, located here:
ABAP Development
if, by chance, a moderator sees this, i guess they can do the necessary transfer too. =)
ryan.

How can we confiure idoc in same client sender as well as receiver

HI Gurus,
How can we create the ale/idoc within the same client, sender as well as receiver.
can u give me step by step procedure.
thanks in advance.

Hi kumar,
see this links these may help u.
http://help.sap.com/saphelp_nw04/helpdata/en/90/c4b523c4c411d2a5ee0060087832f8/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8424011-0d01-0010-e19d-e5bd8ca52244
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/201769e0-3174-2910-e287-baa58d198246
Go through the following Tcode for ALE
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
1)EDI
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
2) ALE
A means of creating and operating distributed applications.
Application Link Enabling (ALE) guarantees a distributed, but integrated, R/3 installation. This involves business-controlled message exchange using consistent data across loosely linked SAP applications.
Applications are integrated using synchronous and asynchronous communication - not by using a central database.
ALE consists of the following layers:
Application services
Distribution services
Communication services
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
Regards,
karthik

IDOC error - same client same system

Hi guru,
i have a requiremnt to generate the IDOC for the same and same client. actually i have to get the data from application server and i have to generate the IDOC.
for this i have created a Zreport and passed the data from application server to segment and i called the
FM "MASTER_IDOC_DISTRIBUTE". after executing the Zreport, IDOC is generated and show the error
status as 29.i.e. Receiver of IDoc is its own logical system.
my logic is as follows.
MOVE 'LS' TO w_edidc-rcvprt.
MOVE 'SBECLNT130' TO w_edidc-rcvprn.
MOVE 'ISU_MR_UPLOAD' TO w_edidc-mestyp.
MOVE 'ISU_MR_UPLOAD01' TO w_edidc-idoctp.
pls let me know the solution for this problem.
Regards,
Balu

Hi,
To send an IDoc from the SAP system to the external system, you must define outbound parameters for the message type and all relevant partners. This is valid even if your receiving system is same as sending systems.
For more information, see Interfaces ® External Systems ® Configure Warehouse Management ® Communication R/3 -> External System ® Maintain Partner Profile in the Implementation Guide for Warehouse Management.
If the system cannot find the partner (that is, the connected partner system) for sending the IDocs, proceed as follows:
Define the missing partner profile.
Resend all existing IDocs, which the system has not yet been able to send.
What is the partner profile of your system ?
Check your partner profiles in WE20 and maintain your message type in Outbound and Inbound parameter for the system.
KR Jaideep,

Idocs processing time between 2 idocs with same material

Hi Gurus
we are getting 2 idocs from other system with same material, first idoc is process successfully, second one is not processing and error throughing - material is currently processing by user WF BATCH. can we set time gap between 2 idocs for processing, where we need to do this?
Thanks in Advance
Ramki

Hi Ramki,
There is another option which you can consider with the help of an ABAPPER. Check if you can use the concept of enqueing.
Ex: When the idoc comes in the SAP system and updates the material quantity in the sales order, it has to get in to the VA02 in order to do this. Now when another idoc is sent along with this simulataneously to update something in the same order, it fails as the order is open by the first idoc.
In this case we write a check in the posting program and check if the order (Order number we get from the idoc) is open or enqued.
If it is enqued then there is a delay by calling an event. This event triggers a job which has a certain delay inserted in it before running.
Hope this helps..
FK

Mapping every row to an idoc with same header

hi,
i have record:
recordset 1..1
Header 1..1
Row      0..unbounded
i want to map it to :
idoc 0...unbounded
Header 1..1
Row     1..1
i want every row in source will create an idoc. every idoc will have same header but different row.
can u please explain how do i do that?
thanks,
Tomer

Hi,
Map row node with IDOC node. It will create an IDOC per row.
Now map header node with header node. Between the header nodes you have to create a User defined function commonlly named CopyPerValue:
public Void copyPerValue (String[] a, String []b, ResultList result, Container container){
for (int i=0; i<a.length; i++){
      result.addValue(b[0]);
You have to map row with a. And header with b.
Regards,
Carlos

Data Conversion rules for EDI processing (same client IDOC processing)

Hi,
I am trying to post IDOCS in same client.Its a PO->SO process.
ie. there will be 1 outbound and inbound idoc in same client using EDI processing.
I am using Data Conversion using Rulesfor converting sender fields.
The LIFNR and PAORG od segment E1EDKA1 has to be converted.
For ALE processing, the Data conversion is been done correctly.
But no conversion is done for EDI.
Can anybody help me with this problem ?
Thanks in advance.
Regards
Megha

Issue solved

Idocs with same client

Similar Messages

Maybe you are looking for