Replacing IDoc - IDoc with IDoc - Proxy

Hi every one,
I have an IDoc - IDoc integration scenario between 4.5B and ECC 6.0 systems. The Idoc in the receiver system is not directly posted but an User - Exit is called and every thing is working fine.
I thought of experimenting replacing the scenario with Idoc - Proxy, and the source being 4.5B and target ECC. The User-Exit stuff as told above will taken care while implementing proxy.
Approach:
I create an inbound interface object in IR and use the Idoc as the message type and generate a server proxy using SPROXY in the ABAP stack of XI.
Please correct me. Also notify me if there are any potentials problems.
Regards,
-Naveen.

Hi,
SPROXY on the ECC system should be used to generate the ABAP proxy, not the XI system. Therefore, configurations will be required on the ECC system to point to the XI system in order to retrieve the interfaces to generate the ABAP proxy.
Also, it might be easier to create a simpler message type to use in the interface. IDOC has a quite complex structure and probably contains a lot of elements which will not be used by your proxy. The proxy interface should be as simple as possible to simplify your program development.
Regards,
Bill

Similar Messages

Idoc to idoc scenario with idoc tunneling

IN idoc to idoc scenario with idoc tunneling the XML_CONVERSION parameter to value 2 is set whish means An IDoc is converted to IDoc-XML if requested by the service
I want to know where we specify this and how we specify?

1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
ref these weblogs.
It is given under;
TCODE - SXMB_ADM
- Integration Engine configuration
- set the XML_CONVERSION parameter to value 2

Query on Idoc Packaging with PI7.1 EHP1

HI PI Experts,
I have a scenario where batch run triggers the 100's of Idocs in R3 in few milli seconds, which means all Idocs are triggered in one go From R3.
Do we still need to set Check box for Collect Idocs in Partner Profile in R3 for Idoc Packaging ?
I want to make out the difference in 2 configs for Idoc Packaging where
A) All Idocs are sent via Report run of RSEOUT00 at a go after collection.
B) All Idocs are triggered at same time via Batch Run at same time.
Assumption:
PI is configured to use Sender Idoc Adapter with Idoc Package Size of 10.
OR
I frame my Query in other way"
What does Collect Idoc and running Report RSEOUT00 achieve to make sure that Multiple IDOC Nodes come into 1 XML message? OR Its only PI Sender Idoc Adpater take care of it when multiple Idocs of same type comes through PI?
Please reply .
Regards,
Anurag

Hi Anurag,
In the sender IDOC adapter if the packaging option is not activated, then the IDoc packages get split into single PI messages, one PI message per IDoc. IDoc sender functionality is enhanced to preserve and process IDoc packages without splitting the IDoc package into individual PI messages. I.e. single PI message contains multiple IDocs including control records. Where as running the report RSEOUT00 will just send all the IDOCs that are in waiting state to their respective destinations.
For the sender IDoc adapter to be able to process packages, it should receive the IDocs in a group. I.e. in the sender partner profile the packaging option has to be activated. Though you've activated the packaging option in the sender partner profile, If you dont check collect option in sendet IDOC adapter then the IDOCs get splitted into individual PI messages.
Regards,
Priyanka

Proxy to JDBC Sync, with Idoc Receiver

Hello all,
I have to set up following synchronous scenario.
PROXY -> PI -> JDBC | JDBC -> PI -> PROXY
JDBC -> PI -> IDOC
In other words, I need that the response from the JDBC Receiver adapter is sent back to R3 to an IDOC and the originating PROXY.
How can I achive this? I mean how can I send the synchronuos response back to the originating PROXY, and in the other hand send an asynchronous message to the IDOC.
This is a message with a large quantity of info, so I'm not sure what to use or how to use it.
Thanks for your help.
Felipe

Hi Felipe
PROXY -> PI -> JDBC | JDBC -> PI -> PROXY
JDBC -> PI -> IDOC
The message to the IDOC need to be sent from response ?
Is your proxy SYNC?
Use a BPM for this
1. receive the message from Proxy.(SYNC)
2. Send it to JDBC (SYNC)
3. Map the proxy request to JDBC request and JDBC response to Proxy response.
4. Send the JDBC response to IDOC
Thanks
Gaurav

IDOC stops with status 30

We have migrated from SAP 4.7 to ECC6 , the Xi is on version 2.0 .
After migration some of our IDOC created from ABAP Proxy are not getting processed automatically. It stops with status 30 and we need to reporcess this . After reporocess the messages are getting processed
Can anyone help in finding out how to find this error
Edited by: Sanjeev Koganti on Aug 7, 2008 9:27 AM
Edited by: Sanjeev Koganti on Aug 7, 2008 9:39 AM
Edited by: Sanjeev Koganti on Aug 7, 2008 9:43 AM

Hi,
The status 30 of IDOC, status text u201EIDOC is ready for dispatching (ALE service)". Internally, the constant ALE_READY_FOR_DISPATCHING represents this status.
Processing Selected Intermediate Documents -->
Use program RSEOUT00 to start processing all selected intermediate documents.
You need to check your ALE settings for that error. test the proxy mannualy using payload.
Then you will come to know wheather your proxy works fine or not.
Go to SPROXY --> Select Your SERVICE INTERFACE --> clikc on TEST button or Press F8 --> provide your payload and check the result.
Regards,
Gunti

Can we send attachements with Idoc?

Hi ,
Can we send attachements with Idoc?

Hi,
1. in standard you cannot
2. you could however send it in a text field
and then combine in adapter or java proxy
on the other hand abap proxies work with attachments
in standard - check out my blog:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Message with IDOC number, created by LSMW, missing in job log in SM37

Hi gurus,
We have a temporary interface which uses LSMW to create IDOCs and update in SAP. It's used for materials, BOMs and document info records. In LSMW we have defined standard message types MATMAS_BAPI, BOMMAT and DOCUMENT_LOAD for the IDOCs. All these have the same problem.
A background job runs and starts LSMW. In the job log in SM37 I want to see which IDOCs were created. For some reason this is different in my development system and my test system, and as far as I know all settings should be the same. In the test system LSMW creates more message lines in the job log, than it does in the dev system. Message number E0-097 is "IDOC XXXX added", and this is missing in the dev system.
This is what it looks like in the dev system:
Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
Import program executed successfully                                                             /SAPDMC/LSMW   509    I
File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW   502    I
Conversion program executed successfully                                                    /SAPDMC/LSMW   513    I
Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')       /SAPDMC/LSMW 516    I
And this is what it looks like in the test system. More information, which is exactly what I want in dev system too:
Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
Import program executed successfully                                                             /SAPDMC/LSMW 509    I
File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW 502    I
Conversion program executed successfully                                                    /SAPDMC/LSMW 513    I
File 'XXX.lsmw.conv' exists                                                                              /SAPDMC/LSMW   502   I
IDoc '0000000002489289' added                                                                      E0                         097   S
File 'XXX.lsmw.conv' transferred for IDoc generation                                      /SAPDMC/LSMW   812   I
Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')      /SAPDMC/LSMW   516   I
In both cases the IDOC is created and update works fine.
My only issue is that I can't see the IDOC number in the dev system. I know I can get the IDOC number in WE02, but in this case we have program logic which reads the job log to be able to check IDOC status before sending OK message back to the other side of the interface.
I hope any of you can have an idea how I can update somewhere to get message E0-097 with IDOC number into the log.
Regards,
Lisbeth

Hi Arun,
If you want to show your messages in the job log you have to use the MESSAGE statement. In case you use WRITE statements an output list be created which can be found in the spool (there is an icon to go to the spool directly).
Regards,
John.

IDoc failed with the error massaeg "Instance of object type could not be ch

Hi All
I am getting IDoc failed with the error massaeg "Instance of object type could not be changed"
Message type :PORDCR
Basic type : PORDCR05
Message no. BAPI003
Status : 51
All POs are get uploaded in SAP during Cut over activities only.
Please suggest on this.It will be a great help.
Thanks
Ajit

Hi
After uploading POs into SAP we are changing quantity and value in PO in Legacy system, and for this all IDocs are failed, subsequently these changes are not triggering to ECC.
Please help
Thanks
Ajit

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

Idoc enhancement with ABAP

Hi all,
we are currently in a project to implement SAP HR as HR master and distribute HR master data to other legacy systems using SAP XI.
There will be two different interfaces from SAP HR to XI, one for real-time updates of changes (delta) and one for batch updates of complete records. We use SAP R/3 4.7 ext2 and want to use Idoc type HRMD_A06 which contains all HR data (we will have to add segments for two infotypes, but that is not the problem).
The problem is that there is some information we need to distribute that not automatically gets included in this Idoc type (such as SAP personell number for manager of the org.unit an employee belongs to). My guess is that this has to be filled using some custom ABAP.
Does anyone have any experience with adding such information to an Idoc? We can always find a suitable field in the Idoc to store the values if we only can retrieve the correct information.
And secondly, how do we make sure this extra information is stored for the correct employee segment in the Idoc?
Finally, can we implement this function module so that it runs after the general Idoc is created, runs through the entire IDoc and adds the correct information for each employee segment, and then send the finished IDoc to XI? This goes for both real-time interface (implemented using change-pointers) and batch interface (scheduled job to collect master data).
Any information or experience on this matter will be highly appreciated. Any other suggestions to how this problems can be solved are also welcome.
Thanks in advance.
Best regards, Kenneth Eriksen

Hi Kenneth,
Sorry for the misleading information abt the user exit at the first place.
For batch process,
1. Run PFAL transaction.
2. Follow the same process to determine the manager in user exit EXIT_SAPLRHAL_003. set the parameter flag as 'X'. Also export the parameter 'Flag' to memory id in the user exit after the process.perform the logic to determine manager pernr only if infotype 0001 is filled.
3. Second user exit EXIT_SAPLRHA0_001 will follow the previous exit. Import the parameter from memory id. if flag eq X. no process.
4. Manager pernr will be passed.
For change-pointer process,
only 1001 information should be triggered by change-pointers.
1.)run rbdmidoc to trigger change-pointers for hrmd_a.
2.)user exit EXIT_SAPLRHAL_003 will be executed internally in the first step. should not perform manager logic as no 0001 infotype filled. It means parameter FLAG is blank.
3). in the user exit EXIT_SAPLRHA0_001 , perform manager logic for change-pointers only if flag eq space.
following logic should be followed :
a.) IDOC_DATA fill contains the 1001 records.
b.) loop at idoc_data.
 read each record and determine 0001 infotype for all employees with new manager(as described in my first reply). append the 0001 records into idoc_data_temp.
c.) process each record by record in idoc_data.
d.) after the endloop. move all the records from idoc_data_temp to idoc_data.
now idoc_data will contain only 0001 records no 1001 records.
e.) again loop at idoc_data, perform manager pernr logic.
The change-pointer process is just overriding the standard process and manipulating custom records.
this is the one way of achieving the solution.
The other solution to achieve change-pointers is to perform lot of customization.
1.) create a custom program to read the change-pointers from bdcpv table to read the unprocessed records for message type hrmd_a.
2.)create infotype 0001 records from 1001 data.
3.) also perform manager pernr logic for 0001 records as we are not calling standard transaction(master_idoc_create_smd_hrmd).
4.) follow the logic in the sample program to create idocs.
FUNCTION ZSKIT_CREATE_IDOCS.
""Local interface:
DATA:
*·······control·record·for·the·IDoc
 IDOC_CONTROL LIKE EDIDC,
*·······data·records·for·the·IDoc
 T_IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE,
*·······table·for·the·IDocs·created·by·MASTER_IDOC_CONTROL
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
*·······partner·type·for·logical·system
C_PARTNER LIKE EDIDC-RCVPRT,
*·······help·variable·for·the·check·if·an·IDoc·has·to·be·created
H_CREATE_IDOC.
*·variables·specific·for·this·example
DATA:
*·······field·strings·with·IDoc·segment·structure
E1XITEM LIKE ZSKILL_CAT occurs 0 with header line,
*·······data·to·be·put·to·the·control·record
C_MESSAGE_TYPE LIKE EDIDC-MESTYP VALUE 'XAMPLE',
C_BASE_IDOC_TYPE LIKE EDIDC-IDOCTP VALUE 'XAMPLE01',
*·······segment·types·to·be·put·to·the·data·record·table
C_HEADER_SEGTYP LIKE EDIDD-SEGNAM VALUE 'E1XHEAD',
C_ITEM_SEGTYP LIKE EDIDD-SEGNAM VALUE 'ZSKILL_CAT'.
E1XITEM-SKILL_ID = '12345678'.
E1XITEM-SKILL_TYPE = 'SKI'.
E1XITEM-SHORT_TEXT = 'Test'.
E1XITEM-LONG_TEXT = 'Test skill'.
E1XITEM-TENANT_ID = 'check1234'.
E1XITEM-BEGDA = sy-datum.
E1XITEM-ENDDA = sy-datum.
E1XITEM-SKILL_UP = '01234567'.
E1XITEM-SKILL_DOWN = '3456789'.
append E1XITEM.
clear E1XITEM.
E1XITEM-SKILL_ID = '12345678'.
E1XITEM-SKILL_TYPE = 'Test'.
E1XITEM-SHORT_TEXT = 'Check'.
E1XITEM-LONG_TEXT = 'check skill'.
E1XITEM-TENANT_ID = 'test1234'.
E1XITEM-BEGDA = sy-datum.
E1XITEM-ENDDA = sy-datum.
E1XITEM-SKILL_UP = '01234567'.
E1XITEM-SKILL_DOWN = '3456789'.
append E1XITEM.
clear E1XITEM.
*···put·the·application·item·record·to·the·IDoc·segment
loop at e1xitem.
*···append·record·to·IDoc·data·table
 T_IDOC_DATA-SEGNAM = C_ITEM_SEGTYP.
 T_IDOC_DATA-SDATA = E1XITEM.
 APPEND T_IDOC_DATA.
ENDLOOP.
idoc_control-rcvprt = 'LS'.
IDOC_CONTROL-RCVPRN = 'DI2440'.
IDOC_CONTROL-MESTYP = 'ZSKIT'.
IDOC_CONTROL-IDOCTP = 'ZSKIT'.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
*·in·update·task···"if·application·document·is·posted·in·update·task
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = T_IDOC_DATA.
*exceptions
*···········error_in_idoc_control··········=·1
*···········error_writing_idoc_status······=·2
*···········error_in_idoc_data·············=·3
*···········sending_logical_system_unknown·=·4
*···········others·························=·5.
*·A·commit·work·has·to·be·done.·It·could·also·be·done·in·the·calling
*·application.
COMMIT WORK.
READ TABLE T_COMM_CONTROL INDEX 1.
IF SY-SUBRC <> 0.
*·no·IDoc·was·created,·you·can·react·here,·if·neccessary
ENDIF.
ENDFUNCTION.
5.) also set the change-pointers records as 'processed' status using standard function module.(search for function module starting like change_pointers_read_mode_set)
Please decide between 2 solutions .
Also revert back for any concerns.
Regards,
Senthil

Inventory count w/o reference doc "MI09" with IDoc WVINVE02

Dear forum,
I am trying to create an inventory count without reference to a document and I thought I would use IDOc WVINVE02 with message code WVINVE. We don't have an SAP inventory document, but would like to use just an external reference.
When running transaction MI09 in the GUI it's quite easy to create an inventory count using:
Plant
Storage location
Special stock
Count date
Material
Quantity
Unit of measure
That's all we want to have.
I have tried to post an IDoc WVINVE02 inbound using FM IDOC_INPUT_STORE_INVENTORY with the corresponding data, but without success. The IDOc interface only states "IDoc not fully processed".
I need some help with how to input data and also need to understand if it is possible to use this IDoc for inventory count WITHOUT a reference document. The documentation available is not clear enough on this. Has anyone experienced a similar challenge?
Thanks!
::Ellen

Hi Ellen,
Were you able to find the solution?
We are facing a similar issue.
Please help.
Thanks,
Pratibha

Read MULTIPLE idocs data with all sgmn to my internal table in a single

Dear SAP Folks!
I have a question, I know to read SINGLE idoc data with all segments, we have FM IDOC_READ_COMPLETELY but my requirement is to Read MULTIPLE idocs data with all segments to my internal table in a single shot without keeping this FM in loop! since it is performance issue, at a time i may want to read 1000 idocs data!
Could anyone please let me know is there any way to get this, keeping mind of performance and any other FM?
Best Regards,
Srini

Hi,
I know idoc numbers and i can write a select Query to DB table EDID4 to get all segments data to my internal table. But i am looking for FM to do this. because i have too many number of idocs and each idoc is having many segments(I am thinking in performance point of view!) The FM IDOC_READ_COMPLETELY can accept only ONE IDOC number as import parameters at a time to get segment data. in similar way do we have any other FM? or other way? except select query to EDID4 table?
Best Regards,
Srini

Want to add multiple idoc type with single message type.

Hi Gurus,
I have a problem. I want to add multiple idoc type with single message type in WE20.
How we can do this in WE20 or is there any other way to do that?
Please help me.
Thanks in advance.
Srimanta.

hi,
basically in partner profile i.e. in we20 , we add details to the receiver / sender port that we have created using we21.
so what exactly we do in that is that we first use the message type for those idocs that we have created.
now based on those message type we create a process code. now this is the reason why you cannot apply several message types with the same name in we20... as process code is unque for each message type.
so thats why you can only assign the same message name to several idocs in we82 and then in we20 define the process code for that message type.
it will solve your problem.
hope this will help you!!!
Thanks & regards,
punit raval.

File to multiple IDOCs scenario with the same receiver system

Hi guys,
I have to design and implement the following scenario:
I will receive one file with many lines (Records) with data for materials, quantities, operations etc..
Based on the values of some fields of each line, I will have to create an IDOC for each material.
For example:
if operation type = "INSERT", and Labor = 001 then create 3 Idocs of type MBGMCR with movement types=101, 261,311 that have to be posted one after the other to the same receiver system.
else if operation type = "INSERT", and Labor <> 001 then create an Idoc MBGMCR with movement type=311 and plant = 1001.
else if operation type = "Delete", and Labor = 001 the created 3 Idocs MBGMCR with movement type=312, 262 1002 and post them serially to the same receiver system.
else if operation type = "Delete", and Labor <> 001 the created 1 Idoc MBGMCR with movement type=312.
All IDOCS are posted to the same SAP R/3 system. We do not care about the sequence, except for the cases where 3 IDOCS are created.
I am trying to think of a good design in performance terms.
It is obvious that I will need BPM for sure.
I am thinking of creating a mapping program that will produce 4 message types for the different cases from the initial file and then create a different message mapping for each case from the message type to the IDOC.
I am asking you if I have to include everything (mappings) in BPM with a "fork" step?
Or shall I produce only the 4 message types and then post them to R/3 and execute the mappings in R/3?
Best Regards
Evaggelos

hi,
>>I am thinking of creating a mapping program that will produce 4 message types for the different cases from the initial file and then create a different message mapping for each case from the message type to the IDOC.
To me this seems to be the right solution.
here u will create different message mappings and write them sequentially in interface determination. the multi mapping will then be utilised in transformation step in BPM.
thus if this is the only requirement there is no need of using a fork step.
[reward if helpful]
regards,
latika.

Mapping Problem with IDOC HRMD_A05

Hi All,
When i am mapping source structure with IDOC HRMD_A05 i am getting Mapping not sufficiently defined...
The idoc is used to change the address of employee(infotype 0006)..
my source structure is
EMPADDR_MT
 EmpAddr1
 Trans_INFTY *
 Address1
 AddressType *
 PERNR *
 EFdate *
 Addr1 *
 Addr2 *
 ADDR4 *
 City *
 Country *
 state *
 Postalcode *
the fields to be mapped
So can any one help me out what r fields to be maintained for HRMD_A05...
Regards,
Sridhar
Message was edited by: sridhar reddy kondam

All the required fields & segments(shown red in mapping editor or min occurence:1) of idoc need to be mapped.If any of the fields are not available in your source for mapping..map those fields with empty constants using constant option of the mapping editor.

Replacing IDoc - IDoc with IDoc - Proxy

Similar Messages

Maybe you are looking for