Import of modified/extended Idoc into XI repository

Dear all,
we have to import a modified/extended Idoc from R/3 into XI repository.
When I do that in the normal way, I get only the original Idoc structure without our additional segments.
The Idoc is SDPICK.SDPIID01 where we added additional segments.
Any help is very much appreciated.
Thanks and best regards,
Philipp

Hi,
IDX1 & IDX2 is for metadata check these links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Thanks,
Prakash

Similar Messages

How to import Custom idoc into IR?

I have a custom idoc and i need to map it with the receiver format after importing into IR . Please let me know the sequence of steps to import custom idoc into Integration repository?
I think I need to first import into IDX2 and then import into repository. Am I correct?

Hi Prateek,
thanks for the information .The normal standard idocs we import by searching the idoc eg- for importing matmas we type mat and we search it, since it is a standard idoc it will be available in the list (after selecting the chek box "Import of idoc or rfc interfaces from sap system permitted").
But my question is how we import custom idoc as they wont be present in the list?

Import of SAP Objects into Integration Repository in XI 3.0

Hi all,
I am not able to import SAP objects into the Integration Repository in XI 3.0. This option is under any Software Component Version. I have selected the radio button "Import of RFC and IDoc interfaces from SAP systems permitted", in the Software Component Version settings. After the connection data is specified for the SAP system nothing appears under the IDoc, Whereas the import of RFCs is successfull.
We also have another installation of SAP XI 3.0, here this option is working properly. Can anyone tell me what is the problem, is is there something else to be configured inorder to do this.
Best regards,
Norway

Hi Stephan
Thank you for your answer. We have followed your instructions but did only get half a success. Here is what we have done:
1) Created "External Definitions" for all related xsd-files with the same name as the xsd-filename and in our own namespace. Our namespace is different from those specified in the xsd-files. We have not change the namespaces in the xsd-files.
2) Maintained the "source"-field with the name for the xsd-file and not the url as specified in our answer. When we used the filename only we got a value the field "name" in the "External References".
3) We made a message mapping and imported the "top-level-xsd-element" from the "External Definition". This resulted in only the top level element and nothing else. What we expected was the possibility to drill down through the complete structure.
What did we doe wrong? Perhaps I could talk you into spending 10 min. and try it your self? This url leads to a zip file with all the related xsd files: http://rep.oio.dk/ubl/xml/schemas/0p71/documentation/resources.html
Do you know if it will be possible to make references across namespaces in a later version of XI?
Regards
Christian

Import extended IDOC to Integration Builder

Hi All,
I´m faced with the following situation using an Idoc with customer extension from a SAP R/3 40B System with my scenario:
IDX2 - Import works fine, basistype and extension in place
Integration Builder: Can ´t see the extension with or without the idoctype but the standardidoctype only.
Thanks for any help.
regards
Carsten

Thanx very much for your reply,
the problem actually is in detail:
I try to import the IDOC-structure into the Design of Integration Builder - what did work for some other - but non-extended IDOCs earlier.
When I start the import I can ´t find the extended IDOC in the list of downloadobjects, but the (related) non-extended standard-IDOC only.
When I import the object that is listed as being non extended it actually is.
I wondered whether the IDOC-extension or the IDOC itself might not be valid so I checked Releasestatus in R/3-Systems what looks good and tried to upload the metadata with IDX2 - it worked.

Error while Importing Metadata into DAC Repository

Hi,
After the successful first time login into DAC and creating repository, when I try to import metadata into DAC repository.
DAC > Tools > DAC Repository Management > Import
I don't see any Applications listed under "Application List"
Can anybody suggest the troubleshooting steps for this?
Regards,
Jitendra

If this is the first time that you are importing make sure that the directory you are importing from is like this -
C:\OBIEE\OracleBI\DAC\export
If this is not the first time then
Can you go inside the following directory
C:\OBIEE\OracleBI\DAC\log
and check for export.log - Look for Applications Section, if you have any application then you had exported it and you should see it under the applications tab when importing otherwise you don't !!Since its an xml file that is generated i believe you have not exported by selecting the applications yo want and that is your problem.
Hope this helps !!
Cheers,
Sid

Import of RFC objects from R/3 into XI repository

Hi All
I am trying to import RFC (Function module) from R/3 ECC6.0 into XI repository using Import of SAP objects icon. And when the username and password of my R/3 is given, it shows an error invalid username and password. But my R/3 login is working with the same uname and password. I have done partner profile, port and RFC destination settings in both R/3 and XI system. But everytime I am getting the same error in XI when importing SAP objects. Any ideas is appreciated.
Thanks
Anand

If XI is installed on Windows you can find this file in
%WINDIR%\system32\drivers\etc\services file,
In Unix this is in /etc/ with the name services
The entry you should see for example <b>sapgw<xx> 33<xx>/tcp</b>
where xx is sap gateway no.

Unable to import IDoc into IR

Hi - For no reason i can't import the IDoc into XI.
The problem seems to be that in backend system is a problem. The basis-type and the segments are all released - to me because i released and de-released them. The Idoc was developed in client 010 and i want to import ist from 011 - of course there was some kind of transport!
In WE20 of backend system i am not able to pick this IDoc for Incoming parameter, no idea why.
In XI i am able to import MetaData via IDX2 but i am still not able to import the IDoc!!
can somebody help?! br Jens

Hi,
1 Scenario
This guide deals with all the configurations required to create an IDoc adapter in Exchange Infrastructure
3.0 to send an IDoc from XI to the SAP backend system.
Unlike other types of adapters, the IDoc adapter has dependencies on the XI 3.0 ABAP configurations and
the backend SAP system configurations. Those configurations information will have to be either created
first or retrieved in order to complete the IDoc adapter configuration.
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
     The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
     The Client must be the client number of the backend SAP system.
     Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
     Double-click on the business system in the Integration Directory.
     Switch to Edit mode.
     Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
     The RFC Destination is from step 3.1.
     The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
Award point if find helpful

Unable to import IDoc into NWBPM from NWDS

Dear PO Experts,
We are migrating an existing interface
(IDoc<-->PI<-->SOAP using BPM (Multiple sync calls)).
We are un able to import IDoc into NW BPM project as a service Interface. (For BPM we exported IDoc into local system as an external definition and did few modifications to the xsd as per below blog and exported back to PO server as an external definition.Create Service Interface for the same .
http://scn.sap.com/community/process-orchestration/blog/2014/09/24/idoc-to-nw-bpm-scenario#comment-542653 )
We are getting below exception while importing IDoc Service Interface into BPM project.I have attached IDoc WSDL file for your reference.Could you please share your expertise on this issue.
>>>An internal error occurred during: "Importing MOIN models for XSDs and WSDLs...".
java.lang.OutOfMemoryError: Java heap space
at java.util.ArrayList.<init>(ArrayList.java:112)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
(XSDParticleImpl.java:1271)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
(XSDParticleImpl.java:1050)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
(XSDParticleImpl.java:1149)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
(XSDParticleImpl.java:1039)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
(XSDParticleImpl.java:1272)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
(XSDParticleImpl.java:1060)
at org.eclipse.xsd.impl.XSDParticleImpl.getDFA
(XSDParticleImpl.java:2041)
at org.eclipse.xsd.impl.XSDModelGroupImpl.validateRoot
(XSDModelGroupImpl.java:599)
at org.eclipse.xsd.impl.XSDComplexTypeDefinitionImpl.validate
(XSDComplexTypeDefinitionImpl.java:1408)
at org.eclipse.xsd.impl.XSDConcreteComponentImpl.validate
(XSDConcreteComponentImpl.java:565)
at org.eclipse.xsd.impl.XSDSchemaImpl.validate(XSDSchemaImpl.java:1653)
at com.sap.tc.esmp.tools.core.util.EMFUtils.validate(EMFUtils.java:613)
at
com.sap.tc.esmp.tools.xsd.xml.EmfSchemaImporter.calculateAffectedPartitions(EmfSchemaImporter.java:903)
at
com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.calculateAffectedPartitions(Wsdl1Importer.java:365)
at
com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.resolveImportLink(Wsdl1Importer.java:545)
at
com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.createChainLink(Wsdl1Importer.java:522)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.init
(Wsdl1Importer.java:461)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.<init>
(Wsdl1Importer.java:337)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer.prepareWsdlImport
(Wsdl1Importer.java:1381)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer.prepareWsdlImport
(Wsdl1Importer.java:1368)
at com.sap.tc.esmp.tools.facade.Import.prepareWsdlImport
(Import.java:106)
at
com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor.doImportFiles(RepositoryMetadataProcessor.java:298)
at
com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor.access$300(RepositoryMetadataProcessor.java:52)
at com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor$4.run
(RepositoryMetadataProcessor.java:248)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Regards
Venkat

Hi Venkat,
Find the below link.
http://scn.sap.com/community/process-orchestration/blog/2014/11/29/using-idocs-in-nwbpm

I have a scenario. Import IDOC into PI and PI transform IDOC to Excel. Using mail adapter attach that Excel using pi and send to customer. Can you please help me on the same?

HI Experts,
I have a scenario. Import IDOC into PI and PI transform IDOC to Excel. Using mail adapter attach that Excel using pi and send to vendor. Can you please help me on the same?
Thanks
SaiSreevastav

Hi Sai,
you can use XSLT or java mapping or adapter module to convert IDOC xml to XLS. Please refer the below blog
Convert incoming XML to Excel or Excel XML – Part 1 - XSLT Way
Convert incoming XML to Excel Sheet Part 2 – Adapter Module way
Convert incoming XML to Excel Sheet
then after converting to Excel, you can use the payloadswap bean in mail adapter
XI: Sender mail adapter - PayloadSwapBean - Step by step
regards,
Harish

How to import the IDOC into Seeburger BIC mapping designer

Hi All,
Can u please tell me how to import the IDOC into Seeburger BIC mapping desginer.
I have scenario My scenario is SAP GTS 7.0.....>Seeburger BIS.....>Atlas customs system for Germany
Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send
to Atlas systeam.
Regards,
Ramesh.

Hi Ramesh
BIC is a tool from Seeburger to transmit the XML data to EDI and EDI to XML.
Seeburger mapping programs for transferring the XML data to EDI data and EDI data to XML data, but not for the structure changing, in the IR your mapping program is same.
Receiver side you need AS2 Adapter for converting data to EDI target structure. we have many EDI versions are available, for converting the EDI to XML or vice versa AS2 gives some default mapping programs, xml to EDI or EDI to XML convertion done through this mapping programs.
Seeburger AS adapter provider provides some mapping programs(for example EDI4010 version or other), if you are using the same EDI version(4010) then you can use that mapping programs, if the version is different then we can manually generate the Seeburger X2E and E2X mappings for the corresponding version and signal(850 or 810 or ..), for this seeburger provides the mapping designer tool (BIC), there we can develope the X2E and E2X mapping programs and configure this in the Seeburger work bench.
Regards
Ramesh

How to import modified files back into Muse

Maybe this is an easy sync issue....hopefully.
I've exported my html files from Muse (after publishing to Biz Catalyst) and want to modify the html, such as ad href's to divs in the slideshow, etc. How can I import these modified html files back into Muse so I can publish back to Business Catalyst?
I realize it's an easy solution to host the exported files on another server, but I'd really like to stay within the Muse/Biz Catalyst environment with updated html's.
thanks much!!

There isn't a way at this time to import HTML files into Muse and expect it to load in Design mode for a subsequent re-publish. The only kind of editing that Muse supports today (outside of Muse) is through Business Catalyst's In-Browser editing feature but that is limited to editing only text (without any formatting or styles) and foreground images <http://www.adobekb.com/working-with-in-browser-editing_pt01.html>. Feel free to submit your feature request over at our Ideas section.
Thanks,
Vinayak

Import BPEL process into integration repository ???

Hey all,
I know that it's possible to export an integration scenario to BPEL4WS.
My first question is if it's also possible to import such a BPEL4WS process into the integration repository?
Second question: Somewhere I read that it's optional to design integration scenarios with the graphical designer. Is that true and is there another way to create such a scenario?
Thanks for your help!
Regards
Matthias

>My first question is if it's also possible to import such a BPEL4WS process into the integration repository?
Yes you can import BPEL4WS, in IR.
1. Create Integration process
2. Switch to BPEL4WS display sceen and import your BPEL.
go through the following link
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/7a7440036f6d1de10000000a1550b0/frameset.htm
>Second question: Somewhere I read that it's optional to design integration scenarios with the graphical designer. Is that true and is there another way to create such a scenario?
Aris is a tool to configure your Integration scenario other than graphical scenario.
I dont think it is available today with XI3.0.
There is lot of documentation available on ARIS with SAP.
Best regards,
Satish

Can I import a 10g MDL file into a 9.2 repository?

Good Morning/Afternoon/Evening
I started with OWB10g and created a repository. After creating several modules I realized I had an Oracle 9.2 database in which to deploy the runtime stuff.
I was unable to install the server side (AIX 5.2) binaries since I didn't have a 10g Universal Installer.
I exported the 10g repository information to an MDL file.
I dropped the 10g repository and created a 9.2 repository and also installed the 9.2 runtime components. All is cool so far.
I then wanted to import the MDL file from the 10g repository into the 9.2 repository and its then I hit the snag.
Is it possible to import a 10g MDL file into a 9.2 repository?
I was hoping the format was a standaard CWM type that would be recognized by either version but it looks like I'm incorrect.
Any other suggestions on how to get the 10g repository information into the 9.2 repository?
I still have the 10g repository on another server so I am able to do other types (?) of exports or whatever.
Many thanks for the help.
Gary

Gary,
I am puzzled by the reason "I was unable to install the server side (AIX 5.2) binaries since I didn't have a 10g Universal Installer." OWB 10g comes with its own copy of 10g Universal Installer. I am not claiming to ever install on AIX myself, but can you list the errors you get, perhaps we can troubleshoot the underlying problem, rather than working around it.
Not to dodge your question on exporting 10g MDL to 9.2. Even though this is an unsupported and untested scenario, because OWB 10g did not introduce any new objects, you can try editing the MDL as below. I don't see any risk in trying. Find the MDLRELEASE and RELEASE statements at the top (not the comments with #, they don't matter and change values back to 9.2, as in:
MDLRELEASE=9.2
RELEASE=9.2.0.2.0
And becuase OWB 9.2 does not know what Database 10g is, if you have any Database locations in your MDL that are set to 10g, change them to 9.2 as in:
[...]Oracle Database|9.2|[...]
Nikolai Rochnik

Problem about extended IDOC(urgent)

Hi experts,
i have idoctype,extended idoc,and one include.. i need modify that according to the requirement.. here i will give the idoctype and extended idoc type and include program .. please help me where exactly i need to do the change and what are the steps required for the requirement..
Exact Requirement: Modify the program which populates the idoctype invoice02 and extension zinvoice02 , if netvalue is zero(vbrp-netwr = 0) then populate the idoc segment E1EDP01.E1EDP26 , BETRG WITH QUALF = # 011' WITH ZERO VALUE. curently segment is not populated.
Please help me in this and explain the steps required for this.
idoctype:invoice02
extended idoc:zinvoice02
include:ZXEDFU02
                               Here i am giving the include program
CASE dobject-kschl.
WHEN 'ZGRI' OR 'ZGDF' OR 'ZGRN' OR 'ZGAE'.
    t_int_edidd[] = int_edidd[].
    t_xtvbdpr[] = xtvbdpr[].
    ta_xvbdkr = xvbdkr.
    CASE int_edidd-segnam.
      WHEN 'E1EDK01'.
        ta_e1edk01 = int_edidd-sdata.
        PERFORM get_shipment_data.
        PERFORM get_route_data.
        int_edidd[] = t_int_edidd[].
      WHEN 'E1EDP01'.
Update segment E1EDP01
1. Update field E1EDP01-PSTYP
2. Accumulated net weight & quantity of batch split items against
E1EDP01 segment of the main invoice item.
        ta_e1edp01 = int_edidd-sdata.
        i_tabix = sy-tabix.
        CLEAR: ta_e1edp02.                                  "DIAG01+
        PERFORM update_segment_e1edp01.
        MOVE ta_e1edp01 TO t_int_edidd-sdata.
        MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
Populate segment Z1EDP08
Fields: ZZDESPACTY_A, ZZACTYUOM
        PERFORM validate_segment USING control_record_out-idoctp
                                  control_record_out-cimtyp
                                  'Z1EDP08'
                            CHANGING n_subrc.
        CHECK n_subrc EQ 0.
        PERFORM calc_invoice_item_zzdespacty_a.             "DIAG02+
        int_edidd[] = t_int_edidd[].                        "DIAG02+
      WHEN 'E1EDP02'.                                       "DIAG01+
        IF int_edidd-sdata(3) = '016'.                      "DIAG01+
          ta_e1edp02 = int_edidd-sdata.                     "DIAG01+
        ENDIF.                                              "DIAG01+
      WHEN 'E1EDP19'.
Populate segment Z1EDL24
Fields: Material Characteristics or Material Class '001'.
        PERFORM validate_segment USING control_record_out-idoctp
                                 control_record_out-cimtyp
                                 'Z1EDL24'
                                 CHANGING n_subrc.
        IF n_subrc EQ 0.
          ta_e1edp19 = int_edidd-sdata.
          CASE ta_e1edp19-qualf.
            WHEN '002'.
              PERFORM get_mat_characteristic USING ta_e1edp19-idtnr.
              PERFORM fill_segment_z1edl24.
              int_edidd[] = t_int_edidd[].
            WHEN OTHERS.
          ENDCASE.
        ENDIF.
      WHEN 'E1EDP26'.
Populate segment E1EDP26
Fields: BETRG
        i_tabix = sy-tabix.
        ta_e1edp26 = int_edidd-sdata.
       IF ta_e1edp26-qualf = '001'. "Gross Price which is always present
          PERFORM fill_segment_e1edp26.
          int_edidd[] = t_int_edidd[].
        ENDIF.
      WHEN 'E1EDP08'.
Populate Segment Z1EDL37                                             *
Fields: Bespoke fields from Handling Unit (VEKP)
        PERFORM validate_segment USING control_record_out-idoctp
                                  control_record_out-cimtyp
                                  'Z1EDL37'
                            CHANGING n_subrc.
        CHECK n_subrc EQ 0.
        ta_e1edp08 = int_edidd-sdata.
        PERFORM fill_segment_z1edl37.
Populate Segment Z1EDP08                                             *
Fields: Total Despatch Activity                                      *
       PERFORM validate_segment USING control_record_out-idoctp
                                 control_record_out-cimtyp
                                 'Z1EDP08'
                           CHANGING n_subrc.
       CHECK n_subrc EQ 0.
       PERFORM calc_invoice_item_acty_total.
        int_edidd[] = t_int_edidd[].
      WHEN OTHERS.
    ENDCASE.
WHEN 'ZGDW'.
Line above added line below removed - Assyst 73789
WHEN 'ZGIN'.
    t_int_edidd[] = int_edidd[].
    t_xtvbdpr[] = xtvbdpr[].
    ta_xvbdkr = xvbdkr.
    CASE int_edidd-segnam.
Start SU02
      WHEN 'E1EDK01'.
        ta_e1edk01 = int_edidd-sdata.
        i_tabix = sy-tabix.
Get the conversion factor
        PERFORM modify_exchange_rate.
        MOVE ta_e1edk01 TO t_int_edidd-sdata.
        MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
        int_edidd[] = t_int_edidd[].
End SU02
*************************************************************SAM01 START
      WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
        ta_e1edp02 = int_edidd-sdata.
        CASE ta_e1edp02-qualf.
          WHEN '002'.
            PERFORM fill_segment_z1edp02.
            PERFORM append_int_edidd TABLES t_int_edidd
                                     USING 'Z1EDP02'
                                            ta_z1edp02.
            int_edidd[] = t_int_edidd[].
          WHEN OTHERS.
        ENDCASE.
***************************************************************SAM01 END
    ENDCASE.
Start of JvdM01
WHEN 'ZGII'.                                              "JvdM01
    t_int_edidd[] = int_edidd[].
    t_xtvbdpr[] = xtvbdpr[].
    ta_xvbdkr = xvbdkr.
    CASE int_edidd-segnam.
      WHEN 'E1EDK01'.
Populate segment Z1EDKSH and Z1REM_STE_CDE
Fields: Shipment Number for Invoice
        Reason code for sales order
        ta_e1edk01 = int_edidd-sdata.
        PERFORM fill_segment_z1edksh_ds.
        PERFORM append_int_edidd TABLES t_int_edidd
                                 USING 'Z1EDKSH'
                                        ta_z1edksh.
        PERFORM fill_segment_z1rem_ste_cde.
        PERFORM append_int_edidd TABLES t_int_edidd
                                 USING 'Z1REM_STE_CDE'
                                        ta_z1rem_ste_cde.
        int_edidd[] = t_int_edidd[].
      WHEN 'E1EDKA1'.
Populate segment Z1EDKA1
Fields: Customer Account Group
        ta_e1edka1 = int_edidd-sdata.
        CASE ta_e1edka1-parvw.
          WHEN 'RE'.   "Bill To Party
            PERFORM fill_segment_z1edka1.
            PERFORM append_int_edidd TABLES t_int_edidd
                                     USING 'Z1EDKA1'
                                            ta_Z1EDKA1.
            int_edidd[] = t_int_edidd[].
        ENDCASE.
      WHEN 'E1EDP01'.
Read segment E1EDP01 for use later                  "JVDM02
        ta_e1edp01 = int_edidd-sdata.
      WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
        ta_e1edp02 = int_edidd-sdata.
        CASE ta_e1edp02-qualf.
          WHEN '002'.
            PERFORM fill_segment_z1edp02.
            PERFORM append_int_edidd TABLES t_int_edidd
                                     USING 'Z1EDP02'
                                            ta_z1edp02.
            int_edidd[] = t_int_edidd[].
          WHEN OTHERS.
        ENDCASE.
      WHEN 'E1EDP19'.
Populate segment Z1EDL24 and Z1EDP01                  "JVDM02
Fields: Pack Size Activity for Material
        Total Activity for Invoice Item
        ta_e1edp19 = int_edidd-sdata.
        CASE ta_e1edp19-qualf.
          WHEN '002'.
            PERFORM fill_segm_z1edl24_and_z1edp01.
            PERFORM append_int_edidd TABLES t_int_edidd
                                     USING 'Z1EDL24'
                                            ta_z1edl24.
            PERFORM append_int_edidd TABLES t_int_edidd
                                     USING 'Z1EDP01'
                                            ta_z1edp01.
            int_edidd[] = t_int_edidd[].
          WHEN OTHERS.
        ENDCASE.
    ENDCASE.
End JvdM01
ENDCASE.
Start SU02 Code Comment for implementing IR 340
**mpc01 - start of insert
start assyst 73789
*IF dobject-kschl = 'ZGDW'."amersham invoices
**IF dobject-kschl = 'ZGIN'."amersham invoices
end assyst 73789
CASE int_edidd-segnam.
for the organisation data header
   WHEN 'E1EDK14'.
     MOVE int_edidd-sdata TO ta_e2edk14.
    where is qualifying organisation = 003 (delivering company code).
     IF ta_e2edk14-qualf = '003' AND ta_e2edk14-orgid NE space.
       SELECT SINGLE waers
         INTO t001-waers
         FROM t001
        WHERE bukrs = ta_e2edk14-orgid.
       IF sy-subrc = 0.
         t_int_edidd[] = int_edidd[].
        get the billing date for the invoice
         LOOP AT t_int_edidd WHERE segnam = 'E1EDK02'.
           MOVE t_int_edidd-sdata TO ta_e1edk02.
           IF ta_e1edk02-qualf = '009'."billing date
             w_fkdat = ta_e1edk02-datum.
             EXIT.
           ENDIF.
         ENDLOOP.
        if no invoice date use current date
         IF w_fkdat IS INITIAL.
           w_fkdat = sy-datum.
         ENDIF.
        change the general document header
         LOOP AT t_int_edidd WHERE segnam = 'E1EDK01'.
           i_tabix = sy-tabix.
           MOVE t_int_edidd-sdata TO ta_e1edk01.
          set the field to the default currency code for the company
           ta_e1edk01-hwaer = t001-waers.
          if the default value equals the idoc currency then exit
           IF t001-waers = ta_e1edk01-curcy.
             EXIT.
           ENDIF.
          get the exchange rates
           SELECT *
             INTO TABLE t_tcurr
             FROM tcurr
            WHERE kurst = 'NYB1'                 " SU01
             WHERE KURST = 'GEBU'                 " SU01
              AND fcurr = ta_e1edk01-curcy
              AND tcurr = t001-waers.
           IF sy-subrc NE 0."no values found
            error the idoc
             MESSAGE e400(vf) WITH c_exchange_rate_error
                     RAISING error_message_received.
             EXIT.
           ENDIF.
           LOOP AT t_tcurr.
            convert to date from inverted date to normal date format.
             CALL FUNCTION 'CONVERSION_EXIT_INVDT_OUTPUT'
                  EXPORTING
                       input = t_tcurr-gdatu
                  IMPORTING
                       output = w_datum.
             CONCATENATE w_datum+6(4)
                         w_datum+3(2)
                         w_datum(2)
                    INTO t_tcurr-datum.
             MODIFY t_tcurr.
           ENDLOOP.
          sort the exchange rates with the newest first.
           SORT t_tcurr BY datum DESCENDING.
          read the first value in the table ie the newest.
           LOOP AT t_tcurr WHERE datum <= w_fkdat.
             EXIT.
           ENDLOOP.
           IF sy-subrc NE 0."no values found
            error the idoc
             MESSAGE e400(vf) WITH c_exchange_rate_error
                     RAISING error_message_received.
             EXIT.
           ENDIF.
Start SU01
Get the Exchange rate from the function module and populate
E1EDK01 TABLE
           w_fcurr = ta_e1edk01-curcy.
           call function 'CONVERT_TO_LOCAL_CURRENCY'
                exporting
                     date             = w_fkdat
                     foreign_amount   = '0'
                     foreign_currency = w_fcurr
                     local_currency   = t001-waers
                     type_of_rate     = 'GEBU'
                importing
                     exchange_rate    = t_tcurr-ukurs
                exceptions
                     no_rate_found    = 1
                     overflow         = 2
                     no_factors_found = 3
                     no_spread_found = 4
                     derived_2_times = 5
                     others           = 6.
End SU01
           ta_e1edk01-wkurs = t_tcurr-ukurs.
          change the header data in segment
           MOVE ta_e1edk01 TO t_int_edidd-sdata.
          update the current idoc segment
           MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
           EXIT.
         ENDLOOP.
        update all of the idoc segments
         int_edidd[] = t_int_edidd[].
       ENDIF.
     ENDIF.
ENDCASE.
*ENDIF.
**mpc01 - end of insert
End SU02 Code Comment for implementing IR 340

Hi Venu,
Try with this code.
If vbrp-netwr = 0.
<b> WHEN 'E1EDP26.
CASE ta_e1edp26-qualf.
ta_e1edp26 = int_edidd-sdata.
WHEN '011'.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'e1edp26'
ta_e1edp26.
int_edidd[] = t_int_edidd[].
ENDCASE.</b>
ENDIF.
Thanks
Manju.

Merging multiple idocs into 1 XML output

Hi Gurus,
I've got a scenario whereby i will need to send payment documents via idocs to XI and XI will output them into an XML file.
At the moment, when i perform a payment run for multiple vendors and send the idocs out, i realised that multiple idocs are being sent out and XI will output multiple XML docs.
Is there any way i can merged these idocs into a single XML document? The idocs are all from the same system.
Thanks in advance.

HI,
I think this is possible using PACKAGING.
Check this note 814393 on Service Market Place.
You want to create or process an XI message with multiple instances of an IDoc (of the same IDoc or extension type) in the mapping.
Please refer below link to follow the steps to Merge IDOCs under single XML,
SAP Network Blog: Collecting IDocs without using BPM
Collecting IDocs without using BPM
IDoc packaging
Reason and Prerequisites
The relevant IDoc is imported into the Integration Repository.
Solution
1) Log on to the Integration Repository.
2) Open the relevant IDoc in the object editor.
3) Select the "Export XSD" menu option in the "Tools" menu.
4) In the subsequent dialog box, assign a file name and save the data to the hard disk of your local PC.
5) Open the file that you have saved in step 4 in an adequate editor (for example, Notepad) for editing.
6) Locate the first entry: <xsd:element name="IDOC" type="<
Idocname>"> and add the following expression, maxOccurs="unbounded", between the value of the type attribute and the closing angular bracket.
Example:
<xsd:element name="IDOC" type="ADR2MAS.ADR2MAS02"
maxOccurs="unbounded">
7) Save the modified file to the hard disk of your local PC.
8) In the message mapping, use the file saved in step 7 instead of the imported IDoc by using the "Import XML or XSD" function in the mapping tool to select the source or target messages.
Thnaks
swarup

Import of modified/extended Idoc into XI repository

Similar Messages

Maybe you are looking for