Transfer Checkbox for 2LIS_02_ITM datasource

Hi Experts,
On enhancing 2LIS_02_ITM with 2 Z-fields and replicating to BI side, the transfer checkbox (5th column on fields tab of datasource display) in datasource is not enabled for these 2 fields and hence these fields are not available to be mapped to infosource.
Any ideas as to how to enable the checkbox.?
rgds
Deepak

Hi.
  Please use RSA6 to edit the datasource 2lis_02_scl and uncheck those 2 fileds you added in.
Best Regards
Martin Xie

Similar Messages

  • Unable to activate Transfer Structure for Generated Datasource in BW3.5

    HI Experts,
    We have a scenario where the data needs to moved from DSO A to Cube B
    we have clicked the Export datasource and created 8(ODS A)
    when created IP for this it gave us all selection in selection screen but we required only 3 Characters
    <br> so we maintained the export datasource and saved it when we again tried to generate datasource it went to short dump       
    <br> with following messages:
    <br>  Short text of error message:                                               
    <br>  Serious internal error:              <br>   
    <br><h4> Transfer structure got deactivated and we are unable to activate it again even by RS_TRANSTRU_ACTIVATE_ALL <br>
    </h2>
    <br>                                                                               
    <br>Technical information about the message:                                   
    <br>  Diagnosis                                                                 
    <br>     A serious internal error occurred. It could not be corrected.         
    <br>  Procedure                                                                 
    <br>      The following information is available on this error:                 
    <br>      1.                                                                    
    <br>       2.                                                                    
    <br>      3.                                                                    
      <br>     4.   OSS note                                                         
       <br>    Check the OSS for corresponding notes and create a new problem        
    <br>      message if necessary.                                                 
    <br>  Message classe...... "RSAR"                                                
    <br>  Number.............. 001                                                   
    <br>  Variable 1.......... " "                                                   
    <br>  Variable 2.......... " "                                                                               
    <br>Source Code Extract                                                                               
    <br>Line  SourceCde                                                                               
    <br> 514         IF g_subrc NE 0.                                                 
    <br>  515           MESSAGE x001.                                                  
    <br>  516         ENDIF.                                                           
    <br>  517 *       Check new version neccessary                                     
    <br>  518         l_curr_version = c_s_is_admin-odsversion.                        
    <br> 519                                                                          
    <br>  520         IF l_new_version EQ rs_c_true.                                   
    <br>  521           IF i_without_versioning EQ rs_c_true.                          
    <br>  522             MESSAGE e023 WITH c_s_is_admin-odsname_tech                  
    <br>  523                               c_s_is_admin-isource                       
    <br>  524                     RAISING no_psa_version_allowed.                      
    <br>  525 *         ELSEIF i_without_versioning EQ 'C' AND                         
    <br>  526 *                i_without_transport  EQ rs_c_true.                      
    <br>  527 *--         special handling for migration.                              
    <br>  528 *-          current system is target system no transport request         
    <br>  529 *-          necessary if a new version is needed                         
    <br>  530           ELSEIF i_without_versioning EQ 'C'        AND                  
    <br>  531                  i_without_transport  EQ rs_c_false.                     
    <br>  532             RAISE inconsistency.                                         
    <br>  533           ENDIF.                   .                                     
    <br> 534                                                                          
    <br>  535           IF i_objtype = rsa_c_istype-data.                              
    <br>  536 *           check type of InfoSource first                               
    <br>  537             SELECT SINGLE issrctype FROM rsis                            
    <br>  538                            INTO l_isrctype                               
    <br>  539                           WHERE isource = c_s_is_admin-isource           
    <br>  540                             AND objvers = rs_c_objvers-active.           
    <br> 541             IF sy-subrc <> 0 OR l_isrctype = rsarc_c_issrctype-ods.          
    <br> 542 *             if generated ODS InfoSource,                                   
    <br> 543 *             no PSA versioning possible                                     
    <br>>>>>               MESSAGE x001.                                                  
    <br> 545             ENDIF.                                                           
    <br> 546           ENDIF.                                                             
    <br> 547           l_next_version = l_curr_version + 1.                               
    <br>548           c_s_is_admin-odsversion = l_next_version.                          
    <br> 549           l_transtru_odsname+13(3) = l_next_version.                         
    <br> 550 *         Don't use old progname but create new one                          
    <br> 551           CLEAR l_progname_ods.                                              
    <br> 552         ELSE.                                                                
    <br> 553           l_next_version = l_curr_version.                                   
    <br>554         ENDIF.                                                               
    <br>555                                                                               
    <br> 556       ENDIF.                                                                 
    <br> 557 *     set transtru_names for IDoc                                            
    <br> 558       c_s_is_admin-odsname       = i_transtru_name.                          
    <br>559       c_s_is_admin-odsname_tech  = l_transtru_odsname.                       
    <br>560     WHEN OTHERS.                                                             
    <br> 561   ENDCASE.                                                                   
    <br> 562
    Edited by: Sachin Shankarrao Dehey on Oct 20, 2010 8:59 AM
    Edited by: Sachin Shankarrao Dehey on Oct 20, 2010 9:03 AM

    Hi,
    Delete all the DS and try creating from starting, to export DS, with correct selections, and then Activate the Transfer Structure..
    Hope Helps,
    Regards,
    Laj

  • Not getting transfer rules for 2LIS_02_HDR , 2LIS_02_ITM and 2LIS_02_SCL

    Hello Bi experts,
    Actually i am implementing standard Purchasing module in BI system.
    While implementing , i have installed cube 0PUR_C04 with data flow before options.
    After installation , i am not getting transfer rule for 2LIS_02_HDR , 2LIS_02_ITM and 2LIS_02_SCL .
    I am getting transfer rule for 2LIS_02_S011 only.
    0PUR_c04 contains these 4 dataspurces - 2LIS_02_HDR , 2LIS_02_ITM and 2LIS_02_SCL , 2LIS_02_S011 .
    So how can i get these transfer rule. and if we want to implement std Purchasing module in BI , which Cubes are required or necessary.
    In metadata repository also , for Cube 0PUR_c04 , it does not showing transfer rule HDR/ITM/SCL. there also it is now showing transfer rules.
    I will be also very thankful if anybody just give me overview of purchasing.
    Thanks,
    Sada.

    Hello Mani,
    Thanks a lot.you are the first one who has answered my que. which i expect .
    Look at following floe in infoprovider in my system. and please tell me what exactly i should do?
    Cube->Purchasing Groups                                                                                0PUR_C04
               Update Rule->0PUR_C04 2LIS_02_HDR                                                                       AY0XVMCJPXXXXXXXXXXXXXXXX
                                    Infosource->Purchasing Data (Document Header Level) as of 2.0B      2LIS_02_HDR
               Update Rule->0PUR_C04 2LIS_02_ITM                                                                         4YSO2PF9XXXXXXXXXXXXXXXXX
                                     INfosource->Purchasing Data (Document Item Level) as of 2.0B          2LIS_02_ITM
               Update Rule->0PUR_C04 2LIS_02_S011                                                                      CSB3FHGQXXXXXXXXXXXXXXXXX
                                     Infosurce->Purchasing groups                                                               2LIS_02_S011
                                                      Transfer Rule->from 2LIS_02_S011 for SC4 Client 600        2LIS_02_S011                  SCXCLNTXXX
                                                                             Datasource->Purchasing groups                    2LIS_02_S011
               Update Rule->0PUR_C04 2LIS_02_SCL                                                                        4ZZ0DMZXXXXXXXXXXXXXXXXXX
                                     Infosource->Pur.Data (Document Schedule Line Level)                         2LIS_02_SCL
    Mani i am expecting answer from you.
    Thanks,
    Sada

  • How to refer field of DataSource in transfer rule for DSO object  in BI 7.0

    hello Gurus,
    I am new to BI 7.
    pls tellme how to refer field of DataSource in transfer rule for DSO object.
    I will assign points to proper answer.
    Praveen.

    hi praveen,
    when u create the transformation for the DSO, it asks for the source. in that you enter your datasource, then you get the datasource fields on one side and the rules in the middle and the DSO objects on the other side. whichever field of DataSource you want to refer in tranformation rule, just connect that field to the rule for the required object of the DSO.
    hope this will help you.
    regards
    vaibhav

  • Error in creating RSDS using transfer rules for master data datasources

    Hi ,
    when i am creating the transfermations(RSDS) using transfer rules for master data datasources while i want to migrate datasource.it is giving the error message saying that INITIAL ERROR OCCURED DURING GENERATION OF THE TRANSFERMATION.AND in the taskbar it is giving the message LOG IS BEING LOADED.
    MY QUESTION IS HOW CAN WE SEE THE LOG? AND
    PLEASE GIVE ME THE STEPS TO MIGRATE MASTER DATASOURCES.
    THANKS IN ADVANCE .

    Hi Ankit,
                  Yoy have to load data to the cube.For that you need update rules.
    Steps to load data to the cube
    1.Replicate the datasource.
    2.Assign Infosource
    3.Create transfer rules
    4.Maintain the update rules to the cube.
    5.Right click on the datasource and schedule an infopackage for it.
    Execute the Infopackage and pull the data to the cube.
    Hope this helps
    Regards
    Karthik

  • Transfer Rules for 7.0 Datasource

    Hi All,
    I am trying to create Transfer rules for 7.0 Datasource, but i am not able to see the 7.0 datasource when i try to assign it to infosource, currently i am using DTP(and it works fine), but is there any way to avoid using DTP and use Transfer rules and update rules for 7.0 datasource?
    Thanks,
    Shetty.

    Hi,
    Probably BI7.0 datasouces are migrated so u have to again convert into 3.5 datasource using RSDS transaction.
    If u want to use 3.5 objects (Infosource) then just install in 3.x version then use that for u r transformation and BI7.0 objects let it be there there is no problem with that.
    Thanks,
    Debasish

  • DBIF_RSQL_INVALID_CURSOR : Error extracting records in RSA3 for 2LIS_02_ITM

    Hi
    I'm extracting the data in R/3 system using tcode RSA3 for transaction datasource (2LIS_02_ITM). When i extracted the transaction data , it was giving time out error. Then i went into debug mode to find the error. While debugging the code it gave me a DBIF_RSQL_INVALID_CURSOR short dump.
    NOTE : Data extraction is working for all 02 transaction data like 2LIS_02_SCL , 2LIS_02_S012. It s failing for only 2LIS_02_ITM only.
    I have pasted the eror message below for reference. Urgent help required.
    From
    Bobby
    ERROR MESSAGE DUMP for DBIF_RSQL_INVALID_CURSOR
    Runtime Errors         DBIF_RSQL_INVALID_CURSOR
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          09.04.2008 12:47:09
    Short text
    Invalid interruption of a database selection.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLMCEX" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    Unable to perform database selection fully.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
    in
    procedure "MCEX_BW_LO_API" "(FUNCTION)", nor was it propagated by a RAISING
    clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    One of the database selections included a database Commit.
    The selection was then supposed to continue. Before a
    database commit, however, all outstanding database selections
    must be concluded.
    Possible causes in the application program:
    While a read process from a database cursor is taking place
    (within a loop SELECT/LOOP/EXEC SQL or before a FETCH command),
    one of the following statements is used:
    - MESSAGE (apart from MESSAGE S...)
    - COMMIT WORK
    - ROLLBACK WORK
    - BREAK-POINT
    - WAIT
    - CALL FUNCTION ... DESTINATION (synchronous RFC)
    - CALL FUNCTION ... STARTING NEW TASK
    - RECEIVE RESULTS
    - CALL DIALOG
    - CALL SELECTION-SCREEN
    - CALL TRANSACTION
    - CALL SCREEN, or any other statement that results in the display of a
    new screen
    Whenever a program runs in debugging mode, a "COMMIT WORK" can
    possibly be triggered during database selection. This abnormal
    termination can also occur in debugging mode even with a correct
    program.
    A "COMMIT WORK" during debugging may be due to the following reasons:
    1. A program or screen was regenerated during debugging
    and updated in the database.
    2. Each user needs a separate process in debugging mode, but
    the number of available processes is restricted. If this
    limit is exceeded, each debugging step then requires a
    "COMMIT WORK".
    The error occurs in a statement in which the table "MC02M_0ITMSETUP " is
    accessed.
    Missing RAISING Clause in Interface
    Program                                 SAPLMCEX
    Include                                 LMCEXU06
    Row                                     1
    Module type                             (FUNCTION)
    Module Name                             MCEX_BW_LO_API
    Trigger Location of Exception
    Program                                 SAPLMCEX
    Include                                 LMCEXU06
    Row                                     220
    Module type                             (FUNCTION)
    Module Name                             MCEX_BW_LO_API
    Source Code Extract
    Line
    SourceCde
    190
    at end of fieldnm.                   "PI 2000.2 SP_353722
    191
    if not <fs_field> in cond_select_tab.
    192
    cond_select = false.
    193
    refresh cond_select_tab.         "PI 2000.2 SP_353722
    194
    exit.
    195
    endif.
    196
    refresh cond_select_tab.             "PI 2000.2 SP_353722
    197
    endat.                               "PI 2000.2 SP_353722
    198
    endloop.
    199
    if cond_select eq true.
    200
    append &2 to e_t_data.
    201
    add 1 to counter.
    202
    endif.
    203
    endloop.
    204
    if s_maximum_size le counter.
    205
    exit.
    206
    endif.
    207
    else.
    208
    close cursor g_cursor.
    209
    s_flg_no_more_data = true.
    210
    exit.
    211
    endif.
    212
    enddo.
    213
    END-OF-DEFINITION.
    214
    end macro *****
    215
    216
    CASE s_estruc.
    217
              extractstruc   internal table    setup table
    218
    *-- MM-PUR
    219
    sel 'MC02M_0HDR'   mc02m_0hdr_tab    mc02m_0hdrsetup.
    >>>>>
    sel 'MC02M_0ITM'   mc02m_0itm_tab    mc02m_0itmsetup.
    221
    sel 'MC02M_0SCL'   mc02m_0scl_tab    mc02m_0sclsetup.
    222
    sel 'MC02M_0SGR'   mc02m_0sgr_tab    mc02m_0sgrsetup.
    223
    sel 'MC02M_0SCN'   mc02m_0scn_tab    mc02m_0scnsetup.
    224
    sel 'MC02M_0CGR'   mc02m_0cgr_tab    mc02m_0cgrsetup.
    225
    sel 'MC02M_0ACC'   mc02m_0acc_tab    mc02m_0accsetup.
    226
    *-- Application '03' (Inventory Management)
    227
    sel 'MC03BF0'      mc03bf0_tab       mc03bf0setup.
    228
    sel 'MC03BX0'      mc03bx0_tab       mc03bx0setup.
    229
    sel 'MC03UM0'      mc03um0_tab       mc03um0setup.
    230
    *-- Application '04'
    231
    sel 'MC04P_0MAT'   mc04p_0mat_tab    mc04p_0matsetup.
    232
    sel 'MC04P_0ARB'   mc04p_0arb_tab    mc04p_0arbsetup.
    233
    sel 'MC04P_0COM'   mc04p_0com_tab    mc04p_0comsetup.
    234
    sel 'MC04PE0MAT'   mc04pe0mat_tab    mc04pe0matsetup.
    235
    sel 'MC04PE0ARB'   mc04pe0arb_tab    mc04pe0arbsetup.
    236
    sel 'MC04PE0COM'   mc04pe0com_tab    mc04pe0comsetup.
    237
    *-- Application '05' (Quality Management)
    238
    sel 'MC05Q1_0INSP' mc05q1_0insp_tab  mc05q1_inspsetup.
    239
    sel 'MC05Q2_0INSP' mc05q2_0insp_tab  mc05q2_inspsetup.

    Hi Bobby,
    Did you already find a solution for this 'issue'?
    I encounter the same problem. In my humble opinion this has nothing to do with the difference between structures.
    When loading data in normal modus, there is no problem. When loading in debug, there is an error.
    I also tested with other data sources and the same issue occurs there while nothing has changed.
    If someone knows how to solve this issue, please reply.
    Thanks!
    Kind regards,
    Bart

  • How can I activate the transfer rules for the ODS updating a data target.

    We are on BW 3.5 and I'm loading data into the 0FIGL_O10 ODS  and then uploading the data into the cube 0FIGL_C10. The data loads just fine to the ODS but when I try to <u><b>'update the data target'</b></u> I get a date & time stamp' error on the info-package transfer rules.
    I then Replicate the datasource 80FIGL_O01.
    I must then <u><b>'activate' the transfer rules</b></u>.
    However I cannot get the transfer rules for 80FIGL_O10 in CHANGE MODE to activate them.
    How can I activate the transfer rules for the ODS updating a data target.
    The error text is as follows:
    DataSource 80FIGL_O10 has to be replicated (time stamp, see long text)
    Message no. R3016
    Diagnosis
    DataSource 80FIGL_O10 does not have the same status as the source system in the Business Information Warehouse.
    The time stamp in the source system is 02/15/2007 10:42:33.
    The time stamp in the BW system is 11/07/2006 13:11:54.
    System response
    The load process has been terminated.
    <b>Procedure
    Copy the DataSource again and then activate the transfer rules that belong to it. You have to activate the transfer rules in every case, even if they are still active after the DataSource has been copied.</b>
    Thanks for your assistance.
    Denny

    Hi Dennis,
           Try, using Business Content to activate your data source
           hope this will help you
    How activate business content?
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a66d5e07211d2acb80000e829fbfe/frameset.htm

  • Error while installing transfer rules for 0PM_C03 from Business content

    Hi All,
    When i try to install the transfer rules for the Infocube 0PM_C03 from the Business Content, i get the following error:
    "Mapping between 2LIS_17_I3HDR  2LIS_17_ORDER is inconsistent".
    Here 2LIS_17_ORDER is the Infosource, and 2LIS_17_I3HDR  is the datasource.
    Also, kindly let me know how can the Infosource and the datasource have different names, like in the case for this Cube.
    Kindly help...

    Hi,
    The datasource and infosource can have different names no issue with that.
    and while selecting transfer rule for installing find with '2LIS_17_I3HDR'.
    Regards,
    Rathy

  • Default locale support for texts datasources

    Hi,
    I faced with problem - does BW support default locales ?
    I have some texts datasources which contain some list of entries for default locale. The question is - what value of LANGU field I should setup for  these entries in order to BW recognize them as for default locales ?
    Thanks. I will be apprecated for any related info.
    Fiodar.

    Hi Fiodar,
    well I am not sure about your requirement, but it sounds like you want to add a default value to langu in case the source system doesn't deliver it.
    If this is the case, create a update routine in your transfer rules for 0langu. In the routine add the following coding:
    if tran_structure-spras is initial. "no language specified
    usually the R/3-field is called spras
      result = sy-langu. "or a literal like 'EN' ...
    else.
    pass the given language to the result of the routine.
      result = tran_structure-spras.
    endif.
    That's it.
    In case your datasource doesn't even deliver a field for the language, you can just set a constant value to 0langu in your transfer rules.
    regards
    Siggi

  • No transfer rules for FI master data sources

    Hi all
    I didnt get transfer rules for some of the FI master datasources.
    0GLACCEXT_T011_HIER
    0NEG_POSTNG_TEXT
    0ITEMSELFLG_TEXT
    When I right click on datasource->create transfer rules->Only other option is enabled.WHen I say continue I am getting this error
    *Infosource(transaction data) is not known.
    How to resolve this isssue.
    Thanks.

    Double click on the data source and go to edit mode, system automatically provides the corresponding BI content infosources if  any and install the same.
    Not all the fields will be mapped with BI info objects.  Only necessary ones as defined in BI content will be available for you.
    If you feel the mapping is incomplete you can modify the same according to the requirement.
    Hope this helps.
    Regards,
    Rangz

  • Creating a transformation for delivered datasource 0TCTPRCSVAR_TEXT

    Hi,
    I am trying to set up my delivered technical content for the BI Administrator cockpit  (all the 0TCT... objects).  Everything is working well except for 4 datasources:
    0TCTBWOBJCT_ATTR
    0TCTBWOBJCT_TEXT
    0TCTPRCSVAR_ATTR
    0TCTPRCSVAR_TEXT
    While all other datasources have installed as version 3.x with associated transfer rules, these datasources have installed as version 7.0 with no transformations.
    I tried to create my own transformations, but for 0TCTPRCSVAR_TEXT there is no available field in the delivered data source to map to characteristic 0TCTPRCSTYP which is a compound of 0TCTPRCSVAR. 
    If I can't load the text for this object then in the BI Administrator cockpit all my DTPs, Infopackages etc display the technical name rather than the text description.
    I am running BW 7 patch 20 with BI_CONT 703 patch 13.
    Has anybody else met this?  Can anyone recommend how I can fill the 0TCTPRCSTYP value in a transformation from 0TCTPRCSVAR_TEXT?
    Thanks,
    Sue

    Hi,
    All the above mentioned 4 datasources have 3.x flow shipped as a part of content.
    go to tx: RSDS , enter the datasource name and from datasource tab at the top choose 'restore 3.x datasource'.
    This will now make them contain 3.x dataflows .
    and would therefore be loaded after scheduling them through process chains.
    Rgds,
    Chithra.

  • Enabling Early Delta Initialization option for LO DataSource 2LIS_06_INV

    Hi Guyz,
    I want to enable Earlt Delta Initialization option for LO DataSource 2LIS_06_INV, as of now its greyed out.
    please tell me if its possible or not, and if yes then please let me know the steps in detail.
    cheerz,
    raps.

    hi,
    Not all Data sources support Early Delta Initialization. Early delta initialization is done to capture the deltas when the initialization is being done between BW and source system (init with data transfer). As init with data transfer takes large time and during this time any records created will also be not captured so we do early delta initialization, also the same can be achieved by executing the init without data transfer and then loading a full repair request. The init without data transfer creats a time stamp and delta is generated for newly posted records.
    regards,
    Arvind.

  • Delta mechanism setting on R/3 side for a datasource from the FI area

    Hi,
    How to activate delta data transfer on the R/3 side for a FI related datasource?
    For sales and logistics related datasources, there's LBWE where you can activate the delta mechanism.
    I have a datasource called 'Committment line items for Funds Management' that comes under FI Management. What is the procedure to activate the delta mechanism for this datasource?
    Thanks
    Edited by: Sanjeev Koganti on Mar 21, 2008 2:07 PM

    Hi,
    Financial Accounting line items are read by extractors directly from the tables in SAP R/3.
    A time stamp on the line items serves to identify the status of the delta data.
    Time stamp intervals that have already been read are stored in a time stamp table.
    The delta dataset is transferred to BW directly, without records being transferred to the delta queue in SAP R/3 (extractor delta method).
    The FI Extractors are typically function module extractors. The function module for the extractors are as follows:
    0FI_TX_4 - BWFID_GET_FITAX_ITEM
    0FI_GL_4 - BWFID_GET_FIGL_ITEM
    0FI_GL_2 - FBIW_DATA_TRANSFER_GL_2
    0FI_GL_1 - FBIW_DATA_TRANSFER_GL_1
    0FI_AR_3 - FBW4_DATA_TRANSFER_AR_3
    0FI_AP_4 - BWFID_GET_FIAP_ITEM
    0FI_AP_3 - FBW4_DATA_TRANSFER_AP_3
    Refer.
    FI-SL Extraction
    http://www.jt77.com/business-warehouse/work-flow-13393.html
    http://www.saptutorials.com/list/1/,B,BW,xhtml
    Steps to move data from SAP r3 into BW
    http://www.jt77.com/business-warehouse-q/index20.html
    http://jt77.com/business-warehouse/work-flow-15111.html
    http://help.sap.com/saphelp_sm32/helpdata/en/f9/eb7641b61b5858e10000000a1550b0/RN_353_e.pdf
    CO-PA and FI-SL EXTRACTIONs
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/FISL/FISL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/66/bc7d2543c211d182b30000e829fbfe/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
    Re: Which tables for LO and FI...
    http://help.sap.com/saphelp_nw04/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
    Difference between FI and LO extraction
    Extraction Steps for FI Data Sources
    FI-GL Extraction steps
    Re: FI Extraction Steps
    http://help.sap.com/saphelp_bw32/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
    Thanks,
    JituK

  • VL06 / LT0S create Transfer Order for Multiple Deliveries

    Dear all,
    My customer is used to create a WM Transfer Order for multiple Deliveries with transaction LT0S. The group that is processed here was created with VL06 / subsequent functions/ Group / Create with WM reference / TO for Multiple Deliveries.
    -Currently I am trying to find a backway processing mode for this. Are Pickwaves a good alternative? Or will they generate TO' s per Delivery?
    -My concern is this: Creating ONE TO is essential to keep the the picking route. With multiple TO's I will lose this. Creation of the group mentioned in the menu path above requires manual input such as giving a name for the group and checking the checkbox TO. for Mult.Del.
    Thank you for your time.
    Sandeep

    Vinod,
    Thanks for taking the time.
    Have been able to have my Pick Waves generated in background jobs. However, not been able to process these Pick Waves in a single TO. Each delivery gets its own TO. So far Pick Waves have not proven to be an alternative to LT0s
    I have not been able to find a setting -like the checkbox in VL06 K Group with WM reference, TO for Multiple Deliveries- that enable me to have ONE TO per Pick Wave.
    Any suggestions?
    Thanks,
    Sandeep and Dave

Maybe you are looking for

  • IChat works but not when I want video chat?!

    Hi On my MBP the iChat work perfect, but on iMac does not want to go on video. Gives me an error and ask to be reported to Apple( which I do all the time). The network is the same, same firewall same 10.5.2. Anybody can give an idea. Thanks Message w

  • Presence status from iMessage not shown in Mail since Mavericks upgrade

    I'm re-posting this in the Mail folder, maybe somebody here knows the answer: https://discussions.apple.com/message/24928633#24928633

  • How to extract register names & their addresses from .inc file of a microcontroller

    Hi, I want to extract register names to a dropdown and their corresponding addresses from .inc file in such a way that when I select a register from dropdown, it has to also show its address in a string indicator. However, only a part of .inc file co

  • Why can't I update?

    Everytime I try to update I get the error message that there is "Another instance of Updater" running. This messages shows up whether I try to update from within the application or download the update (Adobe Bridge 4.0.5 and CameraRaw 6.4.1). Of cour

  • SPA122 - Unit locks up if calls made immediately after register

    I've run across an interesting issue. SPA 122 running Beta FW 1.2.0. If you attempt to make a call immediately after the line light comes on - unit registers to server - the box locks up. You cannot browse to it, and the line gets stuck with dial ton