Help to read the complete basic idoc structure

Hi,
I have the following Basic Idoc structure
1. /DSD/HH_CONTROL01- Control data for hand held interface.
1.1 /DSD/HH_E1CTHD01- Control data header.
1.1.1 /DSD/HH_E1CTAD02- Control idoc- Application data header
1.1.1.1 /DSD/HH_E1CTID03- Control idoc- Application data item
1.1.1.2 /E1WXX01- Segment for customer enhancement to be used as requirement.     
OBSERVATION----
1. The basic idoc (1) is found in table EDBAS and description in EDBAST.
2. The segments (1.1.1.2) are in table EDISEGMENT and EDISEGT.
3. All the other structures (1.1), (1.1.1), (1.1.1.1) are found in tables EDISDEF and some in EDISEGMENT.
QUESTIONS----
1.What query can I write to get the above basic idoc structure?
2.How are the relationships mapped among the tables?
Thank you, points will be awarded for your time and answers.

REPORT  ZPGM_BASIC_IDOC_IMPRT_TO_PCNTR.
TABLES: EDBAS, " Basic types
        IDOCSYN. " Syntax Description for Basic Types
DATA: BEGIN OF ITAB OCCURS 0.
        INCLUDE STRUCTURE IDOCSYN.
DATA: END OF ITAB.
SELECT A~IDOCTYP " Basic type
       B~NR      " Sequential Number of Segment in IDoc Type
       B~SEGTYP  " Segment type
       B~PARSEG  " Name of parent segment
       B~PARPNO  " Sequential number of parent segment
       B~PARFLG  " Flag for parent segment: Segment is start of segment
                                                             "  group
       B~MUSTFL  " Flag: Mandatory entry
       B~OCCMIN  " Minimum number of segments in sequence
       B~OCCMAX  " Maximum number of segments in sequence
       B~HLEVEL  " Hierarchy level of IDoc type segment
       INTO TABLE ITAB
       FROM EDBAS AS A INNER JOIN
            IDOCSYN AS B
        ON AIDOCTYP EQ BIDOCTYP.
SORT ITAB BY IDOCTYP NR." Sort the idoctype and according the segment "
                        "number for the right order in the basic idoc
                        "syntax.
LOOP AT ITAB.
  AT NEW IDOCTYP.
      WRITE:/ '***********'.
      WRITE:/1 ITAB-IDOCTYP.
  ENDAT.
     WRITE:/.
     SY-COLNO = 5 + ( ITAB-PARPNO * 2 ). " this displays the segments
                                         "under the respective parent
                                         "segments.
     WRITE AT SY-COLNO ITAB-SEGTYP.
ENDLOOP.
Thank you.

Similar Messages

  • Basic IDOC Structure Enhancement

    My requirement is to add a new segment to the basic IDOC structure
    I have tried this using a <b>Z</b> type IDOC with reference to the basic type then i am getting an error saying that clipboard is empty.
    Please help me to solve this.
    <b>Thanq</b>

    My requirement is to add a new segment to the basic IDOC structure
    I have tried this using a <b>Z</b> type IDOC with reference to the basic type then i am getting an error saying that clipboard is empty.
    Please help me to solve this.
    <b>Thanq</b>

  • How can I read the complete text I see in spotlight?

    Hey just here to ask a quick question. I just noticed that I can still see messages that i deleted (or so I thought) on spotlight. Now, I would like to know how I can see the complete message. On spotlight you can only see a few words of the text but I would like to read the complete message if possible. I don't sync my phone at all but I do have the icloud on. I tried restoring my phone but I don't have any space left on it. Also, the details show that my phone was last backed up on March or so, does that mean I can view all the deleted messages since March or only the messages I deleted before March?? Please help. Hope I'm very clear and understandable.
    Thanks.
    Luis V.

    Do you happen to know if there is any other way I can view the complete message with outside sources (apps, programs, etc.)? Thanks for the help.

  • How to read the complete path in file upload UI

    Hi,
    I want to know how to read the complete path in file upload UI in java web dynpro.
    I have created 1 file upload UI and than when i do browse and select some file say small.jpg from my local PC, desktop , its path is coming in file upload UI like E:\small.jpg,
    I want to know how to get this path in java webdynpro code.
    please let me know..

    Hi Satyam,
    In webdynpro java, first file stores in server location then it reads from server.
    Create a button with upload and write this code OnAction
    Resource is the attribute name in context of type com.sap.ide.webdynpro.uielementdefinitions.Resource, this attribute is for Resource property for Upload UI Element.
    Then in OnAction of button
    InputStream text = null;
           int temp=0;
           try{
                File file = new File(wdContext.currentContextElement().getResource().getResourceName().toString());
               String path = file.getAbsolutePath();
                wdComponentAPI.getMessageManager().reportSuccess(path);
           }catch(Exception e){
                e.printStackTrace();
        //@@end
    Regards,
    Pradeep
    Edited by: pradeep_546 on May 11, 2011 12:22 PM

  • Need help to read the item details while creating the Opportunity in SAP CR

    Hi,
    I need to read the values entered at item level while creating a new opportunity in SAP CRM 5.0.
    Is there any function modle to do that ? I need to read the custom fields (developed by EEWB)
    and sum  them up and populate at the header level.
    As the data is not saved yet, I cannot read from database in the present scenario.
    Thanks and regards

    Hi,
      U can use CRM_ORDER_READ.
    1) Pass the values for the ITEM guid which u want to read.
    2) ignore the other header guid and object id because it is for whole contract
    3) if u had custmize any table it will be available in the internal table returned by the function module.
    4) u have to identify which internal table will contain the field since many internal table are available with similar meaning.
    4) CRM_ORDER_ORDER is heavy function module it reads entire contract hence u need to specify which internal table u have to read any only those values will be read. for that u have to fill in <b>it_requested_objects</b>
    fill requested ogject with below statement
    INSERT gc_object_name-orderadm_h  INTO TABLE lit_import_tab.
    gc_object_name is constant structure u have to include
    *-Standard Include
      INCLUDE crm_object_names_con.
    Mark helpfull answers
    Regards
    Manoj

  • Urgent, Archiving in the completely new folder structure

    Hello!
    I'd like to create some kind of archiving facility for the users, so that when a file or document is deleted it is tranferred to another structure inside IFS where it resides until finaly deleted - purged. Now, the problem that i have is how to re-create the top-down folder structure in the "archive"? Which classes should I use?
    Any suggestions?
    nenad

    users would like to use the versioning for the other purposes.
    The idea behind archiving is to have old, outdated ans similar documents available for the additional short period of time when users might decide to re-date them, un-delete them or do some similar action....
    nenad
    null

  • Please help to read the XML document with XMLTable

    Hi Gurus,
    I am not very familiar with XML parsing. It seems to me it should be very easy to get the data. For some reason, I am having a problem to get the data.
    SELECT *
    FROM util.hlsr_online_entries e,
    XMLTABLE(
      xmlnamespaces(
       'http://tempuri.org/'    as "dt",
       'urn:schemas-microsoft-com:xml-diffgram-v1' as "dg"),
      '/DataTable/dg:diffgram/DocumentElement/JrShowCustomerHeifers'
      PASSING XMLTYPE(e.entry_data)
      COLUMNS
      SeqNo  FOR ORDINALITY,
      DocumentID NUMBER  PATH 'DocumentID',
      ClubName VARCHAR2(100) PATH 'ClubName') as test
    WHERE e.ref_id = 33422
    The above query does not bring any data for me. My hunts is the problem with DocumentElement tab. I have been trying a different variation to handle.
    Please help me out to tune the query
    I have the following XML document from the DotNet developer
    <?xml version="1.0" encoding="utf-8"?>
    <DataTable xmlns="http://tempuri.org/">
      <xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
        <xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:MainDataTable="JrShowCustomerHeifers" msdata:UseCurrentLocale="true">
          <xs:complexType>
            <xs:choice minOccurs="0" maxOccurs="unbounded">
              <xs:element name="JrShowCustomerHeifers">
                <xs:complexType>
                  <xs:sequence>
                    <xs:element name="DocumentID" type="xs:int" minOccurs="0" />
                    <xs:element name="ClubName" type="xs:string" minOccurs="0" />
                    <xs:element name="LastName" type="xs:string" minOccurs="0" />
                    <xs:element name="FirstName" type="xs:string" minOccurs="0" />
                    <xs:element name="PreferredName" type="xs:string" minOccurs="0" />
                    <xs:element name="Email" type="xs:string" minOccurs="0" />
                    <xs:element name="Exhibitor" type="xs:string" minOccurs="0" />
                    <xs:element name="AnimalName" type="xs:string" minOccurs="0" />
                    <xs:element name="RegistryNo" type="xs:string" minOccurs="0" />
                    <xs:element name="DateofBirth" type="xs:string" minOccurs="0" />
                    <xs:element name="NameofSire" type="xs:string" minOccurs="0" />
                    <xs:element name="SireRegistryNo" type="xs:string" minOccurs="0" />
                    <xs:element name="NameofDam" type="xs:string" minOccurs="0" />
                    <xs:element name="DamRegistryNo" type="xs:string" minOccurs="0" />
                    <xs:element name="Tattoo" type="xs:string" minOccurs="0" />
                    <xs:element name="SecondaryTattoo" type="xs:string" minOccurs="0" />
                    <xs:element name="UniversalIDNumber" type="xs:string" minOccurs="0" />
                    <xs:element name="Tattoo_Location" type="xs:string" minOccurs="0" />
                    <xs:element name="Secondary_Tattoo_Location" type="xs:string" minOccurs="0" />
                    <xs:element name="OracleBreedID" type="xs:int" minOccurs="0" />
                    <xs:element name="JrValidationBreedName" type="xs:string" minOccurs="0" />
                    <xs:element name="ValidationDate" type="xs:dateTime" minOccurs="0" />
                    <xs:element name="ValidatedBy" type="xs:string" minOccurs="0" />
                    <xs:element name="ValidationComment" type="xs:string" minOccurs="0" />
                  </xs:sequence>
                </xs:complexType>
              </xs:element>
            </xs:choice>
          </xs:complexType>
        </xs:element>
      </xs:schema>
      <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
        <DocumentElement xmlns="">
          <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers1" msdata:rowOrder="0">
            <DocumentID>18442</DocumentID>
            <ClubName>Perrin FFA</ClubName>
            <LastName>Hamman</LastName>
            <FirstName>Kaily</FirstName>
            <Email>[email protected]</Email>
            <Exhibitor>Hamman, Kaily</Exhibitor>
            <AnimalName>113</AnimalName>
            <RegistryNo>C1026447</RegistryNo>
            <DateofBirth>01/14/2013</DateofBirth>
            <NameofSire>808 GAME DAY 808 LH</NameofSire>
            <SireRegistryNo>C961101</SireRegistryNo>
            <NameofDam>SADDIE 7/7 LE</NameofDam>
            <DamRegistryNo>C941067</DamRegistryNo>
            <Tattoo>113</Tattoo>
            <SecondaryTattoo />
            <UniversalIDNumber>1194F020</UniversalIDNumber>
            <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
            <Secondary_Tattoo_Location />
            <OracleBreedID>6383</OracleBreedID>
            <JrValidationBreedName>Beefmaster</JrValidationBreedName>
            <ValidationDate>2014-11-25T08:39:00-06:00</ValidationDate>
            <ValidatedBy>laineyb</ValidatedBy>
            <ValidationComment />
          </JrShowCustomerHeifers>
          <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers2" msdata:rowOrder="1">
            <DocumentID>18473</DocumentID>
            <ClubName>Perrin FFA</ClubName>
            <LastName>Hamman</LastName>
            <FirstName>Kaily</FirstName>
            <Email>[email protected]</Email>
            <Exhibitor>Hamman, Kaily</Exhibitor>
            <AnimalName>KPH PURPLE CORALEE 349</AnimalName>
            <RegistryNo>P43461953</RegistryNo>
            <DateofBirth>11/04/2013</DateofBirth>
            <NameofSire>PURPLE MOXY 22X ET</NameofSire>
            <SireRegistryNo>P43126458</SireRegistryNo>
            <NameofDam>TCC CORKY 6603</NameofDam>
            <DamRegistryNo>P42457119</DamRegistryNo>
            <Tattoo>349</Tattoo>
            <SecondaryTattoo>KPH</SecondaryTattoo>
            <UniversalIDNumber>1194F021</UniversalIDNumber>
            <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
            <Secondary_Tattoo_Location>TATTOO - Right Ear</Secondary_Tattoo_Location>
            <OracleBreedID>6389</OracleBreedID>
            <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
            <ValidationDate>2014-12-01T11:55:00-06:00</ValidationDate>
            <ValidatedBy>Hannah</ValidatedBy>
            <ValidationComment />
          </JrShowCustomerHeifers>
          <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers3" msdata:rowOrder="2">
            <DocumentID>18474</DocumentID>
            <ClubName>Perrin FFA</ClubName>
            <LastName>Hamman</LastName>
            <FirstName>Kaily</FirstName>
            <Email>[email protected]</Email>
            <Exhibitor>Hamman, Kaily</Exhibitor>
            <AnimalName>LANGFORDS SWEET N SOUR 4107</AnimalName>
            <RegistryNo>43504761</RegistryNo>
            <DateofBirth>03/02/2014</DateofBirth>
            <NameofSire>LH TNT 1017</NameofSire>
            <SireRegistryNo>43199794</SireRegistryNo>
            <NameofDam>LANGFORDS LADY 2206 ET</NameofDam>
            <DamRegistryNo>43315143</DamRegistryNo>
            <Tattoo>4107</Tattoo>
            <SecondaryTattoo />
            <UniversalIDNumber>1194F018</UniversalIDNumber>
            <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
            <Secondary_Tattoo_Location />
            <OracleBreedID>6398</OracleBreedID>
            <JrValidationBreedName>Hereford</JrValidationBreedName>
            <ValidationDate>2014-11-24T14:26:00-06:00</ValidationDate>
            <ValidatedBy>Validator</ValidatedBy>
            <ValidationComment />
          </JrShowCustomerHeifers>
          <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers4" msdata:rowOrder="3">
            <DocumentID>18475</DocumentID>
            <ClubName>Perrin FFA</ClubName>
            <LastName>Hamman</LastName>
            <FirstName>Kaily</FirstName>
            <Email>[email protected]</Email>
            <Exhibitor>Hamman, Kaily</Exhibitor>
            <AnimalName>PURPLE CCC LYDIA 19A</AnimalName>
            <RegistryNo>P43406978</RegistryNo>
            <DateofBirth>02/05/2013</DateofBirth>
            <NameofSire>PURPLE MB WOMANIZER 14UET</NameofSire>
            <SireRegistryNo>P42945146</SireRegistryNo>
            <NameofDam>PURPLE CMCC NASTIA 9U</NameofDam>
            <DamRegistryNo>P42927201</DamRegistryNo>
            <Tattoo>19A</Tattoo>
            <SecondaryTattoo />
            <UniversalIDNumber>1194F017</UniversalIDNumber>
            <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
            <Secondary_Tattoo_Location />
            <OracleBreedID>6389</OracleBreedID>
            <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
            <ValidationDate>2014-12-01T11:55:00-06:00</ValidationDate>
            <ValidatedBy>Hannah</ValidatedBy>
            <ValidationComment />
          </JrShowCustomerHeifers>
          <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers5" msdata:rowOrder="4">
            <DocumentID>18477</DocumentID>
            <ClubName>Perrin FFA</ClubName>
            <LastName>Hamman</LastName>
            <FirstName>Kaily</FirstName>
            <Email>[email protected]</Email>
            <Exhibitor>Hamman, Kaily</Exhibitor>
            <AnimalName>PURPLE SGW EDEN 12B</AnimalName>
            <RegistryNo>P43521932</RegistryNo>
            <DateofBirth>04/02/2014</DateofBirth>
            <NameofSire>RST TIME'S A WASTIN' 0124</NameofSire>
            <SireRegistryNo>43123163</SireRegistryNo>
            <NameofDam>PURPLE SM WONDER WOMAN 160Y</NameofDam>
            <DamRegistryNo>P43235169</DamRegistryNo>
            <Tattoo>12B</Tattoo>
            <SecondaryTattoo>12B</SecondaryTattoo>
            <UniversalIDNumber>1194F015</UniversalIDNumber>
            <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
            <Secondary_Tattoo_Location>TATTOO - Right Ear</Secondary_Tattoo_Location>
            <OracleBreedID>6389</OracleBreedID>
            <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
            <ValidationDate>2014-12-01T11:56:00-06:00</ValidationDate>
            <ValidatedBy>Hannah</ValidatedBy>
            <ValidationComment />
          </JrShowCustomerHeifers>
        </DocumentElement>
      </diffgr:diffgram>
    </DataTable>

    Hi odie_63,
    Good evening. I am not sure what you are suggesting. Please provide me the example how to solve the problem. I am very new to XML parsing.
    In the meantime, I am having another problem to get the data because .net developer changes the webservice format. To me it is supposed to work fine. May be my eyes are getting blurred so, I can't see where I am wrong.
    Thanks in advance. Please help me out.
    SELECT exh.docid,exh.clubname,exh.lname,exh.fname,exh.exhibitor,exh.animalname
    FROM util.hlsr_online_entries e,
    XMLTABLE(
      xmlnamespaces(
       'http://webservices.hlsr.net/JrShowOracleService/' as "dt",
       'urn:schemas-microsoft-com:xml-diffgram-v1'  as "dg"),
      '/dt:GetJrShowCustomerHeifersResponse/GetJrShowCustomerHeifersResult/dg:diffgram/DocumentElement/JrShowCustomerHeifers'
      PASSING XMLTYPE(e.entry_data)
      COLUMNS
      SeqNo  FOR ORDINALITY,
      DocID  NUMBER  PATH 'DocumentID',
      ClubName VARCHAR2(100) PATH 'ClubName',
      LName  VARCHAR2(100) PATH 'LastName',
      FName  VARCHAR2(100) PATH 'FirstName',
      Email  VARCHAR2(100) PATH 'Email',
      Exhibitor VARCHAR2(100) PATH 'Exhibitor',
      AnimalName VARCHAR2(100) PATH 'AnimalName', 
      RegNo  VARCHAR2(100) PATH 'RegistryNo',
      DOB  VARCHAR2(100) PATH 'DateofBirth',
      SireName VARCHAR2(100) PATH 'NameofSire',
      SireRegNo VARCHAR2(100) PATH 'SireRegistryNo',
      Dam  VARCHAR2(100) PATH 'NameofDam',
      DamRegNo VARCHAR2(100) PATH 'DamRegistryNo',
      Tattoo  VARCHAR2(100) PATH 'Tattoo',
      SecTattoo VARCHAR2(100) PATH 'SecondaryTattoo',
      UnivIDNum VARCHAR2(100) PATH 'UniversalIDNumber',
      TattooLoc VARCHAR2(100) PATH 'Tattoo_Location',
      OraBreedID NUMBER  PATH 'OracleBreedID',
      Breed  VARCHAR2(100) PATH 'JrValidationBreedName',
      ValDate  VARCHAR2(100) PATH 'ValidationDate'
      ) as exh
    WHERE e.ref_id = 33432
    <GetJrShowCustomerHeifersResponse xmlns="http://webservices.hlsr.net/JrShowOracleService/">
      <GetJrShowCustomerHeifersResult>
        <xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
          <xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:MainDataTable="JrShowCustomerHeifers" msdata:UseCurrentLocale="true">
            <xs:complexType>
              <xs:choice minOccurs="0" maxOccurs="unbounded">
                <xs:element name="JrShowCustomerHeifers">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="DocumentID" type="xs:int" minOccurs="0"/>
                      <xs:element name="ClubName" type="xs:string" minOccurs="0"/>
                      <xs:element name="LastName" type="xs:string" minOccurs="0"/>
                      <xs:element name="FirstName" type="xs:string" minOccurs="0"/>
                      <xs:element name="PreferredName" type="xs:string" minOccurs="0"/>
                      <xs:element name="Email" type="xs:string" minOccurs="0"/>
                      <xs:element name="Exhibitor" type="xs:string" minOccurs="0"/>
                      <xs:element name="AnimalName" type="xs:string" minOccurs="0"/>
                      <xs:element name="RegistryNo" type="xs:string" minOccurs="0"/>
                      <xs:element name="DateofBirth" type="xs:string" minOccurs="0"/>
                      <xs:element name="NameofSire" type="xs:string" minOccurs="0"/>
                      <xs:element name="SireRegistryNo" type="xs:string" minOccurs="0"/>
                      <xs:element name="NameofDam" type="xs:string" minOccurs="0"/>
                      <xs:element name="DamRegistryNo" type="xs:string" minOccurs="0"/>
                      <xs:element name="Tattoo" type="xs:string" minOccurs="0"/>
                      <xs:element name="SecondaryTattoo" type="xs:string" minOccurs="0"/>
                      <xs:element name="UniversalIDNumber" type="xs:string" minOccurs="0"/>
                      <xs:element name="Tattoo_Location" type="xs:string" minOccurs="0"/>
                      <xs:element name="Secondary_Tattoo_Location" type="xs:string" minOccurs="0"/>
                      <xs:element name="OracleBreedID" type="xs:int" minOccurs="0"/>
                      <xs:element name="JrValidationBreedName" type="xs:string" minOccurs="0"/>
                      <xs:element name="ValidationDate" type="xs:string" minOccurs="0"/>
                      <xs:element name="ValidatedBy" type="xs:string" minOccurs="0"/>
                      <xs:element name="ValidationComment" type="xs:string" minOccurs="0"/>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
              </xs:choice>
            </xs:complexType>
          </xs:element>
        </xs:schema>
        <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
          <DocumentElement xmlns="">
            <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers1" msdata:rowOrder="0">
              <DocumentID>18442</DocumentID>
              <ClubName>Perrin FFA</ClubName>
              <LastName>Hamman</LastName>
              <FirstName>Kaily</FirstName>
              <Email>[email protected]</Email>
              <Exhibitor>Hamman, Kaily</Exhibitor>
              <AnimalName>113</AnimalName>
              <RegistryNo>C1026447</RegistryNo>
              <DateofBirth>01/14/2013</DateofBirth>
              <NameofSire>808 GAME DAY 808 LH</NameofSire>
              <SireRegistryNo>C961101</SireRegistryNo>
              <NameofDam>SADDIE 7/7 LE</NameofDam>
              <DamRegistryNo>C941067</DamRegistryNo>
              <Tattoo>113</Tattoo>
              <SecondaryTattoo/>
              <UniversalIDNumber>1194F020</UniversalIDNumber>
              <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
              <Secondary_Tattoo_Location/>
              <OracleBreedID>6383</OracleBreedID>
              <JrValidationBreedName>Beefmaster</JrValidationBreedName>
              <ValidationDate>11/25/2014</ValidationDate>
              <ValidatedBy>laineyb</ValidatedBy>
              <ValidationComment/>
            </JrShowCustomerHeifers>
            <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers2" msdata:rowOrder="1">
              <DocumentID>18473</DocumentID>
              <ClubName>Perrin FFA</ClubName>
              <LastName>Hamman</LastName>
              <FirstName>Kaily</FirstName>
              <Email>[email protected]</Email>
              <Exhibitor>Hamman, Kaily</Exhibitor>
              <AnimalName>KPH PURPLE CORALEE 349</AnimalName>
              <RegistryNo>P43461953</RegistryNo>
              <DateofBirth>11/04/2013</DateofBirth>
              <NameofSire>PURPLE MOXY 22X ET</NameofSire>
              <SireRegistryNo>P43126458</SireRegistryNo>
              <NameofDam>TCC CORKY 6603</NameofDam>
              <DamRegistryNo>P42457119</DamRegistryNo>
              <Tattoo>349</Tattoo>
              <SecondaryTattoo>KPH</SecondaryTattoo>
              <UniversalIDNumber>1194F021</UniversalIDNumber>
              <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
              <Secondary_Tattoo_Location>TATTOO - Right Ear</Secondary_Tattoo_Location>
              <OracleBreedID>6389</OracleBreedID>
              <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
              <ValidationDate>12/01/2014</ValidationDate>
              <ValidatedBy>Hannah</ValidatedBy>
              <ValidationComment/>
            </JrShowCustomerHeifers>
            <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers3" msdata:rowOrder="2">
              <DocumentID>18474</DocumentID>
              <ClubName>Perrin FFA</ClubName>
              <LastName>Hamman</LastName>
              <FirstName>Kaily</FirstName>
              <Email>[email protected]</Email>
              <Exhibitor>Hamman, Kaily</Exhibitor>
              <AnimalName>LANGFORDS SWEET N SOUR 4107</AnimalName>
              <RegistryNo>43504761</RegistryNo>
              <DateofBirth>03/02/2014</DateofBirth>
              <NameofSire>LH TNT 1017</NameofSire>
              <SireRegistryNo>43199794</SireRegistryNo>
              <NameofDam>LANGFORDS LADY 2206 ET</NameofDam>
              <DamRegistryNo>43315143</DamRegistryNo>
              <Tattoo>4107</Tattoo>
              <SecondaryTattoo/>
              <UniversalIDNumber>1194F018</UniversalIDNumber>
              <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
              <Secondary_Tattoo_Location/>
              <OracleBreedID>6398</OracleBreedID>
              <JrValidationBreedName>Hereford</JrValidationBreedName>
              <ValidationDate>11/24/2014</ValidationDate>
              <ValidatedBy>Validator</ValidatedBy>
              <ValidationComment/>
            </JrShowCustomerHeifers>
            <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers4" msdata:rowOrder="3">
              <DocumentID>18475</DocumentID>
              <ClubName>Perrin FFA</ClubName>
              <LastName>Hamman</LastName>
              <FirstName>Kaily</FirstName>
              <Email>[email protected]</Email>
              <Exhibitor>Hamman, Kaily</Exhibitor>
              <AnimalName>PURPLE CCC LYDIA 19A</AnimalName>
              <RegistryNo>P43406978</RegistryNo>
              <DateofBirth>02/05/2013</DateofBirth>
              <NameofSire>PURPLE MB WOMANIZER 14UET</NameofSire>
              <SireRegistryNo>P42945146</SireRegistryNo>
              <NameofDam>PURPLE CMCC NASTIA 9U</NameofDam>
              <DamRegistryNo>P42927201</DamRegistryNo>
              <Tattoo>19A</Tattoo>
              <SecondaryTattoo/>
              <UniversalIDNumber>1194F017</UniversalIDNumber>
              <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
              <Secondary_Tattoo_Location/>
              <OracleBreedID>6389</OracleBreedID>
              <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
              <ValidationDate>12/01/2014</ValidationDate>
              <ValidatedBy>Hannah</ValidatedBy>
              <ValidationComment/>
            </JrShowCustomerHeifers>
            <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers5" msdata:rowOrder="4">
              <DocumentID>18477</DocumentID>
              <ClubName>Perrin FFA</ClubName>
              <LastName>Hamman</LastName>
              <FirstName>Kaily</FirstName>
              <Email>[email protected]</Email>
              <Exhibitor>Hamman, Kaily</Exhibitor>
              <AnimalName>PURPLE SGW EDEN 12B</AnimalName>
              <RegistryNo>P43521932</RegistryNo>
              <DateofBirth>04/02/2014</DateofBirth>
              <NameofSire>RST TIME&apos;S A WASTIN&apos; 0124</NameofSire>
              <SireRegistryNo>43123163</SireRegistryNo>
              <NameofDam>PURPLE SM WONDER WOMAN 160Y</NameofDam>
              <DamRegistryNo>P43235169</DamRegistryNo>
              <Tattoo>12B</Tattoo>
              <SecondaryTattoo>12B</SecondaryTattoo>
              <UniversalIDNumber>1194F015</UniversalIDNumber>
              <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
              <Secondary_Tattoo_Location>TATTOO - Right Ear</Secondary_Tattoo_Location>
              <OracleBreedID>6389</OracleBreedID>
              <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
              <ValidationDate>12/01/2014</ValidationDate>
              <ValidatedBy>Hannah</ValidatedBy>
              <ValidationComment/>
            </JrShowCustomerHeifers>
          </DocumentElement>
        </diffgr:diffgram>
      </GetJrShowCustomerHeifersResult>
    </GetJrShowCustomerHeifersResponse>
    Thanks again.

  • Help by reading the pdf files

    I have follow problem. I use the pdftohtml project(using xpdf 3.02) to convert pdf files into html.
    i have problems in reading some files. When the pdf is writtend in some non-standart font using russian charters the conversion into Unicode fails. Maybe some body know how to solve this problem.
    Or you can propose some better converter.

    On Android OS 4.1 - 4.3 (Jelly Bean) or older, Adobe Reader for Android version 11.2.x has a known defect in the "All PDFs" view. The All PDFs view does not show the files and folders on an external SD card. A workaround is to use the Folder View instead of the All PDFs view. We have fixed the defect and plan to include the fix in the next release of Reader for Android.
    On Android OS 4.4 (KitKat) only, neither All PDFs view nor Folder View shows any files or folders on an external SD card.  Reader cannot save any changes to the files on an external SD card, either.  We are still working on fixing the problems.  In the meantime, please copy the files from your external SD card to your device's internal storage (e.g. /storage/emulated/0/Documents/...) using a File Manager/Browser app or use a cloud storage service (Acrobat.com, Dropbox, Google Drive, etc.) to store files.  Sorry for the inconvenience.

  • Get Idoc structure and contents from Shipment Number

    Hi all,
    We have a 3rd Party Logistics company who wants to send us back minimal shipment data to enable us to update our shipment details.  They want to send us the shipment number, and vehicle information.  My tests (and SAP's documentation) have indicated that in order to modify a shipment via the message type SHPADV, you need to have the complete Shipment Idoc structure filled in in order for the idoc to process successfully.
    My client has indicated that they want to use IDoc processing to manage the shipment updates.
    Does anyone know of a FM that can be used to fill the shipment Idoc structures if only a shipment number is filled in?  Or do the structures have to be modified manually?  For example, these is a function called 'IDOC_READ_COMPLETELY' which populates all the segment details if an Idoc number is entered.  I want something similar, but for a document number, in this instance, a shipment number. 
    Cheers,
    Steve

    Roger,
    Thanks for this suggestion.  I chose to go down another path which I put up here for those who have this problem in the future.
    I have passed the shipment number and just the fields that require modification into user exit EXIT_SAPLV55K_020, and recorded the passed in values into variables.
    I then executed the <b>idoc_output_shpmnt</b> idoc, which, when the shipment number is passed in to the nast-objky field, reads the required shipment data and populates the idoc_data table with the segment details as per sending the document out.  But the FM doesn't actually call the ALE layer, so I then loop through the idoc_data table, modifying the fields that need to change with the values I've saved in the variables, and passed the modified idoc_data tables back into the <b>idoc_input_shpmnt</b> FM.  Worked a treat.
    Cheers,
    Steve

  • Basic IDOC Segment Enhancement

    My requirement is to add a new segment to the basic IDOC structure
    I have tried this using a <b>Z</b> type IDOC with reference to the basic type then i am getting an error saying that clipboard is empty.
    Please help me to solve this.
    <b>Thanq</b>

    Dear Srikanth,
    Extending a Basic Type
    Prerequisites
    You must have completed the required steps in Extending an IDoc Type .
    It can occur that you want to fill table fields which already have an equivalent in the basic type but which are not supplied in the standard system. You therefore do not need to extend the basic type, but rather only the function module that supplies the application fields. In this case, skip the procedure.
    Procedure
    1. Choose SAP menu --> Tools --> IDoc Interface/ALE --> Development --> IDoc --> Generate ALE Interface --> IDoc Types (WE30). The IDoc type editor is displayed.
    2. If you have not already done so, create a transport request for your development objects (extension segments, extension, function exit and so on). You can access the Workbench Organizer from the editor by selecting Requests (Organizer). From there, select Request ® Create and reply to the questions which appear on screen. By selecting you can return to the IDoc type editor.
    3. Name your extension in accordance with the customer namespace and choose Extension as the development object. Choose .
    The name of your extension should be no more than 8 characters if you wish to use the extension to communicate with partners who are using SAP Releases prior to 4.0. You can only use extension names with more than 8 characters from Release 4.0 onwards.
    4. Choose one of the following options:
    Create New: Create the extension without a reference.
    · Create copy,which you can then change if necessary
    · Create as successor: Note that only one successor is allowed per release for each extension.
    5. Select the basic type which is to be combined with your extension. Confirm your entries.
    The basic type is displayed as a tree structure. See the color legend (Utilities ® Color legend).
    6. Position the cursor on the segment where you wish to append the extension segments (the reference segment). Choose . You must now assign attributes for these child segments:
    · Mandatory segment (indicator): Must data be written to this segment in the IDoc?
    · Maximum and minimum frequency of use:
    7. You can add further children or “grandchildren” to this or any other reference segment in the basic type.
    8. When the new extension is complete, you can save your entry.
    You should keep the following factors in mind when dealing with extensions:
    · Segments must not explicitly occur more than once in the IDoc type - this means that the extension cannot have any segments which already exist in the basic type. This also means that a successor must not have any segments which already exist in the predecessor.
    · Parent segments of predecessors must remain parent segments in the case of successors.
    · Extension segments cannot be created from reference segments using the Cut and Paste functions and vice versa.
    In the example call your extension Z1ORDERS. Append Z1TEST1 child segment to E1EDP19reference segment in ORDERS01 basic type. The child segment can be used only once
    Best Regards,
    Rajesh
    Please reward points if helpful.

  • Extension of BASIC IDoc

    Hi,
    can any body tell me , what are the steps of BAsic IDoc extension,
    Regards,
    Bhaskar

    Hi..
    These are the Steps to Enhance IDOC Type:
    IDOC EXTENSIONS
    In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
    In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
    1. Create an Extension Type and a New Segment.
    First, letâs determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX
    To create an extension type and new segment:
    Use transaction WE30 or from WEDI go to Development -> IDOC types.
    Enter ZDEBMASX for Object Name.
    Choose Extension Type.
    Click on Create.
    You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
    You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
    You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
    For 4.x, press Create after placing the cursor on segment E1KNVKM.
    You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
    Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
    Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
    For 4.x, you must first create the IDOC segment Z1SADRX from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
    Click on Segment Editor.
    On the next screen, click on Create.
    Enter a development class for the object. Enter.
    This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
    Enter these three columns for all 12 fields. Save.
    Click on Generate/Activate, F3 to step back.
    From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX .Check this box. Save.
    Save again to store the descriptions of the segment, F3 to step back.
    Save the extension type.
    It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
    2. Create an IDOC Type.
    The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
    From transaction WE30 or WEDI go to Development -> IDOC Types.
    Enter ZDEBMASZ for Object Name.
    Click on IDOC Type.
    Click on Create.
    Enter DEBMAS02 for Basic IDOC type.
    Enter ZDEBMASX for extension type.
    Enter a description.
    Enter.
    You will see a display of the composite IDOC type with all segments, including Z1SADRX .
    It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
    3. Link IDOC Type to Message Type.
    The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
    Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
    Click on Display <-> Change.
    Click on New Entries.
    Enter DEBMAS for message type.
    Enter DEBMAS02 for Basic IDOC type.
    Enter ZDEBMASX for extension type.
    Enter your SAP R/3 release number for Release.
    Save.
    This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
    4. Check the IDOC Type.
    Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
    From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
    For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
    The extension type has now been "released."
    You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
    From transaction WE30 or WEDI go to Development -> IDOC types.
    Enter ZDEBMASX for Object name.
    Click on Extension Type.
    From the Development Object menu select Check.
    Repeat the operation for IDOC type ZDEBMASZ.
    A check log will be generated for each run with details of correctness or errors (see Figure 4).
    In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
    Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
    ALE FUNCTION MODULE ENHANCEMENTS
    Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application. It may be necessary to enhance an ALE function module even in situations where an IDOC extension has not been performed if the IDOC data being passed to and from the application requires modifications. The following approach applies to both situations.
    The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
    For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
    From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
    Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
    Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
    All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
    When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
    Execute transaction CMOD.
    Enter name of project, say CSTMAST1.
    Click on Create.
    Enter a description of the project.
    Save.
    Click on SAP Enhancements.
    Enter VSV00001 for Enhancement.
    Save.
    Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
    As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
    The two important factors to consider while developing the customer function are:
    The point in the ALE function module where the function exit occurs
    The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
    Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
    Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
    Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
    Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
    From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
    Find Customer Function 001.
    Double-click on 001.
    The function EXIT_SAPLVV01_001 will be displayed.
    Double-click on INCLUDE ZXVSVU01.
    You will be asked to create a new include object. Proceed as desired.
    Enter code (as in Listing 1).
    Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
    Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
    To maintain the contact personâs business address of a customer:
    Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
    Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
    With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
    Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
    The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
    Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
    Reward if Helpful.

  • Mapping complete input XML structure into one field on target

    Hi,
    I have a scenario where I need to map the complete input XML structure as it is, into one field on target side. so can we achieve this in Graphical Mapping? If yes, please share your valuable info.
    Regards,
    Shiva.

    Hello,
    this is the java map code.just compile it and made a .zip file import it and use it Interface Mapping.
    import com.sap.aii.mapping.api.StreamTransformation;
    import com.sap.aii.mapping.api.AbstractTrace;
    import com.sap.aii.mapping.api.StreamTransformationConstants;
    import java.util.Map;
    import java.io.*;
    public class PayloadToXMLField1 implements StreamTransformation {
        String strXML = new String();
       //Declare the XML tag for your XML message
       String StartXMLTag = "<DocumentBody>";
       String EndXMLTag = "</DocumentBody>";
       //String StartXMLTag1 = "<Code>";
       //String EndXMLTag1 = "</Code>";
        AbstractTrace trace;
        private Map param = null;
        public void setParameter(Map param) {
            this.param = param;
        public void execute(InputStream in, OutputStream out) {
            trace =
                (AbstractTrace) param.get(
                    StreamTransformationConstants.MAPPING_TRACE);
            trace.addInfo("Process Started");
            try {
                StringBuffer strbuffer = new StringBuffer();
                byte[] b = new byte[4096];
                for (int n;(n = in.read(b)) != -1;) {
                    strbuffer.append(new String(b, 0, n));
                strXML = strbuffer.toString();
            } catch (Exception e) {
                System.out.println("Exception Occurred");
            String outputPayload =
                StartXMLTag
             + "<![CDATA["
             + strXML
             + "]]>"
             + EndXMLTag;
            try {
                out.write(outputPayload.getBytes());
             trace.addInfo("Process Completed");;
            } catch (Exception e) {
                trace.addInfo("Process Terminated: Error in writing out payload");;

  • Read Measurement file does not read the first channel of my TDMS file

    When I try to read a TDMS file with the Read Measurement File express VI, the first channel of the data is not there.  When I open the file up in excel the channel exists

    Even I have the same doubt  regarding Labview plss help me reading the Excel file from 23rd row and the graph should be drawn between 1st column and 8th column ,  from 23rd row . Here is the sample data.
    Attachments:
    Book1.xlsx ‏204 KB

  • Reading the Excel from Content Server...

    Hello Experts
    I have a requirement to read the contents of the excel from DMS content server to Internal Table.
    I tried using the function module "SCMS_DOC_READ", but it is reading only the part of the contents and remaining contents are missing in the Internal Table.
    Is there any other way to read the content of excel file stored in content server.
    Many Thanks in advance!!!
    Regards,
    Benu

    Hi Christoph,
    Many thanks for your reply...
    Now I am using the same report for downloading the document from content server but my requirement is to read the contents directly from content server without downloading it to presentation server..
    The function module mentioned in the above post is not reading the complete contents of the excel sheet.
    Regards,
    Benu

  • BAPI & FM to read the Orders, Stock & Pegging Structureu0085

    TC /SAPAPO/RRP3 Product View)
    I am debugging the ‘Context’ option in Product view to get the details of BAPI & FM to read the Orders, Stock & Pegging Structure…
    I have the List of it as follows:
    BAPI_POSRVAPS_GETLIST2            – To Read the Planned Orders
    /SAPAPO/DM_ORDKEY_SELECT_ORDNO    - To get GUID of the Order from LC
    For Pegging Structure
    /SAPAPO/RRP_GET_PRIMARY_REQMTS   
    /SAPAPO/RRP_LC_ORDER_GET_DATA    
    Please let me know if you have any idea about the BAPI for Pegging Structure…

    Try /SAPAPO/OM_ORDER_GETDATA
    /Shibu
    Thanks for rewarding points if this is helpful

Maybe you are looking for

  • IMac to TV (HDMI) : Ghost display when TV is off

    Hi,  I'm using my Sony TV (40BX420) as my secondary display for my iMac 27", connected via MiniDisplay Adapter+HDMI Cable.   When connected everything works fine, the audio & picture appears normally.  I use this setup to watch movies on my bigger sc

  • How can I reset my iCloud password when It's hacked?

    Someone hacked my iCloud. I tried to get the password back but i forgot one of my security questions. I thought "I'll just make a new iCloud and sign out of the old one". Well, I put the "Find my ipod" app on it and I can't sign out with out the pass

  • Reflection Set Properties

    Hello,  I have the below code snippet where I am trying to load dynamic csv files(The columns names can change, so I cant define a regular class and read them into that class) and create a dynamic class with Reflection and then map the data back to t

  • Query to find data of each month

    hi, i have 2 table. 1) Order_tb Name Null? Type ORDERID NOT NULL NUMBER CUSTOMERID NUMBER ORDERDATE DATE 2) Order_d Name Null? Type ORDERID NUMBER PRODUCTID NOT NULL NUMBER PRODUCTNAME VARCHAR2(20) SELLINGPRICE NUMBER i need to find the total find th

  • My iPad says I'm running out space

    My iPad says I'm running out of space. When I go to my usage in settings, it says I have 2.1 gbs left. What does this mean. Also, I want to download an app that is 1.3 gbs, but it won't let me because it says I don't have enough space even though I d