ESLL  missinu00B4 fields in SAP ECC 6.0

Hi, friends!
I have the following issue. Could anyone tell me why in SAP ECC 6.0 the table ESLL has less fields than in SAP ECC 5.0? The point is that, in SAP 6.0, there are function modules that references some of those missing fields and get dump after execution. I´ve been looking for SAP notes and I have not found out anything. Could anyone help me?
Specifically, I find one of the differences in the structure ESLL_PLUS, for instance.
Thanks in advance, family!

Can you please check closely, I actually see 7 more fields in ESSL table in ECC6.0 (108 fields) than in ECC5.0 (101 fields).
Can you list down which fields you are looking for that you think are missing?
I have checked ESLL_PLUS, it seems to be the same in ECC 5.0 and ECC 6.0..
There are two new structures in ECC6.0 ESLL_PEROP_STY and OILESLLDATA which doesnt exist in ECC5.0
Also if you just upgraded recently to ECC 6.0 check SPDD logs.
Also check out SWITCH framework, ESLL_PLUS (ESLL_BOS) may be linked to some new frame work that you did not SWITCH ON... Just a thought.
-- SMA
Edited by: S M A on Oct 19, 2010 10:21 PM

Similar Messages

  • Adding new fields in SAP ECC 6.0

    Hi All,
    I have a requirement to add a couple of fields at the item level of ERP Quotation. I would like to know if SAP ECC 6.0 have some tools like EEWB/AET in SAP CRM.
    Please suggest a solution..
    Any Help/Hint highly appreciated,
    Thanks, Sudeep..

    Can you please check closely, I actually see 7 more fields in ESSL table in ECC6.0 (108 fields) than in ECC5.0 (101 fields).
    Can you list down which fields you are looking for that you think are missing?
    I have checked ESLL_PLUS, it seems to be the same in ECC 5.0 and ECC 6.0..
    There are two new structures in ECC6.0 ESLL_PEROP_STY and OILESLLDATA which doesnt exist in ECC5.0
    Also if you just upgraded recently to ECC 6.0 check SPDD logs.
    Also check out SWITCH framework, ESLL_PLUS (ESLL_BOS) may be linked to some new frame work that you did not SWITCH ON... Just a thought.
    -- SMA
    Edited by: S M A on Oct 19, 2010 10:21 PM

  • Marking Fields as display only in SAP ECC

    Hello Experts,
    We have centralization scenario for Vendor master data. We have a requirement that once the Vendor Master data is created in SAP MDM and syndicated to SAP ECC, the ECC users should not be able to change the data for the fields coming from SAP MDM, i.e they should not be able to make change to the field values in  Vendor Master data coming from SAP MDM, through XK01 and XK02. But at the same time these MDM fields should get updated if it is updated by an IDoc.
    Do we have any exits  for Vendor in SAP ECC which can be called during XK01/XK02 which will make the SAP MDM fields non editable from the XK01/XK02 screen.
    Please help.
    Best Regards
    Manoj

    Hi Manoj,
    In the ECC go to the SPRO transacción and find:
    - Financial Accounting / Accounts Receivable and Accounts Payable / Vendor Accounts / Master Data / Preparations for Creating Vendor Master Data / Define Account Groups with Screen Layout (Vendors)
    You need to change the customizing by each Account Group and put the fields that came from MDM in "Display" mode
    Regards
    Daniel

  • Extracting Values of a Field from a Database Table in SAP ECC System

    Hi,
    I downloaded Extracting Values of a Field from a Database Table in SAP ECC System Using MII 12.0
    senario from sdn. I'm trying to do that senario in MII 12.05. But I have problem with section 6 in page 7 (you can supply senario from sdn)
    "6- Under the loop of Repeater, use action u2018Rowu2019 to append just the string part of the WA which will display only values for field u2018Batchu2019"
    I did not find WA elemen in Output element of Repeater_0
    How can I create WA element?
    Thanks.

    Cemil,
    Set up a SAP JCo Interface action block.  Use the RFC name RFC_READ_TABLE.
    In the link editor map the table to "MARA", set RowCount to something small (20 is good sample size) and create an xml transaction property named FIELDS and copy the following into it:
    <?xml version="1.0" encoding="UTF-8"?><FIELDS>
          <item>
            <FIELDNAME>MATNR</FIELDNAME>
            <OFFSET/>
            <LENGTH/>
            <TYPE/>
            <FIELDTEXT/>
          </item>
          <item>
            <FIELDNAME>MTART</FIELDNAME>
            <OFFSET/>
            <LENGTH/>
            <TYPE/>
            <FIELDTEXT/>
          </item>
          <item>
            <FIELDNAME>BSTME</FIELDNAME>
            <OFFSET/>
            <LENGTH/>
            <TYPE/>
            <FIELDTEXT/>
          </item>
          <item>
            <FIELDNAME>XCHPF</FIELDNAME>
            <OFFSET/>
            <LENGTH/>
            <TYPE/>
            <FIELDTEXT/>
          </item>
          <item>
            <FIELDNAME>DATAB</FIELDNAME>
            <OFFSET/>
            <LENGTH/>
            <TYPE/>
            <FIELDTEXT/>
          </item>
        </FIELDS>
    Then link the Transaction.FIELDS to SAP_JCo_Interface_0.Request{/RFC_READ_TABLE/TABLES/FIELDS}.  You may run into problems with two other fields and optionally they can be removed (set link type to remove xml).  I usually remove them initially for testing.  The two fields are:
    SAP_JCo_Interface_0.Request{/RFC_READ_TABLE/INPUT/NO_DATA}
    SAP_JCo_Interface_0.Request{/RFC_READ_TABLE/INPUT/DELIMITER} (or you can set this to something like a semicolon,";" or tilda,"~".  I find it easier to caclulate position by length, but that is my own idiosyncrasy.)
    Once you get this one working, we can explore how to do filtering on the dataset.  Your output should be something like this:
    <?xml version="1.0" encoding="utf-8"?>
    <RFC_READ_TABLE>
      <INPUT>
        <DELIMITER />
        <NO_DATA />
        <QUERY_TABLE>MARA</QUERY_TABLE>
        <ROWCOUNT>20</ROWCOUNT>
        <ROWSKIPS>0</ROWSKIPS>
      </INPUT>
      <TABLES>
        <DATA>
          <item>
            <WA>000000000000000023ROH 00000000</WA>
          </item>
          <item>
            <WA>000000000000000038HALB 00000000</WA>
          </item>
          <item>
            <WA>000000000000000043HAWA 00000000</WA>
          </item>
          <item>
            <WA>000000000000000058HIBE 00000000</WA>
          </item>
          <item>
            <WA>000000000000000059HIBE 00000000</WA>
          </item>
          <item>
            <WA>000000000000000068FHMI 00000000</WA>
          </item>
          <item>
            <WA>000000000000000078DIEN 00000000</WA>
          </item>
          <item>
            <WA>000000000000000088FERT 00000000</WA>
          </item>
          <item>
            <WA>000000000000000089FERT 00000000</WA>
          </item>
          <item>
            <WA>000000000000000098HALB 00000000</WA>
          </item>
          <item>
            <WA>000000000000000170NLAG 00000000</WA>
          </item>
          <item>
            <WA>000000000000000178NLAG 00000000</WA>
          </item>
          <item>
            <WA>000000000000000188NLAG 00000000</WA>
          </item>
          <item>
            <WA>000000000000000288HALB 00000000</WA>
          </item>
          <item>
            <WA>000000000000000358HAWA 00000000</WA>
          </item>
          <item>
            <WA>000000000000000359HAWA 00000000</WA>
          </item>
          <item>
            <WA>000000000000000521HAWA 00000000</WA>
          </item>
          <item>
            <WA>000000000000000578FERT 00000000</WA>
          </item>
          <item>
            <WA>000000000000000597HAWA 00000000</WA>
          </item>
          <item>
            <WA>000000000000000598VERP 00000000</WA>
          </item>
        </DATA>
        <FIELDS>
          <item>
            <FIELDNAME>MATNR</FIELDNAME>
            <OFFSET>000000</OFFSET>
            <LENGTH>000018</LENGTH>
            <TYPE>C</TYPE>
            <FIELDTEXT>Material Number</FIELDTEXT>
          </item>
          <item>
            <FIELDNAME>MTART</FIELDNAME>
            <OFFSET>000018</OFFSET>
            <LENGTH>000004</LENGTH>
            <TYPE>C</TYPE>
            <FIELDTEXT>Material Type</FIELDTEXT>
          </item>
          <item>
            <FIELDNAME>BSTME</FIELDNAME>
            <OFFSET>000022</OFFSET>
            <LENGTH>000003</LENGTH>
            <TYPE>C</TYPE>
            <FIELDTEXT>Purchase Order Unit of Measure</FIELDTEXT>
          </item>
          <item>
            <FIELDNAME>XCHPF</FIELDNAME>
            <OFFSET>000025</OFFSET>
            <LENGTH>000001</LENGTH>
            <TYPE>C</TYPE>
            <FIELDTEXT>Batch management requirement indicator</FIELDTEXT>
          </item>
          <item>
            <FIELDNAME>DATAB</FIELDNAME>
            <OFFSET>000026</OFFSET>
            <LENGTH>000008</LENGTH>
            <TYPE>D</TYPE>
            <FIELDTEXT>Valid-From Date</FIELDTEXT>
          </item>
        </FIELDS>
        <OPTIONS />
      </TABLES>
    </RFC_READ_TABLE>
    Add a repeater sourced on:
    SAP_JCo_Interface_0.Response{/RFC_READ_TABLE/TABLES/DATA/item}
    Link your repeater output to a tracer with this:
    Repeater_0.Output{/item/WA}
    What you will see in each tracer message is a single line of data with all the fields contents concatenated together.  You can look up what each field in the string represents by the length of the field as returned in the Response segment of the RFC_READ_TABLE rfc.  Then you can parse out the data you are interested in.
    Give this a try and let me know how you succeeded.
    By the way, I could not find the scenario you referred to.  Can you post a link?
    Regards,
    Mike
    Edited by: Michael Appleby on Jan 12, 2009 5:16 PM

  • Using the Open Catalog Interface (OCI) between SAP-ECC 6.0 and SAP-MDM

    Hello ASUG Community.
    I'm working on an SAP-MDM project where we will configure the OCI interface between SAP-ECC 6.0 and SAP-MDM.  The business requirement will be to punch out to SAP-MDM's catalog from SAP-ECC for expensed items (e.g., no material master record exists in SAP-ECC).
    The data that will be returned to SAP-ECC will be purchase price info, material group, short text, & our global SAP-MDM item number.
    The question I've been trying to design around is "where to store the SAP-MDM item number"?
    I've looked into creating a custom filed on EKPO but now feel that a configured text field will be the best solution from an SAP-ECC point of view (less effort on the SAP-ECC side from a development perspective, no need to regenerate the EKPO table, etc.).
    The question I'd like to pose to ASUG is.... Does anyone have experience or an opinion to offer using this functionality?  It seems that I will have to code in a user exit or BAdi to insure that the SAP-MDM item numbers are returned to the appropriate text field on my POu2019s.  Or can this be done using the standard OCI functionality?
    I found OSS note 1347656 which references BADI "ME_CATALOG_INTERFACE" but I'm not sure if this right path to go down or if this would be the correct place to code non-conforming OCI mapping requiremetns.
    Any insight would be most appreciated.
    Thanks.  Sincerely,
    Rich Wortmann

    I would suggest you create a new field for this as you may require thois going forward for reporting as well. Text fields are difficult to report.
    Sorry not sure about the BADI to use.

  • How do we map this scenario in SAP ECC

    Hi Gurus,
    I need a help from you, to get your perspective on how the below mentioned business scenario can be mapped in SAP ECC.
    Scenario: The client is engaged in a business of supplying surgical kits to hospitals. The surgical kit is actually a case with two shelve in it. Tray 1 holds the equipments for surgery and the Tray 2 holds the implants for surgery. There are various different kits depending upon different surgeries. Depending upon the need/demand from the hospital appropriate kit is sent to the sales rep, who then delivers the kit to hospital. Now when the kit is supplied to the hospital, the surgeon uses the equipments from Tray 1 to perform the surgery and consumes some of the implants (as needed) from Tray 2. Once the surgery is done, the equipments are cleaned by the hospital and the kit is sent back to the sales rep.
    At this point the sales rep need to raise an invoice to the hospital for the implants that were consumed from the Tray 2 and also need to charge for the service for using the equipments. Both the equipments and implants have serial numbers and each kit has a serial number.
    Ask from the business
    1.They should be able to track which kits are out in the field and should be able to see the inventory within the kit.
    2.Should be able to consume the implants from inventory, which have been consumed during surgery and raise an invoice to the hospital for consumed implants.
    3.Business should be able to charge for the equipments used
    4.They should be able to track the inventory in the kits
    5.They should be able to depreciate the equipments in the kits.

    Hi,
    You may please check in this forum
    Also, please explore whether [IS-Healthcare|http://help.sap.com/content/documentation/industry/docu_is_health.htm] helps you finding a solution.
    Regards,
    P Gomatheeswaran

  • Query on Field exits in ECC 6.0

    Hi All,
    We have implemented field exits in SAP R/3 4.6c and now we have upgraded to ECC 6.0.
    I need to know the following information:
    Are field exits obsolete in ECC6.0?
    Can we create new field exits in ECC 6.0 ?
    Going forward, what is the alternative technology/concept to be used - enhancement sports, BADIs etc for field validations(or instead of field exits)?
    Regards
    Shiva

    Hi,
    Though it is obsolete, SAP does not say dont you field exit. You can still use field exit. You can still create field exits.
    Whatever is already existing will definitely work. Creating a field exit is much more simpler and easy than the BADIs or Enhancement points.
    Yes you are right, going forward, you will have to use BADIs or Enhancement points.
    Regards,
    Subramanian

  • How to populate custom fields in SAP standard Basic type DELFOR01(E1EDK09)

    I've a requirement to include and populate 2 custom fields in SAP standard basic type DELFOR01 and Segment E1EDK09 (it is at hierarchy level 1 ) .
    The requirement looks very simple but for this, as per my knowledge, I have to create a new  Basic type with the copy of segment E1EDK09 and attach it to outbound process code and write my own function module to populate the segments.
    It seems ok but the there are some existing codes in the user-exits for the SAP standard function module.These codes will not get triggered.(Or I've copy the user-exits code in my FM)
    Can we do it any other way to handle this kind of situation?
    Thanks in advance for your suggestions and help.

    Hi Phani,
    You have done it correctly. ECC additional data to be moved to EWM, 1. you need to enhance the CIF for master data/ bapi  to populate the data in the custom field in EWM. 2. Make your your are not enhancing only one structure. You need to do it in the CI includes so that the field is available in all the related tables/structures.
    3. The BAPI/FM which updated these tables will take care automatically to update the custom field data if the field is correctly added in all the tables.
    4. If the custom fields are added correctly and still the data is not getting saved , then need to check the mapping of the custom field and bepi extension.
    Let me know if this helps.

  • Call Transaction XK02 in SAP ECC 6.0 Version

    Hi All,
    I am working with an object which calls a transaction XK02 to modify the name and contact details fields in Version SAP ECC 6.0.
    The problem is that, when the transaction is run manually and saved or when an SHDB Recording is created, the data is getting updated.
    But when the transaction is called from a program or when the SHDB Recording which is already created is run, the data is not getting updated in Version SAP ECC 6.0.
    The data is getting updated properly when it is done in Version SAP 4.6b.
    Central Address Management System is used here.
    The call transaction statement is running smoothly. The SY-SUBRC is 0 for this.
    The thing is, there is a Check Box at the end of the screen called 'Use Central Address Management' when the SHDB is created.
    If this is checked, the contact details are stored in ADRC and LFA1 tables and only in LFA1 if not checked.
    In the new version SAP ECC 6.0, the data should also get populated in the ADRC table.
    There is a slight change in the logic in SAP ECC 6.0 version.
    Can anybody please help me in this regard?
    Thanks & Regards,
    Vaitheeswaran.

    Hi Prabhu,
    The call transaction statement is running smoothly. The SY-SUBRC is 0 for this.
    The thing is, there is a Check Box at the end of the screen called 'Use Central Address Management' when the SHDB is created.
    If this is checked, the contact details are stored in ADRC and LFA1 tables and only in LFA1 if not checked.
    In the new version SAP ECC 6.0, the data should also get populated in the ADRC table.
    There is a slight change in the logic in SAP ECC 6.0 version.
    Thanks & Regards,
    Vaitheeswaran.

  • SAP Enterprise Project Connection 2.0 in SAP ECC 6.0 EHP6

    Hello experts,
    Before describing any think let me tell u that i am very new to this field.
    We are configuring SAP Enterprise Project Connection 2.0 in our SAP ECC 6.0 EHP6 .I have already installed ABAP add on for EPC in ECC system.
    I have also installed trial version of primavera6 in another system.So now how can i connect my ECC system to Primavera6 through Enterprise Project Connection(EPC). I have gone through the installation guide for SAP Enterprise Project Connection 2.0 SP2.But i could not get any clear idea.
    Any reply is helpful for me..
    Thanks
    Debasis

    Hello Debasis,
    Post EPC installation,you need to perform configuration of EPC through portal.You can see it listed under configuration--> configuration scenarios-->EPC.
    During configuration you will be asked to define path of you primavera installation and a user on that system with sufficient permissions. This user is called APS user.
    Try to do a mock configuration run on sandbox/dev system and then you can follow the guide.
    Regards,
    Hetal

  • Data load from SAP ECC to SAP BI

    Hello Gurus and Experts
                     I am new to BI and I m almost struggling to find a step by step process in loading data from SAP ECC to SAP BI through generic extractors from VBAK. The Problem is I can create an Infopackage for full update and loaded the records.(Lets say Upto this step 100 records are moved to PSA)
    Then I create a sale order in ECC which is a new record that has to be transfered as delta record.
    Now my questions are:
    Am I correct if I moved the initial records into PSA with Full Mode InfoPackage?
    Should I create another infopackage for delta records with Delta Mode or to change the update mode of the infopackage created earlier for Full Update mode?
    Should I create a new infopackage every time to load the delta records?
    Does separate DTP has to be created for Full and Delta updates?
    Please dont be frustrated if my questions are pointless or childish
    I would be glad if someone demonstrate the solutions in steps
    Thanks in Advance
    Karthik

    Hi Ram,
           I have followed all the steps mentioned by you, yet something is lagging in my end.
    Let me lists the steps done by me and please correct me if i am wrong anywhere.
    1. RSO2 in ECC..
    2. Created DS with short, med and long names in SD application component for VBAK with all the fields unchecked in hide selection except document number, time of document, document date, net
    value of the document and document currency.
    3. mentioned a numeric pointer as Document number for delta and used new status for changed records.
    3. saved the datasource. checked the newly created ds using the tcode RSA3.
    4. Replicated the datasource under SD Application Component in BI and Activated it
    6. Performed Transformations
    7.  created an Info Package with FULL UPDATE and executed. I got 6898 records in my PSA
    6. Created DTP with DELTA. Saved and Executed it. Got 6898 records in my DSO
    7. Created Info Package with INIT WITHOUT DATA TRANSFER and scheduled it.
    8. Switched over to ECC and added a sale order
    9. Created an InfoPackage with DELTA UPDATE and Scheduled it.
    -----I didnt receive any records in my PSA
    10. performed DTP.
    ---- I didnt received any new records in my DSO as my delta run is not working..
    PS: I am using WO DSO
    Please correct me if i am wrong anywhere
    Thanks in advance
    Karthik

  • Extraction from SAP ECC to SAP BI

    What are the steps for Extraction from SAP ECC to SAP BI? Thanks.

    Hi,
    we have two types of extractions 1) Application specific 2)cross application
    under applicatin specific -->we have customer genenrated and business content extractions
    under customer generated means LIS, CO-PA, FI-SL(i.e no ready made data source in business content so we have to generate datasource)
    Business content means there is ready made business content datasource so we can use it
    LIS,LO --> when ever we go for extracting logistics informatin
    LO steps
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    LO Cockpit (Use transaction LBWE)
    /people/vikash.agrawal/blog/2006/12/18/one-stop-shop-for-all-your-lo-cockpit-needs
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/21406 [original link is broken] [original link is broken]
    /people/sap.user72/blog/2005/09/05/sap-bw-and-business-content-datasources-in-pursuit-of-the-origins
    To understand LO extraction go through these weblogs by Roberto
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    under cross Applicaion
    Generic extraction-->table, view, infoset query, function module
    Generic extractors are of 3 types:
    1. Based on table/view
    2. Based on Infoset Query
    3. Based on Function module
    GenericSteps
    Log on sap R/3.
    Step 1. create a table or view for generic extraction in se11.
    Step 2. Goto  t-code RSO2
    Step 3. Here u have to decide whether to extract transaction data or master data attributes or texts.
    Step 4. suppose if u have opted for transaction data,then give name in the column ex:ztd_m(data source name)
    Step 5. select create button,this will take u to another screen.
    Step 6. Here u have to decide from which application component u r extacting data.Ex: SD,MM,..
    Step 7. in this screen u have to fill short disciption,medium,long( these r mandatory).
    Step 8. then U have to Table name or view name which u have created in se11.
    Step 9. I f u want to maintain generic delta then u can select generic delta in top left hand side corner.
    Step 10. in next screen u have to give some field which is primary key.
    step 11. here u to specify whether time stamp or cal day or numeric pointer depending on u r requirement.
    step 12. then u have to specify  whether new status for changed records or additive delta.
            If u choose additive delta ,then u have to load data to infocube or ods object.
            If u choose new status for changed records, then u to load data  to ods object only.
    Step 13. then save it.
    Step 14. then logon to sap bw ,then replicate the data source then as usuall.
    COPA
    CO-PA--> for financial info
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/COPA/COPA.pdf
    You can browse forum for more detailed info..
    Regards,
    B

  • MessageBox on Adobe Form in SAP MSS PCR for SAP ECC 5.0

    Hello,
    I have a question regarding the behavior of Adobe form messagebox in SAP HR MSS PCR (Personal Change Request)
    I tried to test how the messagebox looks like, and so I created a PCR scenario with an Adobe form. This form contains a datetime field. I added the script "xfd.host.messageBox("this is message", "this is title") to the "exit" event of the datetime field. Then I did all the necessary steps so that this PCR is displayed in the Portal.
    Now at the runtime, when I select a date value from the datetime field, the messagebox is displayed, BUT within an empty Adobe Reader page. It is not displayed on the top of my adobe form.
    But the strange thing is that when I use tab key to navigate through the datetime field, the messagebox is displayed on the top of my adobe form, without the empty Adobe Reader page.
    I also tried my script with several different event types, including "Change", and "Validate", it behaves the same way. But when I tried it with the event type "MouseExit", no empty Adobe reader page is shown up at all (of course, this is not the right event type for me)
    The environment is SAP ECC 5.0, SAP MSS business package for ECC 5.0, SAP Portal 7.0 (NW 2004s), Adobe LiveCycle 7.1, and Adobe Reader 8.1.1
    Has anyone experienced this? I'd really appreciate any comments and suggestions. Thanks in advance.
    Best regards,
    Harrison

    Antony,
    The Adobe Reader version is 8.1.1
    Just wondering if you used messageBox in interactive forms with ISR framework, and it worked well for you?
    Thanks.
    Harrison

  • Lo-Extraction Job Failed in SAP ECC 6.0

    Hello,
    My Lo-extraction job failed yesterday because of this I'm unable to extract the delta data from SAP ECC 6.0 to BI. When I extract the Delta data from 2LIS_11_VAITM to BI there is no data because of Job failed in SAP ECC 6.0.
    How to get the data back to 2LIS_11_VAITM data source?
    Thanks

    Error log display as follows
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "MESSAGE_TYPE_X" " "
    "SAPLMCEX" or "LMCEXU14"
    "MCEX_UPDATE_11"
    Actually I add ZZ fields to structure if that is the case do i need to delete the  data  from MCEX11 ?
    I delete the data from setup tables but i did not delete the LUW entries?
    When do we delete the LUW entries?
    If the structure changes do I need to cancel the old job and re-schedule job?
    Thanks

  • Regarding XK02 transaction in SAP ECC 6.0 Version

    Hi All,
    I am working with an object which calls a transaction <b>XK02</b> to modify the name and contact details fields in  Version <b>SAP ECC 6.0</b>.
    The problem is that, when the transaction is run manually and saved or when an SHDB Recording is created, the data is getting updated.
    But when the transaction is called from a program or when the SHDB Recording which is already created is run, the data is not getting updated in Version SAP ECC 6.0.
    The data is getting updated properly when it is done in Version SAP 4.6b.
    Central Address Management System is used here.
    Can anybody please help me in this regard?
    Thanks & Regards,
    Vaitheeswaran.

    Hi Prabhu,
    The call transaction statement is running smoothly. The SY-SUBRC is 0 for this.
    The thing is, there is a Check Box at the end of the screen called 'Use Central Address Management' when the SHDB is created.
    If this is checked, the contact details are stored in ADRC and LFA1 tables and only in LFA1 if not checked.
    In the new version SAP ECC 6.0, the data should also get populated in the ADRC table.
    There is a slight change in the logic in SAP ECC 6.0 version.
    Thanks & Regards,
    Vaitheeswaran.

Maybe you are looking for