E1PRTOB segment lacking into AUDIT IDoc

Hi to all,
I have a problem with AUDIT. When I execute the RBDSTATE function module to perform ale Audit, the Audit IDoc is sent to XI but without the E1PRTOB segment into payload (I've seen this into SXI_MONITOR transaction). However, I see the segment into the WE02 transaction in the AUdit sender system, and I've also controlled the metadata into XI IDX2 transaction and they are ok! What is the problem?
Thanks!

Gabriele.
Is your problem fixed..
If its not you might want to take a look at sapnote..828277
Thats your issue..
Regards
Ravi Raman
Pls reward points if useful

Similar Messages

Split Single IDOC into Multiple IDOC's Based on Segment Type

Hi Experts,
I have a scenario IDOC to FILE , Split Single IDOC into Multiple IDOC's based on Segment Type
Outbound:
ZIdocName
Control Record
Data Record
Segment 1
Segment 2
Segment 3
Status Record
I should get output like below
Inbound:
ZIdocName
Control Record
Data Record
Segment 1
Status Record
ZIdocName
Control Record
Data Record
Segment 2
Status Record
ZIdocName
Control Record
Data Record
Segment 3
Status Record
Please suggest me step by step process to achieve this task.
Thanks.

Thanks a lot Harish for reply.
I have small doubt. According to your reply , If we have N number of segments in single IDOC with same fields in all segments then for splitting Single IDOC into Multiple IDOC's based on Segment Type we need to duplicate N number of target IDOC tree structure.
Is that possible to Split single IDOC into Multiple IDOC's based on Segment Type using only one Target IDOC structure without duplicating the Target IDOC structure tree.

How to transfer IDOC - E1EDL24 segment data into my_itab?

Hi Experts,
Am trying to transfer data from a Segment-E1EDL24 to an itab of fs_itm_data.
data: begin of fs_itm_data,
tapos(6),
nista(18),
altme(3),
end of fs_itm_data.
So, when u see this E1EDL24 segment in WE31, there are lot of fields in it.
And am getting the data as,
idoc_data-segnam = E1EDL24
idoc_data-sdata = 00001012345678 (i.e. POSNR+MATNR)
So, to do dump this segment data into itab, am wrting code by using OFF SETTIng ; like,
fs_itm_data-tapos         = edidd-sdata+0(6).
fs_itm_data-nista         = edidd-sdata+146(15).
fs_itm_data-altme         = edidd-sdata+161(3).
1 - but, I dont think that, this is correct practice
2 - if there is no value for Alt UNIT of edidd-sdata+161(3), wht happens?
3 - If MATNR varies in its length, like 1 - 18?
so, let me know that,
1 - How to transfer this segment data into this itab?
THANQ

If I understand ur requirement correctly then u need to move idoc_data-sdata to an internal table itab.In that case no need to move data from idoc_data-sdata to itab directly using OFF SETT.
1st declare one wrokarea of type E1EDL24.
data: w_E1EDL24 type E1EDL24.
Now move the content of idoc_data-sdata to the workarea.
move idoc_data-sdata to w_E1EDL24.
Now u can do field by field assignment to move data from w_E1EDL24 to ur table.
fs_itm_data-tapos = w_E1EDL24-tapos.
fs_itm_data-nista = w_E1EDL24-nista.
fs_itm_data-altme = w_E1EDL24-altme.
Here I am assuming that field names in the structure fs_itm_data are same as field names in the segment w_E1EDL24.
Regards,
Joy.

How to add an feild to a segment to an existing idoc sturucture?

how to add an feild to a segment to an existing idoc sturucture?
please help me out with the step step by process...
thnaks and regards,
anu

Hi
use the WE31 Tcode to edit the segment
see the following steps
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji

Flat File IDOC - ECC, segment defn x in IDoc type y CIM type do not exist

Hi,
I'm working on idoc flat file > sap scenario. Everything seems to be working up until the point where I get an error message:
EDISDEF: Port EDIPORT segment defn E2FINBU000 in IDoc type FIDCCP01 CIM type do not exist
I've loaded the meta data, and the file structure is fine. I believe the issue is related to PI not having the idoc I'm interested in listed in WE30. How do I reference the standard IDOC type FIDCCP01? Ideas I've had are around SWCV or transport from another system, the first I'm not sure which SWCV, the later seems a bit of a bodge and I dont like the idea.
Thanks
James.

Hmm.. some light for the situation. Seems that the segments imported are:
E1FINBU     E2FINBU     31I
E1FINBU     E2FINBU001     40A
E1FINBU     E2FINBU002     40B
E1FINBU     E2FINBU003     45A
E1FINBU     E2FINBU004     45B
E1FINBU     E2FINBU005     46A
E1FINBU     E2FINBU006     46C
Which indeed does not have E2FINBU000, which the IDOC is most definitely trying to pass. I can only guess that the middleware producting this IDOC is flawed, and that standard SAP ALE will accept this as E2FINBU (It works into another SAP system without XI).
Guess I've answered my own question, but feel free to offer light for points
Thanks,
James.

Splitting multiple IDoc XML files into single IDoc messages for R/3

Hi all. I have a problem splitting IDoc XML files coming in to XI. I currently have an interface that takes in single store sale IDoc transactions (type WPUBON01) in an IDoc XML file. I then have some complex graphical mapping on the IDoc before sending to R/3 via the IDoc adapter. This works fine. However, we now wish to include multiple sales in one file i.e. many WPUBON01 IDocs. I could use message splitting to do this BUT the mapping is so complex, I do not wish to have to change it to enable the processing of many IDocs in one file instead of just one.
What I want to do: have one mapping splitting a multiple IDoc XML file into single IDoc messages and then another taking these single messages as before and performing the mapping. I cannot find a way to do this in one interface; the main problem I'm having is getting XI to split the multiple IDocs into many single IDoc messages within XI itself. I'd be very grateful for any advice on the best way to do this.
Thankyou.
Stuart Richards (Halfords, UK)

Bhavesh,
Thanks again for a clear explanation... I'm moving forwards but still struggling. I've been on this all afternoon today (after a break on other things) and just cannot get my message to split properly (though the SOAP adapter problem I had earlier is now fixed!). If my initial IDoc XML file contains this format:
<WPUBON01><IDOC>....</IDOC>
<IDOC>....</IDOC>
<IDOC>....</IDOC></WPUBON01>
.. I'm not sure what the cardinaility on the first message mapping and interface mapping should be. I'd have thought the source interface would be 1 and the target would be 0..unbounded but this isn't working. I'm trying different things but I get different errors each time. Currently, I have the above cardinality in my first interface and I'm passing in the following data:
<WPUBON01><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832292</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160633</VORGZEIT><BONNUMMER>1001</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1001</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832293</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1002</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1002</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832294</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1003</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1003</ZUONR></E1WPB06></E1WPB01></IDOC></WPUBON01>
In the message monitor, I get a chequered flag. Great. However, I get the dreaded error 500 in the SOAP receiver comm channel:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Exception caught by adapter framework: SOAP Error
Delivery of the message to the application using connection AFW failed, due to: SOAP Error.
Any ideas as to what this might be?! I'm getting there.... if I get a solution out of this, I promise to write the blog myself!
Cheers
Stuart

Breaking up of, One IDoc to many IDocs & combing Many IDocs into one IDoc?

Does anybody have any sample code of:
Splitting an IDoc into multiple IDocs and
Combining many similar IDocs into one IDoc
Any pointers will be appreciated.
Regards
Mahesh

This is the code for splitting of an inbound idoc into multiple idoc
REPORT ztemp no standard page heading .
******************Data Declaration for selection screen***************
TABLES: edidc,edidd.
CALL SELECTION-SCREEN 9000.
SELECTION-SCREEN: BEGIN OF SCREEN 9000,
                  BEGIN OF BLOCK b1 WITH FRAME.
SELECT-OPTIONS: idocno FOR edidc-docnum.
SELECTION-SCREEN:END OF BLOCK b1 ,
                  END OF SCREEN 9000.
*******************Data Declaration ************************************
DATA : it_contrl LIKE TABLE OF edidc WITH HEADER LINE,
       it_hdata     LIKE TABLE OF edidd WITH HEADER LINE,
       it_fdata LIKE TABLE OF edidd WITH HEADER LINE,
        it_gdata LIKE TABLE OF edidd WITH HEADER LINE,
       it_data LIKE TABLE OF edidd WITH HEADER LINE,
       it_status LIKE TABLE OF bdidocstat WITH HEADER LINE,
       it_bdwfretvar LIKE TABLE OF bdwfretvar WITH HEADER LINE,
       it_bdi_ser LIKE TABLE OF bdi_ser WITH HEADER LINE,
       it_ldata LIKE TABLE OF edidd WITH HEADER LINE,
       it_tede2 LIKE tede2,
       vbeln LIKE vbak-vbeln,
       idocnum LIKE edidc-docnum,
       result LIKE bdwfap_par-result,
       it_stat LIKE edids.
DATA : count TYPE i ,
       counter TYPE i ,
       temp TYPE i VALUE 1 ,
       line TYPE i ,
       tab LIKE sy-tabix.
*********************passing values to control record*****************
it_contrl-direct = '2'.
it_contrl-rcvprn = 'ID3IDES802'.
it_contrl-rcvprt = 'LS'.
it_contrl-doctyp = 'ORDERS05'.
it_contrl-idoctp = 'ORDERS05'.
it_contrl-sndpor = 'ZSOFI'.
it_contrl-sndprt = 'LI'.
it_contrl-sndprn = '1000'.
it_contrl-mestyp = 'ORDERS'.
APPEND it_contrl.
************************Select query for data*************************
SELECT   * FROM edid4 INTO CORRESPONDING FIELDS OF TABLE it_fdata
WHERE   docnum IN idocno.
SELECT   * FROM edid4 INTO CORRESPONDING FIELDS OF TABLE it_data
WHERE   docnum IN idocno AND segnam NOT LIKE 'E1EDP%' .
SELECT   * FROM edid4 INTO CORRESPONDING FIELDS OF TABLE it_hdata
WHERE   docnum IN idocno AND segnam LIKE 'E1EDP%'.
**************select query to count the no of E1EDP01 segment*********
SELECT COUNT( * ) FROM edid4 INTO count WHERE docnum IN idocno AND
segnam = 'E1EDP01'.
*************to determine the no of idocs to be generated************
count = count / 5.
PERFORM datasplit.
**********************************for remaining idocs*****************
counter = count MOD 5.
IF counter NE 0.
PERFORM dataremain. .
ENDIF.
*&      Form datasplit
      text
--> p1        text
<-- p2        text
FORM datasplit .
LOOP AT it_data.
    MOVE-CORRESPONDING it_data TO it_gdata.
    APPEND it_gdata.
ENDLOOP.
DO count TIMES.
    PERFORM split.
    perform idoccreate.
    enddo.
ENDFORM.                   " datasplit
*&      Form SPLIT
      text
--> p1        text
<-- p2        text
FORM split .
LOOP AT it_hdata.
    IF temp <= 5.
      ON CHANGE OF it_hdata-segnam.
        IF it_hdata-segnam = 'E1EDP01'.
          MOVE-CORRESPONDING it_hdata TO it_gdata.
          APPEND it_gdata.
        ELSE.
          MOVE-CORRESPONDING it_hdata TO it_gdata.
          APPEND it_gdata.
          temp = temp + 1.
        ENDIF.
      ENDON.
    ENDIF.
ENDLOOP.
ENDFORM.                    " SPLIT
*&      Form dataremain
      text
--> p1        text
<-- p2        text
FORM dataremain .
CLEAR it_gdata[].
LOOP AT it_data.
    MOVE-CORRESPONDING it_data TO it_gdata.
    APPEND it_gdata.
ENDLOOP.
LOOP AT it_hdata .
    IF sy-tabix > 10.
      MOVE-CORRESPONDING it_hdata TO it_gdata.
      APPEND it_gdata.
    ENDIF.
ENDLOOP.
perform idoccreate.
ENDFORM.                    " dataremain
*&      Form idoccreate
      text
--> p1        text
<-- p2        text
form idoccreate .
***********************for creating the inbound idocs****************
CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'
   EXPORTING
     pi_status_message             = it_stat
     pi_do_handle_error            = 'X'
   PI_NO_DEQUEUE                 = ' '
     pi_return_data_flag           = 'X'
PI_RFC_MULTI_CP               = '    '
   IMPORTING
     pe_idoc_number                = idocnum
     pe_state_of_processing        = sy-subrc
     pe_inbound_process_data       = it_tede2     "for process code
    TABLES
      t_data_records                = it_gdata
T_LINKED_OBJECTS              =
    CHANGING
      pc_control_record             = it_contrl
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.
COMMIT WORK.
*it_contrl-status = '64'.
modify it_contrl index 1.
****************for posting the idoc**************************
CALL FUNCTION 'IDOC_INPUT_ORDERS'
    EXPORTING
      input_method                = 'A'
      mass_processing             = '1'
   IMPORTING
     workflow_result             = result
APPLICATION_VARIABLE        =
IN_UPDATE_TASK              =
CALL_TRANSACTION_DONE       =
   DOCUMENT_NUMBER             = vbeln
    TABLES
      idoc_contrl                 = it_contrl[]
      idoc_data                   = it_gdata[]
      idoc_status                 = it_status[]
      return_variables            = it_bdwfretvar[]
      serialization_info          = it_bdi_ser[]
EDI_TEXT                    =
EDI_TEXT_LINES              =
   CLEAR : it_contrl-docnum.
COMMIT WORK.
endform.                    " idoccreate

How can we configure or control records go into single idoc thru BODS?

Hi,
Our case is -
IDOC format has three segment. Each segments has child nodes -
1. CONTROL SEGMENT - This is required only once per idoc.
child1
child2
2. SEGMENT1 - sinlge source record to be broken into two segments.
child1
child2
3. SEGMENT2 - sinlge source record to be broken into two segments.
child1
child2
we have a single source (lest say having 100 records).
In the current design which does generates IDOCS but as many as the no of records in source. Currently we use a row generation transform as dummy (with row count as 1) to pass to the IDOC parent nodes's from clause to escape the error - invalid input to the parent nodes.
Child nodes are either mapped to the source table or are null.
Question - How can we configure this in a way that we control how many records go into single idoc. Ex - lets say 50 per idoc so only 2 idoc should be created if 100 records are there.

HI,
this sounds to me like Data Services. If so I would suggest to post this into the Data Service forum.
regards
Ingo HIlgefort

HRMD_ABA05 extension issue. Extension segment not present in idoc.

hi all,
i have built the extension of the HRMD_ABA message type following the istruction of note 105148. My goal is to export the infotype 41 . Soi have done:
1) creation of segment Z1P0041 from E1P0041 ( WE31 )
2) creation of extension ZHRMD_ABA05 from HRMD_ABA05 basic type
3) updated the T777D table for 0041 infotype
4) updated the partner profile for the receiver ( WE20 )
5) updated the idoc tpye assignment ( WE82 )
6 ) updated the receving system idoc input set up ( WE57 )
7) updated the distribution model ( BD64 )
Debugging the outbound process from PFAL i can watch the Z1P0041 segment as output of RH_MASTER_IDOC_DISTRIBUTE_HRMD but i can't view the segment into the idoc.
Can you help me?
Thanks and regards. Luigi.
Edited by: luigi la motta on Feb 8, 2011 9:48 AM

I have solved my problem explained into the previous post.
I have coded into the following enhancements of the sender system:
a) badi HRALE00OUTBOUND_IDOC
b) user exit EXIT_SAPLRHA0_004
c) user exit EXIT_SAPLRHA0_001.
Regards luigi.

How can I split an Orders05 iDoc into multiple iDocs?

Hello,
Can one of you experts please tell me how I can split an ORDERS05 iDoc into multiple iDocs based upon Delivery addresses?
For example, if the iDoc contains 3 different Delivery Addresses then I need to split it into 3 iDocs.
It has been suggested to me that I can Create a custom function module. In this custom fm split the idoc into 3 based on the delivery address and create it using the FM MASTER_IDOC_DISTRIBUTE.
Problem is I don't know how to do this. Any help is greatly appreciated. Thanks.
Dan

Hi Dan Avis
Write a Custom Z program .
1 get order05 idoc number....
2 get the segment details...(Based on you condition...)
3 In a loop send the data to the FM MASTER_IDOC_DISTRIBUTE (Based on you condition...)
4 IDOC will generated,,,every loop and
5 Change the status of original idoc .
or
Create Function module and use the FM as process code to create 3 idocs...and processs...new generated idoc and block original idocs...
Call me if you have questions @ 302 290 5677
Thanks
Ramesh

EDISDEF:Port sid segment defn Z2Q0015000 in idoc type... CIM

Hi Experts,
I am getting the error "EDISDEF:Port <sid> segment defn Z2Q0015000 in idoc type..YHRMD. CIM"
in sm58 of sender sap system. I thought it would be the metadata issue and tried to search the segment 'Z2Q0015000' but unable to find any thing in sender sap.
Even i have tried in idx2. in xi
Please help !!
Regards,
Suresh.

Hi Michal,
Many thanks for your input. The issue is coz the metadata in IDX2 is not updated. The sender system was trying to post the data from the segment which XI doesnt have.
I just tracked the segment from we60 based on the error message and checked the idoc structure in IDX2.Then imported the idoc into IDX2 from sender sap.
once again thanks a lot !!
Regards,
Suresh.

Questions on sending audio tracks from a short film into Audition for mastering

Ok so basically I have a 4 minute film in which i need to master the audio. I have a few quesions as to how to best go about this.
1: Some of the clips came with 2 tracks off the camera yet they are both labeled channel 1 on the beginning of the clip on the timeline. Their properties are listed as follows:
Type: Windows WAVE audio file
File Size: 16.0 MB
Source Audio Format: 48000 Hz - 24 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:00:58:09344
Why are there 2 tracks?
2: Some other audio tracks are just labeled on the timeline as L and R. Both these and the other ones labeled Ch 1 are synced with Pluraleyes from an H4N Zoom recorder so i have no clue why they are labeled different. These one have properties labeled as such:
Type: MPEG Movie
File Size: 69.5 MB
Image Size: 1920 x 1080
Frame Rate: 23.976
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:00:14:20
Pixel Aspect Ratio: 1.0 (1.0)
Yes those are audio files on the timeline.
3: What is the general scoops with these multi track audio files? Do I need both tracks?
4: What would be the best workflow to export all the audio clips into Audition and get them back in the timeline? I heard about importing then in Premiere clicking Undo so you don't have the audio track clips as "Audio Extracted" and you retain the originals, but then just replace them with the Audition audio.
Working with sound is not yet a strong point of mine, i am just a video editor but need to get a grasp on properly handling this.

Cameras although they can record stereo audio often only use a small mono gun mic mounted on the camera. The audio menus on the camera give you the option to record either the mono mic to both tracks (ie. Ch1 input to the camrea is fed to both) or as stereo tracks from a stereo mic or as split tracks with onboard mic via Ch1 to track 1 and, say, a radio mic fed via Ch2 to track 2.
Your first files sound as if they came from the first of those options from an onboard mono mic. You don't necessarily need both trakc as they are identical mono tracks in this case.
The second set of tracks were recorded as a stereo pair on the Zoom, hence L and R. They could be stereo or more likely again are double mono tracks where you will only need one of them.
However, depending on the project, it may be more convenient to keep both tracks if any stereo music or effects are going to be mixed in on the multitrack. The final edited video will probably have two tracks on it anyway even if all the audio content is mono.

Fetching SSIS error message into Audit table using SP

Hi Experts,
I want to fetch SSIS Error Info along with Task Name into Audit table 'Error_Info' column. This is nvarchar(max) datatype, i wrote below Stored Procedure for this (Column names passing dynamically in SP)
CREATE PROC [dbo].[usp_AuditErrorHandler]
@AuditTableName nvarchar(MAX)
,@Audit_Status nvarchar(100)
,@Audit_ErrorDescription sql_variant
,@Audit_PkgEnd_dttm nvarchar(100)
,@task sql_variant
,@errordescription sql_variant
,@Audit_ID nvarchar(10)
,@LogID INT
AS
BEGIN
DECLARE @STRQuery NVARCHAR(MAX)
SET @STRQuery = '
UPDATE '+@AuditTableName+'
SET '+@Audit_Status+' = ''Failed''
,'+@Audit_PkgEnd_dttm+' = GETDATE()
,'+@Audit_ErrorDescription+' = ''Task['+ @task +']:'+@errordescription +'''
WHERE ' +@Audit_ID+ ' = ' + CAST(@LogID AS NVARCHAR)
The above procedure is working fine in SSMS and inserting complete error info into table, but when i am executing thru SSIS Pkg i am getting error like
"[Execute SQL Task] Error: Executing the query "exec usp_AuditErrorHandler ?,?,?,?,?,?,?,?" failed with the following error: "Incorrect syntax near '@P1'.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not established correctly."
So, i tot of checking with string lenght and modifed the code by adding left () to @errordescription as below.
UPDATE '+@AuditTableName+'
SET '+@Audit_Status+' = ''Failed''
,'+@Audit_PkgEnd_dttm+' = GETDATE()
,'+@Audit_ErrorDescription+' = ''Task['+ @task +']:'+LEFT(@errordescription ,100)+'''
WHERE ' +@Audit_ID+ ' = ' + CAST(@LogID AS NVARCHAR)
Here, it is inserting till 119 chars, if i give more than 119 chars pkg is failing with above error.
I want to get insert Complete error info into the column.
Can anybody suggest on this??
Thanks in advance !!!

Thanks Arthur for the response, i have tried with the Sql_Variant data type also, here procedure itself not creating and throwing below error.
"The data types nvarchar(max) and sql_variant are incompatible in the add operator."
This is the procedure i am using to fetch error info into Audit table.
ALTER PROC [dbo].[usp_AuditErrorHandler]
@AuditTableName nvarchar(MAX)
,@Audit_Status nvarchar(100)
,@Audit_PkgEnd_dttm nvarchar(100)
,@Audit_Task_ErrorCode nvarchar(100)
,@Audit_ErrorDescription SQL_VARIANT
,@errorcode nvarchar(max)
,@task SQL_VARIANT
,@errordescription SQL_VARIANT
,@Audit_ID nvarchar(10)
,@LogID INT
AS
BEGIN
SET NOCOUNT ON;
DECLARE @STRQuery SQL_VARIANT
BEGIN TRY
SET @STRQuery = '
UPDATE '+@AuditTableName+'
SET '+@Audit_Status+' = ''Failed''
,'+@Audit_PkgEnd_dttm+' = GETDATE()
,'+@Audit_Task_ErrorCode+' = '''+@errorcode+'''
,'+@Audit_ErrorDescription+' = ''Task['+ @task +']:'+ @errordescription +'''
(Error is giving in this line)
WHERE ' +@Audit_ID+ ' = ' + CAST(@LogID AS NVARCHAR)
EXEC (@STRQuery)
END TRY
Below is the Audit Table Schema

Port &1 segment defn &2 in IDoc type &3 CIM type &4 do not exist

Hello,
I've a question. We would send an standard IDOC from the 4.6C System to our SAP Xi 3.0. I customized the XI with TA IDX1 and IDX2. If we trigger the IDOC to XI I get the follow error message back:
Port SAPQ73 segment defn E2EDL20002 in IDoc type DELVRY03 CIM type &4 do not exist.
The IDOC Vers. is 4.6. In another system with IDOC Vers. 6.20 isn't a problem. So I think its a problem of the IDOC Version, or? So I checked the forum about this topic but I didn't find anything. So, I hope you can help me. Kind Regards Stephan

Hello,
I have exactly the same issue... We're currently upgrading our SAP system 4.7 to ECC6.0. We're also upgraded the system to an unicode system.
Before those change, the interface between SAP and Xi worked well. Since the upgrade, those idocs don't pass any more and get the same error message than Stephan.
I've checked the authorization of the RFC user and he has SAP_ALL and SAP_NEW. Partner profile, RFC connection, port and distribution model didn't changed.
Do someone have an idea why this can appear ?
Thanks in advance.

IDoc to webservice and get the response back into another IDoc.

Hi guys
We have a scenario where we need to send an IDoc to webservice and get the response back into another IDoc.
Questions:
1. Is this scenario possible without a BPM? or do we need to use BPM (Sync-Async bridge).
2. Is there a Async to Sync bridge in BPM?
3. How do I use this bridge in my scenario and customize it?
4. If not possible, provide me the related docs using BPM for the same scenario.
Appreciate your quick response
Regards
Naidu

Hi,
this link may help u............,
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1134. [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403. [original link is broken] [original link is broken] [original link is broken]
Regards,
Azeez khan.

E1PRTOB segment lacking into AUDIT IDoc

Similar Messages

Maybe you are looking for