Assortment Idoc

Hi All,
I have structure Like This ,
WBBDLD.WBBDLD03 Under this v have segmentE1WBB01 Under this segemnt  v have another segemnt E1WBB03 , again under this  segement  v have another segement E1WBB11
under E1WBB11 v have Field called AKTHE
This Field is used for Promotations ( Discount Features)
EX: If I supoose  Buy more Than 20  Articles .In  One or MOre articles may  have  Discount Features  and they caontain some value in AKTHE .
How to do Mapping  for this field , I am facing error  while posting idocs for this field contains values
I need in Graphical Mapping
Regards,
Praveen

Hi
In Standard XI contents for IS Retail & SAP POS Integration, there are 2 levels of mapping.
1)ERPAssortmentListToIXRIMandPrice
2)IXRIMandPriceToGMStore
Do you want to map this field to pos field of promotxn.asc.
You have to do mapping in both levels.
Pls mention the target field which you want to map with AKTHE.
Regards
Abhijit

Similar Messages

  • Is it poosible to control the start date for an assort idoc on the erp sise

    is it poosible to control the start date for an assortment list  idoc on the erp sise

    Hi rodeofive,
    As per my understanding, the issue is a performance issue. And it is caused by there are thousands of values in the drop-down list of parameters in the report.
    To work around this issue, I suggest you should make some changes in the report. For example, we can add additional two parameters with multiple keywords ahead, one for the dropdown contains 95k options, another for dropdown contains 24k options. Then all
    of available values which are begin with the keywords will display in the parameter list. In this scenario, we can create cascading parameters. One is a keyword parameter, and the other parameter is the drop-down list that based on the keyword to display the
    available values.
    For more details about the method, please refer to the following FAQ:
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/8de6c783-9cb4-4b95-9be8-b59bc0049866/forum-faqhow-do-i-add-a-search-feature-in-the-parameter-with-long-drop-down-list?forum=sqlreportingservices#8de6c783-9cb4-4b95-9be8-b59bc0049866
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • No change triggered for assortment list IDOC

    Dear all expert,
    I'm facing a problem and below is issue reproduction steps.
    1. Article 'A' listed to Assortment 'ASM01' which is assigned 3 sites as assortment users.
    2. I executed WDBI for assortment list initialization. 3 IDOC files are generated successfully.
    3. Now, I unassigned one of the site from the assortment ASM01.
    4. I execute WDBU for assortment list IDOC change message. No IDOC is generated for this site.
    Any idea?
    Thank you very much!
    Regards,
    Wso

    Hi Tobias,
    Thanks for your reply!
    Actually i'm newbie on SAP Retail and now looking at listing and assortment stuff. I've configured the Assortment List Profile with checkbox 'Deletions for Listing' selected. Below is the SAP help explanation:
    "Indicator: Generate Deletion Records for Listing
    When you set this indicator, special material header records, carrying the information from the store retail system about the deletion performed, can be sent during deletions of assortment assignments between plant and assortment or during physical deletions of listing conditions in the change version of the assortment list. In the IDoc, these materials are marked with the change indicator AENKZ = 'DELE' in segment E1WBB01."
    So i wonder a IDOC file will be generated for the unassigned site with change indicator DELE for all articles listed to that site.
    Thanks again!
    Regards,
    Wso

  • Assortment List IDoc - WBBDLD03 Taxcode Segment not creating.

    Hi All,
    What configurations are required to send the Tax code from Assortment List Idoc 16th Segment.  Pls. let me know the steps of configuration verification so that it can be send through Assortment List IDOC WBBDLD03 or 6
    Regards
    Ashok

    Hi Milan
    Pls. follow these steps.. for Sending the Tax Codes.
    NOTE : Steps for Tax Code Flow to POS
    Step 1 : MM42 - Basic Data - Check the following
                   Tax Class - (With Value)
                   Tax Data - (Country - CA, Tax Category - CTXJ Tax Jurisdiction, Tax Classification - 1 Taxable (0-Non Taxable, 1 Taxable Etc)).  Taxs Relevant to Article Taxes.
    Step 1.1 : MM42 - Basic Data - Check the following
                      Check for the Assortment List Type, Listing of Assortment to Site in Listing Tab, Price of Article.
    Step 2 : WB02 - Customer Tab - Billing Sales Area - Tax Classification - (1-Liable for Taxes)
    Tax code is pick up from Site - Address (Country, Region Combination of Site master to Assortment List)
    Step 3 : VK11 - Condition Type - CTXJ
    This Tax Condition should have a Combination records for Tax Codes in the List.  (For Country / State / Customer Classification / Article Classification 1. The table should contain the records for 'CA' - (Canada, Region, Tax Class Cust, Tax Class Artic, Valid from, Valid To, Tax Code)
    Step 4 : IMG -> Sales and distribution -> Basic Function -> Pricing -> Pricing Control -> Define and Assign Pricing Procedure -> Maintain pricing procedures (V/08)
                   V/08 - Pricing - VKP001 - Sales Price Princing Branch will carry the Pricing Condition to Outbound Idoc WBBDLD.
                   Solution : Changed the VKP001 Pricing procedure having the standard tax condition MWSI, this one changed to CTXJ which is of Canadian Tax Condition.
    Step 5 : IMG -> Logistics General -> Assortment -> Assortment List -> Maintain Profile for Assortment List -> Selection the Assortment Type -> Check the Condition Type Group
    Step 6 : IMG  -> Sales and distribution  -> Pos Interface  -> POS Outbound  -> Maintain POS Condition Type Group
                   This table is by default Maintained with below Condition types
                   MWSI - Output Tax
                   MWST - Output Tax
                   VKAO - Promo SP IS-R
                   VKPO - Sales Price
                   Add Additional Condition types which need to send to POS including the condition type of Tax.of Canada
                   CTXJ - Tax Jurisdiction Code.
                   KA02 - Promotional Discounts % 1
                   KA04 - Promotional Discount MD 1
    Regards
    Ashok

  • ASSORTMENT MOUDLE IDOC generation

    Hi all,
    I need to create a IDoc for assortment module.
    I am using FM to create IDoc MASTERIDOC_CREATE_ASSMOD.However it is not creating a idoc.IDoc is inbound..
    Could you please suggest me how to process that idoc.
    rgds
    Sandeep

    Hi sandeep,
    Assortment and listing
    TCODES - WSM3 (Mass maintenance), WSP4 (Individual listing)
    This component allows you to create merchandise assortments and assortment modules and assign articles to them. Articles can be automatically assigned directly to assortments as a result of checking rules during article maintenance or assortment maintenance functions. Alternatively, you can manually assign articles to assortment modules and then in turn assign the modules to assortments. In both cases, the system automatically generates listing conditions for each valid combination of article and assortment.
    By assigning assortments to sites you control which assortments — and which articles — a store can purchase or sell. A site cannot purchase or sell an article that is not contained in one of its assortment.
    When you create listing conditions, you also specify a listing period. This determines the timeframe during which sites can procure and sell the articles.
    Listing conditions
    The assignment of the individual articles to assortments is recorded in what are called listing conditions. These listing conditions contain the following:
    The periods of time for which an article is to be assigned to an assortment
    Inclusive or exclusive assignment (that is, whether an article is to be listed or excluded from listing)
    The number of the module which caused the listing conditions to be generated
    Whether the listing is for a promotion listing
    Whether the module is assigned to a rack jobber
    Whether an article is listed as a component of a structured article
    In the case of manual listing using manually created assortment modules, the system creates listing conditions based on the assignment of the assortment module to an assortment.
    In the case of automatic listing, the system uses listing rules to create listing conditions.]
    WSO1, Assortment Module Create. WSO5, Maintain Assortment Module ...
    see this link
    help.sap.com/bp_retailv1600/Retail_China/Documentation/General/what's_new_EN_ZH.ppt -
    thanks
    karthik----
    >reward me if usefull

  • Assortment List IDoc : % Discount Promotion Condition Missing

    Dear All,
    We are working with in IS-Retail Assortment List IDoc for transferring article data to stores (SAP Triversity system). We are facing one problem while transferring the promotional discounts to the POS. We are able to transfer merchandise category level discounts using IDoc WPDREB, but when we go for transferring %discounts (Condition Type KA02) via Assortmnet List (WBBDLD.WBBDLD03) IDoc, it fails to generate the pricing condition (E1WBB07 and E1WBB08). However, we are able to populate the above mentioned segments while working with the condition types VKA0 (Special Price) and KA04 (Absolute Discount). Has anyone faced a problem like this before? Do we need to do any specific setting for %discount condition types?
    Thanks in Anticipation,

    Hi  Somnath 
    sorry for the delay. As it looks like a detailed analyse is necessary.
    Please open an customer message with your question on the IS-R-BD-RPC  component.
    Some one from SAP will take care about the issue. Ensure you have an open system and access data and an example.
    I recommend to post the solution in forum after that.
    regards
    Björn
    Edited by: Björn Panter on May 21, 2008 2:15 PM

  • Added tax not in IDOC

    We added a new tax to our materials, but in the idoc is not showing.
    Segment E1WPA07 is only showing the tax code that was already configured.
    Where can I check why the new tax code is not printing in the idoc WP_PLU with transaction WPMA.
    Thank you, Regards,
    Carlos

    Hi Juan,
    the behaviour that you describe is a fall back that indicates that your price sequence is not determined correctly for the POS Outbound / Assortment list.
    However the correct set up is kind of complicated.
    For the schema determination you normally take attributes from the document (KALVG) and the customer (KALKS) and read the corresponding entry in table T683V. As there is no document in this particular case the document it read the document schema from talbe TWRPGP (field KALVG -You can find this in the IMG --> Logistics - General --> Retail Pricing --> General Parameters for Pricing).
    The determination of the calcschema for the customer is a little bit more complicated. The first challenge is to determine the right customer. If there is a anonymous customer maintained in the POS INBOUND profile for aggregated sales (you must check what POS inbound profile is assigned to your store) the customer calc schema KALKS is read from there. If this field is empty it is read from the customer master data of your store. Only if there is no entry found in T683V the application falls back to one of the standard pricing procedures ( VKP001 - 003).

  • Item lines do not appear in IDoc PRICECATALOGUE

    Hi everyone,
    I'm trying to set up for sending price catalog (to customers) using transaction VPRICAT (SAP 4.6). I've created assortment, assigned material group and assortment user to this assortment, and also created a requirements profile. I'm now able to create a price catalog using VPRICAT. The problem is when IDoc is created there is only the header information in that IDoc. No item line will appear in the IDoc. I appreciate if you could help me to locate the problem.
    Thanks in advance!
    BR,
    /Shahryar

    Any idea?
    /Shahryar

  • Need T code and standard IDOC or BAPI

    Hi All
    Need Transaction Code For Assortment Module.
    Is there any Standard Idoc or Bapi for Assortment Module Conversion. Please share.
    Regards
    Aboli

    Hi,
    Below are the transactions related to Assortment
    WSOA3 Assortment Display
    WSOA1 Assortment Create
    WSOA2 Assortment Change
    WSOA6 Assortment Assignment Tool
    WSO7 Display Assortment Module Assignment to Assortment
    WSL5 Modules In Assortment
    WSO1 Assortment Module Create
    WSO5 Maintain Assortment Module assignment to Assortment
    WSK1 Assortment Copy
    WDBM Manual Selection Assortment List
    I hope it helps you.
    Thanks
    Ravi kanth

  • Materials for idoc

    Hi am interested to learn about idocs can you provide me some useful links

    Hi saranya srithar  ,
    IDoc is an Intermediate document that holds application data.
    A container used to exchange data
    It is independent of the complex SAP structure to store data.
    It serves as the vehicle for data transfer.
    IDoc Type defines the structure and format in which the data is exchanged.
    It is similar to a structure in SAP
    IDoc data is an instance of IDoc Type
    IDoc  acts as a standard SAP interface to exchange business data through ALE.
    From an SAP system, an IDoc can be sent to and received from
    An SAP R/3 system
    An SAP R/2 system
    An EDI subsystem
    Any third-party application software
    Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
    These r all the t/codes which we will come across in IDocs:
    TCODE     TTEXT
    BD10     Send Material
    BD100     IDoc display object channel view
    BD101     Consistency check
    BD102     Outbound registry
    BD103     Inbound registry
    BD104     maintain tbd53
    BD105     Maintain Supported Business Objects
    BD11     Get Material
    BD12     Send customer
    BD13     Get customer
    BD14     Send vendor
    BD15     Open vendor
    BD16     Send Cost Center
    BD17     Get Cost Center
    BD18     Send General Ledger Account
    BD19     Get General Ledger Account
    BD20     IDoc passed to application
    BD21     Select change pointer
    BD22     Delete change pointers
    BD23     Delete serialization data
    BD24     Send Cost Elements
    BD25     Send Activity Type
    BD26     Get Activity Type
    BD27     Send cost center activity prices
    BD28     Send obj/cost element control data
    BD30     Distribute material object list
    BD31     Distribute document object list
    BD32     Distribute plant allocations(matBOM)
    BD33     Distribute material variants (ALE)
    BD34     Distribute order BOM
    BD35     Send Business Process Groups
    BD36     Send Business Processes
    BD37     Send Business Process Price
    BD40     Read change pointer for group
    BD41     Dispatch IDocs for group
    BD42     Check IDocs for group
    BD43     Post IDocs for group
    BD44     Assign Message Types to Serlz. Group
    BD47     Dependencies between methods
    BD48     Dependency method - message
    BD50     Activate Change Ptrs for Mess. Type
    BD51     Maintain function modules (inbound)
    BD52     Activ.change pointer per chng.doc.it
    BD53     Reduction of Message Types
    BD54     Maintaining Logical Systems
    BD55     Maintain IDoc Conversion
    BD55OLD     Maintain IDoc Conversion
    BD56     Maintain IDoc Segment Filters
    BD57     Maintain link and serialization ty.
    BD58     Convert organizational units
    BD59     Allocation object type -> IDoc type
    BD60     Additional data for message type
    BD61     Activate Change Pointers - Generally
    BD62     Define Segment Conversion Rule
    BD62OLD     Define Segment Conversion Rule
    BD63     Transport ALE Tables of Message Type
    BD64     Maintenance of Distribution Model
    BD65     Maintain IDoc type required fields
    BD66     IDoc type field -> change doc.field
    BD67     Maintain methods (inbound)
    BD68     Maintain Lists
    BD68OLD     Maintain Lists
    BD69     Assignment of Message Type to IDoc
    BD70     Synchronize Number Ranges
    BD71     Define FM for dependent bus. object
    BD72     Activate Events
    BD73     Reposting of IDocs (ALE)
    BD75     Convert IDoc Status
    BD77     Distribution of control data
    BD78     Monitoring control data distribution
    BD79     Maintain IDoc Conversion Rules
    BD79OLD     Maintain IDoc Conversion Rules
    BD81     Filter objects parameter filtering
    BD82     Generate Partner Profiles
    BD83     Send IDocs after an ALE error
    BD84     Post IDocs after ALE error
    BD85     Consistency check for transfer
    BD86     Consistency check for sales
    BD87     Status Monitor for ALE Messages
    BD89     Control data model. - initial screen
    BD91     Send Characteristic
    BD92     Send Class
    BD93     Send Classification
    BD95     Specify ALE object types
    BD96     filter objects of receiver determin.
    BD97     Assign RFC dest. to Logical Systems
    BD98     Consistency Check Workflow Connectn.
    BD99     Message type dependencies
    WE02     Display IDoc
    WE05     IDoc Lists
    WE06     Active IDoc monitoring
    WE07     IDoc statistics
    WE08     Status File Interface
    WE09     Search for IDocs by Content
    WE10     Search for IDoc in Archive
    WE11     Delete IDocs
    WE12     Test Modified Inbound File
    WE14     Test Outbound Processing
    WE15     Test Outbound Processing from MC
    WE16     Test Inbound File
    WE17     Test Status File
    WE18     Generate Status File
    WE19     Test tool
    WE20     Partner Profiles
    WE21     Port definition
    WE23     Verification of IDoc processing
    WE24     DefaultValuesForOutboundParameters
    WE27     DefaultValues for Inbound Parameters
    WE30     IDoc Type Development
    WE31     Development IDoc Segment
    WE32     Development IDoc View
    WE34     Object for Display of XML IDocs
    WE40     IDoc Administration
    WE41     Process codes, outbound
    WE42     Process codes, inbound
    WE43     Funct.module: Status record display
    WE44     Partner Types and Checks
    WE45     Forward (inbound) (V3, EDILOGADR)
    WE46     Error and Status Processing
    WE47     Status Maintenance
    WE50     System process codes: Texts
    WE51     System process codes: Change texts
    WE54     FMs for changing file names
    WE55     Function Module for Path Names
    WE56     IDoc Administration
    WE57     Assignment Messages for Appl. Objs
    WE58     Status process codes: Texts
    WE59     Change status process codes
    WE60     Documentation for IDoc types
    WE61     Documentation for IDoc record types
    WE62     Documentation for segments
    WE63     Documentation
    WE64     Documentation message types
    WE70     Conversion: Basic types
    WE71     Conversion: Extensions
    WE72     Conversion: IDoc types
    WE73     Conversion: Logical messages
    WE81     Logical message types
    WE82     Assign Messages for IDoc Type
    WE84     Assignment of IDoc and appl. fields
    WE85     Create Rule Names
    WEBU     Printing Labels via Assortment List
    WEDI     EDI Basis
    WEINBQUEUE     IDoc Inbound Queue
    WEKF     Purchase order SAP Retail
    WEL0     Forward (inbound) (EDILOGADR)
    WEL1     EDI: Interface Invoice for EDILOGADR
    WELI     Maintain Status Groups
    cheers!
    gyanaraj

  • IDOCS types in R/3 system

    Hi ,
       can you please let me know how many types of IDOCS are there in R/3 system.
    Thnx
    Andy

    Hi,
      The following are the types of IDocs
    General   -        Message types / IDoc types / BAPI
    Vendor    -        CREMAS / CREMAS02
    Customer  -        DEBMAS / DEBMAS03
    Accounting  -            Message types / IDoc types / BAPI
    G/L accoun  -            GLMAST / GLMAST01
    Cost center -            COSMAS / COSMAS01
    Cost element -            COELEM / COELEM01
    Cost center group -      COGRP1 / COGRP01
    Cost element group -     COGRP1 / COGRP01
    Activity type        -     COAMAS / COAMAS01
    Activity group     -     COGRP1 / COGRP01
    Activity price     -     COACTV / COACTV01
    Profit center      -     PRCMAS / PRCMAS01
    Profit center group -     COGRP1 / COGRP01
    Profit center account group - COGRP1 / COGRP01
    Logistics   -              Message types / IDoc types / BAPI
    Article master - ARTMAS / ARTMAS02 / RetailMaterial.Clone
    Additional -MMADDI / MMADDI01 /  RetailMaterial.SaveAdditionalReplicas
    Product catalog     -     PRDCAT / PRDCAT01
    Product catalog item -     PRDPOS / PRDPOS01
    Price list     -     PRICAT / PRICAT01
    Assortment     -      ASSORTMENT / ASSORTMENT01 / Assortment.SaveReplica
    Material master     - MATMAS / MATMAS03 - (See Template)
    Service master     - SRVMAS / SRVMAS01
    Characteristic     - CHRMAS / CHRMAS02
    Class          - CLSMAS / CLSMAS03
    Classification     - CLFMAS / CLFMAS01
    Document     - DOCMAS / DOCMAS04
    Purchasing info record - INFREC / INFREC01
    Conditions     -     COND_A / COND_A01
    Order book     -     SRCLST / SRCLST01
    Change master     -     ECMMAS / ECMMAS01
    Bill of material -     BOMMAT / BOMMAT01
    Document BOM     -     BOMDOC / BOMDOC01
    Work breakdown structure -      Project / PROJECT01
    Human Resources  -  Message types / IDoc types / BAPI
    PA object type person     -      HRMD_A / HRMD_A03
    PD object types          -      HRMD_A / HRMD_A03
    Basis       -          Message types / IDoc types / BAPI
    User master record - USERCLONE / USERCLONE01 / User.Clone
    Rgds,
    Jothivel.
    Note: Pls provide some valuable points if you are satisfied.
    Message was edited by: Jothivel Sundaram

  • IDOC Flow in IS Retail

    Hello Friends,
    Can anyone explain in detail, the entire process of the Inbound and Outbound IDOC flow in IS Retail. Atleast some pointers to understand the process of IDOC flow in IS Retail.
    This is required urgently. So am really looking forward for the same. Thank you all in Advance!!!
    Regards,
    Vinod Kapote.

    HI Vinod
    POS inbound & outbound processes are not single step process.. Hence i would suggest you to see the Best practice Building Block R33 in the below link which tells you step by step customization/Business Process needed for Store Connectivity.
    http://help.sap.com/bp_retailv1600/Retail_US/HTML/index.htm
    Go to the above link..Go to Implementation - Implementation tools - Building Block for retail - Download R33
    Store connectivity.
    You  need to maintain the following
    1.Define Logical Syatem
    2. Define Port in WE21
    3.Create Partner profile in WE20 , Maintain Message types
    4.Activate Chainge Pointers in Customization
    5.Create Inbound Profile
    6.Create Outbound Profile
    7.Create Assortment List Profile
    8. Assign the created profiles to Site Master POS Tab .WB02
    9. Maintain customization for Various inbound Process like Store order, Aggregated sales, receipt based sales, Physical Inventory,Goods Movement
    Regards
    Anis

  • Assortment list: Missing data values & structure modification

    Hello all,
    I have the following problem:
    1. I'm using the assortment list (not HPR version) with the structure WBBP_MAX to download data to the local system that is connected to a POS system. I know that this structure is a really massive one, but I'm planning to reduce it (see my number 2 question). The TC I'm using is WDBI\WDBM. Release version ECC6.
    When I'm executing the assortment list initialization\manual I have a missing values problem when displaying the AL for example: the purchasing prices (E1WBB08 - KWERT) appears in the generated Idoc (basic type WBBDLD04) but when I'm displaying the created assortment list, the values for the sales price do not appear . In additional, in the SAP Retail store, the sales price appear for the article overview option but in the store order\assortment list option the price do no appear.
    2. I want to create my own structure as a copy of structure WBBP_MAX. I've copied the structure and started mapping the fields I needed. My question is - is it enough to change the structure and assign the new structure to my AL profile or do I have to modify the RWDBBI_ALV program?
    Regards,
    Mikio

    This code works. How does your code differ in significant ways?
    <?xml version="1.0"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
      <mx:Script>
        <![CDATA[
          import mx.collections.ArrayCollection;
          [Bindable] private var ac:ArrayCollection = new ArrayCollection([
            {id: 1, label: "test1"},
            {id: 20, label: "test20"},
            {id: 3, label: "test3"},
            {id: 40, label: "test40"}
        ]]>
      </mx:Script>
      <mx:List dataProvider="{ac}">
        <mx:itemRenderer>
          <mx:Component>
            <mx:HBox>
              <mx:Label text="{data.id}"/>
              <mx:Label text="{data.label}"/>
            </mx:HBox>
          </mx:Component>
        </mx:itemRenderer>
      </mx:List>
    </mx:Application>
    If this post answers your question or helps, please mark it as such.
    Greg Lafrance - Flex 2 and 3 ACE certified
    www.ChikaraDev.com
    Flex / AIR Development, Training, and Support Services

  • Message WM014  -  Assortement by LSMW

    Hello,
    I want to integrate Assortement by LSMW in SAP ECC.
    At the end of the idoc generation, I have error messages:
    Module 000000010000000868 valable uniquement du 20140513 au 99991231
    (Module 000000010000000868 only avalable from 20140513 to 99991231)
    N° message WM014
    In the table WSOH,  I have all the modules which have a validaty date from today until 99991231
    And in my idoc, the assortement have an avaibility date from 20130101
    NB. At the beginning, my tables are empty.
    Thank you for your help
    Laura

    Thank you
    In the code WSO2,  the dates are from 13/05/2014 until 31/12/999
    NB. In my LSMW, some of my idocs are Ok and are in tables but other don't work and have the error message.
    However my idocs have the same range of dates and modules work for some articles but not for other articles.

  • LIKOND01 IDoc

    Hello Experts,
    We have a requirement of sending listing data (whether articles is listed or delisted) from ECC to a legacy system. We have analyzed the option os using LIKOND01, Assortment 01or WBBDLD03. We opted for LIKOND01 since it is lighter as compared to WBBDLD03. We tried to find the documents related to both of these IDocs in help.sap etc, but could not find any information accept the header and detail records. We just wanted to know how we can trigger this LIKOND01 IDoc in ECC and whether our approach will satisfy our needs.
    Any information in this regard will be appreciated.
    Thanks in advance!!
    Rakesh
    Edited by: rakeshjain_hit on Dec 30, 2010 9:25 AM

    Hello Venu,
    Thanks for your reply.
    LIKOND01.
    We will activate the necessary change pointers and other configurations.
    What we want to know that once the change pointers are activated the LIOKOND01 IDoc will be created as soon as the listing is done in ECC and entry created in WLK1 or we have to use some t-code. Can this be done?
    WBBDLD03
    We also tried to create the WBBDLD IDoc after creating a listing in ECC using transaction WDBU or WDBM, but could not.
    Please provide your input. I have also checked BD50 (whether it is Active) and BD52 also.
    Also i tried Automatic creation of Idoc of basic type WBBDLD, however i checked the FM MASTERIDOC_CREATE_WBBDLD, and when excecuting RBDMIDOC program with the messg type WBBDLD, i am getting a ABAP DUMP.
    Thanks in advance!!
    Rakesh
    Edited by: rakeshjain_hit on Jan 7, 2011 10:31 AM

Maybe you are looking for